Hide Forgot
I wanted to try out using Empathy as my IRC client to get better Shell integration, but I can't seem to get it to connect to my Bip server properly. Bip: http://bip.milkypond.org/ it's an IRC proxy, basically. I have it running on another machine on the local network, with several different IRC networks configured. With Bip, you connect to multiple networks by connecting to the same server with the same nick but different passwords. So I set up Empathy accounts for two, initially - the Bitlbee 'network' (Bitlbee is itself an IM proxy, which lets me run all my IM through IRC...) and Freenode. Empathy can connect to the Bitlbee account, usually, but I can't get it to connect to the &bitlbee control network or find any contacts. I can't get it to connect to the Freenode account at all, it just tries for a long time and fails. Sometimes I see this error in the Bip logs: 30-03-2011 12:08:39 ERROR: Error while reading on fd 311 30-03-2011 12:08:39 ERROR: client read_lines error, closing... (the fd number changes each time). I will attach Empathy's debug log, hope it helps you make any sense of the issue.
Created attachment 488876 [details] empathy log
here's the idle log. I don't know why the server is complaining about the password; the one I set is correct. I checked it in seahorse, it is identical to the password set in xchat-gnome, which connects to the server fine.
Created attachment 488877 [details] idle (irc) log
Hmmm, did some initial testing of IRC support (I normally use irssi), and it looks like Empathy isn't saving passwords during account creation. I'll have to see if I can get some free time this weekend to dig into this a little deeper.
Could you test telepathy-idle-0.1.9-1.fc15 from updates-testing to see if it fixes this for you? Thanks.
I could make this work using the current Telepathy Idle code from Git. While creating the account in Empathy, I create a new network called BIP with localhost as the server. Then I put bip4ever:tata:gimpnet as the password, where bip4ever is the username, tata is the password and gimpnet is the network name as configured in BIP. Or am I missing something?
brian: i'll give it a shot in a bit, thanks.
on a quick test it still looks bad: getting errors about the password from the server in the debug log, and if I quit / restart telepathy the password field for the account is empty. I didn't reboot before testing though, I'll try testing after a reboot and re-creating the account again in a bit.
okay, so I rebooted, deleted both accounts I'd created, went into seahorse and deleted all relevant passwords, then re-created the Bip/Freenode account, and it works. But I then re-created the Bip/Bitlbee account - which, per Bip's design, is the same server with a different password - and that one now refuses to connect (and shows a blank password while trying to connect). I think the problem here may be that Telepathy can't handle the Bip design of multiple accounts with the same IRC server, and the second (and third and fourth etc) created account will always fail; the first time around, I created the Bip/Bitlbee account first and the Bip/Freenode account second.
This is how my BIP configuration looks like: http://rishi.fedorapeople.org/bip.conf
Which version of telepathy-idle are you using? You really need 0.1.9 as it fixes a bug with account having passwords.
That's what I have. It still seems to have trouble with passwords, though.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping