FS#71683 - [firefox] KDE crashes when Detaching one Tab to second screen.

Attached to Project: Arch Linux
Opened by Luca Brockschmidt (LucaB) - Sunday, 01 August 2021, 12:47 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 04 August 2021, 10:06 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Antonio Rojas (arojas)
Architecture x86_64
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After pulling one Tab from Firefox to another screen to create a new Window, KDE crashes, Task Manager and Application launcher are no longer available.
The Firefox Windows as well as all other open applications are still usable.

Additional info:
* package version(s)
linux 5.13.6.arch1-1
firefox 90.0.2-1
plasma-meta 5.22-1
plasma-desktop 5.22.4-1
plasma-wayland-session 5.22.4-2

* link to upstream bug report, if any
https://bugzilla.mozilla.org/show_bug.cgi?id=1723370

Steps to reproduce:
Open A Firefox Window with multiple open Tabs.
Detach one Tab to create a new Window on another Screen.
This task depends upon

Closed by  Antonio Rojas (arojas)
Wednesday, 04 August 2021, 10:06 GMT
Reason for closing:  Upstream
Additional comments about closing:  Request reopen when there's an upstream fix we can apply
Comment by Antonio Rojas (arojas) - Sunday, 01 August 2021, 17:41 GMT
If Plasma is crashing this should be reported to KDE, not to firefox, unless you have some evidence that it's firefox fault. Anyway, please post a backtrace.
Comment by Luca Brockschmidt (LucaB) - Sunday, 01 August 2021, 18:00 GMT
I reported this as a firefox bug, because the same actions in any other browser I tested produce the desired behavior.
Unfortunately I only get a black screen in the end, There is no "report bug" popup. Also I have just replicated the bug a minute ago and cannot find a corresponding entry with coredumpctl.
Do you have any advice how I can get useful debug information?
I'm sorry that I cannot be more specific as I am a relatively new arch user.
Comment by Antonio Rojas (arojas) - Sunday, 01 August 2021, 20:51 GMT
Run gdb plasmashell from a terminal and make it crash
Comment by Luca Brockschmidt (LucaB) - Sunday, 01 August 2021, 22:03 GMT
Thanks for the tip. I've crashed plasmashell multiple times now within gdb and valgrind. At some point it crashed every third time I opened a new window.
One recurring message is "qt.qpa.wayland: Wayland does not support QWindow::requestActivate()".
Apparently plasma uses some QT function that Wayland does not support.
Thank you very much for your support!
Comment by Antonio Rojas (arojas) - Sunday, 01 August 2021, 22:06 GMT
That message is harmless and not related to the crashes. The important information should be in the backtrace.
Comment by Luca Brockschmidt (LucaB) - Monday, 02 August 2021, 10:24 GMT
This is the regular gdb output. Around line 177 plasma crashes and I have tried entering bt as well as backtrace after the prompt "--Type <RET> for more, q to quit, c to continue without paging--".
I cannot get a backtrace.
   gdb1.txt (21.7 KiB)
   gdb.txt (14.3 KiB)
Comment by Antonio Rojas (arojas) - Monday, 02 August 2021, 11:01 GMT
> The Wayland connection broke. Did the Wayland compositor die?

That's the actual issue - it isn't actually crashing, so there's no backtrace. But it's weird since as you say all apps still work, so the compositor is definitely alive. Please report to KDE so they can provide more insight.