I am on Ubuntu 24.04 LTS.

I am using xrandr's brightness switch to invert the colors on my screens, which makes extended work on my computer much easier on my eyes:

$ xrandr --output eDP --brightness -1.0

This generally works as intended. (I can revert it by setting the brightness to +1.0.)

However, for some reason I don't understand, when I invert the colors on some apps fonts render perfectly (Firefox, gnome-terminal) while in others they get garbled to the point of hardly being legible (Thunderbird, Libreoffice).

Here are two sample pictures, each of them showing the same app without color inversion and with color inversion:

The Thunderbird folder pane:

Libreoffice Writer (close-up of a word):

I thought anti-aliasing and/or hinting might be the problem, so I tried disabling them using dconf-editor. But the problem persists. I also disabled anti-aliasing in Libreoffice's options, but it also produced no improvement.

What is causing this and how can I fix the display of text by Thunderbird and Libreoffice when colors are inverted?

I am using RaspAP with default settings on a raspberry pi 5 with raspberry pi os bookworm

the only thing I changed in RaspAP is the name, password and country code, which I set to US (via RaspAP GUI)

I connected my ubuntu machine to it, and it connected perfectly.

I ran a ping google.com, and got no connection.

I pinged 8.8.8.8, and got a perfect connection

My phone connects to it perfectly, reporting no internet access, but when I go to google.com, it loads fine so I don't know what's up with that.

please tell me if you need any more info

I have a docker setup with Laravel Application that works fine on local Mac however, I am facing issues with the deployment on Ubuntu server 24.0.

1. All my paths are correct

2. All my volumes are mapped correctly

3. I checked the file location which exists

4. I have correctly pointed the root for NGINX i.e. both the NGINX and PHP-FPM has the same folder structure /var/www/api/public

5. User & Group ID matches the host OS i.e. 1000:1000 in all containers

6. Permissions:

   1. api: 755

   2. api/storage : 775

   3. api/bootstrap/cache: 775

Where could be the issue?

I have created a git repo for this setup here. The folder structure I have is:

Project Folder
|- docker-laravel
|- api

The log after running docker compose -f docker-compose.yml -f docker-compose.prod.yml logs php

I installed Ubuntu Budgie on my D drive with the drive containing windows 10 removed from the computer. I did not do any reconfiguration of the D drive (2.5 inch SATA) before installing Ubuntu. I followed the standard procedure of flashing Ubuntu on a thumb drive and tried it out on the thumb drive going back and forth between it and windows several times using the boot utility. Then I shutdown, removed the Kingston drive containing windows, booted off the Ubuntu thumb drive and installed Budgie on my D drive. The windows drive was not present during the install. Ubuntu booted fine after selecting the drive on boot up. I shutdown, reinstalled the windows Kingston drive and upon booting up with no changes to the bios it goes to a screen that looks like bios entry but has the spinning circle windows symbol. Ends up in screen saying automatic repair can’t repair your PC. Any suggestions on restoring Windows boot?

I am trying to find out what the user id requirements are for a new user. I am on 24.04.4 LTS, using user add command. What are the requirements for a new user id? I know it can't be more than 8 characters, but are there any other requirements? I suspect we are entering an invalid user id, but without knowing what the requirements are I don't know what part of the user id is not valid.

Thank you

Running Ubuntu 24.04 on a 16 GB Bosgame Ecolite mini-PC, all updates applied. One HDMI monitor, ethernet cable to modem/router, USB connections to mouse, keyboard, printer, and for powering speakers.

The system will run for hours, active or idling, after a boot with no issues. But then at some point a 100 MB/minute memory drain begins until the system locks up and requires a power reset to be restored.

The only user applications that are ever run are Firefox and LibreWriter, though this problem occurs whether they're being used or not. A Tailscale server is used to remotely manage this computer for my elderly mother.

Efforts to identify the cause included running scripts and logging their output to monitor memory use and change:

• One script utilizes ps -e -o pid,uss,pss,rss,vsz,comm=, along with free and free -h to monitor available memory. This executes on a ten second interval.

• A second script uses smemstat to monitor changes in individual processes' use of memory, plus or minus. This snapshots the changes in process memory use every two seconds.

Once the memory drain starts, it proceeds steadily at about 100 MB/minute until oom-killer is triggered. After that machine lock-up is imminent.

It's fairly easy to identify from the script logging when the memory loss starts, but there are no "smoking gun" entries corresponding to that interval in syslog or dmesg. Per ps, the memory associated with each process while this is occurring does not appreciably change (and is nowhere near the Gbs being consumed). Nor does smemstat note any corresponding memory changes.

Where else can I look? What else can I monitor?

Edited to add supplementary Information:

The system happily ran for about 9 months before this memory loss started happening.

Gnome-extensions has been known to cause memory problems. While gnome-extensions are installed, there are none active:

marc@MomsPC:~$ gnome-extensions list
marc@MomsPC:~$ 

One error that does show up a lot in syslog is:

