Summary: | plasmashell crash on Wayland when opening Thunderbird blog entry | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | pyro4hell |
Component: | generic-crash | Assignee: | David Edmundson <kde> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | akselmo, alex765, nate, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi, wayland |
Version: | 5.24.2 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=429627 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
plasmashell output
crash recorded with env WAYLAND_DEBUG=1 plasmashell --replace > log.txt 2>&1 |
Description
pyro4hell
2021-03-31 15:37:54 UTC
Can confirm on Fedora 34, same Qt, Frameworks, and Plasma versions as OP. Make sure to double-click the blog entry to bring it up, merely single-clicking to select it wasn't enough to generate a crash. I think you need to make sure it's the same blog entry, the one ending in 9e9c15d2, but I could be wrong about that. I'm not sure what I could get a backtrace of, because plasmashell thinks kwin is dead, when kwin isn't dead. drkonqi attempts to start, but fails for whatever reason, so I can't currently show a plasmashell backtrace. Some help diagnosing this would be appreciated... Additionally, I'm unable to reproduce this on my Neon Unstable VM. Can you run plasma with WAYLAND_DEBUG=1 and try to reproduce the crash? env WAYLAND_DEBUG=1 thunderbird --replace > log.txt 2>&1 Please redact any sensitive information in the log. --- Note that I cannot reproduce this crash by clicking https://blog.fefe.de/?ts=9e9c15d2 Created attachment 137221 [details]
plasmashell output
Output of plasmashell when reproducing this bug
Glad I'm not alone, thanks Alex for confirming and providing a debug log. I have absolutely no idea if this is related, just looks to me like a double free. In Alex's log the IDs 199 and 250 are deleted twice just before the first "The Wayland connection broke" message [4107345.962] wl_display@1.delete_id(250) [4107358.380] wl_display@1.delete_id(199) [4107358.418] wl_callback@199.done(13707024) [4107358.602] wl_callback@250.done(8458) [4107359.103] wl_display@1.delete_id(250) [4107375.310] wl_display@1.delete_id(199) [4107375.361] wl_callback@199.done(13707041) [4107831.124] wl_callback@250.done(8458) [4107831.198] wl_buffer@201.release() [4107831.730] -> wl_surface@95.frame(new id wl_callback@199) [4107831.796] -> wl_surface@95.attach(wl_buffer@201, 0, 0) [4107831.870] -> wl_surface@95.damage(0, 0, 2147483647, 2147483647) [4107831.941] -> wl_surface@95.commit() [4107831.964] -> wl_display@1.sync(new id wl_callback@250) The Wayland connection broke. Did the Wayland compositor die? Can't reproduce with current git master and the latest Thunderbird. Can anyone who was affected check again with at least Plasma 5.24? Git master or the Plasma 5.24 beta (released tomorrow) would be even better. :) 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! 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! Plasmashell still crashes for me on Arch Linux with the 5.24 update, when opening the earlier mentioned blogpost. It also crashed hard on a random Signal-desktop notification and even crashed instantly when restarting with 'kstart5 plasmashell' Is the backtrace the same? I ask because...
> and even crashed instantly when restarting with 'kstart5 plasmashell'
That sounds like a different, known, already fixed issue.
Can you please get a backtrace of the crash so we can see if it is indeed the same issue, or a different one? Thanks!
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! Created attachment 147201 [details]
crash recorded with env WAYLAND_DEBUG=1 plasmashell --replace > log.txt 2>&1
recorded by first crashing plasmashell, then running the following command
env WAYLAND_DEBUG=1 plasmashell --replace > log.txt 2>&1
and then switch to thunderbird and open the tab with the blogpost and watching plasmashell immediately crash
|