You are not logged in.

Pages: 1

#1 2025-01-22 02:51:23

Wonderfulyeah
Member
Registered: 2021-02-22
Posts: 10

The GNOME desktop crashes.

The desktop crashes occasionally. Usually, when I open the file manager (Files), Files becomes unresponsive. After clicking to force quit, the entire desktop crashes. Here is the complete log (the time of the crash was at 10:09):

10:11:03 AM systemd: Unmounted /var/cache/pacman/pkg.
10:11:03 AM dbus-broker: Dispatched 137246 messages @ 3(±7)μs / message.
10:11:03 AM systemd: Closed libvirt logging daemon socket.
10:11:03 AM NetworkManager: <info>  [1737511863.5134] exiting (success)
10:11:03 AM dbus-broker-lau: Activation request for 'org.freedesktop.nm_dispatcher' failed.
10:11:03 AM NetworkManager: <info>  [1737511863.5039] manager: NetworkManager state is now CONNECTED_SITE
10:11:03 AM systemd: wpa_supplicant.service: Consumed 1.713s CPU time, 7.3M memory peak, 2M memory swap peak.
10:11:03 AM wpa_supplicant: wlan0: CTRL-EVENT-TERMINATING
10:11:03 AM kernel: wlan0: deauthenticating from 20:20:27:75:e9:52 by local choice (Reason: 3=DEAUTH_LEAVING)
10:11:03 AM systemd: Stopped target User and Group Name Lookups.
10:11:03 AM wpa_supplicant: p2p-dev-wlan0: CTRL-EVENT-TERMINATING
10:11:03 AM NetworkManager: <info>  [1737511863.2608] dhcp4 (wlan0): state changed no lease
10:11:03 AM dbus-broker-lau: Activation request for 'org.freedesktop.nm_dispatcher' failed.
10:11:03 AM wpa_supplicant: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
10:11:03 AM NetworkManager: <info>  [1737511863.2568] device (wlan0): state change: activated -> deactivating (reason 'unmanaged', managed-type: 'full')
10:11:03 AM systemd: Stopping WPA supplicant...
10:11:03 AM NetworkManager: <info>  [1737511863.2562] caught SIGTERM, shutting down normally.
10:11:03 AM systemd: Stopping Network Manager...
10:10:59 AM scdaemon: scdaemon[131847]: scdaemon (GnuPG) 2.4.7 stopped
10:10:59 AM gpg-agent: gpg-agent (GnuPG) 2.4.7 stopped
10:10:59 AM systemd: Stopped GnuPG public key management service.
10:10:59 AM keyboxd: keyboxd (GnuPG) 2.4.7 stopped
10:10:59 AM wireplumber: wireplumber: disconnected from pipewire
10:10:59 AM systemd: Stopping Multimedia Service Session Manager...
10:10:59 AM gpg-agent: SIGTERM received - shutting down ...
10:10:59 AM systemd: Removed slice Slice /app/dbus-:1.5-org.gnome.Shell.CalendarServer.
10:10:59 AM wireplumber: m-dbus-connection: <WpDBusConnection:0x5677f5b30d10> Trying to reconnect after core sync
10:10:59 AM systemd: Stopped User preferences database.
10:10:59 AM scdaemon: scdaemon[131847]: SIGTERM received - shutting down ...
10:10:59 AM systemd: Stopping Tracker file system data miner...
10:10:59 AM dbus-broker: Dispatched 324375 messages @ 3(±8)μs / message.
10:10:59 AM systemd-logind: Removed session 9.
10:10:59 AM wireplumber: m-dbus-connection: <WpDBusConnection:0x5677f5b30d10> DBus connection closed: Underlying GIOStream returned 0 bytes on an async read
10:10:59 AM systemd: Stopping User Manager for UID 1000...
10:10:01 AM containerd: time="2025-01-22T10:10:01.796409228+08:00" level=info msg="Stream server stopped"
10:10:01 AM systemd: Stopping containerd container runtime...
10:10:01 AM dockerd: time="2025-01-22T10:10:01.778924688+08:00" level=info msg="Daemon shutdown complete"
10:10:01 AM systemd: Unmounted /var/lib/docker/overlay2/e3fcfdcd92bace54855a320b670ca3a5d0d4a8a5d0f7bdcece1052f09b960247/merged.
10:10:01 AM kernel: docker0: port 1(vethc102cd6) entered disabled state
10:10:01 AM kernel: vethc102cd6 (unregistering): left promiscuous mode
10:10:01 AM kernel: vethc102cd6 (unregistering): left promiscuous mode
10:10:01 AM kernel: vethc102cd6 (unregistering): left allmulticast mode
10:10:01 AM kernel: docker0: port 1(vethc102cd6) entered disabled state
10:10:01 AM NetworkManager: <info>  [1737511801.7089] manager: (vethea4db59): new Veth device (/org/freedesktop/NetworkManager/Devices/19)
10:10:01 AM systemd: Finished Tell Plymouth To Jump To initramfs.
10:10:01 AM kernel: vethea4db59: renamed from eth0
10:10:01 AM kernel: docker0: port 1(vethc102cd6) entered disabled state
10:10:01 AM dockerd: time="2025-01-22T10:10:01.635800403+08:00" level=warning msg="ShouldRestart failed, container will not be restarted" container=4a1cfa6dd1d59bbaad1cc0951ec89296b4c0371edd24f069e13b03996291d9a6 daemonShuttingDown=true error="restart canceled" execDuration=42m7.679589925s exitStatus="{143 2025-01-22 02:10:01.602849131 +0000 UTC}" hasBeenManuallyStopped=false restartCount=0
10:10:01 AM containerd: time="2025-01-22T10:10:01.628787176+08:00" level=info msg="cleaning up dead shim" namespace=moby
10:10:01 AM systemd: docker-4a1cfa6dd1d59bbaad1cc0951ec89296b4c0371edd24f069e13b03996291d9a6.scope: Consumed 24.807s CPU time, 447M memory peak, 102.2M memory swap peak, 173.6M read from disk, 101.6M written to disk.
10:10:01 AM bash: ==> Build complete.
10:10:01 AM systemd: polkit.service: Consumed 2.809s CPU time, 7.9M memory peak, 3.7M memory swap peak.
10:10:01 AM bash:   -> Running build hook: [sd-shutdown]
10:10:01 AM systemd: Stopped Initialize hardware monitoring sensors.
10:10:00 AM bluetoothd: Exit
10:10:00 AM dbus-broker: A security policy denied :1.7 to send method call /midi/profile:org.bluez.GattProfile1.Release to :1.542.
10:10:00 AM systemd: EasyMonitor.service: Consumed 6min 10.555s CPU time, 383.7M memory peak, 2.2M memory swap peak.
10:10:00 AM systemd-logind: Session 9 logged out. Waiting for processes to exit.
10:10:00 AM avahi-daemon: avahi-daemon 0.8 exiting.
10:10:00 AM (modprobe): lm_sensors.service: Referenced but unset environment variable evaluates to an empty string: BUS_MODULES
10:10:00 AM avahi-daemon: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
10:10:00 AM udisksd: udisks daemon version 2.10.1 exiting
10:10:00 AM systemd: Stopped Load/Save OS Random Seed.
10:10:00 AM systemd-logind: Removed session 11.
10:10:00 AM systemd: Stopped Hold until boot process finishes up.
10:10:00 AM bluetoothd: Endpoint unregistered: sender=:1.947 path=/MediaEndpoint/A2DPSource/opus_05_duplex
10:10:00 AM systemd: Stopping Avahi mDNS/DNS-SD Stack...
10:10:00 AM bluetoothd: Endpoint unregistered: sender=:1.947 path=/MediaEndpoint/A2DPSink/opus_g
10:10:00 AM systemd: Stopping Sangfor EasyMonitor Service...
10:10:00 AM bluetoothd: Endpoint unregistered: sender=:1.947 path=/MediaEndpoint/A2DPSource/aac
10:10:00 AM systemd: Stopped target Login Prompts.
10:10:00 AM bluetoothd: Endpoint unregistered: sender=:1.947 path=/MediaEndpoint/A2DPSink/aac
10:10:00 AM systemd: Stopped target Multi-User System.
10:10:00 AM bluetoothd: Endpoint unregistered: sender=:1.947 path=/MediaEndpoint/A2DPSource/aptx
10:10:00 AM systemd: Removed slice Slice /system/getty.
10:10:00 AM bluetoothd: Endpoint unregistered: sender=:1.947 path=/MediaEndpoint/A2DPSink/aptx
10:10:00 AM systemd: Removed slice CUPS Slice.
10:10:00 AM bluetoothd: Endpoint unregistered: sender=:1.947 path=/MediaEndpoint/A2DPSource/aptx_hd
10:10:00 AM systemd-logind: Session 11 logged out. Waiting for processes to exit.
10:10:00 AM bluetoothd: Endpoint unregistered: sender=:1.947 path=/MediaEndpoint/A2DPSink/aptx_hd
10:10:00 AM systemd: session-11.scope: Consumed 342ms CPU time, 127.9M memory peak.
10:10:00 AM bluetoothd: Endpoint unregistered: sender=:1.947 path=/MediaEndpoint/A2DPSource/ldac
10:10:00 AM systemd: Stopped Session 11 of User haye.
10:10:00 AM dockerd: time="2025-01-22T10:10:00.878941189+08:00" level=info msg="Processing signal 'terminated'"
10:10:00 AM systemd: Stopped Getty on tty3.
10:10:00 AM gdm: GLib: Source ID 333 was not found when attempting to remove it
10:10:00 AM systemd: mandoc.timer: Deactivated successfully.
10:10:00 AM gdm-session-wor: pam_unix(gdm-password:session): session closed for user haye
10:10:00 AM systemd: Stopped target Bluetooth Support.
10:10:00 AM bluetoothd: Terminating
10:10:00 AM systemd: Removed slice Slice /system/systemd-coredump.
10:10:00 AM login: pam_unix(login:session): session closed for user haye
10:10:00 AM systemd: Stopping Session 9 of User haye...
10:10:00 AM systemd-logind: System is rebooting.
10:09:57 AM systemd: Started sandboxed app permission store.
10:09:56 AM bluetoothd: Endpoint registered: sender=:1.947 path=/MediaEndpoint/A2DPSource/opus_05_duplex
10:09:56 AM wireplumber: spa.bluez5.midi: org.bluez.GattManager1.RegisterApplication() failed: GDBus.Error:org.bluez.Error.AlreadyExists: Already Exists
10:09:56 AM login: LOGIN ON tty3 BY haye
10:09:56 AM systemd: Started Session 11 of User haye.
10:09:56 AM systemd-logind: New session 11 of user haye.
10:09:56 AM login: pam_unix(login:session): session opened for user haye(uid=1000) by haye(uid=0)
10:09:51 AM systemd: Started Getty on tty3.
10:09:51 AM bluetoothd: Endpoint unregistered: sender=:1.828 path=/MediaEndpoint/A2DPSource/opus_05_duplex
10:09:44 AM systemd: Finished Virtual Console Setup.
10:09:44 AM kernel: Console: switching to colour frame buffer device 160x50
10:09:44 AM systemd: Starting Virtual Console Setup...
10:09:44 AM kernel: fbcon: Taking over console
10:09:32 AM systemd: app-gnome-jetbrains\x2didea\x2dbd4d89b1\x2d8395\x2d42bb\x2da236\x2d2b703e3db0bd-125834.scope: Consumed 2h 18min 41.282s CPU time, 7.2G memory peak, 3.1G memory swap peak.
10:09:29 AM gnome-session-b: WARNING: Client '/org/gnome/SessionManager/Client36' failed to reply before timeout
10:09:29 AM systemd: gvfs-daemon.service: Consumed 9.238s CPU time, 59.1M memory peak, 35.1M memory swap peak.
10:09:28 AM localsearch-3: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
10:09:28 AM systemd: Stopped sandboxed app permission store.
10:09:28 AM localsearch-3: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
10:09:28 AM kernel: rfkill: input handler enabled
10:09:28 AM systemd: Stopping sandboxed app permission store...
10:09:28 AM localsearch-3: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
10:09:28 AM systemd: Stopping Virtual filesystem service - disk device monitor...
10:09:28 AM localsearch-3: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
10:09:28 AM systemd: Stopping Virtual filesystem service - Apple File Conduit monitor...
10:09:28 AM dbus-broker: Dispatched 2849 messages @ 3(±10)μs / message.
10:09:28 AM systemd: Stopping Accessibility services bus...
10:09:28 AM dingtalk: /usr/bin/dingtalk: line 6: 129632 Segmentation fault      (core dumped) ./com.alibabainc.dingtalk
10:09:28 AM systemd: systemd-coredump@8-260861-0.service: Consumed 3.257s CPU time, 2.2G memory peak.
10:09:28 AM systemd-coredum: Process 129632 (com.alibabainc.) of user 1000 dumped core.

