Open ErikEklund opened 6 years ago
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?
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:
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
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.
@raelgc JavaScript console errors posted above
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?
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.
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.
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.
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.
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.
Same issue here on Manjaro KDE...
A change of User-Agent
wouldn't help?
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```
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
@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.
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!
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:
I'm stopping ScudCloud development, please see #628
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
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