Discover is unable to find updates.
It was already explained to you in your other threads. This is a known bug.
https://bugzilla.opensuse.org/show_bug.cgi?id=1243078
Beta testers shouldn’t be surprised by such issues.
Update your system via Myrlyn or zypper. Only use Discover for flatpaks. Besides that flatpaks can also be managed via commandline. flatpak has an extensive and beginner friendly documentation.
We can see that a few folks are experiencing more issues (based on that bug report) than what other folks’ experience. It’s no telling if they are doing installs or updates or package selection correctly, and so on.
As I mentioned previously, the only tab where I see an erroneous error message (as I mentioned in another thread) is when I click on “Home”. Everything else works. See the screenshot below when I did a Discover (for Flatpak updates) moments ago.
And just to be clear, we use “zypper” to do an overall system update. Then use Discover afterwards to do Flatpak updates (as we did with TW and now with Leap 15.6).
BTW - the orange “Exclamation Point” is meant to draw attention to that Tab because there are updates available.
Screenshot checking for Updates with Discover
Screenshot showing after clicking “Update All” and the update completed (see System Tray clock)
I had thought that issues were only on the Home screen, and I see that you got updates. Mine never appeared, so something is still not right.
And as an aside, the Yast2 replacements are still missing things like Samba and firewall management. Where are these going to appear? In Cockpit? When?
@jarome Firewall management is there under Networking. Samba, when someone writes a plugin…
Have you run as root user zypper dup at all?
I’ll do these one at a time … first, Firewall using Cockpit …
Hope the screenshot is helpful.
The “samba option” is coming up … slightly more involved 
"zypper dup’ - Nothing to do, since I reinstalled it 2 days ago.
And where is the partitioner?
Okay, now the addition of Samba stuff … showing as screenshots
.
Click the “Edit …” option
Under “Storage”
The samba under networking adds ports to the firewall, but does not manage shares and allowed users. Thanks.
@jarome there is one available https://github.com/45Drives/cockpit-file-sharing it needs to be integrated into the project…
How do I install it? Zypper does not find it.
@jarome it’s not packaged up as an rpm, or AFAIK integrated into the flatpak version, maybe if the samba service is enabled and running it shows up in the flatpak version?
samba is installed (Ă la Myrlyn), but under Cockpit/services, smb is not listed until I start it with systemctl. The average user might not know the name of the service. Yast2 lists all the installed services. Apparently, Cockpit does not.
The cockpit github sites do not list any installation for OpenSUSE.
After starting samba, the plugins do not show up in Discover Cockpit search.
So, really useful tools are missing. What are the plans for fixing this?
And there is an issue about whether everything is done with Flatpak or rpms. Can flatpak and rpms be intermixed?
@jarome the reason for me to use the flatpak version is I maintain multiple systems and architectures, x86_64, aarch64 and riscv64.
Using the flatpak version on one machine means I can manage all my devices over ssh without the need to install any cockpit related rpms on these systems.
For a single user setup then either the Flatpak or for further integration of packaged up plugins then cockpit-ws would be appropriate.
Hmmmm. Shows up here in this Cockpit.
In Cockpit, click the Services tab in left-hand list, then Services in horizontal sub-menu (it’s the default selection).
Notice the “Filter” fields (circled) … by Name, current State, and File state.
For this screenshot, “all services” are listed.
Notice the up arrow at the right side- it’s pointing to the Scrollbar perspective button, and you can see, this list has many may entries, from A-Z, i.e. all Services.
I saw this. But smb/samba were not listed there until I started the service, iunless I missed seeing it. I looked.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
