I found that when I applied this update, and also updated my kernel to 6.15.3-1 that my laptop battery was literally draining as I watched it - at least 1%/min with virtually nothing running. Reverting to the kernel that I previously used (6.12.34-1), whilst leaving the update in place, fixed the problem.
After installing and booting into linux615, nfs stopped to work properly. On remote system I’m constantly getting “Stale file handle”. I removed and recreated shares, rebooted both servers - same issue. But with linux612 everything works without any error. Is it known issue with 6.15?
I got the very same error message, and solved it by refreshing manjaro and arch keyring as mention here:
After reading https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/blob/master/ChangeLog.md?ref_type=heads#breaking-changes-2, it was still not clear to me what to do.
By trial and error I found that pacman complains about installing xkeyboard-config
if either the old location exists (/usr/share/X11/xkb/) or there are files in the new location (/usr/share/xkeyboard-config-2).
As I have a custom keyboard layout, I moved files to the new location
then used the pacman option --overwrite *xkeyboard-config-2*
.
This worked well: after the upgrade, my 10-year-old keyboard files were in the right place, and after reboot my custom layout was active as usual.
@j77h and anyone who may have missed it;
I have the same update error, and tried to rebuild the gpg keyrings without any luck.
After some googling, and from what i can understand reading Rebuild Todo List Rebuild all packages signed by daurnimator, It appears that the signing key used for ncdu
package expired in 01-07-2025, i.e. the time between the last Manjaro update and now.
I’m not sure, but i suspect that our problem will be solved with the next Manjiaro stable update that will include the rebuilt packages.
Normally there should be nothing to do as the archlinux-keyring-wkd-sync.timer
is enabled by default and refreshes weekly. However one could run the following to do a manual refresh:
sudo archlinux-keyring-wkd-sync
I didn’t miss that post, I quoted it.
After carefully studying all the links in it,
I wasn’t able to figure out exactly what it meant,
so I wrote to let people know that
both the old and the new location must be empty,
unless you want to --overwrite the new location, as I did.
Other methods are mentioned in that post,
but they involve things that I know nothing about.
@Yochanan thank you for the suggestion, i applied it but the error message persists.
For reference, this is what the forced refresh says about the key
Refreshing key 954A3772D62EF90E4B31FBC6C91A9911192C187A with UID daurnimator@archlinux.org...
pub rsa4096 2015-01-25 [SC] [expired: 2025-07-01]
954A3772D62EF90E4B31FBC6C91A9911192C187A
uid [ expired] Daurnimator <daurnimator@archlinux.org>
uid [ expired] Daurnimator <quae@daurnimator.com>
I had never had succes with the online refreshing. Why don’t you try the latest Offline packaged keys as per tutorial?
Errors about keys
Just initialize, do not refresh.
Have you tried refreshing the mirrors?
pamac update --no-aur --force-refresh
Thank you @Teo i followed the instructions that you pointed out (error about keys section) downloading and installing the packages. But this does not resolve the problem with the expired signature in the ncdu
package.
As of now i have tried three solutions:
- delete and clean build of gpg keys from repos using pacman (see the the first suggestion in this thread)
- forced gnupg keys refresh
- delete and clean build of gpg keys from downloaded packages and no forced refresh
At this point i’m fairly confident that the problem lies in the current ncdu
package and not in my system.
If that’s the case, i could simply wait for a future correctly signed one, i like ncdu
but it is not a deal breaker for me since all the other upgrades had gone smoothly.
@soundofthunder yes, i also made sure that the system clock and hardware clock were updated correctly. I tried to search for any problem in my installation but all seams to be correctly working.
Consider that i never skip any update. This time i waited 10 days instead of the usual 2.
Ah… I’m going to have to rebuild all Daurnimator’s packages for the stable branch since his key is expired.
EDIT: Rebuilds incoming; i.e., ncdu
2.8.2-2.0, etc.
Thanks! Installing ncdu
works now!
A post was split to a new topic: Should I downgrade Nvidia drivers?