Bug 2072026

Summary: [abrt] gnome-shell: g_list_prepend(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: martin.kuehl
Component: mutterAssignee: Florian Müllner <fmuellner>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: adscvr, fmuellner, gnome-sig, jadahl, otaylor, philip.wyett, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a02ce2aa8a82cbfbbad311e2dd73583f49ef8c12
Whiteboard: abrt_hash:7f4b0e695676ae045ba80e7b81b092b45a2b29ba;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 17:31:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description martin.kuehl 2022-04-05 12:45:05 UTC 
Description of problem:
#2072025 had just happened (xwayland crashed) and i was starting to realize that all xwayland clients were gone when i got kicked out of my gnome session

Version-Release number of selected component:
gnome-shell-41.4-1.fc35

Additional info:
reporter:       libreport-2.15.2
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
cmdline:        /usr/bin/gnome-shell
crash_function: g_list_prepend
dso_list:       /usr/bin/gnome-shell gnome-shell-41.4-1.fc35.x86_64 (Fedora Project) 1645078666
executable:     /usr/bin/gnome-shell
journald_cursor: s=044c789f093649b590ef38db76515f97;i=3a4fe1;b=a75e3586b5b44d44b6554352157693e3;m=40fcf15c9;t=5dbe6a2deadcb;x=97a3168bb070179f
kernel:         5.16.18-200.fc35.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_list_prepend at ../glib/glist.c:341
 #1 meta_x11_selection_input_stream_new_async at ../src/x11/meta-x11-selection-input-stream.c:523
 #2 meta_selection_source_x11_read_async at ../src/x11/meta-selection-source-x11.c:94
 #3 meta_x11_selection_handle_selection_request at ../src/x11/meta-x11-selection.c:291
 #4 meta_x11_selection_handle_event at ../src/x11/meta-x11-selection.c:445
 #5 process_selection_event at ../src/x11/events.c:1833
 #6 meta_x11_display_handle_xevent at ../src/x11/events.c:1900
 #7 xevent_filter at ../src/x11/events.c:2018
 #8 gdk_event_apply_filters at ../gdk/x11/gdkeventsource.c:79
 #9 gdk_event_source_translate_event at ../gdk/x11/gdkeventsource.c:198
Comment 1 martin.kuehl 2022-04-05 12:45:09 UTC 
Created attachment 1870851 [details]
File: backtrace
Comment 2 martin.kuehl 2022-04-05 12:45:12 UTC 
Created attachment 1870852 [details]
File: core_backtrace
Comment 3 martin.kuehl 2022-04-05 12:45:13 UTC 
Created attachment 1870853 [details]
File: cpuinfo
Comment 4 martin.kuehl 2022-04-05 12:45:15 UTC 
Created attachment 1870854 [details]
File: environ
Comment 5 martin.kuehl 2022-04-05 12:45:16 UTC 
Created attachment 1870855 [details]
File: exploitable
Comment 6 martin.kuehl 2022-04-05 12:45:17 UTC 
Created attachment 1870856 [details]
File: limits
Comment 7 martin.kuehl 2022-04-05 12:45:19 UTC 
Created attachment 1870857 [details]
File: maps
Comment 8 martin.kuehl 2022-04-05 12:45:20 UTC 
Created attachment 1870858 [details]
File: mountinfo
Comment 9 martin.kuehl 2022-04-05 12:45:22 UTC 
Created attachment 1870859 [details]
File: open_fds
Comment 10 martin.kuehl 2022-04-05 12:45:23 UTC 
Created attachment 1870860 [details]
File: proc_pid_status
Comment 11 martin.kuehl 2022-04-05 12:45:25 UTC 
Created attachment 1870861 [details]
File: var_log_messages
Comment 12 Jonas Ådahl 2022-04-06 09:52:53 UTC 
Thanks for the report; I managed to reproduce with a test case, and come up with a fix.
Comment 13 Ben Cotton 2022-11-29 18:42:16 UTC 
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 14 Ben Cotton 2022-12-13 17:31:53 UTC 
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.