Mailinglist Archive: yast-devel (100 mails)

< Previous Next >
Re: [yast-devel] Re: [opensuse-factory] Replacement proposal for the current display-manager.service
  • From: Ancor Gonzalez Sosa <ancor@xxxxxxx>
  • Date: Tue, 27 Jan 2015 10:50:39 +0100
  • Message-id: <54C75F6F.5020302@suse.de>
On 01/27/2015 10:21 AM, Guido Berhoerster wrote:
* Raymond Wooninck <tittiatcoke@xxxxxxxxx> [2015-01-27 09:56]:
On Tuesday 27 January 2015 09:44:36 Guido Berhoerster wrote:

I don't think it is much of an improvement configuring display
manager behavior through /etc/sysconfig/displaymanager while
having to select the actual display manager through some other
mechanism like update-alternatives.

The question is if those settings in /etc/sysconfig/displaymanager are still
really affecting the how the display manager works. I know that GDM and KDM
a
lot of their settings are no longer controlled by YaST, but through their
respective configuration managers. (e.g. Most of the KDM settings are now
controlled by the KDE systemsettings)

So this would be a good opportunity to really look how and where we want to
configure our display managers and have a final cleanup of these settings.

LightDM reads DISPLAYMANAGER_AUTOLOGIN,
DISPLAYMANAGER_PASSWORD_LESS_LOGIN, DISPLAYMANAGER_REMOTE_ACCESS,
DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN, DEFAULT_WM. GDM reads
DISPLAYMANAGER_AUTOLOGIN,
DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN, and
DISPLAYMANAGER_AUTOLOGIN. LXDM reads DISPLAYMANAGER_AUTOLOGIN and
DEFAULT_WM. With the rest I'm not familiar.

The same information for KDM can be found in the comments of this bug
report (credits to Wolfgang Bauer)
https://bugzilla.suse.com/show_bug.cgi?id=907907

Cheers.

--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >