![]() ![]() Perhaps iptables or your kernel needs to be upgraded. libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.4.0-43-Microsoft/'\nmodprobe: WARNING: Module xt_conntrack not found in directory /lib/modules/4.4.0-43-Microsoft`, error: exit status 1"Įrror starting daemon: Error initializing network controller: error obtaining controller instance: failed to create NAT chain: iptables failed: iptables -t nat -N DOCKER: iptables v1.6.0: can't initialize iptables table `nat': Table does not exist (do you need to insmod?) Time="T12:07:23.227671600 01:00" level=warning msg="Running modprobe xt_conntrack failed with message: `modprobe: ERROR. libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/4.4.0-43-Microsoft/'\nmodprobe: WARNING: Module nf_nat not found in directory /lib/modules/4.4.0-43-Microsoft`, error: exit status 1" Watching docker logs I found this: level=warning msg="Running modprobe nf_nat failed with message: `modprobe: ERROR. I've installed Docker on WSL following the steps given to install Docker on Ubuntu but when I execute docker ps I get the following error: docker psĬannot connect to the Docker daemon at unix:///var/run/docker.sock. Windows Subsystem for Linux (WSL) currently has very limited support for. If Xscreensaver's DPMS is off, all is well if it's on, I get this weird behavior.I've tried to run Docker on WSL unsuccessfully. sudo apt purge xfce4-power-manager xscreensaver gnome-screensaver light-locker. I have been able through a process of elimination to narrow down the issue to turning off and on Xscreensaver's power management features. ![]() The only remotely relevant and reasonably close in time I can find is an upgrade of xdg-utils from 1.1.0~rc1 git20111210-6 deb7u1 to 1.1.0~rc1 git20111210-6 deb7u2 about a week before when these problems seem to have started. Old logs don't reveal anything useful the most recent upgrade I did before this apparently started was related to MySQL. I probably made some change when this started, but I'm at a loss as to what that change might have been. May 10 02:21:04 yeono acpid: input device has been disconnected, fd 9 cations, and other subsystems before handing the computer to a new employee. May 10 02:20:47 yeono acpid: input device has been disconnected, fd 9 Running Commands with the Push of a Button. May 10 02:20:17 yeono kernel: input: Unicomp Inc G SpaceSaver as /devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1.2/1-1.2:1.0/input/input52 You should find the xscreensaver application in your Preferences menu (depending upon which desktop you are using. Aside from the regularly flickering light being rather annoying and this obviously nullifying any power savings, it also fills up my system logs with keyboard disconnection and reconnection log entries from the USB subsystem: May 10 02:20:13 yeono acpid: input device has been disconnected, fd 9 However, something is causing the monitors to then start turning fully off, and back on, repeatedly. Then sure enough the monitors do enter power savings mode in accordance with those timeouts, as expected. If I change Xscreensaver's power management settings to the following: Both monitors are connected directly to the computer with no intervening USB hub. My keyboard is hooked up through the USB hub built into one of the monitors, and the mouse is hooked up through the USB hub built into the other. Here is what xset q has to say about DPMS with the above-mentioned settings: DPMS (Energy Star): I'm running Xfce 4.8 and in its Power Manager have set "Put display to sleep" and "Switch off display" to Never in both the "On AC" and "On Battery" settings categories. By the way, i don't use a systemd service at all. A cleaner solution for xscreensaver would be to implement the systemd events directly instead of using another daemon. When I disable power management through the Xscreensaver configuration tool, by unchecking "Power Management Enabled" in the Advanced tab, then everything works fine, except of course I don't get any power management on the monitors. If you want to react to that, you'll have to register your screensaver for that event, which you can do with xss-lock. I have two Dell U2412M monitors hooked up to a single graphics card (one over native DVI and one over HDMI output to DVI input). One of the convents applications of this device its a login screen. Something weird is up with my Xscreensaver 5.15 configuration on Debian Wheezy. This month I moved to YubiKey as a authentication token for my personal daily usage. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |