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 444877 - 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-06-06 20:28 UTC by catalin.porosnicu
Modified: 2007-06-06 22:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description catalin.porosnicu 2007-06-06 20:28:59 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: 140750848 vsize: 140750848 resident: 49569792 share: 19259392 rss: 49569792 rss_rlim: 4294967295
CPU usage: start_time: 1181161605 rtime: 1404 utime: 1342 stime: 62 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 -1208399312 (LWP 4709)]
[New Thread -1288516720 (LWP 4743)]
[New Thread -1345328240 (LWP 4737)]
[New Thread -1319986288 (LWP 4729)]
[New Thread -1235121264 (LWP 4714)]
(no debugging symbols found)
0x003b5402 in __kernel_vsyscall ()

Thread 2 (Thread -1288516720 (LWP 4743))

  • #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 ---------------------
** (evolution:4625): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:4625): DEBUG: mailto URL program: evolution
(evolution:4625): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4625): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(rhythmbox:4709): Rhythmbox-WARNING **: Unable to start mDNS browsing: MDNS service is not running
(rhythmbox:4709): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:4709): Rhythmbox-WARNING **: Unable to stop mDNS browsing: MDNS service is not running
(rhythmbox:4709): 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 Jonathan Matthew 2007-06-06 22:45:43 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 ***