GNOME Bugzilla – Bug 435538
crash in IP Telephony, VoIP and Video Conferencing: Openning IP Telephony ap...
Last modified: 2007-05-03 17:40:11 UTC
Version: 2.0.5 What were you doing when the application crashed? Openning IP Telephony application. This is a fresh install of FC6. 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 18:53:15 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 117125120 vsize: 0 resident: 117125120 share: 0 rss: 19750912 rss_rlim: 0 CPU usage: start_time: 1178208418 rtime: 0 utime: 84 stime: 0 cutime:73 cstime: 0 timeout: 11 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/ekiga' (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 -1208207648 (LWP 25409)] [New Thread -1268266096 (LWP 25428)] [New Thread -1267999856 (LWP 25427)] [New Thread -1267733616 (LWP 25426)] [New Thread -1257243760 (LWP 25425)] [New Thread -1210573936 (LWP 25413)] [New Thread -1210307696 (LWP 25412)] 0x00d9f402 in __kernel_vsyscall ()
+ Trace 132137
Thread 1 (Thread -1208207648 (LWP 25409))
----------- .xsession-errors --------------------- localuser:josho being added to access control list SESSION_MANAGER=local/user:/tmp/.ICE-unix/25074 ** (gnome-session:25074): WARNING **: Host name lookup failure on localhost. ** (bug-buddy:25434): 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 "PHouseKeepingThread::Main()". Could not find the frame base for "PThread::PXBlockOnIO(int, int, PTimeInterval const&)". Could not find the frame base for "PSocket::Select(PSocket::SelectList&, PSocket::SelectList&, PSocket::SelectList&, PTimeInterval const&)". --------------------------------------------------
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 416551 ***