Login issue with Pidgin using SRV records
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ejabberd (Debian) |
Fix Released
|
Unknown
|
|||
| ejabberd (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
| Precise |
Fix Released
|
Medium
|
Adrien Cunin | ||
Bug Description
= Original report =
The problem has been discussed and fixed in these Debian and upstream bugs:
http://
https:/
I am affected by this bug on 12.04 with ejabberd 2.1.10-2ubuntu1. Can you update the Ubuntu package on 12.04?
= Precise SRU =
[Impact]
This bug impacts at least Pidgin users, as they are unable to connect to affected ejabberd servers. The problem appears when Pidgin uses SRV records to find the server.
[Test Case]
* Try connecting to the ejabberd server using Pidgin. Pidgin returns a "not authorized" error.
* Update ejabber package to 2.1.10-2ubuntu1.1.
* Try connecting again. No error appears and you are successfully connected.
[Regression Potential]
The patch concerns a part of the code responsible for connection handling. However, it has been included upstream for several months, and has been in Debian since August.
Related branches
| Changed in ejabberd (Debian): | |
| status: | Unknown → Fix Released |
| Changed in ejabberd (Ubuntu): | |
| importance: | Undecided → Medium |
| Changed in ejabberd (Ubuntu Precise): | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → Adrien Cunin (adri2000) |
| description: | updated |
| summary: |
- No login possible at ejabberd with libpurple and vhost + Login issue with Pidgin using SRV records |

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Quantal Quetzal.
This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.
[1]: https:/ /wiki.ubuntu. com/StableRelea seUpdates# Procedure