Description of problem: On F11 using pidgin, libpurple, and microblog, the twitter chat window opens every few seconds even though there is no new tweet. If closed, it reopens a few seconds later. If left open, it start flashing on the task bar after a few second indicating a new message, even though none has arrived. Version-Release number of selected component (if applicable): pidgin-2.5.6-1.fc11.i586.rpm libpurple-2.5.6-1.fc11.i586.rpm purple-microblog-0.2.1-1.fc11.ir86.rpm How reproducible: always Steps to Reproduce: 1. Install Fedora 11, including pidgin, and microblog 2. add a twitter account 3. minimze pidgin and wait a few seconds Actual results: a chat window opens for twitter even though there is no new tweet. Close the window and it opens again in a few seconds. There seems to be no way to make it go away. If you try to minimize it, it will start flashing on the task bar, display weird numerical codes. Expected results: Normally, I start and minimize pidgin. If an IM, including a tweet, arrives, pidgin opens a chat window displaying the new message. When there is no new IM or tweet, pidgin stay quiet and minimized. Additional info: This may or may not be significant but the chat widow title in the status bar includes some numerical codes in brackets each time it appears or refreshes. This never occurred when I was using pidgin and microblog on Fedora 10. Often several codes appear sequentially but too fast to see. Here are a few that recur frequently: [200] twitter [272] twitter [400] twitter [404] twitter [600] twitter [800] twitter [915] twitter [974] twitter [1600] twitter I have also file a bug with on microblog site: http://code.google.com/p/microblog-purple/issues/detail?id=117
I confirm the same happen in F10. Seems it's a consecuence of the infamous twitpocalypse: http://www.twitpocalypse.com/ So, I'll wait to the upstream fix.
Released bugfix version 0.2.2: http://koji.fedoraproject.org/koji/packageinfo?packageID=6812
purple-microblog-0.2.2-1.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/purple-microblog-0.2.2-1.fc10
purple-microblog-0.2.2-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/purple-microblog-0.2.2-1.fc11
purple-microblog-0.2.2-1.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/purple-microblog-0.2.2-1.fc9
*** Bug 506452 has been marked as a duplicate of this bug. ***
purple-microblog-0.2.2-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
purple-microblog-0.2.2-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
purple-microblog-0.2.2-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
Hmmm... just got the 0.2.2-1 update via yum but it didn't have the expected effect. After rebooting, I tried to start pidgin. It gets about halfway through the startup, to the point it displays the UI showing that it's logging into to all the networks, then it freezes and CPU utilization goes to 100%. I waited about 10 minutes but it never unfroze and I had to kill it. Is there a way to turn off the pidgin plugin without being able to access the accounts menu in pidgin?
@srainwater I'm experience the plugin runs smoothly, anyhow I'll try some test. About your question, you can edit ~/.purple/prefs.xml or can launch pidgin with the -n option for not to connect any protocol. Then you'll be able of doing tests or changes using the GUI.
sorry, please disregard my previous post. I was seeing the unrelated yahoo connection bug which hit this morning. It was just a coincidence that it happened at the same time I installed the microblug plugin. Once I added the work around for the Yahoo bug, everything is working great. So the microblog update seems to be working correctly. Here's a link to the Yahoo bug in case anyone else is suffering from the same problem: http://developer.pidgin.im/ticket/9386