I am currently encountering an issue with my computer monitor link in Display-port.

My setup:

• Ubuntu 24.04.4 LTS (64-bit)
• NVIDIA 1080Ti
• First monitor plugged with HDMI (no issues, work just fine)
• Second monitor plugged with Display-port (detected, but not video signal). I can even move the mouse into the second monitor area.

erzatz@erzatz-All-Series:~$ xrandr
Screen 0: minimum 8 x 8, current 5120 x 1600, maximum 32767 x 32767
HDMI-0 connected primary 2560x1600+0+0 (normal left inverted right x axis y axis) 345mm x 215mm
   2560x1600     59.94*+
   2560x1080     59.94  
   1920x1080     59.94  
   1680x1050     59.95  
   1440x900      59.89  
   1360x765      60.00  
   1280x1024     60.02  
   1280x720      60.00    59.94  
   1152x648      60.00  
   1024x768      60.00  
   800x600       60.32  
   720x480       59.94  
   640x480       59.94  
DP-0 connected 2560x1440+2560+0 (normal left inverted right x axis y axis) 597mm x 336mm
   2560x1440     60.00*+ 144.00   120.00   100.00  
   1920x1080    119.88    60.00    59.94    50.00  
   1280x1024     75.02    60.02  
   1280x720      59.94    50.00  
   1024x768     119.99    99.97    75.03    70.07    60.00  
   800x600      119.97    99.66    75.00    72.19    60.32    56.25  
   720x576       50.00  
   720x480       59.94  
   640x480      119.52    99.77    75.00    72.81    59.94    59.93  
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)

erzatz@erzatz-All-Series:~$ ddcutil detect
Display 1
   I2C bus:  /dev/i2c-3
   DRM connector:           card1-HDMI-A-1
   EDID synopsis:
      Mfg id:               UGD - UNK
      Model:                MD160QH
      Product code:         5654  (0x1616)
      Serial number:        
      Binary serial number: 539166984 (0x20230908)
      Manufacture year:     2022,  Week: 37
   VCP version:         2.2

Display 2
   I2C bus:  /dev/i2c-4
   DRM connector:           card1-DP-1
   EDID synopsis:
      Mfg id:               AOC - UNK
      Model:                Q27B36X
      Product code:         9987  (0x2703)
      Serial number:        XI7RCHA015899
      Binary serial number: 15899 (0x00003e1b)
      Manufacture year:     2025,  Week: 51
   VCP version:         2.2

Results of ubuntu-drivers devices:

erzatz@erzatz-All-Series:~$ ubuntu-drivers devices
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
== /sys/devices/pci0000:00/0000:00:03.0/0000:01:00.0 ==
modalias : pci:v000010DEd00001B06sv00001043sd000085E2bc03sc00i00
vendor : NVIDIA Corporation
model : GP102 [GeForce GTX 1080 Ti]
driver : nvidia-driver-580-server - distro non-free
driver : nvidia-driver-470-server - distro non-free
driver : nvidia-driver-390 - third-party non-free
driver : nvidia-driver-565 - third-party non-free
driver : nvidia-driver-580 - distro non-free
driver : nvidia-driver-535 - distro non-free recommended
driver : nvidia-driver-535-server - distro non-free
driver : xserver-xorg-video-nouveau - distro free builtin

It was working fine before I tried to connect it through a KVM dock.
This one: https://www.avaccess.com/products/idock-b23/

Since then, my monitor is no longer showing any signal, but is well detected:
My screen showing the displays connected, we can see that both screen are connected

I've tried:

• Changed my cable.
• Changed the monitor.
• Unplugged and re-plug the monitor's power.
• Update my NVIDIA's drivers
• Visual check of the GPUs Display-port integrity (no apparent issues)

Does anyone have any idea how to fix this problem?

Ubuntu 26.04 LTS. Desktop PC.

My PC suffered a sudden power loss a few days ago and now goes through a prolonged process before it finally allows booting in to the OS.

The display seems to be indicating errors caused the power loss. I want to check it for errors, but I'm told I need to unmount it first.

How do I unmount the drive where the OS is located? Will my PC still operate?

This is a bit of what the displays shows:

New to the OS so excuse me if the solution is obvious. I have a Huion Tablet GT-156 model with official ubuntu compatible drivers installed, though for whatever reason my the device does not register pressure from the stylus on any software I've tested it on. It's puzzling because the only time I could get it to display strokes from the pen is on the Test Settings drop down in the ubuntu system settings tab; anywhere else the only thing that gets mapped is positioning of the stylus. Is it possible a system process is suppressing inputs?

Ubuntu 26.04 LTS Desktop

I have a Lenovo V15-ADA with Ubuntu 26.04 recently installed.

Upon closing the laptop, the screen locks as expected. When I reopen the laptop, the screen stays dark and I am forced to hard reset the computer.

This problem also occurs after the computer has been hibernating. Whether I move the mouse or press a key in attempt to turn the screen on, I get no response.

I have a Ubuntu server running in my home. Mostly for streaming movies and such but we just got a laptop for the kids and I was trying to set up samba so I can share files from my windows desktop to the laptop, but I'm running into a snag. When I attempt to connect to the share it asks me for my username and password but then I get a message that windows cannot access this network resource:

when I read log.aragorn (name of my desktop) I get

[2026/07/05 17:50:08.185990,  0] ../../source3/param/loadparm.c:3448(process_usershare_file)
  process_usershare_file: stat of /var/lib/samba/usershares/winshare failed. Permission denied

I have created a samba user and added it to the sambashare group.

permissions of my shared file are this:

drwxrwxr-x 2 neal neal 4096 Jul  5 17:34 winshare

