Skip to content
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

Linux Desktop Cllient is "too old and not supported any longer" #2022

Closed
radumas opened this issue Apr 30, 2020 · 22 comments
Closed

Linux Desktop Cllient is "too old and not supported any longer" #2022

radumas opened this issue Apr 30, 2020 · 22 comments

Comments

@radumas
Copy link

radumas commented Apr 30, 2020

I got this error message when trying to log in to the Desktop client

image

Normally it seems like the client updates automatically, so I searched for how to do it manually, found this blog post and then downloaded from https://mail.tutanota.com/desktop/tutanota-desktop-linux.AppImage and followed these instructions

Same result

@charlag
Copy link
Contributor

charlag commented Apr 30, 2020

The latests version you downloaded should run just fine, I think you might start the wrong one by accident.
Let us check this.
Either start AppImage from the terminal
or after start please press F12, type env.versionNumber and press return. What do you see?

@ALGue
Copy link

ALGue commented Apr 30, 2020

Hello, same issue since yesterday (with ubuntu 16.04). I got the same message error and did the same process than radumas (re-downloading one AppImage for linux, give it permission and run it from the terminal). I still have the same message, and clicking "ok" the interface also display "connexion in progress"... Thanks if you have any solution!

@dennisbakhuis
Copy link

Similar issue. Downloaded the AppImage again, but the warning persists. I am on Ubuntu 19.10.

@nikolayhg
Copy link

Same issue with latest https://mail.tutanota.com/desktop/tutanota-desktop-linux.AppImage
Unable to use the Desktop app.

@charlag
Copy link
Contributor

charlag commented May 1, 2020

Please see comment above where I ask to check the version in one of two ways. It definitely must work if the right file is launched.

@nikolayhg
Copy link

nikolayhg commented May 1, 2020

3.72.0

