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 582990 - crash in Rhythmbox Music Player: I've closed the applicat...
crash in Rhythmbox Music Player: I've closed the applicat...
Status: RESOLVED DUPLICATE of bug 576238
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-17 21:50 UTC by jan.teichmann
Modified: 2009-05-24 07:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description jan.teichmann 2009-05-17 21:50:47 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

Thread 1 (Thread 0x7f99820ea810 (LWP 9608))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_spawn_sync
    from /lib64/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /lib64/libglib-2.0.so.0
  • #3 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 raise
    from /lib64/libc.so.6
  • #7 abort
    from /lib64/libc.so.6
  • #8 g_logv
    from /lib64/libglib-2.0.so.0
  • #9 g_log
    from /lib64/libglib-2.0.so.0
  • #10 pthread_attr_setdetachstate
    from /lib64/libgthread-2.0.so.0
  • #11 rhythmdb_finalize
    at rhythmdb.c line 945
  • #12 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #13 rb_shell_finalize
    at rb-shell.c line 957
  • #14 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib64/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #16 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #17 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #18 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #19 ??
    from /usr/lib64/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #20 g_closure_invalidate
    from /lib64/libgobject-2.0.so.0
  • #21 g_closure_unref
    from /lib64/libgobject-2.0.so.0
  • #22 g_signal_handlers_destroy
    from /lib64/libgobject-2.0.so.0
  • #23 ??
    from /lib64/libgobject-2.0.so.0
  • #24 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #25 g_datalist_clear
    from /lib64/libglib-2.0.so.0
  • #26 g_object_unref
    from /lib64/libgobject-2.0.so.0
  • #27 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #28 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #29 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #31 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #32 ??
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #33 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #34 ??
    from /lib64/libglib-2.0.so.0
  • #35 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #36 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #37 main
    at main.c line 330


----------- .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...
--------------------------------------------------
Comment 1 Jonathan Matthew 2009-05-24 07:52:12 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 576238 ***