I click on the Cockpit icon in my favourites and the icon bounces a few times aand then disappears, nothing happens. Why is this?
The first thing to do in a situation where a graphical start of e program does not show anything, is starting ist from a terminal. Then you can see eventual (error) messages.
Hi, all. Juat found an interesting article about YaST being replaced by Cockpit. I have followed the instructions described there for accessing Cockpit, so all sorted!
Install and run cockpit-client-launcher.
Was this an Upgrade from Leap 15.6?
Try to start and post:
systemctl status cockpit.service
It’s always beneficial to post your [possible] solution (article, etc), so others can benefit. It’s also good so some folks can confirm the fix.
Hello,
for some days, cockpit client launcher stopped working for me too : it just didn’t start/open. I don’t know if my situation is the same but in case, I share my problem and my solution :
- Problem :
the service was loaded. You can check with systemctl status cockpit.service, like @Sauerland wrote.
there were errors at start. cockpit-client-launcherreturns :
Traceback (most recent call last):
File "/usr/libexec/cockpit-client", line 23, in <module>
gi.require_version("WebKit", "6.0")
~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.13/site-packages/gi/__init__.py", line 129, in require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace WebKit not available
- Solution for me : after the installation of
typelib-1_0-WebKit-6_0, cockpit client launcher started again without raising any error.
Hope this helps,
Regards
Yes, previously installed and used Cockpit.
entered
- Install cockpit:
zypper in cockpit
2. Enable cockpit:
systemctl enable --now cockpit.socket
3. Open the firewall if necessary:
firewall-cmd --permanent --zone=public --add-service=cockpit
firewall-cmd --reload
as su in konsole. No change, just a brief bouncing icon then zilch.
I now enter “http://localhost:9090/storage” to access Cockpit, can’t remember where I found this in an online article, but it works.
Regards
S
No, new install on Leap 16.0.
I struggled to get Cockpit to work initially, persevered and got it up and running. Then all of a sudden reverted back to a brief bouncing icon and zilch!
S
You don’t need the open firewall port if you are running locally.
You can use cockpit-client-launcher which has a built-in browser.
Opening a browser and entering https://localhost:9090/ is the standard way to open Cockpit locally. I don’t know what you mean by “Click on the Cockpit icon” unless you have cockpit-client-launcher installed.
gunnersson@tulicube:~> cockpit-client-launcher
Traceback (most recent call last):
File "/usr/libexec/cockpit-client", line 20, in <module>
gi.require_version("Gtk", "4.0")
~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/lib64/python3.13/site-packages/gi/__init__.py", line 132, in require_version
raise ValueError('Namespace %s not available for version %s' %
(namespace, version))
ValueError: Namespace Gtk not available for version 4.0
gunnersson@tulicube:~>
So, I use localhost:9090 on Mozilla Firefox. Leap 16.0.
zypper se -s -i cockpit
gunnersson@tulicube:~> zypper se -s -i cockpit
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
S | Name | Type | Version | Arch | Repository
---+-------------------------+--------+-----------------+--------+---------------------------
i | cockpit | Paket | 364-160000.1.1 | x86_64 | openSUSE-Distribution-Leap
i+ | cockpit | Schema | 16.0-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | cockpit-bridge | Paket | 364-160000.1.1 | noarch | openSUSE-Distribution-Leap
i+ | cockpit-client-launcher | Paket | 356-bp160.1.1 | noarch | openSUSE-Distribution-Leap
i | cockpit-firewalld | Paket | 364-160000.1.1 | noarch | openSUSE-Distribution-Leap
i | cockpit-kdump | Paket | 364-160000.1.1 | noarch | openSUSE-Distribution-Leap
i | cockpit-networkmanager | Paket | 364-160000.1.1 | noarch | openSUSE-Distribution-Leap
i | cockpit-repos | Paket | 4.8-160000.1.1 | noarch | openSUSE-Distribution-Leap
i | cockpit-selinux | Paket | 364-160000.1.1 | noarch | openSUSE-Distribution-Leap
i | cockpit-storaged | Paket | 364-160000.1.1 | noarch | openSUSE-Distribution-Leap
i | cockpit-subscriptions | Paket | 16.2-160000.1.1 | noarch | openSUSE-Distribution-Leap
i | cockpit-system | Paket | 364-160000.1.1 | noarch | openSUSE-Distribution-Leap
i | cockpit-ws | Paket | 364-160000.1.1 | x86_64 | openSUSE-Distribution-Leap
i | cockpit-ws-selinux | Paket | 364-160000.1.1 | x86_64 | openSUSE-Distribution-Leap
i | cockpit_client | Schema | 16.0-bp160.1.1 | x86_64 | openSUSE-Distribution-Leap
i+ | patterns-cockpit | Paket | 16.0-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i+ | patterns-cockpit-client | Paket | 16.0-bp160.1.1 | x86_64 | openSUSE-Distribution-Leap
Hinweis: FĂĽr eine erweiterte Suche inkl. nicht momentan aktivierter Remote-Ressourcen bitte
'zypper search-packages' verwenden.
gunnersson@tulicube:~>
zypper se -s -i gtk
gunnersson@tulicube:~> zypper se -s -i gtk
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
S | Name | Type | Version | Arch | Repository
---+----------------------------------+-------+-------------------------------+--------+------------------------------------
i | greetd-gtkgreet-xfce-wayland | Paket | 1.0-bp160.1.2 | noarch | openSUSE-Distribution-Leap
i | gstreamer-plugins-good-gtk | Paket | 1.26.7-160000.2.1 | x86_64 | openSUSE-Distribution-Leap
i | gtk2-engine-murrine | Paket | 0.98.2-bp160.1.1 | x86_64 | openSUSE-Distribution-Leap
i | gtk2-lang | Paket | 2.24.33-160000.2.2 | noarch | openSUSE-Distribution-Leap
i | gtk2-metatheme-adwaita | Paket | 3.28-160000.2.2 | noarch | openSUSE-Distribution-Leap
i | gtk2-metatheme-greybird-geeko | Paket | 3.23.4+git0.c1d46c3-bp160.1.2 | noarch | openSUSE-Distribution-Leap
i | gtk2-theming-engine-adwaita | Paket | 3.28-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | gtk2-tools | Paket | 2.24.33-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | gtk3-branding-openSUSE | Paket | 15.0-lp160.3.1 | noarch | openSUSE-Distribution-Leap
i | gtk3-data | Paket | 3.24.49+14-160000.2.2 | noarch | openSUSE-Distribution-Leap
i | gtk3-lang | Paket | 3.24.49+14-160000.2.2 | noarch | openSUSE-Distribution-Leap
i | gtk3-metatheme-adwaita | Paket | 3.28-160000.2.2 | noarch | openSUSE-Distribution-Leap
i | gtk3-metatheme-greybird-geeko | Paket | 3.23.4+git0.c1d46c3-bp160.1.2 | noarch | openSUSE-Distribution-Leap
i | gtk3-schema | Paket | 3.24.49+14-160000.2.2 | noarch | openSUSE-Distribution-Leap
i | gtk3-tools | Paket | 3.24.49+14-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | gtk4-branding-openSUSE | Paket | 15.0-lp160.3.1 | noarch | openSUSE-Distribution-Leap
i | gtk4-lang | Paket | 4.18.6-160000.2.2 | noarch | openSUSE-Distribution-Leap
i | gtk4-metatheme-greybird-geeko | Paket | 3.23.4+git0.c1d46c3-bp160.1.2 | noarch | openSUSE-Distribution-Leap
i | gtk4-schema | Paket | 4.18.6-160000.2.2 | noarch | openSUSE-Distribution-Leap
i | gtk4-tools | Paket | 4.18.6-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | gtkgreet | Paket | 0.8-bp160.1.10 | x86_64 | openSUSE-Distribution-Leap
i+ | gtkhash | Paket | 1.5-lp160.2.1 | x86_64 | openSUSE-Repositories-Home:C7NhtpnK
i | gtkhash-lang | Paket | 1.5-lp160.2.1 | noarch | openSUSE-Repositories-Home:C7NhtpnK
i | gtksourceview4-lang | Paket | 4.8.4-160000.2.2 | noarch | openSUSE-Distribution-Leap
i | libcanberra-gtk-module-common | Paket | 0.30+2-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | libcanberra-gtk3-0 | Paket | 0.30+2-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | libcanberra-gtk3-module | Paket | 0.30+2-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | libdbusmenu-gtk3-4 | Paket | 16.04.0-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | libgtk-2_0-0 | Paket | 2.24.33-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | libgtk-3-0 | Paket | 3.24.49+14-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | libgtk-4-1 | Paket | 4.18.6-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | libgtk-layer-shell0 | Paket | 0.9.2-bp160.1.3 | x86_64 | openSUSE-Distribution-Leap
i | libgtkmm-3_0-1 | Paket | 3.24.9-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | libgtksourceview-4-0 | Paket | 4.8.4-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | libjavascriptcoregtk-4_1-0 | Paket | 2.52.5-160000.1.1 | x86_64 | openSUSE-Distribution-Leap
i | libqt5-qtbase-platformtheme-gtk3 | Paket | 5.15.17+kde122-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | libwebkit2gtk-4_1-0 | Paket | 2.52.5-160000.1.1 | x86_64 | openSUSE-Distribution-Leap
i | libwlembed-gtk3-0-0 | Paket | 0.0.0-bp160.1.2 | x86_64 | openSUSE-Distribution-Leap
i | libwx_gtk2u_core-suse16_0_0 | Paket | 3.2.8-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | qt6-platformtheme-gtk3 | Paket | 6.9.1-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i+ | thunar-plugin-gtkhash | Paket | 1.5-lp160.2.1 | x86_64 | openSUSE-Repositories-Home:C7NhtpnK
i | typelib-1_0-Gtk-3_0 | Paket | 3.24.49+14-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | webkit2gtk-4_1-injected-bundles | Paket | 2.52.5-160000.1.1 | x86_64 | openSUSE-Distribution-Leap
i | WebKitGTK-4.1-lang | Paket | 2.52.5-160000.1.1 | noarch | openSUSE-Distribution-Leap
i | xdg-desktop-portal-gtk | Paket | 1.15.3-160000.2.2 | x86_64 | openSUSE-Distribution-Leap
i | xdg-desktop-portal-gtk-lang | Paket | 1.15.3-160000.2.2 | noarch | openSUSE-Distribution-Leap
Hinweis: FĂĽr eine erweiterte Suche inkl. nicht momentan aktivierter Remote-Ressourcen bitte
'zypper search-packages' verwenden.
gunnersson@tulicube:~>
That URL is not reliable for subsequent executions.
Use “http[s]://localhost:9090/”
gunnersson@tulicube:~> cockpit-client-launcher
Traceback (most recent call last):
File "/usr/libexec/cockpit-client", line 20, in <module>
gi.require_version("Gtk", "4.0")
~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
File "/usr/lib64/python3.13/site-packages/gi/__init__.py", line 132, in require_version
raise ValueError('Namespace %s not available for version %s' %
(namespace, version))
ValueError: Namespace Gtk not availa
As root:
zypper in typelib-1_0-Adw-1
2 Likes
This is plain wrong. You can bookmark and use any subpage of the Cockpit webpage. If you are not authenticated yet when accessing the page, it will ask for your PW and proceede.
http://localhost:9090/cockpit-repos
http://localhost:9090/packages
http://localhost:9090/system
http://localhost:9090/system/terminal
http://localhost:9090/system/logs
http://localhost:9090/system/services
http://localhost:9090/apps
http://localhost:9090/storage
http://localhost:9090/network
http://localhost:9090/users
(and more dependend on the installed/enabled Cockpit apps)
…
If you only use some or one of the subpages, it makes absolutely sense to bookmark and use it for faster access.
1 Like
Now:
gunnersson@tulicube:~> cockpit-client-launcher
Traceback (most recent call last):
File "/usr/libexec/cockpit-client", line 23, in <module>
gi.require_version("WebKit", "6.0")
~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^
File "/usr/lib64/python3.13/site-packages/gi/__init__.py", line 129, in require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace WebKit not available
gunnersson@tulicube:~>
1 Like
zypper in typelib-1_0-WebKit-6_0 ?
Thank you @Sauerland !