Connect with us

How To

Linux finally does HDR gaming right — here’s the exact setup

Published

on

Linux HDR gaming

HDR gaming on Linux: no longer a pipe dream

For years, High Dynamic Range gaming on Linux was a punchline. You could buy a fancy HDR monitor, boot up a title on Steam, and get… washed-out colors, crushed blacks, or a desktop that looked like someone smeared Vaseline on the screen. The promise was always there. The delivery? Barely.

That’s changed. In 2026, Linux can do HDR gaming properly — not through hacks, not through third-party patches that break every other update, but through genuine, upstream support. The combination of KDE Plasma 6 and Gamescope has turned a frustrating mess into something that just works. Here’s exactly what you need and how to set it up.

What changed? The software stack that finally works

The turning point was Wayland. The display protocol that Linux enthusiasts have been championing for years finally got serious HDR support baked in. But Wayland alone isn’t enough — you need a compositor that knows what to do with it. That’s where KDE Plasma 6 comes in.

KDE’s developers put serious work into color management and HDR output. The result is a desktop environment that can switch between SDR and HDR modes without you needing to restart X11 or fiddle with config files. It just detects your monitor’s capabilities and asks what you want to do.

Then there’s Gamescope. This is Valve’s micro-compositor, originally built for the Steam Deck. It wraps your game in its own little display environment, handling HDR metadata, color conversion, and refresh rate locking. When you launch a game through Gamescope, it gets a clean HDR pipeline — no fighting with the rest of the desktop.

Together, these two pieces form the backbone of modern Linux HDR gaming. No custom kernels. No patched drivers. Just a distro that ships recent software.

Hardware you’ll actually need

Before you dive in, check your gear. HDR on Linux makes specific demands.

GPU: AMD leads, Intel works, Nvidia is complicated

An AMD Radeon RX 6000 or RX 7000 series card is the smoothest path. AMD’s open-source drivers have excellent HDR support under Wayland. Intel’s Arc GPUs also work well if you’re on a recent kernel (6.8 or later).

Nvidia? It’s getting better. The proprietary driver (version 555 and above) supports Wayland HDR, but expect more edge cases — flickering in some full-screen games, weird behavior with multiple monitors. If you have an Nvidia card, make sure you’re on the latest driver and using a distro that ships it cleanly.

Monitor: look for DisplayHDR 600 or higher

Not all HDR monitors are created equal. A DisplayHDR 400 panel will technically work, but the experience is underwhelming — low peak brightness, poor local dimming. Aim for DisplayHDR 600 or better. OLED panels are ideal because each pixel controls its own brightness, giving you true blacks and vibrant highlights.

Your monitor also needs to support HDR10. That’s the standard Linux uses. Dolby Vision and HDR10+ are not supported on the desktop yet.

Cable: DisplayPort 1.4 or HDMI 2.1

This is the part people forget. A cheap HDMI 1.4 cable will bottleneck your HDR signal. Use DisplayPort 1.4 or HDMI 2.1 to get the full 10-bit color depth and high refresh rates. If your monitor and GPU support DSC (Display Stream Compression), even better — you can push 4K at 144Hz with HDR enabled.

Step-by-step: setting up HDR gaming on Linux

Let’s get practical. These steps assume you’re on a distro that packages recent software — Fedora 40+, Arch Linux, or openSUSE Tumbleweed. Ubuntu 24.04 LTS works too, but you’ll need the KDE Plasma 6 backports PPA.

1. Install KDE Plasma 6

If you’re not already on Plasma 6, switch to it. On Fedora: sudo dnf groupinstall "KDE Plasma Workspaces". On Arch: sudo pacman -S plasma-meta. Make sure you log into a Wayland session, not X11 — you’ll see the option at the login screen.

2. Enable HDR in display settings

Open System Settings → Display and Monitor. You should see an “HDR” toggle if your monitor supports it. Turn it on. The screen will go dark for a second, then come back with noticeably richer colors. You can also set the SDR brightness slider here — this controls how bright standard content (like your web browser) appears while HDR is active.

3. Install Gamescope

Gamescope is available in most distro repos. On Fedora: sudo dnf install gamescope. On Arch: sudo pacman -S gamescope. On Ubuntu: sudo apt install gamescope (if the version is too old, grab it from the Kisak Mesa PPA).

4. Launch a game with HDR

Open a terminal and run something like this:

gamescope -W 2560 -H 1440 -r 144 --hdr-enabled -- %command%

Replace the resolution and refresh rate with your monitor’s specs. The --hdr-enabled flag is the magic part — it tells Gamescope to pass HDR metadata to the game.

For Steam games, you can set this as a launch option. Right-click the game in your library → Properties → Launch Options, paste the command above. For non-Steam games, wrap the executable the same way.

5. Check the game’s HDR settings

Not every game automatically switches to HDR mode. You may need to go into the in-game video settings and enable HDR manually. Titles built on modern engines — Unreal Engine 5, Unity HDRP, or Vulkan-native renderers — usually detect the HDR signal and prompt you. Older games with HDR patches (like Resident Evil Village or Cyberpunk 2077) require you to toggle it on.

Which games actually work?

The list is growing fast. Here are the titles I’ve tested that work without major issues:

  • Cyberpunk 2077 — HDR looks stunning on an OLED. Bright neon, deep shadows. Needs in-game HDR enabled.
  • Horizon Forbidden West — Native Linux port. HDR works out of the box with Gamescope.
  • Baldur’s Gate 3 — The UI can be a bit bright in HDR, but the game world benefits hugely from the wider color range.
  • Forza Horizon 5 — Runs via Proton. HDR needs the --hdr-enabled flag and in-game toggle.
  • Doom Eternal — id Tech 7 handles HDR beautifully. Smooth, responsive, and vibrant.

Games that use DirectX 12 with HDR can be trickier. Some need Proton Experimental or GE-Proton to get the HDR path working. Check ProtonDB before you buy.

Troubleshooting common HDR problems on Linux

HDR on Linux isn’t perfect yet. Here’s what you might run into and how to fix it.

Screen goes black when enabling HDR — Your cable might not support the bandwidth. Try lowering the refresh rate to 60Hz temporarily. If that fixes it, upgrade to a certified HDMI 2.1 or DP 1.4 cable.

Colors look washed out in desktop mode — This is usually a color profile issue. Go to System Settings → Color and make sure you have an ICC profile loaded for your monitor. Without it, the desktop can’t map SDR content correctly into the HDR container.

Game crashes on launch with Gamescope — Try adding --mangoapp to the Gamescope command. This enables the performance overlay and sometimes stabilizes the compositor. If that doesn’t work, run the game without Gamescope first to confirm it launches at all.

HDR toggle is grayed out in display settings — Your GPU driver might not be reporting HDR support. Check that you’re on a Wayland session (run echo $XDG_SESSION_TYPE in a terminal — it should say wayland). Also confirm your monitor is connected via a port that supports HDR — some monitors only enable HDR on specific HDMI inputs.

The verdict: is Linux HDR gaming ready?

For the first time, I’d say yes — with caveats. If you have the right hardware (AMD GPU, decent HDR monitor, proper cable) and a distro that stays current, you can get a genuinely good HDR experience. Colors pop. Highlights shine. Black levels stay black.

It’s not as frictionless as Windows, where HDR has been a standard feature for years. But Windows HDR has its own problems — auto brightness, inconsistent app support, and the infamous “washed out desktop” issue that Microsoft still hasn’t fully fixed. Linux’s approach, while newer, is more technically sound: a clean pipeline from compositor to game, with no mystery processing in between.

If you’ve been waiting for the right moment to try HDR gaming on Linux, this is it. Grab a recent distro, install KDE Plasma 6, and let Gamescope handle the heavy lifting. The future of PC gaming is open source — and it’s finally bright.

Continue Reading

Social Media

From Gems to Employees: How to Turn AI Tools Into Autonomous Workers

Published

on

autonomous AI employees

The Weekend Is Almost Here: Don’t Miss This AI Roundup

