(I'm not rawdogging it. I do not know enough about linux to install one of the rawest forms of it.)

cross-posted from: https://reddthat.com/post/45525768

cross-posted from: https://reddthat.com/post/45525722

What's new in this release:

• Optional EGL backend in the X11 driver.
• Support for Bluetooth Low Energy services.
• Moreover support for generating
• Windows Runtime metadata in WIDL.
• ARM64 builds enabled in Gitlab CI.
• Various bug fixes.

The source is available at https://dl.winehq.org/wine/source/10.x/wine-10.12.tar.xz

Binary packages for various distributions will be available from the respective download sites.

You will find documentation here.

Wine is available thanks to the work of many people. See the file AUTHORS for the complete list.

Edit: I fixed it, I think :)

I believe I incorrectly turned my PC off yesterday, possibly resulting in some kind of corruption of my btrfs partition on my boot drive. I managed to boot into a USB with a live image of EndeavourOS I had, then used:
sudo btrfs rescue super-recover /dev/nvme0n1p3 and
sudo btrfs rescue zero-log /dev/nvme0n1p3

This instantly allowed me to mount my boot drive and btrfs partition and access my files. Rebooted, PC came up fine. This has certainly been an experience in patience and Linux in general. Now I can't stop saying btrfs.

Original Post:

Hey gang, hope you're well. I desperately need some Linux help. I was using my desktop (Bazzite w KDE Plasma) just fine, attempting to open some HTML files in Dolphin. It freezes, I physically turn off my desktop and it boots me into a terminal window with the following:

Failed to connect to system scope bus via local transport: No such file or directory  
[363.200643] BTRFS: error (device nvme0n1p3) in btrfs_replay_log:2100: errno=-5 IO failure (Failed to recover log tree)  

Generating "/run/initramfs/rdsosreport.txt"  

Entering emergency mode. Exit the shell to continue.  
Type "journalctl" to view system logs.  
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report.  

Press enter for maintenance (or press Control-D to continue)  

Admittedly my knowledge of Linux is incredibly limited. I have a feeling it has something to do with being unable find my M.2 drive? But the rest may be foreign to me. I figured out how to output 'rdsosreport.txt' and it spat out about a thousand lines that I couldn't scroll up to see. Pressing 'enter' just prompts the terminal as :/var/roothome#, waiting for commands. 'Control-D' just brings me back to that initial message.

There is a line in journalctl that may give us some clues:

BTRFS error (device nvme0n1p3 state E): open_ctree failed: -5  
sysroot.mount: Mount process exited, code=exited, status=32/n/a  
sysroot.mount: Failed with result 'exit-code'  
Failed to mount sysroot.mount - /sysroot.  

Further down there's:
BTRFS: error (device nvme0n1p3) in btrfs_replay_log:2100: error=-5 IO failure (Failed to recover log tree)

I greatly appreciate any time and help you smart folks can offer!

Update: I have Bazzite on a flash drive, and I have the install wizard pulled up on my desktop. Interestingly, and perhaps worryingly, it's taking an abnormally long time to probe my drives. I have two m.2 drives in my desktop, the primary (Samsung EVO 990 2Tb) where Bazzite is installed, and the secondary (WD, I think, 1Tb split into two partitions). The installer has the "install destination" option grayed out, still attempting to locate the drives. It's been about 10 minutes... Could both of the drives be bad? I sincerely hope not...

Hello everyone, I have I guess a bit tricky situation on hand

I have 4 devices (2 computers, 2 cellphones) on my home network, they're all connected on the same LAN, and additionally, all are also running Tailscale (rather out of the box configuration except specific IPv4 addresses given by me)

When going out of home, I normally take up to 2 devices with me and connect to the ones at home through the Tailscale IP

Usually I do this by typing the IP address manually on either scenario, if I'm home I connect typing the LAN IP Addresses for the devices, otherwise I manually type the Tailscale IP addresses

I would like to now optimize this process using Host Names; I would like to type in say, SSH pc1 and that connect via LAN IP if available, and otherwise fallback to Tailscale IP if not

Result being I can just type the one singular host name, and connect successfully regardless if I'm home or not, also using the best possible connection (LAN preferred over Tailscale)

I am aware Tailscale has a feature that it does this out of the box using the Tailscale IP on the same LAN, but this doesn't seem to work on all devices (the phones) and additionally that generates some noticeable overhead given their age too

I have been reading about Avahi and thinking of using it on each device, advertising the same host name with both it's IPs, which I am yet to try but figured I could use more input on solutions if anyone has experience with it, I'd appreciate any

Thanks for reading, and I hope you have a nice day

I'm looking for something in the low hundreds range, mostly to do Visual Studio Code, pretty light html editing, general purpose stuff like Netflix and web browsing.

I'd kind of just like a decent tablet with a keyboard cover. The Pixel tablet might be an option, even if I have to go with something like this.

https://store.google.com/us/product/pixel_tablet $280

https://www.logitech.com/en-us/shop/p/k480-multi-device-wireless $35

I'd of course prefer to run Linux over Android if it works. Is there anything in a similar form factor and function for price in the Linux world?

Thinking nothing more wonky than mint/pop!/bazzite/elementary. I know there is never “one” perfect one but feeling like trying something new on this machine that’s at least somewhat push button. 
Since it no longer receive regular updates from Apple I just want to keep this machine available for use when needed.

I’m pretty comfortable on the above ones I mentioned. I’m not a coder/engineer so I tend to lean heavily on flatpaks and such, though if I have to go into the terminal occasionally I can usually poke my way around

David Heinemeier Hansson, the creator of Ruby on Rails, has tailored together his take on Hyprland combined with Arch. It looks quite neat and promising and looks like a nice entry point for those who don't want to configure hyprland themselves. DHH describes Omarchy as:

Turn a fresh Arch installation into a fully-configured, beautiful, and modern web development system based on Hyprland by running a single command. That's the one-line pitch for Omarchy (like it was for Omakub). No need to write bespoke configs for every essential tool just to get started or to be up on all the latest command-line tools. Omarchy is an opinionated take on what Linux can be at its best.

Omarchy comes in different themes, and by the looks of it this are hotswappable on the go by using the keybinds: Super + Ctrl + Shift + Space.

Theme Showcase

• Website: https://omarchy.org/
• Documantation/Manual: https://manuals.omamix.org/2/the-omarchy-manual
• Github: https://github.com/basecamp/omarchy
• YT video showcase: https://youtu.be/I5Mnni7cea8
• Invidious video showcase: https://invidious.reallyaweso.me/watch?v=I5Mnni7cea8

Once again posting something for reference as I couldn't find it online

Symptoms

No issues after logging in.
After suspending (sleep) and resuming, screen takes 25 - 30 seconds to turn on.
Display settings in Plasma take a long time to load, sometimes don't show automatic rotation option.
Turning on screen after turning off (even without sleep) takes a long time.
No suspicious logs in Kernel and Journald (even after comparing post-fix).
Switching kernel makes no difference.
Logging out and back in temporarily fixes screen rotation and screen waking until next suspend.
Everything works in X11 session apart from screen rotation (appears unsupported).
Running monitor-sensor hangs when running after suspend
systemctl stop iio-sensor-proxy fixes slowdown issues

Workaround

Downgrading to iio-sensor-proxy 3.6-1 following Arch Linux package downgrade instructions.
In my case with a cached package

sudo pacman -U file:///var/cache/pacman/pkg/iio-sensor-proxy-3.6-1-x86_64.pkg.tar.zst

and optionally adding it to IgnorePkg

IgnorePkg   = iio-sensor-proxy # Issues in Wayland after suspend

System info

