Arch Linux User Repository

thenaterhood, thanks for reminding me of that! Worked a treat. Insync forms are hard to follow, I will submit a report at some point though, I have had a hell of a week (in the good and bad sense). As for cimbtti, the service did not exist for me with the newer version, at least I am pretty sure it did not, I will check again for the Insync report, but for now I got to catch up with work. Thank you all, have an amazing rest of your week.

thenaterhood, yes this was working for me prior to 3.9.0 and it's working again after I reverted to the previous version. This is on an Arch system I've been updating for at least 7 years.

Steve

Guys don't forget to enable the service for your user.

systemctl --user --now enable insync

For Schatzs and kynadev was this working for you on the previous version?

I'd also suggest taking a look at the insync forums if you haven't.

Following up from Schatzs / Steve's comment before mine. I get the same output. The systemd services are not created/do not show up when I tried to check their status. I have ran it from KDE on Wayland and (gasp) X11. I have also attempted to run it via CLI and KDE autostart. Other applications are working fine.

I have an idea for what the problem is but I am not sure how to fix it based on this. KDE 6 updated the icon system to match up with GNOME but Insync might not have been changed to be compatible with that, specifically its

I should also note that while I have tried from this AUR, I initially used chaotic-aur's version (same version number though).

Also I really hope we can sort this out soon because I have a few uni assignments relying on it... -_- ... I will ask one of my Profs who has experience with Qt, in case it is Qt related and not GTK or something.

3.9.0 is not working for me, it wont start from my user account. When I started with sudo it started and appeared to be working. I'm using kde wayland and I start insync with kde autostart, not the systemd service. The errors I get in the out.txt file are:

Exception in thread Thread-1:
Traceback (most recent call last):
  File "threading.py", line 980, in _bootstrap_inner
  File "threading.py", line 917, in run
  File "idesklinux/app.py", line 58, in start_core
  File "idesklinux/platapp_impl.py", line 28, in __init__
  File "idesklinux/application_manager.py", line 26, in __init__
  File "idesklinux/application_manager.py", line 82, in __index_apps_for_mimetypes
  File "idesklinux/application_manager.py", line 179, in __record_desktop_files
  File "idesklinux/application_manager.py", line 134, in __canonicalize_mimetype
  File "xdg/Mime.py", line 58, in lookup
  File "xdg/Mime.py", line 72, in __new__
AttributeError: 'NoneType' object has no attribute 'lower'

Steve

Insync 3.9.0 is up and I've switched the package base to Ubuntu 24.04. This seems to work fine on my system and solves the problem several of us have seen with the GUI.

If I run insync from the console there are still errors about posthog but they don't appear to break the UI anymore.

I've been using insync on my Arch install for years now. For the most part it works great. However, I have had an issue with it crashing overnight. I have to upload a lot of video files that are 10gb to 70gb in size and these crashes would slow that process down. I filed at least two bug tickets with InSync itself and we tried some troubleshooting and I provided log files but they could never figure anything out.

Recently though, I made a discovery! I finally figured out that InSync crashes whenever my monitor is turned off (either physically or goes into power saving mode). For some reason the InSync gui does not like this. It's beyond to know why, I'm just a user, not a developer but thought I would put this out here so others who may be experiencing this same issue will know. I'm running KDE 6 with full Wayland by the way.

I've tried to create a shell script (again, very limited knowledge) to restart InSync when it crashes but it doesn't work. If the GUI crashes I have to manually restart it. The backend process will not stay alive or restart via a script. It has to be started via the application icon. Again, I don't know why this is, I'm limited in my skills but reporting here in case others are experiencing the same problems.

Looks like insync 3.9.0 will be out soon. I have a PKGBUILD for it prepped but I notice that insync has removed the Debian links from their release announcement and changed them to "Coming Soon". Hopefully they become available in the next day or so.

Though, makes me wonder if it would be a good idea to switch to the Ubuntu package since that A) seems to solve the problem we're having and B) apparently didn't have whatever problem caused Insync to pull the Debian one.

@aradar: Regarding your js: Failed to load https://app.posthog... error, I'm getting that too now. Unfortunately, I don't have any answer for it and neither do the Insync forums currently.

I'm hesitant to swap the package to a different distro base since it appears we're not the only distro having a crash problem with changing the target directory. It does sound like some folks have had luck uninstalling and reinstalling.