I have just reinstalled Ubuntu MATE 22.04 and cannot get Insync to work. I have been running it for nearly 3 years under Ubuntu MATE on the same system without any trouble until today 
I have installed from the Software Boutique, from the .deb on the website, and from the APT repository and get the same each time. I note if I click around the window, I get taken to the Google Drive and OneDrive login pages.
Would appreciate any help!
Hi @mercunium! So sorry to hear that this is happening to you! 
Could you run the following commands for me please:
lsb_release -a
apt-cache policy insync
Also, could you please quit Insync and check if there are any firewalls/proxy settings that might be blocking Insync?
Hi @mia, that’s ok, it’s all part of the fun… 
mark@mark:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy
mark@mark:~$ apt-cache policy insync
insync:
Installed: 3.8.7.50516-jammy
Candidate: 3.8.7.50516-jammy
Version table:
*** 3.8.7.50516-jammy 500
500 http://apt.insync.io/ubuntu jammy/non-free amd64 Packages
100 /var/lib/dpkg/status
mark@mark:~$
Command output as requested. No, there are no rules in place at all, this is a fresh install Ubuntu MATE 22.04.4 desktop running on a VPS. It’s been running just fine on this system under Ubuntu MATE 20.04 and 22.04 previously and has only been since this reinstall. Nothing else has been done differently.
Edit: The e-mail address I have registered with isn’t the one my Insync registration is for - happy to PM if required.
Hi @mercunium! Could you uninstall 3.8.7 from your machine, then try installing the 3.9.0 build from https://www.insynchq.com/downloads/linux and let me know how it goes?
Hi again @mia ,
I did try installing from the .deb on the Insync website before to no avail but I tried again. Unfortunately, it’s still exactly the same with a black screen.
mark@mark:~$ apt-cache policy insync
insync:
Installed: 3.9.0.60000-jammy
Candidate: 3.9.0.60000-jammy
Version table:
*** 3.9.0.60000-jammy 100
100 /var/lib/dpkg/status
3.8.7.50516-jammy 500
500 http://apt.insync.io/ubuntu jammy/non-free amd64 Packages
Edit: I don’t know if the below output might be of interest too:
mark@mark:~$ insync start --no-daemon
INFO 2024-05-03 10:45:47,361 [mainlogs:_log_run:130] Core(app_version=3.9.0.60000, platform=Linux-x86_64-ubuntu/22.04) initialized
WARNING 2024-05-03 10:45:47,385 [base_events:_run_once:1900] Executing <Task pending name='Task-9' coro=<init() running at ideskcore/core.py:28> wait_for=<Task pending name='Task-10' coro=<SettingsMain._load_settings() running at ideskcore/mainsettings.py:186> cb=[_log_tb_after_delay() at ideskasync/coreloop.py:302, <TaskWakeupMethWrapper object at 0x78d1fc7b1cd0>()] created at ideskcore/mainsettings.py:160> cb=[_log_tb_after_delay() at ideskasync/coreloop.py:302, _chain_future.<locals>._call_set_state() at asyncio/futures.py:391] created at asyncio/events.py:80> took 0.230 seconds
INFO 2024-05-03 10:45:47,401 [mainsettings:_load_settings:236] Loaded settings, machine fingerprint = [xxx]
INFO 2024-05-03 10:45:47,677 [app:start_core:67] core started
INFO 2024-05-03 10:45:47,679 [unix_socket_server:start:106] unix socket server thread start
js: Access to XMLHttpRequest at 'https://us.i.posthog.com/decide/?v=3&ip=1&_=1714729548334&ver=1.110.0' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Access to XMLHttpRequest at 'https://us.i.posthog.com/decide/?v=3&ip=1&_=1714729548886&ver=1.110.0' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Access to XMLHttpRequest at 'https://us.i.posthog.com/e/?ip=1&_=1714729551426&ver=1.110.0' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Access to XMLHttpRequest at 'https://us.i.posthog.com/decide/?v=3&ip=1&_=1714729548886&ver=1.110.0&retry_count=1' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Access to XMLHttpRequest at 'https://us.i.posthog.com/decide/?v=3&ip=1&_=1714729548334&ver=1.110.0&retry_count=1' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Access to XMLHttpRequest at 'https://us.i.posthog.com/e/?ip=1&_=1714729551426&ver=1.110.0&retry_count=1' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Access to XMLHttpRequest at 'https://us.i.posthog.com/decide/?v=3&ip=1&_=1714729548886&ver=1.110.0&retry_count=1&' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Access to XMLHttpRequest at 'https://us.i.posthog.com/decide/?v=3&ip=1&_=1714729548334&ver=1.110.0&retry_count=1&' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
js: Access to XMLHttpRequest at 'https://us.i.posthog.com/e/?ip=1&_=1714729551426&ver=1.110.0&retry_count=1&' from origin 'file://' has been blocked by CORS policy: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'. The credentials mode of requests initiated by the XMLHttpRequest is controlled by the withCredentials attribute.
[...]
INFO 2024-05-03 11:02:20,376 [app:quit:82] quitting
INFO 2024-05-03 11:02:20,380 [unix_socket_server:stop:126] unix socket server thread stop
INFO 2024-05-03 11:02:22,420 [workbase:wait_cancelled_tasks:110] Cancellations of 1 tasks wasn't awaited.
INFO 2024-05-03 11:02:22,432 [app:stop:77] core stopped
INFO 2024-05-03 11:02:22,433 [app:stop:79] clean exitI’ll send this to our Linux engineer for investigation and update you accordingly. Thank you!
Hi @mia, thanks for your help.
As I mentioned before, this is installed on a remote VPS and I was accessing the desktop over VNC. At the time of installation, the Google Chrome Remote Desktop package which I usually use to access the system had been updated and was broken, however, a fix was released last night. I have now installed this and Insync no longer has the black screen.
This still might be something the developers are interested in as it seems strange that it wouldn’t work over VNC, but be assured that all is working well again for me.
I have issues with Fedora 40 but only under a standard (wayland session). It works when I switch to an xorg session.
Thank you for the update, @mercunium! I will be forwarding this to our engineers and explore the possible issues when using over VNC.
@nomadfh That is quite intriguing and potentially annoying! I will have our engineers test this for you. Could you confirm what version you are running please?
Hi @nomadfh! Checking to see what version you’re running so we can do our tests. Thank you!
Hi @mercunium! It’s possible that there was an issue with the Chrome VNC. Our build might’ve had something new that wasn’t handled correctly by VNC which got fixed by the update.