GNOME Bugzilla – Bug 435579
crash in IP Telephony, VoIP and Video Conferencing:
Last modified: 2007-05-03 17:58:43 UTC
Version: 2.0.5 What were you doing when the application crashed? Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.20-1.2948.fc6 #1 SMP Fri Apr 27 19:18:54 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Enabled Memory status: size: 510926848 vsize: 510926848 resident: 21606400 share: 14204928 rss: 21606400 rss_rlim: -1 CPU usage: start_time: 1178214653 rtime: 57 utime: 43 stime: 14 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/ekiga' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496410128 (LWP 3854)] [New Thread 1106008384 (LWP 3948)] [New Thread 1105742144 (LWP 3946)] [New Thread 1074272576 (LWP 3913)] [New Thread 1074006336 (LWP 3912)] 0x00000031f1a0d96f in waitpid () from /lib64/libpthread.so.0
+ Trace 132157
Thread 1 (Thread 46912496410128 (LWP 3854))
----------- .xsession-errors --------------------- starting indexing... indexing #1 - /home/periklis flushing all words Finished indexing. Waiting for new events... Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1a5 specified for 0x1600376 (). GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized ** (bug-buddy:3984): WARNING **: Couldn't load icon for Open Folder Could not find the frame base for "PSyncPoint::Wait(PTimeInterval const&)". Could not find the frame base for "PTimerList::Process()". --------------------------------------------------
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 417801 ***