Headless Ubuntu Server 24.04 Auto-Install via USB (UEFI + Ventoy)

Goal

I’m trying to create a USB drive that can install Ubuntu Server 24.04 on multiple bare-metal nodes in a fully headless way.

Expected Outcome

• Boot priority set to USB HDD

• System installs automatically with no monitor, keyboard, or mouse

• No manual input required at any stage

• OS installs on the only internal drive present (each node has exactly one disk)

• Swap should be disabled

• Works across nodes with:

  • Different CPUs

  • Different RAM sizes

  • Different storage devices (NVMe / SATA SSD)

Current Setup

• USB created using Ventoy

• ISO Image -> ubuntu-24.04.4-live-server-amd64.iso

• ventoy.json configured to load user-data for autoinstall
  → This part is working

• BIOS set to UEFI only

• Verified:

  /sys/firmware/efi
  

  exists, so system is booting in UEFI mode

What’s Working

• Ubuntu ISO boots

• Autoinstall is triggered

• Cloud-init reads user-data

Issue

I’m getting the following error during installation:
Error Snapshot

Questions

1. What is the correct generic storage config for:

   • Single disk (any size)

   • GPT

   • EFI partition

   • Root partition

   • No swap

2. Is there a recommended minimal storage: config for heterogeneous hardware?

3. Is there anything specific required for UEFI-only autoinstall setups?

Additional Context

• No PXE — USB-only deployment

• Goal is repeatable install across homelab nodes

• Ubuntu Server 24.04 LTS

• Headless-only environment

user-data file

#cloud-config
autoinstall:
  version: 1
  apt:
    fallback: offline-install
  install:
    mode: minimized
  locale: en_US.UTF-8
  keyboard:
    layout: us
  timezone: Asia/Kolkata
  drivers:
    install: true
  identity:
    realname: Maverick
    username: maverick
    password: "my_hash_here"
    hostname: pn-01
  ssh:
    install-server: true
    allow-pw: true
  storage:
    layout:
      name: lvm
    wipe: superblock-recursive
    swap:
      size: 0
  network:
    version: 2
    ethernets:
      all_interfaces:
        match:
          name: "e*"
        dhcp4: true
        macaddress: permanent
        dhcp-identifier: mac
        optional: true
  packages:
    - micro
    - htop
    - screenfetch
    - net-tools
    - iperf3
    - curl
    - fio
  late-commands:
    - curtin in-target -- target swapoff -a
    - curtin in-target -- target sed -i '/swap/d' /etc/fstab
    - curtin in-target -- target apt-get purge -y cloud-init
    - curtin in-target -- target rm -rf /etc/cloud/ /var/lib/cloud/
    - curtin in-target -- target apt-get autoremove -y

I set my bash script called pass.sh globally by adding its source path into $PATH in my ./bashrc.

The problem is I can't execute using the sh only using the bash command when I'm in a different directory.

Here is the script's content:

#!/bin/bash

target_account=$1

file_source="/home/ade/Documents/area/passwords/password.txt"

grep -C 4 $target_account $file_source

Here is what happens when I execute it using sh:

sh: 0: cannot open pass.sh: No such file

Is it all because it's incompatible with bash?

In the recent upgrade, the following packages changed:

Start-Date: 2026-02-28  19:10:05
Commandline: aptdaemon role='role-commit-packages' sender=':1.3465'
Upgrade: google-chrome-stable:amd64 (145.0.7632.109-1, 145.0.7632.116-1), software-properties-common:amd64 (0.99.49.3, 0.99.49.4), python3-software-properties:amd64 (0.99.49.3, 0.99.49.4), software-properties-gtk:amd64 (0.99.49.3, 0.99.49.4), linux-firmware:amd64 (20240318.git3b128b60-0ubuntu2.23, 20240318.git3b128b60-0ubuntu2.25), brave-browser:amd64 (1.87.190, 1.87.191)
End-Date: 2026-02-28  19:10:25 

Today, I discovered that my this upgrade caused my system 32GB of RAM to show up as 4GB of RAM. I suspect that linux-firmware:amd64 (20240318.git3b128b60-0ubuntu2.23, 20240318.git3b128b60-0ubuntu2.25) caused this issue.

How do I undo this problem?

I’m reaching out to seek some guidance regarding an issue I'm experiencing with my Ubuntu Pro personal subscription.

Issue overview:

I recently registered for Ubuntu Pro (Personal), which offers access for up to five machines. Currently I have a couple of virtual machines running Ubuntu Server on Proxmox.

1. After I executed the command sudo pro attach "token" on one VM, the dashboard initially showed that I had used 2 of the 5 available slots.

2. Then, when I attached another VM, the dashboard indicated that I had used 4 slots, even though I only ran the command once on each server.

3. Following some advice I found online, I detached the VMs and reattached them, but now it shows that I have used all 5 slots.

Details:

• Ubuntu version: 24.04.4 (both VMs)

• Proxmox version: VE 8.4.17

• Current slot usage: Now it's showing as 5. I only attached 2 servers using the same to token.

I’m a little confused and would appreciate any insights or explanations regarding why my usage count is behaving this way. Has anyone else experienced something similar?

Well, I have been working to get an internal bridge set up in Ubuntu desktop 22.04. I was cleaning up to try again and nuked my network adapter setup (which had been working). The adapter now shows up in the edit connection page in nmtui but does not show up in the activate page, and sudo lshw -c network shows the network is unclaimed.

Would someone be able to point me toward a fix, please?

I'm a voice actor and I recently had a session with a game developer who wanted to do some live direction. We jumped into a Zoom call and I discovered the following:

• Zoom was using my webcam microphone with no option to select the studio mic.
• Zoom was using my headphones.
• Audacity was using my studio microphone.
• Audacity was not using my headphones.

As such, the client could only hear the crappy, webcam audio instead of the studio mic. While Audacity was recording with the correct microphone, playback wasn't audible to any of us (luckily, I didn't have to do any playback for them during the session). Once I exited Zoom, all of my audio devices showed up in Audacity's dropdown menus again. It's like the programs take ownership of the hardware and don't feel like sharing at all.

tl;dr - I'm trying to get multiple applications (Zoom and Audacity) to use the same microphone and headphones at the same time, hopefully without having to add yet more hardware into the chain (like a mixer).

I'm new to Linux, and I'm trying to install WinApps, but I keep getting the same error message of Exiting with status '1'.

omar@omarlaptop:~$ cd ~/.config/winapps/
omar@omarlaptop:~/.config/winapps$ sudo nano ~/.config/winapps/winapps.conf

[sudo] password for omar: 
omar@omarlaptop:~/.config/winapps$ sudo nano ~/.config/winapps/winapps.conf
omar@omarlaptop:~/.config/winapps$ bash <(curl https://raw.githubusercontent.com/winapps-org/winapps/main/setup.sh)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 89623  100 89623    0     0   144k      0 --:--:-- --:--:-- --:--:--  143k
###############################################################################
#                                                                             #
#                             WinApps Install Wizard                          #
#                                                                             #
###############################################################################

Q) Install or uninstall WinApps? --> Install
Q) Configure WinApps for the current user 'omar' or the whole system? --> Current User
Q) Automatically install supported applications or choose manually? --> Manual (Default)

WinApps installation already present at /home/omar/.local/bin/winapps-src. Updating...
Already up to date.
Installing WinApps.
Checking for existing conflicting WinApps installations... Done!
Attempting to load WinApps configuration file... Done!
Checking whether dependencies are installed... Done!
Checking container status... permission denied while trying to connect to the docker API at unix:///var/run/docker.sock
Exiting with status '1'.

When installing VMware Workstation 17.6.4 on Ubuntu 24.04.4, this dialog appears:

...several modules must be compiled and loaded into the running kernel

but this stops, because...

The kernel was built by: x86_64-linux-gnu-gcc-13  
 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0  
You are using: gcc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0  

How do I insert x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0 into my 24.04.4 in order to compile the 2 modules, vmmon and vmnet, and load them into the running kernel?

EDIT #3: I am putting this edit at the top because it changes some things, I think.

Since my last edit my network card stopped working and wifi started showing up as an ethernet card. So then, I reinstalled Ubuntu 24.04, this changed nothing. Then I tried booting Ubuntu 24.03 from USB, same thing except the GPU fans turn off slightly earlier than with Ubuntu 24.04.

Then I tried booting a USB with Mint 22.1 which is on the 6.8.0-51-generic kernel and the GPU fans stay on and the GPU seems to be working, although I could not fully test it using a bare bones Mint boot disk.

What am I missing here? Id expect mint to be the distro with compatibility issues with new hardware.

I have a newly built computer, the GPU is a Radeon RX 9070 XT and the motherboard is an MSI Pro X870E-P WiFi (UEFI is up to date).

I am getting display from the GPU (HDMI) and the GPU's fans turn on when the computer is started but then turn off as soon as the Ubuntu log appears.

I don't really know what I am doing as far as terminal commands go and, for the most part, I don't know what any of the output information means, but the commands that I've found from searching the web all seem to show that the Radeon RX 9070 XT is being recognized by the OS. Furthermore, I tried a couple of diagnostic programs like the Linux hardware probe and they all show that "it's working". However, the GPU seems to be not available to some programs like Blender.

I've been trying to figure this out for weeks but everything that I am finding says that Ubuntu already has the drivers I need so I have no idea what I'm supposed to do. I'm hoping that there's someone out there with the patience to walk me through this.

$ uname -a

Linux work-MS-7E70 6.17.0-14-generic #14~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 15 15:52:10 UTC x86_64 x86_64 x86_64 GNU/Linux

I have not seen any explicit error messages. However, the GPU does not seem to be utilized at all, its temperature readings stay very low, and performance seems to be on par with the CPU's integrated GPU. In Blender there is a settings menu to select the GPU to use for Cycles rendering, it says "No compatible device found".

Edit: I have done some more testing

I have launched various programs using DGPU / IGPU. Some programs fail to open a window using DGPU, some do not fail but when launched with IGPU show the IGPU as having the same LLVM target name as the DGPU.

Edit 2: I just confirmed this using the program "System Profiler and Benchmark". When I launch it normally it displays the graphics card as:

AMD RADEON RX 9070 XT (radeonsi, gfx1201, ACO, DRM 3.64, 6.17.0-14-generic)

But, when I right click and launch using Discrete Graphics Card:

AMD Ryzen 9 9900X 12-Core Processor (radeonsi, raphael_mendocino, ACO, DRM 3.64, 6.17.0-14-generic)

I am typing this because i do not want to make a mistake during install, is the LUKS encryption worth it? I found a question where somebody wanted to enable LUKS post-install and turned out to need to reinstall ubuntu. What are pros and cons of LUKS? And can you disable it post-install? (The version i want to install is 24.04 LTS)

Edit: Editing this so it gets re-opened. I am going to be mostly using my laptop in house, but im very worried about malware, even if linux barely gets any. (windows habit)

Edit 2: To clarify things, i am asking if LUKS will be useful for my case, not asking feedback or opinions of users.

A recent auto-upgrade from 6.14.0-37 to 6.17.0-14 yields a kernel panic at boot: Unable to mount root fs Unknown Block (0,0)

To get the machine up I have to select 6.14.0-37 from the GRUB boot menu. I can no longer do a normal boot/reboot because GRUB auto boots the newest (bad) kernel. I want to remove 6.17.0-14 from the GRUB menu.

All the help articles I've found instruct how to remove old kernel versions. How do I remove the NEWEST kernel version and retain the oldest in GRUB?

In reply to @heynnema:

ls -al /boot | grep init
lrwxrwxrwx  1 root root       28 Feb 22 08:04 initrd.img -> initrd.img-6.17.0-14-generic
-rw-r--r--  1 root root 75369010 Feb 22 08:00 initrd.img-6.14.0-37-generic
lrwxrwxrwx  1 root root       28 Feb 22 06:24 initrd.img.old -> initrd.img-6.14.0-37-generic

In reply to guiverc:

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04.4 LTS
Release:    24.04
Codename:   noble

In reply to david, looks like a DKMS build issue: etting up linux-image-6.17.0-14-generic (6.17.0-14.14~24.04.1) ... Setting up linux-headers-6.17.0-14-generic (6.17.0-14.14~24.04.1) ... /etc/kernel/header_postinst.d/dkms:

• dkms: running auto installation service for kernel 6.17.0-14-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module: Cleaning build area... make -j24 KERNELRELEASE=6.17.0-14-generic -C /lib/modules/6.17.0-14-generic/build M=/var/lib/dkms/virtualbox/7.0.16/build...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/virtualbox-dkms.0.crash' Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64) Consult /var/lib/dkms/virtualbox/7.0.16/build/make.log for more information. dkms autoinstall on 6.17.0-14-generic/x86_64 failed for virtualbox(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information.

• dkms: autoinstall for kernel 6.17.0-14-generic ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.17.0-14-generic (--configure): installed linux-headers-6.17.0-14-generic package post-installation script subprocess returned error exit status 11 dpkg: dependency problems prevent configuration of linux-headers-generic-hwe-24.04: linux-headers-generic-hwe-24.04 depends on linux-headers-6.17.0-14-generic; however: Package linux-headers-6.17.0-14-generic is not configured yet.

dpkg: error processing package linux-headers-generic-hwe-24.04 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic-hwe-24.04: linux-generic-hwe-24.04 depends on linux-headers-generic-hwe-24.04 (= 6.17.0-14.14~24.04.1); however: Package linux-headers-generic-hwe-24.04 is not configured yet.

dpkg: error processing package linux-generic-hwe-24.04 (--configure): dependency problems - leaving unconfigured Processing triggers for linux-image-6.17.0-14-generic (6.17.0-14.14~24.04.1) ... /etc/kernel/postinst.d/dkms:

• dkms: running auto installation service for kernel 6.17.0-14-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... make -j24 KERNELRELEASE=6.17.0-14-generic -C /lib/modules/6.17.0-14-generic/build M=/var/lib/dkms/virtualbox/7.0.16/build...(bad exit status: 2) ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/virtualbox-dkms.0.crash' Error! Bad return status for module build on kernel: 6.17.0-14-generic (x86_64) Consult /var/lib/dkms/virtualbox/7.0.16/build/make.log for more information. dkms autoinstall on 6.17.0-14-generic/x86_64 failed for virtualbox(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information.
• dkms: autoinstall for kernel 6.17.0-14-generic ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.17.0-14-generic (--configure): installed linux-image-6.17.0-14-generic package post-installation script subprocess returned error exit status 11 Errors were encountered while processing: linux-headers-6.17.0-14-generic linux-headers-generic-hwe-24.04 linux-generic-hwe-24.04 linux-image-6.17.0-14-generic

DKMS issue relates to building the VirtulBox 7.0.16 kernel module

As many users, I'm having problems with the bluetooth. I'm using Linux 6.8.0-45-generic on x86_64 #45-Ubuntu 24.04.1 LTS, just freshly installed.
When I go on Settings -> Bluetooth and click the toggle to enable, it instantly disables itself.

My laptop is just bought and you can see the full specs here

I tried to follow most of the steps in

• I can't turn on Bluetooth in Ubuntu 22.04 LTS
• https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592

None solved the problem.
I cannot remove the battery from my laptop, so I tried the disable/enable on the bios trick but did not help.

The main error message reported is:

• Bluetooth: hci0: Opcode 0x0c03 failed: -110

