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 491792 - crash in Rhythmbox Music Player: extracting Java Runtime ...
crash in Rhythmbox Music Player: extracting Java Runtime ...
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-10-30 17:10 UTC by e_gono
Modified: 2007-10-31 22:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description e_gono 2007-10-30 17:10:56 UTC
What were you doing when the application crashed?
extracting Java Runtime Environment


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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 134287360 vsize: 134287360 resident: 35168256 share: 19042304 rss: 35168256 rss_rlim: 4294967295
CPU usage: start_time: 1193763480 rtime: 3538 utime: 3254 stime: 284 cutime:4 cstime: 1 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 -1208206800 (LWP 4869)]
[New Thread -1296483440 (LWP 5503)]
[New Thread -1265013872 (LWP 5175)]
[New Thread -1243767920 (LWP 5055)]
[New Thread -1228465264 (LWP 4929)]
[New Thread -1254257776 (LWP 4880)]
[New Thread -1217975408 (LWP 4877)]
(no debugging symbols found)
0x00b25402 in __kernel_vsyscall ()

Thread 2 (Thread -1296483440 (LWP 5503))

  • #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 (6 sec old) ---------------------
(rhythmbox:4869): GStreamer-CRITICAL **: pad selector_audio_src0:src returned NULL caps from getcaps function
** (rhythmbox:4869): WARNING **: could not link EMPTY: -1
(rhythmbox:4869): GStreamer-WARNING **: Element preroll_audio_src0 is not in bin playbin
(rhythmbox:4869): GStreamer-WARNING **: Element selector_audio_src0 is not in bin playbin
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
(rhythmbox:4869): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:4869): 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 Jonathan Matthew 2007-10-31 22:28:03 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 ***