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 521008 - No error messages that Ekiga can't open Listeners, instead automatic tries to connect
No error messages that Ekiga can't open Listeners, instead automatic tries to...
Status: RESOLVED DUPLICATE of bug 324564
Product: ekiga
Classification: Applications
Component: general
2.0.x
Other All
: Normal enhancement
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-07 15:41 UTC by Marc Reichelt
Modified: 2008-04-02 21:54 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Marc Reichelt 2008-03-07 15:41:45 UTC
If you use one of the latest (K)Ubuntu versions with the NetworkManager and no connection is active (e.g. the NetworkManager is in 'offline' mode or no network connection is found) Ekiga shows error message(s) that the Listeners for SIP or H.323 protocols can't be activated. Ekiga also shows these messages if another program blocks the ports.
This is really bad for the work flow - if you are starting the computer, and no network connection is established (or is establishing - which takes a few seconds) Ekiga should not show these messages. Instead it should show an icon in the panel that indicates that the Listeners couldn't be activated.
Additional, it should check every N seconds if it can start the Listeners.

The optimal behaviour would be:
- Ekiga listens to the NetworkManager and creates the Listeners as soon as the network is ready (and destroys the Listeners as soon as the network is down).
- No error messages are shown - instead, an icon in the panel indicates the connection status.

This would be much better for the work flow.
Comment 1 Damien Sandras 2008-04-02 20:47:38 UTC
There is a similar bug report somewhere, but I can't find it anymore. Anyway, it is on the TODO for 3.00.
Comment 2 Damien Sandras 2008-04-02 21:22:20 UTC
Found it!

*** This bug has been marked as a duplicate of 324564 ***
Comment 3 Marc Reichelt 2008-04-02 21:32:35 UTC
Is this really a duplicate of bug 324564?
My bug is about the messages, only in a second way about the network handling.
Comment 4 Damien Sandras 2008-04-02 21:54:44 UTC
The messages will disappear. If it does not try registering on an inactive interface, then it will not produce any error.