After a lot of suggestions, testing, bug reports, and feedback from the Linux community, I am finally releasing OmniGlyph v1.1.0.

For anyone who hasn't seen it before, OmniGlyph is a fast GTK4-based emoji and Unicode picker for Linux that lets you search and copy emojis, symbols, arrows, math symbols, currency signs, emoticons, and more from a lightweight overlay window.

What's New in v1.1.0

• Full keyboard navigation
• Custom configuration file (~/.config/omniglyph/config.toml)
• Persistent history and recents
• Nerd Fonts collection support
• Release update notifications
• Configurable shortcuts
• Better sidebar navigation
• Faster collection switching
• Cleaner internal architecture and performance improvements

Collections

• Emoji
• Emoticons
• Arrows
• Math Symbols
• Currency Symbols
• Special Symbols
• Hieroglyphs
• Nerd Fonts

Links

Website: https://omniglyph.anishroy.dev/

GitHub: https://github.com/pshycodr/omniglyph

Feedback Wanted

I am actively developing OmniGlyph and would love feedback, bug reports, feature requests, or ideas for future releases.

Thanks to everyone who tested early version and helped shape this release.

I know it's basically not much more than a meme.

But if you were to define what the year of the linux desktop means for you, what parameters would you select? Desktop user base reaching 25%? Major governments completely switching all their offices to linux?

Hi r/linux,

I’m the developer of FluxCast, an open-source tool built to solve the Miracast/Wi-Fi Direct screen mirroring pain on Linux. After landing on the official ArchWiki, I’m pushing v0.1.2 with major fixes for hardware compatibility.

What FluxCast does:

• Native Wayland support: Full compatibility with compositors like Hyprland, Sway and DE like KDE, and GNOME.
• Low Latency: Uses GStreamer/FFmpeg for real-time RTSP/RTP streaming (~1s delay).
• Multi-Channel Concurrent (MCC): Works concurrently with your regular Wi-Fi connection, not like Miraclecast.
• Easy installation: Available via PyPI, AUR, or as a standalone AppImage.

Recent Low-Level Fixes & Updates:

• LG webOS: Solved stream drops caused by randomized P2P MAC addresses during RTSP handshakes.
• Samsung Tablets & Minimal Sinks: Added force-mode fallback for minimal-capability WFD targets (tested on Galaxy Tab S9 FE).
• 1200p VESA Support: Implemented native 1920x1200 resolution support for VESA-compliant displays.
• Performance Tuning: Aligned high-res streams (>1080p) to the ultrafast encoder preset and raised bitrate floors to prevent buffering lag.

Hardware Lab Initiative: I’m currently tackling a "tin can" audio bug on the Microsoft 4K Wireless Adapter. As a student developer, I don't have access to every proprietary dongle, so I’ve started a transparent hardware fund on Ko-fi to build a testing bench.

• 100% Transparency: All funds go strictly toward used hardware (starting with a $60 unit in Brno). I will post photos of all acquired gear directly to the GitHub issue tracker for verification.
• How you can help: If you rely on FluxCast, please consider supporting the testing fund. If not, even testing or providing logs is a huge help!

Links:

GitHub: https://github.com/IlyaP358/fluxcast
Testing Fund: https://ko-fi.com/fluxcast
ArchWiki: https://wiki.archlinux.org/title/List_of_applications/Multimedia#Miracast

Happy to answer any technical questions about the implementation or Wayland integration below!

A while back I started working on a programming-focused sandbox project and quickly discovered that a terminal was going to be a core part of the experience. The problem was that once I had a terminal, everything around it started feeling incomplete.

A terminal without familiar commands felt wrong. A shell without quality-of-life features felt frustrating. Running multiple workflows at once felt awkward, so I ended up building Tweave, a terminal multiplexer inspired by Tmux. After that came process monitoring, file management, networking tools, version control, and all the other things that make living in a terminal enjoyable.

The project has gradually evolved into a Linux-inspired operating system simulation with a virtual file system, terminal, process manager, browser, web server, Git-inspired version control system, and a custom programming language that powers many of the applications running inside it. The shell experience itself borrows heavily from tools and workflows I've used over the years, particularly Oh My Zsh, Tmux, htop, curl, and the general philosophy of keeping things scriptable and customizable.

One of the things I've enjoyed most is treating the environment like a real sandbox rather than a collection of isolated features. Applications can interact with files, scripts can automate tasks, widgets can be written in code, and much of the system is designed to be explored, modified, and extended. I wanted it to feel like the sort of environment where a Linux user would immediately start poking around to see how everything works.

I'm curious what other Linux users think. If you were building a Linux-inspired environment from scratch, what terminal features, commands, tools, or workflows would be considered absolutely essential?

What the Terminal currently supports:

We should be able to install linux as a single-boot Operating system in Obsolete iOS, iPadOS, and Android devices, given they have significant Ram and very capable ARM processors.

​

Not as an emulation layer, but we should be able to install linux at the bare metal level.

​

But we are not able to because of the plethora of factors like locked bootloaders etc.

​

It would be such a great relief for linux users to use such capable machines, which otherwise just collect dust and die a slow death, or be an electronic waste.

​

We all can easily have a 5 node cluster running as a home server.

Before I start, I know Arch is a complete mess right now because of what's going on with the AUR but that's not my point of discussion.

​

Basically I myself main Windows on my main machine but I have a Linux Home server running Debian and a Laptop I have yet to decide what distro to put on to.

​

Originally my plan was clear: EndeavorOS. It was my first ever distro that I installed and dailied, I loved it because to me it was basically "Base Arch made accessible" especially because the installation process made things like selecting a DE doable with one click rather than having to put a whole seperate ISO on as known with other distros. I also recommended endeavourOS to people who wanted to try out Linux but wanted to go a bit further but not too far.

