I'm trying to install Ubuntu desktop 26.04 on a chassis that was manufactured as a backup appliance. The installer keeps failing with no specific error message, I only get the curtin logs and that's it. (The UI shows me a log file and then I figured out how to get the same log file through terminal so I could start saving and comparing logs.)

The OS drive is a refurbished solid state drive that I just got, because the old OS drive in the device was bad.

I figured out some things that I think are helping it get a bit further than it used to:

• Updated the BIOS time to match the local time zone which is also the time zone I'm selecting in the installer. (When I googled one of the early errors I did not save it said maybe the BIOS clock is wrong. But maybe I ought to set it back to UTC?)
• It was getting tripped up trying to read all the drives sometimes, so
• I pulled out the drawers for all the data drives leaving only the OS drive
• Ethernet connection directly to the router
• Sometimes telling the installer to run in offline mode in case the internet connection isn't fully working

I haven't been trying to boot Ubuntu after most of these installs. The one time that I did, it was when it thought it had an internet connection but couldn't actually use it due to having no DNS, and it was missing a bunch of basic utilities. I gave up and tried to reinstall when I hit something I needed (forget which command unfortunately) that normally comes with Ubuntu but was absent, and is installed with a deb file instead of apt, but I couldn't find the deb file online anywhere because it's supposed to come with the OS.

Here are the most recent two logs. One was taken with an additional USB drive plugged in that I use to store the log files, the other one I waited til after it had run before plugging in the log storage USB.

Here's the last little bit of the log that seemed to get the farthest:

