I'm using Ubuntu Mate 25.10.

I'd like to install LibreWolf.

Any suggestions?

Hello to all users here I Install the Ubuntu 24.04 on my computer and in the first I was have a problem with the screen . that I see only Gray screen I fix it . after that i see that I not have sound I go to the control panel and go to sound and i see that I see that the grafs move but no sound . when I try the regolar pin output of speeker on the board it work wall .but in the optical S/PDIF conection no sound i try to fix the problem with chatgpt . we try to install drivers and try to install Alsamixer . pavucontrol . and no sucsses with that if some body here can help me or guide me to selution it well be wonderfull Thank you and have a nice day

I want to set my screen blanking time to half an hour. What are the command line instructions for this?

Ubuntu 25.10 desktop. In the power options there is a choice to set the automatic screen blank, the maximum being 15 minute delay.

My laptop is just low powered computer (travelmate B311), And it was a former windows os laptop until i decided to go on to debian. But when i plug a usb flashstick, It doesn't open or it refuses to recognize on thunar. I cant write, And the usb was labled a card? and i tried portable ssd. It was recognize but it doesnt mount on. I tried all fixes like ntfsfix, Gparted repair, etc. But does not work, like i tried many usb drives, And still says this error. Only a live boot usb Recognized.

I am unable to install any packages in my ubuntu.. Let me know if you guys have faced same Issue.

sudo apt install openssh-server -y
You might want to run 'apt --fix-broken install' to correct these.
Unsatisfied dependencies:
 dbus : Depends: base-files (>= 13.4~)
 libc6 : Breaks: base-files (< 13.3~)
         Breaks: base-files:i386 (< 13.3~)
 openssh-server : Depends: openssh-sftp-server
                  Recommends: ncurses-term but it is not going to be installed
                  Recommends: ssh-import-id but it is not going to be installed
Error: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
Error: The following information from --solver 3.0 may provide additional context:
   Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

I previously put on hold the kernel update on a system as the updates were breaking the system. This was described in this question.

I came across this article:

The Ubuntu 24.04.4 LTS hardware enablement stack (HWE) has finally hit the updates repo, bringing Linux kernel 6.17 and Mesa 25.2.7 to users on the current long-term support release

As such I unheld the kernel using this command and installed the linux-headers-generic-hwe-24.04:

$ sudo apt-mark unhold 6.14.0-33-generic
$ sudo apt update
$ sudo apt install linux-headers-generic-hwe-24.04

However the installation failed because of btusb/4.2. According to AI, I could resolve this issue by removing that bluetooth app

I then removed it and reinstalled linux-headers-generic-hwe-24.04:

$ sudo dkms status
$ sudo dkms remove btusb/4.2 --all
$ sudo apt clean
$ sudo dpkg --configure -a
$ sudo apt update && sudo apt upgrade
$ sudo apt install linux-headers-generic-hwe-24.04
$ uname -a

However 6.14.0-33-generic #33~24.04.1-Ubuntu is still being used.

I rebooted my system and updated the system but still the kernel was not updated. I discovered another problem. The multi-screen display no longer worked and only one monitor would appear. I verified that this issue was unrelated to any hardware issue and is a software issue.

Consequently, went into the terminal mode via Ctrl + Alt + F3 to reinstall purge the nvidia drivers, reinstall the current working linux kernel and reinstalled the nvidia drivers:

$ sudo apt remove --purge nvidia-*
$ sudo apt autoremove
$ sudo apt autoclean
$ sudo apt install linux-headers-$(uname -r)
$ sudo ubuntu-drivers autoinstall
$ sudo reboot

After the reboot, the multi-monitor displays worked again. I reinstalled linux-headers-generic-hwe-24.04:

$ sudo apt remove --purge linux-headers-generic-hwe-24.04
$ sudo apt install linux-headers-generic-hwe-24.04

However, the Linux kernel 6.17 was still not showing up. Also bluetooth can no longer be enabled.

How do I get the Linux kernel 6.17 to be loaded and get the bluetooth to work again?

I confirm that linux-headers-generic-hwe-24.04 is installed.

$ sudo apt install linux-headers-generic-hwe-24.04
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
linux-headers-generic-hwe-24.04 is already the newest version (6.17.0-14.14~24.04.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

However, the linux kernel does not shows to be updated:

$ uname -r
6.14.0-33-generic


$ sudo dpkg --configure -a ; ls -l /boot
.rw-r--r-- 296k root 19 Sep  2025  config-6.14.0-33-generic
drwxr-xr-x    - root  1 Jan  1970  efi
drwxr-xr-x    - root  6 Nov  2025  grub
lrwxrwxrwx    - root  6 Nov  2025  initrd.img -> initrd.img-6.14.0-33-generic
.rw-r--r--  62M root 20 Feb 01:52  initrd.img-6.14.0-33-generic
lrwxrwxrwx    - root  6 Nov  2025  initrd.img.old -> initrd.img-6.14.0-33-generic
.rw-r--r-- 143k root  9 Apr  2024  memtest86+ia32.bin
.rw-r--r-- 144k root  9 Apr  2024  memtest86+ia32.efi
.rw-r--r-- 148k root  9 Apr  2024  memtest86+x64.bin
.rw-r--r-- 149k root  9 Apr  2024  memtest86+x64.efi
.rw------- 9.1M root 19 Sep  2025  System.map-6.14.0-33-generic
lrwxrwxrwx    - root  6 Nov  2025 󰡯 vmlinuz -> vmlinuz-6.14.0-33-generic
.rw-------  16M root 19 Sep  2025  vmlinuz-6.14.0-33-generic
lrwxrwxrwx    - root  6 Nov  2025  vmlinuz.old -> vmlinuz-6.14.0-33-generic

$ hciconfig ; lsusb 
hci0:   Type: Primary  Bus: USB
    BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
    DOWN 
    RX bytes:0 acl:0 sco:0 events:0 errors:0
    TX bytes:61 acl:0 sco:0 commands:1 errors:0

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 214b:7250 Huasheng Electronics USB2.0 HUB
Bus 001 Device 003: ID 046d:091c Logitech, Inc. 罗技高清网络摄像机 C930n
Bus 001 Device 004: ID 05e3:0751 Genesys Logic, Inc. microSD Card Reader
Bus 001 Device 005: ID 056a:0374 Wacom Co., Ltd CTL-4100 [Intuos (S)]
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 413c:1010 Dell Computer Corp. USB 2.0 Hub [MTT]
Bus 003 Device 003: ID 0e8d:0717 MediaTek Inc. Wireless_Device
Bus 003 Device 004: ID 413c:2110 Dell Computer Corp. Dell Wired Multimedia Keyboard
Bus 003 Device 005: ID 26ce:0a08 Generic USB Audio
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
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 002: ID 275d:0ba6  USB OPTICAL MOUSE 
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 011 Device 002: ID 26ce:01a2 ASRock LED Controller

I was not able to make the pointer moving and opted to reinstall my focal fossa. After installation I added another language, and added this another language to the input languages. Then found I can’t type @ anymore, nor I could find it. I changed UK English to US English. I was asked to authenticate and log out. After logging out I could not log in. Another language was/is in the upper right corner, I can’t change for English I am not logged in. I am running live usb now. I am frustrated. Do I need install again? Is there a safe and simple way to solve the trouble by running live usb? Or is it another bug? And do I still need to reinstall focal fossa? Or do I need to install other release? The machine is Asus Vivobook.

hipcc -O3 -Wall -c -fmessage-length=0 -MMD -MP -MF"MyClass_test.d" -MT"MyClass_test.o" -o "MyClass_test.o" "../MyClass_test.cpp"
Finished building: ../MyClass_test.cpp
Building target: Experiment
Invoking: GCC C++ Linker
hipcc -L/opt/rocm/include -L/etc/alternatives/rocm/lib -L/opt/rocm/lib -o "Experiment" ./MyClass.o ./MyClass_test.o -llibrocm_smi64
ld.lld: error: unable to find library -llibrocm_smi64
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
failed to execute:/opt/rocm-7.2.0/lib/llvm/bin/clang++ --driver-mode=g++ -O3 --hip-link  -L/opt/rocm/include -L/etc/alternatives/rocm/lib -L/opt/rocm/lib -o "Experiment" ./MyClass.o ./MyClass_test.o -llibrocm_smi64
make: \*\*\* \[makefile:67: Experiment\] Error 1
"make all" terminated with exit code 2. Build might be incomplete.

"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.

Edit 1, Edit 2, etc, are my responses to @heynnema's heroic efforts to find the solution for me. Our exchange (including help from @nobody) was moved by a moderator from Comments to Chat.

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 Edits, please see the Chat

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

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

Edit 6

Synaptic search for "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:~$ 

Edit 8

sudo apt purge virtualbox-7.2 Appears to remove 7.0, then says, "Package virtualbox-7.2 which provides virtualbox is not installed" ! Did I use the wrong command?

@heynnema: "Install virtualbox-source and virtualbox-modules using Synaptic"

Synaptic shows virtualbox-source but no virtualbox-modules.

Install via Synaptic of virtualbox-source:

E: virtualbox-dkms: installed virtualbox-dkms package post-installation script subprocess returned error exit status 10

But Synaptic does show virtualbox-source as installed.

In the description of virtualbox-source: "The source is placed under /usr/src, and after decompression it can be built to produce a virtualbox-modules-KVERS providing "virtualbox-modules" package." So I shall proceed with the source install...

After install, there is /usr/src/virtualbox.tar.bz2.

Extracting that creates /usr/src/modules/virtualbox/, which contains:

alan@AM5:/usr/src$ ll modules/virtualbox/
total 52
drwxr-xr-x 12 root root 4096 Sep  2  2024 ./
drwxr-xr-x  3 root root 4096 Sep  2  2024 ../
drwxr-xr-x 10 root root 4096 Sep  2  2024 common/
drwxr-xr-x  2 root root 4096 Sep  2  2024 debian/
drwxr-xr-x  2 root root 4096 Sep  2  2024 generic/
drwxr-xr-x  5 root root 4096 Sep  2  2024 include/
-rw-r--r--  1 root root   56 Aug 25  2023 Makefile
drwxr-xr-x  3 root root 4096 Sep  2  2024 math/
drwxr-xr-x  4 root root 4096 Sep  2  2024 r0drv/
drwxr-xr-x  2 root root 4096 Sep  2  2024 VBox/
drwxr-xr-x  3 root root 4096 Sep  2  2024 vboxdrv/
drwxr-xr-x  3 root root 4096 Sep  2  2024 vboxnetadp/
drwxr-xr-x  3 root root 4096 Sep  2  2024 vboxnetflt/
alan@AM5:/usr/src$ 

Edit 9

alan@AM5:/usr/src$ dkms status
virtualbox/7.0.16: added
alan@AM5:/usr/src$

alan@AM5:/usr/src$ sudo dkms build virtualbox/7.0.16
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! 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:/usr/src$ 

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

At one point, it had me run the following for "quick diagnostics":

sudo blkid | grep nvme0n1p7
cat /mnt/root/etc/fstab | grep nvme0n1p7
sudo mount /dev/nvme0n1p7 /mnt/root
journalctl -xb | grep -i "nvme0n1p7\|1785c362\|fsck\|mount"

The output was very long, so I'll give you Perplexity's evaluation of the output:

Key findings from your output​

✅ UUID perfect: /dev/nvme0n1p7 has correct UUID 1785c362-92ff-4a9a-b254-f950db82ad8c
✅ Filesystem mounts fine: Kernel successfully mounted it read-only earlier
❌ Mount point missing: You ran cat and mount without creating /mnt/root first
❌ No /etc/fstab access: Because /mnt/root wasn't mounted when you checked
⚠️ os-prober found your Ubuntu: 40lsb detected /dev/nvme0n1p7:Ubuntu 24.04.3 LTS

A couple more failed fixes/boots back to the BusyBox later, it had me do more diagnostics. Here is the output from that:

ubuntu@ubuntu:~$ # 1. Test if root mounts read-write now
sudo mkdir -p /mnt/test
sudo mount /dev/nvme0n1p7 /mnt/test
mount | grep nvme0n1p7
sudo umount /mnt/test

# 2. Check filesystem health
sudo fsck -n /dev/nvme0n1p7

# 3. Verify GRUB kernel line
sudo mount /dev/nvme0n1p7 /mnt/root
grep "root=" /mnt/root/boot/grub/grub.cfg

# 4. Boot parameter check
sudo mount /dev/nvme0n1p1 /mnt/efi
ls -la /mnt/efi/EFI/ubuntu/
/dev/nvme0n1p7 on /mnt/test type ext4 (rw,relatime)
fsck from util-linux 2.39.3
e2fsck 1.47.0 (5-Feb-2023)
/dev/nvme0n1p7: clean, 528537/32210944 files, 19131061/128843776 blocks
mount: /mnt/root: mount point does not exist.
       dmesg(1) may have more information after failed mount system call.
grep: /mnt/root/boot/grub/grub.cfg: No such file or directory
mount: /mnt/efi: mount point does not exist.
       dmesg(1) may have more information after failed mount system call.
ls: cannot access '/mnt/efi/EFI/ubuntu/': No such file or directory

...to which it said:

Key takeaways from output

✅ /dev/nvme0n1p7 mounts read-write perfectly (rw,relatime) ✅ Filesystem clean (no fsck errors) ❌ Missing /mnt/root, /mnt/efi directories ❌ No /mnt/efi/EFI/ubuntu/ = GRUB EFI files missing (main problem!)

I ran its next code to "Fix the mount directory issues + reinstall GRUB EFI". Output:

ubuntu@ubuntu:~$ # Create missing directories
sudo mkdir -p /mnt/root /mnt/efi

# Remount with proper structure
sudo mount /dev/nvme0n1p7 /mnt/root
sudo mount /dev/nvme0n1p1 /mnt/efi

# Verify GRUB files NOW exist
ls -la /mnt/efi/EFI/ubuntu/
grep "root=" /mnt/root/boot/grub/grub.cfg
total 4390
drwxr-xr-x 2 root root    2048 Mar 30  2025 .
drwxr-xr-x 6 root root    2048 Aug  2 23:20 ..
-rwxr-xr-x 1 root root     108 Jan 31 16:05 BOOTX64.CSV
-rwxr-xr-x 1 root root     117 Jan 31 16:05 grub.cfg
-rwxr-xr-x 1 root root 2660232 Jan 31 16:05 grubx64.efi
-rwxr-xr-x 1 root root  856280 Jan 31 16:05 mmx64.efi
-rwxr-xr-x 1 root root  966664 Jan 31 16:05 shimx64.efi
grep: /mnt/root/boot/grub/grub.cfg: Permission denied

...to which it said "Excellent—GRUB EFI files are present and recent (Jan 31 timestamps), but Permission denied on grub.cfg needs fixing."

So I ran its next code for "Quick permission fix + final verification".

Output:

ubuntu@ubuntu:~$ # Fix grub.cfg permission (live USB -> root filesystem mismatch)
sudo mount -o remount,remount,rw /mnt/root
sudo chmod 644 /mnt/root/boot/grub/grub.cfg
sudo grep "root=" /mnt/root/boot/grub/grub.cfg

# Check what root= parameter GRUB passes to kernel
cat /mnt/root/boot/grub/grub.cfg | grep "linux.*root=" -A 5
    linux   /boot/vmlinuz-6.14.0-36-generic root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c ro  quiet splash $vt_handoff
        linux   /boot/vmlinuz-6.14.0-36-generic root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c ro  quiet splash $vt_handoff
        linux   /boot/vmlinuz-6.14.0-36-generic root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c ro recovery nomodeset dis_ucode_ldr 
        linux   /boot/vmlinuz-6.14.0-35-generic root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c ro  quiet splash $vt_handoff
        linux   /boot/vmlinuz-6.14.0-35-generic root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c ro recovery nomodeset dis_ucode_ldr 
        linux   /boot/vmlinuz-6.14.0-34-generic root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c ro  quiet splash $vt_handoff
        linux   /boot/vmlinuz-6.14.0-34-generic root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c ro recovery nomodeset dis_ucode_ldr 
    linux   /boot/vmlinuz-6.14.0-36-generic root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c ro  quiet splash $vt_handoff
    initrd  /boot/initrd.img-6.14.0-36-generic
}
submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-1785c362-92ff-4a9a-b254-f950db82ad8c' {
    menuentry 'Ubuntu, with Linux 6.14.0-36-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.14.0-36-generic-advanced-1785c362-92ff-4a9a-b254-f950db82ad8c' {
        recordfail
--
        linux   /boot/vmlinuz-6.14.0-36-generic root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c ro  quiet splash $vt_handoff
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-6.14.0-36-generic
    }
    menuentry 'Ubuntu, with Linux 6.14.0-36-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.14.0-36-generic-recovery-1785c362-92ff-4a9a-b254-f950db82ad8c' {
        recordfail
--
        linux   /boot/vmlinuz-6.14.0-36-generic root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c ro recovery nomodeset dis_ucode_ldr 
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-6.14.0-36-generic
    }
    menuentry 'Ubuntu, with Linux 6.14.0-35-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.14.0-35-generic-advanced-1785c362-92ff-4a9a-b254-f950db82ad8c' {
        recordfail
--
        linux   /boot/vmlinuz-6.14.0-35-generic root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c ro  quiet splash $vt_handoff
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-6.14.0-35-generic
    }
    menuentry 'Ubuntu, with Linux 6.14.0-35-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.14.0-35-generic-recovery-1785c362-92ff-4a9a-b254-f950db82ad8c' {
        recordfail
--
        linux   /boot/vmlinuz-6.14.0-35-generic root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c ro recovery nomodeset dis_ucode_ldr 
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-6.14.0-35-generic
    }
    menuentry 'Ubuntu, with Linux 6.14.0-34-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.14.0-34-generic-advanced-1785c362-92ff-4a9a-b254-f950db82ad8c' {
        recordfail
--
        linux   /boot/vmlinuz-6.14.0-34-generic root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c ro  quiet splash $vt_handoff
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-6.14.0-34-generic
    }
    menuentry 'Ubuntu, with Linux 6.14.0-34-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.14.0-34-generic-recovery-1785c362-92ff-4a9a-b254-f950db82ad8c' {
        recordfail
--
        linux   /boot/vmlinuz-6.14.0-34-generic root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c ro recovery nomodeset dis_ucode_ldr 
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-6.14.0-34-generic
    }
}

...to which it responded: "PERFECT—your GRUB config is 100% correct. Every root=UUID=1785c362-92ff-4a9a-b254-f950db82ad8c matches your fstab exactly.​

GRUB hands the kernel the right parameters. The problem is initramfs itself failing to mount root."

It then sent me down this wasted rabbithole of "Since everything else checks out, increase initramfs root delay + force regeneration".

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

Edit 5: As requested from BusyBox window:

(initramfs) ls /sys/module/nvme
ls: /sys/module/nvme: No such file or directory

Is it possible to switch between workspaces using Super+number?

I am on Ubuntu 22.04 and Super+number launch (or switch to an existing) application based on the application bar. I know it's possible to switch to a workspace using Super+PageDown but it takes too long when I have more than 3 workspaces. I don't mind a different hotkeys but that's what I used to because I was previously using i3, a tiled window manager. I find Gnome very good overall since I don't need to tweak basic things like bluetooth, volume, and brightness keys but managing windows can be a bit more efficient in my opinion.

Update: this bug persist on ubuntu 24.04.

Update: I didn't solve this but I found a fantastic workaround. I am using a Window Manager called https://regolith-desktop.com/ which uses i3 under the hood. I highly recommend it for people who loves i3 but also like the nice things Gnome offers. I now have workspaces and window + number jumps to the right workspace. Window+shift+number moves an application into that workspace, and Window+enter opens a new terminal. Life is good!

