Skip to content

VS Code should default to Wayland when possible #207033

Open
@justin13888

Description

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.87.0
  • OS Version: Fedora 39 x86_64

Steps to Reproduce:

Run code from terminal or open VS Code using code.desktop packaged with VS Code for Fedora repositories.

Problem:

It appears VS Code always defaults to XWayland on running on Linux Wayland desktops (at least when I tried on Fedora Workstation 39 and Ubuntu 22.04 LTS). Wayland has been the default display server on most GNU/Linux distros for the past few years, even for NVIDIA drivers. While forcing VS Code to start with Wayland with command-line arguments for example is possible, it is an extra step and the most convenient method to always start VS Code with Wayland is to append --enable-features=UseOzonePlatform --ozone-platform=wayland to your .desktop files or alias code with those arguments.

However, updating VS Code for example on Fedora may overwrite any changes to the .desktop file. There should be a way for VS Code to default to Wayland without manual user invention when Wayland is detected. Open to thoughts and comments on this suggestion and its feasibility!

Note: There may be similar issues or duplicate but I cannot find them

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

feature-requestRequest for new features or functionalitylinuxIssues with VS Code on LinuxwaylandIssue related to wayland display server

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions