Description of problem: after updating to kde 4.3.96 (RC 2) from redhat-kde repository, choqok stoped to log into twitter service. Version-Release number of selected component (if applicable): choqok-0.6.1-7.fc11.i586 How reproducible: since i update i always get an error message when i try to log in. Steps to Reproduce: 1. update to 4.3.96 (RC 2) 2. open choqok and setup a twitter account 3. try to login Actual results: it tries to connect, then it asks me my password once again but this time is kwallet, then an error message saying something about unable to authenticate: the connection to the twitter.com machine was interrupted. The dialog ask me to check my credentias what i did a couple of times. I do can log on the site. Expected results: i would be able to log into the service. Additional info:
I had a similar bug where I was not able to authenticate in Choqok because I did not have KDE4 installed. I had to install KDE 4.2 before it would allow me to log in. It just seems that Choqok is not packaged properly and that some dependency is not being addressed. In Edney's case the Choqok package should have complained when he upgraded KDE that some dependency is not being met, and in my case yum should have installed the required package dependencies when I had first installed Choqok on my sister.
I think you are someway right, cause Choqok started to work as soon as i upgraded to RC3. Indeed that wasn´t the first time it misbehaved after an update of my box. Anyway it´s woking now. Thank you.
Maintainer here. I think I forgot to add a choqok dependency on KWallet. I'll add this when I get the time.
choqok-0.6.6-9.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/choqok-0.6.6-9.fc10
choqok-0.6.6-9.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
Well I'm running choqok-0.6.6-9 on F11 and stil can't login to service. Just to note I'm behind a proxy server. Could it be imposing some restrictions?
fwiw, we determined today the needed dep was more likely kdebase-runtime instead of kdeutils (utrns out kdeutils, pulled in kdebase-runtime itself). (proxy issues are separate to this one).