Bug 330088

Summary:	OAuth is lost after each system reboot
Product:	[Unmaintained] choqok	Reporter:	msirapian
Component:	Twitter	Assignee:	Daniel Kreuter <daniel.kreuter85>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	bugs.kde, guiwiz, JFF, kadeee, mehrdad.momeny, mikael79, nurgle, scarpino
Priority:	NOR
Version First Reported In:	1.4
Target Milestone:	---
Platform:	Debian unstable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description msirapian 2014-01-17 17:16:36 UTC

Hello

Even when my twiiter account is authentificated, after a reboot, the OAuth is lost. I then have to return in the settings to obtain a PIN code and renew the authentification.

I do use kwallet for my password.

It doesn't happen at every reboot but once it happens, of course, the authentification is definitely lost.



Reproducible: Sometimes

Steps to Reproduce:
1. Authentificate Twitter account
2. Shutdown system and reboot
3. Launch choqok and see if OAuth is active or not
Actual Results:  
OAuth is lost, no mention of it, and I have to go in the account settings to renew it

Expected Results:  
OAuth preserved and autoconnection to my Twitter account at Choqok launch

Comment 1 Daniel Kreuter 2014-01-17 18:26:46 UTC

Hi,

I'll try to reproduce this on a debian system tomorrow.

I'm not able to reproduce this bug on Arch Linux.

Comment 2 Andreas Micklei 2014-04-04 09:09:23 UTC

Just to confirm: Happens to me occasionally as well (every few month). It would be nice to give at least an indication that something went wrong.

Comment 3 Geert Lamers 2014-04-10 16:06:02 UTC

I have noticed the same problem.

Comment 4 Guillaume Pierron 2014-04-11 16:10:57 UTC

Happens to me sometimes too.

Debian testing/Jessie.
Choqok 1.4
KDE 4.11.3

Comment 5 Geert Lamers 2014-06-06 19:56:27 UTC

I launched Choqok from the command line, and this is the output when Oauth authentication fails:

$ choqok --nofork
Choqok  1.4
createSignature - consumer secret is empty, make sure that you set itwith QOAuth::Interface::setConsumerSecret()
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
choqok(15604) Choqok::PluginManager::loadPluginInternal: Unable to find a plugin named ' "none" '!
createSignature - consumer secret is empty, make sure that you set itwith QOAuth::Interface::setConsumerSecret()
createSignature - consumer secret is empty, make sure that you set itwith QOAuth::Interface::setConsumerSecret()
createSignature - consumer secret is empty, make sure that you set itwith QOAuth::Interface::setConsumerSecret()
createSignature - consumer secret is empty, make sure that you set itwith QOAuth::Interface::setConsumerSecret()



After re-authenticating, this is the output when launched from command line:

$ choqok --nofork
Choqok  1.4
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
choqok(17369) Choqok::PluginManager::loadPluginInternal: Unable to find a plugin named ' "none" '!


Somehow its secret seems to get lost. Is this the secret stored in KWallet as 'xxx_consumerSecret'? I'll keep an eye out for it to see if it disappears from KWallet next time Choqok decides to disauthenticate.


Choqok 1.4
KDE Development Platform 4.13.1
Qt 4.8.5
Gentoo Linux

Comment 6 Geert Lamers 2014-06-19 20:28:44 UTC

It took a while for Choqok to lose authentication this time around. I checked KWallet, there is a Choqok entry present with 'xxx_consumerSecret' and 'xxx_tokenSecret' entries, but both are now empty.

Comment 7 Andrea Scarpino 2015-08-04 09:01:36 UTC

*** Bug 340387 has been marked as a duplicate of this bug. ***

Comment 8 Andrea Scarpino 2017-12-22 19:37:33 UTC

With current git we migrated to Qt's OAuth implementation, so maybe this is no more valid. Re-open if necessary.