Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 929
    • Issues 929
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 18
    • Merge requests 18
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #12213

Closed
Open
Created Feb 06, 2017 by intrigeri@intrigeriMaintainer7 of 11 tasks completed7/11 tasks

Wayland

Originally created by @intrigeri on #12213 (Redmine)

Run the GNOME session on Wayland instead of X.Org, and adjust whatever is needed, such as:

  • We run quite a few of GUI apps under gksudo/pkexec/sudo, such as the Unsafe Browser. This can be worked around for apps that run via XWayland (i.e. not Wayland-native apps) with hacks like xhost +si:localuser:root, which might be acceptable as a temporary transition measure, as long as there’s a clear plan to fix that at some point (since it defeats some of the benefits of switching to Wayland in the first place, such as security improvement, a11y / IBus / on-screen keyboard support in all graphical apps)
  • Consider dropping the 89cc641f39a5414e763112f698739bb2351da7d8 hack: there are rumors that GDM’s session does not linger after login on Wayland.

Last time we discussed our strategy, we decided this:

  • Focus on real blockers
  • Workarounds are OK, like XWayland
  • OTOH we currently have several bugs that would remain if we use XWayland, like lack of accessibility support, on-screen-keyboard support. So if we have to do significant work we should bundle in making it Wayland native & fixing these issues as well.
  • Tor Launcher MUST run as a native Wayland app (contractual obligation to Sponsor8)

Resources:

  • Debian bugs tagged wayland

Subtasks

Real blockers

  • #18723 (closed)
  • #15142 (whether we have #17803 or not)

Blockers that can be implemented incrementally

i.e. without waiting for the "switch to Wayland" flag day

  • #15828 (closed)
  • #14585 (closed)
  • #14717 (closed)
  • #18007 (closed)
  • #18120 (closed)
  • #8573 (the only X.Org specific bits remaining in our test suite are about Pidgin)

Optional

  • #8309 (closed)
  • #18020: probably ok with XWayland, although we'll get all the bugs/security issues we have in Xorg (no a11y etc, but in particular #15635)
  • #14718: XWayland is OK for now, until we switch to a non-NIH upgrader; splitting out a backend would allow integrating the UI into a potential Tails Settings application.

Other subtasks

  • #14760
  • fix config/chroot_local-includes/usr/lib/systemd/user/org.gnome.Shell@x11.service.d/: probably it will have a different name on Wayland

Related issues

  • Related to #14522
  • Related to #14623
  • Related to #10339 (closed)
  • Related to #14675 (closed)
  • Related to #14712 (closed)
  • Related to #15725
  • Related to #16305 (closed)
  • Related to #7502
  • Related to #9051 (closed)
  • Related to #11579
  • Blocks #15635
  • Related to #16795
  • Related to #5785
  • Related to #11755 (closed)
Edited May 12, 2022 by boyska
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking