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

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

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

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

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

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

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

but this stops, because...

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

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

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

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

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

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

$ uname -a

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

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

Edit: I have done some more testing

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

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

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

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

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

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

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

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

I'm going to have a headless ubuntu 24.04 system which I need to set up a console on. Is it possible to somehow use a different laptop system (probably MS win 11) as a console by connecting their hdmi (or usb) ports? Its network address will probably be obtained via an isp's dhcp, so probably not fixed. The user will need high-res graphics.

I have created a bootable pendrive with Ubuntu 26.04 Daily build ISO.
Downloaded from here: https://cdimage.ubuntu.com/daily-live/current/
I have successfully booted Ubuntu system. I am even writing this post form my booted live pendrive.
Now I want to install the system.
I have desktop icon "Install Ubuntu 26.04 LTS" which when double clicked does not work. Nothing shows up.
I have also on the left side panel icon "Install RELEASE" which also doesn't work when clicked.

I have launched terminal and wanted to manually start installation process.

sudo snap run ubuntu-desktop-bootstrap

bin/bash: /snap/ubuntu-desktop-bootstrap/515/usr/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.42' not found (required by /usr/lib/x86_64-linux-gnu/libtinfo.so.6)

When i check the glibc version, I seem to have correct one.

ldd --version

ldd (Ubuntu GLIBC 2.42-2ubuntu5) 2.42
Copyright (C) 2024 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

Has anyone tried to install the newest preliminary release?

I am trying to access data ont old RAID drive (1 of 2 mirrored). Recognized by Ubuntu as /dev/sda with 4 partitions.

I am using mdadm package. What I did:

sudo mdadm --assemble --run /dev/md127 /dev/sda4
mdadm: /dev/md127 has been started with 1 drive (out of 2).

then

sudo mdadm -D /dev/md127
/dev/md127:
           Version : 0.90
     Creation Time : Thu Feb  2 12:15:30 2017
        Raid Level : raid1
        Array Size : 973525376 (928.43 GiB 996.89 GB)
     Used Dev Size : 973525376 (928.43 GiB 996.89 GB)
      Raid Devices : 2
     Total Devices : 1
   Preferred Minor : 127
       Persistence : Superblock is persistent

     Intent Bitmap : Internal

       Update Time : Fri Jul  7 23:19:03 2017
             State : clean, degraded 
    Active Devices : 1
   Working Devices : 1
    Failed Devices : 0
     Spare Devices : 0

Consistency Policy : bitmap

              UUID : 84f20cfc:0d2045e1:e368bf24:bd0fce41
            Events : 0.7

    Number   Major   Minor   RaidDevice State
       0       8        4        0      active sync   /dev/sda4
       -       0        0        1      removed

and

sudo mdadm -E /dev/md127
mdadm: No md superblock detected on /dev/md127.

next was

sudo mount -o ro /dev/md127 /mnt/disk2
mount: /mnt/disk2: wrong fs type, bad option, bad superblock on /dev/md127, missing codepage or helper program, or other error.

and there I am stuck. Tried to specify FS as ext2, ext3, ext4 - didn't work. Checked

sudo mdadm --examine --scan
ARRAY /dev/md127 UUID=84f20cfc:0d2045e1:e368bf24:bd0fce41

and nothing changes. What am I doing wrong????

P.S. RAID was built automaticaly in WD NAS without manual settings. It was 1 drive NAS so I don't get why it shows as RAID.

EDIT:

sudo blkid
/dev/sda5: UUID="f5b53ee4-3b51-4a28-aff9-0ed3c505f56e" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="96344476-05"
/dev/loop1: TYPE="squashfs"
/dev/loop19: TYPE="squashfs"
/dev/loop17: TYPE="squashfs"
/dev/loop8: TYPE="squashfs"
/dev/sdb4: UUID="84f20cfc-0d20-45e1-e368-bf24bd0fce41" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="1cc03ff4-3314-4ee7-b243-fa73591c4cde"
/dev/sdb1: PARTLABEL="primary" PARTUUID="d784fc1f-b5c0-433c-8acb-3b83cea31b7f"
/dev/loop15: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop0: TYPE="squashfs"
/dev/loop18: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop16: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/sda1: UUID="80F8-E80C" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="96344476-01"
/dev/loop14: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop20: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"

and

sudo file -sL /dev/md127
/dev/md127: data

system was WD Mybook World Edition I (white light) single disk station

kvm_amd CPU x isn't AMD or Hygon?

This text appear early in the boot sequence.

Now this is not really causing any trouble, RIGHT NOW.
But I consider all similar messages to be a potential hazard to the stability of my machine.
Therefore I quite fiercely hunt them down, and "swat them out".
The more of these unwanted messages you have the greater potential for strange interference and malfunction.

These are apparently about virtualbox:
https://unix.stackexchange.com/questions/798132/why-and-how-were-kvm-modules-unexpectedly-enabled-in-ubuntu-24-04
KVM not supported shown in terminal while it is enabled

... but I have this on intel-based hardware,
an oldish i7-9750H-based Asus G731 laptop, with embedded GTX 1660 Ti.
NOTE: 6 cores+HT, so message does not appear for ALL cores(!?)
Virtualbox 7.2(?) IS installed though, but quite seldom used.

I have:
GRUB_CMDLINE_LINUX_DEFAULT= ... kvm.enable_virt_at_load=0
in /etc/default/grub

No go.

