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 114200 - Segmentation Fault as soon as theme-manager opens.
Segmentation Fault as soon as theme-manager opens.
Status: RESOLVED DUPLICATE of bug 105268
Product: gnome-control-center
Classification: Core
Component: [obsolete] theme-manager
unspecified
Other Linux
: Normal critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 114201 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-06-01 15:32 UTC by cdaley
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2



Description cdaley 2003-06-01 15:32:42 UTC
Description of Problem: 
Upon selecting THEME from APPLICATIONS > DESKTOP 
PREFERENCES, the theme-manager opens, displays a 
list of themes, and then crashes: 
 
Application "gnome-theme-manager" (process 1461) has 
crashed 
due to a fatal error. 
(Segmentation fault) 
 
 
This happens everytime I try to open the theme-manager -- 
I've never been able to run it. 
 
Additional Information: 
Gentoo Linux - PPC 
Gnome 2.2.1
Comment 1 Andrew Sobala 2003-06-01 18:14:38 UTC
*** Bug 114201 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Sobala 2003-06-01 18:15:21 UTC
Thanks for the bug report. Without a stack trace from the crash it's
very hard to determine what caused the crash.  Please see
http://bugzilla.gnome.org/getting-traces.cgi for more information
about getting a useful stack trace.
Comment 3 austinsr 2003-06-17 20:45:08 UTC
Backtrace was generated from '/usr/bin/gnome-theme-manager'

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 1085672960 (LWP 22960)]

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols
found)...0xffffe002 in ??
    ()

Thread 1 (Thread 1085672960 (LWP 22960))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib/tls/libc.so.6
  • #4 gnome_theme_save_show_dialog
  • #5 gnome_theme_save_show_dialog
  • #6 gnome_theme_save_show_dialog
  • #7 main
  • #8 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??

Comment 4 Andrew Sobala 2003-06-18 14:14:01 UTC
Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs you find.


*** This bug has been marked as a duplicate of 105268 ***
Comment 5 Andrew Sobala 2003-07-20 23:39:15 UTC
Dude, sneaking around reopening closed bugs is not the way to get your
issue seen by a developer. Best bet is to post useful information to
the *relevant* bug (or to look at it yourself ;)

*** This bug has been marked as a duplicate of 105268 ***
Comment 6 Andrew Sobala 2003-07-20 23:40:16 UTC
Sorry, that comment was directed at joaommp@myrealbox.com