ubuntu-multiseat team mailing list archive

[Robert Ancell <robert.ancell@xxxxxxxxxxxxx>]

** Changed in: lightdm
       Status: New => Triaged

** Changed in: lightdm
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Multiseat, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1364350

Title:
  Support wildcard substitution in seat property values

Status in Light Display Manager:
  Triaged

Bug description:
  Now that LightDM now supports globbing in seat config sections, it
  would be nice if it supports wildcard substitution in seat property
  values, too. For example, this 2-seat configuration:

  [Seat:seat0]
  xserver-config=xorg.conf.seat0

  [Seat:seat1]
  xserver-config=xorg.conf.seat1

  could be condensed to this one:

  [Seat:seat*]
  xserver-config=xorg.conf.%s

  where the wildcard %s should be replaced with corresponding seat name.

  Some questions asked by Robert Ancell about this feature:

  - Does the wildcard work in all config values or just command?

  Yes. The most common use case I can see is seat-name substitution in
  properties like xserver-command, xserver-config, xserver-layout, etc.

  - Could this wildcard be a valid value in other cases and will those values now have to be escaped (potentially breaking existing config)? For this reason, we should use a bigger token, e.g. "%(seat-name)" which is both more self-explanatory and less likely to collide with something else.
  - Are there other values we should give?

  Good point. Adoption of bigger tokens like %(seat-name) opens the
  possibility of supporting wildcards for other seat properties, e.g.
  %(autologin-user), although I can't see any practical use of this.

  - What are the escape rules if you need a literal "%s"?

  We could use a doubled %% as a escape rule for literal "%".

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1364350/+subscriptions