ISO Build ID 2315 VirtualBox installation. Hardware testing will happen soon I hope as well.
I would be remiss if I did not acknowledge that there have been many bugs fixed as of this ISO so thanks to all or our hard working developers.
Host system is fully updated Cooker with VBox 5.22. I set memory to 4GB and disk size to 20GB.
Booting to ‘Live’ takes about 2 minutes.
The weirdest thing of all to me is that if I use ‘Erase disk’ for partitioning it wants to set a / of 11.2GB and swap of 8.5GB? I’m told the gargantuan swap partition has to do with hibernation and how much memory users selects to use for VM? I wish there was a better solution for this, really I do. But as it is I don’t use hibernate and am not doing 8.5GB swap partitions so I used ‘Manual Partitioning’. I set a 18.7GB / and a 1GB swap instead.
System installs without error.
First boot in to installed system took 1 minute and 33 seconds. Note: I am measuring actual boot time from Grub2 menu until sddm login screen first appears with a stop watch (without any tricks). In my experience systemd-analyze is not measuring actual boot time and is only useful for tracing actual systemd problems. I am trying to measure what users actually will experience not something that may be hypothetical. For instance this is what systemd-analyze reports for this 1 min. 33 sec. boot:
Startup finished in 993ms (kernel) + 993ms (initrd) + 4.000s (userspace) = 5.987s
graphical.target reached after 3.991s in userspace
So something takes an additional 1 min. and 27 sec. to boot beyond what systemd is doing in this instance. Post-edit: Also during boot Plymouth screen shows briefly like a second or less then I see a black screen until what ever decides to show sddm login screen. Also for perspective a Lx 3 VM with same settings on same host machine boots in about 20-25 seconds which I consider to be normal. So a minute and half is excessive without a doubt. Post-edit-again: If I boot and keep pressing the ESC key on kbd system boots in a normal 20-25 seconds. So what the bleep is causing this if I or user doesn’t do some kbd trick???
All that being said the ISO boots, installs, and works apparently normally except for booting time.
An issue I don’t believe I’ve noted before in this thread:
User can not edit current profile in Konsole, this is different behavior than I have seen previously as in Lx 3 for instance. If it is not intentional then this is a bug. If this is intentional then this is stupid but easy to work around.
Expected behavior is that user should be able to make changes to Konsole profile without becoming root or changing permissions. In other words expected behavior is to have this work like it always has. If I ever find out if this change in behavior is intentional or not I’ll know whether to file a bug report on this. If anyone knows please illuminate me.
So far I have filed these bug reports against Cooker repos (these are issues mentioned earlier in this thread):
Repository cooker-x86_64 is listed more than once in the configuration
Repos incorrectly named with incorrect URL’s
Lx 4 repo enabled in Cooker installation.
These bug reports are in the interest of making Lx 4 as professional and polished as we are capable. None are major and so far none affect usability, all are easy to work around. But the other side of the coin is that all would be super easy to fix so why not do so?
There are other bugs for instance some with VirtualBox mentioned earlier in this thread. I’ll endeavor to document these as I go with testing.
Post-edit: Lets get some logs in here since I have reported some issues;
journalctl-b.txt (71.8 KB)
dmesg.txt (45.3 KB)
Host machine hardware inxi -F:
inxi-F.txt (1.9 KB)
And may I be the first to wish you all a Merry Christmas and a Happy New Year and Happy Holidays or all of those.