GNOME Bugzilla – Bug 430107
crash in Ekiga Softphone: Starting ekiga after upg...
Last modified: 2007-05-01 20:13:15 UTC
Version: 2.0.9 What were you doing when the application crashed? Starting ekiga after upgrading to version 2.0.9 from the x86 edgy repository. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 105664512 vsize: 0 resident: 105664512 share: 0 rss: 25309184 rss_rlim: 0 CPU usage: start_time: 1176672131 rtime: 0 utime: 218 stime: 0 cutime:80 cstime: 0 timeout: 138 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 -1246251344 (LWP 6866)] [New Thread -1298277472 (LWP 6881)] [New Thread -1300235360 (LWP 6879)] [New Thread -1249686624 (LWP 6870)] [New Thread -1249420384 (LWP 6869)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 128067
Thread 1 (Thread -1246251344 (LWP 6866))
*** Bug 430293 has been marked as a duplicate of this bug. ***
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!
*** This bug has been marked as a duplicate of 434223 ***