When opening and saving files in a Qt application, the app blocks when the file explorer window opens https://askubuntu.com/questions/1564840/when-opening-and-saving-files-in-a-qt-application-the-app-blocks-when-the-file

The file explorer dialog should open without causing the entire application to become unresponsive. The application should remain responsive, aside from the expected modal behavior of the dialog.

Linux/KDE Plasma: Kubuntu 24.04
KDE Plasma Version: 5.27.12
KDE Frameworks Version: 5.115.0

The issue occurs consistently whenever the file explorer dialog is opened.

Sourcing file `/etc/default/grub' /usr/sbin/grub-mkconfig: 42: /etc/default/grub: nvme_core.default_ps_max_latency_us=5500: not found https://askubuntu.com/questions/1564839/sourcing-file-etc-default-grub-usr-sbin-grub-mkconfig-42-etc-default-grub

I installed Ubuntu 24.04 on my Acer laptop. I had to add a parameter to get Ubuntu to recognize my NVMe SSD on boot, but any time I run sudo update-grub or sudo update-grub2, I get this output:

Sourcing file `/etc/default/grub'
/usr/sbin/grub-mkconfig: 42: /etc/default/grub: nvme_core.default_ps_max_latency_us=5500: not found

Does anyone have any idea how to fix this?

System doesn't recognize external hard drive (LaCie) but there is a LaCie file in home that says I am not the owner https://askubuntu.com/questions/1564837/system-doesnt-recognize-external-hard-drive-lacie-but-there-is-a-lacie-file-i

I am very new to Ubuntu and really don't understand much of how this all works, so I apologize if this is a stupid question. I used to be able to back up my files to my external hard drive, but then one day I plugged it in and it said I didn't have permission to modify the files. When I looked online, most solutions suggest this issue is something to do with connecting the hard drive to a windows laptop, which is not the case. The hard drive was used to back up a MacBook in the past, but not recently. The Ubuntu is the only system it has been connected to in months. I've seen some suggestions involving sudo mount but I don't what specifically to do with that and I don't want to screw things up further. I tried lsblk -f but I have no clue what the output means. Here it is in case it's helpful:

$ lsblk -f
NAME FSTYPE FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0
     squash 4.0                                                    0   100% /snap/audacity/1212
loop1
     squash 4.0                                                    0   100% /snap/audacity/1208
loop2
     squash 4.0                                                    0   100% /snap/bare/5
loop3
     squash 4.0                                                    0   100% /snap/thunderbird/1017
loop4
     squash 4.0                                                    0   100% /snap/brave/603
loop5
     squash 4.0                                                    0   100% /snap/brave/604
loop6
     squash 4.0                                                    0   100% /snap/chromium/3369
loop7
     squash 4.0                                                    0   100% /snap/core/17247
loop8
     squash 4.0                                                    0   100% /snap/core/17272
loop9
     squash 4.0                                                    0   100% /snap/core18/2979
loop10
     squash 4.0                                                    0   100% /snap/core18/2999
loop11
     squash 4.0                                                    0   100% /snap/core20/2717
loop12
     squash 4.0                                                    0   100% /snap/core20/2686
loop13
     squash 4.0                                                    0   100% /snap/core22/2339
loop14
     squash 4.0                                                    0   100% /snap/chromium/3375
loop15
     squash 4.0                                                    0   100% /snap/core22/2292
loop16
     squash 4.0                                                    0   100% /snap/core24/1349
loop17
     squash 4.0                                                    0   100% /snap/cups/1142
loop18
     squash 4.0                                                    0   100% /snap/cups/1146
loop19
     squash 4.0                                                    0   100% /snap/digikam/100
loop20
     squash 4.0                                                    0   100% /snap/digikam/101
loop21
     squash 4.0                                                    0   100% /snap/enpass/12
loop22
     squash 4.0                                                    0   100% /snap/ffmpeg-2204/122
loop23
     squash 4.0                                                    0   100% /snap/ffmpeg-2204/126
loop24
     squash 4.0                                                    0   100% /snap/ffmpeg-2404/103
loop25
     squash 4.0                                                    0   100% /snap/ffmpeg-2404/108
loop26
     squash 4.0                                                    0   100% /snap/firefox/7836
loop27
     squash 4.0                                                    0   100% /snap/firefox/7869
loop28
     squash 4.0                                                    0   100% /snap/gimp/550
loop29
     squash 4.0                                                    0   100% /snap/gimp/552
loop30
     squash 4.0                                                    0   100% /snap/gnome-3-28-1804/198
loop31
     squash 4.0                                                    0   100% /snap/gnome-3-34-1804/90
loop32
     squash 4.0                                                    0   100% /snap/gnome-3-34-1804/93
loop35
     squash 4.0                                                    0   100% /snap/gnome-42-2204/226
loop36
     squash 4.0                                                    0   100% /snap/gnome-42-2204/247
loop37
     squash 4.0                                                    0   100% /snap/gnome-46-2404/145
loop38
     squash 4.0                                                    0   100% /snap/gnome-46-2404/153
loop39
     squash 4.0                                                    0   100% /snap/gtk2-common-themes/13
loop40
     squash 4.0                                                    0   100% /snap/gtk-common-themes/1535
loop41
     squash 4.0                                                    0   100% /snap/kf5-5-108-qt-5-15-10-core22/5
loop42
     squash 4.0                                                    0   100% /snap/hunspell-dictionaries/21
loop43
     squash 4.0                                                    0   100% /snap/kf6-core22/42
loop44
     squash 4.0                                                    0   100% /snap/kf6-core22/43
loop45
     squash 4.0                                                    0   100% /snap/kf6-core24/34
loop46
     squash 4.0                                                    0   100% /snap/kf6-core24/36
loop47
     squash 4.0                                                    0   100% /snap/mesa-2404/1165
loop48
     squash 4.0                                                    0   100% /snap/mesa-2404/912
loop49
     squash 4.0                                                    0   100% /snap/qt-common-themes/8
loop50
     squash 4.0                                                    0   100% /snap/qt-common-themes/10
loop51
     squash 4.0                                                    0   100% /snap/snap-store/1113
loop52
     squash 4.0                                                    0   100% /snap/snap-store/1216
loop53
     squash 4.0                                                    0   100% /snap/snapd/25577
loop54
     squash 4.0                                                    0   100% /snap/snapd/25935
loop55
     squash 4.0                                                    0   100% /snap/snapd-desktop-integration/315
loop56
     squash 4.0                                                    0   100% /snap/snapd-desktop-integration/343
loop57
     squash 4.0                                                    0   100% /snap/teams-for-linux/1392
loop58
     squash 4.0                                                    0   100% /snap/teams-for-linux/1499
loop59
     squash 4.0                                                    0   100% /snap/vlc/3777
loop60
     squash 4.0                                                    0   100% /snap/core24/1499
loop61
     squash 4.0                                                    0   100% /snap/firmware-updater/216
sda                                                                         
├─sda1
│    vfat   FAT32       3491-A7AE                             459.3M    10% /boot/efi
└─sda2
     ext4   1.0         7abab72c-e0df-4b5c-aead-f72af7cb0ff7   56.4G    70% /var/snap/firefox/common/host-hunspell

LaCie file permissions:

LaCie file permissions

How do I begin to solve this issue?

EDIT: Here is the output to sudo fdisk -l && udisksctl status

Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 611.95 MiB, 641679360 bytes, 1253280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 617.38 MiB, 647364608 bytes, 1264384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 180.89 MiB, 189681664 bytes, 370472 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 197.32 MiB, 206905344 bytes, 404112 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 180.98 MiB, 189771776 bytes, 370648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop7: 104.23 MiB, 109289472 bytes, 213456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: WDC  WDS250G2B0A
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D13A4908-1868-4D16-94EA-7FC7C69C0EA6

Device       Start       End   Sectors   Size Type
/dev/sda1     2048   1050623   1048576   512M EFI System
/dev/sda2  1050624 488396799 487346176 232.4G Linux filesystem


Disk /dev/loop8: 104.98 MiB, 110080000 bytes, 215000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop9: 55.49 MiB, 58187776 bytes, 113648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop10: 55.49 MiB, 58183680 bytes, 113640 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop11: 63.77 MiB, 66871296 bytes, 130608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop12: 63.77 MiB, 66871296 bytes, 130608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop13: 73.95 MiB, 77545472 bytes, 151456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop14: 73.96 MiB, 77549568 bytes, 151464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop15: 66.85 MiB, 70098944 bytes, 136912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop16: 66.83 MiB, 70078464 bytes, 136872 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop17: 48.82 MiB, 51187712 bytes, 99976 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop18: 47.59 MiB, 49897472 bytes, 97456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop19: 226.74 MiB, 237752320 bytes, 464360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop20: 222.66 MiB, 233480192 bytes, 456016 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop21: 32.39 MiB, 33964032 bytes, 66336 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop22: 62.16 MiB, 65175552 bytes, 127296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop23: 62.16 MiB, 65175552 bytes, 127296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop24: 82.13 MiB, 86114304 bytes, 168192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop25: 96.42 MiB, 101101568 bytes, 197464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop26: 254.56 MiB, 266928128 bytes, 521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop27: 251.64 MiB, 263868416 bytes, 515368 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop28: 16.45 MiB, 17244160 bytes, 33680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop30: 137.23 MiB, 143896576 bytes, 281048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop31: 164.82 MiB, 172830720 bytes, 337560 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop32: 218.39 MiB, 228999168 bytes, 447264 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop33: 218.39 MiB, 228999168 bytes, 447264 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop34: 531.38 MiB, 557187072 bytes, 1088256 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop35: 516.2 MiB, 541278208 bytes, 1057184 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop36: 606.08 MiB, 635518976 bytes, 1241248 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop37: 669.79 MiB, 702320640 bytes, 1371720 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop38: 140 KiB, 143360 bytes, 280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop39: 91.69 MiB, 96141312 bytes, 187776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop40: 450.15 MiB, 472018944 bytes, 921912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop41: 32.07 MiB, 33632256 bytes, 65688 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop42: 2.03 GiB, 2182340608 bytes, 4262384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


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


Disk /dev/loop44: 2.02 GiB, 2166636544 bytes, 4231712 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop45: 1.41 GiB, 1515048960 bytes, 2959080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop46: 394.98 MiB, 414167040 bytes, 808920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop47: 290.77 MiB, 304898048 bytes, 595504 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop48: 188.02 MiB, 197152768 bytes, 385064 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop49: 188.02 MiB, 197152768 bytes, 385064 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop50: 12.93 MiB, 13553664 bytes, 26472 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop51: 12.2 MiB, 12791808 bytes, 24984 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop52: 50.93 MiB, 53399552 bytes, 104296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop53: 48.09 MiB, 50421760 bytes, 98480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop55: 576 KiB, 589824 bytes, 1152 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop54: 139.91 MiB, 146702336 bytes, 286528 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop56: 576 KiB, 589824 bytes, 1152 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop57: 107.25 MiB, 112459776 bytes, 219648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop58: 227.47 MiB, 238518272 bytes, 465856 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop59: 321.1 MiB, 336699392 bytes, 657616 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop60: 107.28 MiB, 112488448 bytes, 219704 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop61: 197.3 MiB, 206888960 bytes, 404080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
MODEL                     REVISION  SERIAL               DEVICE
--------------------------------------------------------------------------
WDC  WDS250G2B0A-00SM50   401000WD  19197F801218         sda 
Ubuntu 24.04 update fails with Kernel panic VFS: Unable to mount root fs on unknown-block(0,0) https://askubuntu.com/questions/1564834/ubuntu-24-04-update-fails-with-kernel-panic-vfs-unable-to-mount-root-fs-on-unkn

after running regular update cycle vie GUI updater, system halts while booting with Kernel panic

VFS: Unable to mount root fs on unknown-block(0,0)

I was able to get the system booting using the recovery console of one of the older Kernel entries.Then I issued:

ls -all /boot
update-initramfs -c -k 6.17.0-19-generic
update-grub

Next reboot was ok.

Another attempt to update with:

sudo apt update
sudo apt upgrade

failed, again.

So I tried:

sudo apt autoremove

which came out:

