I recently installed Regolith Desktop to use alongside Kubuntu Desktop. I have fully disabled screen locking in Kubuntu, such that my display just goes to sleep without needing a password to resume.

However, when I am using Regolith and my screen goes to sleep and I wake it up, I get a KDE-branded lock screen dialog and have to enter my password. Because the screen unlocker has a KDE logo, I assume this is somehow coming from the Kubuntu side.

How might that be happening and what must I change in order to have lock-free monitor sleep in Regolith?

I recently installed Regolith Desktop to use alongside Kubuntu Desktop. I really like it, but unfortunately some KDE/Plasma settings are spilling over into Regolith.

One thing that is bothering me is the meta-s keyboard shortcut. In i3, it is supposed to turn window stacking on and off. However, for me it brings up the sound control panel. I assume this shortcut to the sound control panel is coming from some Plasma/KDE setting, however I cannot figure out which (so as to disable it).

I have looked in ~/.config/kglobalshortcutsrc as well as Settings > Shortcuts, but I do not see it listed anywhere.

I am having the same issue with meta-w, which for me opens the WiFi control panel. I am guessing that both of these settings are in the same place, wherever that is. Can anyone point me towards where these particular shortcuts are set.

Edit: Further information in response to the suggestions.

• My shortcuts settings do not match the KDE documentation linked to, for example I have nothing called "Global shortcuts". Within this area, the meta-s and meta-w shortcuts do not appear.

• Now that I am back using KDE, I just tried the meta-s and meta-w keyboard combinations and they don't work. So maybe it is actually a Regolith issue? I had assumed it was related to KDE as it was a KDE control panel that the shortcut activated.

Solution: Oh, well silly me. It's just that Regolith has it's own system of keybindings. https://www.reddit.com/r/regolithlinux/comments/l0kx3f/stacked_and_tabbed_layouts/

Aims

• Goal of this post: Figure out what xorg.conf configurations are necessary to use each of my dual monitors as a separate X screen.
• Intermediate goal for this post: Figure out why I cannot start X with my manual xorg.conf configuration.
• Success metric: When I can launch xeyes or other X11 apps in a script which specifies which of my monitors they appear on.
• Ultimate purpose: To start LXC GUI containers (meaning a full desktop) such that they appear fullscreen on a chosen monitor. I wish to be able to share a keyboard and move a cursor between the monitors, but not move windows.

My system

• Ubuntu Server 20.04, Nvidia GT 710 video card. Driver is nvidia-dkms-470-server. The connections I am using are HDMI and DVI.
• There are other video cards present on the system, but they are aliased and will be used for passthrough purposes. I see no reason why this should be relevant, but video drivers have surprised me before.

Expected behavior:

• When I run startx &, X should start normally, and then I should be able to open xeyes on either screen 0 or 1 by using DISPLAY=:0.0 or DISPLAY=:0.1 respectively.

Actual behavior:

• I cannot start X, with "no screens found".

• Judging by the logs, xf86OpenConsole might be related to the problem, but I have no idea what that is.

• This is Xorg.0.log after I try sudo startx &.

[  3083.851] (II) Module nvidia: vendor="NVIDIA Corporation"
[  3083.851]    compiled for 1.6.99.901, module version = 1.0.0
[  3083.851]    Module class: X.Org Video Driver
[  3083.851] (II) UnloadModule: "nvidia"
[  3083.851] (II) Unloading nvidia
[  3083.851] (II) Failed to load module "nvidia" (already loaded, 0)
[  3083.851] (II) LoadModule: "nouveau"
[  3083.852] (WW) Warning, couldn't open module nouveau
[  3083.852] (EE) Failed to load module "nouveau" (module does not exist, 0)
[  3083.852] (II) LoadModule: "modesetting"
[  3083.852] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  3083.854] (II) Module modesetting: vendor="X.Org Foundation"
[  3083.854]    compiled for 1.20.11, module version = 1.20.11
[  3083.854]    Module class: X.Org Video Driver
[  3083.854]    ABI class: X.Org Video Driver, version 24.1
[  3083.854] (II) LoadModule: "fbdev"
[  3083.854] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[  3083.855] (II) Module fbdev: vendor="X.Org Foundation"
[  3083.855]    compiled for 1.20.1, module version = 0.5.0
[  3083.855]    Module class: X.Org Video Driver
[  3083.855]    ABI class: X.Org Video Driver, version 24.0
[  3083.855] (II) LoadModule: "vesa"
[  3083.855] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[  3083.856] (II) Module vesa: vendor="X.Org Foundation"
[  3083.856]    compiled for 1.20.4, module version = 2.4.0
[  3083.856]    Module class: X.Org Video Driver
[  3083.856]    ABI class: X.Org Video Driver, version 24.0
[  3083.856] (II) NVIDIA dlloader X Driver  470.82.01  Wed Oct 27 21:23:16 UTC 2021
[  3083.856] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[  3083.856] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  3083.856] (II) FBDEV: driver for framebuffer: fbdev
[  3083.856] (II) VESA: driver for VESA chipsets: vesa
[  3083.856] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[  3083.856] (WW) xf86OpenConsole: setsid failed: Operation not permitted
[  3083.856] (WW) Falling back to old probe method for modesetting
[  3083.856] (WW) Falling back to old probe method for fbdev
[  3083.856] (WW) Falling back to old probe method for modesetting
[  3083.856] (WW) Falling back to old probe method for fbdev
[  3083.856] (EE) No devices detected.
[  3083.856] (EE) 
Fatal server error:
[  3083.856] (EE) no screens found(EE) 
[  3083.856] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org

• If I remove xorg.conf, X starts normally, but without two X screens (only Screen 0), as shown by the output of xrandr:

~$ sudo xrandr -q
Screen 0: minimum 8 x 8, current 4160 x 1440, maximum 16384 x 16384
VGA-0 disconnected primary (normal left inverted right x axis y axis)
DVI-D-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 367mm x 275mm
   1600x1200     60.00*+
   1280x1024     75.02    60.02  
   1152x864      75.00  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   640x480       75.00    59.94  
HDMI-0 connected 2560x1440+1600+0 (normal left inverted right x axis y axis) 597mm x 336mm
   2560x1440     59.95*+
   2048x1152     60.00  
   1920x1440     60.00  
   1920x1200     59.88  
   1920x1080     60.00    59.94    50.00    60.05    60.00    50.04  
   1680x1050     59.95  
   1440x900      59.89  
   1440x576      50.00  
   1440x480      59.94  
   1280x1024     75.02    60.02  
   1280x720      60.00    59.94    50.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    72.81    59.94    59.93 

First attempts

• I made my xorg.conf based on this: https://download.nvidia.com/XFree86/Linux-x86_64/304.137/README/configmultxscreens.html
• I suspect there is something more I need in the monitors section of xorg.conf, but I am not sure what it is.
• I feel like the monitors should reference the Screen definitions in some way, but my random guesses about how to do that have been fruitless.
• I am finding it difficult to adapt the xorg.conf examples I have found to my specific circumstances. I don't know what is mandatory based on my hardware or distro/version.
• /etc/X11/xorg.conf:

Section "Device"
    Identifier "nvidia0"
    Driver "nvidia"
    BusID "PCI:44:00:0"
    Screen 0
EndSection

Section "Device"
    Identifier "nvidia1"
    Driver "nvidia"
    BusID "PCI:44:0:0"
    Screen 1
EndSection


Section "Screen"
    Identifier "Screen0"
    Device "nvidia0"
    Monitor "Monitor0"
    DefaultDepth 24
    Subsection "Display"
        Depth 24
        Modes "1600x1200" "1024x768" "800x600" "640x480"
    EndSubsection
EndSection

Section "Screen"
    Identifier "Screen1"
    Device "nvidia1"
    Monitor "Monitor1"
    DefaultDepth 24
    Subsection "Display"
        Depth 24
        Modes "1600x1200" "1024x768" "800x600" "640x480"
    EndSubsection
EndSection

Section "Monitor"
        Identifier "Monitor0"
EndSection

Section "Monitor"
        Identifier "Monitor1"
        Option "LeftOf" "HDMI-1"
EndSection

Section "ServerLayout"
    Identifier "Main Layout"
    Screen 0 "Screen0"
    Screen 1 "Screen1" leftOf "Screen0"
EndSection

Update - partial success:

