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 64135 - Cannot alter appearance widget, it never opens
Cannot alter appearance widget, it never opens
Status: RESOLVED DUPLICATE of bug 51532
Product: gnome-control-center
Classification: Core
Component: Other Preferences
unspecified
Other other
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2000-01-01 00:21 UTC by rboileau
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description rboileau 2001-11-09 09:37:58 UTC 
Package: control-center
Severity: normal
Version: 0.38
Synopsis: Cannot alter appearance widget, it never opens
Bugzilla-Product: control-center
Bugzilla-Component: other capplets

Description:
I selected, uhh, one of the appearance themes in 'sawfish window
manager' GTK box, and then closed it out with "OK" [Off-topic: Would be
nice if there was an "APPLY" box here].  When I re-opened 'appearance',
it locks up and never gives me the gtk appearance box.

I don't remember the name of the theme, and cannot open it to select it
again.



Debugging Information:

(no debugging symbols found)...0x40578ce9 in __wait4 () from /lib/libc.so.6

+ Trace 13285

  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 gnome_segv_handle
    at gnome-init.c line 659
  • #3 <signal handler called>
  • #4 gtk_container_remove
    at gtkcontainer.c line 729
  • #5 _start
    at eval.c line 41
  • #6 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312
  • #7 gtk_handlers_run
    at gtksignal.c line 1917
  • #8 gtk_signal_real_emit
    at gtksignal.c line 1477
  • #9 gtk_signal_emit
    at gtksignal.c line 552
  • #10 cancel_cb
    at eval.c line 41
  • #11 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312
  • #12 gtk_handlers_run
    at gtksignal.c line 1917
  • #13 gtk_signal_real_emit
    at gtksignal.c line 1477
  • #14 gtk_signal_emit
    at gtksignal.c line 552
  • #15 gtk_button_clicked
    at gtkbutton.c line 336
  • #16 gtk_real_button_released
    at gtkbutton.c line 861
  • #17 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312
  • #18 gtk_signal_real_emit
    at gtksignal.c line 1440
  • #19 gtk_signal_emit
    at gtksignal.c line 552
  • #20 gtk_button_released
    at gtkbutton.c line 327
  • #21 gtk_button_button_release
    at gtkbutton.c line 721
  • #22 gtk_marshal_BOOL__POINTER
    at gtkmarshal.c line 28
  • #23 gtk_signal_real_emit
    at gtksignal.c line 1492
  • #24 gtk_signal_emit
    at gtksignal.c line 552
  • #25 gtk_widget_event
    at gtkwidget.c line 2864
  • #26 gtk_propagate_event
    at gtkmain.c line 1378
  • #27 gtk_main_do_event
    at gtkmain.c line 818
  • #28 gdk_event_dispatch
    at gdkevents.c line 2139
  • #29 g_main_dispatch
    at gmain.c line 656
  • #30 g_main_iterate
    at gmain.c line 877
  • #31 g_main_run
    at gmain.c line 935
  • #32 gtk_main
    at gtkmain.c line 524
  • #33 capplet_gtk_main
    at eval.c line 41
  • #34 main
    at eval.c line 41
  • #35 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 gnome_segv_handle
    at gnome-init.c line 659
  • #3 <signal handler called>
  • #4 gtk_container_remove
    at gtkcontainer.c line 729
  • #5 _start
    at eval.c line 41
  • #6 gtk_marshal_NONE__NONE
    at gtkmarshal.c line 312
  • #7 gtk_handlers_run
    at gtksignal.c line 1917 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-11-09 04:37 -------

The original reporter (rboileau@theinquisition.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, tvgm@ximian.com.
Comment 1 Luis Villa 2002-01-31 15:43:50 UTC 

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