Thanks!

Similar to this issue ubuntu-20-04-boots-to-black-screen-with-flashing-cursor Ubuntu 22.04 also boots to a black screen, however the linked solution doesn't appear to fix the issue for this version.

I have a laptop running Ubuntu 22.04.1 with the following specifications:

   CPU: Intel i7-7700HQ
   GPU: NVIDIA GeForce GTX 1060 Mobile (with nvidia-driver-525)
   RAM: 16GB
   Kernel: 5.15.0-60-generic
   DE: GNOME
   WM: Mutter
   Display server: Xorg

All packages have been updated to latest available versions as of 2023/02/13. Occasionally, when I unlock the system from a suspend or screen lock, the desktop icons are displayed over all opened windows, and I am unable to select any open window until I manually Alt+Tab through them.

What could be the cause of this issue? Any troubleshooting assistance would be highly welcome. I have not found a method of consistently reproducing this problem.

I have attached a screenshot of an open Firefox window after waking up from suspend.

Context:

I have to run a virtual machine with VMWare Player (version 16) on an Ubuntu server (version 18.04) without being able to run the GUI (the server has no display). The virtual machine has already been created, I just need to import the .ovf file and power it on. I read on several posts that the best way is to use an utility called vmrun. The problem is that it is not installed together with VMWare, or at least it is not with the installation I did (if it can help, I used this guide, it's in italian but the commands should be easily understandable).

So, I tried to install vmrun it in several ways (for example by following the instructions in this thread), but I wasn't able to do it. Moreover, every article/guide that I find seems pretty outdated. I even tried to install the VIX API, but I wasn't able to do that either (and, even if I could, I wouldn't know how to use it).

Question:

Is there a way to install a version of VWMare Player that includes vmrun? If yes, how? If no, how can I install vmrun separately?

I am trying to migrate from Windows to Linux, hibernated Windows and installed a fresh new Ubuntu 20.04 on a new disk (LUKS with increased swap size for hibernation). but I get sporadic screen corruption or weird visual artifacts:

Random artifacts 1:

Random artifacts 2:

Sometimes no artifacts:

How can I solve it?

System configuration

• Dell Precision 15" 7540, Xeon E-2286M@2.4GHz, 128 GB ECC RAM, NVIDIA Quadro RTX 5000 16GB VRAM

• Dockingstations at Home and offices: WD19DC (240W)

• Monitors used for Linux migration: 2x 4K U4320Q, 42.5" @ 96dpi font / No scaling

• There are no problems/artifacts with the graphics card in windows (three month uptime
  until a planned restart): In this time following things have been done: Changing daily monitor layout (working at Home2x4k 42"/Office1 2x38"/Office2 3xFullHD 24"), performing daily sleep/resume cycles, some hibernation cycle in case charging is not possible during traveling

Ubuntu 20.04 LTS:

• Artifacts occur after start, reboot, resume from sleep and hibernate

• Artifacts occur rectangular on random locations.

• Sometimes a monitor blanks out for one second without any reasons (hard to reproduce)

• The NVIDA driver 460 version which gets auto-installed by Ubuntu causes artifacts

• I freshly installed again Ubuntu and installed a driver which is currently offered as download on nvidia.com (see below)

• The artifacts occur with GNome and KDE, too. Artfacts starts as soon as I start a terminal window.

• In KDE: I tried kwin --replace& but problem remains

• In KDE: When I press alt tab for switch apps, then artifacts disappear, When I take a screenshot, the image itself has no artifacts.

Last installed versions:

• Kernel: user01@earth2:~$ uname -a Linux earth2 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
• KDE Version:
• user01@earth2:~$ kf5-config --version Qt: 5.12.8 KDE Frameworks: 5.68.0 kf5-config: 1.0
• NVIDIA:

#NVIDIA-Linux-x86_64-450.102.04.run
user01@earth2:~$ nvidia-smi 
Sun Feb  7 18:18:18 2021       
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 450.102.04   Driver Version: 450.102.04   CUDA Version: 11.0     |
|-------------------------------+----------------------+----------------------+
| 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  Quadro RTX 5000     Off  | 00000000:01:00.0 Off |                  N/A |
| N/A   47C    P0    31W /  N/A |   1227MiB / 16091MiB |      2%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

• lspci

user01@earth2:~/Downloads$ lspci
00:00.0 Host bridge: Intel Corporation Device 3e20 (rev 0d)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 0d)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0d)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #0 (rev 10)
00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #1 (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Cannon Lake Mobile PCH SATA AHCI Controller (rev 10)
00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (rev f0)
00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0)
00:1c.5 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #6 (rev f0)
00:1c.6 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #7 (rev f0)
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-LM (rev 10)
01:00.0 VGA compatible controller: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] (rev a1)
01:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1)
01:00.2 USB controller: NVIDIA Corporation TU104 USB 3.1 Host Controller (rev a1)
01:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU104 USB Type-C UCSI Controller (rev a1)
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
03:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
04:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
04:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
04:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
04:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06)
05:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] (rev 06)
39:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] (rev 06)
6e:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card Reader (rev 01)
6f:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
70:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983