Module libQt5Core.so.5 without build-id.
Module libibusplatforminputcontextplugin.so without build-id.
Module dingtalk_dll.so without build-id.
Stack trace of thread 129823:
#0  0x00007e4c4454d253 n/a (dingtalk_dll.so + 0x454d253)
#1  0x00007e4c44551ca5 n/a (dingtalk_dll.so + 0x4551ca5)
#2  0x00007e4c4aca339d n/a (libc.so.6 + 0x9439d)
#3  0x00007e4c4ad2849c n/a (libc.so.6 + 0x11949c)

Stack trace of thread 129633:
#0  0x00007e4c4ad288b2 epoll_wait (libc.so.6 + 0x1198b2)
#1  0x00007e4c3df33eea n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64

10:09:27 AM systemd: Failed to start GNOME XSettings service.
10:09:27 AM gsd-xsettings: Cannot open display:
10:09:27 AM systemd: Starting GNOME XSettings service...
10:09:27 AM gsd-xsettings: Cannot open display:
10:09:27 AM systemd: Starting GNOME XSettings service...
10:09:26 AM gsd-xsettings: Cannot open display:
10:09:26 AM systemd: app-gnome-redisinsight-248657.scope: Consumed 1min 37.361s CPU time, 1G memory peak, 72M memory swap peak.
10:09:26 AM systemd-coredum: Process 248657 (redisinsight) of user 1000 dumped core.

