- Package:
- gnome-shell
- Source:
- gnome-shell
- Description:
- graphical shell for the GNOME desktop
- Submitter:
- Hor Jiun Shyong
- Date:
- 2023-09-24 03:27:02 UTC
- Severity:
- normal
- Tags:
After Debian boot up, GNOME crashes with white screen. I am unable to access terminal console screens via Alt+F1 to F6 (showing cursor blinking). I am only able to access the node after SSH from another node. /var/log/kern.log showing gnome-shell segfault 2023-08-26T18:00:40.251595+08:00 meixian kernel: [ 19.540303] gnome-shell[1746]: segfault at 18 ip 00007f3bc8acc1c0 sp 00007ffc8bc20798 error 4 in libmutter-12.so.0.0.0[7f3bc8a4e000+15000 0] likely on CPU 2 (core 1, socket 0) 2023-08-26T18:00:40.251597+08:00 meixian kernel: [ 19.540329] Code: 1f 00 48 89 c7 e8 a0 6f f8 ff e9 6f fe ff ff 0f 1f 00 c7 43 60 00 00 00 00 e8 5c c6 f8 ff e9 3a fe ff ff 0f 1f 80 00 00 00 00 <48> 8b 47 18 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 f5 53 48 2023-08-26T18:00:40.795605+08:00 meixian kernel: [ 20.085797] gnome-shell[1783]: segfault at 18 ip 00007f059f6cc1c0 sp 00007fffbe59e5b8 error 4 in libmutter-12.so.0.0.0[7f059f64e000+15000 0] likely on CPU 1 (core 0, socket 0) 2023-08-26T18:00:40.795620+08:00 meixian kernel: [ 20.085812] Code: 1f 00 48 89 c7 e8 a0 6f f8 ff e9 6f fe ff ff 0f 1f 00 c7 43 60 00 00 00 00 e8 5c c6 f8 ff e9 3a fe ff ff 0f 1f 80 00 00 00 00 <48> 8b 47 18 c3 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 f5 53 48 Recently I have upgraded the below packages. Start-Date: 2023-08-24 20:13:45 Commandline: apt-get dist-upgrade -V Install: linux-headers-6.4.0-3-common:amd64 (6.4.11-1, automatic), linux-kbuild-6.4.0-3:amd64 (6.4.11-1, automatic), linux-image-6.4.0-3-amd64:amd64 (6.4.11-1, automatic), linux-headers-6.4 .0-3-amd64:amd64 (6.4.11-1, automatic) Upgrade: libimath-3-1-29:amd64 (3.1.6-1, 3.1.9-2), fonts-noto-unhinted:amd64 (20201225-1, 20201225-2), libpipewire-0.3-common:amd64 (0.3.77-1, 0.3.78-1), pipewire-pulse:amd64 (0.3.77-1, 0.3 .78-1), libminizip1:amd64 (1.1-8+b1, 1:1.2.13.dfsg-3), linux-compiler-gcc-13-x86:amd64 (6.4.4-3, 6.4.11-1), linux-headers-amd64:amd64 (6.4.4-3, 6.4.11-1), pipewire:amd64 (0.3.77-1, 0.3.78-1 ), python3-zeroconf:amd64 (0.74.0-2, 0.80.0-1), zlib1g-dev:amd64 (1:1.2.13.dfsg-1, 1:1.2.13.dfsg-3), fonts-noto-mono:amd64 (20201225-1, 20201225-2), linux-image-amd64:amd64 (6.4.4-3, 6.4.11 -1), libspa-0.2-bluetooth:amd64 (0.3.77-1, 0.3.78-1), fonts-noto-core:amd64 (20201225-1, 20201225-2), gstreamer1.0-pipewire:amd64 (0.3.77-1, 0.3.78-1), pipewire-audio:amd64 (0.3.77-1, 0.3.7 8-1), pipewire-bin:amd64 (0.3.77-1, 0.3.78-1), fonts-noto-ui-extra:amd64 (20201225-1, 20201225-2), chrome-gnome-shell:amd64 (42.1-3, 42.1-4), fonts-noto:amd64 (20201225-1, 20201225-2), font s-noto-extra:amd64 (20201225-1, 20201225-2), libspa-0.2-modules:amd64 (0.3.77-1, 0.3.78-1), fonts-noto-ui-core:amd64 (20201225-1, 20201225-2), gnome-browser-connector:amd64 (42.1-3, 42.1-4) , libpipewire-0.3-modules:amd64 (0.3.77-1, 0.3.78-1), zlib1g:amd64 (1:1.2.13.dfsg-1, 1:1.2.13.dfsg-3), pipewire-alsa:amd64 (0.3.77-1, 0.3.78-1), linux-libc-dev:amd64 (6.4.4-3, 6.4.11-1), li bpipewire-0.3-0:amd64 (0.3.77-1, 0.3.78-1) End-Date: 2023-08-24 20:16:08 Start-Date: 2023-08-25 12:02:59 Commandline: apt-get dist-upgrade -V Install: mutter-common-bin:amd64 (44.3-7, automatic), libmutter-12-0:amd64 (44.3-7, automatic), gir1.2-mutter-12:amd64 (44.3-7, automatic), gir1.2-gnomebg-4.0:amd64 (44.0-2, automatic), gir 1.2-nma4-1.0:amd64 (1.10.6-1, automatic) Upgrade: fontconfig:amd64 (2.14.2-3, 2.14.2-4), easy-rsa:amd64 (3.1.5-1, 3.1.6-1), wpasupplicant:amd64 (2:2.10-12, 2:2.10-14), libpango-1.0-0:amd64 (1.50.14+ds-1, 1.51.0+ds-2), libfwupd2:am d64 (1.9.3-1, 1.9.4-2), gnome-remote-desktop:amd64 (43.4-2, 44.2-6), mutter-common:amd64 (43.6-1, 44.3-7), gnome-shell-extensions:amd64 (43.1-1, 44.0-2), gnome-shell:amd64 (43.7-1, 44.3-5), libfontconfig1:amd64 (2.14.2-3, 2.14.2-4), fontconfig-config:amd64 (2.14.2-3, 2.14.2-4), gir1.2-nm-1.0:amd64 (1.42.8-1, 1.44.0-1), libpangocairo-1.0-0:amd64 (1.50.14+ds-1, 1.51.0+ds-2), gr ep:amd64 (3.11-2, 3.11-3), python3-async-timeout:amd64 (4.0.2-1, 4.0.3-1), network-manager:amd64 (1.42.8-1, 1.44.0-1), libpangoft2-1.0-0:amd64 (1.50.14+ds-1, 1.51.0+ds-2), gnome-shell-commo n:amd64 (43.7-1, 44.3-5), mutter:amd64 (43.6-1, 44.3-7), gir1.2-pango-1.0:amd64 (1.50.14+ds-1, 1.51.0+ds-2), libpangoxft-1.0-0:amd64 (1.50.14+ds-1, 1.51.0+ds-2), gnome-shell-extension-prefs :amd64 (43.7-1, 44.3-5), libnm0:amd64 (1.42.8-1, 1.44.0-1), fwupd:amd64 (1.9.3-1, 1.9.4-2) End-Date: 2023-08-25 12:03:32 Thanks. Regards, Hor Jiun Shyong 何俊雄 +60-16-2089567
Linux simayi 6.4.0-3-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.4.11-1 (2023-08-17) x86_64 GNU/Linux Debian GNU/Linux trixie/sid GNOME 44.3 GDM 44.1
Hi, After updating Debian today with below packages, Gnome still starts with white screen. Error as below. Thanks. gnome-shell:amd64 (44.3-5, 44.4-1), mutter:amd64 (44.3-7, 44.4-2) linux-image-6.4.0-4-amd64:amd64 (6.4.13-1, automatic), linux-image-amd64:amd64 (6.4.11-1, 6.4.13-1), Start-Date: 2023-09-07 12:17:22 Commandline: apt-get dist-upgrade -V Install: linux-image-6.4.0-4-amd64:amd64 (6.4.13-1, automatic), linux-kbuild-6.4.0-4:amd64 (6.4.13-1, automatic), linux-headers-6.4.0-4-amd64:amd64 (6.4.13-1, automatic), linux-headers-6.4. 0-4-common:amd64 (6.4.13-1, automatic) Upgrade: libnghttp2-14:amd64 (1.55.1-1, 1.56.0-1), python3-brlapi:amd64 (6.6-2, 6.6-4), mutter-common-bin:amd64 (44.3-7, 44.4-2), xbrlapi:amd64 (6.6-2, 6.6-4), libldb2:amd64 (2:2.7.2+samba4 .18.6+dfsg-1, 2:2.8.0+samba4.19.0+dfsg-1), libbrlapi0.8:amd64 (6.6-2, 6.6-4), libmutter-12-0:amd64 (44.3-7, 44.4-2), virtinst:amd64 (1:4.1.0-2, 1:4.1.0-3), linux-compiler-gcc-13-x86:amd64 ( 6.4.11-1, 6.4.13-1), libwbclient0:amd64 (2:4.18.6+dfsg-1, 2:4.19.0+dfsg-1), linux-headers-amd64:amd64 (6.4.11-1, 6.4.13-1), libsmbclient:amd64 (2:4.18.6+dfsg-1, 2:4.19.0+dfsg-1), mutter-com mon:amd64 (44.3-7, 44.4-2), gnome-shell:amd64 (44.3-5, 44.4-1), linux-image-amd64:amd64 (6.4.11-1, 6.4.13-1), libnet-http-perl:amd64 (6.22-1, 6.23-1), gir1.2-mutter-12:amd64 (44.3-7, 44.4-2 ), gnome-shell-common:amd64 (44.3-5, 44.4-1), libmozjs-102-0:amd64 (102.14.0-1, 102.15.0-1), mutter:amd64 (44.3-7, 44.4-2), python3-ldb:amd64 (2:2.7.2+samba4.18.6+dfsg-1, 2:2.8.0+samba4.19. 0+dfsg-1), libsdl2-2.0-0:amd64 (2.28.2+dfsg-1, 2.28.3+dfsg-1), samba-libs:amd64 (2:4.18.6+dfsg-1, 2:4.19.0+dfsg-1), virt-viewer:amd64 (11.0-2, 11.0-3), gnome-shell-extension-prefs:amd64 (44 .3-5, 44.4-1), linux-libc-dev:amd64 (6.4.11-1, 6.4.13-1) End-Date: 2023-09-07 12:19:30 17.787657] gnome-shell[1684]: segfault at 18 ip 00007f62cfcced54 sp 00007ffcfcdeff98 error 4 in libmutter-12.so.0.0.0[7f62cfc4e000+156000] likely on CPU 2 (core 1, socket 0) [ 17.787670] Code: c7 e8 10 44 f8 ff e9 6f fe ff ff 0f 1f 00 c7 43 60 00 00 00 00 e8 cc 9a f8 ff e9 3a fe ff ff 0f 1f 80 00 00 00 00 f3 0f 1e fa <48> 8b 47 18 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 55 48 89 f5 53 48 [ 18.415736] gnome-shell[1715]: segfault at 18 ip 00007f9f416ced54 sp 00007ffc3a4e58a8 error 4 in libmutter-12.so.0.0.0[7f9f4164e000+156000] likely on CPU 4 (core 2, socket 0) [ 18.415750] Code: c7 e8 10 44 f8 ff e9 6f fe ff ff 0f 1f 00 c7 43 60 00 00 00 00 e8 cc 9a f8 ff e9 3a fe ff ff 0f 1f 80 00 00 00 00 f3 0f 1e fa <48> 8b 47 18 c3 0f 1f 80 00 00 00 00 f3 0f 1e fa 55 48 89 f5 53 48 Regards, Hor Jiun Shyong 何俊雄
Control: tags -1 + moreinfo
get a backtrace for the crash? Usually the easiest way to achieve this is
to use systemd-coredump: see
<https://wiki.debian.org/HowToGetABacktrace#Core_dump> and
<https://wiki.debian.org/HowToGetABacktrace#Running_gdb>.
It is helpful if you can use the reportbug tool to report bugs: that would
provide information on all the packages that gnome-shell depends on.
Thanks,
smcv
Hi, OK I will do a systemd-coredump asap. Thanks. This issue occurred on my home desktop running with Nvidia GPU. Just a moment ago, while using my laptop with AMD Ryzen Pro 7 (with integrated Radeon Graphics), GNOME just crashed with the same white screen. However Debian managed to restart the GNOME session successfully. This is the first time the crash occurred after I have just updated my Debian Testing "Trixie/Sid" with the same packages (as below) that my desktop PC had upgraded earlier today. I am including the generated dmesg error just as a reference. Note: laptop is able to start GNOME successfully unlike my the desktop PC. Note that the error is similar to my desktop error, mentioning "libmutter-clutter-12.so.0.0.0 library. *Laptop error* [29273.788405] gnome-shell[41837]: segfault at 28 ip 00007fcdec6f4c08 sp 00007ffe3b17af80 error 4 in libmutter-clutter-12.so.0.0.0[7fcdec686000+90000] likely on CPU 8 (core 4, socket 0) *Desktop error* 18.415736] gnome-shell[1715]: segfault at 18 ip 00007f9f416ced54 sp 00007ffc3a4e58a8 error 4 in libmutter-12.so.0.0.0[7f9f4164e000+156000] likely on CPU 4 (core 2, socket 0) *Packages upgraded on laptop today* gnome-shell:amd64 (44.3-5, 44.4-1), mutter:amd64 (44.3-7, 44.4-2) linux-image-6.4.0-4-amd64:amd64 (6.4.13-1, automatic), linux-image-amd64:amd64 (6.4.11-1, 6.4.13-1), *Laptop dmesg error* 8355.638038] amdgpu 0000:07:00.0: amdgpu: failed to get a new IB (-512) [ 9622.012708] wfica[15540]: segfault at 968 ip 00007f66eb9722e0 sp 00007ffef9c33870 error 4 in libX11.so.6.4.0[7f66eb954000+8b000] likely on CPU 0 (core 0, socket 0) [ 9622.012728] Code: 48 89 44 24 28 31 c0 48 85 f6 0f 84 e2 00 00 00 48 89 f7 e8 a2 27 fe ff 48 89 c2 31 c0 48 81 fa fe ff 00 00 0f 87 a5 00 00 00 <48> 8b 83 68 09 00 00 48 85 c0 74 05 48 89 df ff 10 ba 08 00 00 00 [10049.238617] amdgpu 0000:07:00.0: amdgpu: failed to get a new IB (-512) [10049.281464] amdgpu: Move buffer fallback to memcpy unavailable [10049.284113] amdgpu 0000:07:00.0: amdgpu: 00000000b854c332 pin failed [12741.774584] perf: interrupt took too long (2502 > 2500), lowering kernel.perf_event_max_sample_rate to 79750 [14633.019139] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled [14633.033281] JFS: nTxBlock = 8192, nTxLock = 65536 [14633.075715] QNX4 filesystem 0.2.3 registered. [18887.101242] amdgpu 0000:07:00.0: amdgpu: failed to get a new IB (-512) [18949.766669] amdgpu 0000:07:00.0: amdgpu: failed to get a new IB (-512) [18949.815284] amdgpu: Move buffer fallback to memcpy unavailable [18949.818943] amdgpu 0000:07:00.0: amdgpu: 0000000016d7300e pin failed [18949.844257] wfica[33300]: segfault at 968 ip 00007f167ff7b2e0 sp 00007ffe82c82cb0 error 4 in libX11.so.6.4.0[7f167ff5d000+8b000] likely on CPU 4 (core 2, socket 0) [18949.844296] Code: 48 89 44 24 28 31 c0 48 85 f6 0f 84 e2 00 00 00 48 89 f7 e8 a2 27 fe ff 48 89 c2 31 c0 48 81 fa fe ff 00 00 0f 87 a5 00 00 00 <48> 8b 83 68 09 00 00 48 85 c0 74 05 48 89 df ff 10 ba 08 00 00 00 [24891.716477] wfica[36804]: segfault at 968 ip 00007f75420452e0 sp 00007ffc03121c40 error 4 in libX11.so.6.4.0[7f7542027000+8b000] likely on CPU 6 (core 3, socket 0) [24891.716507] Code: 48 89 44 24 28 31 c0 48 85 f6 0f 84 e2 00 00 00 48 89 f7 e8 a2 27 fe ff 48 89 c2 31 c0 48 81 fa fe ff 00 00 0f 87 a5 00 00 00 <48> 8b 83 68 09 00 00 48 85 c0 74 05 48 89 df ff 10 ba 08 00 00 00 [29257.318686] traps: Chrome_IOThread[38071] trap invalid opcode ip:56243cc88ad4 sp:7fa85affbc90 error:0 in teams[56243a68b000+5fcb000] [29257.942618] wfica[41540]: segfault at 968 ip 00007efd7a5932e0 sp 00007ffeaf558a80 error 4 in libX11.so.6.4.0[7efd7a575000+8b000] likely on CPU 10 (core 5, socket 0) [29257.942646] Code: 48 89 44 24 28 31 c0 48 85 f6 0f 84 e2 00 00 00 48 89 f7 e8 a2 27 fe ff 48 89 c2 31 c0 48 81 fa fe ff 00 00 0f 87 a5 00 00 00 <48> 8b 83 68 09 00 00 48 85 c0 74 05 48 89 df ff 10 ba 08 00 00 00 [29263.415541] amdgpu 0000:07:00.0: amdgpu: failed to get a new IB (-512) [29263.416983] amdgpu 0000:07:00.0: amdgpu: failed to get a new IB (-512) [29263.419267] amdgpu 0000:07:00.0: amdgpu: failed to get a new IB (-512) [29263.421239] amdgpu 0000:07:00.0: amdgpu: failed to get a new IB (-512) [29263.421250] amdgpu: Move buffer fallback to memcpy unavailable [29263.421559] amdgpu 0000:07:00.0: amdgpu: 00000000e98ed3ac pin failed [29263.425360] amdgpu 0000:07:00.0: amdgpu: failed to get a new IB (-512) [29273.567941] rfkill: input handler enabled [29273.788405] gnome-shell[41837]: segfault at 28 ip 00007fcdec6f4c08 sp 00007ffe3b17af80 error 4 in libmutter-clutter-12.so.0.0.0[7fcdec686000+90000] likely on CPU 8 (core 4, socket 0) [29273.788429] Code: 48 8d 3d 5e 47 02 00 e8 f6 45 f9 ff 31 c0 eb 90 66 90 f3 0f 1e fa 41 56 41 55 49 89 cd 41 54 49 89 f4 55 48 89 d5 53 48 89 fb <4c> 8b 77 28 e8 df 47 f9 ff 48 89 c6 48 8b 03 48 85 c0 74 05 48 39 [29274.295512] audit: type=1400 audit(1694074768.688:41): apparmor="ALLOWED" operation="signal" class="signal" profile="libreoffice-oosplash" pid=11920 comm="oosplash" requested_mask="send" denied_mask="send" signal=term peer="libreoffice-soffice" [29274.295528] audit: type=1400 audit(1694074768.688:42): apparmor="ALLOWED" operation="signal" class="signal" profile="libreoffice-soffice" pid=11920 comm="oosplash" requested_mask="receive" denied_mask="receive" signal=term peer="libreoffice-oosplash" [29274.322823] ------------[ cut here ]------------ [29274.322831] WARNING: CPU: 15 PID: 10615 at mm/gup.c:1101 __get_user_pages+0x57b/0x670 [29274.322845] Modules linked in: ufs qnx4 hfsplus hfs cdrom minix msdos jfs xfs cpuid rfcomm cmac algif_hash algif_skcipher af_alg snd_seq_dummy snd_hrtimer snd_seq snd_seq_device qrtr bnep binfmt_misc ext4 mbcache jbd2 nls_ascii nls_cp437 vfat fat intel_rapl_msr intel_rapl_common edac_mce_amd mt7921e btusb mt7921_common btrtl btbcm btintel mt76_connac_lib btmtk kvm_amd mt76 bluetooth snd_ctl_led kvm snd_hda_codec_realtek snd_hda_codec_generic mac80211 irqbypass jitterentropy_rng ghash_clmulni_intel sha512_ssse3 snd_hda_codec_hdmi sha512_generic drbg uvcvideo ansi_cprng videobuf2_vmalloc libarc4 uvc ecdh_generic snd_hda_intel videobuf2_memops ecc thinkpad_acpi crc16 snd_intel_dspcfg videobuf2_v4l2 nvram cfg80211 snd_intel_sdw_acpi aesni_intel videodev ledtrig_audio crypto_simd snd_hda_codec platform_profile cryptd videobuf2_common mc snd_hda_core rapl snd_pci_acp6x think_lmi snd_hwdep firmware_attributes_class snd_pci_acp5x wmi_bmof pcspkr snd_pcm snd_rn_pci_acp3x acpi_cpufreq ucsi_acpi snd_acp_config sp5100_tco k10temp [29274.323051] snd_soc_acpi snd_timer typec_ucsi watchdog snd_pci_acp3x ccp snd roles rfkill soundcore typec rng_core ac joydev sg amd_pmc hid_multitouch evdev serio_raw nfsd vhost_net tun vhost vhost_iotlb auth_rpcgss tap nfs_acl msr lockd parport_pc grace ppdev lp parport fuse sunrpc loop efi_pstore configfs ip_tables x_tables autofs4 btrfs blake2b_generic efivarfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod hid_logitech_hidpp hid_logitech_dj ses enclosure sd_mod scsi_transport_sas uas usb_storage scsi_mod usbhid scsi_common amdgpu dm_mod drm_buddy gpu_sched nvme i2c_algo_bit drm_suballoc_helper xhci_pci drm_display_helper nvme_core xhci_hcd cec rc_core drm_ttm_helper ttm t10_pi usbcore sdhci_pci drm_kms_helper r8169 cqhci crc64_rocksoft crc64 crc_t10dif sdhci crct10dif_generic hid_generic realtek crc32_pclmul mdio_devres drm psmouse crc32c_intel libphy mmc_core video i2c_piix4 usb_common crct10dif_pclmul [29274.323284] i2c_hid_acpi crct10dif_common i2c_hid battery hid wmi button [29274.323302] CPU: 15 PID: 10615 Comm: chrome_crashpad Not tainted 6.4.0-3-amd64 #1 Debian 6.4.11-1 [29274.323308] Hardware name: LENOVO 21C7CTO1WW/21C7CTO1WW, BIOS R1YET42W (1.19 ) 02/23/2023 [29274.323312] RIP: 0010:__get_user_pages+0x57b/0x670 [29274.323321] Code: 00 e9 cb fd ff ff 48 03 bd 88 00 00 00 e9 c7 fb ff ff 48 81 e1 00 f0 ff ff e9 4b fc ff ff 48 81 e2 00 f0 ff ff e9 b5 fc ff ff <0f> 0b e9 21 fb ff ff f6 c3 04 0f 85 4d ff ff ff 49 8b 3f 48 89 f8 [29274.323326] RSP: 0018:ffffb28bcc8afc70 EFLAGS: 00010202 [29274.323332] RAX: ffff98c243c6fd78 RBX: 000000000005000a RCX: 00007ffebd494fff [29274.323336] RDX: 0000000000000000 RSI: 00007f679c156000 RDI: ffff98bfc0e58000 [29274.323340] RBP: ffff98c0013d5280 R08: ffff98c412eeaa08 R09: 0000000000000001 [29274.323343] R10: ffff98c412eeaa80 R11: ffff98c412eeaa0c R12: 0000000000000000 [29274.323347] R13: ffff98c243c6fd78 R14: ffffb28bcc8afd34 R15: ffffb28bcc8afd34 [29274.323351] FS: 00007f246765c800(0000) GS:ffff98ce6f1c0000(0000) knlGS:0000000000000000 [29274.323356] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [29274.323360] CR2: 000035900036c300 CR3: 000000066b07c000 CR4: 0000000000750ee0 [29274.323364] PKRU: 55555554 [29274.323367] Call Trace: [29274.323372] <TASK> [29274.323375] ? __get_user_pages+0x57b/0x670 [29274.323383] ? __warn+0x81/0x130 [29274.323394] ? __get_user_pages+0x57b/0x670 [29274.323401] ? report_bug+0x191/0x1c0 [29274.323413] ? handle_bug+0x3c/0x80 [29274.323421] ? exc_invalid_op+0x17/0x70 [29274.323427] ? asm_exc_invalid_op+0x1a/0x20 [29274.323442] ? __get_user_pages+0x57b/0x670 [29274.323454] get_user_pages_remote+0x14a/0x400 [29274.323467] __access_remote_vm+0x1bf/0x420 [29274.323479] mem_rw.isra.0+0x111/0x1d0 [29274.323492] vfs_read+0xac/0x320 [29274.323500] ? __x86_return_thunk+0x9/0x10 [29274.323506] ? fpregs_assert_state_consistent+0x26/0x50 [29274.323513] ? __x86_return_thunk+0x9/0x10 [29274.323518] ? exit_to_user_mode_prepare+0x40/0x1d0 [29274.323525] ? __x86_return_thunk+0x9/0x10 [29274.323530] ? syscall_exit_to_user_mode+0x1b/0x40 [29274.323536] ? __x86_return_thunk+0x9/0x10 [29274.323544] __x64_sys_pread64+0x98/0xd0 [29274.323552] do_syscall_64+0x60/0xc0 [29274.323559] entry_SYSCALL_64_after_hwframe+0x77/0xe1 [29274.323566] RIP: 0033:0x7f2467234b97 [29274.323571] Code: 08 89 3c 24 48 89 4c 24 18 e8 e5 ee f8 ff 4c 8b 54 24 18 48 8b 54 24 10 41 89 c0 48 8b 74 24 08 8b 3c 24 b8 11 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 04 24 e8 35 ef f8 ff 48 8b [29274.323575] RSP: 002b:00007fff4b789560 EFLAGS: 00000293 ORIG_RAX: 0000000000000011 [29274.323581] RAX: ffffffffffffffda RBX: 0000000000001000 RCX: 00007f2467234b97 [29274.323585] RDX: 0000000000001000 RSI: 00007fff4b789970 RDI: 0000000000000007 [29274.323588] RBP: 00007fff4b789770 R08: 0000000000000000 R09: 00003590004735a0 [29274.323591] R10: 00007f679c155880 R11: 0000000000000293 R12: 00007fff4b789970 [29274.323595] R13: 0000359000474680 R14: 00007f679c155880 R15: 0000000000001000 [29274.323605] </TASK> [29274.323608] ---[ end trace 0000000000000000 ]--- Regards, Hor Jiun Shyong 何俊雄 Simon McVittie <smcv@debian.org> 于2023年9月7日周四 16:18写道:
With the proprietary Nvidia driver, or with Mesa's open source Nouveau
driver? GNOME Shell uses OpenGL, so the choice of driver is likely to be
significant.
It would probably be a good idea to install systemd-coredump on the laptop
too, so that if this crash happens again, the crash dump will be collected
for later investigation.
If the crash doesn't happen again, no further action is needed, but if
it happens on the AMD laptop again:
* If the backtrace obtained via systemd-coredump looks the same as for the
Nvidia desktop, we can use the same bug report for it.
* But if the backtrace seems significantly different, please report a
separate bug for it. Merging bugs if they turn out to be the same is
easy, but keeping track of two different bugs on the same bug number
gets really confusing, so we should avoid doing that.
Thanks,
smcv
driver? GNOME Shell uses OpenGL, so the choice of driver is likely to be significant. Desktop PC uses below proprietary Nvidia driver. # apt-cache show nvidia-driver Package: nvidia-driver Source: nvidia-graphics-drivers Version: 525.125.06-2 Installed-Size: 1373 Maintainer: Debian NVIDIA Maintainers < pkg-nvidia-devel@lists.alioth.debian.org> Architecture: amd64 Provides: nvidia-driver-any, nvidia-glx-any Depends: nvidia-driver-libs (= 525.125.06-2), nvidia-driver-bin (= 525.125.06-2), xserver-xorg-video-nvidia (= 525.125.06-2), nvidia-vdpau-driver (= 525.125.06-2), nvidia-alternative (= 525.125.06-2), nvidia-kernel-dkms (= 525.125.06-2) | nvidia-kernel-525.125.06 | nvidia-open-kernel-525.125.06 | nvidia-open-kernel-525.125.06, nvidia-support Pre-Depends: nvidia-installer-cleanup, nvidia-legacy-check (>= 495) Recommends: nvidia-settings (>= 525), libnvidia-cfg1 (= 525.125.06-2), nvidia-persistenced Suggests: nvidia-kernel-dkms (>= 525.125.06) | nvidia-kernel-source (>= 525.125.06) | nvidia-open-kernel-source (>= 525.125.06) | nvidia-open-kernel-source (>= 525.125.06) Description-en: NVIDIA metapackage This metapackage depends on the NVIDIA binary driver and libraries that provide optimized hardware acceleration of OpenGL/GLX/EGL/GLES/Vulkan applications via a direct-rendering X Server. Regards, Hor Jiun Shyong 何俊雄 Simon McVittie <smcv@debian.org> 于2023年9月7日周四 17:16写道:
Hi, I have submitted reportbug on this same case: 1050547. Below are the backtrace via systemd-coredump and gdb output. Thanks. coredumpctl_gdb.txt.gz https://drive.google.com/file/d/13g8x6hAvkBznODK1y96Epewk_QLUxDB3/view?usp=sharing core.gnome-shell.117.db5045b3be454eabaf40ab7634cdd15f.1720.1694258007000000.zst.gz https://drive.google.com/file/d/1DreFJWmMfV34cbiad5Dp5d6XslVS1zqm/view?usp=sharing Regards, Hor Jiun Shyong 何俊雄 Hor Jiun Shyong <jiunshyong@gmail.com> 于2023年9月7日周四 18:21写道:
The relevant part is:
#0 0x00007f9e956ced54 in meta_display_get_x11_display () from /lib/x86_64-linux-gnu/libmutter-12.so.0
#1 0x00007f9e956f9a3b in ?? () from /lib/x86_64-linux-gnu/libmutter-12.so.0
#2 0x00007f9e95e95f8f in g_initable_new_valist () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
#3 0x00007f9e95e96069 in g_initable_new () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
#4 0x00007f9e956f9dda in ?? () from /lib/x86_64-linux-gnu/libmutter-12.so.0
#5 0x00007f9e956fd5ce in ?? () from /lib/x86_64-linux-gnu/libmutter-12.so.0
#6 0x00007f9e956fd62d in ?? () from /lib/x86_64-linux-gnu/libmutter-12.so.0
#7 0x00007f9e9568b04e in meta_cursor_tracker_get_sprite () from /lib/x86_64-linux-gnu/libmutter-12.so.0
#8 0x00007f9e94d4cf7a in ?? () from /lib/x86_64-linux-gnu/libffi.so.8
but this is of limited usefulness since you don't have debug symbols for
mutter available.
The easiest way to get the debug symbols is to use:
DEBUGINFOD_URLS="https://debuginfod.debian.net" coredumpctl gdb
and type "bt" at the (gdb) prompt when the symbols have finished
downloading.
Or you could enable the debug symbols apt repository (see
https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols)
and install the libmutter-12-0-dbgsym package. We don't need any other
packages for this particular crash.
In general we can't get a useful backtrace from the actual compressed
core dump: that's something that the bug reporter needs to do. I tried to
get a useful backtrace from this with debug symbols, but it doesn't match
the result you sent and I'm not sure whether it really makes sense.
Sharing these core dumps is also a privacy risk because they can contain
private information, although in this case the crash was from the gdm
login screen before you had a chance to enter any passwords, so it's
probably harmless.
smcv
Hi, Partial output as below and full output as per link. Thanks. https://drive.google.com/file/d/19pahjyQSf_PRw-zQDwtC9FWRPcGQvUfo/view?usp=sharing # DEBUGINFOD_URLS="https://debuginfod.debian.net" coredumpctl gdb PID: 1720 (gnome-shell) UID: 117 (Debian-gdm) GID: 122 (Debian-gdm) Signal: 11 (SEGV) Timestamp: Sat 2023-09-09 19:13:27 +08 (1 day 12h ago) Command Line: /usr/bin/gnome-shell Executable: /usr/bin/gnome-shell Control Group: /user.slice/user-117.slice/session-c1.scope Unit: session-c1.scope Slice: user-117.slice Session: c1 Owner UID: 117 (Debian-gdm) Boot ID: db5045b3be454eabaf40ab7634cdd15f Machine ID: e2ff68e6a046472b82838d16f35a6e1f Hostname: meixian Storage: /var/lib/systemd/coredump/core.gnome-shell.117.db5045b3be454eabaf40ab7634cdd15f.1720.1694258007000000.zst (present) Size on Disk: 6.4M Message: Process 1720 (gnome-shell) of user 117 dumped core. Module libudev.so.1 from deb systemd-254.1-2.amd64 Module libsystemd.so.0 from deb systemd-254.1-2.amd64 Stack trace of thread 1720: #0 0x00007f9e956ced54 meta_display_get_x11_display (libmutter-12.so.0 + 0xced54) #1 0x00007f9e956f9a3b n/a (libmutter-12.so.0 + 0xf9a3b) #2 0x00007f9e95e95f8f g_initable_new_valist (libgio-2.0.so.0 + 0x7df8f) #3 0x00007f9e95e96069 g_initable_new (libgio-2.0.so.0 + 0x7e069) #4 0x00007f9e956f9dda n/a (libmutter-12.so.0 + 0xf9dda) #5 0x00007f9e956fd5ce n/a (libmutter-12.so.0 + 0xfd5ce) #6 0x00007f9e956fd62d n/a (libmutter-12.so.0 + 0xfd62d) #7 0x00007f9e9568b04e meta_cursor_tracker_get_sprite (libmutter-12.so.0 + 0x8b04e) #8 0x00007f9e94d4cf7a n/a (libffi.so.8 + 0x6f7a) #9 0x00007f9e94d4c40e n/a (libffi.so.8 + 0x640e) #10 0x00007f9e94d4cb0d ffi_call (libffi.so.8 + 0x6b0d) Regards, Hor Jiun Shyong 何俊雄 Simon McVittie <smcv@debian.org> 于2023年9月11日周一 01:40写道:
Hi, on 17 Sep, I have reinstall gnome-shell. An additional new package package was installed too: policykit-1-gnome:amd64 (0.105-8, automatic) The issue was resolved and GNOME gdm3 is able to start successfully. Below are the packages involved. Thanks. Start-Date: 2023-09-17 12:17:15 Commandline: apt-get remove gnome-shell -V Install: policykit-1-gnome:amd64 (0.105-8, automatic) Remove: gnome-shell-extensions:amd64 (44.0-2), gnome-shell:amd64 (44.4-1), gdm3:amd64 (45~beta-1), chrome-gnome-shell:amd64 (42.1-4), gnome-session:amd64 (44.0-4), gnome-browser-connector:amd64 (42.1-4), gnome-shell-extension-prefs:amd64 (44.4-1) End-Date: 2023-09-17 12:17:21 Start-Date: 2023-09-17 12:17:44 Commandline: apt-get install gnome-shell -V Install: gnome-shell:amd64 (44.4-1), gdm3:amd64 (45~beta-1, automatic), chrome-gnome-shell:amd64 (42.1-4, automatic), gnome-session:amd64 (44.0-4, automatic), gnome-browser-connector:amd64 (42.1-4, automatic), gnome-shell-extension-prefs:amd64 (44.4-1, automatic) End-Date: 2023-09-17 12:17:53 Regards, Hor Jiun Shyong 何俊雄 +60-16-2089567
Hi,
After updating the below packages yesterday, the GDM3 white screen issue
returns. I have tried with reinstalling gnome-shell but it error still
persists. I have performed a backtrace with debugging symbols. Results are
as below. Thanks.
Start-Date: 2023-09-23 17:10:36
Commandline: apt-get dist-upgrade -V
Upgrade: gnome-text-editor:amd64 (45~beta-2, 45.0-1), libcups2:amd64
(2.4.2-5, 2.4.2-6), tecla:amd64 (45~rc-1, 45.0-1), gnome-user-docs:amd64
(44.3-2, 45.0-1), liferea:amd64 (1.15.2-1,
1.15.3-1),mutter-common-bin:amd64 (44.4-2, 44.5-1), eog:amd64 (45~rc-1,
45.0-1), libglib2.0-bin:amd64 (2.78.0-1, 2.78.0-2), cups-common:amd64
(2.4.2-5, 2.4.2-6), liferea-data:amd64 (1.15.2-1, 1.15.3-1), libgdm1:amd64
(45~beta-1, 45.0.1-1), libmutter-12-0:amd64 (44.4-2, 44.5-1),
cups-client:amd64 (2.4.2-5, 2.4.2-6), cups-ppdc:amd64 (2.4.2-5, 2.4.2-6),
cups-daemon:amd64 (2.4.2-5, 2.4.2-6), libshumate-common:amd64 (1.1~rc-1,
1.1.0-1), mutter-common:amd64 (44.4-2, 44.5-1), libglib2.0-data:amd64
(2.78.0-1, 2.78.0-2), gnome-calendar:amd64 (45~rc-1, 45.0-1),
libshumate-1.0-1:amd64 (1.1~rc-1, 1.1.0-1), cups-ipp-utils:amd64 (2.4.2-5,
2.4.2-6), gdm3:amd64 (45~beta-1, 45.0.1-1), gir1.2-mutter-12:amd64
(44.4-2, 44.5-1), gir1.2-shumate-1.0:amd64 (1.1~rc-1, 1.1.0-1),
gnome-music:amd64 (44.0-2, 45.0-1), gir1.2-gdm-1.0:amd64 (45~beta-1,
45.0.1-1), bash-completion:amd64 (1:2.11-7, 1:2.11-8), libglib2.0-0:amd64
(2.78.0-1, 2.78.0-2), cups-core-drivers:amd64 (2.4.2-5, 2.4.2-6),
gnome-characters:amd64 (45~alpha-2, 45.0-1), cups:amd64 (2.4.2-5, 2.4.2-6),
sysvinit-utils:amd64 (3.07-1, 3.08-1), libqt5designer5:amd64 (5.15.10-3,
5.15.10-5), cups-server-common:amd64 (2.4.2-5, 2.4.2-6), gnome-clocks:amd64
(44.0-2, 45.0-1), libqt5help5:amd64 (5.15.10-3, 5.15.10-5)
End-Date: 2023-09-23 17:11:29
*Backtrace*
Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 meta_display_get_x11_display (display=0x0) at ../src/core/display.c:2513
Download failed: Invalid argument. Continuing without source file
./obj-x86_64-linux-gnu/../src/core/display.c.
2513 ../src/core/display.c: No such file or directory.
[Current thread is 1 (Thread 0x7fb206184e00 (LWP 1761))]
(gdb) bt
#0 meta_display_get_x11_display (display=0x0) at ../src/core/display.c:2513
#1 0x00007fb20aaf9b3b in meta_cursor_sprite_xfixes_initable_init
(initable=0x55724b0cd7c0, cancellable=<optimized out>, error=0x7ffc13ebd0b0)
at ../src/backends/x11/cm/meta-cursor-sprite-xfixes.c:134
#2 0x00007fb20b26d3d3 in g_initable_new_valist (object_type=<optimized
out>, first_property_name=0x7fb20abafb8e "display",
var_args=var_args@entry=0x7ffc13ebcfa0,
cancellable=cancellable@entry=0x0, error=error@entry=0x7ffc13ebd0b0) at
../../../gio/ginitable.c:250
#3 0x00007fb20b26d4bd in g_initable_new (object_type=<optimized out>,
cancellable=cancellable@entry=0x0, error=error@entry=0x7ffc13ebd0b0,
first_property_name=first_property_name@entry=0x7fb20abafb8e "display")
at ../../../gio/ginitable.c:164
#4 0x00007fb20aaf9eda in meta_cursor_sprite_xfixes_new (display=0x0,
cursor_tracker=cursor_tracker@entry=0x557249ae82c0, error=error@entry
=0x7ffc13ebd0b0)
at ../src/backends/x11/cm/meta-cursor-sprite-xfixes.c:110
#5 0x00007fb20aafd6ee in ensure_xfixes_cursor
(tracker_x11=tracker_x11@entry=0x557249ae82c0) at
../src/backends/x11/meta-cursor-tracker-x11.c:94
#6 0x00007fb20aafd74d in meta_cursor_tracker_x11_get_sprite
(tracker=0x557249ae82c0) at
../src/backends/x11/meta-cursor-tracker-x11.c:162
#7 0x00007fb20aa8b05e in meta_cursor_tracker_get_sprite
(tracker=<optimized out>) at ../src/backends/meta-cursor-tracker.c:365
#8 0x00007fb20a0bbf7a in ffi_call_unix64 () at ../src/x86/unix64.S:104
#9 0x00007fb20a0bb40e in ffi_call_int (cif=cif@entry=0x55724ad81410,
fn=fn@entry=0x7fb20aa8b050 <meta_cursor_tracker_get_sprite>,
rvalue=<optimized out>,
rvalue@entry=0x7ffc13ebd2e8, avalue=<optimized out>,
closure=closure@entry=0x0) at ../src/x86/ffi64.c:673
#10 0x00007fb20a0bbb0d in ffi_call (cif=0x55724ad81410, fn=0x7fb20aa8b050
<meta_cursor_tracker_get_sprite>, rvalue=0x7ffc13ebd2e8, avalue=<optimized
out>)
at ../src/x86/ffi64.c:710
#11 0x00007fb20af01fa7 in Gjs::Function::invoke (this=<optimized out>,
context=0x55724a2f63e0, args=..., this_obj=..., r_value=<optimized out>)
at ./obj-x86_64-linux-gnu/../gi/function.cpp:1048
#12 0x00007fb20af02698 in Gjs::Function::call (context=0x55724a2f63e0,
js_argc=<optimized out>, vp=<optimized out>) at
./obj-x86_64-linux-gnu/../gi/function.cpp:1228
#13 0x00007fb208196650 in CallJSNative (args=...,
reason=js::CallReason::Call, native=0x7fb20af025b0
<Gjs::Function::call(JSContext*, unsigned int, JS::Value*)>,
cx=0x55724a2f63e0) at ./js/src/vm/Interpreter.cpp:420
#14 js::InternalCallOrConstruct (cx=0x55724a2f63e0, args=...,
construct=<optimized out>, reason=js::CallReason::Call) at
./js/src/vm/Interpreter.cpp:493
#15 0x00007fb208189d97 in InternalCall (reason=<optimized out>, args=...,
cx=<optimized out>) at ./js/src/vm/Interpreter.cpp:574
#16 js::CallFromStack (args=..., cx=<optimized out>) at
./js/src/vm/Interpreter.cpp:578
#17 Interpret (cx=0x55724a2f63e0, state=...) at
./js/src/vm/Interpreter.cpp:3314
#18 0x00007fb208195d6d in js::RunScript (cx=cx@entry=0x55724a2f63e0,
state=...) at ./js/src/vm/Interpreter.cpp:389
#19 0x00007fb2081981e9 in js::ExecuteKernel (result=..., evalInFrame=...,
envChainArg=..., script=..., cx=0x55724a2f63e0) at
./js/src/vm/Interpreter.cpp:781
#20 js::Execute (cx=0x55724a2f63e0, script=script@entry=...,
envChain=envChain@entry=..., rval=...) at ./js/src/vm/Interpreter.cpp:813
#21 0x00007fb2081f2148 in js::ModuleObject::execute (cx=<optimized out>,
self=self@entry=..., rval=...) at ./js/src/builtin/ModuleObject.cpp:1249
#22 0x00007fb2083631e4 in intrinsic_ExecuteModule (cx=<optimized out>,
argc=<optimized out>, vp=<optimized out>) at
./js/src/vm/SelfHosting.cpp:1891
#23 0x00002b78f24f94e0 in ?? ()
#24 0x00002b78f24f55e8 in ?? ()
#25 0x00007ffc13ebdbd0 in ?? ()
#26 0x0000000000000000 in ?? ()
Regards,
Hor Jiun Shyong 何俊雄
Hor Jiun Shyong <jiunshyong@gmail.com> 于2023年9月11日周一 08:22写道: