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 361248 - crash in Ekiga Softphone: When closing
crash in Ekiga Softphone: When closing
Status: RESOLVED DUPLICATE of bug 359655
Product: ekiga
Classification: Applications
Component: general
2.0.x
Other All
: High critical
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-10 19:48 UTC by Vladimer Sichinava
Modified: 2006-10-15 17:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Vladimer Sichinava 2006-10-10 19:48:19 UTC 
Version: 2.0.3

What were you doing when the application crashed?
When closing


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 1667072 vsize: 0 resident: 1667072 share: 0 rss: 548864 rss_rlim: 0
CPU usage: start_time: 1160330597 rtime: 0 utime: 171 stime: 0 cutime:0 cstime: 0 timeout: 171 it_real_value: 0 frequency: 1005

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-10-10 20:02:03 UTC 
Thanks for the bug report. 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.

Can you reproduce this?
Comment 2 Damien Sandras 2006-10-10 20:14:57 UTC 
I wonder if we shouldn't simply close all those bugs are report them to the Ubuntu bugtracker. Not sure, but it is a new flood of Ubuntu bugs unfortunately.
Comment 3 Karsten Bräckelmann 2006-10-10 21:07:41 UTC 
Damien, unfortunately the real cause for the recent flood of useless stacktraces has not been found. It may be Ubuntu specific, but some investigation seems to point to bug-buddy 2.16.x. Keep in mind that the flood likely appears to be Ubuntu related only, due to the sheer mass of (GNOME) Ubuntu users.

Also, in my experience, installing debugging packages almost always pinpoints the culprit of the crash, even when using bug-buddy to gather the stacktrace.
Comment 4 Damien Sandras 2006-10-15 14:42:00 UTC 
Most probably a DUP of http://bugzilla.gnome.org/show_bug.cgi?id=359655
Comment 5 Sebastien Bacher 2006-10-15 17:07:37 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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