sudo dmesg | grep -i blue
[    2.511496] Bluetooth: Core ver 2.22
[    2.511532] NET: Registered PF_BLUETOOTH protocol family
[    2.511535] Bluetooth: HCI device and connection manager initialized
[    2.511548] Bluetooth: HCI socket layer initialized
[    2.511553] Bluetooth: L2CAP socket layer initialized
[    2.511561] Bluetooth: SCO socket layer initialized
[    4.437283] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.437291] Bluetooth: BNEP filters: protocol multicast
[    4.437307] Bluetooth: BNEP socket layer initialized
[    4.675379] Bluetooth: hci0: Opcode 0x0c03 failed: -110

But differently from many other people who reported the error, when I check the status of bluetooth.service it says active:

sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
     Active: active (running) since Tue 2024-09-17 13:17:46 BST; 21min ago
       Docs: man:bluetoothd(8)
   Main PID: 949 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 37564)
     Memory: 2.8M (peak: 3.1M)
        CPU: 51ms
     CGroup: /system.slice/bluetooth.service
             └─949 /usr/libexec/bluetooth/bluetoothd

Sep 17 13:17:46 matrix bluetoothd[949]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Sep 17 13:17:46 matrix bluetoothd[949]: src/plugin.c:plugin_init() System does not support micp plugin
Sep 17 13:17:46 matrix bluetoothd[949]: src/plugin.c:plugin_init() System does not support vcp plugin
Sep 17 13:17:46 matrix bluetoothd[949]: src/plugin.c:plugin_init() System does not support mcp plugin
Sep 17 13:17:46 matrix bluetoothd[949]: src/plugin.c:plugin_init() System does not support bass plugin
Sep 17 13:17:46 matrix bluetoothd[949]: src/plugin.c:plugin_init() System does not support bap plugin
Sep 17 13:17:46 matrix bluetoothd[949]: Bluetooth management interface 1.22 initialized
Sep 17 13:17:46 matrix systemd[1]: Starting bluetooth.service - Bluetooth service...
Sep 17 13:17:46 matrix (uetoothd)[949]: bluetooth.service: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (>
Sep 17 13:17:46 matrix systemd[1]: Started bluetooth.service - Bluetooth service.

Does anyone have any tips of what could I try/check?

Edited: Adding lsusb output as requested.

$ lsusb; sudo dmesg| grep -i firm
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 13d3:3585 IMC Networks Wireless_Device
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 2b7e:c858 Kingcome FHD WebCam
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

It's an internal blutooth not a usb one... but added in case I'm missing something.

I faced the same issue as described in this r/linuxquestions reddit comment , but for pipewire instead.

In a nutshell: By default, the audio controllers and system allow apps to switch from high quality A2DP to HSP/HFP profiles, which happens because apps force you to use the mic of the bluetooth headset, which requires the low quality HSP profile, as far as I am aware. This happens for example in MS Teams, GMeet, and others.

I want to mirror two displays (laptop and left display) and extend a third (right display).

If that is unclear, I found a substantially equivalent question at How to "overlay"/clone displays in GNOME Wayland that includes some handy images showing two displays are mirrored and one is extended.

Sadly, the only answer was to try something manual. Under Xorg, it is easy to do this with xrandr so I am disappointed that I don't find a simple solution in Wayland / Ubuntu 22.04.

I found a "manual" and quite ugly solution, but I hope there is a better way. I will eventually post the manual solution in detail if there are no better options. In brief, I saved ~/.config/monitors.xml multiple times while changing config, inferred which configuration was active and how to mirror two displays, edited a single <logicalmonitor> to contain the two <monitor> instances that are mirrored, and rebooted.

Ubuntu18.04, GPU GeForce 2070S

I upgraded GPU driver from 460 to 470, using commands:

sudo apt-add-repository -r ppa:graphics-drivers/ppa
sudo apt remove nvidia*
sudo apt autoremove
sudo ubuntu-drivers autoinstall

after reboot, no networks and bluetooth ;(

> ping 8.8.8.8
connect: Network is unreachable

> sudo service networking status
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: active (exited) since Thu 2021-09-23 23:56:31 CST; 24h ago
     Docs: man:interfaces(5)
  Process: 9891 ExecStop=/sbin/ifdown -a --read-environment --exclude=lo (code=exited, status=0/SUCCESS)
  Process: 9972 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS)
  Process: 9962 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=1/FAILURE)
 Main PID: 9972 (code=exited, status=0/SUCCESS)

9月 23 23:56:31 fey-pc systemd[1]: Starting Raise network interfaces...
9月 23 23:56:31 fey-pc systemd[1]: Started Raise network interfaces.

> sudo service bluetooth status
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:bluetoothd(8)

