Bug 378603 – crash in Rhythmbox Music Player: Media library actualizat...

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 378603 - crash in Rhythmbox Music Player: Media library actualizat...


Summary:	crash in Rhythmbox Music Player: Media library actualizat...


Status:	RESOLVED DUPLICATE of bug 366346

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-23 20:08 UTC by bucozerca
Modified:	2006-12-19 10:09 UTC

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

Description bucozerca 2006-11-23 20:08:04 UTC

What were you doing when the application crashed?
Media library actualization.


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

Memory status: size: 119234560 vsize: 0 resident: 119234560 share: 0 rss: 27045888 rss_rlim: 0
CPU usage: start_time: 1164312380 rtime: 0 utime: 551 stime: 0 cutime:492 cstime: 0 timeout: 59 it_real_value: 0 frequency: 32

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 -1229121872 (LWP 8036)]
[New Thread -1263928416 (LWP 8048)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 88864

Thread 1 (Thread -1229121872 (LWP 8036))

#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 gnome_vfs_uri_unref
from /usr/lib/libgnomevfs-2.so.0
#5 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#6 ??
#7 ??
#8 ??
#9 async_job_callback_map_destroy
from /usr/lib/libgnomevfs-2.so.0
#10 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#11 ??
#12 ??
#13 ??
#14 ??
from /usr/lib/libgthread-2.0.so.0
#15 ??
#16 ??
from /usr/lib/libglib-2.0.so.0
#17 ??
#18 g_slice_alloc
from /usr/lib/libglib-2.0.so.0
#19 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 main
#0 __kernel_vsyscall

Comment 1 James "Doc" Livingston 2006-11-25 02:44:10 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Alex Lancaster 2006-12-19 10:09:37 UTC

Stack trace looks the same as bug #366346.

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