In the past I have used SDDM as my display manager all the time. Every setting I typed in, except the password, was there next time. But since
I switched to Mga8, the selected OS always defaults to IceWM.session. A
recent update of SDDM did not change this. Is it a new standard or a bug?

--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On 3/18/21 5:15 AM, Doug Laidlaw wrote:

In the past  I have used SDDM as my display manager all the time.  Every setting I typed in, except the password, was there next time.  But since
I switched to Mga8, the selected OS always defaults to IceWM.session. A recent update of SDDM did not change this.  Is it a new standard or a bug?

The last update of sddm addressed this problem, but only if you accepted "rpmnew" as the new sddm.conf file. If you chose to do nothing, then
nothing was done.

To fix it, look in /etc for the files "sddm.conf" and "sddm.conf.rpmnew"
If you have the rpmnew file, as root rename sddm.conf to something else
(I'd suggest something like "sddm.conf.rpmold") and then rename sddm.conf.rpmnew to sddm.conf.

Then try it out. You'll probably have to log in twice before Plasma is remembered from the last session, but after that it should be OK. Once
you are satisfied that it's working properly, go back to /etc and remove
that old (renamed to something else) sddm.conf file.

Alternatively, you can edit the existing sddm.conf. Look for a line
under "Mageia-specific configuration" that says
"RememberLastSession=false" and remove it. That should take care of your problem, too.

TJ




--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 19/3/21 6:51 am, TJ wrote:

On 3/18/21 5:15 AM, Doug Laidlaw wrote:

In the past  I have used SDDM as my display manager all the time.
Every setting I typed in, except the password, was there next time.
But since I switched to Mga8, the selected OS always defaults to
IceWM.session. A recent update of SDDM did not change this.  Is it a
new standard or a bug?

The last update of sddm addressed this problem, but only if you accepted "rpmnew" as the new sddm.conf file. If you chose to do nothing, then
nothing was done.

To fix it, look in /etc for the files "sddm.conf" and "sddm.conf.rpmnew"
If you have the rpmnew file, as root rename sddm.conf to something else
(I'd suggest something like "sddm.conf.rpmold") and then rename sddm.conf.rpmnew to sddm.conf.

Then try it out. You'll probably have to log in twice before Plasma is remembered from the last session, but after that it should be OK. Once
you are satisfied that it's working properly, go back to /etc and remove that old (renamed to something else) sddm.conf file.

Alternatively, you can edit the existing sddm.conf. Look for a line
under "Mageia-specific configuration" that says
"RememberLastSession=false" and remove it. That should take care of your problem, too.

TJ

Thanks. I normally accept the rpmnew. I remember looking at the
changes and testing again with the .rpmnew file. I will have another look.
[Or was it the .rpmnew? I think that the file with that suffix is the pre-existing file, which is no longer recognized because of it. The replacement has the original filename. But I accepted the new
configuration.]

--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On Fri, 19 Mar 2021 13:29:24 -0400, Doug Laidlaw <laidlaws@hotkey.net.au> wrote:

Thanks. I normally accept the rpmnew. I remember looking at the
changes and testing again with the .rpmnew file. I will have another look. [Or was it the .rpmnew? I think that the file with that suffix is the pre-existing file, which is no longer recognized because of it. The replacement has the original filename. But I accepted the new configuration.]

Assuming "do nothing" is chosen when installing an update ...

Depending on the package creators choice, either the old $configfile is renamed to $configfile.rpmsave and a new $configfile installed, or the $configfile is left
alone and the new $configfile is installed as $configfile.rpmnew.

In the case of sddm, the sddm.conf file was left alone during the installation of the update. The new version of the file was installed as sddm.conf.rpmnew.

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 20/3/21 10:31 am, David W. Hodgins wrote:

On Fri, 19 Mar 2021 13:29:24 -0400, Doug Laidlaw
<laidlaws@hotkey.net.au> wrote:

Thanks.  I normally accept the rpmnew.  I remember looking at the
changes and testing again with the .rpmnew file.  I will have another
look.
[Or was it the .rpmnew?  I think that the file with that suffix is the
pre-existing file, which is no longer recognized because of it.  The
replacement has the original filename.  But I accepted the new
configuration.]

Assuming "do nothing" is chosen when installing an update ...

Depending on the package creators choice, either the old $configfile is renamed
to $configfile.rpmsave and a new $configfile installed, or the
$configfile is left
alone and the new $configfile is installed as $configfile.rpmnew.

In the case of sddm, the sddm.conf file was left alone during the installation
of the update. The new version of the file was installed as sddm.conf.rpmnew.

Regards, Dave Hodgins

I have always believed that the .rpmnew file was the old one. The
dialog usually says "Delete .rpmnew." This the first time I have found
it to be the other way around. Maybe I assumed too much?

Doug.

--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On 21/3/21 12:43 am, Doug Laidlaw wrote:

On 20/3/21 10:31 am, David W. Hodgins wrote:

I have always believed that the .rpmnew file was the old one.  The
dialog usually says "Delete .rpmnew."  This the first time I have found
it to be the other way around.  Maybe I assumed too much?

Doug.

I have just realized that the above is the opposite of what I wrote
earlier. The theory is that a file ending in "rpmnew" is not what the
system is looking for.

Anyway, the .rpmnew file was no longer there. I commented out the line
TJ mentioned, and that seems to have done the trick.

Doug.

--- MBSE BBS v1.0.7.21 (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)