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 444778 - crash in Rhythmbox Music Player: closing the application
crash in Rhythmbox Music Player: closing the application
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-06 16:24 UTC by paulo.chavez
Modified: 2007-06-06 22:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description paulo.chavez 2007-06-06 16:24:23 UTC
What were you doing when the application crashed?
closing the application


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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 124334080 vsize: 124334080 resident: 27746304 share: 16162816 rss: 27746304 rss_rlim: 4294967295
CPU usage: start_time: 1181147281 rtime: 262 utime: 234 stime: 28 cutime:0 cstime: 1 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208637728 (LWP 3440)]
[New Thread -1239164016 (LWP 3492)]
[New Thread -1270633584 (LWP 3491)]
[New Thread -1291613296 (LWP 3489)]
[New Thread -1281123440 (LWP 3485)]
[New Thread -1249653872 (LWP 3447)]
(no debugging symbols found)
0x00a8b402 in __kernel_vsyscall ()

Thread 3 (Thread -1270633584 (LWP 3491))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/nosegneg/libc.so.6
  • #6 abort
    from /lib/i686/nosegneg/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/i686/nosegneg/libc.so.6


----------- .xsession-errors (12 sec old) ---------------------
(K3bDevice::Device) /dev/scd0: Device reports bogus disc information length of 24
(K3bDevice::Device) /dev/scd0:  Number of supported write speeds via GET PERFORMANCE: 1
(K3bDevice::Device) /dev/scd0 : 11080 KB/s
ScimInputContextPlugin()
~ScimInputContextPlugin()
ScimInputContextPlugin()
(K3bDevice::DeviceManager) request for empty device!
Launched ok, pid = 3364
~ScimInputContextPlugin()
ICE default IO error handler doing an exit(), pid = 3361, errno = 0
(rhythmbox:3440): 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-06-06 22:31:33 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 ***