Friday’s looming. You’ve got one foot out the door, but before you log off, there’s a batch of AI intel worth your attention. Save it for later if you must — just don’t skip it.

This week’s edition zeroes in on three areas that matter if you’re building a serious AI workflow: converting Google Gems and custom GPTs into reusable Skills, training autonomous AI employees that actually meet your standards, and the latest industry moves from Gemini and others.

What Are Gems and GPTs — and Why Convert Them?

You’ve probably tinkered with custom GPTs in ChatGPT or played with Gems in Gemini. They’re handy, sure. But they’re also siloed. A GPT lives inside ChatGPT; a Gem stays in Gemini. That’s fine for personal use, but it falls apart when you want a consistent process across your whole operation.

The fix? Turn them into Skills. A Skill is a packaged, reusable capability that any AI agent can call on — regardless of the underlying model. Think of it as the difference between hiring a freelancer who only works in one app and hiring someone who can plug into your entire tech stack.

This isn’t just a nice-to-have. If you’re serious about building autonomous AI employees, Skills are the building blocks. They let you standardize how your AI handles specific tasks, so you’re not reinventing the prompt wheel every Monday morning.

How the Conversion Works

  • Audit what you have: List every custom GPT and Gem you’ve created. Which ones actually save time?
  • Extract the core logic: Strip away the interface and isolate the instructions, knowledge files, and workflow steps.
  • Repackage as a Skill: Define clear inputs and outputs. A Skill should be callable by any agent, not tied to a chat window.

It sounds technical, but the payoff is real. Once your best prompts become Skills, they’re versionable, shareable, and — crucially — usable inside automated pipelines.

Training AI Employees That Match Your Standards

Here’s the uncomfortable truth: most people’s AI assistants are mediocre because they’re trained by accident, not by design. You let the model guess what “good” looks like. Then you’re surprised when the output is generic.

Training an autonomous AI employee is different. You’re not just writing a prompt — you’re onboarding someone. That means setting expectations, providing examples of excellent work, and establishing guardrails for when things go sideways.

Start with a single role. Pick one repetitive task — say, drafting client emails or summarizing industry reports. Build a Skill for it, then train the agent on your feedback loop. Show it what a 9-out-of-10 response looks like. Correct it when it drifts. Over time, it gets faster and sharper.

And here’s the key: it works while you sleep. That’s the whole point of autonomous. You set the standard, the AI meets it, and you’re not in the loop for every single output.

A Simple Training Framework

  1. Define the role: Write a one-paragraph job description for your AI employee.
  2. Give it a Skills stack: Assign the Skills it needs to do the job.
  3. Run a pilot: Test on low-stakes tasks first. Measure accuracy, not speed.
  4. Iterate: Feed corrections back into the Skill definitions.

Done right, you’ll have a workforce that scales without headcount. That’s not sci-fi — it’s just good process design.

Industry News: Gemini and the Wider AI Landscape

Meanwhile, the big players aren’t standing still. Gemini has been rolling out updates that blur the line between chatbot and coworker. New capabilities are pushing toward longer context windows, better tool use, and more reliable multi-step reasoning.

What does that mean for you? The gap between consumer AI and enterprise AI is shrinking. Tools that felt experimental six months ago are now production-ready. But that also means the bar for differentiation is higher. Anyone can chat with a bot. Few can deploy a fleet of autonomous AI employees that actually deliver.

The winners this year won’t be the ones with the fanciest models. They’ll be the ones who figured out how to turn AI into a repeatable, trainable workforce. That starts with Skills — and ends with results.

So before you head out for the weekend, ask yourself: are you still playing with AI, or are you actually putting it to work?

Continue Reading

Social Media

Judge Hands X a Split Verdict in Trademark Fight With Twitter Rival Tweet.app

Published

on

Tweet.app trademark ruling

A Startup Built on Trademark Scraps

Most social media startups begin with a big idea. Operation Bluebird began with a legal loophole. The Virginia-based company, founded by two lawyers, launched with the explicit goal of picking up the trademarks Elon Musk discarded when he renamed Twitter to X. Its homepage doesn’t hide this. It says the company wants to go back and grab what Musk dropped when he “threw the bird away on his way out.”

