So far it worked for me too. Back to mesa-1:24.2.8-1 and llvm-libs-18.1.8-4.
Now, waiting until the next version or fix.
Thank you very much, @Mufflon
Hmmm… just noticed: pamac-gui icon got dark mode all alone:
I updated now and came across the same ‘user@1000.service’ error described by a bunch of other users.
[2025-02-12T01:27:24+0100] [ALPM] running '30-systemd-daemon-reload-user.hook'...
[2025-02-12T01:28:54+0100] [ALPM-SCRIPTLET] Job for user@1000.service failed because the control process exited with error code.
[2025-02-12T01:28:54+0100] [ALPM-SCRIPTLET] See "systemctl status user@1000.service" and "journalctl -xeu user@1000.service" for details.
systemctl status user@1000.service
x user@1000.service - User Manager for UID 1000
Loaded: loaded (/usr/lib/systemd/system/user@.service; static)
Drop-In: /usr/lib/systemd/system/user@.service.d
`-10-login-barrier.conf
Active: failed (Result: exit-code) since Wed 2025-02-12 01:28:54 CET; 13min ago
Duration: 12min 22.767s
Invocation: 33dfd3ec47ba44beab80a9a9b6df19f5
Docs: man:user@.service(5)
Process: 22219 ExecStart=/usr/lib/systemd/systemd --user (code=exited, status=1/FAILURE)
Main PID: 22219 (code=exited, status=1/FAILURE)
Status: "Ready."
Error: code: 71 (Protocol error)
Mem peak: 14.2M
CPU: 397ms
Feb 12 01:26:41 computer systemd-xdg-autostart-generator[25616]: /home/USER/.config/autostart/manjaro-starter.desktop: not generating unit, executable specified in Exec= does not exist.
Feb 12 01:26:41 computer systemd[1]: Reloaded User Manager for UID 1000.
Feb 12 01:27:24 computer systemd[1]: Reloading User Manager for UID 1000...
Feb 12 01:27:24 computer systemd[22219]: Received SIGRTMIN+25 from PID 1 (systemd).
Feb 12 01:27:24 computer systemd[22219]: Reexecuting.
Feb 12 01:28:54 computer systemd[1]: user@1000.service: Reload operation timed out. Killing reload process.
Feb 12 01:28:54 computer systemd[1]: user@1000.service: Main process exited, code=exited, status=1/FAILURE
Feb 12 01:28:54 computer systemd[1]: user@1000.service: Killing process 22229 (appimagelaunche) with signal SIGKILL.
Feb 12 01:28:54 computer systemd[1]: user@1000.service: Failed with result 'exit-code'.
Feb 12 01:28:54 computer systemd[1]: Reload failed for User Manager for UID 1000.
I didn’t notice any problems after reboot though. Same goes for the error
pkill: not a hex string:
I’ve got problems rebuilding python packages due to the upgrade to version 3.13.
pacman -Qoq /usr/lib/python3.12/ lists several packages:
list of packages
caffeine-ng
clang15
pyside2
python-anyascii
python-cssutils
python-ewmh
python-future
python-mock
python-pulsectl
python-random2
python-shiboken2
python-yapsy
vorta-git
If I try to build them with pamac, it only returns an error message:
Error: target not found: python-random2
Nothing else happens and another search returns the same list of packages afterwards.
@mezzo mentions problems with ‘python-future’ in his post but apart from mentioned incompatibility issues there’s no further instructions on how to fix the problem. Any tips on how to fix the issue?
I can’t seem to find ‘python-random2’ in the Arch Linux AUR package database.
It appears almost all of those package are all orphans and/or unneeded. By the way, vorta is in the repos now, so that can replace vorta-git.
Since your profile says you’re using GNOME, I recommend gnome-shell-extension-caffeine instead of caffeine-ng.
If you still want caffeine-ng (dropped from the repos back to the AUR), you’ll need to rebuild python-ewmh & python-pulsectl first.
1 Like
I had no idea what caffeine-ng was and I didn’t install it deliberately. I’ve uninstalled it now. Thanks for the tip with vorta. 
I’ll take a closer look at the other python packages and try to determine whether they’re orphaned. If yes, I’ll try to uninstall them.
EDIT:
I switched from vorta.git to the one in the repositories and also was able to remove all those orphaned python packages by checking every one of them with pacman -Qi package for optional dependencies. pacman -Qoq /usr/lib/python3.12/ doesn’t list any more packages. Nice. 
A post was split to a new topic: Baikal log-in issue following update
3 posts were split to a new topic: After update, desktop background applied to workspace 1 only
7 posts were split to a new topic: Python prominence in Update announcements
2 posts were split to a new topic: Double Commander issues
RustDesk is another possibility, but may require some hands-on setup.
Could it be that the Manjaro 6.13 kernel suffers from the fuse problem mentioned in this video about the Arch Linux 6.13 and 6.13.1 kernels? The problems I experience with the 6.13 kernels and Flatpak apps are pretty much the same.
It is possible, the fuse problem overlaps with the one I reported here about Flatpak installation before it was reported upstream.
1 Like
New update… This will be closed soon.
1 Like