• Mgaapplet not finding Mga 7

    From chris@2:250/1 to All on Sat Aug 31 21:01:53 2019
    For some reason the upgrade applet no longer appears on my system
    offering the Mga 7 upgrade. So I tried the command given in the Wiki
    Release Notes, viz.:

    mgaapplet-upgrade-helper --new_distro_version=7

    but that gives an error message saying 'distribution version 7 not found
    in update list'. Obviously I haven't touched the repos list, but assumed
    this command added the repos for the new release?

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From Jim Beard@2:250/1 to All on Sat Aug 31 22:48:16 2019
    On Sat, 31 Aug 2019 21:01:53 +0100, chris wrote:

    For some reason the upgrade applet no longer appears on my system
    offering the Mga 7 upgrade. So I tried the command given in the Wiki
    Release Notes, viz.:

    mgaapplet-upgrade-helper --new_distro_version=7

    but that gives an error message saying 'distribution version 7 not found
    in update list'. Obviously I haven't touched the repos list, but assumed
    this command added the repos for the new release?

    What do you have in /etc/urpmi/urpmi.cfg ??? assuming you are using
    urpmi for your updates.

    There are several places in /etc where Mageia release 7 is specified, and presumably could be missing. You might check,

    /etc/issue:Mageia release 7 (Official) for x86_64
    /etc/mageia-release:Mageia release 7 (Official) for x86_64 /etc/mandrakelinux-release:Mageia release 7 (Official) for x86_64 /etc/mandrake-release:Mageia release 7 (Official) for x86_64 /etc/mandriva-release:Mageia release 7 (Official) for x86_64
    /etc/ product.id:vendor=Mageia.Org,distribution=Mageia,type=Basic,version=7,branch=Of ficial,release=7,arch=x86_64,product=Default
    /etc/ product.id.Default:vendor=Mageia.Org,distribution=Mageia,type=Basic,version=7,b ranch=Official,release=7,arch=x86_64,product=Default
    /etc/redhat-release:Mageia release 7 (Official) for x86_64
    /etc/release:Mageia release 7 (Official) for x86_64
    /etc/system-release:Mageia release 7 (Official) for x86_64

    You may need to remove all update media with (as root) /usr/sbin/urpmi.removemedia -a
    and then go into Mageia Control Center to Install and Remove Software,
    click on Configure media sources for install and update, and
    Add the media you want.

    I first go to File and select a specific mirror (I usually use the
    Princeton mirror or James Whitby's mirror). I usually choose all media
    except testing and debug.

    That done, if needed, click OK and then go to Update your system and see
    what happens if you try that.

    Cheers!

    jim b.

    --
    UNIX is not user-unfriendly, it merely expects users to be computer-
    friendly.

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From grimble@2:250/1 to All on Sat Aug 31 23:10:33 2019
    On 31/08/2019 21:01, chris wrote:
    For some reason the upgrade applet no longer appears on my system
    offering the Mga 7 upgrade. So I tried the command given in the Wiki
    Release Notes, viz.:

    mgaapplet-upgrade-helper --new_distro_version=7

    but that gives an error message saying 'distribution version 7 not found
    in update list'. Obviously I haven't touched the repos list, but assumed this command added the repos for the new release?
    I read in the release notes or the errata that there was the odd problem (grub?) to be sorted out before the upgrade was released.

    --
    Grimble
    Registered Linux User #450547
    Machine 'mozart' running Plasma 5.12.2 on 4.14.137-desktop-1.mga6 kernel. Mageia release 6 (Official) for x86_64

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Jim Beard@2:250/1 to All on Sun Sep 1 01:02:38 2019
    On Sat, 31 Aug 2019 21:01:53 +0100, chris wrote:

    For some reason the upgrade applet no longer appears on my system
    offering the Mga 7 upgrade. So I tried the command given in the Wiki
    Release Notes, viz.:

    mgaapplet-upgrade-helper --new_distro_version=7

    but that gives an error message saying 'distribution version 7 not found
    in update list'. Obviously I haven't touched the repos list, but assumed
    this command added the repos for the new release?

    After a second look, I conclude you have not yet upgraded to Mageia 7,
    but are looking for how to do it. I have no remedy for the mgaapplet- upgrade-helper problem, but you can do the upgrade manually.

    https://wiki.mageia.org/en/Mageia_7_Release_Notes#Upgrading_online. 2C_using_mgaonline_.28GUI.29

    Or search to find your way to Wiki » Mageia 7 Release Notes

    Scroll down to near the bottom, to the subheadline
    Upgrading online, using urpmi (CLI)

    Follow instructions there, which will basically do what I suggested doing
    in my first reply.

    Cheers!

    jim b.

    --
    UNIX is not user-unfriendly, it merely expects users to be computer-
    friendly.

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Jim Beard@2:250/1 to All on Mon Sep 2 01:18:57 2019
    On Sat, 31 Aug 2019 21:01:53 +0100, chris wrote:

    For some reason the upgrade applet no longer appears on my system
    offering the Mga 7 upgrade. So I tried the command given in the Wiki
    Release Notes, viz.:

    mgaapplet-upgrade-helper --new_distro_version=7

    but that gives an error message saying 'distribution version 7 not found
    in update list'. Obviously I haven't touched the repos list, but assumed
    this command added the repos for the new release?

    Chris,

    Please reply to me here on the newsgroup alt.os.linux.mageia.

    I read a few of the forums at ml.mageia.org but currently cannot respond
    to your messages there. Now and then their mail system changes, and I
    use it so rarely I have not bothered to update my account in months.

    As we both now recognize, you continued to have Mageia 6 installed.
    Going through the process of an online upgrade will take you to Mageia 7,
    but I would recomment downloading the DVD iso for Mageia 7 and burning it
    to a DVD so you can use it if the online upgrade fails due to the
    problems you found in Mageia's bugzilla.

    Otherwise, you could wait and hope things get sorted out. As I mentioned earlier, my online upgrade to Mageia 7 worked smoothly. That does not
    seem to happen for everyone.

    Cheers!

    jim b.

    --
    UNIX is not user-unfriendly, it merely expects users to be computer-
    friendly.

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Mon Sep 2 04:58:35 2019
    On 1/9/19 7:48 am, Jim Beard wrote:
    On Sat, 31 Aug 2019 21:01:53 +0100, chris wrote:

    For some reason the upgrade applet no longer appears on my system
    offering the Mga 7 upgrade. So I tried the command given in the Wiki
    Release Notes, viz.:

    mgaapplet-upgrade-helper --new_distro_version=7

    but that gives an error message saying 'distribution version 7 not found
    in update list'. Obviously I haven't touched the repos list, but assumed
    this command added the repos for the new release?


    I have slightly different problem.
    The Mgaapplet does not recognize the root password.
    It flags a red dialog "Authentication Failure"

    Root password works with everything else.

    Regards


    --
    faeychild
    Running plasmashell 5.15.4 on 5.2.7-desktop-1.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From chris@2:250/1 to All on Mon Sep 2 07:37:15 2019
    On 9/2/19 1:18 AM, Jim Beard wrote:
    On Sat, 31 Aug 2019 21:01:53 +0100, chris wrote:

    For some reason the upgrade applet no longer appears on my system
    offering the Mga 7 upgrade. So I tried the command given in the Wiki
    Release Notes, viz.:

    mgaapplet-upgrade-helper --new_distro_version=7

    but that gives an error message saying 'distribution version 7 not found
    in update list'. Obviously I haven't touched the repos list, but assumed
    this command added the repos for the new release?

    Chris,

    Please reply to me here on the newsgroup alt.os.linux.mageia.

    Jim,

    Apologies. Finger trouble!

    I have downloaded the ISO and burned to a USB drive, but now find a new problem that I can't get into the BIOS to get it to boot from the USB!
    Looks like I will have to try a BIOS reset later (or disconnect other
    drives to see if that brings it back.



    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From Jim Beard@2:250/1 to All on Mon Sep 2 15:12:58 2019
    On Mon, 02 Sep 2019 07:37:15 +0100, chris wrote:

    On 9/2/19 1:18 AM, Jim Beard wrote:
    On Sat, 31 Aug 2019 21:01:53 +0100, chris wrote:

    For some reason the upgrade applet no longer appears on my system
    offering the Mga 7 upgrade. So I tried the command given in the Wiki
    Release Notes, viz.:

    mgaapplet-upgrade-helper --new_distro_version=7

    but that gives an error message saying 'distribution version 7 not
    found in update list'. Obviously I haven't touched the repos list, but
    assumed this command added the repos for the new release?

    Chris,

    Please reply to me here on the newsgroup alt.os.linux.mageia.

    Jim,

    Apologies. Finger trouble!

    I have downloaded the ISO and burned to a USB drive, but now find a new problem that I can't get into the BIOS to get it to boot from the USB!
    Looks like I will have to try a BIOS reset later (or disconnect other
    drives to see if that brings it back.

    Many systems will tell you how to get into the BIOS when you turn the
    computer off and start it up again, or pehaps just warm boot.

    Depending on the mfg and computer, you may need to hit ESC, DEL, F1, F2,
    or some other key when you first turn on the computer, from power off.
    Just keep turning on the power, and if it does not take you to the BIOS
    turn it off again and try another key.

    Cheers!

    jim b.

    --
    UNIX is not user-unfriendly, it merely expects users to be computer-
    friendly.

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From chris@2:250/1 to All on Mon Sep 2 18:37:07 2019
    On 9/2/19 3:12 PM, Jim Beard wrote:
    On Mon, 02 Sep 2019 07:37:15 +0100, chris wrote:
    ....

    I have downloaded the ISO and burned to a USB drive, but now find a new
    problem that I can't get into the BIOS to get it to boot from the USB!
    Looks like I will have to try a BIOS reset later (or disconnect other
    drives to see if that brings it back.

    Many systems will tell you how to get into the BIOS when you turn the computer off and start it up again, or pehaps just warm boot.

    Depending on the mfg and computer, you may need to hit ESC, DEL, F1, F2,
    or some other key when you first turn on the computer, from power off.
    Just keep turning on the power, and if it does not take you to the BIOS
    turn it off again and try another key.

    I'd gone into the BIOS many times in the past, but this was the first
    time this had happened. I think I may have selected Fast Boot at some
    point which bypassed the BIOS setup. I ended up doing the CMOS reset on
    the MB. Now I can boot the ISO from the USB stick. Need to study my partitioning before putting 7 alongside 6.

    As 8 was my first UEFI, I'm not sure what to do with boot partitions
    with multi-distros. Any tips? I use my M.2 for /boot/EFI and /root.
    /home and /var are on a legacy hdd.

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From Jim Beard@2:250/1 to All on Mon Sep 2 23:24:08 2019
    On Mon, 02 Sep 2019 18:37:07 +0100, chris wrote:

    On 9/2/19 3:12 PM, Jim Beard wrote:
    On Mon, 02 Sep 2019 07:37:15 +0100, chris wrote:
    ...

    I have downloaded the ISO and burned to a USB drive, but now find a
    new problem that I can't get into the BIOS to get it to boot from the
    USB! Looks like I will have to try a BIOS reset later (or disconnect
    other drives to see if that brings it back.

    Many systems will tell you how to get into the BIOS when you turn the
    computer off and start it up again, or pehaps just warm boot.

    Depending on the mfg and computer, you may need to hit ESC, DEL, F1,
    F2,
    or some other key when you first turn on the computer, from power off.
    Just keep turning on the power, and if it does not take you to the BIOS
    turn it off again and try another key.

    I'd gone into the BIOS many times in the past, but this was the first
    time this had happened. I think I may have selected Fast Boot at some
    point which bypassed the BIOS setup. I ended up doing the CMOS reset on
    the MB. Now I can boot the ISO from the USB stick. Need to study my partitioning before putting 7 alongside 6.

    As 8 was my first UEFI, I'm not sure what to do with boot partitions
    with multi-distros. Any tips? I use my M.2 for /boot/EFI and /root.
    /home and /var are on a legacy hdd.

    You have lost me again. By "8," do you mean Cauldron?

    Are you using UEFI? That is critical, as trying to dual-boot with both
    mbr and uefi does not work. Getting that correct when you install is mandatory, and installing from the DVD may allow you either, if you
    already have mbr boot, and will by default use mbr if it is there, I
    think.

    How big are your disks? How many? Do you have a need for large
    partitions for things like /music, /videos, /genealogy or other special purposes? If so, you can set up a partition for each, and label the partitions with corresponding names: music, videos, geneal, etc.

    If using uefi, you must install any new system as uefi, and the initial-
    use uefi boot come will go in a special efi partition. I have had my
    problems with this in the past and will rely on your use of Mageia documentation, wiki, and such and help from others to deal with that.

    I currently keep /home on its own partition, but with different os using different configuration files you may need /home for each os either on
    the partition of the os or on a separate partition. Would a 100 GB
    partition for each os be enough for everything except special partitions
    that are the same for all os? One music partition can be shared by all
    os, one geneal partition likewise, etc.

    You can search Google Groups for disk partitions uefi and such with
    limitation to alt.os.linux.mageia. That may involve sorting through
    multiple answers to recurring questions, but there is a lot of good information there.

    Cheers!

    jim b.

    --
    UNIX is not user-unfriendly, it merely expects users to be computer-
    friendly.

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Mon Sep 2 23:51:19 2019
    On Mon, 2 Sep 2019 22:24:08 -0000 (UTC), Jim Beard wrote:
    On Mon, 02 Sep 2019 18:37:07 +0100, chris wrote:

    I currently keep /home on its own partition, but with different os using different configuration files you may need /home for each os either on
    the partition of the os or on a separate partition. Would a 100 GB
    partition for each os be enough for everything except special partitions
    that are the same for all os?


    Yea gads, I would hope 40 GB or less for other OS installs would be enough.


    < One music partition can be shared by all
    os, one geneal partition likewise, etc.

    Yep, and I suggest that /home should be on each OS / with common
    /home/$USER common files linked to a common $USER partition.

    One reason: when using a shared /home/$USER ~Desktop Environment files
    could be clobbered when booting the other install.

    All common user files/directories in my OS /home/$USER are soft linked
    to /accounts/$USER.


    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Tue Sep 3 02:41:49 2019
    On Sun, 01 Sep 2019 23:58:35 -0400, faeychild <faeychild@nomail.afraid.org> wrote:

    I have slightly different problem.
    The Mgaapplet does not recognize the root password.
    It flags a red dialog "Authentication Failure"
    Root password works with everything else.

    Could this be the same problem as in https://bugs.mageia.org/show_bug.cgi?id=16343#c8

    Regards, Dave Hodgins

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

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Doug Laidlaw@2:250/1 to All on Tue Sep 3 04:21:02 2019
    On 3/9/19 11:41 am, David W. Hodgins wrote:
    On Sun, 01 Sep 2019 23:58:35 -0400, faeychild
    <faeychild@nomail.afraid.org> wrote:

    I have slightly different problem.
    The Mgaapplet does not recognize the root password.
    It flags a red dialog "Authentication Failure"
    Root password works with everything else.

    Could this be the same problem as in https://bugs.mageia.org/show_bug.cgi?id=16343#c8

    Regards, Dave Hodgins

    Or, do you have "sudo" enabled for that command? I have added myself to
    the Wheel group, and now the root password is (almost) always flagged as wrong.

    Alternatively, a while back, the password you need for updates was
    switched from root's to user's.

    HTH,

    Doug.


    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Tue Sep 3 06:38:53 2019
    On 3/9/19 1:21 pm, Doug Laidlaw wrote:

    Regards, Dave Hodgins

    Or, do you have "sudo" enabled for that command?  I have added myself to the Wheel group, and now the root password is (almost) always flagged as wrong.

    Alternatively, a while back, the password you need for updates was
    switched from root's to user's.


    You and Doug may be onto something.

    I am not in "wheel" only cdrom system-journel and scanner.

    I am sudo'd only for shutdown

    But next time the update applet pops up I try users password.

    Was there any pressing reason for the password change?

    regards
    --
    faeychild
    Running plasmashell 5.15.4 on 5.2.10-desktop-1.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Tue Sep 3 07:25:18 2019
    On Tue, 03 Sep 2019 01:38:53 -0400, faeychild <faeychild@nomail.afraid.org> wrote:

    But next time the update applet pops up I try users password.
    Was there any pressing reason for the password change?

    There's no mention of the change in the changelog for mgaonline, the
    package mgaapplet is part of, so my guess is that the defaults in
    the polkit package changed.

    That's controlled by the developers of the program polkit. https://gitlab.freedesktop.org/polkit

    When the upstream provider of a package changes their defaults, the
    Mageia developers don't normally override their choices as that makes
    keeping updates in sync with the upstream more work, and debugging of
    any problems that show up more difficult. Defaults are normally only
    overridden if the defaults prevent the package from working properly
    with Mageia.

    Most distributions handle defaults in a similar manner so that users
    who use a given package in multiple distributions find it easier.

    Regards, Dave Hodgins

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

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From James Kerr@2:250/1 to All on Tue Sep 3 09:35:24 2019
    On 03/09/2019 07:25, David W. Hodgins wrote:
    On Tue, 03 Sep 2019 01:38:53 -0400, faeychild
    <faeychild@nomail.afraid.org> wrote:

    But next time the update applet pops up I try users password.
    Was there any pressing reason for the password change?

    There's no mention of the change in the changelog for mgaonline, the
    package mgaapplet is part of, so my guess is that the defaults in
    the polkit package changed.

    That's controlled by the developers of the program polkit. https://gitlab.freedesktop.org/polkit

    When the upstream provider of a package changes their defaults, the
    Mageia developers don't normally override their choices as that makes
    keeping updates in sync with the upstream more work, and debugging of
    any problems that show up more difficult. Defaults are normally only overridden if the defaults prevent the package from working properly
    with Mageia.

    Most distributions handle defaults in a similar manner so that users
    who use a given package in multiple distributions find it easier.

    Regards, Dave Hodgins


    The default (which has been user password for many years) can be changed
    in MCC - Security - "Configure Authentication for Mageia tools"

    Jim


    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From chris@2:250/1 to All on Tue Sep 3 19:12:38 2019
    On 9/2/19 11:51 PM, Bit Twister wrote:
    On Mon, 2 Sep 2019 22:24:08 -0000 (UTC), Jim Beard wrote:
    On Mon, 02 Sep 2019 18:37:07 +0100, chris wrote:

    I currently keep /home on its own partition, but with different os using
    different configuration files you may need /home for each os either on
    the partition of the os or on a separate partition. Would a 100 GB
    partition for each os be enough for everything except special partitions
    that are the same for all os?


    Yea gads, I would hope 40 GB or less for other OS installs would be enough.


    < One music partition can be shared by all
    os, one geneal partition likewise, etc.

    Yep, and I suggest that /home should be on each OS / with common
    /home/$USER common files linked to a common $USER partition.

    One reason: when using a shared /home/$USER ~Desktop Environment files
    could be clobbered when booting the other install.

    All common user files/directories in my OS /home/$USER are soft linked
    to /accounts/$USER.

    To reply to both: typo - should have been Mga6. It was the first time
    I'd used UEFI. So I have a /boot/EFI partition. That's on a 128 GB M.2.
    I also have 128 and 256 SSDs, plus my old HDD (500GB) where my current
    /home (and /var, to minimise read/writes on the SSD) resides. If I put 7
    in a separate partition, I will also keep its /home separate until I'm
    happy all is well to transfer files from my old /home. So plenty of
    space; I just want to take it slowly so I can avoid catastrophic mistakes!


    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Tue Sep 3 23:33:01 2019
    On 3/9/19 6:35 pm, James Kerr wrote:


    The default (which has been user password for many years) can be changed
    in MCC - Security - "Configure Authentication for Mageia tools"


    I have only ever used root password with MCC and the update applet

    "Configure Authentication" is an option that always escapes my mind.

    If it comes to pass that update now works with user password, I may
    change it back

    Thanks


    Regards
    --
    faeychild
    Running plasmashell 5.15.4 on 5.2.10-desktop-1.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Wed Sep 4 05:36:27 2019
    On Tue, 03 Sep 2019 18:33:01 -0400, faeychild <faeychild@nomail.afraid.org> wrote:

    I have only ever used root password with MCC and the update applet "Configure Authentication" is an option that always escapes my mind.

    It slipped my mind during this thread too. On new (non-testing) installs I always go through every option in mcc to refresh my memory of what's
    available, and to deal with changes. In the testing installs, I keep most things at their default settings, but not in my main day-to-day usage
    installs.

    Regards, Dave Hodgins

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

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Wed Sep 4 20:04:27 2019
    On 2019-09-03, James Kerr <jim@jkerr82508.free-online.co.uk> wrote:
    On 03/09/2019 07:25, David W. Hodgins wrote:
    On Tue, 03 Sep 2019 01:38:53 -0400, faeychild
    <faeychild@nomail.afraid.org> wrote:

    But next time the update applet pops up I try users password.
    Was there any pressing reason for the password change?

    There's no mention of the change in the changelog for mgaonline, the
    package mgaapplet is part of, so my guess is that the defaults in
    the polkit package changed.

    That's controlled by the developers of the program polkit.
    https://gitlab.freedesktop.org/polkit

    When the upstream provider of a package changes their defaults, the
    Mageia developers don't normally override their choices as that makes
    keeping updates in sync with the upstream more work, and debugging of
    any problems that show up more difficult. Defaults are normally only
    overridden if the defaults prevent the package from working properly
    with Mageia.

    Most distributions handle defaults in a similar manner so that users
    who use a given package in multiple distributions find it easier.

    Regards, Dave Hodgins


    The default (which has been user password for many years) can be changed
    in MCC - Security - "Configure Authentication for Mageia tools"

    It used to be that EITHER the user password or the root password would
    serve to unlock things ( like the screenlocker) but that disappeared a
    numbe of years ago. That seems to me to be the most reasonable option (
    so that a person who has root can recover a system).
    Why is that no longer an option?

    Jim


    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From David W. Hodgins@2:250/1 to All on Thu Sep 5 08:52:53 2019
    On Wed, 04 Sep 2019 15:04:27 -0400, William Unruh <unruh@invalid.ca> wrote:

    It used to be that EITHER the user password or the root password would
    serve to unlock things ( like the screenlocker) but that disappeared a
    numbe of years ago. That seems to me to be the most reasonable option (
    so that a person who has root can recover a system).
    Why is that no longer an option?

    Which screen saver? Whichever one you are using on that system, check
    with rpm to find it's upstream url. In Mageia 7, there's ... cinnamon-screensaver
    gnome-screensaver
    mate-screensaver
    kscreenlocker
    xfce4-screensaver
    xscreensaver

    So, for example ...
    $ rpm -q -i kscreenlocker|grep ^URL
    URL : https://www.kde.org/

    To find out why they've chosen to change those options, search within
    the given url for mentions of the corresponding package name, it's
    changelog, etc. I don't recall their ever being an option to use
    either password. It's always been one or the other as far as I can
    remember.

    Note that a person with the root password and physical access can always
    open another terminal (alt+ctrl+f3 for example), log in and kill the screensaver on the other terminal.

    Also note that there are many situations where the user at the terminal
    does not have the root password, so anything that requires root password
    by default, can create problems. In most cases, the user at the terminal
    should be allowed to install updates, as getting security updates into
    a system for things like java can be a very high priority, though the
    option to allow that can be disabled using draksec, or using msec in a
    non-gui environment.

    Regards, Dave Hodgins

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

    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sat Sep 7 06:42:43 2019
    On 5/9/19 5:04 am, William Unruh wrote:

    It used to be that EITHER the user password or the root password would
    serve to unlock things ( like the screenlocker) but that disappeared a
    numbe of years ago. That seems to me to be the most reasonable option (
    so that a person who has root can recover a system).
    Why is that no longer an option?


    I have found that alteration of drop down menu order confounds muscle
    memory.

    The new right click menu has "Open With" at the top. In Mg6 it was half
    way down. It take about a week to retrain.

    The settings dialog on user Dolphin has the buttons on the bottom arranged

    OK Apply Cancel.

    Under root Dolphin has the arrangement

    OK Cancel Apply

    It's an odd stumbling block.

    regards
    --
    faeychild
    Running plasmashell 5.15.4 on 5.2.10-desktop-1.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Sun Sep 8 08:29:16 2019
    On 4/9/19 2:36 pm, David W. Hodgins wrote:
    On Tue, 03 Sep 2019 18:33:01 -0400, faeychild
    <faeychild@nomail.afraid.org> wrote:

      I have only ever used root password with MCC and the update applet
    "Configure Authentication" is an option that always escapes my mind.

    It slipped my mind during this thread too. On new (non-testing) installs I always go through every option in mcc to refresh my memory of what's available, and to deal with changes. In the testing installs, I keep most things at their default settings, but not in my main day-to-day usage installs.



    You are correct!! The update applet triggered today and the password is
    now user

    Regards

    --
    faeychild
    Running plasmashell 5.15.4 on 5.2.10-desktop-1.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


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