On Sun, 8 Jul 2018 10:37:10 +1200 Ben Caradoc-Davies <b...@transient.nz> wrote:
> I would use ltrace to see where it is hanging: > > ltrace -tt -n4 -S gimp > > You will need to install ltrace and likely the debug packages for > wherever it is hanging. ltrace -tt -n4 -S /usr/bin/gimp outputs a lot lines and the last one is like: 10:01:04.820439 SYS_futex(0x7f8d0648a9d0, 0, 6356, 0 strace -f /usr/bin/gimp also outputs a lot lines and the last ones are like: [pid 6789] futex(0x7f1d25b6b9d0, FUTEX_WAIT, 6791, NULL <unfinished ...> [pid 6791] futex(0x7f1d3d401968, FUTEX_WAIT_PRIVATE, 2, NULL 'ps aux' tells me that one of the pid is gimp, and the other one is not existing. So it could be that Gimp is just waiting for a dead process. I don't know how to identify this dead process. I looked for a way to force Gimp to run on a single thread and Google pointed me to this URL: https://superuser.com/questions/692138/how-to-force-a-process-to-run-on-a-single-thread-only-with-numactl So I tried: numactl --physcpubind=+1 /usr/bin/gimp and Gimp works :-) Of course I still don't know what the root cause of the problem is... Many many thanks for your help and suggestions :-) -- Thierry
