Maverick slow and flaky after first login
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Shortly before Christmas, I bought a brand new gaming computer for dual-booting Win7 and Ubuntu. After testing the 64-bit Maverick live CD and finding it flaky, mildly put, I still opted to install it on a dedicated hard drive as planned. After enabling the proprietary Nvidia drivers installing the regular updates, adding the Ubuntu X-swat PPA and generally stretching both my patience and my imagination as far as I can, I'm left with one very annoying problem:
To start with, the first login after boot is notably slower than subsequent ones. I mention this because it might be related to the real problem, which is that the first time I've logged in after each boot, my desktop's multitasking capability seems to be gone. If I open a link from Gwibber or from an email, my browser opening will steal the focus entirely and I'm not able to switch between windows or even move any window (including the browser window) until the browser has been closed (sometimes requiring Ctrl-Q as I can't use the menus). Going on for a while, the whole desktop will eventually freeze. If left alone for sufficiently long, It might recognize my next command but at that point, I've usually lost my patience and restarted the machine (Ctr-Alt-Del strangely always works).
The only workaroyund I've found is to log in the first time after boot, then log out, then log in again. The second login is blistering fast and the desktop is super-responsive with no further problems. Very odd in my opinion.
I've tried to reinstall Ubuntu without any improvement. I've tried to run the 32-bit Live CD but it's just as flaky as the 64-bit. Linux Mint Live is just as flaky as Ubuntu, and Fedora 14 live doesn't even boot although it runs super-fast under Virtual Box (as does Ubuntu 10.10...) An old Xubuntu 9.04 Live CD is the first thing in my collection that boots without problems.
Is this all about having too shiny new hardware? I've got an Asus P7P55D-E LX motherboard, A Core i5 processor, and an Nvidia GTX460 graphics card. Anybody with similar experiences and perhaps a tip, please let me hear from you.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSign
Uname: Linux 2.6.35-25-generic x86_64
NonfreeKernelMo
.proc.driver.
.proc.driver.
.proc.driver.
NVRM version: NVIDIA UNIX x86_64 Kernel Module 270.18 Tue Jan 18 21:46:26 PST 2011
GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
Architecture: amd64
Date: Thu Feb 17 19:42:44 2011
DkmsStatus:
virtualbox-ose, 4.0.2, 2.6.35-25-generic, x86_64: installed
nvidia-current, 270.18, 2.6.35-24-generic, x86_64: installed
nvidia-current, 270.18, 2.6.35-25-generic, x86_64: installed
GdmLog:
Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/
sudo: 3 incorrect password attempts
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=sv_FI.utf8
SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 10/29/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1501
dmi.board.
dmi.board.name: P7P55D-E LX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
glxinfo: Error: [Errno 2] Filen eller katalogen finns inte
system:
distro: Ubuntu
codename: maverick
architecture: x86_64
kernel: 2.6.35-25-generic
Thank you for your report. This package failure looks like being caused by a corrupted file system. Please start the "Memory check" from the boot menu. If that runs successfully, please start the desktop cd. Hold right-shift key after the bios checks to get to the grub menu and run "Check disc for errors" option. If the file system corruption is serious, the safest option would be to reinstall your system. Please let us know by comment below if these checks report errors to you.