user01@earth2:~/Downloads$ free -h
              total        used        free      shared  buff/cache   available
Mem:          125Gi       3,5Gi       118Gi       584Mi       3,6Gi       120Gi
Swap:         405Gi          0B       405Gi
user01@earth2:~/Downloads$

At boot up, I get a pop up message stating, Authentication Required, The login keyring did not get unlocked when you logged into your computer. Below this message there is a an area for the authorized password. I want to resolve this issue. Here is some general information that may be of importance: I have opted to have automatic login in settings. This is a relatively recent installation of Focal Fossa. I have created both administrator and user accounts.

I have a custom-built workstation (from early 2018) with NVIDIA GeForce GTX 1080 Ti. It's connected to one screen and a few USB devices.

It came with Ubuntu 16.04 preinstalled. The kernel I'm using is 4.15.0-66-generic. If I remember correctly I was using NVIDIA driver version 390 before; I've updated it to 440.26 since this problem started.

The setup was working fine until I recently updated to Ubuntu 18.04, and now it just hangs every time I boot. After the splash screen (ubuntu with 5 dots), it gets stuck with a bunch of log text (all "OK") blinking, with the last line:

 [ OK ] Started GNOME Display Manager.aemon.ring daemon.rnel crash signatures.

(the part after "Display Manager" seems to be some garbled text from previous lines.)

