Version: unspecified (using Devel) OS: Linux First, my version is 0.9.81-1 which isn't in the list and I'm not running KDE so there is no version number. When I first started Choqok and added a Twitter account I got the option for OAuth, I did that, entered the PIN and it connected and grabbed tweets. Next time I started it up it asked for a username and password. I tried entering them but on the command line I got the following kded(2323)/KPasswdServer KPasswdServer::queryAuthInfoAsync: User = "" , Message= "You need to supply a username and a password to access this site." , WindowId = 0 kded(2323)/KPasswdServer KPasswdServer::processRequest: User = "" , Message = "You need to supply a username and a password to access this site." and other similar messages. I treid a couple of times but this just got repeated. I then went back to set the account up again and tried to re-enable OAuth, it sent me to the Twitter page which asked me about confirming access but didn't give me the option to re-enter the PIN Twitter gave me. The following line appears in the output quite a bit implying it knows it is supposed to do OAuth but hasn't stored the value for some reason choqok(2313) TwitterApiMicroBlog::requestTimeLine: Latest "ReTweets" Id: "21479199377" createSignature - consumer secret is empty, make sure that you set itwith QOAuth::Interface::setConsumerSecret() Reproducible: Always Steps to Reproduce: Start Choqok Actual Results: asks for user/password but then doesn't send them Expected Results: OAuth to work and me not get asked for user/password The severity field in bug report doesn't have an appropriate option for this, it isn't a crash and it isn't major in that it causes data loss but it is major in that I can't use the client. Left at normal but it is more than that
I've just upgraded to the latest version from svn, hand built it and installed but still getting the same problem. I cleared out the settings files and started Choqok, it ran fine for that session, asking for and accepting the OAuth pin but once I'd shut it down and restarted it it started asking for my twitter username and password then doing nothing with them. I see this in the log file. choqok(4076) TwitterApiMicroBlog::requestTimeLine: Latest "Home" Id: "22125161333" createSignature - consumer secret is empty, make sure that you set itwith QOAuth::Interface::setConsumerSecret() choqok(4076) TwitterApiMicroBlog::requestTimeLine: choqok(4076) TwitterApiMicroBlog::requestTimeLine: Latest "Reply" Id: "22124992315" createSignature - consumer secret is empty, make sure that you set itwith QOAuth::Interface::setConsumerSecret() choqok(4076) TwitterApiMicroBlog::requestTimeLine: choqok(4076) TwitterApiMicroBlog::requestTimeLine: Latest "Inbox" Id: "1504195076" createSignature - consumer secret is empty, make sure that you set itwith QOAuth::Interface::setConsumerSecret() choqok(4076) TwitterApiMicroBlog::requestTimeLine: choqok(4076) TwitterApiMicroBlog::requestTimeLine: Latest "Outbox" Id: "1445458029" createSignature - consumer secret is empty, make sure that you set itwith QOAuth::Interface::setConsumerSecret() choqok(4076) TwitterApiMicroBlog::requestTimeLine: choqok(4076) TwitterApiMicroBlog::requestTimeLine: Latest "ReTweets" Id: "22071916202" createSignature - consumer secret is empty, make sure that you set itwith QOAuth::Interface::setConsumerSecret() I tried installing kwallet but that doesn't work properly, complaining about .service files. As I don't use KDE I'm guessing that Choqok expected something to be in place when it saved the key but that thing wasn't so it has now lost it.
Found the problem, you have to have the KDE wallet app installed for this to work. If it is that critical a dependency then something should do an explicit check for it running. To any Debian maintainers reading this, it isn't a package dependency at the moment.
SVN commit 1170422 by momeny: BUG:248480 From now, Choqok will work without KWallet too. Just storing secrets in a text file. M +20 -6 passwordmanager.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1170422
*** Bug 248941 has been marked as a duplicate of this bug. ***