Insync not working with Ubuntu Jammy (FIXED)

Hey guys… the procedure for install insync is wrong and need to be update… I can’t add repository, because ubuntu complains about key stuffs. apt-key is deprecated. Also I can’t install insync on fresh install of ubuntu 22.04 LTS. could you help me please?

Have you tried installing it from the .deb package? Just download it, use sudo dpkg -i *~/Downloads/name_of_the_file.deb* in terminal and don’t forget to change the source info from xenial to jammy as I described in the comment above yours. Then it works perfectly.

1 Like

Just had to move libstdc++.so.6 again or Insync app window keeps crashing when trying to open it.

OS: Ubuntu 22.04 with all the latest updates
Insync version: v3.7.6.50356

I saw a message indicating that this was fixed with 3.7.5… was that re-introduced with 3.7.6?

Hey @wolfi!

Let me check that out with our engineers!

Thank you @mia!

Not 100% sure if it affects all users. Worked fine an hour later when I tried exactly the same on another laptop that had the exact same software versions. There it was not necessary to remove the library file. Not sure what made the difference.

1 Like

@wolfi Am I understanding that both Ubuntu 22.04 machines 1 and 2 had the same setup wherein you had to do the workaround so Insync runs on them? And on machine 1 you had to delete the file, but on machine 2 you just updated your Insync packages and it ran as expected?

@miamoran Correct. I just re-checked on three machines. On my Desktop and one laptop all is fine. Did not have to manually change anything. Only another laptop is affected. There I had to rename the lib file.

Insync was starting (and I guess syncing fine) on all three machines. Could see the tray icon on all. Only issue was when clicking on the tray icon to open the app the app immediately crashed on the affected laptop.

The affected laptop is a frame.work laptop. Has quite new hardware and most significant difference from a user perspective might be the display with fractal scaling enabled in the operating system. But really not sure how that would play a role. And it really works well after the workaround. Not complaining… more an FYI

Edit: Just went back an tested my theory but that was not it. Having scaling enabled / disabled on an operating system level does not make a difference. I use 200% (no fractional scaling) by default, but also same issue persists at 100%. Really have no idea what the difference is to the other machines. Same OS und updates on all of them.

Gotcha @wolfi! Will send details as soon as I know more from our Linux team. Thanks for the continuous efforts to report these issues to us, we appreciate you!

Hello everybody,

I had the same problem everybody show in the first messages.

Today, post purgate al Insync package and personal folder (apt purge insync and remove ~/.config/Insync), I had upgrade the apt repo file (/etc/apt/sources.list.d/insync.list) to deb [signed-by=/usr/share/keyrings/insync-keyring.gpg] http://apt.insync.io/ubuntu jammy non-free contrib with /usr/share/keyrings/insync-keyring.gpg where I had put the gpg, and I re install with apt install insync and almost everything work fine.

When I had try login in insync with Google account, I had a Google error page. I went back to de insync app, and I try (in the rigth up corner) the alternative login way (copy a URL, enter to this page, allow insync in Google, and copy/paste de Google response token to Insync app), and everything work fine again.

Could be a good idea that Insync software engineers fix login with Google account too.

Looking for something usefull in my logs about the error in Google login, I only find this (in .config/Insync/out.txt):

INFO     2022-06-01 20:09:25,822 [app:start_core:53] core started
INFO     2022-06-01 20:09:25,823 [unix_socket_server:start:93] unix socket server thread start
Opening in existing browser session.
Opening in existing browser session.
js: ResizeObserver loop limit exceeded
INFO     2022-06-01 20:10:42,105 [licensework:_do:89] License received: License{'subscriptions': [BaseLicense.Subscription{'code': 'prime', 'is_recurring': False, 'name': 'Prime', 'capabilities': ['ignore_rules', 'shared', 'network_drives'], 'expiry': None}], 'user_id': '<edited>', 'email': '<edited>', 'can_activate_backup_trial': True}
js: ResizeObserver loop limit exceeded

Looking logs, I found another error, when you try re-login with the alternative way, the installer app change again de defaults files (/usr/share/applications/defaults.list), with the corresponding muted errors:

WARNING:root:While reading /usr/share/applications/defaults.list
Traceback (most recent call last):
  File "idesklinux/application_manager.py", line 53, in __index_default_apps
  File "configparser.py", line 696, in read
  File "configparser.py", line 1091, in _read
configparser.DuplicateOptionError: While reading from '/usr/share/applications/defaults.list' [line 274]: option 'application/rdf+xml' in section 'Default Applications' already exists
WARNING:root:While reading /usr/share/applications/defaults.list
Traceback (most recent call last):
  File "idesklinux/application_manager.py", line 53, in __index_default_apps
  File "configparser.py", line 696, in read
  File "configparser.py", line 1091, in _read
configparser.DuplicateOptionError: While reading from '/usr/share/applications/defaults.list' [line 274]: option 'application/rdf+xml' in section 'Default Applications' already exists
WARNING:root:While reading /usr/share/applications/defaults.list
Traceback (most recent call last):
  File "idesklinux/application_manager.py", line 70, in __index_apps_for_mimetypes
  File "configparser.py", line 696, in read
  File "configparser.py", line 1091, in _read
configparser.DuplicateOptionError: While reading from '/usr/share/applications/defaults.list' [line 274]: option 'application/rdf+xml' in section 'Default Applications' already exists
WARNING:root:While reading /usr/share/applications/defaults.list
Traceback (most recent call last):
  File "idesklinux/application_manager.py", line 70, in __index_apps_for_mimetypes
  File "configparser.py", line 696, in read
  File "configparser.py", line 1091, in _read
configparser.DuplicateOptionError: While reading from '/usr/share/applications/defaults.list' [line 274]: option 'application/rdf+xml' in section 'Default Applications' already exists

Thanks for the support Insync Team! Great work!

Best regards,

1 Like

Nice catch @giorgiogiulio, thank you for the information!

Do you mind emailing your logs.db and out.txt files (both from ~/.config/Insync) to support@insynchq.com? We’d love to check out the errors, specifically the one about the defaults.list.

Please include the link to this Forums post when emailing your logs, for easy reference. :slight_smile:

Dear @mia,

Email sent with your requested files.

Have a great day and week,

Best regards,
Giorgiogiulio

1 Like

Thanks for the tip, this worked for me in Kubuntu 22.04, having upgraded from 22.10. In my config file I needed to change impish to jammy.

I used nano to make the change:
first backup the file in case something goes wrong:
sudo cp /etc/apt/sources.list.d/insync.list /etc/apt/sources.list.d/insync.list.bak
open the file in nano to edit:
sudo nano /etc/apt/sources.list.d/insync.list
change impish (or whichever other version) to jammy
ctrl+O to write file
ctrl+X to exit.
done!

Will this be needed every time we upgrade to a new version of insync via .deb package or is it a one time fix?

1 Like

Hi @wholehalf! :slight_smile: We’re expecting this is a one-time fix given that we’re working on Flatpak to make installation (and updates) much more seamless for our Linux community :slight_smile:

Aehm… sorry, but the fix is not working for me and it is pretty annoying…

Paid for it and have a non working app now after upgraded from Ubuntu 20.04 LTS to 22.04 LTS

The latest Version is installed (insync_3.7.11.50381-jammy_amd64) but I have no GUI and it is not working at all…

Any suggestions how to proceed… as all of the above including a purge and complete new installation are not working

Ok, after a second purge and restart of the system … the new installation was working and all is good…

1 Like

Thank you for your update, @Fezzi!