Note: the pipewire-codec-aptx comes from rpmfusion also if you own one of those Sony WH-1000XM* headsets who dont support HSP Audio Gateway ( hsp_ag ), you need to remove that role from the bluez5.headset-roles line.
@johannbg does the package provide only the original AptX codec or its enhanced versions such as AptX HD? IMHO the original AptX codec doesn't have any advantage over what is already available in Fedora SBC-XQ, AAC, LDAC.
I had a nice trip with @sesivany from Prague to Brno. We just found out at the #Fedora 40 release party yesterday that we were taking the same train. We shared travel stories and Jiří gave me some good advice for my trip. Děkuji
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.
@aral Again, I agree that accessibility is of utmost importance and that cultural changes are needed to emphasize it from the beginning. I just think systems that need some non-default configuration for a functional screen reader are importantly different than "operating systems without a functional screen reader".
Both X and Wayland have limitations that in some use-cases make them not viable. Until Wayland catches up, we each get to decide if we prefer Wayland's bugs or X's bugs.
@LiberalArtist All I’m saying is that if you believe that, then shipping with Wayland without monitor support is also different than “operating systems without functional monitor support.” (Unless your point is that there are different criteria for what is acceptable for sighted people – which, clearly, is the case because those operating systems are shipping with monitor support by default but without screen reader support.)
Homebrew is now installed for you with the latest images of Bluefin, Aurora, and Bazzite. We don't have to strongly recommend installing it anymore because it's right there!
Homebrew is a great package manager especially for CLI apps. Give it a whirl if you haven't already.
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.
PSA: Fedora Linux 38 will reach end of life on May 21, next Tuesday.
Time to start upgrading. Fedora 39 will be supported for up to one month after the release of Fedora 41 (~6 months). Fedora 40 will be supported until a month after Fedora 42 (~12 months).
Why dnf upgrade on #Fedora 39 shows me red lines of packageName replacing packageName (name being the same), but only for some? I know a thing or two on Linux #packaging, but not RPM.
@autkin One is being added (wireshark) one is being removed (vga).
It does this because there is likely a conflict somewhere along the line. It's nothing to worry about and completley normal. All package mangers do it. Yours just has color coding so you are a bit more informed.
I decided to try building #FreeCAD from source. I used a F39 toolbox on my #Fedora 40 #Silverblue and installed the prereqs; most from packages, but pyside2 from pip (inside the toolbox) since it hasn't been packaged in Fedora for years. The segfault I'm getting from libshiboken isn't illuminating to me. I could imagine a missing dependency on a package causing a segfault, or maybe no one is building FreeCAD on Fedora and it just doesn't work on F39. 🤔
Not clear that I'm close enough to the beaten path for this to be worth a bug report, though. Quite likely PEBCAK...
@garrett Yeah, it's the same pyside2 problem I ran into in toolbox. Pyside2 has been dropped from Fedora, I think that was because it's not working on current Python.
I think this is a temporary state, and when FreeCAD moves to Pyside6 along with the Qt6 framework, it will be easier. But that's not going to come before FreeCAD 1.0 I think.
So I think at least currently I'll start from a Debian container since @yorik is using Debian.
@yorik Building and running it in a debian:latest container is working, thank you! I used both shiboken and pyside as packaged, not using pip. The current docker build instructions are missing three packages. But one seems to have been intentionally removed, so I just put the information in github for someone who knows what's intended to decide what to do about it.