$ sudo -i
# cat >/etc/modprobe.d/kvm.conf
blacklist kvm
blacklist kvm-amd
blacklist kvm-intel

CTRl+D

# update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-6.17.0-14-generic
...
# 

CTRl+D again

Reboot... I still get a black screen with these boot messages:

[    6.359851]
[   10.531179] kvm_amd: CPU 4 isn't AMD or Hygon
[   11.104935] kvm_amd: CPU 6 isn't AMD or Hygon
[   11.193682] kvm_amd: CPU 9 isn't AMD or Hygon
_

Does anyone have any more ideas on how to actually get rid of this?

I’m preparing several Raspberry Pis that will all run Ubuntu Server. Since each device needs the same applications and initial configuration, I want to create a preconfigured image that I can flash onto any SD card. The only thing that should differ between devices is the Wi‑Fi configuration.

I need to be able to change the Wi‑Fi settings offline, while the SD card is mounted on another Linux system, before booting the Raspberry Pi. However, I can’t find any documentation on how to modify the Wi‑Fi configuration via Netplan without knowing the exact WLAN interface name or being able to run commands on the Pi itself.

It must be possible, though — for example, the Raspberry Pi Imager allows you to set Wi‑Fi credentials through its UI, and the system connects successfully on first boot.

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

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

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

In reply to @heynnema:

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

In reply to guiverc:

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

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

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

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

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

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

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

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

DKMS issue relates to building the VirtulBox 7.0.16 kernel module

I recently installed 24.04.04 on my Lenovo Slim 7 14ILL10 (dual booting with Windows). Audio from my speakers and headphone jack did not work at all. I followed the below guide and installed Cirrus drivers. https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2137115. My speakers now work.

Unfortunately my headphone jack still does not work. Interestingly, testing the headphone output through the Settings app shows sound packets "playing" through my headphones, but no noise at all.

Below is some information that may be helpful.

Edit - I included arecord -L. Hopefully this helps.

Edit 2 - I booted into Fedora. Both the speakers and headphone jack work without issue. Makes me think this is a Ubuntu or Debian specific issue.

Subsystem: Lenovo Device [17aa:3838].

$ lspci | grep -i audio
00:1f.3 Multimedia audio controller: Intel Corporation Lunar Lake-M HD Audio Controller (rev 10)

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sofsoundwire [sof-soundwire], device 0: Jack Out (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 2: Speaker (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 5: HDMI1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 6: HDMI2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 7: HDMI3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: sofsoundwire [sof-soundwire], device 31: Deepbuffer Jack Out (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

arecord -L
null
    Discard all samples (playback) or generate zero samples (capture)
lavrate
    Rate Converter Plugin Using Libav/FFmpeg Library
samplerate
    Rate Converter Plugin Using Samplerate Library
speexrate
    Rate Converter Plugin Using Speex Resampler
jack
    JACK Audio Connection Kit
oss
    Open Sound System
pipewire
    PipeWire Sound Server
pulse
    PulseAudio Sound Server
speex
    Plugin using Speex DSP (resample, agc, denoise, echo, dereverb)
upmix
    Plugin for channel upmix (4,6,8)
vdownmix
    Plugin for channel downmix (stereo) with a simple spacialization
default
    Default ALSA Output (currently PipeWire Media Server)
hw:CARD=sofsoundwire,DEV=1
    sof-soundwire, 
    Direct hardware device without any conversions
hw:CARD=sofsoundwire,DEV=10
    sof-soundwire, 
    Direct hardware device without any conversions
plughw:CARD=sofsoundwire,DEV=1
    sof-soundwire, 
    Hardware device with all software conversions
plughw:CARD=sofsoundwire,DEV=10
    sof-soundwire, 
    Hardware device with all software conversions
dsnoop:CARD=sofsoundwire,DEV=1
    sof-soundwire, 
    Direct sample snooping device
dsnoop:CARD=sofsoundwire,DEV=10
    sof-soundwire, 
    Direct sample snooping device
usbstream:CARD=sofsoundwire
    sof-soundwire
    USB Stream Output

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

Similar to Ubuntu 24.04 (Noble): Wi-Fi stopped working after kernel upgrade to 6.17.0-14-generic (Intel AX211 / iwlwifi), but the solution there does not work for me. As noted below, I'm on version 6.8 of the kernel, while that question is for version 6.17. Presumably, all of the solutions over there are also for 6.17, since they all boil down to the same thing that doesn't do anything for me. No change in behavior at all.

Ubuntu Studio 24.04.1 LTS (KDE 5, kernel 6.8) on a Dell Precision M6800 Mobile Workstation. It was rock-solid before, but I thought I'd upgrade the WiFi, since I found a forum post elsewhere that claimed success. So I got the exact model from that post, and swapped it in:

https://www.amazon.com/8774Mbps-Gigabit-Interface-Bluetooth-BE200HMW/dp/B0DNZS761K?th=1

Edit: Output of the Wireless Info Script is here:
https://drive.google.com/file/d/1hDamjIeDjaBPvvXzgR65BeXS4hg3Ec9n/view?usp=sharing

dmesg:
https://drive.google.com/file/d/1--iBvEnSYAVdLa33QNZh4S6fuPIyFllO/view?usp=sharing
I suspect the relevant part might be this, but I'm not sure what it means:

[    6.792669] Intel(R) Wireless WiFi driver for Linux
[    6.792777] iwlwifi 0000:03:00.0: enabling device (0000 -> 0002)
[    6.795777] iwlwifi 0000:03:00.0: Detected crf-id 0x1001910, cnv-id 0x1001910 wfpm id 0x80000000
[    6.795846] iwlwifi 0000:03:00.0: PCI dev 272b/00f0, rev=0x471, rfid=0x112100
[    6.822777] mc: Linux media interface: v0.10
[    6.847006] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-gl-b0-fm-b0-86.ucode failed with error -2
[    6.872835] workqueue: smp_call_on_cpu_callback hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
[    6.924924] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-gl-b0-fm-b0-85.ucode failed with error -2
[    6.975001] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-gl-b0-fm-b0-84.ucode failed with error -2
[    6.975060] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-gl-b0-fm-b0-83.ucode failed with error -2
[    6.975086] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-gl-b0-fm-b0-82.ucode failed with error -2
[    7.008101] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-gl-b0-fm-b0-81.ucode failed with error -2
[    7.008151] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-gl-b0-fm-b0-80.ucode failed with error -2
[    7.008156] iwlwifi 0000:03:00.0: no suitable firmware found!
[    7.008159] iwlwifi 0000:03:00.0: minimum version required: iwlwifi-gl-b0-fm-b0-80
[    7.008162] iwlwifi 0000:03:00.0: maximum version supported: iwlwifi-gl-b0-fm-b0-86
[    7.008164] iwlwifi 0000:03:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

And on a LiveUSB of UbuntuStudio 24.04.4, with the newer kernel:

ubuntu-studio@ubuntu-studio:~$ sudo dmesg | grep iwl
[   20.141491] iwlwifi 0000:03:00.0: enabling device (0000 -> 0002)
[   20.164852] iwlwifi 0000:03:00.0: Detected crf-id 0x1001910, cnv-id 0x1001910 wfpm id 0x80000000
[   20.164925] iwlwifi 0000:03:00.0: PCI dev 272b/00f0, rev=0x471, rfid=0x112100
[   20.164929] iwlwifi 0000:03:00.0: Detected Intel(R) Wi-Fi 7 BE200 320MHz
[   20.179995] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-gl-b0-fm-b0-102.ucode failed with error -2
[   20.180058] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-gl-b0-fm-b0-101.ucode failed with error -2
[   20.180108] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-gl-b0-fm-b0-100.ucode failed with error -2
[   20.180160] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-gl-b0-fm-b0-99.ucode failed with error -2
[   20.180215] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-gl-b0-fm-b0-98.ucode failed with error -2
[   20.180217] iwlwifi 0000:03:00.0: no suitable firmware found!
[   20.180220] iwlwifi 0000:03:00.0: minimum version required: iwlwifi-gl-b0-fm-b0-98
[   20.180221] iwlwifi 0000:03:00.0: maximum version supported: iwlwifi-gl-b0-fm-b0-102
[   20.180223] iwlwifi 0000:03:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
ubuntu-studio@ubuntu-studio:~$

Continue reading for the order of troubleshooting.

It started up just fine, but no WiFi at all. lspci said:

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d4)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d4)
00:1c.6 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 (rev d4)
00:1c.7 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM87 Express LPC Controller (rev 04)
00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation GP104GLM [Quadro P5000 Mobile] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1)
03:00.0 Network controller: Intel Corporation Wi-Fi 7(802.11be) AX1775*/AX1790*/BE20*/BE401/BE1750* 2x2 (rev 1a)
11:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)

So I swapped back to the old card, same configuration as before, and it wouldn't finish booting! First time it's done that in a VERY long time! It got as far as the second splash screen, after auto-login, for loading the user's settings, and then hung there, gear spinning for far longer than it normally does.

Eventually I gave up, held the power button to force it off, took the card out, and tried to run it with no WiFi card at all. Same thing again: hung on the spinning gear after auto-login.

So I went back to the one configuration that worked - the new WiFi card - and it STILL did the exact same thing: hung on loading user settings.

Then I went into the BIOS and got this, still with the new card:

After that, it finally finished logging in, in the same time that it normally takes, but I don't know how or why since I didn't change anything. Still no WiFi.

aaron@aaron-M6800:~$ ifconfig
Command 'ifconfig' not found, but can be installed with:
sudo apt install net-tools
aaron@aaron-M6800:~$ sudo apt install net-tools
[sudo] password for aaron: 

...

