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 495851 - crash in Rhythmbox Music Player: just testing it out for ...
crash in Rhythmbox Music Player: just testing it out for ...
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-11-11 12:32 UTC by cloud93704
Modified: 2007-11-15 09:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description cloud93704 2007-11-11 12:32:31 UTC 
What were you doing when the application crashed?
just testing it out for the first time


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: 107745280 vsize: 107745280 resident: 26783744 share: 15499264 rss: 26783744 rss_rlim: 4294967295
CPU usage: start_time: 1194784165 rtime: 870 utime: 768 stime: 102 cutime:7 cstime: 2 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 -1208829392 (LWP 8310)]
[New Thread -1256764528 (LWP 8329)]
[New Thread -1246045296 (LWP 8326)]
[New Thread -1220240496 (LWP 8322)]
[New Thread -1233261680 (LWP 8321)]
(no debugging symbols found)
0x00b28402 in __kernel_vsyscall ()

+ Trace 176987

Thread 2 (Thread -1256764528 (LWP 8329))

  • #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 (77 sec old) ---------------------
auditd (pid 1392) is running...
auditd
auditd (pid 1392) is running...
bluetooth
hcid (pid 1561) is running...
sdpd (pid 1571) is running...
bluetooth
hcid (pid 1561) is running...
sdpd (pid 1571) is running...
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x3800021 (Music Play); these messages lack timestamps and therefore suck.
(rhythmbox:8310): 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-11-15 09:27:08 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 ***