Summary: | Compositor crashes after using dashboard until icon in systray is closed | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Hugo Rens <zhugoz.rens> |
Component: | System Tray | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | mgraesslin, notmart, notuxius |
Priority: | NOR | ||
Version: | 5.7.2 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
URL: | https://drive.google.com/open?id=0B0aDRLQv6ztAc1A0XzUzd0NtSVU | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
attachment-31827-0.html
attachment-31924-0.html |
Description
Hugo Rens
2016-07-30 19:30:57 UTC
is plasmashell or kwin crashing? Created attachment 100628 [details]
attachment-31827-0.html
No, both kwin and plasmashell remain usable.
Only the compositor, as far as I know, crashes. The systemtray and dashboard are buggy but running.
(In reply to Hugo Rens from comment #2) > Created attachment 100628 [details] > attachment-31827-0.html > > No, both kwin and plasmashell remain usable. > Only the compositor, as far as I know, crashes. The systemtray and dashboard > are buggy but running. err, kwin is the compositor, so i still have no idea what is crashing :) Created attachment 100665 [details]
attachment-31924-0.html
Oh, my bad...
Actually the windows remain usable (draggable, etc...) but there is no more transparency effects (blurry panel, console background...), and this black square on the top of the screen.
I haven't still been able to reproduce this bug, though.
so seems, nothing is crashing, but composite effects gets disabled? Martin, any idea on that? please provide output of qdbus org.kde.KWin /KWin supportInformation when the problem happens. Please also provide a screenshot of the problem. @Hugo Rens is this bug still relevant for you after updates? (In reply to Alexander Mentyu from comment #7) > @Hugo Rens is this bug still relevant for you after updates? Sorry for my lack of feedback, I didn't actually encountered the bug after a few updates (as far as I can remember) and I'm afraid I can't tell you exactly what update solved the issue. So no, the bug isn't relevant for me anymore. Can I (and should I) do something to close/delete the issue ? No, thanks for your feedback |