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 468889 - crash in Rhythmbox Music Player: exiting application
crash in Rhythmbox Music Player: exiting application
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: 2007-08-21 15:26 UTC by Ken
Modified: 2007-08-23 10:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Ken 2007-08-21 15:26:11 UTC 
What were you doing when the application crashed?
exiting application


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 158720000 vsize: 158720000 resident: 58433536 share: 41504768 rss: 58433536 rss_rlim: 4294967295
CPU usage: start_time: 1187709589 rtime: 4725 utime: 4411 stime: 314 cutime:11 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 -1208927696 (LWP 7088)]
[New Thread -1365247088 (LWP 7157)]
[New Thread -1321210992 (LWP 7154)]
[New Thread -1308673136 (LWP 7101)]
[New Thread -1286218864 (LWP 7096)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 156866

Thread 2 (Thread -1365247088 (LWP 7157))

  • #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 free
    from /lib/libc.so.6 


----------- .xsession-errors (21 sec old) ---------------------
Checking for MMC style command set...
	Drive is MMC style
Error reading command:  
	43 00 00 00 00 00 01 00  0c 00 
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x63 specified for 0x3c006be (Warning - ).
OggS-SEEK: at 0 want 60408 got 51136 (diff-requested 60408)
OggS-SEEK: at 60352 want 520 got 0 (diff-requested -59832)
KCrash: Application 'kaffeine' crashing...
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x63 specified for 0x3c00007 (Kaffeine P).
(rhythmbox:7088): 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...
--------------------------------------------------
Comment 1 palfrey 2007-08-23 10:40:20 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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