Reason why Wayland isn't enabled by default?

I enabled Wayland manually in /etc/gdm3/custom.conf and I’ve seen no issues. Screen tearing went away which is a plus. So is there a logical reason why Wayland isn’t enabled by default?

Not asking for ranting purposes, I’m just curious. I thought Pop_OS! is currently incompatible with Wayland.

Chat

@iwasgodonce
link
English
11•1 year ago
Screen capture doesn’t work in some apps still I’m pretty sure is the main reason. Discord is one app it doesn’t work in if I remember correctly.
- @[email protected]OP
  link
  fedilink
  English
  4•1 year ago
  Thanks a lot for telling me!

Pop!_OS (Linux)

[email protected]

Create a post

You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]

Pop!_OS is an operating system developed by System76 for STEM and creative professionals who use their computer as a tool to discover and create. Unleash your potential on secure, reliable open source software. Based on your exceptional curiosity, we sense you have a lot of it.

Unleash your potential

Whether this is your first experience with Linux, or your latest adventure, all are welcome to discuss and ask questions about Pop!_OS and COSMIC. Keep the discussions friendly though, and remember to assume good intentions whenever you reply. We’re all here because we have a shared love for Linux and open source software.

Support us by buying System76 hardware for you or your company! Or by donating on the Pop!_OS website through the “Support Pop” button. Pop!_OS and COSMIC are fully funded by System76 hardware sales. All systems are assembled in the USA. With your support, we’ll work to push the Linux desktop forward with COSMIC.

Links

Guides

Hardware

Recommended

Community Rules

Follow the Code of Conduct

All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct

Be helpful

Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like “RTM” or links to LMGTFY. Linking to direct sources that answer the asker’s question is fine, but it’s advised to provide some explanation as to how you got to that source.

Critique should be constructive

We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic “It’s bad” or other simple negative comments don’t help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.

This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.

Don’t post malicious “advice”

It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.

Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn’t serious, but a new user might not.

No personal attacks

Posts making a personal attack on any user will not be tolerated.

No hate speech

Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.

11 users / day
57 users / week
151 users / month
761 users / 6 months
5.19K subscribers
345 Posts
1.58K Comments
Modlog