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 101567 - gnome-theme-manager crash on startup for 1st time run - after that it runs without crashing
gnome-theme-manager crash on startup for 1st time run - after that it runs wi...
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: [obsolete] theme-manager
unspecified
Other other
: Urgent critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 101757 102459 102786 103632 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-12-19 01:34 UTC by Greg Schafer
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2


Description Greg Schafer 2002-12-19 01:34:07 UTC 
Package: control-center
Severity: normal
Version: GNOME2.1.5 2.1.5
Synopsis: Crash on startup for 1st time run - after that it runs without crashing
Bugzilla-Product: control-center
Bugzilla-Component: theme-manager
BugBuddy-GnomeVersion: 2.0 (2.1.5)
Description:
Description of Problem:
Crashes when running it for the 1st time. Seems to be OK after that.

This is latest tarballs as of 20021219 and compiled a-la garnome.

control-center-2.1.5



Debugging Information:

Backtrace was generated from '/opt/gnome2.1/bin/gnome-theme-manager'

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

+ Trace 31853

  • #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 g_logv
    at gmessages.c line 486
  • #7 g_log
    at gmessages.c line 500
  • #8 update_list_something
    at gnome-theme-details.c line 447
  • #9 gnome_theme_details_update_from_gconf
    at gnome-theme-details.c line 497
  • #10 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #11 g_closure_invoke
    at gclosure.c line 437
  • #12 signal_emit_unlocked_R
    at gsignal.c line 2822
  • #13 g_signal_emit_valist 
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-12-18 20:34 -------

Reassigning to the default owner of the component, control-center-maint@bugzilla.gnome.org.
Comment 1 Alex Duggan 2002-12-19 01:41:10 UTC 
new crasher introduced in 2.1.5
Comment 2 Andrew Sobala 2002-12-19 16:11:55 UTC 
grrrr. Can anyone verify?
Comment 3 Andrew Sobala 2002-12-20 17:41:36 UTC 
Totally reproducable.
Comment 4 Alex Duggan 2002-12-21 21:57:03 UTC 
*** Bug 101757 has been marked as a duplicate of this bug. ***
Comment 5 André Dahlqvist 2002-12-24 14:51:35 UTC 
Is this a dupe of bug 99402?
Comment 6 Andrew Sobala 2002-12-24 15:33:40 UTC 
No.

Andre, the first few stack frames (lines) in a backtrace are always
the same. You have to look for application-specific frames such as
"update_list_something" in this bug and
"_capplet_widget_server_cancel" in bug 99402 (which is against GNOME
1.4 with a different code path anyway).
Comment 7 Seth Nickell 2002-12-28 23:56:48 UTC 
How do you reproduce this Andrew?
Comment 8 Andrew Sobala 2002-12-29 01:14:21 UTC 
I got this by creating a new user in RH8, starting a GNOME 2.1 session
and starting the theme manager. Boom.

If you can't reproduce it, bug me and I'll check it still happens for me.
Comment 9 Mark Finlay 2002-12-30 13:42:15 UTC 
To reproduce:

rm -rf ~/.g* && gnome-theme-manager
Comment 10 Mark Finlay 2002-12-30 14:37:50 UTC 
Actually. What you have to do to reporduce is log out and delete
~/.gconf/apps/metacity from the console and then log back in 
and run the themes applet. I have no idea why this directory
doesn't exitst in a fresh user account.
Comment 11 Andrew Sobala 2002-12-30 22:13:15 UTC 
serious 2.2.0 blocker. pri=urgent
Comment 12 Andrew Sobala 2003-01-04 01:15:22 UTC 
*** Bug 102459 has been marked as a duplicate of this bug. ***
Comment 13 Alex Duggan 2003-01-07 22:41:18 UTC 
*** Bug 102786 has been marked as a duplicate of this bug. ***
Comment 14 Jonathan Blandford 2003-01-16 19:47:27 UTC 
Fixed in 2.1.7
Comment 15 Andrew Sobala 2003-01-16 20:11:51 UTC 
*** Bug 103632 has been marked as a duplicate of this bug. ***