GNOME Bugzilla – Bug 582990
crash in Rhythmbox Music Player: I've closed the applicat...
Last modified: 2009-05-24 07:52:12 UTC
Version: 0.11.6 What were you doing when the application crashed? I've closed the application. Distribution: Fedora release 10 (Cambridge) Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc) BugBuddy Version: 2.24.2 System: Linux 2.6.27.21-170.2.56.fc10.x86_64 #1 SMP Mon Mar 23 23:08:10 EDT 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 860884992 vsize: 860884992 resident: 90808320 share: 25640960 rss: 90808320 rss_rlim: 18446744073709551615 CPU usage: start_time: 1242578811 rtime: 76125 utime: 65119 stime: 11006 cutime:55 cstime: 22 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' [Thread debugging using libthread_db enabled] [New Thread 0x7f99820ea810 (LWP 9608)] [New Thread 0x7f996c72a950 (LWP 9659)] 0x0000003057c0ec2f in waitpid () from /lib64/libpthread.so.0
+ Trace 215542
Thread 1 (Thread 0x7f99820ea810 (LWP 9608))
----------- .xsession-errors (16 sec old) --------------------- at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:336) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:186) at net.sf.jabref.JabRef.openWindow(JabRef.java:556) at net.sf.jabref.JabRef.<init>(JabRef.java:159) at net.sf.jabref.JabRef.main(JabRef.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at net.sf.jabref.JabRefMain.main(Unknown Source) Öffne: ****literature.bib GThread-ERROR **: file gthread-posix.c: line 171 (g_mutex_free_posix_impl): error 'Das Gerät oder die Ressource ist belegt' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)' aborting... --------------------------------------------------
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 576238 ***