OK, and how? in Myrlyn?
Myrlyn and Cockpit are completely different tools.
Cockpit can be reached via https://localhost:9090 or https://your-IP-address:9090 in a browser (if you have it properly installed). The following screenshot shows the cockpit-packages module (which is completely independent from Myrlyn. Myrlyn is a package management tool only. Cockpit is a replacement for YaST).
@ hui
Thanks for the explanation.
Maybe I’ve understood the rules of Myrlyn and Cockpit.
Only another think: when I try
> firefox https://localhost:9090
I get this:
Not very ideal
If you need to configure CUPS manually, then the CUPS web interface is a means for doing that. YaST adds no value here at all. In general though, most modern network printers are capable of driverlesss IPP printing, with no explicit configuration required, (other than adjusting the firewall to allow mdns to facilitate discovery).
I installed cockpit via zypper (it is in the OSS repos for Slowroll and TW).
sudo zypper in cockpit
All the necessary components were installed…
~> zypper se -si cockpit
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+------------------------+---------+-----------+--------+-----------
i+ | cockpit | package | 334.1-5.1 | x86_64 | repo-oss
i | cockpit-bridge | package | 334.1-5.1 | x86_64 | repo-oss
i | cockpit-networkmanager | package | 334.1-5.1 | noarch | repo-oss
i | cockpit-packagekit | package | 334.1-5.1 | noarch | repo-oss
i | cockpit-storaged | package | 334.1-5.1 | noarch | repo-oss
i | cockpit-system | package | 334.1-5.1 | noarch | repo-oss
i | cockpit-ws | package | 334.1-5.1 | x86_64 | repo-oss
It is socket activated so make sure cockpit.socket is enabled…
~> sudo systemctl enable --now cockpit.socket
Created symlink '/etc/systemd/system/sockets.target.wants/cockpit.socket' → '/usr/lib/systemd/system/cockpit.socket'.
dean@dell-laptop:~> sudo systemctl status cockpit.socket
● cockpit.socket - Cockpit Web Service Socket
Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; enabled; preset: disabled)
Active: active (listening) since Wed 2025-05-21 08:04:10 NZST; 16s ago
Invocation: 5cdb98ce187d4d8f8a5709e898380c7c
Triggers: ● cockpit.service
Docs: man:cockpit-ws(8)
Listen: [::]:9090 (Stream)
Process: 8587 ExecStartPost=/usr/share/cockpit/issue/update-issue localhost (code=exited, status=0/SUCCESS)
Process: 8601 ExecStartPost=/bin/ln -snf active.issue /run/cockpit/issue (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 9171)
CPU: 33ms
CGroup: /system.slice/cockpit.socket
May 21 08:04:10 dell-laptop systemd[1]: Starting Cockpit Web Service Socket...
May 21 08:04:10 dell-laptop systemd[1]: Listening on Cockpit Web Service Socket.
As a regular user, I don’t find it particularly useful in its current state, but that will inevitably change as modules are developed and added.
As already reported, cockpit is installed and followed lines has been already given:
systemctl enable --now cockpit.socket
type or paste code here
$EDITOR /etc/cockpit/disallowed-users
Nevertheless I get
About installing printer driver with CUPS. Yes, I’ve done it in the past sometimes too, but a couple years ago it was no more possible for me. Also changing printer properties is a problem. The last is in YAST quicker and less complicate as with CUPS.
About you other comments I have already written in this thread.
Sincerely, I regret, that YAST will be no more in the next Leap and in the final version of unchangeable SUSE OS, first of all because there are no Leap offshoot.
That message is a result of the connection being https but using a self-signed certificate. There’s no certificate trust chain, so of course FF is going to complain about it.
Self-signed certificates are useful for this type of thing, but it’s reasonable for your browser to alert you to it, because if a website is using a self-signed certificate, that’s potentially a security risk.
But there’s no reasonable way to distribute a “pre-built” SSL certificate, because then you’d have a valid public/private key pair that could be used in ways that would be genuinely harmful.
Better to have a self-signed certificate that doesn’t have a trust chain (and be able to log in remotely over an encrypted connection) as opposed to sending your user and/or root credentials over the network in the clear.
But, as I said earlier - if enough people step up to contribute to maintaining YaST, then certainly something could come of that effort. We are an open source community - and that’s how stuff gets done: Interested people come together and make it happen.
2 Likes
You’d need to start another dedicated topic for this. It is the native graphical way of configuring printers, and for the most part these days no configuration should be required.
+1 to Jim’s explanation re the browser notification.
That’s exactly my thoughts. We’ve always rolled with he changes and SUSE will fill users’ needs on their commercial products for certain.
Then you have the guys who know their stuff and they’ll beef up Cockpit now that the main interface and underlying services are available.
I can see ARGB control and maybe even things that are done by cpupower-gui and CoolerControl. Maybe those will stay just like they are, but nothing would surprise me.
I installed the Cockpit Flatpak and removed it thinking the openSUSE version would be better. It is, by far, much better.
One thing it doesn’t have is Generate Report. At least I couldn’t find it in the TW repos. I installed the Mageia 10 Cauldron packages and they do generate the report.
Maybe they’re named different in openSUSE but I couldn’t find them. They’re called sos 4.9.0-1 and Cockpit-sosreport 338-1.
Since Cockpit is supposed to be universal I figured they’d work and they appear to be working fine. I didn’t find Leap packages for them either. But this is what I think we can expect. Plenty of new modules to do things users need.
Yes, cockpit-sosreport would be a useful component to have. (No official package available yet.)
https://software.opensuse.org/package/cockpit-sosreport?search_term=sosreport
1 Like
@deano_ferrari I assume the sos package is needed.
https://build.opensuse.org/projects/openSUSE:Factory/packages/cockpit/files/cockpit.spec?expand=1
Edit: So it’s just a tarball with system information to attach to a bug report, openSUSE already provides this with the support config tools, the download button saves the file to /var/tmp on the target machine (if logged into Cockpit as root user…). Quicker to open the Cockpit terminal and run from there…
sos report
sos report (version 4.9.1)
This command will collect system configuration and diagnostic
information from this system.
For more information on SoS visit:
Upstream Project : https://github.com/sosreport/sos
The generated archive may contain data considered sensitive and its
content should be reviewed by the originating organization before being
passed to any third party.
No changes will be made to system configuration.
SoS was unable to determine that the distribution of this system is
supported, and has loaded a generic configuration. This may not provide
desired behavior, and users are encouraged to request a new
distribution-specifc policy at the GitHub project above.
Press ENTER to continue, or CTRL-C to quit.
Setting up archive ...
Setting up plugins ...
[plugin:systemd] skipped command 'systemd-resolve --status': required services missing: systemd-resolved.
[plugin:systemd] skipped command 'systemd-resolve --statistics': required services missing: systemd-resolved.
[plugin:wireless] skipped command 'iw list': required kmods missing: cfg80211.
[plugin:wireless] skipped command 'iw dev': required kmods missing: cfg80211.
[plugin:wireless] skipped command 'iwconfig': required kmods missing: cfg80211.
[plugin:wireless] skipped command 'iwlist scanning': required kmods missing: cfg80211.
Running plugins. Please wait ...
Finishing plugins [Running: processor]
Finished running plugins
Creating compressed archive...
Your sos report has been generated and saved in:
/var/tmp/sosreport-hostname-20250521093452.tar.xz
Size 5.45MiB
Owner root
sha256 1c730b539234f4de75abb30aa528905232d0c97275e82e59224bb92c5105dfcd
Please send this file to your support representative.
1 Like
Ok, thanks for clarifying.
1 Like
Yes, of course.
Thanks, I guess I’ll have to look at cockpit in some depth. It’s labeled as a server administration tool, but I’m a Desktop user, so I have not paid much attention to it for desktops . I use Yast for managing Boot loader, firewall, services manager, host names, printer installation, and maybe a couple other things.
I have never been able to install my networked printer with KDE in any version of OpenSUSE. I get: “Failed to get a list of devices: ‘Forbidden’” (or very similar wording) and I have always used the CUPS GUI or Yast.
KDE printer installation works beautifully in any other distro I’ve tried (and that’s quite a few over the pasty 25 years).
open the snmp service port in the firewall.
@LanceHaverkamp Here GNOME uses CUPS…
For printer discovery, it’s usually just mdns (DNS-SD) needed these days. Most network printers support IPP, so no driver or explicit configuration required.
2 Likes
I did a bunch of digging last night, and found that the kde-print-manager can not get root permissions…that’s the entire kde printer adding issue. If I run:
kdesu systemsettings5
so that system settings is run as root, I don’t get the “Forbidden” error. But I never could figure out how clicking on System Settings > Printers is supposed to get root. For some weird reason, it’s being denied the ability to ask for root permission.
I also checked a recent Slowroll installation, and see that the same network printer was installed automagically, I didn’t have to do anything at all! I have no idea if Leap 16 will have that, but if it does, that one less thing to manually install.
4. 1. Install / Deinstall / Configure Printers and Scanners
- OpenPrinting CUPS v3 use IPP Everywhere™
- KDE as a KCM for printer management.
- Cups as a web interface
For scanner OpenPrinting is working with SANE to make driverless scanning a reality.
Maybe a gui will be usefull. But configuring a scanner is not a complex task.
Many modern scanners support “driverless” scanning.[1] You can look for your device’s compatibility on sane-airscan GitHub or Apple AirPrint devices.
Install the sane-airscan package if the scanner is known to work in “driverless” mode. If your scanner is using USB, also install the ipp-usb package and start/enable
ipp-usb.serviceto allow using IPP protocol over USB connection.Otherwise, check SANE - Supported Devices and SANE/Scanner-specific problems to see if your scanner will work with a different driver.
Most scanners should work out of the box. If yours does not, see SANE/Scanner-specific problems for installation instructions.