google-code-export / microblog-purple

Automatically exported from code.google.com/p/microblog-purple
GNU General Public License v3.0
2 stars 0 forks source link

Tweetpocolypse! #116

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.  Log into twitter
2. wait
3. client then behaves erratically

The unique identifier associated to each tweet has now exceeded 2,147,483,6471

For some of your favorite third-party Twitter services not designed to
handle such a case, the sequence will suddenly turn into negative numbers.
At this point, they are very likely to malfunction or crash.

---

This is causing very odd behavior, such as trying to load every single
update into my history every <refresh interval>  and cause my client to
become unresponsive.

The end is nigh!

Original issue reported on code.google.com by ak.hep...@gmail.com on 13 Jun 2009 at 12:10

GoogleCodeExporter commented 9 years ago
I didn't know what the problem was, but I'm getting the same issue as well. All 
a
sudden Pidgin lags every time microblog refreshes Twitter and brings up the 
entire
history.

Original comment by kamigoro...@gmail.com on 13 Jun 2009 at 12:40

GoogleCodeExporter commented 9 years ago
Perhaps the priority should be high?  This bug makes the plugin all but 
useless.  

http://groups.google.com/group/twitter-development-talk/tree/browse_frm/thread/1
e97063bbf0f71a1/dbab1649df4e53be?rnum=1&_done=%2Fgroup%2Ftwitter-development-tal
k%2Fbrowse_frm%2Fthread%2F1e97063bbf0f71a1%3F&pli=1

Original comment by edwardah...@gmail.com on 13 Jun 2009 at 2:19

GoogleCodeExporter commented 9 years ago
Funny, I have the same problem... it's loading the same tweets repeatedly... had
heard about tweetpocalpyse happening and only just clicked that it could be 
what's
causing the problem. Hope it's an easy fix...

Original comment by deand...@gmail.com on 13 Jun 2009 at 10:43

GoogleCodeExporter commented 9 years ago
same problem here...

Original comment by junkca...@gmx.net on 13 Jun 2009 at 12:30

GoogleCodeExporter commented 9 years ago
Same problem here. I've been searching for a while trying to figure out what the
problem was but now it all makes sense. Pidgin was hanging for me on startup and
continues to hang whenever the account is re-enabled. Initially I had to 
uninstall
the plugin to get Pidgin to start up so I could disable the account before 
reinstalling.

Original comment by SilverSt...@gmail.com on 13 Jun 2009 at 1:03

GoogleCodeExporter commented 9 years ago
just in case this needs more confirmations...also I would say this bug should be
critical as opposed to just medium.

Original comment by franzdie...@gmail.com on 13 Jun 2009 at 3:36

GoogleCodeExporter commented 9 years ago
Issue 117 has been merged into this issue.

Original comment by somsaks on 13 Jun 2009 at 4:02

GoogleCodeExporter commented 9 years ago
Issue 118 has been merged into this issue.

Original comment by somsaks on 13 Jun 2009 at 4:03

GoogleCodeExporter commented 9 years ago
Oops! Oops! My bad it seems. Thanks for very quick report and follow up.

Change now commit into SVN, I will create bug fix release soon.

Original comment by somsaks on 13 Jun 2009 at 4:04

GoogleCodeExporter commented 9 years ago
Is the bug fix still on track for a release?

Original comment by themcla...@gmail.com on 14 Jun 2009 at 1:36

GoogleCodeExporter commented 9 years ago
Issue 119 has been merged into this issue.

Original comment by somsaks on 14 Jun 2009 at 3:09

GoogleCodeExporter commented 9 years ago
Issue 120 has been merged into this issue.

Original comment by somsaks on 14 Jun 2009 at 3:09

GoogleCodeExporter commented 9 years ago
Issue 121 has been merged into this issue.

Original comment by somsaks on 14 Jun 2009 at 3:09

GoogleCodeExporter commented 9 years ago
It'll be released very soon.

Original comment by somsaks on 14 Jun 2009 at 7:29

GoogleCodeExporter commented 9 years ago
Is there a twitter feed we can subscribe to to be informed of new releases?

