Bug 567810 – crash in Rhythmbox Music Player: i was listening to a pod...

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 567810 - crash in Rhythmbox Music Player: i was listening to a pod...


Summary:	crash in Rhythmbox Music Player: i was listening to a pod...


Status:	RESOLVED OBSOLETE

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.12.x
Hardware:	Other All

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

URL:
Whiteboard:

Duplicates:	571959 606361 (view as bug list)
Depends on:
Blocks:

Reported:	2009-01-14 23:58 UTC by jan.teichmann
Modified:	2018-05-24 13:56 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description jan.teichmann 2009-01-14 23:58:31 UTC

Version: 0.11.6

What were you doing when the application crashed?
i was listening to a podcast mp3


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.2 2008-11-25 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.9-159.fc10.x86_64 #1 SMP Tue Dec 16 14:47:52 EST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 1039183872 vsize: 1039183872 resident: 66183168 share: 23134208 rss: 66183168 rss_rlim: 18446744073709551615
CPU usage: start_time: 1231976316 rtime: 12829 utime: 11169 stime: 1660 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7fefe87ef800 (LWP 3853)]
[New Thread 0x7fefc70d3950 (LWP 4924)]
[New Thread 0x7fefc98f5950 (LWP 4923)]
[New Thread 0x7fefc84f3950 (LWP 4922)]
[New Thread 0x7fefd1a34950 (LWP 4920)]
[New Thread 0x7fefd2435950 (LWP 4919)]
[New Thread 0x7fefc52d0950 (LWP 4859)]
[New Thread 0x7fefc8ef4950 (LWP 4452)]
[New Thread 0x7fefcecf8950 (LWP 4031)]
[New Thread 0x7fefd630f950 (LWP 3860)]
0x0000003057c0ec2f in waitpid () from /lib64/libpthread.so.0

+ Trace 211557

Thread 1 (Thread 0x7fefe87ef800 (LWP 3853))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_spawn_sync
from /lib64/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /lib64/libglib-2.0.so.0
#3 ??
from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
#4 ??
from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 raise
from /lib64/libc.so.6
#7 abort
from /lib64/libc.so.6
#8 g_assertion_message
from /lib64/libglib-2.0.so.0
#9 g_assertion_message_expr
from /lib64/libglib-2.0.so.0
#10 rhythmdb_tree_entry_delete
at rhythmdb-tree.c line 1637
#11 rhythmdb_entry_delete
at rhythmdb.c line 3519
#12 impl_delete
at rb-podcast-source.c line 1020
#13 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#14 ??
from /lib64/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#16 g_signal_emit
from /lib64/libgobject-2.0.so.0
#17 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#18 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#19 ??
from /lib64/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#21 g_signal_emit
from /lib64/libgobject-2.0.so.0
#22 gtk_widget_activate
from /usr/lib64/libgtk-x11-2.0.so.0
#23 gtk_menu_shell_activate_item
from /usr/lib64/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#25 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#26 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#27 ??
from /lib64/libgobject-2.0.so.0
#28 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#29 g_signal_emit
from /lib64/libgobject-2.0.so.0
#30 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#31 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#32 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#33 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#34 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#35 ??
from /lib64/libglib-2.0.so.0
#36 g_main_loop_run
from /lib64/libglib-2.0.so.0
#37 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#38 main
at main.c line 330



----------- .xsession-errors (11 sec old) ---------------------
(rhythmbox:3853): RhythmDB-WARNING **: trying to sync properties of non-editable file
(rhythmbox:3853): RhythmDB-WARNING **: trying to sync properties of non-editable file
(rhythmbox:3853): RhythmDB-WARNING **: trying to sync properties of non-editable file
(rhythmbox:3853): RhythmDB-WARNING **: trying to sync properties of non-editable file
(rhythmbox:3853): RhythmDB-WARNING **: trying to sync properties of non-editable file
(rhythmbox:3853): RhythmDB-WARNING **: trying to sync properties of non-editable file
[01-14 23:44:40] Torbutton NOTE: Skipping no location: chrome://browser/content/browser.xul
**
RhythmDB:ERROR:rhythmdb-tree.c:1637:rhythmdb_tree_entry_delete: assertion failed: (g_hash_table_remove (db->priv->entries, entry->location))
--------------------------------------------------

Comment 1 Jonathan Matthew 2009-02-16 08:57:17 UTC

*** Bug 571959 has been marked as a duplicate of this bug. ***

Comment 2 Akhil Laddha 2010-01-08 04:11:58 UTC

*** Bug 606361 has been marked as a duplicate of this bug. ***

Comment 3 Akhil Laddha 2010-01-08 04:12:58 UTC

last duplicate has better traces and was filed against 0.12.x

Comment 4 Hans Spaans 2010-01-08 19:14:09 UTC

Are more traces needed when they occur?

Comment 5 mehdi 2011-10-24 20:53:32 UTC

Same thing happenned to me !

Comment 6 GNOME Infrastructure Team 2018-05-24 13:56:00 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rhythmbox/issues/687.