Bug 231814

Could you please specify what you mean by "request"? It doesnt happen to me here with 4.4 and 4.5 Beta 2.

By every request I meant, switching between tabs in the widget, posting comments or when the widget was updating the timeline. 

At the moment I can't reproduce the problem on my home computer with KDE4.5beta2 running kubuntu.

My work station had the problem earlier but I don't have access to it right now so I can't see if it still happens on that machine.

I can confirm this happens for me too...nothing I do seems help.  After configuring the widget, I'll get a prompt asking if the KDE Daemon should be allowed access to KWallet...I'm not really sure about this, so I choose 'Allow Once'.  After this, I get non-stop prompts saying the authentication failed, and I have the option to retry.  If I retry, I get the authentication prompt, with the option to save or not save the password...then the same authentication failure/retry prompt is displayed.

This only started happening a couple days ago, and I've been using this widget for over a year...I don't think I've done anything differently recently.

I've got it configured to authenticate against https://www.twitter.com - is anyone else having this problem (I'm using KDE 4.5 on Ubuntu lucid).

can you take a screenshot of "the authentication prompt" window you are referring to and attach it to this bug report? thanks.

I would, except I no longer get the prompts after I just re-added the widget today.  I now just see a brief notice at the top of the widget that says "Refreshing timeline...", then it goes away, and nothing new is displayed (i.e., no messages from people I'm following on Twitter).  All I see is my profile image next to an input text box.  I can verify that there definitely should be messages when I login on the twitter.com website.  I also tried submitting a new message via the widget, which completed without any error message or authentication prompt...but nothing is actually sent to the twitter.com website.

I'm about to upgrade to 4.5.1...so we'll see if anything different happens there.

Ok, so upgrading to 4.5.1 didn't make a difference.  I figured maybe this was a problem with the user profile settings, so I created a new user, logged in as that user, and reconfigured the widget as usual.  I'm getting the same problem...not the authentication prompt, but a blank widget.  It seems to be accessing my account on Twitter successfully, as my profile image appears next to the text input box.

So perhaps this is a different bug than the original one we were discussing related to the repeated authentication prompt?  Maybe Twitter has changed the way they do things?

Twitter did indeed change the way they handle authentications, they disabled the access via api, applications have to use OAuth now, the microblogging widget propably didn't implement it yet.

See this for verification:
http://arstechnica.com/security/guides/2010/09/twitter-a-case-study-on-how-to-do-oauth-wrong.ars

What should the bug be changed to now?

I'm running trunk and get the same behavior as described on comment #6. The day before yesterday aseigo did a commit that fixed the issue of not getting the password from kwallet.

http://websvn.kde.org/?view=revision&revision=1171688

Now I'm experiencing the same issue as described above but not with twitter: I'm using identi.ca

Cheers,

The microblog dataengine does support OAuth. It has some code paths that disables that, but I'm not sure that's the case here. I'll need to take a look into the code.

I'm not sure (at least in my case) that it's an authentication issue anymore.  How else could it be getting my profile image for my Twitter account?  It seems to be a problem more specific to sending/receiving microblog updates.

FWIW, I've noticed today that Twitter now works again in the Microblogging plasma widget.  I haven't been checking frequently, so I don't know exactly when or what update (if any) fixed this.  Maybe it was just a temporary issue with Twitter's service.

Ok, so it seems that it was a combination of factors for this bug? Can someone confirm that it properly works with 4.5.1 so we can close the bug please?

Cheers,

I have a similar - if not the same problem: since Twitter required oauth, my uBlog widget is broken.

I am running 4.5.1 and I removed and added the widget multiple times and even removed the settings from the plasma rc file.

When running wireshark, Twitter replies with 401: Unauthorized. In the XML it said "Basic authentication is not supported" with error code 53.

Each time it tries to update I get a new authorisation dialog. Since I can see the traffic, I know the username and password are sent but it is not using oauth. Or is there some magic tick box that needs ticking to switch authentication modes?

Created attachment 53544 [details]
api request

Created attachment 53545 [details]
auth failed

Having this issue on 4.5.3, it happens usually if I restart. Today, it was working all day yesterday and some this morning and just randomly started popping up. I get this dialog box (see attached) and even though my credentials are correct and I tick remember me the authentication fails (see attached) and asks to cancel, retry. Cancel closes it out, retry is an endless loop. Removing it and reconfiguring it resolves but of course is an inconvenient solution.

Hi, can you try on a more recent version. I can't reproduce it in KDE 4.7.3

Cheers.

Please, feel free to reopen this report if you still experience this bug in a recent version of KDE :)