my conf file is below (I removed all comments to make it easier to read.

#======================= Global Settings =======================

[global]

           hosts allow = 192.168.0.0/16
           hosts deny = 0.0.0.0/0
           server min protocol = SMB2

   workgroup = WORKGROUP

   server string = %h server (Samba, Ubuntu)

#### Networking ####


;   interfaces = 127.0.0.0/8 eth0

;   bind interfaces only = yes



#### Debugging/Accounting ####

   log file = /var/log/samba/log.%m

   max log size = 1000

   logging = file

   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

   server role = standalone server

   obey pam restrictions = yes

   unix password sync = yes

   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

   pam password change = yes

   map to guest = bad user

########## Domains ###########

;   logon path = \\%N\profiles\%U
;   logon drive = H:
;   logon script = logon.cmd

; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

;   include = /home/samba/etc/smb.conf.%m

;   idmap config * :              backend = tdb
;   idmap config * :              range   = 3000-7999
;   idmap config YOURDOMAINHERE : backend = tdb
;   idmap config YOURDOMAINHERE : range   = 100000-999999
;   template shell = /bin/bash

   usershare allow guests = yes

#======================= Share Definitions =======================

;[homes]
;   comment = Home Directories
;   browseable = no

;   read only = yes

;   create mask = 0700

;   directory mask = 0700

;   valid users = %S

;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
;   write list = root, @lpadmin
[winshare]
path = /srv/samba/winshare
guest ok = yes
browsable = yes
read only = no
writeable = yes
force user = username

I switched desktop environments and now that I switched back to the original, the desktop is not working properly. I have leftover apps from the other environment stuck on the screen. I kept typing different commands in and now I got a frozen Ubuntu screen and the other screen is stretched out.

My homelab VM collapsed, it was on for a few years, so I thought I give a try to the new version.

It is nice, looks good, fast enough, lot programs, just the basic things don't work. You click on SSH allowance, it is on, until you click somewhere else, turnes automaticly off. Remote desktop never worked, screen sharing ask for authentication every second minute... If I just try to setup the system it asks for authentication every minute. And I am in the same vlan! It is far from the old reliable system, I was getting annoyed very fast, probably I put back the old version, if no repair update will arrive.

for many years I'm user of Ubuntu (only LTS) - with the mozillateam ppa added for firefox / thunderbird ESR usage; all running fine.

I would like to know:
--> Who knows a roadmap / timetable etc. of mozillateam relating to older versions of Ubuntu (desktop) ?
In other words:
--> How long does mozillateam make backports of older versions of firefox & thunderbird ESR for older versions of Ubuntu LTS ?

I'm family - cognation - neighbour & friends admin, ca. 20 PCs. All PCs on Ubuntu 24.04 LTS with mozillateam ppa from the start (installation), only FF/TB ESR versions installed - no "standard".
...but there are 2 or 3 PCs still running Ubuntu 20.04 LTS. And the owners won't change because "it is running fine - don't change ! ...". Auto update is still running: OS & software, and FF/TB are regularly updated (to 140ESR by now) - the only ones (& for longer).

No major security concerns: low internet usage - some surfing and emails. But thunderbird will be a problem: migration (of the mailboxes) to a new system is ugly when there are different versions running of old and new TB. Therefore I do need roadmaps of Ubuntu (and mozillateam) and Mozilla software.

Ubuntu 20.04 EOL was in 05/2025, and I know the Ubuntu release cycles too - as well as some of mozillas release hints.
mozillateam is the black box here. And I could not find any roadmap or similar on the web relating to old Ubuntu OS versions. Just relating to FF & TB (security updates until 1 year after release of successor...) - but no roadmap to the underlying OS versions.
Btw: Ubuntu Wiki (mozillateam) link is completely outdated; there are no valid contacts of mozillateam.

Thanks for any help
(and plz: no 'helpful' tips for customer communication / convince...) ;-)

I need some expert advice regarding Ubuntu and NTFS external/internal hard drives. Here is the full story of what happened:

The Setup & Version: I am using Ubuntu 26.04 LTS. I have an SSD and a separate Hard Drive full of important data. To keep my data safe, I disconnected the hard drive completely while installing Ubuntu on my SSD. After a successful installation, I reconnected the hard drive.

The First Issue: Once Ubuntu booted, it completely refused to mount my hard drive partitions. When I click on the partition in the file manager, a popup appears saying 'Error mounting... cannot mount'. After searching online and doing some manual tweaks using the Ubuntu 'Disks' app and the Terminal, I finally got the partitions to show up and open.

The Power Cut / Outage Issue: Shortly after fixing it, we had a sudden power outage, and the computer shut down abruptly. When the power came back and I booted into Ubuntu, the partitions were completely locked again. The same error popup came back, and I had to repeat the same tedious manual troubleshooting fixes via the Disks app and Terminal all over again.

The AI Advice: I asked an AI assistant for a permanent fix, and it suggested that I should format my NTFS partitions to ext4 because Linux handles its native format much better during power cuts. However, I have over 260GB of important data on this hard drive, so formatting is absolutely not an option for me right now.

Right now, I have temporarily moved back to Windows 10 because going through this manual process every single day after a power cut is very frustrating, but I really want to use Ubuntu as my main OS.

I get this pop up

I have a Dell Latitude 3590 with Mesa Intel UHD Graphics 620 with VGA output.

The VGA is connected to a ViewSonic VA2446 External monitor.

   Built-in screen set to 1920×1080 (16:9)
   VA2446 is set to 1920×1080 (16:9)
   OS is Ubuntu Studio 24.04

The issue is the screen is too large for the displays, so the desktop will move to the edge (slide might be a better term) up and down, left or right. Even when the external is disconnected the Dell still does the same thing.

What am I missing here?

I tried to run it from the terminal and received the following message.

steam-runtime-check-requirements[55261]:  
W: Child process exited with code 1: bwrap:  
Can't open /proc/self/mountinfo: Permission denied  

I am using Ubuntu 26.04 with the default GNOME desktop.

I want to change the font and font size in the Terminal, but I cannot find the Preferences option. Most tutorials say to open Terminal and go to Preferences, but that option does not exist in my installation.

I tried:

• Checking the Terminal menu (top-right/hamburger menu).
• Right-clicking inside the Terminal window.
• Looking through the application settings.

None of these show a Preferences option.

Questions:

1. Has the Terminal application changed in Ubuntu 26.04?
2. How can I change the Terminal font and font size?
3. If the Preferences menu was removed, what is the new way to configure the Terminal?

If needed, I can provide screenshots of the Terminal window and menu.

I am new to Ubuntu and have just installed it on my laptop. My first move is to install yWriter to port some of my projects. On the install page for Linux the instructions are to change your terminal location to a newly created folder containing yWriter, however I have only just opened a terminal window for the first time today and have no idea how to change it's present working directory.

