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 445639 - crash in Rhythmbox Music Player: closing application
crash in Rhythmbox Music Player: closing 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-09 00:15 UTC by daniele
Modified: 2007-06-10 12:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description daniele 2007-06-09 00:15:44 UTC
What were you doing when the application crashed?
closing 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.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 659300352 vsize: 659300352 resident: 68681728 share: 20594688 rss: 68681728 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181348033 rtime: 905 utime: 852 stime: 53 cutime:3 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912514920112 (LWP 7491)]
[New Thread 1199884624 (LWP 7547)]
[New Thread 1178904912 (LWP 7542)]
[New Thread 1168415056 (LWP 7533)]
[New Thread 1115965776 (LWP 7506)]
[New Thread 1105209680 (LWP 7499)]
(no debugging symbols found)
0x0000003a9ee0c728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

Thread 2 (Thread 1199884624 (LWP 7547))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /lib64/libglib-2.0.so.0
  • #6 g_log
    from /lib64/libglib-2.0.so.0
  • #7 ??
    from /lib64/libgthread-2.0.so.0
  • #8 ??
    from /usr/lib64/libgnomevfs-2.so.0
  • #9 ??
    from /usr/lib64/libgnomevfs-2.so.0
  • #10 ??
    from /lib64/libglib-2.0.so.0
  • #11 ??
    from /lib64/libglib-2.0.so.0
  • #12 start_thread
    from /lib64/libpthread.so.0
  • #13 clone
    from /lib64/libc.so.6


----------- .xsession-errors ---------------------
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Adding file /home/creche/.aMuleAvviso del window manager: last_focus_time (230301038) is greater than comparison timestamp (230301028).  This most likely represents a buggy client sending inaccurate t
(rhythmbox:7491): Rhythmbox-WARNING **: Unable to start mDNS browsing: Il servizio MDNS non è in esecuzione
(rhythmbox:7491): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:7491): Rhythmbox-WARNING **: Unable to stop mDNS browsing: Il servizio MDNS non è in esecuzione
(rhythmbox:7491): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Dispositivo o risorsa occupata' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-10 12:01:17 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 ***