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 463280 - crash in Rhythmbox Music Player: I am a new user, all I d...
crash in Rhythmbox Music Player: I am a new user, all I d...
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-08-03 22:37 UTC by boggin4fun
Modified: 2007-08-07 13:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description boggin4fun 2007-08-03 22:37:21 UTC 
What were you doing when the application crashed?
I am a new user, all I did was open it to see the interface and then click the "x" in the upper right corner.  As of August 3, my system is entirely up to date.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 119754752 vsize: 119754752 resident: 41390080 share: 24076288 rss: 41390080 rss_rlim: 4294967295
CPU usage: start_time: 1186180585 rtime: 442 utime: 412 stime: 30 cutime:1 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 -1209189840 (LWP 13854)]
[New Thread -1226880112 (LWP 13862)]
[New Thread -1251988592 (LWP 13861)]
[New Thread -1240347760 (LWP 13859)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 152660

Thread 3 (Thread -1251988592 (LWP 13861))

  • #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 ?? 


----------- .xsession-errors ---------------------
Loading "installonlyn" plugin
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x64 specified for 0x220009c ().
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x64 specified for 0x100054b ().
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
(evolution:12670): e-data-server-DEBUG: Loaded default categories
(evolution:12670): e-data-server-DEBUG: Saving categories to "/home/brutus/.evolution/categories.xml"
Loading "installonlyn" plugin
(rhythmbox:13854): libgnomevfs-WARNING **: trying to read a non-existing handle
(rhythmbox:13854): 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-08-07 13:07:33 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 ***