Further to my above posts on VirtualBox, there is an issue with launching VMs. Trying to run a “saved” state VM results in this error:
VM Name: Manjaro-GNOME
GCM#0: Saved GCM fixer set 0X0 differs from the configured one (0X8). [ver=1 pass=final] (VERR_SSM_LOAD_CONFIG_MISMATCH).
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}
… and discarding the saved session doesn’t help; none of the other VMs will start either.
I’m looking into this; may put it in a separate thread if one doesn’t exist already.
Config file issue, by the looks of it. When I’ve fixed it, I’ll report back.
After a few hours logged in (seemingly a random time, though it appears to coincide with launching an application from a panel icon), my desktop freezes, with the mouse pointer changed to what shows when hovering over a link in a browser. The mouse pointer will move, but clicking anywhere has no effect; everything displayed freezes (so for example, the clock stays where it is).
Switching to a TTY and running plasmashell --replace has no effect, but hammering [ctrl][alt][backspace] successfully kills the session and sends me back to the SDDM login screen.
This is on Xorg (as I still can’t make Wayland work the way I need it).
Not something bad enough to open a new thread for, but notable enough to mention here: Ever since this update, KDE Plasma has occasional issues with the mouse when starting up or waking up from suspend, where one of two things happen: Either mouse sensitivity suddenly increases and moving the mouse a little causes the pointer to appear in random directions, and / or the pointer size becomes huge. Thankfully it’s easy to solve by reconnecting the mouse or goes away after writing your password, though this also happens in the login screen before logging in so the problem isn’t Wayland specific as I initially thought.
Related to that or not, waking up from standby is also a bit slower sometimes. Typically there used to be a black screen for some 5 seconds… now it can be a few seconds longer which I can live with, but once it was stuck for over half a minute and I was ready to presume it froze and do a harmful hard restart.
Found another issue, using OBS to capture games using pipewire window capture, the game freezes when in focus. The game losing focus makes it work again until it is in focus and locks up again, and removing the window capture or turning off obs makes the game work normally again. Was able to reproduce in Team Fortress 2 and Lethal Company.
In this latest update Manjaro introduced a meta package to deal with EOL kernels. Since the Linux kernel has two release versions (stable and lts) I was recommending that they create a meta package for the lts version as well.
Timeshift (again) stops working because Cronie Service got disabled (again). I remembered this post as a solution to reenable it – Timeshift-gtk not doing scheduled snapshots
Screenshot tools stopped working with error, but iris driver is present in the system MESA: error: Failed to query drm device. glx: failed to create dri3 screen failed to load driver: iris failed to open /dev/dri/card1: No such file or directory failed to load driver: iris
90% of the problems are the usual suspects. Nvidia and Plasma. I am not saying Plasma is an alpha quality software, no, it is beta quality. And as such it requires more manual work in a rolling release. Fortunately or not, it is very beautiful and trendy, so a great deal of newbie users start with it. The vast majority of which do not read announcements and wikis, so they have problems more often.
My cronie service is also happily running. I suggest @Deeleres you think what package that is not part of the default installation is messing with your services. Maybe something from AUR, or some custom hook?
No, cronie is not an on-demand service. It’s an old-fashioned daemon that runs from boot-up to shutdown.
Also, you can always create manual snapshots even when cronie is not running.
On my system, cronie is disabled because the only thing that depended on it is timeshift, and I don’t use timed backups. I always make manual backups, and I have just made three backups again in the last three days, all manually by way of the timeshift GUI.
And as such it requires more manual work in a rolling release. Fortunately or not, it is very beautiful and trendy, so a great deal of newbie users start with it. The vast majority of which do not read announcements and wikis, so they have problems more often.
