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 357023 - crash in Ekiga Softphone: I am only starting ekiga...
crash in Ekiga Softphone: I am only starting ekiga...
Status: RESOLVED INCOMPLETE
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-21 07:11 UTC by ernillew
Modified: 2006-10-25 14:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description ernillew 2006-09-21 07:11:57 UTC
Version: 2.0.3

What were you doing when the application crashed?
I am only starting ekiga...


Distribution: Gentoo Base System version 1.12.5
Gnome Release: 2.16.0 2006-09-19 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 59908096 vsize: 0 resident: 59908096 share: 0 rss: 21204992 rss_rlim: 0
CPU usage: start_time: 1158822673 rtime: 0 utime: 101 stime: 0 cutime:93 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1518086480 (LWP 23484)]
[New Thread -1520165984 (LWP 23488)]
[New Thread -1519899744 (LWP 23487)]
0xffffe410 in __kernel_vsyscall ()

Comment 1 Damien Sandras 2006-09-21 10:50:20 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.


Also make sure that you are not using a garbled system and have a correct installation. 
Comment 2 Snark 2006-09-21 11:03:11 UTC
Pfff... gentoo again :-/
Comment 3 Snark 2006-09-27 08:58:46 UTC
*** Bug 357895 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2006-10-25 14:38:46 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information Damien and Snark asked for.
Thanks!