*** This bug is a duplicate of bug 2099658 ***
https://bugs.launchpad.net/bugs/2099658
Managed to reproduce the crash while attached to gdb, and here's the
stacktrace from 48.0:
#0 0x0000739de1c1cad0 in meta_kms_cursor_manager_update_sprite
(cursor_manager=0x0, crtc=0x739db4005830, buffer=0x5d0fe3148220,
transform=MTK_MONITOR_TRANSFORM_NORMAL, hotspot=0x7fff03f384b0) at
../src/backends/native/meta-kms-cursor-manager.c:794
data = 0x5d0fe32c3e90
data = <optimized out>
__n = <optimized out>
__s = <optimized out>
__p = <optimized out>
#1 load_cursor_sprite_gbm_buffer_for_crtc.isra.0 (native=<error reading
variable: Cannot access memory at address 0x7fff03f38488>, crtc_kms=<error
reading variable: Cannot access memory at address 0x7fff03f38460>,
pixels=pixels@entry=0x5d0fe2584b70 <error: Cannot access memory at address
0x5d0fe2584b70>, width=<optimized out>, height=<optimized out>,
rowstride=rowstride@entry=120, hotspot=0x7fff03f384b0,
transform=MTK_MONITOR_TRANSFORM_NORMAL, gbm_format=Python Exception <class
'gdb.MemoryError'>: Cannot access memory at address 0x7fff03f38440
#2 0x0000739de1bd0b2e in load_scaled_and_transformed_cursor_sprite
(native=Python Exception <class 'gdb.MemoryError'>: Cannot access memory at
address 0x7fff03f38488
#3 0x0000739de1bd16c0 in realize_cursor_sprite_from_xcursor_for_crtc
(renderer=Python Exception <class 'gdb.MemoryError'>: Cannot access memory at
address 0x7fff03f385c0
#4 realize_cursor_sprite_for_crtc (renderer=<optimized out>, crtc_kms=<error
reading variable: Cannot access memory at address 0x7fff03f38520>,
target_color_state=Python Exception <class 'gdb.MemoryError'>: Cannot access
memory at address 0x7fff03f385d8
#5 meta_cursor_renderer_native_update_cursor (cursor_renderer=Python Exception
<class 'gdb.MemoryError'>: Cannot access memory at address 0x7fff03f385c0
Indeed this is a duplicate of bug 2099658 then. Stacktrace looks a bit
different, possibly because of fractional scaling?
Also no idea why apport couldn't get a proper coredump. GDB's stacktrace
is also full of <Cannot access memory at address> ¯\_(ツ)_/¯
** This bug has been marked a duplicate of bug 2099658
gnome-shell crashed with SIGSEGV in meta_kms_cursor_manager_update_sprite()
during shutdown/logout
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2103700
Title:
gnome-shell crashed with SIGSEGV on logout
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
I've seen multiple times in plucky apport report a gnome-shell SIGSEGV
shortly after login (< 1min), but the session keeps running normally.
ProblemType: Crash
DistroRelease: Ubuntu 25.04
Package: gnome-shell 48~rc-2ubuntu3
ProcVersionSignature: Ubuntu 6.14.0-11.11-generic 6.14.0-rc7
Uname: Linux 6.14.0-11-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.32.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 20 10:59:53 2025
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2024-06-16 (277 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 48~rc-4ubuntu2
Signal: 11
SignalName: SIGSEGV
SourcePackage: gnome-shell
Stacktrace:
#0 0x00007d96978a50bc in ?? ()
No symbol table info available.
Backtrace stopped: Cannot access memory at address 0x7ffdf32656b0
StacktraceTop: ?? ()
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: Upgraded to plucky on 2025-03-06 (14 days ago)
UserGroups: adm cdrom dip libvirt lpadmin lxd mock plugdev sbuild sudo users
wireshark
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2103700/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
