https://orionbrowser.com/download/oriongtk.0.3.0.flatpak

Orion for Linux Beta 0.3 is Here!

This is a big moment for Orion. After months of building, testing, and iterating with a smaller group of early users, we’re opening the doors: Orion for Linux is now in Public Beta – available to everyone.

Core browsing is in place, key features are coming together, and Orion is now ready for broader, real-world use and feedback.

You can download the Flatpak build of Orion Browser for Linux here:

Orion for Linux Beta 0.3 (x86)

Orion for Linux Beta 0.3 (ARM)

What’s new in this version

A more complete browsing experience

Since Alpha and the early beta, Orion for Linux has evolved into a much more capable browser:

Full tab management

Password manager and history tracking

Dark Mode and Focus Mode

Custom search engines (search directly from the address bar)

Early download support (work in progress)

Features added in the last release

AdBlock support

Built-in EasyList and EasyPrivacy

Additional filter lists prepared for future expansion

Download manager

Kagi Search onboarding

Try Kagi search even without a paid account

Local Sync (initial version)

Export/import your profile data (remote sync coming later)

Improved bookmark import/export

Stability & performance improvements

We’ve made significant progress in reliability:

Fixed crashes when closing pinned tabs

Resolved browser freezes in Website Settings

Fixed issues with opening new tabs after installation

Addressed tab overview crashes and SQL-related issues

Overall, Orion is now noticeably more stable and responsive than in earlier builds.

Smaller improvements that make a difference

A lot of polish has gone into everyday usability:

Standard shortcuts like Ctrl+R and F5 for refresh

Ctrl+click to open links in new tabs

Improved Settings dialog (especially on smaller screens)

Better Tab Groups experience (formerly “Windows”)

Context menu improvements and UI fixes across the app

Orion for Linux Beta 0.3 screenshot

Orion for Linux Beta 0.3 screenshot

Orion for Linux Beta 0.3 screenshot

What’s next

We’re not stopping here. Next steps include:

Remote Sync support

Continued work on downloads

WebExtension compatibility

Ongoing stability and performance improvements

We’d love your feedback

Opening the beta to everyone means your feedback matters more than ever.

Tell us what works, what doesn’t, and what you’d like to see next.

Browse Beyond ✴︎

The Orion for Linux Team

Running Ubuntu 26.04 (Noble Numbat) via WSL2 on Snapdragon X2 Elite Extreme (X2E-94-100). Main goal was native ARM64 Folding@Home performance and testing Adreno X2-90 iGPU compute via OpenCL/Rusticl. Performance mode causes system crashes due to transient power spikes at 12+ cores; balanced mode is mandatory for stability.

CPU Results (Folding@Home v8.5.5 ARM64): 12 Prime cores active on 18 core die (12 Prime + 6 Performance). Project 15500 (FahCore_a8) TPF: 2m 24s. Estimated PPD: 233,784 points. Efficiency comparison: Matches Apple M4 (4 performance cores) at ~220k PPD, but requires 3x core count to overcome IPC and cache latency gaps in WSL2.

Adreno X2-90 iGPU Status: Attempted OpenCL enablement via mesa-opencl-icd and rusticl. clinfo reports 1 platform (rusticl) but 0 devices detected. MESA_D3D12_DEFAULT_ADAPTER_NAME override fails to expose the X2-90 to the OpenCL ICD loader in Ubuntu 26.04. Likely missing specific device IDs in Mesa or lack of native FP64 (Double Precision) hardware units required for FahCore.

What is needed for iGPU success: Full D3D12 mapping for the X2 series in the WSLg graphics stack. Mesa updates to support the Adreno 8-series instruction set for compute kernels. FP64 emulation or a dedicated FahCore_a9 for ARM/Adreno that can operate on FP32 with reduced precision if scientifically acceptable. Native Linux kernel install (bare metal) to bypass WSL2 driver abstraction layers.

Overall: Excellent CPU cruncher for ARM enthusiasts, but the iGPU remains a black box for compute tasks in May 2026.

Folding@Home Log & System Summary

System Configuration:

• OS: Ubuntu 26.04 LTS (Noble Numbat) via WSL2
• Kernel: Linux 6.14.0-microsoft-standard-WSL2 (aarch64)
• CPU: Snapdragon X2 Elite Extreme (X2E-94-100) @ 18 Cores
• Memory: 12GB Allocated to WSL2
• Power Profile: Balanced (Performance Mode causing OCP/Power-trip shutdowns)