Original comment by peter.sc...@gmail.com on 14 Jun 2009 at 9:55

GoogleCodeExporter commented 9 years ago
@peter.scully IMHO, the better way is to create a permanently open issue (here 
at
code google) for informing about releases, you only had to maintain suscribed 
to it.

The facebookchat plugin people do in this way and I'm really surprised how 
trivial
and how well fit in my way to wrok.

Original comment by ismael.olea on 14 Jun 2009 at 12:31

GoogleCodeExporter commented 9 years ago
Seems a new release was created, which is awesome, though I was kinda expecting 
a 
message to pop up on here saying so.
Also - doesn't work with Pidgin Portable... "can't find pidgin installation".

Original comment by deand...@gmail.com on 14 Jun 2009 at 3:38

GoogleCodeExporter commented 9 years ago
Has it been verified that the new version addresses this issue? I'm continuing 
to
experience problems and I'm not sure if it's just me or not.

Original comment by SilverSt...@gmail.com on 15 Jun 2009 at 12:54

GoogleCodeExporter commented 9 years ago
Seems to work on me though. The refresh bug doesn't occur anymore and I'm not 
getting
the certificate popup at all.

Thanks for the quick fix!

Original comment by kamigoro...@gmail.com on 15 Jun 2009 at 12:59

GoogleCodeExporter commented 9 years ago
FYI, the ubuntu instructions pointed to on the front page still distribute .21, 
not
.22.  

Original comment by themcla...@gmail.com on 15 Jun 2009 at 1:11

GoogleCodeExporter commented 9 years ago
Sorry, I should post here that the new version is now available. Please help 
verify it.

Ubuntu update will be available soon. For the time being, please feel free use 
source
distro instead.

@peter thanks for idea. that's awesome.

Original comment by somsaks on 15 Jun 2009 at 1:31

GoogleCodeExporter commented 9 years ago
Even after installing this update, I am seeing Pidgin completely hang as soon 
as my
TwitterIM account is enabled. After ending the process and restarting Pidgin, 
the
account is no longer enabled and everything is fine. Re-enable Twitter, and
everything breaks again. Because this seemed to coincide exactly with the
"Twitpocolypse" I thought that was the problem, but if this fix worked for 
everybody
else I'm completely thrown off.

Original comment by SilverSt...@gmail.com on 15 Jun 2009 at 2:07

GoogleCodeExporter commented 9 years ago
0.2.2 has been commited to Fedora to the stable updates:
http://koji.fedoraproject.org/koji/packageinfo?packageID=6812

Original comment by ismael.olea on 15 Jun 2009 at 6:39

GoogleCodeExporter commented 9 years ago
@SilverSteelWolf could you attach debugging log? Run "pidgin -d > debug.log" 
and send
us the debugging log. 

Also, don't sure if this is the cause, but I accidentally uploaded a broken 
version
of source for a short while (about 10 minutes), I noticed that then delete the
uploaded file. I would suggest you to re-download the code and try again.

Original comment by somsaks on 15 Jun 2009 at 10:17

GoogleCodeExporter commented 9 years ago
Attaching debugging log; this is everything that occurs after I activate the 
Twitter
account from the menu.

Original comment by SilverSt...@gmail.com on 15 Jun 2009 at 10:57

Attachments:

GoogleCodeExporter commented 9 years ago
Same with me. Installed the 0.2.2 release this morning and still got the crash. 
Took
me killing off Pidgin like 3 times just to get to the point at which I could 
actually
use the menus and disable the TwitterIM account.

Original comment by adida...@gmail.com on 15 Jun 2009 at 1:41

GoogleCodeExporter commented 9 years ago
Just to make sure, but could you send your ~/.purple/accounts.xml to us? If you 
are
using windows, it will be in c:\Users\<User name>\AppData\Roaming/.purple.

Original comment by somsaks on 15 Jun 2009 at 2:12

GoogleCodeExporter commented 9 years ago
I'm attaching the accounts section for my TwitterIM account. If you need more, 
let me
know.

On WinXP it's actually located here (at least for me it was):

C:\Documents and Settings\<User Name>\Application Data\.purple\

