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 444120 - crash in Rhythmbox Music Player: closing it
crash in Rhythmbox Music Player: closing it
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-04 21:25 UTC by aj5034
Modified: 2007-06-04 22:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description aj5034 2007-06-04 21:25:28 UTC 
What were you doing when the application crashed?
closing it


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 470450176 vsize: 470450176 resident: 33955840 share: 16875520 rss: 33955840 rss_rlim: 18446744073709551615
CPU usage: start_time: 1180992227 rtime: 314 utime: 275 stime: 39 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496376384 (LWP 6219)]
[New Thread 1136679248 (LWP 6260)]
[New Thread 1094719824 (LWP 6229)]
[New Thread 1115699536 (LWP 6227)]
(no debugging symbols found)
0x00000033b6c0c728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

+ Trace 138268

Thread 2 (Thread 1136679248 (LWP 6260))

  • #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 ---------------------
Loading "installonlyn" plugin
Loading "installonlyn" plugin
_gtk_text_util_create_rich_drag_icon: layout size 72 17
_gtk_text_util_create_rich_drag_icon: pixmap size 82 27
_gtk_text_util_create_rich_drag_icon: layout size 96 17
_gtk_text_util_create_rich_drag_icon: pixmap size 106 27
_gtk_text_util_create_rich_drag_icon: layout size 392 17
_gtk_text_util_create_rich_drag_icon: pixmap size 260 27
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2000003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(rhythmbox:6219): 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-04 22:30:03 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 ***