pidgin uses all idle CPU time, and frequent lock ups if gtalk password is incorrect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pidgin (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Pidgin (1:2.4.
gettimeofday(
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=10, events=
recv(45, "", 5, 0) = 0
read(3, 0x8130bd4, 4096) = -1 EAGAIN (Resource temporarily unavailable)
in an endless loop. There were similar bug reports before, but now it is almost a constant problem not allow pidgin to be used more than some seconds ... I don't know which upgrade made things even worse than before, because I was on vacation for a long time not upgrading things for a while.
Sometimes it's even not possible to simply kill pidgin with "kill" command, just with signal 9.
description: | updated |
Sorry, I've just realized that it is maybe because of my modified password on gmail.com, it seems the problem is caused when pidgin tries to connect to gmail.com. Though, I think it is still a bug, because it should be reported as wrong password or something and not with a behaviour like the one I've reported. Pidgin sometimes reported "read error", instead of wrong password.
Should I modify my bug report to reflect the change of my problem?