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 103531 - theme-manager crash upon launch
theme-manager crash upon launch
Status: RESOLVED DUPLICATE of bug 97883
Product: gnome-control-center
Classification: Core
Component: [obsolete] theme-manager
2.1.x
Other Linux
: Normal critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-01-15 00:01 UTC by Jeremy Browne
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2


Description Jeremy Browne 2003-01-15 00:01:23 UTC 
Description of Problem:

Version: GNOME 2.1.90 theme-manager 2.1.6.1

This is a different stack trace from what I'm used to seeing, no doubt
thanks to recent fixes made.

Most recent CVS Changelog entry is:
Tue Jan 14 02:16:22 2003  Jonathan Blandford  <jrb@gnome.org>

        * gnome-theme-manager.c (load_meta_themes): set the correct row to
        the new data.  This was messing a lot up.  Saving now works, so
        long as you don't type bad data.

        * TODO: update.

Debugging Information:

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

[New Thread 16384 (LWP 13714)]
0x4b73c8a9 in wait4 () from /lib/libc.so.6

+ Trace 32734

Thread 1 (Thread 16384 (LWP 13714))

  • #0 wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.0
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 646
  • #4 __pthread_sighandler
    from /lib/libpthread.so.0
  • #5 <signal handler called>
  • #6 gnome_window_manager_get_settings
    at gnome-window-manager.c line 136
  • #7 load_meta_themes
    at gnome-theme-manager.c line 288 






Comment 1


Andrew Sobala





          2003-01-15 00:11:24 UTC
        




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