Thank you for the diagnosis. I wouldn't have thought mtime would be a
problem here but it is. Nix seems to be forcing a MTime of 0 indeed:
nixos% stat /run/current-system/sw/share/icons/hicolor/32x32/apps/firefox.png
File: /run/current-system/sw/share/icons/hicolor/32x32/apps/firefox.png
->
On Wed, Jun 10, 2020 at 2:31 PM Carsten Haitzler wrote:
> yes. possibly. if you change it to 20 sec instead of 10 - does the problem go
> away?
Yes, i had a chance to reboot (kernel update) and so changed the timer
to 20s first. It completed in 12s this time, and there was no error.
> but both
Yes, i can try it increasing the timeout, but since you already found it
can you tell where it is set? :)
Massimo Maiurana
Conrad Knight ha scritto il 11/06/20 alle 18:44:
> On Wed, Jun 10, 2020 at 2:31 PM Carsten Haitzler wrote:
>> yes. possibly. if you change it to 20 sec instead of 10 - does
On Thu, Jun 11, 2020 at 3:59 PM Massimo Maiurana wrote:
> Yes, i can try it increasing the timeout, but since you already found it
> can you tell where it is set? :)
It's in enlightenment-0.24.1/src/bin/e_startup.c, line 33 or thereabouts:
timer = ecore_timer_add(20.0,
