LEAP 16 beta cockpit issues

I finally got cockpit to run by deleting the cockpit-* user and group.
But now I have problems using it.

The GUI is very non-responsive in Chromium and Firefox. If I am in administrative mode, for example, the page will not refresh. Clicking on the left-column items usually does nothing. I have to use the arrow keys to move from menu to menu.

SELinux seems to be blocking Cockpit from doing its things:


How do I turn SELinux off? I did not select it to be installed.

I have cockpit-packagekit installed, but Cockpit will not do updates saying

Current system is not transactional
Only systems managed by transactional-update are supported, please use cockpit-packagekit instead

How do I use cockpit-packagekit in Cockpit? (it did start).

In general, the GUI takes up too much space compared to Yast2. It is painful to scroll through the Services list.

Maybe I’m confused. I’ve been watching the other Cockpit thread from the OP.

I have never gone thru all the trouble to get Cockpit running on Leap 15.6 and 16. I simply run Discover, then install (one-click) the Cockpit Client, and that’s it. No services to install or enable, and no additional packages via YaST or Myrlyn . Am I missing something (?)

Is @jarome installing this way to administer remote machines?

Two screenshots below for 15.6 and 16.

You can see a Cockpit running, alongside proof there are no additional packages or services running.

(yes, it’s my understanding if you’re gonna use Cockpit to admin remote machines, you have to do that).

15.6 Cockpit

16 Cockpit

@aggie that would be the Flatpak version… I use that here as can connect to multiple systems with it, I only installed to test. Likewise the OP is on a M1 ARM Mac with Parallels and ARM architecture…

1 Like

I am just trying to replace Yast2 on my local machine. Remote settings of system stuff scares me, frankly. Cockpit was installed in the ARM alpha dist that I installed.
Discover will not install software since it says no internet (a known bug apparently).
How do I install cockpit client with zypper?

@jarome the flatpak version, if so flatpak --user install org.cockpit_project.CockpitClient

If going to use that, then suggest you uninstall the rpm cockpit packages.

Look at the first screenshot … is that what you’re referring to?
If yes, that is an erroneous error message because of some simple bug that hasn’t been fixed yet.

That message ONLY shows up if you are on the Home tab. Notice the second screenshot, showing us the Updates to be installed - if there really is a ā€œcan’t connect to Internetā€ issue, those update would have the error too. If I click back to the Home tab, that erroneous error message will show up again.

Erroneous error that shows up for everyone on Leap 16

Click on other tabs … no more ā€œInternet errorā€ message

I clicked Update All … a minute later, this screen shows those two have been updated, so yea, Internet connection in Discover works :+1:

Discover on Leap 16 can’t see any RPMs from the openSUSE repos. So also the ā€œInstalledā€ tab is affected.

Because these are Flatpaks from Flathub and not RPMs from the official repos.

The bugreport which explains the reason for the Discover issue:
https://bugzilla.opensuse.org/show_bug.cgi?id=1243078

  1. See the first screenshot - Installed works here … as a matter of fact, I clicked on EVERY tab just now, and no error message … the ONLY error I get is when I click on the Home tab (previously shown).
  2. The focus in this thread is about Cockpit, plus a suggestion to install the Flatpak version of Cockpit (Cockpit is the main subject matter), vs using the lower-level (rpm-oriented) install. The Cockpit-Client via Flatpak is a quick install.

Not sure where the ā€œrpm discussionā€ is in here … use Myrlyn for the rpm stuff.
.
Installed tab shows the proper content - no errors:

This shows All Applications … also, all other tabs show correctly - the only tab that shows an error is Home.

You may want to read the bugreport and what was written (and may have a second look on your screenshots). Discover on Leap 16 ONLY shows flatpaks and no RPMs.
Bildschirmfoto_20250709_170807
I wanted to point out that your claim that only the home tab is affected is not correct. ATM Discover on Leap 16 is not usable as it was in Leap 15.6 (and prior) due to the fact that it can’t see RPMs (as explained in the bugreport).

I installed Tumbleweed in parallels on my Mac Studio. Parallels Tools would not install (but they do on LEAP 16). So it is kinda unusable. But cockpit was not in the default install, and I could not find it. After the install, Myrlyn installed cockpit (I selected most of them) and it ran in a browser window. I did not see the GUI issues I saw with Leap 16 beta.

Back to LEAP 16-beta. I was unable to install cockpit client:

localhost:~ # zypper install flatpak
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
'flatpak' is already installed.
No update candidate for 'flatpak-1.16.0-160000.1.40.aarch64'. The highest available version is already installed.
Resolving package dependencies...
Nothing to do.
localhost:~ # flatpak --user install org.cockpit_project.CockpitClient
Looking for matches…
error: No remote refs found for ā€˜org.cockpit_project.CockpitClient’

Do I need to add a repository?
What do I need to uninstall to use flatpak only?

@jarome use flatpak --user remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo then should be good to install.

If you run zypper se -i cockpit and then uninstall those packages.

@jarome I’m guessing the Tumbleweed install included the use of SELinux?

I got errors when I tried to turn SELinux off in the Tumbleweed install.
I am starting a new install of the 16beta distro in Parallels. Any advice?

So on new installation, the cockpitclient installed. How do I run it? Still in a browser on 9090?
And also, as an aside, why do firefox windows have a big black border?

How to install flatpak version of cockpit?

As user (not root):

flatpak --user install org.cockpit_project.CockpitClient

(After you have added the flathub remote as explained by Malcolm.)

I did it as root, and then again as myself. But I don’t think that the flatpak version of cockpit is installed. myrlyn shows no cockpit things are installed.
How do I start cockpitclient?

Myrlyn only shows RPMs. Flatpaks are a completely different package format.

To run the flatpak Cockpit:

flatpak run org.cockpit_project.CockpitClient

As root, or as me?
Root worked, but just one line for login. Root pwd did not work.
As me, it complained:
jar@leap16beta:~> flatpak run org.cockpit_project.CockpitClient
error: app/org.cockpit_project.CockpitClient/aarch64/master not installed