2026-02-17T14:54:59.419070-06:00 MomsPC gnome-shell[2428]: message repeated 9 times: [ Failed to make thread 'KMS thread' realtime scheduled: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.RealtimeKit1" does not exist]

Though it doesn't appear to correlate with memory loss. And they go away if the rtkit daemon is restarted...at least until it again terminates for some unknown reason.

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

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.

I am incredibly new to Ubuntu so I know next to nothing about how it works. My issue is that after having my computer on for a bit the Wifi stops working and will will not connect to any other Wifi until after I restart my computer I have attempted to look online to try to find drivers but found nothing that works. I don't know what to do to fix this issue.

• Hardware model: HP HP ProBook 455 15.6 inch G9 Notebook PC
• Processor: AMD Ryzen™ 5 5625U with Radeon™ Graphics × 12
• Graphic: AMD Radeon™ Graphics
• Disk Capacity: 1.0 TB
• Firmware Version: U88 Ver. 01.20.00
• OS Type: 64-bit
• GNOME Version: 49
• Windowing System: Wayland
• Kernel Version: Linux 6.17.0-14-generic

This is what the terminal shows for my network controller:

02:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8852BE PCIe 802.11ax Wireless Network Controller [10ec:b852]
    Subsystem: Hewlett-Packard Company Device [103c:88e3]
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
    Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort+ <MAbort- >SERR- <PERR- INTx-
    Latency: 0
    Interrupt: pin A routed to IRQ 80
    IOMMU group: 11
    Region 0: I/O ports at 2000 [size=256]
    Region 2: Memory at fb500000 (64-bit, non-prefetchable) [size=1M]
    Capabilities: <access denied>
    Kernel driver in use: rtw89_8852be
    Kernel modules: rtw89_8852be

I have 5 machines running ubuntu 24.04. After upgrading some packages and rebooting, wakeonlan doesn't seem to work on any of my machines.

The machines are plugged in, and the ethernet port has lights blinking, so the network card should be awake.

I'm not sure whether the problems are due to upgrading packages or something else. I presume that this is a software problem that resulted from package upgrades changing a configuration file / variable somewhere.

Router is TP-Link AX3000. I rebooted and upgraded my router when trying to diagnose the issues, although I'm pretty confident the router is not an issue. Wake On Lan has worked before I upgraded the router firmware, and it has been working for at least a couple years prior to this week. However, there did seem to be an issue with receiving the magic packets when broadcasting to the local network (documented below). Not sure if this is a new issue, or is simply expected behavior.

I have tried to follow the guide here: https://wiki.archlinux.org/title/Wake-on-LAN. I'm out of ideas for what the problem is.

I can post additional files as necessary. Help is much appreciated!

Here is a sample from one of my machines:

The wakeonlan version I use is wakeonlan/noble,now 0.41-12.1 all [installed].

Ethernet should be nao3eth0.

sudo lshw -C network
  *-network                 
       description: Ethernet interface
       product: Ethernet Connection I217-LM
       vendor: Intel Corporation
       physical id: 19
       bus info: pci@0000:00:19.0
       logical name: nao3eth0
       version: 04
       serial: 34:17:eb:ce:b8:af
       size: 1Gbit/s
       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=6.8.0-100-generic duplex=full firmware=0.13-4 ip=192.168.237.103 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:28 memory:f7c00000-f7c1ffff memory:f7c3d000-f7c3dfff ioport:f080(size=32)

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: nao3eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 34:17:eb:ce:b8:af brd ff:ff:ff:ff:ff:ff
    altname eno1
    altname enp0s25
    inet 192.168.237.103/24 brd 192.168.237.255 scope global noprefixroute nao3eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::3617:ebff:fece:b8af/64 scope link 
       valid_lft forever preferred_lft forever

It appears wake on lan is enabled: Wake-on: g.

ethtool nao3eth0
Settings for nao3eth0:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Supported pause frame use: Symmetric Receive-only
    Supports auto-negotiation: Yes
    Supported FEC modes: Not reported
    Advertised link modes:  10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Full
    Advertised pause frame use: Symmetric Receive-only
    Advertised auto-negotiation: Yes
    Advertised FEC modes: Not reported
    Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                         100baseT/Half 100baseT/Full
                                         1000baseT/Full
    Link partner advertised pause frame use: Symmetric
    Link partner advertised auto-negotiation: Yes
    Link partner advertised FEC modes: Not reported
    Speed: 1000Mb/s
    Duplex: Full
    Auto-negotiation: on
    Port: Twisted Pair
    PHYAD: 1
    Transceiver: internal
    MDI-X: off (auto)
    Supports Wake-on: pumbg
    Wake-on: g
        Current message level: 0x00000007 (7)
                               drv probe link
    Link detected: yes

/etc/netplan# cat 00-config.yaml 
network:
  ethernets:
    nao3eth0:
      match:
        macaddress: 34:17:eb:ce:b8:af
      addresses:
       - 192.168.237.103/24
      routes:
       - to: default
         via: 192.168.237.1
      nameservers:
        addresses:
         - 192.168.237.1
      wakeonlan: true
  version: 2
  renderer: NetworkManager

ufw status
Status: inactive

tlp is not installed:

sudo systemctl status tlp.service
Unit tlp.service could not be found.
root@nao3:~# apt list tlp
Listing... Done
tlp/noble 1.6.1-1ubuntu1 all

sudo netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN      45445/smbd          
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1/init              
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN      45445/smbd          
tcp        0      0 0.0.0.0:631             0.0.0.0:*               LISTEN      45452/cupsd         
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      2426/master         
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      1133/systemd-resolv 
tcp        0      0 127.0.0.54:53           0.0.0.0:*               LISTEN      1133/systemd-resolv 
tcp6       0      0 :::139                  :::*                    LISTEN      45445/smbd          
tcp6       0      0 :::22                   :::*                    LISTEN      1/init              
tcp6       0      0 :::445                  :::*                    LISTEN      45445/smbd          
tcp6       0      0 :::631                  :::*                    LISTEN      45452/cupsd         
tcp6       0      0 :::7200                 :::*                    LISTEN      1663/java           
tcp6       0      0 ::1:25                  :::*                    LISTEN      2426/master         
tcp6       0      0 :::37705                :::*                    LISTEN      1663/java           
udp        0      0 127.0.0.54:53           0.0.0.0:*                           1133/systemd-resolv 
udp        0      0 127.0.0.53:53           0.0.0.0:*                           1133/systemd-resolv 
udp        0      0 192.168.237.255:137     0.0.0.0:*                           45438/nmbd          
udp        0      0 192.168.237.103:137     0.0.0.0:*                           45438/nmbd          
udp        0      0 0.0.0.0:137             0.0.0.0:*                           45438/nmbd          
udp        0      0 192.168.237.255:138     0.0.0.0:*                           45438/nmbd          
udp        0      0 192.168.237.103:138     0.0.0.0:*                           45438/nmbd          
udp        0      0 0.0.0.0:138             0.0.0.0:*                           45438/nmbd          
udp        0      0 0.0.0.0:37707           0.0.0.0:*                           45658/avahi-daemon: 
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           45658/avahi-daemon: 
udp6       0      0 :::48418                :::*                                45658/avahi-daemon: 
udp6       0      0 :::5353                 :::*                                45658/avahi-daemon: 

I can receive the magic packets with the machine address. The broadcast address seems to fail, which seems odd. Prior to the upgrade, wakeonlan 34:17:eb:ce:b8:af was sufficient to wakeonlan remotely. I believe this is a separate issue, because wakeonlan is not working whether I specify the ip_address or not.

SERVER:
tcpdump -i nao3eth0 -n -v -s0 udp port 9
tcpdump: listening on nao3eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
13:59:16.935287 IP (tos 0x0, ttl 64, id 65130, offset 0, flags [DF], proto UDP (17), length 130)
    192.168.237.104.55723 > 192.168.237.103.9: UDP, length 102


CLIENT MACHINE:

no packets received:
wakeonlan -i 255.255.255.255 -p 9 34:17:eb:ce:b8:af
Sending magic packet to 255.255.255.255:9 with 34:17:eb:ce:b8:af

packets are received as shown above:
wakeonlan -i 192.168.237.103 -p 9 34:17:eb:ce:b8:af
Sending magic packet to 192.168.237.103:9 with 34:17:eb:ce:b8:af

sysctl -a | grep rp_filter
net.ipv4.conf.all.arp_filter = 0
net.ipv4.conf.all.rp_filter = 2
net.ipv4.conf.default.arp_filter = 0
net.ipv4.conf.default.rp_filter = 2
net.ipv4.conf.lo.arp_filter = 0
net.ipv4.conf.lo.rp_filter = 0
net.ipv4.conf.nao3eth0.arp_filter = 0
net.ipv4.conf.nao3eth0.rp_filter = 2

I was unable to provide all the variables for sysctl since it went over the character limit. I can provide further information upon request.

I believe the problems started occurring after the upgrade on last Friday, 2026-02-13.

/var/log/apt/history.log:

cat history.log

Start-Date: 2026-02-03  06:54:35
Commandline: /usr/bin/unattended-upgrade
Upgrade: libc6:amd64 (2.39-0ubuntu8.6, 2.39-0ubuntu8.7), locales:amd64 (2.39-0ubuntu8.6, 2.39-0ubuntu8.7), libc-dev-bin:amd64 (2.39-0ubuntu8.6, 2.39-0ubuntu8.7), libc-bin:amd64 (2.39-0ubuntu8.6, 2.39-0ubuntu8.7), libc-devtools:amd64 (2.39-0ubuntu8.6, 2.39-0ubuntu8.7), libc6-dbg:amd64 (2.39-0ubuntu8.6, 2.39-0ubuntu8.7), libc6-dev:amd64 (2.39-0ubuntu8.6, 2.39-0ubuntu8.7)
End-Date: 2026-02-03  06:54:57

Start-Date: 2026-02-03  06:55:14
Commandline: /usr/bin/unattended-upgrade
Upgrade: telnet:amd64 (0.17+2.5-3ubuntu4, 0.17+2.5-3ubuntu4.1), inetutils-telnet:amd64 (2:2.5-3ubuntu4, 2:2.5-3ubuntu4.1)
End-Date: 2026-02-03  06:55:18

Start-Date: 2026-02-03  06:55:20
Commandline: /usr/bin/unattended-upgrade
Upgrade: libmysqlclient21:amd64 (8.0.44-0ubuntu0.24.04.2, 8.0.45-0ubuntu0.24.04.1)
End-Date: 2026-02-03  06:55:22

Start-Date: 2026-02-03  06:55:25
Commandline: /usr/bin/unattended-upgrade
Upgrade: openjdk-17-jre-headless:amd64 (17.0.17+10-1~24.04, 17.0.18+8-1~24.04.1)
End-Date: 2026-02-03  06:55:31

Start-Date: 2026-02-03  06:55:52
Commandline: /usr/bin/unattended-upgrade
Upgrade: libpng16-16t64:amd64 (1.6.43-5ubuntu0.3, 1.6.43-5ubuntu0.4)
End-Date: 2026-02-03  06:55:54

Start-Date: 2026-02-04  15:33:11
Commandline: apt-get -y upgrade
Upgrade: va-driver-all:amd64 (2.20.0-2build1, 2.20.0-2ubuntu0.1), libldap2:amd64 (2.6.7+dfsg-1~exp1ubuntu8.2, 2.6.10+dfsg-0ubuntu0.24.04.1), libldap-common:amd64 (2.6.7+dfsg-1~exp1ubuntu8.2, 2.6.10+dfsg-0ubuntu0.24.04.1), libfwupd2:amd64 (1.9.31-0ubuntu1~24.04.1, 1.9.33-0ubuntu1~24.04.1ubuntu1), libqpdf29t64:amd64 (11.9.0-1.1build1, 11.9.0-1.1ubuntu0.1), libva-x11-2:amd64 (2.20.0-2build1, 2.20.0-2ubuntu0.1), libboost-iostreams1.83.0:amd64 (1.83.0-2.1ubuntu3.1, 1.83.0-2.1ubuntu3.2), ldap-utils:amd64 (2.6.7+dfsg-1~exp1ubuntu8.2, 2.6.10+dfsg-0ubuntu0.24.04.1), python-apt-common:amd64 (2.7.7ubuntu5.1, 2.7.7ubuntu5.2), libboost-thread1.83.0:amd64 (1.83.0-2.1ubuntu3.1, 1.83.0-2.1ubuntu3.2), python3-apt:amd64 (2.7.7ubuntu5.1, 2.7.7ubuntu5.2), libboost-locale1.83.0:amd64 (1.83.0-2.1ubuntu3.1, 1.83.0-2.1ubuntu3.2), libva-wayland2:amd64 (2.20.0-2build1, 2.20.0-2ubuntu0.1), libva-drm2:amd64 (2.20.0-2build1, 2.20.0-2ubuntu0.1), mesa-vdpau-drivers:amd64 (25.0.7-0ubuntu0.24.04.2, 25.2.8-0ubuntu0.24.04.1), libva2:amd64 (2.20.0-2build1, 2.20.0-2ubuntu0.1), fwupd:amd64 (1.9.31-0ubuntu1~24.04.1, 1.9.33-0ubuntu1~24.04.1ubuntu1)
End-Date: 2026-02-04  15:33:32

Start-Date: 2026-02-05  06:27:01
Commandline: /usr/bin/unattended-upgrade
Install: linux-tools-6.8.0-94-generic:amd64 (6.8.0-94.96, automatic), linux-modules-extra-6.8.0-94-generic:amd64 (6.8.0-94.96, automatic), linux-tools-6.8.0-94:amd64 (6.8.0-94.96, automatic), linux-modules-6.8.0-94-generic:amd64 (6.8.0-94.96, automatic), linux-headers-6.8.0-94:amd64 (6.8.0-94.96, automatic), linux-image-6.8.0-94-generic:amd64 (6.8.0-94.96, automatic), linux-headers-6.8.0-94-generic:amd64 (6.8.0-94.96, automatic)
Upgrade: linux-headers-generic:amd64 (6.8.0-90.91, 6.8.0-94.96), linux-generic:amd64 (6.8.0-90.91, 6.8.0-94.96), linux-image-generic:amd64 (6.8.0-90.91, 6.8.0-94.96)
End-Date: 2026-02-05  06:27:42

Start-Date: 2026-02-05  06:27:49
Commandline: /usr/bin/unattended-upgrade
Remove: linux-tools-6.8.0-88-generic:amd64 (6.8.0-88.89), linux-tools-6.8.0-88:amd64 (6.8.0-88.89)
End-Date: 2026-02-05  06:27:50

Start-Date: 2026-02-05  06:27:52
Commandline: /usr/bin/unattended-upgrade
Remove: linux-modules-extra-6.8.0-88-generic:amd64 (6.8.0-88.89)
End-Date: 2026-02-05  06:27:55

Start-Date: 2026-02-05  06:27:57
Commandline: /usr/bin/unattended-upgrade
Remove: linux-modules-6.8.0-88-generic:amd64 (6.8.0-88.89), linux-image-6.8.0-88-generic:amd64 (6.8.0-88.89)
End-Date: 2026-02-05  06:28:04

Start-Date: 2026-02-05  06:28:06
Commandline: /usr/bin/unattended-upgrade
Remove: linux-headers-6.8.0-88-generic:amd64 (6.8.0-88.89)
End-Date: 2026-02-05  06:28:07

Start-Date: 2026-02-05  06:28:10
Commandline: /usr/bin/unattended-upgrade
Remove: linux-headers-6.8.0-88:amd64 (6.8.0-88.89)
End-Date: 2026-02-05  06:28:12

Start-Date: 2026-02-06  06:13:40
Commandline: /usr/bin/unattended-upgrade
Upgrade: python3.12:amd64 (3.12.3-1ubuntu0.10, 3.12.3-1ubuntu0.11), libpython3.12-minimal:amd64 (3.12.3-1ubuntu0.10, 3.12.3-1ubuntu0.11), libpython3.12t64:amd64 (3.12.3-1ubuntu0.10, 3.12.3-1ubuntu0.11), python3.12-minimal:amd64 (3.12.3-1ubuntu0.10, 3.12.3-1ubuntu0.11), libpython3.12-stdlib:amd64 (3.12.3-1ubuntu0.10, 3.12.3-1ubuntu0.11)
End-Date: 2026-02-06  06:13:52

Start-Date: 2026-02-06  06:13:56
Commandline: /usr/bin/unattended-upgrade
Upgrade: libglib2.0-bin:amd64 (2.80.0-6ubuntu3.7, 2.80.0-6ubuntu3.8), gir1.2-glib-2.0:amd64 (2.80.0-6ubuntu3.7, 2.80.0-6ubuntu3.8), libglib2.0-data:amd64 (2.80.0-6ubuntu3.7, 2.80.0-6ubuntu3.8), libglib2.0-0t64:amd64 (2.80.0-6ubuntu3.7, 2.80.0-6ubuntu3.8)
End-Date: 2026-02-06  06:14:03

Start-Date: 2026-02-06  06:14:24
Commandline: /usr/bin/unattended-upgrade
Upgrade: tracker-miner-fs:amd64 (3.7.1-1build1, 3.7.1-1ubuntu0.1), tracker-extract:amd64 (3.7.1-1build1, 3.7.1-1ubuntu0.1)
End-Date: 2026-02-06  06:14:29

Start-Date: 2026-02-06  14:43:27
Commandline: apt-get -y upgrade
Upgrade: linux-tools-common:amd64 (6.8.0-94.96, 6.8.0-100.100), linux-libc-dev:amd64 (6.8.0-94.96, 6.8.0-100.100)
End-Date: 2026-02-06  14:43:32

Start-Date: 2026-02-10  06:15:31
Commandline: /usr/bin/unattended-upgrade
Install: linux-image-6.8.0-100-generic:amd64 (6.8.0-100.100, automatic), linux-tools-6.8.0-100-generic:amd64 (6.8.0-100.100, automatic), linux-tools-6.8.0-100:amd64 (6.8.0-100.100, automatic), linux-headers-6.8.0-100-generic:amd64 (6.8.0-100.100, automatic), linux-modules-6.8.0-100-generic:amd64 (6.8.0-100.100, automatic), linux-headers-6.8.0-100:amd64 (6.8.0-100.100, automatic), linux-modules-extra-6.8.0-100-generic:amd64 (6.8.0-100.100, automatic)
Upgrade: linux-headers-generic:amd64 (6.8.0-94.96, 6.8.0-100.100), linux-generic:amd64 (6.8.0-94.96, 6.8.0-100.100), linux-image-generic:amd64 (6.8.0-94.96, 6.8.0-100.100)
End-Date: 2026-02-10  06:16:12

Start-Date: 2026-02-10  06:16:18
Commandline: /usr/bin/unattended-upgrade
Upgrade: libsoup-3.0-0:amd64 (3.4.4-5ubuntu0.6, 3.4.4-5ubuntu0.7), libsoup-3.0-common:amd64 (3.4.4-5ubuntu0.6, 3.4.4-5ubuntu0.7), gir1.2-soup-3.0:amd64 (3.4.4-5ubuntu0.6, 3.4.4-5ubuntu0.7)
End-Date: 2026-02-10  06:16:21

Start-Date: 2026-02-10  06:16:25
Commandline: /usr/bin/unattended-upgrade
Remove: linux-modules-extra-6.8.0-90-generic:amd64 (6.8.0-90.91)
End-Date: 2026-02-10  06:16:28

Start-Date: 2026-02-10  06:16:30
Commandline: /usr/bin/unattended-upgrade
Remove: linux-headers-6.8.0-90-generic:amd64 (6.8.0-90.91)
End-Date: 2026-02-10  06:16:31

Start-Date: 2026-02-10  06:16:33
Commandline: /usr/bin/unattended-upgrade
Remove: linux-tools-6.8.0-90-generic:amd64 (6.8.0-90.91)
End-Date: 2026-02-10  06:16:34

Start-Date: 2026-02-10  06:16:37
Commandline: /usr/bin/unattended-upgrade
Remove: linux-modules-6.8.0-90-generic:amd64 (6.8.0-90.91), linux-image-6.8.0-90-generic:amd64 (6.8.0-90.91)
End-Date: 2026-02-10  06:16:44

Start-Date: 2026-02-10  06:16:46
Commandline: /usr/bin/unattended-upgrade
Remove: linux-tools-6.8.0-90:amd64 (6.8.0-90.91)
End-Date: 2026-02-10  06:16:47

Start-Date: 2026-02-10  06:16:49
Commandline: /usr/bin/unattended-upgrade
Remove: linux-headers-6.8.0-90:amd64 (6.8.0-90.91)
End-Date: 2026-02-10  06:16:52

Start-Date: 2026-02-13  17:51:35
Commandline: apt-get -y upgrade
Upgrade: initramfs-tools-core:amd64 (0.142ubuntu25.5, 0.142ubuntu25.8), initramfs-tools-bin:amd64 (0.142ubuntu25.5, 0.142ubuntu25.8), alsa-ucm-conf:amd64 (1.2.10-1ubuntu5.8, 1.2.10-1ubuntu5.9), motd-news-config:amd64 (13ubuntu10.3, 13ubuntu10.4), base-files:amd64 (13ubuntu10.3, 13ubuntu10.4), initramfs-tools:amd64 (0.142ubuntu25.5, 0.142ubuntu25.8), libpng16-16t64:amd64 (1.6.43-5ubuntu0.4, 1.6.43-5ubuntu0.5)
End-Date: 2026-02-13  17:52:02

Start-Date: 2026-02-16  06:31:21
Commandline: /usr/bin/unattended-upgrade
Upgrade: libfreerdp3-3:amd64 (3.5.1+dfsg1-0ubuntu1.1, 3.5.1+dfsg1-0ubuntu1.2), libwinpr3-3:amd64 (3.5.1+dfsg1-0ubuntu1.1, 3.5.1+dfsg1-0ubuntu1.2), libfreerdp-server3-3:amd64 (3.5.1+dfsg1-0ubuntu1.1, 3.5.1+dfsg1-0ubuntu1.2), libfreerdp-client3-3:amd64 (3.5.1+dfsg1-0ubuntu1.1, 3.5.1+dfsg1-0ubuntu1.2)
End-Date: 2026-02-16  06:31:33

Start-Date: 2026-02-17  06:31:08
Commandline: /usr/bin/unattended-upgrade
Upgrade: libatopology2t64:amd64 (1.2.11-1ubuntu0.1, 1.2.11-1ubuntu0.2), libasound2t64:amd64 (1.2.11-1ubuntu0.1, 1.2.11-1ubuntu0.2), libasound2-data:amd64 (1.2.11-1ubuntu0.1, 1.2.11-1ubuntu0.2)
End-Date: 2026-02-17  06:31:11

Start-Date: 2026-02-17  06:31:15
Commandline: /usr/bin/unattended-upgrade
Upgrade: libgnutls30t64:amd64 (3.8.3-1.1ubuntu3.4, 3.8.3-1.1ubuntu3.5)
End-Date: 2026-02-17  06:31:17

Start-Date: 2026-02-17  06:31:23
Commandline: /usr/bin/unattended-upgrade
Upgrade: libexpat1:amd64 (2.6.1-2ubuntu0.3, 2.6.1-2ubuntu0.4)
End-Date: 2026-02-17  06:31:25

I have been trying to create a simple router for a very simple website with PHP and apache2, but I keep getting 404 messages.
Before you go through this lengthy post, I did add DocumentRoot in nt2.conf in sites-available. I have not added it anywhere else.

I created a new directory called /var/www/nt2 (on Ubuntu 25.10). In there I created this

/var/www/nt2  
   index.php (contains the router)  
   .htaccess  
   views  
      home.php  
      contact.php  
      users.php  
      404.php  

Apache runs fine. PHP has been installed successfully, I have version 8.4.11. I can get any page if I fill in the full path. For example : localhost/views/contact.php. That works, but localhost/contact does not work at all and produces a 404 error.
I'm quite the beginner, but this is not complicated code and I just don't see what I'm not doing right.

This is index.php, I copied it from an article.

<?php  
$request = $_SERVER['REQUEST_URI'];  
$viewDir = __DIR__ . '/views';  
switch ($request) {  
    case '':  
    case '/':  
        require  $viewDir . 'home.php';  
        break;  
    case '/users':  
        require  . 'users.php';  
        break;  
    case '/contact':  
        require $viewDir . 'contact.php';  
        break;  
    default:  
        http_response_code(404);  
        require $viewDir . '404.php';  
}  
?\>  
  

The files in the views folder are all like this:

<?php   
echo "<h1>Contact me</h1>  
<p>Email me: memyselfandI@hotmail.com</p>"  
?>  

Nothing fancy.

I adjusted apache2.conf:
I added the ServerName at the bottom to get rid of a message: (AH00558 - could not reliably determine the server's fully qualified domain.

ServerName  
127.0.0.1  

I also added this :

<Directory /var/www/nt2/>  
        Options Indexes FollowSymLinks  
        AllowOverride None  
        Require all granted  
</Directory>  

I tried changing AllowOverride to All (I did the same thing for <Directory /var/www/> which exists in the default version. Nothing changed so I changed it back to None in both directories.

I created a configuration file in sites-available called nt2.conf and entered these commands: (The domain doesn't really exist btw.)

ServerName www.nt2.com  
ServerAlias nt2  
ServerAdmin webmaster@localhost  
DocumentRoot /var/www/nt2  

Then I ran:
a2ensite nt2.conf
a2dissite 000-default.conf

I also ran:

ufw allow http    
ufw allow https # I don't remember why I did that.      
ufw allow ssh    
ufw allow 'Apache Full' # I found that in an article. 

There's an .htaccess which I got from the same article.

RewriteEngine On  
RewriteCond %{REQUEST_FILENAME} !-f  
RewriteCond %{REQUEST_FILENAME} !-d  
RewriteRule  . /index.php [L]  

I more or less understand what it means, but I did just copy it. I've also tried commenting everything out, but it makes no difference.

I ran a2enmod rewrite

In mods-available I made changes in userdir.conf

UserDir nt2  
UserDir disabled root  
  
<Directory /var/www/nt2>  
        AllowOverride All  
        Options Indexes FollowSymLinks  
        Require all granted  
</Directory>  

I ran a2enmod userdir :

I adjusted php.init and added /var/www/nt2 to include_path (I had an error message).

I looked at all the permissions. /var/www/nt2 is owned by me, $USER. The default folder html is owned by root. All files and directories inside the folder are owned by me.

I added myself to www-data group. (I read that somewhere.)

Nothing works. I'm at the end of my tether and I really cannot figure this out.

I commented out the following in mods-available/php8.4.conf

#<IfModule mod_userdir.c>  
#    <Directory /home/*/public_html>  
#        php_admin_flag engine Off  
#    </Directory>  
#</IfModule>  

I ran a2enmod php8.4

I'm not getting any other error messages. Just the 404.
I reloaded and restarted apache2 a million times.
I ran all the a2blabla commands again and again.

Nope.
I am so tired. I tried ChatGPT. It assured me that my router logic was wrong, gave me more complicated code. It doesn't work at all. I have the impression I don't know what the right question is because I don't know what I don't know. If I do know what I don't know, I can ask good questions and figure it out. I agree this is flimsy code, but I do intend to replace it with classes and a router.php and everything spic and span. I just feel if I understand this bit well, the more complicated stuff will be easier to digest.

I started teaching online and I really need to use Zoom. I always had problems with it, but after installing the Flatpak version at least my video and audio worked. The version I am now is 6.7.2 (6498), and its on Wayland. I can now screen share my entire screen but the school needs me to share just a window, as this removes the bar/menu from the top, however I need to switch between windows i.e. browser and libre but if I try to select even just two ppts it crashes. If I select one window it's fine.

I tried going to advanced settings and changing the screen share setting from auto to pipewire, but it still crashed. I am on Ubuntu 24.04.3 LTS.

thank you in advance

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

I was watching a video online, and suddenly my computer started emitting a high frequency noise. The video did not pause, but the sound of the video was not audible at all. The sound stopped a while after closing the lid.

This issue occurs in YouTube videos running in Firefox web browser as well as in the FreeTube app.

I ran journalctl -r and saw the error message

sof-audio-acpi-intel-byt 808622A8:00: error: reply expected 12 got 0 bytes

The computer is an Acer 11 N7 C731 Chromebook (codename RELM) natively running Ubuntu MATE 22.04. It has an Intel Celeron N3060 processor.

For my needs, I need to install PHP 7.4 (and a module for Apache2), instead of the latest PHP 8.x.

So I run the following command: apt-get install -y php7.4 libapache2-mod-php7.4

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'libapache2-mod-php7.4' for regex 'php7.4'
Note, selecting 'php7.4-fpm' for regex 'php7.4'
Note, selecting 'php7.4-common' for regex 'php7.4'
The following additional packages will be installed:
  libapache2-mod-php libapache2-mod-php8.1 php-common php8.1-cli php8.1-common php8.1-opcache php8.1-readline
Suggested packages:
  php-pear
The following NEW packages will be installed:
  libapache2-mod-php libapache2-mod-php7.4 libapache2-mod-php8.1 php-common php8.1-cli php8.1-common php8.1-opcache php8.1-readline
0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
Need to get 840 B/5193 kB of archives.
After this operation, 21.9 MB of additional disk space will be used.
Get:1 http://eu-frankfurt-1-ad-3.clouds.ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64 libapache2-mod-php7.4 arm64 8.1.2-1ubuntu2.2 [840 B]
Fetched 840 B in 0s (23.5 kB/s)
Selecting previously unselected package php-common.
(Reading database ... 114642 files and directories currently installed.)
Preparing to unpack .../0-php-common_2%3a92ubuntu1_all.deb ...
Unpacking php-common (2:92ubuntu1) ...
Selecting previously unselected package php8.1-common.
Preparing to unpack .../1-php8.1-common_8.1.2-1ubuntu2.2_arm64.deb ...
Unpacking php8.1-common (8.1.2-1ubuntu2.2) ...
Selecting previously unselected package php8.1-opcache.
Preparing to unpack .../2-php8.1-opcache_8.1.2-1ubuntu2.2_arm64.deb ...
Unpacking php8.1-opcache (8.1.2-1ubuntu2.2) ...
Selecting previously unselected package php8.1-readline.
Preparing to unpack .../3-php8.1-readline_8.1.2-1ubuntu2.2_arm64.deb ...
Unpacking php8.1-readline (8.1.2-1ubuntu2.2) ...
Selecting previously unselected package php8.1-cli.
Preparing to unpack .../4-php8.1-cli_8.1.2-1ubuntu2.2_arm64.deb ...
Unpacking php8.1-cli (8.1.2-1ubuntu2.2) ...
Selecting previously unselected package libapache2-mod-php8.1.
Preparing to unpack .../5-libapache2-mod-php8.1_8.1.2-1ubuntu2.2_arm64.deb ...
Unpacking libapache2-mod-php8.1 (8.1.2-1ubuntu2.2) ...
Selecting previously unselected package libapache2-mod-php.
Preparing to unpack .../6-libapache2-mod-php_2%3a8.1+92ubuntu1_all.deb ...
Unpacking libapache2-mod-php (2:8.1+92ubuntu1) ...
Selecting previously unselected package libapache2-mod-php7.4.
Preparing to unpack .../7-libapache2-mod-php7.4_8.1.2-1ubuntu2.2_arm64.deb ...
Unpacking libapache2-mod-php7.4 (8.1.2-1ubuntu2.2) ...
Setting up php-common (2:92ubuntu1) ...
Setting up php8.1-common (8.1.2-1ubuntu2.2) ...
Setting up php8.1-readline (8.1.2-1ubuntu2.2) ...
Setting up php8.1-opcache (8.1.2-1ubuntu2.2) ...
Setting up php8.1-cli (8.1.2-1ubuntu2.2) ...
update-alternatives: using /usr/bin/php8.1 to provide /usr/bin/php (php) in auto mode
update-alternatives: using /usr/bin/phar8.1 to provide /usr/bin/phar (phar) in auto mode
update-alternatives: using /usr/bin/phar.phar8.1 to provide /usr/bin/phar.phar (phar.phar) in auto mode
Setting up libapache2-mod-php8.1 (8.1.2-1ubuntu2.2) ...
apache2_invoke: Enable module php8.1
Setting up libapache2-mod-php7.4 (8.1.2-1ubuntu2.2) ...
Setting up libapache2-mod-php (2:8.1+92ubuntu1) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for php8.1-cli (8.1.2-1ubuntu2.2) ...
Processing triggers for libapache2-mod-php8.1 (8.1.2-1ubuntu2.2) ...
Scanning processes...
Scanning linux images...

Running kernel seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.

but when I checked what PHP version I have installed using php --version, I get the following:

PHP 8.1.2 (cli) (built: Jul 21 2022 12:10:37) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.2, Copyright (c) Zend Technologies
    with Zend OPcache v8.1.2, Copyright (c), by Zend Technologies

Question

Why did I get PHP 8.1.2 even though I explicitly attempted to install PHP 7.4? How can I install PHP 7.4 without any traces of PHP 8.x?

Currently I'm running a dual GPU setup with gyx1080ti and Tesla K80, but I am not able to boot into the X service. My plan is to use the 1080ti as my display GPU and the Tesla K80 for CUDA computing.

Results of lspci:

00:00.0 Host bridge: Intel Corporation Device 9b33 (rev 05)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 05)
00:14.0 USB controller: Intel Corporation Device 43ed (rev 11)
00:14.2 RAM memory: Intel Corporation Device 43ef (rev 11)
00:14.3 Network controller: Intel Corporation Device 43f0 (rev 11)
00:15.0 Serial bus controller [0c80]: Intel Corporation Device 43e8 (rev 11)
00:15.1 Serial bus controller [0c80]: Intel Corporation Device 43e9 (rev 11)
00:16.0 Communication controller: Intel Corporation Device 43e0 (rev 11)
00:17.0 SATA controller: Intel Corporation Device 43d2 (rev 11)
00:1b.0 PCI bridge: Intel Corporation Device 43c0 (rev 11)
00:1b.4 PCI bridge: Intel Corporation Device 43c4 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Device 43b8 (rev 11)
00:1c.7 PCI bridge: Intel Corporation Device 43bf (rev 11)
00:1d.0 PCI bridge: Intel Corporation Device 43b0 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 4385 (rev 11)
00:1f.3 Audio device: Intel Corporation Device f0c8 (rev 11)
00:1f.4 SMBus: Intel Corporation Device 43a3 (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device 43a4 (rev 11)
01:00.0 PCI bridge: PLX Technology, Inc. PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ff)
02:08.0 PCI bridge: PLX Technology, Inc. PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ff)
02:10.0 PCI bridge: PLX Technology, Inc. PEX 8747 48-Lane, 5-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ff)
03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev ff)
04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev ff)
05:00.0 Non-Volatile memory controller: Sandisk Corp Device 5006
06:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1)
06:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1)
08:00.0 Ethernet controller: Intel Corporation Device 15f3 (rev 03)
09:00.0 Non-Volatile memory controller: Sandisk Corp Device 5011 (rev 01)

