Bug 356958 – crash in Rhythmbox Music Player: I tried to edit tag info...

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 356958 - crash in Rhythmbox Music Player: I tried to edit tag info...


Summary:	crash in Rhythmbox Music Player: I tried to edit tag info...


Status:	RESOLVED DUPLICATE of bug 352972

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-09-20 20:01 UTC by willem.vanbergen
Modified:	2006-09-20 20:15 UTC

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

Description willem.vanbergen 2006-09-20 20:01:01 UTC

What were you doing when the application crashed?
I tried to edit tag information on a set of MP3 files


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 62599168 vsize: 0 resident: 62599168 share: 0 rss: 22274048 rss_rlim: 0
CPU usage: start_time: 1158782417 rtime: 0 utime: 65 stime: 0 cutime:60 cstime: 0 timeout: 5 it_real_value: 0 frequency: 4

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228563696 (LWP 12438)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 72859

Thread 1 (Thread -1228563696 (LWP 12438))

#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 strlen
from /lib/tls/i686/cmov/libc.so.6
#5 g_strdup
from /usr/lib/libglib-2.0.so.0
#6 itdb_device_list_devices
from /usr/lib/libgpod.so.0
#7 itdb_device_list_devices
from /usr/lib/libgpod.so.0
#8 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#9 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_object_new
from /usr/lib/libgobject-2.0.so.0
#11 itdb_device_new
from /usr/lib/libgpod.so.0
#12 itdb_set_mountpoint
from /usr/lib/libgpod.so.0
#13 itdb_parse
from /usr/lib/libgpod.so.0
#14 rb_ipod_source_register_type
from /usr/lib/rhythmbox/plugins/libipod.so
#15 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#16 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_object_new
from /usr/lib/libgobject-2.0.so.0
#18 rb_ipod_source_new
from /usr/lib/rhythmbox/plugins/libipod.so
#19 register_rb_plugin
from /usr/lib/rhythmbox/plugins/libipod.so
#20 rb_marshal_OBJECT__OBJECT
#21 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#25 rb_removable_media_manager_queue_transfer
#26 rb_removable_media_manager_scan
#27 rb_shell_new
#28 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#29 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#30 g_object_new
from /usr/lib/libgobject-2.0.so.0
#31 rb_shell_new
#32 main
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-09-20 20:15:22 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Also, the maintainers need more information to fix the bug. Could you please answer the questions in the other report?


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