Input lag in Konsole (karmic)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdebase (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: konsole
Hi everyone,
I'm seeing some extreme input lag in Konsole (4:4.3.2-0ubuntu3) in Karmic. Other apps are not affected, and input speed is fine in virtual terminals. This does not happen each time you start Konsole, for example after a reboot input speed is fine. However, invariably, after the system is up for a few hours, this input lag shows up. It is not an insignificant amount of lag, and it essentially renders Konsole unusable for input and requires a reboot. This started almost immeadiatly upon this fresh install.
Desktop effects are not enabled. This is running in VIrtualBox ver 3.1.4 (latest)
I have seen similar bugs, such as:
https:/
However that bug seems more related to ACPI issues and the acer-wmi kernel module, which are not applicable in my case. I am seeing nothing logged in /var/log/messages at all, and no messages from Konsole. It also never actually crashes, so no crash report is available.
I've also tried starting konsole with:
konsole --notransparency
konsole -graphicssystem raster
I would really appreciate any suggestions as to how to further debug this issue as rebooting this workstation every time Konsole slows down is not that great.
Thank you,
Pete
ProblemType: Bug
Architecture: i386
Date: Sun Mar 21 09:15:39 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kdeinit4
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: kdelibs-bin 4:4.3.2-0ubuntu7.2
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: kde4libs
Uname: Linux 2.6.31-20-generic i686
XsessionErrors: (polkit-
Changed in kdebase (Ubuntu): | |
status: | New → Fix Released |
I installed kdelibs5-dbg kdebase-dbg libx11-6-dbg libxrender1-dbg and attached to a running console instance with gdb, but that seems to cause the instance attached to display a blank screen, so you can no then really use it for input or see what is occurring. However, this bug affects all running instances, so if I get anything useful in gdb I'll post it.