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 444074 - crash in Rhythmbox Music Player:
crash in Rhythmbox Music Player:
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-06-04 19:42 UTC by romanczer
Modified: 2007-06-04 22:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description romanczer 2007-06-04 19:42:32 UTC
What were you doing when the application crashed?



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: OSX-theme
Icon Theme: jaguarx_twirly

Memory status: size: 223932416 vsize: 223932416 resident: 51191808 share: 17924096 rss: 51191808 rss_rlim: 4294967295
CPU usage: start_time: 1180986076 rtime: 1473 utime: 1416 stime: 57 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 -1208489424 (LWP 19175)]
[New Thread -1362535536 (LWP 19203)]
[New Thread -1352045680 (LWP 19202)]
[New Thread -1341555824 (LWP 19201)]
[New Thread -1331065968 (LWP 19200)]
[New Thread -1320576112 (LWP 19199)]
[New Thread -1310086256 (LWP 19198)]
[New Thread -1299596400 (LWP 19197)]
[New Thread -1289106544 (LWP 19196)]
[New Thread -1278616688 (LWP 19195)]
[New Thread -1255265392 (LWP 19192)]
[New Thread -1244439664 (LWP 19185)]
[New Thread -1230374000 (LWP 19182)]
(no debugging symbols found)
0x005d3402 in __kernel_vsyscall ()

Thread 5 (Thread -1331065968 (LWP 19200))

  • #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 ??


----------- .xsession-errors (6 sec old) ---------------------
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
(rhythmbox:19175): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:19175): 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...
(bug-buddy:19205): Gtk-WARNING **: Theme file for jaguarx_twirly has no directories
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-04 22:28:00 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 ***