My current concern is that my NVIDIA driver only supports GTX series devices. I'm just wondering if I could only use the display driver on my GTX card and thus get the X service to start.

It seems the NVIDIA driver works fine, as nvidia-smi successfully finds both of the cards. I also found in the lspci output that the K80 is identified as a "3d controller". Maybe this is the issue?

When using Adobe Reader on a Windows desktop, one can open a PDF and use the fill & sign option. This option does not seem to appear on the Ubuntu version of Adobe Reader. How does one fill and sign PDF documents on Ubuntu?

I used gThumb for several years on 16.04. I installed it on my new 20.04 system but it crashes immediately when started.

I have one HDMI monitor and one DisplayPort monitor and a GeForce GTX 1660 graphics card.

The log file shows what looks like an Nvidia issue but I don't know enough to start troubleshooting it.

Log file:

6:45:49 PM gthumb: gthumb: ../../../../src/cairo-surface.c:930: cairo_surface_reference: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (&surface->ref_count)' failed.  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0):  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0):  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0): DFP-3: Internal TMDS  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0): DFP-3: disconnected  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0):  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0): Ancor Communications Inc VS278 (DFP-2): 2660.0 MHz maximum pixel clock  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0): Ancor Communications Inc VS278 (DFP-2): Internal DisplayPort  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0): Ancor Communications Inc VS278 (DFP-2): connected  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0):  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0): Ancor Communications Inc VS278 (DFP-1): 600.0 MHz maximum pixel clock  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0): Ancor Communications Inc VS278 (DFP-1): Internal TMDS  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0): Ancor Communications Inc VS278 (DFP-1): connected  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0):  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0): DFP-0: Internal TMDS  
6:45:48 PM Xorg: (--) NVIDIA(GPU-0): DFP-0: disconnected  

