GNOME Bugzilla – Bug 382010
crash in Ekiga Softphone: auto-answered a call fro...
Last modified: 2006-12-04 08:50:28 UTC
Version: 2.0.3 What were you doing when the application crashed? auto-answered a call from a netmeeting user his image appeared ok but then ekiga hung Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 110374912 vsize: 0 resident: 110374912 share: 0 rss: 30932992 rss_rlim: 0 CPU usage: start_time: 1165177902 rtime: 0 utime: 23300 stime: 0 cutime:22065 cstime: 0 timeout: 1235 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/ekiga' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1246824784 (LWP 3152)] [New Thread -1262679136 (LWP 5154)] [New Thread -1261495392 (LWP 5143)] [New Thread -1261225056 (LWP 5142)] [New Thread -1260954720 (LWP 5141)] [New Thread -1260688480 (LWP 5140)] [New Thread -1260115040 (LWP 5131)] [New Thread -1259848800 (LWP 5128)] [New Thread -1352741984 (LWP 5055)] [New Thread -1353274464 (LWP 3182)] [New Thread -1353008224 (LWP 3181)] [New Thread -1352168544 (LWP 3178)] [New Thread -1343775840 (LWP 3176)] [New Thread -1248748640 (LWP 3161)] [New Thread -1248482400 (LWP 3160)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 91365
Thread 3 (Thread -1261495392 (LWP 5143))
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** This bug has been marked as a duplicate of 358405 ***