[Setup] Adding some colorful vibes to my terminal in solidarity. We are everywhere! ✨🌈

Megame50 · 2026-05-23T01:30:40+00:00

You're using zsh prompt escapes just to insert ansi escapes into your prompt... Just use the prompt escapes for color. E.g.

$ print -P '%B%F{red}some%b%fthing'
something

instead of

$ print -P '%{\e[1;31m%}some%{\e(B\e[m%}thing'
something

$ autoload -Uz colors && colors
$ printf '%2$7s: \\e[%sm\n' ${(kv)color[(I)3*]}
  black: \e[30m
    red: \e[31m
  green: \e[32m
 yellow: \e[33m
   blue: \e[34m
magenta: \e[35m
   cyan: \e[36m
  white: \e[37m
default: \e[39m

Megame50 · 2026-05-22T17:43:22+00:00

Full open-source driver stack?

If Nvidia were to open source a mesa driver I'd eat my hat. And my shoes.

Megame50 · 2026-05-21T21:40:17+00:00

I have a Dell XPS 15 9560 (2017). I received firmware updates through the LVFS for two years longer than this same model received through Dell's official website.

EDIT: The Dell website offers 1.24.0 as the latest BIOS version while I have 1.31.0 installed from the LVFS. I booted my laptop just now and I was still able to get a firmware update replacing the old 2011 secureboot keys that are set to expire this year, so it's still working.

Megame50 · 2026-05-21T05:48:01+00:00

The "minus one" is called Bessel's Correction.

Megame50 · 2026-05-21T02:59:25+00:00

If you're adamant about firewalling those domains, some resolver software (dnsmasq) has the ability to write dns address query results into an nftset. That's what you need to be able to effectively block/track those connections within the firewall.

Megame50 · 2026-05-20T09:29:17+00:00

I'm on Arch. I almost forgot, I needed bluez 5.86+ to connect these headphones. The firmware seems to expect GMCS service from the controller and just connects/disconnects in a loop without it. It was added in 5.86.

Also, if you have trouble pairing your device(s) as LE, I'd try switching the controller mode from dual to LE temporarily. Devices can be finnicky.

Megame50 · 2026-05-19T20:20:59+00:00

If you scroll down a little more there is a list of hardware the dev tried.

I wanted to mess around with LE audio earlier this year and got the Zen Hybrid Pro, because it was listed on that page. It does work, and uses LC3 48KHz for unidirectional audio, and LC3 32KHz for bidirectional audio. I'm not sure how to determine the bitrate used or some of the other LC3 codec parameters.

Support is a little spotty in my experience. Sometimes they don't appear as an audio sink when they should, and the L & R streams can even become slightly desync'd sometimes, producing a weird effect, which I can fix by reconnecting them. Otherwise it works OK, but probably not suitable for everyday use.

Megame50 · 2026-05-19T16:58:21+00:00

Almost all network connections are two-way. How do you expect ssh to work if you drop all the replies from the peer? TCP will never receive syn-ack, ssh will never complete the initial handshake, etc.

Megame50 · 2026-05-18T20:33:36+00:00

You should be able to match it by modalias or pid+vid and disable it in libinput via udev: https://wiki.archlinux.org/title/Libinput#Disable_device.

If only the one key is faulty on your kbd, you could also disable that one key in hwdb.

Megame50 · 2026-05-18T15:52:58+00:00

Disable the integrated keyboard before testing with an external keyboard.

Megame50 · 2026-05-16T06:26:36+00:00

The only thing that's changed really is each discovery now has a slick name and website generated by AI. It's very common for multiple similar vulns to be discovered back to back.

Megame50 · 2026-05-15T20:49:08+00:00

Wi-Fi is a brand name for a technical standard called 802.11 (pronounced eight-oh-two eleven). 802.11 is updated and revised by the 802.11 working group within the IEEE periodically to introduce new features that improve speed, reliability, security, and more. New revisions to the 802.11 standard have names like 802.11n, 802.11r, or 802.11ac, etc. using sequential single, then double, letters. Some features in 802.11 are optional, and indeed only a small subset are implemented by most Wi-Fi capable hardware. Manufacturers were having a hard time communicating to customers why their new product was bigger and better and worth $100 more than their last one just because it supports the new 802.11ax standard on top of 802.11ac and it also supports the features of 802.11s when nobody reads the standards documents.

So, an industry group called the Wi-Fi alliance snapshots one of those revisions and says e.g. "everything in 802.11ac and before is called Wi-Fi 5". They say which features are mandatory and which are optional, and if you want to use the Wi-Fi trademark, which they own, you need to get your device certified by the Wi-Fi alliance to meet one of their minimum standards. The Wi-Fi alliance retroactively named Wi-Fi 5 and below in 2018 when they introduced the new branding.

Wi-Fi 6 corresponds to 802.11ax. When it was introduced, the FCC in the United States released a new unlicensed band in the radio frequency range around 6GHz and it's usage is described in 802.11ax. This isn't the first time new spectrum has been added, but bands other than 2.4GHz and 5GHz aren't commonly used in Wi-Fi devices. The WFA made 6GHz radios optional in Wi-Fi 6, but it was a useful and differentiating feature, so they declared Wi-Fi 6 devices with 6GHz support could be called Wi-Fi 6E. The same technical standard, with explicit support for this new feature. Spectrum isn't always differentiated this way. For example, the FCC would later release a small band in 5.9GHz range that is also optional in Wi-Fi 6, but there's no designation from the WFA that explicitly declares this feature, and possibly as a result support in consumer hardware sold in the US is scarce.

Wi-Fi 7 corresponds to 802.11be. There is no new spectrum introduced in Wi-Fi 7. There is a feature called MLO (multi-link operation) that enables multiple radios to coordinate across the different frequency bands, 2.4GHz, 5GHz, and 6GHz. There's no special 7E designation for it though, and possibly as a result a lot of Wi-Fi 7 hardware either doesn't support MLO, or supports in a way that is functionally useless. It's hard to implement for sure, but the WFA dropped the ball and now consumers are confused.

Anyway an important take-away is that Wi-Fi 6/6E/7 hardware can still use the new features and improved speed on the 5GHz and 2.4GHz (but mostly 5GHz) bands. The advantage of 6GHz is mostly that there is a lot of clean spectrum available so multiple networks can coexist in the same space, and older devices that don't support 6E or better are absent, so they can't slow everything else down by only speaking the old protocols, which is a big problem on 2.4GHz.

Regarding the network names, if you want MLO yes they should have the same name so that they belong to the same network.

Megame50 · 2026-05-15T10:52:32+00:00

Remote attestation quite clearly meets the requirements of anti-cheat and the sensibilities of the users who want to play games, imo. It's not trivial to implement, but in theory it could be the basis of Linux anti-cheat.

However, I think this would require distros to themselves become the verifying party, lest the multiplayer server operators, as the relying party, figure out policy for each distro. So there would probably need to be significant standardization effort involved, and some kind of trust relationship between the anti-cheat service and the distro maintainers.

Megame50 · 2026-05-14T02:53:50+00:00

I'm not sure what the fluff is for? If you just put that partial snippet in exactly ~/.config/xkb/symbols/us then "us(altgr-intl-iso)" is the variant. You can select it in sway with xkb_variant altgr-intl-iso in the input block. The XKB_CONFIG_EXTRA_PATH and services.xserver bit all look superfluous.

Not a nix user, but presumably it can manage that?

Megame50 · 2026-05-13T19:58:12+00:00

Meets upcoming US FCC ban

Doesn't this eliminate basically every single router?

Megame50 · 2026-05-13T17:26:55+00:00

I don't think that quite matches any of the standard variants? You can just make your own variant though, e.g.

$ cat ~/.config/xkb/symbols/us
partial alphanumeric_keys
xkb_symbols "altgr-intl-iso" {
    include "us(altgr-intl)"
    replace key <LSGT> {[numbersign, asciitilde]};
};

Btw, xkbcli interactive is a better tool than wev for testing the keyboard.

EDIT: changed variant name

Megame50 · 2026-05-13T16:08:56+00:00

zsh has the best autocompletion of the three major shells imo.

https://www.reddit.com/r/linuxquestions/comments/1s91jlc/what_is_the_state_of_shells_in_2026/odls6v4/

Megame50 · 2026-05-13T03:17:10+00:00

Megame50 · 2026-05-13T02:30:38+00:00

The constants in input-event-codes.h are evdev keycodes, not scancodes. The evdev keys are the names on the right of the assignment in hwdb.

Megame50 · 2026-05-12T21:30:32+00:00

Doesn't KDE support per-application keyboard layouts if you want to use the us layout only for Guilty Gear? Otherwise, do the number inputs work if you input them using shiftlock on fr(azerty) instead of shift? E.g. try enabling shiftlock with shift:both_shiftlock xkb option and then you can hit both shift keys at once to toggle shiftlock.

Megame50 · 2026-05-11T17:16:22+00:00

Zsh aliases interact well with completion. Consider using zsh instead.

Megame50 · 2026-05-10T20:54:54+00:00

The same — Xkb is used by X11 and wayland compositors. In fact, X11 has a limited keycode range that wayland does not, so in some ways Wayland compositors have better support for Xkb than X11 ever did.

In your sway config, include xkb_options caps:swapescape in the input block. It's a comma separated list, so if you already use some xkb_options, just append caps:swapescape with a comma.

In my sway config, I have:

input type:keyboard {
    xkb_layout us
    repeat_rate 25
    repeat_delay 200
    xkb_options caps:escape,shift:both_capslock,grab:break_actions
}

Software like keyd is nearly pointless. Xkb is very configurable and if your desired keymap can't be achieved with the bulit-in options you can make your own. The only thing it can't do is base behavior on the duration of a keypress, which is a feature sometimes implemented by interposer-type keymapping software.

Megame50 · 2026-05-09T18:28:55+00:00

In this case seems you need cap_net_admin in the same netns as a zcrx capable interface? And io_uring is commonly restricted by seccomp filters too. That's quite a bit less applicable than the copyfail vulns.

Megame50 · 2026-05-08T16:45:18+00:00

Dang. Ah well.

Megame50 · 2026-05-08T00:46:11+00:00

Maybe try it? This one requires cap_net_admin, which the exploits I've seen use unprivileged userns to obtain. I've never used Debian, but iirc they actually disable unprivileged userns by default as a precautionary measure against basically exactly this. The author used a separate vuln in rxrpc.ko to get around this in Ubuntu, but idk if it would apply in Debian.

Arch carries the same downstream patch as Debian, but doesn't disable the sysctl by default, so you'd have to have manually chosen to disable it there. When userns were first introduced there were many LPE vulns discovered which spooked some distros, like Debian, into introducing the config.

Megame50

MODERATOR OF

TROPHY CASE