The following error message occurred while downloading and installing Ubuntu in a Windows terminal.
Downloading: Ubuntu
Installing: Ubuntu
The system cannot find the file specified.
Error code: Wsl/InstallDistro/Service/RegisterDistro/CreateVm/HCS/
ERROR_FILE_NOT_FOUND
I am setting up an older machine with an Nvidia Quadro K1100M. After installing 26.04, one of the first things I confirmed was that I could connect multiple monitors, and sure enough, it worked out of the box with no issues.
Fast-forward to me doing a bunch of installation and configuration (i.e. running my clunky install script and taking a few manual steps), when I notice that I can no longer connect multiple monitors. Here's some relevant output:
> xrandr
Screen 0: minimum 16 x 16, current 1920 x 1080, maximum 32767 x 32767
None-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 508mm x 285mm
1920x1080 59.96*+
1440x1080 59.99
1400x1050 59.98
1280x1024 59.89
1280x960 59.94
1152x864 59.96
1024x768 59.92
800x600 59.86
640x480 59.38
320x240 59.29
1680x1050 59.95
1440x900 59.89
1280x800 59.81
1152x720 59.97
960x600 59.63
928x580 59.88
800x500 59.50
768x480 59.90
720x480 59.71
640x400 59.95
320x200 58.14
1600x900 59.95
1368x768 59.88
1280x720 59.86
1024x576 59.90
864x486 59.92
720x400 59.27
640x350 59.28
> sudo lshw -c video
*-display UNCLAIMED
description: VGA compatible controller
product: GK107GLM [Quadro K1100M]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list
configuration: latency=0
resources: memory:f4000000-f4ffffff memory:e0000000-efffffff memory:f0000000-f1ffffff ioport:e000(size=128) memory:f5000000-f507ffff
*-display
description: VGA compatible controller
product: 4th Gen Core Processor Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
logical name: /dev/fb0
version: 06
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list fb
configuration: depth=32 latency=0 mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080
resources: memory:f5400000-f57fffff memory:d0000000-dfffffff ioport:f000(size=64) memory:c0000-dffff
The xrandr output is when external monitor(s) are connected. Any configuration of how many monitors/which ports they connect to makes no difference. Unfortunately, I did not record this output after a fresh installation, so I don't have that for comparison.
So there's no driver installed for the GPU, and the OS doesn't see any displays that I connect to the machine. Can anyone shed any light on what might have changed? I really don't want to start over from a fresh installation, and even if I do, there's no guarantee I won't end right back here.
Some more details about drivers:
ubuntu-drivers list produces no output.
Nvidia recommends 418.113. but if I try to run the installer, it fails to build with a bunch of errors about missing header files, e.g. nv-misc.h. I had previously tried using the Additional Drivers dialog on a 24.10 installation to install I believe it was 390.x, but the result was the same.
The nvidia-legacy PPA doesn't appear to have 390 past mantic. When I was trying this on 24.10, I had pretty much concluded that I was going to need to downgrade to an earlier LTS to get it to work, until I tried 26.04 and it magically worked out of the box (until it magically didn't, hence this post).
Nouveau supports my GPU. My theory is that it claimed the GPU out of the box, which is why multiple monitors were briefly working, but then later dropped it for unknown reasons. Here is the output of lsmod | grep nouveau:
nouveau 3178496 0
gpu_sched 69632 1 nouveau
drm_gpuvm 57344 1 nouveau
mxm_wmi 12288 1 nouveau
drm_ttm_helper 20480 1 nouveau
drm_exec 12288 2 drm_gpuvm,nouveau
ttm 135168 2 drm_ttm_helper,nouveau
drm_display_helper 303104 1 nouveau
i2c_algo_bit 16384 1 nouveau
video 77824 3 dell_wmi,dell_laptop,nouveau
wmi 36864 8 video,dell_wmi,wmi_bmof,dell_smm_hwmon,dell_smbios,dell_wmi_descriptor,mxm_wmi,nouveau
My Lenovo Thinkpad x1 Carbon Gen 9, is connected to the Thinkpad docking station (https://support.lenovo.com/gb/en/solutions/PD500180) via USB-C. I've installed Synaptic repository and installed Displaylink driver, this is confirmed at the newest version.
I have 2 Full HD monitors connected to the docking station via HDMI cable and this set up works on a Windows 11 device used for work, an old HP Elitebook running Mint (I can't remember version of the top of my head).
I've gone through a lot of suggested fixes online, including:
The next thing I am trying is another wipe of the device + new Ubuntu 24.04 boot
I can also provide clearer information if needed.
I run a dual boot win11/ubuntu 24.04.4 on my pc at home because some software I use for work only works on Linux. The pc has two monitors. I left it running overnight so I could pick up my work where I left off and when I got back it told me I needed to restart for some problem (do not remember error code or anything) which is when I believe it moved to Linux kernel 6.17.0-35 and after this the mouse stopped working (wouldn’t move in response to input) and the NVIDIA drivers for my 4080 were wrong, locking the resolution to 1080x768 and failing to recognize the 2nd monitor. After updating the drivers to version 580, it recognizes both monitors and the correct resolution on Linux 0-35 but the mouse still didn’t work. Using lsusb also showed it detected the mouse was plugged in. The only previous kernel I have is 6.17.0-19-generic, where the mouse works but the drivers don’t. When I tried to install the drivers appropriate for 0-19 by changing the headers and autoinstalling the drivers they are still not correct after rebooting and selecting 0-19. Does anyone know the way to either get my mouse to work on 0-35(it also works correctly in win11 and BIOS) or the driver to work in 0-19?
Edit 1: I have also discovered there is no driver for my Ethernet adapter or wireless network controller via the command lspci -knn | grep Network -A3
On a machine running Linux Mint, trying to install AMD GPU drivers (I know, they come pre-installed, but tell that to my system. Still getting N/A for Driver in inxi -G), keep getting the same error even after kernel upgrade and apt update/full-update/upgrade/clean/etc. The error says 2.35-0ubuntu3.13 is "to be installed" despite a number of the packages already being installed. Went to force-install the libc6 it mentioned, found out I already had a newer version of it. Command was amdgpu-install --usecase=graphics,opencl.
The following packages have unmet dependencies:
amdgpu-lib : Depends: libdrm-amdgpu-amdgpu1 but it is not installable
amdgpu-multimedia : Depends: libva2 (>= 2.16.0) but 2.14.0-1 is to be installed or
libva2-amdgpu but it is not installable
Depends: libva-drm2 (>= 2.16.0) but 2.14.0-1 is to be installed or
libva-amdgpu-drm2 but it is not installable
Depends: libva-wayland2 (>= 2.16.0) but 2.14.0-1 is to be installed or
libva-amdgpu-wayland2 but it is not installable
Depends: libva-x11-2 (>= 2.16.0) but 2.14.0-1 is to be installed or
libva-amdgpu-x11-2 but it is not installable
Depends: libdrm-amdgpu-amdgpu1 but it is not installable
libdrm-amdgpu-amdgpu1:i386 : Depends: libc6:i386 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
libdrm2-amdgpu : Depends: libc6 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
libdrm2-amdgpu:i386 : Depends: libc6:i386 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
libegl1-amdgpu-mesa : Depends: libc6 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
Depends: libx11-xcb1 (>= 2:1.8.7) but 2:1.7.5-1ubuntu0.3 is to be installed
libegl1-amdgpu-mesa:i386 : Depends: libc6:i386 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
Depends: libx11-xcb1:i386 (>= 2:1.8.7) but 2:1.7.5-1ubuntu0.3 is to be installed
libgbm1-amdgpu : Depends: libc6 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
libgbm1-amdgpu:i386 : Depends: libc6:i386 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
libgl1-amdgpu-mesa-glx : Depends: libc6 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
Depends: libx11-xcb1 (>= 2:1.8.7) but 2:1.7.5-1ubuntu0.3 is to be installed
libgl1-amdgpu-mesa-glx:i386 : Depends: libc6:i386 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
Depends: libx11-xcb1:i386 (>= 2:1.8.7) but 2:1.7.5-1ubuntu0.3 is to be installed
libllvm20.1-amdgpu : Depends: libc6 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
libllvm20.1-amdgpu:i386 : Depends: libc6:i386 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
mesa-amdgpu-libgallium : Depends: libc6 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
Depends: libdrm-amdgpu-amdgpu1 but it is not installable
Depends: libelf1t64 (>= 0.142) but it is not installable
Depends: libx11-xcb1 (>= 2:1.8.7) but 2:1.7.5-1ubuntu0.3 is to be installed
Depends: libstdc++6 (>= 1.5.5) but 1.4.8+dfsg-3build1 is to be installed
mesa-amdgpu-libgallium:i386 : Depends: libc6:i386 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
Depends: libelf1t64:i386 (>= 0.142) but it is not installable
Depends: libx11-xcb1:i386 (>= 2:1.8.7) but 2:1.7.5-1ubuntu0.3 is to be installed
Depends: libstdc++6:i386 (>= 1.5.5) but 1.4.8+dfsg-3build1 is to be installed
mesa-amdgpu-vulkan-drivers : Depends: libc6 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
Depends: libdisplay-info1 (>= 0.1.1) but it is not installable
Depends: libdrm-amdgpu-amdgpu1 but it is not installable
Depends: libelf1t64 (>= 0.142) but it is not installable
Depends: libx11-xcb1 (>= 2:1.8.7) but 2:1.7.5-1ubuntu0.3 is to be installed
Depends: libstdc++6 (>= 1.5.5) but 1.4.8+dfsg-3build1 is to be installed
rocprofiler-register : Depends: libc6 (>= 2.38) but 2.35-0ubuntu3.13 is to be installed
E: Unable to correct problems, you have held broken packages.
I'm trying to connect to a legacy Samba server here on Ubuntu 26.04 using the command: sudo mount.cifs //192.168.0.3/emanoel /mnt cifs credentials=/home/emanoel/.smbcredentials,vers=1.0,iocharset=utf8,file_mode=0777,noperm,gid=1000,uid=1000 0 0
but I can't connect. I believe it's because of SMB 1.0, giving the following error:
mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0.mount error(112): Host is down. Refer to the mount.cifs(8) manual page (e.g., man mount.cifs) and kernel log messages (dmesg).
I added the fstab line, it passes without error, accessing it through Nautilus works without errors, but no files from the share appear.
Everything works as expected on Ubuntu 24.04.
I am trying to set up a VDI (Virtual Desktop Infrastructure) Server, but everything I try is ineffective because Wayland and KDE require me to click on a Share in the Remote Control requested prompt. This kind of defeats the whole purpose of VDI. My users will not have access to the physical machine. They don't have an iDRAC terminal to go into the VM and click the button. And selecting to save my selection doesnt actually save anything. The next time the user logs out everything is forgotten. This has been a problem now on Wayland based OSs for over 4 years. Is there ANY solution yet. If not I will need to go back to another DE.
I should add that the built-in RDP method does not suit my use case, and please don't recommend changing my workflow that is not actually a solution to the issue.
0
I don't really like this answer. It would be nice to have something more native, but installing the remote desktop application (eg. RustDesk) by Flatpak, then set this special permission: flatpak permission-set kde-authorized remote-desktop com.rustdesk.RustDesk yes.
Update: Doesn't actually work. I don't get a prompt anymore, but I also don't get an image. Now I understand why some IT teams just stick with Windows, this is kind of BS.
Update 2: Going back to Windows, no matter how much I save in licensing costs, I am losing them in technician hours. Sorry (K)ubuntu. If you can't run RustDesk as a Remote Desktop without issues, then you are not ready for prime time.
For about the past week, Google Chrome has been crashing frequently and has also become noticeably slower.
I have not changed my environment or Chrome settings recently. CPU and RAM usage seem to have plenty of headroom, and I do not have an unusually large number of tabs open. In fact, I used to keep more tabs open before without any issues.
There does not seem to be any clear pattern to when the problem occurs. Chrome may freeze or crash while scrolling, but it can also happen when I am not actively interacting with the browser.
I have already tried clearing the cache and browsing history, and I also changed settings such as Memory Saver, but none of these made a noticeable difference.
I could not find any obvious error messages or signs of system instability, so I would appreciate any advice on how to investigate or fix this issue.
I found a similar unresolved issue on Ask Ubuntu.
Environment:
OS: Ubuntu 24.04.4 LTS
Hardware: Micro-Star International Co., Ltd. MS-7E16
CPU: AMD Ryzen 9 7900X × 24
RAM: 128 GB
Chrome version: Version 149.0.7827.155 (Official Build) (64-bit)
I was unable to register on login.ubuntu.com. I initially received the email to verify my address, but a few seconds later I received another email stating that my account had been invalidated.
We have confirmed that there are no firewall restrictions or network blocks on our side. Is there another solution?
This app called Software Install, named gnome-software-local-file-flatpak (also sometimes shows up as just Software, named org.gnome.Software) autostarts at login and keeps running in the background.
It is different from App Center snap-store which comes preinstalled. I had to download Software Install from apt (probably came as gnome-software or something), and I used it to install flatpaks (also supports snaps after I turned that setting on) keeps running in the background
How do I stop Software Install / Software from running in the background? I'm using Ubuntu LTS 26.04 with GNOME 50.
NoDisplay=True from /etc/xdg/autostart/gnome-software-service.desktop because no such file exists.PS: This is one thing I dislike about Ubuntu. Things change so much and so quickly - there is no persistence in construction. Is distributed disorganization really a fundamental tenet of open source? On the contrary, I think Linux has been most successful in fields where developers have built things based on a unified scheme and purpose. Too many options isn't necessarily a good thing if it comes at the cost of being worried all the time about what's going wrong in your system.
I was actively using Bluetooth, but it suddenly disappeared from my system. I've tried searching for a solution using AI, but couldn't resolve the issue. What steps should I take to fix and restore my Bluetooth connection?
I know how very contradictory that statement is, but I wanted to try it again without having to reinstall everything since I moved to KDE Plasma. But when checking what'll happen when I trry installing it alongside KDE Plasma to ensure it won't break anything, I noticed that doing apt --simulate ubuntu-desktop is fine but apt --simulate gnome wants to remove the kubuntu-desktop and kubuntu-settings-desktop packages. Is that fair to be concerned that removing those packages will mess with KDE Plasma?
Is there some way to install GNOME with the stuff that is included on native Ubuntu without it messing with KDE Plasma so that if I decide I really am sure I don't like GNOME, I can just remove it and go back to KDE Plasma like nothing happened? Also out of curiosity sake, what is the difference between ubuntu-desktop and gnome packages?
BCM4322 (14e4:432b) with b43 on Ubuntu 26.04 scans WiFi networks, but authentication always times out.
Hardware is detected correctly:
lspci -nn | grep -i broadcom
0d:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4322 802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)
Firmware packages installed:
dpkg -l | grep -E 'b43|bcmwl|broadcom|firmware-b43'
ii b43-fwcutter
ii firmware-b43-installer
ii linux-firmware-broadcom-wireless
My WiFi adapter worked correctly in Ubuntu before.
After a system update, WiFi stopped working.
I previously managed to recover functionality with help from another AI assistant (DeepSeek), but after a later Ubuntu update to 26.04 the problem returned.
Ethernet works perfectly.
Other devices connect to the same router without problems:
Therefore the router itself appears to be working normally.
The adapter:
Example:
nmcli device wifi list
Shows all nearby networks including my own network.
However, any connection attempt fails.
NetworkManager typically reports:
Activation: (wifi) association took too long
ssid-not-found
After a failed attempt, network scanning often becomes unstable and WiFi networks disappear until NetworkManager is restarted.
Restarting NetworkManager restores network visibility.
Router: Totalplay ISP router.
SSID:
Totalplay-2.4G-bc38
Interesting observation:
The same SSID appears advertised through multiple BSSIDs:
64:9D:F3:1D:BC:38 Totalplay-2.4G-bc38
64:9D:F3:1D:BC:41 Totalplay-2.4G-bc38
64:9D:F3:1D:BC:40 Totalplay-5G-bc38
I disabled and reconfigured WiFi multiple times, including router factory reset.
The issue remains.
At boot:
b43-phy0: Broadcom 4322 WLAN found
Loading firmware version 784.2
At some point I observed:
b43-phy0 ERROR: Fatal DMA error
This device does not support DMA on your system.
It will now be switched to PIO.
Because of this, I currently use:
cat /etc/modprobe.d/b43.conf
options b43 pio=1
Current runtime value:
cat /sys/module/b43/parameters/pio
1
To eliminate NetworkManager from the equation I stopped NetworkManager and tested directly with wpa_supplicant.
Configuration:
network={
ssid="Totalplay-2.4G-bc38"
psk=<generated_psk>
bssid=64:9D:F3:1D:BC:38
freq_list=2412
}
This forces:
Result:
Trying to authenticate with 64:9d:f3:1d:bc:38
freq=2412 MHz
nl80211: Authentication request sent successfully
Authentication timed out
The adapter sends authentication requests but never receives a response.
The failure happens before WPA key negotiation.
I tested:
Behavior changes slightly between kernels but neither kernel successfully connects.
I also created a fresh NetworkManager profile and forced:
key-mgmt=wpa-psk
proto=rsn
pairwise=ccmp
group=ccmp
No improvement.
Has anyone seen BCM4322 + b43 authentication failures like this on recent Ubuntu kernels?
Could this be:
Any suggestions for further debugging would be greatly appreciated.
After using for a period, Chrome sometimes becomes very slow and eventually freezes. Sometimes I can restart Chrome, other times I have to reboot my laptop. After many years of fault-free operation under Ubuntu, this problem has gradually become more frequent over the last few weeks.
Do you have any suggestions on how to find out what is causing the problem, and a possible cure? Please provide guidance on what diagnostic information would help to narrow down the cause.
System information:
Diagnostic Information:
System Monitor shows multiple errors even before slowdown, mostly of the form '/opt/google/chrome/chrome -type-renderer --crashpad-handler-pid-4808-enable-crash-reporter-.... followed by another 10 lines of alpha-numeric words and numbers. (I'm not sure if this is connected to the slowdown/freeze problem, although I did once notice a big increase in the number of processes of this type, although I did not manage to capture the details).
CPU usage has periods of 100% usage on some of the 8 CPUs
System Memory (8.0 GB) was 100% full just before latest crash.
After restart, System Memory started at 20% with single tab on Chrome, increased to c. 40% with 6 tabs. swap is at <10%
2-3 hours after restart with 2 Chrome windows, email, LibreOffice Writer, etc. running, memory and swap usage are both >80%
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/4c859583-daba-499b-9918-8bc642b14b80 / 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=4c859583-daba-499b-9918-8bc642b14b80 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"
findmnt -no UUID -T /swapfile
4c859583-daba-499b-9918-8bc642b14b80
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: 5479724 2497868 1505624 97228 1809976 2981856
Swap: 16777212 0 16777212
I am trying to install Lubuntu 26.04 on an old computer, dual boot alongside Windows 10 on the same GPT SSD, however after a successful installation the computer boots into Windows. Grub does not appear, and I have no option to boot into Linux.
The motherboard is a Hybrid EFI Gigabyte 78LMT. Apparently it can make dual booting very tricky, but I lack the technical knowledge to understand details like these. Windows is installed in UEFI mode, but I can only boot from USB in legacy mode; hence, Lubuntu is not installed in EFI mode. The inability to boot USB in EFI mode is a known issue with this motherboard and its "hybrid EFI" technology.
Specs:
Motherboard: Gigabyte GA-78LMT-USB3 Rev. 5.0
CPU: AMD FX-8350 (8-core, 125W, AM3+)
RAM: 8GB DDR3 1600 MHz (2×4 GB)
GPU: AMD Radeon HD 7750 1GB GDDR5
I have tried this solution but boot-repair gives the following error:"The current session is in Bios-compatibility mode". I cannot setup the BIOS to boot USB in EFI mode, the option exists for CD/DVD only, as explained here:
Although Gigabyte's Hybrid EFI contains a full-fledged EFI implementation from an OS's perspective, the firmware setup utility provides almost no options to help you use this functionality. Specifically, only one firmware option, entitled "EFI CD/DVD Boot Option," on the "Advanced BIOS Features" menu, relates to this feature.
In another question, someone tried to install from CD, apparently without success. I have no CD/DVD drive to test this option.
I cannot find any UEFI settings to select Ubuntu as the default operating system to boot either; thus, it seems this solution will not work: no UEFI settings.
I can choose from which disk to boot; Windows and Ubuntu are on the same SDD. I have also an old HDD I use for backup attached to the motherboard; perhaps installing GRUB on it could be a solution?
I've done this many times on different systems, but this has me puzzled:
OS: Ubuntu 26
Had an external drive that I was mounting using the fstab.
/dev/sda1 /data ext4 defaults 0 0
I removed the drive and of course it rebooted and went into recovery mode. So I edited the /etc/fstab and removed the external drive mount. Now when it reboots, it still hangs up on trying to mount that drive.
Does Ubuntu 26 store the information that is/was in the fstab in another spot? Like a database or other file? I noticed the fstab in Ubuntu 26 is very minimal, so I'm guessing there is some sort of other place that needs to be updated??
GNOME Activities Overview workspace thumbnails begin flickering after about 10 minutes of uptime on Ubuntu 26.04 LTS with GNOME Shell 50.1 running on Wayland and Intel Alder Lake-N integrated graphics (i915 driver).
System:
Symptoms:
I’ve tried:
Observations:
Question:
Has anyone seen GNOME Activities Overview workspace thumbnail flickering or corruption on GNOME Shell 50 / Mutter 50 under Wayland, particularly on Intel integrated graphics? Are there known issues, workarounds, or logs that I should investigate further?
Update:
I performed additional testing and found a significant correlation with monitor configuration.
With my original multi-monitor setup (2 ASUS monitors + 1 TCL TV), GNOME Shell produced thousands of repeated errors:
gbm_surface_lock_front_buffer failed Failed to query buffer age, got error 3003
These sessions also exhibited Activities Overview flickering, top-panel flickering, and occasional window-edge artifacts.
I have now tested the system with a single display only (different display: Sony TV over HDMI) and the issue has not reproduced. There is no visible flickering, no rendering corruption, and:
journalctl -b | grep -c "gbm_surface_lock_front_buffer failed" 0
journalctl -b | grep -c "Failed to query buffer age" 0
The issue also reproduced across multiple kernels, including a newer mainline kernel Linux 7.0.12-070012-generic, which makes a pure kernel/i915 explanation seem less likely. Using this mainline kernel the symptoms also started appearing after roughly 10 minutes rather than a few hours.
At this point, the strongest lead appears to be a GNOME Shell/Mutter multi-monitor rendering issue, or an interaction involving multiple outputs.
Update (June 22nd):
The issue now consistently appears ~10 minutes after boot (earlier testing likely just didn’t run under full load).
The “unplug/replug” suggestion didn’t help, but it led to a reliable workaround: boot with only the DP 4K display connected, wait a few minutes, then connect the first HDMI display, wait again, then connect the second HDMI display. This results in a stable session and has provided ~20 hours of uptime without flickering or GBM errors.
I’ve reverted all system tweaks and returned displays to:
DP-1: 3840×2160 @ 60Hz, 200% scaling HDMI-1: 3840×2160 @ 60Hz, 200% scaling HDMI-2: 1920×1080 @ 60Hz, 100% scaling
(Previous all at 1080p configuration was part of testing.)
Driver and desktop tests:
Tried Intel Xe driver → same issue Tried KDE Plasma and Budgie → no flickering/GBM errors, but DP 4K display stayed black until forcing 30Hz via CLI (GUI wouldn’t allow it), so I reverted back to GNOME
Current conclusion: GNOME + Intel display stack on this hardware appears unstable only in full 3-display configurations. Any 1–2 display combination is stable for long periods, but stability on 3 displays only occurs with the staged hotplug sequence (DP first, then HDMIs). Adding DP last reliably triggers the issue.
At this point, this is a workaround rather than a fix.
Starting an installation of Ubuntu 26.04 with full disk wipe using the graphical installer, I have an installation stuck at rsync command for 30+ minutes after an error.
rsync connection closed:
Apr 23 23:21:19 ubuntu subiquity_log.3615[8812]: curtin: Installation started. (24.04.0-193-g67962f8bb)
Apr 23 23:21:19 ubuntu subiquity_log.3615[8812]: {'WORKING_DIR': '/tmp/tmpjeokba_0/scratch',
'OUTPUT_FSTAB': '/tmp/tmpjeokba_0/state/fstab', 'OUTPUT_INTERFACES': '/tmp/tmpjeokba_0/state/
interfaces', 'OUTPUT_NETWORK_CONFIG': '/tmp/tmpjeokba_0/state/network_config', 'OUTPUT_NETWORK_STATE':
'/tmp/tmpjeokba_0/state/network_state', 'TARGET_MOUNT_POINT': '/target', 'CONFIG': '/tmp/tmpjeokba_0/
state/config'}
Apr 23 23:21:19 ubuntu subiquity_log.3615[8812]: start: cmd-install/stage-extract: writing install
sources to disk
Apr 23 23:21:19 ubuntu subiquity_log.3615[8812]: start: cmd-install/stage-extract/builtin: running
'curtin extract'
Apr 23 23:21:19 ubuntu subiquity_event.3615[3615]: curtin command install
Apr 23 23:21:19 ubuntu subiquity_event.3615[3615]: writing install sources to disk
Apr 23 23:21:19 ubuntu subiquity_event.3615[3615]: running 'curtin extract'
Apr 23 23:21:20 ubuntu subiquity_log.3615[8812]: start: cmd-install/stage-extract/builtin/cmd-extract:
curtin command extract
Apr 23 23:21:20 ubuntu subiquity_log.3615[8812]: Installing sources: [{'type': 'tgz', 'uri': 'cp:///
tmp/tmp7ydka4xs/mount'}] to target at /target
Apr 23 23:21:20 ubuntu subiquity_log.3615[8812]: start: cmd-install/stage-extract/builtin/cmd-extract:
acquiring and extracting image from cp:///tmp/tmp7ydka4xs/mount
Apr 23 23:21:20 ubuntu subiquity_log.3615[8812]: Setting up Trivial Source for stack /tmp/tmp7ydka4xs/
mount
Apr 23 23:21:20 ubuntu subiquity_log.3615[8812]: Running command ['rsync', '-aXHAS', '--one-file-
system', '/tmp/tmp7ydka4xs/mount/', '.'] with allowed return codes [0] (capture=False)
Apr 23 23:21:20 ubuntu subiquity_event.3615[3615]: curtin command extract
Apr 23 23:21:20 ubuntu subiquity_event.3615[3615]: acquiring and extracting image from cp:///
tmp/tmp7ydka4xs/mount
Apr 23 23:21:20 ubuntu subiquity_log.3615[8812]: rsync: connection unexpectedly closed (0 bytes
received so far) [Receiver]
Apr 23 23:21:20 ubuntu subiquity_log.3615[8812]: rsync error: error in rsync protocol data stream
(code 12) at io.c(232) [Receiver=3.4.1]
Is there any way to proceed?
Wi-Fi works when it wishes to. Sometimes it works fine despite heavy downloads and fast speed and Bluetooth enabled. Sometimes it goes on strike after loading a couple of tabs in the browser. It may stop working soon after boot, after many minutes, or hours, or not at all. The problem presents itself almost periodical. Usually, It starts having problems when I am using both wifi and bluetooth at the same time. Until now it appeared thrice, and it solved "itself" twice with an update after a number of months between 1 and 4, without any information on what caused or fixed the issue.
On the widget on the top right the wifi cannot detect networks, and if wifi is turned off it cannot be turned on. Sometimes, on boot the wifi voice on the drop-down menu is not even showing. lshw -c network shows network UNCLAIMED.
Running BIOS diagnostics detects no issue.
dmesg ` https://paste.ubuntu.com/p/xJHrD2cr2G/./wireless-info output https://paste.ubuntu.com/p/bVQqnVc7Pj/I've tried reinstalling linux-firmware, NetworkManager restarts, to no avail. After a while, something randomly breaks, and it is especially frustrating as I have no easy access to ethernet cables.
Using older kernels did not work either.
I found that, SOMETIMES, flea reset OR messing with unimportant BIOS options, booting the os, rebooting and changing BIOS options again sometimes allows me for sustained network access (a suggestion I found browsing for solutions)... maybe this last one is not effective, I don't know how to check.
neofetch --stdoutNo dual boot. The machine came with Ubuntu22.04.1 preinstalled. I use it for work, programming, scientific computation, watching videos, and gaming. The original kernel for this Dell was an OEM kernel listed as 6.1.0-1013.13_oem. I have installed HWE kernels and I am currently running the latest HWE available. It worked perfectly for more than 1 year, even after I upgraded the OS to Ubuntu24. To try to fix the issue, I performed a factory reset, and it is back to 22.
I performed hardware and software diagnostics.
I performed diagnostics from the manifacturer's BIOS menu, using quick test and advanced test: all passed
I created wifi logs using the wireless-info script I found here in askubuntu: wget -N -t 5 -T 10 https://github.com/UbuntuForums/wireless-info/raw/master/wireless-info
The following logs were created using ./wireless-info when the wifi crashed, and no LAN network was attached.
https://paste.ubuntu.com/p/bVQqnVc7Pj/ (updated on 23/06/2026)
~https://paste.ubuntu.com/p/T7Pv3NMnXc/~
The following logs were created when the wifi is working just after boot (and it crashes later) using the same script. https://paste.ubuntu.com/p/td4gSKsJFy/ (updated on 23/06/2026) https://paste.ubuntu.com/p/SGFcT7dXyB/ (updated on 24/12/2025)
I welcome any advice on what to do when it will break, or why does it do that, additional diagnostics, readings, tools to install, etc. are more than welcome.
E.g. I have just installed net-tools and iw, and I have read conflicting and old advice suggesting to install backport-iwlwifi-dkms.
Also, the guide in https://help.ubuntu.com/community/WifiDocs/WirelessTroubleShootingGuide seems to be somewhat helpful with understanding the diagnostics. Sadly, it does not provide any help in dealing with the problem I am experiencing.
The problem manifested again. All I did was
sudo apt updateapt list --upgradeble (no hardware, security, or system updates, only software-related updates unrelated to wifi)sudo apt upgrade
After I lost wifi in the middle of the update, the wifi disappeared altogether.What I tried and did not work:
nmcli networking off && nmcli networking on;nmcli radio wifi off && nmcli radio wifi on.What did work for a bit:
The diagnostics were updated in this edit.
This is the old diagnostic of the wifi when it is not working:
https://paste.ubuntu.com/p/xnYs8dGp5W/
I am keeping it for reference, but it lacks iw outputs.
I may have made some progress.
The problem did not appear for some months after some updates. However, with the latest update the issue presented itself again.
I noticed that many error logs show "microcode"
sudo dmesg | grep -iE 'microcode' [ 391.120843] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
A more complete output of dmesg is found here: https://paste.ubuntu.com/p/xJHrD2cr2G/
I tried a couple of workarounds:
sudo iwconfig wlp0s20f3 power off and sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf and reboot, as suggested by @Jeremy31. Sadly, it did not work./etc/modprobe.d/iwlwifi.conf options iwlwif 11n_disable=1 options iwlwifi swcrypto=0 options iwlwifi power_save=0 options iwlwifi uapsd_disable=1 as explained in What is "options iwlwifi 11n_disable=1" in WiFi setting? and https://bbs.archlinux.org/viewtopic.php?id=254766This last fix seems to solve the issue, and without any external fix. In the next days I'll try to isolate the specific options that make the iwlwifi work, to isolate which option causes the iwlwifi module to crash.
The diagnostics and the problem description were updated and cleaned in this edit.
I find it curious that a (possibly) working fix to this issue was found in an Arch Linux forum.
Folks, I have recently purchased this laptop: https://psref.lenovo.com/Product/Yoga/Yoga_Pro_9_14IRP8
And I can only get the front speakers working on Ubuntu 22.04 which results in the sound being not great to say the least.
From reading around I found out that the laptop comes with two sets of speakers like many new Yoga laptops and both of them are supposed to be playing at the same time: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165
Same issue on Fedora: https://discussion.fedoraproject.org/t/problem-with-sound-on-new-lenovo-laptops/72456
I was not able to get the speakers running with the tricks above, does anyone have an idea? Thank you in advance.
I am currently running the kernel: 6.2.0-33-generic.
First of all, I'm not an experienced user so please be as clear as possible in all answers. I recently installed Ubuntu 22.04 on a new HP Victus laptop (This one except with Intel Core i7-12700H and GeForce RTX 3050 Ti). The wifi was working fine. I was not messing with any settings, it just suddenly disconnected and now it says "no wifi adapter found" in settings. I have already tried some solutions from similar questions but nothing works. I'm now online using a tethered android phone.
The wifi adapter does not show up using 'sudo lshw -C network':
*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:06:00.0
logical name: eno1
version: 16
serial: a8:b1:3b:92:0a:eb
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=5.19.0-32-generic firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=twisted pair
resources: irq:19 ioport:3000(size=256) memory:82204000-82204fff memory:82200000-82203fff
*-network
description: Ethernet interface
physical id: 12
bus info: usb@3:3
logical name: enx1e31043ced9f
serial: 1e:31:04:3c:ed:9f
capabilities: ethernet physical
configuration: autonegotiation=off broadcast=yes driver=rndis_host driverversion=5.19.0-32-generic duplex=half firmware=RNDIS device ip=192.168.16.27 link=yes multicast=yes port=twisted pair
I ran a wireless-info script i found. The output is here.
sudo dmesg | grep iwl gives:
[ 1.482435] Loading modules backported from iwlwifi
[ 1.482436] iwlwifi-stack-public:master:10878:f4df8641
rfkill list gives:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
iwconfig gives:
lo no wireless extensions.
eno1 no wireless extensions.
enx1e31043ced9f no wireless extensions.
I hope I haven't messed things up even further trying things from other questions without knowing exactly what I was doing (there are so many, i've lost track of everything I've done). I will use this computer for studying and I've spent a lot of time setting up all the software I will need, CUDA for molecular dynamics simulations and onedrive etc. So I would really like to avoid a fresh install if possible. Thank you in advance for your help.
My computer is stuck at a black screen with cursor before logging in. After booting into Ubuntu 20.04 nothing is working, even the cursor is not moving. It's freezing. I also tried Ctrl+Alt+F4, but it's not opening the terminal. When I restart the system and in grub menu select Advanced options for Ubuntu and select Recovery mode, the recovery mode is not working either. It's stuck. Only the old recovery mode is working. How to fix this problem?
During the OS installation I think I have selected the option to install third-party drivers, firmware, codecs, etc., but I'm not sure.
Hardware specs:
While messing around with wine and learning how to use it I tried to start a game with it (genshin impact), as expected the game doesn't work very well (it simply crash) but I found in the logs some error I would like to fix.
00c9:err:module:import_dll Library WDFLDR.SYS (which is needed by L"C:\\users\\galyfray\\Temp\\mhyprot2.sys") not found
After some research it seems to be a very important lib in windows and messing with it leads to BSOD but nothing about wine.
I'm running Ubuntu 20.04 with wine 5.0.2 wich is setup to emulate like a Win10. The missing lib isn't avalable with winetricks.
I have also several others error I put them bellow if some of them are related to my problem
wine: Read access denied for device L"\\??\\Z:\\", FS volume label and serial are not available.
0030:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0030:fixme:ntdll:EtwEventRegister ({5eec90ab-c022-44b2-a5dd-fd716a222a15}, 0x3161124, 0x4487e40, 0x4487e60) stub.
0030:fixme:ntdll:EtwEventSetInformation (deadbeef, 2, 0x4377370, 43) stub
0035:fixme:ver:GetCurrentPackageId (0x46bfda0 (nil)): stub
0036:fixme:ver:GetCurrentPackageId (0x47cfda0 (nil)): stub
0037:fixme:ver:GetCurrentPackageId (0x48dfda0 (nil)): stub
0038:fixme:ver:GetCurrentPackageId (0x49efda0 (nil)): stub
0030:fixme:font:get_outline_text_metrics failed to read full_nameW for font L"Ani"!
0030:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
0030:fixme:toolhelp:Heap32ListFirst : stub
0030:fixme:font:get_nearest_charset TCI failing on 20000000
0030:fixme:font:get_nearest_charset returning DEFAULT_CHARSET face->fs.fsCsb[0] = 20000000 file = L"/usr/share/fonts/truetype/fonts-gujr-extra/aakar-medium.ttf"
0030:fixme:nls:get_dummy_preferred_ui_language (0x8 0x22f1f0 0x22f140 0x22f1f8) returning a dummy value (current locale)
0030:fixme:nls:get_dummy_preferred_ui_language (0x8 0x22efd0 0x22ef20 0x22efd8) returning a dummy value (current locale)
0030:fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0x70b8f00, 0xaf36a10, 0xb086fc8) stub.
0030:fixme:nls:GetThreadPreferredUILanguages 00000038, 0x22dab0, (nil) 0x22dab8
0030:fixme:nls:get_dummy_preferred_ui_language (0x38 0x22dab0 (nil) 0x22dab8) returning a dummy value (current locale)
0030:fixme:nls:GetThreadPreferredUILanguages 00000038, 0x22dab0, 0x5e7ec40 0x22dab8
0030:fixme:nls:get_dummy_preferred_ui_language (0x38 0x22dab0 0x5e7ec40 0x22dab8) returning a dummy value (current locale)
0030:fixme:winsock:WSALookupServiceBeginW (0x22d7f0 0x00000ff0 0x22d7e8) Stub!
0030:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (000000000022D520 1 C) semi-stub
0030:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (000000000022D1A0 1 C) semi-stub
0030:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (000000000022D0F0 1 C) semi-stub
0030:fixme:iphlpapi:NotifyAddrChange (Handle 0x22da90, overlapped 0x5e7fa50): stub
0030:fixme:win:RegisterDeviceNotificationW (hwnd=0x101f4, filter=0x22d7e0,flags=0x00000000) returns a fake device notification handle!
0030:fixme:win:RegisterDeviceNotificationW (hwnd=0x101f4, filter=0x22d7e0,flags=0x00000000) returns a fake device notification handle!
0030:fixme:font:get_nearest_charset TCI failing on 20000000
0030:fixme:font:get_nearest_charset returning DEFAULT_CHARSET face->fs.fsCsb[0] = 20000000 file = L"/usr/share/fonts/truetype/fonts-gujr-extra/aakar-medium.ttf"
0030:fixme:font:get_outline_text_metrics failed to read full_nameW for font L"Ani"!
0030:fixme:systray:Shell_NotifyIconGetRect stub (0x22efa0) (0x22ef90)
0030:fixme:msg:ChangeWindowMessageFilterEx 0x10204 c062 1 (nil)
0030:fixme:systray:Shell_NotifyIconGetRect stub (0x22efa0) (0x22ef90)
0044:fixme:file:ReplaceFileW Ignoring flags 2
0049:fixme:wlanapi:WlanEnumInterfaces (0000000000000001, 0000000000000000, 000000000E6DEDF8) semi-stub
0053:fixme:process:CreateProcessInternalW Unsupported attribute 0x20002.
0030:fixme:dwmapi:DwmIsCompositionEnabled 000000000022BEA0
0055:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
0055:fixme:ntdll:EtwEventRegister ({d2d578d9-2936-45b6-a09f-30e32715f42d}, 0xc28f00, 0x4aa6a10, 0x4bf6fc8) stub.
0055:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (000000000022F020 1 C) semi-stub
0055:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (000000000022ECA0 1 C) semi-stub
0055:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0044:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
0043:fixme:file:ReplaceFileW Ignoring flags 2
wine: Read access denied for device L"\\??\\C:\\", FS volume label and serial are not available.
0044:fixme:file:ReplaceFileW Ignoring flags 2
wine: Read access denied for device L"\\??\\C:\\", FS volume label and serial are not available.
0073:fixme:time:QueryThreadCycleTime (0xfffffffffffffffe,0x9c1f060): stub!
00e9:fixme:heap:RtlSetHeapInformation 0x570000 0 0x22da50 4 stub
00e9:fixme:heap:EnumSystemFirmwareTables (0x4649524d, 0000000000000000, 0)
00e9:fixme:heap:RtlSetHeapInformation 0x7a0000 0 0x22f1b0 4 stub
00ea:fixme:ver:GetCurrentPackageId (0x9afb00 (nil)): stub
I hope that someone know how to fiw it I will continue my research and update if I found anything. EDIT : I'm using WINEARCH=win64 (the game is in 64 bit as far as know it shouldn't be a problem) and a 64 bit WINEPREFIX
EDIT 2: dowloading and placing the missing file where it should be in the window file tree doesn't solve the problem
I used this command to install pwgen:
sudo snap install pwgen-tyhicks
But I can't find out how to use it. So I want to uninstall it. How do I uninstall it?
After installing Lubuntu, I got the No bootable device error, and after searching the net for a solution, tried to set the Select an UEFI file as trusted for executing option as instructed, but it does not show me any drives. The Information screen in the bios setup shows me HDD0, but the Security screen that's supposed to let me select the efi file shows nothing, unless I insert the USB. I set the supervisor password after installation, and I thought this may be a reason, and installed it all over again. But it's still showing me nothing. I am sure the installation was done on the hard disk because all previous boot options are gone (as I wanted).
What can be the problem? P.S. I am new to Linux.
Edit:
I have tried turning off secure boot, but it did not help.
I have checked and there is one partition with file system lvm2 pv with flags boot and lvm.
It's an Acer Aspire E 15 (E5-575-50RM) that came with Linpus and had no GUI. I have installed lubuntu-17.10.1-desktop-amd64.
I did not use any software to create the USB since my Windows XP is damaged and files are missing or corrupted. I used EaseUS Partition Master to format the USB as FAT32 and then copied the extracted ISO files to it, then marked the single partition as active.
I recently switched to linux full time from windows and while I was trying to update my npm package using n, I got the new binaries in /usr/local/bin and previous version was in /usr/bin. So, it was always picking the previous version.
As per recommendation by a fellow user, I used hash -r command and it worked. But, I don't know what it did.
It would be very helpful if someone could explain its internals to me.
I am trying to help a user solve an issue with a bootable USB drive, but there seems to be a file whose ownership cannot be edited. I thought it would have been possible with:
sudo chown user:user ldlinux.sys
When that is executed, however, terminal gives this error:
Operation not permitted
The extended chat I had with the user can be found here.
My printer is HP laser jet pro p1102. It is a share printer. When I try to print this error message pops up
Unable to connect to CIFS host
How can I make an application automatically start when I have logged in?