edit: here is the guide on the yWriter website. https://www.spacejock.com/yWriter7_Linux.html as you can see, after the initial terminal commands the instructions are to "change your location to that folder", which is a bit too vague for a total noob like me. I tried a couple of cd commands but they all ended with location not found, and I didn't want to mess around too much for fear of doing something I couldn't undo. And I have winetricks installed and was able to copy and paste the first lines just fine

So, what I did was run a command:

'> sudo apt modernize-sources`

The following files need modernizing:
  - /etc/apt/sources.list
  - /etc/apt/sources.list.d/mariadb.list
  - /etc/apt/sources.list.d/packages.cloudpanel.io.list

Modernizing will replace .list files with the new .sources format,
add Signed-By values where they can be determined automatically,
and save the old files into .list.bak files.

This command supports the 'signed-by' and 'trusted' options. If you
have specified other options inside [] brackets, please transfer them
manually to the output files; see sources.list(5) for a mapping.

For a simulation, respond N in the following prompt.
Rewrite 3 sources? [Y/n] y
Modernizing /etc/apt/sources.list...

Modernizing /etc/apt/sources.list.d/mariadb.list...
- Writing /etc/apt/sources.list.d/mariadb.sources

Modernizing /etc/apt/sources.list.d/packages.cloudpanel.io.list...
- Writing /etc/apt/sources.list.d/packages.cloudpanel.io.sources
Warning: Could not determine Signed-By for URIs: https://d17k9fuiwb52nc.cloudfront.net/, Suites: resolute

So, I got the error at the very end.

'> Warning: Could not determine Signed-By for URIs: https://d17k9fuiwb52nc.cloudfront.net/, Suites: resolute`

Whenever I run the command to update the packages sudo apt update -y I get the following error:

'> Notice: Missing Signed-By in the sources.list(5) entry for 'https://d17k9fuiwb52nc.cloudfront.net'

When I use the command

'> cat /etc/apt/sources.list.d/ubuntu.sources'

I get the following:

'> \## Note, this file is written by cloud-init on first boot of an instance  
> \## modifications made here will not survive a re-bundle.  
> \##  
> \## If you wish to make changes you can:  
> \## a.) add 'apt_preserve_sources_list: true' to /etc/cloud/cloud.cfg  
> \##     or do the same in user-data  
> \## b.) add supplemental sources in /etc/apt/sources.list.d  
> \## c.) make changes to template file  
> \##      /etc/cloud/templates/sources.list.ubuntu.deb822.tmpl  
> \##  
>   
> \# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to  
> \# newer versions of the distribution.  
>   
> \## Ubuntu distribution repository  
> \##  
> \## The following settings can be adjusted to configure which packages to use from Ubuntu.  
> \## Mirror your choices (except for URIs and Suites) in the security section below to  
> \## ensure timely security updates.  
> \##  
> \## Types: Append deb-src to enable the fetching of source package.  
> \## URIs: A URL to the repository (you may add multiple URLs)  
> \## Suites: The following additional suites can be configured  
> \##   \<name\>-updates   - Major bug fix updates produced after the final release of the  
> \##                      distribution.  
> \##   \<name\>-backports - software from this repository may not have been tested as  
> \##                      extensively as that contained in the main release, although it includes  
> \##                      newer versions of some applications which may provide useful features.  
> \##                      Also, please note that software in backports WILL NOT receive any review  
> \##                      or updates from the Ubuntu security team.  
> \## Components: Aside from main, the following components can be added to the list  
> \##   restricted  - Software that may not be under a free license, or protected by patents.  
> \##   universe    - Community maintained packages. Software in this repository receives maintenance  
> \##                 from volunteers in the Ubuntu community, or a 10 year security maintenance  
> \##                 commitment from Canonical when an Ubuntu Pro subscription is attached.  
> \##   multiverse  - Community maintained of restricted. Software from this repository is  
> \##                 ENTIRELY UNSUPPORTED by the Ubuntu team, and may not be under a free  
> \##                 licence. Please satisfy yourself as to your rights to use the software.  
> \##                 Also, please note that software in multiverse WILL NOT receive any  
> \##                 review or updates from the Ubuntu security team.  
> \##  
> \## See the sources.list(5) manual page for further settings.  
> Types: deb  
> URIs: https://mirror.hetzner.com/ubuntu/packages  
> Suites: resolute resolute-updates resolute-backports  
> Components: main universe restricted multiverse  
> Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg  
>   
> \## Ubuntu security updates. Aside from URIs and Suites,  
> \## this should mirror your choices in the previous section.  
> Types: deb  
> URIs: https://mirror.hetzner.com/ubuntu/security  
> Suites: resolute-security  
> Components: main universe restricted multiverse  
> Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg'

How to fix this error while updating packages?

I'm running Ubuntu 22.04 on one of my laptops and suddenly DNS doesn't work. It works on all of the other machines on my network. Addressing nodes on my network by IP works. Pinging google or its nameservers gets no response. Resolv.conf looks fine, resolvd is running. Any ideas?

Here's the output from systemctl status systemd-resolved.service

e - Network Name Resolution
     Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2026-07-02 08:52:54 PDT; 1h 33min ago
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
             https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
   Main PID: 836 (systemd-resolve)
     Status: "Processing requests..."
      Tasks: 1 (limit: 9192)
     Memory: 7.7M
        CPU: 241ms
     CGroup: /system.slice/systemd-resolved.service
             ??836 /lib/systemd/systemd-resolved

Jul 02 08:52:54 system76-pc systemd[1]: Starting Network Name Resolution...
Jul 02 08:52:54 system76-pc systemd-resolved[836]: Positive Trust Anchors:
Jul 02 08:52:54 system76-pc systemd-resolved[836]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Jul 02 08:52:54 system76-pc systemd-resolved[836]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.17>
Jul 02 08:52:54 system76-pc systemd-resolved[836]: Using system hostname 'system76-pc'.
Jul 02 08:52:54 system76-pc systemd[1]: Started Network Name Resolution.
Jul 02 08:52:58 system76-pc systemd-resolved[836]: wlp0s20f3: Bus client set default route setting: yes
Jul 02 08:52:58 system76-pc systemd-resolved[836]: wlp0s20f3: Bus client set DNS server list to: 8.8.8.8, 8.8.4.4, 1.1.1.1, 192.168.0.1
lines 1-23/23 (END)

