I ran 3.8.3 under Wayland just fine; I can't vouch for X11, however. Please let me know if anyone else can't run this package. I will consider pinning this package to electron17 as listed below if this is a widespread issue.
Search Criteria
Package Details: rocketchat-desktop 3.9.14-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/rocketchat-desktop.git (read-only, click to copy) |
|---|---|
| Package Base: | rocketchat-desktop |
| Description: | Rocket.Chat Native Cross-Platform Desktop Application via Electron |
| Upstream URL: | https://github.com/RocketChat/Rocket.Chat.Electron |
| Keywords: | chat client electron rocket rocketchat |
| Licenses: | MIT |
| Submitter: | sum01 |
| Maintainer: | buzo |
| Last Packager: | buzo |
| Votes: | 29 |
| Popularity: | 0.040908 |
| First Submitted: | 2017-10-23 16:52 (UTC) |
| Last Updated: | 2024-02-17 12:01 (UTC) |
Dependencies (6)
- electron22 (electron22-binAUR)
- libvips (libvips-gitAUR)
- nodejs (nodejs-gitAUR, nodejs-lts-fermiumAUR, nodejs-sharedAUR, nodejs-lts-hydrogen, nodejs-lts-iron)
- asar (make)
- node-gyp (corepackerAUR) (make)
- yarn (corepackerAUR, yarn-pnpm-corepackAUR, yarn-berryAUR) (make)
Required by (0)
Sources (2)
lmartinez-mirror commented on 2022-04-18 00:31 (UTC)
vtc commented on 2022-04-12 15:06 (UTC)
For now adding community/electron17 as a dependency and patching /usr/bin/rocketchat-desktop to call 'exec electron17 /usr/lib/rocketchat-desktop "$@"' solves problems.
0xFF1E071F commented on 2022-04-12 14:36 (UTC) (edited on 2022-04-12 14:43 (UTC) by 0xFF1E071F)
After this last update, now i have a blank gray screen after connecting my server. My electron version is v18.0.3
When i run from terminal i got this error:
$ rocketchat-desktop
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[17084:0412/154210.444200:ERROR:viz_main_impl.cc(188)] Exiting GPU process due to errors during initialization
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[17116:0412/154210.501225:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[17116:0412/154210.512980:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
/usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../include/c++/11.2.0/bits/unique_ptr.h:659: typename std::add_lvalue_reference<element_type>::type std::unique_ptr<blink::CSSSelector []>::operator[](std::size_t) const [_Tp = blink::CSSSelector [], _Dp = std::default_delete<blink::CSSSelector []>]: Assertion 'get() != pointer()' failed.
dusatvoj commented on 2022-01-27 19:16 (UTC)
update of electron to 16.0.7-2 breaks the ability to scroll up in Rocketchat (reinstalling/recompiling with a clean build does not solve the problem). The client freezes and turns grey, has to be reloaded from the View-menu but you still can't scroll up without the issue reappearing. I switched to the rocketchat-client-bin package because that one does not rely on the installed electron.
Lifesaver!!!
BS86 commented on 2022-01-26 11:56 (UTC) (edited on 2022-01-26 11:58 (UTC) by BS86)
the update of electron to 16.0.7-2 breaks the ability to scroll up in Rocketchat (reinstalling/recompiling with a clean build does not solve the problem). The client freezes and turns grey, has to be reloaded from the View-menu but you still can't scroll up without the issue reappearing. I switched to the rocketchat-client-bin package because that one does not rely on the installed electron.
lmartinez-mirror commented on 2021-08-25 03:21 (UTC)
Co-maintainer spots are open, as I don't use this often enough.
lmartinez-mirror commented on 2021-07-12 16:35 (UTC)
I'll revert the package version for the time being then, thanks!
AlynxZhou commented on 2021-07-12 08:32 (UTC)
Hi, it seems version 3.3.0 of rocketchat-desktop has a bug that leads into high cpu usage: https://github.com/RocketChat/Rocket.Chat.Electron/issues/2068, and 3.3.0 seems unpublished now, they have a 3.2.3 release as newest.
lmartinez-mirror commented on 2021-06-27 16:52 (UTC)
Forgot about that, thanks for the tip! I thought simply changing nodejs-lts-fermium to nodejs was enough. Pushing a fix.
Pinned Comments