element-hq
Complete freeze if no desktop notification deamon is running on Linux
After running in background for a little while, the Riot Desktop client completely freezes when I come back to it. This happens very often (once every 30m at least). Is there some way I can debug this myself? If I have the dev tools open, they freeze, too. Also sending the log file via the settings page.
- OS: Arch Linux (up-to-date), i3
- Version: Latest git master (bf56a00d60a44d7f2e9d2c7748aedb31c62ba9a8)
Edit: I installed riot-desktop-git from the AUR: https://aur.archlinux.org/packages/riot-desktop-git
This only seems to happen after I received a message while the app was in the background.
This is still happening all the time. Anybody here who can help me track down the issue?
If I don't kill Riot but instead try to launch a new instance, the frozen instance disappears after a minute or so and a new instance comes up which is working. Still pretty annoying.
I found out why this is happening! Riot froze because it was trying to dispatch a desktop notification, but in my setup with i3 there was no daemon to accept these. Disabling desktop notifications solved this problem for me 🎉 Another way to fix this issue is to run a notification daemon like dunst. I will see if I can fix this bug if I have the time.
I confirm, disabling the notification seems to fix the issues on archlinux with the latest desktop build from AUR.
Have this issue too, was able to track it down: If you get a Message in the Background, riot tries to send a notification. If no notify-daemon is running, riot can't handle the error and dies Workaround is either to install a notification daemon (like dunst) or to disable desktop-notifications in the riot-settings
Still a problem for me. Presumably this is https://github.com/electron/electron/issues/21912
My Riot freezes whenever I get a message, freezes my whole pc for split second too. AND ALSO it freezes a little when the "is typing" thing appears.