> sudo ifconfig -a
br-0edafad07ad9: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.19.0.1  netmask 255.255.0.0  broadcast 172.19.255.255
        inet6 fe80::42:2ff:fedf:94e2  prefixlen 64  scopeid 0x20<link>
        ether 02:42:02:df:94:e2  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 331  bytes 48011 (48.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-ab415028e09a: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 172.18.255.255
        ether 02:42:18:4f:89:44  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        ether 02:42:cc:31:62:ec  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 71164  bytes 47374312 (47.3 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 71164  bytes 47374312 (47.3 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I check apt log

> less /var/log/apt/history.log

Start-Date: 2021-09-23  22:48:59
Commandline: apt remove nvidia*
Requested-By: fey (1000)
Remove: nvidia-kernel-common-460:amd64 (460.91.03-0ubuntu0.18.04.1), nvidia-modprobe:amd64 (384.111-2), nvidia-utils-460:amd64 (460.91.03-0ubuntu0.18.04.1), nvidia-prime:amd64 (0.8.16~0.18.04.1), nvidia-dkms-460:amd64 (460.91.03-0ubuntu0.18.04.1), nvidia-compute-utils-460:amd64 (460.91.03-0ubuntu0.18.04.1), nvidia-driver-440:amd64 (450.119.03-0ubuntu0.18.04.1), nvidia-driver-450:amd64 (460.91.03-0ubuntu0.18.04.1), nvidia-driver-460:amd64 (460.91.03-0ubuntu0.18.04.1), nvidia-kernel-source-460:amd64 (460.91.03-0ubuntu0.18.04.1), nvidia-settings:amd64 (470.57.01-0ubuntu0.18.04.1)
End-Date: 2021-09-23  22:49:15

Start-Date: 2021-09-23  22:49:25
Commandline: apt autoremove
Requested-By: fey (1000)
Remove: libdrm-nouveau2:i386 (2.4.101-2~18.04.1), libnvidia-compute-460:i386 (460.91.03-0ubuntu0.18.04.1), libnvidia-encode-460:amd64 (460.91.03-0ubuntu0.18.04.1), libnvidia-encode-460:i386 (460.91.03-0ubuntu0.18.04.1), xserver-xorg-video-nvidia-460:amd64 (460.91.03-0ubuntu0.18.04.1), libpciaccess0:i386 (0.14-1), libnvidia-gl-460:amd64 (460.91.03-0ubuntu0.18.04.1), libnvidia-gl-460:i386 (460.91.03-0ubuntu0.18.04.1), libgl1:i386 (1.0.0-2ubuntu2.3), libnvidia-fbc1-460:amd64 (460.91.03-0ubuntu0.18.04.1), libnvidia-fbc1-460:i386 (460.91.03-0ubuntu0.18.04.1), libelf1:i386 (0.170-0.4ubuntu0.1), libnvidia-decode-460:amd64 (460.91.03-0ubuntu0.18.04.1), libnvidia-decode-460:i386 (460.91.03-0ubuntu0.18.04.1), linux-headers-5.3.0-53-generic:amd64 (5.3.0-53.47~18.04.1), libnvidia-cfg1-460:amd64 (460.91.03-0ubuntu0.18.04.1), dkms:amd64 (2.3-3ubuntu9.7), libdrm-amdgpu1:i386 (2.4.101-2~18.04.1), libllvm10:i386 (1:10.0.0-4ubuntu1~18.04.2), libnvidia-ifr1-460:amd64 (460.91.03-0ubuntu0.18.04.1), libnvidia-ifr1-460:i386 (460.91.03-0ubuntu0.18.04.1), libglx0:i386 (1.0.0-2ubuntu2.3), libgl1-mesa-dri:i386 (20.0.8-0ubuntu1~18.04.1), screen-resolution-extra:amd64 (0.17.3), libxdamage1:i386 (1:1.1.4-3), linux-headers-5.3.0-53:amd64 (5.3.0-53.47~18.04.1), libedit2:i386 (3.1-20170329-1), libdrm-intel1:i386 (2.4.101-2~18.04.1), libdrm-radeon1:i386 (2.4.101-2~18.04.1), libnvidia-common-460:amd64 (460.91.03-0ubuntu0.18.04.1), libatomic1:i386 (8.4.0-1ubuntu1~18.04), libnvidia-extra-460:amd64 (460.91.03-0ubuntu0.18.04.1), libxcb-glx0:i386 (1.13-2~ubuntu18.04), libsensors4:i386 (1:3.4.0-4), libglx-mesa0:i386 (20.0.8-0ubuntu1~18.04.1)
End-Date: 2021-09-23  22:49:33

Start-Date: 2021-09-23  22:51:09
Commandline: apt-get install -o DPkg::options::=--force-confnew -y nvidia-driver-470 linux-modules-nvidia-470-generic-hwe-18.04-edge
Requested-By: fey (1000)
Install: libdrm-nouveau2:i386 (2.4.101-2~18.04.1, automatic), linux-image-5.4.0-86-generic:amd64 (5.4.0-86.97~18.04.1, automatic), libnvidia-compute-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-compute-470:i386 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-encode-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-encode-470:i386 (470.63.01-0ubuntu0.18.04.2, automatic), nvidia-kernel-common-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libpciaccess0:i386 (0.14-1, automatic), xserver-xorg-video-nvidia-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-gl-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-gl-470:i386 (470.63.01-0ubuntu0.18.04.2, automatic), libgl1:i386 (1.0.0-2ubuntu2.3, automatic), libnvidia-fbc1-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-fbc1-470:i386 (470.63.01-0ubuntu0.18.04.2, automatic), libelf1:i386 (0.170-0.4ubuntu0.1, automatic), libnvidia-decode-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-decode-470:i386 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-cfg1-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), nvidia-utils-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), nvidia-prime:amd64 (0.8.16~0.18.04.1, automatic), libdrm-amdgpu1:i386 (2.4.101-2~18.04.1, automatic), libllvm10:i386 (1:10.0.0-4ubuntu1~18.04.2, automatic), linux-signatures-nvidia-5.4.0-86-generic:amd64 (5.4.0-86.97~18.04.1, automatic), linux-modules-5.4.0-86-generic:amd64 (5.4.0-86.97~18.04.1, automatic), nvidia-compute-utils-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), linux-modules-nvidia-470-generic-hwe-18.04-edge:amd64 (5.4.0-86.97~18.04.1), libnvidia-ifr1-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libnvidia-ifr1-470:i386 (470.63.01-0ubuntu0.18.04.2, automatic), nvidia-driver-470:amd64 (470.63.01-0ubuntu0.18.04.2), libglx0:i386 (1.0.0-2ubuntu2.3, automatic), libgl1-mesa-dri:i386 (20.0.8-0ubuntu1~18.04.1, automatic), screen-resolution-extra:amd64 (0.17.3, automatic), libxdamage1:i386 (1:1.1.4-3, automatic), libedit2:i386 (3.1-20170329-1, automatic), libdrm-intel1:i386 (2.4.101-2~18.04.1, automatic), libdrm-radeon1:i386 (2.4.101-2~18.04.1, automatic), libnvidia-common-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libatomic1:i386 (8.4.0-1ubuntu1~18.04, automatic), linux-objects-nvidia-470-5.4.0-86-generic:amd64 (5.4.0-86.97~18.04.1, automatic), libnvidia-extra-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), libxcb-glx0:i386 (1.13-2~ubuntu18.04, automatic), libsensors4:i386 (1:3.4.0-4, automatic), nvidia-kernel-source-470:amd64 (470.63.01-0ubuntu0.18.04.2, automatic), nvidia-settings:amd64 (470.57.01-0ubuntu0.18.04.1, automatic), linux-modules-nvidia-470-5.4.0-86-generic:amd64 (5.4.0-86.97~18.04.1, automatic), libglx-mesa0:i386 (20.0.8-0ubuntu1~18.04.1, automatic)
Remove: libnvidia-compute-460:amd64 (460.91.03-0ubuntu0.18.04.1)
End-Date: 2021-09-23  22:52:01

Start-Date: 2021-09-23  23:26:26
Commandline: apt autoremove
Requested-By: fey (1000)
Remove: linux-modules-5.4.0-78-generic:amd64 (5.4.0-78.87~18.04.1), linux-image-5.4.0-77-generic:amd64 (5.4.0-77.86~18.04.1), linux-image-5.4.0-78-generic:amd64 (5.4.0-78.87~18.04.1), linux-modules-extra-5.4.0-77-generic:amd64 (5.4.0-77.86~18.04.1), linux-headers-5.4.0-78-generic:amd64 (5.4.0-78.87~18.04.1), linux-hwe-5.4-headers-5.4.0-77:amd64 (5.4.0-77.86~18.04.1), linux-hwe-5.4-headers-5.4.0-78:amd64 (5.4.0-78.87~18.04.1), linux-headers-5.4.0-77-generic:amd64 (5.4.0-77.86~18.04.1), linux-modules-extra-5.4.0-78-generic:amd64 (5.4.0-78.87~18.04.1), linux-modules-5.4.0-77-generic:amd64 (5.4.0-77.86~18.04.1)
End-Date: 2021-09-23  23:26:35

other info

> uname -r
5.4.0-86-generic

> dpkg -l | grep 'linux-' | grep '^ii'
ii  binutils-x86-64-linux-gnu                       2.30-21ubuntu1~18.04.5                           amd64        GNU binary utilities, for x86-64-linux-gnu target
ii  linux-base                                      4.5ubuntu1.6                                     all          Linux image base package
ii  linux-firmware                                  1.173.20                                         all          Firmware for Linux kernel drivers
ii  linux-generic-hwe-18.04                         5.4.0.81.91~18.04.73                             amd64        Complete Generic Linux kernel and headers
ii  linux-headers-5.4.0-81-generic                  5.4.0-81.91~18.04.1                              amd64        Linux kernel headers for version 5.4.0 on 64 bit x86 SMP
ii  linux-headers-generic-hwe-18.04                 5.4.0.81.91~18.04.73                             amd64        Generic Linux kernel headers
ii  linux-hwe-5.4-headers-5.4.0-81                  5.4.0-81.91~18.04.1                              all          Header files related to Linux kernel version 5.4.0
ii  linux-image-5.4.0-81-generic                    5.4.0-81.91~18.04.1                              amd64        Signed kernel image generic
ii  linux-image-5.4.0-86-generic                    5.4.0-86.97~18.04.1                              amd64        Signed kernel image generic
ii  linux-image-generic-hwe-18.04                   5.4.0.81.91~18.04.73                             amd64        Generic Linux kernel image
ii  linux-libc-dev:amd64                            4.15.0-154.161                                   amd64        Linux Kernel Headers for development
ii  linux-modules-5.4.0-81-generic                  5.4.0-81.91~18.04.1                              amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-5.4.0-86-generic                  5.4.0-86.97~18.04.1                              amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-extra-5.4.0-81-generic            5.4.0-81.91~18.04.1                              amd64        Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii  linux-modules-nvidia-470-5.4.0-86-generic       5.4.0-86.97~18.04.1                              amd64        Linux kernel nvidia modules for version 5.4.0-86
ii  linux-modules-nvidia-470-generic-hwe-18.04-edge 5.4.0-86.97~18.04.1                              amd64        Extra drivers for nvidia-470 for the generic-hwe-18.04-edge flavour
ii  linux-objects-nvidia-470-5.4.0-86-generic       5.4.0-86.97~18.04.1                              amd64        Linux kernel nvidia modules for version 5.4.0-86 (objects)
ii  linux-signatures-nvidia-5.4.0-86-generic        5.4.0-86.97~18.04.1                              amd64        Linux kernel signatures for nvidia modules for version 5.4.0-86-generic
ii  linux-signed-generic-hwe-18.04                  5.3.0.62.115                                     amd64        Complete Signed Generic Linux kernel and headers (dummy transitional package)
ii  linux-sound-base                                1.0.25+dfsg-0ubuntu5                             all          base package for ALSA and OSS sound systems
ii  syslinux-common                                 3:6.03+dfsg1-2ubuntu0.18.04.2                    all          collection of bootloaders (common)
ii  syslinux-legacy                                 2:3.63+dfsg-2ubuntu9                             amd64        Bootloader for Linux/i386 using MS-DOS floppies

