On Fri, Jun 5, 2020 at 12:34 PM Carsten Haitzler <ras...@rasterman.com> wrote: > well putting printfs in the code to begin getting logs.
Ok, i found where the timer is set and cleared, added a few debug lines, with time stamps. It looks like everything goes as expected, it just takes too long: .... ESTART: 4.54442 [0.00038] - E_Comp_Canvas Keys Grab Done ESTART: 4.54444 [0.00002] - Run Startup Apps E: timer started Sat Jun 6 20:15:30 2020 ESTART: 4.54457 [0.00013] - Run Startup Apps Done ESTART: 4.54458 [0.00001] - E_Comp Thaw .... ESTART: 17.34377 [0.15196] - SLEEP RRR: CB screen change... RRR: CB output change... RRR: CB screen change... RRR: CB output change... E: efreet didn't notify about cache update E: sent profile set req to 0xe00023 [standard] E: timer cleared Sat Jun 6 20:15:44 2020 RETRY backlight set as 0.05 != 0.41 (expected) try=0 RRR: CB screen change... So it took 14s to get to that point, and the error is triggered a little before that (but still longer than the 10s set for the timer). Should the timer be set for longer? Or would that just be hiding the fact that something is taking too long? (The full output from E while starting is at https://pastebin.com/DnpN5DQ7 in case anyone wants it.) Thanks, -Conrad. _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
