systemd 257-rc1 Released With A Ton Of New Features & Changes

[cutterjohn]

🍿🍿🍿🍿🍿 <- grab one it is open corn for everyone

grabbing one, but only to see if the discussion can color within the lines... or IOW if the train can stay on the tracks.... or some other sort of metaphor...

[cutterjohn]

I spent way too many hours last weekend trying to figure why my all AMD Zen 4 system was hard crashing when resuming from sleep on kernel 6.11.x. After lots of farking about with UEFI settings, different AMD GPUs, etc., I eventually found this systemd issue thread...

https://github.com/systemd/systemd/issues/33626

Looks like there are some bugs between 6.11 and systemd 256. I love the 'we know basic functionality is badly broken for some people, but we decided to not change our behavior in hopes that the kernel will fix their bugs eventually' response .

HEY! I had this but I changed my keyboard! (I remember that now) and it stopped crashing on resumer from sleep! Thanks for the extra research, as the only thing that I like about the replace kb is the LED backlighting(GREEN!, low intensity), rather go back to my unicomp model m, 104 classic... Im missing the clack clack clack as I got mushy mech switches in the replacement.... and Im not really sure that LED backligting on the kb is worth it... oh crap Im derailing the thread....

[usta]

grabbing one, but only to see if the discussion can color within the lines... or IOW if the train can stay on the tracks.... or some other sort of metaphor...

all we need is a system-colord , system-traind and system-systemd [ btw i do love systemd ]

[cutterjohn]

all we need is a system-colord , system-traind and system-systemd [ btw i do love systemd ]

I had momentarily forgotten but was referring to the 'fieldbus' removal, which generated 6+(?) pages of comments w/c. 5 being ontopic... OK Im done Im NOT going to derail this thread or color outside of the lines any longer...

[toves]

A worthy successor to Where's Wally.

Name a function, service or feature that systemd hasn't claimed to have implemented.

If I wanted to trojan almost every Linux system running today, systemd would be the go to target.

[intelfx]

If I wanted to trojan almost every Linux system running today, systemd would be the go to target.

How about Linux kernel?

[Espionage724]

HEY! I had this but I changed my keyboard! (I remember that now) and it stopped crashing on resumer from sleep! Thanks for the extra research, as the only thing that I like about the replace kb is the LED backlighting(GREEN!, low intensity), rather go back to my unicomp model m, 104 classic... Im missing the clack clack clack as I got mushy mech switches in the replacement.... and Im not really sure that LED backligting on the kb is worth it... oh crap Im derailing the thread....

Go for a QMK firmware keyboard and have RGB patterns on the keyboard itself! I don't think it's QML but I have a Hi75 and along with somehow feeling and sounding like typing on hard-candy clouds, I'm not sure how I was typing on the Corsair K70 I came from for years (literally feels like hard-pressure bricks ).

But having several RGB patterns on the keyboard itself is so much nicer than dealing with the... probably-comparably-worse-than-systemd Corsair iCUE software that last I checked early-V5 was shy of being a 1GB compressed driver download to control RGB lights with a GPU/RAM eating background daemon (OpenRGB wasn't ideal on Windows iirc; ckb-next on Linux was tolerable and minimal); and saves USB/CPU bandwidth by not having the OS doing the RGB. Basically, I'm not entertaining keyboards that need software to control RGB and now know it's possible!

I had a Model M for a bit; missed the Super key initially but for GNOME I re-bound that to bracket [ and was fine with that

[pWe00Iri3e7Z9lHOX2Qx]

Bugs have to be fixed where they happen (i.e., in the kernel), not papered over where it's most convenient in the short term.

If you demand zero bugs or a short-term-optimal response to them, use a stable / QA-ed distribution (and probably pay for that privilege).

I agree in general. I'd argue that there are certain basic capabilities that warrant thoughtful consideration of the actual impact to end users though, with functioning sleep falling into that bucket. Whether you are worried about filesystem corruption / data loss from repeated forced hard power offs, or near self-immolation of your "oops I'm not really sleeping" or "oops I woke up" laptop in a bag, totally broken sleep can cause a bunch of very unpleasant problems. I'm hoping they figure out any remaining issues before 6.12 flips to LTS.

[onlyLinuxLuvUBack]

Next systemd version should be released with no new features but just with most of its more than 2000 issues resolved: it would be a great release

just merge all code into 1 file and feed it to ai and have it rewritten in rust.

[caligula]

Surely you meant to say "distros with a shitty libc"?

Maybe you should read more about the topic. Glibc has lots of issues with code quality.