Here is a screenshot from the Gnome crash report:

^{Click image to enlarge.}

After awakening from a regular sleep in Ubuntu 18.04, I often notice strange characters bugs in the Gnome interface. I link screenshots to this post. The only way I found to fix it is to perform a reboot.

It happens to me with French and English interfaces, and it happened with 2 different Ubuntu 18.04 installations on my computer.

I though this issues may be related to How to fix missing characters from font after awakening from suspend?, still none of the proposed solutions worked for me, and my characters didn't disappeared, but changed.

I guess it may be related to interference between my NVidia card (840M), the Intel Display HD card, and Gnome...

I am using NVidia additional drivers : GM108M (Geforce 840M) nvidia-driver-390 (proprietary, tested), on an Asus computer - UX303ln.

Desktop characters bug:

Application launcher characters bug:

I faced a new issue : after going to sleep mode, my computer wasn't able to recover from the dark screen.

I even tried ALT+SYST+[R, E, I, S, U, B] to reboot the computer, without success. I had to hard reboot by holding the power switch. One week ago, a similar problem caused my SSD to be corrupted. I had to buy a new one and that's why I could say I tried two different Ubuntu installation. Maybe this is linked to the data corruption issue with the new Linux version? https://www.phoronix.com/scan.php?page=news_item&px=Linux-4.19.8-Released

