Apt errors on Ubuntu 26.04 https://askubuntu.com/questions/1564148/apt-errors-on-ubuntu-26-04

If this isn't the appropriate place to get help I apologize.

These are the apt errors I'm getting:

Setting up rsyslog (8.2512.0-1ubuntu3) ...
warn: The user `syslog' is already a member of `adm'.
dpkg: error processing package rsyslog (--configure):
installed rsyslog package post-installation script subprocess returned error        exit status 10
Setting up kdump-tools (1:1.10.7ubuntu3) ...
dpkg: error processing package kdump-tools (--configure):
installed kdump-tools package post-installation script subprocess returned   error exit status 10
Setting up grub-pc (2.14-2ubuntu1) ...
dpkg: error processing package grub-pc (--configure):
installed grub-pc package post-installation script subprocess returned error  exit status 10
dpkg: dependency problems prevent configuration of grub-gfxpayload-lists:
grub-gfxpayload-lists depends on grub-pc (>= 1.99~20101210-1ubuntu2); however:
Package grub-pc is not configured yet.

dpkg: error processing package grub-gfxpayload-lists (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                          dpkg: dependency  problems prevent configuration of grub-efi-amd64-signed:
grub-efi-amd64-signed depends on grub-efi-amd64 | grub-pc; however:
Package grub-efi-amd64 is not installed.
Package grub-pc is not configured yet.

dpkg: error processing package grub-efi-amd64-signed (--configure):
dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                          Errors were    encountered while processing:
rsyslog
kdump-tools
grub-pc
grub-gfxpayload-lists
grub-efi-amd64-signed
Error: Sub-process /usr/bin/dpkg returned an error code (1)

I realize I took my chances by using 26.04 this early. Any help would be appreciated. Thanks.

Is it possible to specify a second method for unlocking a disk in /etc/crypttab after fido2-device? https://askubuntu.com/questions/1564147/is-it-possible-to-specify-a-second-method-for-unlocking-a-disk-in-etc-crypttab

An encrypted system drive in Ubuntu 25.10 can be unlocked with a FIDO2 compatible security key at boot time if

dm_crypt-0 UUID=XXXXX none luks,fido2-device=auto

is specified in /etc/crypttab, then initramfs is rebuilt with

sudo dracut -f

However, this method prevents unlocking of the disk at boot time if the security key is not present, even if the disk has a password in another LUKS key slot. The system never asks for the password.

Is it possible to modify /etc/crypttab so that unlocking is first attempted using the fido2-device method, and if that fails, subsequently with the password?

No audio from jacked earphones even if detected on Ubuntu 24.04.4 LTS https://askubuntu.com/questions/1564144/no-audio-from-jacked-earphones-even-if-detected-on-ubuntu-24-04-4-lts

I need help to fix my audio please. I have a Lunar Lake chip on my Lenovo Slim 7i Aura Edition. Thanks for helping.

The email address has been invalidated https://askubuntu.com/questions/1564140/the-email-address-has-been-invalidated

When adding a new user to the Ubuntu Pro account, the user will receive the 'Finish your registration' email from Ubuntu; however, seconds later, another email will arrive stating that the user's email address has been invalidated and removed from Ubuntu One.

Any thoughts? Seems odd that this is set up as an enterprise solution, yet we are unable to add admins to the Ubuntu Pro portal.

how to reinstall a flatpack package? https://askubuntu.com/questions/1564139/how-to-reinstall-a-flatpack-package

I had a connection issue while downloading a flatpak package and the last two parts couldn't be downloaded, what can I do?

Do I reinstall the whole thing?

How to get apps to use the "system" printing settings in 25.10 https://askubuntu.com/questions/1564137/how-to-get-apps-to-use-the-system-printing-settings-in-25-10

I've looked at opera snap ubuntu 25.10 printers missing which sadly doesn't answer my question.

I was trying to print a bunch of PDFs the other day and realised that my Ubuntu 25.10 system's Settings -> Printers had one view of which printers were available, and what printing settings should be applied (duplex, paper size, colour etc), then my browser (Vivaldi) had a completely different view of the printing reality (i.e. not "seeing" the system defined printer) even when asked to "Print using system dialogue".

Vivaldi is indeed a snap installation, but I checked the settings of the app (via Settings -> Apps -> Vivaldi) and I see that cups (which I suppose means "printing") just shows two dashes, with no other options available when the drop-down is expanded:

Vivaldi application permissions

Any idea how to resolve this, so that Vivaldi sees the system printers?

Bad default entry in boot menu? [closed] https://askubuntu.com/questions/1564136/bad-default-entry-in-boot-menu

I have a bad entry in the boot menu which is the default. When I simply boot the PC, that entry activates but can't boot. It just reboots after 1-2 seconds, effectively entering a boot loop.

enter image description here

When I press F7 to get to the boot menu, I have to select the second entry to successfully boot the OS. How can I get rid of that bad entry? I tried grub-customizer, but there I don't even see that bad entry (starting with "UEFI")...

enter image description here

Ubuntu 24.04.01 on MacBookAir no Wifi detected after the second installation https://askubuntu.com/questions/1564135/ubuntu-24-04-01-on-macbookair-no-wifi-detected-after-the-second-installation

I had to reinstall Ubuntu 24.04.01 on my MacBook Air due to an issue

After the installation the computer was working but the WIFI stopped to be detected after updating to 24.04.04. It shows only the Bluetooth option.

What can I do? Thanks for your help

I can't download the Ubuntu installer over a 4G router https://askubuntu.com/questions/1564134/i-cant-download-the-ubuntu-installer-over-a-4g-router

I am having exactly the same problem as this post.

Stops downloading large file after 2GB

My rig is connected to a 4G router with a data limit.

When I try to download a large file (like the Ubuntu installer), when it reaches 2G it slows down to kHz (too small to give a value). It shows up in Firefox by appearing to freeze and just stops when using wget

I have tested this on 22.04 and 24.04 on two different rigs. I haven' tried it with WIN10 yet and can't at the moment because the data has just rolled over. (I have to ration it in the early part of the month.)

In the past I was able to download ubuntu installer in stages over Mozilla by pausing (before the forced stop) and stopping & restarting Firefox & resuming. However, I tried multiple times with the latest version of 24.04 and could not get it. (The best I did was get within 30s of the finish.) In the past I downloaded a earlier version 24.04.01 @ 6.2G. Yes its bigger but possibly Firefox has been tweaked a bit.

The restart of Firefox always resyncs with the download on the first go (@2G) but get worse as you go along (4G, 6G etc), and the delay gets bigger. I think the resync times out in some way,

The questions: -

Firstly Are there any download limits in Ubuntu or Firefox. (I don't think there are but I have to ask.)

Secondly: Is there a way to download a big (> 2G) file? For example, will downloading through multiple channels work? Any other suggestions?

Thirdly, Is there a way to extend the resync timeout in Firefox? (Hopfully allowing a bigger download.)


The following question/answer has been suggested as a solution.

How to download an ISO file for Ubuntu?

The first answer really only suggests bittorrent as a solution with no real details. the other two answers don't really address the problem of a download size limit.

I have only been introduced to bittorrent a moment ago so I am far from an expert on it but I did find the following details

https://linuxvox.com/blog/ubuntu-bittorrent/

I have had a quick scan and there are a few things that would worry me about using it. Firstly, your rig appears to become part of the network and other users can access the files you have downloaded. Being on a limited data tariff that does not really work for me. Also I am a home user and there appears to security issues. Currently my security is locked down. However, feel free to convince me.

Install problem [closed] https://askubuntu.com/questions/1564132/install-problem

I installed Debian 13 on my laptop and am trying to install Brave browser. In the terminal, i write the command and hit enter, it asks users passwd [sudo] xxxxx-user passwd: i write passwd and no letters appear to screen, then hit enter and anwser is: xxxxx is not in sudoers file. What should be done?

Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver is either not loaded or not set up correctly https://askubuntu.com/questions/1564103/kernel-driver-not-installed-rc-1908-the-virtualbox-linux-kernel-driver-is-eit

"Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver is either not loaded or not set up correctly"

"…Please reinstall virtualbox-dkms package and load the kernel module by executing 'modprobe vboxdrv' as root."

$ uname -a
Linux AM5 6.17.0-14-generic #14~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 15 15:52:10 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

This appears to be a recurring problem with no definitive answer: each time it comes up, a previous solution fails to work and a new answer is needed. I've lost track of how many questions and 'answers' I've read on this.

There must be many thousands of people who rely upon Virtualbox to run other Linux, and especially Windows, on Linux. And many will be on Ubuntu. So I don't understand why there isn't already a fix. I don't even know which update caused it. All of a sudden, VB can't start a virtual machine.

Would subscribing to Ubuntu Pro help?

Perhaps I got a 'phased' update, so most of the rest of you are oblivious of the problem?

NB, I've checked the BIOS: secure boot is DISABLED.


Below is some of what I've tried.

So, first try what it says in the error message:

$ sudo apt reinstall virtualbox-dkms
[sudo] password for alan: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 38 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for virtualbox-dkms:amd64

Keep going — maybe the modprobe will work:

$ sudo modprobe vboxdrv
[sudo] password for alan: 
alan@AM5:~$ 

Restart Virtualbox. Try to start virtual machine. Virtual machine immediately goes from 'Saved' to 'Aborted Saved'.

Powering VM up...
VM Name: ...
The VM session was aborted.
Result code: NS_ERROR_FAILURE (0X80004005)
Component: SessionMachine
Interface: ISession {c044...}

Thank goodness I have a backup.

Edit grub and roll back to old kernel: nothing changes.

Let's try update/upgrade:

sudo apt upgrade  

[...]  

Setting up virtualbox-dkms (7.0.16-dfsg-2ubuntu1.1) ...
Removing old virtualbox-7.0.16 DKMS files...
Module virtualbox-7.0.16 for kernel 6.14.0-37-generic (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko.zst:
 - Uninstallation
   - Deleting from: /lib/modules/6.14.0-37-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

vboxnetadp.ko.zst:
 - Uninstallation
   - Deleting from: /lib/modules/6.14.0-37-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

vboxnetflt.ko.zst:
 - Uninstallation
   - Deleting from: /lib/modules/6.14.0-37-generic/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.
depmod...
Deleting module virtualbox-7.0.16 completely from the DKMS tree.
Loading new virtualbox-7.0.16 DKMS files...
Building for 6.14.0-37-generic 6.17.0-14-generic
Building initial module for 6.14.0-37-generic
Done.

vboxdrv.ko.zst:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/6.14.0-37-generic/updates/dkms/

vboxnetadp.ko.zst:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/6.14.0-37-generic/updates/dkms/

vboxnetflt.ko.zst:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/6.14.0-37-generic/updates/dkms/
depmod...
Building initial module for 6.17.0-14-generic
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.
dpkg: error processing package virtualbox-dkms (--configure):
 installed virtualbox-dkms package post-installation script subprocess returned error exit status 10  

[...]  

errors were encountered while processing:
 virtualbox-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

Consult /var/lib/dkms/virtualbox/7.0.16/build/make.log for more information.

I forgot to capture this before attempting to reinstall VB --- it's gone.

Tried to install a later version of VB direct from Oracle: failed.
Now I get: "Failed to acquire the VirtualBox COM object. The application will now terminate."

Yes, I know, I should have taken a more systematic approach. But it's difficult to write this on the machine you're trying to fix. Especially as some 'answers' have such enticing 'solutions'...


To understand the 'Edit's, please see the Comments

Edit 1

Managed to install VB 7.1
Same original problem, but now it says to run /sbin/vboxconfig

$ sudo /sbin/vboxconfig
[sudo] password for alan: 
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
alan@AM5:~$ 

Look at /var/log/vbox-setup.log to find out what went wrong.

Building the main VirtualBox module.
Error building the module:
make V=1 CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/6.17.0-14-generic/build M=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j32
 modules
make[1]: warning: -j32 forced in submake: resetting jobserver mode.
make  -C /tmp/vbox.0 \
-f /usr/src/linux-headers-6.17.0-14-generic/Makefile modules
warning: the compiler differs from the one used to build the kernel
  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-13 (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

[...]  
[several "fatal error" messages:]

VBox/cdefs.h: No such file or directory  
VBox/sup.h: No such file or directory  
iprt/string.h: No such file or directory  
internal/iprt.h: No such file or directory  
the-linux-kernel.h: No such file or directory  
$ ll /usr/bin | grep gcc
lrwxrwxrwx  1 root root   23 Sep  4  2024 gcc-13 -> x86_64-linux-gnu-gcc-13*

So it would appear the warning about the compiler is a red herring.

Edit 2

$ dpkg -l *virtualbox*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                           Version                    Architecture Description
+++-==============================-==========================-============-==============================================
ic  virtualbox                     7.0.16-dfsg-2ubuntu1.1     amd64        x86 virtualization solution - base binaries
un  virtualbox-2.0                 <none>                     <none>       (no description available)
un  virtualbox-2.1                 <none>                     <none>       (no description available)
un  virtualbox-2.2                 <none>                     <none>       (no description available)
un  virtualbox-3.0                 <none>                     <none>       (no description available)
un  virtualbox-3.1                 <none>                     <none>       (no description available)
un  virtualbox-3.2                 <none>                     <none>       (no description available)
un  virtualbox-4.0                 <none>                     <none>       (no description available)
un  virtualbox-4.1                 <none>                     <none>       (no description available)
un  virtualbox-4.2                 <none>                     <none>       (no description available)
un  virtualbox-4.3                 <none>                     <none>       (no description available)
un  virtualbox-5.0                 <none>                     <none>       (no description available)
un  virtualbox-5.1                 <none>                     <none>       (no description available)
un  virtualbox-5.2                 <none>                     <none>       (no description available)
un  virtualbox-6.0                 <none>                     <none>       (no description available)
un  virtualbox-6.1                 <none>                     <none>       (no description available)
un  virtualbox-7.0                 <none>                     <none>       (no description available)
ii  virtualbox-7.1                 7.1.8-168469~Ubuntu~noble  amd64        Oracle VirtualBox
rc  virtualbox-7.2                 7.2.6-172322~Ubuntu~plucky amd64        Oracle VirtualBox
un  virtualbox-dkms                <none>                     <none>       (no description available)
rc  virtualbox-ext-pack            7.0.16-1                   all          extra capabilities for VirtualBox, downloader.
un  virtualbox-guest-additions-iso <none>                     <none>       (no description available)
un  virtualbox-guest-modules       <none>                     <none>       (no description available)
un  virtualbox-modules             <none>                     <none>       (no description available)
un  virtualbox-ose                 <none>                     <none>       (no description available)
un  virtualbox-qt                  <none>                     <none>       (no description available)
un  virtualbox-source              <none>                     <none>       (no description available)
alan@AM5:~$ 
$ sudo dkms status
[sudo] password for alan: 
alan@AM5:~$ 

(no output from dkms status)

Yes, linux-headers-6.17.0-14-generic installed:

$ sudo apt show linux-headers-6.17.0-14-generic
Package: linux-headers-6.17.0-14-generic
Version: 6.17.0-14.14~24.04.1
Priority: optional
Section: devel
Source: linux-hwe-6.17
Origin: Ubuntu
Maintainer: Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 30.6 MB
Provides: linux-headers, linux-headers-3.0
Depends: linux-hwe-6.17-headers-6.17.0-14, libc6 (>= 2.38), libdw1t64 (>= 0.171), libelf1t64 (>= 0.144), libgcc-s1 (>= 4.2), libssl3t64 (>= 3.0.0), zlib1g (>= 1:1.2.3.3)
Download-Size: 3,979 kB
APT-Manual-Installed: yes
APT-Sources: http://gb.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
Description: Linux kernel headers for version 6.17.0
 This package provides kernel header files for version 6.17.0.
 .
 This is for sites that want the latest kernel headers.  Please read
 /usr/share/doc/linux-headers-6.17.0-14/debian.README.gz for details.

alan@AM5:~$ 

Edit 3

$ sudo apt purge virtualbox=7.0.16-dfsg-2ubuntu1.1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED
  virtualbox*
0 to upgrade, 0 to newly install, 1 to remove and 12 not to upgrade.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
(Reading database ... 479790 files and directories currently installed.)
Purging configuration files for virtualbox (7.0.16-dfsg-2ubuntu1.1) ...

$ sudo apt purge virtualbox-ext-pack=7.0.16-1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED
  virtualbox-ext-pack*
0 to upgrade, 0 to newly install, 1 to remove and 12 not to upgrade.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
(Reading database ... 479788 files and directories currently installed.)
Purging configuration files for virtualbox-ext-pack (7.0.16-1) ...
$ sudo apt reinstall ./virtualbox-7.1_7.1.8-168469~Ubuntu~noble_amd64.deb 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'virtualbox-7.1' instead of './virtualbox-7.1_7.1.8-168469~Ubuntu~noble_amd64.deb'
0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 12 not to upgrade.
Need to get 0 B/108 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 /tmp/virtualbox-7.1_7.1.8-168469~Ubuntu~noble_amd64.deb virtualbox-7.1 amd64 7.1.8-168469~Ubuntu~noble [108 MB]
Preconfiguring packages ...        
(Reading database ... 479788 files and directories currently installed.)
Preparing to unpack .../virtualbox-7.1_7.1.8-168469~Ubuntu~noble_amd64.deb ...
Unpacking virtualbox-7.1 (7.1.8-168469~Ubuntu~noble) over (7.1.8-168469~Ubuntu~noble) ...
Setting up virtualbox-7.1 (7.1.8-168469~Ubuntu~noble) ...
info: The group `vboxusers' already exists as a system group. Exiting.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1.1ubuntu3) ...
Processing triggers for mate-menus (1.26.1-1build3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu5) ...
Rebuilding /usr/share/applications/bamf-2.index...
alan@AM5:/tmp$ 

Same fatal errors: "no such file or directory"

NB 7.1 not in repository, only have .deb from Oracle (sorry, didn't make that clear).

Edit 4

Reinstall of VB 7.1 from within ~/Downloads/Virtualbox/

alan@AM5:~/Downloads/Virtualbox$ sudo apt reinstall ./virtualbox-7.1_7.1.8-168469~Ubuntu~noble_amd64.deb 
[sudo] password for alan: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'virtualbox-7.1' instead of './virtualbox-7.1_7.1.8-168469~Ubuntu~noble_amd64.deb'
0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 12 not to upgrade.
Need to get 0 B/108 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 /home/alan/Downloads/Virtualbox/virtualbox-7.1_7.1.8-168469~Ubuntu~noble_amd64.deb virtualbox-7.1 amd64 7.1.8-168469~Ubuntu~noble [108 MB]
Preconfiguring packages ...        
(Reading database ... 479788 files and directories currently installed.)
Preparing to unpack .../virtualbox-7.1_7.1.8-168469~Ubuntu~noble_amd64.deb ...
Unpacking virtualbox-7.1 (7.1.8-168469~Ubuntu~noble) over (7.1.8-168469~Ubuntu~noble) ...
Setting up virtualbox-7.1 (7.1.8-168469~Ubuntu~noble) ...
info: The group `vboxusers' already exists as a system group. Exiting.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1.1ubuntu3) ...
Processing triggers for mate-menus (1.26.1-1build3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu5) ...
Rebuilding /usr/share/applications/bamf-2.index...
N: Download is performed unsandboxed as root, as file '/home/alan/Downloads/Virtualbox/virtualbox-7.1_7.1.8-168469~Ubuntu~noble_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
alan@AM5:~/Downloads/Virtualbox$ 

Re-run of /sbin/vboxconfig

alan@AM5:~/Downloads/Virtualbox$ sudo /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
alan@AM5:~/Downloads/Virtualbox$ 
$ grep -i "no such" /var/log/vbox-setup.log
linux/../SUPDrvInternal.h:47:10: fatal error: VBox/cdefs.h: No such file or directory
SUPDrvInternal.h:47:10: fatal error: VBox/cdefs.h: No such file or directory
SUPDrvInternal.h:47:10: fatal error: VBox/cdefs.h: No such file or directory
SUPDrvInternal.h:47:10: fatal error: VBox/cdefs.h: No such file or directory
SUPDrvInternal.h:47:10: fatal error: VBox/cdefs.h: No such file or directory
SUPLibAll.c:41:10: fatal error: VBox/sup.h: No such file or directory
common/string/strformatrt.c:42:10: fatal error: iprt/string.h: No such file or directory
combined-agnostic1.c:38:10: fatal error: internal/iprt.h: No such file or directory
combined-agnostic2.c:38:10: fatal error: internal/iprt.h: No such file or directory
combined-os-specific.c:38:10: fatal error: the-linux-kernel.h: No such file or directory

Edit 5

alan@AM5:~/Downloads/Virtualbox$ ls -al virtualbox-7.1_7.1.8-168469~Ubuntu~noble_amd64.deb 
-rw-rw-r-- 1 alan alan 108093464 May  3  2025 virtualbox-7.1_7.1.8-168469~Ubuntu~noble_amd64.deb
$ dpkg -l *headers* | grep ii
ii  linux-headers-6.11.0-21-generic  6.11.0-21.21~24.04.1 amd64        Linux kernel headers for version 6.11.0 on 64 bit x86 SMP
ii  linux-headers-6.11.0-29-generic  6.11.0-29.29~24.04.1 amd64        Linux kernel headers for version 6.11.0 on 64 bit x86 SMP
ii  linux-headers-6.14.0-37-generic  6.14.0-37.37~24.04.1 amd64        Linux kernel headers for version 6.14.0
ii  linux-headers-6.17.0-14-generic  6.17.0-14.14~24.04.1 amd64        Linux kernel headers for version 6.17.0
ii  linux-headers-6.8.0-100          6.8.0-100.100        all          Header files related to Linux kernel version 6.8.0
ii  linux-headers-6.8.0-100-generic  6.8.0-100.100        amd64        Linux kernel headers for version 6.8.0 on 64 bit x86 SMP
ii  linux-headers-generic            6.8.0-100.100        amd64        Generic Linux kernel headers
ii  linux-headers-generic-hwe-24.04  6.17.0-14.14~24.04.1 amd64        Generic Linux kernel headers
ii  linux-hwe-6.11-headers-6.11.0-21 6.11.0-21.21~24.04.1 all          Header files related to Linux kernel version 6.11.0
ii  linux-hwe-6.11-headers-6.11.0-29 6.11.0-29.29~24.04.1 all          Header files related to Linux kernel version 6.11.0
ii  linux-hwe-6.14-headers-6.14.0-37 6.14.0-37.37~24.04.1 all          Header files related to Linux kernel version 6.14.0
ii  linux-hwe-6.17-headers-6.17.0-14 6.17.0-14.14~24.04.1 all          Header files related to Linux kernel version 6.17.0
alan@AM5:~/Downloads/Virtualbox$ 
$ sudo apt purge virtualbox-7.1
[sudo] password for alan: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  liblzf1 libqt6core6t64 libqt6dbus6t64 libqt6gui6t64 libqt6help6 libqt6network6t64 libqt6opengl6t64 libqt6printsupport6t64
  libqt6qml6 libqt6qmlmodels6 libqt6quick6 libqt6sql6-sqlite libqt6sql6t64 libqt6statemachine6 libqt6waylandclient6
  libqt6waylandcompositor6 libqt6waylandeglclienthwintegration6 libqt6waylandeglcompositorhwintegration6 libqt6widgets6t64
  libqt6wlshellintegration6 libqt6xml6t64 libsdl-ttf2.0-0 libsdl1.2debian libtpms0 libts0t64 qt6-gtk-platformtheme
  qt6-qpa-plugins qt6-translations-l10n qt6-wayland
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED
  virtualbox-7.1*
0 to upgrade, 0 to newly install, 1 to remove and 12 not to upgrade.
After this operation, 242 MB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 479788 files and directories currently installed.)
Removing virtualbox-7.1 (7.1.8-168469~Ubuntu~noble) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1.1ubuntu3) ...
Processing triggers for mate-menus (1.26.1-1build3) ...
Processing triggers for shared-mime-info (2.4-4) ...
Processing triggers for bamfdaemon (0.5.6+22.04.20220217-0ubuntu5) ...
Rebuilding /usr/share/applications/bamf-2.index...
(Reading database ... 479039 files and directories currently installed.)
Purging configuration files for virtualbox-7.1 (7.1.8-168469~Ubuntu~noble) ...
dpkg: warning: while removing virtualbox-7.1, directory '/usr/local' not empty so not removed
alan@AM5:~/Downloads/Virtualbox$ 

Synaptic used to install virtualbox 7.0.16-dfsg-2ubuntu1.1
Synaptic also chose and installed virtualbox-dkms and virtualbox-qt

synaptic installing VB 7.0

synaptic error message while trying to install VB 7.0

Virtualbox will run, but I'm back to the original problem.

Edit 6

Synaptic search for "linux-headers-generic":
synaptic: "linux-headers-generic" Looks like the 6.8 headers are still installed.

Uninstall?

From HWE kernels in Ubuntu docs: "HWE (Hardware Enablement) kernels are only enabled on Ubuntu long-term support (LTS) releases...By default, Ubuntu Desktop installations of 24.04 default to tracking the HWE stack.".

alan@AM5:~$ uname -r
6.17.0-14-generic
alan@AM5:~$ 
alan@AM5:~$ dkms status
virtualbox/7.0.16: added
alan@AM5:~$ 

Edit 7

alan@AM5:~$ sudo dkms build virtualbox/7.0.16
[sudo] password for alan: 
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 -j32 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.
alan@AM5:~$ 

The resulting make.log:
/var/lib/dkms/virtualbox/7.0.16/build/make.log [pastebin]

Output from:
sudo apt install build-essential dkms linux-headers-$(uname -r) [pastebin]

alan@AM5:~$ sudo /sbin/vboxconfig
[sudo] password for alan: 
sudo: /sbin/vboxconfig: command not found
alan@AM5:~$ 
alan@AM5:~$ sudo modprobe vboxdrv
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/6.17.0-14-generic
alan@AM5:~$ 
How can I fix boot problem (ending up in BusyBox, UUID not found) https://askubuntu.com/questions/1563923/how-can-i-fix-boot-problem-ending-up-in-busybox-uuid-not-found

I have a dual boot setup (Windows and Ubuntu) on my computer. For background, a while ago when I had different Ubuntu issues I already disabled Windows' "Fast Startup".

The current issue: I tried one day to boot into Ubuntu 24.04, and I just got a screen with the following text:

BusyBox v1.36.1 (Ubuntu 1:1.36.1-6ubuntu3.1) built-in shell (ash) Enter 'help' for a list of built-in commands.
(initramfs)

If I enter "exit" I get:

BusyBox v1.36.1 (Ubuntu 1:1.36.1-6ubuntu3.1) built-in shell (ash) Enter 'help' for a list of built-in commands.
(initramfs) exit
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! UUID=1785c362-92ff-4a9a-b254-f950db82ad8c does not exist. Dropping to a shell!
BusyBox v1.36.1 (Ubuntu 1:1.36.1-6ubuntu3.1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)

My next step was a long, long foray trying to get Perplexity to help me fix the problem. I will summarize for you anything that may be illuminating from those attempts.

It had me create a removable drive to boot Ubuntu temporarily from, and get to the Terminal.

The rest of the diagnostics/changes it had me do I have in this text doc, in case it's useful information for you: https://u.pcloud.link/publink/show?code=XZeSwl5ZqN4vNjc74hSMFUA4RXXT102SEIo7

If anyone can help me where the AI could not, I would be very appreciative. Of course I will give any other information you may need.


Edit: As asked for me to add cat /etc/fstab:

ubuntu@ubuntu:~$ cat /etc/fstab
overlay / overlay rw 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0

Edit 2: As asked for me to add blkid:

ubuntu@ubuntu:~$ blkid
/dev/nvme0n1p1: LABEL_FATBOOT="ESP" LABEL="ESP" UUID="7C4A-25B2" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="d633f6fd-adee-4dff-9951-1be157495497"
/dev/nvme0n1p3: LABEL="OS" BLOCK_SIZE="512" UUID="3E86654D866506AD" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d6cda5f4-67bd-4bc5-9fcc-f979042784a1"
/dev/nvme0n1p4: LABEL="WINRETOOLS" BLOCK_SIZE="512" UUID="D87E1B9A7E1B710C" TYPE="ntfs" PARTUUID="2d9bb834-833f-4ff6-9e43-1e9651579884"
/dev/nvme0n1p5: LABEL="Image" BLOCK_SIZE="512" UUID="C6F21BB2F21BA629" TYPE="ntfs" PARTUUID="e04d2531-67e1-4a7b-9a78-4ca878a9b894"
/dev/nvme0n1p6: LABEL="DELLSUPPORT" BLOCK_SIZE="512" UUID="D80C94CE0C94A950" TYPE="ntfs" PARTUUID="ffb1e1f8-cbbb-4fcf-a159-443048d108ad"
/dev/nvme0n1p7: UUID="1785c362-92ff-4a9a-b254-f950db82ad8c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2760a97d-1428-48af-a023-bc67925f1398"
/dev/sda2: LABEL="Data" BLOCK_SIZE="512" UUID="4A229D11229D02DD" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="ca056f81-9027-4410-b0e2-da1cde2b08a8"
/dev/sdb1: BLOCK_SIZE="2048" UUID="2025-08-05-18-20-26-00" LABEL="Ubuntu 24.04.3 LTS amd64" TYPE="iso9660" PARTLABEL="ISO9660" PARTUUID="b5416491-a6d3-42b2-a3f7-260427bcf601"
/dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/sdb4: LABEL="writable" UUID="ef27101d-0856-49ef-a053-f0a67ec43059" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4de67e78-749f-4939-b303-43325e007e60"
/dev/sdb2: SEC_TYPE="msdos" LABEL_FATBOOT="ESP" LABEL="ESP" UUID="73B7-988D" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="Appended2" PARTUUID="b5416491-a6d3-42b2-a3f4-260427bcf601"
/dev/loop2: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"

Edit 3: From running sudo bash -c 'mount /dev/nvme0n1p7 /mnt && cat /mnt/etc/fstab':

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p7 during curtin installation
/dev/disk/by-uuid/1785c362-92ff-4a9a-b254-f950db82ad8c / ext4 defaults 0 1
# /boot/efi was on /dev/nvme0n1p1 during curtin installation
/dev/disk/by-uuid/7C4A-25B2 /boot/efi vfat defaults 0 1
/swap.img   none    swap    sw  0   0
/dev/disk/by-uuid/3E86654D866506AD /mnt/3E86654D866506AD auto nosuid,nodev,nofail 0 0
/dev/disk/by-id/usb-WD_My_Book_25EE_574343374B32554344485033-0:0-part1 /mnt/usb-WD_My_Book_25EE_574343374B32554344485033-0:0-part1 auto nosuid,nodev,nofail,noauto 0 0
UUID=4A229D11229D02DD  /media/rua/Data/  ntfs-3g  uid=1000,gid=1000,dmask=022,fmask=133  0  0

Edit 4: Put AI information above into an external text file to reduce the increasing size of this post.

Tried code in BusyBox initramfs:

BusyBox v1.36.1 (Ubuntu 1:1.36.1-6ubuntu3.1) built-in shell (ash) Enter 'help' for a list of built-in commands.
(initramfs) ls / sys/class/block
sys/class/block:
loop3 loop5 loop? loop loop2 loop4 loopб loop1
/:
dev
root
kernel
usr
bin
conf etc
init
lib
lib32
lib64
run
sbin
var
sys
proc tmp
lib.usr-is-merged scripts
(initramfs) mount /dev/disk/by-uuid/1785c362-92ff-4a9a-b254-f950db82ad8c /mnt
mount: mounting /dev/disk/by-uuid/1785c362-92ff-4a9a-b254-f950db82ad8c on /mnt failed: No such file or directory (initramfs)
Ubuntu Budgie, OpenRazer, and Secure Boot https://askubuntu.com/questions/1563684/ubuntu-budgie-openrazer-and-secure-boot

I recently cleared my laptop of Windows and installed Ubuntu Budgie 24.04.3 LTS. It is a 2018 Razer Blade 15 Adv. I have two problems.

  1. I installed OpenRazer, which also includes enrolling a MOK. It seems to randomly forget the MOK. It cannot load OpenRazer until I re-enroll the MOK again. Is there something that would remove the MOK automatically?

  2. Sometimes the system will lock up tight and I have to force reboot. The special key (PrtSc) to talk directly to the kernel doesn't work to reboot. I have to force power off. The special key works when not frozen. Also with this comes the MOK being removed from the boot and OpenRazer not loading. Where would I look to figure out what is causing these lock ups? I have checked the logs, but nothing jumps out.

Disk is invisible yet the first part of the boot process is executed [closed] https://askubuntu.com/questions/1562249/disk-is-invisible-yet-the-first-part-of-the-boot-process-is-executed

Computer info:

  • Dell XP 15 9560
  • Ubuntu 20.04.3 LTS (yeah, I know)
  • bootable USB with Ubuntu 24.04.3 LTS
  • The disk has a small ext2 partition for /boot, the rest has been assigned to a logical volume group.

When I tried to boot after a power outage, it dropped to initramfs.

Neither blkid nor lsblk returned anything (the initramfs prompt is returned immediately).

This is odd. The initramfs prompt proves that at least partition one of the disk should be visible.

I ran a full hardware scan from the BIOS. It reported a problem with the batteries (which I removed when they started to swell) and with the integrated webcam (which I don't use anyway).  Even in thorough test mode the disk comes out clean.

I tried booting in recovery mode. There it complains that it cannot find volume group ubuntu-mate-vg. To me this suggests a VG corruption.

When I boot from a bootable USB (Ubuntu 24.04.3), there's no trace of the disk. It does not show up in lshw. When it is not visible, I cannot examine it further.

Do you have any suggestions on how this is possible and how I might proceed?

PS: Note that the disk is not detected in Ubuntu 24.04.3, so this is not just a old version issue.

When I tried to boot after a power outage, it dropped to an (initramfs) prompt.

[    2.819917] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)
[    2.821254] scsi host0: ahci
[    2.821423] idma64 idma64.0: Found Intel integrated DMA 64-bit
[    2.822210] scsi host1: ahci
[    2.823926] ata1: DUMMY
[    2.824975] ata2: SATA max UDMA/133 abar m5242880@0xad100000 port 0xad100180 irq 16
[    2.827231] cryptd: max_cpu_qlen set to 1000
[    2.832562] AVX2 version of gcm_enc/dec engaged.
[    2.833659] AES CTR mode by8 optimization enabled
[    2.857632] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002)
[    2.858942] idma64 idma64.1: Found Intel integrated DMA 64-bit
[    2.870331] i2c_hid i2c-DLL07BE:01: i2c-DLL07BE:01 supply vdd not found, using dummy regulator
[    2.871134] i2c_hid i2c-DLL07BE:01: i2c-DLL07BE:01 supply vddl not found, using dummy regulator
[    3.026742] input: DLL07BE:01 06CB:7A13 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL07BE:01/0018:06CB:7A13.0003/input/input12
[    3.027559] input: DLL07BE:01 06CB:7A13 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL07BE:01/0018:06CB:7A13.0003/input/input13
[    3.028442] hid-generic 0018:06CB:7A13.0003: input,hidraw2: I2C HID v1.00 Mouse [DLL07BE:01 06CB:7A13] on i2c-DLL07BE:01
[    3.140289] ata2: SATA link down (SStatus 4 SControl 300)
[    3.531303] nvidia: loading out-of-tree module taints kernel.
[    3.531964] nvidia: module license 'NVIDIA' taints kernel.
[    3.532611] Disabling lock debugging due to kernel taint
[    3.540265] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    3.545974] nvidia-nvlink: Nvlink Core is being initialized, major device number 238
[    3.547040] nvidia 0000:01:00.0: enabling device (0006 -> 0007)
[    3.663216] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  470.256.02  Thu May  2 14:37:44 UTC 2024
[    3.675466] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  470.256.02  Thu May  2 14:50:40 UTC 2024
[    3.677865] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[    3.678616] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...   Volume group "ubuntu-mate-vg" not found
  Cannot process volume group ubuntu-mate-vg
