Rocket.Chat.Electron
Rocket.Chat.Electron copied to clipboard
RocketChat
Application silently closes a few seconds after startup
Search before asking
- [X] I had searched in the issues and found no similar issues.
Operating System
- [ ] macOS
- [ ] Windows
- [X] Linux
Operating System Version
KDE Neon User Edition 5.27 (Ubuntu 22.04)
It happens on the web browser too?
No, it just happens on the Desktop app
Rocket.Chat Desktop App Version
3.9.9
Rocket.Chat Server Version
6.4
Describe the bug
Since this affects the flatpak package I originally reported this as flathub/chat.rocket.RocketChat#122. Since it looks like some electron and not a flatpak specific issue (which might be caused by the flatpak packaging though) I was asked by @andrevmatos to file it upstream. That issue has some more information like a partial strace output which I'll omit here.
I have two KDE neon installations which are configured very similarly. One one of them I can use the RocketChat flatpak without issues, on a recently installed one it behaves a bit weirdly:
When I start the application it first seems to work fine and if I am quick enough I can even log in to our server. But after a few (20 or so?) seconds the main window just closes and disappears without any traces. This even happens if I leave it sitting at the login screen.
There is no relevant output on stdout or stderr but the application exits with status code 137. I also can't find any traces of a crash dump or the like.
When this happens the process disappears; the View -> Tray Icon option is disabled.
I can reproduce this even when I purge the application data (via rm -r ~/.var/app/chat.rocket.RocketChat). I didn't test if this makes it reproducible on that other machine too since I don't want to break it as well.
How to Reproduce
- Install RocketChat from Flathub
- Start Rocket Chat
- Wait (around 20 seconds)
Describe your Expected behavior
The main window should not disappear/"crash".
Anything else
Happens every time I start the application. I couldn't find any relevant logs but can provide them if pointed into the right direction.
My KDE runs as a Wayland session but I tested X11/XWayland by running the app as flatpak run chat.rocket.RocketChat --ozone-platform-hint=x11 as well.
Are you willing to submit a code contribution?
- [ ] Yes, I am willing to submit a Pull Request!
This may be caused by the recent flatpak builds updated to use org.electronjs.Electron2.BaseApp//23.08 as base, but afaics, this only adds some utilities and libs, like libnotify and zypak to allow the bundled electron app to run happily under flatpak's sandbox.
Maybe that zypak thingy is the cause? When the app is running I can see a zypak-sandbox zombie:
21957 ? Sl 0:04 | \_ /usr/bin/konsole
21969 pts/1 Ss 0:00 | | \_ /bin/bash
22979 pts/1 S+ 0:00 | | | \_ bwrap --args 40 rocketchat-desktop --enable-logging
22988 pts/1 S+ 0:00 | | | \_ bwrap --args 40 rocketchat-desktop --enable-logging
22989 pts/1 Sl+ 0:02 | | | \_ /app/Rocket.Chat/rocketchat-desktop --ozone-platform-hint=auto --enable-logging
22992 pts/1 S+ 0:00 | | | | \_ cat
22993 pts/1 S+ 0:00 | | | | \_ cat
22998 pts/1 S+ 0:00 | | | | \_ /app/Rocket.Chat/rocketchat-desktop --type=zygote --no-zygote-sandbox --enable-logging
23048 pts/1 Sl+ 0:00 | | | | | \_ /app/Rocket.Chat/rocketchat-desktop --type=gpu-process --enable-logging --ozone-platform=wayland --enable-crash-reporter=cbff32b1-ef97-4587-bcab-75f81a86d12d,no_channel --user-data-dir=/home/stretz/.var/app/chat.rocket.RocketChat/config/Rocket.Chat --gpu-
23000 pts/1 Z+ 0:00 | | | | \_ [zypak-sandbox] <defunct>
23053 pts/1 Sl+ 0:00 | | | | \_ /app/Rocket.Chat/rocketchat-desktop --type=utility --utility-sub-type=network.mojom.NetworkService --lang=en-US --service-sandbox-type=none --enable-logging --enable-crash-reporter=cbff32b1-ef97-4587-bcab-75f81a86d12d,no_channel --user-data-dir=/home/stretz/.
23104 pts/1 Sl+ 0:02 | | | | \_ /app/Rocket.Chat/rocketchat-desktop --type=renderer --enable-crash-reporter=cbff32b1-ef97-4587-bcab-75f81a86d12d,no_channel --user-data-dir=/home/stretz/.var/app/chat.rocket.RocketChat/config/Rocket.Chat --app-path=/app/Rocket.Chat/resources/app.asar --no-san
23122 pts/1 Rl+ 0:07 | | | | \_ /app/Rocket.Chat/rocketchat-desktop --type=renderer --enable-crash-reporter=cbff32b1-ef97-4587-bcab-75f81a86d12d,no_channel --user-data-dir=/home/stretz/.var/app/chat.rocket.RocketChat/config/Rocket.Chat --app-path=/app/Rocket.Chat/resources/app.asar --no-san
23149 pts/1 Sl+ 0:00 | | | | \_ /app/Rocket.Chat/rocketchat-desktop --type=utility --utility-sub-type=audio.mojom.AudioService --lang=en-US --service-sandbox-type=none --enable-logging --enable-crash-reporter=cbff32b1-ef97-4587-bcab-75f81a86d12d,no_channel --user-data-dir=/home/stretz/.var/
23151 pts/1 Sl+ 0:00 | | | | \_ /app/Rocket.Chat/rocketchat-desktop --type=utility --utility-sub-type=video_capture.mojom.VideoCaptureService --lang=en-US --service-sandbox-type=none --enable-logging --enable-crash-reporter=cbff32b1-ef97-4587-bcab-75f81a86d12d,no_channel --user-data-dir=/ho
23012 ? S 0:00 | | | \_ bwrap --args 41 /app/bin/zypak-helper child - /app/Rocket.Chat/rocketchat-desktop --type=zygote --enable-logging
23013 ? S 0:00 | | | \_ /app/Rocket.Chat/rocketchat-desktop --type=zygote --enable-logging
and when I digged through my journal I can find a reference to a single crash of zypak-helper:
Okt 05 16:20:33 xxx systemd[991]: Started app-flatpak-chat.rocket.RocketChat-18654.scope.
Okt 05 16:20:34 xxx systemd-coredump[18669]: Process 18662 (zypak-helper) of user 1000 dumped core.
Found module /app/bin/zypak-helper with build-id: 4962fb043349757d56df198e46f14f2e99b1edb0
Found module /usr/lib/x86_64-linux-gnu/libgpg-error.so.0.34.0 with build-id: 66cc26d5493ce374c98594c6a0401b5babc949e2
Found module /usr/lib/x86_64-linux-gnu/libzstd.so.1.5.5 with build-id: ef336733bc42252fc4a1848f48c479d6761ff425
Found module /usr/lib/x86_64-linux-gnu/liblzma.so.5.4.4 with build-id: 80e8ea4bf6558267fa0c66752f261d43a45cc01a
Found module /usr/lib/x86_64-linux-gnu/libgcrypt.so.20.4.2 with build-id: f50c791459d7f8fa9d45254e52fa84469ba3db6f
Found module /usr/lib/x86_64-linux-gnu/libc.so.6 with build-id: 8d9c562a7b90a3dfab1b1eb53105c2abd1bec806
Found module /usr/lib/x86_64-linux-gnu/libm.so.6 with build-id: 261d700577656be20d724cca9148afe1f6f92825
Found module /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.32 with build-id: 048bce33408e20582b93c7688412336cd38193f5
Found module /usr/lib/x86_64-linux-gnu/liblz4.so.1.9.4 with build-id: 62f3dcd878cd96b4d9bf4719e77ff0721723d1fd
Found module /usr/lib/x86_64-linux-gnu/libcap.so.2.69 with build-id: dbb554666d42410a10ff9816d1e7d0866c2f1f95
Found module /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 with build-id: 60db3e30d811175413e221075abcd8042d4b2d41
Found module /usr/lib/x86_64-linux-gnu/libsystemd.so.0.37.0 with build-id: 4148dc2a14757429d8fff9b2180f7ffa3f97aaee
Found module /usr/lib/x86_64-linux-gnu/libdbus-1.so.3.32.4 with build-id: 7ca0f9284a0b985e71080e0861ee5068b3983716
Found module /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2 with build-id: 9c0f1d2a4d06184563fd4fed1484f2737cb83198
Found module linux-vdso.so.1 with build-id: 0f002072a3870b153e72719ac3e6693d78320c19
Stack trace of thread 2:
#0 0x00007f66687bae14 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x90e14)
#1 0x00007f6668768dce n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x3edce)
#2 0x00007f666875083f n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2683f)
#3 0x0000557377a20b9d n/a (/app/bin/zypak-helper + 0xab9d)
#4 0x0000557377a2222c n/a (/app/bin/zypak-helper + 0xc22c)
#5 0x00007f666875208a n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2808a)
#6 0x00007f666875214b n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x2814b)
#7 0x0000557377a1ed75 n/a (/app/bin/zypak-helper + 0x8d75)
Okt 05 16:20:34 xxx systemd[991]: Started Launch DrKonqi for a systemd-coredump crash (PID 18670/UID 0).
Okt 05 16:20:34 xxx drkonqi-coredump-launcher[18678]: Unable to find file for pid 18662 expected at "kcrash-metadata/18662.ini"
Okt 05 16:20:34 xxx drkonqi-coredump-launcher[18678]: QFile::remove: Empty or null file name
Okt 05 16:20:34 xxx drkonqi-coredump-launcher[18678]: Nothing handled the dump :O
I have similar issue, application closes every time after few seconds when I receive message. I am using Ubuntu 22.04.3 LTS with flatpak rocket chat version 3.9.9
@Firiks that sounds like flathub/chat.rocket.RocketChat#121 instead and should be fixed by the latest rebuild of the flatpak. Please comment on that bug if updating the flatpak fixed the issue for you.
We did some additional debugging in flathub/chat.rocket.RocketChat#122 and what I found were some odd KILL signals being sent by something. I am still trying to identify the source.
i encountered this today on fedora 39 with flatpak v 3.9.10, rocketchat 6.4.8.
it seems like rocket chat closed while a new notification arrived.
is there anything we can do to better support rocket.chat under wayland? fedora has switched to wayland as their primary desktop environment. are there logs we can supply oder anything else that would make it possible for this to be fixed? :)
for me it is reproducible a few minutes after startup or when in a jitsi call when using this start arguments for the current flatpak:
/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=/app/bin/rocketchat-desktop --file-forwarding chat.rocket.RocketChat @@u %U @@ --enable-features=WebRTCPipeWireCapturer,UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland