Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
slapos slapos
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Merge requests
  • !394

Merged
Created Sep 05, 2018 by Jérome Perrin@jeromeOwner

Use XORG_LOCK_DIR for Xorg lock files and sockets

  • Overview 11
  • Commits 8
  • Changes 26

The case of firefox 60 described in the commit messages showed that we should not use $TMPDIR instead of /tmp in our patch to isolate $DISPLAYs.

This introduce a new environment variable XORG_LOCK_DIR with clearer semantics.

Softwares relying on this have been updated or removed when not used.

The following softwares where already OK:

  • ERP5 and erp5testnode did not set $TMPDIR and were using /tmp/
  • cloudooo runs in --headless mode
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: fix/SLAPOS_XORG_LOCK_DIR
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7