OS: Arch Linux x64
Host: Lenovo ThinkPad L390 Yoga
Kernel: 6.12.35-1-lts
DE: Plasma 6.4.2 iio-sensor-proxy (broken version): 3.7-1
Last full system upgrade: 2025-07-06

Posting here too as I've not had any responses in the more relevant communities.

Hi there, I've got these really odd issue where certain windows will cause random lines like the one in the screenshot appear on my screen. They will often flicker a bit and will dissapear if I hover my mouse over them. The lines will display what is beneath the window itself. These occour quite frequently and are frankly getting quite annoying to deal with.

Is this a known issue with KDE right now? It does not happen while using Gnome on the same machine + screen. If it matters I am running CachyOS+KDE 6.4.1+AMD.

If there is anythign I can do to fix this then I'd greatly appriciate some pointers!

Symptoms

Stylus taps are registered as well as button presses (on the last cursor position). Cursor doesn't change position.
"Test tablet" in "Drwaing Tablet" KDE settings only displays Stylus release events.
X11 works.
Finger touch still works.

Solution

Rename or delete ~/.config/kcminputrc, or remove config section related to "Pen" (not tested). Deleting the config resets other mouse pointer settings like speed, device enabled/disabled and calibrations.
Then log out and log back in.

Precursor

Testing pen in "Test tablet" section.

Other attempted fixes

Log out and back in - Fail
Reboot - Fail
Moving cursor on login screen and during login process - Fail
Insert and remove pen again - Fail
Shutdown and disconnect battery (in UEFI) - Fail
Removing kcminputrc after diffing with Timeshift snapshot and filtering for interesting files with grep - Pass

System info

OS: Arch Linux x64
Host: Lenovo ThinkPad L390 Yoga
Kernel: 6.12.30-1-lts
DE: Plasma 6.3.5
Libinput: 1.28.1-1
Last full system upgrade: 2025-05-28

I think that you are not allowed to speak freely on most platforms. And when i say speak freely i dont mean to have right to offend people, just to have right to normaly tell your opinion.

cross-posted from: https://pawb.social/post/27451562

Seemingly for the first time, the Bazzite gaming-focused Linux distro has appeared on the Steam Hardware Survey. Well done to the Bazzite team for making such an amazing distro for gaming (and now just general usage as a while too)! Been my main choice for going on a year now for my general use distro, and I haven't looked back.

https://store.steampowered.com/hwsurvey/?platform=linux

Hi! Got an issue I couldn't figure out

When I use /etc/fstab to automount an SMB share using CIFS, I cannot unmount it without root privileges. If I mount it manually (as a non-privileged user), everything works just fine.

Also, an application I mount the share for (Pika Backup, based on borg) cannot access backups unless I unmount the share with root privileges and then mount it back manually.

A respective line in /etc/fstab is: //address/directory /mnt/backup cifs credentials=...,user,auto,iocharset=utf8 0 2

Highlighted user option to make it clear I didn't forget it.

Any advice?

• Not all distros ship SELinux and the ones that do, don't actually configure it securely.

• New users are expected to keep copying and pasting commands from their browsers to their terminal which compromises some Linux security defenses.

• KDE, GNOME and Sway are the only functional Desktop Environments/Window Managers that support Wayland all, while the Other DEs are not even close to shipping with Wayland.

• Most if not all of the Linux Distros in 2025 ship with Grub bootloader, which suffers from a lot of problems, instead of using the bootloaders that does not support BIOS and will improve the reliability of booting and provide a more stable experience.

cross-posted from: https://reddthat.com/post/44560289

What's new in this release:

• Preparation work for NTSync support.
• More support for generating Windowsill Runtime metadata in WIDL.
• Various bug fixes.

The source is available at https://dl.winehq.org/wine/source/10.x/wine-10.11.tar.xz

Binary packages for various distributions will be available from the respective download sites.

You will find documentation here.

Wine is available thanks to the work of many people. See the file AUTHORS for the complete list.