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 495520 - 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-10 09:30 UTC by szjbxy19861119
Modified: 2007-11-10 13:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description szjbxy19861119 2007-11-10 09:30:23 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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 165097472 vsize: 165097472 resident: 35864576 share: 19021824 rss: 35864576 rss_rlim: 4294967295
CPU usage: start_time: 1194686080 rtime: 1066 utime: 962 stime: 104 cutime:1 cstime: 2 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209014560 (LWP 3844)]
[New Thread -1312396400 (LWP 4206)]
[New Thread -1290998896 (LWP 4196)]
[New Thread -1248117872 (LWP 3898)]
[New Thread -1343865968 (LWP 3887)]
[New Thread -1269994608 (LWP 3853)]
(no debugging symbols found)
0x00555402 in __kernel_vsyscall ()

Thread 2 (Thread -1312396400 (LWP 4206))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/nosegneg/libc.so.6
  • #6 abort
    from /lib/i686/nosegneg/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 (8 sec old) ---------------------
the application.
Unknown message: No such IMContext
Unknown message: An invalid char is given at scim_bridge_string_to_uint (): -
Unknown message: Invalid message: Close the connection.
Failed to receive messages at scim_bridge_client_read_and_dispatch ()
An IOException at scim_bridge_client_handle_key_event ()
An IOException at filter_key_event ()
An IOException occurred at scim_bridge_client_imcontext_filter_key_event ()
(rhythmbox:3844): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:3844): 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 Jonathan Matthew 2007-11-10 13:58:54 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 ***