GNOME Bugzilla – Bug 488666
crash in Volume Control: I am listening and using...
Last modified: 2007-10-20 23:15:57 UTC
Version: 2.18.0 What were you doing when the application crashed? I am listening and using Kopete. 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: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 68534272 vsize: 68534272 resident: 15486976 share: 11083776 rss: 15486976 rss_rlim: 4294967295 CPU usage: start_time: 1192985270 rtime: 252 utime: 216 stime: 36 cutime:23 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-volume-control' (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 -1209026320 (LWP 9470)] (no debugging symbols found) 0x0073b402 in __kernel_vsyscall ()
+ Trace 171736
Thread 1 (Thread -1209026320 (LWP 9470))
----------- .xsession-errors --------------------- CLIENT: Task: Task::done() CLIENT: Task: emitting finished Transfer ACCEPTED by: StatusNotifierTask Transfer ACCEPTED by: StatusNotifierTask Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! CLIENT: Task: Task::done() CLIENT: Task: emitting finished Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Transfer ACCEPTED by: StatusNotifierTask CLIENT: Task: Task::done() CLIENT: Task: emitting finished Transfer ACCEPTED by: StatusNotifierTask CLIENT: Task: Task::done() CLIENT: Task: emitting finished --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 471133 ***