This is great but can we please also have Fedora (& Ubuntu, etc.) acknowledge they started shipping operating systems without a functional screen reader when they switched to Wayland and that that’s still the case?
This is not to name and shame. Unless we acknowledge this as an error on par with shipping without monitor support and unless the culture is altered to make accessibility a showstopper, it’ll happen again.
'" The data shows that “frozen” vendor #Linux kernels, created by branching off a release point and then using a team of engineers to select specific patches to back-port to that branch, are buggier than the upstream “stable” Linux #kernel created by Greg Kroah-Hartman. '"
@vegard@kernellogger "a team of engineers" COULD do that (hint, Android does, by just taking the stable updates), but the paper shows that a specific "team of engineers" currently does NOT do that, which puts the users of those kernels potentially at a greater risk.
Read the paper, it's interesting.
Disclosure, I read it before it was published, but had no influence on it at all.
@kernellogger as usual, the point is not that these are bug free, but that they are regression free. The kernel upstream releases break userspace on every new release, and kernel maintainers don't care. See https://github.com/torvalds/linux/commit/a1912f712188291f9d7d434fba155461f1ebef66 for example, as Daan just found out, which removed a mount option without caring that it is still being used, so since 6.8 every btrfs device can no longer be mounted by systemd
#!/usr/bin/env python
import datetime, os, sys
for line in sys.stdin:
line=line.strip().split(' ')
print(datetime.datetime.fromisoformat(line[0]).astimezone(), ' '.join(line[1:]))
I was Nobara user, then I am using Fedora right now. I want to use things like Hyprland etc. and ya know, Its damn cool to say I am using arch btw. So I’ve decided to use Arch Linux. But everyone says its always breaking and gives problems. That’s because of users, not OS… right? I love to deal with problems but I don’t...
Wie kann ich in /etc/network/interfaces in #Debian es einstellen, dass auf allen Interfaces #DHCP gemacht wird, auch wenn ich jetzt noch nicht weiß, wie das Interface in Zukunft heißen wird?
Jetzt steht da halt:
iface enp1s0 inet dhcp
Aber auf einer anderen Hardware heißt das Ding ja vielleicht eth0 statt enp1s0...
Also was tun?
Brauch ich ein Startupscript, dass die Config generiert?
@adamsdesk This is actually fantastic, I'm relatively new to git and have been just randomly opening files in .git till I found the origin URL. Also thank you for providing a fish function too!
Big news! Winamp's source code will be available on September 24!
This release invites developers worldwide to contribute to its evolution to help create the perfect player for Windows users
I hope also #Linux#Developer get into the project.
For Global Accessibility Awareness Day, we want to recognize the work being done on accessibility by @matt as part of the @gnome Foundation. He is the lead for @accesskit and is currently working on Newton, a Wayland-oriented solution for assistive technologies that can modernize accessibility on the Linux desktop!
The Fedora Accessibility Working Group is looking to work closer with upstream as we aim to improve accessibility on Fedora. If you are interested in joining, participating, collaborating, or sharing your experience, please reach out with the Fedora DEI tag on our forum.
