Public bug reported:
When the nis server is not reachable during start up (e.g. cable not
connected, network not reachable, ...) an error with HAL (hardware
abstraction layer) is raised and system gets incredibly slow.
First during boot it fails to connect to ypbind server (expected behaviour int
his case).
(see first screenshot)
After that the boot process and start of gdm gets incredibly slow (two
or more minutes). Login as local user is possible (although lasting
several minutes, again very slow), then GNOME settings manager raises an
error. (see second screenshot)
After confirming, the following error message is raised after two or more
minutes:
--------------
Internal error - failed to initialize HAL!
--------------
(see third screenshot)
I assigned this bug to package 'nis' although I'm not sure if this is really a
nis issue but an issue with the init process.
Error can be reproduced inside a virtual machine (e.g. virtualbox) with virtual
network cable not connected.
** Affects: nis (Ubuntu)
Importance: Undecided
Status: New
** Tags: autofs hal nis ypbind
--
When nis server is not reachable during startup, system gets very slow and HAL
fails to initialise
https://bugs.launchpad.net/bugs/252499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
