Re: gdm3 stalled

Hi, maybe "systemd-analyze blame" shows that a running unit that is expected to start within a few ms actually took several s to initialize. systemd-analyze blame | grep -v "ms " it "gives an impression of the performance of program code, but cannot accurately reflect latency introduced by waiting for hardware and similar events." Regards, Ralf