• Reconfigured xorg.conf using nvidia-xconfig.
• I can now start X
• No joy with respect to actually getting an X Screen for every monitor.
• My current xorg.conf:

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 470.82.01


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    Screen          0
    VendorName     "NVIDIA Corporation"
    Option      "Monitor-DVI-D-0" "DVI"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "Unknown"
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    Screen          1
    VendorName     "NVIDIA Corporation"
    Option      "Monitor-HDMI-0" "HDMI"
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    SubSection     "Display"
    Depth       24
    EndSubSection
EndSection

• But xrandr still only shows Screen0

~$ sudo xrandr -q
Screen 0: minimum 8 x 8, current 4160 x 1440, maximum 16384 x 16384
VGA-0 disconnected primary (normal left inverted right x axis y axis)
DVI-D-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 367mm x 275mm
   1600x1200     60.00*+
   1280x1024     75.02    60.02  
   1152x864      75.00  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   640x480       75.00    59.94  
HDMI-0 connected 2560x1440+1600+0 (normal left inverted right x axis y axis) 597mm x 336mm
   2560x1440     59.95*+
   2048x1152     60.00  
   1920x1440     60.00  
   1920x1200     59.88  
   1920x1080     60.00    59.94    50.00    60.05    60.00    50.04  
   1680x1050     59.95  
   1440x900      59.89  
   1440x576      50.00  
   1440x480      59.94  
   1280x1024     75.02    60.02  
   1280x720      60.00    59.94    50.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    72.81    59.94    59.93  

Edit: One additional note: I have tried supplying the PCI IDs under the "Device" section like BusID "PCI:44:0:0". That actually seems to be the cause of my earlier problem with X not starting with:

[   229.284] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[   229.284] (WW) xf86OpenConsole: setsid failed: Operation not permitted

Yet another update

I removed the PCI BusID specification from the Device section of xorg.conf, as for some reason it prevented me from starting X with the xf86OpenConsole errors mentioned above. However I did notice that Nvidias more recent documentation suggests using a ServerLayout section. I added the second screen to this section, and it did change the output of xrandr, but not in the way I wanted. It still only mentions Screen0, but now there is no info about my HDMI monitor (although I have a cursor on it). This is now the output of xrandr:

~$ sudo xrandr -q
Screen 0: minimum 8 x 8, current 1600 x 1200, maximum 16384 x 16384
VGA-0 disconnected primary (normal left inverted right x axis y axis)
DVI-D-0 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 367mm x 275mm
   1600x1200     60.00*+
   1280x1024     75.02    60.02  
   1152x864      75.00  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   640x480       75.00    59.94  

And my xorg.conf currently looks like this:

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Screen      1  "Screen1" rightOf "Screen0" 
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    Option         "DPMS" "DVI"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    Screen          0
    VendorName     "NVIDIA Corporation"
    Option      "Monitor-DVI-D-0" "DVI"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "Unknown"
    Option         "DPMS" "HDMI"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    Screen          1
    VendorName     "NVIDIA Corporation"
    Option      "Monitor-HDMI-0" "HDMI"
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    SubSection     "Display"
    Depth       24
    EndSubSection
EndSection

Edit: One more thing: I tried adding Option "ZaphodHeads" to my Device sections, but that did not help. Perhaps it isn't what I wanted, or maybe I didn't configure it correctly, I don't know.

What is with the insane list of dependencies for the proprietary nvidia drivers?

I have been trying to get GUI LXC containers to work, but that is another story. It's mainly relevant because it is the reason why I want the drivers to be able to drive a display, but not bring all the trappings of a desktop.

In the process of trying different driver versions/sources, I noticed that Gnome kept getting installed. Indeed, even the server version of the nvidia drivers pulls in a crazy list of dependencies. Do I really need all this crap? How do I figure out what crap I really do need? Does this come from Nvidia or the Universe repo maintainers?

