GNOME Bugzilla – Bug 577527
Crash when registering/unregistering an invalid account
Last modified: 2009-04-20 15:52:54 UTC
I created a "test" account, then registered/unregistered it (of course it fails since I just wrote "test" everywhere) :
+ Trace 214065
I'm not sure if the problem is in ekiga or deeper in opal yet.
I reported upstream as https://sourceforge.net/tracker/?func=detail&aid=2725071&group_id=204472&atid=989748 Notice: it happens with both opal-3.6.1 and opal-svn.
Hi Snark, Just to notify I linked this bug with this one in the Ubuntu BTS: https://bugs.launchpad.net/ekiga/+bug/359607 Best regards, Yannick
I can't reproduce it now : upstream probably fixed it...
*** Bug 579439 has been marked as a duplicate of this bug. ***
Is there plans to put this fix in a ekiga 3.2.1 and associated opal/ptlib release?
Next gnome stable is scheduled in one month from now. Do you need a release soon? By the way, would ubuntu use the new version, if any?
well it seems we missed the 2.26.1 release which was April 15. It would be nice to get a stable release (I was hoping to get one with 2.26.1) to fix a few of these style crash bugs. I've had 2-3 bug reports on rawhide and the one I reported (now a dupe of this one) I see quite regularly so I would like to get a fix into it before a F11 release and I get loaded with them. Its already in freeze and we'd need to get the fix in within 10 days. I have no idea of the ubuntu release policy. I don't use it at all!
Is it worth to make a new release? If there is only 1 or 2 bugs, you could use a patch in your packages, what do you think?
Hi Eugen, I guess if we release for the next Gnome, Ubuntu will _probably_ ship it in the next cycle, i.e. in 9.10 (in october 2009)
(In reply to comment #8) > Is it worth to make a new release? If there is only 1 or 2 bugs, you could use > a patch in your packages, what do you think? I can patch if necessary. I'd rather not, but if I was given the details of what the patches were I would. Is there a reason we're following random gnome releases?
We agreed not to make a release a few days ago because: - Damien is little available these times, and I hesitated to make a release - there were/are very few fixes in branch (there are in trunk only for the moment) - the bug "crash at exit" is still not fixed (maybe it's glib faulty here, I don't know) Now I see that more and more crashes are fixed, so I imagined that it is interesting to do a release. However, ptlib and opal should make a release too, should I bother them? I think it is worth for ubuntu people, because there are several fixes from their bugzilla which are fixed now (in trunk...); but I also think that now it is too late for 9.04. I understand that it's a bit silly what I say, but... if it is not difficult for you to integrate a few patches, I would prefer that you do it...
> I understand that it's a bit silly what I say, but... if it is not difficult > for you to integrate a few patches, I would prefer that you do it... Well a fix for this one would be a good start but for the life of me can't see it in git/svn. Would be nice if the commit revision is mentioned in the bug report.
It's upstream, comment #1.
http://opalvoip.svn.sourceforge.net/viewvc/opalvoip/opal/ is the web interface to opal repository.
(In reply to comment #14) > http://opalvoip.svn.sourceforge.net/viewvc/opalvoip/opal/ is the web interface > to opal repository. > I do know where upstream is :-) But I don't see what the svn revision number is in the upstream bug report. It says in the upstream bug that its fixed in trunk and 3.6.2 but there is no 3.6.2 release yet and I don't have the time to troll through svn logs to work out what the fix was.
Pretty sure this one: http://opalvoip.svn.sourceforge.net/viewvc/opalvoip?view=rev&revision=22421
Yes!