gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) minor_code 57)]

Bug #2014986 reported by Valtýr Kári Daníelsson
108
This bug affects 11 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
High
Unassigned
mutter (Ubuntu)
Fix Released
High
Daniel van Vugt

Bug Description

https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sun Apr 2 01:49:43 2023
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2023-03-30 (2 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 44.0-2ubuntu2
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_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in _XEventsQueued()
UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago)
UserGroups: N/A
separator:

Revision history for this message
Valtýr Kári Daníelsson (fixgoats) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 XPending (dpy=0x5575647c98d0) at ../../src/Pending.c:55
 g_main_context_prepare (context=0x55756471a3b0, priority=0x7ffc06655650) at ../../../glib/gmain.c:3784
 g_main_context_iterate.constprop.0 (context=0x55756471a3b0, block=1, dispatch=1, self=<optimized out>) at ../../../glib/gmain.c:4256
 g_main_loop_run (loop=0x5575665b4b60) at ../../../glib/gmain.c:4479
 meta_context_run_main_loop (context=context@entry=0x557564718780, error=error@entry=0x7ffc06655708) at ../src/core/meta-context.c:482

tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Seems to always be:

Received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 8835 error_code 8 request_code 131 (XInputExtension) minor_code 57)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the MUTTER_SYNC environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the meta_x_error() function.)

summary: - gnome-shell crashed with signal 5 in _XEventsQueued()
+ gnome-shell crashed with signal 5 in _XEventsQueued() [The error was
+ 'BadMatch (invalid parameter attributes)'. (Details: serial 8835
+ error_code 8 request_code 131 (XInputExtension) minor_code 57)]
summary: gnome-shell crashed with signal 5 in _XEventsQueued() [The error was
- 'BadMatch (invalid parameter attributes)'. (Details: serial 8835
+ 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx
error_code 8 request_code 131 (XInputExtension) minor_code 57)]
summary: - gnome-shell crashed with signal 5 in _XEventsQueued() [The error was
- 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx
- error_code 8 request_code 131 (XInputExtension) minor_code 57)]
+ [nvidia] gnome-shell crashed with signal 5 in _XEventsQueued() [The
+ error was 'BadMatch (invalid parameter attributes)'. (Details: serial
+ xxxx error_code 8 request_code 131 (XInputExtension) minor_code 57)]
tags: added: nvidia
Changed in nvidia-graphics-drivers-525 (Ubuntu):
status: New → Confirmed
Changed in gnome-shell (Ubuntu):
importance: Undecided → High
Changed in nvidia-graphics-drivers-525 (Ubuntu):
importance: Undecided → High
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: [nvidia] gnome-shell crashed with signal 5 in _XEventsQueued() [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) minor_code 57)]

Looks like most of the crash reports are from systems using the Nvidia driver, but then most Xorg sessions will be due to the Nvidia driver being installed.

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

See also bug 2015035.

