1. 10 Mar, 2021 2 commits
  2. 09 Mar, 2021 2 commits
    • Harald Sitter's avatar
      extra qml strings correctly · 7b82e090
      Harald Sitter authored
      since our l10n scripts run with the assumption that the code is c++ we'd
      not correctly support all javascripty strings that qml can do. notably
      template literals, but also ""+\n"" multi-line strings
      7b82e090
    • Harald Sitter's avatar
      report smartctl failure codes to the user · 3d10fed3
      Harald Sitter authored
      as it turns out there are a number of issues that do not result in an
      actually bad SMART status and would not get reported to the user. to
      keep the code lean we'll simply look at the exit code bits of smartctl
      as they more or less cover all failure scenarios anyway. we'll then
      translate those to pretty strings and expose them on the Device objects
      for consumption in the qml KCM as "instabilities". they are set visually
      apart from actual bad status through different icon and description
      because it's hard to say if an instability is in fact indicative of
      imminent hard-failure or merely a hiccup (e.g. power loss during a disk
      operation).
      
      BUG: 429804
      FIXED-in: 5.22
      3d10fed3
  3. 08 Mar, 2021 3 commits
    • Harald Sitter's avatar
      add some additional samples · dc6903b9
      Harald Sitter authored
      - missing-status failed to retrieve data because ioctl timed out
      - pass-freebsd is a passing check on freebsd (doesn't really differ from
      linux)
      dc6903b9
    • Harald Sitter's avatar
      always try to notify on device appearance · 98e1fddc
      Harald Sitter authored
      since a hotfix that changed when exactly devices appear the
      notifications have been broken as they'd never get emitted when the
      failed property was already true when the deviceAdded signal fired (i.e.
      pretty much always unless the state changed while the system was
      running)
      
      to fix this always try to notify on devices when they appear. if they
      aren't failing we aren't raising notifications anyway
      98e1fddc
    • Harald Sitter's avatar
      add a simulation mode based on the fixture pool · eada1e17
      Harald Sitter authored
      it's very tricky to actively test the UI because you can't just inject
      arbitrary SMART data blobs.
      
      this refactor seeks to remedy that by abstracting away the device
      notification from solid and based on that implement a complete
      simulation mode where both the device notifier (the bit enumerating
      solid) and the ctl (the bit doing kauth + smartctl) are replaced by
      mocking instances at runtime. these instances then use the data in the
      fixture pool instead of actually looking at the active hardware on the
      system. this effectively allows us to check how all the various fixtures
      are actually handled by the actual production code.
      
      for convenience more than anything this is on by default when building
      in debug mode. also for convenience the fixtures are rcc'd into the
      binary instead of looked up from disk (also relocatability is of course
      always a concern)
      
      (this actually reveals a problem with the notification tech: it doesn't
      notify on devices that are failing right out the gate since a fix that
      changed how devices are added to the monitor :()
      eada1e17
  4. 02 Mar, 2021 1 commit
  5. 23 Feb, 2021 1 commit
  6. 11 Feb, 2021 1 commit
  7. 30 Jan, 2021 1 commit
  8. 24 Jan, 2021 2 commits
  9. 21 Jan, 2021 5 commits
  10. 18 Jan, 2021 2 commits
  11. 16 Jan, 2021 3 commits
  12. 15 Jan, 2021 1 commit
  13. 10 Jan, 2021 2 commits
  14. 05 Jan, 2021 1 commit
  15. 21 Dec, 2020 1 commit
  16. 20 Dec, 2020 2 commits
  17. 18 Dec, 2020 1 commit
  18. 17 Dec, 2020 1 commit
  19. 16 Dec, 2020 5 commits
  20. 05 Dec, 2020 2 commits
  21. 01 Dec, 2020 1 commit