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 485412 - crash in Rhythmbox Music Player: looking for music
crash in Rhythmbox Music Player: looking for music
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-10-10 14:34 UTC by lukakipic
Modified: 2007-10-11 16:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description lukakipic 2007-10-10 14:34:19 UTC 
What were you doing when the application crashed?
looking for music


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: 107962368 vsize: 107962368 resident: 29061120 share: 17403904 rss: 29061120 rss_rlim: 4294967295
CPU usage: start_time: 1192026400 rtime: 1312 utime: 1182 stime: 130 cutime:4 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 -1208497616 (LWP 2790)]
[New Thread -1317930096 (LWP 2932)]
[New Thread -1254990960 (LWP 2895)]
[New Thread -1244501104 (LWP 2798)]
(no debugging symbols found)
0x0072d402 in __kernel_vsyscall ()

+ Trace 169269

Thread 2 (Thread -1317930096 (LWP 2932))

  • #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 (10 sec old) ---------------------
localuser:luka being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2392
Failed to connect to socket /tmp/fam-luka-
(gnome-panel:2505): Gtk-WARNING **: Failed to connect to the FAM server
(gnome-panel:2505): Gtk-WARNING **: Not adding file monitor on '/home/luka/.recently-used.xbel', failed to connect to FAM server
error getting update info:  Cannot open/read repomd.xml file for repository: fedora
(rhythmbox:2790): 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 Susana 2007-10-11 16:53:45 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 ***