Ubuntu
gnome-shell package

gnome-shell crashed with signal 5 in _XEventsQueued()

Bug #2015647 reported by Erich Eickmeyer
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Crash happened upon boot.

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Apr 8 11:53:30 2023
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2023-03-04 (34 days ago)
InstallationMedia: Edubuntu 23.04 "Lunar Lobster" - Alpha amd64 Binary-1 (20230304)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/false
 XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 44.0-2ubuntu3
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
 XPending () from /lib/x86_64-linux-gnu/libX11.so.6
 g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 XPending (dpy=0x560906913030) at ../../src/Pending.c:55
 g_main_context_check (context=0x5609068633b0, max_priority=0, fds=<optimized out>, n_fds=<optimized out>) at ../../../glib/gmain.c:4093
 g_main_context_iterate.constprop.0 (context=0x5609068633b0, block=<optimized out>, dispatch=1, self=<optimized out>) at ../../../glib/gmain.c:4273
 g_main_loop_run (loop=0x5609086d08d0) at ../../../glib/gmain.c:4479
 meta_context_run_main_loop (context=context@entry=0x560906861780, error=error@entry=0x7ffeb4b15318) at ../src/core/meta-context.c:482

tags: removed: need-amd64-retrace
Erich Eickmeyer (eeickmeyer)
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007f7748ee4f67 in ?? ()
 No symbol table info available.
 #1 0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceSource:
 #0 0x00007f7748ee4f67 in ?? ()
 #1 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for libnvidia-gl-525
no debug symbol package found for libnvidia-gl-510

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Duplicate of bug 2015027 (bug 2014986)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.