By looking more specifically for this dark screen problem here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950 , I discovered the "nouveau" driver issue concerning nVidia graphics cards. Two possibilities are proposed : downgrade the Linux Kernel to 4.14 or disable nouveau through GRUB. I have chosen the second option for now. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/comments/24

Set

nouveau.modeset=0

to GRUB_CMDLINE_LINUX in the /etc/default/grub file, after that run:

sudo update-grub
sudo reboot

I will answer this issue in a few days if I found out the problem not to occur anymore.

Cheers.

I'm completely new to Linux and wanted to experiment a little, so I don't really know what I'm doing. I am on working Ubuntu 18.04 and I have been unable to get Visual Studio Code to start again, even though it was working before. Trying to launch it through the application menu only resulted in a short loading animation followed by nothing. Launching it through the terminal issued /usr/lib/snapd/snap-confine: error while loading shared libraries: libudev.so.1: failed to map segment from shared object. I already tried to reinstall it. But attempting it through the terminal somehow didn't work at all manuel@Manuel-Ubuntu:~$ sudo dpkg --remove visual-studio-code dpkg: warning: ignoring request to remove visual-studio-code which isn't installed. According to the Ubuntu Software center it was installed.

I tried the suggestion by @karel snap-confine refuses to launch application to avoid permission attack, which didn't help my problem.

