New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For Linux, appimage, Standard Note update simply does not work #347

Open
WritingSolutions2020 opened this Issue Oct 14, 2018 · 5 comments

Comments

Projects
None yet
2 participants
@WritingSolutions2020

WritingSolutions2020 commented Oct 14, 2018

Linux Mint, MATE desktop, 32-bit. But not sure the Linux distribution is the issue here...

EDIT: Unless one truly understands Linux, and so can use root privileges to perform a command-line update, updating Standard Notes on Linux simply does not work.

  1. There's NO way to update from the GUI. One must use the command line interface (CLI).

  2. Using sudo to start SN from the command line does NOT enable one to perform an update from the GUI. The command line indicates activity but the update does NOT occur.

  3. One must manually locate and find the updated appimage, download it, get it in the desired folder with the correct owner and privileges, then start it with sudo privileges to get it to install.

What a pain in the sitzon!

This is truly annoying. What's needed is:

  1. GUI feedback, or at least some sensible feedback, about what is and is not happening.

  2. The update process puts the updated appimage in the same folder as the version that's being used to update SN.

This has become especially important given SN's seemingly once-per-week update needs. I "get" that updates can be beneficial, but on Linux it becomes an issue of stopping work and performing the functional equivalent of a system administration task rather than simply updating and application...

Thanks,
Riley
SFO

@mobitar

This comment has been minimized.

Member

mobitar commented Oct 14, 2018

We could add more GUI around this. Just a matter of improving over time. Recently we added the Updates menu which really helped provide more clarity (much more opaque before that). The only thing missing now would be some sort of progress indicator. But yeah, I imagine we'll do stuff here. Just other things with higher priority to be done first.

@WritingSolutions2020 WritingSolutions2020 changed the title from For Linux, make Standard Note update more like Postman to For Linux, appimage, Standard Note update simply does not work Oct 28, 2018

@WritingSolutions2020

This comment has been minimized.

WritingSolutions2020 commented Oct 28, 2018

See my rewrite of the issue. At this point it seems impossible to update the SN appimage on Linux from the GUI. Sigh...

@mobitar

This comment has been minimized.

Member

mobitar commented Oct 29, 2018

@WritingSolutions2020 still unable to replicate your issue, and no one else seems to have the same problem. Might be because you're 32 bit. Need to investigate more when I get the chance. But, this is the reason we added the Updates menu with "Manual download". In case auto doesn't work. This way at least you know there's a new version.

@WritingSolutions2020

This comment has been minimized.

WritingSolutions2020 commented Oct 30, 2018

Part of the problem may be that I've put the executable in /usr/local/StandardNotes and made its owner root. I've done that to align SN's installation directory with similar programs such as Postman. With this in mind, it'd be great if SN would:

  1. "Know" where its executable is and update to that folder. (I instead find updated appimage files in a hidden directory in my home folder...)

  2. Ask for the necessary permissions via a prompt ala other software updates.

@mobitar

This comment has been minimized.

Member

mobitar commented Oct 31, 2018

It should definitely know where it's located and update the file in place in your existing directory. But it may be that because it's placed in a folder it doesn't have permissions to, it defaults back to your home directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment