Comment 101 for bug 1439288

(In reply to André Miranda from comment #98)
> @Ali, so your patch probably doesn't fix this either.
I reverted back to thunar 1.6.6 with "improved patch" and have *no* issues. This is because I moved sections inside nested if blocks to avoid "nailing" dbus.

Let's investigate here:

thunar-gio-extensions.c -> both patches same
thunar-size-label.c -> both patches same
thunar-transfer-job.c -> both patches differ (of course)

fkt "thunar_transfer_job_execute"

Quick investigation triggering object before the for loop. This may cause the same amout of "nailing" traffic as the previous code in "thunar_transfer_job_veryify_destination". So basicly a new "high amount" of triggering has been introduced in a new function, while removed in the previous one.

I will comment that particular part out of the code and re-compile thunar and report back as I type now.

As I thought. I commented the object referencing block before the for loop and re-compiled. Problem gone.