That’s not your typical mission statement. But it might be a clever one.

On Wednesday, a federal court in Delaware delivered a split ruling in the trademark fight between X Corp. and Operation Bluebird. Judge Colm F. Connolly granted X’s request for a preliminary injunction on eight Twitter-related marks. That means the startup can’t call itself Twitter.now. The core “Twitter” name stays with X, at least for now.

But here’s the twist. The judge denied X’s motion regarding two other marks: the word “tweet” and the Twitter bird logo. He wrote that Operation Bluebird was “likely to succeed in proving both that X Corp. discontinued the bona fide use of the Tweet mark and Bird logo and that it intends not to resume the use of the marks.”

In plain English: X gave up on those words and images. The public kept using them, and now a rival can too.

The Lawyers Behind the ‘Tweet’ Revival

Operation Bluebird isn’t run by Silicon Valley dreamers. It’s led by Michael Peroff, an Illinois-based attorney, and Stephen Coates, who once worked as a trademark lawyer at Twitter. Their legal pedigree makes their claim of wanting to build a fresh social network feel a bit thin. The real prize here is likely the trademarks themselves, which carry value independent of any actual product.

Still, the startup is going through the motions. It has rebranded its website as Tweet.app and opened its doors to early testers. The company told TechCrunch that more than 172,000 people requested a handle before launch. That number probably reflects lingering public affection for the Twitter brand — a name the startup can no longer use.

There’s a catch, though. To reserve a handle and join, users must pay $20. That fee likely helps cover the mounting legal bills.

What the Judge Actually Decided

This ruling isn’t final. It’s a preliminary injunction, which means the court is weighing the likelihood of success on the merits. Judge Connolly sided with X on the eight marks tied directly to the Twitter name. He sided with Operation Bluebird on the Tweet mark and the bird logo.

The case will now proceed to a full trial to determine whether X retains any rights to the Twitter marks, given that the company now operates under the X banner in most places.

For now, the practical outcome is this:

  • X keeps exclusive rights to the “Twitter” name.
  • Operation Bluebird can use the word “tweet” and the bird logo.
  • The startup must rebrand away from Twitter.now.

A Question of Abandonment

The core legal question is whether X abandoned these marks through non-use. In trademark law, abandoning a mark means discontinuing its use with no intent to resume. Musk’s aggressive rebrand to X in 2023 left the word “tweet” and the bird logo in limbo. The company kept the Twitter handle on its own platform but stopped using the bird in most official capacities.

Coates, now president of Operation Bluebird, framed the ruling as a victory for the public. “They kept the word. They let go of the bird, and they let go of the tweet,” he wrote in an announcement shared via email with TechCrunch. “A tweet was never a corporation. It’s one person saying something. That word survived three years of a company trying to replace it, because the public declined to stop using it. We think that tells you who it belongs to.”

That’s a poetic argument. Whether it holds up in court remains to be seen.

What This Means for X and Its Rivals

For X, this ruling is a mixed bag. It protects the core Twitter trademark, which the company still uses in some contexts. But it opens the door for competitors to use the word “tweet” and the bird imagery — elements that remain culturally significant even if X has moved on.

For anyone tracking Elon Musk’s X rebrand and its legal fallout, this case is worth watching. It could set a precedent for how courts treat abandoned trademarks in the fast-moving world of social media. If X loses the full case, it might have to accept that the bird and the tweet belong to the public now.

The startup’s approach is unusual, but it’s not without precedent. Companies have long scooped up abandoned trademarks and repurposed them. The difference here is scale: Twitter’s marks are among the most recognized in internet history.

For now, Tweet.app lives. Twitter.now is dead. And the bird, it seems, has found a new perch.

Continue Reading

How To

I finally found an easy way to make Windows remember exactly where every app window belongs

Published

on

Windows remember app positions

