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 461511 - crash in Rhythmbox Music Player: i closed the program.
crash in Rhythmbox Music Player: i closed the program.
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-07-29 15:55 UTC by focus_water
Modified: 2007-08-02 10:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description focus_water 2007-07-29 15:55:31 UTC 
What were you doing when the application crashed?
i closed the program. 


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: Salocin
Icon Theme: glass-icons

Memory status: size: 135176192 vsize: 135176192 resident: 34058240 share: 19042304 rss: 34058240 rss_rlim: 4294967295
CPU usage: start_time: 1185724343 rtime: 874 utime: 814 stime: 60 cutime:2 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 -1209013712 (LWP 19956)]
[New Thread -1268388976 (LWP 20018)]
[New Thread -1289634928 (LWP 20006)]
[New Thread -1268122736 (LWP 19984)]
[New Thread -1220568176 (LWP 19980)]
[New Thread -1244079216 (LWP 19963)]
(no debugging symbols found)
0x00635402 in __kernel_vsyscall ()

+ Trace 151382

Thread 2 (Thread -1268388976 (LWP 20018))

  • #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) ---------------------
(gnome-theme-manager:3651): capplet-common-WARNING **: Could not open file "(null)"
(gnome-theme-manager:3651): capplet-common-WARNING **: Could not open file "(null)"
(gnome-theme-manager:3651): capplet-common-WARNING **: Could not open file "(null)"
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x64 specified for 0x120af09 ().
compiz: No GLXFBConfig for default depth, this isn't going to work.
compiz: Failed to manage screen: 0
compiz: No manageable screens found on display :0.0
** Message: Found best visual for GL: 0x24
(rhythmbox:19956): 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-08-02 10:10:13 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 ***