Some time after the update (right after resuming) my GNOME (Wayland) session just quit on me. All of a sudden I was sitting in front of a black screen (Display port: no signal) and didn’t know what to do.
I quickly changed to a virtual terminal with Ctrl+Alt+F3 and the display came back with the terminal. When I switched back to the GNOME session with Ctrl+Alt+F2, it was working again. I’ve checked the journal and founds thousands of drmModeAtomicCommit gnome-shell error messages:
It seemed to have started right before a suspend and really went wild after the resume an hour later. Therefore I’ve added some additional journal entries right before the first error.
gsd-power[1725]: g_variant_new_string: assertion 'string != NULL' failed
gnome-shell[1596]: loading user theme: /home/USER/.local/share/themes/Custom-Accent-Colors/gnome-shell/gnome-shell.css
NetworkManager[804]: <info> [1743557273.4457] agent-manager: agent[8ec1e65200249bca,:1.78/org.gnome.Shell.NetworkAgent/1000]: agent registered
gsd-power[1725]: g_variant_new_string: assertion 'string != NULL' failed
gnome-shell[1596]: Page flip failed: drmModeAtomicCommit: Invalid argument
gnome-shell[1596]: Page flip failed: drmModeAtomicCommit: Invalid argument
systemd-logind[807]: The system will suspend now!
…
systemd[1]: systemd-suspend.service: Deactivated successfully.
systemd[1]: Finished System Suspend.
systemd[1]: Stopped target Sleep.
systemd[1]: Reached target Suspend.
systemd-logind[807]: Operation 'suspend' finished.
systemd[1]: Stopped target Suspend.
…
gnome-shell[1596]: crtc_frame->pending_update=0x7fa99c12b450, deadline_timer_state=2
gnome-shell[1596]: Cursor update failed: drmModeAtomicCommit: Device or resource busy
gnome-shell[1596]: Cursor update failed: drmModeAtomicCommit: Device or resource busy
gnome-shell[1596]: Cursor update failed: drmModeAtomicCommit: Device or resource busy
gnome-shell[1596]: Cursor update failed: drmModeAtomicCommit: Device or resource busy
…
gnome-shell[1596]: Cursor update failed: drmModeAtomicCommit: Device or resource busy
gnome-shell[1596]: Page flip failed: drmModeAtomicCommit: Device or resource busy
gnome-shell[1596]: Page flip failed: drmModeAtomicCommit: Device or resource busy
gnome-shell[1596]: Cursor update failed: drmModeAtomicCommit: Device or resource busy
gnome-shell[1596]: Cursor update failed: drmModeAtomicCommit: Device or resource busy
gnome-shell[1596]: Page flip failed: drmModeAtomicCommit: Device or resource busy
gnome-shell[1596]: Cursor update failed: drmModeAtomicCommit: Device or resource busy
…
gnome-shell[1596]: Page flip failed: drmModeAtomicCommit: Invalid argument
…
The error hasn’t happend since yesterday right after the switch to the virtual terminal and back. I’ve got no clue what to look out for or what caused the problem.
Another thing I noticed after the update is a display error in the GNOME shutdown menu top right.
I’ve selectively enabled/disabled all the pre-installed GNOME extensions. When I disable the “User Themes” extension, the strange button/glitch seems to disappear.
This is a theming issue, due to the Custom Accent Colors extension which is now deprecated and removed from the repositories.
It’s mentioned here.
And that seems a fair workaround. 
Regards.
4 Likes
The Custom Accent Colors extension has been removed from my system and I do have manjaro-gnome-settings installed. If you open the ‘User Themes’ settings there’s still a ‘Custom-Accent-Colors’ setting listed.
Should we uninstall gnome-shell-extensions? It wouldn’t let me though because ‘manjaro-gnome-settings’ is listed as a dependency.
By the way, I’m still having lots of these drmModeAtomicCommit errors. On the other hand I haven’t had the ‘User Themes’ extension disabled until now. Are these error message the result of this extension?
I watched the journal in realtime with journalctl -f and noticed the error messages popping up when hovering with the mouse like over the button in the shutdown menu. It might happen with all other windows as well. Not sure. All I see is thousand of these error message when moving the mouse.
EDIT:
Disabling ‘User Themes’ extension and rebooting didn’t help. I had nearly 10,000 drmModeAtomicCommit error messages in the last hour. I’m really desperate and don’t know what to do to fix it.
EDIT2:
This is really nervewracking. As soon as my monitor goes to sleep after 5 minutes (accordings to energy settings) journalctl -f starts generating drmModeAtomicCommit error messages.
In this state every mouse movement over the desktop seems to issue these error messages.
Only switching to a virtual terminal and switching back seems to fix it for a while.
Your posts have been moved to a dedicated Support thread.
Please rename the title to something that better suits your issue, and will hopefully attract quality responses from the Community.
I don’t use Gnome, but what I might do (in this order) is;
- Switch to one of the default global themes
- Uninstall
manjaro-gnome-extension-settings temporarily.
sudo pacman -Rns manjaro-gnome-extension-settings
- Uninstall
gnome-shell-extension-custom-accent-colors (as it’s still listed, it’s likely still installed).
sudo pacman -Rns gnome-shell-extension-custom-accent-colors
- Reinstall
manjaro-gnome-extension-settings if it’s needed.
sudo pacman -Syu manjaro-gnome-extension-settings
Again, this is only a guess. Other factors may be in play.
Regarding;
Frankly, I know little about how this function works, but I believe its part of the drm backend for kwin which somehow interacts with the kernel. 
I’m sure others might have some deeper insight.
Regards.
System Information
Output of this command (formatted according to forum requirements) may be useful for those wishing to help:
inxi --filter --verbosity=8
or the short form:
inxi -zv8
Be prepared to provide more information and outputs from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
Thanks for the dedicated Support thread.
Switch to one of the default global themes
I’m using the stock theme and haven’t meddled with the theme settings ever. I wouldn’t know where to change the theme. All I did in the GNOME settings dialog for Appearance was adding a background image. According to the gnome-tweaks app it could be Adwaita-dark we’re talking about.
Uninstall gnome-shell-extension-custom-accent-colors (as it’s still listed, it’s likely still installed).
It’s definitely uninstalled. I’ve checked:
sudo pacman -Rns gnome-shell-extension-custom-accent-colors
error: target not found: gnome-shell-extension-custom-accent-colors
Nevertheless, if I check the settings for the ‘User Themes’ extension, it still shows an entry for ‘Custom Accent Colors’ (which I’ve change to ‘Default’ even though the extension is disabled atm)
I also want to give a short little update of what I did (out of sheer desperation). As a result, the error message don’t show up at the moment but I’m not sure if it’s because of what I did.
I’ve switched to kernel 6.12.20-2-MANJARO from 6.6. and also did the small little upgrade yesterday for the new mutter version:
[ALPM] upgraded mutter (48.0-4.2 -> 48.1-1)
I’ll keep an eye on it and when the error message return, I’ll report back. 
I tend to take a minimalist approach to theming as well. With a nice looking theme already installed as a default, a wallpaper slideshow (Plasma option) is usually plenty of scenery for my taste.
Switching to User Themes Default rather than Custom-Accent-Colors probably helped in this case. If the extension was disabled, having it still selected in the GUI might have been contributing.
Be sure to post your system information as requested if the errors continue, and if they don’t return, remember to mark an appropriate solution to this topic.
Regards.