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 463369 - 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-08-04 08:00 UTC by oliavelino
Modified: 2007-08-07 13:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description oliavelino 2007-08-04 08:00:24 UTC
What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.13.fc7xen #1 SMP Tue Jul 17 10:38:27 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: 162017280 vsize: 162017280 resident: 57995264 share: 28983296 rss: 57995264 rss_rlim: 4294967295
CPU usage: start_time: 1186214076 rtime: 1475 utime: 1326 stime: 149 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208781088 (LWP 4454)]
[New Thread -1403446384 (LWP 4582)]
[New Thread -1298547824 (LWP 4578)]
[New Thread -1319527536 (LWP 4557)]
[New Thread -1392956528 (LWP 4551)]
[New Thread -1266812016 (LWP 4466)]
[New Thread -1244623984 (LWP 4461)]
(no debugging symbols found)
0x00ce4402 in __kernel_vsyscall ()

Thread 3 (Thread -1298547824 (LWP 4578))

  • #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 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
    from /lib/libglib-2.0.so.0
  • #21 ??
  • #22 ??
    from /lib/libglib-2.0.so.0


----------- .xsession-errors (16 sec old) ---------------------
Watching directory /home/avelino/fedora-install-guide-en (total watches = 78)
Watching directory /home/avelino/fedora-install-guide-en/figs (total watches = 79)
Watching directory /home/avelino/fedora-install-guide-en/stylesheet-images (total watches = 80)
Watching directory /home/avelino/fedora-install-guide-en/figs/CVS (total watches = 81)
indexing #100 - /home/avelino/fedora-install-guide-en/figs/fboot-finish.png
flushing all words
Finished indexing. Waiting for new events...
(rhythmbox:4454): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:4454): 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...
** Message: don't know how to handle text/uri-list
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-08-07 13:12:49 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 ***