Bug 450997 - x11: Translucent windows get stuck in transparent state on desktop
Summary: x11: Translucent windows get stuck in transparent state on desktop
Status: RESOLVED DUPLICATE of bug 438552
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.24.2
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-01 09:28 UTC by slartibart70
Modified: 2022-03-22 02:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description slartibart70 2022-03-01 09:28:14 UTC
i opened kate on virtual desktop 2 on monitor 2.
Then i resized and moved the kate window to another position
kate was having the translucent/transparent state when moving.

When i stopped moving, the window kept its transparent state, but was fully functional.
Moreover, switching to virt. desktop1, the kate window was still there (obviously, it did not have the option set to 'appear on all desktops').
going back to virt.desktop2 , another thing appearing was the z-stacking with other windows, kate did not want to go into the background (behind other windows when they are in foreground due to clicking on those)

Then i closed the editor (ctrl-w), and still, the transparent kate window kept stuck at its position, but only on virt. desktop2 (not appaering on virt.desktop 1 or 3 or 4)

now i'm stuck with a transparent, non functional kate window covering other windows.
a restart of plasmashell did not help
(
kquitapp5 plasmashell
kstart5 plasmashell
)
so... only a logout/re-login helps?
Comment 1 slartibart70 2022-03-04 13:26:21 UTC
happened again, this time with a terminal (konsole) window.
But, going into systemsettings/desktop effects/ 
and toggling 'translucency' off and on again, the window 'recovered'

This should really be fixed
(i know, the 'new' default is translucency disabled, but there never was a problem before plasma 5.24.x)
Comment 2 Nate Graham 2022-03-22 02:35:34 UTC

*** This bug has been marked as a duplicate of bug 438552 ***