![\"\"](\"https:\/\/www.foell.org\/justin\/files\/2019\/10\/img_6518.jpg\")
<\/a><\/figure>\n\n\n\n\n\n\n\nThe light at the bottom\/front of the case isn’t well explained. It turns solid white during charging. It blinks white occasionally and what that means still remains a mystery \u00af\\_(\u30c4)_\/\u00af<\/p>\n\n\n\n It for sure goes amber when there’s 10% or less battery life remaining.<\/p>\n\n\n\n Here are other settings in detail that I did in other posts:<\/p>\n\n\n\n The boot time on this laptop is strangely long – consistently 2 mins 20 seconds before I would see the login screen. I changed the grub configuration so I could see what the hold-up was by pressing escape on the splash screen<\/a>. I also used Update:<\/strong> I had to add the “normal” localhost addresses for Then I applied the change with It’s not immediately apparent that the loopback alias is available from looking at Because I’m running Wayland, apps that you can normally start with Here’s one solution<\/a>, but I instead put the file in My Microsoft Mouse 3600<\/a> seemed slow at first, so I turned the mousepoll up to maximum<\/a> velocity. I’m not sure if it’s 100%, but I do think it feels better.<\/p>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\nSettings Reference<\/h2>\n\n\n\n
Windows<\/del> Linux-X\/C\/V key combinations for Cut\/Copy\/Paste<\/a>.<\/li>Boot time<\/h3>\n\n\n\n
systemd-analyze blame<\/code><\/a> to confirm what I saw: the network.service was taking too damn long. Turns out it was my fault. Ubuntu 18.04 introduces a service called netplan<\/a> to handle network adapter configuration. I had added a loopback alias like I normally do the old way<\/a>. Netplan didn’t like that, so I removed my lo:0<\/code> entries from \/etc\/network\/interfaces<\/code> and added the following netplan configuration<\/a> file:<\/p>\n\n\n\nsudo vi \/etc\/netplan\/02-loopback-alias.yaml<\/code><\/p>\n\n\n\nnetwork:\n version: 2\n renderer: networkd\n ethernets:\n lo:\n addresses: [ 127.0.0.1\/8, \"::1\/128\", 10.254.254.254\/32 ]\n<\/pre>\n\n\n\n
lo<\/code> as well. Without them in Ubuntu 20.04 when I would resume after suspend\/sleep lo<\/code> would come back online with only 10.254.254.254<\/code>. Then DNS wouldn’t work because connections to 127.0.x.x<\/code> for resolved & dnsmasq<\/a> would not work.<\/p><\/blockquote>\n\n\n\nsudo netplan apply<\/code>. Boot time went from over two minutes to under 20 seconds.<\/p>\n\n\n\nifconfig<\/code>. Instead use ip address<\/code> to confirm it’s there:<\/p>\n\n\n\n1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000\n link\/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00\n inet 127.0.0.1\/8 scope host lo\n valid_lft forever preferred_lft forever\n inet 10.254.254.254\/32 scope global lo\n valid_lft forever preferred_lft forever\n inet6 ::1\/128 scope host \n valid_lft forever preferred_lft forever\n<\/pre>\n\n\n\n
X Applications that Require Root (sudo)<\/h3>\n\n\n\n
sudo<\/code> (like synaptic) will give this response on the command line:<\/p>\n\n\n\nUnable to init server: Could not connect: Connection refused
\n(synaptic:29383): Gtk-WARNING **: 13:31:07.736: cannot open display: :0<\/code><\/p><\/blockquote>\n\n\n\n~\/.config\/autostart\/xhost.desktop<\/code>.<\/p>\n\n\n\nBluetooth Mouse<\/h3>\n\n\n\n
Deep Sleep<\/h3>\n\n\n\n