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 469761 - crash in Rhythmbox Music Player: playing one MP3 file.
crash in Rhythmbox Music Player: playing one MP3 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-08-24 00:15 UTC by lucie.sagittarius
Modified: 2007-08-27 12:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description lucie.sagittarius 2007-08-24 00:15:00 UTC
What were you doing when the application crashed?
playing one MP3 file.


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: 496025600 vsize: 496025600 resident: 45682688 share: 25714688 rss: 45682688 rss_rlim: 18446744073709551615
CPU usage: start_time: 1187914361 rtime: 144 utime: 126 stime: 18 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 46912584989456 (LWP 562)]
[New Thread 1115699536 (LWP 752)]
[New Thread 1105209680 (LWP 648)]
[New Thread 1084229968 (LWP 637)]
[New Thread 1094719824 (LWP 581)]
(no debugging symbols found)
0x00002aaaad796808 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

Thread 2 (Thread 1115699536 (LWP 752))

  • #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 (6 sec old) ---------------------
streaming task paused, reason not-linked (-1)
totem-video-thumbnailer couln't open file 'file:///media/windows/D/%E4%B8%96%E7%BA%AA%E6%98%AD%E9%98%B3.wmv'
Reason: You do not have a decoder installed to handle this file. You might need to install the necessary plugins..
(rhythmbox:562): libgnomevfs-CRITICAL **: gnome_vfs_close_cancellable: assertion `handle != NULL' failed
GThread-ERROR **: file gthread-posix.c: line 171 (): error '设备或资源忙' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)'
aborting...
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: Error: You do not have a decoder installed to handle this file. You might need to install the necessary plugins.
gstplaybasebin.c(2203): prepare_output (): /play
** Message: Missing plugin: gstreamer.net|0.10|totem|MPEG-1 Layer 3 (MP3) decoder|decoder-audio/mpeg, mpegversion=(int)1, layer=(int)3 (MPEG-1 Layer 3 (MP3) decoder)
** Message: Automatic missing codec installation not supported (helper script missing)
--------------------------------------------------
Comment 1 palfrey 2007-08-27 12:31:05 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 ***