summary: - [nvidia] gnome-shell crashed with signal 5 in _XEventsQueued() [The
- error was 'BadMatch (invalid parameter attributes)'. (Details: serial
- xxxx error_code 8 request_code 131 (XInputExtension) minor_code 57)]
+ [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch
+ (invalid parameter attributes)'. (Details: serial xxxx error_code 8
+ request_code 131 (XInputExtension) minor_code 57)]
Changed in xorg-server (Ubuntu):
status: New → Confirmed
importance: Undecided → High
tags: added: regression-release rls-ll-incoming
summary: - [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch
- (invalid parameter attributes)'. (Details: serial xxxx error_code 8
- request_code 131 (XInputExtension) minor_code 57)]
+ gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid
+ parameter attributes)'. (Details: serial xxxx error_code 8 request_code
+ 131 (XInputExtension) minor_code 57)]
no longer affects: nvidia-graphics-drivers-525 (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I think this might be originating from a call to XIChangeProperty() but I can't yet find any API mismatches between mutter and xserver-xorg-input-libinput. Although there are new properties upstream, neither of the packages in Ubuntu support them yet.

If anyone can reproduce one of these crashes then please help us to debug the issue by adding MUTTER_SYNC=1 to /etc/environment, then reboot and tell us what new crashes the system encounters.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xserver-xorg-input-libinput (Ubuntu):
status: New → Confirmed
Revision history for this message
Ken VanDine (ken-vandine) wrote :

I added MUTTER_SYNC=1 to my environment and got the attached crash file

Revision history for this message
Ken VanDine (ken-vandine) wrote :

Another crash file from what appears to be from the gdm instance of gnome-shell

Revision history for this message
Ken VanDine (ken-vandine) wrote :

Another crash file from gnome-shell running as gdm

Revision history for this message
Ken VanDine (ken-vandine) wrote :

Another crash file generated with waking from suspend

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Download full text (3.2 KiB)

Comment #11: Corrupt (bug 2015857)

Comment #13: Missing some debug symbols (library unloaded?!) but getting closer:

#10 0x00007f9a42e7e71f in () at /lib/x86_64-linux-gnu/libX11.so.6
#11 0x00007f9a434e4b50 in () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#12 0x00007f9a434e4dc4 in () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#13 0x00007f9a4347587f in () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#14 0x00007f9a43475a19 in () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#15 0x00007f9a43478a3f in () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#16 0x00007f9a434e40e1 in () at /lib/x86_64-linux-gnu/libmutter-12.so.0
#17 0x00007f9a43713ebb in clutter_seat_handle_event_post ()
    at /usr/lib/x86_64-linux-gnu/mutter-12/libmutter-clutter-12.so.0
#18 0x00007f9a43707183 in _clutter_process_event ()
    at /usr/lib/x86_64-linux-gnu/mutter-12/libmutter-clutter-12.so.0

Comment #14: SUCCESS!

#11 0x00007fed52e7e67f in XSync () at /lib/x86_64-linux-gnu/libX11.so.6
#12 0x00007fed52e7e71f in () at /lib/x86_64-linux-gnu/libX11.so.6
#13 0x00007fed534e4b50 in change_property
    (settings=<optimised out>, device=0x558b3a712470, property=<optimised out>, type=156, format=32, data=0x7ffe3f8a1b74, nitems=1)
    at ../src/backends/x11/meta-input-settings-x11.c:184
#14 0x00007fed534e4dc4 in meta_input_settings_x11_set_speed
    (settings=settings@entry=0x558b3a7073e0, device=0x558b3a712470, speed=speed@entry=0) at ../src/backends/x11/meta-input-settings-x11.c:249
#15 0x00007fed5347587f in settings_device_set_double_setting
    (value=0, func=0x7fed534e4d50 <meta_input_settings_x11_set_speed>, device=<optimised out>, input_settings=0x558b3a7073e0)
    at ../src/backends/meta-input-settings.c:231
#16 settings_set_double_setting
    (value=0, func=0x7fed534e4d50 <meta_input_settings_x11_set_speed>, unset_capabilities=CLUTTER_INPUT_CAPABILITY_TOUCHPAD, capabilities=CLUTTER_INPUT_CAPABILITY_POINTER, input_settings=0x558b3a7073e0)
    at ../src/backends/meta-input-settings.c:248
#17 update_device_speed (input_settings=0x558b3a7073e0, device=<optimised out>)
    at ../src/backends/meta-input-settings.c:511
#18 0x00007fed53475a19 in apply_device_settings
    (input_settings=0x558b3a7073e0, device=0x0)
    at ../src/backends/meta-input-settings.c:1483
#19 0x00007fed53478a3f in meta_input_settings_remove_device
    (input_settings=0x558b3a7073e0, device=0x558b3a6f8140)
    at ../src/backends/meta-input-settings.c:1629
--Type <RET> for more, q to quit, c to continue without paging--
#20 0x00007fed534e40e1 in meta_seat_x11_handle_event_post
    (event=0x558b3d639db0, seat=0x558b3a6dbc70)
    at ../src/backends/x11/meta-seat-x11.c:836
#21 meta_seat_x11_handle_event_post (seat=0x558b3a6dbc70, event=0x558b3d639db0)
    at ../src/backends/x11/meta-seat-x11.c:810
#22 0x00007fed53713ebb in clutter_seat_handle_event_post
    (seat=0x558b3a6dbc70, event=0x558b3d639db0)
    at ../clutter/clutter/clutter-seat.c:598
#23 0x00007fed53707183 in _clutter_process_event (event=0x558b3d639db0)
    at ../clutter/clutter/clutter-main.c:919
#24 0x00007fed5371aa20 in _clutter_stage_process_queued_events
    (stage=0x558b3a6e8690) at ../clutter/clutter/clutter-stage.c:757
#25 0x00007fed53706f69 ...

Read more...

Changed in mutter (Ubuntu):
assignee: nobody → Daniel van Vugt (vanvugt)
importance: Undecided → High
status: New → In Progress
Changed in gnome-shell (Ubuntu):
status: Confirmed → Invalid
Changed in mutter (Ubuntu):
milestone: none → ubuntu-23.04
no longer affects: xorg-server (Ubuntu)
no longer affects: xserver-xorg-input-libinput (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Ken VanDine verified that the patch from merge request 2960 fixed his crashes.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mutter - 44.0-2ubuntu4

---------------
mutter (44.0-2ubuntu4) lunar; urgency=medium

  [ Daniel van Vugt ]
  * Add proposed patch to treat XIChangeProperty errors as warnings,
    fixes crash on login or resume from suspend with Nvidia graphics drivers
    (LP: #2014986)

 -- Jeremy Bícha <email address hidden> Fri, 14 Apr 2023 14:32:30 -0400

Changed in mutter (Ubuntu):
status: In Progress → Fix Released
tags: added: fixed-in-mutter-44.1 fixed-upstream
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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