> lspci -vvv
...
22:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
    Subsystem: Micro-Star International Co., Ltd. [MSI] RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 0, Cache Line Size: 64 bytes
    Interrupt: pin A routed to IRQ 10
    Region 0: I/O ports at f000 [size=256]
    Region 2: Memory at f7504000 (64-bit, non-prefetchable) [size=4K]
    Region 4: Memory at f7500000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: <access denied>
...

however, nvidia driver works well

> nvidia-smi
Sat Sep 25 00:43:24 2021       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.63.01    Driver Version: 470.63.01    CUDA Version: 11.4     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:26:00.0  On |                  N/A |
| 33%   36C    P8    21W / 215W |    572MiB /  7974MiB |      1%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
                                                                               
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      2194      G   /usr/bin/gnome-shell               88MiB |
|    0   N/A  N/A      3776      G   /usr/lib/xorg/Xorg                233MiB |
|    0   N/A  N/A      4000      G   /usr/bin/gnome-shell              183MiB |
|    0   N/A  N/A      4890      G   ...AAAAAAAAA= --shared-files       10MiB |
|    0   N/A  N/A      5757      G   gnome-control-center                2MiB |
|    0   N/A  N/A     11742      G   ...AAAAAAAAA= --shared-files       40MiB |
+-----------------------------------------------------------------------------+

Thanks for your help

This question has been asked in different ways over time. Specifically, given current versions, I'd like to chart memory usage of processes over time, ideally in comparison with other processes.

Use case: With regular updates I'll reboot my Ubuntu systems once every couple weeks - a required process for which Linux fans used to mock Windows users. If I don't restart for maybe three weeks or a month, the system eventually becomes inaccessible, with the console reporting out of memory conditions. To determine which process(es) is/are responsible for this I want to see which processes consume and then do not release memory. A graph should show at least one process with an average consumption that is greater than its release - until memory is exhausted. That is - a line graph should should show one or more processes continuing to go up from one reboot to the next.

I understand that I can craft a solution with RRDtool, pidstat, ps in a cron, etc. Before I create a DIY project I'd like to know if there is an existing tool that already does this. I have to believe there is. Of course if I have to create it, I'll FOSS it. Thanks.

I'm running a pretty vanilla Ubuntu 20.04 on a ThinkPad L490 and occasionally (I'd say it's about a 10% chance, I can't make out any pattern) it gets stuck during the boot process. I get stuck at a black screen with these error messages during boot:

[  17.565121] Bluetooth: hci0: Applying Intel DDC parameters completed
[  17.621860] NET: Registered protocol family 38
[  32.769553] kauditd_printk_skb: 40 callbacks suppressed
[  32.769553] audit: type=1400 audit(1601618595.284:52): apparmor="STATUS" operation=
[  32.774318] iwlwifi 0000:05:00.0: Applying debug destination EXTERNAL_DRAM
[  32.890383] iwlwifi 0000:05:00.0: Applying debug destination EXTERNAL_DRAM
[  32.968589] iwlwifi 0000:05:00.0: FW already configured (0) - re-configuring
[FAILED] Failed to start LSB: Record successful boot for GRUB.
See 'systemctl status grub-common.service' for details.
[FAILED]Failed to start Snap Daemon.
See 'systemctl status snapd.service' for details.
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
         Starting Wait until snapd is fully seeded...
[  OK  ] Stopped Login Service.
         Starting Login Service...
[  OK  ] Stopped Snap Daemon.
         Starting Snap Daemon...
[FAILED] Failed to start Hostname Service.
See 'systemctl status systemd-hostnamed.service' for details.
[FAILED] Failed to start Wait until snapd is fully seeded.
See 'systemctl status snapd.seeded.service' for details.
[   ***] (6 of 6) A start job is running for Rotate log files (10min 31s / no limit)
_

When this happens, I force a hard shutdown and reboot, which solved the problem every time.

On top of this, I changed my /etc/default/grub to contain:

GRUB_TIMEOUT_STYLE=countdown
GRUB_TIMEOUT=1
GRUB_RECORDFAIL_TIMEOUT=15

And the grub menu always shows up for 15 seconds. So I guess there is an error during boot every time, but it doesn't always get the boot stuck?

I tried uncommenting WaylandEnable=false in /etc/gdm3/custom.conf, as was suggested in some similar posts, but to no avail.

Where could I go to debug this? I'm not really familiar with the boot and logging systems.

I downloaded AMDGPU Pro for graphics, installed it and entered sudo reboot.

After the reboot the Ubuntu 18.04 boot got stuck at a black screen showing OK OK OK...

The message, where the boot process apparently got stuck:

Started disk manager.service....r systemd-networkd.crashed before the ppp link was shut down....

The GUI is also not loading. Can anyone tell me how to resolve this error?

/dev/sda5: clean, 216207/3751936 files, 2325592/15000064 blocks
[  OK  ] Started File System Check on /dev/disk/by-uuid/A226-E83E.
         Mounting /boot/efi...
[  OK  ] Mounted /boot/efi.
[  OK  ] Reached target Local File Systems.
         Starting Tell Plymouth To Write Out Runtime Data...
         Starting Clean up any mess left by 0dns-up...
         Starting Create Volatile Files and Directories...
         Starting AppArmor initialization...
         Starting Set console font and keymap...
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Set console font and keymap.
[  OK  ] Started Clean up any mess left by 0dns-up.
[  OK  ] Started Create Volatile Files and Directories.
         Starting Update UTMP about System Boot/Shutdown...
         Starting Network Name Resolution...
         Starting Network Time Synchronization...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Host and Network Name Lookups.
[  OK  ] Started AppArmor initialization.
         Starting Raise network interfaces...
         Starting Load AppArmor profiles managed internally by snapd...
[  OK  ] Started Load AppArmor profiles managed internally by snapd.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on UUID daemon activation socket.
[  OK  ] Started ACPI Events Check.
         Starting Socket activation for snappy daemon.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Started CUPS Scheduler.
[  OK  ] Reached target Paths.
[  OK  ] Started Message of the Day.
[  OK  ] Started Discard unused blocks once a week.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Started Trigger anacron every hour.
[  OK  ] Listening on ACPID Listen Socket.
[  OK  ] Started Daily apt download activities.
[  OK  ] Started Daily apt upgrade and clean activities.
[  OK  ] Reached target Timers.
[  OK  ] Listening on CUPS Scheduler.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on Socket activation for snappy daemon.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting Dispatcher daemon for systemd-networkd...
[  OK  ] Started Disk Manager. service....r systemd-networkd.crashed before the ppp link was shut down....  
_

I don't remember installing anything recently but when I pulled my laptop out of standby today I got the following notification:

In words: An error occurred, please run Package Manager from the right-click menu or apt-get in a terminal to see what is wrong. The error message was: Error: Opening the cache (E:Couldn't create temporary file to work with /var/lib/apt/lists/de.archive.ubuntu.com_ubuntu__dists__bionic__InRelease - mkstemp (2: No such file or directory), E:The package lists or status file could not be parsed or opened.)'. This usually means that your installed packages have unmet dependencies (Side question: Is there a log file somewhere to copy the text from?)

I don't know what the right-click menu is. When I click on preferences, Software & Updates opens up, but I'm unsure what to do there.

running apt-get check diplays

Reading package lists... Error! E: Couldn't create temporary file to work with /var/lib/apt/lists/de.archive.ubuntu.com_ubuntu_dists_bionic_InRelease - mkstemp (2: No such file or directory) E: The package lists or status file could not be parsed or opened.

I have since tried: per https://sillycodes.com/quick-tip-couldnt-create-temporary-file/:

sudo apt-get clean sudo mv /var/lib/apt/lists /tmp sudo mkdir -p /var/lib/apt/lists/partial sudo apt-get clean sudo apt-get update reverted with sudo mv /tmp /var/lib/apt/lists

There were error messages for several repositories, examplary: W: GPG error: http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease: Couldn't create temporary file /tmp/apt.conf.tiVq7R for passing config to apt-key E: The repository 'http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default.

I am using Ubuntu 18.04.4, login screen is not visible. I got stuck at a black screen with the following boot messages.

[  OK  ] Started CUPS Scheduler.
[  OK  ] Started Set the CPU Frequency Scaling governor.
[  OK  ] Started D-Bus System Message Bus.
         Starting WPA supplicant...
         Starting Network Manager...
         Starting Avahi mDNS/DNS-SD Stack...
         Starting LSB: Record successful boot for GRUB...
[  OK  ] Started Regular background program processing daemon.
         Starting Dispatcher daemon for systemd-networkd...
[  OK  ] Reached target Login Prompts.
         Starting Accounts Service...
         Starting Disk Manager...
         Starting LSB: Speech Dispatcher...
         Starting Login Service...
         Starting Bluetooth service...
         Starting Thermal Daemon Service...
         Starting Snappy daemon...
[  OK  ] Started System Logging Service.
[  OK  ] Started Restore /etc/resolv.conf if the system crashed be
[  OK  ] Started Detect the available GPUs and deal with any syste
[  OK  ] Started Save/Restore Sound Card State.
[  OK  ] Started LSB: Speech Dispatcher.
         Starting Authorization Manager...
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Make remote CUPS printers available locally.
[  OK  ] Started LSB: automatic crash report generation.
[  OK  ] Started VirtualBox Linux kernel module.
         Starting vboxballoonctrl-service.service...
         Starting vboxweb-service.service...
         Starting vboxautostart-service.service...
[  OK  ] Started Login Service.
[  OK  ] Started vboxweb-service.service.
[  OK  ] Started Bluetooth service.
[  OK  ] Reached target Bluetooth.
[  OK  ] Started vboxautostart-service.service.
[  OK  ] Started vboxballoonctrl-service.service.
[  OK  ] Started LSB: Record successful boot for GRUB.
[  OK  ] Started Authorization Manager.
[  OK  ] Started Accounts Service.
[  OK  ] Started Thermal Daemon Service.
[  OK  ] Started Raise network interfaces.
         Starting Hostname Service...
[  OK  ] Started WPA supplicant.
[  OK  ] Started Hostname Service.  
_

Could anyone help me to start my laptop in the usual login screen?

I have installed the xserver-xorg-video-dummy-hwe-18.04 to let I use the VNC without needs to connect HDMI cable to my ubuntu machine.

I followed the Topic here, and successfully able to use VNC connect to Ubuntu machine without plugged-in monitor.

However, there are side effect is that, if I connect the HDMI cable to the ubuntu machine, it will display _ (black screen with cursor blinking at the top) and not show lightdm login screen as expected.

If I remove /etc/X11/xorg.conf from directory, reboot, I can now back using the monitor plugged-in.

Question

Are there possible to able to use video-dummy with/without monitor at the same time? may be like secondary mirroring display mode. How to config /etc/X11/xorg.conf properly?

So that I can use the desktop no matter real monitor has connected to HDMI port or not.

Well, my problem is that I press the volume control on the keyboard, I see the bar in the screen going down, but it doesn't do anything until it's at 0. So the volume is on 0 or 100%.

I have done many things trying to fix it. Finally, I did something that I read here How do I change the way Ubuntu adjusts my volume mixer levels? , and it works, but not forever. For example, the solution just remains one song in YouTube. After that, again, very loud sound or silence. I go by the terminal to check /etc/pulse/default.pa and everything is ok, like I left it before.

I don't know what to do. I'm getting crazy.
Thank you so much for your time!

EDIT: I had Windows 10 before in this PC, but I reformatted to Ubuntu 18.04.3 LTS. The model is an ASUS ZENBOOK UX490U. And finally, typing lspci -v | grep -i vga in the terminal, I get this:

00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) (prog-if 00 [VGA controller])

Suppose I opened my file manager nemo and select a file named "abc" In the location bar, it shows media/myuser/folder1/subfoler/ and the selected file name is abc.

How can assign the selected (highlighted) file name with full path in a variable in my bash script (please note this file is not in home directory) anybody can help me please?

I have Windows 10 installed on my system and I am trying to install Ubuntu 18.04.2 along with windows 10 in dual boot mode. I have a single HDD, and since my C: didn't had as much space as 20GB, hence I had allocated space for Ubuntu by partitioning from E: (E: is also a primary partition in my system). I am installing using USB flash drive During installation of Ubuntu, it didn't detect windows and I went ahead with something else option, and I selected my partition, and also specified the mount point as /, with use as option ext4. However in next step I'm getting an error saying No EFI System partition was found My Windows always runs using Bios, and not using Uefi. If windows is not using Uefi i do not know why i am getting this error. Please provide some help regarding this error, it's causes and tentative solutions. Thanks

SSH connection has been working properly, but today unfortunately it stopped.

I had lots of tries to solve it.

linux@mylinux:~$ ssh root@XX.XX.XXX.XXX
ssh: connect to host XX.XX.XXX.XXX port 22: Connection refused

linux@mylinux:~$ ssh root@XX.XX.XXX.XXX -p 8787
ssh: connect to host XX.XX.XXX.XXX port 8787: Connection refused

>>>linux@mylinux:~$ ssh root@XX.XX.XXX.XXX -vvv
OpenSSH_7.4p1 Ubuntu-10, OpenSSL 1.0.2g  1 Mar 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "XX.XX.XXX.XXX" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to XX.XX.XXX.XXX [XX.XX.XXX.XXX] port 22.
debug1: connect to address XX.XX.XXX.XXX port 22: Connection refused
ssh: connect to host XX.XX.XXX.XXX port 22: Connection refused

ssh - status

>● ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2017-11-18 15:42:28 IST; 31min ago
 Main PID: 6940 (sshd)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/ssh.service
           └─6940 /usr/sbin/sshd -D

Also, I have removed openssh-sever and reinstalled it, but it can not succeed.

When I try to connect via localhost then it is a success, but on a remote site it is refused.

But I still can not succeed.

Why is my SSH connection refused?

cat /etc/ssh/sshd_config

Host *

*#    $OpenBSD: sshd_config,v 1.100 2016/08/15 12:32:04 naddy Exp $

*# This is the sshd server system-wide configuration file.  See
*# sshd_config(5) for more information.

*# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin

*# The strategy used for options in the default sshd_config shipped with
*# OpenSSH is to specify options with their default value where
*# possible, but leave them commented.  Uncommented options override the
*# default value.

*#Port 22
*#AddressFamily any
*#ListenAddress 0.0.0.0
*#ListenAddress ::

*#HostKey /etc/ssh/ssh_host_rsa_key
*#HostKey /etc/ssh/ssh_host_ecdsa_key
*#HostKey /etc/ssh/ssh_host_ed25519_key

*# Ciphers and keying
*#RekeyLimit default none

