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 413559 - crash in Rhythmbox Music Player: Changing ID3 tags AGAIN!
crash in Rhythmbox Music Player: Changing ID3 tags AGAIN!
Status: RESOLVED DUPLICATE of bug 396827
Product: rhythmbox
Classification: Other
Component: general
0.9.6
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-01 19:13 UTC by david.hagar
Modified: 2007-03-02 01:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description david.hagar 2007-03-01 19:13:03 UTC 
What were you doing when the application crashed?
Changing ID3 tags AGAIN!


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 153763840 vsize: 0 resident: 153763840 share: 0 rss: 39170048 rss_rlim: 0
CPU usage: start_time: 1172775473 rtime: 0 utime: 6499 stime: 0 cutime:5880 cstime: 0 timeout: 619 it_real_value: 0 frequency: 10

Backtrace was generated from '/usr/bin/rhythmbox'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1228412736 (LWP 24066)]
[New Thread -1317041248 (LWP 24263)]
[New Thread -1384182880 (LWP 24261)]
[New Thread -1254442080 (LWP 24103)]
[New Thread -1308648544 (LWP 24102)]
[New Thread -1289094240 (LWP 24086)]
[New Thread -1290798176 (LWP 24081)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 114986

Thread 1 (Thread -1228412736 (LWP 24066))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 rhythmdb_property_model_delete_prop
    at rhythmdb-property-model.c line 618
  • #11 rhythmdb_property_model_entry_removed_cb
    at rhythmdb-property-model.c line 536
  • #12 _remove_entry_cb
    at rhythmdb-property-model.c line 277
  • #13 gtk_tree_model_iter_next
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_tree_model_foreach
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 rhythmdb_property_model_set_property
    at rhythmdb-property-model.c line 308
  • #16 g_object_set_valist
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_object_set
    from /usr/lib/libgobject-2.0.so.0
  • #18 rebuild_child_model
    at rb-library-browser.c line 588
  • #19 rb_library_browser_set_selection
    at rb-library-browser.c line 622
  • #20 view_property_selected_cb
    at rb-library-browser.c line 351
  • #21 g_cclosure_marshal_VOID__POINTER
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #26 rb_property_view_selection_changed_cb
    at rb-property-view.c line 705
  • #27 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #32 _gtk_tree_view_find_node
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 g_cclosure_marshal_VOID__BOXED
    from /usr/lib/libgobject-2.0.so.0
  • #34 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #35 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #36 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #37 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #38 gtk_tree_model_row_deleted
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 rhythmdb_property_model_delete_prop
    at rhythmdb-property-model.c line 633
  • #40 rhythmdb_property_model_prop_changed_cb
    at rhythmdb-property-model.c line 521
  • #41 rb_marshal_VOID__BOXED_INT_POINTER_POINTER
    at rb-marshal.c line 363
  • #42 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #43 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #44 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #45 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #46 rhythmdb_query_model_entry_changed_cb
    at rhythmdb-query-model.c line 899
  • #47 rb_marshal_VOID__BOXED_POINTER
    at rb-marshal.c line 408
  • #48 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #49 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #50 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #51 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #52 emit_entry_changed
    at rhythmdb.c line 791
  • #53 g_hash_table_foreach
    from /usr/lib/libglib-2.0.so.0
  • #54 rhythmdb_commit_internal
    at rhythmdb.c line 915
  • #55 timeout_rhythmdb_commit
    at rhythmdb.c line 942
  • #56 g_source_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #57 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #58 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #59 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #60 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #61 main
    at main.c line 381
  • #0 __kernel_vsyscall 






Comment 1


Alex Lancaster





          2007-03-02 01:08:56 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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