mine boots fine w/out this
mine boots fine w/out this
After the update, I’m getting the dreaded
[amdgpu]] *ERROR* ring gfx_0.0.0 timeout error on my AMD 5700XT every time I try to do something 3D related, like Blender, ParaView, or games. On X11 this causes my session to terminate. On Wayland it just hangs.
Haven’t found a solution yet.
I just update my second older computer running an even newer install of Manjaro KDE. Running Kernel 6.2.8-1 with no AUR enabled. I oddly enough got the same error messages as my previous post.
Might this be something to do with using the Unites_States mirrors in Pamac?
Pamac error message upon 3-31-2023 updates finished installing:
Error while configuring manjaro-keyring Error while configuring manjaro-keyring Error while configuring manjaro-keyring Error while configuring manjaro-keyring Error while configuring manjaro-keyring Error while configuring manjaro-keyring Error while configuring manjaro-keyring Error while configuring manjaro-keyring A restart is required for the changes to take effect.
/var/log/pacman.logs relevant error messages:
[2023-04-01T10:35:49-0400] [ALPM] transaction started [2023-04-01T10:35:49-0400] [ALPM] upgraded archlinux-keyring (20230130-1 -> 20230320-1) [2023-04-01T10:35:49-0400] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg... [2023-04-01T10:35:56-0400] [ALPM-SCRIPTLET] ==> Updating trust database... [2023-04-01T10:35:56-0400] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2023-07-07 [2023-04-01T10:35:56-0400] [ALPM-SCRIPTLET] ==> Updating trust database... [2023-04-01T10:35:56-0400] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2023-07-07 [2023-04-01T10:35:57-0400] [ALPM] upgraded manjaro-keyring (20221028-4 -> 20230318-1) [2023-04-01T10:35:57-0400] [ALPM-SCRIPTLET] ==> Appending keys from manjaro.gpg... [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] ==> Locally signing trusted keys in keyring... [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] -> Locally signed 2 keys. [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] ==> Importing owner trust values... [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] ==> Disabling revoked keys in keyring... [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] -> Disabled 8 keys. [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] ==> Updating trust database... [2023-04-01T10:35:59-0400] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2023-07-07 [2023-04-01T10:35:59-0400] [ALPM] transaction completed
After the update, gdm shows up as an orphan in pamac GUI. Removing it apparently put me in cmd-line at boot.
Mark it as explicitly installed:
sudo pacman -D --asexplicit gdm
In the future, be more careful about removing orphans.
My issue with this update:
I was running the old linux60 kernels (that aren’t supported anymore but I was unaware because I forgot to check) and when updating something went wrong with the kernels and GDM.
I was made aware of the fact today, when the screen lock activated when I was AFK for a while. The DM was throwing an error and not giving me the option to enter a password and unlock.
I rebooted and reached a tty. I logged in from there and using startx I could log in to a GUI.
I researched the forums extensively to understand what was wrong.
- Old not supported kernel still active
I cleaned up the kernels (I am now on linux62) and but the issue was there again.
I tried a systemctl on GDM and an error occurred stating there was no GDM, I, therefore, installed and enabled GDM following this guide in the Wiki, and my laptop boots correctly and GDM works.
For some reason being on older kernels when updating deleted GDM from my system or an older version was still there active and prevented the new one to work even if I had the new latest kernel.
Note to self, always check kernels before upgrading and read the release notes so that you know what to expect.
There it is. I did remove the orphans! So in fact it was me who removed it… unwillingly. Thanks @kevin77 for this explanation on how it was magically gone.
Can the maintainers of Manjaro please confirm clearly that the solution about disk encryption error provided by Skunkie: [Unstable Update] 2023-02-17 - Plasma 5.27 LTS, GNOME, Python - #50 by Skunkie
Is the final/working solution?
Many of us are not technical or semi-technical and asking us to run
sudo commands to GRUB at the risk of borking our machines requires some assurances from the maintainers.
A clear outline for what people should do if they are on GRUB or UEFI is required here.
- How do we check if GRUB or UEFI?
- If GRUB, do what?
- If UEFI, do what?
- Does the DE matter? Does this apply to all DEs (KDE, etc.)
A clear & final solution that works and not “might work”, please!
I’ve got an Issue with VirtualBox which is not starting any virtual machine since the Update.
Was running fine with Kernel 6.2.7 , is running fine with kernel 6.1.21, but is not running with kernel 6.2.8.
Something with kernel driver error, sorry didn’t write down the exact message.
Switched back to 6.1 and now everything is running fine again.
the system has updated smoothly (manjaro gnome) but i found out that after restart the headphone doesn’t work unless i unplug it and plug it again .
i found the solution in the forum
the title : [Dell Laptop: Analog Speaker Audio only after plugging and unplugging headphones]
the link :
the solution is deleting your pulseaudio user settings
rm ~/.config/pulse/cookie ~/.config/pulse/*.tdb
I allowed myself to edit the wiki post in order to clarify the two points regarding GRUB, if anyone wants to double check me.
Great operating system, smooth update. Thanks for everything. The combination of Plasma and Manjaro has proved stellar. Come on everyone, consider donating to Manjaro on a regular basis. I have been a supporter 5 for the last months for the price of two espressos a month. Small price to pay for a great system!
so this is why i now don’t have my desktop anymore?
Automatically removing orphans could lead to problems, list them out and do it manually, it’s only a bit of time but could potentially save you time.
A post was split to a new topic: Davinci Resolve: gpu init failed, cannot find opengl
I’m getting a systemd error on boot after the update:
Failed to insert module 'nvidia_uvm': No such device
System continues on afterwards and finishes booting.
For background, I am using vfio-pci to stub out my nvidia card for GPU passthrough to a VM. I don’t need to load any drivers for it.
lspci -nnk shows these drivers are correctly in-use for the video card.
EDIT: I simply added nvidia, nvidia-drm, and nvidia-uvm to the blacklist, restarted systemd-modules-load successfully.
Also for some feedback on the LUKS encrypted drive solution, I ran update-grub and grub-install after adding the cryptodisk module to the grub config. Didn’t rerun mkinitcpio however since it didn’t make sense to me do so (the pacman hooks already run this, and the grub config doesn’t affect the kernel images). Rebooted fine save for the one error message.
May I make a suggestion for the partition scheme?
It is very nice that Manjaro includes Plymouth again. Plymouth CAN be particularly useful if the root partition is encrypted - because the graphical password prompt has a few advantages over the simple text input. (It also just looks better…)
In order for the graphical password prompt to work with EFI we need actually an unencrypted /boot-partition in addition the unencrypted /boot/efi and /root partitions.
I know there is supposed to be a potential security vulnerability with an unencrypted /boot. I’m not sure what it is, but other otherwise professional distributions (Fedora, Ubuntu, …) do this as well. So maybe this would be a nice addition to the installer for Manjaro?
I read the comments about Grub and blocked it for now. Than the update went smooth.
Thanks to that Great Community and the Manjaro Team.
It’s for sure a great job of the team to deal with all that hardware out there.
A Backup on a 1TB SSD before major updates is done in 15 minutes, no big deal at all and Timeshift should be active for the root partition anyway!
Among the Arch forks, I still believe that Manjaro is the best choice concerning “user friendliness”.
Long live Manjaro
I am still having an issue with grub. I followed the solution for grub with LUKS and am left with a grub_debug_malloc not found error and dropped into grub rescue.
I followed solutions from
Decided to revert to pre 3.31 until this can be solved.
I had the issue with grub that went into rescue mode, but I was able to start the live ISO and chroot and fix the grub installation.
Update /etc/default/grub config to add cryptodisk module
GRUB_PRELOAD_MODULES="cryptodisk part_gpt part_msdos"
Then apply changes
sudo mkinitcpio -P
sudo grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=manjaro # as I use UEFI and my ESP is /boot (where my EFI folder is located i.e: /boot/EFI)
After fixing the boot, I had to edit the desktops in edit mode → manage desktops and panels.
Somehow I had several panels in one desktop, and the secondary was swapped with a fresh config.
Also it seems that Wayland still have issues with nvidia on 5.27, so I’ll keep x11 for now
Noticed a new issue after the update: when I disconnect my displayport monitor, plasmashell segfaults and is restarted by systemd. System info:
Operating System: Manjaro Linux KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 5.10.176-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i5-10600K CPU @ 4.10GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C75 System Version: 1.0
Before plasmashell crashes I see this in the journal logs:
kwin_x11: kwin_core: Parse error in tiles configuration for monitor "5b7a5ba4-43cc-5910-8e98-f358f9d54b43" : "illegal value" Creating default setup
I have 1 DP monitor, and 1 HDMI. No crashes if I turn off the HDMI monitor, only happens with displayport. Also occurs if I switch the DP monitor to another input.
EDIT: SOLVED. I added an entry to ~/.config/kwinrc with the “ghost” monitor uuid:
No more segfaults!