GNOME Bugzilla – Bug 404612
crash in Ekiga Softphone: Didn't do anything. Ekig...
Last modified: 2007-03-28 03:00:36 UTC
Version: 2.0.3 What were you doing when the application crashed? Didn't do anything. Ekiga just sat there in systray and got so bored that it crashed. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 119816192 vsize: 0 resident: 119816192 share: 0 rss: 22298624 rss_rlim: 0 CPU usage: start_time: 1170686985 rtime: 0 utime: 279 stime: 0 cutime:252 cstime: 0 timeout: 27 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 -1247553872 (LWP 23267)] [New Thread -1249477728 (LWP 23272)] [New Thread -1249211488 (LWP 23271)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 108177
Thread 1 (Thread -1247553872 (LWP 23267))
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!