Summary: | Plasma crash when taking a screenshot | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Marvin Häuser <mhaeuser> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | kde, nate, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.21.3 | ||
Target Milestone: | 1.0 | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Marvin Häuser
2021-03-31 11:16:06 UTC
*** This bug has been marked as a duplicate of bug 435015 *** Good day Mr. Redondo, As I have written in my report, it is likely closely related to the bug you marked as duplicate, yet yesterday's update resolved the original symptoms, but not the ones described here. Did yesterday's update only include a partial fix? Thank you a lot! Sorry, I assumed for it top be the same because of the backtrace, but if that's indeed the case, I will deduplicate it I saw there just was a another update. I cannot easily verify whether this one fully resolved the issue because it only happens very rarely (I'd say once or twice a week?). I found no way to reliably reproduce this yet, sorry. On a different note, I assumed the screenshot not being available in clipboard was a consequence of the crash, but I think sometimes it is unavailable without any crash. It happens with a custom hotkey bound to 'spectacle -brc'. Quickly searching (I previously did not realise the default is to search only open tickets, sorry!) yields only fixed or Wayland-related (I am on X11) issues. Is there a ticket I should be aware of, or should I open a new one? Unfortunately I cannot reliably reproduce this issue either. Thanks a lot! Okay, I realised the screenshot being unavailable was due to a configuration error of the clipboard manager, so not-a-bug. Sorry, I'm still getting used to how KDE and Linux work. :) So far, since today's update, even heavy provocation did not yield any of the previous symptoms. *** This bug has been marked as a duplicate of bug 430862 *** |