Bug 430583

Summary:	Transparency level not correct right after login
Product:	[Plasma] plasmashell	Reporter:	David de Cos <david.decos>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED FIXED
Severity:	minor	CC:	nate, niccolo.venerandi, notmart, plasma-bugs
Priority:	NOR
Version:	5.20.4
Target Milestone:	1.0
Platform:	openSUSE
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=423297
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Transparency level right after logging into Plasma Transparency level after running 'plasmashell --replace'.

Description David de Cos 2020-12-19 15:02:41 UTC

SUMMARY
When I log into Plasma, my panel is much more opaque than it should (whatever is set by Breeze Transparent Dark). This happens about 80% of the times I boot my computer and log into Plasma. Running 'plasmashell --replace' restores the expected level of transparency every time.

STEPS TO REPRODUCE
1. Use Breeze Transparent Dark as Plasma style (I don't know if this happens with other transparent themes)
2. Reboot your computer (not sure this happens after a simple logout+login)
3. Log in

OBSERVED RESULT
Panel is much darker than it should. Running 'plasmashell --replace' fixes it.

EXPECTED RESULT
Panel should show the transparency level set by Breeze Transparent Dark, without needing to restart plasmashell.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Leap 15.2
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2
Graphics Processor: Mesa DRI Intel® HD Graphics 520

ADDITIONAL INFORMATION
Relevant screenshots added in the following comments.

Comment 1 David de Cos 2020-12-19 15:03:36 UTC

Created attachment 134206 [details]
Transparency level right after logging into Plasma

Comment 2 David de Cos 2020-12-19 15:05:37 UTC

Created attachment 134207 [details]
Transparency level after running 'plasmashell --replace'.

Comment 3 Nate Graham 2021-03-09 15:41:26 UTC

Reminds me of Bug 423297.

Comment 4 David de Cos 2021-03-10 09:15:52 UTC

I had actually almost forgotten about this bug, because now I realize I haven't seen it for some time, at least several weeks. It must have been fixed with some update in the last couple of months.

Should I mark it as solved?

Comment 5 Marco Martin 2021-03-10 11:36:56 UTC

(In reply to David de Cos from comment #4)
> Should I mark it as solved?

yep.
keep an eye on it and reopen if happens again on post 5.21 versions of plasma