ubuntu-multiseat team mailing list archive
-
ubuntu-multiseat team
-
Mailing list archive
-
Message #00068
Re: [Merge] lp:~ubuntu-multiseat/lightdm/multiseat-logging into lp:lightdm
> FAIL: test-lock-seat-console-kit
[snip]
> Events:
> RUNNER DAEMON-START
> XSERVER-0 START VT=7
> *XSERVER-0 INDICATE-READY
[snip]
> *STOP-DAEMON
> XSERVER-0 TERMINATE SIGNAL=15
> SESSION-X-0 TERMINATE SIGNAL=15
> XSERVER-1 TERMINATE SIGNAL=15
> GREETER-X-1 TERMINATE SIGNAL=15
> RUNNER DAEMON-TERMINATE SIGNAL=9
> ^^^ expected "RUNNER DAEMON-EXIT STATUS=0"
I put this test in a tight infinite loop and let it run for a while on my raring system. I couldn't reproduce this failure. Oddly it looks like it's the test runner that killed lightdm; the process that was killed is the lightdm process itself.
--
https://code.launchpad.net/~ubuntu-multiseat/lightdm/multiseat-logging/+merge/180238
Your team Ubuntu Multiseat is subscribed to branch lp:~ubuntu-multiseat/lightdm/seatunity-call-parent.
References