Linux

48314 readers

83 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

117

The cost of maintaining Xorg (mastodon.social)

submitted 1 year ago by ugjka to c/[email protected]

42 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago) (1 children)

I really wanted Wayland to work for me. I just bought a new ASUS laptop (and ASUS has a great Linux compatibility track record, mind you!), 7th Gen Ryzen+Radeon, all AMD. I figured, let's use Wayland on this one.

I installed KDE Neon, updated the kernel (some stuff is broken on the LTS kernel, no big deal, easy fix), switched to the Wayland session, everything was fine...until I opened any chromium-based app. Crashed kwin, killed the session completely, it recovered, but in a new session. Switched to X11, everything works. Maybe if I grabbed a newer mesa from a PPA it would work, but:

Crashing the window manager killing the session is awful and doesn't happen in X11
Chromium shouldn't crash the compositor at all
Even if it's AMD's new graphics drivers being buggy, that still shouldn't kill the session!

And I know, technically KDE could (and afaik, is) implement session management so that doesn't happen. But to my knowledge, literally 0 WMs/DEs can recover the session after a compositor crash currently, and that's a big deal.