Original comment by adida...@gmail.com on 15 Jun 2009 at 4:02

Attachments:

GoogleCodeExporter commented 9 years ago
.2.2.1 out of the repository on ubuntu still seems broke. same behaviour.  On a 
side
note, I am unable to compile the source because make is unable to find -lpurple 
(yup,
purple-dev and pidgin-dev are installed) . I had read something about libraries 
not
matching causing this compile time issue, perhaps this fix isn't working 
because I
have a mismatch somewhere?

Original comment by themcla...@gmail.com on 15 Jun 2009 at 5:36

GoogleCodeExporter commented 9 years ago
We have succes! 
mv .purple/ purple.bak
sudo apt-get remove pidgin-microblog
sudo apt-get remove pidgin
sudo apt-get remove libpurple-dev
sudo apt-get remove libpurple0
sudo apt-get update
sudo apt-get install pidgin
sudo apt-get install pidgin-microblog

Original comment by themcla...@gmail.com on 15 Jun 2009 at 6:00

GoogleCodeExporter commented 9 years ago
It seems that version 0.2.2 has fixed the problem, but I was wondering when the 
the
Portable Apps - friendly version will be released?

Original comment by tstod...@gmail.com on 15 Jun 2009 at 8:28

GoogleCodeExporter commented 9 years ago
Seems like adidalax and I are experiencing the same issue, but we're on WinXP.

Original comment by SilverSt...@gmail.com on 16 Jun 2009 at 1:18

GoogleCodeExporter commented 9 years ago
I have the same problem as SilverSteelWolf and adidalax, on Ubuntu 9.04, 
compiled
from the latest source.

Original comment by dvpdiner2 on 16 Jun 2009 at 1:32

GoogleCodeExporter commented 9 years ago
@adidalax your accounts.xml seems ok, nothing weird in the configuration. (I 
asked
because once I had problem when something unusual was presented in 
accounts.xml, I
think I fixed that but maybe I overlooked something).

@SilverSteelWolf is it crash at the same place when you run in debugging mode? 
The
last line of the debug.log shown that it crash after Trillian log reader. What 
did
the Trillian log reader do?

Also, please make sure to remove the old plug-in before installing new one.

1. Stop Pidgin
2. Uninstall the old plug-in (either from Add/Remove program or apt-get remove 
or
make uninstall)
3. compile & install new one

Original comment by somsaks on 16 Jun 2009 at 5:03

GoogleCodeExporter commented 9 years ago
It always crashes with the same behavior: activating the TwitterIM account. 
With the
log reader plugin disabled, the last point in the log is:

g_log: pidgin_conv_get_window: assertion 'gtkconv != NULL' failed
g_log: pidgin_conv_get_window: assertion 'gtkconv != NULL' failed

Twice like that, and then Pidgin is completely unusable until I kill the 
process and
restart.

Original comment by SilverSt...@gmail.com on 16 Jun 2009 at 10:55

GoogleCodeExporter commented 9 years ago
@silverSteelWolf can you try disabling Twitgin? the last few gtkconv suggest me 
that
the bug relies in Twitgin.

Original comment by somsaks on 16 Jun 2009 at 11:13

