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 440582 - crash in Rhythmbox Music Player: Playing a wav file
crash in Rhythmbox Music Player: Playing a wav file
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-05-22 22:31 UTC by ntmadden
Modified: 2007-05-22 22:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ntmadden 2007-05-22 22:31:57 UTC
What were you doing when the application crashed?
Playing a wav file


Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3175.fc7 #1 SMP Mon May 21 11:35:59 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: 128188416 vsize: 128188416 resident: 37134336 share: 20418560 rss: 37134336 rss_rlim: 4294967295
CPU usage: start_time: 1179872816 rtime: 741 utime: 690 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209054672 (LWP 4507)]
[New Thread -1310164080 (LWP 4635)]
[New Thread -1299674224 (LWP 4633)]
[New Thread -1278694512 (LWP 4548)]
[New Thread -1244681328 (LWP 4512)]
(no debugging symbols found)
0x001b5402 in __kernel_vsyscall ()

Thread 2 (Thread -1310164080 (LWP 4635))

  • #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 ---------------------
(evolution:3632): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3632): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3632): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:3632): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
** (nautilus:3093): WARNING **: destroyed file has call_when_ready pending
closing
CalDAV Eplugin starting up ...
(rhythmbox:4507): 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 Jonathan Matthew 2007-05-22 22:53: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 ***