Bug 409364 – crash in Rhythmbox Music Player: Importing a folder throu...

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 409364 - crash in Rhythmbox Music Player: Importing a folder throu...


Summary:	crash in Rhythmbox Music Player: Importing a folder throu...


Status:	RESOLVED DUPLICATE of bug 369214

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-18 18:31 UTC by ewiley
Modified:	2007-03-17 02:51 UTC

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

Description ewiley 2007-02-18 18:31:07 UTC

What were you doing when the application crashed?
Importing a folder through a Windows share, Fedora Core 6


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 184840192 vsize: 0 resident: 184840192 share: 0 rss: 20508672 rss_rlim: 0
CPU usage: start_time: 1171823280 rtime: 0 utime: 255 stime: 0 cutime:230 cstime: 0 timeout: 25 it_real_value: 0 frequency: 2

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208346912 (LWP 2757)]
[New Thread -1351648368 (LWP 2868)]
[New Thread -1341158512 (LWP 2867)]
[New Thread -1330668656 (LWP 2866)]
[New Thread -1320178800 (LWP 2865)]
[New Thread -1309688944 (LWP 2864)]
[New Thread -1299199088 (LWP 2863)]
[New Thread -1288709232 (LWP 2862)]
[New Thread -1278219376 (LWP 2861)]
[New Thread -1267729520 (LWP 2860)]
[New Thread -1244955760 (LWP 2859)]
[New Thread -1233642608 (LWP 2857)]
[New Thread -1255445616 (LWP 2765)]
(no debugging symbols found)
0x00d29402 in __kernel_vsyscall ()

+ Trace 111805

Thread 4 (Thread -1330668656 (LWP 2866))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/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/libc.so.6
#6 abort
from /lib/libc.so.6
#7 dbus_malloc
from /lib/libdbus-1.so.3
#8 dbus_watch_set_data
from /lib/libdbus-1.so.3
#9 dbus_message_unref
from /lib/libdbus-1.so.3
#10 gnome_vfs_daemon_message_iter_get_file_info
from /usr/lib/libgnomevfs-2.so.0
#11 gnome_vfs_daemon_message_iter_get_file_info
from /usr/lib/libgnomevfs-2.so.0
#12 gnome_vfs_get_file_info_uri_cancellable
from /usr/lib/libgnomevfs-2.so.0
#13 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#14 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#15 gnome_vfs_is_primary_thread
from /usr/lib/libgnomevfs-2.so.0
#16 g_thread_pool_push
from /lib/libglib-2.0.so.0
#17 g_thread_create_full
from /lib/libglib-2.0.so.0
#18 start_thread
from /lib/libpthread.so.0
#19 clone
from /lib/libc.so.6

Comment 1 Alex Lancaster 2007-02-19 06:32:34 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!

This may be fixed in a more recent version.  Can you please set the exact version in the "Version" field on the bug?

Comment 2 André Klapper 2007-03-17 02:51:26 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 369214 ***