x2goclient using high cpu
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
x2goclient (Debian) |
Fix Released
|
Unknown
|
|||
x2goclient (Ubuntu) |
Fix Released
|
High
|
Reinhard Tartler | ||
Trusty |
Fix Released
|
High
|
Reinhard Tartler | ||
Utopic |
Fix Released
|
High
|
Reinhard Tartler |
Bug Description
[Impact]
* x2goclient is polling on the X11 connection socket, taking one CPU to 100% utilization
* Wasting lots of battery power
* Affects the general use of x2goclient
[Test Case]
* Connect to a remote x2go server (no special settings required to trigger this bug)
* Check CPU usage with top/htop/similar
[Regression Potential]
* None Known
Original report follows:
x2goclient using high cpu
# top
top - 16:36:06 up 7:41, 3 users, load average: 2.59, 2.03, 1.21
Tasks: 218 total, 1 running, 217 sleeping, 0 stopped, 0 zombie
%Cpu(s): 35.3 us, 21.4 sy, 0.0 ni, 42.9 id, 0.2 wa, 0.1 hi, 0.0 si, 0.0 st
KiB Mem: 8010800 total, 4088948 used, 3921852 free, 298072 buffers
KiB Swap: 4303372 total, 0 used, 4303372 free. 2214540 cached Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
21155 ukokiku 20 0 600848 37712 24612 S 200.9 0.5 18:01.83 x2goclient
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: x2goclient 4.0.1.1-1
ProcVersionSign
Uname: Linux 3.13.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
Date: Thu Mar 6 16:31:49 2014
InstallationDate: Installed on 2013-11-29 (97 days ago)
InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: x2goclient
UpgradeStatus: Upgraded to trusty on 2014-02-28 (5 days ago)
Related branches
CVE References
Changed in x2goclient (Debian): | |
status: | Unknown → New |
description: | updated |
Changed in x2goclient (Ubuntu Utopic): | |
assignee: | nobody → Reinhard Tartler (siretart) |
Changed in x2goclient (Ubuntu Trusty): | |
assignee: | nobody → Reinhard Tartler (siretart) |
Changed in x2goclient (Debian): | |
status: | New → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.