Skip to content
Snippets Groups Projects
  1. Oct 28, 2022
  2. Jun 21, 2022
  3. Mar 31, 2022
  4. Jan 27, 2022
  5. Sep 01, 2021
  6. Aug 06, 2021
  7. Aug 03, 2021
  8. Jul 20, 2021
    • Ludovico de Nittis's avatar
      Adjust LD_PRELOAD and LD_AUDIT to prevent ELF warnings · e7a5f274
      Ludovico de Nittis authored and Simon McVittie's avatar Simon McVittie committed
      
      When a game is launched with the Steam Overlay feature enabled (it's on
      by default), we end up with an LD_PRELOAD that contains
      `gameoverlayrenderer.so` two times, one for 32-bit and the other for
      64-bit processes.
      
      However this leads to a warning that is harmless but scary for users and
      developers unaware of that:
      `ERROR: ld.so: object
      '/home/me/.local/share/steam/ubuntu12_64/gameoverlayrenderer.so' from
      LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.`
      
      And every 64-bit process prints something similar about the ELFCLASS32.
      
      By creating a temporary directory and using the dynamic linker token
      expansion `$PLATFORM` we can let a process preload only the
      `gameoverlayrenderer.so` for the right ABI.
      
      Signed-off-by: default avatarLudovico de Nittis <ludovico.denittis@collabora.com>
      e7a5f274
  9. May 20, 2021
  10. May 12, 2021
  11. Feb 26, 2021
    • Simon McVittie's avatar
      pressure-vessel: Put apt-style severity prefixes on messages · dbf21961
      Simon McVittie authored
      
      These indicate which lines are harmless and which lines are really bad,
      without taking up too much space.
      
      The mapping from GLib log level to message is not 100% obvious, because
      G_LOG_LEVEL_ERROR is "worse than" an error. We diagnose "can't happen"
      situations (assertion failures, etc.) as "Internal error". Ideally,
      users should never see these: they indicate a bug.
      
      For situations that will cause pressure-vessel to exit with an error,
      introduce a new log level flag PV_LOG_LEVEL_FAILURE and map it to the
      apt-style "E:" prefix. pv_log_failure() is a convenience macro to log
      at level PV_LOG_LEVEL_FAILURE. Conceptually this is a fatal error, but
      it's a fatal error prompted by something external to pressure-vessel,
      for which we want pressure-vessel to clean up "nicely" and exit
      gracefully, even though it's going to fail - so we can't use g_error()
      for this.
      
      In the parts of main() that involve parsing command-line arguments,
      add usage_error() as syntactic sugar for pv_log_failure(). I might
      eventually turn these into G_OPTION_ERROR_FAILED as we factor out
      more of main() into helper functions, but for now they're handled
      separately.
      
      For less-severe log levels, use single-letter prefixes similar to apt's.
      
      Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
      dbf21961
  12. Feb 25, 2021
  13. Feb 23, 2021
  14. Jan 13, 2021
  15. Jan 05, 2021
  16. Dec 10, 2020
  17. Dec 03, 2020
  18. Nov 17, 2020
  19. Oct 22, 2020
    • Simon McVittie's avatar
      pressure-vessel: Disable GIO modules differently · 92b1c2b6
      Simon McVittie authored
      
      Now that GIO_MODULE_DIR has been backported into scout's GLib, we can
      disable GIO modules completely, instead of loading them but then not
      using them. This avoids some misleading warnings (#32).
      
      This will not be completely effective on non-Debian systems until we
      also patch scout's GLib to make GIO_MODULE_DIR take precedence over
      the hard-coded legacy search path /usr/lib/gio/modules.
      
      The unit test for this is still in tests/pressure-vessel/utils.c
      for now.
      
      Signed-off-by: default avatarSimon McVittie <smcv@collabora.com>
      92b1c2b6
  20. Sep 29, 2020
  21. Sep 28, 2020
  22. Sep 25, 2020
  23. Sep 09, 2020
  24. Sep 02, 2020
    • Ludovico de Nittis's avatar
      Initial support for custom graphics provider path and Flatpak · d7ad67a2
      Ludovico de Nittis authored
      
      pressure-vessel had a few hard coded assumptions about the host system
      and where to look at for the graphics provider.
      
      For example it was assumed that the root was the same host system used
      by both pressure-vessel current environment (where pressure-vessel-wrap
      runs) and also later on by `bwrap`.
      
      But when we run pressure-vessel in a Flatpak container, the final
      `bwrap` command is expected to be executed against the real host system
      (mounted in `/run/host`, in Flatpak).
      
      Also when we are in a Flatpak container we might want to pick the
      graphics stack from the host system (`/run/host`), from the Flatpak
      container itself or it could even be a completely separate one.
      (T22373, T22371)
      
      Signed-off-by: default avatarLudovico de Nittis <ludovico.denittis@collabora.com>
      d7ad67a2
    • Ludovico de Nittis's avatar
      utils: Add pv_file_test_in_sysroot · cbd9e214
      Ludovico de Nittis authored
      
      With this new function it will be possible to test the existence or
      properties of a given filename under a specific sysroot.
      
      Signed-off-by: default avatarLudovico de Nittis <ludovico.denittis@collabora.com>
      cbd9e214
  25. Aug 19, 2020
  26. Aug 18, 2020
  27. Aug 04, 2020
  28. Aug 03, 2020
  29. Jul 29, 2020
  30. Jul 21, 2020
  31. Feb 26, 2020
Loading