Maverick slow and flaky after first login

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.

The computer in question is currently on service for a network problem but I'll try the file system check once I get it back, probably in the middle of next week. As far as reinstalling is concerned, I've already done that once and it unfortunately didn't help.

If you did a complete reinstall, the file system should have been okay. Normally, if the file system has problems and you can reinstall, a complete fsck should have been done by the partitioner. I suspect the check then would become just a time waster for you.

Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

That's great! I'll await any further instructions. Do let me know in case more information or any actions are needed from my side.

Just to add some information, I've now tried to run the live CD of Natty Alpha 3 on my problem computer. It reverted to standard Gnome in stead of using Unity, and it was just as flaky as Maverick. Noteworthy, Natty Alpha 3 Live ran smoothly, with Unity, on my Sony Vaio laptop with AMD processor and ATI graphics.

Just wanted to say that I too experience this bug. I'll attach all things Lars attached in the morning.

Another note: After receiving the computer from service last Friday (due to a networking problem on both Win7 and Ubuntu), several major components have been exchanged; The MB is now a P7P55-M (no longer P7P55DE LX), the PSU has also been changed along with the DVD station and even the tower itself. What remains is the combination Core i5 + GTX460, and the memory chips are also the same. With all these changes, the problem still remains the same.

Today, I tried running PCLinuxOS 2010.12 from a live CD and discovered it had the same problem as Ubuntu. Since the PCLOS Live doesn't use autologon, I could log out without rebooting and log back on. The second time, things worked as they should whereas the first logon was slow and flaky just like in Maverick. PCLOS of course uses KDE and the X.org package was x11-server-xorg v1.65-2pclos2010. I just wanted to add this information in case it matters. It doesn't seem like a lot is happening otherwise.

Tried the Debian 6 Live CD today and no problems there. It uses xorg v1:7.5+8. Maverick uses v1:7.5+6ubuntu3.

Tried the recently released Natty beta live CD today. The problems remain, however. Natty beta has xorg 1:7.6~3ubuntu11 and linux kernel 2.6.38-7.

The Natty beta 2 live CD still has the same problem. I'm going to give Natty a final shot after its release but I can't say I'm very optimistic. The rest of the family now refuses to use Ubuntu on this computer and if the problem continues to receive what appears to be no attention at all (forgive me if I'm wrong), I'll have to look for another distro for this machine.

Today, I've tried a lot of different live CDs and it seems that one thing common to the distros that have the problem I've reported here is that they use xorg version 1:7.5. v1:7.4 or older seem to work well. The only exception to the rule so far is Debian 6 as mentioned in an earlier post. But Debian is Debian. Another distro that seems to work is Fedora 15 beta, using xorg 1.10-1-11fc15. Isn't the Natty release meant to have xorg 1:10 too?

Yesterday, I made a fresh install of Natty and sadly, the stability issues upon first logon after each boot remain the same. It makes no difference whether I log on to Unity, Classic, or Classic with no effects.

HOWEVER, I have now booted into recovery mode and as I write, I have thirteen (13) windows open each of Firefox and Opera! The window management is now flawless even though the low-graphics mode of course is no great joy on my 22-inch widescreen monitor. In the normal graphics mode, the first window of any program would have been unmovable and required Ctrl-Q to quit. More than a few tries, and the whole desktops would freeze.

Now that Natty is out the door, I wish somebody would have the time to look at this bug because right now. Ubuntu is not fully functional on this computer.

Almost two months with Natty, always keeping it up-to-date, and adding xorg-edgers fresh X crack PPA. Still no remedy for the problem. Today, I installed Linux 2.6.39-3 from the kernel PPA but that didn't help either. What's the status of this bug?

This is to confirm that this bug also exists in Oneiric alpha. Please adress it.

I tried out Oneiric Alpha 3 and still no change. I'm running Linux Mint Debian Edition alongside Ubuntu now and while that works perfectly, it really doesn't feel like home to me. Some action or at least some feedback would be much appreciated.

Would it be better if I reported a new bug about this on Natty or Oneiric? I guess Maverick bugs aren't really receiving a lot of attention anymore, or am I wrong?

This is posted from a Live CD session of the just received Oneiric beta. However, I had to log out and then back in to get control enough to do this. In other words, the reported bug still exists in Oneiric beta.

The problem still exists in the newly released Oneiric beta 2.

Please report a new bug from an Oneiric system (Live CD or install) about the linux package using the command 'ubuntu-bug linux' and set this bug report to Invalid. Thanks in advance.

Right. I might be waiting until the release first.

After Christmas, after way too long time, I was just about to follow the given recommendation and post a new bug on this issue when I realised that the computer all of a sudden had started to function properly after one year of problems. Failing to identify any recent updates that I'd expect to miraculously cure the box, I remembered that we'd just bought a new mouse for it. So I plugged in the old mouse again and rebooted, just to find the old problems had returned. I then connected a third mouse that we have in the household, rebooted again, and voila: problem gone again.

So the whole problem, mysteriously sticking with this computer through three versions of Ubuntu was all due to a bad mouse, admittedly a rather cheap one but nonetheless. It never crossed my mind but now, it makes all the more sense. So I guess this bug can be closed permanently now :-)

This bug report is being closed based on the original reporters comment above that it was caused by faulty hardware. Please continue to report valid bugs in the future.