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 696668 - Excessive time to reconnect to ekiga after sleep
Excessive time to reconnect to ekiga after sleep
Status: RESOLVED WONTFIX
Product: ekiga
Classification: Applications
Component: Account stack
4.0.x
Other Linux
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
gnome[unmaintained]
: 664082 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-03-27 04:30 UTC by mikehawk
Modified: 2020-06-06 16:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description mikehawk 2013-03-27 04:30:19 UTC 
Whenever my laptop goes to sleep it takes an inordinate amount of time (~5 minutes) to log back into my ekiga account.  It initially returns the message "Transport Error could not connect" and then moves to "Could not register(Failed)."  I was connecting through wifi and I suspect this might be a cause of the error.  Though it is possible to simply restart ekiga and have it connect as normal, this is not an ideal fix. I haven't tested this with other SIP accounts so I do not know if it is an issue specific to ekiga accounts or not.
Comment 1 Eugen Dedu 2013-03-27 08:34:56 UTC 
This appears after resume, no matter the network.  It is a known issue.
Comment 2 Eugen Dedu 2013-04-05 13:14:42 UTC 
*** Bug 664082 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2020-06-06 16:31:25 UTC 
Ekiga is not under active development anymore:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/273

Ekiga saw its last release 7 years ago. The last code commits were 4 years ago.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (and transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active Ekiga development again in the future.