1. 30 Jan, 2019 4 commits
    • Piotr Drąg's avatar
      Update POTFILES.in · 620b3f57
      Piotr Drąg authored
    • Christian Kellner's avatar
      thunderbolt: react to security level changes · 05f2c5ef
      Christian Kellner authored
      Listen for security level changes, which in theory should not really
      happen at all with the exception that on hardware where force power
      is not support and boltd has not yet seen the thunderbolt controller
      because it was powered down. Then we should get an initial change
      from 'unknown' to the real level. Handle it in the same way that
      as if boltd was restarted, i.e. the dbus name owner changed
    • Christian Kellner's avatar
      thunderbolt: specific message for unknown security · b9136fd4
      Christian Kellner authored
      If bolt cannot determine the security level, which in theory should
      never happen[1] the standard no-thunderbolt message seems not
      entirely appropriate. Instead show a different message that is more
      tailored to this unusual case.
      [1] The following (unlikely) reasons would invoke such a scenario:
         - new security level not supported by boltd
         - old hardware with not force-power support and the thunderbolt
           controller has not yet been powered up
    • Christian Kellner's avatar
      thunderbolt: plug leak when name owner changes · 31a77ad0
      Christian Kellner authored
      Should not happen very often in the real world, but ever time the
      name owner changed (i.e. boltd was restarted) the name_owner
      variable was leaked.
  2. 29 Jan, 2019 32 commits
  3. 27 Jan, 2019 2 commits
  4. 26 Jan, 2019 1 commit
  5. 24 Jan, 2019 1 commit