Carlos E. R. wrote:
On 10/02/2019 18.30, Richmond wrote:
Carlos E. R. wrote:
On 10/02/2019 08.10, Richmond wrote:
Darryl Gregorash wrote:
On 2019-02-09 08:54 PM, Carlos E. R. wrote:
On 09/02/2019 21.49, Richmond wrote: > Darryl Gregorash wrote: >> On 2019-02-09 01:21 PM, Richmond wrote: >>> yast2 configure display manager used to allow you to change the display >>> manager, but it no longer works, although the option is still there. >>> >>> Google tells me I must use: >>> >>> sudo update-alternatives --config default-displaymanager >>> >>> Why is the option still in Yast2 if it doesn't work? Why this change? >>> >>> >> Where are you trying to change this, the one in /etc/sysconfig-->Display >> manager, or the one in Miscellaneous/Alternatives? >> Note that you must have the yast2-alternative package installed (I >> thought it was installed by default?) for the second of these to be present. >> > I meant to say it is yast2 sysconfig. It takes you into a config editor > and the display manager is under "desktop" I think, also the window manager. Unfortunately, that module can display variables that no longer work.
How do you mean? It looks to me like it's only offering choices that are already installed on the system.
Well for example it has an option to change the display manager, which used to work, but no longer works, which is why I started this thread. Clearly someone has decided that there should be another way to change the display manager, but why? and why has this option been left there non-functioning, without any indication that it is non-functioning? You always had to reboot the computer for the change to work, or at least take it to rescue mode, so it would be very useful if the option actually called the new script to update the display manager. It is not an option, nor a choice, it is a variable in a config file, and the config file exists, but the variable is now ignored.
The file is "/etc/sysconfig/displaymanager" and the variable is "DISPLAYMANAGER":
## Path: Desktop/Display manager ## Description: settings to generate a proper displaymanager config ## Type: string(kdm,xdm,gdm,wdm,console) ## Default: "" ## Config: xdm,kdm,gdm # # Here you can set the default Display manager (kdm/xdm/gdm/wdm/console). #
The variable being there, then "yast2 sysconfig" shows it. I'd say that if you invent a new variable it will also be shown.
Yes, IMO something should have deleted or commented out the variable or add a comment on the section saying that it will not work.
The fact is, you have to use the "yast2 alternatives" or the "update-alternatives" command now.
I have edited the file like this:
## Path: Desktop/Display manager ## Description: settings to generate a proper displaymanager config DEPRECATED 0 ## Type: string(kdm,xdm,gdm,wdm,console) ## Default: "" ## Config: xdm,kdm,gdm # # Here you can set the default Display manager (kdm/xdm/gdm/wdm/console). DEPRECATED 1 # DISPLAYMANAGER="lightdm" ## Path: Desktop/Display manager ## Description: settings to generate a proper displaymanager config - DEPRECATED 2 ## Type: yesno ## Default: no # Tenía puesto kdmº # wdm no reconoce xfce como iniciable. # lightdm
And now YaST says that the variable is "DEPRECATED 1".
Is that just on your computer, or have you done it for the next release of opensuse? My computer, obviously.
Okay, so to ask my original question again, why was this change made? what was wrong with the original way of changing the display manager which worked for so long? There must be some advantage to the new way I guess, or it would not have been changed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org