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 465582 - crash in Rhythmbox Music Player: try to play mp3 file
crash in Rhythmbox Music Player: try to play 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-11 03:35 UTC by jigishpthakar
Modified: 2007-08-27 12:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jigishpthakar 2007-08-11 03:35:14 UTC
What were you doing when the application crashed?
try to play mp3 file



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

Memory status: size: 118521856 vsize: 118521856 resident: 29130752 share: 17268736 rss: 29130752 rss_rlim: 4294967295
CPU usage: start_time: 1186697126 rtime: 692 utime: 620 stime: 72 cutime:5 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 -1208108496 (LWP 3391)]
[New Thread -1256195184 (LWP 3432)]
[New Thread -1232647280 (LWP 3431)]
[New Thread -1219626096 (LWP 3430)]
[New Thread -1275417712 (LWP 3429)]
[New Thread -1243948144 (LWP 3399)]
(no debugging symbols found)
0x0067c402 in __kernel_vsyscall ()

Thread 3 (Thread -1232647280 (LWP 3431))

  • #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 (28 sec old) ---------------------
closing
closing
closing
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x45 specified for 0xe029bb ().
** Message: don't know how to handle audio/x-m4a
** Message: Error: You do not have a decoder installed to handle this file. You might need to install the necessary plugins.
gstplaybasebin.c(2182): prepare_output (): /play
** Message: Missing plugin: gstreamer.net|0.10|totem|MPEG-4 AAC demuxer|decoder-audio/x-m4a (MPEG-4 AAC demuxer)
** Message: Automatic missing codec installation not supported (helper script missing)
Failed to load file:///mnt/dhaval/torrents/New%20Faww/300%20Soundtrack%20-%20Returns%20a%20King.mp3: Did not receive a reply. Possible causes include: the remote application did not send a reply, the 
(rhythmbox:3391): 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 palfrey 2007-08-27 12:36:41 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 ***