Bug 411871 – crash in Rhythmbox Music Player: I changed the id3 tag of...

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 411871 - crash in Rhythmbox Music Player: I changed the id3 tag of...


Summary:	crash in Rhythmbox Music Player: I changed the id3 tag of...


Status:	RESOLVED DUPLICATE of bug 396827

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.9.6
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	RhythmBox Maintainers
QA Contact:	RhythmBox Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-25 12:05 UTC by Harald
Modified:	2007-02-25 12:22 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Harald 2007-02-25 12:05:04 UTC

What were you doing when the application crashed?
I changed the id3 tag of a file which was in focus manually with id3v2.


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

Memory status: size: 105484288 vsize: 0 resident: 105484288 share: 0 rss: 40460288 rss_rlim: 0
CPU usage: start_time: 1172402254 rtime: 0 utime: 4209 stime: 0 cutime:3922 cstime: 0 timeout: 287 it_real_value: 0 frequency: 6

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 -1228076272 (LWP 5729)]
[New Thread -1275077728 (LWP 5740)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 113746

Thread 1 (Thread -1228076272 (LWP 5729))

#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_prop_changed_cb
at rhythmdb-property-model.c line 521
#12 rb_marshal_VOID__BOXED_INT_POINTER_POINTER
at rb-marshal.c line 363
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#17 rhythmdb_query_model_base_entry_prop_changed
at rhythmdb-query-model.c line 945
#18 rb_marshal_VOID__BOXED_INT_POINTER_POINTER
at rb-marshal.c line 363
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 rhythmdb_query_model_entry_changed_cb
at rhythmdb-query-model.c line 899
#24 rb_marshal_VOID__BOXED_POINTER
at rb-marshal.c line 408
#25 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#29 emit_entry_changed
at rhythmdb.c line 791
#30 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#31 rhythmdb_commit_internal
at rhythmdb.c line 915
#32 rb_song_info_sync_entries
at rb-song-info.c line 1294
#33 rb_song_info_response_cb
at rb-song-info.c line 672
#34 g_cclosure_marshal_VOID
from /usr/lib/libgobject-2.0.so.0
#35 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#36 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#37 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#38 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#39 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#40 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#41 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#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 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#47 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#48 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#49 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#50 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#51 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#52 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#53 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#54 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#55 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#56 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#57 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#58 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#59 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#60 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#61 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#62 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#63 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#64 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#65 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#66 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#67 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#68 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#69 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#70 main
at main.c line 381
#0 __kernel_vsyscall

Comment 1 Alex Lancaster 2007-02-25 12:22:29 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 ***