*# Logging
*#SyslogFacility AUTH
*#LogLevel INFO

*# Authentication:

*#LoginGraceTime 2m
*#PermitRootLogin prohibit-password
*#StrictModes yes
*#MaxAuthTries 6
*#MaxSessions 10

*#PubkeyAuthentication yes

*# Expect .ssh/authorized_keys2 to be disregarded by default in future.
*#AuthorizedKeysFile    .ssh/authorized_keys .ssh/authorized_keys2

*#AuthorizedPrincipalsFile none

*#AuthorizedKeysCommand none
*#AuthorizedKeysCommandUser nobody

*# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
*#HostbasedAuthentication no
*# Change to yes if you don't trust ~/.ssh/known_hosts for
*# HostbasedAuthentication
*#IgnoreUserKnownHosts no
*# Don't read the user's ~/.rhosts and ~/.shosts files
*#IgnoreRhosts yes

*# To disable tunneled clear text passwords, change to no here!
*#PasswordAuthentication yes
*#PermitEmptyPasswords no

*# Change to yes to enable challenge-response passwords (beware issues with
*# some PAM modules and threads)
ChallengeResponseAuthentication no

*# Kerberos options
*#KerberosAuthentication no
*#KerberosOrLocalPasswd yes
*#KerberosTicketCleanup yes
*#KerberosGetAFSToken no

*# GSSAPI options
*#GSSAPIAuthentication no
*#GSSAPICleanupCredentials yes
*#GSSAPIStrictAcceptorCheck yes
*#GSSAPIKeyExchange no

*# Set this to 'yes' to enable PAM authentication, account processing,
*# and session processing. If this is enabled, PAM authentication will
*# be allowed through the ChallengeResponseAuthentication and
*# PasswordAuthentication.  Depending on your PAM configuration,
*# PAM authentication via ChallengeResponseAuthentication may bypass
*# the setting of "PermitRootLogin without-password".
*# If you just want the PAM account and session checks to run without
*# PAM authentication, then enable this but set PasswordAuthentication
*# and ChallengeResponseAuthentication to 'no'.
UsePAM yes

*#AllowAgentForwarding yes
*#AllowTcpForwarding yes
*#GatewayPorts no
X11Forwarding yes
*#X11DisplayOffset 10
*#X11UseLocalhost yes
*#PermitTTY yes
PrintMotd no
*#PrintLastLog yes
*#TCPKeepAlive yes
*#UseLogin no
*#UsePrivilegeSeparation sandbox
*#PermitUserEnvironment no
*#Compression delayed
*#ClientAliveInterval 0
*#ClientAliveCountMax 3
*#UseDNS no
*#PidFile /var/run/sshd.pid
*#MaxStartups 10:30:100
*#PermitTunnel no
*#ChrootDirectory none
*#VersionAddendum none

*# no default banner path
*#Banner none

*# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

*# override default of no subsystems
Subsystem    sftp    /usr/lib/openssh/sftp-server

*# Example of overriding settings on a per-user basis
*#Match User anoncvs
*#    X11Forwarding no
*#    AllowTcpForwarding no
*#    PermitTTY no
*#    ForceCommand cvs server

Here

sudo netstat -tlpena | grep -i "ssh"

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          25237      1260/sshd
tcp6       0      0 :::22                   :::*                    LISTEN      0          25239      1260/sshd

AND

sudo iptables -S

-P INPUT DROP
-P FORWARD DROP
-P OUTPUT ACCEPT
-N ufw-after-forward
-N ufw-after-input
-N ufw-after-logging-forward
-N ufw-after-logging-input
-N ufw-after-logging-output
-N ufw-after-output
-N ufw-before-forward
-N ufw-before-input
-N ufw-before-logging-forward
-N ufw-before-logging-input
-N ufw-before-logging-output
-N ufw-before-output
-N ufw-logging-allow
-N ufw-logging-deny
-N ufw-not-local
-N ufw-reject-forward
-N ufw-reject-input
-N ufw-reject-output
-N ufw-skip-to-policy-forward
-N ufw-skip-to-policy-input
-N ufw-skip-to-policy-output
-N ufw-track-forward
-N ufw-track-input
-N ufw-track-output
-N ufw-user-forward
-N ufw-user-input
-N ufw-user-limit
-N ufw-user-limit-accept
-N ufw-user-logging-forward
-N ufw-user-logging-input
-N ufw-user-logging-output
-N ufw-user-output
-A INPUT -j ufw-before-logging-input
-A INPUT -j ufw-before-input
-A INPUT -j ufw-after-input
-A INPUT -j ufw-after-logging-input
-A INPUT -j ufw-reject-input
-A INPUT -j ufw-track-input
-A FORWARD -j ufw-before-logging-forward
-A FORWARD -j ufw-before-forward
-A FORWARD -j ufw-after-forward
-A FORWARD -j ufw-after-logging-forward
-A FORWARD -j ufw-reject-forward
-A FORWARD -j ufw-track-forward
-A OUTPUT -j ufw-before-logging-output
-A OUTPUT -j ufw-before-output
-A OUTPUT -j ufw-after-output
-A OUTPUT -j ufw-after-logging-output
-A OUTPUT -j ufw-reject-output
-A OUTPUT -j ufw-track-output
-A ufw-after-input -p udp -m udp --dport 137 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp -m udp --dport 138 -j ufw-skip-to-policy-input
-A ufw-after-input -p tcp -m tcp --dport 139 -j ufw-skip-to-policy-input
-A ufw-after-input -p tcp -m tcp --dport 445 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp -m udp --dport 67 -j ufw-skip-to-policy-input
-A ufw-after-input -p udp -m udp --dport 68 -j ufw-skip-to-policy-input
-A ufw-after-input -m addrtype --dst-type BROADCAST -j ufw-skip-to-policy-input
-A ufw-after-logging-forward -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW BLOCK] "
-A ufw-after-logging-input -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW BLOCK] "
-A ufw-before-forward -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 3 -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 4 -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 11 -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 12 -j ACCEPT
-A ufw-before-forward -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A ufw-before-forward -j ufw-user-forward
-A ufw-before-input -i lo -j ACCEPT
-A ufw-before-input -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A ufw-before-input -m conntrack --ctstate INVALID -j ufw-logging-deny
-A ufw-before-input -m conntrack --ctstate INVALID -j DROP
-A ufw-before-input -p icmp -m icmp --icmp-type 3 -j ACCEPT
-A ufw-before-input -p icmp -m icmp --icmp-type 4 -j ACCEPT
-A ufw-before-input -p icmp -m icmp --icmp-type 11 -j ACCEPT
-A ufw-before-input -p icmp -m icmp --icmp-type 12 -j ACCEPT
-A ufw-before-input -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A ufw-before-input -p udp -m udp --sport 67 --dport 68 -j ACCEPT
-A ufw-before-input -j ufw-not-local
-A ufw-before-input -d 224.0.0.251/32 -p udp -m udp --dport 5353 -j ACCEPT
-A ufw-before-input -d 239.255.255.250/32 -p udp -m udp --dport 1900 -j ACCEPT
-A ufw-before-input -j ufw-user-input
-A ufw-before-output -o lo -j ACCEPT
-A ufw-before-output -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A ufw-before-output -j ufw-user-output
-A ufw-logging-allow -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW ALLOW] "
-A ufw-logging-deny -m conntrack --ctstate INVALID -m limit --limit 3/min --limit-burst 10 -j RETURN
-A ufw-logging-deny -m limit --limit 3/min --limit-burst 10 -j LOG --log-prefix "[UFW BLOCK] "
-A ufw-not-local -m addrtype --dst-type LOCAL -j RETURN
-A ufw-not-local -m addrtype --dst-type MULTICAST -j RETURN
-A ufw-not-local -m addrtype --dst-type BROADCAST -j RETURN
-A ufw-not-local -m limit --limit 3/min --limit-burst 10 -j ufw-logging-deny
-A ufw-not-local -j DROP
-A ufw-skip-to-policy-forward -j DROP
-A ufw-skip-to-policy-input -j DROP
-A ufw-skip-to-policy-output -j ACCEPT
-A ufw-track-output -p tcp -m conntrack --ctstate NEW -j ACCEPT
-A ufw-track-output -p udp -m conntrack --ctstate NEW -j ACCEPT
-A ufw-user-input -p tcp -m tcp --dport 22 -j ACCEPT
-A ufw-user-limit -m limit --limit 3/min -j LOG --log-prefix "[UFW LIMIT BLOCK] "
-A ufw-user-limit -j REJECT --reject-with icmp-port-unreachable
-A ufw-user-limit-accept -j ACCEPT