sudo apt install --dry-run nvidia-driver-470-server | less

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  acl adwaita-icon-theme apg aptdaemon aptdaemon-data aspell aspell-en
  at-spi2-core avahi-daemon avahi-utils bluez bolt bubblewrap build-essential
  cheese-common colord colord-data cpp cpp-9 cracklib-runtime cups-pk-helper
  dbus-user-session dbus-x11 dconf-cli dconf-gsettings-backend dconf-service
  dctrl-tools desktop-file-utils dictionaries-common dirmngr dkms
  dns-root-data dnsmasq-base docbook-xml dpkg-dev emacsen-common enchant-2
  evolution-data-server evolution-data-server-common fakeroot fontconfig
  fprintd g++ g++-9 gcc gcc-9 gcc-9-base gcr gdm3 geoclue-2.0
  gir1.2-accountsservice-1.0 gir1.2-atk-1.0 gir1.2-atspi-2.0
  gir1.2-freedesktop gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0
  gir1.2-gdkpixbuf-2.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0
  gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0
  gir1.2-gtk-3.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-json-1.0
  gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7
  gir1.2-packagekitglib-1.0 gir1.2-pango-1.0 gir1.2-polkit-1.0 gir1.2-rsvg-2.0
  gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs
  gkbd-capplet glib-networking glib-networking-common glib-networking-services
  gnome-control-center gnome-control-center-data gnome-control-center-faces
  gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus
  gnome-online-accounts gnome-session-bin gnome-session-common
  gnome-settings-daemon gnome-settings-daemon-common gnome-shell
  gnome-shell-common gnome-startup-applications gnome-user-docs gnupg
  gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf
  gpgsm gsettings-desktop-schemas gstreamer1.0-clutter-3.0 gstreamer1.0-gl
  gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-pulseaudio
  gstreamer1.0-x gtk-update-icon-cache hicolor-icon-theme humanity-icon-theme
  hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config
  ippusbxd language-selector-gnome libaa1 libalgorithm-diff-perl
  libalgorithm-diff-xs-perl libalgorithm-merge-perl libappindicator3-1
  libappstream4 libarchive13 libasan5 libasound2-plugins libaspell15
  libassuan0 libasyncns0 libatk-bridge2.0-0 libatk1.0-0 libatk1.0-data
  libatomic1 libatspi2.0-0 libavahi-client3 libavahi-common-data
  libavahi-common3 libavahi-core7 libavahi-glib1 libavc1394-0 libbluetooth3
  libboost-thread1.71.0 libc-dev-bin libc6-dev libcaca0 libcairo-gobject2
  libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse
  libcc1-0 libcdparanoia0 libcheese-gtk25 libcheese8 libclutter-1.0-0
  libclutter-1.0-common libclutter-gst-3.0-0 libclutter-gtk-1.0-0
  libcogl-common libcogl-pango20 libcogl-path20 libcogl20 libcolord-gtk1
  libcolord2 libcolorhug2 libcrack2 libcrypt-dev libcups2 libcurl3-gnutls
  libdaemon0 libdatrie1 libdbusmenu-glib4 libdbusmenu-gtk3-4 libdconf1
  libdpkg-perl libdrm-amdgpu1 libdrm-intel1 libdrm-nouveau2 libdrm-radeon1
  libdv4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3
  libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24
  libedataserverui-1.2-2 libegl-mesa0 libegl1 libenchant-2-2 libepoxy0
  libexif12 libfakeroot libfile-fcntllock-perl libflac8 libfontenc1
  libfprint-2-2 libgail-common libgail18 libgbm1 libgcc-9-dev libgck-1-0
  libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22
  libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common libgdm1
  libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgl1 libgl1-mesa-dri
  libglapi-mesa libgles2 libglib2.0-bin libglvnd0 libglx-mesa0 libglx0
  libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19
  libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common
  libgoa-backend-1.0-1 libgomp1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12
  libgraphene-1.0-0 libgraphite2-3 libgsound0 libgssdp-1.2-0
  libgstreamer-gl1.0-0 libgstreamer-plugins-base1.0-0
  libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 libgtk-3-0 libgtk-3-bin
  libgtk-3-common libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgtop-2.0-11
  libgtop2-common libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3
  libgusb2 libgweather-3-16 libgweather-common libharfbuzz-icu0 libharfbuzz0b
  libhunspell-1.7-0 libhyphen0 libibus-1.0-5 libical3 libice6 libidn11
  libiec61883-0 libieee1284-3 libinput-bin libinput10 libisl22 libitm1
  libjack-jackd2-0 libjansson4 libjavascriptcoregtk-4.0-18 libjbig0
  libjpeg-turbo8 libjpeg8 libjson-glib-1.0-0 libjson-glib-1.0-common libksba8
  liblcms2-2 libldb2 libllvm12 liblsan0 libmbim-glib4 libmbim-proxy
  libmediaart-2.0-0 libmm-glib0 libmozjs-68-0 libmp3lame0 libmpc3 libmpfr6
  libmpg123-0 libmtdev1 libmutter-6-0 libmysqlclient21 libndp0
  libnl-route-3-200 libnm0 libnma0 libnotify4 libnpth0 libnspr4 libnss-mdns
  libnss3 libnvidia-cfg1-470-server libnvidia-common-470-server
  libnvidia-compute-470-server libnvidia-decode-470-server
  libnvidia-encode-470-server libnvidia-extra-470-server
  libnvidia-fbc1-470-server libnvidia-gl-470-server libnvidia-ifr1-470-server
  libopenjp2-7 libopus0 liborc-0.4-0 libpackagekit-glib2-18 libpam-fprintd
  libpam-gnome-keyring libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0
  libpangoxft-1.0-0 libpcsclite1 libphonenumber7 libprotobuf17 libproxy1v5
  libpulse-mainloop-glib0 libpulse0 libpulsedsp libpwquality-common
  libpwquality1 libqmi-glib5 libqmi-proxy libquadmath0 libraw1394-11
  librest-0.7-0 librsvg2-2 librsvg2-common librygel-core-2.6-2
  librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2
  libsamplerate0 libsane libsane-common libsbc1 libsecret-1-0 libsecret-common
  libshout3 libsm6 libsmbclient libsnapd-glib1 libsndfile1 libsnmp-base
  libsnmp35 libsoup-gnome2.4-1 libsoup2.4-1 libsoxr0 libspeex1 libspeexdsp1
  libstartup-notification0 libstdc++-9-dev libstemmer0d libtag1v5
  libtag1v5-vanilla libtalloc2 libteamdctl0 libtevent0 libthai-data libthai0
  libtheora0 libtiff5 libtsan0 libtwolame0 libubsan1 libudisks2-0 libv4l-0
  libv4lconvert0 libvdpau1 libvisual-0.4-0 libvorbisenc2 libvpx6 libvte-2.91-0
 libvte-2.91-common libvulkan1 libwacom-bin libwacom-common libwacom2
  libwavpack1 libwayland-client0 libwayland-cursor0 libwayland-egl1
  libwayland-server0 libwbclient0 libwebkit2gtk-4.0-37 libwebp6 libwebpdemux2
  libwebrtc-audio-processing1 libwhoopsie-preferences0 libwhoopsie0 libwoff1
  libx11-xcb1 libxatracker2 libxaw7 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0
  libxcb-icccm4 libxcb-image0 libxcb-keysyms1 libxcb-present0 libxcb-randr0
  libxcb-render-util0 libxcb-res0 libxcb-shape0 libxcb-sync1 libxcb-util1
  libxcb-xfixes0 libxcb-xkb1 libxcb-xv0 libxcomposite1 libxcursor1 libxdamage1
  libxfixes3 libxfont2 libxft2 libxi6 libxinerama1 libxkbcommon-x11-0
  libxkbcommon0 libxkbfile1 libxklavier16 libxmu6 libxpm4 libxrandr2
  libxshmfence1 libxslt1.1 libxss1 libxt6 libxtst6 libxv1 libxvmc1 libxxf86vm1
  libyelp0 linux-libc-dev manpages-dev mesa-vdpau-drivers mesa-vulkan-drivers
  mobile-broadband-provider-info modemmanager mousetweaks mutter mutter-common
  mysql-common network-manager network-manager-gnome network-manager-pptp
  nvidia-compute-utils-470-server nvidia-dkms-470-server
  nvidia-kernel-common-470-server nvidia-kernel-source-470-server nvidia-prime
  nvidia-settings nvidia-utils-470-server p11-kit p11-kit-modules packagekit
  packagekit-tools patch pinentry-curses pinentry-gnome3 pkg-config ppp
  pptp-linux pulseaudio pulseaudio-module-bluetooth pulseaudio-utils
  python3-aptdaemon python3-aptdaemon.gtk3widgets python3-cairo python3-cups
  python3-cupshelpers python3-defer python3-ibus-1.0 python3-ldb
  python3-macaroonbakery python3-protobuf python3-rfc3339 python3-talloc
  python3-tz python3-xkit rtkit rygel samba-libs sane-utils
  screen-resolution-extra session-migration sgml-base sgml-data
  switcheroo-control system-config-printer system-config-printer-common
  system-config-printer-udev ubuntu-docs ubuntu-mono ubuntu-session
  ubuntu-wallpapers ubuntu-wallpapers-focal unzip update-inetd usb-modeswitch
  usb-modeswitch-data vdpau-driver-all wamerican whoopsie-preferences
  wpasupplicant x11-common x11-xkb-utils x11-xserver-utils xdg-dbus-proxy
  xfonts-base xfonts-encodings xfonts-utils xml-core xserver-common
  xserver-xephyr xserver-xorg xserver-xorg-core xserver-xorg-input-all
  xserver-xorg-input-libinput xserver-xorg-input-wacom xserver-xorg-legacy
  xserver-xorg-video-all xserver-xorg-video-amdgpu xserver-xorg-video-ati
  xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-nouveau
  xserver-xorg-video-nvidia-470-server xserver-xorg-video-qxl
  xserver-xorg-video-radeon xserver-xorg-video-vesa xserver-xorg-video-vmware
  xwayland yaru-theme-gnome-shell yelp yelp-xsl zenity zenity-common

When I installed from the .run file downloaded from the Nvidia website, I also ended up with bits of Gnome.

I see that a different package nvidia-headless-470-server has a much more reasonable list of dependencies, but I do need it to be graphics-capable as it will be driving GUI apps. But preferably using X without a window manager.

I was away from for over a year, and when I turned on my computer, I discovered that I could no longer connect to any networks. When I left the ethernet was working fine. All other devices in the house can connect without issues. These are the steps I have taken:

1. Checked the cables.
2. Checked the status of NetworkManager with systemctl. It was running, but I restarted it anywyway and that made no difference.
3. Tried connecting using wifi. I can see my wifi network and enter my password, but get a disconnect error after a few seconds of trying to connect.
4. Booted from a Lubuntu bootable USB. Wifi and ethernet both work right off the bat, websites loaded.
5. Checked my system time. If it's off, it's off by less than 1 minute.
6. After connecing with the bootable usb, when I restarted into my installation, wifi showed as connected (instead of "connecting" as it did before). However I could not load any pages or ping anything (even my router). After restarting again, all I have seen is the behavior described in #3.

I'm at somewhat of a loss as to what to try next. The usual stuff isn't working.

