Bug 359929 – crash in Rhythmbox Music Player: I just start the player....

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 359929 - crash in Rhythmbox Music Player: I just start the player....


Summary:	crash in Rhythmbox Music Player: I just start the player....


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-10-05 16:26 UTC by Andrey Kalinin
Modified:	2006-10-05 16:29 UTC

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

Description Andrey Kalinin 2006-10-05 16:26:09 UTC

What were you doing when the application crashed?
I just start the player. It begun to scan folders and then show me this message.


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

Memory status: size: 112803840 vsize: 0 resident: 112803840 share: 0 rss: 27140096 rss_rlim: 0
CPU usage: start_time: 1160065515 rtime: 0 utime: 463 stime: 0 cutime:430 cstime: 0 timeout: 33 it_real_value: 0 frequency: 17

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 -1229272304 (LWP 4748)]
[New Thread -1296880736 (LWP 4762)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 74713

Thread 1 (Thread -1229272304 (LWP 4748))

#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 *__GI_raise
from /lib/tls/i686/cmov/libc.so.6
#6 *__GI_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 g_cclosure_marshal_VOID__BOXED
from /usr/lib/libgobject-2.0.so.0
#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_entry_to_iter
#18 rhythmdb_query_model_get_type
#19 rhythmdb_query_model_remove_entry
#20 rhythmdb_query_model_new
#21 rb_marshal_VOID__BOXED_POINTER
#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 rhythmdb_emit_entry_deleted
#27 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#28 rhythmdb_error_quark
#29 rhythmdb_commit
#30 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#31 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#33 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#34 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#35 main
#0 __kernel_vsyscall

Comment 1 Elijah Newren 2006-10-05 16:29:19 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.

Matches the stack trace in bug 359551, which has been marked as a duplicate of 359083

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