Element is offline after the first log on

[Ithvr]

Steps to reproduce

1. Log on the client for the first time
2. Verify the client
3. Restart the client

Outcome

What did you expect?

I expect that when I start Element that I get log on as normal

What happened instead?

Everything works fine when I log on Element Desktop the first time, but after I restart the client is stuck being offline telling that "Connectivity to the server has been lost."
I know the server is working well since it works on other clients, and the browser version of element

Operating system

OpenSUSE Tumbleweed

Application version

Element-Desktop 1.11.15

How did you install the app?

OpenSUSE repository

Homeserver

element.ithvr.no

Will you send logs?

Yes

[N0Manches]

I have the same error on opensuse tumbleweed for weeks.
Tried to delete all configs, reinstall... nothing works.

Clicking on "Help & About" just closes the window.

Information for package element-desktop:
----------------------------------------
Repository     : openSUSE-Tumbleweed-Oss
Name           : element-desktop
Version        : 1.11.17-1.1
Arch           : noarch
Vendor         : openSUSE
Installed Size : 4.0 MiB
Installed      : Yes
Status         : up-to-date
Source package : element-desktop-1.11.17-1.1.src
Upstream URL   : https://github.com/vector-im/element-desktop
Summary        : A glossy Matrix collaboration client - desktop
Description    : 
    A glossy Matrix collaboration client - desktop

openSUSE Tumbleweed 20230110

When I try to use flatpak or the PWA with ungoogled-chromium I am logged out as soon the process is terminated.
So it also does not work on Fedora.

Really annoying... atm I can only use the web version in the browser on all my operating system I use. (Of course the other version are also web versions... but I think one can understand the point...)

[t3chguy]

I suggest reporting this upstream to the OpenSUSE package (community) maintainer. It isn't one we package & support

[N0Manches]

