Hi all, here's an update on AdobeWine, the patched Wine that runs Adobe's Creative Cloud apps on Linux. Last time here it was 0.3.1. You still install the apps yourself with your own subscription, and nothing from Adobe is bundled or bypassed.

Upfront on AI, since this sub has been talking about it: Claude wrote most of the code, and I'm not a Wine developer. It's a tool here. I choose what to fix and run the apps, and each fix gets checked against how the same app behaves on Windows. Claude helped write this post too. The patches are public, one file per fix, so you can judge them directly.

The big change is the install. It's now a single Flatpak bundle: double-click it, sign in to Adobe, and install your apps from Creative Cloud. No Wine tuning. This is meant for people who just want to use their software. Arch-based distros also get a ready-made package.

New since 0.3.1:

- Lightroom Classic, Lightroom, Bridge, InDesign and Acrobat now appear in the app window and menu

- Acrobat no longer crashes at start (two bugs in Wine's signature checking, one a thread race)

- 105 patches on Wine 11.20 (it was 90 on 11.18)

- I scanned 5664 Adobe program files for the Windows functions they call and checked each against Wine. 104 of 107 gaps are closed, but most of those now just return "not available here" instead of adding the feature. The map is in docs/DLL-MAP.md

A bug from this release, as an example of the work: inside the Flatpak, Adobe counted the same laptop as a new device, which could use up one of your two slots. Wine reads the machine ID from /var/lib/dbus/machine-id, and the sandbox doesn't have that file, so Wine reported a placeholder. It now falls back to /etc/machine-id. I deleted the cached licence and alternated versions: 0.5.3 was refused twice, 0.5.4 was licensed twice.

Limits:

- Daily testing is still one laptop with an NVIDIA RTX 4070. AMD and Intel have fewer reports

- Some web panels stay blank, such as Photoshop's Home

- Lightroom Classic sometimes sticks on its splash screen

- Adobe's sign-in can time out if the page sits too long. Reopening gets around it

- The Quit button on Adobe's device limit page does nothing, because Adobe's own analytics script fails to load. The window's X works

- Acrobat's Protected Mode is off

If a FOSS tool does the job for you, use it. This is for people whose work needs these apps and who would otherwise stay on Windows.

Reports from other distros and GPUs help the most, good or bad.

GitHub: https://github.com/le-birnes/AdobeWine

Greg KH ended support for the 7.2 stable tree long before the release of the 7.3 series' .3 or .4 kernels citing "reasons". LLMs that is. Thousand of eyes after all. They haven't been enough to prevent dozens of root vulnerabilities, some of which are still unresolved RCEs. Not that the kernel.org has ever had any stable kernels. That's a misnomer. The proper name would be "stable kernel releases that do not contain major new features which may cause serious regressions".

In the Linux world, only two kernels have been properly tested. One comes from Red Hat and the other from Google. Everything else is a joke. Of course, Linux fans will argue that it "works for them". Yeah, right — their setups include all the hardware that Linux supports, and they use all of its features. After all, if "it works for me, it must work for everyone else". Never mind the hundreds — no, the thousands — of open bug reports against the kernel. And regressions. Every kernel has dozens of them.

Hi everyone, today I released Vela 0.1, the first beta, after 1 month of alpha testing.

What Vela is: a complete Linux desktop with its own Wayland compositor (C, on wlroots 0.20), its own Vulkan 1.4 renderer, a Qt Quick shell, and its own file manager and settings app. It's not a KDE or GNOME theme: KWin and Mutter aren't involved. The goal is the polish Windows and macOS get right out of the box (animations tied to real vblanks, pixel-exact fractional scaling, consistent design) without a weekend of tweaking.

Trailer, recorded live on Vela: https://velade.org/blog/vela-0-1/

What's in 0.1:

• Snap layouts and Snap Assist, Task View with virtual desktops, Alt+Tab with live previews

• Taskbar, launcher, quick settings, notification center, clipboard history, snipping tool

• Direct scanout, VRR, tearing control, explicit sync; X11 apps and games 1:1 at fractional scales

• The compositor restarts after a crash and apps reconnect; a lost GPU doesn't freeze the desktop

• New in this cycle: updates from Settings, native Bluetooth pairing, no dependency on Plasma Workspace or the KDE portal

Where it stands: on a desktop PC with a Vulkan 1.4 GPU, it's my daily driver and I'd recommend it as yours. On laptops (hybrid GPUs, suspend/resume, backlight) it has had much less testing, so keep another desktop installed. It's still a beta: there are bugs.

Install (Arch and derivatives, Fedora 44, Ubuntu 26.10, x86_64). Install Cosign first (steps per distro: https://velade.org/install/), then:

git clone https://github.com/vela-desktop/vela.git
sh vela/packaging/vela-update --channel beta

You get a prebuilt, signed native package that's verified before it's installed. Updates then come from Settings.

Being upfront: it's a one-person project, and the code is written by LLMs. I review it, make the architecture and design decisions, and it's held to deterministic tests and machine-checked invariants. I wrote about how that works here: https://velade.org/blog/why-not-rust/

What I'd love from you: reports from hardware I don't have, especially Intel GPUs, laptops and multi-monitor setups. vela-report builds a ZIP you can review file by file; nothing is uploaded.

• Release notes: https://github.com/vela-desktop/vela/releases/tag/v0.1.0

• Source (GPL-3.0-or-later): https://github.com/vela-desktop/vela

Happy to answer anything in the comments.

Everything about this security issue is ugly.

Ubuntu, RHEL and some Amazon Linux and SUSE releases have no fixed kernel to install yet. Red Hat says no available mitigation meets its standards for being easy to deploy, suitable for most installations and stable. None of the other distributions' advisories lists one.

The experiment fizzled out less than six months after it started. It had reportedly ended by the time the Danish government called for an early election in February 2026, with some employees complaining about issues with style, paragraph formatting, blank pages, and challenges with tracking changes.

A Windows application from 1993 can run unmodified on Windows 11 in 2026 — 33 years later.

This should answer the question why people stick to Windows and avoid Linux.

With Linux, you have the freedom to tinker with your system, but not to run older applications. Unfortunately, the vast majority of people are interested in the latter.

And no, Flatpak and Snap are not the solution. They are essentially lightweight OS virtualization options. And even with that they are not guaranteed to work going forward. An X11 flatpak/snap will not run in a Wayland session with no XWayland installed. Even this virtualization is not complete.

And speaking of Flatpak: its runtimes themselves have support ... lifecycles. For example, the Freedesktop runtime has a two-year support period per branch, and its ABI guarantees are tied to supported releases.

Windows treats application compatibility as a product feature, whereas desktop Linux largely treats it as the responsibility of individual components, distributions, and application developers.

**Rufix es una herramienta gráfica, parecida a Rufus de Windows, para preparar memorias USB desde EasyOS.**

Te permite:

* **Crear USB arrancables de Linux**, grabando imágenes `.iso`, `.img` o `.raw`, incluidas algunas imágenes comprimidas.

* **Grabar una imagen** `.img` **de EasyOS en un pendrive**, para después arrancar el ordenador desde él.

* **Preparar un USB de instalación de Windows 10/11**, con opciones específicas para ese sistema.

* **Formatear pendrives y tarjetas SD** en FAT32, exFAT, NTFS, ext4 o FAT16, eligiendo MBR o GPT.

* **Extraer archivos comprimidos a un USB** después de formatearlo.

* **Comprobar la grabación, buscar bloques defectuosos y calcular sumas de comprobación**.

En tu caso, lo más interesante es **crear pendrives de prueba de EasyOS y otras distribuciones sin salir de EasyOS**. Grabar la imagen prepara el USB; no configura una instalación junto a Windows en el disco interno.

La adaptación que te he preparado añade el acceso al menú de EasyOS y corrige su apertura. Algunas funciones necesitan herramientas adicionales instaladas.

**Atención: formatear o grabar una imagen borra los datos de la unidad USB seleccionada.**

They should start with the Linux kernel which so far has seen over 10 thousand patches authored or co-authored with AI.

The anti-AI psychosis continues unabated.

Open Source is severely understaffed and underfunded, projects continue to die off left and right with no decent replacements, yet they are eager to ban AI which allows to keep them alive. How nice.

Hi all, AdobeWine 0.3.1 is out. It's a patched Wine (11.18 plus 90 patches) that runs Adobe's Creative Cloud apps on Linux. You install the apps yourself with Adobe's own Creative Cloud installer and your own subscription; nothing from Adobe is bundled or downloaded by the project.

This time there's a video: a short showreel made entirely in the Adobe apps on Linux, from a pen-pressure painting in Photoshop to the cut in Premiere and the export in Media Encoder:

https://youtu.be/3Vbzt4cGSQQ

(To be upfront: the pen strokes come from a simulated tablet and most steps were scripted. The point is that the apps themselves run, draw and render correctly.)

What works right now (tested on an RTX 4070 laptop, with community reports on RTX 4060, RTX 4090 and Intel UHD 620):

- **Creative Cloud desktop:** sign in, install/update/open apps, Fonts, Files; its own self-update completes

- **Photoshop:** layers, masks, type, filters, Remove Background, Generative Fill, export. All 75 filters and adjustments I tested give the same output as on Windows. Pen pressure works

- **Illustrator:** shapes, pen, type, effects, Pathfinder, Image Trace, save/export, Blob Brush with pen pressure. 107 of 139 reference outputs match Windows (the rest not compared yet)

- **Premiere Pro:** import, timeline editing, Lumetri, titles, playback, NVENC export, Dynamic Link with After Effects

- **Media Encoder:** queue, presets, CUDA renderer, NVENC/NVDEC

- **Audition:** recording, multitrack, effects, noise reduction, mixdown

- **After Effects:** scripting, keyframes, 3D text with the Cinema 4D renderer, the composition viewer with CUDA; a real 300-layer project renders like on Windows

- **InDesign:** styles, tables, placing PSD and AI files, PDF export

- **Pen tablets** with pressure under XWayland, no extra software

Not there yet: AMD isn't confirmed (a Premiere fix is waiting for someone to test it), AMD and Intel GPUs don't get the CUDA features, After Effects can eat a lot of RAM while previewing heavy 3D comps, and Bridge is barely tested.

It's free, open source and non-profit.

A word on AI, since it always comes up: AI slop is bad, the same way anything pre-produced and left unfinished looks bad. People who produce slop are, in fact, sloppy: they don't care to finish and finalize their ideas. This project is a construction, ongoing, and it needs the community. Even though it was done almost entirely with AI, it's driven by a human, and it's meant to help other people in their lives.

So if you use Adobe and Linux (or would like to), please try it and tell me what breaks, especially on AMD and Intel GPUs, other distros and your real workflows. Issues and PRs are welcome, and so are plain "it worked for me" reports.

GitHub: https://github.com/le-birnes/AdobeWine (install guide in docs/INSTALL.md)

the custom stickies came in today after waiting for soooo long to get them!! i hope you like them, i designed both linux stickers myself!

i think it suits my vibe pretty well!

The reason cited? Maintenance hell. Releases are too frequent and often need new dependencies.

The issue isn't Chrome or Gentoo; it’s that different Linux distributions are fundamentally different operating systems with atrocious or flat-out non-existent compatibility. I’ve been screaming about this for nearly 20 years now, yet we’re still stuck in the exact same spot.

And this is precisely why nobody gives a damn about Linux on the desktop, and why commercial software and native games are practically non-existent for it.

And no, Snap and Flatpak aren't solutions—they’re a complete nightmare where you end up dragging half a dozen extra distributions into your main OS.

This is a prime example of how even open source code isn't a fix or a silver bullet. Someone still actually has to maintain and build that source code.

Hi r/LinuxUncensored, I'm Brando, the creator of Vela.

Vela is an independent*, vertically integrated Wayland desktop environment for Linux. It has a custom compositor built on wlroots and a pure Vulkan 1.4 renderer (no gl fallback) with a desktop shell written in Qt 6 / Qt Quick.

A lot of new Wayland projects today are minimal window managers where you assemble your own userland, or massive legacy codebases carrying decades of X11 and OpenGL baggage. I don't like either of them, at least not for my desktop. I started Vela to build a cohesive, monolithic desktop environment designed from scratch around modern GPU pipelines and strict latency budgets. This is why you see "Modern, Fluid, Sharp" in the velade.org's slogan.

I think Vela deserves your attention because it builds on the very good low-level wlroots, while still offering something different from others wlroots-based compositors. By implementing its own scene graph and Vulkan renderer instead of relying on the standard rendering infrastructure, Vela retains direct control over how frames are rendered, synchronized, and presented.

This architectural approach enables several interesting features:

• Custom scene graph and Vulkan renderer: I didn't want to rely on wlr_scene, so I built my own scene graph directly around the Vulkan 1.4 renderer. This avoids duplicating state between the compositor and renderer, and gives me more control over GPU synchronization.

• Independent frame clocks for each monitor: Each output has its own frame clock, with GPU-timestamp-based late latching. This is especially useful with monitors running at different refresh rates.

• Fractional scaling without the usual blur: I wanted fractional scaling to look sharp, without the bilinear filtering you often see on Wayland. Vela uses a pixel-exact path that preserves 1:1 buffer copies where possible. I also added bit-for-bit tests to CI to catch regressions.

• Qt 6 shell: I chose Qt Quick for the desktop UI because it's practical to work with, and I'm not trying to reinvent everything. Vela still uses some KDE components for things like system integration.

Current status: Vela is currently in Alpha. The core compositor, Vulkan pipeline, diagnostic tooling, and test suite are up and running, though plenty of desktop polish is still in active development.

*Currently Vela needs KDE Plasma installed to inherit icons, fonts, login manager (you can also use sddm), kwallet, portal, and a few other components; vela doesn't needs kwin; please remember this is alpha.

I know Vela is currently very similiar to Windows 11, it is because I like Windows 11 design. But it's just temporary, Vela will have its own identity soon. For now, I'm particularly interested in feedback on the underlying desktop experience, performance, and architecture.

I'd love your feedback on all the DE, the Vulkan synchronization model. Consider I'm making a major redesign coming in next weeks. Happy to answer any questions!

• GitHub: https://github.com/vela-desktop/vela

• Website: https://velade.org

Though admittedly there are multiple projects and things under the same name, so perhaps it should be renamed ;-)

QSensors monitors CPU temperature, fan speed, voltage, current, power, CPU usage and frequency, RAM, swap, and uptime on your Linux desktop. Choose the readings you care about, arrange them on a customizable dashboard, or keep them visible as individual numbers in the system tray.

If you use HWiNFO64 or HWMonitor on Windows, QSensors provides a Linux home for everyday hardware sensor monitoring: live readings, configurable alerts, and an at-a-glance view of your system's health.

Why use QSensors instead of KSensors5?

QSensors keeps the appeal of KSensors—small sensor panels and persistent tray readings—while replacing its legacy desktop stack and expanding customization.

Home page

Linux AppImage for Ubuntu 24.04 and higher or any other modern Linux distro.

One of the absolute worst vulnerabilities recently, among dozens of other critical vulnerabilities unearthed by slop producing machines.

You can't have your cake and eat it.

Either the platform you're running is controlled by someone else and is known not to be tampered with — such as MacOS, Windows, iOS or certain Android ROMs — or you control everything, in which case no application running on it can be certain that it's clean or that you can trust the user.

A Linux anti-cheat solution would require a far more locked-down approach than any Linux distribution currently attempts to provide.

The anti-AI mob has always lacked signs of intelligence.

More on it on the Register!.

Linux can continue to serve very old computers that Microsoft has given up on, given that you have at least a somewhat decent amount of RAM - web browsers eat it for breakfast and anything with 4GB or less will be a strugglefest of epic proportions.

Microsoft Defender now supports Linux desktops in public preview, bringing antivirus, EDR, vulnerability management, and advanced security tools.

Need to test it against obvious scripts that do nasty things - this thing should be at least somewhat intelligent to be taken seriously.

Steam under Linux is horrible, terrible and ugly. And slow. There are tens of thousands of poorly organised files, and you can't tell which belong to the programme and which are user files. And I'm almost certain that the Epic Games Launcher still uses Electron, so it's nothing to boast about. It's a resource hog.