Bug 2110936 - gnome-shell crashes - probably on The error was 'BadWindow (invalid Window parameter)'.
Summary: gnome-shell crashes - probably on The error was 'BadWindow (invalid Window pa...
Keywords:
Status: CLOSED DUPLICATE of bug 2110041
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-26 08:27 UTC by Martin Sehnoutka
Modified: 2022-07-26 11:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-26 11:14:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Martin Sehnoutka 2022-07-26 08:27:24 UTC
Description of problem:
As described in the Bodhi update in the negative karma comment:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-0ce968f910
gnome crashes, screen goes black, ctrl+c returns me to back to GDM.

Version-Release number of selected component (if applicable):
gnome-shell-41.8.1-1.fc35

How reproducible:
not sure, but happened already 4 times today

Steps to Reproduce:
1. start gnome
2. use it
3. wait until it crashes

Actual results:
Jul 26 09:53:45 m.artin.hp gnome-shell[2598]: The program 'gnome-shell' received an X Window System error.
                                              This probably reflects a bug in the program.
                                              The error was 'BadWindow (invalid Window parameter)'.
                                                (Details: serial 8661 error_code 3 request_code 22 (core protocol) minor_code 0)
                                                (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 GDK_SYNCHRONIZE environment
                                                 variable to change this behavior. You can then get a meaningful
                                                 backtrace from your debugger if you break on the gdk_x_error() function.)
Jul 26 09:53:45 m.artin.hp tilix[7587]: Error reading events from display: Connection reset by peer
Jul 26 09:53:45 m.artin.hp xdg-desktop-por[3901]: Error reading events from display: Broken pipe
Jul 26 09:53:45 m.artin.hp xdg-desktop-por[3883]: Error reading events from display: Broken pipe
Jul 26 09:53:45 m.artin.hp firefox[5085]: Error reading events from display: Broken pipe
Jul 26 09:53:45 m.artin.hp gnome-calendar[3664]: Error reading events from display: Broken pipe
Jul 26 09:53:45 m.artin.hp evolution-alarm[2975]: Error reading events from display: Broken pipe
Jul 26 09:53:45 m.artin.hp gsd-media-keys[2908]: Error reading events from display: Broken pipe
Jul 26 09:53:45 m.artin.hp gsd-wacom[2926]: Error reading events from display: Broken pipe
Jul 26 09:53:45 m.artin.hp gsd-power[2911]: Error reading events from display: Broken pipe
Jul 26 09:53:45 m.artin.hp gsd-keyboard[2902]: Error reading events from display: Broken pipe
Jul 26 09:53:45 m.artin.hp gsd-color[2892]: Error reading events from display: Broken pipe
Jul 26 09:53:45 m.artin.hp systemd[2466]: org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=exited, status=1/FAILURE

Additional info:
According to lotussteve from Bodhi, it gets fixed by downgrade. I'm currently running gnome-shell-41.0-4.fc35.x86_64 and it hasn't crashed yet.

Comment 1 Martin Sehnoutka 2022-07-26 08:44:53 UTC
No, downgrade did not help. I'm still experiencing the issue.

Comment 2 Jonas Ådahl 2022-07-26 09:28:46 UTC
Probably the same as https://bugzilla.redhat.com/show_bug.cgi?id=2110041; please try the update linked in that bug.

Comment 3 Martin Sehnoutka 2022-07-26 11:14:13 UTC
Yes, that's exactly it. I've tried to "fix" the issue with upgrade to f36 and so far, it seems to work (for almost 2.5 hours now, which is a lot compared to 10 minutes before the upgrade). I'm closing this bug as a duplicate of #2110041.

Thanks for the quick reply!

*** This bug has been marked as a duplicate of bug 2110041 ***


Note You need to log in before you can comment on or make changes to this bug.