Posted  by  admin

Slack Electron

Package Details: slack-electron 4.14.0-1

  1. Electronjs Example
  2. Slack Electronica
  3. Slack Electron Github
  4. Slack Electronically
  5. Slack Electron Vulnerability
  6. Slack Electronics

Slack-Electron An Electron wrapper for Slack, since the default Linux client has positioning issues. Slack-Electron An Electron wrapper for Slack, since the default Linux client has positioning issues. From my understanding you want to inspect or manipulate some HTML of a electron app which is installed? This is how I figured out how to access (on Mac OS) using Slack as an example: Go to your Applications Folder - Slack - Right click 'Show Package Contents' Go To 'Contents-Resources - app.asar.unpacked'.

Key Action / Focus the search bar: Esc: Focus the search bar and cleans it ↓ Select the next search result ↑ Select the previous search result: Enter: Open the selected search result.

Package Actions

  • View PKGBUILD / View Changes
Git Clone URL: (read-only, click to copy)
Package Base: slack-electron
Description: Slack Desktop (Beta) for Linux, modified to use the system 'electron' package instead of its own
Upstream URL:
Licenses: custom: Slack
Conflicts: slack-desktop
Provides: slack, slack-desktop
Submitter: whiredplanck
Maintainer: yurikoles
Last Packager: yurikoles
Votes: 11
Popularity: 1.24
First Submitted: 2020-07-05 17:00
Last Updated: 2021-04-02 10:32

Dependencies (2)

  • electron(electron-ozone, electron-beta-bin, electron-nightly-npm)
  • libappindicator-gtk3(libappindicator-gtk3-ubuntu, libappindicator-bzr)(optional) – for notification indicator in the status bar on GNOME

Sources (2)

djmattyg007 commented on 2021-04-24 01:04

The latest update has made the PKGBUILD significantly more difficult to review.

Why were all references to 'slack' updated to '${_product}'? It's longer to write and more difficult to read.

Can you please update the bin script to use '#!/bin/bash' instead of '#!/bin/sh'? Pacman has a hard dependency on bash, so everyone will always have it installed. There's no reason to use '#!/bin/sh' on an Arch Linux system.

pychuang commented on 2021-04-21 20:05

@Koffiepoeder It's working for me. I'm using Sway and simply executed slack --enable-features=UseOzonePlatform --ozone-platform=wayland.

hpstg commented on 2021-04-21 14:23

Still cannot login with the latest PKGBUILD, which looks to have the changes integrated. This is under X11 in Gnome.

Electronjs Example

Koffiepoeder commented on 2021-04-21 09:48

For those wondering, using this version to get slack to run under wayland did NOT work for me (i.e. changing /user/bin/slack with the chromium flags --enable-features=UseOzonePlatform --ozone-platform=wayland). Kind of expected, but at least worth a try.

pychuang commented on 2021-03-19 18:52

@mvdan A request for making it an orphan package is already pending. Once the request goes through, other users can take over the package and push new changes.

mvdan commented on 2021-03-19 14:46

What can be done to get this package updated and/or integrate @qubidt's changes?

qubidt commented on 2021-02-10 15:52

Updated the PKGBUILD to fix the issues others mentioned. Also updated slack versions and moved the installation directory to /usr/lib to make it more consistent with other electron packages. Not sure which change specifically fixed the issue but I can 'sign in' successfully now.

slack-electron AUR diff:

crabvk commented on 2021-02-02 17:38

Slack electronegativity

I had the same problem. Then I quit my job and removed slask. Problem solved.

brando56894 commented on 2021-02-02 14:36

This one won't login for me, after I click 'Sign In' it brings me to the website which then tells me to login, which I do, then it tells me it wants to open Slack, and when it does it just opens a new instance telling me to sign in.

I removed this version and installed slack-desktop and it worked perfectly the first time.

djmattyg007 commented on 2021-01-28 03:44

Slack Electronica

Using '#!/usr/bin/env sh' in the shebang is pointless, because bash is a hard dependency of pacman. Everyone will always have it installed, so you may as well just refer directly to /bin/bash.

Written by

Slack Electron Github

Written by

Electron, a popular web application writing platform underlying some extremely widespread software including Skype and Slack, is vulnerable to a critical remote code execution vulnerability.

Apps are only vulnerable if they run on Microsoft Windows and register themselves as the default handler for a protocol like myapp://. MacOS and Linux apps are not vulnerable. Referred to as a “Protocol Handler Vulnerability,” the problem has been assigned the number CVE-2018-1000006.

Protocols like slack:// make it so that users can click links from other software like a web browser and directly go to, for instance, the Slack app.

Several widely used apps are built on Electron, including Windows desktop apps for the encrypted messaging app Signal, the audio chat app Discord and the content management system WordPress. However, most of these apps don’t register themselves as the default handler for a protocol like myapp:// so they are not vulnerable. You can find a full list of Electron apps here to better understand the popularity of Electron, but it’s not a definitive list of apps impacted by this vulnerability.

The recently released Slack versions 3.0.3+ for Windows addresses the vulnerability, according to a Slack spokesperson who urged all users to upgrade immediately.

A Microsoft spokesperson confirmed the newest version of Skype mitigated the vulnerability.

Electron’s appeal is that developers can easily write an app using web technology like HTML, CSS and JavaScript instead of rewriting it multiple times in different languages for multiple platforms.

Slack Electronically

Electron published new versions of their software to fix the vulnerability on Tuesday. All developers are urged to upgrade immediately.

Slack Electron Vulnerability

Update: Added a comment from Microsoft.

Slack Electronics

-In this Story-

Electron, Microsoft Windows, Skype, Slack