GNOME Bugzilla – Bug 579568
crash in Rhythmbox Music Player: Crashed while closing rh...
Last modified: 2009-04-20 03:05:40 UTC
Version: 0.12.0 What were you doing when the application crashed? Crashed while closing rhythmbox Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.24.3 2009-04-01 (Gentoo) BugBuddy Version: 2.24.2 System: Linux 2.6.26-gentoo-r1 #3 SMP Thu Nov 20 21:59:07 EST 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 744361984 vsize: 744361984 resident: 45203456 share: 25104384 rss: 45203456 rss_rlim: 18446744073709551615 CPU usage: start_time: 1240106218 rtime: 3158 utime: 2254 stime: 904 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' [Thread debugging using libthread_db enabled] [New Thread 0x7f580cc0c7a0 (LWP 8447)] [New Thread 0x424b4950 (LWP 29820)] [New Thread 0x40818950 (LWP 29819)] [New Thread 0x4109a950 (LWP 29818)] 0x00007f58085bdf0f in __libc_waitpid (pid=1272, stat_loc=0x7fff14d5fee0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
+ Trace 214623
Thread 1 (Thread 0x7f580cc0c7a0 (LWP 8447))
----------- .xsession-errors (11 sec old) --------------------- DONT change group for Karma contactgid 336a treegid 336a wait:0 inl:1 ** (gnomeicu:8444): DEBUG: Buffer does not hold 16, only had 0 DONT change group for NetHunter contactgid 336a treegid 336a wait:0 inl:1 ** (gnomeicu:8444): DEBUG: Buffer does not hold 16, only had 0 ** (gnomeicu:8444): DEBUG: Buffer does not hold 4, only had 2 DONT change group for Karma contactgid 336a treegid 336a wait:0 inl:1 ** (gnomeicu:8444): DEBUG: Buffer does not hold 16, only had 0 GThread-ERROR **: file gthread-posix.c: line 171 (g_mutex_free_posix_impl): error 'Device or resource busy' during 'pthread_mutex_destroy ((pthread_mutex_t *) mutex)' aborting... --------------------------------------------------
*** This bug has been marked as a duplicate of 576238 ***