telepathy-idle runs up to 100 % cpu usage

Bug #1042659 reported by Xwarman
90
This bug affects 19 people
Affects Status Importance Assigned to Milestone
telepathy-idle (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

On my pc telepathy-idle runs up to near 100 % cpu usage permanently. I have a proxy server configured from time to time. That proxy block every port for IMs i have in use. If Empathy is runnig and tryes to connect via that proxy, conneciton fails and telepahty runs up.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: telepathy-idle 0.1.11-2
ProcVersionSignature: Ubuntu 3.2.0-30.47-generic 3.2.27
Uname: Linux 3.2.0-30-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
Date: Tue Aug 28 11:18:27 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: telepathy-idle
UpgradeStatus: Upgraded to precise on 2012-04-13 (136 days ago)

Revision history for this message
Xwarman (xwarman) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in telepathy-idle (Ubuntu):
status: New → Confirmed
Revision history for this message
vak (khamenya) wrote :

"This should have been fixed in 0.1.12-1"
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659306

Revision history for this message
Rick Fowler (ricklfowler) wrote :

This issues appears to have returned in 13.04 with telepathy-idle version 0.1.14-1.

Revision history for this message
Luke Hoersten (lukehoersten) wrote :

I'm having this issue in 13.04 as well.

Revision history for this message
Forage (forage) wrote :

Same here

Revision history for this message
BenJ (ben-jolitz) wrote :

I got this today after IRC failed to log in when I resumed.

Had to use kill on it.

Revision history for this message
Andreas Schildbach (schildbach) wrote :

I also think it has got to do with IRC not being able to log in.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.