Arch Linux User Repository

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.

For anyone else also struggling with this, downgrading to the latest PKGBUILD with version 3.8.6 resolved the problem for me. I found this solution in the following two posts in the insync forum: [1] https://forums.insynchq.com/t/insync-3-8-7-50507-1-wont-start-on-arch-aur-fixed-via-version-update/19580/5 [2] https://forums.insynchq.com/t/insync-3-8-7-does-not-start-on-opensuse-tumbleweed-with-users-workaround/19595/8

I guess I will stick to this version until the problem is resolved according to the official forums :)

By "Please change the source to Ububtu 2024", I think that @petergdd means to change _dist= from "bookworm" to "noble" in the PKGBUILD. I can replicate the experience of inync crashing when trying to change the target directory with "bookworm" specified.

Please change the source to Ububtu 2024, then the app will no longer crash when you try to change the target directory.

I haven't personally experienced any problems today. Your error sounds like something non package related, maybe some telemetry endpoint insync wants to talk to is/was unavailable. Just speculation on my part though.

If you continue to have a problem you may want to take a look on the insync forums. I do see a post from a little over a week ago that sounds like what you're seeing, but no resolution.

For me, the package suddenly stopped working (the GUI opens super slowly and is not responsive when it finally opens, and it is also not doing any synchronization anymore in this state).

If I run the client with insync start --no-daemon I get a bunch of js: Failed to load https://app.posthog.com/decide/?v=<removed>&ip=<removed>&_=<removed>&ver=1.26.0: ... messages but nothing really helpful.

So far tried to solve this by switching the PKGBUILD to the package for debian trixie, but this didn't help.

Is this just on my end, or is it also broken for others at the moment?

Ayyyy that's good news! I've updated the package. Thanks for opening a forum thread.

With the new release of 3.8.7.50507, I can confirm that the issue is solved for me. I only updated the version and checksum in the PKGBUILD, so not sure if the patches affect anything.