The boot gets stuck with this screen blinking

What I've tried:

• Purging and reinstalling the NVIDIA driver. I did apt-get remove --purge nvidia-* then add-apt-repository ppa:graphics-drivers/ppa and apt-get update, ubuntu-drivers autoinstall. What I have now, nvidia-440, is the recommended version for my GPU according to ubuntu-drivers devices.
• Purging and reinstalling xorg-* xserver-xorg.
• Enabling DRM mode setting. I added nvidia-drm.modeset=1 to the line GRUB_CMDLINE_LINUX_DEFAULT in my /etc/default/grub and did update-grub. I've also tried nomodeset, to no avail.
• Using lightdm instead of gdm3, with dpkg-reconfigure lightdm. When I reboot after this, the boot doesn't hang and I can reach the login screen, but then I get stuck in a login loop; permission settings of .Xauthority were fine, so I don't know what's wrong. (xdm gave me the same problem)
• Checking /etc/X11/xorg.conf. I initially didn't have one; creating one with nvidia-xconfig made no difference.
• Selecting a previous kernel 4.15.0-65-generic.

I still cannot boot or log in successfully.

My problem appears to be similar to gdm3 display manager hangs after booting with Ubuntu 18.10; however, I cannot disable my NVIDIA GPU because I need to use it for work (also, unlike that post lightdm doesn't work for me, as stated above). I also need the GUI for work.

This machine is indispensable to my work and I really need to fix this problem as soon as possible, but I am still quite inexperienced with Ubuntu and am at a loss what to do. Any help would be greatly appreciated.

First: I have tried for MANY hours and numerous fixes to try to get this to work. So I am sorry that this is filled with questions that have been asked multiple times. Second: I am not very good with linux, so please excuse my ignorance

• I could not get an external monitor to be recognized, so I installed nvidia driver 390 as it was recommended
• Monitor still was not recognized, so I opened x server and it looked like this:

• one of the fixes for xserver was to purge Nvidia drivers and reinstall (390 again), so I did.
• now my system is booting to a black screen, and only works in recovery mode
• I tried newer drivers, including one downloaded directly from Nvidia (418 I believe), that installation failed. So I downloaded it through the terminal. Still black screen
• Secure Boot is disabled in the BIOS.
• My system is set up for dual boot on two separate SSDs.
• Ever since upgrading to 18.04 my computer will not shut down properly or reboot. It gets to the end of the process and never powers off. I wiped the drive and did a fresh install of Ubuntu, but still isn't working (apparently this can be an issue stemming from the graphics card driver as well). This I can live with, however I can't live with black screens.

More screenshots:

Results of ubuntu-drivers devices:

Results of ubuntu-drivers devices:

lshw -numeric -C display:
  *-display UNCLAIMED       
       description: VGA compatible controller
       product: GP107M [GeForce GTX 1050 Ti Mobile] [10DE:1C8C]
       vendor: NVIDIA Corporation [10DE]
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list
       configuration: latency=0
       resources: memory:de000000-deffffff memory:c0000000-cfffffff memory:d0000000-d1ffffff ioport:e000(size=128) memory:df000000-df07ffff
  *-display UNCLAIMED
       description: VGA compatible controller
       product: Intel Corporation [8086:591B]
       vendor: Intel Corporation [8086]
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 04
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list
       configuration: latency=0
       resources: memory:dd000000-ddffffff memory:b0000000-bfffffff ioport:f000(size=64) memory:c0000-dffff

Results of lshw -numeric -C display:

More stuff:

chris:~$ nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

I tried switching prime select to intel and back, but it didn't work.
The kernel is up–to–date.

I have freshly installed ubuntu 18.04.1 LTS. My usb wifi adapter which works perfetcly fine in windows 10 in the same system (dual boot), is not recognized here. the chip of the adapter is a Realtek 8811AU/8812AU.

I have gone through various posts here to identify but could not find anything to work. By going through different posts, i am providing the o/p of some commands before hand only.

$ lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth           Dongle (HCI mode)
Bus 001 Device 007: ID 0bda:a811 Realtek Semiconductor Corp. 
Bus 001 Device 006: ID 18d1:4ee3 Google Inc. Nexus 4 (tether)
Bus 001 Device 005: ID 1b1c:1b37 Corsair 
Bus 001 Device 003: ID 046d:0a4d Logitech, Inc. G430 Surround Sound Gaming  Headset
Bus 001 Device 002: ID 046d:c246 Logitech, Inc. Gaming Mouse G300
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ sudo lshw -C network

*-network                 
   description: Ethernet interface
   product: Ethernet Connection (2) I219-V
   vendor: Intel Corporation
   physical id: 1f.6
   bus info: pci@0000:00:1f.6
   logical name: enp0s31f6
   version: 31
   serial: 40:8d:5c:ed:9f:2f
   capacity: 1Gbit/s
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k firmware=0.8-4 latency=0 link=no multicast=yes port=twisted pair
   resources: irq:123 memory:df100000-df11ffff
*-network
   description: Ethernet interface
   physical id: 2
   logical name: enp0s20f0u6
   serial: ae:42:24:15:38:31
   capabilities: ethernet physica
   configuration: broadcast=yes driver=rndis_host driverversion=22-Aug-2005 firmware=RNDIS device ip=192.168.42.168 link=yes multicast=yes

lspci -knn | grep Net -A3; rfkill list
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

Here is the output of the wireless info script: http://paste.ubuntu.com/p/ZPhd97zK5X/

I have read-only usb drive and could not fix it. I have read some articles about it and tried to fix but I couldn't.

I unmounted drive and used dosfsck to check and repair MS-DOS filesystems, because it is FAT filesystem and run:

dosfsck -a /dev/sdb1

it gave the output:

fsck.fat 4.1 (2017-01-24) open: Read-only file system

So what can I do with it? Can I repair or it's time to throw it in a trash?

Because of a hardware failure my motherboard has just been replaced. After the replacement, my system (Ubuntu 17.10) doesn't boot:

ALERT! UUID=dd84f4b3-d5bf-42e4-9b5e-ec685a461fad does not exist. Dropping to a shell.

I've used a Live USB Ubuntu to debug this problem. Here are some results:

/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/nvme0n1p3 during installation
UUID=dd84f4b3-d5bf-42e4-9b5e-ec685a461fad /               ext4    errors=remount-ro 0       1

# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=B38D-559B  /boot/efi       vfat    umask=0077      0       1
# swap was on /dev/nvme0n1p4 during installation
UUID=f4134c38-10b9-478f-b550-54650a9f5140 none            swap    sw              0       0

blkid

/dev/nvme0n1p1: SEC_TYPE="msdos" UUID="B38D-559B" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="98be6c97-c354-49a6-a432-9201d56a421b"
/dev/nvme0n1p2: LABEL="OS" UUID="B39E-7035" TYPE="vfat" PARTLABEL="fat32" PARTUUID="d3006358-8d82-4e0b-99f8-87a5261cf7e8"
/dev/nvme0n1p3: LABEL="UBUNTU" UUID="dd84f4b3-d5bf-42e4-9b5e-ec685a461fad" TYPE="ext4" PARTUUID="24e5b96d-f20c-43dd-9e48-672760b0e6f7"
/dev/sda1: LABEL="UBUNTU 17_1" UUID="88D4-322D" TYPE="vfat" PARTUUID="3d0a270b-01"

fdisk -l

Disk /dev/loop0: 1.3 GiB, 1427259392 bytes, 2787616 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/nvme0n1: 477 GiB, 512110190592 bytes, 1000215216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 43E35EBE-2A73-404A-9D4A-851815F33F9A

Device             Start        End   Sectors   Size Type
/dev/nvme0n1p1        34     488281    488248 238.4M EFI System
/dev/nvme0n1p2    488282    5934980   5446699   2.6G Microsoft basic data
/dev/nvme0n1p3   5935104  933576703 927641600 442.3G Linux filesystem
/dev/nvme0n1p4 933576704 1000214527  66637824  31.8G Linux swap


Disk /dev/sda: 28.7 GiB, 30752636928 bytes, 60063744 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x3d0a270b

Device     Boot Start      End  Sectors  Size Id Type
/dev/sda1  *     2048 60063743 60061696 28.7G  c W95 FAT32 (LBA)

It looks like the UUID's in fstab are correct, but I still get that error message.

How can I repair my Ubuntu installation?

I've tried the given solution in ALERT! /dev/disk/by-uuid/xxxxxxxxx does not exist. Dropping to a shell, but unfortunately that didn't help (I mounted /dev/nvme0n1p3). Still the same problem.

Update: When I select UEFI boot mode in system setup, I still get this problem. But when I select legacy boot I got 'no boot device found'. But here comes the tricky part: when I select legacy mode and use F12 to select UEFI/Ubuntu, it starts without a problem.

I'm trying to edit a text file in terminal using the nano command however when I do it and specify the correct location it shows nothing. If I go and open the actual text file then all the content is in there.

I have just installed Xubuntu 17.10, and I have noticed that grub did not detect my previous Manjaro installation (which is still intact in another partition, I checked).

How do I get grub to add Manjaro as booting option? Please provide easy-to-follow instructions, as I am a newbie.

Thanks

EDIT 1: I have already tried using sudo update-grub and sudo update-grub2, rebooting after using each one, and it made no difference at all. Moreover, I want to point out that at boot time I do not see the grub menu -- the screen is blank for a few seconds, and then Xubuntu boots normally.

Edit 2: I don't know if this matters, but the filesystem of my Manjaro OS partition is btrfs

My firefox refuses to launch even after a clean re-install. This happens with the taskbar shortcut as well as when launching through terminal sensible-browser.

It just gives me this Mozilla Crash Reporter Terminal Error alongside Crash Reporter

Any ideas?

PS Ubuntu is running on Raspberry Pi 3 and was confirmed working a few days ago

I know that I'm using the proxy(tor) by the precise return of this command:

sudo proxychains sh -c 'apt update'

However, when I do this in 2 steps, the command's return isn't as precise as before: proxychains xfce4-terminal Wait for the terminal window to appear, then enter:

sudo apt update

Why? Plus, if I uninstall tor the 2 steps method still works; it shouldn't !

I have created my 1st Virtual Box machine after turning on Virtualization in my BIOS and it went immediately down because I did not have a Windows 7 boot image set for it to boot from. I have 3 original Win 7 Installation disks so I need to know how to put 1 on a flash as an ISO and be able to feed the data to the virtual machine that I want to run.

Alternatively, there are many referenced for virtual Linux machines, how do I get one and make it work?

My desire is to create my first working VM. From here I go to try more powerful VM stuff from the real world. Will do heavy collaboration with experienced persons, I am a Linux advanced newbie with heavy experience in hdwe and software. Running 32GB server on AMD Phenom II 6 core with 3 laptop/workstations. SSDs, SSHDs and HDs total storage over 20TB.

Thanks DL

I use notepad++ from Wine.

I want to set Notepad++ as one of the default editors. I tried to set it by right-clicking on a file, then Open With. But I did not see Notepad++ in the resulting list (even after clicking on Choose Other Programs).

This is definitely NOT a duplicate. The "possible duplicate" I even said I tried in the original question. As for anything else, well, 16 comments and 1 answer that didn't work. It's clearly not a generic or common solution as the other questions like mine.

     ian@ian:~$ sudo apt-get install skype
    [sudo] password for ian: 
    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:
     skype : Depends: skype-bin
    E: Unable to correct problems, you have held broken packages.`

I've tried every solution for every question similar to "you have held broken packages," including those in How do I resolve unmet dependencies after adding a PPA?. I've purged every ppa, and I've no idea what to try now. apt-mark showhold gave no output. My sources.list is below. Thanks for any help.

# deb cdrom:[Ubuntu 14.04 LTS _Trusty Tahr_ - Release amd64 (20140417)]/ trusty main restricted

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://us.archive.ubuntu.com/ubuntu/ trusty main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ trusty main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://us.archive.ubuntu.com/ubuntu/ trusty-updates main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ trusty-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ trusty universe
deb-src http://us.archive.ubuntu.com/ubuntu/ trusty universe
deb http://us.archive.ubuntu.com/ubuntu/ trusty-updates universe
deb-src http://us.archive.ubuntu.com/ubuntu/ trusty-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
## team, and may not be under a free licence. Please satisfy yourself as to 
## your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://us.archive.ubuntu.com/ubuntu/ trusty multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ trusty multiverse
deb http://us.archive.ubuntu.com/ubuntu/ trusty-updates multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ trusty-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ trusty-backports main restricted universe multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ trusty-backports main restricted universe multiverse

deb http://security.ubuntu.com/ubuntu trusty-security main restricted
deb-src http://security.ubuntu.com/ubuntu trusty-security main restricted
deb http://security.ubuntu.com/ubuntu trusty-security universe
deb-src http://security.ubuntu.com/ubuntu trusty-security universe
deb http://security.ubuntu.com/ubuntu trusty-security multiverse
deb-src http://security.ubuntu.com/ubuntu trusty-security multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
deb http://archive.canonical.com/ubuntu trusty partner
# deb-src http://archive.canonical.com/ubuntu trusty partner

## This software is not part of Ubuntu, but is offered by third-party
## developers who want to ship their latest software.
deb http://extras.ubuntu.com/ubuntu trusty main
# deb-src http://extras.ubuntu.com/ubuntu trusty main

After entering sudo apt-get install skype-bin skype libqtwebkit4 libqtgui4, I got this:

ian@ian:~$ sudo apt-get install skype-bin skype libqtwebkit4 libqtgui4 libqtgui4:i386 libqtwebkit4:i386 libtiff5:i386 libjbig0:i386
Reading package lists... Done
Building dependency tree       
Reading state information... Done
libqtgui4 is already the newest version.
libqtwebkit4 is already the newest version.
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:
 libjbig0 : Breaks: libjbig0:i386 (!= 2.0-2+deb7u1) but 2.0-2ubuntu4.1 is to be installed
 libjbig0:i386 : Breaks: libjbig0 (!= 2.0-2ubuntu4.1) but 2.0-2+deb7u1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

We all know that SSDs have a limited predetermined life span. So the question for me is how do I check in (Ubuntu) Linux what the current health status of my SSD is? And maybe an estimation how long it will take?

Graphical tool is preferred, but command line tool would also be fine.

I'm using Xubuntu 12.04 LTS

I added some extra repositories with the Software Sources program. But when I reload the package database, I get an error like the following:

W: GPG error: http://ppa.launchpad.net trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8BAF9A6F

I know I can fix it using apt-key in a terminal, according to the official Ubuntu documentation. But I would have liked to do it graphically. Is there a way to do this without using a terminal?