OMLx 4.0 Pre-Alpha ISO Plasma development builds

rugyada · 2018-10-02 11:29:30 UTC

Products available for download [HERE]

Testing in VBox virtual machines.

- Build 2232 still showing the “Calamares Initialization Failed" issue;
- Plasma Desktop so far looks mostly usable;
- Still very loooong time before live desktop show up (~5 min.);
- Logout/login working;
- Firefox working;
- Falkon not working;
- Leafpad install test: install looks successful (sorry no screenshots) but launching the app made the desktop crash and exit, returning to sddm. Once entered, got a message error “Could not start ksmserver”;
- Libreoffice made the desktop crash and exit too.

.
Some screenshots

@Cooker

Colin · 2018-10-02 13:50:37 UTC

Hi Ruru,
I just did a new build and can confirm the calamares issue; the services module is missing. As for the slow startup something is blocking the X server if you do ctrl+F2 (i.e. try to get a virtual console) the system will startup immediately. Doing this seems to trigger the bootup to continue.

rugyada · 2018-10-02 14:04:30 UTC

Hi,

yes the report above is for 2232 Plasma ISO.
I added just now 3 more screenshots with pkexec /usr/bin/calamares -d command for a verbose output. Hope it helps.

Did not know, will try thanks.
In my opinion the calamares issue need to be solved asap, so we can test the system installed.

ben79 · 2018-10-02 18:19:42 UTC

Ummm… Noodling around with it feels like things underneath still aren’t ready. Like the already noted LO crashing desktop. Here’s a little thing that should be fixed soonish.

This is because permissions for /usr/share/konsole/OMV.profile are set to 0644. I believe our users would be happier if we set this to 0744 so user can change look of their konsole. Obviously the work around is:

# chmod 744 /usr/share/konsole/OMV.profile

On a more positive note dnf works:

this also shows consequences of workaround for konsole permissions.

On a negative note trying to attach a file to thunderbird cashes it sending user on a search for a workaround.

So definitely a work in progress.

But it is good we have an ISO builder that is working, and the download issue is fixed, the graphics in VBox issue is fixed, and except for having to “trick” system in to booting with ALT>F2 >>> ALT>F1 the boot issue in VBox is mostly fixed. Will be interesting to see what devs come up with after mass rebuild is finished new package lists are created and Calamares gets fixed. Things might get interesting.

ben79 · 2018-10-02 18:24:41 UTC

While we’re talking about things to fix here’s another one.

Post-edit: Worth noting is that a lot of problems will likely be resolved by developers finishing mass rebuild and then developers doing their normal magic to get an ISO ‘really’ ready for us Alpha testers.

rugyada · 2018-10-02 18:46:07 UTC

To change the look of konsole just create a new profile.
Menu Settings > Manage Profiles > New Profile

bero · 2018-10-02 18:46:25 UTC

Why would you want to make a konsole profile executable (644 -> 744: Afterwards executable by owner)?

Also, users certainly shouldn’t be able to write to anything in /usr/share/konsole (because that’s the system wide files used by every user). konsole automatically creates new override files in the user’s home directory when changing settings.

LO doesn’t crash the desktop on real HW (at least not on mine, Threadripper with an AMD GPU).

Alt+F2/Alt+F1 isn’t necessary on real HW either.

Maybe VB needs some fixing.

rugyada · 2018-10-02 18:53:39 UTC

Installed calamares-3.2.2-2 in live mode.
Now better, but installation failed with the error in screenshot
Console log here

TPG · 2018-10-02 19:00:07 UTC

This is cause by missing typelib() requires on some g* packages on network-manager-applet, tuned, hplip-systray, firewalld-applet

TPG · 2018-10-02 19:00:49 UTC

This is because if broken OpenGL/EGL support.

Please run glxinfo

TPG · 2018-10-02 19:08:39 UTC

New calamares -3 is building, with fixed settings. If you like you can edit /etc/calamares/modules/services.conf

and remove line with - services-openrc
then you can start calamares and try to install it

rugyada · 2018-10-02 19:14:27 UTC

Thanks @TPG
Now I created a new vbox machine. Will wait for calamares -3 to finish building, install it and report.

ben79 · 2018-10-02 19:28:29 UTC

That is not what I want but just what I found. What I want and probably users in general will want is simply to be able to adjust their profile without having to resort to a work around. It should be noted that the very first thing the error message says is to “either change the permissions of the configuration of the profile configuration file”. So I would say that based on what @bero says that error message should be changed.

If I was really smart I would have checked permissions on the same file in Lx 3 which are the same at 0644 as they are on the # 2232 ISO so the problem lies elsewhere. But again the point is more related to users being able to set things to their liking without having to resort to a workaround. If there has been a policy change either in OpenMandriva or upstream then the error message should indicate that. It doesn’t so at the moment at least I’m considering this a bug. Post-edit: All I want is to be able to make settings in Konsole in Lx 4.0 exactly the same as I already can in Lx 3.

And apologies if my knee jerked and I did the first thing the error message suggested as a work around. Setting a new profile is the better and safer workaround.

rugyada · 2018-10-02 21:13:48 UTC

Works!

Console log here

ben79 · 2018-10-02 23:40:04 UTC

Where is the package? I can’t find.

