I think the specific issue with the application discussed in that thread is resolved, but there’s still a general issue.
Right now, GNOME Software, and presumably other Flathub-enabled software centers, do not have a way to present command-line applications in a meaningful way to users. This means that even when the tool doesn’t do something surprising (let alone malicious), it’s a bad experience — the user installs and then hits the “Open” button and nothing happens, and then when they search in the desktop environment, can’t find it anywhere.
Flathub needs a policy that all such packages should be hidden from accidental discovery, until there is software center client support for them. Otherwise, distros need to put big warnings on any suggestions to non-expert users that they look at Flathub as a software source.
I’m sorry; I don’t mean to pick a fight. I’ve removed that comment from my post above. I misunderstood your comments about the lack of a policy against command line applications claiming to be desktop applications as an endorsement of those applications doing that. But even the misunderstanding does not justify my being rude about it. Again, sorry.
I think we are actually in agreement that this should be disallowed?
I’m not disagreeing, and we pay attention to CLI applications being marked as such during submission. Hardware Probe was accepted 3 years ago before we started making the review process more strict. It doesn’t mean CLI applications are forbidden on Flathub, but they need to be designated as console-applications or should not ship metainfo at all.
For the record. we do allow TUI applications with the type set to desktop-application as long as desktop launcher has Terminal=true.
This ideal still has some issues.
in this specific example, you need to avoid opening it via clicking on launch.
as that will open a temporary CLI, run the benchmark, and then close the CLI.
which deletes the results of the benchmark.
you must instead manually open a terminal and then run it with an unwieldly
flatpak run com.geekbench.Geekbench6
now you will be able to see the results when finished since you ran it through an already opened CLI
There’s nothing in the desktop-entry spec requiring the terminal to stay open. I don’t think Terminal=true was really intended for this use case. And in fact, I wouldn’t want the terminal to stay open after quitting a real TUI application, e.g. htop.