Escape key in vim sometimes suspends Gnome https://askubuntu.com/questions/1568835/escape-key-in-vim-sometimes-suspends-gnome

I use vim in gnome-terminal a whole lot everyday, and that means of course that I use the Escape key a lot. Sometimes when I hit Escape to exit vim's input mode, the result instead is that Gnome suspends (locks?), requiring me to wake it up and give it my password to get back in. When I do get back in, it's both evident and unsurprising that vim had not received the \033 character because it remains in input mode. So I have to hit Escape a second time (and sometimes this one too gets captured and results in another screen lock). This happens maybe three or four times over the course of an 8–10-hour work day, apparently at random—I have not found any pattern to when or why.

I'm running Ubuntu 26.04 LTS on an Acer Aspire 5, but the same thing happened in 24.04 LTS.

It seems to me most likely that I have an unfortunate setting for some Gnome configuration, but when I search for either "escape" or "ESC" within "Keyboard Shortcuts" in the Settings app, I find only these three entries:

Action Shortcut
Switch system controls directly Ctrl+Alt+Escape
Switch windows directly Alt+Escape
Restore the keyboard shortcuts Super+Escape

Besides, a hypothetical conflict with some rogue key binding doesn't go very far in explaining why the undesirable behavior (locking Gnome) is intermittent.

Per this post, I also looked at the settings in gnome-terminal's main menu and found nothing bound to Escape.

What's causing this problem, and what are some fixes?

Riattivazione molto lenta del PC dalla sospensione [closed] https://askubuntu.com/questions/1568834/riattivazione-molto-lenta-del-pc-dalla-sospensione

Salve. Ho installato Kubuntu 26.04 LTS sul mio notebook HP 250 G7 (processore Intel Core i3 7020U, 16 GB di RAM, SSD nvme da 256 GB) ed ho un problema: quando sospendo il PC (tramite l'apposita opzione nel menù o chiudendo il coperchio) la riattivazione è molto lenta (a volte richiede anche minuti prima che il PC si riattivi mostrando la schermata di login. In precedenza avevo Windows 10, sostituito in seguito con Zorin OS 17.3 e non ho mai avuto questo problema. Da Zorin OS 18 ho iniziato a riscontrarlo. Ho provato anche con Ubuntu 26.04 LTS ma il problema purtroppo persiste: come posso risolvere?

Cyrillic fonts in LaTeX, check which of them are installed https://askubuntu.com/questions/1568833/cyrillic-fonts-in-latex-check-which-of-them-are-installed

I want to check which Cyrillic LaTeX fonts are installed on my computer.
I tried to compile an LaTeX file, which I had in an old computer, and could compile on that old computer. But when I try compile it on my newer computer I got following messages

Missing character: There is no е ("435) in font larm1200!

Missing character: There is no т ("442) in font larm1200!

Missing character: There is no ы ("44B) in font larm1200!

           ............

With other word, one such a line for every letter.

Thanks for answer!

Fingerprint Reader on Nimo laptop running Ubuntu 26.04 https://askubuntu.com/questions/1568832/fingerprint-reader-on-nimo-laptop-running-ubuntu-26-04

Running lsusb I get this output:

Bus 005 Device 002: ID 2808:c652 FocalTech FocalTech Fingerprint Device

The fingerprint option is not available in settings so I'm sure this is a missing driver issue.

I'm a linux newbie so any help in getting the fingerprint scanner to work would be super helpful!

Cursor freezing when waking from suspend? https://askubuntu.com/questions/1568831/cursor-freezing-when-waking-from-suspend

Running 26.04 LTS , Nvidia GPU.

Occasionally, but not always, when I wake the machine from suspend, the cursor is frozen.

Everything else works - I can use the keyboard to navigate.

It seems like it's losing the USB connection to my mouse. If I reboot the PC, it comes back.

I tried the method of going to my TTY session (ctrl-alt-f3) and then back to GUI, but that doesn't seem to wake the mouse.

Any ideas?

This didn't happen when running under Windows so I don't think it's a problem with the mouse specifically - it seems like Ubuntu is putting the USB devices in some sort of sleep state when suspended but not waking the mouse when resuming. I don't know enough to confirm or diagnose that, though! Pretty new to this system.

Thanks

Some icons in nautilus don't fit to zoom level - at least .img and .fits https://askubuntu.com/questions/1568829/some-icons-in-nautilus-dont-fit-to-zoom-level-at-least-img-and-fits

Brand new installation of 26.04 on a Lenovo laptop, and I'm looking at some old files in Nautilus - this is the list view:

enter image description here

In grid view, the icon size fits when at next-to-biggest zoom level, but the icons don't change size when adjusting zoom level. This is the smallest zoom level:

enter image description here

As can be seen, these are all .img-files - in other directories I have the same problem with .fits-files.

So I thought maybe it's just unknown files - but I tried creating files e.g. asdf.qgtzx and they zoom nicely.

What's going on here?

My system running on 26.04 will not boot after kernel update to 7.0.0-29 : EFI stub: WARNING: failed to measure data for event 1: 08000000000000000b https://askubuntu.com/questions/1568828/my-system-running-on-26-04-will-not-boot-after-kernel-update-to-7-0-0-29-efi-s

My system does not finish the normal boot sequence after updating to the kernel version 7.0.0-29.

The boot screen will show the grub list and boot using the default option after the timer expires but does not get to the login screen. It does bot throw any errors when trying to boot like this.

When I select the recovery option using the same kernel version, it does boot all the way to the login screen but it does show the following error just before the boot sequence starts:

EFI stub: WARNING: failed to measure data for event 1: 08000000000000000b

I have installed the boot repair tool and created a BootInfo summary linked here

I am relatively new on Linux and I am not sure how to resolve this issue.

I would highly appreciate any pointers.

Brightness is screwed on my Dell after upgrading Ubuntu to the newest version [closed] https://askubuntu.com/questions/1568826/brightness-is-screwed-on-my-dell-after-upgrading-ubuntu-to-the-newest-version

I've been running Ubuntu for about two weeks now. At first it was fine, but then I upgraded Ubuntu to the newest version, and now the brightness is super dark on the laptop and it can't be fixed. My Dell is a Latitude 7300. I reinstalled the original version I had again, but I noticed it has some old video codecs and it wasn't playing videos from my Jellyfin server properly.

Is there any fix for this? I'm finally getting used to the user interface, so I don't want to go back to using Windows unless I really have to. Also this tagging system is silly. It's almost like you don't want feedback.

i updated to the newest firmwear on my laptop (lenovo thinkpad yoga l13 gen 2) and now the keyboard wont wake it from sleep https://askubuntu.com/questions/1568825/i-updated-to-the-newest-firmwear-on-my-laptop-lenovo-thinkpad-yoga-l13-gen-2-a

so, i updated my laptop (lenovo thinkpad yoga l13 gen 2) and now when it goes to sleep (usally from closing the lid) it wont wake, i have to long hold the powerbutton to turn it off completly than turn it back on.

Sound has suddenly stopped working https://askubuntu.com/questions/1568824/sound-has-suddenly-stopped-working

I am running Ubuntu 26.04 on a Ryzen 5 on a Gigabyte Aorus Elite AX V2 motherboard.

This morning, my sound does not work. It worked fine yesterday, but not today.

On the settings page, under "Sound" it shows no input or output devices.

I wanted to try it on a USB stick, but the system is not recognizing them at this moment. That happens occasionally, so I am not concerned.

From another post I see that this was requested, so I will include that:

arecord -L && inxi -A

record -L && inxi -A  
null  
    Discard all samples (playback) or generate zero samples (capture)  
lavrate  
    Rate Converter Plugin Using Libav/FFmpeg Library  
samplerate  
    Rate Converter Plugin Using Samplerate Library  
speexrate  
    Rate Converter Plugin Using Speex Resampler  
jack  
    JACK Audio Connection Kit  
oss  
    Open Sound System  
pulse  
    PulseAudio Sound Server  
speex  
    Plugin using Speex DSP (resample, agc, denoise, echo, dereverb)  
upmix  
    Plugin for channel upmix (4,6,8)  
vdownmix  
    Plugin for channel downmix (stereo) with a simple spacialization  
usbstream:CARD=Generic  
    HD-Audio Generic  
    USB Stream Output  
hw:CARD=Generic_1,DEV=0  
    HD-Audio Generic, ALC897 Analog  
    Direct hardware device without any conversions  
hw:CARD=Generic_1,DEV=2  
    HD-Audio Generic, ALC897 Alt Analog  
    Direct hardware device without any conversions  
plughw:CARD=Generic_1,DEV=0  
    HD-Audio Generic, ALC897 Analog  
    Hardware device with all software conversions  
plughw:CARD=Generic_1,DEV=2  
    HD-Audio Generic, ALC897 Alt Analog  
    Hardware device with all software conversions  
default:CARD=Generic_1  
    HD-Audio Generic, ALC897 Analog  
    Default Audio Device  
sysdefault:CARD=Generic_1  
    HD-Audio Generic, ALC897 Analog  
    Default Audio Device  
front:CARD=Generic_1,DEV=0  
    HD-Audio Generic, ALC897 Analog  
    Front output / input  
dsnoop:CARD=Generic_1,DEV=0  
    HD-Audio Generic, ALC897 Analog  
    Direct sample snooping device  
dsnoop:CARD=Generic_1,DEV=2  
    HD-Audio Generic, ALC897 Alt Analog  
    Direct sample snooping device  
usbstream:CARD=Generic_1  
    HD-Audio Generic  
    USB Stream Output  
Audio:  
  Device-1: Advanced Micro Devices [AMD/ATI] Radeon High  
    Definition Audio driver: snd_hda_intel  
  Device-2: Advanced Micro Devices [AMD] Ryzen HD Audio  
    driver: snd_hda_intel  
  API: ALSA v: k7.0.0-29-generic status: kernel-api  

I have uninstalled and reinstalled Pulseaudio and ALSA, with no effect. I would try headphones, but there is no ability to connect from the Settings menu.

I suspect that the problems lies somewhere connected to the Settings menu lack of options, but I am up in the air on this.

Possibly of some help is the fact that the output on the "Simple Wireplumber GUI" is blank under each of the headings. Is that possibly an indication?

I just saw this , although I am not certain that it offers any help:

sudo fuser -v /dev/snd/*  
aplay -lL  
lsusb -t  
sudo journalctl -b  
  
 Discard all samples (playback) or generate zero samples (capture)  
lavrate  
    Rate Converter Plugin Using Libav/FFmpeg Library  
samplerate  
    Rate Converter Plugin Using Samplerate Library  
speexrate  
    Rate Converter Plugin Using Speex Resampler  
jack  
    JACK Audio Connection Kit  
oss  
    Open Sound System  
pulse  
    PulseAudio Sound Server  
speex  
    Plugin using Speex DSP (resample, agc, denoise, echo, dereverb)  
upmix  
    Plugin for channel upmix (4,6,8)  
vdownmix  
    Plugin for channel downmix (stereo) with a simple spacialization  
hw:CARD=Generic,DEV=3  
    HD-Audio Generic, MSI MP251  
    Direct hardware device without any conversions  
hw:CARD=Generic,DEV=7  
    HD-Audio Generic, HDMI 1  
    Direct hardware device without any conversions  
hw:CARD=Generic,DEV=8  
    HD-Audio Generic, HDMI 2  
    Direct hardware device without any conversions  
hw:CARD=Generic,DEV=9  
    HD-Audio Generic, HDMI 3  
    Direct hardware device without any conversions  
plughw:CARD=Generic,DEV=3  
    HD-Audio Generic, MSI MP251  
    Hardware device with all software conversions  
plughw:CARD=Generic,DEV=7  
    HD-Audio Generic, HDMI 1  
    Hardware device with all software conversions  
plughw:CARD=Generic,DEV=8  
    HD-Audio Generic, HDMI 2  
    Hardware device with all software conversions  
plughw:CARD=Generic,DEV=9  
    HD-Audio Generic, HDMI 3  
    Hardware device with all software conversions  
hdmi:CARD=Generic,DEV=0  
    HD-Audio Generic, MSI MP251  
    HDMI Audio Output  
hdmi:CARD=Generic,DEV=1  
    HD-Audio Generic, HDMI 1  
    HDMI Audio Output  
hdmi:CARD=Generic,DEV=2  
    HD-Audio Generic, HDMI 2  
    HDMI Audio Output  
hdmi:CARD=Generic,DEV=3  
    HD-Audio Generic, HDMI 3  
    HDMI Audio Output  
dmix:CARD=Generic,DEV=3  
    HD-Audio Generic, MSI MP251  
    Direct sample mixing device  
dmix:CARD=Generic,DEV=7  
    HD-Audio Generic, HDMI 1  
    Direct sample mixing device  
dmix:CARD=Generic,DEV=8  
    HD-Audio Generic, HDMI 2  
    Direct sample mixing device  
dmix:CARD=Generic,DEV=9  
    HD-Audio Generic, HDMI 3  
    Direct sample mixing device  
usbstream:CARD=Generic  
    HD-Audio Generic  
    USB Stream Output  
hw:CARD=Generic_1,DEV=0  
    HD-Audio Generic, ALC897 Analog  
    Direct hardware device without any conversions  
plughw:CARD=Generic_1,DEV=0  
    HD-Audio Generic, ALC897 Analog  
    Hardware device with all software conversions  
default:CARD=Generic_1  
    HD-Audio Generic, ALC897 Analog  
    Default Audio Device  
sysdefault:CARD=Generic_1  
    HD-Audio Generic, ALC897 Analog  
    Default Audio Device  
front:CARD=Generic_1,DEV=0  
    HD-Audio Generic, ALC897 Analog  
    Front output / input  
surround21:CARD=Generic_1,DEV=0  
    HD-Audio Generic, ALC897 Analog  
    2.1 Surround output to Front and Subwoofer speakers  
surround40:CARD=Generic_1,DEV=0  
    HD-Audio Generic, ALC897 Analog  
    4.0 Surround output to Front and Rear speakers  
surround41:CARD=Generic_1,DEV=0  
    HD-Audio Generic, ALC897 Analog  
    4.1 Surround output to Front, Rear and Subwoofer speakers  
surround50:CARD=Generic_1,DEV=0  
    HD-Audio Generic, ALC897 Analog  
    5.0 Surround output to Front, Center and Rear speakers  
surround51:CARD=Generic_1,DEV=0  
    HD-Audio Generic, ALC897 Analog  
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers  
surround71:CARD=Generic_1,DEV=0  
    HD-Audio Generic, ALC897 Analog  
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers  
dmix:CARD=Generic_1,DEV=0  
    HD-Audio Generic, ALC897 Analog  
    Direct sample mixing device  
usbstream:CARD=Generic_1  
    HD-Audio Generic  
    USB Stream Output  
**** List of PLAYBACK Hardware Devices ****  
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [MSI MP251]  
  Subdevices: 1/1  
  Subdevice #0: subdevice #0  
card 0: Generic [HD-Audio Generic], device 7: HDMI 1 [HDMI 1]  
  Subdevices: 1/1  
  Subdevice #0: subdevice #0  
card 0: Generic [HD-Audio Generic], device 8: HDMI 2 [HDMI 2]  
  Subdevices: 1/1  
  Subdevice #0: subdevice #0  
card 0: Generic [HD-Audio Generic], device 9: HDMI 3 [HDMI 3]  
  Subdevices: 1/1  
  Subdevice #0: subdevice #0  
card 1: Generic_1 [HD-Audio Generic], device 0: ALC897 Analog [ALC897 Analog]  
  Subdevices: 1/1  
  Subdevice #0: subdevice #0  
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M  
    |__ Port 003: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M  
        |__ Port 004: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 12M  
        |__ Port 004: Dev 004, If 1, Class=Human Interface Device, Driver=usbhid, 12M  
    |__ Port 006: Dev 003, If 0, Class=Human Interface Device, Driver=usbhid, 12M  
    |__ Port 009: Dev 005, If 0, Class=Wireless, Driver=btusb, 12M  
    |__ Port 009: Dev 005, If 1, Class=Wireless, Driver=btusb, 12M  
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/5p, 20000M/x2  
    |__ Port 003: Dev 002, If 0, Class=Hub, Driver=hub/4p, 5000M  
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M  
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M  
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M  
/:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M  
/:  Bus 007.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M  
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M  
        |__ Port 002: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M  
            |__ Port 003: Dev 005, If 0, Class=Mass Storage, Driver=usb-storage, 480M  
            |__ Port 004: Dev 006, If 0, Class=Hub, Driver=hub/4p, 480M  
                |__ Port 001: Dev 007, If 0, Class=Mass Storage, Driver=usb-storage, 480M  
        |__ Port 004: Dev 004, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M  
        |__ Port 004: Dev 004, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M  
Aug 05 08:28:52 frank kernel: Linux version 7.0.0-29-generic (>  
Aug 05 08:28:52 frank kernel: Command line: BOOT_IMAGE=/boot/v>  
Aug 05 08:28:52 frank kernel: KERNEL supported cpus:  
Aug 05 08:28:52 frank kernel:   Intel GenuineIntel  
Aug 05 08:28:52 frank kernel:   AMD AuthenticAMD  
Aug 05 08:28:52 frank kernel:   Hygon HygonGenuine  
Aug 05 08:28:52 frank kernel:   Centaur CentaurHauls  
Aug 05 08:28:52 frank kernel:   zhaoxin   Shanghai    
Aug 05 08:28:52 frank kernel: BIOS-provided physical RAM map:  
Aug 05 08:28:52 frank kernel: BIOS-e820: [mem 0x00000000000000>  
Aug 05 08:28:52 frank kernel: BIOS-e820: [mem 0x00000000000a00>  
Aug 05 08:28:52 frank kernel: BIOS-e820: [mem 0x00000000001000>  
Aug 05 08:28:52 frank kernel: BIOS-e820: [mem 0x0000000009aff0>  
Aug 05 08:28:52 frank kernel: BIOS-e820: [mem 0x000000000a0000>  
Aug 05 08:28:52 frank kernel: BIOS-e820: [mem 0x000000000a2000>  
Aug 05 08:28:52 frank kernel: BIOS-e820: [mem 0x000000000a2120>  
Aug 05 08:28:52 frank kernel: BIOS-e820: [mem 0x000000000b0000>  
Aug 05 08:28:52 frank kernel: BIOS-e820: [mem 0x000000000b0210>  
Aug 05 08:28:52 frank kernel: BIOS-e820: [mem 0x000000008827e0>  
Aug 05 08:28:52 frank kernel: BIOS-e820: [mem 0x000000008e27e0>  
Aug 05 08:28:52 frank kernel: BIOS-e820: [mem 0x000000008e47f0>  
Aug 05 08:28:52 frank kernel: BIOS-e820: [mem 0x000000009047f0>  
Aug 05 08:28:52 frank kernel: BIOS-e820: [mem 0x00000000985ff0>  
lines 1-23

I am led to believe this should help if the problem is in "Pipewire"

I have just looked at Pulseaudio volume and that is being refused. It's probably a redundant comment, but that is news to me.

Having turned off the computer for an hour, I notice it is not recognizing my USB sticks either. Once in a while that is the case, but repeatedly in short succession is distinctly odd. I am going to GParted to see if it is recognized there. I am assuming that it is not. That might be a further indication of the problem.

KDE Wallet always pop up in first installation https://askubuntu.com/questions/1568823/kde-wallet-always-pop-up-in-first-installation

How to fix KDE wallet for first time installation I hate every i am install in new computer KDE Wallet always Pop Up

Booting issue ("Warning: /dev/mapper/ubuntu --vg-ubuntu--lv does not exist") https://askubuntu.com/questions/1568820/booting-issue-warning-dev-mapper-ubuntu-vg-ubuntu-lv-does-not-exist

Twice now when I boot, enter my passphrase to decrypt my drive (before entering my regular user password) it take a long time, problem, then I get the following (see image above??) (also when I power off, then turn the power back on and boot).

The strange thing is that the second time I reboot (after I select the first option "Ubuntu" from the black and white reboot screen), it boots normally without errors and all my disks/data/folders/files appear to be OK.

I am not sure what the issue may be, and whether this will increase in terms of problems. I am a relative neophyte about Ubuntu, but I know how to enter commands to check things and the like. What can I do to resolve this issue?

Upgrade dialog from 25.10 to 26.04 does nothing https://askubuntu.com/questions/1568818/upgrade-dialog-from-25-10-to-26-04-does-nothing

I want to upgrade to 26.04, however the dialog box does nothing and just closed when I pressed upgrade.

Going through the terminal also gets me nowhere, as it just tells me to install any updates available, but all the updates I do have are shown as not upgrading or kept back due to phasing (and have been for months).

:~$ sudo do-release-upgrade
[sudo: authenticate] Password:
Checking for a new Ubuntu release
Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife

Please install all available updates for your release before upgrading.
:~$ sudo apt update
Get:1 https://repo.steampowered.com/steam stable InRelease [3,622 B]
Hit:2 http://security.ubuntu.com/ubuntu questing-security InRelease                                                            
Hit:3 https://dl.google.com/linux/chrome-stable/deb stable InRelease                                                           
Hit:4 http://pl.archive.ubuntu.com/ubuntu questing InRelease                                                                   
Hit:5 http://pl.archive.ubuntu.com/ubuntu questing-updates InRelease                                               
Hit:6 http://pl.archive.ubuntu.com/ubuntu questing-backports InRelease
Hit:7 https://ppa.launchpadcontent.net/kisak/kisak-mesa/ubuntu plucky InRelease
Hit:8 https://ppa.launchpadcontent.net/obsproject/obs-studio/ubuntu questing InRelease
Fetched 3,622 B in 1s (5,203 B/s)
3 packages can be upgraded. Run 'apt list --upgradable' to see them.
Notice: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://dl.google.com/linux/chrome-stable/deb stable InRelease' doesn't support architecture 'i386'
dragonia@dragonia-System-Product-Name:~$ sudo apt upgrade
Not upgrading yet due to phasing:
  fwupd  libfwupd3

Not upgrading:
  steam-libs-i386:i386

Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 3
Notice: Some packages may have been kept back due to phasing.
My computer got stuck suddenly https://askubuntu.com/questions/1568817/my-computer-got-stuck-suddenly

My computer got stuck suddenly. This computer desktop was built with ultra 7 265k + Asus TUFF Gaming B860-PLUS WiFi. It has no GPU. My operating system is Ubuntu 24.04, and the kernel is 7.0.0-28-generic.

I configured /etc/default/grub with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pcie_aspm=off pcie_port_pm=off intel_idle.max_cstate=1 processor.max_cstate=1 zswap.enabled=0 i915.enable_psr=0 i915.enable_dc=0 intel_idle.nomwait=1 nvme_core.default_ps_max_latency_us=0 nvme_core.multipath=N sysrq_always_enabled=1 split_lock_detect=off transparent_hugepage=never".

The session type is x11 and also Wayland. The same thing happens with Ubuntu 26.04.

All of this parameter I used for testing to prevent hard hang. None of this work and also didn't work with "quiet splash"

Don't see grub OS selection menu anymore, always boots Windows https://askubuntu.com/questions/1568816/dont-see-grub-os-selection-menu-anymore-always-boots-windows

I searched, and I tried several tutorials already, but one week on, I still can only boot into Windows, no matter what I have tried.

I created a grub repair usb drive, ran the automatic repair, no change.

I got the information from Boot-Repair tool. Perhaps someone can look at it and see an obvious mistake which stops Ubuntu 24.04 from booting.

============================== Boot Info Summary ===============================

 => Windows is installed in the MBR of /dev/nvme0n1.

nvme0n1p1: _____________________________________________________________________

    File system:       vfat
    Boot sector type:  FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /efi/Boot/bkpbootx64.efi /efi/Boot/bootx64.efi 
                       /efi/Boot/fbx64.efi /efi/Boot/mmx64.efi 
                       /efi/ubuntu/grubx64.efi /efi/ubuntu/mmx64.efi 
                       /efi/ubuntu/shimx64.efi /efi/ubuntu/grub.cfg 
                       /efi/Microsoft/Boot/SecureBootRecovery.efi 
                       /efi/Microsoft/Boot/bootmgfw.efi 
                       /efi/Microsoft/Boot/bootmgr.efi 
                       /boot/grub/i386-pc/core.img

nvme0n1p2: _____________________________________________________________________

    File system:       
    Boot sector type:  -
    Boot sector info: 

nvme0n1p3: _____________________________________________________________________

    File system:       ntfs
    Boot sector type:  NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  Windows 10 or 11
    Boot files:        /Windows/System32/winload.exe

nvme0n1p4: _____________________________________________________________________

    File system:       ntfs
    Boot sector type:  NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        

nvme0n1p5: _____________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  
    Boot files:        /grub/grub.cfg

nvme0n1p6: _____________________________________________________________________

    File system:       ext4
    Boot sector type:  Grub2 (v1.99-2.00)
    Boot sector info:  Grub2 (v2.00) is installed in the boot sector of 
                       nvme0n1p6 and looks at sector 66440 of the same hard 
                       drive for core.img. core.img is at this location and 
                       looks for (,gpt1)/boot/grub. It also embeds following 
                       components:
                       
                       modules
                       -------------------------------------------------------
                       fshelp fat part_gpt biosdisk
                       -------------------------------------------------------
    Operating System:  Ubuntu 24.04.3 LTS
    Boot files:        /boot/grub/grub.cfg /etc/fstab /etc/default/grub

sda: ___________________________________________________________________________

    File system:       iso9660
    Boot sector type:  Unknown
    Boot sector info: 
    Mounting failed:   mount: /mnt/BootInfo/FD/sda: /dev/sda already mounted or mount point busy.


================================ 2 OS detected =================================

OS#1 (linux):   Ubuntu 24.04.3 LTS on nvme0n1p6
OS#2 (windows):   Windows 10 or 11 on nvme0n1p3

================================ Host/Hardware =================================

CPU architecture: 64-bit
Video: Skylake GT2 [HD Graphics 520] from Intel Corporation
Live-session OS is Linuxmint 64-bit (Linux Mint 21.2, victoria, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: 1.36.3(1.36) from Dell Inc.
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot disabled (confirmed by mokutil).
BootCurrent: 0006
Timeout: 0 seconds
BootOrder: 0006,0007,0000,0001,0002,0003,0004,0005
Boot0000* Windows Boot Manager  HD(1,GPT,59d9ad93-4a6e-4b0d-8989-2bb20faa2a8a,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...,................
Boot0001* Diskette Drive    BBS(Floppy,Diskette Drive,0x0)..BO
Boot0002* M.2 PCIe SSD  BBS(HD,INTEL SSDPEKNW512G8H ,0x0)..BO
Boot0003* USB Storage Device    BBS(USB,Generic Flash Disk 8.07,0x0)..BO
Boot0004* CD/DVD/CD-RW Drive    BBS(CDROM,CD/DVD/CD-RW Drive,0x0)..BO
Boot0005* Onboard NIC   BBS(Network,IBA CL Slot 00FE v0110,0x0)..BO
Boot0006* ubuntu    PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/HD(1,MBR,0x14eb2669,0x23c,0x2130)/File(\EFI\boot\grubx64.efi)
Boot0007* UEFI: INTEL SSDPEKNW512G8H, Partition 1   HD(1,GPT,59d9ad93-4a6e-4b0d-8989-2bb20faa2a8a,0x800,0x32000)/File(EFI\Microsoft\Boot\bootmgfw.efi)..BO

07e25dcaf57c776875f78fa36827c58e   nvme0n1p1/Boot/bkpbootx64.efi
07e25dcaf57c776875f78fa36827c58e   nvme0n1p1/Boot/bootx64.efi
39bc76ff6662f4fbe9aa116e4c997b41   nvme0n1p1/Boot/fbx64.efi
4ba5a5aad43c197e9fb58b76b404d287   nvme0n1p1/Boot/mmx64.efi
94c7467f956700d44c5b4dcd3967535c   nvme0n1p1/ubuntu/grubx64.efi
4ba5a5aad43c197e9fb58b76b404d287   nvme0n1p1/ubuntu/mmx64.efi
07e25dcaf57c776875f78fa36827c58e   nvme0n1p1/ubuntu/shimx64.efi
7918e876cbdea0d4fff0fbf55a2e8184   nvme0n1p1/Microsoft/Boot/SecureBootRecovery.efi
3a796d91c84cb79d704ac39aa5d6760c   nvme0n1p1/Microsoft/Boot/bootmgfw.efi
674435479f27e62028fb3bfb3c5b1176   nvme0n1p1/Microsoft/Boot/bootmgr.efi

============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

nvme0n1 : is-GPT,   no-BIOSboot,    has---ESP,  not-usb,    not-mmc, has-os,    has-win,    2048 sectors * 512 bytes

Partitions info (1/3): _________________________________________________________

nvme0n1p1   : no-os,    64, nopakmgr,   no-docgrub, nogrub, nogrubinstall,  no-grubenv, noupdategrub,   not-far
nvme0n1p3   : is-os,    64, nopakmgr,   no-docgrub, nogrub, nogrubinstall,  no-grubenv, noupdategrub,   end-after-100GB
nvme0n1p4   : no-os,    64, nopakmgr,   no-docgrub, nogrub, nogrubinstall,  no-grubenv, noupdategrub,   end-after-100GB
nvme0n1p5   : no-os,    64, nopakmgr,   no-docgrub, nogrub, nogrubinstall,  grubenv-ok, noupdategrub,   end-after-100GB
nvme0n1p6   : is-os,    64, apt-get,    signed grub-efi ,   grub2,  grub-install,   grubenv-ok, update-grub,    end-after-100GB

Partitions info (2/3): _________________________________________________________

nvme0n1p1   : is---ESP, part-has-no-fstab,  no-nt,  no-winload, no-recov-nor-hid,   no-bmgr,    notwinboot, vfat
nvme0n1p3   : isnotESP, part-has-no-fstab,  no-nt,  haswinload, no-recov-nor-hid,   no-bmgr,    notwinboot, ntfs
nvme0n1p4   : isnotESP, part-has-no-fstab,  no-nt,  no-winload, recovery-or-hidden, no-bmgr,    notwinboot, ntfs
nvme0n1p5   : isnotESP, part-has-no-fstab,  no-nt,  no-winload, no-recov-nor-hid,   no-bmgr,    notwinboot, ext4
nvme0n1p6   : isnotESP, fstab-has-goodEFI,  no-nt,  no-winload, no-recov-nor-hid,   no-bmgr,    notwinboot, ext4

Partitions info (3/3): _________________________________________________________

nvme0n1p1   : not--sepboot, no-kernel,  part-has-no-fstab,  not-sep-usr,    no---usr,   part-has-no-fstab,  no--grub.d, nvme0n1
nvme0n1p3   : not--sepboot, no---boot,  part-has-no-fstab,  not-sep-usr,    no---usr,   part-has-no-fstab,  no--grub.d, nvme0n1
nvme0n1p4   : not--sepboot, no---boot,  part-has-no-fstab,  not-sep-usr,    no---usr,   part-has-no-fstab,  no--grub.d, nvme0n1
nvme0n1p5   : maybesepboot, no---boot,  part-has-no-fstab,  not-sep-usr,    no---usr,   part-has-no-fstab,  no--grub.d, nvme0n1
nvme0n1p6   : not--sepboot, with-boot,  fstab-without-boot, not-sep-usr,    with--usr,  fstab-without-usr,  std-grub.d, nvme0n1

fdisk -l (filtered): ___________________________________________________________

Disk nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk identifier: E78CBBF1-E904-423C-A9D6-61E03F2D447F
             Start        End   Sectors   Size Type
nvme0n1p1      2048     206847    204800   100M EFI System
nvme0n1p2    206848     239615     32768    16M Microsoft reserved
nvme0n1p3    239616  835328652 835089037 398.2G Microsoft basic data
nvme0n1p4 835330048  836372479   1042432   509M Windows recovery environment
nvme0n1p5 836372480  842532863   6160384   2.9G Linux filesystem
nvme0n1p6 842532864 1000212479 157679616  75.2G Linux filesystem
Disk sda: 29.3 GiB, 31457280000 bytes, 61440000 sectors
Disk identifier: 0x14eb2669
     Boot   Start      End  Sectors  Size Id Type
sda1  *          0  5138431  5138432  2.5G  0 Empty
sda2           572     9067     8496  4.1M ef EFI (FAT-12/16/32)
sda3       5140480 61439999 56299520 26.8G 83 Linux

parted -lm (filtered): _________________________________________________________

sda:31.5GB:scsi:512:512:msdos:Generic Flash Disk:;
2:293kB:4643kB:4350kB:::esp;
3:2632MB:31.5GB:28.8GB:ext4::;
nvme0n1:512GB:nvme:512:512:gpt:INTEL SSDPEKNW512G8H:;
1:1049kB:106MB:105MB:fat32:EFI system partition:boot, esp;
2:106MB:123MB:16.8MB::Microsoft reserved partition:msftres;
3:123MB:428GB:428GB:ntfs:Basic data partition:msftdata;
4:428GB:428GB:534MB:ntfs::hidden, diag;
5:428GB:431GB:3154MB:ext4::;
6:431GB:512GB:80.7GB:ext4::;

Free space >10MiB: ______________________________________________________________

sda: 4.43MiB:2510MiB:2506MiB

blkid (filtered): ______________________________________________________________

NAME        FSTYPE   UUID                                 PARTUUID                             LABEL                  PARTLABEL
sda         iso9660  2023-12-23-05-05-55-00                                                    Boot-Repair-Disk 64bit 
├─sda1      iso9660  2023-12-23-05-05-55-00               14eb2669-01                          Boot-Repair-Disk 64bit 
├─sda2      vfat     8D6C-A9F8                            14eb2669-02                          ESP                    
└─sda3      ext4     edc3aaae-5be2-4131-8986-f6d0557cbdc0 14eb2669-03                          writable               
nvme0n1                                                                                                               
├─nvme0n1p1 vfat     3885-6BF2                            59d9ad93-4a6e-4b0d-8989-2bb20faa2a8a                        EFI system partition
├─nvme0n1p2                                               d25b1fd7-3db8-4dd4-97ec-fd651e020d41                        Microsoft reserved partition
├─nvme0n1p3 ntfs     04DA90B5DA90A488                     5f75025d-22ba-4eb8-bf94-3f4bfb26ed7b                        Basic data partition
├─nvme0n1p4 ntfs     7C10F23E10F1FEC8                     797e2163-0960-4e13-9317-3f497f916c39                        
├─nvme0n1p5 ext4     f5f74cd9-0b33-42b9-8821-f29a0e7ea4c5 349d04b7-2265-41f6-8749-fd40bf98eb43                        
└─nvme0n1p6 ext4     f154bc0e-d890-47c5-bb2c-b61162cbe77a c81ca9a0-d339-4f56-a91c-689f687c4993                        

Mount points (filtered): _______________________________________________________

                                                             Avail Use% Mounted on
/dev/nvme0n1p1                                                 49M  49% /mnt/boot-sav/nvme0n1p1
/dev/nvme0n1p3                                              307.6G  23% /mnt/boot-sav/nvme0n1p3
/dev/nvme0n1p4                                               88.3M  83% /mnt/boot-sav/nvme0n1p4
/dev/nvme0n1p5                                                2.2G   0% /mnt/boot-sav/nvme0n1p5
/dev/nvme0n1p6                                               46.2G  32% /mnt/boot-sav/nvme0n1p6
/dev/sda1                                                        0 100% /cdrom

Mount options (filtered): ______________________________________________________

/dev/nvme0n1p1                                              vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
/dev/nvme0n1p3                                              fuseblk         ro,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme0n1p4                                              fuseblk         ro,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme0n1p5                                              ext4            rw,relatime
/dev/nvme0n1p6                                              ext4            rw,relatime
/dev/sda1                                                   iso9660         ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8

=================== nvme0n1p1/efi/ubuntu/grub.cfg (filtered) ===================

search.fs_uuid f154bc0e-d890-47c5-bb2c-b61162cbe77a root 
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

================= nvme0n1p1: Location of files loaded by Grub ==================

           GiB - GB             File                                 Fragment(s)
            ?? = ??             boot/grub/i386-pc/core.img                     1

====================== nvme0n1p5/grub/grub.cfg (filtered) ======================

Windows Boot Manager (on nvme0n1p1)   osprober-efi-3885-6BF2
### END /etc/grub.d/30_os-prober ###
UEFI Firmware Settings   uefi-firmware
### END /etc/grub.d/30_uefi-firmware ###

================= nvme0n1p5: Location of files loaded by Grub ==================

           GiB - GB             File                                 Fragment(s)
 399.364032745 = 428.813864960  grub/grub.cfg                                  1

=================== nvme0n1p6/boot/grub/grub.cfg (filtered) ====================

Ubuntu   f154bc0e-d890-47c5-bb2c-b61162cbe77a
Windows Boot Manager (on nvme0n1p1)   osprober-efi-3885-6BF2
### END /etc/grub.d/30_os-prober ###
UEFI Firmware Settings   uefi-firmware
### END /etc/grub.d/30_uefi-firmware ###

======================== nvme0n1p6/etc/fstab (filtered) ========================

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p6 during curtin installation
/dev/disk/by-uuid/f154bc0e-d890-47c5-bb2c-b61162cbe77a / ext4 defaults 0 1
# /boot/efi was on /dev/nvme0n1p1 during curtin installation
/swap.img   none    swap    sw  0   0
UUID=3885-6BF2  /boot/efi       vfat    defaults      0       1

==================== nvme0n1p6/etc/default/grub (filtered) =====================

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || echo Ubuntu`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
GRUB_DISABLE_OS_PROBER=false

================= nvme0n1p6: Location of files loaded by Grub ==================

           GiB - GB             File                                 Fragment(s)
 402.147296906 = 431.802372096  boot/grub/grub.cfg                             1
 431.977497101 = 463.832305664  boot/vmlinuz                                   1
 474.172809601 = 509.139177472  boot/vmlinuz-6.17.0-20-generic                 1
 431.977497101 = 463.832305664  boot/vmlinuz-6.17.0-22-generic                 1
 474.172809601 = 509.139177472  boot/vmlinuz.old                               1
 416.089687347 = 446.772899840  boot/initrd.img                                4
 476.370933533 = 511.499395072  boot/initrd.img-6.17.0-20-generic              1
 416.089687347 = 446.772899840  boot/initrd.img-6.17.0-22-generic              4
 476.370933533 = 511.499395072  boot/initrd.img.old                            1

=================== nvme0n1p6: ls -l /etc/grub.d/ (filtered) ===================

-rwxr-xr-x 1 root root 18133 Sep 11  2024 10_linux
-rwxr-xr-x 1 root root 43202 Sep 11  2024 10_linux_zfs
-rwxr-xr-x 1 root root 14513 Sep 11  2024 20_linux_xen
-rwxr-xr-x 1 root root   786 Sep 11  2024 25_bli
-rwxr-xr-x 1 root root 13120 Sep 11  2024 30_os-prober
-rwxr-xr-x 1 root root  1174 Sep 11  2024 30_uefi-firmware
-rwxr-xr-x 1 root root   722 Dec  5  2024 35_fwupd
-rwxr-xr-x 1 root root   214 Sep 11  2024 40_custom
-rwxr-xr-x 1 root root   215 Sep 11  2024 41_custom

Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would reinstall the grub-efi of
nvme0n1p6,
using the following options:  nvme0n1p1/boot/efi
Additional repair would be performed: unhide-bootmenu-10s use-standard-efi-file restore-efi-backups

Final advice in case of suggested repair: ______________________________________

Please do not forget to make your UEFI firmware boot on the Ubuntu 24.04.3 LTS entry (nvme0n1p1/efi/****/grub****.efi (**** will be updated in the final message) file) !
If your computer reboots directly into Windows, try to change the boot order in your UEFI firmware.
If your UEFI firmware does not allow to change the boot order, change the default boot entry of the Windows bootloader.
For example you can boot into Windows, then type the following command in an admin command prompt:
bcdedit /set {bootmgr} path \EFI\****\grub****.efi (**** will be updated in the final message)
Encrypted partition on HDD doesn't get bigger than 2TB https://askubuntu.com/questions/1568815/encrypted-partition-on-hdd-doesnt-get-bigger-than-2tb

On an 8TB external HDD, I created an encrypted partition using cryptsetup:

sudo cryptsetup luksFormat /dev/sdX
sudo cryptsetup open /dev/sdX encrypted_drive
sudo mkfs.ext4 /dev/mapper/encrypted_drive

I am wondering why the partition created on the disk is not bigger than 2TB?!

I have tried to expand/enlarge the partition, but I had no success.

Install wireshark with debian package https://askubuntu.com/questions/1568814/install-wireshark-with-debian-package

Can't use "apt install wireshark" - due to proxy issues.

I'm fine with using a "dpkg -i " to install wireshark.

I don't know where to get the package itself. wireshark.org doesn't seem to have it. Other sites seem to indicate that it's available - but the links don't work, etc.

Looking for ideas as to what to try next.

Ubuntu 26.04 LTS Server cannot see hardware RAID-1 on Supermicro EPYC server - Software RAID won't allow a boot device https://askubuntu.com/questions/1568810/ubuntu-26-04-lts-server-cannot-see-hardware-raid-1-on-supermicro-epyc-server-s

This is a crazy problem with a brand new UEFI system where the boot USB doesn't even see the hardware RAID-1 drives (1TB SSD, 8TB SATA). Of course it has the latest AMI Bios and the RAID has been set up properly.

When I follow the "Try or install Ubuntu" prompt it doesn't see the RAID drives but it DOES see the individual drives. What gives? Am I missing something in the UEFI settings or is there an issue with the Ubuntu installer? This is a 64GB ECC Epyc CPU and should be an easy install.

If I use custom disk layout I can create a software RAID and set up the boot/root on the SSD but it DOES NOT allow me to continue, as if I haven't chosen a boot device so I think the installer has an issue.

Install gimp-plugins-gmic from snap https://askubuntu.com/questions/1568794/install-gimp-plugins-gmic-from-snap

I have gimp and gimp-plugins-gmic installed from snap

$ snap list gimp-plugins-gmic 
Name               Version  Rev  Tracking       Publisher  Notes
gimp-plugins-gmic  4.0.2    31   latest/stable  wfrench    -
$ snap list gimp
Name  Version  Rev  Tracking       Publisher  Notes
gimp  3.2.4    560  latest/stable  gimp✓      -
$ snap connections gimp-plugins-gmic 
Interface                Plug               Slot                            Notes
content[gimp-plugins-3]  gimp:gimp-plugins  gimp-plugins-gmic:gimp-plugins  -
$ snap connections gimp
Interface                Plug                  Slot                            Notes
alsa                     gimp:alsa             -                               -
content[gimp-plugins-3]  gimp:gimp-plugins     gimp-plugins-gmic:gimp-plugins  -
content[gnome-46-2404]   gimp:gnome-46-2404    gnome-46-2404:gnome-46-2404     -
content[gpu-2404]        gimp:gpu-2404         mesa-2404:gpu-2404              -
content[gtk-3-themes]    gimp:gtk-3-themes     gtk-common-themes:gtk-3-themes  -
content[icon-themes]     gimp:icon-themes      gtk-common-themes:icon-themes   -
content                  gimp:npu-libs         -                               -
content[sound-themes]    gimp:sound-themes     gtk-common-themes:sound-themes  -
cups                     gimp:cups             cups:cups                       -
custom-device            gimp:intel-npu        -                               -
dbus                     -                     gimp:dbus-gimp                  -
desktop                  gimp:desktop          :desktop                        -
desktop-legacy           gimp:desktop-legacy   :desktop-legacy                 -
gsettings                gimp:gsettings        :gsettings                      -
home                     gimp:home             :home                           -
network                  gimp:network          :network                        -
opengl                   gimp:opengl           :opengl                         -
personal-files           gimp:gimp-config      :personal-files                 -
removable-media          gimp:removable-media  -                               -
wayland                  gimp:wayland          :wayland                        -
x11                      gimp:x11              :x11                            -

But there is no gimp-plugins-gmic in GIMP's Filters menu as expected

enter image description here

How to install gimp-plugins-gmic from snap and use it in gimp?

Surface pro 4 kernel not in Advanced options https://askubuntu.com/questions/1568642/surface-pro-4-kernel-not-in-advanced-options

Ubuntu 26.04 LTS MS Surface Pro 4 laptop

I have followed the install process for the kernel at least 3 times not it does not appear in the Advanced Options.

I am just about to give up. Does anyone have a solution?

Installation process:

Debian / Ubuntu

First you need to import the keys we use to sign packages.

wget -qO - https://raw.githubusercontent.com/linux-surface/linux-surface/master/pkg/keys/surface.asc
| gpg --dearmor | sudo dd of=/etc/apt/trusted.gpg.d/linux-surface.gpg

After this you can add the repository configuration and update APT.

echo "deb [arch=amd64] https://pkg.surfacelinux.com/debian release main"
| sudo tee /etc/apt/sources.list.d/linux-surface.list

sudo apt update

If you encounter any issues reading "Error 401 Unauthorized" during the update or the installation below, please have a look at this.

Now you can install the linux-surface kernel and its dependencies.

sudo apt install linux-image-surface linux-headers-surface libwacom-surface iptsd

Ubuntu 26.04: Due to a bug, don't install libwacom-surface.

Important: Support for iptsd only goes back to the latest LTS release at the time of writing (Debian 11 and Ubuntu 22.04). If you are using an older release, and the above command fails, then please remove iptsd from it. You will still be able to use basic singletouch through the kernel driver, but multitouch and the stylus will not work.

After that you can install our secureboot key. This will import the key that the linux-surface kernel is signed with into your bootloader, so that the kernel is bootable without disabling secureboot.

sudo apt install linux-surface-secureboot-mok

This package will print instructions to the terminal. In case you missed those, it will ask you to reboot. Then, upon reboot, a blue menu (MokManager) should pop up, asking you whether you want to enroll the key. You need to interact with the menu and select "Enroll" to proceed. Confirm with ok/yes and when asked for a password enter surface. Note that MokManager expects a QWERTY keyboard layout, you may need to adjust your input accordingly. In case you missed the menu or accidentally chose the wrong options, you can uninstall (fully) and then reinstall the package and reboot to trigger the menu again.

Note that this will only work if your Debian derivative supports secure boot out-of-the-box. If if not, please consult the wiki of your distribution and set up secure boot for distro/stock kernels first. You also want to skip installing the package for now and only install it after you have set this up.

The linux-surface kernel will be installed alongside the default kernel provided by the distribution. This way you have a backup kernel you can use if something goes wrong. The bootloader will pick up the kernel by default, but you should update its configuration to make sure it was recognized.

sudo update-grub

Finally, reboot your system and you should boot into the linux-surface kernel. Please make sure you are actually using the right kernel by checking if the output of uname -a contains the string surface. If it doesn't contain that string, you are still using the default kernel and need to configure your bootloader.

The kernel does not appear in the advanced options in the grub menu.

Ubuntu screen stays black after waking from sleep (Dell Latitude E7450, Wayland) https://askubuntu.com/questions/1568552/ubuntu-screen-stays-black-after-waking-from-sleep-dell-latitude-e7450-wayland

im having a really annoying problem on my dell latitude e7450 (intel graphics) where Ubuntu won't turn the screen back on after sleep. the laptop wakes up, but the screen just stays totally black.

I'm on the latest version of Ubuntu and I'm using Wayland. (just to be clear, I want to stick with Wayland and I haven't tried xorg at all for this).

Here's a list of what I've tried so far using Kate to edit the config files:

I tried fixing the Intel power-saving stuff:

I added i915.enable_dc=0 and i915.enable_psr=0 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.

Forced deep sleep:

I also added mem_sleep_default=deep to the grub cmdline to make sure it's actually going into a real sleep state.

Enabled early KMS for the graphics driver:

I added i915 to the bottom of my /etc/initramfs-tools/modules file so the driver loads early.

After doing all that, i ran sudo update-grub and sudo update-initramfs -u and rebooted.

Even after updating Ubuntu to the latest version and applying all these fixes, it still doesn't fix the screen wake up problem. Does anyone know what else I can try to fix this black screen issue on Wayland?

System Details Report

Date generated: 2026-07-22 20:42:03

Hardware Information:

  • Hardware Model: Dell Inc. Latitude E7450

  • Memory: 16.0 GiB

  • Processor: Intel Core i7-5600U × 4

  • Graphics: Intel HD Graphics 5500 (BDW GT2)

  • Disk Capacity: 512.1 GB

Software Information:

  • Firmware Version: A24

  • OS: Ubuntu 26.04

  • OS Build: (null)

  • OS Type: 64-bit

  • GNOME Version: 50

  • Windowing System: Wayland

  • Kernel Version: Linux 7.0.0-28-generic

Note: This is definitely an Ubuntu specific software issue. The laptop wakes from sleep perfectly fine on other operating systems like MX Linux,Fedora, EndeavourOS so the hardware and screen are fully functional.

Ubuntu does not return to GUI mode after updating to 24.04 from 22.04 https://askubuntu.com/questions/1568528/ubuntu-does-not-return-to-gui-mode-after-updating-to-24-04-from-22-04

Upgrade from dialog box: error message: some third-party entries in your ‘sources.list’ were disabled. You can re-enable after upgrading with ‘software-properties’ tool or your package manager.

Continue Y

Also during upgrade I was asked to Run ‘fwupdmgr get upgrades

The upgrade proceeded and left the laptop in the Terminal, so I ran: sudo apt-get clean && sudo apt-get autoremove && sudo apt reboot which resulted in an attempt to reboot to the GUI, but it failed and returned to Terminal mode:

Ubuntu 24.04 LTS cyborg-16290p-K-AA75A1 tty1
cyborg-16290P-K-AA75A1 login:
I need help with support for TP-Link UB600 Bluetooth Dongle on Kubuntu 26.04 please https://askubuntu.com/questions/1568248/i-need-help-with-support-for-tp-link-ub600-bluetooth-dongle-on-kubuntu-26-04-ple

I've been trying to get my UB600 Bluetooth dongle to work, however it seems that it's not compatible out of the box. In fact, there's only 1 place with a solution how to get it to work however it seems the explanation on how to do it goes over my head. I've tried using what they gave me in konsole but some things just error and I can't seem to get around that. The fix I've been attempting is this. The issue I'm having is, it detects the Bluetooth dongle, but the computer is then unable to detect any Bluetooth devices at all. The lsusb is exactly as shown on that link as is the journalctl.

Results of lsusb | grep -i 'tp-link':

Bus 001 Device 012: ID 37ad:0600  TP-Link Bluetooth USB Adapter

Results of journalctl:

usb 1-1: new full-speed USB device number 12 using xhci_hcd
usb 1-1: New USB device found, idVendor=37ad, idProduct=0600, bcdDevice= 2.00
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: TP-Link Bluetooth USB Adapter
usb 1-1: Manufacturer:
usb 1-1: SerialNumber: 18694530DB8B
Bluetooth: MGMT ver 1.23

I ran sudo dmesg | grep -i bluetooth and got this:

server@server-z87hd3:~$ sudo dmesg | grep -i bluetooth
[sudo] password for server: 
[647887.635955] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[647887.709668] Bluetooth: MGMT ver 1.23
[648046.220743] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[648046.221733] Bluetooth: hci0: RTL: rom_version status=0 version=1
[648046.222744] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[648046.222748] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[648046.224331] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[648046.224378] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[648046.376751] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[648046.443866] Bluetooth: MGMT ver 1.23
[648062.029928] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[648062.105001] Bluetooth: MGMT ver 1.23
[648220.950989] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[648220.951983] Bluetooth: hci0: RTL: rom_version status=0 version=1
[648220.952966] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[648220.952969] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[648220.953197] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[648220.953223] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[648221.105982] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[648221.173128] Bluetooth: MGMT ver 1.23
[648256.225222] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[648256.298247] Bluetooth: MGMT ver 1.23
[649742.374342] Bluetooth: MGMT ver 1.23
[682771.713073] usb 1-1: Product: TP-Link Bluetooth USB Adapter
[682771.785356] Bluetooth: MGMT ver 1.23

Is there any chance somebody could explain to me like I'm a 5 year old how to apply that patch, or better yet, create a solution for me? I am running Kubuntu 26.04 on kernel 7.0.0-27-27.

Edit: Following "david" in the comments advice results.

server@server-z87hd3:~$ sudo apt install bluetooth bluez -y
[sudo: authenticate] Password:       
bluez is already the newest version (5.85-4ubuntu0.1).
bluez set to manually installed.
Installing:                 
  bluetooth

Suggested packages:
  bluez-meshd

Summary:
  Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 3
  Download size: 6,600 B
  Space needed: 36.9 kB / 180 GB available

Get:1 http://archive.ubuntu.com/ubuntu resolute-updates/universe amd64 bluetooth all 5.85-4ubuntu0.1 [6,600 B]
Fetched 6,600 B in 0s (121 kB/s)      
Selecting previously unselected package bluetooth.
(Reading database… 268329 files and directories currently installed.)
Preparing to unpack …/bluetooth_5.85-4ubuntu0.1_all.deb…
Unpacking bluetooth (5.85-4ubuntu0.1)…
Setting up bluetooth (5.85-4ubuntu0.1)…
server@server-z87hd3:~$ sudo systemctl start bluetooth
server@server-z87hd3:~$ sudo systemctl enable bluetooth
Synchronizing state of bluetooth.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable bluetooth
server@server-z87hd3:~$ bluetoothctl show | grep "Powered"
        Powered: yes
server@server-z87hd3:~$ bluetoothctl
[NEW] Media /org/bluez/hci1 
        SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
        SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Controller 18:69:45:30:DB:8B Discovering: yes
[bluetoothctl]> power on#
Invalid argument on#
[bluetoothctl]> power on
Changing power on succeeded
[bluetoothctl]> agent on
Agent is already registered
[bluetoothctl]> default-agent
Default agent request successful
[bluetoothctl]> discoverable on
hci1 new_settings: powered connectable bondable ssp br/edr le secure-conn ll-privacy 
[CHG] Controller 18:69:45:30:DB:8B Connectable: yes
hci1 new_settings: powered connectable discoverable bondable ssp br/edr le secure-conn ll-privacy 
Changing discoverable on succeeded
[CHG] Controller 18:69:45:30:DB:8B Discoverable: yes
[bluetoothctl]> pairable on
Changing pairable on succeeded
[bluetoothctl]> scan on
SetDiscoveryFilter success
Discovery started
[bluetoothctl]> 

I have disabled Secure Boot and run Bluetoothctl show:

server@server-z87hd3:~$ bluetoothctl show
Controller 18:69:45:30:DB:8B (public)
        Manufacturer: 0x005d (93)
        Version: 0x0a (10)
        Name: server-z87hd3 #2
        Alias: server-z87hd3 #2
        Class: 0x006c0104 (7078148)
        Powered: yes
        PowerState: on
        Discoverable: yes
        DiscoverableTimeout: 0x000000b4 (180)
        Pairable: yes
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Phonebook Access Client   (0000112e-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (185f3df4-3268-4e3f-9fca-d4d5059915bd)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (03b80e5a-ede8-4b33-a751-6ce34ec4c700)
        UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0555
        Discovering: yes
        Roles: central
        Roles: peripheral
Advertising Features:
        ActiveInstances: 0x00 (0)
        SupportedInstances: 0x04 (4)
        SupportedIncludes: tx-power
        SupportedIncludes: appearance
        SupportedIncludes: local-name
        SupportedSecondaryChannels: 1M
        SupportedSecondaryChannels: 2M
        SupportedSecondaryChannels: Coded
        SupportedCapabilities.MinTxPower: 0xffffffa6 (-90)
        SupportedCapabilities.MaxTxPower: 0x0000 (0)
        SupportedCapabilities.MaxAdvLen: 0xfb (251)
        SupportedCapabilities.MaxScnRspLen: 0xfb (251)
        SupportedFeatures: CanSetTxPower
        SupportedFeatures: HardwareOffload
server@server-z87hd3:~$ 

This is what my results are like with my 5.0 dongle for comparison:

server@server-z87hd3:~$ bluetoothctl show
Controller 04:42:1A:54:A8:55 (public)
        Manufacturer: 0x005d (93)
        Version: 0x0a (10)
        Name: server-z87hd3 #2
        Alias: Asus 5.0
        Class: 0x006c0104 (7078148)
        Powered: yes
        PowerState: on
        Discoverable: no
        DiscoverableTimeout: 0x000000b4 (180)
        Pairable: yes
        UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
        UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
        UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (185f3df4-3268-4e3f-9fca-d4d5059915bd)
        UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
        UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Phonebook Access Client   (0000112e-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Vendor specific           (03b80e5a-ede8-4b33-a751-6ce34ec4c700)
        UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v1D6Bp0246d0555
        Discovering: no
        Roles: central
        Roles: peripheral
Advertising Features:
        ActiveInstances: 0x00 (0)
        SupportedInstances: 0x04 (4)
        SupportedIncludes: tx-power
        SupportedIncludes: appearance
        SupportedIncludes: local-name
        SupportedSecondaryChannels: 1M
        SupportedSecondaryChannels: 2M
        SupportedSecondaryChannels: Coded
        SupportedCapabilities.MinTxPower: 0xffffffed (-19)
        SupportedCapabilities.MaxTxPower: 0x0017 (23)
        SupportedCapabilities.MaxAdvLen: 0xfb (251)
        SupportedCapabilities.MaxScnRspLen: 0xfb (251)
        SupportedFeatures: CanSetTxPower
        SupportedFeatures: HardwareOffload
server@server-z87hd3:~$ bluetoothctl
[NEW] Media /org/bluez/hci1 
        SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
        SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[NEW] Media /org/bluez/hci0 
        SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
        SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Controller 04:42:1A:54:A8:55 Discovering: yes
[G522 Gaming Headset]> scan on
SetDiscoveryFilter success
Discovery started
[NEW] Device DE:B6:45:46:3D:0B Govee_H6076_3D0B
[NEW] Device FF:02:3C:C8:FA:46 BLE MF8470
[CHG] Device 40:58:99:CF:16:D0 RSSI: 0xffffffbd (-67)
[NEW] Device D0:C8:03:C6:6F:76 Govee_H61D5_6F76
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[NEW] Device 33:36:9F:00:1E:8B 33-36-9F-00-1E-8B
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffad (-83)
[CHG] Device FF:02:3C:C8:FA:46 UUIDs: 19fe1b3d-4c5b-36b8-4043-c09ddc76099e
[NEW] Device DE:CD:2F:A8:FA:1A ET-2850 Series
[NEW] Device DC:6E:02:C6:22:87 Govee_H7078_2287
[NEW] Device DE:B6:41:06:19:77 Govee_H6022_1977
[NEW] Device C8:FF:77:CB:9B:32 VW1-UK-MAA1830A
[NEW] Device 13:12:70:E3:1C:0B 13-12-70-E3-1C-0B
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffab (-85)
[NEW] Device DC:B4:D9:F4:2A:42 DC-B4-D9-F4-2A-42
[NEW] Device D6:50:84:C6:55:17 Govee_H6099_5517
[NEW] Device 00:00:00:00:00:00 00-00-00-00-00-00
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffad (-83)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb9 (-71)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbb (-69)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb3 (-77)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb1 (-79)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 40:58:99:CF:16:D0 RSSI: 0xffffffbf (-65)
[CHG] Device 13:12:70:E3:1C:0B RSSI: 0xffffffbd (-67)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffbf (-65)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa5 (-91)
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffb9 (-71)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 33:36:9F:00:1E:8B RSSI: 0xffffffb9 (-71)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffad (-83)
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffb5 (-75)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbf (-65)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffffa1 (-95)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb9 (-71)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffb9 (-71)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffffa1 (-95)
[CHG] Device D6:50:84:C6:55:17 AdvertisingFlags:
  00                                               .               
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffad (-83)
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffb9 (-71)
[CHG] Device 13:12:70:E3:1C:0B RSSI: 0xffffffbd (-67)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device D6:50:84:C6:55:17 AdvertisingFlags:
  06                                               .               
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffb9 (-71)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffaf (-81)
[CHG] Device 40:58:99:CF:16:D0 RSSI: 0xffffffbf (-65)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa7 (-89)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffaf (-81)
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffad (-83)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa9 (-87)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device 33:36:9F:00:1E:8B RSSI: 0xffffffb9 (-71)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa9 (-87)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa9 (-87)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffc9 (-55)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbb (-69)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffffa1 (-95)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffad (-83)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbd (-67)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbf (-65)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffb5 (-75)
[CHG] Device D0:C8:03:C6:6F:76 RSSI: 0xffffffcd (-51)
[CHG] Device 40:58:99:CF:16:D0 RSSI: 0xffffffbd (-67)
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffab (-85)
[CHG] Device 33:36:9F:00:1E:8B RSSI: 0xffffffb9 (-71)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa5 (-91)
[CHG] Device DE:B6:45:46:3D:0B RSSI: 0xffffffaf (-81)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffbf (-65)
[CHG] Device DC:6E:02:C6:22:87 RSSI: 0xffffffb5 (-75)
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffb1 (-79)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffff9f (-97)
[CHG] Device 13:12:70:E3:1C:0B RSSI: 0xffffffbd (-67)
[CHG] Device DC:B4:D9:F4:2A:42 RSSI: 0xffffffb1 (-79)
[CHG] Device D6:50:84:C6:55:17 RSSI: 0xffffffa1 (-95)
[CHG] Device FF:02:3C:C8:FA:46 RSSI: 0xffffffb1 (-79)
[CHG] Device 00:00:00:00:00:00 RSSI: 0xffffffbb (-69)
[CHG] Device DE:CD:2F:A8:FA:1A RSSI: 0xffffffa5 (-91)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffc7 (-57)
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffb9 (-71)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffbf (-65)
[DEL] Device 13:12:70:E3:1C:0B 13-12-70-E3-1C-0B
[CHG] Device DE:B6:41:06:19:77 RSSI: 0xffffffad (-83)
[CHG] Device C8:FF:77:CB:9B:32 RSSI: 0xffffffc7 (-57)

iw reg get with both dongles in:

server@server-z87hd3:~$ iw reg get
global
country 00: DFS-UNSET
        (2402 - 2472 @ 40), (6, 20), (N/A)
        (2457 - 2482 @ 20), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
        (2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
        (5170 - 5250 @ 80), (6, 20), (N/A), AUTO-BW, PASSIVE-SCAN
        (5250 - 5330 @ 80), (6, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
        (5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN
        (5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN
        (57240 - 63720 @ 2160), (N/A, 0), (N/A)

server@server-z87hd3:~$ 

iw reg get with only 6.0


server@server-z87hd3:~$ iw reg get
global
country 00: DFS-UNSET
        (755 - 928 @ 2), (N/A, 20), (N/A), PASSIVE-SCAN
        (2402 - 2472 @ 40), (N/A, 20), (N/A)
        (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
        (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
        (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
        (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
        (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
        (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
        (57240 - 63720 @ 2160), (N/A, 0), (N/A)

server@server-z87hd3:~$ 

iw reg get with neither:

server@server-z87hd3:~$ iw reg get
global
country 00: DFS-UNSET
        (755 - 928 @ 2), (N/A, 20), (N/A), PASSIVE-SCAN
        (2402 - 2472 @ 40), (N/A, 20), (N/A)
        (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
        (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
        (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
        (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
        (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
        (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
        (57240 - 63720 @ 2160), (N/A, 0), (N/A)

server@server-z87hd3:~$ 

I followed the steps on myshell to create a patch and I get this error, any idea how to rectify this error?

server@server-z87hd3:~/btusb-patched$ make
make -C /lib/modules/7.0.0-28-generic/build M=/home/server/btusb-patched modules
make[1]: Entering directory '/usr/src/linux-headers-7.0.0-28-generic'
make[2]: Entering directory '/home/server/btusb-patched'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: x86_64-linux-gnu-gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0
  You are using:           gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0
  MODPOST Module.symvers
ERROR: modpost: "btmtk_recv_event" [btusb.ko] undefined!
make[4]: *** [/usr/src/linux-headers-7.0.0-28-generic/scripts/Makefile.modpost:147: Module.symvers] Error 1
make[3]: *** [/usr/src/linux-headers-7.0.0-28-generic/Makefile:2065: modpost] Error 2
make[2]: *** [/usr/src/linux-headers-7.0.0-28-generic/Makefile:248: __sub-make] Error 2
make[2]: Leaving directory '/home/server/btusb-patched'
make[1]: *** [Makefile:248: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-7.0.0-28-generic'
make: *** [Makefile:5: all] Error 2

This is the attempt after following your steps exactly.

server@server-z87hd3:~/btusb-patched$ make
make -C /lib/modules/7.0.0-28-generic/build/ M=/home/server/btusb-patched modules
make[1]: Entering directory '/usr/src/linux-headers-7.0.0-28-generic'
make[2]: Entering directory '/home/server/btusb-patched'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: x86_64-linux-gnu-gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0
  You are using:           gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0
  CC [M]  btusb.o
In file included from <command-line>:
/usr/src/linux-headers-7.0.0-28-generic/include/linux/kconfig.h:5:10: fatal error: generated/autoconf.h: No such file or directory
    5 | #include <generated/autoconf.h>
      |          ^~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[4]: *** [/usr/src/linux-headers-7.0.0-28-generic/scripts/Makefile.build:289: btusb.o] Error 1
make[3]: *** [/usr/src/linux-headers-7.0.0-28-generic/Makefile:2115: .] Error 2
make[2]: *** [/usr/src/linux-headers-7.0.0-28-generic/Makefile:248: __sub-make] Error 2
make[2]: Leaving directory '/home/server/btusb-patched'
make[1]: *** [Makefile:248: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-7.0.0-28-generic'
make: *** [Makefile:4: all] Error 2

Make file looks like this:

obj-m := btusb.o btmtk.o
KDIR  := /lib/modules/7.0.0-28-generic/build/
all:
    $(MAKE) -C $(KDIR) M=$(PWD) modules
clean:
    $(MAKE) -C $(KDIR) M=$(PWD) clean

Yes, I used tab, not spaces. Edit: I should specify this dongle is a Bluetooth 6.0 dongle.

How to change GNOME Clock alarm sound (file)? https://askubuntu.com/questions/1536620/how-to-change-gnome-clock-alarm-sound-file

Till Ubuntu 22.04 I could just replace the /usr/share/sounds/freedesktop/stereo/alarm-clock-elapsed.ogg with a new sound file (with the same name) and it worked.
But in Ubuntu 24.04 it does not work. The same beeping sound reappears although I even deleted the file (/usr/share/sounds/freedesktop/stereo/alarm-clock-elapsed.oga – oga instead of ogg in the past).

Is there a new place and folder?

I searched the internet and dconf-editor but could not find any hint for a new location or solution.

Failure to mount external harddisk in Ubuntu 22.04 https://askubuntu.com/questions/1509682/failure-to-mount-external-harddisk-in-ubuntu-22-04

Recently I have switched from Ubuntu 18.04 to Ubuntu 22.04. One of my external hard disks, a Western Digital Elements 3 TB hard disk, which has always mounted properly in 18.04, did mount and worked properly for a few days in 22.04. Then it stopped working because it became impossible to mount it. When using it with another computer under Windows 11, it mounts and works properly. The error message in Ubuntu 22.04:

Unable to access "Elements". 
Error mounting /dev/sdi1 at /media/lubomir/Elements1: Unknown error when mounting /dev/sdi1

Please help me to resolve this.

Enchanced Session in Hyper-V greyed out after restart https://askubuntu.com/questions/1411739/enchanced-session-in-hyper-v-greyed-out-after-restart

I'm using Ubuntu 20.04 on Hyper-v 21H2 Windows Version I've followed instructions from below link : http://c-nergy.be/blog/?p=14888 and xrdp session has started (but I was only black screen) so I had to restart VM and now, Enchanced Session button is greyed out and I'm not asked to log into xrdp anymore.

I've checked xrdp and xrdp daemon is actve and running. I've also run Set-VM -VMName "Ubuntu 20.04" -EnhancedSessionTransportType HvSocket again but it did not helped.

How to Install dnsmasq on Ubuntu? [duplicate] https://askubuntu.com/questions/1383886/how-to-install-dnsmasq-on-ubuntu

I tried on ubuntu 16.04 and 20.04, however I cannot install dnsmasq.

The error I get is:

Package dnsmasq is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  dnsmasq-base

E: Package 'dnsmasq' has no installation candidate

Is this no longer a package available on ubuntu repos?

How to install and configure mDNS on Ubuntu 18.04? https://askubuntu.com/questions/1335936/how-to-install-and-configure-mdns-on-ubuntu-18-04

According to the link. https://www.howtoinstall.me/ubuntu/18-04/avahi-daemon/

The method it provides for installing mDNS consists of just two lines of command:

sudo apt update
sudo apt install avahi-daemon

According to the link: What is mDNS? Is it possible to make mDNS query without mdns service running?

One friend replied:

Ubuntu systems just need avahi-daemon and libnss-mdns installed.

So the first question is :

What is the standard method for installing mDNS on ubuntu 18.04?

The second question is:

After installing mDNS, how should I configure mDNS?

The third question is:

How can I verify the functionality of mDNS?

How can I keep Ubuntu updated automatically? https://askubuntu.com/questions/1260567/how-can-i-keep-ubuntu-updated-automatically

I want help to

  • make Ubuntu 'update && upgrade' itself automatically,
  • select the settings for this automatic system.

How can I do it? Please advice about

  • where to find the menu (GUI) or file (command line) to do it,
  • what settings that can be recommended (if different from the default).

As a bonus, please describe how different types of program packages are treated,

  • program packages from Ubuntu repositories and PPAs
  • snap packages
  • flatpak packages
  • other kinds of programs/packages.
ALSA samples capture: cannot open device https://askubuntu.com/questions/201506/alsa-samples-capture-cannot-open-device

I'm quite new to Linux (Lubuntu 12.04 for sake of precision) and ALSA programming at all. I'm trying to write a C program to capture audio from internal PC microphone for processing it. So as first step I google a bit and I found this article for capturing audio samples

A tutorial on using the ALSA Audio API

but when I compile it and execute it with:

./mycapture "default" or ./mycapture "hw:0,0" and all the possible variants on theme it always raises the error:

cannot open device hw:0,0 (no such file or directory).

So the issue is: what is the name of the mic audio device to pass as parameter to record the audio from mic ?

The mic is working ok because the Sound Recorder program records sounds perfectly and I can playback them.

The output of the aplay -l is the following :

**** List of PLAYBACK Hardware Devices ****
card 0: I82801DBICH4 [Intel 82801DB-ICH4], device 0: Intel ICH [Intel 82801DB-ICH4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: I82801DBICH4 [Intel 82801DB-ICH4], device 4: Intel ICH - IEC958 [Intel 82801DB-ICH4 - IEC958]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

and this is the amixer output (cut)

Simple mixer control 'Master',0
  Capabilities: pvolume pswitch penum
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 31 [100%] [0.00dB] [on]
  Front Right: Playback 31 [100%] [0.00dB] [on]
Simple mixer control 'Master Mono',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
  Playback channels: Mono
  Limits: Playback 0 - 31
  Mono: Playback 4 [13%] [-40.50dB] [on]
Simple mixer control 'PCM',0
  Capabilities: pvolume pswitch penum
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 31 [100%] [12.00dB] [on]
  Front Right: Playback 31 [100%] [12.00dB] [on]
Simple mixer control 'CD',0
  Capabilities: pvolume pswitch cswitch cswitch-exclusive penum
  Capture exclusive group: 0
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Front Left: Playback 0 [0%] [-34.50dB] [off] Capture [off]
  Front Right: Playback 0 [0%] [-34.50dB] [off] Capture [off]
Simple mixer control 'Mic',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined cswitch cswitch-exclusive penum
  Capture exclusive group: 0
  Playback channels: Mono
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono: Playback 22 [71%] [-1.50dB] [on]
  Front Left: Capture [on]
  Front Right: Capture [on]
Simple mixer control 'Mic Boost (+20dB)',0
  Capabilities: pswitch pswitch-joined penum
  Playback channels: Mono
  Mono: Playback [off]
Simple mixer control 'Mic Select',0
  Capabilities: enum
  Items: 'Mic1' 'Mic2'
  Item0: 'Mic1'
Simple mixer control 'Stereo Mic',0
  Capabilities: pswitch pswitch-joined penum
  Playback channels: Mono
  Mono: Playback [off]

so for aplay it seems I have no recording device, but for amixer I've got the mic, a mic boost and mic stereo as well with all those gorgeous stuffs on their place !!. If so, how could my Sound Recorder record the audio without any problem at all ?!?!

For sure I'm giving the wrong device name to the command line for capturing audio but I'm loosing the hope for finding the correct one !

Please help....before I tear my hair out !!!