# dnf upgrade calamares
Repository cooker-i686 is listed more than once in the configuration
Repository cooker-i686-debuginfo is listed more than once in the configuration
Repository cooker-testing-i686 is listed more than once in the configuration
Repository cooker-testing-i686-debuginfo is listed more than once in the configuration
Repository cooker-updates-i686 is listed more than once in the configuration
Repository cooker-updates-i686-debuginfo is listed more than once in the configuration
Repository cooker-testing-x86_64 is listed more than once in the configuration
Repository cooker-testing-x86_64-debuginfo is listed more than once in the configuration
Repository cooker-updates-x86_64 is listed more than once in the configuration
Repository cooker-updates-x86_64-debuginfo is listed more than once in the configuration
Repository cooker-x86_64 is listed more than once in the configuration
Repository cooker-x86_64-debuginfo is listed more than once in the configuration
OpenMandriva 4.0 - x86_64                                                                                                                   126  B/s | 169  B     00:01    
OpenMandriva 4.0 - x86_64 - Updates                                                                                                         125  B/s | 169  B     00:01    
Failed to synchronize cache for repo 'openmandriva-x86_64', ignoring this repo.
Failed to synchronize cache for repo 'updates-x86_64', ignoring this repo.
Last metadata expiration check: 1 day, 1:50:33 ago on Mon 01 Oct 2018 09:47:41 PM UTC.
Dependencies resolved.
Nothing to do.
Complete!

# rpm -qa calamares
calamares-3.2.2-1.x86_64

# dnf repolist
Repository cooker-i686 is listed more than once in the configuration
Repository cooker-i686-debuginfo is listed more than once in the configuration
Repository cooker-testing-i686 is listed more than once in the configuration
Repository cooker-testing-i686-debuginfo is listed more than once in the configuration
Repository cooker-updates-i686 is listed more than once in the configuration
Repository cooker-updates-i686-debuginfo is listed more than once in the configuration
Repository cooker-testing-x86_64 is listed more than once in the configuration
Repository cooker-testing-x86_64-debuginfo is listed more than once in the configuration
Repository cooker-updates-x86_64 is listed more than once in the configuration
Repository cooker-updates-x86_64-debuginfo is listed more than once in the configuration
Repository cooker-x86_64 is listed more than once in the configuration
Repository cooker-x86_64-debuginfo is listed more than once in the configuration
OpenMandriva 4.0 - x86_64                                                                                                                   126  B/s | 169  B     00:01    
OpenMandriva 4.0 - x86_64 - Updates                                                                                                         126  B/s | 169  B     00:01    
Failed to synchronize cache for repo 'openmandriva-x86_64', ignoring this repo.
Failed to synchronize cache for repo 'updates-x86_64', ignoring this repo.
Last metadata expiration check: 1 day, 1:53:53 ago on Mon 01 Oct 2018 09:47:41 PM UTC.
repo id                                                                  repo name                                                                                    status
cooker-updates-x86_64                                                    OpenMandriva Cooker - x86_64 - Updates                                                            0
cooker-updates-x86_64-contrib                                            OpenMandriva Cooker - x86_64 - Contrib - Updates                                                  0
cooker-updates-x86_64-non-free                                           OpenMandriva Cooker - x86_64 - Non-free - Updates                                                 0
cooker-updates-x86_64-restricted                                         OpenMandriva Cooker - x86_64 - Restricted - Updates                                               0
cooker-x86_64                                                            OpenMandriva Cooker - x86_64                                                                 16,868
cooker-x86_64-contrib                                                    OpenMandriva Cooker - x86_64 - Contrib                                                       10,915
cooker-x86_64-non-free                                                   OpenMandriva Cooker - x86_64 - Non-free                                                         155
cooker-x86_64-restricted                                                 OpenMandriva Cooker - x86_64 - Restricted                                                       145

ben79 · 2018-10-03 00:08:04 UTC

You idiot try:

# dnf --refresh upgrade calamares

My brain does not grasp needing to tell dnf to refresh if I’m requesting an upgrade but that appears to be necessary.

Anyway now result:

ben79 · 2018-10-03 00:14:19 UTC

OK, now this is complaining but do we need 8.5 GB swap partition to go with 6.2 GB /? Seems odd.

Anyway it’s easy to use ‘Manual Partitioning’ so not much of a complaint unless you think about all the users that will just accept the default.

And it may be worth pointing out to myself and others that we do have some very Pre-pre-alpha testing going on here so maybe premature to be reporting a lot of issues.

But, but, it has been so long since we had anything to test…

ben79 · 2018-10-03 00:47:14 UTC

OK, so here’s latest result with this version of calamares:

$ rpm -qa calamares
calamares-3.2.2-3.x86_64

Here is entire konsole output of ‘pkexec /usr/bin/calamares -d’:

Cooker-calamares-konsole.txt (34.3 KB)

Post-edit: Don’t think this is relevant but just in case here is ‘/etc/calamares/modules/services.conf’:

calamares-services.conf.txt (912 Bytes)

Post-edit-2: My buzzards luck with Cooker/Lx 4.0 continues unabated.

TPG · 2018-10-03 07:41:54 UTC

@ben79 This is very strange error:

grub2-install: error: efibootmgr failed to register the boot entry: Unknown error 19559280.

I’ve registered an issue for efibootmgr:

I’m building new efibootmgr-17 so please try with it.

ben79 · 2018-10-03 09:11:51 UTC

I will try. This seems to be a VBox issue, I was able to install in hardware with calamares-3.2.2-3.x86_64.

However there are partitioning issues in hardware install. I could not install to an existing partition so I ended up installing on some free space I had.

The reason it would not install on existing partition is a case of OpenMandriva mounting disease, I tried umount from cli and unmounting with KDE Partition Manager and neither worked. So I seemed to be forced to install on unused disk space. Not everyone is going to have unused disk space.