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 466312 - crash in Rhythmbox Music Player: Just trying to use Rhyth...
crash in Rhythmbox Music Player: Just trying to use Rhyth...
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-13 17:44 UTC by robertdaleweir
Modified: 2007-08-23 10:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description robertdaleweir 2007-08-13 17:44:45 UTC
What were you doing when the application crashed?
Just trying to use Rhythmbox to play some Flac ripped songs.  It skipped on the songs as well as hung up.


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: 720515072 vsize: 720515072 resident: 54476800 share: 27762688 rss: 54476800 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187112486 rtime: 2314 utime: 2088 stime: 226 cutime:2 cstime: 2 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 46912584989456 (LWP 2947)]
[New Thread 1126189392 (LWP 3084)]
[New Thread 1115699536 (LWP 3083)]
[New Thread 1136679248 (LWP 3074)]
[New Thread 1105209680 (LWP 3058)]
[New Thread 1094719824 (LWP 2952)]
(no debugging symbols found)
0x00002aaaad796808 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

Thread 4 (Thread 1136679248 (LWP 3074))

  • #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 ---------------------
    parser.close()
  File "/usr/lib64/python2.5/site-packages/_xmlplus/sax/expatreader.py", line 226, in close
    self.feed("", isFinal = 1)
  File "/usr/lib64/python2.5/site-packages/_xmlplus/sax/expatreader.py", line 220, in feed
    self._err_handler.fatalError(exc)
  File "/usr/lib64/python2.5/site-packages/_xmlplus/sax/handler.py", line 38, in fatalError
    raise exception
xml.sax._exceptions.SAXParseException: <unknown>:1:0: no element found
(rhythmbox:2947): 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...
sys:1: Warning: g_hash_table_destroy: assertion `hash_table != NULL' failed
sys:1: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 palfrey 2007-08-23 10:25:55 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 ***