Bugzilla – Bug 245006
Random color changes on Computer icon
Last modified: 2007-12-19 18:54:03 UTC
SLED changes the surrounding color of the "Computer" icon. Without rhyme or reason it changes the color. It seems that the color is indicating a change in system status, but I cannot find any description on how to change or interpret this behavior. [I would attache screenshot, but can't find an option to do so]
Created attachment 118899 [details] main screen - look at the color of the computer icon
-> Jimmy, Cc: Anna
That's just incredibly odd. Richard, what Theme are you running? Open your Control Center and check your Theme setting to find out. regards, Anna
I've never changed it - still the default - "Gilouche". All I did was change the desktop background to the ellipsis image, but that shouldn't affect that...
Mine does this as well, although mine usually turns either pink or blue (the same color as the highlight on a program flashing in the window list). My panel is also partially transparent. If I remove the main menu from the panel and re-add it, it usually returns to normal, temporarily.
I have a feeling that it might be related to the panel being translucent. I'm adjusting my own panel's opacity to see if I can trigger the bug on my system here -- and hopefully I will be able to track it down and figure this out. (I don't think it's directly theme-caused, but I may be able to do something in the theme to prevent this from happening.)
Created attachment 118972 [details] Update of Gilouche Here's a tarball of an updated Gilouche which may address this issue. I have added a transparent PNG which is displayed behind the button in NORMAL state. To test, untar this file in your home directory, like so: tar xvf gilouche-update-070213.tar.gz Later, when done testing this theme, you will want to remove your local copy of Gilouche, as it overrides your system-wide version. To do so, perform the following in a terminal: rm -rf ~/.themes/Gilouche/ Please let me know if this theme update solves the issue.
Actually, you will want to run something like the following in the terminal instead: tar xvf bug-245006_gilouche-update-070213.tar.gz -C $HOME ...as Bugzilla renames the files.
ok...I have installed the custom Gilouche. I will keep running with this until I have confidence the color does not reappear. It's a bit tricky since it seems like a random thing. Just to be clear: once I click on the Computer icon it becomes transparent, meaning it will switch from whatever color it has to white and opens the shortcut menu. Also...I do have a default transparency set on my taskbar. Should I leave it as is?
Created attachment 119392 [details] Screenshot after modification has been applied
Hmm. I haven't noticed it on my machine at all. Are you using Compiz or Metacity? (I'm using Metacity.)
Does updating to http://dist.suse.de/dist/full-sle10-sp-i386/suse/i586/gnome-main-menu.rpm solve the problem?
I get a whole bunch of dependency problems. What packages should I install and are these SP1 betas? (In reply to comment #12) > Does updating to > http://dist.suse.de/dist/full-sle10-sp-i386/suse/i586/gnome-main-menu.rpm solve > the problem? >
The packages in that directory are from the SP1 beta builds, yes. I don't know why you would get a bunch of dependency problems. It might want to pull in packages, if you are still running SLED 10 proper, rather than the SP1 builds. As far as I can tell, this should be fixed in Beta 4. Can you verify that when the build becomes available for you to install (if it isn't already)? (In reply to comment #13) > I get a whole bunch of dependency problems. What packages should I install and > are these SP1 betas?
Created attachment 120862 [details] Pretty in Pink
Hi. Your link only offered the gnome-main-menu which then triggered the dependency issues. I haven't applied a full SP1 beta yet - this is my day to day system and I can't afford to fry it... Meanwhile - enclosed is a screenshot for everybody's delight. My system stepped up the color varations to new extremes! ;-)
Hi Richard! Just wanted you to know that all of us on my team (I'm Dobey and Garrett's manager) are using SP1 on our production machines -- and we're fine. I would recommend updating to SP1 as a way to help you out with your dependency issues. Just a recommendation -- and a statement of faith in SP1.
Does this bug still happen with SP1 or SP2?
(In reply to comment #19 from Federico Mena Quintero) > Does this bug still happen with SP1 or SP2? > I have not seen it again since I started using the final version of SP1. It seems to be fixed.
Thanks for comfirming, Richard :) Closing the bug.