GNOME Bugzilla – Bug 370231
crash in Ekiga Softphone: navigation web
Last modified: 2007-01-14 18:54:51 UTC
Version: 2.0.3 What were you doing when the application crashed? navigation web Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 112881664 vsize: 0 resident: 112881664 share: 0 rss: 33652736 rss_rlim: 0 CPU usage: start_time: 1162591239 rtime: 0 utime: 11838 stime: 0 cutime:4306 cstime: 0 timeout: 7532 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 -1246976336 (LWP 11326)] [New Thread -1309680736 (LWP 11441)] [New Thread -1307702368 (LWP 11428)] [New Thread -1309414496 (LWP 11427)] [New Thread -1260766304 (LWP 11371)] [New Thread -1309115488 (LWP 11362)] [New Thread -1308796000 (LWP 11361)] [New Thread -1304974432 (LWP 11346)] [New Thread -1304708192 (LWP 11345)] [New Thread -1304441952 (LWP 11344)] [New Thread -1277551712 (LWP 11342)] [New Thread -1296049248 (LWP 11340)] [New Thread -1249231968 (LWP 11331)] [New Thread -1248965728 (LWP 11330)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 82528
Thread 4 (Thread -1309414496 (LWP 11427))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
*** Bug 384093 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 367982 ***