I think is something with pamac. I do not use pacman to upgrade my system, I always use pamac using this command below.
pamac upgrade --force-refresh
To bypass these I have commented non-free repo and the upgrade was successful using the command posted earlier. After reboot, I have uncommented the non-free repo and tried again the same command to upgrade the mesa with non-free mesa and surprise the same error regarding invalid signature.
Then I have tried again the command but without –force-refresh and what are you known, It worked by ignoring the signature error.
Maybe can someone light me, what I must to do to make it work when I use pamac upgrade --force-refresh…
You can’t partially update if you use Nvidia drivers. Well if you don’t use the binary modules for the kernels and use dkms then you might, if you find the old binaries for that or compile them yourself from our sources.
As i was reading, i can confirm i too “lost” my secondary monitor setting after a reboot-
Altough, i found out they were not lost, but Plasma detected the secondary monitor as a new one.
The settings for the monitor are still present when entering “edit mode” > “manage desktop and panels” under “disconnected monitor X” , you click on the hamburger menu of the panel you want and just "move it to [fullname of the monitor] and then delete the disconnected monitor.
Another really minor issue is that icon sizes in my main bar are a bit weird, but after changing the setting they got fine.
GRUB_DEFAULT=saved
GRUB_TIMEOUT=10
GRUB_TIMEOUT_STYLE=hidden
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet lsm=lockdown,yama,apparmor,bpf"
GRUB_CMDLINE_LINUX="cryptdevice=/dev/nvme0n1p2:mytlscryptvg root=/dev/mytlscryptvg/root resume=/dev/mytlscryptvg/swap"
# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
#GRUB_SAVEDEFAULT=true
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable booting from LUKS encrypted devices
GRUB_ENABLE_CRYPTODISK=y
@Grimmzz You may just need to add cryptodisk to this line GRUB_PRELOAD_MODULES="part_gpt part_msdos" as first entry and call update-grub once. Else read thru the article @ruziel pointed at. Also this is linked in the first post and second post already.
After the update all of my 3 monitors finally work as intended.
HDMI audio disappeared at first, but then I found out that my system now has two HDMI profiles. I switched to HDMI 2 and audio is working again.
Haven’t found any new bugs yet.
So update went surprisingly well for me.
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.
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
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
Solution:
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.
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
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!
