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 460651 - crash in Rhythmbox Music Player: quitting application
crash in Rhythmbox Music Player: quitting 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-07-26 16:41 UTC by pkocian
Modified: 2007-07-29 01:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description pkocian 2007-07-26 16:41:19 UTC
What were you doing when the application crashed?
quitting 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-27.fc7 #1 SMP Tue Jul 17 17:19:58 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: 689741824 vsize: 689741824 resident: 52944896 share: 27549696 rss: 52944896 rss_rlim: 18446744073709551615
CPU usage: start_time: 1185467869 rtime: 445 utime: 394 stime: 51 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912709351616 (LWP 7332)]
[New Thread 1126455632 (LWP 7398)]
[New Thread 1105209680 (LWP 7395)]
[New Thread 1115965776 (LWP 7387)]
[New Thread 1105475920 (LWP 7340)]
[New Thread 1094719824 (LWP 7336)]
(no debugging symbols found)
0x00002aaab1888808 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

Thread 2 (Thread 1126455632 (LWP 7398))

  • #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 ---------------------
JACK tmpdir identified as [/dev/shm]
Expression 'ValidateParameters( outputParameters, outputDeviceInfo, StreamMode_Out )' failed in 'src/hostapi/oss/pa_unix_oss.c', line: 1206
I/O warning : failed to load external entity "/home/jaro/.config/audacious/playlist.xspf"
Varovanie správcu okien:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3400003 (Audacious)
Varovanie správcu okien:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Varovanie správcu okien:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3400003 (Audacious)
Varovanie správcu okien:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Creating link /home/jaro/.kde/socket-chello085216192044.chello.sk.
Created link from "/home/jaro/.kde/socket-chello085216192044.chello.sk" to "/tmp/ksocket-jaro"
(rhythmbox:7332): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error 'Zariadenie alebo iný zdroj je používané' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-29 01:54:47 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 ***