Arch Linux

teagum

Member

Registered: 2024-11-07

Posts: 2

gnome freezes when hitting the close window button (x)

gnome freezes repeatedly but irregularly when hit the x-button to close a window. Specifically, it only happens, when I close an app that was shipped with gnome, like the setting app, or calculator.

Symptoms:

• GUI freezes immediately after hitting x-button

• mouse cursor freezes

• no keyboard input possible

• cannot change to another tty

• cold start required

• shortly after freezing the CPU fan starts to spin much faster

I have been experimenting a lot to reproduce the error, however, I cannot find any regularity. It just happens sometimes.

Following are the last lines for journalctl from the last boot a freeze happend until the hard reset:

Nov 18 06:39:01 xxxyyy systemd[1]: archlinux-keyring-wkd-sync.service: Deactivated successfully.
Nov 18 06:39:01 xxxyyy systemd[1]: archlinux-keyring-wkd-sync.service: Consumed 1.868s CPU time, 6.8M memory peak.
Nov 18 06:39:09 xxxyyy systemd[1]: Stopping Accounts Service...
Nov 18 06:39:09 xxxyyy systemd[1]: accounts-daemon.service: Deactivated successfully.
Nov 18 06:39:09 xxxyyy systemd[1]: Stopped Accounts Service.
Nov 18 06:39:09 xxxyyy systemd[1]: Starting Accounts Service...
Nov 18 06:39:09 xxxyyy accounts-daemon[718748]: started daemon version 23.13.0
Nov 18 06:39:09 xxxyyy systemd[1]: Started Accounts Service.
Nov 18 06:39:09 xxxyyy systemd[1]: Reloading D-Bus System Message Bus...
Nov 18 06:39:09 xxxyyy systemd[1]: Reloaded D-Bus System Message Bus.
Nov 18 06:40:15 xxxyyy systemd[1356]: Created slice Slice /app/dbus-:1.2-org.gnome.baobab.
Nov 18 06:40:15 xxxyyy systemd[1356]: Started dbus-:1.2-org.gnome.baobab@0.service.
Nov 18 06:40:15 xxxyyy gnome-shell[1466]: Object .Gjs_ui_messageTray_Notification (0x56240cf00ea0), has been already disposed — impossible to emit any signal on it. This might be caused by the object having been destroyed from C >
                                            == Stack trace for context 0x56240a86cf70 ==
                                            #0   56240a980d08 i   resource:///org/gnome/shell/ui/messageTray.js:475 (16e0623d240 @ 74)
                                            #1   56240a980c60 i   resource:///org/gnome/shell/ui/messageTray.js:471 (16e0623d1f0 @ 63)
                                            #2   56240a980bd8 i   resource:///org/gnome/shell/ui/calendar.js:810 (16e06243ba0 @ 22)
                                            #3   56240a980b48 i   resource:///org/gnome/shell/ui/init.js:21 (32c530470c90 @ 48)