done.
Begin: Running /scripts/local-premount ... [    16.524828] psmouse serio1: Failed to deactivate mouse on isa0060/serio1: -5
[    17.004827] psmouse serio1: Failed to enable mouse on isa0060/serio1
[    21.300859] input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input11
[    21.504826] psmouse serio1: Failed to enable mouse on isa0060/serio1
Begin: Waiting for suspend/resume device ... Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for suspend/resume device
done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ...   Volume group "ubuntu-mate-vg" not found
  Cannot process volume group ubuntu-mate-vg
done.
done.
Gave up waiting for root file system device.   Common problems:
  - Boot args (cat /proc/cmdline)
    - Check rootdelay= (did the system wait long enough?)
  - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/mapper/ubuntu--mate--vg-root does not exist.  Dropping to a shell!

BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) blkid
(initramfs) _
Desktop environment keeps crashing on Dell Latitude 5411 with Ubuntu 24.04 https://askubuntu.com/questions/1559075/desktop-environment-keeps-crashing-on-dell-latitude-5411-with-ubuntu-24-04

On a fresh installation, my desktop environment is crashing once a day. I thought that it was a wayland issue or graphic card issue. I first blacklisted nouveau to disable the dpgu (product: GP108M [GeForce MX250])

But since didn't solve my issue (and because of another issue), I switched to Xorg. Still, my desktop environment keeps crashing back to the login page (like the very first login and not the locked state kind of login page).

The $ journalctl -p 3 shows me the following relevant lines:

Oct 31 11:37:39 ubuntu gdm3[2936]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Oct 31 11:37:39 ubuntu gdm3[2936]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Oct 31 11:37:51 ubuntu gdm-password][45946]: gkr-pam: unable to locate daemon control file
Oct 31 11:37:52 ubuntu gdm3[2936]: Gdm: on_display_added: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Oct 31 11:37:53 ubuntu systemd[45993]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-46316.scope - Application launched by gnome-session-binary.
Oct 31 11:37:53 ubuntu systemd[45993]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-46318.scope - Application launched by gnome-session-binary.
Oct 31 11:37:53 ubuntu systemd[45993]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-46322.scope - Application launched by gnome-session-binary.
Oct 31 11:37:54 ubuntu systemd[45993]: Failed to start app-gnome-spice\x2dvdagent-46457.scope - Application launched by gnome-session-binary.
Oct 31 11:37:54 ubuntu systemd[45993]: Failed to start app-gnome-ubuntu\x2dreport\x2don\x2dupgrade-46495.scope - Application launched by gnome-session-binary.
Oct 31 11:37:55 ubuntu gdm3[2936]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed

I am using the igpu: Intel(R) Core(TM) i7-10850H CPU @ 2.70GHz


