Bug 371593 – crash in Rhythmbox Music Player: I was saving changes to ...

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 371593 - crash in Rhythmbox Music Player: I was saving changes to ...


Summary:	crash in Rhythmbox Music Player: I was saving changes to ...


Status:	RESOLVED DUPLICATE of bug 359083

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:	2006-11-06 16:41 UTC by sohanley
Modified:	2006-11-06 17:32 UTC

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

Description sohanley 2006-11-06 16:41:14 UTC

What were you doing when the application crashed?
I was saving changes to the Song Properties for approximately 300 songs at once. The application appeared to hang, so I clicked X to close the Song Properties dialog box, then hit Force Quit when prompted.


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

Memory status: size: 92487680 vsize: 0 resident: 92487680 share: 0 rss: 29720576 rss_rlim: 0
CPU usage: start_time: 1162831435 rtime: 0 utime: 1401 stime: 0 cutime:1168 cstime: 0 timeout: 233 it_real_value: 0 frequency: 2

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 -1229011280 (LWP 7590)]
[New Thread -1267737696 (LWP 7606)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 83651

Thread 1 (Thread -1229011280 (LWP 7590))

#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_new
#11 rhythmdb_property_model_new
#12 rb_marshal_VOID__BOXED_INT_POINTER_POINTER
#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_new
#18 rb_marshal_VOID__BOXED_POINTER
#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_emit_entry_deleted
#24 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#25 rhythmdb_error_quark
#26 rhythmdb_commit
#27 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#28 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#29 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#30 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#31 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#32 main
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-11-06 17:32:20 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.


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