News for hackers. Stuff that matters.
Re:Do not leave XPS laptop in any sleep/hibernate/standby mo... by fxtentacle on Friday September 24, 2021 @05:12PM (#28647887)
> Why a person would ever walk away from a computer without saving is beyond me.

In my case, it was mostly executables that I'm in the process of debugging and stepping through. I'm not aware of any debugger which can save and restore open file handles.

> I just feel like a lot of the problems people have with Windows 10 aren't really in the software, but are between the keyboard and chair.

I would have argued just like you before I encountered the cursed tablet. That thing had an integrated battery, so no matter what you tried, it could still turn on by itself if it wanted to. The only reliable way to make it stop making noises in the middle of the night was to thoroughly drain its battery.

That said, the Dell XPS support post that I commented on is by itself pretty detailed about all the issues that Dell machines are having with Windows 10. I think you'll believe me that Dell wouldn't publicly post that unless they had a lot of support requests related to it. So it's apparently a widespread issue.

Re:Do not leave XPS laptop in any sleep/hibernate/standby mo... by Terr_ on Friday September 24, 2021 @05:42PM (#28648145)
> executables that I'm in the process of debugging

In my case, virtual-machines. When Windows 10 decided it had to reboot, it would kill them dead. You can't quicksave those, and even if you did they have a higher-than-normal chance of not coming back up cleanly.

Re:Do not leave XPS laptop in any sleep/hibernate/standby mo... by PeterisP on Saturday September 25, 2021 @10:35AM (#28653505)
That's interesting, I usually treat the ability of easily snapshotting and restoring virtual machines as one of the main reasons for doing things inside a VM.
Re:Do not leave XPS laptop in any sleep/hibernate/standby mo... by Terr_ on Saturday September 25, 2021 @10:02PM (#28657768)
I believe some of the Ubuntu ones would occasionally just not recover correctly, some kind of video-card issue most likely.

In any case, Win10 did not signal VirtualBox to save state -- or else didn't give it enough time -- so I would occasionally come back to my office to find everything I was working on gone due to some mystery-reboot that I didn't recall scheduling.