-
-
Notifications
You must be signed in to change notification settings - Fork 29
Description
Syncthing and Synctrayzor were working fine for me until now. Today I've finally given in and agreed to upgrade to 2.1.0.
After upgrade, it was no longer running, so I started SyncTrayzor again. And was greeted with a warning that there are mixed v1 and v2 files that cause crashes. And sure enough, now synctrayzor crashes when I start it. But that did not happen before.
Warn users if a mixed v1/v2 install is detected. These installs contain files from SyncTrayzor v1, which are incompatible with SyncTrayzor v2 and cause frequent crashes.
Release 2.1.0 introduced the warning, according to the release notes.
- But did the new version perhaps also introduce the issue?
After running into that crash, the next start of SyncTrayzor complained about an already-running syncthing. Which was true, as my other devices reported the PC as online. I did not find it in Task Manager though, nor in the tray bar. So I killed it by using the option in SyncTrayzor's menu to kill all syncthing processes.
After that, everything is now working again. Except that when I close SyncTrayzor and open it again, I get that popup about the v1/v2 mixing. This can get annyoing.
I would appreciate some more detailed guidance in there, how to perform this cleanup in the least-disrupting way. I'm hoping I can reuse the syncthing data without setting up everything fresh. But I don't think I am using the portable version, and I don't know where the data folder is.
- How do I keep user data if I am not using the portable version?
Finally, I feel like the popup might not even be so relevant in my case, as it is now no longer crashing again. The only crash was the first time I started synctrayzor after upgrading.
- How can I tell whether there really is anything broken that needs my attention?
I'm attaching the logfile. While it spans the whole times from the upgrade to now, I doubt it contains much useful information though. The stack trace doesn't really say much.
Thank you for maintaining!