Nov 18 06:40:15 xxxyyy gnome-shell[1466]: Object .Gjs_ui_messageTray_Notification (0x56240cf00ea0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using s>
                                            == Stack trace for context 0x56240a86cf70 ==
                                            #0   56240a980d08 i   resource:///org/gnome/shell/ui/messageTray.js:481 (16e0623d240 @ 148)
                                            #1   56240a980c60 i   resource:///org/gnome/shell/ui/messageTray.js:471 (16e0623d1f0 @ 63)
                                            #2   56240a980bd8 i   resource:///org/gnome/shell/ui/calendar.js:810 (16e06243ba0 @ 22)
                                            #3   56240a980b48 i   resource:///org/gnome/shell/ui/init.js:21 (32c530470c90 @ 48)
Nov 18 06:40:15 xxxyyy systemd[1]: Starting Hostname Service...
Nov 18 06:40:15 xxxyyy systemd[1]: Started Hostname Service.
Nov 18 06:40:30 xxxyyy kernel: nouveau 0000:01:00.0: baobab[718895]: job timeout, channel 40 killed!
Nov 18 06:40:30 xxxyyy kernel: nouveau 0000:01:00.0: gsp: mmu fault queued
Nov 18 06:40:30 xxxyyy kernel: nouveau 0000:01:00.0: gsp: rc engn:00000001 chid:40 type:31 scope:1 part:233
Nov 18 06:40:30 xxxyyy kernel: nouveau 0000:01:00.0: fifo:000000:0005:0028:[baobab[718895]] errored - disabling channel
Nov 18 06:40:30 xxxyyy kernel: nouveau 0000:01:00.0: baobab[718895]: channel 40 killed!
Nov 18 06:40:30 xxxyyy gnome-shell[1466]: meta_wayland_buffer_process_damage: assertion 'buffer->resource' failed
Nov 18 06:40:30 xxxyyy systemd[1356]: dbus-:1.2-org.gnome.baobab@0.service: Consumed 11.310s CPU time, 26.9M memory peak.
Nov 18 06:40:45 xxxyyy systemd[1]: systemd-hostnamed.service: Deactivated successfully.

This is the journalctl output from when I open gnome settings directly after restart (do not know if it's related):

Nov 18 06:42:58 xxxyyy systemd[1361]: Starting GNOME XSettings service...
Nov 18 06:42:58 xxxyyy gnome-shell[3335]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Nov 18 06:42:58 xxxyyy gnome-shell[3335]: > Warning:          Unsupported maximum keycode 708, clipping.
Nov 18 06:42:58 xxxyyy gnome-shell[3335]: >                   X11 cannot support keycodes above 255.
Nov 18 06:42:58 xxxyyy gnome-shell[3335]: > Warning:          Could not resolve keysym XF86KbdInputAssistPrevgrou
Nov 18 06:42:58 xxxyyy gnome-shell[3335]: > Warning:          Could not resolve keysym XF86KbdInputAssistNextgrou
Nov 18 06:42:58 xxxyyy gnome-shell[3335]: Errors from xkbcomp are not fatal to the X server

Machine detail:

• HP zBook

• 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz

• Linux 6.11.8-arch1-2 x86_64

• GNOME Shell 47.1

Last edited by teagum (2024-11-18 07:14:21)

seth

Member

Registered: 2012-09-03

Posts: 58,698

Re: gnome freezes when hitting the close window button (x)

cold start required

This will drop all reelvant logs, try https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

However

Nov 18 06:40:30 xxxyyy kernel: nouveau 0000:01:00.0: baobab[718895]: channel 40 killed!

Is this a hybrid system?

lspci

Do you run gnome on X11 or wayland? (no, the xkeyboard stuff does not tell that)

Consider https://wiki.archlinux.org/title/NVIDIA

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

teagum

Member

Registered: 2024-11-07

Posts: 2

Re: gnome freezes when hitting the close window button (x)

I've enable the SysRq keys, but error did not happen since then.

Is this a hybrid system?

Yes, its a hybrid system:

00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
	DeviceName: Onboard IGD
	Subsystem: Hewlett-Packard Company Device 8846
	Kernel driver in use: i915
	Kernel modules: i915, xe
01:00.0 3D controller: NVIDIA Corporation TU117GLM [Quadro T500 Mobile] (rev a1)
	Subsystem: Hewlett-Packard Company Device 8848
	Kernel driver in use: nouveau
	Kernel modules: nouveau

Do you run gnome on X11 or wayland?

I run it on wayland.

---

I followed the instructions on https://wiki.archlinux.org/title/NVIDIA again and upgraded all relevant packages. Then I recognized that the last time I worked on the graphics driver, I forgot to persist the kernel parameter setting for vulkan. I fix that now. Maybe that was the root of all evil.

Thanks for the hint.

Last edited by teagum (2024-11-19 06:58:35)