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 497602 - crash in Rhythmbox Music Player: 放歌曲呗,放不出来~
crash in Rhythmbox Music Player: 放歌曲呗,放不出来~
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-11-17 09:52 UTC by 553046646
Modified: 2007-11-18 14:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description 553046646 2007-11-17 09:52:40 UTC
What were you doing when the application crashed?
放歌曲呗,放不出来~


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: 132734976 vsize: 132734976 resident: 31666176 share: 18116608 rss: 31666176 rss_rlim: 4294967295
CPU usage: start_time: 1195293248 rtime: 374 utime: 345 stime: 29 cutime:2 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 -1208284624 (LWP 3672)]
[New Thread -1278887024 (LWP 3702)]
[New Thread -1268057200 (LWP 3696)]
[New Thread -1242252400 (LWP 3694)]
[New Thread -1256363120 (LWP 3677)]
(no debugging symbols found)
0x00c56402 in __kernel_vsyscall ()

Thread 2 (Thread -1278887024 (LWP 3702))

  • #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 ---------------------
totem-video-thumbnailer couln't open file 'file:///media/JUST%20SO/%E6%96%B0%E5%BB%BA%E6%96%87%E4%BB%B6%E5%A4%B9/%E8%9D%B4%E8%9D%B6%E5%90%BB%E8%8A%B1%E5%B1%B1.rm'
Reason: You do not have a decoder installed to handle this file. You might need to install the necessary plugins..
sys:1: Warning: g_value_array_free: assertion `value_array != NULL' failed
** Message: don't know how to handle application/vnd.rn-realmedia
** 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
totem-video-thumbnailer couln't open file 'file:///root/Music/%E8%9D%B4%E8%9D%B6%E5%90%BB%E8%8A%B1%E5%B1%B1.rm'
Reason: The playback of this movie requires a Realmedia demuxer plugin which is not installed..
sys:1: Warning: g_value_array_free: assertion `value_array != NULL' failed
(rhythmbox:3672): 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...
--------------------------------------------------
Comment 1 André Klapper 2007-11-18 14:51:17 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 ***