Applying debconf selections
Checking if target_proc (/target/proc) is a mount
It's not, using normal behavior
Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'debconf-set-selections'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It's not, using normal behavior
Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'dpkg-query', '--list'] with allowed return codes [0] (capture=True)
Running command ['mount', '--bind', '/dev', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/proc', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/run', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/target/usr/bin/true', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
TIMED subp(['udevadm', 'settle']): 0.006
Running command ['mount', '--make-private', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/dev', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/proc', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/run', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/target/usr/bin/true', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
TIMED subp(['udevadm', 'settle']): 0.009
Running command ['mount', '--make-private', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False)
UEFI remove old olders efi state:
EFIBootState(current='0009', timeout='1 seconds', order=['000A', '0009', '0005'], entries={'0005': EFIBootEntry(name='Hard Drive', path='BBS(HD,,0x0)414d474f414d4e4fa5000000010000006f0057004400430020005700440042004e0043004500320035003000300050004e00430000000501090002000000007fff040002010c00d041030a0000000001010600021f03120a000400ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63800310032003400370032003200340030003100350037002000200020002000200020002000200000007fff0400414d424f414d4e4f9b000000010000006300200055005300420020004400490053004b00200032002e003000200050004d004100500000000501090002000000007fff040002010c00d041030a000000000101060000140305060001007fff040001043600ef47642dc93ba041ac194d51d01b4ce6300037003000310039003700360032004600380042003200440045003000380000007fff0400414d424f'), '0009': EFIBootEntry(name='UEFI:  USB DISK 2.0 PMAP', path='PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(2,GPT,2fdf80be-e145-40c5-aa51-61a53ab5282e,0xc21d04,0x2838)AMBO'), '000A': EFIBootEntry(name='UEFI: WDC WDBNCE2500PNC', path='PciRoot(0x0)/Pci(0x1f,0x2)/Sata(4,65535,0)/HD(1,GPT,502aff24-45b2-456a-a358-7eafc504c6f4,0x800,0x219800)AMBO')})
installing grub to target=/target devices=['/dev/sda1'] [replace_defaults=True]
Checking if target_proc (/target/proc) is a mount
It's not, using normal behavior
Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/target', 'dpkg', '--print-architecture'] with allowed return codes [0] (capture=True)
updated /target/etc/default/grub to set: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Using grub install command: /usr/lib/grub/grub-multi-install
Grub install cmds:
[['efibootmgr', '-v'], ['dpkg-reconfigure', 'grub-efi-amd64'], ['update-grub'], ['/usr/lib/grub/grub-multi-install'], ['efibootmgr', '-v']]
Running command ['mount', '--bind', '/dev', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/proc', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/run', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/target/usr/bin/true', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'dpkg-reconfigure', 'grub-efi-amd64'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'update-grub'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', '/usr/lib/grub/grub-multi-install'] with allowed return codes [0] (capture=True)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
TIMED subp(['udevadm', 'settle']): 0.004
Running command ['mount', '--make-private', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False)
Skipped reordering of UEFI boot methods.
Currently booted UEFI loader might no longer boot.
Running command ['mount', '--bind', '/dev', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/proc', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/run', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/sys/firmware/efi/efivars', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--bind', '/target/usr/bin/true', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Checking if target_proc (/target/proc) is a mount
It is, so unshare will use --mount-proc=/target/proc
Running command ['unshare', '--fork', '--pid', '--mount-proc=/target/proc', '--', 'chroot', '/target', 'efibootmgr', '-v'] with allowed return codes [0] (capture=True)
Running command ['udevadm', 'settle'] with allowed return codes [0] (capture=False)
TIMED subp(['udevadm', 'settle']): 0.008
Running command ['mount', '--make-private', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/usr/bin/ischroot'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys/firmware/efi/efivars'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/sys'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/run'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/proc'] with allowed return codes [0] (capture=False)
Running command ['mount', '--make-private', '/target/dev'] with allowed return codes [0] (capture=False)
Running command ['umount', '/target/dev'] with allowed return codes [0] (capture=False)
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/install-grub: SUCCESS: installing grub to target devices
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/configuring-bootloader: SUCCESS: configuring target system bootloader
start: cmd-install/stage-curthooks/builtin/cmd-curthooks/copy-cdrom-metadata: copying metadata from /cdrom
copying media-info into target
/cdrom/.disk/ubuntu_dist_channel not found, skipping
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/copy-cdrom-metadata: SUCCESS: copying metadata from /cdrom
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: SUCCESS: curtin command curthooks
{'current': '0009', 'timeout': '1 seconds', 'order': '000A,0009,0005'}
{'current': '0009', 'timeout': '1 seconds', 'order': '000A,0009,0005'}
{'current': '0009', 'timeout': '1 seconds', 'order': '0000,000A,0009,0005'}
curtin: Installation finished.

If anyone can help, I would really really appreciate it. I've been struggling with this device for multiple days at this point. I've installed earlier versions of ubuntu desktop on laptops without issue several times before (currently posting this from 24.04) but this particular hardware just hates me or something.

I use the terminal quite frequently and last night I notice something strange. I could switch to my other tabs in the gnome-terminal with Alt+number as always, except if the key was Alt+2. I kept trying the keyboard shortcut with the left Alt key but it would not work and I later found out that the right alt key allows the shortcut to work. But that is an incovenience since my muscle memory favors left Alt for switching.

I tried using gsettings reset and I restarted the computer but gave up after the situation persisted. However, I was typing out something and tried to write 'Geoffrey west' with a capital 'w' and noticed that a capital 'w' was not being typed. That is weird since I can clearly type a capital 'G'.

I have read these stackoverflow answers

1. 'https://superuser.com/a/821256'
2. 'https://askubuntu.com/questions/1410523/why-some-keys-doesnt-work-on-my-ubuntu-laptop'

1 suggests using sudo dpkg-reconfigure keyboard-configuration but the answer did not tell how to know the correct keyboard for a hp-15-dyxxx laptop keyboard. The default keyboard there as was revealed with

debconf-show keyboard-configuration

is Generic 105-key PC. Below is the full output

debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied
  keyboard-configuration/compose: No compose key
  keyboard-configuration/modelcode: pc105
  keyboard-configuration/xkb-keymap:
  keyboard-configuration/unsupported_options: true
  keyboard-configuration/toggle: No toggling
  keyboard-configuration/altgr: The default for the keyboard layout
  keyboard-configuration/switch: No temporary switch
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/variantcode:
  keyboard-configuration/unsupported_config_layout: true
  keyboard-configuration/unsupported_config_options: true
  debian-installer/console-setup-udeb/title:
  console-setup/detected:
* keyboard-configuration/variant: English (US)
  console-setup/ask_detect: false
  console-setup/detect:
  keyboard-configuration/store_defaults_in_debconf_db: true
  keyboard-configuration/optionscode:
* keyboard-configuration/layout: English (US)
  keyboard-configuration/unsupported_layout: true
  keyboard-configuration/other:
  keyboard-configuration/model: Generic 105-key PC
  keyboard-configuration/layoutcode: us

I also want to note that while the left shift is not working with 'w', with the right shift, I can produce 'W'. Again that is not convenient. I notice similarly with xev that while 'w' and right shift keys will trigger an event separately, 'w' will not trigger any event when right shift is pressed down. What can I do to get my keyboard working properly again?

Initially I succeeded in installing Ubuntu 24.04 in parallel to Windows 10, but even after repairing the boot partition with Boot-Repair (https://paste.debian.net/hidden/bc192e4d) I don't get the system working, because it fails to find the boot partition.

============================= Boot Repair Summary ==============================

modprobe: FATAL: Module efivars not found in directory /lib/modules/6.14.0-27-generic
cat: /mnt/boot-sav/sda4/etc/apt/sources.list: No such file or directory
cat: /mnt/boot-sav/sda4/etc/apt/sources.list: No such file or directory
cat: /mnt/boot-sav/sda4/etc/apt/sources.list: No such file or directory
cat: /mnt/boot-sav/sda4/etc/apt/sources.list: No such file or directory

Recommended repair: ____________________________________________________________

The default repair of the Boot-Repair utility will purge (in order to remove grub-efi) and reinstall the grub2 of
sda4 into the MBR of sda.
Grub-efi will not be selected by default because no ESP detected.
Additional repair will be performed: unhide-bootmenu-10s win-legacy-basic-fix


/boot/efi removed in sda4/fstab
Quantity of real Windows: 1
WinSE in sda2
Copied Win boot files from sda1 to sda2
chroot /mnt/boot-sav/sda4 apt-get -y update
Purge the GRUB of /dev/sda4
grub-pc available
Paketlisten werden gelesen…
Abhängigkeitsbaum wird aufgebaut…SET@_progressbar1.pulse()

Statusinformationen werden eingelesen…
0 aktualisiert, 0 neu installiert, 1 erneut installiert, 0 zu entfernen und 441 nicht aktualisiert.
Es müssen 137 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
Holen:1 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 grub-pc amd64 2.12-1ubuntu7.3 [137 kB]
Herunterladen abgeschlossen; Nur-Herunterladen-Modus aktiv
DEBCHECK debOK, grub-pc
DEBCHECK debOK
Please type: sudo chroot "/mnt/boot-sav/sda4" dpkg --configure -ansudo chroot "/mnt/boot-sav/sda4" apt-get install -fynsudo chroot "/mnt/boot-sav/sda4" apt-get purge --allow-remove-essential -y grub-com*nsudo chroot "/mnt/boot-sav/sda4" apt-get purge --allow-remove-essential -y grub2-com*nsudo chroot "/mnt/boot-sav/sda4" apt-get purge --allow-remove-essential -y shim-signednsudo chroot "/mnt/boot-sav/sda4" apt-get purge --allow-remove-essential -y grub-common:*nsudo chroot "/mnt/boot-sav/sda4" apt-get purge --allow-remove-essential -y grub2-common:*n
Then type: sudo chroot "/mnt/boot-sav/sda4" apt-get install -y grub-pc

Unhide GRUB boot menu in sda4/etc/default/grub

====================== Reinstall the grub-pc of /dev/sda4 ======================

chroot /mnt/boot-sav/sda4 grub-install --version
grub-install (GRUB) 2.12-1ubuntu7.3

==> Reinstall the GRUB of /dev/sda4 into the MBR of /dev/sda

chroot /mnt/boot-sav/sda4 grub-install /dev/sda
Installing for i386-pc platform.
Installation finished. No error reported.

chroot /mnt/boot-sav/sda4 update-grub
Sourcing file `/etc/default/grub'
Found linux image: /boot/vmlinuz-6.14.0-27-generic
Found initrd image: /boot/initrd.img-6.14.0-27-generic
Adding boot menu entry for UEFI Firmware Settings ...

Unhide GRUB boot menu in sda4/boot/grub/grub.cfg

Bootsektor wurde erfolgreich repariert.

Sie können Ihren Rechner nun neu starten.
Bitte stellen Sie sicher, dass Ihr BIOS von sda (ATA SAMSUNG MZ7LH480) startet!

Die Startdateien für [sda4 (end>100GB)] liegen weit hinten auf der Festplatte. Ihr BIOS könnte sie nicht erkennen. Bitte legen Sie eine Partition vom Typ /boot an und versuchen es ggf. erneut. (EXT4, >200MB, Anfang des Datenträgers). Das könnte mit Werkzeugen wie gParted geschehen. Danach wählen Sie diese Partition über Option [Separate /boot-Partition:] von [Startreparatur]. (https://help.ubuntu.com/community/BootPartition)Bitte setzen Sie Ihr BIOS in den Legacy-Modus, um Ihr Ubuntu 24.04.3 LTS zu starten, und geben Sie dann den Befehl [sudo update-grub] ein, um den Eintrag Windows in Ihr GRUB-Menü aufzunehmen.


============================ Boot Info After Repair ============================

 => Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 1 of 
    the same hard drive for core.img. core.img is at this location and looks 
    for (,msdos4)/boot/grub. It also embeds following components:
    
    modules
    ---------------------------------------------------------------------------
    fshelp ext2 part_msdos biosdisk
    ---------------------------------------------------------------------------
 => Grub2 (v2.00) is installed in the MBR of /dev/sdb and looks at sector 1 of 
    the same hard drive for core.img. core.img is at this location and looks 
    for (hd0,msdos1)/boot/grub. It also embeds following components:
    
    modules
    ---------------------------------------------------------------------------
    biosdisk fshelp fat exfat ext2 ntfs ntfscomp part_msdos
    ---------------------------------------------------------------------------

sda1: __________________________________________________________________________

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

sda2: __________________________________________________________________________

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

sda3: __________________________________________________________________________

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

sda4: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  Ubuntu 24.04.3 LTS
    Boot files:        /boot/grub/grub.cfg /etc/fstab /etc/default/grub 
                       /boot/grub/i386-pc/core.img

sdb1: __________________________________________________________________________

    File system:       vfat
    Boot sector type:  MSWIN4.1: FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /boot/grub/grub.cfg /efi/boot/bootx64.efi 
                       /efi/boot/grubx64.efi /efi/boot/mmx64.efi

sdb2: __________________________________________________________________________

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


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

OS#1 (linux):   Ubuntu 24.04.3 LTS on sda4
OS#2 (windows):   Windows 8 or 10 on sda2

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

CPU architecture: 64-bit
Video: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller from Intel Corporation
Live-session OS is Ubuntu 64-bit (Ubuntu 24.04.3 LTS, noble, x86_64)

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

BIOS/UEFI firmware: FBKTE0AUS(1.224) from LENOVO
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot enabled according to mokutil - Bitte melden Sie diese Nachricht an boot.repair@gmail.com.
BootCurrent: 000A
Timeout: 1 seconds
BootOrder: 000A,0008,0009,0004,0003,0000
Boot0000* Ubuntu    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0003* Generic Usb Device    VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0004* CD/DVD Device VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0008  UEFI: IP6 Intel(R) Ethernet Connection I217-LM    PciRoot(0x0)/Pci(0x19,0x0)/MAC(d8cb8ababd3c,0)/IPv6([::]:<->[::]:,0,0)0000424f
Boot0009  UEFI: IP4 Intel(R) Ethernet Connection I217-LM    PciRoot(0x0)/Pci(0x19,0x0)/MAC(d8cb8ababd3c,0)/IPv4(0.0.0.00.0.0.0,0,0)0000424f
Boot000A* UEFI: (FAT)SanDisk    PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(1,0)/HD(1,MBR,0xfbc93123,0x80,0x3b9fee0)0000424f

94c7467f956700d44c5b4dcd3967535c   sda1/BOOT/bootx64.efi
39bc76ff6662f4fbe9aa116e4c997b41   sda1/BOOT/fbx64.efi
4ba5a5aad43c197e9fb58b76b404d287   sda1/BOOT/mmx64.efi
94c7467f956700d44c5b4dcd3967535c   sda1/ubuntu/grubx64.efi
4ba5a5aad43c197e9fb58b76b404d287   sda1/ubuntu/mmx64.efi
07e25dcaf57c776875f78fa36827c58e   sda1/ubuntu/shimx64.efi
07e25dcaf57c776875f78fa36827c58e   sda1/BOOT/BOOTX64.efi

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

Disks info: ____________________________________________________________________

sda : notGPT,   no-BIOSboot,    has-noESP,  not-usb,    not-mmc, has-os,    has-win,    2048 sectors * 512 bytes
sdb : notGPT,   no-BIOSboot,    has-noESP,  usb-disk,   not-mmc, no-os, no-wind,    128 sectors * 512 bytes

Partitions info (1/3): _________________________________________________________

sda1    : no-os,    64, nopakmgr,   no-docgrub, nogrub, nogrubinstall,  no-grubenv, noupdategrub,   not-far
sda2    : is-os,    64, nopakmgr,   no-docgrub, nogrub, nogrubinstall,  no-grubenv, noupdategrub,   end-after-100GB
sda3    : no-os,    64, nopakmgr,   no-docgrub, nogrub, nogrubinstall,  no-grubenv, noupdategrub,   end-after-100GB
sda4    : is-os,    64, apt-get,    signed grub-pc grub-efi ,   grub2,  grub-install,   grubenv-ok, update-grub,    end-after-100GB
sdb2    : no-os,    64, nopakmgr,   no-docgrub, nogrub, nogrubinstall,  no-grubenv, noupdategrub,   not-far

Partitions info (2/3): _________________________________________________________

sda1    : isnotESP, part-has-no-fstab,  no-nt,  no-winload, no-recov-nor-hid,   bootmgr,    is-winboot, ntfs
sda2    : isnotESP, part-has-no-fstab,  no-nt,  haswinload, no-recov-nor-hid,   bootmgr,    notwinboot, ntfs
sda3    : isnotESP, part-has-no-fstab,  no-nt,  no-winload, no-recov-nor-hid,   no-bmgr,    notwinboot, ntfs
sda4    : isnotESP, fstab-has-goodEFI,  no-nt,  no-winload, no-recov-nor-hid,   no-bmgr,    notwinboot, ext4
sdb2    : isnotESP, part-has-no-fstab,  no-nt,  no-winload, no-recov-nor-hid,   no-bmgr,    notwinboot, 

Partitions info (3/3): _________________________________________________________

sda1    : not--sepboot, no---boot,  part-has-no-fstab,  not-sep-usr,    no---usr,   part-has-no-fstab,  no--grub.d, sda
sda2    : not--sepboot, no---boot,  part-has-no-fstab,  not-sep-usr,    no---usr,   part-has-no-fstab,  no--grub.d, sda
sda3    : not--sepboot, no---boot,  part-has-no-fstab,  not-sep-usr,    no---usr,   part-has-no-fstab,  no--grub.d, sda
sda4    : not--sepboot, with-boot,  fstab-without-boot, not-sep-usr,    with--usr,  fstab-without-usr,  std-grub.d, sda
sdb2    : maybesepboot, no---boot,  part-has-no-fstab,  not-sep-usr,    no---usr,   part-has-no-fstab,  no--grub.d, sdb

fdisk -l (filtered): ___________________________________________________________

Disk sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk identifier: 0xac5a2c2c
     Boot     Start       End   Sectors   Size Id Type
sda1  *         2048    104447    102400    50M  7 HPFS/NTFS/exFAT
sda2          104448 468375058 468270611 223.3G  7 HPFS/NTFS/exFAT
sda3       936646656 937697279   1050624   513M 27 Hidden NTFS WinRE
sda4       468375060 936645668 468270609 223.3G 83 Linux
Partition table entries are not in disk order.
Disk sdb: 29.81 GiB, 32010928128 bytes, 62521344 sectors
Disk identifier: 0xfbc93123
     Boot    Start      End  Sectors  Size Id Type
sdb1  *         128 62521183 62521056 29.8G  c W95 FAT32 (LBA)
sdb2       62521263 62521325       63 31.5K ea Linux extended boot

parted -lm (filtered): _________________________________________________________

sda:480GB:scsi:512:4096:msdos:ATA SAMSUNG MZ7LH480:;
1:1049kB:53.5MB:52.4MB:ntfs::boot;
2:53.5MB:240GB:240GB:ntfs::;
4:240GB:480GB:240GB:ext4::;
3:480GB:480GB:538MB:ntfs::msftres;
sdb:32.0GB:scsi:512:512:msdos:SanDisk Cruzer Fit:;
1:65.5kB:32.0GB:32.0GB:fat32::boot, lba;
2:32.0GB:32.0GB:32.3kB:::bls_boot;

blkid (filtered): ______________________________________________________________

NAME   FSTYPE   UUID                                 PARTUUID                             LABEL             PARTLABEL
sda                                                                                                         
├─sda1 ntfs     4888F79388F77DAE                     ac5a2c2c-01                          System-reserviert 
├─sda2 ntfs     E048F94948F91ECA                     ac5a2c2c-02                                            
├─sda3 ntfs     742498FD2498C410                     ac5a2c2c-03                                            
└─sda4 ext4     a0ca6ff1-b6d7-4a85-98b2-d1a9df00a032 ac5a2c2c-04                          kubuntu_2404      
sdb                                                                                                         
├─sdb1 vfat     FABD-3A4E                            fbc93123-01                          THOMAS_LAUK       
└─sdb2                                               fbc93123-02                                            

Mount points (filtered): _______________________________________________________

                        Avail Use% Mounted on
/dev/sda1               14.3M  71% /mnt/boot-sav/sda1
/dev/sda2               87.8G  61% /mnt/boot-sav/sda2
/dev/sda3               88.3M  83% /mnt/boot-sav/sda3
/dev/sda4              199.8G   4% /mnt/boot-sav/sda4
/dev/sdb1               10.8G  64% /cdrom
efivarfs                77.4K  36% /sys/firmware/efi/efivars

Mount options (filtered): ______________________________________________________

/dev/sda1              fuseblk     rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/sda2              fuseblk     rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/sda3              fuseblk     rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/sda4              ext4        rw,relatime
/dev/sdb1              vfat        ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro

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

Ubuntu   a0ca6ff1-b6d7-4a85-98b2-d1a9df00a032
### END /etc/grub.d/30_os-prober ###
UEFI Firmware Settings   uefi-firmware
### END /etc/grub.d/30_uefi-firmware ###

========================== sda4/etc/fstab (filtered) ===========================

# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=a0ca6ff1-b6d7-4a85-98b2-d1a9df00a032 /              ext4    discard    0 1
/swapfile                                 swap           swap    defaults   0 0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

======================= sda4/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

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

           GiB - GB             File                                 Fragment(s)
            ?? = ??             boot/grub/grub.cfg                             1
 377,468076706 = 405,303261184  boot/grub/i386-pc/core.img                     1
 340,948003769 = 366,090131456  boot/vmlinuz                                   2
 340,948003769 = 366,090131456  boot/vmlinuz-6.14.0-27-generic                 2
 340,948003769 = 366,090131456  boot/vmlinuz.old                               2
 341,104253769 = 366,257903616  boot/initrd.img                                3
 341,104253769 = 366,257903616  boot/initrd.img-6.14.0-27-generic              3
 341,104253769 = 366,257903616  boot/initrd.img.old                            3

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

-rwxr-xr-x 1 root root 18133 Mär 17  2025 10_linux
-rwxr-xr-x 1 root root 43202 Mär 17  2025 10_linux_zfs
-rwxr-xr-x 1 root root 14513 Mär 17  2025 20_linux_xen
-rwxr-xr-x 1 root root   786 Mär 17  2025 25_bli
-rwxr-xr-x 1 root root 13120 Mär 17  2025 30_os-prober
-rwxr-xr-x 1 root root  1174 Mär 17  2025 30_uefi-firmware
-rwxr-xr-x 1 root root   214 Mär 17  2025 40_custom
-rwxr-xr-x 1 root root   215 Mär 17  2025 41_custom

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

Try or Install Kubuntu
Kubuntu (safe graphics)
OEM install (for manufacturers)
Boot from next volume
UEFI Firmware Settings
Test memory

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

           GiB - GB             File                                 Fragment(s)
            ?? = ??             boot/grub/grub.cfg                             1
paste.ubuntu.com ko ()

I hesitate to follow the advice to increase sda1 on linux because it would end up in resizing sda2 (Windows 7/8/10 partitions should only be modified by windows tools!?) ...

The final advice of boot-repair '... Finally select sda1 as [Separate /boot-Partition:] in register [Startreparatur] ...) could not be followed, because on my live-ubuntu sda1 wasn't detected, thus it couldn't be selected. ...

What would be the best solution?

Would it be possible to follow the aforementioned advice while running Boot-Repair from a live image or isn't sda1 big enough? Is there a console command to point from sda1 to sda4?

I'm trying to open a new xterm window with a different PS1. I've tried:

xterm -e '/bin/bash -i -l -c "export PS1=foo"'

This immediately closes xterm. So I tried:

xterm -hold -e '/bin/bash -i -l -c "export PS1=foo"'

which keeps xterm open, but I can't use it, i.e.: there is no prompt. Then played around with various options like:

xterm  -e  "export PS1=foo; $SHELL"

and so on ... But none seem to work. Can you please help?

$ xterm -version
XTerm(390)
$ bash --version
GNU bash, version 5.2.21(1)-release (x86_64-pc-linux-gnu)

I recently performed a clean install of Ubuntu 26.04 LTS and after a few days of which, today, I went to update the apps on my App Center. I clicked the Install All button and normally I was asked to authorize the install, and I did it. After that, the authorization screen popped up again. One thing I noted this time was that the authorization screen also had some warning saying something like the source can't be trusted or so. I've only installed manually from sources that are verified in the App Center (those with the green badge with a tick mark). For unofficial sources, I opted for .deb official packages or direct from their websites. Why am I still getting such warnings? Is this normal or should I worry? Here's a screenshot of the packages that I was trying to update.

Also when I pressed the Cancel button of the authorization dialog, the dialog re-appeared, always! This was just forcing me to authorize by showing it repeatedly even when pressing the Cancel button. And a couple of times I did re-authorize.

Xubuntu 26.04 - the display brightness slider in the upper panel area is not working anymore, moving it just has no effect.

I added this command line:

xrandr --output eDP1 --brightness 0.7

to the Session and Startup panel - autostart

but obviously the power manager seems to overrule this entry - it also shows no effect other than reducing the brightness after startup for about one second and then going up to 100 % again.

Does anyone has an advice for this issue? Thanks!

As far as spinners go, this one is probably not the best out there. Is there a way to swap it out for a calmer, more neutral spinner, or disable it entirely? The one in 25.10 was just fine

Thunderbird 153.0 (64-bit) on Ubuntu 26.04 crashed while checking email or receiving email from Google accounts. I tried to remove Thunderbird and install it again, but I did not succeed.

I can not log into Ubuntu Pro as it gives me a 502 error Bad Gateway. I am trying to activate Ubuntu Pro on Ubuntu 26.04. I have a Ubuntu One account but in that account there is no place to activate Ubuntu Pro. Not sure how I will be notified once you have sorted out your website as one can not log into your Ubuntu Pro website either as it gives a bad gateway error. It is not GUFW as that is disabled.

I'm using Ubuntu 24.04.4 on x86_64 PC with Canon MF230 connected via Ethernet. Printing a pdf file from Okular worked just fine last night, but stopped today. PC reboot and power cycling the printer didn't help. Here are the screenshots showing the print job permanently stuck on pending:

The scanning works just fine, but the printing doesn't. Any clues will be greatly appreciated.

Printing from another Ubuntu 24.04.4 PC goes into processing mode for a few seconds and stops in paused mode.

Printing from Windows PC works fine.

I upgraded from Ubuntu 24.04 to Ubuntu 26.04 using sudo do-release-upgrade -d and now man (manual) pages aren't working. I tried man atoi and I get No manual entry for atoi although compiling that with gcc worked fine, but the absence of man pages is bothering me.

I had a Lenovo Thinkpad T490 with a 256GB NVMe 2280 SSD loading Windows 11.

I want to install Kubuntu 26.04 on this laptop. For this I got another 256GB NVMe 2230 SSD and connected it to the WLAN port of the laptop.

Windows recognised this drive correctly. Then I boot from Kubuntu Live USB and that recognises both drives as well.

I installed Kubuntu on the new SSD with a partition configuration of 300MB FAT32 partition mounted to /boot/efi and boot flag on, and the rest of the drive formatted to ext4 mounted to /.

Install process goes on smoothly and it says "Finished". However, on reboot (after removing the live USB), it directly boots to Windows without the dual boot options.

So, as suggested in a Youtube video, I removed the original 2280 SSD and then reinstalled Kubuntu on the new 2230 SSD using the live USB (this time used Erase Disk option instead of manual partitioning).

This time again, the install went on smoothly, but when I rebooted after removing the liveusb, it doesn't show boot screen at all. Instead the BIOS asks for a medium to boot from.

I'd like to mention that in case of both installs, Kubuntu shows in the BIOS boot priority list and it didn't work even after putting it on the top of the list.

I am returning to Linux after 15 years, so please be patient with me.

Output of efibootmgr from live USB is:

kubuntu@kubuntu:~$ efibootmgr 

BootCurrent: 001F
Timeout: 2 seconds
BootOrder: 0001,001C,0010,0011,0012,0013,0014,0015,001B,001F,0019,001A,0000,001D,001E,0020,0021,0022,0023
Boot0000* Windows Boot Manager  HD(1,GPT,76f26192-bf42-41dc-b9e9-43d8205dd33d,0x800,0x32000)/\EFI\ubuntu\grubx64.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000033000100000010000000040000007fff0400
Boot0001* Kubuntu       HD(1,GPT,96c89b38-a577-4bde-a1c4-8ded1adb3746,0x1000,0x96000)/\EFI\ubuntu\shimx64.efi
Boot0010  Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu     FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012  Diagnostic Splash Screen      FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013  Lenovo Diagnostics    FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014  Regulatory Information        FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)
Boot0015  ThinkShield secure wipe       FvFile(3593a0d5-bd52-43a0-808e-cbff5ece2477)
Boot0016  Startup Interrupt Menu        FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0017  Rescue and Recovery   FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0018  MEBx Hot Key  FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
Boot0019* USB CD        VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot001A* USB FDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot001B* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot001C* NVMe1 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a401)
Boot001D* ATA HDD0      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f602)
Boot001E* ATA HDD1      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f601)
Boot001F* USB HDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot0020* PXE BOOT      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot0021* LENOVO CLOUD  VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri(https://download.lenovo.com/pccbbs/cdeploy/efi/boot.efi)
Boot0022  Other CD      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35406)
Boot0023  Other HDD     VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f606)
Boot0024* IDER BOOT CDROM       PciRoot(0x0)/Pci(0x14,0x0)/USB(11,1)
Boot0025* IDER BOOT Floppy      PciRoot(0x0)/Pci(0x14,0x0)/USB(11,0)
Boot0026* ATA HDD       VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0027* ATAPI CD      VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)

I can't directly see the pictures when there are some in the folders, I see the generic picture icon instead of the actual pictures. How to change that ?

Yes "show the thumbnails" is activated on "all files" in the preferences.

I tried debugging with ChatGPT, to no avail.

Thanks

Computer : MSI GT72 dominator pro, Ubuntu 24.04.

Edit: some picture do have a thumbnail, some don't ; same format...strange.

FINAL UPDATE

I finally got this janky operating system fixed.

My System

1. version of Ubuntu 24.04.4 LTS
2. output of uname -r is: 7.0.0-28-generic
3. GPU hardware name/model: GeForce GTX 1060 6GB

Because the screen size is 640x480 I can only see partial dialogs. Dialogs with interactive buttons are off screen. There is no known (to me) method to views dialogs that require a space larger than 640x480 pixels.

At the time when the screen size got stuck at 640x480 I was NOT updating anything. I was only using the computer in normal ways that users use computers.

At the time when the screen size got stuck at 640x480 I had unusual problems with my external USB drive not functioning correctly and acting weird. This led to rebooting my Ubuntu machine. This is when the resolution got stuck at 640x480.

At the time when the screen size got stuck at 649x480 I tried updating my Ubuntu machine thinking this may fix the problem. Things got worse. The updater couldn't accomplish certain things and gave errors. Due to the above condition I am unable to describe what these problems were for lack of visuals (i.e. dialogs off the screen).

I'd rather not reformat the entire system - but this may be the only option.

UPDATE 1:

After reading random solutions on the internet I have this really bad feeling that it's 100% impossible for me to fix this. If my system has recently updated to something absolutely incompatible with my GPU card then I guess I'm just hosed. There's no way I'll be able to "hack" a driver as others have suggested.

This is why I've always been against upgrades - especially when nothing was broken to begin with. At the very least there should be some method to roll back to the previous state if some problem like this were to occur.

EDIT 1 & 2 - (A) added Ubuntu version (B) added descriptive text. (C) deleted a paragraph (D) Deleted and added text at top

EDIT 3

I believe I have the Desktop version of Ubuntu - it just says Ubuntu 24.04.4 LTS with no mention about kernels. I installed the original Desktop version in January of 2026 using a bootable USB. Therefore, the version was likely version 22 (or close to that version).

I wasn't updating (yesterday) when the resolution got stuck at 640x480. Although it is possible that one or two or three or seven days ago I updated. I just don't know. But my machine was in high resolution mode when I booted it - it was only after rebooting (yesterday) that the resolution issue showed up. Regarding Updates: although I wasn't updating anything yesterday I began updating to try to fix the sudden resolution problem. Updating failed. I got error messages. I tried a partial update. I guess that worked. (except for the resolution).

I ran the following command to see if there were NVIDIA errors:

Sudo dmesg

I saved the above output to a text file, then searched for things like “error” – and found nothing. The output text is lengthy. The copy is on my MacBook). I am hesitant to post all this data online (it is lengthy). Therefore, it would be helpful if I had some idea what to look for.

I copied the dpkg.log file (to my MacBook). This should have information on system updates. Which there are because I deleted all NVIDIA stuff and then ran an update to force an update (this procedure is online somewhere). But there was an update prior to this (which was failing for some reason). Again, what should I look for here?

I created a bootable USB with Ubuntu 22.04.5 on it and observed that I could achieve a default resolution of 1080x1920 (and higher). I used the “Try Ubuntu” menu item (which is neat). I got the ISO from here: https://releases.ubuntu.com/jammy/

Prior to creating the above bootable USB I did the same, but using Ubuntu 26.04 for the bootable USB (the latest as of today’s date). I got this ISO from here: https://ubuntu.com/download/desktop This didn't work. I got the following error so I killed it

Ubuntu 26.04 [ 27.969569] Novacore0000:03:00.0 Unsupported chipset: boot42 = 0x136a1000 (architecture 0x13, implementation 0x6)

That's all I have for now - as of July 24, 2026.

Reinstalling an Ubuntu version that works for my NVIDA card is likely the most efficient. Long distance computer forensics will take years (sarcasm) to find the root problem. But, I think everybody already knows what the problem is. Ubuntu doesn't work with my graphics card. Pretty simple.

I now know that Ubuntu 22.04.5 works.

EDIT 4 - added the output of uname -r at top (7.0.0-28-generic). running "sudo apt update && sudo apt full-upgrade" followed by rebooting did not fix the problem.

Space repartition:

Inability to scroll to the left with the slider:

I had lots of unused space on my (almost) unused Windows partition, so I wanted to switch it to Ubuntu. When I open gparted, here's what the diagram looks like:

[EFI system partition] -> [Microsoft boot partition] -> [Basic data partition (Microsoft's storage)] -> free space -> [Ubuntu partition].

The problem is that given that Ubuntu is at the right of the space I want to add to it, I can't fuse to the left nor move with gparted. I don't know what to do to be able to fuse the two.

At this point I'm almost ready to uninstall Ubuntu and create a new partition with more space. I've also seen that you can create a live USB key. If that's less far-fetched than all the black magic required to fuse a partition to the left, I'll take it.

SOLUTION : formatting a USB stick with Rufus and put Ubuntu 26.04 on it as an ISO image. You can go up to the BIOS by rebooting your computer and smashing F2 (or F10, F12 depending on your brand). Put USB-HDD in n°1 priority, it will allow you to launch Ubuntu from the stick. You can then use GPARTED to move the other partitions on the computer safely.

My screen resolution has defaulted to 800 x 600 after an update and I cannot change it. I have an Nvidia 3060 GPU. I am running Ubuntu 26.04. Kernel is Linux 7.0.0-27 Generic. In the Systems Details it shows "Software Rendering" under "Graphics". Should it not show the graphics card installed?

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

Edit: I should specify this dongle is a Bluetooth 6.0 dongle.

After upgrading from Ubuntu 25. to Ubuntu 26.04 LTS, randomly when starting Thunderbird the screen freezes and says "kernel panic fatal exception in interrupt" After restart it continues to work, but randomly crashes again?

After accepting the offer to update from 22.04 LTS to 24.04.01 LTS the system stands still during the boot process showing only the "FUJITSU" splash screen. (To be precise: The "FUJITSU" shows up, then the screen gets black for ~1sec, then it re-appears. The "black-screen" time is normally where one can press F2 and F12 to enter the BIOS)

• Entering the BIOS does not work any longer.
• The system does not start.
• BIOS recovery cannot be entered (also not by changing the jumpers on the main board). The USB stick is not detected and not booted.

After mounting the same M2 memory in a second PC with the system boots up and enters the new Ubuntu Linux. After the next reboot the same happens also to this second PC. It stands still in the same position, not being able to enter BIOS or the OS.

• Mounting back the earlier working M2 memory into the PC does not recover the system.
• removing the backup battery does not help
• The keyboard is USB, same slot that worked to enter the BIOS before. PS/2 is not available to me.

Any idea on what happens to the system that is permanent? Any idea what else can help to recover two earlier well working PCs (Fujitsu Siemens P756/E94+)?

As the title says, automatic login is not working. I've tried a few things, turning it off and on, changing the password, and restarting the system. I always get asked for a password on login however, and with a forced long password it gets abit annoying to have to type it in every time I need to log in.

Output of lsb_release -a

No LSB modules are avalible.
Distributor ID: Ubuntu
Description: Ubuntu 22.04 LTS
Release: 22.04
Codename: jammy

EDIT: It seems that automatic login is configured correctly in accordance with GDM3, however it is simply refuseing to work.

Since more than one month I see this process "gvfs-udisks2-volume-monitor" using one of my cpu-cores constantly between 25 and 50 %.
I'm running Ubuntu 22.04.3 LTS on Linux 6.2.0-35-generic, x86-64, Consumer hardware used as server and media system, CPU: Ryzen 3 4300GE, OS and some data is on an nvme-ssd (2tb 970 evo plus), data is on 3 hard drives, two of them are in a mdadm-raid and mainly sleeping, all in a self-printed pc-case, no other storage connected, two usb connected for giving power to switch and light and one usb for USV-communication and one for keyboard. Unplugging all USBs does not change cpu-usage. gvfs versions seems to be 1.48.2-0ubuntu1. I mainly run Nextcloud, Jellyfin, and Apache2, some minor apps and docker containers.
Here is a graph of the cpu-usage measured every half an hour with ps -e -o pid,user,comm,%cpu | grep 'gvfs-udisks', the spike at the end was after a reboot:

Please help me fix this.
I don't know what additional info is needed, I will just list things I've tried here:

1. I tried killing it according to this answer but then I was not able to access or empty my trash and it came back alive anyway so I reverted.
2. I tried stopping all my docker containers with no difference.
3. to make sure this is no virus I was looking at parent processes:

    richi@richihomecl:~$ sudo ps -e -o ppid,pid,user,comm,%cpu | grep 'gvfs-udisks'  
       7797    8280 richi    gvfs-udisks2-vo 31.8  
    richi@richihomecl:~$ sudo ps -q 7797 -o ppid,pid,user,comm,%cpu  
       PPID     PID USER     COMMAND         %CPU  
          1    7797 richi    systemd          2.7  

    richi@richihomecl:~$ sudo lsof -p 8280
    lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
          Output information may be incomplete.
    lsof: WARNING: can't stat() fuse.portal file system /run/user/1000/doc
          Output information may be incomplete.
    COMMAND    PID  USER   FD      TYPE             DEVICE SIZE/OFF     NODE NAME
    gvfs-udis 8280 richi  cwd       DIR              253,0     4096 73662467 /home/richi
    gvfs-udis 8280 richi  rtd       DIR              253,0     4096        2 /
    gvfs-udis 8280 richi  txt       REG              253,0   187360 89142453 /usr/libexec/gvfs-udisks2-volume-monitor
    gvfs-udis 8280 richi  mem       REG              253,0  6070224 89129711 /usr/lib/locale/locale-archive
    gvfs-udis 8280 richi  DEL       REG              253,0          74451910 /home/richi/.config/dconf/user
    gvfs-udis 8280 richi  mem       REG              253,0   204237 92540357 /usr/share/glib-2.0/schemas/gschemas.compiled
    gvfs-udis 8280 richi  mem       REG              253,0   268520 91099771 /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
    gvfs-udis 8280 richi  mem       REG              253,0   211448 91099041 /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
    gvfs-udis 8280 richi  mem       REG              253,0   149760 89141471 /usr/lib/x86_64-linux-gnu/libgpg-error.so.0.32.1
    gvfs-udis 8280 richi  mem       REG              253,0   633536 89141817 /usr/lib/x86_64-linux-gnu/libpcre2-8.so.0.11.0
    gvfs-udis 8280 richi  mem       REG              253,0   220192 89141176 /usr/lib/x86_64-linux-gnu/libblkid.so.1.1.0
    gvfs-udis 8280 richi  mem       REG              253,0  1296312 89141417 /usr/lib/x86_64-linux-gnu/libgcrypt.so.20.3.4
    gvfs-udis 8280 richi  mem       REG              253,0   125152 89141633 /usr/lib/x86_64-linux-gnu/liblz4.so.1.9.3
    gvfs-udis 8280 richi  mem       REG              253,0   841808 89142186 /usr/lib/x86_64-linux-gnu/libzstd.so.1.4.8
    gvfs-udis 8280 richi  mem       REG              253,0   170456 89141635 /usr/lib/x86_64-linux-gnu/liblzma.so.5.2.5
    gvfs-udis 8280 richi  mem       REG              253,0   166240 89131188 /usr/lib/x86_64-linux-gnu/libudev.so.1.7.2
    gvfs-udis 8280 richi  mem       REG              253,0   940560 89131573 /usr/lib/x86_64-linux-gnu/libm.so.6
    gvfs-udis 8280 richi  mem       REG              253,0   485744 89130717 /usr/lib/x86_64-linux-gnu/libpcre.so.3.13.3
    gvfs-udis 8280 richi  mem       REG              253,0   166280 89141928 /usr/lib/x86_64-linux-gnu/libselinux.so.1
    gvfs-udis 8280 richi  mem       REG              253,0  2216304 89131567 /usr/lib/x86_64-linux-gnu/libc.so.6
    gvfs-udis 8280 richi  mem       REG              253,0    39024 89142907 /usr/lib/x86_64-linux-gnu/libcap.so.2.44
    gvfs-udis 8280 richi  mem       REG              253,0    47688 89141357 /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0
    gvfs-udis 8280 richi  mem       REG              253,0   273056 89141676 /usr/lib/x86_64-linux-gnu/libmount.so.1.1.0
    gvfs-udis 8280 richi  mem       REG              253,0   108936 89142180 /usr/lib/x86_64-linux-gnu/libz.so.1.2.11
    gvfs-udis 8280 richi  mem       REG              253,0    22736 89130058 /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0.7200.4
    gvfs-udis 8280 richi  mem       REG              253,0   395424 89141926 /usr/lib/x86_64-linux-gnu/libsecret-1.so.0.0.0
    gvfs-udis 8280 richi  mem       REG              253,0   807936 89130244 /usr/lib/x86_64-linux-gnu/libsystemd.so.0.32.0
    gvfs-udis 8280 richi  mem       REG              253,0   768072 89142042 /usr/lib/x86_64-linux-gnu/libudisks2.so.0.0.0
    gvfs-udis 8280 richi  mem       REG              253,0    51272 89141519 /usr/lib/x86_64-linux-gnu/libgudev-1.0.so.0.3.0
    gvfs-udis 8280 richi  mem       REG              253,0  1277712 89129107 /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7200.4
    gvfs-udis 8280 richi  mem       REG              253,0   387464 89130070 /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.7200.4
    gvfs-udis 8280 richi  mem       REG              253,0  1924496 89129102 /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.7200.4
    gvfs-udis 8280 richi  mem       REG              253,0    63552 91099033 /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
    gvfs-udis 8280 richi  mem       REG              253,0   240936 89131564 /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
    gvfs-udis 8280 richi  DEL       REG              0,325                81 /run/user/1000/dconf/user
    gvfs-udis 8280 richi    0r      CHR                1,3      0t0        5 /dev/null
    gvfs-udis 8280 richi    1u     unix 0xffff8d79f5fa72c0      0t0    60407 type=STREAM
    gvfs-udis 8280 richi    2u     unix 0xffff8d79f5fa72c0      0t0    60407 type=STREAM
    gvfs-udis 8280 richi    3u  a_inode               0,14        0       62 [eventfd]
    gvfs-udis 8280 richi    4u  a_inode               0,14        0       62 [eventfd]
    gvfs-udis 8280 richi    5u     unix 0xffff8d79ff563b80      0t0    59199 type=STREAM
    gvfs-udis 8280 richi    6u  a_inode               0,14        0       62 [eventfd]
    gvfs-udis 8280 richi    7u     sock                0,8      0t0    59223 protocol: NETLINK
    gvfs-udis 8280 richi    8u     unix 0xffff8d79b371d0c0      0t0    60994 type=STREAM
    gvfs-udis 8280 richi    9r  a_inode               0,14        0       62 inotify
    gvfs-udis 8280 richi   10r      REG               0,22        0    60410 /proc/8280/mountinfo
    gvfs-udis 8280 richi   11u  a_inode               0,14        0       62 [eventfd]

    richi@richihomecl:~$ sudo blkid
    /dev/mapper/luks-9e54f936-e7c0-4ece-ab06-89776d516967: LABEL="2tb970" UUID="2690fc02-ffbc-4092-a32d-db407eb73b7d" BLOCK_SIZE="4096" TYPE="ext4"
    /dev/loop1: TYPE="squashfs"
    /dev/loop29: TYPE="squashfs"
    /dev/mapper/WDraid: LABEL="WDraid" UUID="d905f54b-ccc2-4b29-870a-b329df2acf62" BLOCK_SIZE="4096" TYPE="ext4"
    /dev/loop19: TYPE="squashfs"
    /dev/nvme0n1p3: UUID="9e54f936-e7c0-4ece-ab06-89776d516967" TYPE="crypto_LUKS" PARTUUID="f305037b-35ba-4a9c-bb66-b7fdc64a7301"
    /dev/nvme0n1p1: UUID="B21E-68FD" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="2ba3bf16-203e-4be0-88fd-d033f3b4d8f8"
    /dev/nvme0n1p2: UUID="f8a307c1-a09b-46b8-ba2a-eec90b30dc5e" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="f70eb402-21a3-4f22-9834-93274ba688b5"
    /dev/loop27: TYPE="squashfs"
    /dev/loop17: TYPE="squashfs"
    /dev/loop8: TYPE="squashfs"
    /dev/loop35: TYPE="squashfs"
    /dev/loop25: TYPE="squashfs"
    /dev/sdb1: UUID="bd83c4b8-dcd4-4102-b3fc-70a998991db4" TYPE="crypto_LUKS" PARTUUID="9da340fa-7116-40fd-96b4-5b15b446fa77"
    /dev/loop15: TYPE="squashfs"
    /dev/loop6: TYPE="squashfs"
    /dev/loop33: TYPE="squashfs"
    /dev/loop23: TYPE="squashfs"
    /dev/loop13: TYPE="squashfs"
    /dev/loop4: TYPE="squashfs"
    /dev/loop31: TYPE="squashfs"
    /dev/loop21: TYPE="squashfs"
    /dev/loop11: TYPE="squashfs"
    /dev/md0: UUID="b37c932a-cee9-4c00-b1c4-55d6c46c8e45" TYPE="crypto_LUKS"
    /dev/loop2: TYPE="squashfs"
    /dev/mapper/TOSHI1: LABEL="Toshi1" UUID="c4d5c0a1-740f-4746-b894-d066e815b5bf" BLOCK_SIZE="4096" TYPE="ext4"
    /dev/loop0: TYPE="squashfs"
    /dev/loop28: TYPE="squashfs"
    /dev/loop18: TYPE="squashfs"
    /dev/loop9: TYPE="squashfs"
    /dev/loop26: TYPE="squashfs"
    /dev/sdc1: UUID="50bcf8e3-684f-6aa2-b325-bb179aecbe3d" UUID_SUB="777aced7-3e40-f978-54cf-badee5b17989" LABEL="richihomecl:0" TYPE="linux_raid_member" PARTUUID="6360d8c2-01"
    /dev/loop16: TYPE="squashfs"
    /dev/loop7: TYPE="squashfs"
    /dev/loop34: TYPE="squashfs"
    /dev/loop24: TYPE="squashfs"
    /dev/sda: UUID="50bcf8e3-684f-6aa2-b325-bb179aecbe3d" UUID_SUB="168752fb-a767-8fa3-31d3-b51b1d7963bb" LABEL="richihomecl:0" TYPE="linux_raid_member"
    /dev/loop14: TYPE="squashfs"
    /dev/loop5: TYPE="squashfs"
    /dev/loop32: TYPE="squashfs"
    /dev/loop22: TYPE="squashfs"
    /dev/loop12: TYPE="squashfs"
    /dev/loop3: TYPE="squashfs"
    /dev/loop30: TYPE="squashfs"
    /dev/loop20: TYPE="squashfs"
    /dev/loop10: TYPE="squashfs"

    richi@richihomecl:~$ sudo lsblk
    NAME                                          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
    loop0                                           7:0    0     4K  1 loop  /snap/bare/5
    loop1                                           7:1    0  95,7M  1 loop  /snap/bombsquad/13
    loop2                                           7:2    0  94,5M  1 loop  /snap/bombsquad/16
    loop3                                           7:3    0   9,6M  1 loop  /snap/canonical-livepatch/246
    loop4                                           7:4    0   9,9M  1 loop  /snap/canonical-livepatch/248
    loop5                                           7:5    0 105,8M  1 loop  /snap/core/16091
    loop6                                           7:6    0 105,8M  1 loop  /snap/core/16202
    loop7                                           7:7    0  55,7M  1 loop  /snap/core18/2785
    loop8                                           7:8    0  55,7M  1 loop  /snap/core18/2790
    loop9                                           7:9    0  63,4M  1 loop  /snap/core20/1974
    loop10                                          7:10   0  63,5M  1 loop  /snap/core20/2015
    loop11                                          7:11   0  73,9M  1 loop  /snap/core22/858
    loop12                                          7:12   0  73,9M  1 loop  /snap/core22/864
    loop13                                          7:13   0 240,5M  1 loop  /snap/firefox/3206
    loop14                                          7:14   0 238,8M  1 loop  /snap/firefox/3252
    loop15                                          7:15   0 521,4M  1 loop  /snap/gimp/393
    loop16                                          7:16   0 520,9M  1 loop  /snap/gimp/405
    loop17                                          7:17   0 164,8M  1 loop  /snap/gnome-3-28-1804/194
    loop18                                          7:18   0 164,8M  1 loop  /snap/gnome-3-28-1804/198
    loop19                                          7:19   0 218,4M  1 loop  /snap/gnome-3-34-1804/90
    loop20                                          7:20   0 218,4M  1 loop  /snap/gnome-3-34-1804/93
    loop21                                          7:21   0 349,7M  1 loop  /snap/gnome-3-38-2004/140
    loop22                                          7:22   0 349,7M  1 loop  /snap/gnome-3-38-2004/143
    loop23                                          7:23   0   497M  1 loop  /snap/gnome-42-2204/141
    loop24                                          7:24   0 496,9M  1 loop  /snap/gnome-42-2204/132
    loop25                                          7:25   0   140K  1 loop  /snap/gtk2-common-themes/13
    loop26                                          7:26   0  81,3M  1 loop  /snap/gtk-common-themes/1534
    loop27                                          7:27   0  91,7M  1 loop  /snap/gtk-common-themes/1535
    loop28                                          7:28   0  37,1M  1 loop  /snap/hunspell-dictionaries-1-7-2004/2
    loop29                                          7:29   0 126,3M  1 loop  /snap/silex-desktop/x1
    loop30                                          7:30   0  12,3M  1 loop  /snap/snap-store/959
    loop31                                          7:31   0  45,9M  1 loop  /snap/snap-store/638
    loop32                                          7:32   0  40,9M  1 loop  /snap/snapd/20290
    loop33                                          7:33   0  40,8M  1 loop  /snap/snapd/20092
    loop34                                          7:34   0 407,8M  1 loop  /snap/telegram-desktop/5113
    loop35                                          7:35   0 409,8M  1 loop  /snap/telegram-desktop/5133
    sda                                             8:0    0 931,5G  0 disk  
    └─md0                                           9:0    0 931,4G  0 raid1 
      └─WDraid                                    253:1    0 931,4G  0 crypt /mnt/WDraid
    sdb                                             8:16   0  12,7T  0 disk  
    └─sdb1                                          8:17   0  12,7T  0 part  
      └─TOSHI1                                    253:2    0  12,7T  0 crypt /mnt/TOSHI1
    sdc                                             8:32   0 931,5G  0 disk  
    └─sdc1                                          8:33   0 931,5G  0 part  
      └─md0                                         9:0    0 931,4G  0 raid1 
        └─WDraid                                  253:1    0 931,4G  0 crypt /mnt/WDraid
    nvme0n1                                       259:0    0   1,8T  0 disk  
    ├─nvme0n1p1                                   259:1    0   550M  0 part  /boot/efi
    ├─nvme0n1p2                                   259:2    0   768M  0 part  /boot
    └─nvme0n1p3                                   259:3    0   1,8T  0 part  
      └─luks-9e54f936-e7c0-4ece-ab06-89776d516967 253:0    0   1,8T  0 crypt /var/snap/firefox/common/host-hunspell
                                                                             /

    sudo strace -p 8280
    strace: Process 8280 attached
    restart_syscall(<... resuming interrupted read ...>) = 1
    write(3, "\1\0\0\0\0\0\0\0", 8)         = 8
    clock_gettime(CLOCK_MONOTONIC, {tv_sec=8491, tv_nsec=751319759}) = 0
    write(3, "\1\0\0\0\0\0\0\0", 8)         = 8
    write(3, "\1\0\0\0\0\0\0\0", 8)         = 8
    clock_gettime(CLOCK_MONOTONIC, {tv_sec=8491, tv_nsec=751414675}) = 0
    poll([{fd=3, events=POLLIN}, {fd=10, events=0}], 2, 0) = 2 ([{fd=3, revents=POLLIN}, {fd=10, revents=POLLERR}])
    read(3, "\3\0\0\0\0\0\0\0", 16)         = 8
    openat(AT_FDCWD, "/proc/self/mountinfo", O_RDONLY|O_CLOEXEC) = 12
    newfstatat(12, "", {st_mode=S_IFREG|0444, st_size=0, ...}, AT_EMPTY_PATH) = 0
    read(12, "23 30 0:21 / /sys rw,nosuid,node"..., 1024) = 1024
    readlink("/proc", 0x7ffee7779b50, 1023) = -1 EINVAL (Invalid argument)
    readlink("/proc/self", "8280", 1023)    = 4
    readlink("/proc/8280", 0x7ffee7779b50, 1023) = -1 EINVAL (Invalid argument)
    readlink("/proc/8280/mountinfo", 0x7ffee7779b50, 1023) = -1 EINVAL (Invalid argument)
    read(12, "atime shared:10 - cgroup2 cgroup"..., 1024) = 1024
    read(12, "ev,noexec,relatime shared:21 - r"..., 1024) = 1024
    read(12, ",nodev,relatime shared:61 - squa"..., 1024) = 1024
    read(12, "/snap/gnome-3-28-1804/194 ro,nod"..., 1024) = 1024
    read(12, ",nodev,relatime shared:95 - squa"..., 1024) = 1024
    read(12, "190 30 7:33 / /snap/snapd/20092 "..., 1024) = 1024
    read(12, "pd/ns rw,nosuid,nodev,noexec,rel"..., 1024) = 1024
    read(12, "3VEVSKOLL7QYTPBFMO5A3RA:/var/lib"..., 1024) = 1024
    read(12, "ay2/l/4VBMVTNPL5OCWOA6UNNNUMKFJL"..., 1024) = 1024
    read(12, "ker/overlay2/l/ALHLFNCYV4NERBARI"..., 1024) = 1024
    read(12, "r/lib/docker/overlay2/l/EDGWEROK"..., 1024) = 1024
    read(12, "4e11783ebe54da55de218b0d2290b7af"..., 1024) = 1024
    read(12, "MLZVRMRBX6BWDSQBRQ6Q2:/var/lib/d"..., 1024) = 1024
    read(12, " - overlay overlay rw,lowerdir=/"..., 1024) = 1024
    read(12, "lib/docker/overlay2/c746ceabc818"..., 1024) = 1024
    read(12, "31e13b0686a9f9d553901eac2188d6b6"..., 1024) = 1024
    read(12, "2LAGQVHUPH:/var/lib/docker/overl"..., 1024) = 1024
    read(12, "QAKUXGAQSYD232JRY76:/var/lib/doc"..., 1024) = 1024
    read(12, "l/K7FU5IHM2J5C645CPDS4XXHJJQ:/va"..., 1024) = 1024
    read(12, "overlay2/l/ROUKI7LRQI763Z3BPMCGV"..., 1024) = 1024
    read(12, "b/docker/overlay2/l/QLHKYUYVRF5A"..., 1024) = 1024
    read(12, "CD:/var/lib/docker/overlay2/l/NE"..., 1024) = 1024
    read(12, "N3TYOH6VIVY:/var/lib/docker/over"..., 1024) = 1024
    read(12, "y overlay rw,lowerdir=/var/lib/d"..., 1024) = 1024
    read(12, "2/l/VIBDZDKVQLOLHQR46SBCXVX4KI:/"..., 1024) = 1024
    read(12, "er/overlay2/l/5UTZBETHRGXRM7AQVN"..., 1024) = 1024
    read(12, "/lib/docker/overlay2/l/GPBZL5C4Z"..., 1024) = 1024
    read(12, "5JBU:/var/lib/docker/overlay2/l/"..., 1024) = 1024
    read(12, "7JKTPWNKCGVQA:/var/lib/docker/ov"..., 1024) = 1024
    read(12, "3IVOXWK3OBPT6VUITEG43GU:/var/lib"..., 1024) = 1024
    read(12, "ay2/l/4NNKABRN2XMT62P6FVE5J4HZA5"..., 1024) = 1024
    read(12, "53ea18d rw shared:2575 - nsfs ns"..., 1024) = 1024
    read(12, "/var/lib/docker/overlay2/50041e2"..., 1024) = 1024
    read(12, " 27 0:4 net:[4026534294] /run/do"..., 1024) = 1024
    read(12, "4793] /run/docker/netns/a6c2da44"..., 1024) = 1024
    read(12, "W:/var/lib/docker/overlay2/l/CRU"..., 1024) = 1024
    read(12, "] /run/snapd/ns/telegram-desktop"..., 1024) = 1024
    read(12, "0:350 / /var/lib/docker/overlay2"..., 1024) = 1024
    read(12, "cker/overlay2/l/J3RNDWQAEMTVXC4K"..., 1024) = 1024
    read(12, "/overlay2/b5e01bdffa939fa5acc117"..., 1024) = 1024
    read(12, "var/lib/docker/overlay2/l/F26LND"..., 1024) = 1024
    read(12, "d/merged rw,relatime shared:1573"..., 1024) = 1024
    read(12, "=/var/lib/docker/overlay2/l/NHF5"..., 1024) = 1024
    read(12, "time shared:1640 - overlay overl"..., 1024) = 1024
    read(12, "5I:/var/lib/docker/overlay2/l/WI"..., 1024) = 1024
    read(12, "V7NIVEC55SI4:/var/lib/docker/ove"..., 1024) = 1024
    read(12, "A35BKHQPZYGSONCLB2WF6W:/var/lib/"..., 1024) = 1024
    read(12, "ay2/l/IJPLWZCZR5XYDZNF4IKNTAWTIT"..., 1024) = 1024
    read(12, "cker/overlay2/l/CRYKKZKU6WT7L6KU"..., 1024) = 1024
    read(12, "pperdir=/var/lib/docker/overlay2"..., 1024) = 1024
    read(12, "diff,workdir=/var/lib/docker/ove"..., 1024) = 1024
    read(12, "ee35/work,nouserxattr\n9168 30 0:"..., 1024) = 1024
    read(12, "3c0bd09dc7341ce63674c66c1167a/me"..., 1024) = 1024
    read(12, "b/docker/overlay2/l/YPJMBJXOYQGJ"..., 1024) = 1024
    read(12, "O2:/var/lib/docker/overlay2/l/F2"..., 1024) = 1024
    read(12, "VED6AMWNQW4P:/var/lib/docker/ove"..., 1024) = 1024
    read(12, "3425 - nsfs nsfs rw\n10486 27 0:4"..., 1024) = 1024
    read(12, "r/lib/docker/overlay2/l/TOXUWY6H"..., 1024) = 1024
    read(12, "E6ODRIT:/var/lib/docker/overlay2"..., 1024) = 1024
    read(12, "G:/var/lib/docker/overlay2/l/EK6"..., 1024) = 1024
    read(12, "ker/overlay2/49b70ef1f3316af2657"..., 1024) = 1024
    read(12, "/c4008157d6bfbe3d8d66cf1f2da243d"..., 1024) = 1024
    read(12, "ZP6VE3D3OWP4:/var/lib/docker/ove"..., 1024) = 1024
    read(12, "werdir=/var/lib/docker/overlay2/"..., 1024) = 1024
    read(12, "2cfb32f3f39ce1757453b579d1991a67"..., 1024) = 1024
    read(12, "orkdir=/var/lib/docker/overlay2/"..., 1024) = 1024
    read(12, "225b025d15896a28b03e7c02f6914b48"..., 1024) = 1024
    read(12, "/var/lib/docker/overlay2/1974463"..., 1024) = 1024
    read(12, "ib/docker/overlay2/a8b66aac8f67f"..., 1024) = 1024
    read(12, "4830 27 0:4 net:[4026537242] /ru"..., 1024) = 1024
    read(12, "b/docker/overlay2/c14d9210ebc906"..., 1024) = 1024
    read(12, "3269c38042a5bd61ca8378bf906efbd6"..., 1024) = 1024
    read(12, "ocker/netns/1d7dc84444fc rw shar"..., 1024) = 55
    read(12, "", 1024)                      = 0
    close(12)                               = 0
    getuid()                                = 1000
    newfstatat(AT_FDCWD, "/run", {st_mode=S_IFDIR|0755, st_size=1400, ...}, 0) = 0
    newfstatat(AT_FDCWD, "/run/mount/utab", {st_mode=S_IFREG|0644, st_size=2449, ...}, 0) = 0
    openat(AT_FDCWD, "/run/mount/utab", O_RDONLY|O_CLOEXEC) = 12
    newfstatat(12, "", {st_mode=S_IFREG|0644, st_size=2449, ...}, AT_EMPTY_PATH) = 0
    read(12, "SRC=/dev/loop0 TARGET=/snap/bare"..., 4096) = 2449
    read(12, "", 4096)                      = 0
    close(12)                               = 0
    getuid()                                = 1000
    newfstatat(AT_FDCWD, "/etc/fstab", {st_mode=S_IFREG|0664, st_size=958, ...}, 0) = 0
    openat(AT_FDCWD, "/proc/self/mountinfo", O_RDONLY|O_CLOEXEC) = 12
    newfstatat(12, "", {st_mode=S_IFREG|0444, st_size=0, ...}, AT_EMPTY_PATH) = 0
    read(12, "23 30 0:21 / /sys rw,nosuid,node"..., 1024) = 1024
    REPEATING ITSELF

    richi@richihomecl:~$ dpkg -l | grep gvfs
    ||/ Name                                                        Version                                                        Architecture Description
    ii  gvfs:amd64                                                  1.48.2-0ubuntu1                                                amd64        userspace virtual filesystem - GIO module
    ii  gvfs-backends                                               1.48.2-0ubuntu1                                                amd64        userspace virtual filesystem - backends
    ii  gvfs-common                                                 1.48.2-0ubuntu1                                                all          userspace virtual filesystem - common data files
    ii  gvfs-daemons                                                1.48.2-0ubuntu1                                                amd64        userspace virtual filesystem - servers
    ii  gvfs-fuse                                                   1.48.2-0ubuntu1                                                amd64        userspace virtual filesystem - fuse server
    ii  gvfs-libs:amd64                                             1.48.2-0ubuntu1                                                amd64        userspace virtual filesystem - private libraries

    richi@richihomecl:~$ grep gvfs-udi /var/log/syslog
    Oct 30 11:02:47 richihomecl dbus-daemon[2834]: [session uid=125 pid=2834] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.9' (uid=125 pid=3135 comm="/usr/libexec/tracker-miner-fs-3 " label="unconfined")
    Oct 30 11:03:02 richihomecl dbus-daemon[7923]: [session uid=1000 pid=7923] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.7' (uid=1000 pid=7981 comm="/usr/libexec/tracker-miner-fs-3 " label="unconfined")
    Oct 30 11:03:22 richihomecl systemd[2752]: gvfs-udisks2-volume-monitor.service: Consumed 11.545s CPU time.

I'd like to do the same thing like that:

Increase number of old kernels to keep on autoremove

but in Ubuntu 22.04 I can't find the apt-auto-removal file.

Update:

These are the contents of this directory.

00aptitude        15update-stamp      20packagekit          60icons
00trustcdrm       20apt-esm-hook.conf 20snapd.conf          60icons-hidpi
01autoremove      20archive           50appstream           70debconf
01-vendor-ubuntu  20auto-upgrades     50command-not-found   99update-notifier
10periodic        20dbus              50unattended-upgrades

and I have an "01autoremove" file, and this is what I have inside:

/etc/apt/apt.conf.d$ cat 01autoremove :

APT
{
  NeverAutoRemove
  {
    "^firmware-linux.*";
    "^linux-firmware$";
    "^linux-image-[a-z0-9]*$";
    "^linux-image-[a-z0-9]*-[a-z0-9]*$";
  };

  VersionedKernelPackages
  {
    # kernels
    "linux-.*";
    "kfreebsd-.*";
    "gnumach-.*";
    # (out-of-tree) modules
    ".*-modules";
    ".*-kernel";
  };

  Never-MarkAuto-Sections
  {
    "metapackages";
    "contrib/metapackages";
    "non-free/metapackages";
    "restricted/metapackages";
    "universe/metapackages";
    "multiverse/metapackages";
  };

  Move-Autobit-Sections
  {
    "oldlibs";
    "contrib/oldlibs";
    "non-free/oldlibs";
    "restricted/oldlibs";
    "universe/oldlibs";
    "multiverse/oldlibs";
  };
};

Do you know what I need to change?

As described by ubuntu.com/blog/ubuntu-core-in-lxd-containers, Ubuntu Core can be installed via snapcraft.io/lxd by executing lxc launch images:ubuntu-core/16 ubuntu-core. The tutorial is outdated because the most new version of Ubuntu Core appears to be 20 (instead of 16).

Consequently, I executed lxc launch images:ubuntu-core/20 ubuntu-core, which has failed to do what it should have done. What should be done?

$ lxc launch images:ubuntu-core/20 ubuntu-core

Creating ubuntu-core
 
Error: Failed instance creation: Failed getting image: Failed parsing
stream: 
Get "https://uk.images.linuxcontainers.org/streams/v1/index.json": x509: 
certificate has expired or is not yet valid: 
current time 2021-09-01T15:42:30+01:00 is after 2021-09-01T12:00:00Z

I'd like to install latest konsole on Ubuntu 20.10.

I see in the public repo that latest version is konsole/groovy,now 4:20.08.2-0ubuntu1 amd64, but I know that the current latest is 21.04.1.

Is there a way to always have latest version and keep it automatically updated (PPA, flatpak, snap etc...)?

Thanks

I have little linux experience and am wondering if anyone can help me with this? I have a Realtek 8812AU / 8821AU USB wifi dongle and am needing the drivers for it so I don't have to be tethered to my router. I've tried using make, git clone, and DKMS to clone repos and build the drivers, and when I've gotten some to show up and be selected in Ubuntu's Software & Updates additional drivers panel, the adapter still never works (when it is in use a blue light flashes). How can I get it to work?

Here is some info:

typing lsusb:

Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 04d9:a096 Holtek Semiconductor, Inc. Keyboard
Bus 005 Device 002: ID 046d:c08b Logitech, Inc. G502 SE HERO Gaming Mouse
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:0811 Realtek Semiconductor Corp. Realtek 8812AU/8821AU 802.11ac WLAN Adapter [USB Wireless Dual-Band Adapter 2.4/5Ghz]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ifconfig:

enp9s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.111  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::c359:a278:e1b5:db83  prefixlen 64  scopeid 0x20<link>
        inet6 2605:a601:aa70:5500:6219:62f8:1dc0:d75d  prefixlen 64  scopeid 0x0<global>
        inet6 2605:a601:aa70:5500:a045:24ef:8c9d:5636  prefixlen 64  scopeid 0x0<global>
        ether a8:a1:59:35:e7:65  txqueuelen 1000  (Ethernet)
        RX packets 227570  bytes 297235969 (297.2 MB)
        RX errors 0  dropped 7  overruns 0  frame 0
        TX packets 111209  bytes 10197829 (10.1 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

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

I have accidentally hidden the toolbar in Dolphin. How can I get it back? I cannot find any option to restore it.

I apologize in advance as my Linux knowledge is very limited.I've installed Ubuntu 17.04 Server in a test environment and attempted to install Samba. During the installation the winbind daemon will not start. I've ran apt update && upgrade before installing Samba however it seems that it didn't help out. I've tested Ubuntu version 16.04 LTS and it works without any errors. I'm a bit lost as to why Winbind will not work on 17.04, Google search results didn't help. If anyone needs more info I'll gladly provide it but you'll probably need to show me the command to do it.

Thank you

Jun 14 10:53:18 UbtNicholas systemd[1]: Failed to start Samba Winbind Daemon.
-- Subject: Unit winbind.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit winbind.service has failed.
--
-- The result is failed.
Jun 14 10:53:18 UbtNicholas systemd[1]: winbind.service: Unit entered failed state.
Jun 14 10:53:18 UbtNicholas systemd[1]: winbind.service: Failed with result 'exit-code'.
Jun 14 10:53:30 UbtNicholas sudo[23772]: nilaberge : TTY=pts/0 ; PWD=/home/nilaberge ; USER=root ; COMMAND=/bin/su
Jun 14 10:53:30 UbtNicholas sudo[23772]: pam_unix(sudo:session): session opened for user root by nilaberge(uid=0)
Jun 14 10:53:30 UbtNicholas su[23773]: Successful su for root by root
Jun 14 10:53:30 UbtNicholas su[23773]: + /dev/pts/0 root:root
Jun 14 10:53:30 UbtNicholas su[23773]: pam_unix(su:session): session opened for user root by nilaberge(uid=0)
Jun 14 10:53:30 UbtNicholas su[23773]: pam_systemd(su:session): Cannot create session: Already running in a session
Jun 14 10:53:55 UbtNicholas systemd[1]: Starting Samba Winbind Daemon...
-- Subject: Unit winbind.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit winbind.service has begun starting up.
Jun 14 10:53:55 UbtNicholas systemd[1]: winbind.service: Supervising process 23803 which is not our child. We'll most likely not notice
Jun 14 10:53:55 UbtNicholas systemd[1]: winbind.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 10:53:55 UbtNicholas systemd[1]: Failed to start Samba Winbind Daemon.
-- Subject: Unit winbind.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit winbind.service has failed.
--
-- The result is failed.
Jun 14 10:53:55 UbtNicholas systemd[1]: winbind.service: Unit entered failed state.
Jun 14 10:53:55 UbtNicholas systemd[1]: winbind.service: Failed with result 'exit-code'.

There's almost a similar question but the question assumes that it worked on 17.04

Link to the similar question: Winbind Broken on Reboot In Ubuntu 17.04

UPDATE 1: After following andreas advice in running testparm, it found some lines that were old so I've removed them and restarted the winbind service. Still does an error but the systemCTL has found something that might pin point a bit better where the issue is.

Jun 26 10:14:29 UbtNicholas winbindd[1493]: [2017/06/26 10:14:29.432130,  0] ../source3/winbindd/winbindd_cache.c:3244(initialize_winbindd_cache)
Jun 26 10:14:29 UbtNicholas winbindd[1493]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Jun 26 10:14:29 UbtNicholas winbindd[1493]: [2017/06/26 10:14:29.435598,  0] ../source3/winbindd/winbindd_util.c:892(init_domain_list)
Jun 26 10:14:29 UbtNicholas winbindd[1493]:   Could not fetch our SID - did we join?
Jun 26 10:14:29 UbtNicholas winbindd[1493]: [2017/06/26 10:14:29.436118,  0] ../source3/winbindd/winbindd.c:1401(winbindd_register_handlers)
Jun 26 10:14:29 UbtNicholas winbindd[1493]:   unable to initialize domain list
Jun 26 10:14:29 UbtNicholas systemd[1]: winbind.service: Main process exited, code=exited, status=1/FAILURE
Jun 26 10:14:29 UbtNicholas systemd[1]: Failed to start Samba Winbind Daemon.
Jun 26 10:14:29 UbtNicholas systemd[1]: winbind.service: Unit entered failed state.
Jun 26 10:14:29 UbtNicholas systemd[1]: winbind.service: Failed with result 'exit-code'.

I was trying to install Realtek_RTS5229_Linux_Driver_v1.07 which I downloaded from [here][1]

When I run the make command I get the following error:-

make[1]: Leaving directory `/usr/src/linux-headers-3.13.0-32-generic'
make: *** [LINUX] Error 2

I have 64 bit Ubuntu 12.04 LTS installed.

For example in Xorg.0.log ...

[ 15708.908] (WW)

And in the log files it states

[ 15708.905] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.`

Is the first number the time?

Is there any literature on this subject? Or suggested ways to read through them and be able to make sense of them more fully?

I recently cloned my hard drive to a new one with an additional 250GB of space (232GiB per Gparted). This has left 232 GiB of unallocated space at the end of the drive that I would like to redistribute amongst the existing partitions. I would like to add some to sda1, some to sda2, etc.. I realize that one can only merge partition space when the unallocated space is adjacent, but can't figure out the best way to do this, given existing partitions are all primary... Can someone advise on this? BTW, since this is a cloned drive, the original is still intact, so I don't need to backup.