In the app, going File > Workspace > Sign in to new workspace launches a browser window. After selecting the workspace in browser, it launches back a deep link back to slack but it doesn't work. Nothing happens on the slack-desktop.
After digging into the matter it sounds like the kde-open5 from kde-cli-tools is doing some funky lower-casing on first element of URL (slack://A/B/C becomes slack://a/B/C). This sounds like an old bug: _bug.cgi?id=429408
I'm using Archlinux, and neither clicking on link didn't work, neither passing link to slack arguments. Also you can find a correct link if you open dev console in browser it should be in console output. If you copy this link to your clipboard (ctrl+c) and then you switch to your slack app. It seems like onFocus slack automatically reads the clipboard and process it if it's a link. That gets be logged in.
I have this problem almost every time I restart my computer, and I have some 10 active slack workspaces, so hacked a quick bash script to do the caps trick for me. It's not meant to be robust, but it works. I'll leave it here in case it's useful for anybody else.
I don't seem to have the setting that Shawn mentions, but i was able to make this work by opening up the /usr/lib/slack/resources/app.asar.unpacked/src/static directory, making a copy of the slack-taskbar-rest.png file and renaming it to slack-taskbar-unread.png to overwrite the version with the blue dot.
Until then, this should be a community wiki, to prevent a new answer from being generated for each new slack version. Add your scripts here, and clearly state the latest version on which it works, newest on top.
More elaborate but hopefully future-proof answer. You want to search for setTrayIcon function in the main.*.js file (in 4.27 it's named main.bundle.js). Look for code using the icon file - const O = nt.resolve(__dirname, "resources", 'slack-taskbar-$t.ico'); In this case variable t is the status selecting the image. You want to add condition changing t to "rest" when it's "unread".
I found these problems, my slack was installed by *.deb and yesterday I updated to version 4.27. I solved it by updating the nvidia video card drivers, using the drivers from the nvidia-driver package.
- The whole system freezes, I can't switch to another terminal and fix things
- It occurs on Gnome Wayland and XOrg
- It is resolved by starting with linux-lts (5.15.86-1) instead of linux (6.1.4.arch1-1)
Slack has really followed the MS model. First, you could use them with any irc client. Then they broke that, though it can still be used with weechat using the wee_slack plugin. They seem to get worse and worse, but as most companies use Windows, they get away with it. I hope that some other company comes along and is as nice as Slack pretended to be, allowing irc clients and so on, without tying you to their bloated apps. Right now, all I can say is try to get your company to use something less Microsoft-ish.
I'm using Garuda Linux for a while now and recently I was in need of using slack for professional usage I immediately found that it was not working as expected because, in the dragonized edition, Slack fails to sign in!
Open the slack client and click on login. Now the redirect will fail and you won't be logged in but in Browser, you'll see that slack gives you one magic link. Simply click on that button to copy the magic link and click on the slack app.
I am right now to setup an Pop!_OS installation to see, what goes wrong with jack and eve launcher. And btw i am tired to search solutions for problems, which are not associated with a standard installation of some linux distribution. EVE Launcher works with
Description of the issue:
When clicking on a link, like within the web based version of slack. The correct action should be that it opens up the slack workspace in my local client. I receive an error pointing to unable to xdg-open
I do think this is it You should be able to see an entry for slack in brave://settings/handlers which may not be set. - I do not have any entries. But I also installed Brave via snap and I there are no update options there (my desktop is RHEL 7.7) - should I take a different approach to installing brave to pick up the updates? Any guidance on how to address the handlers?
I doubt that they provide support for all linux distributions on the planet. Having a small, new distro has a lot of advantages, but a disadvantage is certainly that you need to do the things yourself that you need to get done.
Slackware's package management system, collectively known as pkgtools, can administer (.mw-parser-output .monospacedfont-family:monospace,monospacepkgtool), install (installpkg), upgrade (upgradepkg), and remove (removepkg) packages from local sources. It can also uncompress (explodepkg) and create (makepkg) packages. The official tool to update Slackware over a network or the internet is slackpkg. It was originally developed by Piter Punk as an unofficial way to keep Slackware up-to-date. It was officially included in the main tree in Slackware 12.2,[43] having been included in extras/ since Slackware 9.1.[44] When a package is upgraded, it will install the new package over the old one and then remove any files that no longer exist in the new package. When running upgradepkg, it only confirms that the version numbers are different, thus allowing downgrading the package if desired.
Packages contain all the files for that program, as well as additional metadata files used by the package manager. The package tarball contains the full directory structure of the files and is meant to be extracted in the system's root directory during installation. The additional metadata files, located under the special install/ directory within the tarball, usually include a slack-desc file, which is a specifically formatted text file that is read by the package manager to provide users with a description of the packaged software,[46] as well as a doinst.sh file, which is a post-unpacking shell script allowing creation of symbolic links, preserving permissions on startup files, proper handling of new configuration files, and any other aspects of installation that can not be implemented via the package's directory structure.[47] During the development of 15.0, Volkerding introduced support for a douninst.sh uninstall script that can be launched when removing or upgrading a package.[48] This allows package maintainers to run commands when a package is uninstalled.
Slackware is also available for the IBM S/390 architecture in the form of Slack/390 and for the ARM architecture under Slackware ARM (originally known as 'ARMedslack'). Both ports have been declared "official" by Patrick Volkerding.[107][108] However, the S/390 port is still at version 10.0 for the stable version and 11.0 for the testing/developmental version, and has had no updates since 2009.[109][110] Also, on May 7, 2016, the developer of Slackware ARM announced 14.1 will be EOL on September 1, 2016 and development of -current will cease with the release of 14.2, however support for 14.2 will be maintained for the foreseeable future.[111] The EOL announcement for 14.1 was added to the changelog on June 25, 2016,[112] and the EOL announcement for 14.2 was added to the changelog on December 21, 2022.[113]
I'm an IRC kind of guy. I appreciate the simplicity of pure text chat,emoticons instead of emojis, and the vast array of IRC clients and servers tochoose from, including the option to host your own. All of my interactivecommunication happens over IRC either through native IRC channels (like#linuxjournal on Freenode) or using a local instance of Bitlbee to act as anIRC gateway to other chat protocols. Because my IRC client supportsconnecting to multiple networks at the same time, I've been able to manageall of my personal chat, group chat and work chat from a single window thatI can connect to from any of my computers.
If this is the only Slack account you have created, it will label it as"slack", and you can refer to it that way. Otherwise, you'll need to typeaccount list in the Bitlbee console and see how Bitlbee numbered your slackaccount, and then replace slack in the above commands with the numberassociated with that account.
The primary benefit from subscribing to LWN is helping to keep us publishing, but, beyond that, subscribers get immediate access to all site content and access to a number of extra site features. Please sign up today! By Jonathan Corbet
January 12, 2010 One of the best ways to reduce a system's power usage is to avoid waking upthe CPU whenever possible. Minimizing wakeups, in turn, is facilitated byensuring that timers expire at the same time when it makes sense to do so.Waking the processor once to handle two timers is much more efficient thanhandling them in two separate wakeups. But doing so typically requiresadjusting expiration times. For standard (not high resolution) kerneltimers, the only way to make that adjustment is with theround_jiffies() function, which makes timeout periods coarser inthe hopes that they will coincide more often. This method works to anextent, but it requires code changes wherever timers are used.Arjan van de Ven has proposed an enhancement to the timer API - called timer slack - which should makeit easier to coalesce timer events. In essence, it adds a certain amountof fuzziness to timer expiration times, giving the kernel some flexibilityin how the timers are scheduled. That fuzziness is set with: void set_timer_slack(struct timer_list *timer, int slack_hz);In essence, this call says that any timeout scheduled with the giventimer can be delayed by up to slack_hz jiffies. Bydefault, the slack is set to 0.4% of the total timeout period - a veryconservative value.When the timer is queued, the actual expiration time is determined by meansof a simple algorithm to choose a well-defined time within the slackperiod. The value of this approach is that it makes it easy to coalesce timerevents from multiple sources without needing to change every call site.Additional flexibility can then be had by increasing the slack forspecific, frequently-used timers, but, even without that, slack timersshould improve power efficiency on many systems. Index entries for this article KernelTimers (Log in to post comments) Timer slack Posted Jan 21, 2010 15:03 UTC (Thu) by jch (guest, #51929) [Link]