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 468863 - crash in Rhythmbox Music Player: closing Rhythmbox
crash in Rhythmbox Music Player: closing Rhythmbox
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-21 14:06 UTC by jasadell
Modified: 2007-08-23 08:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description jasadell 2007-08-21 14:06:45 UTC 
What were you doing when the application crashed?
closing Rhythmbox


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:10:34 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: 100294656 vsize: 100294656 resident: 35860480 share: 22650880 rss: 35860480 rss_rlim: 4294967295
CPU usage: start_time: 1187705084 rtime: 360 utime: 334 stime: 26 cutime:1 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 -1208264144 (LWP 19593)]
[New Thread -1273820272 (LWP 29562)]
[New Thread -1252840560 (LWP 29276)]
[New Thread -1231049840 (LWP 19669)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 156845

Thread 2 (Thread -1273820272 (LWP 29562))

  • #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 free
    from /lib/libc.so.6 


----------- .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:19593): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:19593): 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 Peter 2007-08-23 08:38:11 UTC 
By eye, the stack track looks very much like bug 465739 (also when closing RB).

Duplicate of 465739?
Comment 2 Jonathan Matthew 2007-08-23 08:54:16 UTC 
These are both actually duplicates of bug 434003.  The gthread error message in this bug is a sure indicator, and the general form of 465739 is good enough.

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 ***