| Summary: | IOTM icon background glitshes out at random when cursor is over a Flatpak Teams window | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Reiddragon <this.is.reid> |
| Component: | Task Manager and Icons-Only Task Manager widgets | Assignee: | Eike Hein <hein> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.21.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | screenshot showing the glitch in action | ||
|
Description
Reiddragon
2021-03-08 07:31:43 UTC
Created attachment 136477 [details]
screenshot showing the glitch in action
Whoa, that is weird. Seems like a cache corruption issue. Does the issue disappear completely if you clear your plasma cache with `rm ~/.cache/plasma*`? (In reply to Nate Graham from comment #2) > Whoa, that is weird. Seems like a cache corruption issue. > > Does the issue disappear completely if you clear your plasma cache with `rm > ~/.cache/plasma*`? unfortunately it's not particularly consistent, and might not be related to the cached Plasma theme getting corrupted as last time I managed to trigger the bug it was tied to a single virtual desktops, all others were completely fine Also not sure if it will help much but disabling and reenabling the compositor fixes it for whatever reason (or maybe that was just a coincidence, I don't know as I haven't been able to find a consistent way to reproduce it in order to triage it properly and see what exactly is the trigger So far pretty much the only constant I managed to find is Teams always being around when the bug glitch in OK so compositing being enabled is a factor. That makes me suspect cache issues even more, since different SVGs are used depending on the compositing status. Please try clearing the plasma cache and restarting plasmashell the next time it happens. Thanks! (In reply to Nate Graham from comment #4) > OK so compositing being enabled is a factor. That makes me suspect cache > issues even more, since different SVGs are used depending on the compositing > status. Please try clearing the plasma cache and restarting plasmashell the > next time it happens. Thanks! Just managed to reproduce it, turns it out's not related to compositing after all as I disabled the compositor and it's still there Wiping the cache didn't help either Cool, thanks for the update. What kind of graphics hardware are you using? (In reply to Nate Graham from comment #6) > Cool, thanks for the update. What kind of graphics hardware are you using? Intel UHD Thanks. Are you using a non-default Plasma theme? Any other non-default settings at all? (In reply to Nate Graham from comment #8) > Thanks. Are you using a non-default Plasma theme? Any other non-default > settings at all? added a sticky note and memory usage plasmoid, removed the show desktop plasmoid, and using a custom colorscheme, otherwise it's completely stock New update: seems to happen pretty consistently on all but the first virtual desktop, meanwhile Teams seems to not be related with any of it, at least not anymore I re-tested this with today's git master (which will become Plasma 6.5), and still can't reproduce it. Can you try again with Plasma 6.4 or later? Thanks a lot! (In reply to Nate Graham from comment #11) > I re-tested this with today's git master (which will become Plasma 6.5), and > still can't reproduce it. Can you try again with Plasma 6.4 or later? Thanks > a lot! it has already been years since the Teams desktop client for Linux has been dropped by Microsoft, and that was the only program I could ever reproduce this bug with. And regardless of that, I no longer own the hardware I got that graphics bug on (that Intel UHD GPU had quite a lot of weird graphical glitches I got since filing this bug, many not related to Plasma) For all intents and purposes, I have no way of even attempting to reproduce this bug anymore and track it down to something in Plasma or the i915 GPU driver or w/e else in the system. Thanks anyway, I guess we'll have to close this one out. |