Corey Hull

That's the name I would have expected it to be--no wonder I couldn't find it. Also attached is a screenshot from synaptic showing all expected repositories are present. corey@pepper:~$ suggested bash: suggested: command not found corey@pepper:~$ sudo suggested sudo: suggested: command not found corey@pepper:~$ whereis suggested suggested: corey@pepper:~$ sudo apt search suggested | grep '^sug' WARNING: apt does not have a stable CLI interface. Use with caution in scripts. corey@pepper:~$

Environment: fresh install of Peppermint OS Mini, Debian base, 64-bit. The 'suggested' app (for choosing browsers and/or other common programs) works fine. Using the synaptic package manager I installed pepinstall along with its dependencies. Now when I try to run ‘suggested’ (either from welcome or pep hub), there is a momentary flash of a window (too quick to read) and then it disappears. I don’t know what exact program is trying to run otherwise I might be able to see something in a terminal.

I recently installed with the Peppermint OS Mini build (Debian 64-bit). This build does not include Pepinstall out-of-the-box. When I first went looking for it (using apt search) I could not find it. Figured out I needed to do sudo apt search. Normally apt search does not require sudo. Turns out the file /etc/apt/sources.list.d/peppermint.list only had owner privs (-rw-------). All the other files in the /etc/apt directory and its sub-directories have world read access (-rw-r--r--). Pretty sure this...

Sorry, sometimes I guess I don't explain things very well. I am not asking what flatpaks are or how they work. I am reporting what appears to be a bug in the pepinstall program. In pepinstall, under preferences, is a toggle option to show (or not) unverified flatpaks. No matter how it it toggled it still always displays unverified flatpaks. They do have a little red shield icon indicating they are unverified, but it still shows them. I think it's not supposed to.

However I have "Show unverified Flatpaks" toggled it still always shows them. One example: Zoom.

I had the same error but "got through it." No guarantees, just sharing my experience hoping it might help someone else. The error made me think it was failing during some final update process and maybe the base install was okay. So despite the error I tried booting into the newly installed system. It booted up. Then I manually kept running and rerunning apt updates and apt upgrades. They would fail with an error saying to run this or that command (sorry I did not document, but they were the apt commands...

Thank you for taking the time to give such a detailed answer. I've done further reading and now realize the whole PWA thing is bigger than I was aware. I'm sure whatever direction the project is going with Kumo is more informed than anything I was aware of. I can easily set up a launcher or two using luakit and that will be fine for me.

No problem, thanks.