It’s also possible to have voltage issues on a device with multi-cell batteries.
My laptop charges on a type-C charger, but only if it can get 15+ volts. If it’s a 12V charger, that isn’t enough to push a charge into its battery. It will run on 12V but won’t charge at all, even if it’s off.
Well, Nvidia initially didn’t intend to support Wayland at all. They’re being dragged into it kicking and screaming, one step at a time.
Depends on what they actually need to do. When it’s a drive that’s working and they just have to image it and run some recovery software it should be pretty cheap.
Clean room repair of dead hard disks is a different story.
If there’s something really important on that disk, don’t do ANYTHING, just unplug it and hand it over to a data recovery company.
If there isn’t anything really important on there, go ahead and try and do it yourself.
Paying $100 to a data recovery company can save you a ton of headaches if it has the only copy of your thesis on there and you mess it up trying to fix things yourself.
I switched my laptop to Wayland about three years ago. AMD graphics, normal DPI 60Hz screen, doesn’t really do more than run a web browser.
My gaming desktop needed more of those troublesome edge cases hammered out - freesync in xwayland, app DPI scaling in xwayland, etc. I only switched it last year.
I’d argue the root cause was Nvidia insisting that X11 was the future, they’d never support Wayland, and refusing to participate in any of the design processes. As a result when they got dragged kicking and screaming into supporting Wayland, nothing that had been developed without Nvidia suited their hardware or drivers.
They first tried to throw their weight around by forcing EGLStreams on everyone, failed, and they’ve been scrambling to catch up ever since.
Well, kind of.
Linus needs to call out bad code, it’s an important part of Linux’s quality control. He doesn’t need to tell people to kill themselves.
That’s because their code quality is usually an absolute dumpster fire that only works if Wine exactly replicates obscure Windows bugs.
Man, I thought having more CPU cores was what made compile jobs faster, I’ve never tried compiling on more screens before. TIL.
Firefox only takes half an hour on my Ryzen 5800X desktop anyway. Modern CPUs can chew through those chunky compile jobs pretty quickly.
Yeah, if you want certain pages in certain screens it would work, and then they’d stay there
Window rules based on the application name and window title?
I’d call that one a ‘blue plate’.
If it’s open source it’s under the user’s control, so it’s almost impossible for a company to guarantee DRM is actually implemented instead of the device just claiming to implement it, decrypting the stream and not actually implementing any restrictions.
The whole point of DRM is to take control away from the end user so their device does what a company wants instead of what the device’s owner wants. If the user has control, you can’t have DRM.
I just tried it. Create a “Screen capture (PipeWire)” source, there’s a popup asking you to pick a display or “Full Workspace” which shares everything.
Those can do the heavy lifting, but OBS still has to ask them to do it.
Yeah, some things check DPI when they start and then won’t respond to changes or receive new environment variables. A reboot makes sure everything is using the newest settings.
No, my KDE panels work fine, so that’s not the issue.
Tried restarting?
If stuff is designed for big servers that run Linux, it’s easier to get it to run on a desktop PC if the PC runs Linux too because then it’s the same thing except much less powerful.