elementary / sideload

Sideload Flatpaks on elementary OS
https://elementary.io
GNU General Public License v3.0
46 stars 14 forks source link

Add an uninstall button for already installed flatpaks? #82

Open sprite-1 opened 4 years ago

sprite-1 commented 4 years ago

Prerequisites

Describe the bug

image

I installed Aqueducts from Flathub via its *.flatpakref file but the AppCenter is unable to detect it. image This leads me to believe that maybe it's a good idea to add an "Uninstall" button for right in Sideload to make things easy and intuitive for users.

To Reproduce

Steps to reproduce the behavior:

  1. Go to https://flathub.org/apps/details/com.endlessnetwork.aqueducts
  2. Click on Install
  3. Open the downloaded *.flatpakref file.
  4. Install it.
  5. Go to AppCenter and look for Aqueduct

Expected behavior

There should be an Uninstall button in the AppCenter for AqueDuct.

Platform Information

davidmhewitt commented 4 years ago

I've modified the title of your issue as maybe it's a valid point that Sideload should offer an uninstall option. I'll leave that as a decision for the design team.

But, as you've probably realised, this sounds like more of an issue/bug with AppCenter than it is with Sideload. I can't reproduce it with the game you mention or any other app.

It sometimes takes AppCenter a few seconds after opening to realise that an app is installed and then it will change from having an Install button to having an Uninstall button. If you can provide any more information about the AppCenter issue and open a new issue in the AppCenter repository, that would be helpful.

sprite-1 commented 4 years ago

It sometimes takes AppCenter a few seconds after opening to realise that an app is installed and then it will change from having an Install button to having an Uninstall button. If you can provide any more information about the AppCenter issue and open a new issue in the AppCenter repository, that would be helpful.

Unfortunately after reboot, the issue is no longer there so I can't comment further on that end, but I do appreciate the rename of the issue, that probably fits the bill more. Hopefully the UX team sees it