-
Notifications
You must be signed in to change notification settings - Fork 99
Switch workspace opens workspace in default browser, not Scudcloud #608
Comments
@LunkRat Thanks for raising this. I've published a fix and packages for Ubuntu. Please, run a system upgrade and report feedback. |
@raelgc indeed, it fixed the problem. I forgot that the UI has the teams/workspaces as icons on the leftmost black strip of the Sidebar. When I raised this issue, Scudcloud was not showing the team switcher icons at all. Now they appear and they work as expected. Thank you! |
@LunkRat Indeed, the leftbar was not appearing due the issue. Thank you for your time reporting and testing the issue! |
I remember installing a ScudCloud update around the time the fix was released, but I'm still having this issue. The new workspace opens in my default browser, Firefox. ScudCloud versionScudCloud 1.64-1 Distribution and desktop informationDistribution: Ubuntu 16.04 LTS |
Slack has just change how their JS loads the teams list again (including several other minor changes)... |
I am also still having this problem.. ScudCloud version ScudCloud 1.64-1 Distribution: Ubuntu 16.04 LTS |
I've published a new Ubuntu version, disabling the quicklist. But this time Slack changed a lot of their JS. I'm sure we'll face new issues. |
This issue also occurs on Scudcloud version 1.65-2.fc28 on Fedora 28. P.S. Kudos to your whole team for the Linux love. |
This issue also occurs on Scudcloud version 1.65-2.fc28 on Fedora 28. Note that Scudcloud has to forward me over to onelogin.com for SSO authentication with the target Slack workspace, which pops the default browser up for authentication. It then opens the target Slack workspace in the browser just fine, so it's not a show stopper, just a minor inconvenience. P.S. Kudos to your whole team for the Linux love. |
ScudCloud Version
Distro and Desktop info
Expected behavior
Open alternate (signed-in) workspace in scudcloud
Actual behavior
Alternate (signed-in) workspace opens in Chromium
Steps to reproduce
The text was updated successfully, but these errors were encountered: