Kubuntu: Very high reaction time

[etienner]

When desktop effects are enabled the system is very slow, it takes about 2 seconds to open a minimized window. This does not happen if they are not enabled.
The animation in krunner take about 3 seconds, independently from the desktop effects.

I'm using Ubuntu jaunty (development branch),

[lspci]
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon HD 3400 Series

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in compiz.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you gather some more information for this bug report using the command 'apport-collect 348475' in a terminal? Thanks in advance.

[etienner (etienner)]

Architecture: amd64
Dependencies:

DistroRelease: Ubuntu 9.04
NonfreeKernelModules: fglrx
Package: compiz None [modified: /var/lib/dpkg/info/compiz.list]
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev pulse-rt sambashare

[Bryce Harrington (bryce)]

Hi etienner,

Thanks for including the attached files. Could you also include your /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[etienner (etienner)]

Here is the requested Xorg.0.log
I'm now using a fresh instal of the released Kubuntu 9.04.
If the desktop effects are enabeled, the reaction time is still very high.

[Bryce Harrington (bryce)]

I've posted a new version of the -fglrx driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get fglrx 8.620 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[etienner (etienner)]

I've installed the fglrx driver, unfortunately it does not solve the issue. I attach again the xorg.0.log.

[etienner (etienner)]

I've installed the fglrx driver on Jaunty. Unfortunately it does not solve the issue. I attach again the xorg.0.log.

[Bryce Harrington (bryce)]

Hmm, well possibly this is not an -fglrx bug after all.

Fwiw, in Jaunty we saw some performance issues on other drivers, that were resolved by moving to the 2.6.30-rc2 (or newer) kernel, so that would be the next thing I'd recommend trying. There were also suspicion that the version of Qt included in Jaunty was causing some perf/corruption issues for Kubuntu users, so downgrading (or upgrading) that would be another option.

Otherwise, you can wait and retest on Karmic once we have the final -fglrx, xserver and kernel in place, probably in a month or two.

[etienner (etienner)]

Thanks. It would be grate if you add a post here once you have put the final fglrx driver in Keramic, so that I can test it.

[etienner (etienner)]

I'm now using 2.6.31-16-generic (kubuntu 9.10), and unfortunately this problem is still present.

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.