Module [dso] without build-id.
Module [dso] without build-id.
Stack trace of thread 248657:
#0  0x00005bd9aea147fe n/a (n/a + 0x0)
#1  0x00005bd9aea14337 n/a (n/a + 0x0)
#2  0x00005bd9aea14869 n/a (n/a + 0x0)
#3  0x00005bd9aaf6f007 n/a (n/a + 0x0)
#4  0x00005bd9afb54a55 n/a (n/a + 0x0)
#5  0x00005bd9afc0246c n/a (n/a + 0x0)
#6  0x0000756b9e30e5f1 n/a (libglib-2.0.so.0 + 0x5e5f1)
#7  0x0000756b9e3700ab n/a (libglib-2.0.so.0 + 0xc00ab)
#8  0x0000756b9e30ca55 g_main_context_iteration (libglib-2.0.so.0 + 0x5ca55)
#9  0x00005bd9aeae183c n/a (n/a + 0x0)
#10 0x00005bd9aea847e1 n/a (n/a + 0x0)
#11 0x00005bd9aea43f0e n/a (n/a + 0x0)
#12 0x00005bd9ad5ac89f n/a (n/a + 0x0)
#13 0x00005bd9ad5ae4e2 n/a (n/a + 0x0)
#14 0x00005bd9ad5aa036 n/a (n/a + 0x0)
#15 0x00005bd9ab1e1520 n/a (n/a + 0x0)
#16 0x00005bd9ab1e2a2e n/a (n/a + 0x0)
#17 0x00005bd9ab1e2888 n/a (n/a + 0x0)
#18 0x00005bd9ab1e054a n/a (n/a + 0x0)
#19 0x00005bd9ab1e0630 n/a (n/a + 0x0)
#20 0x00005bd9aae8d017 n/a (n/a + 0x0)
#21 0x0000756b9ce35e08 n/a (libc.so.6 + 0x25e08)
#22 0x0000756b9ce35ecc __libc_start_main (libc.so.6 + 0x25ecc)
#23 0x00005bd9aaa6902a n/a (n/a + 0x0)
ELF object binary architecture: AMD x86-64

