Bug 380354 – crash in Rhythmbox Music Player: Just letting Rhythmbox p...

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 380354 - crash in Rhythmbox Music Player: Just letting Rhythmbox p...


Summary:	crash in Rhythmbox Music Player: Just letting Rhythmbox p...


Status:	RESOLVED INCOMPLETE

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-29 01:51 UTC by Kristoffer Lundén
Modified:	2008-06-08 11:53 UTC

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

Description Kristoffer Lundén 2006-11-29 01:51:14 UTC

What were you doing when the application crashed?
Just letting Rhythmbox play my collection, nothing more.


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

Memory status: size: 234860544 vsize: 0 resident: 234860544 share: 0 rss: 45682688 rss_rlim: 0
CPU usage: start_time: 1164752864 rtime: 0 utime: 790374 stime: 0 cutime:342514 cstime: 0 timeout: 447860 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 -1228396880 (LWP 23370)]
[New Thread -1407226976 (LWP 31771)]
[New Thread -1321206880 (LWP 31769)]
[New Thread -1388348512 (LWP 31699)]
[New Thread -1248048224 (LWP 31490)]
[New Thread -1363170400 (LWP 27813)]
[New Thread -1243575392 (LWP 24935)]
[New Thread -1312814176 (LWP 23393)]
[New Thread -1268335712 (LWP 23379)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 90162

Thread 1 (Thread -1228396880 (LWP 23370))

#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 IA__g_logv
#8 IA__g_log
#9 IA__g_assert_warning
#10 rhythmdb_entry_set_internal
#11 rhythmdb_entry_set
#12 rhythmdb_shutdown
#13 rhythmdb_shutdown
#14 g_timeout_dispatch
at gmain.c line 3422
#15 IA__g_main_context_dispatch
at gmain.c line 2045
#16 g_main_context_iterate
at gmain.c line 2677
#17 IA__g_main_loop_run
at gmain.c line 2881
#18 IA__gtk_main
at gtkmain.c line 1024
#19 main
#0 __kernel_vsyscall

Comment 1 Alex Lancaster 2006-11-29 02:00:03 UTC

Stack trace looks similar to bug #361926 which was closed as INCOMPLETE because no new information was provided.

Can you include a stacktrace that has debug symbols for rhythmbox as well as gtk?

Comment 2 Kristoffer Lundén 2006-11-29 02:19:07 UTC

Rhythmbox doesn't usually crash (good thing) so I'm not sure I can reproduce. Bug buddy collected and sent this. 

I have however now installed rhythmbox-dbg and already had libgtk2.0-0-dbg - is there any more dbg packages I should have *if* it happens again?

Comment 3 James "Doc" Livingston 2006-11-29 06:54:31 UTC

That crash (and the one in bug 361926 as well) are the result of an assertion begin triggered, in particular some of Rhythmbox's code not ensuring that a string read from somewhere if UTF-8 before passsing it to the database.

rhythmbox-dbg will be enough, as we just need to know what piece of Rhythmbox's code is failing to do the verification. Thanks.

Comment 4 Kristoffer Lundén 2007-07-05 23:42:48 UTC

Haven't had a crash since... don't know about your policy on this stuff, but feel free to close the bug as far as I'm concerned. :)

Comment 5 André Klapper 2008-06-08 11:53:53 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!