Gnome not quite stable on X11 with NVIDIA

I have been running gnome on X11 with the nvidia G06 driver. The card is a GeForce GT 1030.

At first glance, it works as well as it did on Leap 15.4 or Debian Bookworm (aka Debian 12). I skipped Leap 15.5.

  1. The first noticeable issue is some video breakage in full screen playback about 15 to 20 percent from the top. I have only used mpv thus far.

  2. The second issue is that gnome will become sluggish and unstable. For example, executing a file save from chrome, I might have to wait minutes before the file save dialogue resolves. Eventually, gnome will crash. As far as I can remember, all of the crashes over the last couple of weeks have been triggered by writing to disk.

  3. The third issue, and the most reliable way to cause a crash, is write files with avidemux3-qt5. Using avidemux to write a file, gnome will eventually crash!

A snippet from the logs from yesterday morning, when gnome crashed while writing a file from avidemux. (The system appeared completely stable prior to the crash, none of the sluggishness I described in 2)

ul 12 07:01:06 orca.attlocal.net org.avidemux.Avidemux.desktop[20054]: [FF] Saving
Jul 12 07:01:06 orca.attlocal.net org.avidemux.Avidemux.desktop[20054]:  [saveLoop] 12:01:06-735  avg fps=30000
Jul 12 07:01:06 orca.attlocal.net org.avidemux.Avidemux.desktop[20054]:  [initUI] 12:01:06-735  Muxer, creating UI, video duration is 00:13:06,000
Jul 12 07:01:06 orca.attlocal.net org.avidemux.Avidemux.desktop[20054]:  [qtRegisterDialog] 12:01:06-736  reparenting widget encodingDialog
Jul 12 07:01:06 orca.attlocal.net org.avidemux.Avidemux.desktop[20054]: [muxerFFmpeg::saveLoop] Final audio delay: 0 ms
Jul 12 07:01:06 orca.attlocal.net gnome-shell[16739]: **
Jul 12 07:01:06 orca.attlocal.net gnome-shell[16739]: libmutter:ERROR:../src/core/window.c:1529:meta_window_unmanage: assertion failed: (window->display->focus_window != window)
Jul 12 07:01:06 orca.attlocal.net gnome-shell[16739]: Bail out! libmutter:ERROR:../src/core/window.c:1529:meta_window_unmanage: assertion failed: (window->display->focus_window != window)
Jul 12 07:01:06 orca.attlocal.net gnome-shell[16739]: == Stack trace for context 0x563d731fcba0 ==
Jul 12 07:01:06 orca.attlocal.net gnome-shell[16739]: #0   563d732e3288 i   resource:///org/gnome/shell/ui/init.js:21 (17bd02a70ba0 @ 48)
Jul 12 07:01:06 orca.attlocal.net polkitd[2566]: Unregistered Authentication Agent for unix-session:14 (system bus name :1.1143, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from b>
Jul 12 07:01:06 orca.attlocal.net systemd[16279]: org.gnome.Shell@x11.service: Main process exited, code=dumped, status=6/ABRT
Jul 12 07:01:06 orca.attlocal.net gnome-terminal-[20355]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
Jul 12 07:01:06 orca.attlocal.net systemd[16279]: org.gnome.Shell@x11.service: Failed with result 'core-dump'.
Jul 12 07:01:06 orca.attlocal.net systemd[16279]: org.gnome.Shell@x11.service: Triggering OnFailure= dependencies.
Jul 12 07:01:06 orca.attlocal.net systemd[16279]: org.gnome.Shell@x11.service: Consumed 27min 51.978s CPU time.
Jul 12 07:01:06 orca.attlocal.net systemd[16279]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 1.
Jul 12 07:01:06 orca.attlocal.net systemd[16279]: Started GNOME Session Failed lockdown screen (user).
Jul 12 07:01:06 orca.attlocal.net systemd[16279]: Reached target GNOME Session Failed.
Jul 12 07:01:06 orca.attlocal.net systemd[16279]: Disable GNOME Shell extensions after failure was skipped because of an unmet condition check (ConditionPathExists=/run/user/1000/gnome-shell-disable-extensions).
Jul 12 07:01:06 orca.attlocal.net systemd[16279]: Starting GNOME Shell on X11...
Jul 12 07:01:06 orca.attlocal.net gnome-shell[28928]: Running GNOME Shell (using mutter 45.3) as a X11 window and compositing manager
Jul 12 07:01:07 orca.attlocal.net /usr/lib/gdm/gdm-x-session[16500]: (--) NVIDIA(GPU-0): DFP-0: disconnected
Jul 12 07:01:07 orca.attlocal.net /usr/lib/gdm/gdm-x-session[16500]: (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
Jul 12 07:01:07 orca.attlocal.net /usr/lib/gdm/gdm-x-session[16500]: (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
Jul 12 07:01:07 orca.attlocal.net /usr/lib/gdm/gdm-x-session[16500]: (--) NVIDIA(GPU-0):
Jul 12 07:01:07 orca.attlocal.net /usr/lib/gdm/gdm-x-session[16500]: (--) NVIDIA(GPU-0): BenQ PD2500Q (DFP-1): connected
Jul 12 07:01:07 orca.attlocal.net /usr/lib/gdm/gdm-x-session[16500]: (--) NVIDIA(GPU-0): BenQ PD2500Q (DFP-1): Internal TMDS
Jul 12 07:01:07 orca.attlocal.net /usr/lib/gdm/gdm-x-session[16500]: (--) NVIDIA(GPU-0): BenQ PD2500Q (DFP-1): 600.0 MHz maximum pixel clock
Jul 12 07:01:07 orca.attlocal.net /usr/lib/gdm/gdm-x-session[16500]: (--) NVIDIA(GPU-0):
Jul 12 07:01:07 orca.attlocal.net gsd-media-keys[16831]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/gnome/Shell”
Jul 12 07:01:07 orca.attlocal.net gnome-shell[28928]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1c00006 specified for 0x1c0d612.
Jul 12 07:01:08 orca.attlocal.net gnome-shell[28928]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
Jul 12 07:01:08 orca.attlocal.net gnome-shell[28928]: Will monitor session 14
Jul 12 07:01:08 orca.attlocal.net gsd-media-keys[16831]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/gnome/Shell”

The problem appears to be is mutter.

For the time being, I am running gnome on wayland. I hope to use avidemux quite a bit today to learn if the problem extends to wayland or is limited to X11.

Are you an Orca user? All those log messages you pasted come from it. If you are not, it should be removed or disabled.

Hello,

The posted log comes from the “journalctl” command. “orca” in the log signifies the hostname, not the application.

ox@orca$ hostname
orca.attlocal.net
ox@orca$

I do have the orca screen reader installed as it is automatically installed by default with gnome, but I have never used it.

The most relevant part of the posted log edited down a bit:

org.avidemux.Avidemux.desktop[20054]: [muxerFFmpeg::saveLoop] Final audio delay: 0 ms
gnome-shell[16739]: **
gnome-shell[16739]: libmutter:ERROR:../src/core/window.c:1529:meta_window_unmanage: assertion failed: (window->display->focus_window != window)
gnome-shell[16739]: Bail out! libmutter:ERROR:../src/core/window.c:1529:meta_window_unmanage: assertion failed: (window->display->focus_window != window)
gnome-shell[16739]: == Stack trace for context 0x563d731fcba0 ==
gnome-shell[16739]: #0   563d732e3288 i   resource:///org/gnome/shell/ui/init.js:21 (17bd02a70ba0 @ 48)
polkitd[2566]: Unregistered Authentication Agent for unix-session:14 (system bus name :1.1143, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from b>
systemd[16279]: org.gnome.Shell@x11.service: Main process exited, code=dumped, status=6/ABRT
gnome-terminal-[20355]: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
systemd[16279]: org.gnome.Shell@x11.service: Failed with result 'core-dump'.
systemd[16279]: org.gnome.Shell@x11.service: Triggering OnFailure= dependencies.
systemd[16279]: org.gnome.Shell@x11.service: Consumed 27min 51.978s CPU time.
Jul 12 07:01:06 orca.attlocal.net systemd[16279]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 1.
systemd[16279]: Started GNOME Session Failed lockdown screen (user).
systemd[16279]: Reached target GNOME Session Failed.

avidemux saved a file (which did save correctly), which triggered an error in mutter, which caused gnome-shell to barf. Why writing a file to disk should be problematic for the window manager is a bit bizarre. The only ui element involved would be creating/updating the icon/thumbnail in nautilus and/or nemo. And somewhere in there policykit got touched.

I recommend omitting hostname from output in most help request pastes, for less overall noise, and better fit into available horizontal space, e.g.:

# journalctl -b --no-host |  tail -5
Jul 13 17:56:22 systemd[1]: Started Hostname Service.
Jul 13 17:56:28 rtkit-daemon[1025]: Successfully made thread 16766 of process 1235 (/opt/kde3/bin/kdeinit) owned by '1050' RT at priority 20.
Jul 13 17:56:33 rtkit-daemon[1025]: Successfully made thread 16780 of process 1235 (/opt/kde3/bin/kdeinit) owned by '1050' RT at priority 20.
Jul 13 17:56:37 rtkit-daemon[1025]: Successfully made thread 16792 of process 1235 (/opt/kde3/bin/kdeinit) owned by '1050' RT at priority 20.
Jul 13 17:57:03 systemd[1]: systemd-hostnamed.service: Deactivated successfully.
#

Will mpv crash if run from an IceWM session instead of Gnome?

I have no real problem with mpv. It does not run as well as it should on gnome/x11, but I am almost certain this is gnome/x11 problem. It runs as expected on gnome/wayland.

avidemux3-qt5 crashes both gnome/x11 and gnome/wayland.

The problem appears to be in:

avidemux3-qt5
gnome
nvidia G06 drivers
some combination of the above

I will try to crash icewm when I have extra time. It is not really a priority because I won’t use icewm anyway. If I decide I can’t live without avidemux, I’ll go back to debian.

Thanks for the “–no-host” tip! I should have looked at the man page at some point :slight_smile:.

That’s one step in a troubleshooting process. If something doesn’t work in Gnome, but works in IceWM, then most probably an issue with Gnome.

Another test would be … create a new user account. Log into that user account using Gnome … then execute the same application and perform the same procedure (writing file, whatever …). Does it work?? If yes, then it’s probably an issue with your real user account configuration [files].

1 Like

Thanks for the suggestion! Of course, it would be much easier to test and troubleshoot if it happened every time, which it does not …

You’ve reported multiple problems. Using IceWM to run mpv is simply a troubleshooting step to determine whether mpv itself is having problem, or showcasing some Gnome problem.

@oxwrongagain Sounds similar to this bug https://gitlab.gnome.org/GNOME/mutter/-/issues/2644

Thanks malcolmlewis,

It very well could be the same or a related issue, but the syslog I got when crashing on wayland doesn’t give the same information … very little information really … or maybe I looked at the wrong part of the log … my eyes will be permanently damaged if I keep looking at syslogs …

It seems my options are to quit using avidemux to write files (using it only as a visual guide for reading timestamps is still helpful and doesn’t crash anything) or use a pre-44 release of gnome.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.