-
Notifications
You must be signed in to change notification settings - Fork 99
ScudCloud always displays the loading screen #294
Comments
I see the same problem :( One important difference: today I updated to Ubuntu 15.10 (from 15.04) and cannot login since this update |
I'm experiencing the same issue. |
Yep, me too! This is what I see when starting from the terminal: "sni-qt/4972" WARN 18:05:42.647 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE (python3:4972): Gdk-WARNING **: /build/gtk+2.0-qOsbtf/gtk+2.0-2.24.10/gdk/x11/gdkproperty-x11.c:325 invalid X atom: 500 |
Haven't been able to connect since I got into work this morning, over 3 hours ago. Can load it in my browser fine, but that's impractical. |
I've got the same issue. So far I've deleted my ~/.config/scudcloud directory and then removed and reinstalled ScudCloud which didn't help. |
I started to get the same here too. But, of course, I changed nothing on ScudCloud. Let me see if I can try any workaround. |
Same issue here in Ubuntu 14.04. |
I installed the plaidchat client, and it's working fine. |
I'm having the same issue here on Ubuntu 15.10. No error message but stuck with the Loading screen |
Could it be related to the User Agent HTTP header? |
I get |
+1 for plaidchat |
plaidchat may be working, but that does not fix scudcloud |
|
Getting the same issue here. Ubuntu 14.04 and ScudCloud reports version 1.0.89. Keeps getting stuck on the loading "spinner" . Let me know if there is anything else you need to help get this solved. |
+1 |
It also stopped working for me, stuck at loading screen, Ubuntu 15.04 |
Same here, Ubuntu 14.04. Tried:
No (relevant) errors when booting from CLI. |
For what its worth it's broken for me too this morning. This is what I get when launching from the cli Got bus address: "unix:abstract=/tmp/dbus-M9KctBOjDZ,guid=2668a7aefc4786ec276317e5564d8220" Ubuntu 15, trusty, Gnome3, All updates, I also just updated scudcloud too. |
Same for me. Ubuntu 14.04 LTS. Also tried to delete config but it doesn't help. |
Same here, Ubuntu 15.10
|
Same for me today on Arch. Didn't update anything. It worked yesterday. Now only web client works. If anybody can tell me how to get SSL private key from scudcloud I can use Wireshark to log network traffic. |
Slack's own beta Linux client works for me under Mint 17.2/64 |
Same here on Ubuntu 15.04 :( |
Moved to Slack's app. Goodbye. |
It doesn't work for me either on Ubuntu 15.10. I am now using the beta client for Linux (https://slack.com/downloads). |
Same for me, ubuntu 14.04 |
Moved to Slack official beta app, I fear that they killed Scud voluntarely :( |
Please, upgrade. |
Version 1.1.1 works again. Thanks! |
Just upgraded too. Fixed the problem. Thanks 👍 |
Many thanks ! |
Can confirm upgrade fixed issue 👍 |
Same here, all working fine after upgrade 👍 |
Thanks for the quick fix! 🤘 |
Hi, Version 1.1.1 was working fine this afternoon at office, but now, at home, I always loading screen:
😞 |
Be advised, slack is also having connectivity issues now in general, so it On Mon, Nov 23, 2015 at 2:43 PM, Gilles FELIX notifications@github.com
|
You've right, I try in Firefox, same issue |
You can see the Slack's status page here: https://status.slack.com/ |
I actually cant even hit the status page... |
same here, so giving a try to the official client |
same here, switched to official client. |
@wikier and @nadar Not sure if you understood the latest messages. ScudCloud was updated and it's working normally. Slack itself was facing problems, including their status page. Of course, you're free to use any client you want. And it's great the fact we have now 3 clients on Linux, so, in case of problems, we can switch between them. |
@raelgc i have read the latest messages and updated the application but it still displayed the loading screen. Probably the application update did not work. i dunno. #294 (comment) |
@nadar I cannot say for every supported distro. But it's updated for Ubuntu (all supported versions) and in code base. Maybe we need to wait for other maintainers. As a workaround for now, you can apply the fix manually, editing the # Now with local storage we need history enabled
QWebSettings.globalSettings().setAttribute(QWebSettings.PrivateBrowsingEnabled, False)
# Enabling Local Storage (now required by Slack)
QWebSettings.globalSettings().setAttribute(QWebSettings.LocalStorageEnabled, True) Make sure Slack changed their engine to now assume that all browsers and clients will answer for LocalStorage. |
Hey all, lead developer of the Slack Linux client - the Scudcloud breakage on our end was definitely unintentional / accidental, we're never going to intentionally get in the way or try to cause problems for anyone who writes a 3rd party client, and we're hugely appreciative of the hard work @raelgc and others have done to code up a great app for Linux users! |
Thanks @paulcbetts. It's very reassuring to hear that from a Slack employee. |
What a honor! @paulcbetts posting here! Paul, thank you for the make that clear. It was clear to me that the issues discussed here were caused by Slack improving/upgrading their product and qtwebkit not being able to properly run these changes. But now we have this mention from you, it's clear to everyone! |
This is still happening on v1.1.12, built from source. |
I have the following version, installed from the package repository: ScudCloud 1.39 ...and still the same error. PrivateBrowsingEnabled is False and LocalStorageEnabled is set to True. |
Yes, I just upgraded to 1.43 and did a general package upgrade before, and now it works. Thank you! |
You're welcome! :) |
Is there any issue with scudcloud again today as I started to face the same issue which was reported 4 days back. I am using LinuxMint 17.1 ScudCloud 1.43 |
I've been experiencing a nasty issue since today evening. ScudCloud simply does not go beyond the loading screen and does in fact lock the user out.
The terminal returns no errors whatsoever, not even in debug mode. Slack (meant as the service itself) is otherwise running fine; it works okay using the web client (under Firefox 42), the official Linux client (which, by the way, is by far worse than ScudCloud) and the mobile app. I tried deleting the configuration folder, but to no avail.
I do not know whether this problem is just momentary or if it is permanent, but I think it may be better to take note of the problem now so investigations can possibly take place if it is confirmed.
The text was updated successfully, but these errors were encountered: