Strange behavior of tutanota-desktop-bin on i3wm


I use tutanota-desktop and, more or less 1 out of 2, it doesn’t start properly: the applet starts but the window does not, or if it does it is black.
I don’t know whether this is a problem from my distribution or from the package itself. So I ask here first.

Here is what I get when I launch tutanota-desktop(I don’t know if it is very useful since I get the same thing when it works and when it doesn’t).
Many thanks!

the monkey has been patched
(node:4802) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `tutanota-desktop --trace-deprecation ...` to show where the warning was created)
version:   3.89.5
config up to date
[ApplicationWindow] startFile:  file:///opt/tutanota-desktop/resources/app.asar/index-desktop.html
[DownloadManager] getting dictionaries from:
default mailto handler: false
[DownloadManager] spellcheck-dictionary-initialized es-419
scheduling to check sse in 1 seconds
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
Webapp ready
autoUpdater info:
 Checking for update
autoUpdater info:
desktop file exists, checking version...
autoUpdater info:
 Update for version 3.89.5 is not available (latest version: 3.89.5, downgrade is disallowed).
autoUpdater info:
 update not available: {
  version: '3.89.5',
  files: [
      url: 'tutanota-desktop-linux.AppImage',
      sha512: '***',
      size: 89988149,
      blockMapSize: 93257
  path: 'tutanota-desktop-linux.AppImage',
  sha512: '***',
  releaseDate: '2021-10-20T10:26:03.629Z',
  signature: '***'
last missed notification check: { lastMissedNotificationCheckTime: 1635072793914 }
scheduling to check sse in 19 seconds
starting sse connection
lookup sse request
established SSE connection
received new timeout: heartbeatTimeout:240
scheduling to check sse in 288 seconds
sse heartbeat 240
scheduling to check sse in 288 seconds
sse heartbeat 240
scheduling to check sse in 288 seconds
downloading missed notification
missed notification response 200
MissedNotification is empty
scheduling to check sse in 288 seconds
dl missed notification response closed
storing push identifier
sse heartbeat 240
scheduling to check sse in 288 seconds
sse heartbeat 240
scheduling to check sse in 288 seconds
sse heartbeat 240
scheduling to check sse in 288 seconds
sse heartbeat 240
scheduling to check sse in 288 seconds

1 Like

Are you using tutanota-desktop or tutanota-desktop-bin?

Actually there is, the latest version is 3.89.20.


Yes I did the update, with same issue.
I use tutanota-desktop-bin 3.89.20-1
Should I try tutanota-desktop instead?

You could. Both work fine for me.

Mmm… I tried to install tutanota-desktop and I have the following error:

==> Starting build()...
npm notice 
npm notice New patch version of npm available! 8.1.3 -> 8.1.4
npm notice Changelog:
npm notice Run npm install -g npm@8.1.4 to update!
npm notice 
npm ERR! network Socket timeout
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/alex/.cache/yay/tutanota-desktop/src/npm_cache/_logs/2021-11-27T11_01_49_807Z-debug.log
==> ERROR: A failure occurred in build().
 -> error making: tutanota-desktop

I don’t understand, from yay I have

2 community/npm 8.1.3-1 (1.3 MiB 5.9 MiB) (Installed)
    A package manager for javascript

So, no version 8.1.4 announced here.

Coming back to the initial problem, do you use tutanota-desktop-bin with i3wm?
I don’t really know where to start looking but I’m wondering if the problem could not be related to i3wm.
As another problem (maybe related?), from time to time, the appearance changes. I used the dark mode and sometimes it just ‘comes back’ to the light one.
In desktop settings I have:
-Run in the background: Yes
-Run on startup: No (I launched it from my i3config file)
-Desktop integration: Activated
I played with the above options with no improvement.

As the error says, the error was network related, not with NPM.

The Arch community package is flagged out of date, so 8.1.3 is still the current version we have.

No, I use GNOME.

Oh, sorry about that, I just didn’t see it (too tired I guess).