According to Ubuntu Security page, the linux project in Bionic and Focal has a status of "Needed". I'm assuming this project refers to linux-generic in the APT repository, so linux should be 4.15 in Bionic and 5.4 in Focal. I also made a brief test on Ubuntu Focal with linux-image-5.4.0-100-generic (amd64) and failed to exploit. Thus I assume Bionic on 4.15 is also unaffected.
So why is it still shown as "Needed" for Bionic and Focal?
I have migrated my Ubuntu Focal server firewall backend from legacy iptables to netfilter, by running update-alternatives --set iptables /usr/sbin/iptables-nft and rebooting the server. Now all tables shown in iptables-legacy -S are empty, but when I run iptables -S the last line always says:
# Warning: iptables-legacy tables present, use iptables-legacy to see them
I have since removed iptables-legacy from alternatives using the following command:
update-alternatives --remove iptables /usr/sbin/iptables-legacy
And now only the netfilter version is shown
root@iBug-Server:~# update-alternatives --display iptables
iptables - auto mode
link best version is /usr/sbin/iptables-nft
link currently points to /usr/sbin/iptables-nft
link iptables is /usr/sbin/iptables
slave iptables-restore is /usr/sbin/iptables-restore
slave iptables-save is /usr/sbin/iptables-save
/usr/sbin/iptables-nft - priority 20
slave iptables-restore: /usr/sbin/iptables-nft-restore
slave iptables-save: /usr/sbin/iptables-nft-save
How can I get rid of this warning?
I'm planning a system upgrade from Eoan to Focal on a remote machine where I only have SSH access. I've previously dealt with broken packages causing the system to boot into rescue mode, so I want to ensure whatever happens I can keep my access to the server. To further secure the process, I'm doing a rehearsal using a local virtual machine running the target system.
With my knowledge in Ubuntu, I did the following tasks beforehand:
systemctl edit ssh.service and insert DefaultDependencies=no to [Unit] section and WantedBy=rescue.target to [Install] section, then systemctl enable ssh.service. Systemd reports "created symbolic link".systemctl edit rescue-ssh.target and insert WantedBy=rescue.target to [Install] section, then systemctl enable rescue-ssh.target.Then I edited grub to enable boot menu, update-grub then systemctl reboot, and use e to edit the default entry. I scrolled down to the first linux line and appended rescue and booted this entry with Ctrl-X, which led to this screen:
Everything seems fine here as I can SSH into this VM right at this point.
My question begins:
I tried again in a different way to test SSH availability in rescue mode. First I booted the system normally into graphical mode (with GNOME and whatever), started a terminal and ran systemctl isolate rescue.target. I see the same prompt text again, but when trying to SSH into the VM, I got the following result:
ubuntu@WSL:~ $ ssh root@vmwares
Warning: Permanently added '192.168.2.5' (ECDSA) to the list of known hosts.
Timeout, server 192.168.2.5 not responding.
255|ubuntu@WSL:~ $
Running systemctl status ssh.service highlighted the following text:
pam_systemd(sshd:session): Failed to create session: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Restarting systemd-logind.service makes no difference. Going back to graphical interface with systemctl isolate default.target brings everything back to normal again.
Question: Why can't I login to SSH when the rescue target is isolated from graphical.target? How to I resolve this?
I think there's something to do with "isolating targets", but apparently things have gone beyond my knowledge.
I'm trying to setup a box as a remote server and am stuck configuring VNC server now.
The box has no discrete GPU and is running on UHD Graphics 630 shipped with Core i7-8750H, and it's set up with Ubuntu 19.04 (Disco Dingo) and an active internet connection (no firewall so far). There was a monitor during the initial setup (OS installation etc.), but has since been removed (the box itself was moved to another place), so it's only accessible via SSH now.
I installed LightDM, X11VNC and xserver-xorg-video-dummy, and configured a dummy display, mostly following this answer.
I connect this headless box with RealVNC (on my Windows PC) and entered my password on the login screen, and got a black screen with only the wallpaper and nothing to interact with.
I'm trying to find out a way to get a functional desktop environment, something like this:
This VNC server works perfectly fine if I attach a monitor to the box and login with another physical keyboard attached together, but this is not applicable anymore after the initial setup because I intend to use it as a remote server with internet as the only external I/O device. (And this is how I grabbed the above screenshot.)
I suppose this issue would be identical with Bionic (18.04 LTS) and Cosmic (18.10).
I'm learning the CLI interface of Advanced Packaging Tool. From the output of apt(8) when its stdout isn't a terminal, it isn't suitable for "scripts expecting stable programming interface", so I'm taking a look at apt-get(8).
One difference between apt update and apt-get update is that the latter is missing a final line after all cache has been updated:
8 packages can be upgraded. Run 'apt list --upgradable' to see them.
I want to know how I can get this exact line displayed with apt-get(8).
I created a dd if=/dev/sda image on an NUC running a possibly customized Ubuntu 15.04. The NUC has 2 GB RAM, 16 GB SSD and runs on Intel Celeron 1037U.
I created a new virtual hard disk and dd'd the image to that virtual hard disk in another running system, and then created a new virtual machine on this restored virtual hard disk.
The problem I'm having is, the virtual machine does not start normally and gets stuck at this screen. The Last login line updates every 15 seconds. By examining $HOME/.profile, it seems it's stuck at this line:
exec startx &> ~/.xsession-errors
Checking the logs it appears like that the display (screen / monitor) has changed and Xorg doesn't work with that, but I am not 100% sure.
Here's the tail of the file /var/log/Xorg.0.log
[ 54.521] (++) using VT number 1
[ 54.521] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[ 54.521] (WW) xf86OpenConsole: setsid failed: Operation not permitted
[ 54.521] (WW) Falling back to old probe method for modesetting
[ 54.521] (WW) Falling back to old probe method for fbdev
[ 54.521] (II) Loading sub module "fbdevhw"
[ 54.521] (II) LoadModule: "fbdevhw"
[ 54.521] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 54.521] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 54.521] compiled for 1.17.1, module version = 0.0.2
[ 54.521] ABI class: X.Org Video Driver, version 19.0
[ 54.521] (WW) Falling back to old probe method for vesa
[ 54.521] (EE) No devices detected.
[ 54.521] (EE)
Fatal server error:
[ 54.521] (EE) no screens found(EE)
[ 54.521] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 54.521] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 54.521] (EE)
Note: I am able to attach this virtual disk to another VM and chroot into the system inside and investigate for issues. I have managed to install open-vm-tools after chroot-ing into the system but still same problem.
How do I boot this VM up?
I installed PyPy3 via sudo snap install and when I'm installing packages, I get this error:
OSError: [Errno 30] Read-only file system: '/snap/pypy3/2/site-packages/easy_install.py'
I tried finding the mount point and remounting with sudo mount -o rw,remount but to no avail:
mount: /snap/pypy3/2: cannot remount /dev/loop11 read-write, is write-protected.
I want to mount some directories under /snap as RW.
I'm trying to install Bionic Beaver 18.04 LTS in VMware Workstation 14. The host is Windows 10 Enterprise v1709 64-bit.
I downloaded the ISO from release.ubuntu.com and I used tools to check the checksums to ensure that the file was downloaded correctly. Then I opened VMware and created a new virtual machine.
In VMware, I selected "Typical (recommended)", then "I will install the operating system later" (I don't want Easy Install this time, but it's the same - it still blackscreens), then went through a few steps as usual. I set VMware to store the virtual disk as a single file and set it to 32 GB.
After creating the VM, I increased the memory to 4 GB (VMware defaults it to 1 GB after detecting Ubuntu 64-bit) and processor core count to 4 (VMware defaults it to 1), deleted the printer and inserted the ISO file as "CD/DVD". I left all other settings as their defaults. Then I started the VM.
It went through a few screens that are familiar to me, and nothing showed up after hearing the familiar "drum" sound. I only have a mouse that I can move in and out of VMware.
Any help?
I'm running Windows Subsystem for Linux and the color in Windows console is bad. I like the color palette in Ubuntu 16.04 very much. I've already known how to change the colors in a Windows console, and all I need is the colors from Ubuntu terminal. I use 16.04 with its default desktop environment, ubuntu-unity. What's the colors' RGB values in the default terminal? Foreground colors and background colors.
echo -e "\e[30;1mA\e[31;1mB\e[32;1mC\e[33;1mD\e[34;1mE\e[35;1mF\e[36;1mG\e[37;1mH"