GNOME Bugzilla – Bug 386479
crash in Ekiga Softphone: 1ere lancée du programme
Last modified: 2007-03-03 21:13:19 UTC
Version: 2.0.3 What were you doing when the application crashed? 1ere lancée du programme Distribution: openSUSE 10.2 (X86-64) Gnome Release: 2.16.1 2006-11-28 (SUSE) BugBuddy Version: 2.16.0 Memory status: size: 431464448 vsize: 431464448 resident: 9441280 share: 24350720 rss: 33792000 rss_rlim: 1792762880 CPU usage: start_time: 1166272223 rtime: 137 utime: 127 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/gnome/bin/ekiga' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47729254563904 (LWP 7514)] [New Thread 1074805056 (LWP 7586)] [New Thread 1074538816 (LWP 7585)] [New Thread 1158465856 (LWP 7575)] [New Thread 1158199616 (LWP 7573)] [New Thread 1074272576 (LWP 7540)] [New Thread 1074006336 (LWP 7539)] (no debugging symbols found) 0x00002b68d3c761f6 in poll () from /lib64/libc.so.6
+ Trace 94598
Thread 6 (Thread 1074272576 (LWP 7540))
What were you doing exactly when it crashed? Was it in the druid at the network detection phase? (in which case disabling accessibility might help).
Julien, look for gnome_gtk_module_info_get generally gives a good idea of where it crashed. For example, here, we see a crash in pwlib while connecting to ekiga.net/ip through http. However, no way to determine why it crashed.
*** Bug 389848 has been marked as a duplicate of this bug. ***
A consequence of bug 364480. *** This bug has been marked as a duplicate of 364480 ***
*** Bug 395719 has been marked as a duplicate of this bug. ***
*** Bug 414223 has been marked as a duplicate of this bug. ***