Leap16.1 Beta1 and problems

Tested on private PC , Existing Win10 and same problem whit partions as Leap16…, . Likewise tested SLES 16.1 in the cloud whit a colleague.

Yes, - the horse have left the barn.
Regards

1 Like

Without a proper explanation about your issue or request for assistance, the post is somewhat meaningless.

I’ve just installed Leap 16.1 (yep .1) on a third machine and had zero issues. And yes, I did custom partitioning (altering to use XFS).

It took me about 20 minutes. (with KDE)

16.1 Alpha… I could never get 16 installed and gave up, but let me try this alpha and see what happens.

Not seeking assistance just a wittle rant about the agama installer. :stuck_out_tongue_winking_eye:

1 Like

If you have ideas or concerns about Agama, it’s best to share them directly and constructively with the project upstream:

https://github.com/agama-project/agama

That way they can be properly reviewed and addressed.

1 Like

it’s clearly stated you have some missing settings with software did you try to rectify these problems ? if so ? what software settings you have right now ?

1 Like

Yeah, I’m seeing the same thing. SELinux Support is the only thing with a check, but after clicking on a few other things, the message is still there and it’s not clear what’s missing. :thinking:

No issues at all…

2 Likes

So likely user error not yet disclosed?

1 Like

Yeah, a undisclosed user error.

Alpha testers need to bring a minimum of linux knowledge and skills. To give the developers a chance to fix a potential issue, testers must be able to do some basic troubleshooting steps. Providing a reliable way to reproduce the issue and describing the steps done are the minimum informations needed for the devs.

3 Likes

if you took a screen shot from these setting someone could help you

1 Like

@jonte1 Again a waste of my time. I went out to test in a VM, but did check and … Leap 16 Beta 1 has not been released. FULL STOP.

1 Like

you should select the software in the “software” item.

At least one alpha tester was able to pin it down to a missing internet connection. Agama logs are required for further analysis.
https://bugzilla.opensuse.org/show_bug.cgi?id=1261150