I don't see anything amiss.

I have RAID6 disks running well on a old server running Ubuntu 12 with an old mdadm v3.2.5. That RAID is built directly on the disk, not into a partition.

I moved my 5 disks to my new server, with fresh install of Ubuntu 26.

When I boot my new server, the RAID is not created, and a partition is created on the 5 disks! I can not understand how Ubuntu can write to the disks without asking!

If a bring back the disk to my old server, it will not be created, but I can recreate it with the command

mdadm --create /dev/md125 --assume-clean --level=6 --raid-devices=5 /dev/sde /dev/sdd /dev/sdf /dev/sdc /dev/sdb

How can I prevent my new Ubuntu 26 from creating a partition on the 5 RAID disks. I just want UBUNTU to do nothing with them during boot. Than I could use mdadm to assemble, or create the RAID6.

I have played with grub to set to skip option to fsck, and it did not solve my problem. Something else is creating those partitions.

Here is what is created on my 5 RAID6 disks by something

sdb                         8:16   0   2.7T  0 disk
└─sdb1                      8:17   0    16M  0 part
sdc                         8:32   0   2.7T  0 disk
└─sdc1                      8:33   0    16M  0 part
sdd                         8:48   0   2.7T  0 disk
└─sdd1                      8:49   0    16M  0 part
sde                         8:64   0   2.7T  0 disk
└─sde1                      8:65   0    16M  0 part
sdf                         8:80   0   2.7T  0 disk
└─sdf1                      8:81   0    16M  0 part

I am having a HP laptop with AMD ryzen 3 3250u processor and I installed ubuntu 26 LTS and I tried to add a hibernation device in the laptop using a swap file but what I am experiencing is that when I run the command sudo systemctl hibernate my screen goes blank for sometime and return back to the lockscreen, sometime it work for the first time and subsequent hibernate fails, I am pasting my configuration files

/etc/fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p8 during curtin installation
/dev/disk/by-uuid/15cf6fe2-efa4-47b6-9adc-bb279ca2ef48 / ext4 defaults 0 1
# /boot/efi was on /dev/nvme0n1p1 during curtin installation
/dev/disk/by-uuid/D6BC-8F6E /boot/efi vfat defaults 0 1
/swapfile none swap sw 0 0

/etc/default/grub

# If you change this file or any /etc/default/grub.d/*.cfg file,
# run 'update-grub' afterwards to update /boot/grub/grub.cfg.
# For full documentation of the options in these files, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`( . /etc/os-release && echo ${NAME} )`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash resume=UUID=15cf6fe2-efa4-47b6-9adc-bb279ca2ef48 resume_offset=169984"
GRUB_CMDLINE_LINUX=""

# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
#GRUB_DISABLE_OS_PROBER=false

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE/GOP/UGA
# you can see them in real GRUB with the command `videoinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

/etc/initramfs-tools/conf.d/resume

RESUME=UUID=15cf6fe2-efa4-47b6-9adc-bb279ca2ef48 resume_offset=169984

findmnt -no UUID -T /swapfile
15cf6fe2-efa4-47b6-9adc-bb279ca2ef48

sudo filefrag -v /swapfile | awk '$1=="0:" {print substr($4,1,length($4)-2)}'
169984

here is the result for the kernel command

