Package Details: rocketchat-desktop 3.0.7-1

Git Clone URL: (read-only, click to copy)
Package Base: rocketchat-desktop
Description: Rocket.Chat Native Cross-Platform Desktop Application via Electron.
Upstream URL:
Keywords: chat client electron rocket rocketchat
Licenses: MIT
Conflicts: rocketchat-client-bin
Submitter: sum01
Maintainer: matthias.lisin
Last Packager: matthias.lisin
Votes: 17
Popularity: 0.56
First Submitted: 2017-10-23 16:52
Last Updated: 2020-11-09 20:55

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

Turtizzle commented on 2019-02-21 16:08

@matthias.lisin That's weird, I am using xfce4-notifyd and have a default timeout of 10 seconds configured, which works fine when I test it with notify-send. My rocketchat messages do not disappear though... and it used to work when I was still testing it with the hardcoded 10 seconds patch.

Honestly, the behavior I'd prefer is having a single notification that adapts when new messages arrive, similarly to how smartphones tell you about consecutive messages... or have notifications automatically disappear when you read the respective messages in RocketChat... but that's a larger issue. As for what do do now, I suppose that's up to you. You can always make it configurable in the PKGBUILD for people who prefer it differently, if you want... that's what we build packages from source for. :P

matthias.lisin commented on 2019-02-19 09:33

@ruebsd By all means, I can't see how any of my patches might have caused this. I just cleaned everything and recompiled it again and I honestly can't reproduce what I have seen on your screenshot.

Would you be so kind to compile rocketchat from source (master) and maybe from the v2.14.7 tag? Does this solve the issue? Is it really just this AUR Package?

@Turtizzle So, messages disappear after a few seconds for me on KDE. Guess it really uses the default. If I don't read the notifications in time they minimize to tray, which I'm not really sure is good or bad. What do you think about this, and should be go back to a fixed timeout instead?

ruebsd commented on 2019-02-18 18:53

@matthias.lisin, I tried rocketchat-client-bin, that aur worked without a hitch for me. As for this aur, I tried it again and got the same result I described in the previous comment. I took a screenshot of it, so I'll send you the link on irc.

matthias.lisin commented on 2019-02-18 11:59

Hello ruebsd, I can't reproduce this. Please try installing the binary package rocketchat-client-bin and tell me if you get the same issues.

ruebsd commented on 2019-02-18 11:19

I tried it the other day, but it seems like the input textbox isn't show anywhere on the screen. The main display area also seems kind of buggy - the text gets cut off on the right and doesn't wrap when you resize the window so only way to see full messages is by going fullscreen. :(

matthias.lisin commented on 2019-02-14 14:56

Some notification daemon don't set their own timeout and rely on the application, so I guess relying on the default settings might not be the best solution for those daemons.

Turtizzle commented on 2019-02-14 14:12

Reporting back after testing for 1 day myself: I've had mixed results with this particular patch. Earlier, I tested it with a hardcoded timeout of 10 seconds, which worked fine. I assumed, removing it entirely would use the default value, but now the messages won't disappear again, just like before. :/

I'll keep you informed if I figure out more.

matthias.lisin commented on 2019-02-13 14:47

Hello Turtizzle my friend, Thanks for the suggestion, I've been annoyed by the never disappearing notifications for a while now but never got around to see what's wrong.

I have applied the suggested patch, let's see how well it works.

Turtizzle commented on 2019-02-13 14:21

May I suggest adding the following patch? It removes the hard coded 24h notification timeout and uses the configured default timeout of the notification daemon instead.

diff -ura package.orig/src/background/notifications.js
--- package.orig/src/background/notifications.js    2019-02-13 15:06:35.778156745 +0100
+++ 2019-02-13 15:07:01.368069410 +0100
@@ -86,7 +86,6 @@
            body: body && this.escapeBody(body),
            icon: icon ? path.resolve(icon) : 'info',
            appName: app.getName(),
-           timeout: 24 * 60 * 60 * 1000,
            sound: silent ? undefined : 'message-new-instant',
            actions: process.env.XDG_CURRENT_DESKTOP !== 'Unity' ? {
                default: '',

matthias.lisin commented on 2019-02-08 08:45

There is a good chance the next release will use Electron 3.

To the future, and beyond. ( ͡° ͜ʖ ͡°)