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 514199 - crash in Rhythmbox Music Player: WAS WRITING CD TO DISC ,...
crash in Rhythmbox Music Player: WAS WRITING CD TO DISC ,...
Status: RESOLVED DUPLICATE of bug 434003
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-04 01:38 UTC by 9ballbump
Modified: 2008-02-04 10:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description 9ballbump 2008-02-04 01:38:00 UTC
What were you doing when the application crashed?
WAS WRITING CD TO DISC , PRESSED PLAY AND IT BOMBED! STILL THIS IS
A GREAT PRODUCT. THANKS,GE BUMP


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 206942208 vsize: 206942208 resident: 43159552 share: 19611648 rss: 43159552 rss_rlim: 4294967295
CPU usage: start_time: 1202088751 rtime: 1101 utime: 990 stime: 111 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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 -1208141264 (LWP 3114)]
[New Thread -1373672560 (LWP 3192)]
[New Thread -1255867504 (LWP 3191)]
[New Thread -1321223280 (LWP 3190)]
[New Thread -1310733424 (LWP 3143)]
[New Thread -1266357360 (LWP 3140)]
[New Thread -1279263856 (LWP 3138)]
[New Thread -1289753712 (LWP 3137)]
[New Thread -1300243568 (LWP 3136)]
[New Thread -1255601264 (LWP 3123)]
[New Thread -1245111408 (LWP 3119)]
(no debugging symbols found)
0x00e7c402 in __kernel_vsyscall ()

Thread 2 (Thread -1373672560 (LWP 3192))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    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 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /lib/libgthread-2.0.so.0
  • #10 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #11 ??
  • #12 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #13 ??
  • #14 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #15 ??
  • #16 pthread_mutex_unlock
    from /lib/libpthread.so.0


----------- .xsession-errors ---------------------
Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second.
Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second.
Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second.
Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second.
(rhythmbox:3114): RhythmDB-WARNING **: trying to sync properties of non-editable file
(rhythmbox:3114): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:3114): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
sys:1: Warning: g_hash_table_destroy: assertion `hash_table != NULL' failed
sys:1: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 Jonathan Matthew 2008-02-04 10:22:33 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 434003 ***