10:09:26 AM systemd: Failed to start GNOME XSettings service.
10:09:26 AM gsd-xsettings: Cannot open display:
10:09:26 AM systemd: Starting GNOME XSettings service...
10:09:26 AM gsd-xsettings: Cannot open display:
10:09:26 AM systemd: Starting GNOME XSettings service...
10:09:25 AM polkitd: Unregistered Authentication Agent for unix-session:9 (system bus name :1.545, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
10:09:25 AM systemd: app-gnome-org.gnome.TextEditor-255845.scope: Consumed 13.754s CPU time, 127.3M memory peak.
10:09:25 AM gsd-media-keys: Cannot open display:
10:09:25 AM systemd: org.gnome.SettingsDaemon.Wacom.service: Main process exited, code=exited, status=1/FAILURE
10:09:25 AM gsd-wacom: Cannot open display:
10:09:25 AM systemd: org.gnome.SettingsDaemon.Power.service: Main process exited, code=exited, status=1/FAILURE
10:09:25 AM gsd-power: Cannot open display:
10:09:25 AM systemd: Starting GNOME Wacom tablet support service...
10:09:24 AM systemd-coredum: Process 129632 (com.alibabainc.) of user 1000 terminated abnormally with signal 11/SEGV, processing...
10:09:24 AM com.alibabainc.: [0122/100924.946109:ERROR:elf_dynamic_array_reader.h(64)] tag not found
10:09:24 AM systemd: Failed to start GNOME power management service.
10:09:24 AM gsd-media-keys: Cannot open display:
10:09:24 AM systemd: org.gnome.SettingsDaemon.Power.service: Main process exited, code=exited, status=1/FAILURE
10:09:24 AM gsd-power: Cannot open display:
10:09:24 AM systemd: org.gnome.SettingsDaemon.Wacom.service: Main process exited, code=exited, status=1/FAILURE
10:09:24 AM gsd-wacom: Cannot open display:

Offline

#2 2025-01-22 07:29:42

seth
Member
Registered: 2012-09-03
Posts: 60,756

Re: The GNOME desktop crashes.

Here is the complete log (the time of the crash was at 10:09):

No it's not - in your efforts to hide that your hostname probably reveals some weird sex-kink you've no only broken syntax highlighting (thanks for that) but also remove the pid and relations of the coredumps and pretty much everything else.

Baecause it's like top-posting.
Why not?
Also don't use -r

The journal "starts" w/ 

10:09:24 AM gsd-wacom: Cannot open display:

what means at this point the display server is already gone and everything afterwards is - most likely - just a consequence of that.

Post teh entire journal for a boot covering such crash

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

for the last one.

I already know that you're into hamsters wearing speedos, but iff you feel like you've to obfuscate anything you can pseudonymize it, ie. replace "idliketofuckmyhamster" with "innocenthostname" and "haye" with "myusername" and generally every token "aaa" with a unique "xxx" and "bbb" with "yyy" - not just everything with "xxx".

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

Offline

#3 2025-01-23 07:59:38

Wonderfulyeah
Member
Registered: 2021-02-22
Posts: 10

Re: The GNOME desktop crashes.

here is the complete log:
https://0x0.st/8XHX.txt

Offline

#4 2025-01-23 08:48:43

seth
Member
Registered: 2012-09-03
Posts: 60,756

Re: The GNOME desktop crashes.

The journal spans 4 days and is 54MB, about 45MB  of it spam from some dingbatalk and jetnobrains… but well, I asked for it.
Just for everyone else to know.

The only crashes inside are

Jan 20 14:10:32 titan systemd-coredump[60135]: Process 60092 (WeChatAppEx) of user 1000 dumped core.
Jan 20 17:54:22 titan systemd-coredump[108749]: Process 60674 (wps) of user 1000 dumped core.
Jan 20 17:55:27 titan systemd-coredump[109487]: Process 108770 (wps) of user 1000 dumped core.
Jan 20 18:03:46 titan systemd-coredump[112017]: Process 111506 (wps) of user 1000 dumped core.
Jan 21 09:30:47 titan systemd-coredump[123953]: Process 123331 (wps) of user 1000 dumped core.
Jan 21 09:30:59 titan systemd-coredump[124188]: Process 14033 (com.alibabainc.) of user 1000 dumped core.
Jan 21 09:37:26 titan systemd-coredump[129053]: Process 127248 (wps) of user 1000 dumped core.
Jan 22 10:09:26 titan systemd-coredump[260745]: Process 248657 (redisinsight) of user 1000 dumped core.
Jan 22 10:09:28 titan systemd-coredump[260862]: Process 129632 (com.alibabainc.) of user 1000 dumped core.

There's also massive spam from some broken (as is custom with gnome updates) 3rd party extensions, *very* notably "blur-my-shell" but also "CoverflowAltTab@palatis.blogspot.com"
If they're updated versions available, update those - otherwise get rid of them.

That being said, there's no indication of gnome crashing - other than you're losing the connection to the display server about here:

Jan 22 10:08:48 titan gnome-shell[124995]: st_widget_get_theme_node called on the widget [0x56a6aa739620 StLabel:insensitive ("腾格尔")] which is not in the stage.
Jan 22 10:08:50 titan wireplumber[124880]: spa.bluez5.sink.media: 0x5677f5ebcf38: error 24
Jan 22 10:08:50 titan bluetoothd[616]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Jan 22 10:08:50 titan wireplumber[124880]: spa.bluez5: Failed to release transport /org/bluez/hci0/dev_4C_99_92_28_E3_A3/fd2: Method "Release" with signature "" on interface "org.bluez.MediaTransport1" doesn't exist
Jan 22 10:08:50 titan gsd-media-keys[125131]: Unable to get default sink
Jan 22 10:08:50 titan gnome-shell[124995]: Object .Gjs_ui_messageTray_Notification (0x56a6a97f5bd0), has been already disposed — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
                                           == Stack trace for context 0x56a6a1d6b4e0 ==
                                           #0   7ffceb2e8220 b   resource:///org/gnome/shell/ui/messageTray.js:475 (3a03caa3d290 @ 74)
                                           #1   56a6a1e5f3c0 i   resource:///org/gnome/shell/ui/messageTray.js:471 (3a03caa3d240 @ 63)
                                           #2   56a6a1e5f338 i   resource:///org/gnome/shell/ui/calendar.js:810 (3a03caa43bf0 @ 22)
                                           #3   56a6a1e5f2a8 i   resource:///org/gnome/shell/ui/init.js:21 (1267eb170c90 @ 48)
Jan 22 10:08:50 titan gnome-shell[124995]: Object .Gjs_ui_messageTray_Notification (0x56a6a97f5bd0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
                                           == Stack trace for context 0x56a6a1d6b4e0 ==
                                           #0   7ffceb2e8220 b   resource:///org/gnome/shell/ui/messageTray.js:481 (3a03caa3d290 @ 148)
                                           #1   56a6a1e5f3c0 i   resource:///org/gnome/shell/ui/messageTray.js:471 (3a03caa3d240 @ 63)
                                           #2   56a6a1e5f338 i   resource:///org/gnome/shell/ui/calendar.js:810 (3a03caa43bf0 @ 22)
                                           #3   56a6a1e5f2a8 i   resource:///org/gnome/shell/ui/init.js:21 (1267eb170c90 @ 48)
Jan 22 10:08:53 titan gnome-shell[124995]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xa00008 specified for 0xa002b7 (wechat).
Jan 22 10:09:04 titan gnome-shell[124995]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xa00008 specified for 0xa002de (wechat).
Jan 22 10:09:08 titan wechat-universal.desktop[260610]: /sandbox/dde-file-manager
Jan 22 10:09:08 titan wechat-universal.desktop[260612]: Fake deepin file manager: dbus-send to open '/home/haye/Documents/WeChat_Data/xwechat_files/qhyboy_79af/msg/file/2025-01/hs_err_pid1(1).log' in file manager
Jan 22 10:09:10 titan gnome-shell[124995]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xa00008 specified for 0xa002e3 (wechat).
Jan 22 10:09:11 titan wechat-universal.desktop[260631]: /sandbox/dde-file-manager
Jan 22 10:09:11 titan wechat-universal.desktop[260633]: Fake deepin file manager: dbus-send to open '/home/haye/Documents/WeChat_Data/xwechat_files/qhyboy_79af/msg/file/2025-01/hs_err_pid1(1).log' in file manager
Jan 22 10:09:23 titan gnome-text-edit[255845]: Lost connection to Wayland compositor.
Jan 22 10:09:23 titan gnome-calendar[131727]: Lost connection to Wayland compositor.
Jan 22 10:09:23 titan xdg-desktop-por[125569]: Error reading events from display: Broken pipe
Jan 22 10:09:23 titan gjs[125543]: Error reading events from display: Broken pipe
Jan 22 10:09:23 titan xdg-desktop-por[125484]: Lost connection to Wayland compositor.
Jan 22 10:09:23 titan remmina[125142]: Error reading events from display: Broken pipe

I almost suspect you might be running out of filehandles/sockets and that's what's causing the conneciton losses.
Wrt the log, when you say

Usually, when I open the file manager (Files), Files becomes unresponsive.

do you mean the FM like nautilus or some file open dialog (notably from weechat)?

There's a throughline of gvfsd errors related to wsdd (SMB/windows hostname detection/sharing)…

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

Offline

#5 2025-01-23 09:05:58

Wonderfulyeah
Member
Registered: 2021-02-22
Posts: 10

Re: The GNOME desktop crashes.

Thank you for your reply. The file manager I mentioned refers to Nautilus.

seth wrote:

The journal spans 4 days and is 54MB, about 45MB  of it spam from some dingbatalk and jetnobrains… but well, I asked for it.
Just for everyone else to know.

The only crashes inside are

Jan 20 14:10:32 titan systemd-coredump[60135]: Process 60092 (WeChatAppEx) of user 1000 dumped core.
Jan 20 17:54:22 titan systemd-coredump[108749]: Process 60674 (wps) of user 1000 dumped core.
Jan 20 17:55:27 titan systemd-coredump[109487]: Process 108770 (wps) of user 1000 dumped core.
Jan 20 18:03:46 titan systemd-coredump[112017]: Process 111506 (wps) of user 1000 dumped core.
Jan 21 09:30:47 titan systemd-coredump[123953]: Process 123331 (wps) of user 1000 dumped core.
Jan 21 09:30:59 titan systemd-coredump[124188]: Process 14033 (com.alibabainc.) of user 1000 dumped core.
Jan 21 09:37:26 titan systemd-coredump[129053]: Process 127248 (wps) of user 1000 dumped core.
Jan 22 10:09:26 titan systemd-coredump[260745]: Process 248657 (redisinsight) of user 1000 dumped core.
Jan 22 10:09:28 titan systemd-coredump[260862]: Process 129632 (com.alibabainc.) of user 1000 dumped core.

There's also massive spam from some broken (as is custom with gnome updates) 3rd party extensions, *very* notably "blur-my-shell" but also "CoverflowAltTab@palatis.blogspot.com"
If they're updated versions available, update those - otherwise get rid of them.

That being said, there's no indication of gnome crashing - other than you're losing the connection to the display server about here:

Jan 22 10:08:48 titan gnome-shell[124995]: st_widget_get_theme_node called on the widget [0x56a6aa739620 StLabel:insensitive ("腾格尔")] which is not in the stage.
Jan 22 10:08:50 titan wireplumber[124880]: spa.bluez5.sink.media: 0x5677f5ebcf38: error 24
Jan 22 10:08:50 titan bluetoothd[616]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Jan 22 10:08:50 titan wireplumber[124880]: spa.bluez5: Failed to release transport /org/bluez/hci0/dev_4C_99_92_28_E3_A3/fd2: Method "Release" with signature "" on interface "org.bluez.MediaTransport1" doesn't exist
Jan 22 10:08:50 titan gsd-media-keys[125131]: Unable to get default sink
Jan 22 10:08:50 titan gnome-shell[124995]: Object .Gjs_ui_messageTray_Notification (0x56a6a97f5bd0), has been already disposed — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
                                           == Stack trace for context 0x56a6a1d6b4e0 ==
                                           #0   7ffceb2e8220 b   resource:///org/gnome/shell/ui/messageTray.js:475 (3a03caa3d290 @ 74)
                                           #1   56a6a1e5f3c0 i   resource:///org/gnome/shell/ui/messageTray.js:471 (3a03caa3d240 @ 63)
                                           #2   56a6a1e5f338 i   resource:///org/gnome/shell/ui/calendar.js:810 (3a03caa43bf0 @ 22)
                                           #3   56a6a1e5f2a8 i   resource:///org/gnome/shell/ui/init.js:21 (1267eb170c90 @ 48)
Jan 22 10:08:50 titan gnome-shell[124995]: Object .Gjs_ui_messageTray_Notification (0x56a6a97f5bd0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
                                           == Stack trace for context 0x56a6a1d6b4e0 ==
                                           #0   7ffceb2e8220 b   resource:///org/gnome/shell/ui/messageTray.js:481 (3a03caa3d290 @ 148)
                                           #1   56a6a1e5f3c0 i   resource:///org/gnome/shell/ui/messageTray.js:471 (3a03caa3d240 @ 63)
                                           #2   56a6a1e5f338 i   resource:///org/gnome/shell/ui/calendar.js:810 (3a03caa43bf0 @ 22)
                                           #3   56a6a1e5f2a8 i   resource:///org/gnome/shell/ui/init.js:21 (1267eb170c90 @ 48)
Jan 22 10:08:53 titan gnome-shell[124995]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xa00008 specified for 0xa002b7 (wechat).
Jan 22 10:09:04 titan gnome-shell[124995]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xa00008 specified for 0xa002de (wechat).
Jan 22 10:09:08 titan wechat-universal.desktop[260610]: /sandbox/dde-file-manager
Jan 22 10:09:08 titan wechat-universal.desktop[260612]: Fake deepin file manager: dbus-send to open '/home/haye/Documents/WeChat_Data/xwechat_files/qhyboy_79af/msg/file/2025-01/hs_err_pid1(1).log' in file manager
Jan 22 10:09:10 titan gnome-shell[124995]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xa00008 specified for 0xa002e3 (wechat).
Jan 22 10:09:11 titan wechat-universal.desktop[260631]: /sandbox/dde-file-manager
Jan 22 10:09:11 titan wechat-universal.desktop[260633]: Fake deepin file manager: dbus-send to open '/home/haye/Documents/WeChat_Data/xwechat_files/qhyboy_79af/msg/file/2025-01/hs_err_pid1(1).log' in file manager
Jan 22 10:09:23 titan gnome-text-edit[255845]: Lost connection to Wayland compositor.
Jan 22 10:09:23 titan gnome-calendar[131727]: Lost connection to Wayland compositor.
Jan 22 10:09:23 titan xdg-desktop-por[125569]: Error reading events from display: Broken pipe
Jan 22 10:09:23 titan gjs[125543]: Error reading events from display: Broken pipe
Jan 22 10:09:23 titan xdg-desktop-por[125484]: Lost connection to Wayland compositor.
Jan 22 10:09:23 titan remmina[125142]: Error reading events from display: Broken pipe

I almost suspect you might be running out of filehandles/sockets and that's what's causing the conneciton losses.
Wrt the log, when you say

Usually, when I open the file manager (Files), Files becomes unresponsive.

do you mean the FM like nautilus or some file open dialog (notably from weechat)?

There's a throughline of gvfsd errors related to wsdd (SMB/windows hostname detection/sharing)…

Offline

Pages: 1

Board footer

Powered by FluxBB