On 7/11/22 14:28, Patrick O'Callaghan wrote:
On Mon, 2022-07-11 at 11:21 -0700, ToddAndMargo via users wrote:
On 7/11/22 08:44, Patrick O'Callaghan wrote:
On Mon, 2022-07-11 at 09:09 -0500, Michael Hennebry wrote:
On Sun, 10 Jul 2022, ToddAndMargo via users wrote:
Not to ask too stupid a question, but I notice problems like these after I do a `dnf upgrade`. Have you tried the universal Windows cure-all solutions and rebooted your computer?
Thanks. I have sound now.
I often have rather a lot of files open. I won't do a killall gvim until I've ascertained that none need saving. I won't do the reboot until important external media have been removed. When I'm already having trouble, I prefer not to rely too much on how things are supposed to handle their death throes.
BTW I'd thought reinstalling was the Windows cure-all.
Rebooting, not reinstalling.
In case it wasn't obvious, I was merely pointing that Michael had misread the previous post, which mentioned rebooting, not reinstalling. That's all.
It is worse than you think. One of the unethical things M$ does is called Fast Boot (Fast Startup). Basically when you think you have shutdown, you have only exited your programs and suspended. So when you, haha, power back up, "Look see how fast it boots!" and you get back all of the sins of the past.
So basically hibernation. I'm not fan of MS, but isn't it a bit of a stretch to call it "unethical"?
poc
No stretch at all. Shutdown means to shutdown, not to hibernate/suspend. M$ is lying to its customers so they can brag about how fast their stuff boots.