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 423916 - crash in color scheme code
crash in color scheme code
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
2.10.x
Other Linux
: Normal critical
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2007-03-28 21:33 UTC by Jens Granseuer
Modified: 2007-04-30 19:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Jens Granseuer 2007-03-28 21:33:25 UTC
When starting gnome-theme-manager, it crashes with the following trace.

control-center version is 2.18.0, gtk+ is 2.10.11.

I also tried patching my version of gtk with the changes currently in the 2-10 branch which touch the color scheme code, but to no avail.

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

Thread 1 (Thread 1024 (LWP 20560))

  • #0 wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.0
  • #3 libgnomeui_module_info_get
    from /opt/gnome2/lib/libgnomeui-2.so.0
  • #4 pthread_sighandler
    from /lib/libpthread.so.0
  • #5 <signal handler called>
  • #6 g_hash_table_foreach
    at ghash.c line 675
  • #7 get_color_scheme
    at gtksettings.c line 1861
  • #8 gtk_settings_get_property
    at gtksettings.c line 624
  • #9 object_get_property
    at gobject.c line 659
  • #10 g_object_get_valist
    at gobject.c line 1177
  • #11 g_object_get
    at gobject.c line 1222
  • #12 gnome_theme_details_init
  • #13 gnome_theme_details_update_from_gconf
  • #14 free_all
  • #15 g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #16 g_closure_invoke
    at gclosure.c line 490
  • #17 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #18 g_signal_emit_valist
    at gsignal.c line 2199
  • #19 g_signal_emit
    at gsignal.c line 2243
  • #20 gnome_window_manager_settings_changed
    from /opt/gnome2/lib/libgnome-window-settings.so.1
  • #21 value_changed
    at metacity-window-manager.c line 71
  • #22 gconf_marshal_VOID__STRING_POINTER
    from /opt/gnome2/lib/libgconf-2.so.4
  • #23 g_closure_invoke
    at gclosure.c line 490
  • #24 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #25 g_signal_emit_valist
    at gsignal.c line 2199
  • #26 g_signal_emit
    at gsignal.c line 2243
  • #27 gconf_client_value_changed
    from /opt/gnome2/lib/libgconf-2.so.4
  • #28 gconf_client_change_set_from_current
    from /opt/gnome2/lib/libgconf-2.so.4
  • #29 gconf_client_change_set_from_current
    from /opt/gnome2/lib/libgconf-2.so.4
  • #30 gconf_client_change_set_from_current
    from /opt/gnome2/lib/libgconf-2.so.4
  • #31 g_idle_dispatch
    at gmain.c line 4096
  • #32 g_main_dispatch
    at gmain.c line 2061
  • #33 g_main_context_dispatch
    at gmain.c line 2613
  • #34 g_main_context_iterate
    at gmain.c line 2694
  • #35 g_main_loop_run
    at gmain.c line 2898
  • #36 gtk_main
    at gtkmain.c line 1154
  • #37 main

Comment 1 Matthias Clasen 2007-04-30 19:28:17 UTC
2007-04-30  Matthias Clasen  <mclasen@redhat.com>

        * gtk/gtksettings.c (settings_update_color_scheme):
        Make sure we always have a color_hash.  (#423916, Jens Granseuer)