Bug#525864: ekiga: Segfaults at startup
Eugen Dedu
Eugen.Dedu at pu-pm.univ-fcomte.fr
Tue Apr 28 21:31:57 UTC 2009
Mathias Brodala wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi.
>
> Eugen Dedu, 28.04.2009 22:09:
>> Mathias Brodala wrote:
>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>
>>> Hi.
>>>
>>> Eugen Dedu, 27.04.2009 17:31:
>>>> Mathias Brodala wrote:
>>>>> Since a few days Ekiga fails to start yielding a segfault.
>>>>> Since ekiga uses gconf instead of config files I am not able to
>>>>> check if there is a problem with my account.
>>>> ekiga version 3.2 will hopefully be uploaded to unstable in one
>>>> week. It fixes some crashes and bugs. Version 2 is not
>>>> maintained anymore.
>>> Are there already some packages or source files for building them
>>> on my own? I’d like to test the upload as soon as possible and
>>> don’t like to rely on Skype.
>> http://wiki.ekiga.org, last section (developers): you can download
>> latest sources and build yourself, or can use the snapshots I make
>> weekly.
>
> Thanks for the info. Seems to work fine except of the network connection
> error I get on each start:
>
>> Ekiga did not manage to configure your network settings
>> automatically. You can still use it, but you need to configure your
>> network settings manually.
>>
>> Please see
>> http://wiki.ekiga.org/index.php/Enable_port_forwarding_manually for
>> instructions
This means that you are behind a symmetric nat, and ekiga does not work
in that case. More information are at the above address.
> I could only do some echo calls for now but there seems nothing wrong
> with my connection. How do I disable the message above?
This is interesting, do you say that ekiga shows that message, still it
works (you have audio and video when you call 500 at ekiga.net)?
--
Eugen
More information about the pkg-gnome-maintainers
mailing list