Arch Linux User Repository

On my machine (up to date on 2019/11/1) the build got stuck while rebuilding packages. Installing eslint solved the issue. Also there is the warning:

warning " > @rocket.chat/eslint-config@0.4.0" has incorrect peer dependency "eslint@^4.19.1 || ^5.16.0".

Is there a missing dependency?

Just pushed an update to fix build with electron 7.

• https://github.com/atom/node-spellchecker/issues/127
• https://github.com/atom/node-spellchecker/pull/128

Finally got rid of the python2 dependency. node-gyp works fine with python now.

Had to pin nodejs version to 12 because it doesn't build with 13 (which is in community-testing right now)

Updated to 2.15.5. Please excuse the delay, there were some issues upstream.

To build this nodejs<12 is now required. Version 12 is in community-testing right now and breaks the build due to a dependency. I have created an issue upstream https://github.com/anaisbetts/node-system-idle-time/issues/17

Hopefully this will be resolved soon. If it is not the case, I'll recreate the issue in the rocketchat repository.

The notification timeout works fine in the new version... I guess it's fixed by ignoring the issue. :)

Hello my dudes. So there we go 2.15.0 is out. The notifications timeout patch is gone and hopefully all the related issues as well.

Now depends on electron (3) instead of electron2. This is good, but might not quiet perfect since upstream actually wants electron 4(!).

As you can see in the PKGBUILD, I downgraded to electron@^3.1.4, because I noticed at least one thing that was broken. Looks like 4 is not fully backwardscompatible.

@Turtizzle

I didn't know what to answer or what to do. But today I saw this merged pull request arrive:

https://github.com/RocketChat/Rocket.Chat.Electron/pull/1101

This might actually solve all the notification issues. Let's hope it does.

@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

@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?

@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.

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.