Public bug reported:
After rebooting into the new kernel I found that the clock was gaining
about 25 seconds per hour, too fast for ntpd to correct it. Reverting
to the previous kernel makes the problem go away.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-35-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900943
Title:
System clock runs fast in kernel 2.6.32-36
To manage notifications about this bug go to:
NB that in the bug description it says linux-image-2.6.32-35-generic -
this kernel is fine. It is 2.6.32-36 that has the problem.
** Attachment removed: AlsaDevices.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/900943/+attachment/2622211/+files/AlsaDevices.txt
--
You received
On 06/12/11 22:58, Brad Figg wrote:
@Dom,
There is a new Lucid kernel in -proposed. Can you enable proposed; run
update manager; select the new kernel (2.6.32-37.81) and install that.
If that still shows the problem, I'd like to work with you on
identifying which comment caused this
I see it got unmarked as a security bug. If I may try to re-explain why
I think it *is* a bug. Firstly, many VNC users set very weak passwords
(e.g. 'password') because they are using it internally behind a
firewall, and anyone with physical access to one machine has physical
access to the other
Dell Latitude C400 here, got the same with Ubuntu 10.04 and before that
Ubuntu 9.04. Specifically, after booting, and logging in the first
time, there is no mouse pointer. If I lock the screen (by leaving it
idle for a while or by finding the lock screen widget that I've set up
for this purpose)
Hi Marc, I am the original user. Thanks to Alan for filing the bug
report. I'll clarify a couple of things. The machine (running Ubuntu
9.04) is on a typical domestic 192.168.1.x network, and *does* have
internet access via a typical domestic Comtrend router. The router is
not configured to
Alan,
your comment went in while I was writing the above. Hope it's cleared things
up a bit. There seem to be two issues here with Network Manager:
1. It doesn't play nicely with hard-coded interfaces in /etc/network/interfaces
2. If eth1 (for example) gets reassigned from a wired interface to