I've just upgraded to a Dell E5570 and am running 14.04. I want to be able to attach an external monitor, but in Mirror mode. (I'm running fvwm with multiple virtual windows and I need to be able to see all of them on the external monitor.) When I attach the external monitor, everything works, but only in extended or "twinview" mode. From gnome-control-center display, when I switch to mirror mode, and click Apply, I get the same error that has been reported elsewhere, in particular here and also here, with a screenshot i.e.:

GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon was not provided by any .service files

My problem seems different from those previously reported, since I have no problems with extended mode. The threads above suggest that xrandr or arandr can fix these kinds of problems. But I've searched the documentation for xrandr and arandr, neither seem to have an option for mirror mode.

On a previous laptop (Dell E6530, running 12.04), I was able to fix this problem by installing an Nvidia driver. I have attempted to do this on the new E5570, but I have been unable to get it to work.

Here's the output from xrandr:

Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
   1920x1080      60.0*+   59.9     48.0
   1680x1050      60.0     59.9
   1600x1024      60.2
   1400x1050      60.0
   1600x900       60.0
   1280x1024      60.0
   1440x900       59.9
   1280x960       60.0
   1368x768       60.0
   1360x768       59.8     60.0
   1152x864       60.0
   1280x720       60.0
   1024x768       60.0
   1024x576       60.0
   960x540        60.0
   800x600        60.3     56.2
   864x486        60.0
   640x480        59.9
   720x405        60.0
   640x360        60.0
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 930mm x 523mm
   1920x1080      60.0*+   59.9
   1680x1050      60.0
   1280x1024      75.0     60.0
   1280x960       75.0
   1152x864       75.0     60.0
   1024x768       75.1     75.0     60.0
   832x624        74.6
   800x600        75.0     60.3
   640x480        75.0     60.0
   720x400        70.1
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

I have a single external monitor, but am running fvwm, which is a desktop manager that enables me to have multiple virtual desktops. The image below is a schematic map of what my setup looks like, i.e., there a six virtual desktops, in a 2x3 configuration, each one has multiple xterms open.

Jacob, your xrandr suggestion enabled me to view the left-most and the right-most columns, but not the middle column of these virtual desktops. Currently, I still have a 2x3 setup with the left column, the right column, and a blank column. As I mentioned last time, it's striking that the middle column of virtual desktops (each screen in the middle has two xterms, including the one that's in focus in the image) is the column that's not visible now, but when I attached the external monitor originally and was in extended mode, the middle column was the only column that I could see.

I'd very much like to be able to have access to all six virtual desktops when I'm attached to an external monitor.

Trying to install pbh5-tools on my Ubuntu 12.04 virtual machine. I have encountered countless problems trying to get the program to install. I get the error:

In file included from /tmp/easy_install-BEtAkS/h5py-2.5.0/h5py/defs.c:287:0:
/tmp/easy_install-BEtAkS/h5py-2.5.0/h5py/api_compat.h:27:18: fatal error: hdf5.h: No such file or directory

I have tried downloading libhdf5-dev to solve this, but when I use sudo apt-get libhdf5-dev, I get this response.

Package libhdf5-dev is a virtual package provided by:
  libhdf5-serial-dev 1.8.4-patch1-3ubuntu2
  libhdf5-openmpi-dev 1.8.4-patch1-3ubuntu2
  libhdf5-mpich-dev 1.8.4-patch1-3ubuntu2
  libhdf5-lam-dev 1.8.4-patch1-3ubuntu2

When I try installing the individual packages I get the same response:

E: Unable to locate package 1.8.4-patch1-3ubuntu2

I downloaded the patch, configured it, made it, and installed it, but I still cant get it to work. Don't know what to do really.

It has been 2 weeks since I bought my first ever Windows laptop with the aim of replacing Windows, but I have been unsuccessful.

The hardware is as follows:

• Asus 15' F550D
• A8 AMD processor
• Radeon HD 8670M graphics

The laptops runs EFI "BIOS". I managed to switch off Fast Boot and Secure Boot in EFI .

I managed to to boot from USB which I mounted the Ubuntu 13.10 on, but I can not get pass the GRUB menu as no matter when I chose I end up facing a black screen with backlight on, and I cannot get anywhere beyond that.

I have tried the following with no success:

• Alternative versions of Ubuntu (13.04 , 12.10 and Kubuntu 13.10 (all 64-bit)) problem remains.

• Editing the boot options in grub and using nomodeset

What can I try next?

In a perfect world I would be aiming to have a dual boot system, but if it's easier to lose the big virus living in my system, Windows 8, then I'm more than happy to go with that.

I know, I know, I should have never gotten a Canon to connect to a Linux box...

But the SANE supported-scanners doc said that the CanoScan 700F is supported "Good". I took that to mean that it can scan at all but the highest res setting (9600 dpi).

But I haven't been able to actually scan anything except a low res preview.

I can see in /var/log/kern.log that the kernel sees it:

Jan 23 20:30:22 morpheus kernel: [269901.872029] usb 1-2: new high-speed USB device number 14 using ehci_hcd
Jan 23 20:30:22 morpheus kernel: [269902.005556] usb 1-2: New USB device found, idVendor=04a9, idProduct=1907
Jan 23 20:30:22 morpheus kernel: [269902.005564] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 23 20:30:22 morpheus kernel: [269902.005569] usb 1-2: Product: CanoScan
Jan 23 20:30:22 morpheus kernel: [269902.005573] usb 1-2: Manufacturer: Canon

This usually works:

$ sudo sane-find-scanner 
[sudo] password for xxx: 

# sane-find-scanner will now attempt to detect your scanner. If the
# result is different from what you expected, first make sure your
# scanner is powered up and properly connected to your computer.

# No SCSI scanners found. If you expected something different, make sure that
# you have loaded a kernel SCSI driver for your SCSI adapter.

could not fetch string descriptor: Operation timed out
could not fetch string descriptor: Operation timed out
found USB scanner (vendor=0x04a9, product=0x1907) at libusb:001:014

This works only sometimes:

$ sudo scanimage -Lv

No scanners were identified. If you were expecting something different, ...

And when xsane does find the scanner and I try to scan something, it clicks a little, then just hangs.

Does anyone have experience getting this device to work on some version of LInux or should I just send it back and get an HP scanner?

I'm trying to log into Ubuntu desktop. I get the following error message:

PTY allocation request failed

What does it mean and how to connect to my desktop?

This is the output with -v:

debug1: Reading configuration data /home/evag/.ssh/config  
debug1: /home/evag/.ssh/config line 1: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config 
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: auto-mux: Trying existing master
debug1: mux_client_request_session: master session id: 2
PTY allocation request failed

Given the output presented above with the verbose option, I think I understand where the problem comes from: I have two computers, A and B. I'm using a controlmaster in A to keep persistent connections to B. A logs into B in a safe way, with command=/bin/false to limit the usage A has on B (it has only forwarding capabilities).

However I would want to connect to ssh from A to B without using this identity (-i), but the problem is that since there is a persistent connection, it uses the existing connection regardless of the option I put in -i, so I end up with not being able to allocate a PTY.

So given that there is an existing controlmaster and protected connection from A to B, how can I get another connection from A to B, but this time with full rights?