Bug 275399

Summary:	Error at request "/1/statuses/friends.xml?cursor=-1"
Product:	[Unmaintained] choqok	Reporter:	Samuel Suther <s.suther>
Component:	Twitter	Assignee:	Mehrdad Momeny <mehrdad.momeny>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	gmlastik, matt.casters
Priority:	NOR
Version First Reported In:	1.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Samuel Suther 2011-06-11 15:10:38 UTC

Version:           1.0 (using KDE 4.6.2) 
OS:                Linux

I have click on an Twitter Name>> Action xxx follow... from this moment, everytime on startup i got this message on commandline:

Error at request  "/1/statuses/friends.xml?cursor=-1"

And this message as Dialoge in choqok: "This method requires authentication"

But the authentication for choqok is alredy set in Twitter account.



Reproducible: Didn't try




OS: Linux (i686) release 2.6.38-8-generic
Compiler: cc

Comment 1 Matt Casters 2011-06-14 22:06:00 UTC

Same error on Kubuntu 11.04, Choqok 1.0, KDE 4.6.2:

Choqok  1.0 
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
matt@kettle:/tmp/ksocket-matt$ Enchant dict for "nl" 0x7f2b64339b50 
Enchant dict for "nl" 0x7f2b64349b80 
choqok(13882): Error at request  "/1/statuses/friends.xml?cursor=-1"  :  "This method requires authentication." 
KCrash: Application 'choqok' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/matt/.kde/socket-kettle/kdeinit4__0
Warning: connect() failed: : Bestand of map bestaat niet
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly
QSocketNotifier: Invalid socket 20 and type 'Read', disabling...

I tried to remove ~/.kde/share/apps/choqok and ~/.kde/share/config/choqokrc but after entering the same credentials I keep getting this error.

Comment 2 Mehrdad Momeny 2011-06-19 05:51:27 UTC


*** This bug has been marked as a duplicate of bug 275185 ***