10·
22 days agoYes. They’re live, so feel free to ask them about it. They can explain it much better than I ever could.
KDE Plasma is the only desktop with a functional screen reader on Wayland and even then its limited. Other than that, KDE has a magnifying glass setting bound to
Super++/-/0you can enable.
Perhaps if you LoL players want to see it succeed you could come together and create a fund to pay an actual professional to make the assets for the game.
They promised so a while back, some time just after first introducing the Steam Deck. They’re keeping that promise.
Valve did promise us that they were going to improve VR support on Linux quite a while back, good to see that they’re keeping that promise.
I will warn you that her Live streams are really technical low level coding, though in her next stream she’ll be testing games and stuff so it’ll be a little bit more entertaining than usual.
If you’re interested in that kinda stuff, it’s a gold mine for learning and she does answer questions from the chat. Also, some pretty notable developers will show up to the live streams from time to time and hangout in chat.
I enjoy it. ☺️
Np. I forgot to add the stream link, that’s my bad. Kinda stayed up all night for Lina’s live stream.
Yes, literally the end of her last Livestream.
https://youtu.be/qTj60x9eMu4?t=5h58m39s
Just wait and see how good those drivers are first.
AMD given nvidia having a better performance to cost ratio
When the fuck?
and the fact that they have the potential for HDMI2.1 support which AMD doesn’t have a solution to yet.
An open source solution exists for Intel, the way it works is just by a translation layer between HDMI & DisplayPort. I imagine AMD will do the same thing.
123·2 months agoHell yeah!! So many needed fixes that have been bugging me for a while are finally fixed!!
Why should we have the same standard for two fundamentally different languages with distinct design philosophies and features?
Even if the C coding standard was used, it fundamentally will not make Rust more legible to C-only kernel devs. Imposing the C coding standard on Rust would be fundamentally counterproductive, as it would undermine Rust’s safety and productivity features. Rust’s coding guidelines align with its design principles, promoting idiomatic Rust code that leverages language features like ownership, borrowing, and lifetimes.
This ensures that Rust code in the kernel is safe, concurrent, and maintainable, while adhering to the language’s best practices. While the C coding standard served its purpose well for the procedural C language, it is ill-suited for a modern language like Rust, which has different priorities and language constructs. Having separate coding standards allows each language to shine in its respective domain within the kernel, leveraging their strengths while adhering to their respective design philosophies. Having separate coding standards for C and Rust within the kernel codebase is the sensible approach.
In any case, it’s the temporary file directory so it should be fine to delete them manually.
Just make sure that podman isn’t running while you’re deleting them, assuming it is podman.
This error is caused by a compatibility issue between Wine’s RandR (X11 display extension) implementation and the NVIDIA proprietary drivers.
a. Install winetricks and run
winetricks orm=backbuffer glsl=disableThis will configure Wine to use a different rendering method that is compatible with the NVIDIA drivers.&/Or
b. Use a tool like Q4Wine to configure the Wine prefix and set the “UseRandR” option to “N” This will disable Wine’s use of the RandR extension and use a fallback method instead.
That should fix it.
Not really, the source is more about the entire concept in computer science. It’s extremely comprehensive, for those who want to know it inside and out. TLDR : Ring 0 means anything directly controlling the hardware, which is usually the kernel. There’s also rings beyond zero that are reserved for specific things, for example -1 for hypervisors like KVM & Hyper-V.
Specifically it’s at Ring 0.
What’s the WINE error message you get with the proprietary driver?
Font rendering is complex and depends on several settings and features lining up perfectly. Anti-aliasing, DPI, fractional scaling, hinting, and subpixel rendering are all important factors that contribute to the quality and appearance of text on a digital display.
On KDE plasma the fractional scaling also plays a role in text rendering. Then there’s also the “Legacy Application Scaling” for X11 apps on the Wayland session.
Windows native games are shown…