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 510866 - crash in Rhythmbox Music Player: Distribution: Fedora rel...
crash in Rhythmbox Music Player: Distribution: Fedora rel...
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: 2008-01-20 18:32 UTC by cleberl
Modified: 2008-01-20 22:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description cleberl 2008-01-20 18:32:58 UTC
What were you doing when the application crashed?
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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 151842816 vsize: 151842816 resident: 39763968 share: 20271104 rss: 39763968 rss_rlim: 4294967295
CPU usage: start_time: 1200857187 rtime: 1905 utime: 1759 stime: 146 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 -1208624592 (LWP 4264)]
[New Thread -1329931376 (LWP 4569)]
[New Thread -1298461808 (LWP 4435)]
[New Thread -1340421232 (LWP 4300)]
[New Thread -1265927280 (LWP 4275)]
[New Thread -1244947568 (LWP 4270)]
(no debugging symbols found)
0x006b2402 in __kernel_vsyscall ()

Thread 2 (Thread -1329931376 (LWP 4569))

  • #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 ---------------------
(rhythmbox:4264): libgnomevfs-CRITICAL **: gnome_vfs_uri_ref: assertion `uri != NULL' failed
(rhythmbox:4264): libgnomevfs-CRITICAL **: gnome_vfs_get_file_info_uri_cancellable: assertion `uri != NULL' failed
(rhythmbox:4264): libgnomevfs-CRITICAL **: gnome_vfs_uri_unref: assertion `uri != NULL' failed
(rhythmbox:4264): libgnomevfs-CRITICAL **: gnome_vfs_uri_to_string: assertion `uri != NULL' failed
(rhythmbox:4264): libgnomevfs-CRITICAL **: gnome_vfs_uri_unref: assertion `uri != NULL' failed
(rhythmbox:4264): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Dispositivo ou recurso está ocupado' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
--------------------------------------------------
Comment 1 Jonathan Matthew 2008-01-20 22:44:12 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 ***