After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 358201 - crash in Ekiga Softphone:
crash in Ekiga Softphone:
Status: RESOLVED DUPLICATE of bug 358155
Product: ekiga
Classification: Applications
Component: general
2.0.x
Other All
: High critical
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-28 21:27 UTC by hrober
Modified: 2006-09-29 12:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description hrober 2006-09-28 21:27:08 UTC 
Version: 2.0.3

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 1810432 vsize: 0 resident: 1810432 share: 0 rss: 552960 rss_rlim: 0
CPU usage: start_time: 1159459467 rtime: 0 utime: 114 stime: 0 cutime:0 cstime: 0 timeout: 114 it_real_value: 0 frequency: 36787

Backtrace was generated from '/usr/bin/ekiga'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Comment 1 Karsten Bräckelmann 2006-09-28 21:40:41 UTC 
Thanks for taking the time to report this bug.

This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug.

Also, unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 Snark 2006-09-29 12:34:22 UTC 

*** This bug has been marked as a duplicate of 358155 ***