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 499123 - crash in Rhythmbox Music Player: i cant play mp3 songs
crash in Rhythmbox Music Player: i cant play mp3 songs
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-23 08:40 UTC by arun.triangle
Modified: 2007-11-25 11:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description arun.triangle 2007-11-23 08:40:27 UTC
What were you doing when the application crashed?
i cant play mp3 songs


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: Clearlooks
Icon Theme: Fedora

Memory status: size: 116666368 vsize: 116666368 resident: 28917760 share: 16973824 rss: 28917760 rss_rlim: 4294967295
CPU usage: start_time: 1195809033 rtime: 326 utime: 296 stime: 30 cutime:2 cstime: 1 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 -1209050576 (LWP 3496)]
[New Thread -1231242352 (LWP 3695)]
[New Thread -1220752496 (LWP 3513)]
[New Thread -1244263536 (LWP 3509)]
(no debugging symbols found)
0x00322402 in __kernel_vsyscall ()

Thread 2 (Thread -1231242352 (LWP 3695))

  • #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 (6 sec old) ---------------------
    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'
(rhythmbox:3496): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:3496): 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...
warning: /usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex_ndl14.map saved as /usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex_ndl14.map.rpmsave
warning: /usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex_dl14.map saved as /usr/share/texmf-var/fonts/map/pdftex/updmap/pdftex_dl14.map.rpmsave
warning: /usr/share/texmf-var/fonts/map/dvipdfm/updmap/dvipdfm_ndl14.map saved as /usr/share/texmf-var/fonts/map/dvipdfm/updmap/dvipdfm_ndl14.map.rpmsave
warning: /usr/share/texmf-var/fonts/map/dvipdfm/updmap/dvipdfm_dl14.map saved as /usr/share/texmf-var/fonts/map/dvipdfm/updmap/dvipdfm_dl14.map.rpmsave
--------------------------------------------------
Comment 1 Susana 2007-11-25 11:45:41 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 ***