In LEAP 16, yast2 won't run in graphical mode

English Applications
1

I installed Yast2 with Myrlyn, and when I try to use it, I get
ο»Ώqt gui wanted but not found
There are no yast2 qt modules listed.
qt6 is installed. How to fix?
I cannot figure out hoe to use Cockpit.

2

SDB:System_upgrade_to_Leap_16.0#Major_changes

Most of YaST stack was removed from SLES 16 and therefore Leap

leap-16-enters-beta

  • The traditional YaST stack is retired in favor of:
  • Cockpit for system management
  • Myrlyn as a drop-in replacement for the YaST Software GUI (Note: YaST is still available in Tumbleweed but will no longer be developed. YaST has been removed from Leap 16 and Myrlyn takes on this role of software installation like YaST. If someone is interested in the maintanece of YaST for further development and bugfixes, the sources are available on github.)

As of Leap 16, Yast2 is dead and buried. So you don’t have much choice:

  • Tumbleweed, while yast is still available (not for long)

  • Use Cockpit, even if it’s much less complete

  • switch to mageia and its control center (draktools)

3

For Cockpit, have a look here…

See chapter for TW and Leap for installation, and line at the bottom for how to access it in browser.

https://cockpit-project.org/running#tumbleweed

4

I can’t get the Cockpit service to start. Nor can I get the socket to work.

 
localhost:~ # systemctl enable --now cockpit.socket
Job failed. See "journalctl -xe" for details.
localhost:~ # journalctl -xe
β–‘β–‘ 
β–‘β–‘ A start job for unit UNIT has finished successfully.
β–‘β–‘ 
β–‘β–‘ The job identifier is 10883.
Jul 06 15:58:40 localhost.localdomain systemd[2703]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (>
β–‘β–‘ Subject: A start job for unit UNIT has finished successfully
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
β–‘β–‘ 
β–‘β–‘ A start job for unit UNIT has finished successfully.
β–‘β–‘ 
β–‘β–‘ The job identifier is 10887.
Jul 06 15:58:40 localhost.localdomain systemd[2703]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (>
β–‘β–‘ Subject: A start job for unit UNIT has finished successfully
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
β–‘β–‘ 
β–‘β–‘ A start job for unit UNIT has finished successfully.
β–‘β–‘ 
β–‘β–‘ The job identifier is 10891.
Jul 06 15:58:40 localhost.localdomain systemd[2703]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (>
β–‘β–‘ Subject: A start job for unit UNIT has finished successfully
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
β–‘β–‘ 
β–‘β–‘ A start job for unit UNIT has finished successfully.
β–‘β–‘ 
β–‘β–‘ The job identifier is 10895.
Jul 06 15:58:40 localhost.localdomain systemd[2703]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (>
β–‘β–‘ Subject: A start job for unit UNIT has finished successfully
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
β–‘β–‘ 
β–‘β–‘ A start job for unit UNIT has finished successfully.
β–‘β–‘ 
β–‘β–‘ The job identifier is 10899.
Jul 06 15:58:40 localhost.localdomain systemd[2703]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (>
β–‘β–‘ Subject: A start job for unit UNIT has finished successfully
β–‘β–‘ Defined-By: systemd
β–‘β–‘ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
β–‘β–‘ 
β–‘β–‘ A start job for unit UNIT has finished successfully.
β–‘β–‘ 
β–‘β–‘ The job identifier is 10903.
Jul 06 15:58:40 localhost.localdomain systemd[2703]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds i>
lines 7476-7520/7520 (END)
5
  1. YaST has been deprecated - β€œold” news, as they say.
  2. Time to learn how to use it :+1:

An easy option is to execute the Discover app. Next, search for β€œCockpit Client” (Flatpak). Install. Done.

6

To any openSUSE Administrators who might be watching.

This thread is not about Tumbleweed (odd marked as such).

It should be marked for β€œleap-16-beta”.

1 Like
7

There was no choice for Leap 16 beta.

9

You don’t understand , I think … read my reply again … it does NOT matter what happened during install

10

image
image1198Γ—754 122 KB

Discover claims I have no internet

11

I do not see any claim of no internet

If you think of the β€œRed exclamation point”, it’s because it’s still working to update info.

12

Leap 16 Beta here … in Discover, confirming Cockpit installed

cc
cc937Γ—382 67.8 KB

13

Please listen to what the others said already. There is no way you are gonna run YaST on Leap 16. Rather ask for help on getting Cockpit to work. ( in a new thread ). Before doing so, please search the forums, your solution might already be out there

1 Like
14

This is a known bug.
https://bugzilla.opensuse.org/show_bug.cgi?id=1243078

15

Been running all night. Discover still not working

image
image1191Γ—759 145 KB

16

Leap 16.0 is planned not to have Qt5 anymore which the YaST2 Qt UI (libyui-qt) needs, so we had to disable it.

The NCurses UI is still available; use a terminal window and start it with

sudo yast (not yast2) for the YaST NCurses control center or
sudo yast <module-name> to start a YaST module directly or
sudo yast --list to list the modules.

Be aware that YaST will likely be removed for the final version of Leap 16.0 completely.
You might want to familiarize yourself with Myrlan for package management and Cockpit for the other system administration tasks.

2 Likes