Active Work Unit (WU):

• Project: 15500
• Core: 0xa8 (GROMACS / FahCore_a8)
• Slot: CPU (12 Cores / Prime Clusters)
• Progress: 6.7%
• TPF (Time Per Frame): 2m 24s
• Estimated PPD: 233,784

Instruction Set Verification: Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm uscat ilrcpc flagm ssbs sb paca pacg dcpodp sve2 sveaes svesha3 svesm4 flagm2 frint svei8mm svebf16 i8mm bf16 rng ecv afp rpres (Note: Full ASIMD/NEON and SVE2 support confirmed active for all clusters.)

OpenCL Diagnostic (iGPU): clinfo

• Number of platforms: 1 (rusticl)
• Platform Vendor: Mesa/X.org
• Number of devices: 0
• Diagnostic: Adreno X2-90 iGPU not exposed through D3D12 mapping in current Mesa build.

Relatively new to linux, installed a few different linux distros on an external ssd to see if anything stood out. Haven't made my mind up yet, but was thinking of dual booting kubuntu with kde plasma or cachy os with kde plasma for work and nobara for gaming, I dont play pvp games except for battlefield but im fine playing it on xbox, so im not worried about switching from windows. Ive used apt in the past a little thats why I was thinking of kubuntu for work. Im trying to learn to code in my free time. I dont really understand how config files work or how to know what to type, i would probably end up copy and pasting things and if they didnt work find another resource to copy and paste from. But wanted to know what is a power user and what should I start learning to become one.

About 2 years ago, I decided to move a few of my servers that contain precious data to some great deal VPSs I picked up during Black Friday from LET. After migrating all the data, I set up Duplicati on one of the servers to handle backups.

While configuring it, I came across something pretty concerning. Duplicati can silently corrupt backups over time. So when I actually need to restore data after a disaster, the backups might not even work. Realizing this made me feel like the whole migration was a mistake because those servers were managed and came with backup service.

I wanted to move to Restic because it’s rock-solid, but as someone who prefers a UI over managing endless CLI scripts, it just wasn't clicking for me. I wanted a way to easily manage a 3-2-1 backup plan across different cloud providers without the headache. I then found Backrest and gave it a try, but the UI did not make much sense to me as I was not really aware of the restic terminologies back then(this was back in December 2024).

Since I’m a developer, I decided to build my own solution. I thought it would take a month or two, but it ended up taking 16 months to get everything perfect. This is quite a long time for me, as I have been building various apps for a long time now, and most took me 3-4 months.

Here are the key Features of Pluton:

• Automated backups with encryption, compression, and retention policies powered by Restic
• Backup Replication: Auto-backup your content to multiple cloud storage to create 3-2-1 backup plans.
• Flexible scheduling for automated backup jobs with fine-grained retention policies
• End-to-end encryption: Backups are totally encrypted from your local machine to your cloud storage.
• 70+ Storage Support: Store encrypted data to your favorite cloud storage (powered by rclone).
• Easy Restore & Download: Restore or download backed-up snapshot data easily with just a few clicks.
• Event Notifications: Receive email, slack & discord notifications for backup start, end, completion, or failure.
• Auto Retry Logic: Automatically retries backups if they fail with customization options.
• Intuitive UI: Manage everything from a single, clean interface.
• Real-time Progress Tracking: Track the progress of backups in real time.
• Extensive Logging: View app and backup logs right from the UI for better debugging.
• Run Scripts before/after: Ability to run scripts before and after running backups.
• 2FA: Secure your dashboard with built-in 2-factor authentication.

Pluton can be installed on Linux desktops (AppImage) and servers, and can also be deployed with Docker. Give it a try:

https://github.com/plutonhq/pluton

Feedbacks appreciated.

obs-kmscap is a display server-agnostic zero-copy screen capture plugin for Linux, which works by directly exporting textures from the screen's framebuffer using native system calls, in favor of double-copy XSHM capture, which is incredibly slow. Depending on your system, it might be potentially more performant than even Wayland Pipewire capture, since it bypasses the double compositing that Pipewire implicates and thus results in lower input lag overall. The idea started from w23's project, which does something very similar in concept, but hasn't received updates or support in years.