addendum: Here is a sample of journalctl -b 0 -u NetworkManager output`

Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1165] policy: auto-activating connection 'MYWIFINWTWORK' (f3bef4ef-9f4d-471d-9288-835949887f58)
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1171] device (wlp5s0): Activation: starting connection 'MYWIFINWTWORK' (f3bef4ef-9f4d-471d-9288-835949887f58)
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1173] device (wlp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1177] manager: NetworkManager state is now CONNECTING
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1181] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1185] device (wlp5s0): Activation: (wifi) access point 'MYWIFINWTWORK' has security, but secrets are required.
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1185] device (wlp5s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1187] sup-iface[0x5604bb5e1920,wlp5s0]: wps: type pbc start...
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1217] device (wlp5s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1221] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1224] device (wlp5s0): Activation: (wifi) connection 'MYWIFINWTWORK' has security, and secrets exist.  No new secrets needed.
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1225] Config: added 'ssid' value 'MYWIFINWTWORK'
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1225] Config: added 'scan_ssid' value '1'
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1225] Config: added 'bgscan' value 'simple:30:-70:86400'
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1225] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1226] Config: added 'auth_alg' value 'OPEN'
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1226] Config: added 'psk' value '<hidden>'
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1340] device (wlp5s0): supplicant interface state: disconnected -> scanning
Oct 12 22:01:07 virtland NetworkManager[5959]: <info>  [1634090467.1340] device (p2p-dev-wlp5s0): supplicant management interface state: disconnected -> scanning
Oct 12 22:01:32 virtland NetworkManager[5959]: <warn>  [1634090492.1007] device (wlp5s0): Activation: (wifi) association took too long, failing activation
Oct 12 22:01:32 virtland NetworkManager[5959]: <info>  [1634090492.1007] device (wlp5s0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Oct 12 22:01:32 virtland NetworkManager[5959]: <info>  [1634090492.1012] manager: NetworkManager state is now DISCONNECTED
Oct 12 22:01:32 virtland NetworkManager[5959]: <warn>  [1634090492.1026] device (wlp5s0): Activation: failed for connection 'MYWIFINWTWORK'
Oct 12 22:01:32 virtland NetworkManager[5959]: <info>  [1634090492.1029] device (wlp5s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 12 22:01:32 virtland NetworkManager[5959]: <info>  [1634090492.1044] device (wlp5s0): supplicant interface state: scanning -> disconnected
Oct 12 22:01:32 virtland NetworkManager[5959]: <info>  [1634090492.1044] device (p2p-dev-wlp5s0): supplicant management interface state: scanning -> disconnected
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9290] policy: auto-activating connection 'MYWIFINWTWORK' (f3bef4ef-9f4d-471d-9288-835949887f58)
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9296] device (wlp5s0): Activation: starting connection 'MYWIFINWTWORK' (f3bef4ef-9f4d-471d-9288-835949887f58)
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9298] device (wlp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9302] manager: NetworkManager state is now CONNECTING
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9308] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9312] device (wlp5s0): Activation: (wifi) access point 'MYWIFINWTWORK' has security, but secrets are required.
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9312] device (wlp5s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9315] sup-iface[0x5604bb5e1920,wlp5s0]: wps: type pbc start...
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9343] device (wlp5s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9350] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9353] device (wlp5s0): Activation: (wifi) connection 'MYWIFINWTWORK' has security, and secrets exist.  No new secrets needed.
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9354] Config: added 'ssid' value 'MYWIFINWTWORK'
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9354] Config: added 'scan_ssid' value '1'
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9354] Config: added 'bgscan' value 'simple:30:-70:86400'
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9354] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9355] Config: added 'auth_alg' value 'OPEN'
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9355] Config: added 'psk' value '<hidden>'
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9463] device (wlp5s0): supplicant interface state: disconnected -> authenticating
Oct 12 22:01:58 virtland NetworkManager[5959]: <info>  [1634090518.9463] device (p2p-dev-wlp5s0): supplicant management interface state: disconnected -> authenticating
Oct 12 22:01:59 virtland NetworkManager[5959]: <info>  [1634090519.1292] device (wlp5s0): supplicant interface state: authenticating -> disconnected
Oct 12 22:01:59 virtland NetworkManager[5959]: <info>  [1634090519.1292] device (p2p-dev-wlp5s0): supplicant management interface state: authenticating -> disconnected
Oct 12 22:02:09 virtland NetworkManager[5959]: <info>  [1634090529.1349] device (wlp5s0): supplicant interface state: disconnected -> scanning
Oct 12 22:02:09 virtland NetworkManager[5959]: <info>  [1634090529.1350] device (p2p-dev-wlp5s0): supplicant management interface state: disconnected -> scanning
Oct 12 22:02:09 virtland NetworkManager[5959]: <info>  [1634090529.9928] device (wlp5s0): supplicant interface state: scanning -> authenticating
Oct 12 22:02:09 virtland NetworkManager[5959]: <info>  [1634090529.9929] device (p2p-dev-wlp5s0): supplicant management interface state: scanning -> authenticating
Oct 12 22:02:10 virtland NetworkManager[5959]: <info>  [1634090530.1647] device (wlp5s0): supplicant interface state: authenticating -> disconnected
Oct 12 22:02:10 virtland NetworkManager[5959]: <info>  [1634090530.1648] device (p2p-dev-wlp5s0): supplicant management interface state: authenticating -> disconnected
Oct 12 22:02:20 virtland NetworkManager[5959]: <info>  [1634090540.1716] device (wlp5s0): supplicant interface state: disconnected -> scanning
Oct 12 22:02:20 virtland NetworkManager[5959]: <info>  [1634090540.1716] device (p2p-dev-wlp5s0): supplicant management interface state: disconnected -> scanning
Oct 12 22:02:24 virtland NetworkManager[5959]: <warn>  [1634090544.1004] device (wlp5s0): Activation: (wifi) association took too long, failing activation
Oct 12 22:02:24 virtland NetworkManager[5959]: <info>  [1634090544.1004] device (wlp5s0): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Oct 12 22:02:24 virtland NetworkManager[5959]: <info>  [1634090544.1009] manager: NetworkManager state is now DISCONNECTED
Oct 12 22:02:24 virtland NetworkManager[5959]: <warn>  [1634090544.1020] device (wlp5s0): Activation: failed for connection 'MYWIFINWTWORK'
Oct 12 22:02:24 virtland NetworkManager[5959]: <info>  [1634090544.1024] device (wlp5s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 12 22:02:24 virtland NetworkManager[5959]: <info>  [1634090544.9327] device (wlp5s0): supplicant interface state: scanning -> disconnected
Oct 12 22:02:24 virtland NetworkManager[5959]: <info>  [1634090544.9327] device (p2p-dev-wlp5s0): supplicant management interface state: scanning -> disconnected
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9466] policy: auto-activating connection 'MYWIFINWTWORK' (f3bef4ef-9f4d-471d-9288-835949887f58)
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9473] device (wlp5s0): Activation: starting connection 'MYWIFINWTWORK' (f3bef4ef-9f4d-471d-9288-835949887f58)
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9474] device (wlp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9480] manager: NetworkManager state is now CONNECTING
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9486] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9492] device (wlp5s0): Activation: (wifi) access point 'MYWIFINWTWORK' has security, but secrets are required.
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9492] device (wlp5s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9496] sup-iface[0x5604bb5e1920,wlp5s0]: wps: type pbc start...
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9530] device (wlp5s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9536] device (wlp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9539] device (wlp5s0): Activation: (wifi) connection 'MYWIFINWTWORK' has security, and secrets exist.  No new secrets needed.
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9539] Config: added 'ssid' value 'MYWIFINWTWORK'
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9539] Config: added 'scan_ssid' value '1'
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9539] Config: added 'bgscan' value 'simple:30:-70:86400'
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9539] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9539] Config: added 'auth_alg' value 'OPEN'
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9540] Config: added 'psk' value '<hidden>'
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9641] device (wlp5s0): supplicant interface state: disconnected -> authenticating
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9642] device (p2p-dev-wlp5s0): supplicant management interface state: disconnected -> authenticating
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9977] device (wlp5s0): supplicant interface state: authenticating -> associating
Oct 12 22:02:50 virtland NetworkManager[5959]: <info>  [1634090570.9978] device (p2p-dev-wlp5s0): supplicant management interface state: authenticating -> associating
Oct 12 22:02:51 virtland NetworkManager[5959]: <info>  [1634090571.1163] device (wlp5s0): supplicant interface state: associating -> 4-way handshake
Oct 12 22:02:51 virtland NetworkManager[5959]: <info>  [1634090571.1163] device (p2p-dev-wlp5s0): supplicant management interface state: associating -> 4-way handshake
Oct 12 22:03:00 virtland NetworkManager[5959]: <warn>  [1634090580.1538] sup-iface[0x5604bb5e1920,wlp5s0]: connection disconnected (reason 2)
Oct 12 22:03:00 virtland NetworkManager[5959]: <info>  [1634090580.1588] device (wlp5s0): supplicant interface state: 4-way handshake -> disconnected
Oct 12 22:03:00 virtland NetworkManager[5959]: <info>  [1634090580.1597] device (wlp5s0): Activation: (wifi) disconnected during association, asking for new key
Oct 12 22:03:00 virtland NetworkManager[5959]: <info>  [1634090580.1598] device (wlp5s0): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed')
Oct 12 22:03:00 virtland NetworkManager[5959]: <info>  [1634090580.1602] device (p2p-dev-wlp5s0): supplicant management interface state: 4-way handshake -> disconnected
Oct 12 22:03:00 virtland NetworkManager[5959]: <warn>  [1634090580.1618] device (wlp5s0): no secrets: No agents were available for this request.
Oct 12 22:03:00 virtland NetworkManager[5959]: <info>  [1634090580.1618] device (wlp5s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Oct 12 22:03:00 virtland NetworkManager[5959]: <info>  [1634090580.1623] manager: NetworkManager state is now DISCONNECTED
Oct 12 22:03:00 virtland NetworkManager[5959]: <warn>  [1634090580.1632] device (wlp5s0): Activation: failed for connection 'MYWIFINWTWORK'
Oct 12 22:03:00 virtland NetworkManager[5959]: <info>  [1634090580.1636] device (wlp5s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Oct 12 22:03:01 virtland NetworkManager[5959]: <info>  [1634090581.2593] device (wlp5s0): supplicant interface state: disconnected -> inactive
Oct 12 22:03:01 virtland NetworkManager[5959]: <info>  [1634090581.2594] device (p2p-dev-wlp5s0): supplicant management interface state: disconnected -> inactive

Also I checked journalctl again after again trying to plug in my ethernet and bring it up with ip link set. I'm not sure if it is relevant or not.

Oct 12 19:18:30 virtland kernel: igb 0000:04:00.0 enp4s0: renamed from eth0
Oct 12 19:18:35 virtland NetworkManager[5959]: <info>  [1634080715.3773] manager: (enp4s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Oct 13 00:28:49 virtland NetworkManager[5959]: <info>  [1634099329.6246] audit: op="connection-activate" uuid="95ca1a5d-7e4c-4a9e-9581-e600b3e40c24" name="Ethernet connection 1" pid=19985 uid=1000 result="fail" reason="Connection 'Ethernet connection 1' is not available on device enp4s0 because device is strictly unmanaged"
Oct 13 00:53:24 virtland sudo[275807]:     boss : TTY=pts/0 ; PWD=/home/boss ; USER=root ; COMMAND=/usr/sbin/ip link set enp4s0 up
Oct 13 00:53:24 virtland systemd-networkd[1541]: enp4s0: Link UP
Oct 13 00:53:26 virtland kernel: igb 0000:04:00.0 enp4s0: igb: enp4s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Oct 13 00:53:26 virtland kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready
Oct 13 00:53:26 virtland systemd-networkd[1541]: enp4s0: Gained carrier
Oct 13 00:53:26 virtland NetworkManager[5959]: <info>  [1634100806.9401] device (enp4s0): carrier: link connected
Oct 13 00:53:28 virtland avahi-daemon[5951]: Joining mDNS multicast group on interface enp4s0.IPv6 with address fe80::7285:c2ff:fe65:9f1b.
Oct 13 00:53:28 virtland avahi-daemon[5951]: New relevant interface enp4s0.IPv6 for mDNS.
Oct 13 00:53:28 virtland systemd-networkd[1541]: enp4s0: Gained IPv6LL
Oct 13 00:53:28 virtland avahi-daemon[5951]: Registering new address record for fe80::7285:c2ff:fe65:9f1b on enp4s0.*.
Oct 13 00:53:39 virtland sudo[276134]:     boss : TTY=pts/0 ; PWD=/home/boss ; USER=root ; COMMAND=/usr/sbin/ip link set enp4s0 up

UPDATE: It all works now! Problem is, I have no idea why as I changed absolutely no configurations. All I did is leave the computer off for a couple hours.

I rebooted and the wifi interface came up and connected, but then disconnected.

boss@virtland:~$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=63 time=2.30 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=63 time=2.01 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=63 time=4.40 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=63 time=5.89 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=63 time=2.47 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=63 time=2.51 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=63 time=40.1 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=63 time=9.10 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=63 time=3.88 ms
^C
--- 192.168.1.1 ping statistics ---
12 packets transmitted, 9 received, 25% packet loss, time 11044ms
rtt min/avg/max/mdev = 2.005/8.075/40.126/11.531 ms
boss@virtland:~$ sudo ip link set enp4s0 up^C
boss@virtland:~$ ping google.com
PING google.com (142.251.35.174) 56(84) bytes of data.
64 bytes from lga25s78-in-f14.1e100.net (142.251.35.174): icmp_seq=1 ttl=117 time=20.2 ms
64 bytes from lga25s78-in-f14.1e100.net (142.251.35.174): icmp_seq=2 ttl=117 time=11.1 ms
64 bytes from lga25s78-in-f14.1e100.net (142.251.35.174): icmp_seq=3 ttl=117 time=25.0 ms
64 bytes from lga25s78-in-f14.1e100.net (142.251.35.174): icmp_seq=4 ttl=117 time=7.98 ms
64 bytes from lga25s78-in-f14.1e100.net (142.251.35.174): icmp_seq=5 ttl=117 time=11.3 ms
64 bytes from lga25s78-in-f14.1e100.net (142.251.35.174): icmp_seq=6 ttl=117 time=14.3 ms
64 bytes from lga25s78-in-f14.1e100.net (142.251.35.174): icmp_seq=7 ttl=117 time=29.9 ms
64 bytes from lga25s78-in-f14.1e100.net (142.251.35.174): icmp_seq=8 ttl=117 time=31.6 ms
64 bytes from lga25s78-in-f14.1e100.net (142.251.35.174): icmp_seq=9 ttl=117 time=14.1 ms
64 bytes from lga25s78-in-f14.1e100.net (142.251.35.174): icmp_seq=11 ttl=117 time=15.6 ms
From virtland (10.0.0.23) icmp_seq=31 Destination Host Unreachable
From virtland (10.0.0.23) icmp_seq=32 Destination Host Unreachable
From virtland (10.0.0.23) icmp_seq=33 Destination Host Unreachable
From virtland (10.0.0.23) icmp_seq=34 Destination Host Unreachable
From virtland (10.0.0.23) icmp_seq=38 Destination Host Unreachable
From virtland (10.0.0.23) icmp_seq=41 Destination Host Unreachable
From virtland (10.0.0.23) icmp_seq=42 Destination Host Unreachable
^C
--- google.com ping statistics ---
45 packets transmitted, 10 received, +7 errors, 77.7778% packet loss, time 44801ms
rtt min/avg/max/mdev = 7.978/18.107/31.643/7.808 ms, pipe 4
boss@virtland:~$ 

When the interface comes up again (without any intervention)

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000              
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00                                                
    inet 127.0.0.1/8 scope host lo                                                                       
       valid_lft forever preferred_lft forever                                                           
    inet6 ::1/128 scope host                                                                             
       valid_lft forever preferred_lft forever                                                           
2: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000                  
    link/ether 70:85:c2:65:9f:1b brd ff:ff:ff:ff:ff:ff                                                   
3: enp6s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000      
    link/ether 70:85:c2:65:9f:19 brd ff:ff:ff:ff:ff:ff                                                   
4: wlp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000     
    link/ether 28:c6:3f:15:64:27 brd ff:ff:ff:ff:ff:ff                                                   
    inet 10.0.0.23/24 brd 10.0.0.255 scope global dynamic noprefixroute wlp5s0                           
       valid_lft 86319sec preferred_lft 86319sec                                                         
    inet6 fe80::1347:560:8ccd:7267/64 scope link noprefixroute                                           
       valid_lft forever preferred_lft forever                                                           
5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 
    link/ether 52:54:00:3d:df:24 brd ff:ff:ff:ff:ff:ff                                                   
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
6: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000

I tried plugging the ethernet in again (this time to a different port) and bringing up ip with ip link set. This time it seems to have worked. What is odd though is that the applet icon still shows that I am disconnected. I suspect my problems may not be over.

boss@virtland:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 70:85:c2:65:9f:1b brd ff:ff:ff:ff:ff:ff
3: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 70:85:c2:65:9f:19 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.7/24 brd 10.0.0.255 scope global dynamic enp6s0
       valid_lft 86224sec preferred_lft 86224sec
    inet6 fe80::7285:c2ff:fe65:9f19/64 scope link 
       valid_lft forever preferred_lft forever
4: wlp5s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 28:c6:3f:15:64:27 brd ff:ff:ff:ff:ff:ff
5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:3d:df:24 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
6: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:3d:df:24 brd ff:ff:ff:ff:ff:ff
boss@virtland:~$ ping google.com
PING google.com (142.250.80.46) 56(84) bytes of data.
64 bytes from lga34s34-in-f14.1e100.net (142.250.80.46): icmp_seq=1 ttl=117 time=10.7 ms
64 bytes from lga34s34-in-f14.1e100.net (142.250.80.46): icmp_seq=2 ttl=117 time=13.5 ms
64 bytes from lga34s34-in-f14.1e100.net (142.250.80.46): icmp_seq=3 ttl=117 time=4.89 ms
64 bytes from lga34s34-in-f14.1e100.net (142.250.80.46): icmp_seq=4 ttl=117 time=10.0 ms
64 bytes from lga34s34-in-f14.1e100.net (142.250.80.46): icmp_seq=5 ttl=117 time=12.7 ms
64 bytes from lga34s34-in-f14.1e100.net (142.250.80.46): icmp_seq=6 ttl=117 time=15.0 ms
64 bytes from lga34s34-in-f14.1e100.net (142.250.80.46): icmp_seq=7 ttl=117 time=5.72 ms
64 bytes from lga34s34-in-f14.1e100.net (142.250.80.46): icmp_seq=8 ttl=117 time=8.78 ms
64 bytes from lga34s34-in-f14.1e100.net (142.250.80.46): icmp_seq=9 ttl=117 time=10.9 ms
64 bytes from lga34s34-in-f14.1e100.net (142.250.80.46): icmp_seq=10 ttl=117 time=3.92 ms
64 bytes from lga34s34-in-f14.1e100.net (142.250.80.46): icmp_seq=11 ttl=117 time=5.95 ms
^C
--- google.com ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 10017ms
rtt min/avg/max/mdev = 3.920/9.277/14.969/3.560 ms

I want to install Darwin Calendar Server on Ubuntu 20.04. In the past (Bionic), this could be done with

sudo apt install calendarserver

It looks like it still is in the Debian repositories: https://wiki.debian.org/CalendarServer

Has it changed names? Should I use a PPA or build it from source?

I have successfully set up nginx using these instructions, but one part has never worked for me, and that bothers me even though it does not seem to cause an problems.

root@devtest:/home/dev-admin# ufw app list
Available applications:
  Nginx Full
  Nginx HTTP
  Nginx HTTPS
  OpenSSH
root@devtest:/home/dev-admin# sudo ufw delete allow 'Nginx HTTP'
Could not delete non-existent rule
Could not delete non-existent rule (v6)
root@devtest:/home/dev-admin# ufw app list
Available applications:
  Nginx Full
  Nginx HTTP
  Nginx HTTPS
  OpenSSH

What am I missing here? Is this not the correct syntax to delete the rule? This is on Ubuntu 20.04, but I get the same result on 18.04.

I have been having problems with KVM crashing, and the kernel crash dumps seem to point to a NIC problem, possibly a driver issue. However, before reporting, it has been recommended that I try using the latest mainline kernel as described here How to update kernel to the latest mainline version without any Distro-upgrade? :

I tried this, but of course it broke ZFS, so I had to reboot back into my old kernel. I can think of a few ways I might do this, but I don't know what the recommended way would be.

1. Install zfs-dkms, reboot, then install the new kernel. I'm worried that switching to DKMS in my main kernel might leave me in an even more inconvenient postion.
2. Use a testing version of zfsutils that works with the most recent kernel possible. I'm not sure who to ask. Trial and error seems like a lot of work.
3. Make an alternative install that is as similar to my current install as possible: Install Ubuntu onto a bootable USB, build zfsutils from source in that environment, then install libvirt, NFS, and other packages I need to reproduce the crash. This seems like a fair amount of work for something that isn't an exact replication of my problem situation.

I am using an Xubuntu guest virtual machine with Virt-Manager, Spice, and QXL. I want to rotate the virtual display to be vertical so as to fit my monitor.

Stuff I tried:

• Settings > Display in Xubuntu guest: There is a Rotation popup menu, but the only available option is None.
• Rotating via xrandr doesnt work:

~$ xrandr -q
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
Virtual-0 connected primary 1024x768+0+0 0mm x 0mm
   1024x768      59.95*+
   1920x1200     59.95  
   1920x1080     60.00  
   1600x1200     59.95  
   1680x1050     60.00  
   1400x1050     60.00  
   1280x1024     59.95  
   1440x900      59.99  
   1280x960      59.99  
   1280x854      59.95  
   1280x800      59.96  
   1280x720      59.97  
   1152x768      59.95  
   800x600       59.96  
   848x480       59.94  
   720x480       59.94  
   640x480       59.94  
Virtual-1 disconnected
Virtual-2 disconnected
Virtual-3 disconnected
~$ xrandr --output Virtual-0 --rotate right
xrandr: output Virtual-0 cannot use rotation "right" reflection "none"

• echo 3 | sudo tee /sys/class/graphics/fbcon/rotate had no effect and gave no error.
• As far as I can tell, I have the right drivers installed:

~$ apt list --installed | grep -i spice

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

spice-vdagent/bionic,now 0.17.0-1ubuntu2 amd64 [installed]
~$ apt list --installed | grep -i qxl

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

xserver-xorg-video-qxl/bionic,now 0.1.5-2build1 amd64 [installed]

• My XML looks OK, right?

    <graphics type='spice' autoport='yes'>
      <listen type='address'/>
      <image compression='off'/>
    </graphics>
    <sound model='ich9'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/>
    </sound>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>

Is there a way to have a virtual vertical monitor with a Xubuntu guest?

I cannot seem to get an xrandr command to rotate my monitor at startup.

The script:

cat /etc/X11/Xsession.d/999_test                                                                                                     
xrandr --output DVI-D-3 --off --output HDMI-3 --off --output VGA-1 --mode 1920x1080 --pos 0x0 --rotate left --output DVI-D-2-1 --off --output DP-2-1 --off --output DP-2-2 --off --output HDMI-2-1 --off --output DP-2-3 --off --output DisplayPort-1-3 --off --output DisplayPort-1-4 --off --output DisplayPort-1-5 --off --output HDMI-A-1-1 --off --output DVI-D-1-1 --off

xclock &

and the script itself is working, because if I add xclock & to the end of the script, I start my session with xclock lauched, but my screen not rotated (until I run the command from the terminal)

After logging in, if I run

 sh /etc/X11/Xsession.d/999_test

It works exactly as expected, rotating my monitor and opening xclock.

I don't see any errors related to xrandr or my script name in ~/.xsession-errors. Is that where I would expect to find them? I am using Lubuntu 20.04

Edit: As I had been using LXDE before, which has less advanced monitor management, I thought I needed to run this. Even though I do not need to, I'd still like to figure out why this didn't work. I thought that by naming it starting with 999 my script would be executed last and thus not be overridden by anything else.

I am confused about whether my /tmp using tmpfs is respecting the size parameter that I gave to it in /etc/fstab:

My fstab entries now read:

root_pool/var/tmp  /tmp /var/tmp zfs rw,nodev,nosuid 0 0
tmpfs /tmp tmpfs rw,nodev,nosuid,noexec,nr_inodes=5k,size=2G,mode=1777 0 0
tmpfs /dev/shm tmpfs   defaults,nodev,nosuid,nr_inodes=5k,mode=700,size=4G 0 0

But according to du, it is using half of my memory (which I understand is the default) instead of the size I meant to allocate to it.

 ~ df /tmp
Filesystem     1K-blocks  Used Available Use% Mounted on
tmpfs           65921428     0  65921428   0% /tmp

So is the size parameter simply not having any effect? I am working with Ubuntu 20.04

Edit I can mount it manually with

sudo mount -oremount,size=4G /tmp

When I do that /tmp is the expected 20.04 GB.

Edit: systemd status:

● tmp.mount - Temporary Directory (/tmp)
     Loaded: loaded (/etc/systemd/system/tmp.mount; enabled; vendor preset: enabled)
     Active: active (mounted) since Wed 2020-06-17 13:30:35 EDT; 8min ago
      Where: /tmp
       What: tmpfs
       Docs: https://systemd.io/TEMPORARY_DIRECTORIES
             man:file-hierarchy(7)
             https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
      Tasks: 0 (limit: 154317)
     Memory: 76.0K
     CGroup: /system.slice/tmp.mount

Jun 17 13:30:35 virtland systemd[1]: Mounting Temporary Directory (/tmp)...
Jun 17 13:30:35 virtland systemd[1]: Mounted Temporary Directory (/tmp).

and journalctl -u tmp.mount

-- Reboot --
Jun 17 13:27:50 virtland systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting an>
Jun 17 13:27:50 virtland systemd[1]: Mounting Temporary Directory (/tmp)...
Jun 17 13:27:50 virtland systemd[1]: Mounted Temporary Directory (/tmp).
Jun 17 13:29:43 virtland systemd[1]: Unmounting Temporary Directory (/tmp)...
Jun 17 13:29:43 virtland systemd[1]: tmp.mount: Succeeded.
Jun 17 13:29:43 virtland systemd[1]: Unmounted Temporary Directory (/tmp).
-- Reboot --
Jun 17 13:30:35 virtland systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting an>
Jun 17 13:30:35 virtland systemd[1]: Mounting Temporary Directory (/tmp)...
Jun 17 13:30:35 virtland systemd[1]: Mounted Temporary Directory (/tmp).

Edit2: Setting the size of tmpfs for /dev/shm is working as expected:

# in fstab
tmpfs /dev/shm tmpfs   defaults,nodev,nosuid,nr_inodes=5k,mode=700,size=4G 0 0

tmpfs                                  13184288       2328   13181960   1% /run
tmpfs                                   4194304      41056    4153248   1% /dev/shm
tmpfs                                      5120          4       5116   1% /run/lock
tmpfs                                  65921432          0   65921432   0% /sys/fs/cgroup
tmpfs                                  65921432          0   65921432   0% /tmp
tmpfs                                  13184284          8   13184276   1% /run/user/1000

Also, it seems that the noexec option, although recommended by many security guides, is problematic because some programs (including apt) need to execute from /tmp. I understand that this can be gotten around, but I don't want to have to figure out every program that needs to be an exception.

I am about to do a custom installation of Ubuntu Desktop which requires some command line work. To save myself time, I created a text file of the commands I wanted to use un hope of copy-pasting them between tmux panes. Unfortunately, I am having trouble getting GPM to work.

In order to be able to install GPM, I added the universe repository, but after doing so I was able to install it.

When I run sudo systemctl enable gpm, I get a message that gpm is not a native service, redirecting to systemd-sysv-install. When I run sudo systemctl start gpm, the service fails to start. Running journalctl -xe revealed a likely sounding error: cannot open/dev/mouse.

As /dev/mouse did not exist, I tried making symbolic links to the likely looking things that do exist /dev/input/mouse0 and /dev/input/mice/. I was then able to run enable gpm without error, but no cursor appeared. The pointer works fine in the GUI though.

A look at systemctl status gpm showed it still whining about /dev/mouse.

I have installed gpm in the Arch installer and it worked fine without any configuration. What do I have to do to configure the Ubuntu installer live usb to use gpm in the console?

Edit: Partial success!

If I run gpm -m /dev/input/mice or gpm -m /dev/input/mouse0 gpm activates but does not work correctly. By that I mean that mouse input elicits a response, but not the right one.

Moving the mouse does a combination of scrolling, selecting, and copy-pasting while mouse clicks and the scroll wheel have no effect.

I just installed Ubuntu Server 20.04 and am trying to get GPU Passthrough working, but I can't seem to get VFIO enabled using methods that worked previously:

/etc/initramfs-tools/modules:

vfio
vfio_iommu_type1
vfio_pci
vfio_virqfd
vhost-net

/etc/default/grub:

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash iommu=1 amd_iommu=on vfio_pci.ids=10de:1b81,10de:10f0 vfio_iommu_type1.allow_unsafe_interrupts=1"
GRUB_CMDLINE_LINUX=

But it seems that VFIO is not enabled in the kernel.

~$  lsmod | grep kvm
kvm_amd                98304  0
kvm                   663552  1 kvm_amd
ccp                    86016  13 kvm_amd
~$ lsmod | grep vfio
~$ 

There is no way I can bind the drivers of my GPU to VFIO unless I can confirm that VFIO is enabled, correct?

Edit: I previously had passthrough and everything working beautifully for about a year under Arch. So this is clearly an Ubuntu thing. I am using a Thredripper 1950X on ASROck x399 Taichi.

Edit2: Some progress I got vfio_mdev loaded. Is that now in place of reguler vfio or do I still need to get vfio loaded?

$ sudo modprobe vfio_mdev
$ lsmod | grep -i vfio
vfio_mdev              16384  0
mdev                   24576  1 vfio_mdev

Edit 3: OK, so it seems that vfio is no longer a module, but is built into the kernel. https://forum.level1techs.com/t/ubuntu-20-04-missing-kernel-modules-for-vfio-pci-and-vfio-iommu-type1/156327/2

that indeed appears to be true:

~$ cat /boot/config-5.4.0-33-generic | grep -i vfio
CONFIG_KVM_VFIO=y
CONFIG_VFIO_IOMMU_TYPE1=y
CONFIG_VFIO_VIRQFD=y
CONFIG_VFIO=y
CONFIG_VFIO_NOIOMMU=y
CONFIG_VFIO_PCI=y
CONFIG_VFIO_PCI_VGA=y
CONFIG_VFIO_PCI_MMAP=y
CONFIG_VFIO_PCI_INTX=y
CONFIG_VFIO_PCI_IGD=y
CONFIG_VFIO_MDEV=m
CONFIG_VFIO_MDEV_DEVICE=m
# CONFIG_SAMPLE_VFIO_MDEV_MTTY is not set
# CONFIG_SAMPLE_VFIO_MDEV_MDPY is not set
# CONFIG_SAMPLE_VFIO_MDEV_MDPY_FB is not set
# CONFIG_SAMPLE_VFIO_MDEV_MBOCHS is not set

Ok, so if it's built-in, then it makes sense that lsmod would not show it as it is not a module. Is there some way to confirm that vfio is working. Is this output from dmesg enough to confirm that and move on to my next issue (that pci-alias' aren't working the way they did before). But that is another thread.

dmesg | grep -i -e vfio
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=/dev/mapper/main--VG-lvroot ro quiet splash iommu=1 amd_iommu=on vfio_pci vfio_iommu_type1.allow_unsafe_interrupts=1 vt.handoff=7
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=/dev/mapper/main--VG-lvroot ro quiet splash iommu=1 amd_iommu=on vfio_pci vfio_iommu_type1.allow_unsafe_interrupts=1 vt.handoff=7
[    0.532762] VFIO - User Level meta-driver version: 0.3

I just installed Ubuntu 20.04 and then installed xubuntu-core. When prompted, I chose lightdm as my login manager. I then disabled everything I could find related to screen locking, but I still have to enter my password after the screen goes off. Is there some crazy hidden setting I am missing?

I realize I could remove lightlocker, but why in this context does "disable" not mean disable? Is it a bug or a design decision?

I scripted my partition and LVM scheme for my last installation (that was of Arch Linux) I now want to switch to Ubuntu, but use the same scheme that I used before, which was separate pairs of mirrors for /home and /

However, the Ubuntu installer does not seem to allow me to use existing partitions. Is this possible with the Ubuntu installer, or do I have to do it through the interface. And can I script it somehow?

Edit: I realized I forgot to set the partition table of my usb as GPT, maybe that is why I couldn't select done even after adding the desired partion as /boot Edit2: I remade the usb with a GPT partition table, but while I was able to see the EFI partition I had previously made, but was not able to get the installer to use it.

And if I can't use my pre-existing partitions, can I at least do something equivalent to the "alternative" installer approach in Ubuntu 18.04? I recall this worked for me before: Install Ubuntu 18.04 desktop with RAID 1 and LVM on machine with UEFI BIOS

This is the partition scheme that worked for me under Arch and I was hoping to use with Ubuntu:

#!/bin/bash

yes | sgdisk --zap-all -g /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915160K
yes | sgdisk --zap-all -g /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915161E
yes | sgdisk --zap-all -g /dev/disk/by-id/ata-Samsung_SSD_860_EVO_250GB_S3YHNX0KC01493P
yes | sgdisk --zap-all -g /dev/disk/by-id/ata-Samsung_SSD_860_EVO_250GB_S3YHNX0KC01512Y
#set up partitions, making sure there is a separate /boot partition so that LVM can be mounted


# I picked the value of 6144KiB based on this https://bbs.archlinux.org/viewtopic.php?pid=1385980#p1385980
yes | parted --script /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915160K \
    mklabel GPT \
    mkpart ESP fat32 6144KiB 1% \
    set 1 boot on \
    name 1 efi \
    mkpart primary 1% 2% \
    name 2 boot \
    mkpart primary 2% 99% \
    name 3 lvm-root

yes | parted --script /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915161E \
    mklabel GPT \
    mkpart primary fat32 6144KiB 5% \
    name 1 efi-boot-backups \
    mkpart primary 5% 99% \
    name 2 lvm-snapshots-root


yes | parted --script /dev/disk/by-id/ata-Samsung_SSD_860_EVO_250GB_S3YHNX0KC01493P \
    mklabel GPT \
    mkpart primary 6144KiB 2% \
    name 1 emergency \
    mkpart primary 2% 99% \
    name 2 lvm-home

yes | parted --script /dev/disk/by-id/ata-Samsung_SSD_860_EVO_250GB_S3YHNX0KC01512Y \
    mklabel GPT \
    mkpart primary 6144KiB 2% \
    name 1 emergency2 \
    mkpart primary 2% 99% \
    name 2 lvm-snapshots-home 


yes| parted /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915160K set 3 lvm on
yes | parted /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915161E set 2 lvm on
yes | parted /dev/disk/by-id/ata-Samsung_SSD_860_EVO_250GB_S3YHNX0KC01493P set 2 lvm on
yes | parted /dev/disk/by-id/ata-Samsung_SSD_860_EVO_250GB_S3YHNX0KC01512Y set 2 lvm on

yes | pvcreate /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915160K-part3
yes | pvcreate /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915161E-part2
yes | pvcreate /dev/disk/by-id/ata-Samsung_SSD_860_EVO_250GB_S3YHNX0KC01493P-part2
yes | pvcreate /dev/disk/by-id/ata-Samsung_SSD_860_EVO_250GB_S3YHNX0KC01512Y-part2

yes | vgcreate main-VG /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915160K-part3
yes | vgextend main-VG /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915161E-part2

yes | vgextend main-VG /dev/disk/by-id/ata-Samsung_SSD_860_EVO_250GB_S3YHNX0KC01493P-part2
yes | vgextend main-VG /dev/disk/by-id/ata-Samsung_SSD_860_EVO_250GB_S3YHNX0KC01512Y-part2

vgdisplay

yes | lvcreate -L 60G main-VG -n lvroot /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915160K-part3
yes | lvcreate -L 16G main-VG -n lvtmp /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915160K-part3
yes | lvcreate -L 8G main-VG -n lvswap /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915160K-part3
yes | lvcreate -L 220G main-VG -n lvhome /dev/disk/by-id/ata-Samsung_SSD_860_EVO_250GB_S3YHNX0KC01493P-part2

#setupsnapshots
yes | lvcreate -L 100G -s -n /dev/main-VG/root_snap01 /dev/main-VG/lvroot
yes | lvcreate -L 240G -s -n /dev/main-VG/home_snap01 /dev/main-VG/lvhome

smartctl -l scterc,70,70 /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915160K
smartctl -l scterc,70,70 /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915161E
smartctl -l scterc,70,70 /dev/disk/by-id/ata-Samsung_SSD_860_EVO_250GB_S3YHNX0KC01493P
smartctl -l scterc,70,70 /dev/disk/by-id/ata-Samsung_SSD_860_EVO_250GB_S3YHNX0KC01512Y

yes | mkfs.f2fs /dev/main-VG/lvroot
yes | mkfs.f2fs /dev/main-VG/lvhome

yes | mkfs.ext4 /dev/main-VG/lvtmp
yes | mkfs.fat -F32 /dev/disk/by-id/ata-Samsung_SSD_850_EVO_120GB_S21SNX0H915160K-part1
yes | tune2fs -O "^has_journal /dev/main-VG/lvtmp"

yes | mkswap /dev/main-VG/lvswap
yes | swapon /dev/main-VG/lvswap

I downloaded Ubuntu Server 18.04.2 (classic installer) and put it on a flash drive. I then ran the integrity check and all was well. But then I realized that I wanted to install the HWE kernel. After selecting HWE kernel, the installer start screen reloads, and I wondered if I would get a different result if I ran the integrity check with the HWE kernel.

Turns out it did, and the EFI.img file failed the MD5 check. ./boot/grub/efi.img file failed the MD5 checksum

I double checked the SHA256 of the iso I used to burn the USB (made with USB creator), and it was fine, so I figured I must have a bunk USB stick. I tried another stick (this time using dd copy method) and got the same problem. I then tried a third USB stick of a different brand (again using dd), and still the same.

So is there a problem in the installer itself? Or does the exact same file keep getting corrupted every time I try to create the bootable USB?

Edit: Ok, now I am really confused. It seems that efi.img file becomes corrupted at some point during the check. Here is a sequence of shots to illustrate:

1. I booted from the UEFI partition of my USB drive (oddly, on all the USB drives I have made today, there are two UEFI partitions seen by the BIOS, not sure if this is relevant).
2. Next I ran the integrity check in the main menu: it passed:
3. Then I went into the HWE kernel and tried the integrity check from there, which failed (the original reason for this post).
4. Then this is the real kicker.. now when I run the integrity check from the main menu, I get the same error!! Did the act of doing the check somehow cause corruption?

And one other thing: What is the "classic" keyboard based installer called officially? I don't know what to file the bug under since it doesn't seem to have a handy name like "Subiquity".

Update: If I select sandisk instead of sandisk: uefi partition, that does a legacy boot with a different looking main menu. However then I cannot create UEFI partitions in the manual partition editor. Perhaps the EFI section is in use to boot the usb and that is why checksumming fails? Is the classic installer even maintained anymore?

I just installed Ubuntu server and XFCE4, however the desktop is completely different than any other xfce I have installed, with a gnome-like launcher and both Ubuntu and Debian screen backgrounds, as well as no start menu or panel. But Thunar is there.

I understand that there were a lot of changes to Xubuntu 19.04, but nothing I read about said anything about this. So take a look at my screenshot of a fresh install of Ubuntu Server + xfce4 (and a few utilities).

Is this expected (nevermind the checkerboard pattern thing, sometimes my graphics card does that).

Additional notes: This happened on two installs back-to-back. Also, the mouse tracking and stuff are really slow, although that could be due to having five monitors spread across three video cards, but I don't remember this being an issue in the past)

I want to use the latest version of QEMU (3.1) with my installation of Ubuntu Server 18.04.2. I have managed to install it, but it seems that the new installation is not correctly connected to all the dependencies (or perhaps I need to manually upgrade other packages to get them in sync with my upgraded QEMU?)

the error I got was:

ERROR    unsupported configuration: this QEMU does not support 'qxl' video device
Removing disk 'WINVM.img'                                   |    0 B  00:00     
Domain installation does not appear to have been successful.
If it was, you can restart your domain by running:
  virsh --connect qemu:///system start myWINVM
otherwise, please restart your installation.

Do my suspicions about the cause of the problem seem reasonable? What should I try to get QXL working again (it was working before the QEMU upgrade).

I messed up my Ubuntu 18.04.1 installation and decided to reinstall, which meant creating a new USB since I couldn't find the old one. To my surprise, the installer looked completely different than before, and had options it did not have before. For example before where I simply selected one of my network interfaces, I now choose "create bond" and then select the interface. It also appears that the manual configuration of RAID disks is different now. Unfortunately I don't have pictures from the previous installer, but here is a shot of the new one:

I am confused because this is ostensibly the exact same version that I downloaded before. Where are these changes documented? Were they officially announced someplace?

I am trying to install Ubuntu Server 18.04 on a pair of 128GB SSDs in RAID1. I followed the "advanced installation" instructions on the Ubuntu help site: https://help.ubuntu.com/lts/serverguide/advanced-installation.html

It seems to have gone well in that when I boot with Gparted I can see the RAID volume and it looks like I expect it to (two drives two partitions each), I cannot see the drives in BIOS (and the installer said that in completed successfully).

Based on other threads, (such as How to install Ubuntu 14.04/16.04 64-bit with a dual-boot RAID 1 partition on an UEFI/GPT system? ) I understand that there needs to be a boot partition, but I thought that was the point of the "boot flag" option that I picked for the partitions that I want to install on. Since the instructions tell me create a new partition table and explicitly tell me to make swap and install partitions, I did not manually create a boot partition prior to creating the swap partition. Because if I was supposed to make a boot partition, they would have told me to make a partition of a few hundred Mb after creating the partition table and before creating the swap partition, right?

Is there something missing from the instructions or am I missing something? I am going to destroy my RAID volume and restart the installation, doing what I just suggested and will report back. But the documentation seems so thorough, could that really have been left out?