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 103890 - gnome-theme-manager crashes when run
gnome-theme-manager crashes when run
Status: RESOLVED DUPLICATE of bug 97883
Product: gnome-control-center
Classification: Core
Component: [obsolete] theme-manager
unspecified
Other other
: Normal critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-01-19 18:37 UTC by Clayton
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Clayton 2003-01-19 18:35:12 UTC 
Package: control-center
Severity: critical
Version: GNOME2.1.90 2.1.6
Synopsis: gnome-theme-manager crashes when run
Bugzilla-Product: control-center
Bugzilla-Component: theme-manager
BugBuddy-GnomeVersion: 2.0 (2.1.90)
Description:
Description of Problem:
I clicked on Applications -> Desktop Preferences - > Theme; the
application that was run crashed as soon as it started.




Debugging Information:

Backtrace was generated from
'/home/cyberclay/garnome/bin/gnome-theme-manager'

[New Thread 1024 (LWP 21181)]
0x40ab6369 in __wait4 () at __wait4:-1
	in __wait4

+ Trace 32909

Thread 1 (Thread 1024 (LWP 21181))

  • #0 __wait4
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 646
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 g_logv 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-19 13:35 -------

Reassigning to the default owner of the component, control-center-maint@bugzilla.gnome.org.
Comment 1 Andrew Sobala 2003-01-19 19:05:07 UTC 
Please upgrade to control center 2.1.7 (from ftp.gnome.org) and help
us test it. This should be fixed in that version.

*** This bug has been marked as a duplicate of 97883 ***