apt autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  libnvidia-compute-550 nvidia-firmware-580-580.95.05
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 105 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 273996 files and directories currently installed.)
Removing libnvidia-compute-550:amd64 (550.163.01-0ubuntu0.24.04.2) ...
Removing nvidia-firmware-580-580.95.05 (580.95.05-0ubuntu0.24.04.3) ...
Setting up linux-image-6.17.0-19-generic (6.17.0-19.19~24.04.2) ...
Setting up linux-headers-6.17.0-19-generic (6.17.0-19.19~24.04.2) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.17.0-19-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 -j8 KERNELRELEASE=6.17.0-19-generic -j8 -C /lib/modules/6.17.0-19-generic/build M=/var/lib/dkms/blksnap/6.3.2.1207/build modules...(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/blksnap.0.crash'
Error! Bad return status for module build on kernel: 6.17.0-19-generic (x86_64)
Consult /var/lib/dkms/blksnap/6.3.2.1207/build/make.log for more information.
dkms autoinstall on 6.17.0-19-generic/x86_64 failed for blksnap(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-19-generic
   ...fail!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
dpkg: error processing package linux-headers-6.17.0-19-generic (--configure):
 installed linux-headers-6.17.0-19-generic package post-installation script subprocess returned error exit status 11
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          No apport report written because the error message indicates it
s a followup error from a previous failure.
                                           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-19-generic; however:
  Package linux-headers-6.17.0-19-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-19.19~24.04.2); 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-19-generic (6.17.0-19.19~24.04.2) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 6.17.0-19-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 -j8 KERNELRELEASE=6.17.0-19-generic -j8 -C /lib/modules/6.17.0-19-generic/build M=/var/lib/dkms/blksnap/6.3.2.1207/build modules...(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/blksnap.0.crash'
Error! Bad return status for module build on kernel: 6.17.0-19-generic (x86_64)
Consult /var/lib/dkms/blksnap/6.3.2.1207/build/make.log for more information.
dkms autoinstall on 6.17.0-19-generic/x86_64 failed for blksnap(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-19-generic
   ...fail!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.17.0-19-generic (--configure):
 installed linux-image-6.17.0-19-generic package post-installation script subprocess returned error exit status 11
No apport report written because MaxReports is reached already
                                                              Errors were encountered while processing:
 linux-headers-6.17.0-19-generic
 linux-headers-generic-hwe-24.04
 linux-generic-hwe-24.04
 linux-image-6.17.0-19-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

In this error messages I found the note to consult make.log:

cat /var/lib/dkms/blksnap/6.3.2.1207/build/make.log
DKMS make.log for blksnap-6.3.2.1207 for kernel 6.17.0-19-generic (x86_64)
Sat Mar 14 10:02:14 PM CET 2026
make: Entering directory '/usr/src/linux-headers-6.17.0-19-generic'
make[1]: Entering directory '/var/lib/dkms/blksnap/6.3.2.1207/build'
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.1) 13.3.0
  You are using:           gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0
  CC [M]  bdevfilter.o
  CC [M]  log.o
  CC [M]  log_histogram.o
  CC [M]  big_buffer.o
  CC [M]  cbt_map.o
  CC [M]  chunk.o
  CC [M]  ctrl.o
  CC [M]  diff_io.o
cbt_map.c:7:10: fatal error: linux/blk_snap.h: No such file or directory
    7 | #include <linux/blk_snap.h>
      |          ^~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [/usr/src/linux-headers-6.17.0-19-generic/scripts/Makefile.build:287: cbt_map.o] Error 1
make[3]: *** Waiting for unfinished jobs....
ctrl.c:11:10: fatal error: linux/blk_snap.h: No such file or directory
   11 | #include <linux/blk_snap.h>
      |          ^~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [/usr/src/linux-headers-6.17.0-19-generic/scripts/Makefile.build:287: ctrl.o] Error 1
log.c:11:10: fatal error: linux/blk_snap.h: No such file or directory
   11 | #include <linux/blk_snap.h>
      |          ^~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [/usr/src/linux-headers-6.17.0-19-generic/scripts/Makefile.build:287: log.o] Error 1
chunk.c:21:24: error: redefinition of ‘bdev_nr_sectors’
   21 | static inline sector_t bdev_nr_sectors(struct block_device *bdev)
      |                        ^~~~~~~~~~~~~~~
In file included from chunk.h:6,
                 from chunk.c:8:
/usr/src/linux-headers-6.17.0-19-generic/include/linux/blkdev.h:824:24: note: previous definition of ‘bdev_nr_sectors’ with type ‘sector_t(struct block_device *)’ {aka ‘long long unsigned int(struct block_device *)’}
  824 | static inline sector_t bdev_nr_sectors(struct block_device *bdev)
      |                        ^~~~~~~~~~~~~~~
chunk.c: In function ‘bdev_nr_sectors’:
chunk.c:23:32: error: ‘struct block_device’ has no member named ‘bd_inode’
   23 |         return i_size_read(bdev->bd_inode) >> 9;
      |                                ^~
diff_io.c: In function ‘diff_io_do’:
diff_io.c:180:40: warning: passing argument 1 of ‘bio_alloc_bioset’ makes pointer from integer without a cast [-Wint-conversion]
  180 |                 bio = bio_alloc_bioset(gfp, nr_iovecs, &diff_io_bioset);
      |                                        ^~~
      |                                        |
      |                                        gfp_t {aka unsigned int}
In file included from /usr/src/linux-headers-6.17.0-19-generic/include/linux/blkdev.h:17,
                 from diff_io.c:6:
/usr/src/linux-headers-6.17.0-19-generic/include/linux/bio.h:356:51: note: expected ‘struct block_device *’ but argument is of type ‘gfp_t’ {aka ‘unsigned int’}
  356 | struct bio *bio_alloc_bioset(struct block_device *bdev, unsigned short nr_vecs,
      |                              ~~~~~~~~~~~~~~~~~~~~~^~~~
diff_io.c:180:56: warning: passing argument 3 of ‘bio_alloc_bioset’ makes integer from pointer without a cast [-Wint-conversion]
  180 |                 bio = bio_alloc_bioset(gfp, nr_iovecs, &diff_io_bioset);
      |                                                        ^~~~~~~~~~~~~~~
      |                                                        |
      |                                                        struct bio_set *
/usr/src/linux-headers-6.17.0-19-generic/include/linux/bio.h:357:40: note: expected ‘blk_opf_t’ {aka ‘unsigned int’} but argument is of type ‘struct bio_set *’
  357 |                              blk_opf_t opf, gfp_t gfp_mask,
      |                              ~~~~~~~~~~^~~
diff_io.c:180:23: error: too few arguments to function ‘bio_alloc_bioset’
  180 |                 bio = bio_alloc_bioset(gfp, nr_iovecs, &diff_io_bioset);
      |                       ^~~~~~~~~~~~~~~~
/usr/src/linux-headers-6.17.0-19-generic/include/linux/bio.h:356:13: note: declared here
  356 | struct bio *bio_alloc_bioset(struct block_device *bdev, unsigned short nr_vecs,
      |             ^~~~~~~~~~~~~~~~
chunk.c: In function ‘chunk_store_failed’:
chunk.c:80:17: error: implicit declaration of function ‘LIMIT_BEGIN’ [-Werror=implicit-function-declaration]
   80 |                 LIMIT_BEGIN(7)
      |                 ^~~~~~~~~~~
In file included from /usr/src/linux-headers-6.17.0-19-generic/include/asm-generic/bug.h:22,
                 from /usr/src/linux-headers-6.17.0-19-generic/arch/x86/include/asm/bug.h:103,
                 from /usr/src/linux-headers-6.17.0-19-generic/arch/x86/include/asm/alternative.h:9,
                 from /usr/src/linux-headers-6.17.0-19-generic/arch/x86/include/asm/nospec-branch.h:10,
                 from /usr/src/linux-headers-6.17.0-19-generic/arch/x86/include/asm/irqflags.h:9,
                 from /usr/src/linux-headers-6.17.0-19-generic/include/linux/irqflags.h:18,
                 from /usr/src/linux-headers-6.17.0-19-generic/include/linux/spinlock.h:59,
                 from /usr/src/linux-headers-6.17.0-19-generic/include/linux/mmzone.h:8,
                 from /usr/src/linux-headers-6.17.0-19-generic/include/linux/gfp.h:7,
                 from /usr/src/linux-headers-6.17.0-19-generic/include/linux/slab.h:16,
                 from chunk.c:3:
/usr/src/linux-headers-6.17.0-19-generic/include/linux/printk.h:484:10: error: expected expression before ‘{’ token
  484 |         ({                                                              \
      |          ^
/usr/src/linux-headers-6.17.0-19-generic/include/linux/printk.h:514:26: note: in expansion of macro ‘printk_index_wrap’
  514 | #define printk(fmt, ...) printk_index_wrap(_printk, fmt, ##__VA_ARGS__)
      |                          ^~~~~~~~~~~~~~~~~
/usr/src/linux-headers-6.17.0-19-generic/include/linux/printk.h:557:9: note: in expansion of macro ‘printk’
  557 |         printk(KERN_ERR pr_fmt(fmt), ##__VA_ARGS__)
      |         ^~~~~~
chunk.c:81:17: note: in expansion of macro ‘pr_err’
   81 |                 pr_err("Failed to store chunk #%lu\n", chunk->number);
      |                 ^~~~~~
chunk.c:80:17: error: called object is not a function or function pointer
   80 |                 LIMIT_BEGIN(7)
      |                 ^~~~~~~~~~~
chunk.c:82:17: error: implicit declaration of function ‘LIMIT_STOP’; did you mean ‘RLIMIT_STACK’? [-Werror=implicit-function-declaration]
   82 |                 LIMIT_STOP()
      |                 ^~~~~~~~~~
      |                 RLIMIT_STACK
/usr/src/linux-headers-6.17.0-19-generic/include/linux/printk.h:484:10: error: expected expression before ‘{’ token
  484 |         ({                                                              \
      |          ^
/usr/src/linux-headers-6.17.0-19-generic/include/linux/printk.h:514:26: note: in expansion of macro ‘printk_index_wrap’
  514 | #define printk(fmt, ...) printk_index_wrap(_printk, fmt, ##__VA_ARGS__)
      |                          ^~~~~~~~~~~~~~~~~
/usr/src/linux-headers-6.17.0-19-generic/include/linux/printk.h:557:9: note: in expansion of macro ‘printk’
  557 |         printk(KERN_ERR pr_fmt(fmt), ##__VA_ARGS__)
      |         ^~~~~~
chunk.c:83:17: note: in expansion of macro ‘pr_err’
   83 |                 pr_err("Too many chunk have failed, stop flooding\n");
      |                 ^~~~~~
chunk.c:82:17: error: called object is not a function or function pointer
   82 |                 LIMIT_STOP()
      |                 ^~~~~~~~~~
chunk.c:84:17: error: implicit declaration of function ‘LIMIT_END’ [-Werror=implicit-function-declaration]
   84 |                 LIMIT_END()
      |                 ^~~~~~~~~
chunk.c:84:28: error: expected ‘;’ before ‘diff_area_set_corrupted’
   84 |                 LIMIT_END()
      |                            ^
      |                            ;
   85 |                 diff_area_set_corrupted(diff_area, error);
      |                 ~~~~~~~~~~~~~~~~~~~~~~~
diff_io.c:191:17: error: implicit declaration of function ‘bio_set_op_attrs’ [-Werror=implicit-function-declaration]
  191 |                 bio_set_op_attrs(bio, opf, op_flags);
      |                 ^~~~~~~~~~~~~~~~
chunk.c: In function ‘bdev_nr_sectors’:
chunk.c:24:1: error: control reaches end of non-void function [-Werror=return-type]
   24 | };
      | ^
cc1: some warnings being treated as errors
diff_io.c:223:17: error: implicit declaration of function ‘io_set_flag’; did you mean ‘bio_set_flag’? [-Werror=implicit-function-declaration]
  223 |                 io_set_flag(bio, BIO_FILTERED);
      |                 ^~~~~~~~~~~
      |                 bio_set_flag
make[3]: *** [/usr/src/linux-headers-6.17.0-19-generic/scripts/Makefile.build:287: chunk.o] Error 1
diff_io.c:223:34: error: ‘BIO_FILTERED’ undeclared (first use in this function)
  223 |                 io_set_flag(bio, BIO_FILTERED);
      |                                  ^~~~~~~~~~~~
diff_io.c:223:34: note: each undeclared identifier is reported only once for each function it appears in
bdevfilter.c:372:2: error: #error "Your kernel is too old for this module."
  372 | #error "Your kernel is too old for this module."
      |  ^~~~~
cc1: some warnings being treated as errors
bdevfilter.c:374:1: error: expected identifier or ‘(’ before ‘{’ token
  374 | {
      | ^
make[3]: *** [/usr/src/linux-headers-6.17.0-19-generic/scripts/Makefile.build:287: diff_io.o] Error 1
In file included from /usr/src/linux-headers-6.17.0-19-generic/include/linux/linkage.h:7,
                 from /usr/src/linux-headers-6.17.0-19-generic/include/linux/printk.h:8,
                 from /usr/src/linux-headers-6.17.0-19-generic/include/asm-generic/bug.h:22,
                 from /usr/src/linux-headers-6.17.0-19-generic/arch/x86/include/asm/bug.h:103,
                 from /usr/src/linux-headers-6.17.0-19-generic/arch/x86/include/asm/alternative.h:9,
                 from /usr/src/linux-headers-6.17.0-19-generic/arch/x86/include/asm/barrier.h:5,
                 from /usr/src/linux-headers-6.17.0-19-generic/include/linux/list.h:11,
                 from /usr/src/linux-headers-6.17.0-19-generic/include/linux/module.h:12,
                 from bdevfilter.c:3:
bdevfilter.c:381:15: error: ‘submit_bio_noacct_notrace’ undeclared here (not in a function); did you mean ‘submit_bio_noacct’?
  381 | EXPORT_SYMBOL(submit_bio_noacct_notrace);
      |               ^~~~~~~~~~~~~~~~~~~~~~~~~
/usr/src/linux-headers-6.17.0-19-generic/include/linux/export.h:76:23: note: in definition of macro ‘__EXPORT_SYMBOL’
   76 |         extern typeof(sym) sym;                                 \
      |                       ^~~
/usr/src/linux-headers-6.17.0-19-generic/include/linux/export.h:89:41: note: in expansion of macro ‘_EXPORT_SYMBOL’
   89 | #define EXPORT_SYMBOL(sym)              _EXPORT_SYMBOL(sym, "")
      |                                         ^~~~~~~~~~~~~~
bdevfilter.c:381:1: note: in expansion of macro ‘EXPORT_SYMBOL’
  381 | EXPORT_SYMBOL(submit_bio_noacct_notrace);
      | ^~~~~~~~~~~~~
bdevfilter.c:389:1: error: expected identifier or ‘(’ before ‘{’ token
  389 | {
      | ^
bdevfilter.c: In function ‘ftrace_handler_submit_bio_noacct’:
bdevfilter.c:420:62: error: ‘submit_bio_noacct_handler’ undeclared (first use in this function); did you mean ‘submit_bio_noacct_notrace’?
  420 |                 instruction_pointer_set(regs, (unsigned long)submit_bio_noacct_handler);
      |                                                              ^~~~~~~~~~~~~~~~~~~~~~~~~
      |                                                              submit_bio_noacct_notrace
bdevfilter.c:420:62: note: each undeclared identifier is reported only once for each function it appears in
bdevfilter.c: At top level:
bdevfilter.c:426:17: error: initialization of ‘void (*)(long unsigned int,  long unsigned int,  struct ftrace_ops *, struct ftrace_regs *)’ from incompatible pointer type ‘void (*)(long unsigned int,  long unsigned int,  struct ftrace_ops *, struct pt_regs *)’ [-Werror=incompatible-pointer-types]
  426 |         .func = ftrace_handler_submit_bio_noacct,
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bdevfilter.c:426:17: note: (near initialization for ‘ops_submit_bio_noacct.func’)
cc1: some warnings being treated as errors
make[3]: *** [/usr/src/linux-headers-6.17.0-19-generic/scripts/Makefile.build:287: bdevfilter.o] Error 1
make[2]: *** [/usr/src/linux-headers-6.17.0-19-generic/Makefile:2016: .] Error 2
make[1]: *** [/usr/src/linux-headers-6.17.0-19-generic/Makefile:248: __sub-make] Error 2
make[1]: Leaving directory '/var/lib/dkms/blksnap/6.3.2.1207/build'
make: *** [Makefile:248: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-6.17.0-19-generic'

Now here I got lost, its beyond my knowledge.
Any help appreciated.

Wifi drivers on an older MacBook Pro https://askubuntu.com/questions/1564830/wifi-drivers-on-an-older-macbook-pro

this is a bit long but I think it may be helpful to others.

I recently installed Ubuntu 24.04.1 on an older MacBook (1911-1912 with a Broadcom BCM4331 WiFi) and was impressed that everything worked perfectly from the get go. Being a newbie to Linux I eventually messed things up and had to reinstall a few times. The second install the WiFi would not work no matter what I tried. On a subsequent install the automatically installed drivers worked again. then on the final (current) install they initially would not work.

I tried pretty much all the suggestions from googling the problem including:

sudo apt update
sudo apt purge bcmwl-kernel-source
sudo apt install firmware-b43-installer

...but I could not get it to work.

I finally tripped over the following set of instructions on a Mint distro page:

cd /tmp
wget https://archive.ubuntu.com/ubuntu/pool/restricted/b/broadcom-sta/broadcom-sta-dkms_6.30.223.271-23ubuntu1.2_all.deb
sudo apt install ./broadcom-sta-dkms_6.30.223.271-23ubuntu1.2_all.deb

This worked and I am now on WiFi. I hope this is helpful to others, but my question is: How is the last set of instructions different from the: firmware-b43-installer, and would there have been an easier way to find the correct driver than the hit or miss approach?

Wine is already installed, but wine32 is missing? [duplicate] https://askubuntu.com/questions/1564825/wine-is-already-installed-but-wine32-is-missing

Look at the last two messages of the terminal. It says Wine is installed, but also that wine32 is missing. What does this mean? How can I fix it?

doesn't support architecture 'I386'
N: Skipping acquire of configured file 'restricted/binary-I386/Packages' as 
repository 'http://security.ubuntu.com/ubuntu noble-security InRelease' doesn't support architecture 'I386'
N: Skipping acquire of configured file 'universe/binary-I386/Packages' as 
repository 'http://security.ubuntu.com/ubuntu noble-security InRelease' doesn't support architecture 'I386'
N: Skipping acquire of configured file 'multiverse/binary-I386/Packages' as 
repository 'http://security.ubuntu.com/ubuntu noble-security InRelease' doesn't support architecture 'I386'
xeqxz@eirik-og-petras-pc:~$ sudo apt install wine
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
wine is already the newest version (9.0~repack-4build3).
The following package was automatically installed and is no longer required:
  libllvm19
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 95 not upgraded.
xeqxz@eirik-og-petras-pc:~$ wine --version
it looks like wine32 is missing, you should install it.
as root, please execute "apt-get install wine32:i386"
wine-9.0 (Ubuntu 9.0~repack-4build3)
xeqxz@eirik-og-petras-pc:~$

I'm new to Linux. I'm trying to run a Windows .exe file to play a game.

OneDrive crashing https://askubuntu.com/questions/1564822/onedrive-crashing

I linked my onedrive and google drive account via gnome from settings. Gdrive works well but when i open the onedrive folder and then try to open a folder in it, it loads for a bit then it crashes and shows connection lost error. I am dual booting with windows enter image description here

How is it possible that ubuntu 22.04 use an older glibc version than the Debian version it's based on? https://askubuntu.com/questions/1564816/how-is-it-possible-that-ubuntu-22-04-use-an-older-glibc-version-than-the-debian

I'm rather beginner with c++ development and could not find an answer to this question.

I wanted to compile on Debian 12 (oldest lts) to make sure that all downstream distros could run my little tool.
But I realized that Debian 12 uses glibc 2.36 and Ubuntu 22.04 which is suposed to be based on Debian 12 uses glibc 2.35 ? an older version ?

I don't understand how this can be ? I assumed that ubuntu would always be one or two version newer than it's base depending on the release.
Does that kind of version difference (older than base) happen often ?

Thanks !

Why did ubuntu switch from gnu-coreutils to uutils https://askubuntu.com/questions/1564801/why-did-ubuntu-switch-from-gnu-coreutils-to-uutils

When I see a stable, well-accepted package like coreutils get removed, my initial reaction is something of shock. However, I know the danger of "speaking without knowledge" to use the biblical wording, and that the Ubuntu people know way more about this than I do, but:

Why did the Ubuntu team want to change from coreutils to uutils?

I know there's a big push for "safer" languages like rust right now, is simply that the reason? or is there a more complex reason? It seems like a mature project like coreutils would no longer have any memory leaks or similar errors that might make the Ubuntu team have second thoughts about using it. So, why?

Just a note for those who don't know, this is not in an LTS release yet, just in intern releases.

Browsers and programmes not connecting or opening Web pages & Proton VPN not connecting [closed] https://askubuntu.com/questions/1564797/browsers-and-programmes-not-connecting-or-opening-web-pages-proton-vpn-not-con

Ubuntu system 24.04.3 LTS

My wi-fi Internet connection is strong. However..... Recently all of my browsers (TOR, Millard, Firefox) decided not to open any page links and have the error message: 'hmm. We're having trouble finding that site. We can't connect to the server at xxxxx' 'if you entered the correct address you can try again later, check network connection, check Firefox has permission to access the Web (you might be behind a firewall)'.

The software updater has the error message: 'Failed to download repository information' or 'failed to download package files'. 'Check your Internet connection'.

Proton VPN has the 'loading app' message but the circle just keeps going around and won't connect.

I am a complete novice with trying to sort this type of technical issue so any help will be gratefully received!

; <<>> DiG 9.18.39-0ubuntu0.24.04.2-Ubuntu <<>> example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 40285
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;example.com.           IN  A

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Fri Mar 13 19:56:23 GMT 2026
;; MSG SIZE  rcvd: 40

Command "ip" is unknown, try "ip address help".

;  (1 server found)
;; global options: +cmd
;; no servers could be reached

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3073mšs

Although I'm sure I ran the original command correctly, I just re-ran it and got the following result:

; <<>> DiG 9.18.39-0ubuntu0.24.04.2-Ubuntu <<>> example.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44967
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;example.com.           IN  A

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Sat Mar 14 16:37:27 GMT 2026
;; MSG SIZE  rcvd: 40

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute 
       valid_lft forever preferred_lft forever
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 1c:75:08:05:25:00 brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 5c:ac:4c:32:fb:27 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.194/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp2s0
       valid_lft 81248sec preferred_lft 81248sec
    inet6 2a00:23c7:345b:b801:7916:aa72:6e69:f23b/64 scope global temporary dynamic 
       valid_lft 299sec preferred_lft 119sec
    inet6 2a00:23c7:345b:b801:6f1:5204:5b7a:7944/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 299sec preferred_lft 119sec
    inet6 fe80::715:23c5:ea79:58e4/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: pvpnksintrf1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether e6:29:5e:70:19:54 brd ff:ff:ff:ff:ff:ff
    inet 100.85.0.1/24 brd 100.85.0.255 scope global noprefixroute pvpnksintrf1
       valid_lft forever preferred_lft forever
    inet6 fdeb:446c:912d:8da::/64 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::7ede:34b5:3a54:64ab/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
default via 100.85.0.1 dev pvpnksintrf1 proto static metric 98 
default via 192.168.1.254 dev wlp2s0 proto dhcp src 192.168.1.194 metric 600 
100.85.0.0/24 dev pvpnksintrf1 proto kernel scope link src 100.85.0.1 metric 98 
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.194 metric 600
Wifi not working because of missing firmware https://askubuntu.com/questions/1564770/wifi-not-working-because-of-missing-firmware

After I did a update of my Ubuntu 25.10 the wifi stopped working. I have tried reinstalling but when I did a update the wifi stopped working again. I am using TPM encryption on my disk.

The PC is a Dell Precision 7680.

I found that sudo dmesg | grep wifi shows

[    9.903015] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-89.ucode failed with error -2
[    9.903028] iwlwifi 0000:00:14.3: no suitable firmware found!
[    9.906650] iwlwifi 0000:00:14.3: iwlwifi-so-a0-gf-a0-89 is required
[    9.911118] iwlwifi 0000:00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

So the iwlwifi-so-a0-gf-a0-89 is missing and I guess this should be part of linux-firmware.

When I do sudo apt install linux-firmware I get

Solving dependencies... Error!  
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
 boot-managed-by-snapd : Conflicts: linux-firmware but 20250901.git993ff19b-0ubuntu1.9 is to be installed

Cannot install linux-firmware on system as boot is managed by snapd.
Error: Unable to satisfy dependencies. Reached two conflicting decisions:
   1. linux-firmware:amd64=20250901.git993ff19b-0ubuntu1.9 is selected for install
   2. linux-firmware:amd64=20250901.git993ff19b-0ubuntu1.9 is not selected for install because:
      1. boot-managed-by-snapd:amd64 is selected for install
      2. boot-managed-by-snapd:amd64 Conflicts linux-firmware
         [selected boot-managed-by-snapd:amd64]

How can I solve this dependency error ?

Update

I have tried reinstalling again and the wifi works in the installer but once I boot the installed OS it stops working.

I am also using Secure Boot and here is the output from some typical diagnostic commands:

$ lspci -nnk | grep -A2 0280
0000:00:14.3 Network controller [0280]: Intel Corporation Raptor Lake-S PCH CNVi WiFi [8086:7a70] (rev 11)
    Subsystem: Intel Corporation Device [8086:4090]
    Kernel modules: iwlwifi
$ lspci | grep -i network
0000:00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi (rev 11)
$ lsmod | grep iwlwifi
iwlwifi               651264  0
cfg80211             1474560  1 iwlwifi
$ sudo dmesg | grep iwl
[    8.438932] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[    8.444539] iwlwifi 0000:00:14.3: Detected crf-id 0x400410, cnv-id 0x80401 wfpm id 0x80000020
[    8.444564] iwlwifi 0000:00:14.3: PCI dev 7a70/4090, rev=0x430, rfid=0x2010d000
[    8.444566] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz
[    8.444606] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-89.ucode failed with error -2
[    8.444608] iwlwifi 0000:00:14.3: no suitable firmware found!
[    8.446252] iwlwifi 0000:00:14.3: iwlwifi-so-a0-gf-a0-89 is required
[    8.447179] iwlwifi 0000:00:14.3: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
$ rfkill list && iwconfig
1: dell-wifi: Wireless LAN
    Soft blocked: no
    Hard blocked: no
2: dell-bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no
3: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
Command 'iwconfig' not found, did you mean:
  command 'iconfig' from deb ipmiutil (3.2.1-1)
  command 'ifconfig' from deb net-tools (2.10-1.3ubuntu2)
Try: sudo apt install <deb name>
$ modinfo iwlwifi|grep -i sign
signer:         Build time autogenerated kernel key
signature:      72:E4:0A:69:D0:09:3B:A6:12:F8:65:1D:D9:F5:67:9D:D2:29:24:0E:

Update 2

$ uname -a
Linux KN-Home 6.17.0-5-generic #5-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 22 10:00:33 UTC 2025 x86_64 GNU/Linux
$ snap list pc-kernel
Name       Version     Rev   Tracking      Publisher   Notes
pc-kernel  6.17.0-5.5  2852  25.10/stable  canonical✓  kernel

I tries to do a snap refresh after the above and then I got a new version but Wifi is still not working.

$ snap list pc-kernel
Name       Version       Rev   Tracking      Publisher   Notes
pc-kernel  6.17.0-14.14  3140  25.10/stable  canonical✓  kernel

Update 3

Finally got the wifi to work by downloading two files and putting them in /lib/firmware/. Like this:

git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
sudo cp ./linux-firmware/intel/iwlwifi/iwlwifi-so-a0-gf-a0-89.ucode /lib/firmware/
sudo cp ./linux-firmware/intel/iwlwifi/iwlwifi-so-a0-gf-a0.pnvm /lib/firmware/

Before doing the above solution I tried updating pc-kernel to both candidate (6.17.0-16.16) and beta (6.17.0-19.19) channel but this did not work and I reverted back to the stable channel.

I would like to know where would I normally have had these files ? Should they have been part of pc-kernel and where would the files have been in that case ? Right now I guess they will not be updated automatically so it is still a temporary fix.

Thanks

Latest Kernel 6.19.0-9 and latest Nvidia driver suspend throws kernel panic https://askubuntu.com/questions/1564763/latest-kernel-6-19-0-9-and-latest-nvidia-driver-suspend-throws-kernel-panic

When my laptop resumes I'm greeted with a kernel error and a locked up laptop (have to hold the power button for 10 seconds), lots of stuff on the screen. I found this is in syslog, after the clip line it matches pretty close to what was on the screen except for the stack trace. 6.18.0-9 worked fine. I don't know what the version of Nvidia driver was installed unfortunately. And the 6.18 kernel is no longer in the default apt repositories so going back isn't much of an options. It references what I assume is the Nvidia driver so my guess is it's something in there but I have no idea where to go next, other than this site to ask.

A lot of these

2026-03-11T17:47:20.363906-06:00 edslaptop gnome-shell[6360]: (../src/backends/native/meta-onscreen-native.c:1937):meta_onscreen_native_swap_buffers_with_damage: runtime check failed: (onscreen_native->next_frame == NULL)

Followed by this

2026-03-11T17:47:21.007993-06:00 edslaptop suspend: nvidia-suspend.service
2026-03-11T17:47:21.008085-06:00 edslaptop logger[9265]: <13>Mar 11 17:47:21 suspend: nvidia-suspend.service
2026-03-11T17:47:21.013432-06:00 edslaptop gnome-shell[6360]: (../src/backends/native/meta-onscreen-native.c:1937):meta_onscreen_native_swap_buffers_with_damage: runtime check failed: (onscreen_native->next_frame == NULL)
2026-03-11T17:47:21.013491-06:00 edslaptop gnome-shell[6360]: (../clutter/clutter/clutter-frame-clock.c:703):clutter_frame_clock_notify_ready: code should not be reached
2026-03-11T17:47:21.025509-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSource/ldac
2026-03-11T17:47:21.025781-06:00 edslaptop kernel: rfkill: input handler enabled
2026-03-11T17:47:21.025907-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSink/aptx_hd
2026-03-11T17:47:21.026401-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSource/aptx_hd
2026-03-11T17:47:21.027063-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSink/aptx
2026-03-11T17:47:21.027368-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSource/aptx
2026-03-11T17:47:21.027857-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSink/aac
2026-03-11T17:47:21.028147-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSource/aac
2026-03-11T17:47:21.028516-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSink/opus_g
2026-03-11T17:47:21.028752-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSource/opus_g
2026-03-11T17:47:21.029301-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSink/sbc
2026-03-11T17:47:21.029629-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSource/sbc
2026-03-11T17:47:21.029992-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSource/aptx_ll_1
2026-03-11T17:47:21.030274-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSource/aptx_ll_0
2026-03-11T17:47:21.030588-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
2026-03-11T17:47:21.030775-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
2026-03-11T17:47:21.031075-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSource/faststream
2026-03-11T17:47:21.031358-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSource/faststream_duplex
2026-03-11T17:47:21.031697-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSink/opus_05
2026-03-11T17:47:21.032169-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSource/opus_05
2026-03-11T17:47:21.032515-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSink/opus_05_duplex
2026-03-11T17:47:21.032936-06:00 edslaptop bluetoothd[2155]: Endpoint unregistered: sender=:1.94 path=/MediaEndpoint/A2DPSource/opus_05_duplex
2026-03-11T17:47:21.052994-06:00 edslaptop gsd-media-keys[6494]: Unable to get default sink
2026-03-11T17:47:21.053114-06:00 edslaptop gsd-media-keys[6494]: Unable to get default source
2026-03-11T17:47:21.053974-06:00 edslaptop gnome-shell[6360]: JS ERROR: TypeError: this._input._stream is null#012_updatePrivacyIndicator@resource:///org/gnome/shell/ui/status/volume.js:538:27#012InputIndicator/<@resource:///org/gnome/shell/ui/status/volume.js:524:18#012set stream@resource:///org/gnome/shell/ui/status/volume.js:104:18#012_readInput@resource:///org/gnome/shell/ui/status/volume.js:551:44#012InputIndicator/<@resource:///org/gnome/shell/ui/status/volume.js:515:50#012@resource:///org/gnome/shell/ui/init.js:20:20
2026-03-11T17:47:21.089056-06:00 edslaptop systemd[1]: grub-initrd-fallback.service: Deactivated successfully.
2026-03-11T17:47:21.089231-06:00 edslaptop systemd[1]: Finished grub-initrd-fallback.service - GRUB failed boot detection.
2026-03-11T17:47:21.431749-06:00 edslaptop kernel: nvidia 0000:01:00.0: Enabling HDA controller
2026-03-11T17:47:24.215828-06:00 edslaptop systemd[1]: nvidia-suspend.service: Deactivated successfully.
2026-03-11T17:47:24.215916-06:00 edslaptop systemd[1]: Finished nvidia-suspend.service - NVIDIA system suspend actions.
2026-03-11T17:47:24.216218-06:00 edslaptop systemd[1]: nvidia-suspend.service: Consumed 2.932s CPU time over 3.222s wall clock time, 20.9M memory peak.
2026-03-11T17:47:24.218449-06:00 edslaptop systemd[1]: Starting systemd-suspend.service - System Suspend...
2026-03-11T17:47:24.251738-06:00 edslaptop systemd[1]: session-2.scope: Unit now frozen-by-parent.
2026-03-11T17:47:24.251818-06:00 edslaptop systemd[1]: user.slice: Unit now frozen.
2026-03-11T17:47:24.251855-06:00 edslaptop systemd[1]: user-1000.slice: Unit now frozen-by-parent.
2026-03-11T17:47:24.251887-06:00 edslaptop systemd[1]: user@1000.service: Unit now frozen-by-parent.
2026-03-11T17:47:24.252089-06:00 edslaptop systemd-sleep[9378]: Successfully froze unit 'user.slice'.
2026-03-11T17:47:24.275895-06:00 edslaptop systemd-sleep[9378]: Performing sleep operation 'suspend'...
2026-03-11T17:47:24.277054-06:00 edslaptop kernel: PM: suspend entry (s2idle)
2026-03-11T17:47:24.283064-06:00 edslaptop kernel: Filesystems sync: 0.005 seconds
2026-03-11T17:47:24.992672-06:00 edslaptop kernel: jump_label: Fatal kernel bug, unexpected op at nvkms_kthread_q_callback+0x73/0x180 [nvidia_modeset] [0000000053cd4c57] (e9 97 00 00 00 != 0f 1f 44 00 00)) size:5 type:1
2026-03-11T17:47:24.992689-06:00 edslaptop kernel: fbcon: Taking over console
2026-03-11T17:47:24.992692-06:00 edslaptop kernel: ------------[ cut here ]------------
2026-03-11T17:47:24.992693-06:00 edslaptop kernel: kernel BUG at arch/x86/kernel/jump_label.c:73!
2026-03-11T17:47:24.992694-06:00 edslaptop kernel: Oops: invalid opcode: 0000 [#1] SMP NOPTI
2026-03-11T17:47:24.992695-06:00 edslaptop kernel: CPU: 1 UID: 0 PID: 9378 Comm: systemd-sleep Tainted: G        W  OE       6.19.0-9-generic #9-Ubuntu PREEMPT(voluntary) 
2026-03-11T17:47:24.992695-06:00 edslaptop kernel: Tainted: [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
2026-03-11T17:47:24.992696-06:00 edslaptop kernel: Hardware name: Alienware Alienware 16 Area-51 AA16250/0XYV46, BIOS 1.8.0 09/10/2025
2026-03-11T17:47:24.992697-06:00 edslaptop kernel: RIP: 0010:__jump_label_patch.cold+0x24/0x26
2026-03-11T17:47:24.992697-06:00 edslaptop kernel: Code: f8 e9 04 8a 18 00 48 c7 c3 b8 49 e1 a5 41 56 45 89 e1 49 89 d8 4c 89 e9 4c 89 ea 4c 89 ee 48 c7 c7 78 7e 8c a4 e8 94 76 01 00 <0f> 0b 0f b6 f0 48 c7 c7 e0 01 45 a5 88 45 f7 e8 20 8e b8 00 0f b6
2026-03-11T17:47:24.992698-06:00 edslaptop kernel: RSP: 0018:ffffcd1ae29afc28 EFLAGS: 00010246
2026-03-11T17:47:24.992698-06:00 edslaptop kernel: RAX: 00000000000000a8 RBX: ffffffffa420668a RCX: 0000000000000000
2026-03-11T17:47:24.992699-06:00 edslaptop kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
2026-03-11T17:47:24.992699-06:00 edslaptop kernel: RBP: ffffcd1ae29afc58 R08: 0000000000000000 R09: 0000000000000000
2026-03-11T17:47:24.992699-06:00 edslaptop kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000005
2026-03-11T17:47:24.992700-06:00 edslaptop kernel: R13: ffffffffc1800793 R14: 0000000000000001 R15: 0000000000000000
2026-03-11T17:47:24.992701-06:00 edslaptop kernel: FS:  00007da8aa94ec80(0000) GS:ffff8c06f9ac1000(0000) knlGS:0000000000000000
2026-03-11T17:47:24.992701-06:00 edslaptop kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2026-03-11T17:47:24.992701-06:00 edslaptop kernel: CR2: 00005dbd8e8924f0 CR3: 000000013212f002 CR4: 0000000000f72ef0
2026-03-11T17:47:24.992702-06:00 edslaptop kernel: PKRU: 55555554
2026-03-11T17:47:24.992702-06:00 edslaptop kernel: Call Trace:
2026-03-11T17:47:24.992703-06:00 edslaptop kernel:  <TASK>
2026-03-11T17:47:24.992703-06:00 edslaptop kernel:  arch_jump_label_transform_queue+0x37/0x90
2026-03-11T17:47:24.992704-06:00 edslaptop kernel:  __jump_label_update+0x47/0x100
2026-03-11T17:47:24.992704-06:00 edslaptop kernel:  jump_label_update+0x5c/0x110
2026-03-11T17:47:24.992704-06:00 edslaptop kernel:  static_key_slow_inc_cpuslocked+0x53/0xa0
2026-03-11T17:47:24.992705-06:00 edslaptop kernel:  static_key_slow_inc+0x1f/0x40
2026-03-11T17:47:24.992705-06:00 edslaptop kernel:  freeze_processes+0xd1/0xe0
2026-03-11T17:47:24.992706-06:00 edslaptop kernel:  enter_state+0xdc/0x590
2026-03-11T17:47:24.992706-06:00 edslaptop kernel:  pm_suspend+0x49/0x90
2026-03-11T17:47:24.992706-06:00 edslaptop kernel:  state_store+0x2e/0x60
2026-03-11T17:47:24.992707-06:00 edslaptop kernel:  kobj_attr_store+0x12/0x40
2026-03-11T17:47:24.992707-06:00 edslaptop kernel:  sysfs_kf_write+0x74/0x90
2026-03-11T17:47:24.992708-06:00 edslaptop kernel:  kernfs_fop_write_iter+0x161/0x210
2026-03-11T17:47:24.992708-06:00 edslaptop kernel:  vfs_write+0x25b/0x490
2026-03-11T17:47:24.992708-06:00 edslaptop kernel:  ksys_write+0x71/0xf0
2026-03-11T17:47:24.992709-06:00 edslaptop kernel:  __x64_sys_write+0x19/0x30
2026-03-11T17:47:24.992709-06:00 edslaptop kernel:  x64_sys_call+0x79/0x2360
2026-03-11T17:47:24.992710-06:00 edslaptop kernel:  do_syscall_64+0x81/0x5c0
2026-03-11T17:47:24.992710-06:00 edslaptop kernel:  ? exc_page_fault+0x90/0x1b0
2026-03-11T17:47:24.992710-06:00 edslaptop kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
2026-03-11T17:47:24.992711-06:00 edslaptop kernel: RIP: 0033:0x7da8aa0a0146
2026-03-11T17:47:24.992711-06:00 edslaptop kernel: Code: 47 ba 04 00 00 00 48 8b 05 c7 0c 17 00 64 89 10 48 c7 c2 ff ff ff ff c9 48 89 d0 c3 0f 1f 84 00 00 00 00 00 48 8b 45 10 0f 05 <48> 89 c2 48 3d 00 f0 ff ff 77 0f c9 48 89 d0 c3 66 2e 0f 1f 84 00
2026-03-11T17:47:24.992712-06:00 edslaptop kernel: RSP: 002b:00007ffccd5dfa70 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
2026-03-11T17:47:24.992712-06:00 edslaptop kernel: RAX: ffffffffffffffda RBX: 00005dbd8e888310 RCX: 00007da8aa0a0146
2026-03-11T17:47:24.992712-06:00 edslaptop kernel: RDX: 0000000000000004 RSI: 00005dbd8e8914e0 RDI: 0000000000000007
2026-03-11T17:47:24.992713-06:00 edslaptop kernel: RBP: 00007ffccd5dfa80 R08: 0000000000000000 R09: 0000000000000000
2026-03-11T17:47:24.992713-06:00 edslaptop kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000004
2026-03-11T17:47:24.992713-06:00 edslaptop kernel: R13: 0000000000000004 R14: 00005dbd8e8914e0 R15: 0000000000000000
2026-03-11T17:47:24.992714-06:00 edslaptop kernel:  </TASK>
2026-03-11T17:47:24.992715-06:00 edslaptop kernel: Modules linked in: rfcomm snd_seq_dummy snd_hrtimer xfrm_user xfrm_algo xt_CHECKSUM xt_MASQUERADE xt_conntrack xt_set ipt_REJECT ip_set nf_reject_ipv4 xt_tcpudp xt_addrtype nft_compat x_tables nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables bridge stp llc ccm snd_ctl_led snd_soc_sof_sdw snd_sof_probes snd_soc_intel_hda_dsp_common xe snd_soc_rt722_sdca snd_soc_rt1320_sdw drm_gpusvm_helper regmap_sdw_mbq regmap_sdw gpu_sched snd_hda_codec_intelhdmi drm_gpuvm snd_soc_dmic drm_exec drm_suballoc_helper overlay qrtr cmac algif_hash algif_skcipher af_alg bnep binfmt_misc snd_sof_pci_intel_mtl snd_sof_intel_hda_generic soundwire_intel snd_sof_intel_hda_sdw_bpt snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda_mlink snd_sof_intel_hda soundwire_cadence snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_hda_ext_core snd_soc_acpi_intel_match snd_hda_codec_nvhdmi snd_soc_acpi_intel_sdca_quirks soundwire_generic_allocation snd_hda_codec_hdmi snd_soc_sdw_utils snd_soc_acpi
2026-03-11T17:47:24.992716-06:00 edslaptop kernel:  soundwire_bus snd_hda_intel snd_soc_sdca snd_hda_codec nls_iso8859_1 snd_soc_core snd_hda_core cmdlinepart intel_uncore_frequency snd_intel_dspcfg snd_compress intel_uncore_frequency_common snd_intel_sdw_acpi ac97_bus snd_hwdep spi_nor x86_pkg_temp_thermal snd_pcm_dmaengine iwlmld intel_powerclamp mtd mei_gsc_proxy intel_rapl_msr snd_pcm mac80211 snd_seq_midi snd_seq_midi_event coretemp i915 snd_rawmidi libarc4 snd_seq processor_thermal_device_pci dell_wmi snd_seq_device processor_thermal_device uvcvideo btusb processor_thermal_wt_hint snd_timer videobuf2_vmalloc uvc platform_temperature_control btmtk processor_thermal_soc_slider videobuf2_memops btrtl dell_smbios dell_wmi_sysman iwlwifi kvm_intel processor_thermal_rfim drm_buddy intel_pmc_core snd btbcm videobuf2_v4l2 dcdbas processor_thermal_rapl kvm irqbypass rapl intel_cstate alienware_wmi dell_wmi_ddv i2c_i801 intel_rapl_common soundcore cfg80211 dell_smm_hwmon drm_display_helper btintel firmware_attributes_class videobuf2_common wmi_bmof
2026-03-11T17:47:24.992717-06:00 edslaptop kernel:  dell_wmi_descriptor spi_intel_pci pmt_telemetry crc8 i2c_smbus processor_thermal_wt_req cec spi_intel i2c_mux int3403_thermal pmt_discovery processor_thermal_power_floor videodev mei_me bluetooth processor_thermal_mbox pmt_class int340x_thermal_zone rc_core intel_vpu mei mc i2c_algo_bit platform_profile nvidia_wmi_ec_backlight intel_pmc_ssram_telemetry acpi_pad int3400_thermal intel_vsec intel_hid nvidia_uvm(OE) acpi_thermal_rel joydev acpi_tad sparse_keymap input_leds mac_hid sch_fq_codel nvme_fabrics efi_pstore nfnetlink hid_sensor_custom hid_sensor_hub intel_ishtp_hid usbhid nvidia_drm(OE) nvidia_modeset(OE) spi_pxa2xx_platform ucsi_acpi dw_dmac hid_multitouch typec_ucsi dw_dmac_core hid_generic 8250_dw spi_pxa2xx_core typec nvidia(OE) rtsx_pci_sdmmc nvme drm_ttm_helper ttm video intel_lpss_pci nvme_core ghash_clmulni_intel intel_lpss psmouse intel_ish_ipc rtsx_pci nvme_keyring idma64 intel_ishtp thunderbolt nvme_auth hkdf i2c_hid_acpi i2c_hid hid wmi pinctrl_meteorlake pinctrl_meteorpoint serio_raw
2026-03-11T17:47:24.992718-06:00 edslaptop kernel:  parport_pc lp ppdev parport msr dmi_sysfs autofs4 aesni_intel
2026-03-11T17:47:24.992718-06:00 edslaptop kernel: ---[ end trace 0000000000000000 ]---
2026-03-11T17:47:24.992719-06:00 edslaptop kernel: RIP: 0010:__jump_label_patch.cold+0x24/0x26
2026-03-11T17:47:24.992719-06:00 edslaptop kernel: Code: f8 e9 04 8a 18 00 48 c7 c3 b8 49 e1 a5 41 56 45 89 e1 49 89 d8 4c 89 e9 4c 89 ea 4c 89 ee 48 c7 c7 78 7e 8c a4 e8 94 76 01 00 <0f> 0b 0f b6 f0 48 c7 c7 e0 01 45 a5 88 45 f7 e8 20 8e b8 00 0f b6
2026-03-11T17:47:24.992720-06:00 edslaptop kernel: RSP: 0018:ffffcd1ae29afc28 EFLAGS: 00010246
2026-03-11T17:47:24.992720-06:00 edslaptop kernel: RAX: 00000000000000a8 RBX: ffffffffa420668a RCX: 0000000000000000
2026-03-11T17:47:24.992720-06:00 edslaptop kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
2026-03-11T17:47:24.992721-06:00 edslaptop kernel: RBP: ffffcd1ae29afc58 R08: 0000000000000000 R09: 0000000000000000
2026-03-11T17:47:24.992721-06:00 edslaptop kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000005
2026-03-11T17:47:24.992727-06:00 edslaptop kernel: R13: ffffffffc1800793 R14: 0000000000000001 R15: 0000000000000000
2026-03-11T17:47:24.992728-06:00 edslaptop kernel: FS:  00007da8aa94ec80(0000) GS:ffff8c06f9ac1000(0000) knlGS:0000000000000000
2026-03-11T17:47:24.992728-06:00 edslaptop kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2026-03-11T17:47:24.992729-06:00 edslaptop kernel: CR2: 00005dbd8e8924f0 CR3: 000000013212f002 CR4: 0000000000f72ef0
2026-03-11T17:47:24.992729-06:00 edslaptop kernel: PKRU: 55555554
2026-03-11T17:47:24.993502-06:00 edslaptop systemd[1]: systemd-suspend.service: Main process exited, code=killed, status=11/SEGV
2026-03-11T17:47:24.993653-06:00 edslaptop systemd[1]: systemd-suspend.service: Failed with result 'signal'.
2026-03-11T17:47:24.993740-06:00 edslaptop systemd[1]: Failed to start systemd-suspend.service - System Suspend.
2026-03-11T17:47:24.993816-06:00 edslaptop systemd[1]: Dependency failed for suspend.target - Suspend.
2026-03-11T17:47:24.993851-06:00 edslaptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
2026-03-11T17:47:24.995432-06:00 edslaptop systemd[1]: Stopped target sleep.target - Sleep.
2026-03-11T17:47:24.996883-06:00 edslaptop systemd-resolved[851]: Closing all remaining TCP connections.
2026-03-11T17:47:24.996976-06:00 edslaptop systemd-resolved[851]: Resetting learnt feature levels on all servers.
2026-03-11T17:47:24.997175-06:00 edslaptop ModemManager[2408]: <msg> [sleep-monitor-systemd] system is resuming
2026-03-11T17:47:24.997385-06:00 edslaptop NetworkManager[2386]: <info>  [1773272844.9967] manager: sleep: wake requested (sleeping: yes  enabled: yes)
2026-03-11T17:47:24.997450-06:00 edslaptop NetworkManager[2386]: <info>  [1773272844.9968] device (wlp131s0f0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
2026-03-11T17:47:24.997501-06:00 edslaptop systemd[1]: Starting grub2-common.service - Record successful boot for GRUB...
2026-03-11T17:47:24.998467-06:00 edslaptop systemd[1]: Starting nvidia-resume.service - NVIDIA system resume actions...
2026-03-11T17:47:24.998756-06:00 edslaptop rtkit-daemon[3175]: Resuming known real-time threads.
2026-03-11T17:47:24.998817-06:00 edslaptop rtkit-daemon[3175]: Successfully made thread 7930 of process 6793 owned by '1000' high priority at nice level 15.
2026-03-11T17:47:24.998851-06:00 edslaptop rtkit-daemon[3175]: Successfully made thread 6388 of process 6360 owned by '1000' high priority at nice level -15.
2026-03-11T17:47:24.998881-06:00 edslaptop rtkit-daemon[3175]: Successfully made thread 6008 of process 5912 owned by '1000' RT at priority 20.
2026-03-11T17:47:24.998914-06:00 edslaptop rtkit-daemon[3175]: Successfully made thread 5912 of process 5912 owned by '1000' high priority at nice level -11.
2026-03-11T17:47:24.998951-06:00 edslaptop rtkit-daemon[3175]: Successfully made thread 6002 of process 5914 owned by '1000' RT at priority 20.
2026-03-11T17:47:24.998988-06:00 edslaptop rtkit-daemon[3175]: Successfully made thread 5914 of process 5914 owned by '1000' high priority at nice level -11.
2026-03-11T17:47:24.999020-06:00 edslaptop rtkit-daemon[3175]: Successfully made thread 5998 of process 5913 owned by '1000' RT at priority 20.
2026-03-11T17:47:24.999048-06:00 edslaptop rtkit-daemon[3175]: Successfully made thread 5917 of process 5893 owned by '1000' RT at priority 20.
2026-03-11T17:47:24.999075-06:00 edslaptop rtkit-daemon[3175]: Successfully made thread 5893 of process 5893 owned by '1000' high priority at nice level -11.
2026-03-11T17:47:24.999101-06:00 edslaptop rtkit-daemon[3175]: Resumed scheduling 9 threads.
2026-03-11T17:47:25.295723-06:00 edslaptop kernel: Console: switching to colour frame buffer device 160x50
2026-03-11T17:47:25.306695-06:00 edslaptop suspend: nvidia-resume.service
2026-03-11T17:47:25.306774-06:00 edslaptop logger[9390]: <13>Mar 11 17:47:25 suspend: nvidia-resume.service
2026-03-11T17:47:25.350816-06:00 edslaptop systemd[1]: grub2-common.service: Deactivated successfully.
2026-03-11T17:47:25.351185-06:00 edslaptop systemd[1]: Finished grub2-common.service - Record successful boot for GRUB.
2026-03-11T17:47:25.452692-06:00 edslaptop NetworkManager[2386]: <info>  [1773272845.4525] device (p2p-dev-wlp131s0f0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
2026-03-11T17:47:25.452796-06:00 edslaptop NetworkManager[2386]: <warn>  [1773272845.4525] device (p2p-dev-wlp131s0f0): error setting IPv4 forwarding to '1': Resource temporarily unavailable
2026-03-11T17:47:25.452842-06:00 edslaptop NetworkManager[2386]: <info>  [1773272845.4527] manager: NetworkManager state is now CONNECTED_LOCAL
2026-03-11T17:47:26.159764-06:00 edslaptop kernel: nvidia-modeset: nvidia-modeset: ACPI reported no NVIDIA native backlight available; attempting to use ACPI backlight.
2026-03-11T17:47:26.174399-06:00 edslaptop systemd[1]: nvidia-resume.service: Deactivated successfully.
2026-03-11T17:47:26.174547-06:00 edslaptop systemd[1]: Finished nvidia-resume.service - NVIDIA system resume actions.
2026-03-11T17:47:29.044677-06:00 edslaptop ModemManager[2408]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:80/0000:80:1c.5/0000:83:00.0': not supported by any plugin
2026-03-11T17:47:30.021572-06:00 edslaptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
2026-03-11T17:47:30.457236-06:00 edslaptop NetworkManager[2386]: <error> [1773272850.4569] device (wlp131s0f0): Couldn't initialize supplicant interface: Timeout was reached
2026-03-11T17:47:31.652783-06:00 edslaptop kernel: NVRM: nvAssertFailedNoLog: Assertion failed: 0 @ osapi.c:1942
2026-03-11T17:47:40.730272-06:00 edslaptop NetworkManager[2386]: <warn>  [1773272860.7297] device (wlp131s0f0): re-acquiring supplicant interface (#1).
2026-03-11T17:47:44.927818-06:00 edslaptop systemd[1]: Starting update-notifier-download.service - Download data for packages that failed at package install time...
2026-03-11T17:47:44.962506-06:00 edslaptop systemd[1]: Starting apt-daily.service - Daily apt download activities...
2026-03-11T17:47:44.989657-06:00 edslaptop systemd[1]: update-notifier-download.service: Deactivated successfully.
2026-03-11T17:47:44.989774-06:00 edslaptop systemd[1]: Finished update-notifier-download.service - Download data for packages that failed at package install time.
2026-03-11T17:47:45.190414-06:00 edslaptop systemd[1]: Starting apt-news.service - Update APT News...
2026-03-11T17:47:45.192388-06:00 edslaptop systemd[1]: Starting esm-cache.service - Update the local ESM caches...
2026-03-11T17:47:45.731129-06:00 edslaptop NetworkManager[2386]: <error> [1773272865.7308] device (wlp131s0f0): Couldn't initialize supplicant interface: Timeout was reached
2026-03-11T17:47:46.244065-06:00 edslaptop dbus-daemon[2159]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.21' (uid=0 pid=2183 comm="/usr/lib/snapd/snapd" label="unconfined")
2026-03-11T17:47:52.984093-06:00 edslaptop unattended-upgrade: Not running on this development release before 2026-04-01
2026-03-11T17:47:55.726082-06:00 edslaptop NetworkManager[2386]: <warn>  [1773272875.7256] device (wlp131s0f0): re-acquiring supplicant interface (#2).
2026-03-11T17:48:00.731687-06:00 edslaptop NetworkManager[2386]: <error> [1773272880.7310] device (wlp131s0f0): Couldn't initialize supplicant interface: Timeout was reached
2026-03-11T17:48:05.640890-06:00 edslaptop kernel: message repeated 3 times: [ NVRM: nvAssertFailedNoLog: Assertion failed: 0 @ osapi.c:1942]
2026-03-11T17:48:06.031765-06:00 edslaptop kernel: nvidia 0000:01:00.0: Enabling HDA controller
2026-03-11T17:48:10.733402-06:00 edslaptop NetworkManager[2386]: <warn>  [1773272890.7328] device (wlp131s0f0): re-acquiring supplicant interface (#3).
2026-03-11T17:48:11.245227-06:00 edslaptop dbus-daemon[2159]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.21' (uid=0 pid=2183 comm="/usr/lib/snapd/snapd" label="unconfined")
2026-03-11T17:48:15.738922-06:00 edslaptop NetworkManager[2386]: <error> [1773272895.7383] device (wlp131s0f0): Couldn't initialize supplicant interface: Timeout was reached
2026-03-11T17:48:16.728489-06:00 edslaptop PackageKit: daemon quit
2026-03-11T17:48:25.727266-06:00 edslaptop NetworkManager[2386]: <warn>  [1773272905.7267] device (wlp131s0f0): re-acquiring supplicant interface (#4).
2026-03-11T17:48:30.732739-06:00 edslaptop NetworkManager[2386]: <error> [1773272910.7321] device (wlp131s0f0): Couldn't initialize supplicant interface: Timeout was reached
2026-03-11T17:48:40.733432-06:00 edslaptop NetworkManager[2386]: <warn>  [1773272920.7328] device (wlp131s0f0): re-acquiring supplicant interface (#5).
2026-03-11T17:48:45.738925-06:00 edslaptop NetworkManager[2386]: <error> [1773272925.7383] device (wlp131s0f0): Couldn't initialize supplicant interface: Timeout was reached
2026-03-11T17:48:45.739088-06:00 edslaptop NetworkManager[2386]: <info>  [1773272925.7384] device (wlp131s0f0): supplicant interface keeps failing, giving up
Poor Sound Quality ASUS Zephyrus G14 (ALC285) https://askubuntu.com/questions/1541557/poor-sound-quality-asus-zephyrus-g14-alc285

I’m running Ubuntu 22.04 on my ASUS Zephyrus G14 with a Realtek ALC285 sound card. My built-in speaker sound is high-pitched and kinda robotic. Sound through HDMI works correctly. Some things I've tried are changing the sample rate, different alsa model overrides, overriding the speaker mapping with hdajackretask, increasing volume, increasing base volume with an equalizer.

Has anyone gotten the sound to work well?

Specs:

Laptop: ASUS Zephyrus G14
Audio Codec: Realtek ALC285
Ubuntu Version: 22.04 LTS
Kernel: 6.8.0-52-generic

Default Sink (pactl list sinks):

Sink #63
    State: IDLE
    Name: alsa_output.pci-0000_65_00.6.HiFi__hw_Generic_1__sink
    Description: Family 17h/19h HD Audio Controller Speaker + Headphones
    Driver: PipeWire
    Sample Specification: s32le 2ch 48000Hz
    Channel Map: front-left,front-right
    Owner Module: 4294967295
    Mute: no
    Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
            balance 0.00
    Base Volume: 65536 / 100% / 0.00 dB
    Monitor Source: alsa_output.pci-0000_65_00.6.HiFi__hw_Generic_1__sink.monitor
    Latency: 0 usec, configured 0 usec
    Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
    Properties:
        alsa.card = "2"
        alsa.card_name = "HD-Audio Generic"
        alsa.class = "generic"
        alsa.components = "HDA:10ec0285,10431e83,00100002"
        alsa.device = "0"
        alsa.driver_name = "snd_hda_intel"
        alsa.id = "Generic_1"
        alsa.long_card_name = "HD-Audio Generic at 0xdd6c0000 irq 104"
        alsa.mixer_device = "_ucm0004.hw:Generic_1"
        alsa.mixer_name = "Realtek ALC285"
        alsa.name = "ALC285 Analog"
        alsa.resolution_bits = "16"
        alsa.subclass = "generic-mix"
        alsa.subdevice = "0"
        alsa.subdevice_name = "subdevice #0"
        api.alsa.card.longname = "HD-Audio Generic at 0xdd6c0000 irq 104"
        api.alsa.card.name = "HD-Audio Generic"
        api.alsa.open.ucm = "true"
        api.alsa.path = "hw:Generic_1"
        api.alsa.pcm.card = "2"
        api.alsa.pcm.stream = "playback"
        audio.channels = "2"
        audio.position = "FL,FR"
        card.profile.device = "0"
        device.api = "alsa"
        device.class = "sound"
        device.id = "54"
        device.profile.description = "Speaker + Headphones"
        device.profile.name = "HiFi: hw:Generic_1: sink"
        device.routes = "2"
        factory.name = "api.alsa.pcm.sink"
        media.class = "Audio/Sink"
        device.description = "Family 17h/19h HD Audio Controller"
        node.name = "alsa_output.pci-0000_65_00.6.HiFi__hw_Generic_1__sink"
        node.nick = "ALC285 Analog"
        node.pause-on-idle = "false"
        object.path = "alsa:pcm:2:hw:Generic_1:playback"
        priority.driver = "1000"
        priority.session = "1000"
        factory.id = "18"
        clock.quantum-limit = "8192"
        client.id = "41"
        node.driver = "true"
        factory.mode = "merge"
        audio.adapt.follower = ""
        library.name = "audioconvert/libspa-audioconvert"
        object.id = "63"
        object.serial = "63"
        node.max-latency = "16384/48000"
        api.alsa.period-size = "1024"
        api.alsa.period-num = "32"
        api.alsa.headroom = "0"
        api.acp.auto-port = "false"
        api.acp.auto-profile = "false"
        api.alsa.card = "2"
        api.alsa.use-acp = "true"
        api.dbus.ReserveDevice1 = "Audio2"
        device.bus = "pci"
        device.bus_path = "pci-0000:65:00.6"
        device.enum.api = "udev"
        device.icon_name = "audio-card-analog-pci"
        device.name = "alsa_card.pci-0000_65_00.6"
        device.nick = "HD-Audio Generic"
        device.plugged.usec = "6415867"
        device.product.id = "0x15e3"
        device.product.name = "Family 17h/19h HD Audio Controller"
        device.subsystem = "sound"
        sysfs.path = "/devices/pci0000:00/0000:00:08.1/0000:65:00.6/sound/card2"
        device.vendor.id = "0x1022"
        device.vendor.name = "Advanced Micro Devices, Inc. [AMD]"
        device.string = "2"
    Ports:
        [Out] Speaker: Speaker (type: Speaker, priority: 100, availability unknown)
        [Out] Headphones: Headphones (type: Headphones, priority: 200, availability group: Headphone, not available)
    Active Port: [Out] Speaker
    Formats:
        pcm

ALSA modules (cat /proc/asound/modules):

0 snd_hda_intel
1 snd_hda_intel
2 snd_hda_intel
3 snd_acp_legacy_mach

ALSA cards (cat /proc/asound/cards):

0 [NVidia         ]: HDA-Intel - HDA NVidia
                     HDA NVidia at 0xdd080000 irq 102
1 [Generic        ]: HDA-Intel - HD-Audio Generic
                     HD-Audio Generic at 0xdd6c8000 irq 103
2 [Generic_1      ]: HDA-Intel - HD-Audio Generic
                     HD-Audio Generic at 0xdd6c0000 irq 104
3 [acppdmmach     ]: acp-pdm-mach - acp-pdm-mach
                     ASUSTeKCOMPUTERINC.-ROGZephyrusG16GA605WI_GA605WI-1.0-GA605WI

Audio system logs(dmesg | grep -i audio):

[    5.302027] snd_hda_intel 0000:64:00.1: Handle vga_switcheroo audio client
[    5.302446] snd_hda_intel 0000:65:00.1: Handle vga_switcheroo audio client
[    5.327178] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:08.1/0000:65:00.1/sound/card1/input22
[    5.328109] snd_hda_codec_realtek hdaudioC2D0: autoconfig for ALC285: line_outs=2 (0x17/0x14/0x0/0x0/0x0) type:speaker
[    5.328116] snd_hda_codec_realtek hdaudioC2D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    5.328118] snd_hda_codec_realtek hdaudioC2D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[    5.328120] snd_hda_codec_realtek hdaudioC2D0:    mono: mono_out=0x0
[    5.328121] snd_hda_codec_realtek hdaudioC2D0:    inputs:
[    5.328123] snd_hda_codec_realtek hdaudioC2D0:      Internal Mic=0x13
[    5.328124] snd_hda_codec_realtek hdaudioC2D0:      Internal Mic=0x12
[    6.417695] input: HD-Audio Generic Headphone as /devices/pci0000:00/0000:00:08.1/0000:65:00.6/sound/card2/input27

Alsamixer: enter image description here

Pavucontrol: enter image description here

Ubuntu 24.04 screen freezes quite often https://askubuntu.com/questions/1531352/ubuntu-24-04-screen-freezes-quite-often

Facing this issue after I upgraded to Ubuntu 24.04 few months back. I tried various solutions on this forum as well as on other forums, but got no permanent result. After recommendation from one of the forum post I installed the disk repair tool and following is the result. https://paste.ubuntu.com/p/W7NNPypN8p/ I am not an expert in ubuntu or hardware. Mainly working as a developer of php. So if anyone can guide me whats wrong in the system and how can i correct it ?

Thanks in advance.

How to downgrade from kernel 6.5 to 6.2 on Ubuntu 22.04? https://askubuntu.com/questions/1503321/how-to-downgrade-from-kernel-6-5-to-6-2-on-ubuntu-22-04

How do I downgrade kernel 6.5 to 6.2 on Ubuntu 22.04? This is to resolve my Wi-Fi persistent disconnection issues.

How do I detach a system added to my Ubuntu pro subscription? https://askubuntu.com/questions/1500922/how-do-i-detach-a-system-added-to-my-ubuntu-pro-subscription

I have 3 machines attached however I can only find 2 on my estate, is it possible to detach a token from the portal or get a list of machines? its possible the other server has been decommed and I would like to release that token.

Ubuntu only boots with advanced recovery options after upgrading to 22.04 https://askubuntu.com/questions/1426830/ubuntu-only-boots-with-advanced-recovery-options-after-upgrading-to-22-04

I have a computer that someone set up for me with two options during boot: Windows or Ubuntu.

All was fine under the Ubuntu system for about 8 months. The other week I was prompted to upgrade to Ubuntu 22.04 which I did.

Today, I ran the updater and it told me to restart the computer.

Now when I restart and I choose Ubuntu, it won't start and hangs.

I have the option to boot Ubuntu with Advanced options. I have tried all of them. The first two options, generic and recovery mode, don't work.

But the second generic option starts Ubuntu properly and I arrive at the Ubuntu desktop.

What has happened and what can I do to resolve this so it starts normally without having to use the Advanced boot options?

No hardware has changed and the computer is only used for basic word processing and web.

I am a relative newbie and perhaps out my depth with knowing how to resolve issues under Ubuntu.

The first error screen existed and Ubuntu did continue to start to desktop OK. I understand that this could be a BIOS setting that doesn't affect Ubuntu starting.

[    1.079720] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.S
PT4._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330)
[    1.079737] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previ
ous error (AE_NOT_FOUND) (20210730/psparse-529)
[    1.080605] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-33
0)
[    1.080614] ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
/dev/sda5: recovering journal
/dev/sda5: clean, 243172/4898816 files, 12237393/19568128 blocks
[    2.276619] mtd device must be supplied (device name is empty)
[    3.172831] mtd device must be supplied (device name is empty)

Another screen showing a list is what happens now. It displays this list of boot messages, then in a moment goes to a blank screen with a cursor where it gets stuck forever. Does anything in this list indicate a problem I could solve?

         Starting Process error reports when automatic reporting is enabled...
[  OK  ] Started LSB: automatic crash report generation.
[  OK  ] Started System Logging Service.
[  OK  ] Finished Remove Stale Online ext4 Metadata Check Snapshots.
[  OK  ] Finished Record successful boot for GRUB.
         Starting GRUB failed boot detection...
[  OK  ] Started User Login Management.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started WPA supplicant.
[  OK  ] Started Thermal Daemon Service.
[  OK  ] Started Switcheroo Control Proxy service.
[  OK  ] Started Network Manager.
[  OK  ] Reached target Network.
         Starting Network Manager Wait Online...
         Starting Save/Restore Sound Card State...
         Starting CUPS Scheduler...
         Starting OpenVPN service...
         Starting Permit User Sessions...
[  OK  ] Started Unattended Upgrades Shutdown.
[  OK  ] Finished OpenVPN service.
[  OK  ] Finished Permit User Sessions.
[  OK  ] Finished Save/Restore Sound Card State.
[  OK  ] Started Authorization Manager.
[  OK  ] Reached target Sound Card.
         Starting Modem Manager...
         Starting Hold until boot process finishes up...
[  OK  ] Started Power Profiles daemon.
         Starting Hostname Service...
[  OK  ] Finished GRUB failed boot detection.
[  OK  ] Started Accounts Service.
[  OK  ] Started Hostname Service.
[  OK  ] Started CUPS Scheduler.
         Starting Network Manager Script Dispatcher Service...
[  OK  ] Started Network Manager Script Dispatcher Service.
[  OK  ] Started Modem Manager.
[  OK  ] Started Disk Manager.
[  OK  ] Finished Process error reports when automatic reporting is enabled.
[  OK  ] Started Snap Daemon.
         Starting Wait until snapd is fully seeded...
         Starting Time & Date Service...
[  OK  ] Started Dispatcher daemon for systemd-networkd.
[  OK  ] Started Time & Date Service.
[  OK  ] Finished Wait until snapd is fully seeded.
Changing the auto save directory for screen shots and screen cast in Ubuntu 22.04 https://askubuntu.com/questions/1408611/changing-the-auto-save-directory-for-screen-shots-and-screen-cast-in-ubuntu-22-0

I recently switched to Ubuntu 22.04 and I really like its default screenshot UI, but there seems to be no way to change the autosave directory. It saves the pictures to the $HOME/Pictures/Screenshots directory and I want it to save them to another directory. I know there are alternatives such as using gnome-screenshot but I want to use the default one.

Please suggest a method to resolve this issue. And please feel free to ask for other additional information.

Thanks in advance.

How to install Emacs 27.1 via ppa on 20.04.1? https://askubuntu.com/questions/1287342/how-to-install-emacs-27-1-via-ppa-on-20-04-1

I have a fresh 20.04.1 Ubuntu and I want to install Emacs 27. The standard emacs from apt-get is 26.3, so I want to install it via ppa.

So I run software-properties-gtk, go to other software and add ppa:kelleyk/emacs. A pop-up appears asking me to update the package sources, I confirm. Now I try to install it:

$ sudo apt-get install emacs27
[sudo] password for myusername: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  emacs-bin-common emacs-common emacs-el emacs-gtk gsfonts imagemagick-6-common libfprint-2-tod1
  liblqr-1-0 libmagickcore-6.q16-6 libmagickwand-6.q16-6
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  emacs27-common
The following NEW packages will be installed:
  emacs27 emacs27-common
0 upgraded, 2 newly installed, 0 to remove and 12 not upgraded.
Need to get 21,9 MB of archives.
After this operation, 95,8 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://ppa.launchpad.net/kelleyk/emacs/ubuntu focal/main amd64 emacs27-common all 27.1~1.git86d8d76aa3-kk2+20.04 [18,2 MB]
Get:2 http://ppa.launchpad.net/kelleyk/emacs/ubuntu focal/main amd64 emacs27 amd64 27.1~1.git86d8d76aa3-kk2+20.04 [3.651 kB]
Fetched 21,9 MB in 5s (4.847 kB/s)   
Selecting previously unselected package emacs27-common.
(Reading database ... 185797 files and directories currently installed.)
Preparing to unpack .../emacs27-common_27.1~1.git86d8d76aa3-kk2+20.04_all.deb ...
Unpacking emacs27-common (27.1~1.git86d8d76aa3-kk2+20.04) ...
dpkg: error processing archive /var/cache/apt/archives/emacs27-common_27.1~1.git86d8d76aa3-kk2+20.04_all.deb (--unpack):
 trying to overwrite '/usr/include/emacs-module.h', which is also in package emacs-common 1:26.3+1-1ubuntu2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Selecting previously unselected package emacs27.
Preparing to unpack .../emacs27_27.1~1.git86d8d76aa3-kk2+20.04_amd64.deb ...
Unpacking emacs27 (27.1~1.git86d8d76aa3-kk2+20.04) ...
Errors were encountered while processing:
 /var/cache/apt/archives/emacs27-common_27.1~1.git86d8d76aa3-kk2+20.04_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

A pop-up from software updater appears:

The package system is brocken
Check if you are using third party repositories. If so disable them, since they are a common source of problems.
Furthermore run the following command in a Terminal: apt-get install -f
Transaction failed: The package system is broken
 The following packages have unmet dependencies:

emacs27: Depends: emacs27-common but it is not installed
         Depends: libgmp10 (>= 2:6.0.0) but 2:6.2.0+dfsg-4 is installed
         Depends: libice6 (>= 1:1.0.0) but 2:1.0.10-0ubuntu1 is installed
         Depends: libxfixes3 (>= 1:4.0.1) but 1:5.0.3-2 is installed
         Depends: zlib1g (>= 1:1.1.4) but 1:1.2.11.dfsg-2ubuntu1.1 is installed

But sudo apt-get install libgmp10 libice6 libxfixes3 zlib1g shows them to be already installed.

netplan how to set hostname via option 12 https://askubuntu.com/questions/1285155/netplan-how-to-set-hostname-via-option-12

I run Ubuntu 20.04 based from the cloudimage... so netplan has its 50-cloud-init.yaml which just says .. use dhcp

In the background it uses systemd-networkd as backoffice

But how can I advise ubuntu to set the hostname based on option 12? In the past we used dhclient exit hooks but with netplan and systemd this doesn't work anymore. So how can I do this ?

The UseHostname Option in Section DHCP in /etc/systemd/networkd.conf is not accepted (unknown option)

Syslog-ng broken/won't install after 16.04 > 18.04 dist upgrade https://askubuntu.com/questions/1164877/syslog-ng-broken-wont-install-after-16-04-18-04-dist-upgrade

I recently upgraded my Ubuntu Server 16.04 VM to 18.04. After the upgrade, syslog-ng was failing to start, so I purged it and tried reinstalling it. Every time I go to reinstall it, I get the "//Install failure" at the bottom of this post. The "//Status Output" is also listed as well for reference.

Things I've tried to resolve: -Manually remove any .service locations that I found via a 'find / -name 'syslog-ng'; -Ensuring there are no other syslog programs installed (i.e. rsyslog) via an 'apt purge sy[tab tab]'; -Deleted old kernel files via 'apt remove linux-[tab tab]; -Ensure there are no other programs listening on 514 via 'netstat -ptan | grep 514'; -Installed, purged, rebooted, and tried again. No success.

I'm kind of lost here. I'm by no means a linux guru, but I can navigate and program fairly well. I'm just not understanding what's going on. Any help would be greatly appreciated.

//Status Output

● syslog-ng.service - System [HOSTNAME] Daemon
   Loaded: loaded (/lib/systemd/system/syslog-ng.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2019-08-10 20:04:59 EDT; 3min 27s ago
     Docs: man:syslog-ng(8)
  Process: 14296 ExecStart=/usr/sbin/syslog-ng -F $SYSLOGNG_OPTS (code=exited, status=1/FAILURE)
 Main PID: 14296 (code=exited, status=1/FAILURE)
   Status: "Starting up... (Sat Aug 10 20:04:58 2019"

Aug 10 20:04:58 [HOSTNAME] systemd[1]: Failed to start System [HOSTNAME] Daemon.
Aug 10 20:04:59 [HOSTNAME] systemd[1]: syslog-ng.service: Service hold-off time over, scheduling restart.
Aug 10 20:04:59 [HOSTNAME] systemd[1]: syslog-ng.service: Scheduled restart job, restart counter is at 5.
Aug 10 20:04:59 [HOSTNAME] systemd[1]: Stopped System [HOSTNAME] Daemon.
Aug 10 20:04:59 [HOSTNAME] systemd[1]: syslog-ng.service: Start request repeated too quickly.
Aug 10 20:04:59 [HOSTNAME] systemd[1]: syslog-ng.service: Failed with result 'exit-code'.
Aug 10 20:04:59 [HOSTNAME] systemd[1]: Failed to start System [HOSTNAME] Daemon.

//Install Failure

apt-get install syslog-ng
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libbson-1.0-0 libdbi1 libesmtp6 libhiredis0.13 libivykis0 libmongoc-1.0-0 libnet1 libprotobuf-c1
  librabbitmq4 libriemann-client0 libsnappy1v5 syslog-ng-core syslog-ng-mod-add-contextual-data
  syslog-ng-mod-amqp syslog-ng-mod-extra syslog-ng-mod-geoip syslog-ng-mod-getent
  syslog-ng-mod-graphite syslog-ng-mod-journal syslog-ng-mod-json syslog-ng-mod-map-value-pairs
  syslog-ng-mod-mongodb syslog-ng-mod-python syslog-ng-mod-redis syslog-ng-mod-riemann
  syslog-ng-mod-smtp syslog-ng-mod-snmptrapd-parser syslog-ng-mod-sql syslog-ng-mod-stardate
  syslog-ng-mod-stomp syslog-ng-mod-tag-parser syslog-ng-mod-xml-parser
Suggested packages:
  rabbitmq-server graphite-web mongodb-server libdbd-mysql libdbd-pgsql libdbd-sqlite3 activemq
The following NEW packages will be installed:
  libbson-1.0-0 libdbi1 libesmtp6 libhiredis0.13 libivykis0 libmongoc-1.0-0 libnet1 libprotobuf-c1
  librabbitmq4 libriemann-client0 libsnappy1v5 syslog-ng syslog-ng-core
  syslog-ng-mod-add-contextual-data syslog-ng-mod-amqp syslog-ng-mod-extra syslog-ng-mod-geoip
  syslog-ng-mod-getent syslog-ng-mod-graphite syslog-ng-mod-journal syslog-ng-mod-json
  syslog-ng-mod-map-value-pairs syslog-ng-mod-mongodb syslog-ng-mod-python syslog-ng-mod-redis
  syslog-ng-mod-riemann syslog-ng-mod-smtp syslog-ng-mod-snmptrapd-parser syslog-ng-mod-sql
  syslog-ng-mod-stardate syslog-ng-mod-stomp syslog-ng-mod-tag-parser syslog-ng-mod-xml-parser
0 upgraded, 33 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1,342 kB of archives.
After this operation, 5,547 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Extracting templates from packages: 100%
Selecting previously unselected package libbson-1.0-0.
(Reading database ... 82125 files and directories currently installed.)
Preparing to unpack .../00-libbson-1.0-0_1.9.2-1_amd64.deb ...
Unpacking libbson-1.0-0 (1.9.2-1) ...
Selecting previously unselected package libdbi1:amd64.
Preparing to unpack .../01-libdbi1_0.9.0-5_amd64.deb ...
Unpacking libdbi1:amd64 (0.9.0-5) ...
Selecting previously unselected package libesmtp6.
Preparing to unpack .../02-libesmtp6_1.0.6-4.3build1_amd64.deb ...
Unpacking libesmtp6 (1.0.6-4.3build1) ...
Selecting previously unselected package libhiredis0.13:amd64.
Preparing to unpack .../03-libhiredis0.13_0.13.3-2.2_amd64.deb ...
Unpacking libhiredis0.13:amd64 (0.13.3-2.2) ...
Selecting previously unselected package libsnappy1v5:amd64.
Preparing to unpack .../04-libsnappy1v5_1.1.7-1_amd64.deb ...
Unpacking libsnappy1v5:amd64 (1.1.7-1) ...
Selecting previously unselected package libmongoc-1.0-0.
Preparing to unpack .../05-libmongoc-1.0-0_1.9.2+dfsg-1build1_amd64.deb ...
Unpacking libmongoc-1.0-0 (1.9.2+dfsg-1build1) ...
Selecting previously unselected package libnet1:amd64.
Preparing to unpack .../06-libnet1_1.1.6+dfsg-3.1_amd64.deb ...
Unpacking libnet1:amd64 (1.1.6+dfsg-3.1) ...
Selecting previously unselected package libprotobuf-c1:amd64.
Preparing to unpack .../07-libprotobuf-c1_1.2.1-2_amd64.deb ...
Unpacking libprotobuf-c1:amd64 (1.2.1-2) ...
Selecting previously unselected package librabbitmq4:amd64.
Preparing to unpack .../08-librabbitmq4_0.8.0-1ubuntu0.18.04.1_amd64.deb ...
Unpacking librabbitmq4:amd64 (0.8.0-1ubuntu0.18.04.1) ...
Selecting previously unselected package libivykis0:amd64.
Preparing to unpack .../09-libivykis0_0.42.2-1_amd64.deb ...
Unpacking libivykis0:amd64 (0.42.2-1) ...
Selecting previously unselected package syslog-ng-mod-journal.
Preparing to unpack .../10-syslog-ng-mod-journal_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-journal (3.13.2-3) ...
Selecting previously unselected package syslog-ng-core.
Preparing to unpack .../11-syslog-ng-core_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-core (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-json.
Preparing to unpack .../12-syslog-ng-mod-json_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-json (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-extra.
Preparing to unpack .../13-syslog-ng-mod-extra_3.13.2-3_all.deb ...
Unpacking syslog-ng-mod-extra (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-tag-parser.
Preparing to unpack .../14-syslog-ng-mod-tag-parser_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-tag-parser (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-xml-parser.
Preparing to unpack .../15-syslog-ng-mod-xml-parser_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-xml-parser (3.13.2-3) ...
Selecting previously unselected package libriemann-client0:amd64.
Preparing to unpack .../16-libriemann-client0_1.9.1-1_amd64.deb ...
Unpacking libriemann-client0:amd64 (1.9.1-1) ...
Selecting previously unselected package syslog-ng-mod-sql.
Preparing to unpack .../17-syslog-ng-mod-sql_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-sql (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-mongodb.
Preparing to unpack .../18-syslog-ng-mod-mongodb_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-mongodb (3.13.2-3) ...
Selecting previously unselected package syslog-ng.
Preparing to unpack .../19-syslog-ng_3.13.2-3_all.deb ...
Unpacking syslog-ng (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-add-contextual-data.
Preparing to unpack .../20-syslog-ng-mod-add-contextual-data_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-add-contextual-data (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-amqp.
Preparing to unpack .../21-syslog-ng-mod-amqp_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-amqp (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-geoip.
Preparing to unpack .../22-syslog-ng-mod-geoip_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-geoip (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-getent.
Preparing to unpack .../23-syslog-ng-mod-getent_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-getent (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-graphite.
Preparing to unpack .../24-syslog-ng-mod-graphite_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-graphite (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-map-value-pairs.
Preparing to unpack .../25-syslog-ng-mod-map-value-pairs_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-map-value-pairs (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-python.
Preparing to unpack .../26-syslog-ng-mod-python_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-python (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-redis.
Preparing to unpack .../27-syslog-ng-mod-redis_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-redis (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-riemann.
Preparing to unpack .../28-syslog-ng-mod-riemann_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-riemann (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-smtp.
Preparing to unpack .../29-syslog-ng-mod-smtp_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-smtp (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-snmptrapd-parser.
Preparing to unpack .../30-syslog-ng-mod-snmptrapd-parser_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-snmptrapd-parser (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-stardate.
Preparing to unpack .../31-syslog-ng-mod-stardate_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-stardate (3.13.2-3) ...
Selecting previously unselected package syslog-ng-mod-stomp.
Preparing to unpack .../32-syslog-ng-mod-stomp_3.13.2-3_amd64.deb ...
Unpacking syslog-ng-mod-stomp (3.13.2-3) ...
Setting up libhiredis0.13:amd64 (0.13.3-2.2) ...
Setting up libdbi1:amd64 (0.9.0-5) ...
Setting up libnet1:amd64 (1.1.6+dfsg-3.1) ...
Processing triggers for ureadahead (0.100.0-21) ...
Setting up libbson-1.0-0 (1.9.2-1) ...
Setting up libesmtp6 (1.0.6-4.3build1) ...
Setting up libprotobuf-c1:amd64 (1.2.1-2) ...
Setting up libivykis0:amd64 (0.42.2-1) ...
Setting up libriemann-client0:amd64 (1.9.1-1) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Setting up libsnappy1v5:amd64 (1.1.7-1) ...
Processing triggers for systemd (237-3ubuntu10.25) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Setting up libmongoc-1.0-0 (1.9.2+dfsg-1build1) ...
Setting up librabbitmq4:amd64 (0.8.0-1ubuntu0.18.04.1) ...
Setting up syslog-ng-mod-journal (3.13.2-3) ...
Setting up syslog-ng-core (3.13.2-3) ...
Job for syslog-ng.service failed because the control process exited with error code.
See "systemctl status syslog-ng.service" and "journalctl -xe" for details.
invoke-rc.d: initscript syslog-ng, action "restart" failed.
● syslog-ng.service - System Logger Daemon
   Loaded: loaded (/lib/systemd/system/syslog-ng.service; disabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Sat 2019-08-10 20:04:57 EDT; 7ms ago
     Docs: man:syslog-ng(8)
  Process: 14194 ExecStart=/usr/sbin/syslog-ng -F $SYSLOGNG_OPTS (code=exited, status=1/FAILURE)
 Main PID: 14194 (code=exited, status=1/FAILURE)
   Status: "Starting up... (Sat Aug 10 20:04:57 2019"
dpkg: error processing package syslog-ng-core (--configure):
 installed syslog-ng-core package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of syslog-ng-mod-redis:
 syslog-ng-mod-redis depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-redis (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
      dpkg: dependency problems prevent configuration of syslog-ng-mod-python:
 syslog-ng-mod-python depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-python (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
      dpkg: dependency problems prevent configuration of syslog-ng-mod-map-value-pairs:
 syslog-ng-mod-map-value-pairs depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-map-value-pairs (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-smtp:
 syslog-ng-mod-smtp depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-smtp (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-geoip:
 syslog-ng-mod-geoip depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-geoip (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-amqp:
 syslog-ng-mod-amqp depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-amqp (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-sql:
 syslog-ng-mod-sql depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-sql (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-json:
 syslog-ng-mod-json depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-json (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-getent:
 syslog-ng-mod-getent depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-getent (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-snmptrapd-parser:
 syslog-ng-mod-snmptrapd-parser depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-snmptrapd-parser (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng:
 syslog-ng depends on syslog-ng-core (>= 3.13.2); however:
  Package syslog-ng-core is not configured yet.
 syslog-ng depends on syslog-ng-mod-sql; however:
  Package syslog-ng-mod-sql is not configured yet.
 syslog-ng depends on syslog-ng-mod-json; however:
  Package syslog-ng-mod-json is not configured yet.

dpkg: error processing package syslog-ng (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-stomp:
 syslog-ng-mod-stomp depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-stomp (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-mongodb:
 syslog-ng-mod-mongodb depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-mongodb (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-stardate:
 syslog-ng-mod-stardate depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-stardate (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-add-contextual-data:
 syslog-ng-mod-add-contextual-data depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-add-contextual-data (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-graphite:
 syslog-ng-mod-graphite depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-graphite (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-riemann:
 syslog-ng-mod-riemann depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-riemann (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-tag-parser:
 syslog-ng-mod-tag-parser depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-tag-parser (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-xml-parser:
 syslog-ng-mod-xml-parser depends on syslog-ng-abi-3.13-0; however:
  Package syslog-ng-abi-3.13-0 is not installed.
  Package syslog-ng-core which provides syslog-ng-abi-3.13-0 is not configured yet.

dpkg: error processing package syslog-ng-mod-xml-parser (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              dpkg: dependency problems prevent configuration of syslog-ng-mod-extra:
 syslog-ng-mod-extra depends on syslog-ng-mod-json (>= 3.13.2-3); however:
  Package syslog-ng-mod-json is not configured yet.
 syslog-ng-mod-extra depends on syslog-ng-mod-json (<< 3.13.2-3.1~); however:
  Package syslog-ng-mod-json is not configured yet.

dpkg: error processing package syslog-ng-mod-extra (--configure):
 dependency problems - leaving unconfigured
No apport report written because MaxReports is reached already
                                                              Processing triggers for libc-bin (2.27-3ubuntu1) ...
Errors were encountered while processing:
 syslog-ng-core
 syslog-ng-mod-redis
 syslog-ng-mod-python
 syslog-ng-mod-map-value-pairs
 syslog-ng-mod-smtp
 syslog-ng-mod-geoip
 syslog-ng-mod-amqp
 syslog-ng-mod-sql
 syslog-ng-mod-json
 syslog-ng-mod-getent
 syslog-ng-mod-snmptrapd-parser
 syslog-ng
 syslog-ng-mod-stomp
 syslog-ng-mod-mongodb
 syslog-ng-mod-stardate
 syslog-ng-mod-add-contextual-data
 syslog-ng-mod-graphite
 syslog-ng-mod-riemann
 syslog-ng-mod-tag-parser
 syslog-ng-mod-xml-parser
 syslog-ng-mod-extra
E: Sub-process /usr/bin/dpkg returned an error code (1)

Adding sources list and journalctl output.

//Journalctl output

-- Unit syslog-ng.service has failed.
--
-- The result is RESULT.
Aug 11 21:32:22 [HOSTNAME] systemd[1]: syslog-ng.service: Service hold-off time over, scheduling restart.
Aug 11 21:32:22 [HOSTNAME] systemd[1]: syslog-ng.service: Scheduled restart job, restart counter is at 5.
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Automatic restarting of the unit syslog-ng.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Aug 11 21:32:22 [HOSTNAME] systemd[1]: Stopped System Logger Daemon.
-- Subject: Unit syslog-ng.service has finished shutting down
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit syslog-ng.service has finished shutting down.
Aug 11 21:32:22 [HOSTNAME] systemd[1]: syslog-ng.service: Start request repeated too quickly.
Aug 11 21:32:22 [HOSTNAME] systemd[1]: syslog-ng.service: Failed with result 'exit-code'.
Aug 11 21:32:22 [HOSTNAME] systemd[1]: Failed to start System Logger Daemon.
-- Subject: Unit syslog-ng.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit syslog-ng.service has failed.
--
-- The result is RESULT.

//Sources

cat /etc/apt/sources.list | grep deb
# deb cdrom:[Ubuntu-Server 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.3)]/ xenial main restricted
# deb cdrom:[Ubuntu-Server 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.3)]/ xenial main restricted
deb http:// us.archive.ubuntu. com/ubuntu/ bionic main restricted
# deb-src http:// us.archive.ubuntu. com/ubuntu/ xenial main restricted
deb http://us.archive.ubuntu. com/ubuntu/ bionic-updates main restricted
# deb-src http:// us.archive.ubuntu. com/ubuntu/ xenial-updates main restricted
deb http:// us.archive.ubuntu. com/ubuntu/ bionic universe
# deb-src http:// us.archive.ubuntu. com/ubuntu/ xenial universe
deb http:// us.archive.ubuntu. com/ubuntu/ bionic-updates universe
# deb-src http:// us.archive.ubuntu. com/ubuntu/ xenial-updates universe
deb http:// us.archive.ubuntu. com/ubuntu/ bionic multiverse
# deb-src http:// us.archive.ubuntu. com/ubuntu/ xenial multiverse
deb http:// us.archive.ubuntu. com/ubuntu/ bionic-updates multiverse
# deb-src http:// us.archive.ubuntu. com/ubuntu/ xenial-updates multiverse
deb http:// us.archive.ubuntu. com/ubuntu/ bionic-backports main restricted universe multiverse
# deb-src http:// us.archive.ubuntu. com/ubuntu/ xenial-backports main restricted universe multiverse
# deb http:// archive.canonical. com/ubuntu xenial partner
# deb-src http:// archive.canonical. com/ubuntu xenial partner
deb http:// security.ubuntu. com/ubuntu bionic-security main restricted
# deb-src http:// security.ubuntu. com/ubuntu xenial-security main restricted
deb http:// security.ubuntu. com/ubuntu bionic-security universe
# deb-src http:// security.ubuntu. com/ubuntu xenial-security universe
deb http:// security.ubuntu. com/ubuntu bionic-security multiverse
# deb-src http:// security.ubuntu. com/ubuntu xenial-security multiverse
Creating a Portable Ubuntu 18.04 OS in a External SSD https://askubuntu.com/questions/1110115/creating-a-portable-ubuntu-18-04-os-in-a-external-ssd

I have been trying from last few days to create a Portable OS. My reasons being

  1. Avoiding Dual Boot
  2. To make the OS like Plug and Play

Before trying on External SSD as they are costly, I first tried installing OS on a 32 GB Sandisk Flashdrive which is working very smoothly. Hence I removed all the boot options other than my current windows and I tried installing on my SSD.

I bought Sandisk Extreme and Samsung T5 but Ubuntu Installation didn’t go through as planned. On both the drives it went Straight up to the GRUB Command Line. This feels like the BLUE SCREEN OF DEATH FOR UBUNTU. I must have tried installing more than 10 times, with the help of Answers on Internet.

How To Rescue Non Booting Grub2

I went through step by step as shown in this link. Even in my case I can see content only in (hd0, 1)/ . But I can see only 1 folder which is efi/. I cannot see any other folders that are shown in the link. Same answer is posted everywhere.

Folders - lost+found/ bin/ boot/ cdrom/ dev/ etc/ home/ lib/ lib64/ media/ mnt/ opt/ proc/ root/ run/ sbin/ srv/ sys/ tmp/ usr/ var/ vmlinuz vmlinuz.old initrd.img initrd.img.old

None of these folders are visible for me.

Let me Tell you my Ubuntu installation process.

  1. Opened the Try and Install Ubuntu
  2. Went through the initial installation process
  3. Clicked on Something Else
  4. 16GB for Swap (logical and end of the storage)
  5. Rest for primary, ext4 and root as “/“ partition
  6. Next , Next ....

This is what I followed.

I have reached the CONCLUSION that Ubuntu cannot be installed in an External SSD I HOPE IT”S NOT TRUE AND THERE SHOULD BE A WAY AROUND. It worked perfectly well in PenDrive. I could just plug the pendrive(INSTALLED OS AND NOT THE BOOTABLE) and start using Ubuntu.

I chose SSD because it is more durable as well as faster than a hdd.

I am open to any Suggestions to Improve my above long Question with Explanation if it’s not Understandable.

Please Let me know if any more details are required from my side.

enter image description here GRUB command line

How to visit a webpage using PuTTY? https://askubuntu.com/questions/1109529/how-to-visit-a-webpage-using-putty

I'm using Ubuntu VPS server, and I want to do a simple thing. I want to go to a webpage through the terminal to do a couple of checks regarding my website's traffic. I just need it to open a browser (not visually of course), go to a URL, and that's it. How do I do that guys?

MacOS-like file preview with spacebar for Xubuntu https://askubuntu.com/questions/887464/macos-like-file-preview-with-spacebar-for-xubuntu

I came across a question on Ask Ubuntu that mentioned that Ubuntu ships with a similar feature to macOS' preview, where you can select a file and press the spacebar to get a preview of the file.

However, I am using Xubuntu 16.04 which is a blend of Linux that uses Xfce which has a different file manager (Thunar) and doesn't seem to support this feature. When I press the spacebar, it just opens the file the same way like double clicking on it would.

Is there a way to get this feature in Xubuntu?

Is there a way to enable tap to click for the Thinkpad trackpoint using systemd in 15.04? https://askubuntu.com/questions/612413/is-there-a-way-to-enable-tap-to-click-for-the-thinkpad-trackpoint-using-systemd

Is there a way to enable tap to click for the Thinkpad trackpoint using systemd in 15.04? I know sensitivity can be adjusted, but I have not seen a way to enable tap to click. There's instructions here on how to adjust sensitivity under systemd:

Increase Trackpoint Sensititvity with SystemD (Ubuntu 15.04 or later)

I've not found out how to enable tap to click though

Ralink RT3290 wifi driver is not working in 14.04 https://askubuntu.com/questions/567806/ralink-rt3290-wifi-driver-is-not-working-in-14-04

I tried this but I got this error:

sudo dkms install -m rt3290sta -v 2.6.0.0 --force
Error! Could not find module source directory.
Directory: /usr/src/rt3290sta-2.6.0.0 does not exist.
How to configure iBall airway 3G usb modem in Ubuntu 14.04 https://askubuntu.com/questions/530034/how-to-configure-iball-airway-3g-usb-modem-in-ubuntu-14-04

I bought new iball Airway 21MP 3G modem last month. But Ubuntu 14.04 doesn't detect my device. It is perfectly working in windows with installed driver. I'm not getting an option to "Enable mobile broadband" in top panel. but lsusb list the device

root@eldho-Latitude-E6410:~# lsusb
Bus 002 Device 005: ID 1782:0003 Spreadtrum Communications Inc. -------->>>>
root@eldho-Latitude-E6410:~#

As per the link " How do I get an iball 3.5G modem working on Ubuntu?"
I captured the USB sniffs to find the switch event for a working product ID and vendor ID.
But it shows the same ID in that too.

Please help....!!!!

How do I create a persistent Fedora live USB? https://askubuntu.com/questions/457638/how-do-i-create-a-persistent-fedora-live-usb

I have successfully created a live USB for Fedora 20 on my Ubuntu 12.04 using dd:

sudo dd bs=8M if=Fedora-Live-Desktop-x86_64-20-1.iso of=/dev/sdb

...but I have not been able to find out how to make it persistent. Do you have any suggestions?

Startup Disk Creator is not an option because I am unable to select an ISO file.

UNetbootin failed when I added 512 MB that should persist and also without it. (using a 2 GB USB stick)

Warning: Could not boot
Warning: /dev/disk/by-label/Fedora-Live-Desktop-x86_64-20-1 does not exist
Warning: /dev/mapper/live-rw does not exist

Resulting logs: rdsosreport, journalctl

How do I disable mouse magnet on middle edge with multi monitors? https://askubuntu.com/questions/109338/how-do-i-disable-mouse-magnet-on-middle-edge-with-multi-monitors

I use Ubuntu 12.04 on a two screen setup. Multiscreen on 12.04 has generally become much better, but there is one thing that really gets on my nerves: there's a mouse magnet of sorts on the middle edge (between the two screens). It's undoubtedly there to make it easier to interact with the launcher on the right screen. But I have enough trust in my mousing skills, the magnet is more annoying than helpful in my case. Can I disable it somehow?

I have installed python-doc. How can I access it? https://askubuntu.com/questions/101681/i-have-installed-python-doc-how-can-i-access-it

Sorry if this is a such an obvious question, but where does Ubuntu put documentation packages for python, node.js, redis, mysql, mongodb, and other applications?

And why I cannot access it by typing python-doc in the terminal?