Bug 433102 - Moving Firefox tabs between two monitors crashes the compositor
Summary: Moving Firefox tabs between two monitors crashes the compositor
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: platform-wayland-nested (show other bugs)
Version: 5.21.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-17 18:31 UTC by Ben Schröder
Modified: 2021-03-20 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Output of sudo journalctl -b 0 --no-pager (120.52 KB, text/plain)
2021-02-17 18:31 UTC, Ben Schröder
Details
KCrash Report, generated 2021.02.18 (2.11 KB, text/vnd.kde.kcrash-report)
2021-02-18 12:29 UTC, Ben Schröder
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Schröder 2021-02-17 18:31:02 UTC
Created attachment 135780 [details]
Output of sudo journalctl -b 0 --no-pager

SUMMARY
When i try to detach a tab from Firefox and move it directly to the second monitor the compositor crashes and restarts.
If i detach a tab and not move it over directly and let it settle and resize first the compositor does not crash.

STEPS TO REPRODUCE
1. Open Firefox
2. Open two tabs
3. Pick one tab and move it directly over to the second monitor

OBSERVED RESULT
Second screen turns black, compositor crashes. After a few seconds the compositor restarts and the system becomes usable again.

EXPECTED RESULT
Tab/Window gets moved to second monitor and is usable.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20210215
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.10.16-1-default
OS Type: 64-bit
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 1700X Eight-Core Processor
Memory: 15,5 GiB of RAM
Graphics Processor: AMD Radeon RX 5600 XT
Monitors: 2x 1440p 144Hz 1x Display Port 1x HDMI 2.1

This Bug only applies to Wayland or Full Wayland session, it does not appear when using X11.
The Bug does not appear if using a browser based on Chromium, only Firefox based ones.

If further logs are needed i will be happy to help.
Comment 1 Ben Schröder 2021-02-18 12:29:21 UTC
Created attachment 135844 [details]
KCrash Report, generated 2021.02.18
Comment 2 David Edmundson 2021-02-18 13:05:03 UTC
That backtrace is a client crashing as a result of kwin crashing, rather than a crashlog of kwin itself.

Can you run coredumpctl gdb kwin_wayland and see if that gives us anything
Comment 3 Bug Janitor Service 2021-03-05 04:33:23 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2021-03-20 04:33:48 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!