Skip to content
This repository has been archived by the owner on Oct 29, 2018. It is now read-only.

Can't log in to workspace #616

Open
ErikEklund opened this issue Apr 28, 2018 · 18 comments
Open

Can't log in to workspace #616

ErikEklund opened this issue Apr 28, 2018 · 18 comments

Comments

@ErikEklund
Copy link

ScudCloud Version

ScudCloud 1.65 Python 3.6.5 Qt 5.10.1 WebKit 602.1 PyQt 5.10.1 SIP 4.19.8

Distro and Desktop info

  • Distribution: Arch
  • Version/Release: -
  • Desktop environment: Deepin

Expected behavior

After entering my login credentials, the workspace should load normally

Actual behavior

Stuck on loader screen - it never finished loading.

Steps to reproduce

  1. Install scudcloud and start it
  2. Enter credentials for a new workspace
  3. Observe the loader. Nothing else happens and it never finishes.
@raelgc
Copy link
Owner

raelgc commented Apr 29, 2018

Hi @ErikEklund and thanks for reporting this. I faced this onetime, started it with scudcloud --debug=True to check the problem, then it started properly. Still an issue for you?

@ErikEklund
Copy link
Author

I tried starting with the debug flag. No change in behavior and no output in the terminal (except for "Mouse button 1" and "URL Changed", not helpful). So yes, still an issue. The console showed this though:

deepinscreenshot_select-area_20180429220435

@thismatters
Copy link

Version Info

  • ScudCloud 1.65
  • Python 3.6.5
  • Qt 5.9.5
  • WebKit 602.1
  • PyQt 5.10.1
  • SIP 4.19.7

Distro and Desktop Info

  • Distro: lubuntu
  • Version: 18.4
  • Desktop Environment: AwesomeWM

I'm seeing the same behavior:

$ scudcloud --debug=True
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
URL Changed: https://slack.com/signin
Mouse Button 1
URL Changed: https://xxxxxx.slack.com/
Mouse Button 1
Mouse Button 1
URL Changed: https://xxxxxx.slack.com/messages

@raelgc
Copy link
Owner

raelgc commented May 2, 2018

The goal of start with the debug is being able to right click and select Inspect and then select the Console tab. There we can see JavaScript errors.

@ErikEklund
Copy link
Author

@raelgc JavaScript console errors posted above

@raelgc
Copy link
Owner

raelgc commented May 2, 2018

Thanks @ErikEklund. I remember this issue.

Is it to hard for you downgrade your Qt to, at least, Qt 5.7.1 (instead of 5.10.1) and test again?

@ErikEklund
Copy link
Author

I tried digging up 5.7.1 in the arch package archive, but after downgrade scudcloud failed with error message libicui18n.so.58: cannot open shared object file: No such file or directory. I tried downgrading icu as well, but that didn't seem to help. So no, can't seem to get scudcloud running on a lower version for now.

@raelgc
Copy link
Owner

raelgc commented May 2, 2018

I'm facing a hardtime with Qt/Webkit: older and newer versions are not working with Slack internal JS code. Sometimes I think scudcloud is good candidate for a flatpack/snap package (so I can include the required Qt version). The problem is this will make the package huge in size or in requirements.

@ErikEklund
Copy link
Author

I see. I don't know if it helps in any way, but right now I'm running the official Slack client (not flatpak / snap versions) with qt 5.10.1 with no issues. I'm not sure if it's built in the same way as scudcloud though, so might not be important.

@ErikEklund
Copy link
Author

On that note, the official slack client is 220 MB, vs ~350k for scudcloud :). I'm not sure people would mind a larger client, as long as it works.

@raelgc
Copy link
Owner

raelgc commented May 2, 2018

Slack official client uses Electron, which is a JS packaged version of Chromium (the open source version of Google Chrome). So it's not using Webkit as engine for HTML/CSS/JS rendering, but Google blink.

@petr-nehez
Copy link

Same issue here on Manjaro KDE...
A change of User-Agent wouldn't help?

@masoud-al
Copy link

masoud-al commented May 31, 2018

Same issue on ArchLinux with Cinnamon desktop and ScudCloud 1.65, PyQt 5.10.1
output of the scudcloud --debug=True

libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
qt5ct: D-Bus system tray: no
qt5ct: D-Bus global menu: no
URL Changed: https://slack.com/signin
Mouse Button 1
Link Clicked: https://xyz.slack.com/
URL Changed: https://xyz.slack.com/messages```

@bashM0nk3y
Copy link

bashM0nk3y commented Jul 14, 2018

Same issue on:
Arch Linux KDE 4.14.55-1-lts
plasma version 5.13.3
KDE framworks 5.47.0
ScudCloud 1.65
Python 3.6.6
Qt 5.11.1
WebKit 602.1
PyQt 5.11.2
SIP 4.19.12

Output after:

...$ scudcloud --debug=true
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
URL Changed: https://slack.com/signin
Mouse Button 1
Link Clicked: https://10-sec.slack.com/
URL Changed: https://10-sec.slack.com/messages

@raelgc
Copy link
Owner

raelgc commented Jul 15, 2018

@masoud-al and @bashM0nk3y You need to post the content of the web console: after start with debug enabled, right click in the messages, select Inspect, then the Console tab and paste here the content.

@bashM0nk3y
Copy link

bashM0nk3y commented Jul 15, 2018

Imgur Link - https://imgur.com/a/rznEvzc Just in case you have trouble viewing.

Looks like this is very similar, although not identical to ErikEklund's (OP) post.

Please let me know if there is anything at all that I can do to make debugging this issue easier on you!

@raelgc
Copy link
Owner

raelgc commented Jul 15, 2018

Thanks @bashM0nk3y. I can see it's the same problem affecting all of us not using 16.04: webkit newer than 5.7 has problems with ProxyObject in the JS side.

For now we have only all those hard options to try:

  • we can wait until webkit fix this issue some day
  • we can expect React considers webkit a supported browser
  • you can try use annulen webkit which has the Proxy disabled (I used this as fix for Ubuntu 16.04)
  • we can try replace webkit with Chromium (big effort)

@raelgc
Copy link
Owner

raelgc commented Oct 26, 2018

I'm stopping ScudCloud development, please see #628

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants