Summary: | Plasma Crashes after Clicking on Hamburger Menu on Panel | ||
---|---|---|---|
Product: | [Frameworks and Libraries] libplasma | Reporter: | Edward Reiss <ebreiss> |
Component: | libplasma | Assignee: | Marco Martin <notmart> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | akontsevich, bj.cardon, kde, nate |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Edward Reiss
2018-08-08 01:43:39 UTC
*** Bug 392624 has been marked as a duplicate of this bug. *** Bug still exists in Plasma 5.14: when notification comes, for example from Skype or Riot, Plasma freezes and starts to consume 100% core CPU. When it will be fixed???!!! Bug exists for years since 5.9, 5.10 versions till now!!! https://bugs.kde.org/show_bug.cgi?id=390534 https://bugs.kde.org/show_bug.cgi?id=381154 Can you reproduce this reliably? I cannot. If I click twice on the hamburger menu button, nothing crashes. Is something more needed? (In reply to Nate Graham from comment #3) > Can you reproduce this reliably? I cannot. If I click twice on the hamburger > menu button, nothing crashes. Is something more needed? I know nothing about hamburger and why our bugs made duplicate of this. I can reproduce reliable freezes with notifications. (In reply to Aleksey Kontsevich from comment #4) > (In reply to Nate Graham from comment #3) > > Can you reproduce this reliably? I cannot. If I click twice on the hamburger > > menu button, nothing crashes. Is something more needed? > > I know nothing about hamburger and why our bugs made duplicate of this. I > can reproduce reliable freezes with notifications. I think your bug is unrelated to this one. Are you still experiencing this in Plasma 5.20? Looks like there haven't been any duplicate reports in two years 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! |