Bug 2190350

Summary:

[abrt] gnome-shell: wl_resource_add_destroy_listener(): gnome-shell killed by SIGSEGV

Product:

[Fedora] Fedora

Reporter:

noname <oranges5>

Component:

gnome-shell

Assignee:

GNOME SIG Unassigned <gnome-sig>

Status:

CLOSED EOL

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

urgent

Docs Contact:

Priority:

unspecified

Version:

CC:

adscvr, fmuellner, gael, gnome-sig, jadahl, oranges5, otaylor, philip.wyett

Target Milestone:

---

Keywords:

AutomationTriaged

Target Release:

---

Hardware:

x86_64

OS:

Unspecified

URL:

https://retrace.fedoraproject.org/faf/reports/bthash/0f31f3a6689eff708be4d7a14bbf6038919bb0d

Whiteboard:

abrt_hash:f59b9ecaec0fdf37b07fcde45d12ea14aa139720;VARIANT_ID=workstation;

Fixed In Version:

Doc Type:

---

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2024-05-21 14:47:16 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: proc_pid_status	none
File: maps	none
File: limits	none
File: environ	none
File: open_fds	none
File: mountinfo	none
File: os_info	none
File: cpuinfo	none
File: core_backtrace	none
File: exploitable	none
File: dso_list	none
File: backtrace	none

Description noname 2023-04-28 04:39:22 UTC

Description of problem:
moving a window from a smaller resolution monitor placed on the left over to a 4k monitor caused window to automatically resize and then gnome crashed

Version-Release number of selected component:
gnome-shell-44.0-4.fc38

Additional info:
reporter:       libreport-2.17.9
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=5c0a45e741b34368951b741081883be0;i=10243;b=30a05e4b133e4ea98f1ea41c373de804;m=d580d1e96;t=5fa5e063cba58;x=f4cf625bda16eeee
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.12-200.fc37.x86_64
package:        gnome-shell-44.0-4.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: wl_resource_add_destroy_listener
comment:        moving a window from a smaller resolution monitor placed on the left over to a 4k monitor caused window to automatically resize and then gnome crashed

Truncated backtrace:
Thread no. 1 (30 frames)
 #0 wl_resource_add_destroy_listener at ../src/wayland-server.c:842
 #1 meta_wayland_keyboard_set_focus at ../src/wayland/meta-wayland-keyboard.c:791
 #2 meta_wayland_seat_set_input_focus at ../src/wayland/meta-wayland-seat.c:424
 #3 meta_wayland_compositor_set_input_focus at ../src/wayland/meta-wayland.c:156
 #4 meta_display_sync_wayland_input_focus at ../src/core/display.c:1354
 #5 meta_compositor_grab_end at ../src/compositor/compositor.c:377
 #6 meta_display_handle_event at ../src/core/events.c:242
 #7 event_callback at ../src/core/events.c:520
 #8 _clutter_event_process_filters at ../clutter/clutter/clutter-event.c:1691
 #9 clutter_stage_notify_grab_on_pointer_entry at ../clutter/clutter/clutter-stage.c:4027
 #10 clutter_stage_notify_grab at ../clutter/clutter/clutter-stage.c:4093
 #11 clutter_stage_unlink_grab at ../clutter/clutter/clutter-stage.c:4225
 #12 meta_window_drag_end at ../src/compositor/meta-window-drag.c:386
 #14 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3802
 #17 meta_window_unmanage at ../src/core/window.c:1431
 #18 meta_wayland_shell_surface_destroy_window at ../src/wayland/meta-wayland-shell-surface.c:305
 #19 xdg_toplevel_destructor at ../src/wayland/meta-wayland-xdg-shell.c:214
 #20 destroy_resource at ../src/wayland-server.c:732
 #21 wl_resource_destroy at ../src/wayland-server.c:749
 #22 meta_wayland_xdg_toplevel_finalize at ../src/wayland/meta-wayland-xdg-shell.c:1005
 #24 meta_wayland_surface_finalize at ../src/wayland/meta-wayland-surface.c:1465
 #26 destroy_resource at ../src/wayland-server.c:732
 #27 for_each_helper at ../src/wayland-util.c:416
 #28 wl_map_for_each at ../src/wayland-util.c:430
 #29 wl_client_destroy at ../src/wayland-server.c:928
 #30 wl_client_connection_data at ../src/wayland-server.c:343
 #31 wl_event_loop_dispatch at ../src/event-loop.c:1027
 #32 wayland_event_source_dispatch at ../src/wayland/meta-wayland.c:114
 #35 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276
 #37 meta_context_run_main_loop at ../src/core/meta-context.c:482

Comment 1 noname 2023-04-28 04:39:25 UTC

Created attachment 1960631 [details]
File: proc_pid_status

Comment 2 noname 2023-04-28 04:39:27 UTC

Created attachment 1960632 [details]
File: maps

Comment 3 noname 2023-04-28 04:39:28 UTC

Created attachment 1960633 [details]
File: limits

Comment 4 noname 2023-04-28 04:39:30 UTC

Created attachment 1960634 [details]
File: environ

Comment 5 noname 2023-04-28 04:39:32 UTC

Created attachment 1960635 [details]
File: open_fds

Comment 6 noname 2023-04-28 04:39:33 UTC

Created attachment 1960636 [details]
File: mountinfo

Comment 7 noname 2023-04-28 04:39:35 UTC

Created attachment 1960637 [details]
File: os_info

Comment 8 noname 2023-04-28 04:39:36 UTC

Created attachment 1960638 [details]
File: cpuinfo

Comment 9 noname 2023-04-28 04:39:38 UTC

Created attachment 1960639 [details]
File: core_backtrace

Comment 10 noname 2023-04-28 04:39:39 UTC

Created attachment 1960640 [details]
File: exploitable

Comment 11 noname 2023-04-28 04:39:41 UTC

Created attachment 1960641 [details]
File: dso_list

Comment 12 noname 2023-04-28 04:39:42 UTC

Created attachment 1960642 [details]
File: backtrace

Comment 13 simon 2023-07-04 12:39:04 UTC

This happened when I opened OBs studio and moved it from my monitor to my regular laptop screen. Having looked up the erro message I think it's because the scaling is different. I've changed the resolution on my native screen so I can scale them the same, and it hasn't broken yet, but it's still annoying.


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=149b505977834308b86bc5e0faf5741e;i=794cb;b=9aacffdc0f5048d0867ef786737e7d1d;m=14e82f3e;t=5ffa85d54abc9;x=5f729a1d056c633a
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-200.fc38.x86_64
package:        gnome-shell-44.2-1.fc38
runlevel:       N 5
dso_list:       /usr/bin/gnome-shell gnome-shell-44.2-1.fc38.x86_64 (Fedora Project) 1686719548
backtrace_rating: 4
crash_function: wl_resource_add_destroy_listener
comment:        This happened when I opened OBs studio and moved it from my monitor to my regular laptop screen. Having looked up the erro message I think it's because the scaling is different. I've changed the resolution on my native screen so I can scale them the same, and it hasn't broken yet, but it's still annoying.

Comment 14 Jacob Shtabnoy 2023-08-15 01:48:43 UTC

I closed mpv and the entire shell froze for a few seconds, then kicked me back to the login.


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=84c278a383bd43b08c2403f5cac46b19;i=5082bb;b=3f8bce7446e74517974dda27cc7a0309;m=bd7feb827;t=602ec2f85a070;x=41a990b3c361c3ba
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.9-200.fc38.x86_64
package:        gnome-shell-44.3-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: wl_resource_add_destroy_listener
comment:        I closed mpv and the entire shell froze for a few seconds, then kicked me back to the login.

Comment 15 samvandende 2023-08-24 11:16:35 UTC

I have two monitors: one external 1080p monitor with 1x scaling factor and one internal (laptop) 2880x1800 monitor with 1.5x scaling factor.
Dragging a window (created using the winit library in the rust programming language) from the external to the internal monitor crashed gnome-shell.

Another note: resizing that same window from fullscreen to windowed (tested on the external monitor) often crashes it with the following terminal output:
wl_surface@31: error 2: Buffer size (10x895) must be an integer multiple of the buffer_scale (2).


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=1dd8926856454f189b3226a3f6b50424;i=12551b;b=58c5ebbea1ee4d53afc21db01534f545;m=25492c3a;t=603a89b207cae;x=64bed2f5eef77794
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.11-200.fc38.x86_64
package:        gnome-shell-44.3-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: wl_resource_add_destroy_listener

Comment 16 Gael 2023-10-02 15:47:28 UTC

ABRT told me that this crash seems related to this bug : https://retrace.fedoraproject.org/faf/reports/787176/

Comment 17 pureacetone 2023-10-30 02:44:41 UTC

I was playing a wav file on mpv and gnome-shell restarted.


reporter:       libreport-2.17.11
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=1aaf70fdca204682a2ef6b82ceeeb0f0;i=697660;b=6ace77fd4a594356836c672937f677db;m=127a839b08;t=608e5df222673;x=a24472838fe4b448
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.5.8-200.fc38.x86_64
package:        gnome-shell-44.5-1.fc38
runlevel:       N 5
dso_list:       /usr/bin/gnome-shell gnome-shell-44.5-1.fc38.x86_64 (Fedora Project) 1695265122
backtrace_rating: 4
crash_function: wl_resource_add_destroy_listener
comment:        I was playing a wav file on mpv and gnome-shell restarted.

Comment 18 Fedora Admin user for bugzilla script actions 2023-12-06 08:22:56 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 16:13:24 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:47:16 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.