Bug 2175908 - [abrt] gnome-shell: wl_resource_get_client(): gnome-shell killed by SIGSEGV
Summary: [abrt] gnome-shell: wl_resource_get_client(): gnome-shell killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 38
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:36024fbbe1b8bb5f1fedf1ba476...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-06 18:28 UTC by Nikita
Modified: 2024-05-21 14:29 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-21 14:29:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: proc_pid_status (1.41 KB, text/plain)
2023-03-06 18:28 UTC, Nikita
no flags Details
File: maps (3.97 KB, text/plain)
2023-03-06 18:28 UTC, Nikita
no flags Details
File: limits (1.29 KB, text/plain)
2023-03-06 18:28 UTC, Nikita
no flags Details
File: environ (2.65 KB, text/plain)
2023-03-06 18:28 UTC, Nikita
no flags Details
File: open_fds (13.98 KB, text/plain)
2023-03-06 18:28 UTC, Nikita
no flags Details
File: mountinfo (3.59 KB, text/plain)
2023-03-06 18:28 UTC, Nikita
no flags Details
File: os_info (756 bytes, text/plain)
2023-03-06 18:28 UTC, Nikita
no flags Details
File: cpuinfo (2.67 KB, text/plain)
2023-03-06 18:28 UTC, Nikita
no flags Details
File: core_backtrace (72.22 KB, text/plain)
2023-03-06 18:28 UTC, Nikita
no flags Details
File: exploitable (81 bytes, text/plain)
2023-03-06 18:28 UTC, Nikita
no flags Details
File: var_log_messages (170 bytes, text/plain)
2023-03-06 18:28 UTC, Nikita
no flags Details
File: backtrace (40.51 KB, text/plain)
2023-03-06 18:28 UTC, Nikita
no flags Details

Description Nikita 2023-03-06 18:28:04 UTC
Description of problem:
I opened VS Code "Save as" dialog, the file dialog hung a bit, and then GNOME Shell crashed, bringing me to GDM.

Version-Release number of selected component:
gnome-shell-44~beta-2.fc38

Additional info:
reporter:       libreport-2.17.7
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=b8786f10ea9342618ffa7e4a213694d0;i=1b95f;b=28effbbdb94b40a383646bc1d37b2e85;m=a7c8d59a6;t=5f63f424b74d0;x=71c3827eef84ea09
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.2.0-63.fc38.x86_64
package:        gnome-shell-44~beta-2.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: wl_resource_get_client
comment:        I opened VS Code "Save as" dialog, the file dialog hung a bit, and then GNOME Shell crashed, bringing me to GDM.

Truncated backtrace:
Thread no. 0 (16 frames)
 #0 wl_resource_get_client at ../src/wayland-server.c:799
 #1 meta_wayland_keyboard_get_focus_client at ../src/wayland/meta-wayland-keyboard.c:820
 #2 owner_changed_cb at ../src/wayland/meta-wayland-data-device-primary.c:214
 #3 ffi_call_unix64 at ../src/x86/unix64.S:104
 #4 ffi_call_int at ../src/x86/ffi64.c:673
 #5 ffi_call at ../src/x86/ffi64.c:710
 #6 g_cclosure_marshal_generic at ../gobject/gclosure.c:1536
 #8 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3802
 #11 meta_x11_selection_shutdown at ../src/x11/meta-x11-selection.c:545
 #12 meta_x11_display_dispose at ../src/x11/meta-x11-display.c:167
 #14 meta_display_shutdown_x11 at ../src/core/display.c:848
 #16 xserver_died at ../src/wayland/meta-xwayland.c:448
 #17 g_task_return_now at ../gio/gtask.c:1309
 #18 complete_in_idle_cb at ../gio/gtask.c:1323
 #22 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276
 #24 meta_context_run_main_loop at ../src/core/meta-context.c:482

Comment 1 Nikita 2023-03-06 18:28:08 UTC
Created attachment 1948471 [details]
File: proc_pid_status

Comment 2 Nikita 2023-03-06 18:28:10 UTC
Created attachment 1948472 [details]
File: maps

Comment 3 Nikita 2023-03-06 18:28:12 UTC
Created attachment 1948473 [details]
File: limits

Comment 4 Nikita 2023-03-06 18:28:15 UTC
Created attachment 1948474 [details]
File: environ

Comment 5 Nikita 2023-03-06 18:28:17 UTC
Created attachment 1948475 [details]
File: open_fds

Comment 6 Nikita 2023-03-06 18:28:19 UTC
Created attachment 1948476 [details]
File: mountinfo

Comment 7 Nikita 2023-03-06 18:28:21 UTC
Created attachment 1948477 [details]
File: os_info

Comment 8 Nikita 2023-03-06 18:28:23 UTC
Created attachment 1948478 [details]
File: cpuinfo

