Public bug reported:

The issue is happening 9 out of 10 times.
It is hard to get a crash dump in /var/crash during this error though, but I 
found one from few days ago. Looks like should be relevant.

I've reported it, see OOPS ID: b68253a2-ea4c-11ed-af33-fa163e55efd0

Laptop: Lenovo ThinkPad X1 Carbon Gen 10, model 21CB007WCK

root@x1:~# uname -a
Linux x1 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  6 07:48:48 
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux


To reproduce:
1. Win+L to lock the session
2. Screen turns black as expected
3. Login back to your session
4. Welcome to the new & clean session... all unsaved work is lost!
5. see gnome-shell segfault in libmutter-12.so in dmesg

root@x1:~# dmesg -T |grep segf
[Thu May  4 17:45:04 2023] gnome-shell[2554]: segfault at ffffffffffffff78 ip 
00007f3d10961115 sp 00007ffd72b85f78 error 5 in 
libmutter-12.so.0.0.0[7f3d1084a000+13d000] likely on CPU 0 (core 0, socket 0)
[Fri May  5 14:09:43 2023] gnome-shell[24568]: segfault at 11 ip 
00007f4c14161119 sp 00007ffd4590de28 error 4 in 
libmutter-12.so.0.0.0[7f4c1404a000+13d000] likely on CPU 9 (core 17, socket 0)


Logs from "ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash" command

May 04 09:24:31 x1 systemd[1]: Started whoopsie.service - crash report 
submission.
May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Using lock path: 
/var/lock/whoopsie/lock
May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Parsing 
/var/crash/_usr_bin_gnome-shell.1000.crash.
May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Uploading 
/var/crash/_usr_bin_gnome-shell.1000.crash.
May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Sent; server replied with: No 
error
May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Response code: 200
May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Reported OOPS ID 
b68253a2-ea4c-11ed-af33-fa163e55efd0


It was difficult to figure how to send the report in Ubuntu 23.04, previously 
it was just working... but with Ubuntu 23.04 there was this error:

May 04 09:21:33 x1 systemd[1]: Starting apport-autoreport.service - Process 
error reports when automatic reporting is enabled...
May 04 09:21:33 x1 systemd[1]: Started whoopsie.service - crash report 
submission.
May 04 09:21:33 x1 whoopsie[53709]: [09:21:33] Using lock path: 
/var/lock/whoopsie/lock
May 04 09:21:33 x1 systemd[1]: whoopsie.service: Deactivated successfully.
May 04 09:21:33 x1 whoopsie-upload-all[53708]: ERROR: whoopsie.path is not 
enabled
May 04 09:21:33 x1 systemd[1]: apport-autoreport.service: Main process exited, 
code=exited, status=1/FAILURE
May 04 09:21:33 x1 systemd[1]: apport-autoreport.service: Failed with result 
'exit-code'.
May 04 09:21:33 x1 systemd[1]: Failed to start apport-autoreport.service - 
Process error reports when automatic reporting is enabled.


Fixed by changing "Send error reports to Canonical" (in gnome control panel -> 
"Privacy" -> "Diagnostics") from "Automatic" to "Never" and re-running the 
`ubuntu-bug` command again.


gnome-shell 44.0-2ubuntu3
intel-media-va-driver:amd64 23.1.2+dfsg1-1


root@x1:~# lshw -class display
  *-display                 
       description: VGA compatible controller
       product: Alder Lake-P Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       logical name: /dev/fb0
       version: 0c
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
       configuration: depth=32 driver=i915 latency=0 mode=1920x1200 
resolution=1920,1200 visual=truecolor xres=1920 yres=1200
       resources: iomemory:600-5ff iomemory:400-3ff irq:199 
memory:603d000000-603dffffff memory:4000000000-400fffffff ioport:2000(size=64) 
memory:c0000-dffff memory:4010000000-4016ffffff memory:4020000000-40ffffffff

root@x1:~# lshw -class multimedia
  *-multimedia:0 UNCLAIMED  
       description: Multimedia controller
       product: Intel Corporation
       vendor: Intel Corporation
       physical id: 5
       bus info: pci@0000:00:05.0
       version: 02
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress pm cap_list
       configuration: latency=0
       resources: iomemory:600-5ff memory:603c000000-603cffffff
  *-multimedia:1
       description: Audio device
       product: Alder Lake PCH-P High Definition Audio Controller
       vendor: Intel Corporation
       physical id: 1f.3
       bus info: pci@0000:00:1f.3
       logical name: card0
       logical name: /dev/snd/controlC0
       logical name: /dev/snd/hwC0D0
       logical name: /dev/snd/hwC0D2
       logical name: /dev/snd/pcmC0D0c
       logical name: /dev/snd/pcmC0D0p
       logical name: /dev/snd/pcmC0D31p
       logical name: /dev/snd/pcmC0D3p
       logical name: /dev/snd/pcmC0D4p
       logical name: /dev/snd/pcmC0D5p
       logical name: /dev/snd/pcmC0D6c
       logical name: /dev/snd/pcmC0D7c
       version: 01
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi bus_master cap_list
       configuration: driver=sof-audio-pci-intel-tgl latency=64
       resources: iomemory:600-5ff iomemory:600-5ff irq:200 
memory:603ead8000-603eadbfff memory:603e900000-603e9fffff

** Affects: gnome-shell (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: gnome-shell libmutter mutter segfault

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2018455

Title:
  gnome-shell exits after screen lock / unlock & login segfault
  libmutter-12.so.0.0.0 in Ubuntu 23.04 on Lenovo X1 Carbon Gen10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018455/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to