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 689212 - Crash when opening preferences
Crash when opening preferences
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: general
2.97
Other Linux
: Normal critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-11-28 11:50 UTC by Lionel Landwerlin
Modified: 2018-05-24 17:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Valgrind log (140.33 KB, text/plain)
2012-11-28 12:03 UTC, Lionel Landwerlin
Details
dconf dump (1.28 KB, text/plain)
2012-11-28 13:19 UTC, Lionel Landwerlin
Details

Description Lionel Landwerlin 2012-11-28 11:50:13 UTC
Just click edit -> preferences


(gdb) thread apply all bt

Thread 1 (Thread 0x7ffff7fa49c0 (LWP 32601))

  • #0 g_type_is_a
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #1 g_signal_connect_data
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #2 gtk_cell_view_set_model
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #3 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #4 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #5 gtk_combo_box_set_model
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #6 impl_get_config_widget
    at rb-library-source.c line 802
  • #7 rb_shell_preferences_append_view_page
    at rb-shell-preferences.c line 380
  • #8 rb_shell_preferences_new
    at rb-shell-preferences.c line 416
  • #9 rb_shell_get_property
    at rb-shell.c line 1765
  • #10 g_object_get_valist
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #11 g_object_get
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #12 rb_shell_cmd_preferences
    at rb-shell.c line 2850
  • #13 g_closure_invoke
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #14 ??
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #18 g_closure_invoke
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #19 ??
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #22 gtk_widget_activate
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #23 gtk_menu_shell_activate_item
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #24 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #25 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #26 ??
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #27 g_signal_emit_valist
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #28 g_signal_emit
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #29 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #30 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #31 gtk_main_do_event
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #32 ??
    from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  • #33 g_main_context_dispatch
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #34 ??
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #35 g_main_context_iteration
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #36 g_application_run
    from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  • #37 main
    at main.c line 99

Comment 1 Lionel Landwerlin 2012-11-28 11:51:38 UTC
The crash happens in thread 3 (the one doing dconf related stuff).
Comment 2 Lionel Landwerlin 2012-11-28 12:03:20 UTC
Created attachment 230081 [details]
Valgrind log

I tried to run rhythmbox under valgrind but it crashes pretty early.
That's probably another problem but it might help to fix the original bug.
Comment 3 Jonathan Matthew 2012-11-28 12:33:25 UTC
The first crash looks like your dconf state is messed up. What output do you get from 'dconf dump /org/gnome/rhythmbox/' ?

The crash you saw under valgrind looks like a bug that was fixed after 2.97.
Comment 4 Lionel Landwerlin 2012-11-28 13:19:21 UTC
Created attachment 230084 [details]
dconf dump
Comment 5 Jonathan Matthew 2012-11-28 21:04:02 UTC
Guess that wasn't it. Can you install debug symbols for glib and dconf and get another stack trace?
Comment 6 Lionel Landwerlin 2012-11-29 10:43:45 UTC
Crash in thread 9 :

(gdb) thread apply all bt

Thread 1 (Thread 0x7fc5caddd9c0 (LWP 2941))

  • #0 unescape_gstring_inplace
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./glib/gmarkup.c line 593
  • #1 g_markup_parse_context_parse
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./glib/gmarkup.c line 1400
  • #2 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #3 gtk_builder_add_from_file
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #4 rb_builder_load
    at rb-builder-helpers.c line 73
  • #5 impl_get_config_widget
    at rb-library-source.c line 726
  • #6 rb_shell_preferences_append_view_page
    at rb-shell-preferences.c line 380
  • #7 rb_shell_preferences_new
    at rb-shell-preferences.c line 416
  • #8 rb_shell_get_property
    at rb-shell.c line 1765
  • #9 object_get_property
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gobject/gobject.c line 1294
  • #10 g_object_get_valist
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gobject/gobject.c line 2019
  • #11 g_object_get
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gobject/gobject.c line 2109
  • #12 rb_shell_cmd_preferences
    at rb-shell.c line 2850
  • #13 g_closure_invoke
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gobject/gclosure.c line 777
  • #14 signal_emit_unlocked_R
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gobject/gsignal.c line 3551
  • #15 g_signal_emit_valist
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gobject/gsignal.c line 3300
  • #16 g_signal_emit
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gobject/gsignal.c line 3356
  • #17 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #18 g_closure_invoke
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gobject/gclosure.c line 777
  • #19 signal_emit_unlocked_R
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gobject/gsignal.c line 3481
  • #20 g_signal_emit_valist
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gobject/gsignal.c line 3300
  • #21 g_signal_emit
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gobject/gsignal.c line 3356
  • #22 gtk_widget_activate
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #23 gtk_menu_shell_activate_item
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #24 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #25 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #26 _g_closure_invoke_va
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gobject/gclosure.c line 840
  • #27 g_signal_emit_valist
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gobject/gsignal.c line 3211
  • #28 g_signal_emit
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gobject/gsignal.c line 3356
  • #29 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #30 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #31 gtk_main_do_event
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #32 ??
    from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  • #33 g_main_dispatch
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./glib/gmain.c line 2715
  • #34 g_main_context_dispatch
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./glib/gmain.c line 3219
  • #35 g_main_context_iterate
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./glib/gmain.c line 3290
  • #36 g_main_context_iteration
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./glib/gmain.c line 3351
  • #37 g_application_run
    at /build/glib2.0-ZoE1pP/glib2.0-2.34.2/./gio/gapplication.c line 1624
  • #38 main
    at main.c line 99

Comment 7 GNOME Infrastructure Team 2018-05-24 17:46:53 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/1246.