Element hangs on launch on Fedora 33 - TypeScript element-web
Description
Running the flatpak on Fedora 33, it seems like the app is trying to auto update as soon as it launches and hangs while using 100% cpu. Flatpak maintainer suggested this is probably an app issue and not flatpak since I was already logged in..
Steps to reproduce
- Launch the app
- Some UI elements load
- After 2-3 secs the app hangs
- Can quit through tray icon but not through UI
Logs being sent: no (app hangs) Some logs: Flatpak logs:
○ → flatpak run im.riot.Riot
/home/kkpk/.var/app/im.riot.Riot/config/Element exists: yes
/home/kkpk/.var/app/im.riot.Riot/config/Riot exists: no
Gtk-Message: 17:46:57.259: Failed to load module "canberra-gtk-module"
Gtk-Message: 17:46:57.259: Failed to load module "pk-gtk-module"
Gtk-Message: 17:46:57.259: Failed to load module "canberra-gtk-module"
Gtk-Message: 17:46:57.259: Failed to load module "pk-gtk-module"
Starting auto update with base URL: https://packages.riot.im/desktop/update/
Auto update not supported on this platform
Flatpak info:
→ flatpak info im.riot.Riot
Element - Create, share, communicate, chat and call securely, and bridge to
other apps
ID: im.riot.Riot
Ref: app/im.riot.Riot/x86_64/stable
Arch: x86_64
Branch: stable
Version: 1.7.15
License: Apache-2.0
Origin: flathub
Collection: org.flathub.Stable
Installation: system
Installed: 237.1 MB
Runtime: org.freedesktop.Platform/x86_64/20.08
Sdk: org.freedesktop.Sdk/x86_64/20.08
Commit: 99279bd6c362634e3439d4db557aac318f22b30a8b04911f7a4186ab4e6a25b3
Parent: ab84f1bb239daa39fc500cb0f543c7f5f989808d332b2ad3e069530ee348db9c
Subject: Update element-desktop_1.7.14_amd64.deb to 1.7.15 (4cf3b826)
Date: 2020-12-08 20:05:17 +0000
Version information
- Platform: desktop
For the desktop app:
- OS: Fedora 33
- Version: 1.7.15
4 Answer:
Hmm, I don't think it's about the app trying to update, since that's disabled on Linux.
Somehow, we'll either need to figure out what the app is doing when it hangs, or find a way to reproduce it on a developer machine.
Are you able to try logging into https://develop.element.io in a browser? Does the issue occur there?
@jryans no issues on the web. my account seems to log in without issues. is just on the fedora flatpak. It was suggested to me this could be an issue with the cache and should be fixed by fully removing the app and its cache/config then reinstalling. I'm just waiting before doing that to see if I can provide more logs. Let me know if there's a good way to debug this that can be helpful.
@keponk At the moment, I don't have anything quick in mind, unfortunately... My only idea at the moment would involve brewing custom builds with extra logging added, but that would likely take several attempts, and also wouldn't be packaged as Flatpak either, so perhaps it means it can't access the data storage of your main install.
I guess for the moment, I'd say proceed with clearing app cache / reinstalling. If it goes away, that's good news for now, and then we can use this issue to track if it comes back.
I guess for the moment, I'd say proceed with clearing app cache / reinstalling. If it goes away, that's good news for now, and then we can use this issue to track if it comes back.
And since the issue is gone after reinstallation, this doesn’t seem very actionable. Shall we just close now?
Read next
- Jetpack search page from WP.com indicates a WP.com site, even when self-hosted - wp-calypso
- Connect component not exported (aws-amplify-vue) - amplify-js
- olive [CRASH] Moved position of Sequence Viewer - Cplusplus
- process.send() blocked indefinitely if buffer is full - Python pwntools
- vscode Cannot right-click copy text from markdown preview window TypeScript
- Splat doesn't work for array - yq
- dlopen hook breaks objects that attempt to open dynamic libraries from their runpaths - libTAS
- Custom referrer snippet not working - koko-analytics