$ ./tutanota-desktop-linux.AppImage 
[2020-05-01T07:30:35.313Z] the monkey has been patched
[2020-05-01T07:30:35.475Z] config up to date
[2020-05-01T07:30:35.612Z] creating alarm notification!
[2020-05-01T07:30:35.613Z] creating alarm notification!
[2020-05-01T07:30:35.613Z] creating alarm notification!
[2020-05-01T07:30:35.614Z] creating alarm notification!
[2020-05-01T07:30:35.615Z] creating alarm notification!
[2020-05-01T07:30:35.617Z] _connectedSseInfo {
  identifier: '..................',
  sseOrigin: 'https://mail.tutanota.com',
  userIds: [ ..................' ]
}
[2020-05-01T07:30:35.622Z] scheduling to reconnect sse in 1 seconds
[2020-05-01T07:30:35.623Z] argv:  [ '/tmp/.mount_tutanoVzul5m/tutanota-desktop' ]
[2020-05-01T07:30:35.623Z] version:   3.72.0
[2020-05-01T07:30:36.004Z] startFile:  file:///tmp/.mount_tutanoVzul5m/resources/app.asar/desktop.html
[2020-05-01T07:30:36.780Z] default mailto handler: false
[2020-05-01T07:30:36.782Z] alarm storage initialized
[2020-05-01T07:30:36.874Z] scheduled 4 alarm timeouts for  MTU4NTE5MjU4OTczNg
[2020-05-01T07:30:36.875Z] scheduled 4 alarm timeouts for  MTU4Mzc2OTIzMjUxNA
[2020-05-01T07:30:36.875Z] scheduled 1 alarm timeouts for  MTU4NTkzNjcwNzkzOA
[2020-05-01T07:30:36.876Z] scheduled 1 alarm timeouts for  MTU4MzU5NzMxOTIxMg
[2020-05-01T07:30:36.876Z] scheduled 0 alarm timeouts for  MTU4NTM0MzQ4MjUwMA

@xidod
Copy link

xidod commented May 2, 2020

same here. If i run the AppImage from terminal says version 3.72.0 but if i open the developer tools and type env.VersionNumber on the console says 3.68.1

@nikolayhg
Copy link

On my side:
env.versionNumber="3.69.2"

@charlag
Copy link
Contributor

charlag commented May 2, 2020

It means your .desktop points elsewhere than your appimage. Run through the terminal and re-run desktop intergration from desktop settings in app.

@xidod
Copy link

xidod commented May 3, 2020

I tried to delete the .desktop and all the appimage that i have on my system and re-download the tutanota client but with the same result. He has worked only after reboot the machine

@nikolayhg
Copy link

@charlag How do I "re-run desktop intergration from desktop settings in app"?

@charlag
Copy link
Contributor

charlag commented May 4, 2020

@nikolayhg open working Tutanota version, Settings->Desktop->Desktop Integration

closing because this is not a bug in Tutanota, but .appimage pointing to the wrong file

@charlag charlag closed this as completed May 4, 2020
@nikolayhg
Copy link

nikolayhg commented May 4, 2020

@charlag I am unable to access the Settings because when I open the AppImage, I am required to login and in the login view there are no Settings. Also I cannot login due to the error of this issue. How should I fix this issue?

@charlag
Copy link
Contributor

charlag commented May 4, 2020

@nikolayhg you had a new version when you started from the terminal, didn't you?

@nikolayhg
Copy link

yes

@charlag
Copy link
Contributor

charlag commented May 4, 2020

Then launch it from the terminal so that you can log in and access settings.

@nikolayhg
Copy link

@charlag please reread my comment. I do not see any settings in the login view, no matter whether I launch the AppImage with double click or from the terminal
image

@charlag
Copy link
Contributor

charlag commented May 4, 2020

I'm sorry but I am unable to provide support to you further. If you launch it from the terminal, then you get up-to-date version which should let you log in and access settings.
Otherwise just delete any mention of Tutanota from ~/.local/share/applications and start AppImage again.

@nikolayhg
Copy link

nikolayhg commented May 4, 2020

If you launch it from the terminal, then you get up-to-date version which should let you log in and access settings.

That's incorrect. I am unable to login.

Otherwise just delete any mention of Tutanota from ~/.local/share/applications and start AppImage again.

Thank you for the advice. I removed the tutanota .desktop file(s), but I still get the same error when trying to login. Currently I cannot restart my system, as suggested by xidod.

$ rm ~/.local/share/applications/tutanota-desktop.desktop
$ rm ~/.local/share/applications/appimagekit-tutanota-desktop.desktop

I removed also the following directory, which contained a tutanota AppImage:

$ rm -r ~/.cache/tutanota-desktop-updater/

@nikolayhg
Copy link

I fixed the issue. It might not be with the tutanota source code itself, but it seems to be with its deployment to Linux. Here is what I did:

I searched for every tutanota file I could find: find / -iname '*tutanota*'. In my home directory there only the latest AppImage, but in the /tmp directory there was the directory /tmp/.mount_tutanoO9dWHq which contained lots of old tutanota files from March 2020.

I unmounted it:

sudo umount -l /tmp/.mount_tutanoO9dWHq/
sudo umount -f /tmp/.mount_tutanoO9dWHq/

And then removed it:

rm -r /tmp/.mount_tutanoO9dWHq/

Afterwards running the latest AppImage was like starting from scratch. It asked whether I would like to integrate it in the Desktop, confirmed and then I could successfully login.

@radumas
Copy link
Author

radumas commented May 11, 2020

I just did this and ran the appImage from the command line and it worked, per the comment above, like starting from scratch. Shouldn't the updater be removing .desktop files?

$ rm ~/.local/share/applications/tutanota-desktop.desktop
$ rm ~/.local/share/applications/appimagekit-tutanota-desktop.desktop

@charlag
Copy link
Contributor

charlag commented May 11, 2020

@radumas this shouldn't be necessary normally, I guess this in an artefact from the previous integration system. Maybe @ganthern knows better

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants