Description of problem: Version-Release number of selected component: sway-1.4-4.fc32 Additional info: reporter: libreport-2.12.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-691.scope cmdline: sway crash_function: wl_list_insert executable: /usr/bin/sway journald_cursor: s=339b3d615f654aa2882e29a905196421;i=5b522;b=564ef206f1804020a396d69bc6a4ac4a;m=13d331ed69;t=5a469b2541e8d;x=a4dc91b7532db26a kernel: 5.6.7-300.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #0 wl_list_insert at src/wayland-util.c:49 #1 wl_signal_add at /usr/include/wayland-server-core.h:441 #2 xwm_set_seat at ../xwayland/selection/selection.c:309 #3 wlr_xwayland_set_seat at ../xwayland/xwayland.c:479 #4 seat_send_focus at ../sway/input/seat.c:176 #6 seat_set_focus at ../sway/input/seat.c:1079 #8 input_manager_set_focus at ../sway/input/input-manager.c:410 #9 view_map at ../sway/tree/view.c:650 #10 handle_map at ../sway/desktop/xwayland.c:440 #11 wlr_signal_emit_safe at ../util/signal.c:29
Created attachment 1682765 [details] File: backtrace
Created attachment 1682767 [details] File: core_backtrace
Created attachment 1682768 [details] File: cpuinfo
Created attachment 1682769 [details] File: dso_list
Created attachment 1682770 [details] File: environ
Created attachment 1682771 [details] File: exploitable
Created attachment 1682772 [details] File: limits
Created attachment 1682773 [details] File: maps
Created attachment 1682774 [details] File: mountinfo
Created attachment 1682775 [details] File: open_fds
Created attachment 1682776 [details] File: proc_pid_status
This happened when I was using external display and my laptop display. External Monitor <-> DisplayPort <-> Dell DA300 hub <-> Thunderbolt <-> laptop This happened at the moment when I disconnected Dell DA300's thunderbolt from my laptop. There was nothing else than external monitor connected to the DA300 for the whole time.
I am not very fluent in backtracing, but it seems to me that it is related to: https://github.com/swaywm/wlroots/issues/1684
Can you force this crash to happen again by repeating the situation? (It might be necessary to start an application that still uses Xorg, as the backtrace suggests xwayland being involved.)
I've tried to reproduce this issue: - I am not sure if it is the same crash, but sway crashes almost every time when I connect/disconnect DA300 hub via thunderbolt. - I also tried to connect/disconnect DisplayPort cable, and power on/off external monitor, and the crash did not occur. - I've deleted all abrt problems yesterday, and now during this reproduction attempts abrt did not catch any problem.
Could you try to install sway from this copr and give it if you can reproduce the issue as well: https://copr.fedorainfracloud.org/coprs/defolos/sway-experimental/? (That is sway & wlroots from the master branch)
I've installed sway 1.4+git52bd6ae and wlroots 0.10.1+git46c83cb. After reboot (just for sure), disconnect of DA300 no longer crashes sway (Yay!), unfortunattely I am not able to reconnect external monitor. Sway sees it as: swaymsg -t get_outputs Output eDP-1 'Sharp Corporation 0x144A 0x00000000' (focused) Current mode: 3200x1800 @ 59.981998 Hz Position: 0,1080 Scale factor: 2.000000 Scale filter: nearest Subpixel hinting: unknown Transform: normal Workspace: 2 Max render time: off Adaptive sync: disabled Available modes: 3200x1800 @ 47.985001 Hz 3200x1800 @ 59.981998 Hz Output DP-1 'Dell Inc. DELL P2719H GV1LPS2' (inactive) Available modes: 720x400 @ 70.082001 Hz 640x480 @ 59.939999 Hz 640x480 @ 75.000000 Hz 800x600 @ 60.317001 Hz 800x600 @ 75.000000 Hz 1024x768 @ 60.004002 Hz 1024x768 @ 75.028999 Hz 1152x864 @ 75.000000 Hz 1280x1024 @ 60.020000 Hz 1280x1024 @ 75.025002 Hz 1600x900 @ 60.000000 Hz 1920x1080 @ 60.000000 Hz Executing `swaymsg output DP-1 enable` does not change anything.
Hm, that is rather unfortunate. This probably means that the underlying bug is still present, it just manifests differently now. Could you report this upstream https://github.com/swaywm/sway and post the link to the issue here? I'll try to help out, but I'm afraid you'll have to eventually also build sway yourself.
Reported upstream GitHub as https://github.com/swaywm/sway/issues/5318
Michal: should I rebuild sway and wlroots from git into my copr so that you can test it?
FEDORA-2020-c8d4ba0d3d has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c8d4ba0d3d
I've submitted the patched version as an update to F32. Please test!
FEDORA-2020-c8d4ba0d3d has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-c8d4ba0d3d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c8d4ba0d3d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-c8d4ba0d3d has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.