FreeFileSync Forum

Manually download and install using NON-donation 12.1 installer. I found that the donation edition has gtk3.


How did you determine that? The build should be GTK2-based.

Well, this is what I saw:
1. Downloaded 12.1 donation edition installer when I first saw the update notification. After ...

My installation that auto-updated to the problematic version, is not notifying of an update to pull the GTK2 build. Please, thank you. drak, 07 Mar 2023, 16:44

Manually download and install using NON-donation 12.1 installer. I found that the donation edition has gtk3.

I've reverted FFS back to GTK2 until this issue has been sorted out. Zenju, 24 Feb 2023, 18:09

Is this going to be available for download/installation, or should I download and install 12.0?

This worked for me as expected. No hangs.
However, also got this:
(FreeFileSync_x86_64:246593): Gtk-CRITICAL **: 17:29:57.211: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar


Update: When launched from FreeFileSync.desktop containing the following...
Exec=GDK ...

This is due to the switch to GTK3 and seems to affect KDE only.

Let's test something. Are the hangs reproducible if you start FreeFileSync via command line as
GDK_SYNCHRONIZE=1 FreeFileSync
?

This worked for me as expected. No hangs.
However, also got this:
(FreeFileSync_x86_64:246593): Gtk ...

+1

Operating System: Kubuntu 22.04
KDE Plasma Version: 5.24.7
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-60-generic (64-bit)

libgtk-3.0 version 3.24.33-1ubuntu2

See viewtopic.php?t=5750#p19010 ...

The Linux package is currently always portable, because nobody complained so far. But it seems you're right and the default should be "local installation". I'll be changing that for the next version

@Zenju Thanks.

You may want to add the creation of ~/.FreeFileSync/Logs/ at the first run. Until this directory is created, FFS complains that the dir does not exist when one clicks the default log path in the Options window.

@tohelpanother FFS now seems to default to the installation directory to write files which, at least in Linux, results in the kind of permission issues that you are seeing. I'm running Ubuntu 16.04 too. Here's what I did:

Created directory: mkdir ~/.FreeFileSync
Copied an existing GlobalSettings ...

What about the deprecation and removal of "%AppData%\FreeFileSync\LastSyncs.log"? No complaints, anyone?


I don't know if this question was answered. As of v. 10.5, the fixed "default log path" does not work well. I've described the issue here with screenshots of the errors. The following is ...

System: Kubuntu 16.04

The Options dialog/window shows the 'Default log path' as /opt/FreeFileSync/Logs. Upon hovering over the path "dummy" appears as a hint (not captured in screenshot). FFS10.5-defaultLog-dummy.png

Clicking on the path causes the following error because the directory wasn't ...

+1