Lagging response and frequent application freezes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xorg
I am getting lagging responses from half my mouse movements and keyboard interactions, and often application windows will freeze for anything from a few moments up to a few minutes at a time. It doesn't matter what application it is, be it Thunderbird, Firefox, or even gedit.
I've tried using the non-nvidia non-propriety drivers, and both the available nvidia drives with no help. I even tried to install drivers from nvidia.com, but it wouldn't install easily.
Please let me know what extra information I can provide to help debug this issue.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSign
Uname: Linux 2.6.35-24-generic x86_64
NonfreeKernelMo
.proc.driver.
NVRM version: NVIDIA UNIX x86_64 Kernel Module 260.19.06 Mon Sep 13 04:29:19 PDT 2010
GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
Architecture: amd64
Date: Sun Jan 9 21:08:01 2011
DkmsStatus: nvidia-current, 260.19.06, 2.6.35-24-generic, x86_64: installed
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 12/28/2004
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6
dmi.board.name: NF-CK804
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardSof
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: maverick
architecture: x86_64
kernel: 2.6.35-24-generic
affects: | xorg (Ubuntu) → nvidia-graphics-drivers (Ubuntu) |
Hey Stephen,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect <bug-number>
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run this right after reproducing the problem.)