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 498441 - crash in Rhythmbox Music Player: copy files
crash in Rhythmbox Music Player: copy files
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-11-20 10:20 UTC by jinglingabc123
Modified: 2007-11-25 11:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jinglingabc123 2007-11-20 10:20:47 UTC
What were you doing when the application crashed?
copy files 


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 08:53:03 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: 156246016 vsize: 156246016 resident: 38150144 share: 21192704 rss: 38150144 rss_rlim: 4294967295
CPU usage: start_time: 1195553654 rtime: 235 utime: 215 stime: 20 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 -1208731936 (LWP 3790)]
[New Thread -1272468592 (LWP 3985)]
[New Thread -1369441392 (LWP 3900)]
[New Thread -1315578992 (LWP 3805)]
[New Thread -1283376240 (LWP 3804)]
[New Thread -1261585520 (LWP 3795)]
(no debugging symbols found)
0x0097a402 in __kernel_vsyscall ()

Thread 2 (Thread -1272468592 (LWP 3985))

  • #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 ---------------------
    return self.NameToInfo[name]
KeyError: 'opt/magnatune/info/song_info.xml'
窗口管理器警告:last_focus_time (1552893728) is greater than comparison timestamp (1552893725).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _N
closing
closing
closing
** Message: don't know how to handle text/uri-list
** Message: Hit unexpected error "I/O 错误" while doing a file operation.
(rhythmbox:3790): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:3790): 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 Susana 2007-11-25 11:38:46 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 434003 ***