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 468143 - crash in Rhythmbox Music Player: Shut down application
crash in Rhythmbox Music Player: Shut down application
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-08-19 09:11 UTC by maboitemailaspam
Modified: 2007-08-20 08:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description maboitemailaspam 2007-08-19 09:11:06 UTC
What were you doing when the application crashed?
Shut down application


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 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: 700649472 vsize: 700649472 resident: 57139200 share: 30937088 rss: 57139200 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187511986 rtime: 939 utime: 868 stime: 71 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 46912496351184 (LWP 7247)]
[New Thread 1084229968 (LWP 7838)]
[New Thread 1168415056 (LWP 7828)]
[New Thread 1105475920 (LWP 7317)]
[New Thread 1094719824 (LWP 7251)]
(no debugging symbols found)
0x00000031f1e0c808 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

Thread 2 (Thread 1084229968 (LWP 7838))

  • #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 ---------------------
Traceback (most recent call last):
  File "/usr/lib64/rhythmbox/plugins/magnatune/MagnatuneSource.py", line 312, in __download_update_cb
    out.write(catalog.read("opt/magnatune/info/song_info.xml"))
  File "/usr/lib64/python2.5/zipfile.py", line 471, in read
    zinfo = self.getinfo(name)
  File "/usr/lib64/python2.5/zipfile.py", line 462, in getinfo
    return self.NameToInfo[name]
KeyError: 'opt/magnatune/info/song_info.xml'
(rhythmbox:7247): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:7247): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Périphérique ou ressource occupé' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-08-20 08:54:53 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 ***