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 497734 - crash in Rhythmbox Music Player: playing song
crash in Rhythmbox Music Player: playing song
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-17 19:58 UTC by abhishek221196
Modified: 2007-11-18 14:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description abhishek221196 2007-11-17 19:58:13 UTC
What were you doing when the application crashed?
playing song


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:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 136749056 vsize: 136749056 resident: 35221504 share: 19914752 rss: 35221504 rss_rlim: 4294967295
CPU usage: start_time: 1195286048 rtime: 662 utime: 535 stime: 127 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208157648 (LWP 2977)]
[New Thread -1329894512 (LWP 3024)]
[New Thread -1287668848 (LWP 3002)]
[New Thread -1329628272 (LWP 2996)]
[New Thread -1219789936 (LWP 2985)]
[New Thread -1232811120 (LWP 2981)]
(no debugging symbols found)
0x00cd8402 in __kernel_vsyscall ()

Thread 2 (Thread -1329894512 (LWP 3024))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/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 ---------------------
  File "/usr/lib/python2.5/zipfile.py", line 471, in read
    zinfo = self.getinfo(name)
  File "/usr/lib/python2.5/zipfile.py", line 462, in getinfo
    return self.NameToInfo[name]
KeyError: 'opt/magnatune/info/song_info.xml'
** Message: Failed to load /media/200711171941/kabhi alvida naa kehna/AlbumArt_{5B7D3C02-2B1B-4B74-96FD-35EF844FA978}_Small.jpg into memory: Failed to read from file '/media/200711171941/kabhi alvida 
** Message: Failed to load /media/200711171941/kabhi alvida naa kehna/AlbumArt_{5B7D3C02-2B1B-4B74-96FD-35EF844FA978}_Small.jpg into memory: Failed to read from file '/media/200711171941/kabhi alvida 
** Message: Failed to load /media/200711171941/kabhi alvida naa kehna/AlbumArt_{5B7D3C02-2B1B-4B74-96FD-35EF844FA978}_Small.jpg into memory: Failed to read from file '/media/200711171941/kabhi alvida 
(rhythmbox:2977): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:2977): 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 André Klapper 2007-11-18 14:51:08 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 ***