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?
For some reason the upgrade applet no longer appears on my systemI read in the release notes or the errata that there was the odd problem (grub?) to be sorted out before the upgrade was released.
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?
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?
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?
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?
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.
On 9/2/19 1:18 AM, Jim Beard wrote:
On Sat, 31 Aug 2019 21:01:53 +0100, chris wrote:Jim,
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.
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.
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.
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.
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?
os, one geneal partition likewise, etc.
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.
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
Regards, Dave HodginsOr, 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.
But next time the update applet pops up I try users password.
Was there any pressing reason for the password change?
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
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.
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.
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
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?
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?
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 286 |
Nodes: | 16 (2 / 14) |
Uptime: | 83:26:12 |
Calls: | 6,495 |
Calls today: | 6 |
Files: | 12,096 |
Messages: | 5,276,833 |