Public bug reported:
kdm should be started later, after Networking is up and Remote
Filesystems are also up.
Reason: in Enterprise environments a Desktop system is used by non-admin users.
After showing up the logon screen an successful logon of a user must be
possible.
Nearly all Linux Entrerprise Desktops are using IMHO NIS+NFS. So an user Logon
may show/usable after User Athorisation (NIS) and the User $HOME (normally
served as NFS) is avaible.
in /etc/init/kdm.conf should read as follow:
----- x----x----x----
[ ... ]
start on ((filesystem
and runlevel [!06]
and local-filesystems and remote-filesystems and net-device-up
and started dbus
and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1
or stopped udev-fallback-graphics))
or runlevel PREVLEVEL=S)
[...]
This closes here also Bug #599812 (NIS Problem).
BTW: It silences the Helpdesk lines dramatically ...
** Affects: kde-workspace (Ubuntu)
Importance: Undecided
Status: New
** Tags: kdm upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876399
Title:
kdm upstart profile
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/876399/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs