After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 104210 - Theme manager refuses to work with no meta themes installed
Theme manager refuses to work with no meta themes installed
Status: RESOLVED OBSOLETE
Product: gnome-control-center
Classification: Core
Component: [obsolete] theme-manager
2.4.x
Other other
: Normal major
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
AES[BIGBADBUG]
Depends on:
Blocks:
 
 
Reported: 2003-01-23 10:20 UTC by Johannes Rohr
Modified: 2006-04-30 11:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Johannes Rohr 2003-01-23 10:19:59 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.

Comment 1 Andrew Sobala 2003-01-23 17:54:39 UTC
Regression->High
Comment 2 Andrew Sobala 2003-02-08 16:50:16 UTC
*** Bug 105585 has been marked as a duplicate of this bug. ***
Comment 3 Kjartan Maraas 2003-07-09 12:53:30 UTC
Is this still behaving the same way?
Comment 4 Chris Lahey 2004-03-03 21:39:36 UTC
It is.
Comment 5 Johannes Rohr 2004-03-05 21:27:06 UTC
Yep. Situation is unchanged (sorry for the delay in responding!)
Comment 6 Johannes Rohr 2004-03-05 21:28:24 UTC
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.
Comment 7 Luis Villa 2004-12-08 17:43:36 UTC
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.
Comment 8 Johannes Rohr 2005-01-16 13:30:55 UTC
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.
Comment 9 Thomas Wood 2006-01-03 23:45:46 UTC
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?
Comment 10 Thomas Wood 2006-04-30 11:00:00 UTC
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.