Bug 202578

Summary: KDEµBlog plasmoid shows only my own twitter messages
Product: [Unmaintained] plasma4 Reporter: Christian Muehlhaeuser <muesli>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aseigo, rdieter
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Christian Muehlhaeuser 2009-08-05 08:19:52 UTC 
Version:            (using KDE 4.3.0)
Installed from:    Ubuntu Packages

Not sure if this is really the right place for this bug-report, but for what it's worth, here we go:

I have just upgraded from KDE 4.2 to 4.3 (Kubuntu packages). Now the KDEµBlog plasmoid (twitter plasmoid) shows only my own messages (the once I've twittered). I've checked the settings dialog and "Show Friends" is checked.

I tried un-checking it, but this causes plasma to crash, as soon as I click the Ok button then. This should possibly be a separate bug-report.

Not changing anything in the settings dialog and pressing Ok doesn't crash plasma, but it makes the plasmoid look disabled and while it still shows my own messages in the background, there's now a "Configure..." button on top of them.

Conclusion: Twitter plasmoid seems broken, I expect it to show my friends messages, not my own messages. Pressing Ok after toggling "Show Friends" crashes plasma. Not changing anything and pressing the Ok button makes the plasmoid screw up its main view.
Comment 1 Aaron J. Seigo 2009-08-05 15:19:00 UTC 
the crashes, showing friends are all fixed in the branch and trunk in svn already.
Comment 2 Christian Muehlhaeuser 2009-09-02 00:52:12 UTC 
I just updated to Kubuntu's 4.3.1 packages and it's still only showing my own messages, and none of the messages that the people who I'm following are writing.

I keep this closed for a few more days to see if it's Kubuntu's packaging fault... Comments appreciated though ;-)
Comment 3 Rex Dieter 2009-09-30 21:25:15 UTC 

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