GoogleCodeExporter commented 9 years ago
I get the same issue with or without Twitgin enabled, also ending with the g_log
errors. As you probably saw in my earlier attachment, all of the tweets seem to 
have
been retrieved (at least, they're all visible in the log). 

Original comment by SilverSt...@gmail.com on 16 Jun 2009 at 11:34

GoogleCodeExporter commented 9 years ago
@SilverSteelWolf yes, that's why I think twitgin might be the cause, since 
Twitgin is
the one doing work after Twitter plug-in. From the log, it seems that it's 
already
left Twitter plug-in scope.

To make sure that Twitgin is not really intercepting the message anymore, please
check your .purple/prefs.xml, look for <pref name='plugins'> and make sure 
there is
no "twitgin" listed in <pref name='loaded'> section.

Original comment by somsaks on 16 Jun 2009 at 11:50

GoogleCodeExporter commented 9 years ago
Well, I was able to verify that twitgin wasn't listed among the loaded plugins. 
I was
hoping to avoid this but it sounds like I should try just uninstalling 
everything
Pidgin and starting over. Seems to have worked for #30.

Original comment by SilverSt...@gmail.com on 17 Jun 2009 at 11:19

GoogleCodeExporter commented 9 years ago
I just got the 0.2.2 update for Fedora via yum this morning. It didn't exactly 
get
things working again. What happens now is that Pidgin freezes during startup 
and CPU
utilization goes to 100%. Even after waiting 10 minutes, Pidgin never completes
startup, so I can't disable the microblog plugin from the account or tools 
menu. Any
suggestions?

Original comment by steevit...@gmail.com on 18 Jun 2009 at 4:07

GoogleCodeExporter commented 9 years ago
@steevithak

I've been using it without any trouble. Maybe you should trace it and look for 
any
kind of error reporting or suspecting message.

Original comment by ismael.olea on 18 Jun 2009 at 4:12

GoogleCodeExporter commented 9 years ago
This is the kind of behavior I've been experiencing, although I don't get the 
high CPU usage. When you can do to 
save Pidgin in the meantime is just uninstall microblog, then disable the 
now-unknown account. You can now 
reinstall microblog and enable the account from Pidgin at your leisure to test 
if it works. When it freezes and you 
restart Pidgin, the account will revert to disabled and Pidgin should start up 
fine.

Original comment by SilverSt...@gmail.com on 18 Jun 2009 at 4:13

GoogleCodeExporter commented 9 years ago
Update: I was incorrect in blaming the microblog plugin update for the troubles.
Turns out it was the Pidgin/yahoo connection bug which hit this morning. Once I 
added
the work around for the Yahoo issue and restarted, everything seems to be 
working
fine with the microblog plugin. Here's a link to the Yahoo issue: 

 http://developer.pidgin.im/ticket/9386

Original comment by steevit...@gmail.com on 18 Jun 2009 at 5:44

GoogleCodeExporter commented 9 years ago
Just wanted to add my thanks.   I've had no issues with this since the release 
of 0.22.

Original comment by ak.hep...@gmail.com on 18 Jun 2009 at 6:01

GoogleCodeExporter commented 9 years ago
Uninstalled/reinstalled Pidgin and plugins with no change in behavior. Pidgin 
still
hangs immediately upon activating the TwitterIM account. Would it be advisable 
to try
and clear out my user data (accounts, preferences) and try again?

Original comment by SilverSt...@gmail.com on 18 Jun 2009 at 9:36

GoogleCodeExporter commented 9 years ago
@SilverSteelWolf make a backup copy of your .purple, then remove the whole 
directory,
uninstall both MBPurple and Pidgin, then reinstall again. Let me know if this 
works
for you.

Original comment by somsaks on 19 Jun 2009 at 4:05

GoogleCodeExporter commented 9 years ago
Uninstalled Pidgin, backed up and cleared contents of .purple folder, 
reinstalled
Pidgin and microblog. Everything works great now - thanks for your patience.

Original comment by SilverSt...@gmail.com on 23 Jun 2009 at 11:10

GoogleCodeExporter commented 9 years ago
One other follow-up: It appears that what was causing the problem was my twitter
conversation log and the History plugin that shows previous conversations in 
new IM
windows. I've cleared out that particular log only and it seems to have solved
things. Too bad I didn't realize this before having to reset all of my 
preferences. :P

Original comment by SilverSt...@gmail.com on 23 Jun 2009 at 11:31

GoogleCodeExporter commented 9 years ago

Original comment by somsaks on 26 Aug 2009 at 6:35

GoogleCodeExporter commented 9 years ago
This started happening to me earlier this week.  I've tried the uninstall 
reinstall
along with wiping out my .purple.  Nothing seems to work as the twitter plug-in
continually downloads from twitter.  It seems to always download 197 tweets as 
well,
I don't know if that number has any significance.  I've also upgraded to 0.23 
of the
MB plug-in and that doesn't seem to have made any difference.  Any new ideas?

Original comment by lerner.s...@gmail.com on 25 Sep 2009 at 11:58