Bug 178415 - Twitter applet displays unusable KIO password dialogs when entered password is invalid
Summary: Twitter applet displays unusable KIO password dialogs when entered password i...
Status: RESOLVED DUPLICATE of bug 177234
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-microblogging (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-21 23:39 UTC by Diederik van der Boor
Modified: 2008-12-23 23:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Diederik van der Boor 2008-12-21 23:39:57 UTC
Version:           onbekend (using 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2)) "release 3.1", KDE:KDE4:UNSTABLE:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (i686) release 2.6.27.7-9-pae

The twitter applet gives some weird behavior if your entered password is invalid.

Example:
- add the twitter applet to the desktop
- open the preferences
- configure the account, add an incorrect password.

Now, the twitter applet will spawn a KIO password dialog. This dialog does not allow you to enter your user name. After a second failed attempt, the next dialog does allow you to enter the username + password.

The next time the twitter engine makes a request, this problem starts all over again until the password is set properly in the preferences dialog.
Comment 1 FiNeX 2008-12-21 23:48:11 UTC
I've had the same problem on konqueror, probably a kdelibs bug.

*** This bug has been marked as a duplicate of bug 177234 ***
Comment 2 Diederik van der Boor 2008-12-23 23:21:12 UTC
hmm., these seam to be separate issues:
- kdelibs has a bug with password dialogs.
- twitter applet does not update it's password in the settings if you enter the correct password in the KIO dialog.

should this bug be reopened?