Project

General

Profile

Feature #12213

Wayland

Added by intrigeri 10 months ago. Updated 2 months ago.

Status:
In Progress
Priority:
Elevated
Assignee:
Category:
-
Target version:
Start date:
03/04/2017
Due date:
% Done:

2%

QA Check:
Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

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

  • Our test suite uses xdotool, that only partly works on Wayland: xdotool set_desktop N still works, but xdotool key Super doesn't, and xdotool search --name only works for apps that are not Wayland native.
  • We run quite a few of GUI apps under gksudo/pkexec/sudo. 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)

Resources:

team: intrigeri (upgrader), bertagaz (the rest), anonym (review)


Subtasks

Bug #12297: Make Tails Server compatible with Wayland Confirmedsegfault

Feature #14585: Investigate Dogtail's long-term viabilityIn Progressanonym

Feature #14717: Adjust doc writing guidelines wrt. screenshots for WaylandConfirmedbertagaz

Feature #14718: Make Tails Upgrader compatible with WaylandConfirmedintrigeri

Feature #14760: Adjust doc for Wayland: starting graphical applications as rootConfirmed


Related issues

Related to Tails - Feature #14522: Make Tails usable for blind users Confirmed 07/06/2014
Related to Tails - Bug #14623: Tor Browser sandbox breakout via X11 testing extensions Confirmed 09/12/2017
Related to Tails - Bug #10339: Are the security risks introduced by Vidalia-like tools worth it? Rejected 10/06/2015
Related to Tails - Bug #14675: GNOME on-screen keyboard is broken without the X11 XTEST extensions Resolved 09/16/2017
Related to Tails - Bug #14712: Display backlight brightness regressions in 3.2~rc1 Resolved 09/24/2017

Associated revisions

Revision 6b55a57a (diff)
Added by intrigeri 2 months ago

Use X.Org in amnesia's GNOME session (refs: #12213).

Since a few months gdm3 defaults to Wayland in Debian testing/sid,
just like upstream. But we're not ready yet.

History

#1 Updated by intrigeri 10 months ago

  • Description updated (diff)

#2 Updated by BitingBird 4 months ago

  • Description updated (diff)

#3 Updated by BitingBird 4 months ago

  • Target version changed from Tails_4.0 to 2019

#4 Updated by intrigeri 3 months ago

#5 Updated by intrigeri 3 months ago

The set of problems we need to solve for Wayland overlap greatly with the set of problems #14522 needs solving too.

#6 Updated by intrigeri 3 months ago

  • Description updated (diff)

#7 Updated by intrigeri 3 months ago

  • Description updated (diff)

#8 Updated by intrigeri 3 months ago

  • Related to Bug #14623: Tor Browser sandbox breakout via X11 testing extensions added

#9 Updated by intrigeri 3 months ago

  • Related to Bug #10339: Are the security risks introduced by Vidalia-like tools worth it? added

#10 Updated by intrigeri 3 months ago

  • Related to Bug #14675: GNOME on-screen keyboard is broken without the X11 XTEST extensions added

#11 Updated by intrigeri 3 months ago

  • Related to Bug #14712: Display backlight brightness regressions in 3.2~rc1 added

#12 Updated by intrigeri 3 months ago

  • Assignee set to bertagaz

(as per roadmap)

#13 Updated by intrigeri 2 months ago

  • Status changed from Confirmed to In Progress

Also available in: Atom PDF