aaron@aaron-M6800:~$ ifconfig
eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet ***.***.***.***  netmask ***.***.***.***  broadcast ***.***.***.***
        inet6 ****::****:****:****:****  prefixlen 64  scopeid 0x20<link>
        ether 34:e6:d7:**:**:**  txqueuelen 1000  (Ethernet)
        RX packets 143994  bytes 165365853 (165.3 MB)
        RX errors 0  dropped 2  overruns 0  frame 0
        TX packets 97963  bytes 16432715 (16.4 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xf7800000-f7820000  

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

aaron@aaron-M6800:~$ sudo lshw -class network
[sudo] password for aaron: 
  *-network                 
       description: Ethernet interface
       product: Ethernet Connection I217-LM
       vendor: Intel Corporation
       physical id: 19
       bus info: pci@0000:00:19.0
       logical name: eno1
       version: 04
       serial: 34:e6:d7:**:**:**
       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-94-lowlatency duplex=full firmware=0.13-3 ip=192.168.20.98 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:41 memory:f7800000-f781ffff memory:f783d000-f783dfff ioport:f080(size=32)
  *-network UNCLAIMED
       description: Network controller
       product: Wi-Fi 7(802.11be) AX1775*/AX1790*/BE20*/BE401/BE1750* 2x2
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:03:00.0
       version: 1a
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix cap_list
       configuration: latency=0
       resources: memory:f7700000-f7703fff
aaron@aaron-M6800:~$ rfkill list all
1: dell-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: no
2: dell-bluetooth: Bluetooth
        Soft blocked: yes
        Hard blocked: no
3: hci0: Bluetooth
        Soft blocked: yes
        Hard blocked: no
aaron@aaron-M6800:~$ sudo dmesg | grep -i firmware
[23505.872167] audit: type=1400 audit(1771394432.473:1374): apparmor="DENIED" operation="open" class="file" profile="snap.firmware-updater.firmware-notifier" name="/proc/sys/vm/max_map_count" pid=40061 comm="firmware-notifi" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
aaron@aaron-M6800:~$ 

Fortunately, my home dock is wired, which is how I'm posting this, but I do need WiFi when I take it places. At this point, I'd be happy if either card worked, but of course I'd still prefer the new one. Any ideas?

Using TERMINAL in Ubuntu 24.04.3lts Wayland - Linux 6.8.0-85-generic, how do I SUCCESSFULLY uninstall nautilus completely, and aferwhich, how do I reinstall it SUCCESSFULLY - dependencies and all...?

Currently, I can copy, edit, move, etc. files using terminal so drive itself and permissions seem no problem, edit using nano, etc., but nautilus seems to just want to crash (like it's corrupt) so want to reinstall, not repair, it.

from terminal:

Desktop$ nautilus
** Message: 19:33:27.602: Connecting to org.freedesktop.Tracker3.Miner.Files
Gsk-Message: 19:33:30.917: Failed to realize renderer of type 'GskNglRenderer' for surface 'GdkWaylandToplevel': OpenGL ES 3.0 is not supported by this renderer.

Gsk-Message: 19:34:24.833: Failed to realize renderer of type 'GskNglRenderer' for surface    'GdkWaylandPopup': OpenGL ES 3.0 is not supported by this renderer.

Gsk-Message: 19:34:46.395: Failed to realize renderer of type 'GskNglRenderer' for surface 'GdkWaylandPopup': OpenGL ES 3.0 is not supported by this renderer.

Shouldn't that be Gsk.NglRenderer, not GskNglRenderer?

OK, Daniel T, I ran dpkg -V, but no /bin lines at all:

/Desktop$ dpkg -V
?????????   /boot/vmlinuz-6.8.0-94-generic
missing     /etc/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /etc/polkit-1/localauthority/20-org.d (Permission denied)
missing     /etc/polkit-1/localauthority/30-site.d (Permission denied)
missing     /etc/polkit-1/localauthority/50-local.d (Permission denied)
missing     /etc/polkit-1/localauthority/90-mandatory.d (Permission denied)
missing     /var/lib/polkit-1/localauthority (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/20-org.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/30-site.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/50-local.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/90-mandatory.d (Permission denied)
?????????   /boot/vmlinuz-6.8.0-85-generic
missing     /lib/modules/6.8.0-35-generic
?????????   /boot/kernel.efi-6.8.0-79-generic
??5?????? c /etc/apt/apt.conf.d/10periodic
??5?????? c /etc/UPower/UPower.conf
??5?????? c /etc/conky/conky.conf
??5?????? c /etc/mono/config
??5?????? c /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf
?????????   /usr/libexec/sssd/proxy_child
missing     /var/lib/polkit-1/localauthority (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d/org.blueman.pkla (Permission denied)
?????????   /boot/vmlinuz-6.8.0-53-generic
?????????   /lib/netplan/00-network-manager-all.yaml
?????????   /boot/System.map-6.8.0-53-generic
??5?????? c /etc/fuse.conf
?????????   /boot/System.map-6.8.0-84-generic
missing   c /etc/grub.d/10_linux
?????????   /usr/libexec/sssd/selinux_child
??5?????? c /etc/tlp.conf
?????????   /usr/libexec/sssd/krb5_child
?????????   /usr/libexec/sssd/ldap_child
missing     /var/cache/cups/rss (Permission denied)
missing     /var/spool/cups/tmp (Permission denied)
??5?????? c /etc/update-manager/release-upgrades
?????????   /boot/System.map-6.8.0-85-generic
????????? c /etc/sudoers
????????? c /etc/sudoers.d/README
missing     /var/lib/polkit-1/localauthority (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d/org.freedesktop.Flatpak.pkla (Permission denied)
?????????   /boot/vmlinuz-6.8.0-84-generic
missing     /var/lib/polkit-1/localauthority (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d/gnome-initial-setup.pkla (Permission denied)
??5?????? c /etc/gdm3/custom.conf
??5?????? c /etc/sysctl.conf
missing     /var/lib/polkit-1/localauthority (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d/org.freedesktop.packagekit.pkla (Permission denied)
?????????   /boot/vmlinuz-6.8.0-79-generic
missing     /var/lib/polkit-1/localauthority (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d/com.ubuntu.desktop.pkla (Permission denied)
????????? c /etc/default/cacerts
?????????   /boot/System.map-6.8.0-79-generic
????????? c /etc/fwupd/fwupd.conf
missing     /var/lib/polkit-1/localauthority (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d (Permission denied)
missing     /var/lib/polkit-1/localauthority/10-vendor.d/fwupd.pkla (Permission denied)
?????????   /boot/System.map-6.8.0-50-generic
?????????   /boot/System.map-6.8.0-94-generic

In lieu of using termnal on the desktop, would using the RECOVERY tool from grub and dropping into root be better way to uninstall, then reboot and again to the tool to root, to reinstall nautilus?

I can run Firefox, browse away, play things, etc., and all is fine until I try to attach a file to an email which tries to bring up a nautilus type window, or try to download/save a file which also tries to bring up a nautilus type window, then it'll try but ends up crashing Firefox during the attempt. I assume a piece of nautilus is what the browser uses - same with using something like LibreOffice - try to open a file which tries to bring up the window and that does similarly...

using "LIBGL_ALWAYS_SOFTWARE=1 nautilus", I noticed I can rename a file, but try to copy it, and the freeze/blink off-on/crash happen as the window pops up (with read only message at its bottom) for where to copy it to...

@steeldriver:

Desktop$ ldd "$(command -v firefox)"
linux-vdso.so.1 (0x00007ffdff992000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007d6836703000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007d68366fe000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007d6836400000)
/lib64/ld-linux-x86-64.so.2 (0x00007d683672d000)

"Try sudo apt install --reinstall ubuntu-desktop^ to fix default packages, including nautilus. – Archisman Panigrahi" - are you sure that's right 'cause I just get:

Desktop$ sudo apt install --reinstall ubuntu-desktop^
[sudo] password for batgirl: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package ubuntu-desktop^
E: Couldn't find task 'ubuntu-desktop'

but w/o the '^' on the end I still get:

Desktop$ sudo apt install --reinstall ubuntu-desktop
[sudo] password for batgirl: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package ubuntu-desktop        

NOTE: Posted new inquiry cleaned-up w/o all the rabbit holes at: Need help with terrible file manager type ‘glitch’?

OK, let's just try:

Desktop$ sudo apt install --reinstall nautilus
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 40 not upgraded.
Need to get 510 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 nautilus amd64 1:46.4-0ubuntu0.2 [510 kB]
Fetched 510 kB in 1s (402 kB/s)   
(Reading database ... 444973 files and directories currently installed.)
Preparing to unpack .../nautilus_1%3a46.4-0ubuntu0.2_amd64.deb ...
Unpacking nautilus (1:46.4-0ubuntu0.2) over (1:46.4-0ubuntu0.2) ...
Setting up nautilus (1:46.4-0ubuntu0.2) ...
Processing triggers for gnome-menus (3.36.0-1.1ubuntu3) ...
Processing triggers for man-db (2.12.0-4build2) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for desktop-file-utils (0.27-2build1) ...

Maybe I have not found a way to get a good scan in Ubuntu. IMHO, a good scan file is high resolution and small. For the same resolution, smaller is better.

I scan documents almost exclusively. For example, nowadays I am scanning hard copy tax documents that arrive in the mail, as my accountant expects everything to be uploaded.

I have tried xsane, scanlite and scanpage, but the files are typically ginormous (bigger than a MB). Using Windows Fax and Scan in Windows 7, I set the resolution to 300 dpi and scanned an Ubuntu printer test printout. I get a nice looking image tiff that weighs in at 66 Kb.

You can see for yourself, download what I got here, filename:

Windows_Fax_n_Scan_ubuntu_print_test_2026-02-07.tiff

You can try it! Print a test page in your system settings, printers. Then scan it and compare what you got with what I got from Windows 7.

(I have not tried later Windows versions. I need Windows 7 for one application. I do not use Windows 7 for email or surfing.)

As suggested by Daniel T, in Ubuntu, I tried simple-scan on the same printer test printout. I set the resolution to 300 dpi and compression at max. I got a 143 Kb pdf (more than double the size of the Windows 7 scan). To my eye, the print is dark gray, not as black as in the tiff. You can download what I got here, filename:

simple-scan_text_300dpi_max_compress_2026-02-07.pdf

Again, if you like, you can try it and see for yourself.

Until I find a good way to scan in Ubuntu, I will be dual booting into Windows 7 when I need to scan. Is there a way to scan in Ubuntu that I have not discovered? If there is no way to get an equally small and crisp document scan in Ubuntu, I am hoping to get the attention of the developers of an Ubuntu scan app, hence challenging them to scan as good as Windows 7.

On further research I see my Lenovo T410 isn't certified for Ubuntu.

First time Linux user here; Lenovo T410 laptop running windows 10. Lenovo T410 laptop, downloaded Ubuntu Desktop, 24.04.3 desktop amd64 (Intel / AMD from Ubuntu Desktop page. Tried Balena Etcher multiple times downloaded this and the Ubuntu several times in case there was corruption in the downloads. always got the Error: (0,h.RequestMetadata) is not a function.

I gave up and used Rufus 4.11.2285 screenshot attached.

This flashed the ISO to the flash drive (32GB Sandisk). This is where I'm stuck. I can't get flash drive to boot and load Ubuntu. On attempting to boot from the flash drive, I get the "Loading Grub", "Welcome to Grub!" message and one second later it reboots, to produce the same message over and over again until I interrupt.

In searching for solutions, I don’t seem to have the same options as often suggested. Available boot modes are either “quick” or “diagnostics.” From these screenshots you'll see there's no reference to any UEFI. Screenshots of BIOS info and various options. I don't see any UEFI Fast Book options on my T410 where I'm trying to load Linux. On my T16 I see many references in the BIOS menus to UEFI.

BIOS info:

Boot menu from restart:

Boot priority order - This is only choice that causes the Grub message:

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

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

I tried to follow most of the steps in

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

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

The main error message reported is:

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

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

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

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

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

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

Edited: Adding lsusb output as requested.

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

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

I am trying to get a GPU system load monitor to work in xfce4 panel. Is there any way to configure the current CPU system load monitor to reflect GPU usage? I know we can run a script in genmon generic monitor but I don't have the skills necessary to create the script.

I have an AMD GPU and currently use gpu-mon --gui for monitoring but would like to have something similar to the CPU monitor in the panel, preferably for GPU load and vram mem load.

Thanks

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

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

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

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

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

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

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

I am trying to install Ubuntu 20.04 on a USB drive I created on another Ubuntu device. I have successfully used this USB drive to install Ubuntu 20.04 on my laptop. I am now trying to use it to install Ubuntu 20.04 on my desktop.

When I boot from the USB drive, I get the following errors:

Initramfs unpacking failed: Decoding failed
usb 2-2: device descriptor read/64, error -32
usb 2-2: device descriptor read/64, error -32
usb 2-2: device descriptor read/64, error -32
usb 2-2: device descriptor read/64, error -32
usb 2-2: device not accepting address 5, error -32
usb 2-2: device not accepting address 6, error -32
usb usb2-port2: unable to enumerate USB device    
usb 5-1: device descriptor read/64, error -110
usb 5-1: device descriptor read/64, error -110
usb 5-1: device descriptor read/64, error -110
usb 5-1: device descriptor read/64, error -110
usb 5-1: device not accepting address 4, error -110
usb 5-1: device not accepting address 5, error -110
usb usb5-port1: unable to enumerate USB device
usb 5-2: device descriptor read/64, error -32
usb 5-2: device descriptor read/64, error -32
usb 5-2: device descriptor read/64, error -32
usb 5-2: device descriptor read/64, error -32
usb 5-2: device not accepting address 8, error -32
usb 5-2: device not accepting address 9, error -32
usb usb5-port2: unable to enumerate USB device
usb 5-3: device descriptor read/64, error -32
usb 5-3: device descriptor read/64, error -32
usb 5-3: device descriptor read/64, error -32
usb 5-3: device descriptor read/64, error -32
usb 5-3: device not accepting address 12, error -32
usb 5-3: device not accepting address 13, error -32
usb usb5-port3: unable to enumerate USB device
usb 5-4: device descriptor read/64, error -32
usb 5-4: device descriptor read/64, error -32
usb 5-4: device descriptor read/64, error -32
usb 5-4: device descriptor read/64, error -32
usb 5-4: device not accepting address 16, error -32
usb 5-4: device not accepting address 17, error -32
usb usb5-port4: unable to enumerate USB device
Unable to find a medium container a live file system
Attempt interactive netboot from a URL?
yes no (default yes):

At some point during this process my screen shows the name of my motherboard and then UBUNTU underneath, with a rotating wheel.

Anyone have any idea what is going on? Based on other things I've read, I am afraid my motherboard is having problems providing power to the USB port. But, the USB port seems to work fine when I boot into Ubuntu and interact with it there.

I find it really frustrating when people send me links to samba shares while I'm on linux. I know some file browsers think they support copy/pasting smb links into the location bar but in practice it just doesn't work. Nautilus just says "Oops! Something went wrong". Dolphin correctly reformats the link and asks for a password but always fails with access denied.

The reliable way is to mount them: https://unix.stackexchange.com/questions/99065/how-to-mount-a-windows-samba-windows-share-under-linux

But hontestly, I cbf rewriting all the \ to / 🤦, creating a temporary mount point, entering the password, then opening a file browser at that location etc. People on windows can just click on the link and it opens. How can I get the same level of convenience on linux?

I'm running kubuntu but will happily take all suggestions.

I am quite new to linux and have recently installed Ubunutu 18.04 LTS.

I am trying to install NASA GMAT (available at https://sourceforge.net/projects/gmat/). After downloading .tar.gz I extracted the archive and found a README file. The command line version of GMAT found in /bin of the file works perfectly fine.

However, when I try to run "./GMAT_Beta" I get the following error:

./GMAT_Beta./GMAT_Beta: error while loading shared libraries: libpng15.so.15: cannot open shared object file: No such file or directory

Now I have checked via Synaptics Package Manger and using apt command that I have libpng16-16 - installed version "1.6.34-1ubuntu.18.04.2".

I want to install libpng15 for GMAT to function. Can someone please guide me: 1. Where and how to install libpng15 from? 2. Will I have to remove the already installed version or can they co-exist together?

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

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

1.Do you recomend using sudo apt-get upgrade command before installing Synaptic through terminal?

2.(in the future): Before uninstalling an old module version which was ACTIVE on this kernel, should i manually set it to inactive ? Or ubuntu does this by default with an OK exit in all cases?

3.please observe the 2 errors:

a. Error! Bad return status for module build on kernel
b. error processing package oem

4.whats worse: being a 3rd party, could not report the ,,serious problem”

below, I will post the output of my terminal. Is this normal ?

Setting up   oem-audio-hda-daily-dkms (0.201612080732~ubuntu16.04.1) ...
Removing old oem-audio-hda-daily-0.201612080732~ubuntu16.04.1 DKMS files...

-------- Uninstall Beginning --------
Module:  oem-audio-hda-daily
Version: 0.201612080732~ubuntu16.04.1
Kernel:  4.4.0-23-generic (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
DKMS: uninstall completed.
------------------------------
Deleting module version: 0.201612080732~ubuntu16.04.1
completely from the DKMS tree.
------------------------------
Done.
Loading new oem-audio-hda-daily-0.201612080732~ubuntu16.04.1 DKMS files...
First Installation: checking all kernels...
Building only for 4.4.0-87-generic
Building for architecture x86_64
Building initial module for 4.4.0-87-generic

ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/oem-audio-hda-daily-dkms.0.crash'

Error! Bad return status for module build on kernel: 4.4.0-87-generic (x86_64)

Consult /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/make.log for more information.

dpkg: error processing package oem-audio-hda-daily-dkms (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up sgml-data (2.0.10) ...
Setting up libept1.5.0:amd64 (1.1+nmu3) ...
Setting up librarian0 (0.8.1-6) ...
Setting up synaptic (0.83) ...
Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
Setting up docbook-xml (4.5-7.3) ...
Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
Setting up rarian-compat (0.8.1-6) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Processing triggers for menu (2.1.47ubuntu1) ...
Errors were encountered while processing:
 oem-audio-hda-daily-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

Thanks in advance.

@heynnema ..........

DKMS make.log for oem-audio-hda-daily-0.201612080732~ubuntu16.04.1 for kernel 4.4.0-87-generic (x86_64)
Wednesday 9 August 2017, 16:30:04 +0100
make -C /lib/modules/4.4.0-87-generic/build M=/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build modules
make[1]: Entering directory '/usr/src/linux-headers-4.4.0-87-generic'
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hda_bind.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hda_codec.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hda_jack.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hda_auto_parser.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hda_sysfs.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hda_controller.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hda_proc.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hda_hwdep.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hda_beep.o
  LD [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/snd-hda-codec.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hda_generic.o
  LD [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/snd-hda-codec-generic.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/patch_realtek.o
  LD [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/snd-hda-codec-realtek.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/patch_cmedia.o
  LD [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/snd-hda-codec-cmedia.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/patch_analog.o
  LD [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/snd-hda-codec-analog.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/patch_sigmatel.o
  LD [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/snd-hda-codec-idt.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/patch_si3054.o
  LD [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/snd-hda-codec-si3054.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/patch_cirrus.o
  LD [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/snd-hda-codec-cirrus.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/patch_ca0110.o
  LD [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/snd-hda-codec-ca0110.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/patch_ca0132.o
  LD [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/snd-hda-codec-ca0132.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/patch_conexant.o
  LD [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/snd-hda-codec-conexant.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/patch_via.o
  LD [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/snd-hda-codec-via.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/patch_hdmi.o
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/patch_hdmi.c: In function ‘register_i915_notifier’:
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/patch_hdmi.c:2338:38: warning: assignment from incompatible pointer type [-Wincompatible-pointer-types]
  spec->i915_audio_ops.pin_eld_notify = intel_pin_eld_notify;
                                      ^
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hda_eld.o
  LD [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/snd-hda-codec-hdmi.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hda_intel.o
  LD [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/snd-hda-intel.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hda_bus_type.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_bus.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_device.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_sysfs.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_regmap.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_controller.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_stream.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/array.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdmi_chmap.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/trace.o
  CC [M]  /var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.o
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.c: In function ‘snd_hdac_sync_audio_rate’:
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.c:215:9: error: too few arguments to function ‘acomp->ops->sync_audio_rate’
  return acomp->ops->sync_audio_rate(acomp->dev, port, rate);
         ^
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.c: In function ‘snd_hdac_acomp_get_eld’:
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.c:252:47: warning: passing argument 3 of ‘acomp->ops->get_eld’ makes integer from pointer without a cast [-Wint-conversion]
  return acomp->ops->get_eld(acomp->dev, port, audio_enabled,
                                               ^
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.c:252:47: note: expected ‘int’ but argument is of type ‘bool * {aka _Bool *}’
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.c:253:8: warning: passing argument 4 of ‘acomp->ops->get_eld’ from incompatible pointer type [-Wincompatible-pointer-types]
        buffer, max_bytes);
        ^
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.c:253:8: note: expected ‘bool * {aka _Bool *}’ but argument is of type ‘char *’
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.c:253:16: warning: passing argument 5 of ‘acomp->ops->get_eld’ makes pointer from integer without a cast [-Wint-conversion]
        buffer, max_bytes);
                ^
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.c:253:16: note: expected ‘unsigned char *’ but argument is of type ‘int’
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.c:252:9: error: too few arguments to function ‘acomp->ops->get_eld’
  return acomp->ops->get_eld(acomp->dev, port, audio_enabled,
         ^
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.c: In function ‘snd_hdac_sync_audio_rate’:
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.c:216:1: warning: control reaches end of non-void function [-Wreturn-type]
 }
 ^
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.c: In function ‘snd_hdac_acomp_get_eld’:
/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.c:254:1: warning: control reaches end of non-void function [-Wreturn-type]
 }
 ^
scripts/Makefile.build:258: recipe for target '/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.o' failed
make[3]: *** [/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore/hdac_i915.o] Error 1
scripts/Makefile.build:403: recipe for target '/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore' failed
make[2]: *** [/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build/hdacore] Error 2
Makefile:1420: recipe for target '_module_/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build' failed
make[1]: *** [_module_/var/lib/dkms/oem-audio-hda-daily/0.201612080732~ubuntu16.04.1/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.4.0-87-generic'
Makefile:53: recipe for target 'all' failed
make: *** [all] Error 2

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

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

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

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

Here's the output from xrandr:

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

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

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

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

I'm trying to get an OpenStack Nova compute node running within a container to boot a server in a nested container.

Everything works fine until I ask Nova in the controller to boot the server. During the server boot process in the compute container, libvirt uses qemu-nbd to export the qcow2 disk image downloaded from OpenStack Glance as a previous step to launching the nested container. With the default lxc configuration qemu-nbd fails.

I've worked out the lxc.conf file to allow using qemu-nbd from within the container, but I must be missing something because even if the container activates the node /dev/nbd0 I can't see the /dev/nbd0p1 entry corresponding to the partition in the qcow2 disk image.

Here's the lxc.conf file for my Nova container:

# Template used to create this container: /usr/share/lxc/templates/lxc-download
# Parameters passed to the template: -d ubuntu -r trusty -a i386
# For additional config options, please look at lxc.container.conf(5)

# Distribution configuration
lxc.include = /usr/share/lxc/config/ubuntu.common.conf
lxc.arch = x86

# Container specific configuration
lxc.rootfs = /var/lib/lxc/compute/rootfs
lxc.utsname = compute

# Network configuration
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = lxcbr0
lxc.network.hwaddr = 00:16:3e:90:16:e0

lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br0.1000
lxc.network.hwaddr = 00:16:3e:90:16:e1

# This is the public interface
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br0.2000
lxc.network.hwaddr = 00:16:3e:90:16:e2

# Added so certain functions (iptables, nova-compute, ...) work
lxc.mount.entry = /lib/modules/3.13.0-43-generic     /var/lib/lxc/compute/rootfs/lib/modules/3.13.0-43-generic none ro,bind 0 0

# Added so the compute node can run LXC VMs
lxc.mount.auto = cgroup
lxc.aa_profile = lxc-container-default-with-nesting

# Allow the container to mknod (needed by qemu-nbd...)
lxc.cgroup.devices.allow = c *:* m
lxc.cgroup.devices.allow = b *:* m

# Allow the container to use the host's nbd devices
lxc.cgroup.devices.allow = b 43:* rwm # Every nbd device in the host

It can be verified easily on the command line. Assuming we have the qcow disk image in /root/cirros-0.3.3-i386-disk.img:

root@compute:~# qemu-nbd -c /dev/nbd0 cirros-0.3.3-i386-disk.img -f qcow2
root@compute:~# ls -d /sys/class/block/nbd0p1
/sys/class/block/nbd0  /sys/class/block/ndb0p1
root@compute:~# ls /dev/nbd0*
/dev/nbd0

It seems the block device exists in the kernel, but the /dev/nbd0p1 device node has not been created. Anyone knows what am I missing in my container configuration?

P.S. I know OpenStack Nova by default doesn't work with container VMs, there are some changes I need to do in Nova code; but I need to overcome this hurdle first

I've just installed apache2 on my box, along with php5.

I can navigate to "localhost" and it works. But I can't access this webserver from another machine... or even locally using the IP address. Other posts such as Apache (and other services) work on localhost, but not IP address suggest firewall settings and also checking to make sure I'm listening not just on localhost but *80.

This is what I have in ports.conf:

me@mydev:/etc/apache2$ cat ports.conf 
# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default.conf

Listen 80

<IfModule ssl_module>   Listen 443 </IfModule>

<IfModule mod_gnutls.c>     Listen 443 </IfModule>

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet 

The default firewall doesn't seem to be enabled:

me@mydev:/etc/apache2$ sudo ufw status
[sudo] password for me: 
Status: inactive
me@mydev:/etc/apache2$ 

Just not sure what else I should check. Thanks.

EDIT 1

Results from IP tables query:

me@mydev:/etc/apache2$ sudo iptables -L
[sudo] password for me: 
Chain INPUT (policy ACCEPT) target     prot opt source              
destination         

Chain FORWARD (policy ACCEPT) target     prot opt source              
destination         

Chain OUTPUT (policy ACCEPT) target     prot opt source              
destination
me@mydev:/etc/apache2$

And I am able to successfully ping the box from different machines.

EDIT 2

Here are the results from the nmap command:

me@mydev:/var/www/html/test$ nmap localhost

Starting Nmap 6.40 ( http://nmap.org ) at 2014-12-01 04:04 EST
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00020s latency).
Not shown: 997 closed ports
PORT    STATE SERVICE
22/tcp  open  ssh
80/tcp  open  http
631/tcp open  ipp

Nmap done: 1 IP address (1 host up) scanned in 0.04 seconds
me@mydev:/var/www/html/test$ 

And for the IP:

me@mydev:/var/www/html/test$ nmap 10.238.59.63

Starting Nmap 6.40 ( http://nmap.org ) at 2014-12-01 04:08 EST
Nmap scan report for mydev.testdomain.bg.org (10.238.59.63)
Host is up (0.00024s latency).
Not shown: 998 closed ports
PORT   STATE SERVICE
22/tcp open  ssh
80/tcp open  http

Nmap done: 1 IP address (1 host up) scanned in 0.04 seconds
me@mydev:/var/www/html/test$

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

The hardware is as follows:

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

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

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

I have tried the following with no success:

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

• Editing the boot options in grub and using nomodeset

What can I try next?

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

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

PTY allocation request failed

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

This is the output with -v:

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

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

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

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