GNOME Bugzilla – Bug 148413
(Almost) nothing happens when selecting themes
Last modified: 2006-10-01 03:34:30 UTC
Description of Problem: I have a very similar problem to bug #86486. I have created a new user, installed some new themes and everything worked fine for a while. But now when I select a theme, regardless of whether it is a theme in the "Theme Preferences" window, or a Metacity/GNOME theme in the "Theme Details" window, nothing happens anymore except that the selection is highlighted. So I created a new user and tried that out. Again, it worked only for a while and after some days nothing happened anymore. The same problem occured on two different machines, both the current Debian Sarge. I never manually edited any configuration files, nor used gconf to modifiy anything. There is no output on the commandline. Steps to reproduce the problem: 1. Run gnome-theme-manager 2. Click on the various themes 3. Note that nothing happens Additional Information: $ gnome-theme-manager --version Gnome gnome-theme-manager 2.6.1
I forgot to mention: The problem was not 100% identical on both machines: On one machine, the problem was not that /nothing/ changed when I clicked a theme. Rather, only /some/ elements of a theme changed. For example, when the current theme was "Smokey Blue" and I clicked the "Gorilla" GTK theme in the theme details, the Gorilla theme appeared (meaning the widget color changed) except for the buttons, which were still "Smokey Blue", so the GTK2 themes were "mixed".
*** Bug 148514 has been marked as a duplicate of this bug. ***
do you still have this problem ? Do is happen all the time, or does it work if the session just started ? Does a "killall gnome-settings-daemon" fixes the problem ?
Yes, the problem persists. However, killing gnome-settings-daemon causes some improvement: After killing it, more controls change properly, but the color of some widgets still looks weird. And when I switch around between different themes long enough, the problem keeps getting worse until I kill gnome-settings-daemon again. I would be happy to give more debugging output, as I have seen the same behavior on three different machines now.
I also just noticed similar problems with the background switcher - selecting a background just does not do anything any more. You will probably know better whether or not these problems may be related.
could you attach some screenshot of the problem to the bug report ?
Created attachment 34320 [details] Industrial Theme Screenshot Note that the attached theme selector has "Industrial" selected but the theme is different. When selecting the same theme using a newly created user everything looks fine.
Created attachment 34321 [details] Smokey Blue Theme screenshot Another screenshot showing "Smokey Blue" with an incorrect scroll bar. IIRC the buttons should look different either.
Same thing here. Happened after 2.8.1 upgrade in debian sid. gnome-theme-manager version here is 2.8.1 Weird, it happens on my laptop,but a desktop pc with the same config won't happen.
the screenshots on the comments #7 and #8 seems to be corrects. The scrollbar is a part of the GTK theme and you're changing the window border the comment #9 is an another problem. Do you have the problem just after the login or after killing gnome-settings-daemon.
I am not just changing the metacity theme, I have been clicking the themes only in the Theme preferences, not in the Theme Details. The Theme Details window was just opened for your information. Also, in #8 the controls /do/ change to Smokey, except for that one single widget (the scrollbar).
I suspect this is a problem with the setup of the particular machine, rather than a bug in the theme manager. If it is a bug, then it is almost certainly going to be an issue with the settings-daemon or gconf itself. Since there is no reliable way of reproducing this bug, I'm going to mark it NEEDINFO. Unless it is still reproducible, I suspect it can be marked obsolete or incomplete soon.
Closing this bug report as no further information has been provided. Samuel, if you still face this issue with a current gnome version, please reopen this bug report. Thanks in advance!