$ lspci -v -s $(lspci | awk '/VGA/{print $1}')
00:02.0 VGA compatible controller: Intel Corporation CometLake-H GT2 [UHD Graphics] (rev 05) (prog-if 00 [VGA controller])
    DeviceName: Onboard - Video
    Subsystem: Dell CometLake-H GT2 [UHD Graphics]
    Flags: bus master, fast devsel, latency 0, IRQ 190
    Memory at eb000000 (64-bit, non-prefetchable) [size=16M]
    Memory at 80000000 (64-bit, prefetchable) [size=256M]
    I/O ports at 4000 [size=64]
    Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
    Capabilities: <access denied>
    Kernel driver in use: i915
    Kernel modules: i915

This very annoying to deal with everyday, even losing some work. Are there any other ways to debug this?

How to fix the Boot screen being stuck with “Failed to start Gnome Display Manager” https://askubuntu.com/questions/1448321/how-to-fix-the-boot-screen-being-stuck-with-failed-to-start-gnome-display-manag

My computer is stuck at a boot screen, with the line says “Failed to start Gnome Display Manager”. I was moving images from folder to folder, and then I had an error saying it’s not responding, now goes the gnome. How do I fix this?

My computer is Ubuntu 22.10

How can I get the equivalent of the Activities view for only one app? https://askubuntu.com/questions/1433134/how-can-i-get-the-equivalent-of-the-activities-view-for-only-one-app