Every morning, the ritual repeats. Open the same half-dozen apps, then spend five minutes dragging, resizing, and nudging each window into its designated spot across two monitors. By lunch, something shifts—a notification steals focus, a window snaps to the wrong screen—and the carefully built layout crumbles. It’s maddening.

I’d tried every trick I knew. Windows built-in snap layouts help, but they only work one window at a time. Third-party tools exist, but most feel like overkill or cost money. Then I stumbled on a free utility hiding inside PowerToys: Workspaces. It’s the closest thing to a magic button I’ve found for Windows remember app positions—and it’s genuinely easy.

What is PowerToys Workspaces?

Workspaces is a relatively new addition to Microsoft’s PowerToys suite, which has been around for years as a grab-bag of productivity utilities. It lets you capture a snapshot of your current desktop layout—which apps are open, where they sit, their size, and even which monitor they’re on—and save it as a named workspace.

Later, with one click, you can relaunch all those apps and have them snap back into their exact positions. No dragging. No resizing. No remembering which browser profile goes on the left screen. It’s like a bookmark for your entire desktop.

Why I stopped using manual snap layouts

Windows Snap Layouts (the hover-over-the-maximize-button feature) is fine for a quick two-window split. But it fails when you need a precise arrangement across multiple monitors or want to restore a full set of apps after a reboot. Workspaces solves that because it handles the whole layout as one unit, not window by window.

How to set up Workspaces in PowerToys

Here’s the part that sold me: setup takes less than a minute. You don’t need to configure anything complicated—just capture what’s already on your screen.

  1. Install PowerToys from the Microsoft Store or GitHub if you haven’t already.
  2. Open PowerToys and select Workspaces from the left sidebar.
  3. Arrange your apps the way you want them on your monitor(s).
  4. Click Capture Workspace—PowerToys takes a snapshot of every open window’s position and size.
  5. Give your workspace a name, like “Work” or “Coding Setup.”
  6. That’s it. You can now launch that workspace anytime from the Workspaces editor or a shortcut.

One note: Workspaces works best with apps that support command-line launching or have standard window handles. Most everyday programs—browsers, editors, terminals, chat apps—work flawlessly. Occasionally, a stubborn app might not restore perfectly, but in my testing, that’s rare.

Restoring a layout with one click

Once you’ve saved a few workspaces, using them is even simpler. Open the Workspaces editor, hover over a saved layout, and hit the launch button. PowerToys opens all the apps and arranges them exactly as captured. You can also assign a keyboard shortcut to each workspace, which turns the whole process into a single keystroke.

I now have three saved workspaces: one for writing (browser, editor, notes app), one for development (terminal, IDE, preview window), and one for communication (email, Slack, calendar). Morning startup went from a five-minute chore to a ten-second flick of a key.

What makes this different from other layout tools

I’ve tested utilities like FancyZones (also part of PowerToys) and paid tools like DisplayFusion. FancyZones is excellent for creating custom snap regions, but it doesn’t launch apps or restore a full set. DisplayFusion does window management across monitors, but it costs money and has a steeper learning curve.

Workspaces hits a sweet spot. It’s free, it’s built into a tool you might already use, and it requires zero configuration for basic use. If you’re juggling multiple monitors or just tired of rearranging after every reboot, this is the easy way to make Windows remember app positions without buying anything or wrestling with scripts.

Tips for getting the most out of Workspaces

  • Capture after a clean setup: Close apps you don’t want in the layout before capturing, so you don’t freeze in a stray window.
  • Use separate workspaces for different tasks: Don’t try to cram everything into one layout. Save distinct setups for distinct modes of work.
  • Combine with FancyZones: If you want more granular control over snap regions, set up FancyZones first, then capture a workspace that uses those zones.
  • Test with your key apps: Some apps (like elevated admin tools) may not restore automatically. Test your core set to see if anything needs a manual nudge.

If you’re like me and you’ve spent months fighting your own desktop, give Workspaces a shot. It’s the rare productivity fix that actually sticks. And for more Windows productivity tips, check out our guide on customizing your taskbar for faster workflows or setting up a multi-monitor display like a pro.

Continue Reading

Trending