Describe the bug
During interactive sign-in, the Chromium version that gets downloaded and opens is 128, while Slack only supports Chromium 137 or higher. During automatic sign-in the Slack login goes on for more than 10 minutes without actually doing anything after the browser has been downloaded and extracted and I assume opened in the background. This was in the terminal for 10 minutes: Logging in to Slack, it will take 25-40 seconds.
Authentication type (please read)
email + password
Automatic and interactive
To Reproduce
Steps to reproduce the behavior:
- Run
slackdump workspace new in interactive mode, Chromium gets downloaded and opens at the login page, but the page is a white blank page. The same link works in my Firefox for login.
Expected behavior
The Slack login page would appear, showing the email and password fields.
Output
If applicable, add output to help explain your problem.
Desktop (please complete the following information):
- OS: CachyOS Linux [v7.0.0-1-cachyos]
- OS Version: rolling
- Slackdump Version: 4.3.0
Additional context
I can only assume that the unsupported browser is causing this bug. I can also assume that's why the automatic method doesn't work either.
Describe the bug
During interactive sign-in, the Chromium version that gets downloaded and opens is 128, while Slack only supports Chromium 137 or higher. During automatic sign-in the Slack login goes on for more than 10 minutes without actually doing anything after the browser has been downloaded and extracted and I assume opened in the background. This was in the terminal for 10 minutes:
Logging in to Slack, it will take 25-40 seconds.Authentication type (please read)
email + password
Automatic and interactive
To Reproduce
Steps to reproduce the behavior:
slackdump workspace newin interactive mode, Chromium gets downloaded and opens at the login page, but the page is a white blank page. The same link works in my Firefox for login.Expected behavior
The Slack login page would appear, showing the email and password fields.
Output
If applicable, add output to help explain your problem.
Desktop (please complete the following information):
Additional context
I can only assume that the unsupported browser is causing this bug. I can also assume that's why the automatic method doesn't work either.