Bug 366318 - No transparency, blur or shadows in plasmashell at startup
Summary: No transparency, blur or shadows in plasmashell at startup
Status: RESOLVED DUPLICATE of bug 362531
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 5.7.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-01 01:09 UTC by Pablo
Modified: 2016-08-01 07:30 UTC (History)
0 users

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


Attachments
qdbus org.kde.KWin /KWin supportInformation (5.98 KB, text/plain)
2016-08-01 01:11 UTC, Pablo
Details
Screenshot of the bug (106.78 KB, image/png)
2016-08-01 01:16 UTC, Pablo
Details
Screenshot after killing and restarting plasmashell (200.98 KB, image/png)
2016-08-01 01:17 UTC, Pablo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pablo 2016-08-01 01:09:24 UTC
When login into my session plasmashell taskbar, kickoff menu and krunner have neither transparency with blur nor shadows. "killall plasmashell && plasmashell" from konsole fixes it. 



Reproducible: Always

Steps to Reproduce:
1. Login into a plasma session.

Actual Results:  
Plasmashell apparently has no compositing (other types of windows seems fine, so other effects like "slide" for plasma widgets).

Expected Results:  
Plasmashell panel, kickoff, etc, should have transparency, blur, and shadows.

I'm running openSUSE tumbleweed up to date. My system has an AMD Radeon 7750 with opensource mesa drivers. I'll happily provide any needed information.
Comment 1 Pablo 2016-08-01 01:11:13 UTC
Created attachment 100402 [details]
qdbus org.kde.KWin /KWin supportInformation
Comment 2 Pablo 2016-08-01 01:16:16 UTC
Created attachment 100403 [details]
Screenshot of the bug
Comment 3 Pablo 2016-08-01 01:17:37 UTC
Created attachment 100404 [details]
Screenshot after killing and restarting plasmashell
Comment 4 Martin Flöser 2016-08-01 07:30:24 UTC

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