Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#19343 - [telepathy-butterfly] connection manager crashes (possibly related: [libproxy])
Attached to Project:
Arch Linux
Opened by Jouke Witteveen (jouke) - Monday, 03 May 2010, 13:24 GMT
Last edited by Ionut Biru (wonder) - Wednesday, 05 May 2010, 17:26 GMT
Opened by Jouke Witteveen (jouke) - Monday, 03 May 2010, 13:24 GMT
Last edited by Ionut Biru (wonder) - Wednesday, 05 May 2010, 17:26 GMT
|
DetailsEmpathy cannot connect through telepathy/butterfly. The connection manager seems to crash and Empathy displays "No reason specified" as error message.
Downgrading to 0.5.8 fixes the problem. The NEWS file of telepathy-butterfly suggests it might be a problem with libproxy being outdated (I have got it installed). Perhaps upgrading it will fix the problem. |
This task depends upon
Closed by Ionut Biru (wonder)
Wednesday, 05 May 2010, 17:26 GMT
Reason for closing: Fixed
Additional comments about closing: libproxy 0.3.1-1
Wednesday, 05 May 2010, 17:26 GMT
Reason for closing: Fixed
Additional comments about closing: libproxy 0.3.1-1
* libproxy can now be used to automatically retrieve proxy settings
and give these settings to papyon. NOTE: the version of
python-libproxy in Ubuntu (0.2.3) has a bug which makes butterfly
segfault -- version 0.3.1 is known to work. (fd.o#27121)
so is clearly a bug in libproxy and that should be assigned properly