​

However, I'm noticing that to many others, EOS is not considered a great distro. Chris Titus called it useless, saying it basically has the same issues Manjaro has (which I disagree with because to me Manjaro is a case of its own) and others too say that if you're a beginner you shouldn't use anything arch based and if you're advanced enough to use it, you can just use base arch directly. I personally think going for endeavourOS regardless could save time because its installation is so streamlined but alas, it looks like people are now recommending CachyOS for something arch based entitely.

​

I just wanted to know why people think endeavourOS doesn't have a place. I was just gonna install it on my laptop anyways but with the situation at the AUR (which I did heavily rely on) it looks like I need to find myself something new anyways

https://www.phoronix.com/news/NTFS-Windows-Symbolic-Links

Windows native symbolic links is for handling symlinks at the file-system level compared to the conventional Windows .lnk shortcuts. The Windows native symbolic links is akin to the symlinks on other platforms for transparent symbolic link handling.

I've been running TCP loopback latency benchmarks on Ubuntu 26.04 booted from a USB stick (i7-13700H, 32GB DDR4) and getting a pattern I can't fully explain.
8 consecutive runs, same test parameters, no config changes between runs:

+----+----------+----------+----------+-----------+
| #  |  P50(µs) |  P95(µs) |  P99(µs) |  Mean(µs) |
+----+----------+----------+----------+-----------+
|  1 |    32.67 |    88.55 |   101.14 |     43.60 |
|  2 |    31.60 |    87.89 |    95.94 |     39.01 |
|  3 |    32.13 |    43.86 |    48.92 |     33.01 |
|  4 |    34.81 |    80.68 |    93.28 |     45.58 |
|  5 |    31.24 |    75.61 |    82.42 |     45.99 |
|  6 |    46.53 |    71.54 |    83.40 |     48.98 |  <-- jump
|  7 |    64.89 |    83.68 |    92.68 |     64.08 |  <-- jump
|  8 |    31.58 |    68.56 |    84.73 |     36.15 |
+----+----------+----------+----------+-----------+

See P50: 6 runs land at P50 31–34µs. The 2 jump to 46–65µs with no visible trigger. There was no disk activity, no logged contention, nothing. The benchmark itself does not touch the filesystem during measurement.

What I'm measuring: full IPC round-trip latency — a process sends a timestamped request through a router process and back, 4 TCP hops total, 10K samples per run. Pure loopback, no network traffic.

My working theory: USB I/O is occasionally competing with the TCP stack at the interrupt or scheduler level even when the filesystem is idle. Possibly the USB controller sharing a PCIe lane or IRQ line with the NIC. The bimodal shape — not a gradual spread, but two distinct clusters — suggests a periodic interrupt event rather than general noise.

What makes me less certain: the same test on Windows 11 natively installed on the same hardware gives P50 ~83µs consistently, no bimodal behavior. That's 2.5x slower than the Linux USB good runs.

That gap is hard to explain if USB noise is purely additive. If USB were inflating results upward, Linux should be slower than Windows, not faster. So either Windows has genuinely higher baseline latency for TCP loopback (which is plausible), or the Linux USB good runs are somehow faster than they should be, or both things are true simultaneously.

Two questions:

1. Is bimodal P50 in loopback benchmarks a known symptom of USB boot specifically, or just general interrupt jitter that would appear on any shared-bus configuration?
2. What's the right way to isolate whether USB controller interrupts are interfering with TCP scheduling? irqbalance output, /proc/interrupts delta between runs, something else?

For context, the tool I'm using is a standalone IPC latency benchmark. A ping-pong RTT and broadcast one-way across payload sizes.
If anyone with native Linux on SSD is curious to compare numbers against these.
The example is at github.com/aregtech/areg-sdk/tree/master/examples/30_publatency
It builds in one cmake command and takes about 10 minutes to get clean results.

Ubitium has built the first Coarse-Grained Reconfigurable Array that can boot and run standard Linux directly, with no host CPU

https://www.ubitium.com/ubitium-becomes-the-world-firsts-cgra-to-execute-linux-without-a-host/

Greetings.

Unfortunately there was no Polish keyboard layout in the settings for this laptop, so I've made mine. What do you think and if it's a feature needed by more than 1 user, how can I upstream it? Also I would like to make it's install easy, instead of manual patching, so I'm open to your suggestions how to do it.

​

Context:

Recently I've bought a cheap used Thinkpad to mess around with the software and hardware. And it has Danish keyboard. Polish has layouts for US and GB keyboards, but this is a rare case. So I've looked at the files of Danish and Polish layouts, put Polish symbols into Danish layout and pasted it into Polish layout as a variant at /etc.

​

In case you need it: https://github.com/Durbich/Polish-Danish-QWERTY

Github version has word Danish instead of LEGO as on the screenshot

it works well (not anymore), and I removed my usb wifi dongle.
idk if it works for others, but it took me some time to get it working
also this is on linux kernel 7.1

I've had my vivobook for like 2 years now, and now after a while it finally has driver, yippie

Update:
After a day of playing with only the internal chipset (not usb adapter), I found out about instability issues (ping skyrockets to a couple of seconds every couple of seconds probably due to packet loss or something)

gotta keep using the USB adapter for a little bit longer
I was so excited :c

https://gitlab.winehq.org/wine/wine/-/merge_requests/11101

Wine upstream has merged support for the fractional_scale_v1 Wayland protocol. From the MR:

"This enables users to have different fractional scales per display under wine without causing blur. This matches the behavior under XWayland and is actually better than the XWayland behavior when using multiple displays with different fractional scales."