Whenever I try to restart or shutdown my laptop it freezes up completely and never continues with the process.

I have tried:

• Setting GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force apm=power_off" in /etc/default/grub
• Adding apm power_off=1 to /etc/modules
• Updating everything fully
• Installing Nvidia graphic drivers

This doesn't only occur on shutdown. It sometimes stalls from regular use.

I also went through the logs and here is everything in the important section:

^{Click image to enlarge.}

Question for Apt

The title pretty much states my entire question, but to rephrase it... What does "reading database" mean when upgrading via apt? Is the database custom, meaning that it does not use mysql or mariadb?

Any suggestions, would be appreciated!

Is it possible to disable autorefresh in snap? This link says that Snaps are updated automatically in the background to the latest version, every day. Some snaps (e.g. vlc) are built daily, and it makes no sense to install them every day.

I am currently taking a Cyber Security Course online and the instructor uses both, JD-GUI and Boomerang Decompilers. Therefore, I would like to get help on how to install those for Ubuntu. I have looked up videos and other forums on installation guides and they have not been pretty helpful, or at least understandable for me. Your help is greatly appreciated!

Thanks in advance!

I am using Xubuntu 14.04 on an ASUS X55V(i3 CPU and Nvidia 610m GPU). I installed the recommended proprietary driven in the GUI (352.63). I installed Nvidia Settings, too, and it lets me choose if I want to use the integrated GPU or the Nvidia GPU. When I am playing a video on YouTube or in VLC I can see it uses my GPU (but as the picture shows, it does not use video engine. Does it have anything to do with it?).

