Bug 218928 - Transparency in Kwin affects also Keramik's window buttons
Summary: Transparency in Kwin affects also Keramik's window buttons
Status: RESOLVED DUPLICATE of bug 211552
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-16 15:17 UTC by Andrea
Modified: 2009-12-16 15:30 UTC (History)
0 users

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


Attachments
Keramik decoration screenshot (170.01 KB, image/jpeg)
2009-12-16 15:18 UTC, Andrea
Details
Plastik decoration screenshot (165.47 KB, image/jpeg)
2009-12-16 15:19 UTC, Andrea
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrea 2009-12-16 15:17:50 UTC
Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    openSUSE RPMs

Hi all,
I have enabled desktop effects of Kwin to have transparent panels. Currently I am using Keramik as window theme. My system is an openSUSE 11.2 with KDE 4.3.4 release 2 installed using openSUSE's KDE4 repositories.

My problem is that also window buttons (like close and minimize) are transparent; more precisely, the black part (i.e., the x of close and _ of minimize) is trasparent while other parts of the button is ok. If I choose a different window theme, like Plastik, such buttons are no more transparent. I think the problem is due to the color of the transparent part: in Keramik, the color is a pure black (#000000) while in Plastik is a very dark grey (#141312).

I will attach two screenshot: one with Keramik and another one with Plastik to highlight the effect...
Comment 1 Andrea 2009-12-16 15:18:37 UTC
Created attachment 39095 [details]
Keramik decoration screenshot
Comment 2 Andrea 2009-12-16 15:19:08 UTC
Created attachment 39096 [details]
Plastik decoration screenshot
Comment 3 Martin Flöser 2009-12-16 15:30:14 UTC

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