[opensuse] yast2 configure display manager
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? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Richmond composed on 2019-02-09 19:21 (UTC):
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?
My guess is whoever added yast2 alternatives might have felt there should be an overlap period before removing the deprecated selection, and for testing that related branches were all found and adjusted accordingly, so remains on someone's todo list. If you were to bring this up on the yast-devel list you might get a better answer, maybe a fix, or be asked to file a bug. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/09/2019 01:47 PM, Felix Miata wrote:
If you were to bring this up on the yast-devel list you might get a better answer, maybe a fix, or be asked to file a bug.
There is one of those too? I've lost count... (which is a negative side-effect of list fragmentation, the likelihood of an additional subscription to post to another list to report the same thing already reported decreases dramatically) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin composed on 2019-02-10 03:17 (UTC-0600):
Felix Miata wrote:
If you were to bring this up on the yast-devel list you might get a better answer, maybe a fix, or be asked to file a bug.
There is one of those too? I've lost count...
The problem with that particular list I think is that its subscribers don't know about any other lists, much less pay any attention to them. Then again, /this/ list is not a support list, or is it? We have opensuse-support for "support" now, if it can determined how to tell the difference between "openSUSE support", "Generic questions and User to User support" and completely off-topic.
(which is a negative side-effect of list fragmentation, the likelihood of an additional subscription to post to another list to report the same thing already reported decreases dramatically)
This is true. Just like gummints. Too many rules for anyone to keep track of them all, much less deal with obeyance. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-02-09 02:49 PM, 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.
OK, make sure yast2-alternatives is installed, and try using Miscellaneous/Alternatives. That method is mentioned in https://en.opensuse.org/SDB:Change_Display_Manager Note that the information for Leap 15.0 is down the page a bit. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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". -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
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? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
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
On 11/02/2019 13.13, Richmond wrote:
Carlos E. R. wrote:
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.
I believe it is an upstream change. Dunno. There are several subsystems in Linux that use update-alternatives to choose, well, alternatives. It is the consistent method. And the change has been documented: <https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.0/index.html#general> 5.2 Use update-alternatives to Set Login Manager and Desktop Session In the past, you could use /etc/sysconfig or the YaST module /etc/sysconfig Editor to define the login manager and desktop session. Starting with openSUSE Leap 15.0, the values are not defined using /etc/sysconfig anymore but with the alternatives system. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On Mon, 11 Feb 2019 21:26:01 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 11/02/2019 13.13, Richmond wrote:
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.
I believe it is an upstream change. Dunno. There are several subsystems in Linux that use update-alternatives to choose, well, alternatives. It is the consistent method.
And the change has been documented:
<https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.0/index.html#general>
5.2 Use update-alternatives to Set Login Manager and Desktop Session
Well that's fine if you know that a 'login manager' is the same thing as a 'display manager' :(
In the past, you could use /etc/sysconfig or the YaST module /etc/sysconfig Editor to define the login manager and desktop session. Starting with openSUSE Leap 15.0, the values are not defined using /etc/sysconfig anymore but with the alternatives system.
Since everybody else seems to be just rabbiting on, I've opened https://bugzilla.opensuse.org/show_bug.cgi?id=1125040 Maybe somebody would like to confirm it. :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/02/2019 21.53, Dave Howorth wrote:
On Mon, 11 Feb 2019 21:26:01 +010 "Carlos E. R." <> wrote:
On 11/02/2019 13.13, Richmond wrote:
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.
I believe it is an upstream change. Dunno. There are several subsystems in Linux that use update-alternatives to choose, well, alternatives. It is the consistent method.
And the change has been documented:
<https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/15.0/index.html#general>
5.2 Use update-alternatives to Set Login Manager and Desktop Session
Well that's fine if you know that a 'login manager' is the same thing as a 'display manager' :(
Good catch. Report documentation bug in bugzilla :-)
In the past, you could use /etc/sysconfig or the YaST module /etc/sysconfig Editor to define the login manager and desktop session. Starting with openSUSE Leap 15.0, the values are not defined using /etc/sysconfig anymore but with the alternatives system.
Since everybody else seems to be just rabbiting on, I've opened https://bugzilla.opensuse.org/show_bug.cgi?id=1125040
Maybe somebody would like to confirm it. :)
Ah, you did mention the doc issue. :-) But that will probably have to be reported separately. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))
On Sun, 10 Feb 2019 11:32:37 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
And now YaST says that the variable is "DEPRECATED 1".
That#s the wrong word to choose. Deprecated implies that it still works but will not work at some future time. That's what should have been there before. Now it should say something like "Obsolete. See ... instead." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/02/2019 20.46, Dave Howorth wrote:
On Sun, 10 Feb 2019 11:32:37 +0100 "Carlos E. R." <> wrote:
And now YaST says that the variable is "DEPRECATED 1".
That#s the wrong word to choose. Deprecated implies that it still works but will not work at some future time. That's what should have been there before. Now it should say something like "Obsolete. See ... instead."
You are right. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-02-10 01:10 AM, Richmond wrote:
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.
Then stop using the sysconfig editor, and use the Miscellaneous/Alternatives method. It's down at the bottom in the YaST control center, default-displaymanager. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 10 Feb 2019 08:12:04 -0600 Darryl Gregorash <raven@accesscomm.ca> wrote:
On 2019-02-10 01:10 AM, Richmond wrote:
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.
Then stop using the sysconfig editor, and use the Miscellaneous/Alternatives method. It's down at the bottom in the YaST control center, default-displaymanager.
Hmm. Which os/desktop is under discussion here? There's no such thing in my 15/xfce YaST Control Center so I think you might be localizing your thought processes to the desktop you are using, which would definitely disqualify your overly authoritative "barking" at the OP. sysconfig Editor is still there, tho, in 15/xfce. Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-02-10 12:47 PM, Ralph wrote:
On Sun, 10 Feb 2019 08:12:04 -0600 Darryl Gregorash <raven@accesscomm.ca> wrote:
On 2019-02-10 01:10 AM, Richmond wrote:
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. Then stop using the sysconfig editor, and use the Miscellaneous/Alternatives method. It's down at the bottom in the YaST control center, default-displaymanager. Hmm. Which os/desktop is under discussion here?
There's no such thing in my 15/xfce YaST Control Center so I think you might be localizing your thought processes to the desktop you are using, which would definitely disqualify your overly authoritative "barking" at the OP. sysconfig Editor is still there, tho, in 15/xfce.
Ralph
It's Leap 15.0, and which desktop manager is being used has nothing to do with the selections available in YaST. Yes, the sysconfig editor is still in YaST here too (sddm), but that, as we are seeing, no longer works to change the desktop manager. Look down at the bottom in YaST, and you will see a heading "Miscellaneous". In the box right under that, you should see the title "Alternatives". If you do not, you need to install the package "yast2-alternatives", and maybe also "update-alternatives" -- all as per the SDB. For Leap 15.0, the SDB also says absolutely nothing about using the sysconfig editor -- ergo, I assumed that means it is no longer working. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 10 Feb 2019 13:03:28 -0600 Darryl Gregorash <raven@accesscomm.ca> wrote:
Look down at the bottom in YaST, and you will see a heading "Miscellaneous". In the box right under that, you should see the title "Alternatives". If you do not, you need to install the package "yast2-alternatives", and maybe also "update-alternatives" -- all as per the SDB.
Alternatives is not there in YaST Control Center in 15/xfce with all updates. Why are these packages not installed automatically, either originally or as an update, if it is replacing another (installed) function? Ralph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 10 Feb 2019 13:23:00 -0600 Ralph <suselist@cableone.net> wrote:
On Sun, 10 Feb 2019 13:03:28 -0600 Darryl Gregorash <raven@accesscomm.ca> wrote:
Look down at the bottom in YaST, and you will see a heading "Miscellaneous". In the box right under that, you should see the title "Alternatives". If you do not, you need to install the package "yast2-alternatives", and maybe also "update-alternatives" -- all as per the SDB.
Alternatives is not there in YaST Control Center in 15/xfce with all updates. Why are these packages not installed automatically, either originally or as an update, if it is replacing another (installed) function?
Ralph
I agree with Ralph. Darryl, you're being unduly harsh to Ralph and Richmond. It should not be necessary to look at some web page to understand the information the GUI is presenting. It seems to be a clear YaST bug. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-02-10 01:49 PM, Dave Howorth wrote:
I agree with Ralph. Darryl, you're being unduly harsh to Ralph and Richmond. It should not be necessary to look at some web page to understand the information the GUI is presenting. It seems to be a clear YaST bug.
I don't believe I am being harsh on anyone. It isn't necessary for anyone to look at some web page; I have already done that, and the solution has been posted several times. I posted the URL to that SDB article in case anyone needed clarification or more detail. I don't think it is a YaST bug; rather, it is a configuration bug: the module should be getting installed automatically for everyone as part of the base installation. However one names it, though, it certainly is a bug. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 10 Feb 2019 14:03:48 -0600 Darryl Gregorash <raven@accesscomm.ca> wrote:
On 2019-02-10 01:49 PM, Dave Howorth wrote:
I agree with Ralph. Darryl, you're being unduly harsh to Ralph and Richmond. It should not be necessary to look at some web page to understand the information the GUI is presenting. It seems to be a clear YaST bug.
I don't believe I am being harsh on anyone. It isn't necessary for anyone to look at some web page; I have already done that, and the solution has been posted several times. I posted the URL to that SDB article in case anyone needed clarification or more detail.
I don't think it is a YaST bug; rather, it is a configuration bug: the module should be getting installed automatically for everyone as part of the base installation. However one names it, though, it certainly is a bug.
Well, to be pedantic there are two bugs, both of which are associated with YaST. Which component will you report it against if not YaST? One you mention. The other is that the sysconfig editor should not offer to edit the setting without providing some kind of warning that it will have no effect and a different mechanism must be used. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/02/2019 21.24, Dave Howorth wrote:
On Sun, 10 Feb 2019 14:03:48 -0600 Darryl Gregorash <raven@accesscomm.ca> wrote:
On 2019-02-10 01:49 PM, Dave Howorth wrote:
I agree with Ralph. Darryl, you're being unduly harsh to Ralph and Richmond. It should not be necessary to look at some web page to understand the information the GUI is presenting. It seems to be a clear YaST bug.
I don't believe I am being harsh on anyone. It isn't necessary for anyone to look at some web page; I have already done that, and the solution has been posted several times. I posted the URL to that SDB article in case anyone needed clarification or more detail.
I don't think it is a YaST bug; rather, it is a configuration bug: the module should be getting installed automatically for everyone as part of the base installation. However one names it, though, it certainly is a bug.
Well, to be pedantic there are two bugs, both of which are associated with YaST. Which component will you report it against if not YaST? One you mention. The other is that the sysconfig editor should not offer to edit the setting without providing some kind of warning that it will have no effect and a different mechanism must be used.
That one is not a yast bug, but a sysconfig file bug. Yast simply presents what it finds in the file. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Darryl Gregorash wrote:
On 2019-02-10 01:49 PM, Dave Howorth wrote:
I agree with Ralph. Darryl, you're being unduly harsh to Ralph and Richmond. It should not be necessary to look at some web page to understand the information the GUI is presenting. It seems to be a clear YaST bug.
I don't believe I am being harsh on anyone. It isn't necessary for anyone to look at some web page; I have already done that, and the solution has been posted several times. I posted the URL to that SDB article in case anyone needed clarification or more detail.
So you are saying people should read the opensuse mailing list to see how to configure the system? I think the confusion here is that you are answering a question I didn't ask, namely, how to change the display manager with Yast. In fact I had already changed the display manager before I posted to this list, and included an instruction on how to do it. My question was why was the method changed, and why was the old broken method left in there like a trap for the unwary? We don't want broken things in the configuration, and endless questions being posted in forums, otherwise we would be like Debian, and no one wants that, do they? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-02-11 06:18 AM, Richmond wrote:
Darryl Gregorash wrote:
On 2019-02-10 01:49 PM, Dave Howorth wrote:
I agree with Ralph. Darryl, you're being unduly harsh to Ralph and Richmond. It should not be necessary to look at some web page to understand the information the GUI is presenting. It seems to be a clear YaST bug.
I don't believe I am being harsh on anyone. It isn't necessary for anyone to look at some web page; I have already done that, and the solution has been posted several times. I posted the URL to that SDB article in case anyone needed clarification or more detail.
So you are saying people should read the opensuse mailing list to see how to configure the system? I think the confusion here is that you are answering a question I didn't ask, namely, how to change the display manager with Yast. In fact I had already changed the display manager before I posted to this list, and included an instruction on how to do it. My question was why was the method changed, and why was the old broken method left in there like a trap for the unwary? If you had done things right in the first place and consulted the SUSE Database, would we even be having this inane discussion?
I don't know why the sysconfig entry is still there, and why its wording is the same as forever. I have a guess or two, but if I mention those, probably this thread will go on forever. As a hint, though, Leap 42.3 is still in support, and that may have something to do with it. If for any reason that sysconfig entry is still needed, could it have been amended to included a statement, "Deprecated for Leap 15+. Use Misc/Alternatives instead"? Of course, and it probably should have been. So instead of carrying on in this thread, you could have done something useful like sending a note to the YaST team, or opening a bug report. @Dave Howorth: /now/ I am getting harsh. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-02-10 01:23 PM, Ralph wrote:
On Sun, 10 Feb 2019 13:03:28 -0600 Darryl Gregorash <raven@accesscomm.ca> wrote:
Look down at the bottom in YaST, and you will see a heading "Miscellaneous". In the box right under that, you should see the title "Alternatives". If you do not, you need to install the package "yast2-alternatives", and maybe also "update-alternatives" -- all as per the SDB. Alternatives is not there in YaST Control Center in 15/xfce with all updates. Why are these packages not installed automatically, either originally or as an update, if it is replacing another (installed) function?
Ralph
I don't recall if it was installed automatically here; I just noticed it when this thread opened, after I read the SDB article. If it wasn't automatic, I have no idea why it wasn't. It certainly should be. A bug report seems to be in order; meanwhile, do install that package, because there are more entries there, and I willing to wager those can no longer be changed in the sysconfig editor either. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/02/2019 19.47, Ralph wrote:
On Sun, 10 Feb 2019 08:12:04 -0600 Darryl Gregorash <raven@accesscomm.ca> wrote:
On 2019-02-10 01:10 AM, Richmond wrote:
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.
Then stop using the sysconfig editor, and use the Miscellaneous/Alternatives method. It's down at the bottom in the YaST control center, default-displaymanager.
Hmm. Which os/desktop is under discussion here?
There's no such thing in my 15/xfce YaST Control Center so I think you might be localizing your thought processes to the desktop you are using, which would definitely disqualify your overly authoritative "barking" at the OP. sysconfig Editor is still there, tho, in 15/xfce.
It has been said days ago that you have to install the yast alternatives module yourself. Telcontar:~ # rpm -qa | grep -i yast | grep -i alter yast2-alternatives-4.0.0-lp150.1.1.x86_64 Telcontar:~ # Desktop is irrelevant. It also works in text mode. look: YaST2 - menu @ Telcontar ┌──────────────────────────────────────────────────────┐ │ YaST Control Center │ └──────────────────────────────────────────────────────┘ ┌──────────────┐ ┌─────────────────────────────────────┐ │Software │ │Alternatives <====== │ │System │ │Autoinstallation Cloning System │ │Hardware │ │Autoinstallation Configuration │ │Network Servic│ │Installation Server │ │Security and U│ │Snapper │ │Virtualization│ │System Log │ │Support │ │Systemd Journal │ │Miscellaneous │ │Vendor Driver CD │ │ │ │ │ │ │ │ │ │ │ │ │ └├────────┤────┘ └─────────────────────────────────────┘ [Help] [Run][Quit] -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Richmond composed on 2019-02-09 19:21 (UTC):
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
If that's what really happened, Google got it wrong. There's also yast2 alternatives: in 15.0: http://fm.no-ip.com/SS/Suse/YaST/150/150Alternatives.jpg S | Name | Type | Version | Arch | Repository i+ | yast2-alternatives | package | 4.0.0-lp150.1.1 | x86_64 | OSS in TW: http://fm.no-ip.com/SS/Suse/YaST/TW/yastTW-misc-alternatives20190125.jpg i+ | yast2-alternatives | package | 4.1.0-1.2 | x86_64 | OSS-- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Richmond composed on 2019-02-09 19:21 (UTC):
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?
Since you started the thread, presumably you experienced the problem. A bug report has been filed, but the reporter mainly just pointed to this thread, without being bothered by any failure. I've not been bothered by it either. Maybe you could be the one to fulfill the request for additional info: https://bugzilla.opensuse.org/show_bug.cgi?id=1125040 -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Carlos E. R. -
Darryl Gregorash -
Dave Howorth -
David C. Rankin -
Felix Miata -
Ralph -
Richmond