NVIDIA X Server Settings:

I also ticked the ani-aliasing checkboxes which include the following settings:

• Enable FXAA(ticked)
• Antiostrolpic filtering(override app settings-ticked)
• Texture quality(texture sharpening-ticked)

I installed the Ubuntu restricted extras, well and lastly I found this:
http://blog.riswan.com/2012/05/how-to-fix-slow-choppy-video-playback.html
I followed all the instructions with no luck.

formatc2013@formatc2013-X55VD:~$ lspci|grep VGA
[00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF119M \[GeForce 610M\] (rev a1)][1]

I would like to know, what is the reason of this screen tearing, and what commands to run in order to fix it.

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

For the last 3 years I've been using a Samsung notebook. I was using Ubuntu 13.10 until 2 weeks ago. Then I decided to format and install Ubuntu 14.04 LTS.

Everything was working great, until the third day, when I did not do anything else than installing the software updates, I noticed my battery was not being recognized. The battery indicator shows charging, and when I click it it just says Battery. The day started to malfunction just said unknown battery, and when I unplugged my laptop it shut down.

If a try to turn on my laptop with the battery in and not plugged into an AC adapter, it does not turn on: it only works when its plugged in. Also, when its plugged in with the battery the light showing the battery status is now always switching from green to red (which it never did before).

