I have my authorization user and password in ~/.twinkle/foo.cfg but still get prompted for the username and password when registering to the SIP server
Under Setup -> System Settings -> General is 'foo' checked to be a startup profile? And under Setup -> User Profile -> foo is the SIP authentication section correctly filled out? Note that you need to make sure the realm is right for some servers or it just rejects your auth. Also, anything useful under ~/.twinkle/twinkle.log for a failed startup?
Yes and yes. The realm must be right since when I then type in the username and password again, it registers fine. In the log file, it's just not doing an authorization pass at all the first time before it asks for the username/pass
Does the twinkle.log say it's reading foo.cfg ? Are there any REGISTER SIP requests showing up in there on startup? I assume permissions are ok on the foo.cfg file(s)? I'm pretty puzzled by this as my setup here registers me with 3 providers on startup with no issues. ;(
Yep, it says its reading the config. And I see it with my config for talk.fp.org also. With my talk.fp.org account, ~/.twinkle/fedora.cfg starts out with # USER user_name=katzj user_domain=talk.fedoraproject.org user_display=Jeremy Katz user_organization= auth_realm=talk.fedoraproject.org auth_name=katzj auth_pass=<PASSWORDHERE> I'll attach the twinkle log from it. But everything looks reasonable to me :-/
Do you have: register_at_startup=yes in the cfg file? Also, can you attach the twinkle.log?
Yep :-/
I realize this would be slightly black magic, but could you try the 1.3.2 version I just built for rawhide? http://koji.fedoraproject.org/koji/taskinfo?taskID=802992
Doesn't help and nothing appears different to me in the log :(
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
A completely random plea to try the 1.4.2 currently in rawhide?
Jeremy is gone, closing this bug out as I am not in the position to reproduce.