Not exactly. When you select a text and copy it, the two selections will end up containing the same text, but you can write to either selection without affecing the other by using an API, e.g. a website’s “copy to clipboard” button, or xclip/wl-copy.

Clipboard managers with a history feature are an altogether different layer on top of the standard selections. Plasma’s clipboard manager only cares about the clipboard selection, and even then, there are exceptions (e.g. copying a password for KeepassXC doesn’t save it in the history).

Yes. X11 replaced X10’s obsolete cut buffers (which can be modified by any process) with state-of-the-art selections. There are three selections in X11: a primary, a secondary, and a clipboard.

In modern desktops, the primary selection is overwritten every time you select some text (including in the terminal), which makes its content very ephemeral. You can paste it with the middle mouse button.

The secondary selection is generally not used, but it’s present in the specification, and you can use xclip -selection secondary to access it. Wayland doesn’t seem to have a secondary selection.

The clipboard selection is what most people understand to be THE clipboard. You have to write to it explicitly (through a keyboard shortcut, API, or CLI tool), and its content persists until it is overwritten, explicitly cleared, or the X server is killed. While the primary and secondary can only contain text, the clipboard can contain many kinds of data.

Gee, X11! How come your mom lets you have THREE clipboards?

They’re putting the information on the side? What’s next, 1-to-5-star rating system? Fugly yellow background color? Buffering?

Charlie says my music is better!

FIRST!

apt download yuzu will download the deb file (but not dependencies) of the latest release to the PWD. But if you want the latest dev version, you’ll have to build from source.

X is still the only choice for certain roles. Wayland is missing absolute window positioning (required for certain multi-window apps), color management, and drawing tablet support is spotty. Some apps will never be ported to Wayland.

X is bloated, old, obsolete, impossible to maintain, and immortal.

And between the two of them, a thin line of evil-mode users who claim allegiance to both sides.

Mullvad was actually “raided” by the Swedish police. They left with fuck all. It was great publicity for Mullvad.

But don’t whip the horse for not immediately finding the water on its own.

You could at least practice what you preacH.

Bash says that the fewer command can’t be found…

Download the official iso from Microsoft, install it, then run MAS on it if you really want to activate it.

How did the saying go? [NOUN_1] don’t [VERB] [NOUN_2], it’s people that [VERB] [NOUN_2].

Nvidia is unfortunately kind of a dick about Linux support. The open-source Nouveau driver is making great strides, but I don’t think it’ll be ready for general adoption for several years. The proprietary driver (the nvidia-dkms package) is far more usable, but there are always some issues.

If you want to focus on gaming, you should consider Nobara or Garuda Linux.

Garuda is based on Arch, and its main selling point is that whatever you need for gaming (Wine, Steam, DXVK, VKD3D) is either installed out of the box, or installed and configured in one click. Since Arch, and by extension, Garuda, is a rolling release, it gets very frequent updates that are always cutting edge, but it might require some maintenance at times.

Nobara is maintained by Glorious Eggroll, who also maintains custom Wine and Proton releases and has made massive contributions to Linux gaming. It’s based on Fedora, which is a point-release distribution - it receives security updates continuously, and feature updates every few years, so it should require little maintenance.

I didn’t realize you were new, it sounded like an issue anyone could have. Gaming on Linux is definitely not a perfect experience. Please don’t be afraid to ask around in the various linux_gaming communities, there are always people who are willing to help.

What’s your computer like? What brand and model is your GPU? What distribution? If the GPU is Nvidia, do you know if you have the open-source Nouveau or the proprietary Nvidia driver?

A bit of a glossary:

• Wine: a compatibility layer that allows Windows executables to run on Linux systems by translating Windows system calls to Linux calls.
• Proton: a derivative of Wine maintained by Valve, optimized for gaming on Steam.
• Wineprefix or prefix: a mock-up of a Windows filesystem. The application running inside Wine sees this as the C: drive. The default wineprefix is located in ~/.wine. The system’s root directory is mounted as the Z: drive.
• Lutris, Bottles, Heroic: graphical front-ends to manage many aspects of your Wine applications.

I don’t personally use bottles, it hates running inside Hyprland.

If you want games straight from GOG, try the Heroic launcher on Flathub. It has direct GOG integration and Flatpak’s permission system. You can then use Flatseal (also from Flathub) to adjust its security - particularly if you want to install games outside $HOME, which needs an extra permission.

You can also download the offline installer from GOG and just run Wine from the terminal.

I can’t speak for VMware’s technology, but the company just got bought by Broadcom, so treat them with Red Hat-like suspicion.

The official flatpak release of Bottles offers sandboxing. It comes from Flatpak itself, so other similar apps (like Heroic) might support it too.

Another option is to chroot before running Wine (so Z: doesn’t point at the real system root), or su into another user (Wine inherits the user’s privileges). It’s also possible to run Wine inside a container, but GUI support is questionable.

Ultimately, running an untrusted executable is always a risk, regardless of the OS. If you want near-absolute safety, you’ll want a different machine - either a VM or a heavily firewalled physical machine.