| Summary: | Theme Manager crashes at startup | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | hossein <hossein> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
hossein
2003-03-24 00:57:12 UTC
I dont know what the hell happened. I mistakenly set this in gentoo ppc? It should have gone in x86 and under gnome. Sorry about this no problem, bout to say, mine works fine =) does this gnome theme manager still have the fam-related bugs? if you're running FAM, stop it and try running theme manager then. What happens? what version of control center ? Okay, control-center shows 2.2.1 at the risk of sounding stupid, what is FAM and how do you stop it? Thanks that is weird how it recursively called gnome_theme_save_dialog_show() multiple times. have you tried lowering your CFLAGS to -march=pentium3? and maybe looks rather similar to this bug: http://bugzilla.gnome.org/show_bug.cgi?id=105268 I will try resetting the cflags. I had them initially at O3 and fomitframepointer, then when I saw the no debug symbols found, I tried setting my flags to -g (only) and removing the fomit and re emerged control center. I get the same error and no other stack info. I was reading through and I think I cam accross a post in the forums that symbols are stripped manually after a package is emerged? Thanks for the help guys. if you add DEBUGBUILD="yes" in your /etc/make.conf it will not strip the binaries. looking at the strcmp in the code, it seems to be pointing to either you have no themes installed or your gconf doesn't have the key /desktop/gnome/interface/gtk_theme set. try using gconf-editor to see if you have that key set to something other than empty or NULL. FIXED! after entering a theme name into the key you specified, the theme manager now starts properly. It is odd that just because the key was not set, the theme manager crashed. Thanks again yeah, can someone check if the key gets set on a basic install. liquidx, what do you think. should we patch the code to get around this possible problem ? Also, just out of curiousity, if I were to modify my gconf directly (as might have happened in this case and lead to this issue) is there a way to restore a default version of it? This seems a little too much like the windows registry. Also, just in case this might help, as I remmember, the key's type was not even a string, but an integer. Thanks again the default value for this key is "Default", thats in /etc/gconf/schemas/... i can't figure why it would suddenly get switched to the wrong type. i'll have a look and see if i can whip up a patch .. reporter did you or did you not fiddle with the keys yourself ? i mean this shouldnt happen out of the blue if the install sets the keys right. sorry for the delayed response. I cannot say if the keys were fiddled with or not as there are 3 other users that are currently using this system. I suppose it was a mistake on my part to just use one username for all. Nevertheless, should the theme-manager segfault even in that case? hmm not really, but it's impossible to make software completely 'foolproof' so to say. seems to be related to invalid gconf keys |
