Slackfix
Wrapper script, attempts to execute Slack with the correct URI argument.
The electron environment in Tumbleweed seems to suffer from a flaw similar to kde-open5 [1], that results in Slack failing to open the workspace correctly. It mangles the host part of the URI into lowerspace, which is Slack's undoing.
Background
Generic URL handling is defined in RFC 3986: URI Generic Syntax, where section 3.2.2 says: "The host subcomponent is case-insensitive"). The electron environment appears to conform with that in newer releases.
The simplest place to solve this would be also on the Slack side by accepting a lower case host part of the internal slack:// URI, or it shouldn't use any host part at all (slack:///...).
Since they are aware of this issue since several month, we cannot rely on a fix provided anytime soon [3], so here's a (hopefully) suitable antidote.
External resources
[1] KDE issue: https://bugs.kde.org/show_bug.cgi?id=429408 [2] https://www.rfc-editor.org/rfc/rfc3986 [3] With the usual outcome: we do not support openSUSE Tumbleweed, use the snap packages! Needless to say, they suffer from the same issue.
1 maintainer
Metadata
1 maintainer
Release files for slackfix 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| slackfix-0.1.2.tar.gz | 11.6 kB | Without provenance | Details |
Release files / slackfix-0.1.2.tar.gz
| Download URL | slackfix-0.1.2.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
02da78c14e2b375d8debde00535f9c4609bf8e8fadd80453c27aba29654a6a34
|
|
BLAKE2b-256 checksum How to use checksums |
2e19c02b93725cc0fc2b72510e289be225daccfff26f85b5bf4a1354fa6106c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/6.0.0 pkginfo/1.9.6 requests/2.28.2 requests-toolbelt/0.9.1 tqdm/4.64.1 CPython/3.8.16
|
Security for slackfix 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
