Yes, thanks @TPG. Verified fixed.
Sound issue also verified fixed.
The issue above about slow booting due to some systemd services I think, am pretty sure is fixed. So there should no longer be any need to disable or mask services for that.
I am seeing a problem with booting in VBox only not on hardware:
Post-edit: OK, I have not timed it but booting in VBox take 2 maybe 3 minutes. There have been no changes, disabling, or masking of any systemd services in this VM.
Nothing revealing here but I can guarantee you that it is not booting in 5-10 seconds. So maybe another command is needed to trace what’s wrong?
$ systemd-analyze
Startup finished in 1.007s (kernel) + 1.084s (initrd) + 6.539s (userspace) = 8.631s
graphical.target reached after 5.862s in userspace
So here are some logs:
dmesg.txt (51.8 KB)
boot.log.txt (154.0 KB)
I have not investigated those logs just generated and posted them so far.
So if you update your Cooker install and see all these errors:
I know a work around for that:
Which indicates we have some duplicates that maybe devs would want to remove?
Also there are some repos enabled that are empty. If they are empty they are useless. For one there is never anything in Updates repos in Cooker. Also can be disabled is ‘openmandriva-x86_64.repo’ both release and updates. They are not in use yet either.
So you end up with what long time Cooker users are used to 4 repos only:
If you don’t believe me that the ones I disabled are empty then simply go to the URL’s and look.
There is also:
cooker-nonfree-i686.repo
cooker-non-free-x86_64.repo
cooker-nonfree-x86_64.repo
cooker-nonfree-x86_64-source.repo
Only one of those exists in x86_64 or i686 repos:
cooker-non-free-x86_64.repo
So currently there is no ‘cooker-non-free-i686.repo’ which does exist and the 3 with no hyphen (nonfree) do not exist. Interesting huh? 
Post-edit: User Information: For now none of the repos in ‘/etc/yum.repos.d’ beginning with ‘openmandriva’ are used. I presume they are for Lx 4.0 release after repos get split.
Regarding the issue with: systemd-ask-password-plymouth.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
I timed a boot in VBox @ 2 minutes 45 seconds. I don’t have a clue for any work around.
In dmesg:
[Sat Nov 10 20:37:46 2018] systemd[1]: /lib/systemd/system/systemd-ask-password-plymouth.service:13: Executable "-watch" not found in path "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", ignoring
[Sat Nov 10 20:37:46 2018] systemd[1]: systemd-ask-password-plymouth.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
FWIW: There is /usr/bin/watch on this VBox system.
Not to surprisingly journalctl shows:
Nov 10 20:37:46 omv systemd[1]: systemd-ask-password-plymouth.path: Refusing to start, unit to trigger not loaded.
Nov 10 20:37:46 omv systemd[1]: Failed to start Forward Password Requests to Plymouth Directory Watch.
-- Subject: Unit systemd-ask-password-plymouth.path has failed
and later in the process:
Nov 10 20:37:46 omv systemd[1]: /lib/systemd/system/systemd-ask-password-plymouth.service:13: Executable "-watch" not found in path "/usr/local/sbin:/usr/local/bin:/usr/sb>
Nov 10 20:37:46 omv systemd[1]: systemd-ask-password-plymouth.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
Nov 10 20:37:46 omv systemd[1]: Started Reload Configuration from the Real Root.
…
-- Unit basic.target has finished shutting down.
Nov 10 20:37:46 omv systemd[1]: systemd-ask-password-plymouth.path: Refusing to start, unit to trigger not loaded.
Nov 10 20:37:46 omv systemd[1]: Failed to start Forward Password Requests to Plymouth Directory Watch.
-- Subject: Unit systemd-ask-password-plymouth.path has failed
And it is possible I missed something. 
(The log files are above in post # 104 with a screen shot.)
Testing in VBox virtual machines.
Plasma ISO build ID 2280 fresh install, after full updates - of course lots of packages coming from mass rebuild - I am stuck with this
or this, if I don’t switch plymouth to system boot messages
I can get a VT, in case, and run commands. But nothing else…
In my opinion it’s time to build a new up-to-date ISO 
.
Postedit:
2 Likes
fixed in plymouth
2 Likes
Unfortunately i still do not have any idea why system-udev-settle takes some much time.
1 Like
Plasma ISO build ID 2280 fresh install fully updated
Testing in VBox virtual machines.
- Network working
- Firefox working
- Falkon: not working, see output
- Libreoffice: not working, see output
- New distro theme displayed
-
No more long time before desktop show up!
.
$ falkon
falkon: error while loading shared libraries: libicui18n.so.62: cannot open shared object file: No such file or directory
.
$ libreoffice --writer
javaldx: Could not find a Java Runtime Environment!
Warning: failed to read path from javaldx
/usr/lib64/libreoffice/program/soffice.bin: error while loading shared libraries: libicui18n.so.62: cannot open shared object file: No such file or directory
.
$ rpm -qa|grep icu
lib64icudata63-63.1-1.x86_64
lib64icuuc63-63.1-1.x86_64
lib64harfbuzz-icu0-2.1.1-1.x86_64
lib64icui18n63-63.1-1.x86_64
icu-data-63.1-1.x86_64
.
$ systemd-analyze
Startup finished in 1.221s (kernel) + 1.215s (initrd) + 6.809s (userspace) = 9.246s
graphical.target reached after 6.799s in userspace
.
$ systemd-analyze blame
4.397s systemd-udev-settle.service
1.073s firewalld.service
692ms accounts-daemon.service
671ms udisks2.service
611ms dracut-initqueue.service
581ms NetworkManager-wait-online.service
541ms ModemManager.service
533ms polkit.service
360ms upower.service
324ms NetworkManager.service
291ms initrd-switch-root.service
263ms dnf-makecache.service
258ms systemd-vconsole-setup.service
215ms nftables.service
193ms systemd-udev-trigger.service
185ms vboxadd.service
143ms systemd-networkd-wait-online.service
142ms avahi-daemon.service
130ms systemd-networkd.service
122ms nscd.service
110ms systemd-logind.service
102ms rtkit-daemon.service
100ms cups.service
.
$ uname -a
Linux omlx-2280 4.19.2-desktop-2omv4000 #1 SMP Fri Nov 16 23:54:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
.
1 Like
New ISO is available 2315
This ISO ships:
kernel-release 4.19.2
KDE Plasma 5.14.3
KF 5.52.0
New smooth boot process (plymouth, kernel etc)
Many fixed bugs. Boot time around 5 seconds in vbox.
2 Likes
Will try it tomorrow
1 Like
Plasma ISO build ID 2315
Testing in VBox virtual machines.
Falkon working
LibreOffice working
[ruru@omlx-2315 ~]$ systemd-analyze
Startup finished in 1.256s (kernel) + 1.260s (initrd) + 5.695s (userspace) = 8.213s
graphical.target reached after 5.681s in userspace
.
[ruru@omlx-2315 ~]$ systemd-analyze blame
3.381s systemd-udev-settle.service
1.623s vboxadd.service
953ms udisks2.service
749ms ModemManager.service
661ms polkit.service
648ms dracut-initqueue.service
549ms plymouth-quit.service
537ms plymouth-quit-wait.service
487ms NetworkManager-wait-online.service
287ms nscd.service
280ms iptables.service
279ms nftables.service
279ms systemd-logind.service
263ms systemd-update-utmp.service
250ms initrd-switch-root.service
229ms packagekit.service
221ms systemd-vconsole-setup.service
207ms NetworkManager.service
178ms systemd-udev-trigger.service
138ms systemd-resolved.service
124ms systemd-networkd-wait-online.service
100ms systemd-udevd.service
In my opinion we may be ready for Alpha release.
Same here in live mode.
Done.
2 Likes
Getting ready to test ISO 2315.
Some bugs I’m aware of in addition to the Graphics/Wonderful black screen issue that @AngryPenguin and @luca have.
-
Duplicate repos leading to error message when users update with dnf. The duplicates are i686 main and x86_64 main both are listed twice. Described here.
-
Incorrectly named repos for non-free. There are as I recall 3 entries for nonfree instead of non-free. Described here.
-
VirtualBox setting for “Show Toolbar” is not respected. Users has to set this again every time they open VBox. Screen-shot to come in next post.
-
Will add/subtract to list as I test. There are more I can’t remember at the moment.
1 Like
