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 442995 - crash in Rhythmbox Music Player: could be with due to net...
crash in Rhythmbox Music Player: could be with due to net...
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-06-01 18:16 UTC by sandeepbajaj
Modified: 2007-06-03 12:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description sandeepbajaj 2007-06-01 18:16:45 UTC
What were you doing when the application crashed?
could be with due to netlag issue , the player got hungged.


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: 132083712 vsize: 132083712 resident: 35414016 share: 19177472 rss: 35414016 rss_rlim: 4294967295
CPU usage: start_time: 1180721622 rtime: 714 utime: 661 stime: 53 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 -1208477136 (LWP 3807)]
[New Thread -1272497264 (LWP 3869)]
[New Thread -1262007408 (LWP 3851)]
[New Thread -1283380336 (LWP 3824)]
[New Thread -1225573488 (LWP 3815)]
[New Thread -1238594672 (LWP 3813)]
(no debugging symbols found)
0x0067f402 in __kernel_vsyscall ()

Thread 2 (Thread -1272497264 (LWP 3869))

  • #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 (11 sec old) ---------------------
Traceback (most recent call last):
  File "/usr/lib/rhythmbox/plugins/jamendo/JamendoSource.py", line 225, in __download_update_cb
    out.write(catalog.read())
  File "/usr/lib/python2.5/gzip.py", line 220, in read
    self._read(readsize)
  File "/usr/lib/python2.5/gzip.py", line 275, in _read
    self._read_eof()
  File "/usr/lib/python2.5/gzip.py", line 311, in _read_eof
    raise IOError, "CRC check failed"
IOError: CRC check failed
(rhythmbox:3807): 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 sandeepbajaj 2007-06-02 03:53:36 UTC
were listing to online radio, the one which are already on list & suddenly it got stucked.
Comment 2 Philip Withnall 2007-06-03 10:42:27 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 ***
Comment 3 sandeepbajaj 2007-06-03 12:59:15 UTC
thanks