Arch Linux User Repository

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.

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.

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.

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.new/src/background/notifications.js
--- package.orig/src/background/notifications.js    2019-02-13 15:06:35.778156745 +0100
+++ package.new/src/background/notifications.js 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: '',

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

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

The package now uses the system electron2. Therefore it is now a dependency of this package. Don't worry about the additional size of the new dependency, because this package lost most than 120M of size itself!

Spell checking now uses the system hunspell dictionaries instead of using the ones provided by upstream. This is a breaking change and you need to install the desired hunspell-* packages to re-enable spell checking. Again, this is a zero sum game, the size gained by installing system hunspell dicts is lost through removing the package dicts.

Next upstream rocketchat-update is likely to use electron3, so don't worry about electron2 being somewhat a waste of space if you have electron installed also. It's gone soon.

As always, report problems.

I decided against leaving this package broken. As a temporary solution the yarn.lock Lockfile will be ignored.

Waiting for https://github.com/RocketChat/Rocket.Chat.Electron/issues/1024

Also had to patch the package.json due to (another) broken dependencie concerning electron-updater. I quickly tested it on my home machine and it seems to work.

Everything is a mess.

God have mercy

Edit: this comment is obsolete now

Hi je-vv, yes, it's broken now. But I can't fix it that easily because it's an issue somewhere else. (this whole event-stream drama)

I reported it upstream and will update as soon as it's fixed upstream. I would really like to patch it myself, but I'm not an expert and will probably break something else if I try to.

Build of 2.14.4 failing with:

==> Extracting sources...
  -> Extracting rocketchat-desktop-2.14.4.tar.gz with bsdtar
==> Starting prepare()...
patching file electron-builder.json
Hunk #1 succeeded at 86 (offset 10 lines).
patching file tasks/release.js
==> Removing existing $pkgdir/ directory...
==> Starting build()...
yarn install v1.12.3
[1/4] Resolving packages...
[2/4] Fetching packages...
error https://registry.yarnpkg.com/event-stream/-/event-stream-3.3.6.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "Unexpected end of data"
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: build: failure on package rocketchat-desktop

Updated to 2.14.4

Changes from 2.14.3 to 2.14.4