the Bug seems to persist on saucy (13.10) but i don't have a blinking
numlock.
furthermore, it seems like the goa-daemon comsumes 90-100% on a cpu for
every user that is logged in, therefore locking a cpu per user that is
logged in.
$ dpkg -l | grep gnome-settings-daemon
ii gnome-settings-daemo
Well, i think at least when it comes to my problems, handling this bug
is finished. looks like hardware defect, what wasn't obvious .
i added the -proposed sources as described and when i wanted to install
something with apt-get, i got an error while the installation was running.
readonly filesy
So, after a few days of further testing i'm convinced that the 3.8.0-29
version of the kernel still has some problems.
yesterday, i got the black screen with a blinking underscore again, but after
rebooting i got a screen with
"/ has to be checked for errors", done, automatic reboot, login worke
after reboot the filesystem was writeable again, not sure what caused
the error listed in dmesg, thus it doesn't make much sense trying the
other kernel, i think (if you meant me).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
So...i've had a similiar problem after updating from 3.8.0-27 to
3.8.0-29.
while booting i got a "general error mounting filesystems" with a prompt to
enter the root-pw for maintanance, which was frozen so i couldn't enter the
root pw. or do anything.
in contrary to your problem, the 3.8.0-27 ve
