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 453277 - 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-07-03 02:25 UTC by netolf
Modified: 2007-07-03 22:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description netolf 2007-07-03 02:25:27 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 09:29:36 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 732958720 vsize: 732958720 resident: 65470464 share: 21192704 rss: 65470464 rss_rlim: 18446744073709551615
CPU usage: start_time: 1183429131 rtime: 600 utime: 572 stime: 28 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912709388480 (LWP 4631)]
[New Thread 1084229968 (LWP 4860)]
[New Thread 1126455632 (LWP 4838)]
[New Thread 1168415056 (LWP 4728)]
[New Thread 1157925200 (LWP 4695)]
[New Thread 1094986064 (LWP 4640)]
[New Thread 1094719824 (LWP 4638)]
(no debugging symbols found)
0x00002aaab1893728 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0

Thread 2 (Thread 1084229968 (LWP 4860))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /lib64/libglib-2.0.so.0
  • #6 g_log
    from /lib64/libglib-2.0.so.0
  • #7 ??
    from /lib64/libgthread-2.0.so.0
  • #8 ??
    from /usr/lib64/libgnomevfs-2.so.0
  • #9 ??
    from /usr/lib64/libgnomevfs-2.so.0
  • #10 ??
    from /lib64/libglib-2.0.so.0
  • #11 ??
    from /lib64/libglib-2.0.so.0
  • #12 start_thread
    from /lib64/libpthread.so.0
  • #13 clone
    from /lib64/libc.so.6


----------- .xsession-errors ---------------------
(rhythmbox:4631): Rhythmbox-WARNING **: Unable to stop mDNS browsing: MDNS service is not running
libhal.c 3110 : LibHalContext *ctx is NULL
libhal.c 276 : LibHalContext *ctx is NULL
libhal.c 3278 : LibHalContext *ctx is NULL
libhal.c 3296 : LibHalContext *ctx is NULL
libhal.c 3222 : LibHalContext *ctx is NULL
** (rhythmbox:4631): WARNING **: hal_shutdown failed: (null)
(rhythmbox:4631): 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-07-03 22:08:32 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 ***