I guessed it was just my battery dieing, so I tried in another notebook like mine and was working perfectly, full battery, 3 hrs and a half running. How can I get Ubuntu to recognize my battery? I really don't want a laptop that is a portable PC, I need a portable laptop again.

I'm getting this error launching hostapd with minimal conf

Failed to update rate sets in kernel module

I've just installed Ubuntu-GNOME 13.04. When I was using Ubuntu 12.04 did not receive this kind of error, so I assume is not hardware problem. Do I need to add extra wifi drivers? How to?

Kernel info:

Linux  3.8.0-31-generic #46-Ubuntu SMP Tue Sep 10 19:56:49 UTC 2013 i686 athlon i686 GNU/Linux

PC: Aspire One 722.

Today I bought my first laptop with Ubuntu installed. Everything was working, until I decided to make the update. I used the update manager, installed all the updates, but then my wireless stopped working.

I went to the DELL site, where I created an account, but due to the fact that some tools only work with IE (and they suggest to install it!! can't believe...), when I select my laptop model to download the drivers the answer is 0 results... Can't believe also!

I checked on the internet for a solution, but I didn't find any. Can someone help me?

If I make a lshw this is what I think is the wireless info:

*-network UNCLAIMED description: Network controller product: QCA9565 / AR9565
Wireless Network Adapter vendor: Qualcomm Atheros

I have an ASUS A55V which comes with the infamous nVidia Optimus chipset. I installed bumblebee, and tested it correctly with optirun glxspheres. The problem is that I cannot change the screen resolution, from both the nVidia Panel and the Ubuntu Display utility, which is fixed at 640x480. The strange thing is that if I attach an external monitor, it's correctly detected and I can configure it normally with a decent resolution.

Laptop screen's resolution is fixed no matter if the external monitor is plugged in or not. And a curious thing is that even if the external monitor is unplugged, it still shows at the nVidia settings...

Do you have any hints on how to solve this?

Using xrandr seems to work to add a new resolution and set it up, but the display is limited to the center of the screen. Here's a screenshot so you know what I mean.

I'm using two monitors of different brands and resolutions with NVIDIA TwinView, which works well enough, but one thing that's getting to me is how the mouse can move off the edge of the visible screen space below the left-hand screen and above the right-hand screen (see screenshot).

It makes it much more difficult to hit buttons at the bottom/top of each screen, since the cursor just disappears off the edge. Is there a way of changing this behavior?