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 497484 - crash in Rhythmbox Music Player: Buona sera, sono un nuov...
crash in Rhythmbox Music Player: Buona sera, sono un nuov...
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-16 21:16 UTC by alessandro
Modified: 2007-11-18 14:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description alessandro 2007-11-16 21:16:00 UTC
What were you doing when the application crashed?
Buona sera, sono un nuovo utilizzatore di Linux e sto imparando ad usarlo. Ho provato ad ascoltare dei brani musicali ma il riproduttore mi dice che non ha i codec. Purtroppo non posso aggiornare il sistema in quando facendolo mi blocca il router (D-Link DSL-G624T) e non capisco come mai. Grazie per l'aiuto che posso ricevere.


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

Memory status: size: 109199360 vsize: 109199360 resident: 30801920 share: 17993728 rss: 30801920 rss_rlim: 4294967295
CPU usage: start_time: 1195247271 rtime: 482 utime: 439 stime: 43 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 -1208333776 (LWP 3715)]
[New Thread -1230840944 (LWP 3779)]
[New Thread -1220351088 (LWP 3730)]
[New Thread -1244177520 (LWP 3724)]
(no debugging symbols found)
0x00364402 in __kernel_vsyscall ()

Thread 2 (Thread -1230840944 (LWP 3779))

  • #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 ---------------------
Traceback (most recent call last):
  File "/usr/lib/rhythmbox/plugins/magnatune/MagnatuneSource.py", line 312, in __download_update_cb
    out.write(catalog.read("opt/magnatune/info/song_info.xml"))
  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'
(rhythmbox:3715): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:3715): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Dispositivo o risorsa occupata' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
--------------------------------------------------
Comment 1 André Klapper 2007-11-18 14:50:01 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 ***