Enabling synchronization causes random disabling of GNOME extensions

[0xF4CED]

This has already been reported on the Chrome Web Store (not by me). I can confirm the issue, but I never got "a warning notification about timeout of syncing".

[nE0sIghT]

What can you say about disabled extensions - are they always random? Are they system extensions?

[0xF4CED]

It's affecting all extensions. Not at the same time, but it seems to be random. Sometimes only one gets disabled, some times three.

[nE0sIghT]

How are you using your GNOME Shell devices - at same time, sequential or both?
Please list your extensions and tell me if some of them are system extensions.

[0xF4CED]

Extensions in use:
alternate-tab@gnome-shell-extensions.gcampax.github.com <--System extension
dash-to-dock@micxgx.gmail.com
dynamic-panel-transparency@rockon999.github.io
user-theme@gnome-shell-extensions.gcampax.github.com <--System extension

I only use one device. So sync is just for kind of backup for me.

[nE0sIghT]

Do you using "sleep mode" with your device?

[0xF4CED]

Yes I am.

[mattsch]

This has been driving me crazy as well. I'm getting it after a simple screen lock/timeout and wakeup as well. My extensions:
refresh-wifi@kgshank.net
caffeine@patapon.info
alternate-tab@gnome-shell-extensions.gcampax.github.com
gravatar@jr.rlabs.io
netspeed@hedayaty.gmail.com
places-menu@gnome-shell-extensions.gcampax.github.com
drive-menu@gnome-shell-extensions.gcampax.github.com
suspend-button@laserb
TopIcons@phocean.net
GPaste@gnome-shell-extensions.gnome.org - System
auto-move-windows@gnome-shell-extensions.gcampax.github.com

[0xF4CED]

@mattsch If you disable syncing, it will work normal for now.

[nE0sIghT]

This is fixed in master.
It would be helpfull if someone will test changes.

[Tamas-Toth-ebola]

Hello!

I'm tryed to install the unpacked version of this extension directly downloaded from GitHub to test it but I get this error message: 'Value 'key' is missing or invalid.'

Could you please navigate me on the most easier install process?

Thanks a lot in advance!

[Tamas-Toth-ebola]

OK! Seems I got it but not everything is clear yet:( I'm testing it.

[Tamas-Toth-ebola]

OK!

After the second try of installing it from source I think was successfully done. Before everything I simply unistalled the 'stock' extension from Chrome. First time I tried to use directly the extension folder as unpacked extension but after a 'key' error message I tried to follow strictly what are in the Wiki. Seemed that the installation was succesfully done as I got back the extension with 8.2 version but installed as enterprise policy.

The problem is that after 3 brute force test I got back the error. I tried to send my device to standby and get back. Between the secont trial I simply made my job then tried again to send into standby. Later I again waked it up. Until this point there was everything OK. And after some minutes I tried to send my device again to standby and after the wak I got the error again. 2-3 of my extensions was disabled again.

Just one information about the environment. My Chrome runs always in the background as I use some of such extensions or web applications.

Sorry to said my test results:(

[nE0sIghT]

@ebola-dc

1. Remove chrome-gnome-shell policy files from /etc/{chromium,opt/chrome}/policies/managed/ and uninstall GNOME Shell integration browser extension installed from Chrome store, but keep distro's chrome-gnome-shell package.
2. Install coreutils, jq, 7z (p7zip) system packages.
3. Download latest chrome-gnome-shell git master sources.
4. From the sources root create build directory and cd to it.
5. Run cmake -DBUILD_CONNECTOR=OFF ../ && make
6. Load extension in browser from build/extension/chrome directory

[Tamas-Toth-ebola]

Hmmm... Thanks!... The 'enterprise policy' installed seemd the same.

Now as I tried to clean everything sem I made a mistake as currently I simply could not use the connector. Extension tells me thazt I have no connector while it's installed. I tried to remove and reinstall but nothing. I cleared everything about htis extension and removed the connector. Then I tried to install the connector and the extension from the store but nothing:( I'm killed it:)

If I check the /ect/opt;chromium... native-messaging-host dir those are empty and could not get it's content again.

As I'm not have more time for now I need to leave the whole process but as I told after I installed it based on the wiki as an enterprise extension the result was the same:(

Sorry for leaving now:( (and for my English too:))

[nE0sIghT]

If I check the /ect/opt;chromium... native-messaging-host dir those are empty and could not get it's content again.

Just reinstall distro's chrome-gnome-shell package.

[Tamas-Toth-ebola]

Hello!

After all I tryed to restore all of the functions before. I had lot of problem with connector itself (neither versiion of distribution or your PPA not made new host files on a computer what ever destructed from this aspect but I copied from anouther sterile device) but at the end I just sucessfully restored everything.

So currently I have 3 devices enablend extension from latest source code as you can see on the following screenshot:

The problem is what I wrote before. With this new and corrected Chrome extension the result is the same. Half hours ago I got simply uninstalled Gnome extensions not just disabled ones. After 2 hours sleep of my device and after the wake up I simply lost almost all of my Gnome extensions.

Sorry to say but I need to absolutly finally report taht the problem is still available sot the issue is not solved yet:(

Thanks for your continous efforts!

[Tamas-Toth-ebola]

Hello!

I know that this is not a strong opinion but maybe could help.

With this 'fresh' version directly from source code the problem is lot rarer. Not solved as I still got 'disabling' and 'uninstalling' twice while I use this last 'beta' but obviously rarer then before.

Hope taht this information could also be helpful.

Thanks again!

[nE0sIghT]

@ebola-dc

Please try this:

1. Clean build directory in source code
2. Edit extension/include/sync.js file: change line const SYNC_QUEUE_TIMEOUT = 3000; to const SYNC_QUEUE_TIMEOUT = 10000;
3. Rebuild extension and reload to your devices

[Tamas-Toth-ebola]

Thank you!

Something such change was my first idea in my other thread. I did it, and installed. Let's see the result in the next days.

Thanks again!

[Tamas-Toth-ebola]

OK!

Just to inform you it seems that the longer timeout and the other changes made good result as in the last 2 weeks I did not have the original problem. Please make longer the timeout value in your official release also.

Thanks for it!

[nE0sIghT]

@ebola-dc I increased timeout to 7 secs.

[ckrzen]

I had to disable the:

Synchronize GNOME Shell extensions list:
If enabled, your GNOME Shell extensions list will be synchronized with your Google account.

option due to having my .config/google-chrome dir copied from my main system to alt workstation for ease of install.

Not sure if this causes problems like one-way sync, but -- just letting you know.

[bulletmark]

I'm on Arch Linux with google-chrome 66.0.3359.181-1 and chrome-gnome-shell 10.1-1 and my extensions frequently get disabled due to this issue, both on my notebook and my PC. Clearly this issue is not fixed.