After hibernation ekiga says registration failed.

[Kaito]

Binary package hint: ekiga

Ekiga 2.0.3
Processor Intel(R) Pentium(R) M processor 1.60GHz
Memory 482MB (320MB used)
Operating System Ubuntu 6.10

Kernel: 2.6.17-10-generic

After hibernation ekiga cannot register.
After disable and enable again the account in the accounts settings the registration succes.

[Jan (jan23)]

I can confirm this bug.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? May you try to reproduce it with a newer version of Ubuntu like Feisty or Gutsy? Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you may test this behavior with a newer version of Ubuntu like Gutsy Gibbon you may grab a CD Image from here: http://www.ubuntu.com/testing/ ; Thanks and we appreciate your help.

[Roger Binns (ubuntu-rogerbinns)]

This issue is still present in Ekiga in Gutsy (all updates applied). After doing a hibernate, Ekiga tries to reregister on the resume and fails (in my case it says the failure is due to a timeout). There is no easy way of getting Ekiga to re-register (it would be nice if it tried a few times after a failure) other than disabling and re-enabling all the accounts or restarting Ekiga.

[Jon (spam-jonkowal)]

I second the confirmation, using Gutsy (Ekiga 2.0.11, all Ubuntu updates applied). I always have to restart/re-register ekiga manually to be able to receive or place phone calls after resuming from hibernate.

[Jamin W. Collins (jcollins)]

I too can confirm this. Running fully updated Gutsy with current Ekiga v2.0.11. It would be nice if there were some menu option to re-attempt registration or perhaps a configurable number of retries with delays between them.

I don't know that I agree with the priority assigned to this bug. Ekiga would be quite useful on laptops, but this bug is a rather large annoyance to using it in such environments. Personally, I have it configured to register with my home Asterisk system to receive notification of potentially important calls while I'm out. However, as it currently stands it's nearly useless to keep it running when moving between locations.

Please consider raising the priority of this bug and addressing the timeout/retry issue.

[Christian Gogolin (cgogolin-deactivatedaccount)]

I can confirm the exact same problem under Debian Lenny with Ekiga version 2.00.

[Roger Binns (ubuntu-rogerbinns)]

This appears to be fixed in Intrepid with Ekiga 2.0.12-0ubuntu5

[Nikolaus Rath (nikratio)]

I'd like to petition for this bug being fixed in hardy as well please.

[Sebastien Bacher (seb128)]

could somebody confirm if the bug is fixed in intrepid?

[sim909 (srizzi)]

No, the bug is still there for me.
Running intrepid and ekiga 2.0.12-0ubuntu5, all packages in my system updated to latest version.
The same happens after a suspend.

After a couple of minutes from resume the status bar goes from "registration failed: timeout" to "missed calls: 0 - voice mails:0", making me think that it has registered with my sip server, when in fact it hasn't. No need to restart ekiga, disabling and re-enabling the account is enough.

I only started using ekiga with intrepid, so cannot comment on previus versions.
I'd be happy to provide more info if needed.

[sim909 (srizzi)]

Trying to find a fix for the problem, I was thinking of having ekiga being killed at suspend/hibernate and then restarted at resume. My (newbie) attempt is to add the following script as /etc/pm/sleep.d/01ekiga.fix (substitute sim909 with actual user name):

++++++
#!/bin/sh

case "$1" in
 hibernate|suspend)
  if [ -n "`pidof ekiga`" ] ; then
       touch /tmp/ekiga.fix.by.sim909
   killall ekiga
  fi
  ;;
 thaw|resume)
  if [ -f /tmp/ekiga.fix.by.sim909 ] ; then
   su -c "ekiga --display=:0.0 &" sim909
   rm /tmp/ekiga.fix.by.sim909
  fi
  ;;
 *) exit $NA
  ;;
esac
+++++

The problem now is that ekiga does not start, complaining that there is a gconf error. I think the error is somehow related to trying to start ekiga from outside of the x session. No problem starting it within the x session.

Any suggestions?

[Alexander Grundner (agrundner)]

Same error in 8.10 as well. I'm wondering if it has something to do with the fact that it's managing a third party SIP service like Gizmo instead of it's native service?

[sim909 (srizzi)]

I know, as I said in December I am also running Intrepid, problem still there. I was hoping that someone would comment on my (clumsy?) attempt to circumvent the problem...

What I didn't mention is that I also use ekiga with third party sip service, thought it wouldn't matter but you never know...

[Andreas Moog (ampelbein)]

This should be reported on bugzilla.gnome.org by somebody having that issue. It would be handy if you could run ekiga from a terminal with 'ekiga -d 4 > ekiga-log.txt 2>&1' and attach the logfile.

[sim909 (srizzi)]

I have since switched to ubuntu 9.04 that comes with ekiga 3.2, the issue seems fixed, although I haven't done extensive testing.

[Yannick Defais (sevmek)]

Hi,

Can someone else confirm this is fixed using Ubuntu Jaunty (ekiga 3.2.0)?

Best regards,
Yannick

[sim909 (srizzi)]

I am now running jaunty and ekiga 3.2, problem seems fixed for me

[Yannick Defais (sevmek)]

Thank you. Closing this bug. Feel free to reopen if needed.

Best regards,
Yannick