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 452791 - 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-07-01 10:27 UTC by vivekananda_1985_p
Modified: 2007-07-01 22:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description vivekananda_1985_p 2007-07-01 10:27:21 UTC
What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 102248448 vsize: 102248448 resident: 35524608 share: 24076288 rss: 35524608 rss_rlim: 4294967295
CPU usage: start_time: 1183285569 rtime: 311 utime: 284 stime: 27 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 -1208776144 (LWP 2979)]
[New Thread -1251132528 (LWP 2990)]
[New Thread -1236878448 (LWP 2988)]
[New Thread -1226388592 (LWP 2985)]
(no debugging symbols found)
0x00307402 in __kernel_vsyscall ()

Thread 2 (Thread -1251132528 (LWP 2990))

  • #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 ---------------------
Window manager warning: last_focus_time (2188594962) is greater than comparison timestamp (2168818246).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _N
Window manager warning: last_user_time (2188590242) is greater than comparison timestamp (2168818246).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x3c01bf6 (Resolving ) appears to be one of the offending windows with a timestamp of 2188509409.  Working around...
Window manager warning: 0xa00003 (Top Panel) appears to be one of the offending windows with a timestamp of 2188590201.  Working around...
Window manager warning: 0xa00035 (Bottom Pan) appears to be one of the offending windows with a timestamp of 4733178.  Working around...
Window manager warning: 0x120001f (Desktop) appears to be one of the offending windows with a timestamp of 2188586002.  Working around...
Window manager warning: 0x3c0000c (Package Up) appears to be one of the offending windows with a timestamp of 2188510941.  Working around...
Window manager warning: 0x320007e (Mozilla Fi) appears to be one of the offending windows with a timestamp of 2188590242.  Working around...
Window manager warning: last_user_time (2188506813) is greater than comparison timestamp (2169202972).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x3c03fb6 (Dependenci) appears to be one of the offending windows with a timestamp of 2188506813.  Working around...
(rhythmbox:2979): 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-07-01 22:30: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 ***