There are no lines with the command passwd, these are the only lines with the descriptive word password. Edit: The iso was downloaded from SourceForge yesterday and this installation was yesterday.
.. Job 23 "Set password for user ben79" +wt 0.166667 tot.wt 21.6667
.. Job 24 "Set password for user root" +wt 0.166667 tot.wt 21.8333
passwd --help
Usage: passwd [OPTION...] <accountName>
-k, --keep-tokens keep non-expired authentication tokens
-d, --delete delete the password for the named account (root only); also removes password lock if any
-l, --lock lock the password for the named account (root only)
-u, --unlock unlock the password for the named account (root only)
-e, --expire expire the password for the named account (root only)
-f, --force force operation
-x, --maximum=DAYS maximum password lifetime (root only)
-n, --minimum=DAYS minimum password lifetime (root only)
-w, --warning=DAYS number of days warning users receives before password expiration (root only)
-i, --inactive=DAYS number of days after password expiration when an account becomes disabled (root only)
-S, --status report password status on the named account (root only)
--stdin read new tokens from stdin (root only)
Help options:
-?, --help Show this help message
--usage Display brief usage message
Looks like something is trying to “delete the password for the named account” and at the same time “lock the password for the named account”. What would be locking the root password?
So quick workaround is “don’t do whatever you’re doing to try to delete the root user”
longer fix is to check what calamares is doing, the combination of -d and -l to passwd doesn’t make sense (so it might be assuming passwd is patched for some other distro)
but in the mean time just don’t try to disable root during installation and disable root manually after installation
@deltakprime I was able to reproduce the same error. I did this by using separate passwords for user and root and leaving the root password blank. The installer interprets that as “lock the account” which triggers this error. I do not know if this is what accounts for your situation.
There are more technical details to this but developer is testing a possible fix for this. However the fix will only be applied to upcoming releases of OMLx.
When I asked “Is this what you get?” I meant to ask you if the new longer log file (“failed calamares install log.txt” - 1,012 lines) I was uploading came through for you to view, instead of the truncated version of only 393 lines you reported, which did not contain the lines 938 - 974 I had referred to.
Regarding the suggested quick workaround:
It appears that the responding dev is presuming that I am personally attempting to do this.
I was not personally responsible for trying to delete the root user via a CLI-based installation… I merely entered the requested installation information by filling out the on-screen GUI-based Calamares installer page section asking for the user name and passwords. (I entered a name and user password, and left the admin password blank.)
So:
My immediate response is to attempt the installation by creating and entering both the user and admin password.
(Attempting now, will advise of result.)
TTYL
Ok, got past the previous error to the 90% (on-screen) progress indicator, failed with message:
Installation Failed
External command failed to finish.
Command/usr/calamares-post-script failed to finish in 180 seconds.
There was no output from the command.
I will run installation again with the log saving option.
TTYL
Apologies for my confusion about the logs. Yes I got the full log in that post.
No one thinks you were trying to delete the root user, it was setting root password empty that is doing this. This is actually a bug that may go back to Mandrake days. Thanks for discovering and reporting this.
Any fix will only appear in future versions of OMLx. The fix we are attempting needs to be tested and that will take some time.
Once again, installation got to the 90% (on-screen) progress indicator, failed with message:
Installation Failed
External command failed to finish.
Command/usr/calamares-post-script failed to finish in 180 seconds.
There was no output from the command.
Line 864 of the attached log file:
15:32:37 [1]: void Calamares::ViewManager::onInstallationFailed(const QString &, const QString &)
ERROR: Installation failed: "External command failed to finish."
.. - message: "External command failed to finish."
.. - details: Command <i>/usr/sbin/calamares-post-script</i> failed to finish in 180 seconds.
There was no output from the command.
15:32:38 [6]: void Calamares::ViewManager::onInstallationFailed(const QString &, const QString &)
Calamares will quit when the dialog closes.
15:32:38 [6]: void CalamaresUtils::callQmlFunction(QQuickItem *, const char *)
QML "onLeave()" is missing.
15:32:38 [6]: void Config::doNotify(bool, bool)
Notification not sent; completion: failed
15:32:57 [6]: void Config::doRestart(bool)
mode= "never" user wants restart? false force restart? false
Shutting down Calamares...
.. Finished shutdown.
[live@omv-598 ~]$
The external command that failed to finish is:
[/usr/sbin/calamares-post-script
I entered that command in Konsole and obtained this result:
[live@omv-598 ~]$ /usr/sbin/calamares-post-script
Removing not needed language packages..
Failed to load expired repos cache: [Errno 13] Permission denied: '/var/cache/dnf/expired_repos.json'
Error: This command has to be run with superuser privileges (under the root user on most systems).
Cleaning up..
rm: cannot remove '/live/.cache/fontconfig': Permission denied
rm: cannot remove '/etc/ssh/sshd_config.d/50-live-iso.conf': Permission denied
rm: cannot remove '/etc/nsswitch.conf.bak': Permission denied
rm: cannot remove '/etc/nsswitch.conf.rpmsave': Permission denied
Failed to load expired repos cache: [Errno 13] Permission denied: '/var/cache/dnf/expired_repos.json'
Error: This command has to be run with superuser privileges (under the root user on most systems).
chown: changing ownership of '/var/lib/rpm/.rpm.lock': Operation not permitted
chown: changing ownership of '/var/lib/rpm/rpmdb.sqlite': Operation not permitted
chown: changing ownership of '/var/lib/rpm/rpmdb.sqlite-shm': Operation not permitted
chown: changing ownership of '/var/lib/rpm/rpmdb.sqlite-wal': Operation not permitted
chown: changing ownership of '/var/lib/rpm': Operation not permitted
rm: cannot remove '/var/lib/rpm/.rpm.lock': Permission denied
We are not on VirtualBox , removing virtualbox-guest-additions
Failed to load expired repos cache: [Errno 13] Permission denied: '/var/cache/dnf/expired_repos.json'
Error: This command has to be run with superuser privileges (under the root user on most systems).
[live@omv-598 ~]$
Now attempting the installation as su (sudo), will advise…
Not sudo or su. To run Calamares in Konsole and generate a log file in the /home/live directory open Konsole and run:
$ pkexec calamares -d | tee /home/live/calamares-installation-log.txt
For all users: This is correct command for any current version of OMLx including Cooker, Rolling, and Rock. If anyone has trouble installing OMLx read this first.
That’s what I had originally done, which failed with this message:
Installation Failed
External command failed to finish.
Command/usr/calamares-post-script failed to finish in 180 seconds.
There was no output from the command.
I am now going through your “read this first” link point-by-point to exhaust all cited possibilities.
Will advise…
I ran inxi_F.txt per your link suggestion, and obtained the output of the attached file: inxi_F.txt (2.0 KB)
Note appearing at the end of line 3:
<superuser required>
As you had previously stated not to use the sudo command, I presume that there is another alternative way to do this, and am exploring options.
Suggestions?
No I did not mean to not use the sudo command. To run the Calamares installer requires a very specific command. For Calamares it needs to be pkexec not sudo. But sudo is perfectly OK for most things one would do in terminal that require super user privileges.
pkexec=something like packagekit execute. Using pkexec has to do with the scripts Calamares runs.
As far as inxi -F the only thing that needs super user is serial number of computer or motherboard. Generally that is not needed for problem solving here. You might need that for dealing with the people that made the computer of mobo. You can run sudo inxi -F or sudo inxi -M if you need those serial numbers.
Ok, thanks for the clarification.
Unless you have any other ideas to try, I suppose the appropriate action would be to submit the information in a bug report.
I haven’t done that before, but I did sign up & log in to their site. I’ll check back tomorrow with you here before I post to their site, in case you have any suggestions.
Thanks again for all your help.
There is one problem. The log does not begin at the beginning. There could be very important information that is missing. We need a calamares installation log with absolutely everything. The log should be begin with the command you use to open calamares installer and everything after until calamares installer either finishes or fails.
Worth noting: the error is for /usr/sbin/calamares-post-script which is a post installation script, and for some reason it times out before it finishes.
Your install log seems to show a successful installation with boot loader installed. When it gets to this point:
grub2-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
grub2-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
Installation finished. No error reported.
The important part there is “Installation finished. No error reported.”
Generating grub configuration file ...
Found theme: /boot/grub2/themes/OpenMandriva/theme.txt
Found background: /boot/grub2/themes/OpenMandriva/background.png
Found linux image: /boot/vmlinuz-5.16.7-desktop-1omv4003
Found initrd image: /boot/initrd-5.16.7-desktop-1omv4003.img
Found memtest image: /boot/memtest.bin
Remove echo commands from "/boot/grub2/grub.cfg"
It is done. Calamares has finished installation and installed grub2 boot menu with an entry to boot /boot/initrd-5.16.7-desktop-1omv4003.img,
After that all it is doing is removing unneeded packages. It then removes most of those packages and at the end something times out. And I think maybe 5 packages did not get removed.
So try booting into the new system. If you can boot into new system then you can open terminal and run:
