You are not logged in.
The computer turns off from the power supply; it does not know any sleep modes from birth. smile
The issue JWM-Kit references likely doesn't affect you if you're running Windows 7. As far as I can tell, Windows' "fake shutdown" "fast startup" was implemented starting in Windows 10.
For those unfamiliar with this "feature," here's how it works. When you tell Windows 10+ to "shut down," it just... lies to you. It instead invokes sleep state S4, aka hibernation or suspend to disk. Whether or not you pull the plug at this point has no bearing, as power is not required in S4, because the system state has been saved to non-volatile memory. If you want Windows to actually shut down, you need to hold down Shift when you select the shut down option. Fast startup can also be permanently disabled in Power & sleep settings.
Mike, the line you quote is prepended with a '#', that means it is commented out, and therefore not functional. You need to delete the '#' to enable it.
I've been experiencing the same issue whenever one of my machines was disconnected from the network, but I wasn't sure what was the cause, as sudo has never behaved this way in the past. Thanks to your suggestion, I just found and un-commented the 'probe_interfaces false' line. While that did away with the error message, I'm still getting a long timeout before the command executes. So something else is apparently still misconfigured.
Thanks for the info, everyone. I was dreading having to install PA, but some applications absolutely require it.
Does anyone know if PW supports CLI control in the same way as PA, for example, with pactl & pacmd? I need it for my volume hotkey scripts, among other things. More on PA CLI control here:
https://shallowsky.com/linux/pulseaudio … -line.html
You still need the non-free nvidia firmware to use certain video acceleration features with the nouveau driver. It's discussed here:
https://nouveau.freedesktop.org/VideoAcceleration.html
The noveau driver also lacks support for a number of other features present in the proprietary driver, most notably compute. Some cards don't even have 3D support at this time. More info here:
https://nouveau.freedesktop.org/FeatureMatrix.html
I use nouveau because it does everything I need it to do, but my needs aren't all that demanding.
Apparently dpkg started displaying a warning about this issue to users sometime last year, I'm not sure if it still does. Someone filed a bug report about it last year:
https://bugs.debian.org/cgi-bin/bugrepo … 994388#132
More discussion at lwn.net, including a comment from the responsible party, and some critical responses:
https://lwn.net/Articles/889026/
I can't vouch for the accuracy of the comments, but one person in the lwn.net thread posted the following:
There is no actual breakage. Apart from a few minor issues that were fixed long ago, everything else is purely theoretical constructions that nobody has ever seen outside of manually-crafted examples in the 3 years this has been the default for new Debian and Ubuntu installations... The reality is that you personally don't like the change. Which is cool. And it appears you are using your position to try to block it and retroactively justify it using old dpkg bugs, giving yourself a veto over the technical committee.
I'm using Firefox ESR from the repository on Excalibur with only ALSA installed, no PulseAudio or PipeWire. I didn't need to edit any configuration files. Is this a new feature? I seem to remember having to install PulseAudio to get Firefox audio in the past.
eudev apparently tries to find egrep in /bin and I had only added a symbolic link for /bin/grep to /usr/bin/grep at the time.
I may have encountered this issue today when I upgraded Excalibur on a couple of different laptops. I saw some eudev errors during boot, but I wasn't able to find any related info anywhere in /var/log. Is there somewhere else these errors might have been logged?
Anything that accessed the display backlight had stopped working: console blanking no longer turned off the backlight, and brightnessctl couldn't find the display. Also, I'm not sure if it was related, but X would no longer start with the modesetting driver. Oddly, it still worked with the Intel and nouveau drivers (on different machines.)
I went ahead and installed the usrmerge package. It failed on the first pass, but I got lucky, and only had to delete a few relatively unimportant files to get it to finish. Everything seemed to be working normally again on the next boot, with no errors reported.
Edited to add: I just ran usrmerge on the second laptop with zero errors, which was a pleasant surprise. The backlight is working again on this machine as well; however, a Minecraft server is still failing to start, so it appears I still have other issues. The Minecraft issue was due to a Java update, and unrelated to usrmerge. All is now working on this system as well.