GNOME Bugzilla – Bug 104210
Theme manager refuses to work with no meta themes installed
Last modified: 2006-04-30 11:00:00 UTC
Package: control-center Severity: normal Version: 2.2.0 Synopsis: Theme manager refuses to work with no meta themes installed Bugzilla-Product: control-center Bugzilla-Component: theme-manager Description: Description of Problem: If it doesn't find an "index.theme" around, gnome-theme-manager aborts operation. This is a bad idea because switching between already installed themes is only one part of the program's function. "gnome-theme-manager" is also a metatheme _installer_ and _editor_. That a theme installer will only work if themes are already installed is kind of bone-headed! Steps to reproduce the problem: 1. Start gnome-theme-manager with no themes installed. 2. See the error message 3. Actual Results: It quits again. Expected Results: It should pick up my current GTK, Metacity and Icon themes as a "pseude theme" called "Current Settings", allowing me to edit, save or rename it --- or to install new themes. ------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-23 05:19 ------- Reassigning to the default owner of the component, control-center-maint@bugzilla.gnome.org.
Regression->High
*** Bug 105585 has been marked as a duplicate of this bug. ***
Is this still behaving the same way?
It is.
Yep. Situation is unchanged (sorry for the delay in responding!)
I should say that I'm running Gnome 2.4.2, Debian Sarge. I have no idea if anything has changed in the development branch.
Given that we distribute a large number of metathemes at this point, I can't find this a high priority bug any longer. Still, badly unexpected behavior and should be fixed.
The problem is that this behaviour introduces an unnecessary dependency of gnome-control-center on gnome-themes, because the former is not fully functional without the latter.
I can't seem to reproduce this bug with the CVS head version of gnome-theme-manager. I removed all themes from my ~/.themes directory, and from my $PREFIX/share/themes directory. The theme manager opened with no metathemes in the list, except for the auto generated "custom" theme. Can you confirm you still have this problem?
I can't find any reason why the current release will exit if no themes are found. The only reason it currently exits is if no gconf keys are found (bug 144040 has more information about this). Feel free to re-open if you can still reproduce the problem with the current release.