| Summary: | Crash in QQuickItem::isEnabled on startup | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Alex <appwebsec> |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | bhush94, cmvbay, crglasoe, emmanuel.hugonnet, gustavo.almatos, johngeoffreywalker, jon, justin.zobel, kanegraves23, leszek.lesner, matthewisrippin, plasma-bugs, pnunn, r.lechner, rwtech09, samuelbernardo.mail, sebastian, thewest123lp, tomek-k |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.7.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | plasmashell crash stack trace | ||
|
Description
Alex
2016-09-21 07:19:47 UTC
*** Bug 370916 has been marked as a duplicate of this bug. *** I can confirm this bug; after installing Linux 4.8.3 and rebooting, plasmashell crashed 3 times in a row. My right monitor was completely black except I could mouse over it, just like the description in Bug 370916. My stack trace is also very similar to the one in 370916, but differs slightly from the one in this report. Created attachment 101696 [details]
plasmashell crash stack trace
and this happens every time? Even if you run "plasmashell" manually? If so can you run it in valgrind and attach that log. It does not happen every time. After a couple of tries, I did get the crash to occur with the same characteristics as before (black right monitor) by starting plasmashell manually. However, when I managed to catch the same situation running plasmashell under valgrind it did not crash... It's possible the race doesn't occur when running under valgrind. *** Bug 371743 has been marked as a duplicate of this bug. *** *** Bug 371789 has been marked as a duplicate of this bug. *** *** Bug 371936 has been marked as a duplicate of this bug. *** *** Bug 372274 has been marked as a duplicate of this bug. *** *** Bug 372396 has been marked as a duplicate of this bug. *** *** Bug 372490 has been marked as a duplicate of this bug. *** *** Bug 372773 has been marked as a duplicate of this bug. *** *** Bug 373049 has been marked as a duplicate of this bug. *** *** Bug 373064 has been marked as a duplicate of this bug. *** *** Bug 372928 has been marked as a duplicate of this bug. *** *** Bug 373231 has been marked as a duplicate of this bug. *** To restate my comment so it can be seen by all the new people. I can't reproduce this and I don't have anywhere near enough data to do anything with this. Can someone who can reprocue this run "valgrind plasmashell" and get a log from there. *** Bug 374932 has been marked as a duplicate of this bug. *** I don't believe I've had this crash occur since I upgraded to Plasma 5.8.4, and I definitely haven't had it occur with Plasma 5.8.5. I just checked through all the duplicates, and all of them report a plasma version <5.8.4, so it's possible the crash was fixed in that version. Fwiw, I was never able to get the crash to occur under Valgrind. *** Bug 366169 has been marked as a duplicate of this bug. *** *** Bug 378378 has been marked as a duplicate of this bug. *** *** Bug 404509 has been marked as a duplicate of this bug. *** Thank you for the report. As this was reported on an older version of plasmashell, can you please test on a recent and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. 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! |