snowflake icon indicating copy to clipboard operation
snowflake copied to clipboard

If installed as Snap - doesn't work properly - but ok when installed via deb package

Open DrJaymz opened this issue 5 years ago • 5 comments

When I installed via snap on Mint it didn't work properly, specifically opening files and integration with editors amongst other things links and buttons don't do anything. Once you install Deb package it works properly. I also installed on some other ubuntu derived VM and the problem is the same.

I would have thought then, that someone else had seen that problem.

Not really a bug per-se but if you have issues with it, try installing using deb package instead.

DrJaymz avatar Aug 10 '20 09:08 DrJaymz

I'm on Ubuntu 20.04 with the latest Muon version that I just installed. Tried first with the snap package, but it cannot read my .ssh keys as expected. But anyway, connecting to a remote with user/password ( without ssh keys ) works only when terminal is the default connection, if file is the default, it doesn't work.

tutume avatar Aug 25 '20 19:08 tutume

I'm on Ubuntu 20.04 with the latest Muon version that I just installed. Tried first with the snap package, but it cannot read my .ssh keys as expected. But anyway, connecting to a remote with user/password ( without ssh keys ) works only when terminal is the default connection, if file is the default, it doesn't work.

You have to enable snap to access .ssh in Ubuntu. Easiest way in GUI: UBuntu software store -> Snowflake -> Permission and enable ss-keys Képernyőkép erről: 2020-11-08 11-47-22

angmac avatar Nov 08 '20 10:11 angmac

Thanks for the reply. I'm relative new to Linux Desktop/Snap apps and I forgot about this settings on Ubuntu Software App.

Anyways, If I connection using password it works just fine, but if I use ssh keys, it just give me "Unable to connect to server SERVER at IP. Do you want to retry? (Cancel/No/Yes). Any ideas?

tutume avatar Nov 10 '20 21:11 tutume

  • No permission to access the ssh-keys
  • You try to use non-RSA keys or OpenSSH-specific RSA keys

OpenSSH specific RSA keys: the private key begins with -----BEGIN OPENSSH PRIVATE KEY----- and not -----BEGIN RSA PRIVATE KEY-----

You have to use ssh-keygen -m PEM when generating the keys.

Anyway, when you start the snowflake snap form a terminal (just type snowflake as a normal program), it should write a java exception when something goes wrong.

angmac avatar Nov 11 '20 11:11 angmac

This was my case. My RSA key uses the openssh standard as I generate with ssh-keygen without -m pem option. thanks for your help. Would be good to have this information on some documentation.

I don't know if there are other ways to do that, but as I always use passphrase to protect SSH keys, I had to do in multple steps as follow:

# backup your original key as the command will overwrite your key
cp ~/.ssh/id_rsa ~/.ssh/id_rsa.openssh_bkp
# convert from openssh format to PEM format
ssh-keygen -f /path/to/key -m pem -p
# you can remove password by adding `-N ""`
ssh-keygen -f /path/to/key -m pem -p -N ""

By my tests it doesn't work with ssh-agent, so you have to remove password or add password to the connection profile. Currently, a bad thing as any password is saved in plain text.

Good software with great potencial to help many users.

tutume avatar Nov 12 '20 21:11 tutume