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 444647 - crash in Rhythmbox Music Player: nothing, just open it
crash in Rhythmbox Music Player: nothing, just open 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-06 09:16 UTC by swordcenter
Modified: 2007-06-06 10:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description swordcenter 2007-06-06 09:16:53 UTC
What were you doing when the application crashed?
nothing, just open 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.20-2925.9.fc7xen #1 SMP Tue May 22 09:29:36 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: 640905216 vsize: 640905216 resident: 65671168 share: 22298624 rss: 65671168 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181121245 rtime: 757 utime: 691 stime: 66 cutime:0 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 46912709310656 (LWP 10605)]
[New Thread 1094719824 (LWP 10743)]
[New Thread 1084229968 (LWP 10677)]
[New Thread 1105209680 (LWP 10620)]
(no debugging symbols found)
0x00002aaab1880728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

Thread 2 (Thread 1094719824 (LWP 10743))

  • #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 (12 sec old) ---------------------
--- Hash table keys for warning below:
--> file:///root
(nautilus:8468): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
libvir: Xen Daemon 错误 : GET操作失败: 
libvir: 错误 : 配置文件语法错误: 需要一个名称
libvir: 错误 : 配置文件语法错误: 需要一个名称
libvir: 错误 : 配置文件语法错误: 需要一个名称
(rhythmbox:10605): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:10605): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error '设备或资源忙' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-06 10:39:51 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 ***