Bug 136126 - konqueror file view black on black
Summary: konqueror file view black on black
Status: RESOLVED FIXED
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 3.3.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-22 11:41 UTC by Wolfram R. Sieber
Modified: 2009-11-29 23:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
sample zebra view of konqueror (51.12 KB, image/png)
2006-10-22 11:43 UTC, Wolfram R. Sieber
Details
~/.kde/share/config/kdeglobals as requested by Brams (7.98 KB, text/plain)
2006-10-23 11:22 UTC, Wolfram R. Sieber
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfram R. Sieber 2006-10-22 11:41:48 UTC
Version:           3.3.2 (using KDE 3.3.2,  (3.1))
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-13)
OS:                Linux (i686) release 2.6.8-3-k7

When I open a directory in konqueror, say /, every second row of the view is black. Normally, there rows are alternating white and a light blue. Now, one row is black and the next one light.

When I shut down the PC yesterday, everything was fine. When I started it up today, I got that zebra like view. Sorry, I have no idea, what might have caused that behaviour.

I opened several directories and several new instances of konqueror to see whether or not I could get rid of those black text on black background rows, but I couldn't.

.
If konqueror uses a background image for the bars, I'd like to hear from you soon for what file I have to look at, or which one I could replace to fix that obstructive view. Otherwise, if that misbehaviour originates from a color scheme, I also would like to heare from you, where/how I could fix it.

And no, I didn't play around with my color scheme since yesterday.
Comment 1 Wolfram R. Sieber 2006-10-22 11:43:09 UTC
Created attachment 18225 [details]
sample zebra view of konqueror
Comment 2 Bram Schoenmakers 2006-10-22 13:40:17 UTC
Still, it may be useful to recheck your color scheme and re-define the "alternating list color". This helped with a similar problem in the Kopete contact list.
Comment 3 Bram Schoenmakers 2006-10-22 13:42:31 UTC
Oh, but first, copy your ~/.kde/share/config/kdeglobals file first and post it here. I'm wondering if the alternating list color is corrupt or something. Thanks.
Comment 4 Wolfram R. Sieber 2006-10-23 11:22:05 UTC
Created attachment 18231 [details]
~/.kde/share/config/kdeglobals as requested by Brams

For privacy reasons, I removed history lists, marked as "[deleted for reasons
of privacy]".
Comment 5 Wolfram R. Sieber 2006-10-23 11:25:05 UTC
There's only one "lternat" in the file:

alternateBackground=238,246,255

.
If those values are rgb, then it should be a pretty bright color, I think.
Comment 6 Wolfram R. Sieber 2006-12-20 14:21:17 UTC
I determined the problem in terms of config files. Below ~/.kde I found konquerorrc files (including backup ones with konquerorrcRANDOMSTUFF names).

Thanks to the konquerorrcRANDOMSTUFF files I could determine the last bugfree version, diff it against the current one.

I noticed that the current one contained a "BgImage=" entry while the last working rc file contained a "BgImage=/usr/share/apps/konqueror/tiles/", so I set the BgImage of the current rc to the value of the previous one.

That made it!

.
Now the konqueror doesn't show any zebra view anymore. ... I assume, any prior twiddling on the kcontrol -> appearance -> style/* resulted in a side-effect, which dropped the BgImage value.

Hence, I suggest, whatever application makes changes to the ~/.kde/share/config/konquerorrc should make sure that BgImage gets a valid value. At least, the kcontrol action chain mentioned above should make that sure. Especially, since the assumption that it were a problem with the color settings was wrong and, unfortunately, misleading.
Comment 7 Doug Leonard 2007-01-04 06:03:04 UTC
I got the same thing after upgrading my gentoo kde 3.4 monolithic to 3.5 modular. The solution above worked... but I would say put this in the "confirmed category" because I can certainly confirm it.  I have no idea what caused it, but I know what fixed it.
Comment 8 Doug Leonard 2007-01-04 06:14:22 UTC
Also I understand that there is a fix and it's just a small configuration thing and beyond that it's probably pretty low priority, but I would none the less not agree that this is  a resolved bug (at least not from what is stated above).  A solution for how the user can fix it is not the same thing as understanding why it happens in the first place, and it seems reasonable to say it shouldn't happen, so that seems like a bug to me.
Comment 9 Wolfram R. Sieber 2007-01-04 22:35:00 UTC
I accede in Doug's arguing, that the problem can happen at any time again, therefore the solution described above cannot be assessed as fixed. Hence I re-open the bug, as suggested.
Comment 10 FiNeX 2009-11-29 22:57:49 UTC
This bug is no more reproducible in KDE4: konqueror uses dolphin as file manager which doesn't have this bug.