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 472727 - 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-09-02 04:06 UTC by chenyong881102
Modified: 2007-09-05 16:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description chenyong881102 2007-09-02 04:06:39 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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 181456896 vsize: 181456896 resident: 39387136 share: 21291008 rss: 39387136 rss_rlim: 4294967295
CPU usage: start_time: 1188705955 rtime: 301 utime: 283 stime: 18 cutime:5 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 -1209161168 (LWP 4501)]
[New Thread -1320805488 (LWP 4537)]
[New Thread -1332741232 (LWP 4529)]
[New Thread -1320273008 (LWP 4523)]
[New Thread -1309783152 (LWP 4521)]
[New Thread -1252459632 (LWP 4519)]
[New Thread -1266181232 (LWP 4517)]
[New Thread -1276671088 (LWP 4509)]
(no debugging symbols found)
0x0018d402 in __kernel_vsyscall ()

+ Trace 159751

Thread 2 (Thread -1320805488 (LWP 4537))

  • #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 free
    from /lib/libc.so.6 


----------- .xsession-errors ---------------------
    self._err_handler.fatalError(exc)
  File "/usr/lib/python2.5/site-packages/_xmlplus/sax/handler.py", line 38, in fatalError
    raise exception
xml.sax._exceptions.SAXParseException: <unknown>:1:0: no element found
(rhythmbox:4501): libnotify-CRITICAL **: notify_notification_update: assertion `summary != NULL && *summary != '\0'' failed
(rhythmbox:4501): libnotify-CRITICAL **: notify_notification_update: assertion `summary != NULL && *summary != '\0'' failed
(rhythmbox:4501): libnotify-CRITICAL **: notify_notification_update: assertion `summary != NULL && *summary != '\0'' failed
(rhythmbox:4501): 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 palfrey 2007-09-05 16:58: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 ***