It is a pity that only debian based distros are officially supported :(.

So on debian based distros everything works fine? There is no spam on your server requests?

M_MISSING_TOKEN: MatrixError: [401] Invalid Authorization header.

In another thread someone explained that sometimes (sometimes is not the case for me here) a key... is incorrectly saved in the Browser IndexedDB.

[t3chguy]

@N0Manches that can happen if your keyring isn't available when the app launches, so the key to unlock idb is missing

[N0Manches]

found the others
#1079
element-hq/element-web#18584

But of course I verified it with my Android phone then everything works fine until I restart the application, everytime. No idea what I could do differently.
But what is a bit strange to me that I need to verify it twice first it asked for the keys desktop -> android. Afterwards my phone says there is a new device android -> desktop. Is that normal? The verification process with the qr code are both the same.

[AUSBird]

I'm also having the same issue. I login and it works until the application restarts when the whole app just wont connect.

My console output after restarting gives me this

Keytar isn't installed; secure key storage is disabled.
Seshat isn't installed, event indexing is disabled.
/home/ausbird/.config/Element exists: yes
/home/ausbird/.config/Riot exists: no
No update_base_url is defined: auto update is disabled
Fetching translation json for locale: en_EN
Changing application language to en-us,en,en,en
Fetching translation json for locale: en-us
Fetching translation json for locale: en
Fetching translation json for locale: en
Fetching translation json for locale: en
Resetting the UI components after locale change
Resetting the UI components after locale change
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[19320:0116/080329.443447:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[19383:0116/080329.500425:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
Changing application language to en-us,en,en,en
Fetching translation json for locale: en-us
Fetching translation json for locale: en
Fetching translation json for locale: en
Fetching translation json for locale: en
Resetting the UI components after locale change

I noticed it mentions Keytar isn't installed; secure key storage is disabled., is this potentially part of a cause for the issue?

[subscribernamegoeshere]

where would i find this keytar message? my ctrl shift i from inside element-desktop client on this opensuse 15.4 machine doesnt show keytar error. those look like very early-on messages from a log, but i can only just as fast press ctrl+shift+i and eventually only kind of see later bootstrapping messages of this element-desktop client?

I see stuff like the following:

....
rageshake.ts:73 Restoring session for @subscribernamegoeshereyougettheidea:matrix.org
rageshake.ts:73 setLoggedIn: mxid: @subscribernamegoeshereyougettheidea:matrix.org deviceId: DEVICEIDHERE000000 guest: false hs: https://matrix-client.matrix.org/ softLogout: false freshLogin: false
....
rageshake.ts:73 StorageManager: Checking storage consistency
rageshake.ts:73 StorageManager: Local storage supported? true
rageshake.ts:73 StorageManager: IndexedDB supported? true
rageshake.ts:73 StorageManager: Local storage contains data? true
rageshake.ts:73 StorageManager: Crypto initialised? true
rageshake.ts:73 StorageManager: Sync store using IndexedDB contains data? true
rageshake.ts:73 StorageManager: Crypto store using IndexedDB contains data? true
rageshake.ts:73 StorageManager: Storage consistency checks passed
rageshake.ts:73 Expected a pickle key, but none provided. Encryption may not work.
.....
rageshake.ts:73 Session persisted for @subscribernamegoeshereyougettheidea:matrix.org
rageshake.ts:73 Lifecycle: Starting MatrixClient
rageshake.ts:73 EventIndex: Event indexing isn't installed for the platform, not initializing.
rageshake.ts:73 IndexedDBStore.startup: connecting to backend
rageshake.ts:73 MatrixClientPeg: waiting for MatrixClient store to initialise
rageshake.ts:73 StorageManager: Persistent? true
rageshake.ts:73 Switching to room id ROOMID1GOESHERE:matrix.org at event undefined
rageshake.ts:73 IndexedDB worker is ready
logger.ts:46 LocalIndexedDBStoreBackend.connect: connecting...
logger.ts:46 LocalIndexedDBStoreBackend.connect: awaiting connection...
logger.ts:46 LocalIndexedDBStoreBackend.connect: connected
logger.ts:46 LocalIndexedDBStoreBackend: loading account data...
logger.ts:46 LocalIndexedDBStoreBackend: loading sync data...
logger.ts:46 LocalIndexedDBStoreBackend: loaded sync data
logger.ts:46 LocalIndexedDBStoreBackend: loaded account data
logger.ts:46 LocalIndexedDBStoreBackend: loaded initial data
rageshake.ts:73 IndexedDBStore.startup: loading presence events
rageshake.ts:73 IndexedDBStore.startup: processing presence events
rageshake.ts:73 Crypto: Starting up crypto store...
rageshake.ts:73 connecting to indexeddb matrix-js-sdk:crypto
rageshake.ts:73 connected to indexeddb matrix-js-sdk:crypto
rageshake.ts:73 Crypto: initialising roomlist...
rageshake.ts:73 Crypto: initialising crypto object...
rageshake.ts:73 Crypto: initialising Olm...
rageshake.ts:73 Crypto: initialising Olm device...
rageshake.ts:73 Unable to initialise e2e Error: OLM.BAD_ACCOUNT_KEY
.......

[AUSBird]

I ran the element app from a terminal and it gave me that output

…

On Sat, Jan 21, 2023 at 10:07 PM subscribername goes here < ***@***.***> wrote: where would i find this keytar message? my ctrl shift i from inside element-desktop client on this opensuse 15.4 machine doesnt show keytar error. those look like very early-on messages from a log, but i can only just as fast press ctrl+shift+i and eventually only kind of see later bootstrapping messages of this element-desktop client? I see stuff like the following: .... rageshake.ts:73 Restoring session for @subscribernamegoeshereyougettheidea: matrix.org rageshake.ts:73 setLoggedIn: mxid: @subscribernamegoeshereyougettheidea: matrix.org deviceId: DEVICEIDHERE000000 guest: false hs: https://matrix-client.matrix.org/ softLogout: false freshLogin: false .... rageshake.ts:73 StorageManager: Checking storage consistency rageshake.ts:73 StorageManager: Local storage supported? true rageshake.ts:73 StorageManager: IndexedDB supported? true rageshake.ts:73 StorageManager: Local storage contains data? true rageshake.ts:73 StorageManager: Crypto initialised? true rageshake.ts:73 StorageManager: Sync store using IndexedDB contains data? true rageshake.ts:73 StorageManager: Crypto store using IndexedDB contains data? true rageshake.ts:73 StorageManager: Storage consistency checks passed rageshake.ts:73 Expected a pickle key, but none provided. Encryption may not work. ..... rageshake.ts:73 Session persisted for @subscribernamegoeshereyougettheidea: matrix.org rageshake.ts:73 Lifecycle: Starting MatrixClient rageshake.ts:73 EventIndex: Event indexing isn't installed for the platform, not initializing. rageshake.ts:73 IndexedDBStore.startup: connecting to backend rageshake.ts:73 MatrixClientPeg: waiting for MatrixClient store to initialise rageshake.ts:73 StorageManager: Persistent? true rageshake.ts:73 Switching to room id ROOMID1GOESHERE:matrix.org at event undefined rageshake.ts:73 IndexedDB worker is ready logger.ts:46 LocalIndexedDBStoreBackend.connect: connecting... logger.ts:46 LocalIndexedDBStoreBackend.connect: awaiting connection... logger.ts:46 LocalIndexedDBStoreBackend.connect: connected logger.ts:46 LocalIndexedDBStoreBackend: loading account data... logger.ts:46 LocalIndexedDBStoreBackend: loading sync data... logger.ts:46 LocalIndexedDBStoreBackend: loaded sync data logger.ts:46 LocalIndexedDBStoreBackend: loaded account data logger.ts:46 LocalIndexedDBStoreBackend: loaded initial data rageshake.ts:73 IndexedDBStore.startup: loading presence events rageshake.ts:73 IndexedDBStore.startup: processing presence events rageshake.ts:73 Crypto: Starting up crypto store... rageshake.ts:73 connecting to indexeddb matrix-js-sdk:crypto rageshake.ts:73 connected to indexeddb matrix-js-sdk:crypto rageshake.ts:73 Crypto: initialising roomlist... rageshake.ts:73 Crypto: initialising crypto object... rageshake.ts:73 Crypto: initialising Olm... rageshake.ts:73 Crypto: initialising Olm device... rageshake.ts:73 Unable to initialise e2e Error: OLM.BAD_ACCOUNT_KEY ....... — Reply to this email directly, view it on GitHub <#850>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABWKI2NJ7GQR6KXIIKEWZJTWTPGRJANCNFSM6AAAAAATCTAQXI> . You are receiving this because you commented.Message ID: ***@***.***>

[subscribernamegoeshere]

I ran the element app from a terminal and it gave me that output

thanks for this information. by the way did you already file a bugreport with opensuse folks for this situation or anyone in here to really get this stuff solved on the opensuse platforms? thanks.

[aylen384]

The keytar and Seshat messages are unrelated. They are, because on openSUSE element-desktop is build without native bindings that would allow searching for messages. This is because of the abysmal node/cargo build process not being easy to run in the secure build environment that doesn't have internet access.

I have to say that I don't run into this issues on tumbleweed.
This is my startup log:

Keytar isn't installed; secure key storage is disabled.
Seshat isn't installed, event indexing is disabled.
/home/MYUSER/.config/Element exists: yes
/home/MYUSER/.config/Riot exists: no
No update_base_url is defined: auto update is disabled
Fetching translation json for locale: en_EN
Changing application language to de
Fetching translation json for locale: de
Resetting the UI components after locale change
Resetting the UI components after locale change
Changing application language to de
Fetching translation json for locale: de
Resetting the UI components after locale change

[subscribernamegoeshere]

i am far from being technically knowledgeable about all of this, i dont build my software on my own. coming back to this logged out state after every restart of the element application, what is the actual root cause that opensuse vendor and their compilation does have this bug? is this already known? will opensuse ever again have a working and lasting element application? what was different in december or november of last year that their compiled and built application worked normally and now does not any more? any real answers to this?

[aylen384]

The problem is that I cannot reproduce this issue on my tumbleweed installation.

You could try to delete your .config/Element directory and start with a fresh config. (Make sure you have a different client still logged in to keep your encrypted chats).
Also you could create a test account on a different server and see if the issue only appears on that particular server.

[subscribernamegoeshere]

doesnt help at all removing the .config/Element/ folder. the client re-logs in and re-verfiies with other existing devices.

upon first shutdown of the new opensuse logged-in instance newly creasted device id and all, it is immediately offline for good upon the next re-start of this client. once again. all the same.

how are we gonna figure out whats happening? please solve this. :(
p,s, but this is open suse 15.4 x64 over here not tumbleweed. also this uses matrix.org simple username password account. what i remember maybe changed around the very end of last year is that for the first time i have had a second fellow participant chat with a second person via matrix and this user created a very new user account on matrix.org and this chat was immediately kind of end to end encrypted or was forced to this setting by this other party. my other chats to one other person is not yet end to end encrypted. thats the only thing i remember.

also the newly created linux client shows this one settings complaint in the security area that components would be missing to be able to search through end to end encrypted messages or so it complains in that one area with explanatory text or something on how to build the client or what components would be missing. maybe this is another hint.