Bug 179971 - default colors are unreadable
Summary: default colors are unreadable
Status: RESOLVED DOWNSTREAM
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-07 23:33 UTC by kavol
Modified: 2009-02-21 03:36 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot showing the problem (163.02 KB, image/png)
2009-01-07 23:37 UTC, kavol
Details
Clean Blend and Aya theme - Aya looks broken (84.11 KB, image/png)
2009-01-11 18:25 UTC, Marian Kyral
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kavol 2009-01-07 23:33:47 UTC
Version:           4.1.87 (using Devel)
OS:                Linux
Installed from:    Compiled sources

Hi.

Using the recent snapshot 4.1.87, texts on the panel are unreadable due to color combinations like black on black. I tried to log out, remove all the .something settings in ~ and log in again to rule out some obsolete settings that are incompatible, but everything is the same. Also icons in krunner are affected. See the attached screenshot.

Note that I have not found any corresponding color settings within systemsettings, and if I try to use settings available after rightclicking the panel, I am unable to do so, as I cannot read anything.
Comment 1 kavol 2009-01-07 23:37:38 UTC
Created attachment 30021 [details]
screenshot showing the problem

note that there should be clock visible on the righthand side of the panel ...
Comment 2 Dario Andres 2009-01-07 23:39:51 UTC
What theme are you using ?
I have experienced the krunner image (buttons with red borders) when I was using a broken theme (I uninstalled it and it broke).
Comment 3 Aaron J. Seigo 2009-01-08 00:10:34 UTC
this is obviously a theme issue, or less likely a graphics driver issue. none of the svg's are being painted, which is why everything looks so horrible.

try remove ~/.kde/cache-*/plasma* and ~/.kde/cache-*/kpc/plasma* and see if that fixes anything for you.
Comment 4 kavol 2009-01-09 01:52:47 UTC
just to be safe, in text mode, again, I've completely removed the directories ~/.config, ~/.kde and ~/.local (as these three seemed to hold some KDE or Qt related settings), then I've logged in again into KDE and everything was the same

as for the theme selection, SystemSettings shows me that the Widget style is Oxygen, while color scheme is "Current" - selecting Oxygen and applying that does not make any difference, then Icons are Oxygen, window decorations are Ozone - once again, selecting Oxygen does not make any change to the colors, login screen is Default and emoticons are kde4

as for the graphics driver, right now I am using nVidia driver version 96.43.09 (as the card is old GeForce), but from what I've heard, I should experience just performance problems, not wrong results (note also that the desktop effects are disabled, as per the default)
Comment 5 Marian Kyral 2009-01-11 18:24:27 UTC
I have the same problem. The only working theme, I found, is Clean Blend.

I have two laptops, one with NV 7600, second with NV 8400, latest drivers (180.22), both have the same problem. Really looks like broken themes.
Comment 6 Marian Kyral 2009-01-11 18:25:34 UTC
Created attachment 30136 [details]
Clean Blend and Aya theme - Aya looks broken
Comment 7 Marian Kyral 2009-01-15 21:35:07 UTC
Solved, I had no installed the default oxygen theme. After emerging  kde-base/kdebase-desktoptheme it works.
Comment 8 Aaron J. Seigo 2009-01-16 01:49:33 UTC
aha! =) whew! well, one more strange mystery solved. the default theme is a requirement, which is why it is now in kdebase/runtime/
Comment 9 kavol 2009-01-16 22:39:29 UTC
well, yes, that works for me too

however, if the theme is a requirement, then something should fail during configure phase before compilation, just like with any other missing required package, and so that a check should be added => I do not consider it solved
Comment 10 Marian Kyral 2009-01-16 23:24:00 UTC
I think you should ask gentoo kde team, why was the oxygen theme split out. Probably there should be an dependency in the plasma-workspace package (or kdelibs?)
Comment 11 kavol 2009-01-16 23:33:28 UTC
as for Gentoo, there is a kdebase-desktoptheme dependency withing the kdebase set from kde-testing overlay (but I wonder why this did not come into effect ...)

but I am talking about cmake check for the needed files, not about the packaging - just like nepomuk component checks if kdelibs are built with nepomuk support etc.
Comment 12 Marian Kyral 2009-01-16 23:42:48 UTC
(In reply to comment #11)
> as for Gentoo, there is a kdebase-desktoptheme dependency withing the kdebase
> set from kde-testing overlay (but I wonder why this did not come into effect
> ...)

Probably was added later.

> but I am talking about cmake check for the needed files, not about the
> packaging - just like nepomuk component checks if kdelibs are built with
> nepomuk support etc.
> 

Nepomuk is separated package, oxygen theme is part of kdebase. This is a difference. It is distributed as one package, splitting was decision of Gentoo kde team.