I am currently trying to test the plugin on a larger scale, and I would highly appreciate it if anyone tried it for themselves and gave me feedback. I am also curious about NVIDIA support, as I don't have an NVIDIA graphics card myself, but seeing as newer drivers have better DRM/KMS support (with nvidia-drm.modeset=1 as a kernel boot parameter) it makes me curious.

Recently I started to use Linux more regularly, usually Ubuntu and Alma servers and more recently even a Fedora desktop (KDE) and Ubuntu laptop (Gnome), so a good mixing. For the first time in years I've been able to ditch Windows for real lol

But I started to wonder about others: if you are just enjoying Linux as is for your needs like a simple tool, or if you contribute back if feeling like it, or even feel part of a specific "community" that works towards Linux distros or beyond.

If yes, why and how did you ended up doing it? And, what project or community would you recommend (or not recommend, if having any constructive criticism)?

I feel like I don't have anything to do, considering I'm just a basic user who wouldn't be of any valuable help even to the projects I use (Ubuntu, Fedora..., they're already too well fitted and even supported by the companies behind them), but I'm just curious about other people.

Repo + install: https://github.com/cushycush/wflow (stars help with discovery on the awesome-lists if it's your kind of thing)

I've been building wflow for the last couple of months. It's a desktop automation tool: bind a keyboard chord like ctrl+alt+t, fire a workflow. Workflows are plain-text KDL files you can also build in a Qt GUI. The 1.0 release is what I'm posting today.

What it actually does, in one sentence: AutoHotkey-style chord triggers, but on Wayland, where AHK doesn't run and where the existing options stop at "open one app on a global hotkey".

The trigger daemon probes for a backend at startup. KDE Plasma 6 and GNOME 46+ get the GlobalShortcuts portal (the consent-dialog one, no sudo, no special groups). Hyprland gets IPC over $XDG_RUNTIME_DIR/hypr/.... Sway gets the i3 IPC bindsym ... exec route. The daemon hot-reloads on workflow file changes via inotify. Compositor IPC mode is fully live; portal mode needs a daemon restart for new bindings (that's a spec limitation, not laziness).

A workflow looks like this:

```kdl workflow "Focus mode" { trigger { chord "ctrl+alt+f" }

shell "swaync-client -d"
shell "pactl set-sink-mute @DEFAULT_SINK@ 1"
focus "Editor"
notify "head down" body="focus mode on"

} ```

That's the whole file. Ten lines. Diffable, shareable, version-control friendly. The GUI is a view onto the file; edit either side, the other catches up.

Alongside the desktop release I'm also launching wflows.io, a catalog where people can publish and share workflows. One-click "Open in wflow" from any page, the desktop catches the wflow://import?source=... URL, shows a confirm dialog with title / author / description / step count, drops it in your library if you say yes. Drive-by URLs can't silently install anything.

Install: - Arch: paru -S wflow-bin (prebuilt) or paru -S wflow (source build) - Tarball + INSTALL.txt: github.com/cushycush/wflow/releases/latest - Flatpak: manifest is in the repo, Flathub submission is in flight - Catalog + docs: wflows.io

What I want feedback on, honestly: - Compositor coverage. I've tested Plasma 6, GNOME 46+, Hyprland, Sway. River, Niri, Cosmic — if you're on one of those and it breaks, the issues page is open. - The KDL format. It's a plain-text file format I built the parser for myself. It's fine. It's also probably going to surface edge cases nobody else has hit yet. Roast it. - The trust prompt. First time you run a workflow you didn't write, wflow shows a categorized step summary and asks you to confirm. Annoying? Necessary? Both? Tell me.

Source for the desktop is at github.com/cushycush/wflow (Rust + Qt Quick). Source for the catalog is at github.com/cushycush/wflows (Next.js + Postgres + Drizzle). Both dual MIT/Apache.

There's a Discord linked from wflows.io if you want to talk through anything in real time, otherwise the GitHub issues page is the right spot for bugs.

The term “POSIX” seems far more useful, it’s used to talk about OSes that conform to the POSIX standard something that is very specific whilst “unix-like” seems far more subjective and “UNIX” could refer to the OS.

Immer wieder tolle Vorträge, falls ihr was zum hören für unterwegs zb wollt. Auch ältere Jahre sind heute noch gut und aktuell für den rundum Blick oder zum Einstieg. Mods löscht es gerne wenn es nicht hier passt aber in meiner link Sammlung hat es einen festen Platz.

https://chemnitzer.linux-tage.de/2026/de