Comment 9 Nikita 2023-03-06 18:28:25 UTC
Created attachment 1948479 [details]
File: core_backtrace

Comment 10 Nikita 2023-03-06 18:28:26 UTC
Created attachment 1948480 [details]
File: exploitable

Comment 11 Nikita 2023-03-06 18:28:28 UTC
Created attachment 1948481 [details]
File: var_log_messages

Comment 12 Nikita 2023-03-06 18:28:30 UTC
Created attachment 1948482 [details]
File: backtrace

Comment 13 Nikita 2023-04-25 06:02:40 UTC
I clicked "Open Folder.." on a Welcome screen, then VS Code opened xdg-desktop-portal, and then gnome-shell crashed, taking me to GDM.


reporter:       libreport-2.17.9
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=a54ed9ff6bf742ee91ef153ef1066873;i=256de8;b=4a853368c2a1468a9650b7158e0cfa9c;m=b1d353cf5;t=5fa224c005bf1;x=8d6c8ce9e179f6a8
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.2.11-300.fc38.x86_64
package:        gnome-shell-44.0-4.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: wl_resource_get_client
comment:        I clicked "Open Folder.." on a Welcome screen, then VS Code opened xdg-desktop-portal, and then gnome-shell crashed, taking me to GDM.

Comment 14 Alex 2023-06-21 08:54:08 UTC
I was working mainly with 3 win10 VM under Virtual Box 7.0 (installed from Oracle RPM package) and "Only Office" spreadsheet, when the desktop environment has freezed and crashed it.
After that the Gnome session has been closed.
I'm working with a ASUS ROG Zephyrus G14 (2022) [GA402RK] with a custom kernel from the ASUS Linux group.


reporter:       libreport-2.17.10
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=787473255d6e41b69ccb9e0fb9032bcf;i=a162f;b=c3b789c8534a4686879fc2c0cdbe8f96;m=190f1bacc;t=5fe9f94c24464;x=fa5dfe614eed2aa
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.3.8-204.rog.fc38.x86_64
package:        gnome-shell-44.2-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: wl_resource_get_client

Comment 15 Mathias Nicolajsen Kjærgaard 2023-08-01 16:07:41 UTC
Switched between applications - from Chrome to IntelliJ IDEA


reporter:       libreport-2.17.11
package:        gnome-shell-44.3-1.fc38
backtrace_rating: 4
reason:         gnome-shell killed by SIGSEGV
kernel:         6.4.6-200.fc38.x86_64
rootdir:        /
runlevel:       N 5
executable:     /usr/bin/gnome-shell
crash_function: wl_resource_get_client
journald_cursor: s=1ebfeb05b15f4a3f90c193bc07855763;i=b8743;b=2a23e3b80f6a448c84ec82c011db1775;m=24c40bef2a;t=601db851a9692;x=f29ff5db97ba23d1
type:           CCpp
comment:        Switched between applications - from Chrome to IntelliJ IDEA
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
cmdline:        /usr/bin/gnome-shell
uid:            1000

Comment 16 Mathias Nicolajsen Kjærgaard 2023-08-01 16:16:28 UTC
The crash happened at the same time as a crash in Xwayland: https://bugzilla.redhat.com/show_bug.cgi?id=2191684
Probably related to the Nouveau graphics driver.

Comment 17 Maxim Therrien 2023-08-10 16:18:04 UTC
Using touchscreen to navigate GNOME Shell. Opened VSCode, GNOME shell unexpectedly crashed.


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=79f6cf1eabe047be88a5c5743570eb37;i=8be35;b=3c85bcf80aff4529a146ad5fa1729ba1;m=3173fd0ab;t=60293da2aa790;x=b96219d1e455a597
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         6.4.7-200.fc38.x86_64
package:        gnome-shell-44.3-1.fc38
runlevel:       N 5
dso_list:       /usr/bin/gnome-shell gnome-shell-44.3-1.fc38.x86_64 (Fedora Project) 1691511008
backtrace_rating: 4
crash_function: wl_resource_get_client
comment:        Using touchscreen to navigate GNOME Shell. Opened VSCode, GNOME shell unexpectedly crashed.

Comment 18 Fedora Admin user for bugzilla script actions 2023-12-06 08:22:06 UTC
This component is maintained by the GNOME project. Issues with it should be reported directly to GNOME at https://gitlab.gnome.org/GNOME/.

This issue should only be kept open if it:

1. Relates to Fedora packaging or integration with other Fedora components
2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions

If this issue isn't needed for either of these two reasons, please:

 * create an issue with GNOME
 * add a link to the GNOME issue here
 * close this issue as CLOSED/UPSTREAM

Thank you!

Comment 19 Aoife Moloney 2024-05-07 15:58:40 UTC
This message is a reminder that Fedora Linux 38 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21.
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 '38'.

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. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 38 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 20 Aoife Moloney 2024-05-21 14:29:35 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 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.


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