3 posts were split to a new topic: Xscreensaver no longer starts its daemon when I log in
This isn’t a manjaro issue at all but: I had w-okada rvc from github break (my install was done using python-conda from AUR, not anaconda or docker), I tried uninstalling all the AUR python stuff and re-installing it first (uninstall python-conda and then repeatedly uninstall orphans), but there is a problem with the AUR python-ninja package when I reinstall. I have generated a correct checksum for the package and was going to just change that in the build file, but I don’t want to try that till my monthly full system backup so instead:
The current solution for me was to timeshift back to before the update, update, then uninstall the 3 packages related to error for missing python packages (get error, uninstall, re-install the py package from AUR, get new error) the first 3 times i tried to run rvc, but NOT uninstall the AUR python-libmamba when I got:
Error while loading conda entry point: conda-libmamba-solver (No module named ‘libmambapy’)
Note: I did uninstall and reinstall conda-libmamba-solver from AUR I think that was the last one before it worked again, but if you uninstall the python-libmamba, when installing it again you get the python-ninja problem.
At least for me, rvc works as before despite the error message, but I haven’t tried adding models through the web interface, but if that doesn’t work, you can add them manually anyway.
I did also have the grub menu being hidden issue, but that was super simple, just GRUB_TIMEOUT_STYLE=menu in /etc/default/grub and then update-grub.
1 Like
That was also removed from mine. 
I issued the reboot, looked away to grab a drink and when I looked back it was already at the Desktop; I had to check the uptime to make sure I really had rebooted.
IMHO there should have been a .pacnew instead; changing things like this is a bit naughty. 
But then, I suppose, there’s the issue of all the people who don’t merge those.
EDIT:
The GRUB menu was appearing; I just missed it the first time. 
2 Likes
I am experiencing the same issue. Pamac started downloading normally (I used the TTY) and then seemed to stop - at least I got the output: “terminated” even though there were only about half of the packages downloaded. However, I noticed that pamac was still running in the background so I waited.
After several minutes my laptop stopped making noise so I ran “pamac checkupdates” and it gave me the output, that my system was up to date.
I will try rebooting now and see if the update worked out okay…fingers crossed!
Edit: I rebooted and everything seems to work fine 
Just as an info: I DID run sudo pacman -Sy libpamac before I started the update, but experienced the issue nevertheless…
1 Like
Since the update, LibreOffice is not working anymore… The same for both fresh and still versions.
When I call it, just flashes the welcome screen and stops.
If called from terminal, the output is:
The application cannot be started. The component manager is not available. ("premature end of file:///home/XXX/.config/libreoffice/4/user/uno_packages/cache/registry/com.sun.star.comp.deployment.component.PackageRegistryBackend/common.rdb")
Any ideas?
And after some uninstalling and reinstallin process, now the error read is:
terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException'
Remove this file or better whole /home/XXX/.config/libreoffice (make backup before if you have here something important). Probably you have installed some plugins that’s incompatible with new LO version.
2 Likes
Everything worked smoothly for me except that I had to uninstall-then-reinstall “Bottles” (the AUR version) and all of its orphans on all my computers to get that program to work again.
(I’d use the Flatpak version of “Bottles”, but that version has trouble accessing the local file system, which makes it useless for my needs. And recently Wine has been acting up badly, so it’s not an option. So I now use AUR Bottles for all my Windows emulation needs.)
I have problem with update onlyoffice 8.3.0
onlyoffice-desktopeditors not start
launch from terminal
QApplication: invalid style override passed, ignoring it.
(DesktopEditors:8849): GLib-CRITICAL **: 08:25:43.308: g_atomic_ref_count_dec: assertion ‘old_value > 0’ failed
zsh: segmentation fault (core dumped) onlyoffice-desktopeditors
to solve have downgrade to version 8.2.2
2 Likes
With Flatseal you can set permission for Flatpak packages and allow access to filesystem.
2 Likes
After the update was done, I rebooted and was under the impression that everything was fine. I was still running kernel 6.12 at the time. The only “new” thing I noticed were some unfamiliar log statements in journalctl:
Feb 08 15:55:15 amadeus-4 /usr/lib/gdm-wayland-session[1401]: discover_other_daemon: 1
Feb 08 18:05:32 amadeus-4 kernel: rtsx_pci 0000:02:00.0: Unable to change power state from D3hot to D0, device inaccessible
Feb 08 18:51:42 amadeus-4 kernel: amdgpu 0000:64:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Feb 08 18:51:43 amadeus-4 kernel: amdgpu 0000:64:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
But again, the system seemed to work fine. So I went ahead and installed kernel 6.13 and rebooted.
In journalctl, I noticed some other unfamiliar statements compared to those mentioned above with kernel 6.12:
Feb 08 18:58:21 amadeus-4 kernel: nvme nvme0: using unchecked data buffer
Feb 08 18:58:21 amadeus-4 gsd-usb-protect[1809]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
I continued to test everything until, when I tried to open a video file, the machine suddenly froze and I had to reboot.
Although I can somehow reproduce the freezes by trying to open certain files on my machine (sometimes immediately, sometimes after a few attempts) or even attaching such a file to an email in Thunderbird, there are no statements visible for those freezes in journalctl.
I just wanted to share that while I am now back to 6.12 and consider the update successful.
This is my system:
- Host: 21D4CTO1WW (ThinkPad Z16 Gen 1)
- Display (LEN4146): 3840x2400 @ 60 Hz (as 1920x1200) in 16" [Built-in]
- DE: GNOME 47.3
- WM: Mutter (Wayland)
- CPU: AMD Ryzen 5 PRO 6650H (12) @ 4.56 GHz
- GPU: AMD Radeon 680M [Integrated]
- Memory: 14.89 GiB
2 Likes
Hi,
I see issue on kernel 6.13, I use pipewire and wireplumber.
When I connect bluetooth headphones (Creative SoundBlaster Jam), they start with A2DP profile SBC codec.
Than when I need to run conversation on teams or something else I switch them to HSP/HFP profile mSBC codec.
On kernel 6.13 the switch to HSP/HFP works fine, but when I switch back, headphones are silent and require bluetooth reconnect to work again.
Journalctl output during the switch to HSP/HFP and back:
lut 08 14:31:00 stacjonarny kded6[10220]: org.kde.pulseaudio: No object for name "bluez_output.00_02_3C_77_9C_83.1"
lut 08 14:31:00 stacjonarny kdeconnectd[10858]: 2025-02-08T14:31:00 org.kde.pulseaudio: No object for name "bluez_output.00_02_3C_77_9C_83.1"
lut 08 14:31:00 stacjonarny plasmashell[10354]: org.kde.pulseaudio: No object for name "bluez_output.00_02_3C_77_9C_83.1"
lut 08 14:31:00 stacjonarny pipewire-pulse[10357]: mod.client-node: port (nil): set_param 4 0x605af5d0b708: Zły argument
lut 08 14:31:00 stacjonarny pipewire[7637]: pw.core: 0x6079fbc532a0: error -22 for resource 53: port_set_param(Spa:Enum:ParamId:Format) failed: Zły argument
lut 08 14:31:00 stacjonarny pipewire[7637]: mod.client-node: 0x6079fbff5030: error seq:2313 -22 (port_set_param(Spa:Enum:ParamId:Format) failed: Zły argument)
lut 08 14:31:08 stacjonarny kded6[10220]: org.kde.pulseaudio: No object for name "bluez_output.00_02_3C_77_9C_83.1"
lut 08 14:31:08 stacjonarny kdeconnectd[10858]: 2025-02-08T14:31:08 org.kde.pulseaudio: No object for name "bluez_output.00_02_3C_77_9C_83.1"
lut 08 14:31:08 stacjonarny plasmashell[10354]: org.kde.pulseaudio: No object for name "bluez_output.00_02_3C_77_9C_83.1"
On kernel 6.12 the switch back to A2DP works fine:
lut 08 14:34:20 stacjonarny kded6[10709]: org.kde.pulseaudio: No object for name "bluez_output.00_02_3C_77_9C_83.1"
lut 08 14:34:20 stacjonarny kdeconnectd[11172]: 2025-02-08T14:34:20 org.kde.pulseaudio: No object for name "bluez_output.00_02_3C_77_9C_83.1"
lut 08 14:34:20 stacjonarny plasmashell[10778]: org.kde.pulseaudio: No object for name "bluez_output.00_02_3C_77_9C_83.1"
lut 08 14:34:20 stacjonarny pipewire-pulse[10773]: mod.client-node: port (nil): set_param 4 0x582864b15bb8: Zły argument
lut 08 14:34:20 stacjonarny pipewire[8496]: pw.core: 0x5f9ca87e42a0: error -22 for resource 52: port_set_param(Spa:Enum:ParamId:Format) failed: Zły argument
lut 08 14:34:20 stacjonarny pipewire[8496]: mod.client-node: 0x5f9ca8b4d580: error seq:2517 -22 (port_set_param(Spa:Enum:ParamId:Format) failed: Zły argument)
lut 08 14:34:23 stacjonarny kded6[10709]: org.kde.pulseaudio: No object for name "bluez_output.00_02_3C_77_9C_83.1"
lut 08 14:34:23 stacjonarny kdeconnectd[11172]: 2025-02-08T14:34:23 org.kde.pulseaudio: No object for name "bluez_output.00_02_3C_77_9C_83.1"
lut 08 14:34:23 stacjonarny plasmashell[10778]: org.kde.pulseaudio: No object for name "bluez_output.00_02_3C_77_9C_83.1"
lut 08 14:34:26 stacjonarny wireplumber[8498]: pw.node: (bluez_output.00_02_3C_77_9C_83.1-72) graph xrun not-triggered (0 suppressed)
lut 08 14:34:26 stacjonarny wireplumber[8498]: pw.node: (-72) xrun state:0x7aeef2ca4008 pending:4/2 s:123128123198 a:123128175293 f:123128194771 waiting:52095 process:19478 status:triggered
Sorry that’s partially not in english, “Zły argument” means “Invalid argument”.
1 Like
@mikaka27 I would recommend sticking with 6.12 until these sort of bugs are fixed. Do you have any specific need to use 6.13 e.g. some feature(s) not in 6.12?
3 Likes
Not really, I can wait
2 Likes
I have no problem here, but from old experiences, I think that could be a Java or a graphic toolkit incompatibility.
See for example
https://bbs.archlinux.org/viewtopic.php?id=206869
https://bbs.archlinux.org/viewtopic.php?id=275263
https://bbs.archlinux.org/viewtopic.php?id=296128
Have you any AUR/foreign package installed that is related to java/graphic plugin? I used to have a problem like that due to an orphaned package lingering around…
Hello:
I am using Manjaro with Gnome. After this last update (performed without apparent problems) I’ve been working a couple of days where I suffered frequent crashes, at any time and doing anything, that would completely freeze my desktop and force me to hold down the power button to shut down my computer.
I was still using kernel 6.6 although I experienced the same problems with 6.12.
So far the only solution that allows me to work normally is to have used timeshift to go back to a restore point created before upgrading.
Before the restore I checked the information that journalctl could give me but found nothing relevant beyond some “system is too slow possibly due to some problem” (sorry, I didn’t take the message literally and after the restore I have lost the logs).
I have a feeling that the problem could be coming from some graphical stack update, but I don’t know where to investigate.
Anyone else with this problem, can anyone offer any suggestions on where to investigate?
Thanks
2 Likes
After the system update, Anki stopped working, throwing the error ModuleNotFoundError: No module named 'aqt'
Had to rebuild the AUR package with $ pamac build anki-bin and it fixed the issue.
1 Like
Same problem here. I have to install the old mesa (mesa-1:24.2.8-1-x86_64.pkg.tar.zst) and the old llvm-libs (llvm-libs-18.1.8-4-x86_64.pkg.tar.zst). That work for me.
1 Like
Yes, but there was no error logged, nor something unusual.
This is my first post, I hope I can give back some useful information to the community after I already found so much important information here.
I probably have the same problem. This had occurred from time to time over the last year, but seems to be much more frequent after the latest update (around twice a day). Over the course of all these crashes, I had the impression that they mostly happened when I used applications which use XWayland. I’m using Gnome with Wayland on a Ryzen mobile machine with Radeon 780M graphics.
I’m now trying an X11 session instead of Wayland, and it seems that this has improved the situation much. I didn’t have any crash in two days. Of course this is by far no proof, but at least it could be some hint…
If I get another crash during the next days, I’ll inform you 
2 Likes
2 posts were split to a new topic: Desktop icons have no name