Bug 367125 – crash in Rhythmbox Music Player: opening mp3 files on a s...

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 367125 - crash in Rhythmbox Music Player: opening mp3 files on a s...


Summary:	crash in Rhythmbox Music Player: opening mp3 files on a s...


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-10-29 19:59 UTC by roblkuhnjr
Modified:	2006-10-29 20:11 UTC

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

Description roblkuhnjr 2006-10-29 19:59:14 UTC

What were you doing when the application crashed?
opening mp3 files on a server, adding lwatch folder


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

Memory status: size: 150970368 vsize: 0 resident: 150970368 share: 0 rss: 27402240 rss_rlim: 0
CPU usage: start_time: 1162151619 rtime: 0 utime: 3791 stime: 0 cutime:3207 cstime: 0 timeout: 584 it_real_value: 0 frequency: 22

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 -1228609344 (LWP 4516)]
[New Thread -1338287200 (LWP 4911)]
[New Thread -1329894496 (LWP 4910)]
[New Thread -1313109088 (LWP 4909)]
[New Thread -1287930976 (LWP 4908)]
[New Thread -1279538272 (LWP 4907)]
[New Thread -1271145568 (LWP 4906)]
[New Thread -1296323680 (LWP 4905)]
[New Thread -1243354208 (LWP 4904)]
[New Thread -1304716384 (LWP 4903)]
[New Thread -1253049440 (LWP 4902)]
[New Thread -1321501792 (LWP 4746)]
[New Thread -1262707808 (LWP 4529)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79985

Thread 1 (Thread -1228609344 (LWP 4516))

#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 André Klapper 2006-10-29 20:11:59 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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