Pidgin 2.5.0 crashes on Bonjour protocol when Ubuntu Intrepid is used on both ends

[komputes]

Pidgin 2.5.0 crashes on Bonjour protocol when Ubuntu Intrepid is used on both ends. Please note that Intrepid to Hardy works well (Pidgin 2.5.0 <-> 2.4.1). I am using an updated installation of Ubuntu Intrepid Ibex, and the other side is using a LiveCD of Intrepid Ibex Alpha6.

Apport could not report the bug because it complains that Pidgin is not a "Valid Ubuntu Package". Backtrace of the program does not work since there does not seem to be this package in the ddeb repositories:

pidgin-dbgsym=1:2.5.1-0ubuntu2

I have uploaded the output of starting pidgin in debug mode hoping this will help.

[komputes (komputes)]

With pidgin 1:2.5.2-0ubuntu1 the program does not crash, but it still does not work. I think more attention should be paid to the regressions introduced in Intrepid when it comes to pidgin/bonjour. I am experiencing file transfer not working, not being able to message due to timeouts and not being able to see peers when connected.

[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? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

[komputes (komputes)]

I am still having these issues with Bonjour on Pidgin 1:2.5.2-0ubuntu1. Yesterday I sent a message via bonjour and the recipient end computer simply crashed (completely froze up). Bonjour protocol in pidgin definitely needs to be reviewed and tested.

[J. Austin Rodriguez (jeanaustinr)]

Thank you for taking the time to report this bug and helping to make Ubuntu and Pidgin better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu and Pidgin since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current development versions. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect <bug #>, and any other logs that are relevant for this particular issue.

For more details, refer to http://developer.pidgin.im/wiki/FullChangeLog.