lp:~robert-ancell/lightdm/multiseat-logging-whitespace

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

1763. By Robert Ancell on 2013-08-13

Fix whitespace

1762. By Richard Hansen on 2013-08-04

log the values of the XDG_SEAT and XDG_VTNR variables

This makes it easier to debug multiseat setups.

1761. By Richard Hansen on 2013-08-04

delay setting Session pid to 0 (for logging)

The Session pid is currently used in Session log messages. Delay
setting it to 0 so that more log messages have a meaningful prefix (to
make it possible to correlate them with other log messages).

1760. By Richard Hansen on 2013-08-04

add session PID to Session (including Greeter) log messages

This makes it easier to debug multiseat setups.

1759. By Richard Hansen on 2013-08-04

have Session implement the Logger interface

This is a step toward logging the session PID in each Session
log message, which will make it easier to debug multiseat setups.

The PID is set to 0 when the Session process terminates, so it is not
possible to follow a Session's complete lifetime in the logs. But
it's better than nothing.

A future commit could easily change this to log some other identifier,
such as the associated Display or Seat name, or the PID before the
process terminated.

1758. By Richard Hansen on 2013-08-04

add display server name to DisplayServer log messages

This makes it easier to debug multiseat setups.

1757. By Richard Hansen on 2013-08-04

have DisplayServer implement the Logger interface

This is a step toward logging the display server name in each
DisplayServer log message, which will make it easier to debug
multiseat setups.

1756. By Richard Hansen on 2013-08-04

add seat name to Seat log messages

This makes it easier to debug multiseat setups.

1755. By Richard Hansen on 2013-08-04

have Seat implement the Logger interface

This is a step toward logging the seat name in each Seat log message,
which will make it easier to debug multiseat setups.

1754. By Richard Hansen on 2013-08-04

make the Seat available everywhere a log message is generated

This will make it possible to prefix the log messages with the Seat's
name.