Kalpa clean install but no desktop after reboot

English Install/Boot/Login
1

Hello,

I am getting a blank screen after the first reboot. Configured auto login during install. Keyboard input works so I am able to login via cli.

Splash does not show errors during boot or shut down.
Using iso from 20th june and latest ventoy.

Any help would be great.

2

Should not use an install helper the iso should be boot ready

1 Like
3

Ventoy is not recommended nor supported by openSUSE. Ventoy adds boot parameters to openSUSE images, which renders the system broken. Additionally there where recently security issues discovered with Ventoy (undocumented blobs).
When you open an openSUSE bugreport and it gets known that you used Ventoy for installation, the bugreport will be closed as invalid due to the above reasons.

You can use it, but do not expect any support from the openSUSE maintainers when issues due to this tool occur.

1 Like
4

I’ve heard something vaguely about ventoy’s security issue in the past, but I thought that it would be resolved by now. Best practice would be to create a thumbdrive then without the use of ventoy. Will report back asap. Thank you for the advice.

5

It is far from being resolved…

6

By the way the same thing happens in boxes and virtualbox…

7

Pinging @sfalken

8

That was always the case. I guess nobody advised to use any other tool then dd or something that you are 100% certain that it does nothing more then dd.

Why would one even try to “resolve” an issue that is not an issue because you should not use that product for what you want to do at all.

9

Using Ventoy means (not only on openSUSE)

  • no support
  • not getting the intended installed system
10

I use(d) that product for multiple use cases. There is more out there than opensuse distro’s (that apparently don’t work with ventoy).

But the problem and concern around the blobs are valid regardless and should be resolved so this cool tool can be used safely.

11
12

Found something here too:

13

You don’t get the point. Ventoy is a problem, not openSUSE ( or other distros ). Despite of their promises and claims, they have not fixed it. You, as a consumer, do not get what you intended. There is something fundamentally wrong with it’s design and code.

14

sudo systemctl disable display-manager-legacy.service
sudo systemctl enable --now sddm.service

This is the “fix” and it’s the only one. I apologize for this breakage, but I don’t have the ability, nor do I want the ability to be able to enable and disable services on other peoples running systems. There are likely to be a few more things like this, as I get Kalpa into shape for a Beta announcement.

1 Like