Port listeningn / registration broken (by design)

Bug #69525 reported by V S
4
Affects Status Importance Assigned to Milestone
ekiga (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Running edgy and the latest ekiga,

when for instance connected through WLAN and the link goes down and comes back up, Ekiga doesn't re-register but stays offline. You have to register by hand again.

Also, if I start it when my links are down, it doesn't know how to start the listeners. Registration is impossible, when I try it, it immediately says it didn't work and I don't see any network traffic in the sniffer.

Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :

Has this been upstreamed? Do you need more information?

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for your bug report. Is this still an issue with the latest version of ekiga? Which version are you currently using? You can check via 'dpkg -l ekiga'.

Changed in ekiga:
assignee: nobody → brian-murray
status: Unconfirmed → Needs Info
Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :

Yes, it is. This is by design, as I pointed out. It's in 2.0.3-0ubuntu5 as well as in snapshot 20070208-01-feisty.1 from snapshots.ekiga.net.

It goes as far as when starting ekiga when I have no network connection for it being unfunctional until restarted (even trying to register my account by hand doesn't work, it just always says "registration failed" presumably because it doesn't have the socket to use).

Changed in ekiga:
assignee: brian-murray → nobody
importance: Undecided → Low
status: Needs Info → Confirmed
Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :

Hey,

to be clear: I have to fully restart the application each time there's a change in my network topology. I don't know what the criteria for "low" bugs is, though.

Revision history for this message
V S (th-deactivatedaccount-deactivatedaccount) wrote :

Sorry for still bitching, but now with network manager this happens upon every boot (because the network isn't up yet when ekiga starts). So I can't get ekiga to start automatically when I start X.

Revision history for this message
Brian Murray (brian-murray) wrote :

The gnomemeeting / ekiga bug report mentions opal being a blocker for this and links here: http://sourceforge.net/tracker/index.php?func=detail&aid=1588780&group_id=80674&atid=560612

Changed in gnomemeeting:
status: Unknown → Confirmed
Changed in gnomemeeting:
status: Confirmed → Invalid
Revision history for this message
Andreas Moog (ampelbein) wrote :

That should be fixed long time ago, please reopen if you still get the issue.

Changed in gnomemeeting:
status: Invalid → Unknown
Changed in ekiga (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: Confirmed → Fix Released
Changed in gnomemeeting:
status: Unknown → Fix Released
Changed in gnomemeeting:
importance: Unknown → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.