journalctl --since today -p emerg..err
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20251212>
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:44:22 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:44:22 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:44:25 Zenbook systemd[1]: Failed to activate swap swapfile.swap - /swapfile.
Jun 22 17:44:26 Zenbook kernel: ACPI Error: No handler for Region [RCM0] (000000002bbd688e) [S>
Jun 22 17:44:26 Zenbook kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20251212/>
Jun 22 17:44:26 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.ESDT due to previous err>
Jun 22 17:44:26 Zenbook kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to pre>
Jun 22 17:44:28 Zenbook systemd[1]: Failed to activate swap swapfile.swap - /swapfile.
Jun 22 17:44:29 Zenbook systemd[1]: Failed to activate swap swapfile.swap - /swapfile.
Jun 22 17:44:35 Zenbook kernel: 
Jun 22 17:44:35 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 17:44:35 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBC due to previous err>
Jun 22 17:44:35 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 17:44:35 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBE due to previous err>
Jun 22 17:44:41 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:41 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:42 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:42 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:42 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:42 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:43 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:44 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:45 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:46 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:46 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:46 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:47 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:47 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:47 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:47 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:49 Zenbook gdm-password][2992]: gkr-pam: unable to locate daemon control file
Jun 22 17:44:53 Zenbook systemd[3231]: Failed to start app-gnome-snap\x2duserd\x2dautostart-37>
Jun 22 17:44:56 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:56 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:57 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:44:58 Zenbook systemd[3231]: Failed to start snap.prompting-client.daemon.service - >
Jun 22 17:45:00 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:00 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:10 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:11 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:27 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:45:27 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:48:00 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:48:01 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:48:49 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:48:49 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:24 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:49:40 Zenbook gdm3[1640]: Gdm: Failed to list cached users: GDBus.Error:org.freedesk>
-- Boot 6222b8fdb133452c9a58e6ee5f5c0f39 --
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20251212>
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:50:01 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 17:50:01 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 17:50:01 Zenbook kernel: Failed to create device parport0
Jun 22 17:50:05 Zenbook kernel: ACPI Error: No handler for Region [RCM0] (00000000d3275a16) [S>
Jun 22 17:50:05 Zenbook kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20251212/>
Jun 22 17:50:05 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.ESDT due to previous err>
Jun 22 17:50:05 Zenbook kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to pre>
Jun 22 17:50:14 Zenbook kernel: 
Jun 22 17:50:14 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 17:50:14 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBC due to previous err>
Jun 22 17:50:14 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 17:50:14 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBE due to previous err>
Jun 22 17:50:20 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:20 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:21 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:22 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:22 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:24 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:24 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:25 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:45 Zenbook gdm-password][3131]: gkr-pam: unable to locate daemon control file
Jun 22 17:50:51 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:51 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:52 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:52 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:54 Zenbook systemd[3204]: Failed to start snap.prompting-client.daemon.service - >
Jun 22 17:50:56 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:50:56 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:15 Zenbook systemd-sleep[5143]: Failed to put system to sleep. System resumed aga>
Jun 22 17:51:15 Zenbook kernel: PM: hibernation: Image allocation is 79836 pages short
Jun 22 17:51:15 Zenbook systemd[1]: Failed to start systemd-hibernate.service - System Hiberna>
Jun 22 17:51:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:34 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:35 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 17:51:51 Zenbook chronyd[1427]: Could not connect to [2620:2d:4002:1::3123]:4460 (4.ntp>
Jun 22 17:51:52 Zenbook chronyd[1427]: Could not connect to [2620:2d:4000:1::2123]:4460 (1.ntp>
Jun 22 12:28:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 12:28:26 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 12:28:31 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 12:28:32 Zenbook kernel: NVRM: No NVIDIA GPU found.
Jun 22 12:43:13 Zenbook systemd-sleep[9679]: Failed to put system to sleep. System resumed aga>
Jun 22 12:43:13 Zenbook kernel: PM: hibernation: Image allocation is 116000 pages short
Jun 22 12:43:13 Zenbook systemd[1]: Failed to start systemd-hibernate.service - System Hiberna>
-- Boot f38d6bb7801c425387f1a8e9dbed4398 --
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20251212>
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 12:55:39 Zenbook kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.WLBU._ST>
Jun 22 12:55:39 Zenbook kernel: ACPI Error: Aborting method \_SB.WLBU._STA due to previous err>
Jun 22 12:55:43 Zenbook kernel: ACPI Error: No handler for Region [RCM0] (000000003573ea84) [S>
Jun 22 12:55:43 Zenbook kernel: ACPI Error: Region SystemCMOS (ID=5) has no handler (20251212/>
Jun 22 12:55:43 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.ESDT due to previous err>
Jun 22 12:55:43 Zenbook kernel: ACPI Error: Aborting method \_SB.PCI0.LPC0.EC0._Q42 due to pre>
Jun 22 12:55:51 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 12:55:51 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBC due to previous err>
Jun 22 12:55:51 Zenbook kernel: ACPI BIOS Error (bug): Attempt to CreateField of length zero (>
Jun 22 12:55:51 Zenbook kernel: ACPI Error: Aborting method \_SB.WMID.WQBE due to previous err>
Jun 22 12:56:00 Zenbook chronyd[1458]: Could not connect to [2620:2d:4002:1::3123]:4460 (4.ntp>
Jun 22 12:57:43 Zenbook gdm-password][3020]: gkr-pam: unable to locate daemon control file
Jun 22 12:57:51 Zenbook systemd[3095]: Failed to start snap.prompting-client.daemon.service - >
Jun 22 12:58:16 Zenbook kernel: PM: hibernation: Image allocation is 83357 pages short
Jun 22 12:58:16 Zenbook systemd-sleep[4989]: Failed to put system to sleep. System resumed aga>
Jun 22 12:58:17 Zenbook systemd[1]: Failed to start systemd-hibernate.service - System Hiberna>

free
               total        used        free      shared  buff/cache   available
Mem:         5479732     3315900      944936      138456     1614868     2163832
Swap:       16777212       42820    16734392

sudo swapon --show
NAME      TYPE SIZE   USED PRIO
/swapfile file  16G 925.1M   -1

ls -lha /dev/disk/by-uuid
total 0
drwxr-xr-x  2 root root 160 Jun 28 22:19 .
drwxr-xr-x 12 root root 240 Jun 28 22:19 ..
lrwxrwxrwx  1 root root  10 Jun 28 22:19 15cf6fe2-efa4-47b6-9adc-bb279ca2ef48 -> ../../sda4
lrwxrwxrwx  1 root root  10 Jun 28 22:19 28D6-4C0F -> ../../sda3
lrwxrwxrwx  1 root root  15 Jun 28 22:19 4E4A61734A61592B -> ../../nvme0n1p2
lrwxrwxrwx  1 root root  10 Jun 28 22:19 8E5A33945A337853 -> ../../sda2
lrwxrwxrwx  1 root root  15 Jun 28 22:19 C260-A33D -> ../../nvme0n1p1
lrwxrwxrwx  1 root root  10 Jun 28 22:19 b8cfc018-6aa3-407c-bae8-4c7f643c146d -> ../../sda5

df
Filesystem     1K-blocks     Used Available Use% Mounted on
tmpfs            1200800     5032   1195768   1% /run
/dev/sda4       54822144 34869628  17135236  68% /
tmpfs            3002000    39544   2962456   2% /dev/shm
efivarfs             160       87        69  56% /sys/firmware/efi/efivars
none                1024        0      1024   0% /run/credentials/systemd-journald.service
none                1024        0      1024   0% /run/credentials/systemd-resolved.service
tmpfs            3002000      348   3001652   1% /tmp
/dev/sda3        1046508     6452   1040056   1% /boot/efi
tmpfs             600400      100    600300   1% /run/user/1000

sudo blkid
/dev/nvme0n1p1: UUID="C260-A33D" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="ae7b16d0-eb14-47e7-9a6c-4b9e75b0af67"
/dev/nvme0n1p2: BLOCK_SIZE="512" UUID="4E4A61734A61592B" TYPE="ntfs" PARTUUID="f6b6807e-f516-4383-a17b-600f9967e2f9"
/dev/sda2: LABEL="Directory" BLOCK_SIZE="512" UUID="8E5A33945A337853" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="59c46e43-2a47-437e-9b29-917a7baebede"
/dev/sda3: LABEL_FATBOOT="BOOT" LABEL="BOOT" UUID="28D6-4C0F" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="BOOT" PARTUUID="588b1594-4bd0-44f9-922d-0f5b0ca8a030"
/dev/sda4: LABEL="ROOT" UUID="15cf6fe2-efa4-47b6-9adc-bb279ca2ef48" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="ROOT" PARTUUID="ae5cab5c-3514-494c-99f8-7acbb7710d44"
/dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop17: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop8: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop15: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop6: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop13: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop4: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop11: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop2: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop9: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop16: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop7: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop14: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop5: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop12: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop3: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop10: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/sda1: PARTLABEL="Microsoft reserved partition" PARTUUID="236f1e99-7832-4089-9411-4dfdbeb10e8b"

I am trying to install Ubuntu onto an older Dell laptop using a freshly flashed and validated SanDisk USB 3.0 drive (flashed via balenaEtcher).

The boot sequence starts up fine, but it completely freezes every single time right after reading the very last APT cache repository line: Get:5 file:/cdrom resolute/main amd64 Packages [31.7 kB]

I tried:

• Replaced the USB drive entirely (originally used a generic UDisk which threw I/O buffer errors, switched to a brand new SanDisk 16GB).

• Removed quiet splash from the GRUB menu to view the verbose terminal logs.

• Tried booting with nomodeset (Safe Graphics mode).

• Tried appending various combinations of boot flags like acpi=off, noapic, and irqpoll.

The logs:

Right before it hits the Get:5 line and hangs, the logs show a couple of errors regarding the communication bus and filesystem:

fuse: device /dev/fuse not found. Kernel module not loaded?
dbus-daemon: A connection to the bus can't be made
Failed to create stream fd: No such file or directory

This is the terminal output right at the freezing point. Since it is stalling the exact millisecond it finishes loading the configuration files and tries to hand over control to the display manager/graphics, I suspect it's a legacy hardware or kernel conflict with this specific Dell motherboard architecture.

Begin: Creating debconf-communicate fifo mechanism ... [    6.216597] evm: overlay not supported
done.
Begin: Running /scripts/casper-bottom ... Begin: Moving mount points... ... done.
Begin: Configuring fstab... ... done.
Begin: Setting up swap... ... done.
Begin: Setting up locales... ... done.
Begin: Setting up automatic login... ... done.
Begin: Setting hostname... ... done.
Begin: Setting up console keyboard... ... done.
Begin: Applying desktop settings... ... done.
Begin: Regenerating SSL certificate... ... hostname: Name or service not known
make-ssl-cert: Could not get FQDN, using '(none)'.
make-ssl-cert: You may want to fix your /etc/hosts and/or DNS setup and run
make-ssl-cert: 'make-ssl-cert generate-default-snakeoil --force-overwrite'
make-ssl-cert: again.
done.
Begin: Loading preseed file... ... done.
Begin: Adding live session user... ... passwd: password changed.
Failed to create stream fd: No such file or directory
Failed to create stream fd: No such file or directory
Failed to create stream fd: No such file or directory
dbus-daemon[723]: [session uid=1000 pid=18446744073709551615 pidfd=5] Activating service name='org.gtk.vfs.Daemon' re
dbus-daemon[723]: [session uid=1000 pid=18446744073709551615 pidfd=5] Successfully activated service 'org.gtk.vfs.Daemon'
dbus-daemon[723]: [session uid=1000 pid=18446744073709551615 pidfd=5] Activating service name='org.gtk.vfs.Metadata' re
fuse: device /dev/fuse not found. Kernel module not loaded?
dbus-daemon[723]: [session uid=1000 pid=18446744073709551615 pidfd=5] Successfully activated service 'org.gtk.vfs.Meta
A connection to the bus can't be made
done.
Begin: Setting up init... ... done.
Begin: Configuring accessibility options... ... done.
Begin: Disabling update-notifier... ... done.
Begin: Enabling detection of crashes... ... done.
Begin: Disabling unnecessary KDE services... ... done.
Begin: Disabling the lock screen for LXQt (LP: #2000787)... ... done.
Begin: Generating APT cache for cdrom... ... Ign:1 file:/cdrom resolute InRelease
Get:2 file:/cdrom resolute Release [664 B]
Get:2 file:/cdrom resolute Release [664 B]
Get:3 file:/cdrom resolute Release.gpg [228 B]
Get:3 file:/cdrom resolute Release.gpg [228 B]
Get:4 file:/cdrom resolute/restricted amd64 Packages [14.5 kB]
Get:5 file:/cdrom resolute/main amd64 Packages [31.7 kB]

Do you have any advice on what specific kernel boot parameters or BIOS tweaks I need to use to force it past this graphical handshake?

I've been reading the forums and found quite a few people with a similar issue, but none of the solutions worked for me.

My internal microphone is not working on Ubuntu. It works fine on Windows (dual boot), so it's definitely a software/driver issue.

System info:

• Computer: ASUS VivoBook X515EA
• Ubuntu: 25.10 (Questing)
• Audio chip: Realtek ALC256 (Intel Tiger Lake-LP Smart Sound)
• Audio server: PipeWire 1.4.7

What I've tried:

• Setting options snd-hda-intel model=asus-zenbook in /etc/modprobe.d/
• Adjusting capture levels in alsamixer (F4 view, HDA Intel PCH card)
• Setting the default source with pactl set-default-source
• Reinstalling PipeWire and resetting WirePlumber config
• Running amixer -c 0 cset numid=6 2 to select Internal Mic 1 (node 0x1b)

What I found:

• arecord -D hw:0,0 with Internal Mic 1 selected (numid=6 set to 2) does show vumeter activity so ALSA can capture audio at the hardware level
• However, PipeWire does not seem to pass the audio through, parecord and pw-record both record silence
• The dmesg shows the driver picks up two internal mic nodes: Internal Mic=0x12 and Internal Mic=0x1b
• Capture Switch (numid=8) needs to be set on,on manually after every reboot

arecord -l output:

List of CAPTURE Hardware Devices  
card 0: PCH \[HDA Intel PCH\], device 0: ALC256 Analog \[ALC256 Analog\]  
  Subdevices: 1/1  
  Subdevice #0: subdevice #0  

It seems like ALSA captures audio correctly when configured manually, but PipeWire/WirePlumber doesn't route it properly to applications. Any ideas on what could be causing this or how to fix it?

I am on a dual-boot (Ubuntu 24.04.03 LTS - Windows 10) configuration, and noticed that my second monitor stopped being detected via HDMI when on Ubuntu. Prior to my 24.04 upgrade (I was using 22.04), everything worked fine.

My setup is the following:

[HP E243i monitor's HDMI port]->[HDMI cable]->[laptop's HDMI port]

On Windows, it works fine. On Ubuntu, nothing is detected (the screen blinks when connecting to the computer, then goes back to sleep).

Running xrandr -q --verbose | rg -i HDMI outputs

HDMI-1 disconnected (normal left inverted right x axis y axis)

After trying X vs Wayland, upgrading the NVIDIA drivers to 535, 550 or 580 (recommended), nothing worked. Then, I tried to use an HDMI to USB-C adapter I have... and it worked!

[HP E243i monitor's HDMI port]->[HDMI cable]->[HMDI to USB-C adapter]->[laptop's USB-C port]

However, that's not really ideal for me and I'd like not to have to use the adapter.

Finally, it's probably worth mentioning that using the same HDMI cable, but with my TV, the following works...

[TV's HDMI port]->[HDMI cable]->[laptop's HDMI port]

Changing the HDMI cable doesn't seem to have any impact.

Does anyone have an idea of how to fix this?

Thanks in advance!

System info:

Linux jeertmans 6.14.0-35-generic #35~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Oct 14 13:55:17 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
    Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics]
    Kernel driver in use: i915
    Kernel modules: i915, xe
--
01:00.0 3D controller: NVIDIA Corporation TU117GLM [Quadro T500 Mobile] (rev a1)
    Subsystem: Lenovo TU117GLM [Quadro T500 Mobile]
    Kernel driver in use: nvidia
    Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia

I am facing a delay of 9 seconds between printing jobs. Printer is TSC TE310 label printer and OS is Ubuntu 24.04 LTS and connected throught USB. The 1st print comes instantly without any delay through the printer but job reamins processing for approx 9 seconds in printer queue. for 2nd jobs same repates.

I'm new to Ubuntu, used DOS when I was a kid. Able to install Label Range LP320 Thermal Label printer through the terminal. I got "Printing stopped" message using 24.04.

We have an unattended update setup. To make sure nothing slips, we check for pending security updates and trigger a warning if there is something available but not installed for a week.

Now we have a server with security updates not installed for a while because of the periodic package update failing without any indication of it. We would like to add a trigger to the monitoring to detect this, however, that seems not so simple.

apt update prints an error and has a non-zero exit status:

# apt update
. . . 
E: Some index files failed to download. They have been ignored, or old ones used instead.
# echo $?
100

However, the above did set the "success" stamp at:

# ls -l /var/lib/apt/periodic/update-success-stamp
-rw-r--r-- 1 root root 0 Oct 11 10:58 /var/lib/apt/periodic/update-success-stamp

Also, despite the error, the systemd service apt-daily.service is exiting with exit status 0.

How is it possible to detect that the daily package update is failing?

I am running Ubuntu 22.04

cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"

After updating my system a while ago, I noticed that multiple icons within the Desktop environment were replaced by compatibility mode icons (or at least very outdated ones) and red stop/prohibited symbols (see screenshots). These are all system icons meaning that also all system apps are affected (e.g. Terminal (+ symbol for multiple tabs), many parts of settings, the "Show apps" symbol in the taskbar, ...).

This guy seemed to have a similar problem, but his provided fix did not help in my case: Red icons in Ubuntu 22.04

I tried multiple suggestions by friends and colleagues and the internet, nothing worked or brought back the icons:

1. Update icon cache
2. Reinstall Ubuntu Desktop
3. Reinstall Gnome
4. Reinstall all packages using icons by searching the links that point to /usr/share/icons/

Does anyone have additional solutions I can try out? Missing these is especially frustrating in apps that heavily rely on their icons and when there is no additional description until being hovered.

If any questions arise, either due to missing details or my German language settings, I will happily clarify the question.

System Information:

• Ubuntu 22.04
• X11 Desktop
• Gnome
• No further customization

I have been trying to install the driver for my canon printer but I always get the error shown below. I also tried to convert the package from .rpm to .deb and try it to run it from there, but again it does not work.

jorge@jorge-VPCEH3N6E:~/Downloads/cnijfilter-mg2500series-4.00-1-rpm$ 
sudo bash install.sh
[sudo] password for jorge: 
==================================================

Canon Inkjet Printer Driver

Version 4.00
Copyright CANON INC. 2001-2013

All Rights Reserved.

==================================================
An error occurred. A necessary package could not be found in the proper location. 

Can someone let me know where can a get the file -deb?? Thanks

I am getting this error on service apache2 restart

Error: SSLCertificateFile: file '/etc/apache2/ssl/www_example_com.crt' does not exist or is empty

I am trying to configure comodo ssl certificate on ubuntu ec2 instance with LAMP and I have performed all official steps by following below links.

https://help.ubuntu.com/community/ApacheMySQLPHP

https://help.ubuntu.com/14.04/serverguide/httpd.html#https-configuration

Please help.

Startup error photos:

ata1.00: status: { DRDY ERR }
ata1.00: error: { ABRT }
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x5
ata1.00: failed command: READ DMA
ata1.00: cmd c8/00:20:00:c1:e7/00:00:00:00:00/ee tag 0 dma 16384 in
         res 51/04:20:00:c1:e7/00:00:00:00:00/ee Emask 0x1 (device error)

Any ideas?

I have an Ubuntu computer running 16.04, and I only have one graphics card.

My brother and I constantly fight over who gets to use it, so I'm trying to do everyone a favor and install multiseat.

• I would be seat0, with the VGA port, a mouse, a keyboard, and the headphone jacks on the back of the computer.

• He would be seat1, with the DVI-D port, a mouse, a keyboard, and the headphone jacks on the front of the computer.

• We would share the Wi-Fi dongle to connect to the internet.

I am completely at a loss on how to do this. What files do I create, where do they go, and what do I put in them? A well-formatted answer (not an online guide) would be nice.

The output of lspci:

00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation C220 Series Chipset Family H81 Express LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
01:00.0 PCI bridge: PLX Technology, Inc. PEX 8609 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch with DMA (rev ba)
01:00.1 System peripheral: PLX Technology, Inc. PEX 8609 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch with DMA (rev ba)
02:01.0 PCI bridge: PLX Technology, Inc. PEX 8609 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch with DMA (rev ba)
02:05.0 PCI bridge: PLX Technology, Inc. PEX 8609 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch with DMA (rev ba)
02:07.0 PCI bridge: PLX Technology, Inc. PEX 8609 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch with DMA (rev ba)
02:09.0 PCI bridge: PLX Technology, Inc. PEX 8609 8-lane, 8-Port PCI Express Gen 2 (5.0 GT/s) Switch with DMA (rev ba)
03:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
04:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
05:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
06:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
08:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

The output of ls /dev/input/by-path/:

pci-0000:00:14.0-usb-0:1:1.2-event-kbd
pci-0000:00:14.0-usb-0:2:1.0-event-kbd
pci-0000:00:14.0-usb-0:7:1.0-event-mouse
pci-0000:00:14.0-usb-0:1:1.2-event-mouse
pci-0000:00:14.0-usb-0:3.1:1.0-event-mouse
pci-0000:00:14.0-usb-0:7:1.0-mouse
pci-0000:00:14.0-usb-0:1:1.2-mouse
pci-0000:00:14.0-usb-0:3.1:1.0-mouse
platform-eeepc-wmi-event

When I launch gta_sa.exe the screen goes blank and comes back with the screen resolution messed up. The desktop is HUGE.

With the game also fully responsive I can only see the top right of the game.

I am using Ubuntu 14.04LTS, with an Intel CPU + integrated graphics, with a GTX650 GPU. I asked this question on SO but they said it was offtopic.

I want to use my GPU for debugging CUDA code and for that I need to change display to integrated only. This is the error I get when I try to debug it currently:

"All cuda devices are used for display and cannot be used while debugging"

I went into the BIOS and switched primary display to iGPU (the integrated one, HD4600). Nothing came out of the GPU ports anymore (in terms of display) and I plugged my monitors into the motherboard. Only one of the monitors works. Normally I have them like:

|[Monitor 1, VGA]| |[Monitor 2, DVI]|

In that configuration, with iGPU, nothing is displayed on Monitor 1 (it's black, but the computer knows it's there - the green light is on and all my windows open on it). The only way to get it to work is to swap Monitor 2 to VGA and Monitor 1 to DVI.

If I enter lspci | grep VGA into Terminal, I get this:

00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GTX 650] (rev a1)

Running xrandr gives me:

Screen 0: minimum 8 x 8, current 3360 x 1050, maximum 16384 x 16384
DVI-D-0 disconnected primary (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
VGA1 connected 1680x1050+0+0 474mm x 296mm
   1680x1050      60.0*+
   1600x1000      60.0 +
   1280x1024      75.0     72.0     60.0  
   1440x900       75.0     59.9  
   1152x864       75.0  
   1024x768       75.1     70.1     60.0  
   800x600        72.2     75.0     60.3  
   640x480        75.0     72.8     66.7     60.0  
   720x400        70.1  
DP1 disconnected
HDMI1 disconnected
HDMI2 connected 1680x1050+1680+0 474mm x 296mm
   1680x1050      60.0*+
   1600x1000      60.0 +
   1280x1024      75.0     72.0     60.0  
   1440x900       75.0     59.9  
   1152x864       75.0  
   1024x768       75.1     70.1     60.0  
   800x600        72.2     75.0     60.3  
   640x480        75.0     72.8     66.7     60.0  
   720x400        70.1  
HDMI3 disconnected
VIRTUAL1 disconnected

It isn't an HDMI connection, I don't know why it thinks it is. With the GPU, it knows it's DVI. Anyway...

This is the xorg.conf (if I change it, it just overwrites it):

Section "ServerLayout"
    Identifier "layout"
    Screen 0 "nvidia"
    Inactive "intel"
EndSection

Section "Device"
    Identifier "intel"
    Driver "intel"
    BusID "PCI:0@0:2:0"
    Option "AccelMethod" "SNA"
EndSection

Section "Screen"
    Identifier "intel"
    Device "intel"
EndSection

Section "Device"
    Identifier "nvidia"
    Driver "nvidia"
    BusID "PCI:1@0:0:0"
    Option "ConstrainCursor" "off"
EndSection

Section "Screen"
    Identifier "nvidia"
    Device "nvidia"
    Option "AllowEmptyInitialConfiguration" "on"
    Option "IgnoreDisplayDevices" "CRT"
EndSection

This is my 10-monitors.conf file in /usr/share/X11/xorg.conf.d/:

  GNU nano 2.2.6                                      File: /usr/share/X11/xorg.conf.d/10-monitors.conf                                                                                   

Section "Monitor"
    Identifier     "VGA1"
EndSection

Section "Monitor"
    Identifier     "HDMI2"
EndSection

Section "Device"
   Identifier      "intel0"
   Driver          "intel"
   BusID           "PCI:0@0:2:0"
EndSection

Section "Device"
   Identifier      "intel1"
   Driver          "intel"
   BusID           "PCI:0@0:2:0"
EndSection

Section "Screen"
   Identifier     "Screen0"
   Device         "intel0"
   Monitor        "VGA1"
   DefaultDepth   24
   SubSection     "Display"
      Depth       24
      Modes       "1680x1050" "1920x1080"
   EndSubSection
EndSection

Section "Screen"
   Identifier     "Screen1"
   Device         "intel1"
   Monitor        "HDMI2"
   DefaultDepth   24
   SubSection     "Display"
      Depth       24
      Modes       "1680x1050" "1920x1080"
   EndSubSection
EndSection

This still doesn't permit my CUDA code to be debugged. If I run lsof /dev/nvidia* I get:

COMMAND  PID     USER   FD   TYPE  DEVICE SIZE/OFF  NODE NAME
compiz  1659 cinnamon  mem    CHR 195,255          11805 /dev/nvidiactl
compiz  1659 cinnamon  mem    CHR   195,0          11806 /dev/nvidia0
compiz  1659 cinnamon   11u   CHR 195,255      0t0 11805 /dev/nvidiactl
compiz  1659 cinnamon   12u   CHR   195,0      0t0 11806 /dev/nvidia0
compiz  1659 cinnamon   13u   CHR   195,0      0t0 11806 /dev/nvidia0
compiz  1659 cinnamon   14u   CHR   195,0      0t0 11806 /dev/nvidia0

So I guess Compiz (X server?) is using it still. How do I stop it from using it?