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 483863 - crash in Rhythmbox Music Player: look at music players se...
crash in Rhythmbox Music Player: look at music players se...
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-10-05 20:00 UTC by andresch
Modified: 2007-10-05 23:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description andresch 2007-10-05 20:00:35 UTC 
What were you doing when the application crashed?
look at music players settings to see why the sound is not heard, but device test works


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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 120627200 vsize: 120627200 resident: 30887936 share: 17965056 rss: 30887936 rss_rlim: 4294967295
CPU usage: start_time: 1191614298 rtime: 315 utime: 287 stime: 28 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 -1208120784 (LWP 3497)]
[New Thread -1263760496 (LWP 3522)]
[New Thread -1217889392 (LWP 3508)]
[New Thread -1228379248 (LWP 3506)]
[New Thread -1241400432 (LWP 3505)]
(no debugging symbols found)
0x00561402 in __kernel_vsyscall ()

+ Trace 168097

Thread 2 (Thread -1263760496 (LWP 3522))

  • #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 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
    from /lib/libglib-2.0.so.0
  • #21 ??
  • #22 ??
    from /lib/libglib-2.0.so.0 


----------- .xsession-errors ---------------------
Package xml-commons-apis - 1.3.03-0jpp.1.fc7.i386 already installed and latest version
Package jakarta-commons-modeler - 2.0-3jpp.1.fc7.i386 already installed and latest version
Package classpathx-mail - 1.1.1-4jpp.3.i386 already installed and latest version
Package jakarta-commons-validator - 1.1.4-5jpp.1.i386 already installed and latest version
Package ldapjdk - 4.17-1jpp.7.i386 already installed and latest version
Package xerces-j2 - 2.7.1-7jpp.2.i386 already installed and latest version
Package java_cup - 1:0.10-0.k.6jpp.1.i386 already installed and latest version
Package log4j - 1.2.13-3jpp.2.i386 already installed and latest version
Package xalan-j2 - 2.7.0-6jpp.1.i386 already installed and latest version
Package classpathx-jaf - 1.0-9jpp.1.i386 already installed and latest version
(rhythmbox:3497): 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 Jonathan Matthew 2007-10-05 23:57:18 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 ***