I'm using Ubuntu 22.04.1 LTS

When I hit the super key Activities is called and I can see all the windows.

My question: Is there a way to customize a shortcut so that if I hit (for example) super+t I see all the windows of a particular app (for example the terminal)?

Ubuntu can not turn the monitor on after unlock https://askubuntu.com/questions/1426233/ubuntu-can-not-turn-the-monitor-on-after-unlock

Ubuntu 22.04, 5.15.0-41-generic, i12700K integrated graphics, monitor Asus pg32uq connected through HDMI. This is not a laptop. All power saving features that I could find through GUI settings are turned off.

This is what happens when the monitor is connected to Ubuntu machine only. When the computer is locked, the monitor is blank. Pressing buttons on the keyboard does not make the monitor show any information from Ubuntu. A message "HDMI no signal" appears on the monitor from time to time. I assume that the computer starts sending signal and then stops periodically. After pressing Ctrl-Alt-F1,Ctrl-Alt-F2,Space a few times a screen with my account name appears. After I enter the password, the screen goes blank again. In most cases, it shows me Ubuntu desktop after that. In some cases, after the password is entered, the monitor shows "HDMI no signal" again and I have to repeat the process of unlocking from scratch.

The following happens when the monitor is connected to Ubuntu and Windows machines at the same time. I have described the horror with the monitor connected to just one Linux computer above. I also have a Windows 10 laptop, which I connect to the same monitor through another HDMI port. The laptop works with this monitor perfectly, regardless of whether Ubuntu machine is connected or not. However, connecting the laptop makes the situation for Ubuntu worse. The monitor auto-switches between HDMI ports when it does not sense a signal. There is no way to turn auto-source off for this monitor. As soon as the monitor senses no signal on the port connected to the Linux machine, it switches back to the Windows machine. In many cases I find it impossible to login into Ubuntu machine without physically disconnecting the monitor from the Windows machine first. After Windows laptop is disconnected from the monitor, the situation for Ubuntu from impossible becomes terrible, as described above.

Any ideas how to make Ubuntu send a video signal all the time?

Ubuntu keeps freezing https://askubuntu.com/questions/1402395/ubuntu-keeps-freezing

My laptop has an SSD and 16GB of RAM, so I know the problem isn’t specs. This laptop used to have Windows and I never ever had any performance issues with it, but this changed ever since I switched to Ubuntu. I did it because I work with Docker and it runs faster on Linux.

The problem is, sometimes the system just completely freezes and I have to wait several minutes for it to work again. There are times it takes so long it’s faster to reboot it with the power button. Does anyone has any idea of what may be causing this? It happens at least 3 times a day and I am pissed.

I usually use Docker, Firefox, Discord and VSCode at the same time. I used all this on Windows too, and never had any problems except for the fact that Docker works much better on Linux.

Ubuntu doesn't recognize my internal hard drive https://askubuntu.com/questions/1395756/ubuntu-doesnt-recognize-my-internal-hard-drive

All of a sudden yesterday when I boot Ubuntu 20.04 from EFI (grub) it just goes to a black screen. In the BIOS it recognizes my hard drive as the 250GB Samsung SSD, but when I go to load Ubuntu, it boots to a black screen.

So I loaded Ubuntu from a USB and when I went to install there was nothing on the Drives page. I cancelled the installation and went to "Try Ubuntu" and into Disks and the only disks it showed were the loop stuff and the 32GB USB stick. It didn't pick up the 250GB internal hard drive.

I don't mind a clean reinstall if something is corrupted, but I do need files off the original install.

ubuntu@ubuntu:~$ sudo lsblk -f
NAME   FSTYPE   LABEL                     UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0  squash                                                               0   100%   /rofs
loop1  squash                                                               0   100%   /snap/core
loop2  squash                                                               0   100%   /snap/gnome
loop3  squash                                                               0   100%   /snap/gtk-
loop4  squash                                                               0   100%   /snap/snap
loop5  squash                                                               0   100%   /snap/snap
sda    iso9660  Ubuntu 20.04.3 LTS amd64  2021-08-19-11-03-38-00
├─sda1 iso9660  Ubuntu 20.04.3 LTS amd64  2021-08-19-11-03-38-00              0   100%   /cdrom
├─sda2 vfat     54C5-9C6C
└─sda3 ext4     writable                 9fbee645-7648-4108-a9c2-9690006d103a 16.3G   32%   /var/crash
sr0
ubuntu@ubuntu:~$
Is MariaDB 10.3 compatible with MySQL 8.0.20, dependency check failed https://askubuntu.com/questions/1246995/is-mariadb-10-3-compatible-with-mysql-8-0-20-dependency-check-failed

I have installed Ubuntu 20.04 applied Devstack for Openstack application

mysql is working:

stack@rafael-VirtualBox:~/devstack$ mysql --version
mysql  Ver 8.0.20-0ubuntu0.20.04.1 for Linux on x86_64 ((Ubuntu))
stack@rafael-VirtualBox:~/devstack$ mysql

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 68
Server version: 8.0.20-0ubuntu0.20.04.1 (Ubuntu)

Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
root@rafael-VirtualBox:~# systemctl status mysql

mysql.service - MySQL Community Server

     Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)

     Active: active (running) since Tue 2020-06-02 15:09:08 CDT; 2 days ago
    Process: 986 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
   Main PID: 1086 (mysqld)
     Status: "Server is operational"
      Tasks: 61 (limit: 4616)
     Memory: 325.4M
     CGroup: /system.slice/mysql.service
             └─1086 /usr/sbin/mysqld


Jun 02 15:08:41 rafael-VirtualBox systemd[1]: Starting MySQL Community Server...
Jun 02 15:09:08 rafael-VirtualBox systemd[1]: Started MySQL Community Server.

When I try to install MariaDB:

sudo apt update
sudo apt install mariadb-server
sudo mysql_secure_installation

I receive the following:

root@rafael-VirtualBox:~# sudo apt update
Hit:1 http://us.archive.ubuntu.com/ubuntu focal InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu focal-backports InRelease         
Hit:4 http://security.ubuntu.com/ubuntu focal-security InRelease            
Reading package lists... Done
Building dependency tree       
Reading state information... Done
45 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@rafael-VirtualBox:~# sudo apt install mariadb-server
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 **mariadb-server : Depends: mariadb-server-10.3 (>= 1:10.3.22-1ubuntu1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.**

So this error threw me for a loop.... why wouldn't it be installed automatically???

The following packages have unmet dependencies:
mariadb-server : Depends: mariadb-server-10.3 (>= 1:10.3.22-1ubuntu1) but it is not going to be installed

E: Unable to correct problems, you have held broken packages.

Seems like change of the commands did the trick:

sudo apt install mariadb-server-10.3
sudo apt install mariadb-server
root@rafael-VirtualBox:/var/log# sudo mysql_secure_installation

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
      SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!

In order to log into MariaDB to secure it, we'll need the current
password for the root user.  If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.

Enter current password for root (enter for none): 
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Enter current password for root (enter for none): 
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Enter current password for root (enter for none):

So how do I resolve the ERROR 2002, none of the web info or YouTube videos have Ubuntu 20.4 with MariaDb 10.3


UPDATE:

I edited /etc/mysql/my.cnf and /etc/mysql/cnf to get past this issue, but stumbled on another....

#cat > /etc/mysql/my.cnf << EOF
#cat > /etc/mysql/mariadb.cnf << EOF

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port        = 3306
socket      = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

[mysqld]
max_connections = 1024
#default-storage-engine = InnoDB
#sql_mode = TRADITIONAL
#bind-address = 0.0.0.0
#lower_case_table_names = 2
user        = mysql
pid-file    = /var/run/mysqld/mysqld.pid
socket      = /var/run/mysqld/mysqld.sock
port        = 3306
basedir     = /usr/bin
datadir     = /var/lib/mysql
tmpdir      = /tmp
lc-messages-dir = /usr/share/mysql
skip-external-locking

innodb_buffer_pool_size = 10M
innodb_log_file_size = 1000M

character_set_server           = utf8mb4                             # For modern applications, default in MySQL 8.0
thread_cache_size              = 151                                 # Up to max_connections makes sense


[mysqld_safe]
socket      = /var/run/mysqld/mysqld.sock
nice        = 0

next issue:

Jun  4 20:55:21 rafael-VirtualBox mysqld[76969]: 2020-06-04 20:55:21 0 [ERROR] InnoDB: Invalid flags 0x4800 in ./ibdata1
Jun  4 20:55:21 rafael-VirtualBox mysqld[76969]: 2020-06-04 20:55:21 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
Jun  4 20:55:22 rafael-VirtualBox mysqld[76969]: 2020-06-04 20:55:22 0 [Note] InnoDB: Starting shutdown...
Jun  4 20:55:22 rafael-VirtualBox kernel: [ 6034.871865] audit: type=1400 audit(1591322122.402:15641): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnect
ed path" error=-13 profile="/usr/sbin/mysqld" name="run/systemd/notify" pid=76969 comm="mysqld" requested_mask="w" denied_mask="w" fsuid=132 ouid=0
Jun  4 20:55:22 rafael-VirtualBox mysqld[76969]: 2020-06-04 20:55:22 0 [ERROR] Plugin 'InnoDB' init function returned error.
Jun  4 20:55:22 rafael-VirtualBox mysqld[76969]: 2020-06-04 20:55:22 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jun  4 20:55:22 rafael-VirtualBox mysqld[76969]: 2020-06-04 20:55:22 0 [Note] Plugin 'FEEDBACK' is disabled.
Jun  4 20:55:22 rafael-VirtualBox mysqld[76969]: 2020-06-04 20:55:22 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded

Then had to clear the system tables:

systemctl stop mariadb
rm -R /var/lib/mysql/*
mysql_install_db --user=mysql --basedir=/usr --datadir=/var/lib/mysql

restarted the Mariadb service, no errors, but stuck in Activating state:

root@rafael-VirtualBox:/opt/stack# systemctl start mariadb

root@rafael-VirtualBox:/var/lib/mysql# systemctl status mariadb
● mariadb.service - MariaDB 10.3.22 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
     Active: activating (start) since Thu 2020-06-04 21:20:03 CDT; 9s ago
       Docs: man:mysqld(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 78228 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 78235 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 78237 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_STAR>
   Main PID: 78300 (mysqld)
      Tasks: 30 (limit: 4616)
     Memory: 55.2M
     CGroup: /system.slice/mariadb.service
             └─78300 /usr/sbin/mysqld

Jun 04 21:20:03 rafael-VirtualBox mysqld[78300]: 2020-06-04 21:20:03 0 [Note] InnoDB: Waiting for purge to start
Jun 04 21:20:03 rafael-VirtualBox mysqld[78300]: 2020-06-04 21:20:03 0 [Note] InnoDB: 10.3.22 started; log sequence number 1625457; transaction id 21
Jun 04 21:20:03 rafael-VirtualBox mysqld[78300]: 2020-06-04 21:20:03 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Jun 04 21:20:03 rafael-VirtualBox mysqld[78300]: 2020-06-04 21:20:03 0 [Note] Plugin 'FEEDBACK' is disabled.
Jun 04 21:20:03 rafael-VirtualBox mysqld[78300]: 2020-06-04 21:20:03 0 [Note] InnoDB: Buffer pool(s) load completed at 200604 21:20:03
Jun 04 21:20:03 rafael-VirtualBox mysqld[78300]: 2020-06-04 21:20:03 0 [Note] Server socket created on IP: '::'.
Jun 04 21:20:03 rafael-VirtualBox mysqld[78300]: 2020-06-04 21:20:03 0 [Note] Reading of all Master_info entries succeeded
Jun 04 21:20:03 rafael-VirtualBox mysqld[78300]: 2020-06-04 21:20:03 0 [Note] Added new Master_info '' to hash table
Jun 04 21:20:03 rafael-VirtualBox mysqld[78300]: 2020-06-04 21:20:03 0 [Note] /usr/sbin/mysqld: ready for connections.
Jun 04 21:20:03 rafael-VirtualBox mysqld[78300]: Version: '10.3.22-MariaDB-1ubuntu1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Ubuntu 20.04
lines 1-24/24 (END)

to:

Job for mariadb.service failed because a timeout was exceeded.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
root@rafael-VirtualBox:/opt/stack# systemctl status mariadb.service
● mariadb.service - MariaDB 10.3.22 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
     Active: failed (Result: timeout) since Thu 2020-06-04 21:14:44 CDT; 1min 24s ago
       Docs: man:mysqld(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 77248 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 77256 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 77261 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemc>
    Process: 77318 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
   Main PID: 77318 (code=exited, status=0/SUCCESS)

Jun 04 21:14:43 rafael-VirtualBox mysqld[77318]: 2020-06-04 21:14:43 0 [Note] Event Scheduler: Purging the queue. 0 events
Jun 04 21:14:43 rafael-VirtualBox mysqld[77318]: 2020-06-04 21:14:43 0 [Note] InnoDB: Starting shutdown...
Jun 04 21:14:43 rafael-VirtualBox mysqld[77318]: 2020-06-04 21:14:43 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
Jun 04 21:14:43 rafael-VirtualBox mysqld[77318]: 2020-06-04 21:14:43 0 [Note] InnoDB: Instance 0, restricted to 160 pages due to innodb_buf_pool_du>
Jun 04 21:14:43 rafael-VirtualBox mysqld[77318]: 2020-06-04 21:14:43 0 [Note] InnoDB: Buffer pool(s) dump completed at 200604 21:14:43
Jun 04 21:14:44 rafael-VirtualBox mysqld[77318]: 2020-06-04 21:14:44 0 [Note] InnoDB: Shutdown completed; log sequence number 1625457; transaction >
Jun 04 21:14:44 rafael-VirtualBox mysqld[77318]: 2020-06-04 21:14:44 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
Jun 04 21:14:44 rafael-VirtualBox mysqld[77318]: 2020-06-04 21:14:44 0 [Note] /usr/sbin/mysqld: Shutdown complete
Jun 04 21:14:44 rafael-VirtualBox systemd[1]: mariadb.service: Failed with result 'timeout'.
Jun 04 21:14:44 rafael-VirtualBox systemd[1]: Failed to start MariaDB 10.3.22 database server.

I'll take suggestion to continue my investigation


UPDATE


Looks like there is a bug in installing Mariadb

In case you are bitten by this bug, the solution is given as a suggestion in the bug report:

  1. echo "/usr/sbin/mysqld { }" > /etc/apparmor.d/usr.sbin.mysqld
  2. apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld
  3. systemctl restart mariadb

Background

If you previously had MySQL installed, it activated an AppArmor profile which is incompatible with MariaDB. apt-get remove --purge only removes the profile, but does not deactivate/unload it. Only manually unloading it lets MariaDB work unhindered by AppArmor.

My output has changed to ACTIVE:

root@rafael-VirtualBox:/var/lib/mysql# echo "/usr/sbin/mysqld { }" > /etc/apparmor.d/usr.sbin.mysqld
root@rafael-VirtualBox:/var/lib/mysql# apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld
Removal succeeded for "/usr/sbin/mysqld".
root@rafael-VirtualBox:/var/lib/mysql# systemctl restart mariadb
root@rafael-VirtualBox:/var/lib/mysql# systemctl status mariadb
● mariadb.service - MariaDB 10.3.22 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2020-06-04 21:27:03 CDT; 5s ago
       Docs: man:mysqld(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 78643 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 78655 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 78657 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_STAR>
    Process: 78745 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 78747 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUCCESS)
   Main PID: 78713 (mysqld)
     Status: "Taking your SQL requests now..."
      Tasks: 31 (limit: 4616)
     Memory: 60.2M
     CGroup: /system.slice/mariadb.service
             └─78713 /usr/sbin/mysqld

Jun 04 21:27:03 rafael-VirtualBox mysqld[78713]: 2020-06-04 21:27:03 8 [Warning] Access denied for user 'debian-sys-maint'@'localhost' (using password: YES)
Jun 04 21:27:03 rafael-VirtualBox mysqld[78713]: 2020-06-04 21:27:03 9 [Warning] Access denied for user 'debian-sys-maint'@'localhost' (using password: YES)
Jun 04 21:27:03 rafael-VirtualBox /etc/mysql/debian-start[78752]: Looking for 'mysql' as: /usr/bin/mysql
Jun 04 21:27:03 rafael-VirtualBox /etc/mysql/debian-start[78752]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Jun 04 21:27:03 rafael-VirtualBox /etc/mysql/debian-start[78752]: Version check failed. Got the following error when calling the 'mysql' command line client
Jun 04 21:27:03 rafael-VirtualBox /etc/mysql/debian-start[78752]: ERROR 1045 (28000): Access denied for user 'debian-sys-maint'@'localhost' (using password: YES)
Jun 04 21:27:03 rafael-VirtualBox /etc/mysql/debian-start[78752]: FATAL ERROR: Upgrade failed
Jun 04 21:27:03 rafael-VirtualBox /etc/mysql/debian-start[78762]: Checking for insecure root accounts.
Jun 04 21:27:03 rafael-VirtualBox mysqld[78713]: 2020-06-04 21:27:03 10 [Warning] Access denied for user 'debian-sys-maint'@'localhost' (using password: YES)
Jun 04 21:27:03 rafael-VirtualBox debian-start[78765]: ERROR 1045 (28000): Access denied for user 'debian-sys-maint'@'localhost' (using password: YES)
How do I use the softdog module? https://askubuntu.com/questions/1246187/how-do-i-use-the-softdog-module

I am trying to use the software watchdog kernel module called softdog. I am not sure how to use it properly.

I have removed the module from ...

/etc/modprobe.d/blacklist-watchdog.conf

Then I have run...

modprobe softdog

This resulted in the following line in dmesg...

│[60656.721980] softdog: initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0)

So it seems like softdog was initialized correctly.

Once softdog initializes the files /dev/watchdog and /dev/watchdog0 are created.

But I have not started a watchdog daemon, so I assume no one is feeding these files (no clue why there is two).

I am expecting that because I do not have a watchdog daemon installed, that softdog will reboot the system....but this is not what I am seeing. (fyi I plan on installing a watchdog daemon once I can confirm that softdog module is capable of restarting the system).

Has anyone ever successfully configured the softdog module to work as a software watchdog?

Wifi and settings system are missing https://askubuntu.com/questions/1212314/wifi-and-settings-system-are-missing

I installed ubuntu 18.04 LTS this week. So at first, I had a problem with the wifi connection. It really was not stable; wifi was disconnected every 5 minutes. So I googled about it and tried this command:

sudo apt install wicd-gtk

Then, I somehow uninstalled network-manager

sudo apt remove network-manager-gnome network-manager

and I rebooted.

Unfortunately, that made it even worse as the settings menu disappeared. So basically I can't connect to wifi and I can't open the settings menu.

I have tried:

sudo apt install-gnome-control-center

and also many more commands. I'm kind of new to Ubuntu.

UFW rules with NAT/masquerading https://askubuntu.com/questions/1151289/ufw-rules-with-nat-masquerading

I am trying to use Ubuntu as a router of a kind by limiting a computer on my private network to what it can connect to on the internet.

The Ubuntu box has two NICs, one is internet facing (enp0s3), one is facing this single private PC (enp0s8).

To start with, I wanted to see if I could just allow DNS from the private box through the Ubuntu. I followed some instructions to add some "route allow" rules such as it results in:

ufw status verbose
Status: active
Logging: on (low)
Default: deny (incoming), deny (outgoing), allow (routed)
New profiles: skip

To                         Action      From
--                         ------      ----
8.8.8.8 on enp0s3          ALLOW FWD   Anywhere on enp0s8        
8.8.4.4 on enp0s3          ALLOW FWD   Anywhere on enp0s8        
10.0.1.5 on enp0s8         ALLOW FWD   Anywhere on enp0s3   

10.0.1.5 is my private PC. Using Wireshark I can see DNS requests being made on both enp0s3 and enp0s8, but the ones on enp0s3 have no reply.

So after a bit more reading, I found I needed to set up NAT and masquerading, so I put the following into rules.before:

# NAT table rules
*nat
:POSTROUTING ACCEPT [0:0]

# Forward traffic through eth0 - Change to match you out-interface
-A POSTROUTING -s 10.0.1.0/24 -o enp0s3 -j MASQUERADE

# don't delete the 'COMMIT' line or these nat table rules won't
# be processed
COMMIT

This worked - but too well. Now all traffic is getting out and returned to my private PC, the default deny outgoing and the other UFW rules all seem to be bypassed.

So my question is simple - I want the private PC to get connectivity through Ubuntu such as the NAT provided, but with the outgoing restrictions as I thought I configured initially using the ufw command lines. Is there a way I get can get the UFW rules to somehow apply after the NAT does its thing?

TIA.

Here is the full before.rules file. My only change was the NAT table rules:

#
# rules.before
#
# Rules that should be run before the ufw command line added rules. Custom
# rules should be added to one of these chains:
#   ufw-before-input
#   ufw-before-output
#   ufw-before-forward
#

# NAT table rules
*nat
:POSTROUTING ACCEPT [0:0]

# Forward traffic through eth0 - Change to match you out-interface
-A POSTROUTING -s 10.0.1.0/24 -o enp0s3 -j MASQUERADE

# don't delete the 'COMMIT' line or these nat table rules won't
# be processed
COMMIT


# Don't delete these required lines, otherwise there will be errors
*filter
:ufw-before-input - [0:0]
:ufw-before-output - [0:0]
:ufw-before-forward - [0:0]
:ufw-not-local - [0:0]
# End required lines


# allow all on loopback
-A ufw-before-input -i lo -j ACCEPT
-A ufw-before-output -o lo -j ACCEPT

# quickly process packets for which we already have a connection
-A ufw-before-input -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A ufw-before-output -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A ufw-before-forward -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT

# drop INVALID packets (logs these in loglevel medium and higher)
-A ufw-before-input -m conntrack --ctstate INVALID -j ufw-logging-deny
-A ufw-before-input -m conntrack --ctstate INVALID -j DROP

# ok icmp codes for INPUT
-A ufw-before-input -p icmp --icmp-type destination-unreachable -j ACCEPT
-A ufw-before-input -p icmp --icmp-type time-exceeded -j ACCEPT
-A ufw-before-input -p icmp --icmp-type parameter-problem -j ACCEPT
-A ufw-before-input -p icmp --icmp-type echo-request -j ACCEPT

# ok icmp code for FORWARD
-A ufw-before-forward -p icmp --icmp-type destination-unreachable -j ACCEPT
-A ufw-before-forward -p icmp --icmp-type time-exceeded -j ACCEPT
-A ufw-before-forward -p icmp --icmp-type parameter-problem -j ACCEPT
-A ufw-before-forward -p icmp --icmp-type echo-request -j ACCEPT

# allow dhcp client to work
-A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT

#
# ufw-not-local
#
-A ufw-before-input -j ufw-not-local

# if LOCAL, RETURN
-A ufw-not-local -m addrtype --dst-type LOCAL -j RETURN

# if MULTICAST, RETURN
-A ufw-not-local -m addrtype --dst-type MULTICAST -j RETURN

# if BROADCAST, RETURN
-A ufw-not-local -m addrtype --dst-type BROADCAST -j RETURN

# all other non-local packets are dropped
-A ufw-not-local -m limit --limit 3/min --limit-burst 10 -j ufw-logging-deny
-A ufw-not-local -j DROP

# allow MULTICAST mDNS for service discovery (be sure the MULTICAST line above
# is uncommented)
-A ufw-before-input -p udp -d 224.0.0.251 --dport 5353 -j ACCEPT

# allow MULTICAST UPnP for service discovery (be sure the MULTICAST line above
# is uncommented)
-A ufw-before-input -p udp -d 239.255.255.250 --dport 1900 -j ACCEPT

# don't delete the 'COMMIT' line or these rules won't be processed
COMMIT
Grub pointing to an incorrect windows partition https://askubuntu.com/questions/1072614/grub-pointing-to-an-incorrect-windows-partition

I just installed an Ubuntu 18.04 on the side of my windows 10 partition. after the install, every time I tried to boot to windows it always told me that winload.exe does not exist/is corrupted and windows can't boot.

Apparently grub has incorrectly assigned my second HDD as the windows 10 boot drive (/dev/sdc1) instead of my SSD (SATA 0, partition 0)(/dev/sda0/ I think), that of telling windows to try to boot from there, and of course, it didn't work, as there are no windows there.

So how can I change it to point to the SSD instead?

also, a little clarifier :

I have 1 SSD and 2 HDD, formerly I only have 1 HDD, but I've since upgraded to an SSD and proceed to reinstall windows to the new SSD. I forgot if I ever did a full wipe on the former HDD, as there is still some leftover windows file (who knows if the MBR ever get wiped on that HDD)

I haven't yet tried to boot it from the windows boot manager option on bios, I guess I will try that later

edit : added the output from boot-info

after i see the boot-info output, there are something that i don't understand. like why grub told me in the grub menu that windows is on /dev/sdc3/ when clearly sdc3 is not even a thing on my computer.

and when i run the sudo update-grub command, the windows partition changes to sdc1, which is a thing, but still is the wrong HDD

Edit 2 :

I did the bootrec /fixmbr thing to try and restore windows bootloader into MBR. But sadly i still can't boot back to windows, let alone ubuntu. And as i dont have much time, i just reinstalled the whole thing.

Thank you very much for everyone bothering to answer. I hope your answer will be beneficial for someone else

Setting up hard drive in QEMU+KVM? https://askubuntu.com/questions/764041/setting-up-hard-drive-in-qemukvm

I'm running Ubuntu 16.04 LTS and I am using QEMU+KVM+OVMF for a Windows VM. Is there a way to mount physical hard drives to the VM only without using a container, as well as keep the data that is still on them?

There are examples of this I assume but I only see them in XML format and I use QEMU command line script. Not very familiar with conversions, no idea what format I'd need to put it in.

http://pastebin.com/WRaZuM02 The script I use. I supposedly need to use UUID for my hard drives but I never seen that used in CLI before.

How to keep sfdisk working? https://askubuntu.com/questions/696274/how-to-keep-sfdisk-working

I updated to Ubuntu 15.10 but it causes a huge issue for me: sfdisk doesn't work anymore.

I really need sfdisk to build partitions on SD card for my embedded Linux but it seems that options have changed.

Here is my script:

CARD_DEV=$1

unset LANG

umount ${CARD_DEV}* >& /dev/null

if [ -b "$CARD_DEV" ] ; then
    echo "*************** Formatting SD card... ***************"
    dd if=/dev/zero of=$CARD_DEV bs=1024 count=1024
    SIZE=`fdisk -l $CARD_DEV | grep Disk | awk '{print $5}'`
    echo DISK SIZE - $SIZE bytes
    CYLINDERS=`echo $SIZE/255/63/512 | bc`
    echo CYLINDERS - $CYLINDERS
    {
        echo 1,9,0x0C,*
        echo 10,,,-
    } | sfdisk -D -H 255 -S 63 -C $CYLINDERS $CARD_DEV
    mkfs.vfat -F 32 -n "boot" ${CARD_DEV}1
    mke2fs -j -L "filesystem" ${CARD_DEV}2
fi

And the output error:

sfdisk: invalid option -- 'D'

 sfdisk [options] <dev> [[-N] <part>]
 sfdisk [options] <command>

Display or manipulate a disk partition table.

Commands:
 -A, --activate <dev> [<part> ...] list or set bootable MBR partitions
 -d, --dump <dev>                  dump partition table (usable for later input)
 -g, --show-geometry [<dev> ...]   list geometry of all or specified devices
 -l, --list [<dev> ...]            list partitions of each device
 -s, --show-size [<dev> ...]       list sizes of all or specified devices
 -T, --list-types                  print the recognized types (see -X)
 -V, --verify                      test whether partitions seem correct

 --part-label <dev> <part> [<str>] print or change partition label
 --part-type <dev> <part> [<type>] print or change partition type
 --part-uuid <dev> <part> [<uuid>] print or change partition uuid
 --part-attrs <dev> <part> [<str>] print or change partition attributes

 <dev>                     device (usually disk) path
 <part>                    partition number
 <type>                    partition type, GUID for GPT, hex for MBR

Options:
 -a, --append              append partitions to existing partition table
 -b, --backup              backup partition table sectors (see -O)
     --bytes               print SIZE in bytes rather than in human readable format
 -f, --force               disable all consistency checking
     --color[=<when>]      colorize output (auto, always or never)
                             colors disabled by default
 -N, --partno <num>        specify partition number
 -n, --no-act              do everything except write to device
     --no-reread           do not check whether the device is in use
 -O, --backup-file <path>  override default backup file name
 -o, --output <list>       output columns
 -q, --quiet               suppress extra info messages
 -X, --label <name>        specify label type (dos, gpt, ...)
 -Y, --label-nested <name> specify nested label type (dos, bsd)

 -L, --Linux               deprecated, only for backward compatibility
 -u, --unit S              deprecated, only sector unit is supported

 -h, --help     display this help and exit
 -v, --version  output version information and exit

Available columns (for -o):
 gpt: Device Start End Sectors Size Type Type-UUID Attrs Name UUID
 dos: Device Start End Sectors Cylinders Size Type Id Attrs Boot End-C/H/S
      Start-C/H/S
 bsd: Slice Start End Sectors Cylinders Size Type Bsize Cpg Fsize
 sgi: Device Start End Sectors Cylinders Size Type Id Attrs
 sun: Device Start End Sectors Cylinders Size Type Id Flags

For more details see sfdisk(8).

Version:

sfdisk from util-linux 2.26.2
How do I disable the touchpad while typing on Macbook? https://askubuntu.com/questions/317650/how-do-i-disable-the-touchpad-while-typing-on-macbook

I have a Macbook Pro 5.5 and I can't disable the touchpad while I'm typing. I have tried downloading gsynaptics manager or something like that, but still no dice!

This is driving me up the wall, please help.

Mouse/Touchpad Settings for Samsung Series 9 in Ubuntu 13.04 https://askubuntu.com/questions/302441/mouse-touchpad-settings-for-samsung-series-9-in-ubuntu-13-04

I've just installed Ubuntu 13.04 on my Samsung Series 9, and I'm having trackpad issues. The community page for the series 9 indicates that the trackpad (including gestures, etc) works out of the box, but I'm unable to scroll with two fingers, min/max with three, etc. When I open up the mouse/trackpad settings, I see options that only relate to the mouse, almost as though a trackpad is not being detected:

{Not enough reputation points to post image, but I only have settings for 1) primary button, 2) Double-click speed and 3) Pointer speed}

However, looking at the output from xinput list, the touchpad is certainly being detected:

salexander@Sammy:~$ xinput list
 Virtual core pointer                       id=2    [master pointer  (3)]
   ↳ Virtual core XTEST pointer                 id=4    [slave  pointer  (2)]
   ↳ PS/2 Elantech Touchpad                     id=11   [slave  pointer  (2)]
 Virtual core keyboard                      id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
    ↳ Power Button                              id=8    [slave  keyboard (3)]
    ↳ WebCam SC-13HDL11624N                     id=9    [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=10   [slave  keyboard (3)]

Any idea what could be going on? Any reason I would be having issues with the trackpad when the Samsung Series 9 Community page indicates everything is alright? Googling didn't provide much help, and I couldn't find any bug reports with this description (I'll be sure to create one).

Thanks in advance for the help!

How do I free up disk space? https://askubuntu.com/questions/5980/how-do-i-free-up-disk-space

My Ubuntu cloud server has left only 900MB of disk space.

I'll just empty the directory /tmp and wondering if there is any other location to clean up.