Summary: | Plasma desktop can crash when panels move between screens | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | clubmajo |
Component: | System Monitor widgets | Assignee: | Marco Martin <notmart> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bhush94, brianara3, edwin.jablonski.pl, kde, kde, notmart, plasma-bugs, roxannascheijen+3v46f7qi, tgroman5 |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.5.1 | ||
Target Milestone: | 1.0 | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
clubmajo
2016-01-24 11:31:17 UTC
*** Bug 359061 has been marked as a duplicate of this bug. *** seems that in plotter the m_node is deleted without noticing. but is that possible? (on view change) its flag are QSGNode::OwnedByParent and has no parent I'm using plasmashell 5.5.4 and the issue of moving widgets doesn't give so many problems as before. I cannot replicate the crash easily but in rare occasions I ended crashing plasma with the same backtrace This time, plasma crashed when I was with focus in a chromium window and I moved the mouse to the other screen and quickly began with a drag action in a widget. I don't know if it helps but I have issues with EGL mesa making crash kwin but that crash is unrelated to this bug *** Bug 366460 has been marked as a duplicate of this bug. *** *** Bug 366329 has been marked as a duplicate of this bug. *** I experimented the same issue with the same backtrace of original report in the next version: Application: plasmashell (5.7.5) Frameworks Version: 5.26.0 Qt Version: 5.6.1 Operating System: Linux 4.7.4-gentoo x86_64 Can confirm. Moving panel back and forth between screens will always crash plasmashell. KDE Neon 5.8.1, intel hd 3000 *** Bug 372371 has been marked as a duplicate of this bug. *** can this still be reproduced? with the combination Plasma 5.8 Qt 5.8 and intel modesettings drivers i can't reproduce this at all anymore *** This bug has been marked as a duplicate of bug 349289 *** |