System Environment:

• OS: Ubuntu 26.04 LTS (recently upgraded from Ubuntu 24.04 LTS)

• Hardware: Dell OptiPlex 3070 (Intel Integrated Graphics)

• Default Display Server: Wayland

• Applications Affected: Conky, GLava, and bibisco (Electron)

1. Background & Problem

Prior to upgrading from Ubuntu 24.04 LTS to 26.04 LTS, desktop widgets and applications loaded reliably. Since the upgrade to 26.04, transparency and window rendering intermittently fail on cold boot for Conky, GLava, and bibisco.

• The processes actually launch and run in the background (confirmed via ps aux and terminal PIDs).

• However, no graphical windows map or render onto the screen.

• Re-launching the commands manually from a running session terminal does not force them to appear.

• It often takes two or three system reboots before the desktop compositor draws them correctly.

2. What Was Investigated

A. Display Server Verification

Checking the active session via terminal:

Bash

echo $XDG_SESSION_TYPE

Output: wayland

Because GLava relies on X11 root-window docking and Conky relies on transparent window layers, running under Wayland via XWayland appears to cause a race condition during startup where window buffers fail to map.

B. Attempting to Switch to X11 (Xorg)

We tried forcing an X11 session by editing /etc/gdm3/custom.conf and un-commenting and adding session preference:

Plaintext

WaylandEnable=false
PreferredSession=x11

Results:

1. GDM Session Options: An "Ubuntu on Xorg" option appeared in GDM. However, selecting it and attempting to log in fails immediately—it drops right back to the GDM login screen (login loop).

2. GNOME Option: Selecting standard GNOME from GDM causes the system to freeze completely upon logging in, requiring a hard power button reset.

3. Missing Session Files: Checking /usr/share/xsessions/ initially revealed that standard ubuntu-xorg.desktop session files were missing post-upgrade (only lightdm-xsession.desktop and openbox.desktop were present).

4. Manual Session File Creation: After manually generating an ubuntu-xorg.desktop file, GDM still fails to start the Xorg session and kicks the user back to the login prompt.

3. Questions for the Community

1. What logs (journalctl, GDM, or Xorg logs) should be inspected to identify why Xorg drops immediately back to GDM on an Intel OptiPlex 3070 following an upgrade from 24.04 to 26.04?

2. Are there leftover configuration files or package conflicts from the 24.04 to 26.04 upgrade known to break the X11 session or cause XWayland rendering issues for desktop overlays?

3. Is there a recommended Wayland/XWayland compositor configuration or wlr-layer-shell workaround to prevent desktop overlay tools (GLava/Conky) from launching as "invisible" background processes on Ubuntu 26.04?

Whenever running OpenMPI programs, I am experiencing an hwloc error on Ubuntu 24.04 LTS (kernel 6.17.0-35-generic):

****************************************************************************
* hwloc 2.10.0 received invalid information from the operating system.
*
* Failed with error: intersection without inclusion
* while inserting Group0 (P#16 subtype Cluster groupkind 222-0 cpuset 0x00000f00)
* at L1d (P#16 cpuset 0x00000104)
* coming from: linux:sysfs:cluster
*
* The following FAQ entry in the hwloc documentation may help:
*   What should I do when hwloc reports "operating system" warnings?
* Otherwise please report this error message to the hwloc user's mailing list,
* along with the files generated by the hwloc-gather-topology script.
* 
* hwloc will now ignore this invalid topology information and continue.
****************************************************************************
****************************************************************************
* hwloc 2.10.0 received invalid information from the operating system.
*
* Failed with error: intersection without inclusion
* while inserting Group0 (P#16 subtype Cluster groupkind 222-0 cpuset 0x00000f00)
* at L1d (P#16 cpuset 0x00000104)
* coming from: linux:sysfs:cluster
*
* The following FAQ entry in the hwloc documentation may help:
*   What should I do when hwloc reports "operating system" warnings?
* Otherwise please report this error message to the hwloc user's mailing list,
* along with the files generated by the hwloc-gather-topology script.
* 
* hwloc will now ignore this invalid topology information and continue.
****************************************************************************

The output of hwloc-ls is:

Machine (62GB total)
  Package L#0
    NUMANode L#0 (P#0 62GB)
    L3 L#0 (36MB)
      L2 L#0 (3072KB) + L1d L#0 (48KB) + L1i L#0 (64KB) + Core L#0 + PU L#0 (P#0)
      L2 L#1 (3072KB) + L1d L#1 (48KB) + L1i L#1 (64KB) + Core L#1 + PU L#1 (P#1)
      L1d L#2 (48KB) + L1i L#2 (64KB)
        L2 L#0 (3072KB) + Core L#2 + PU L#2 (P#2)
        Core L#3 + PU L#3 (P#8)
      L1d L#3 (48KB) + L1i L#3 (64KB)
        L2 L#1 (3072KB) + Core L#4 + PU L#4 (P#3)
        Core L#5 + PU L#5 (P#10)
      L1d L#4 (48KB) + L1i L#4 (64KB)
        L2 L#2 (3072KB) + Core L#6 + PU L#6 (P#4)
        Core L#7 + PU L#7 (P#12)
      L1d L#5 (48KB) + L1i L#5 (64KB)
        L2 L#3 (3072KB) + Core L#8 + PU L#8 (P#5)
        Core L#9 + PU L#9 (P#14)
      L2 L#2 (3072KB) + L1d L#6 (48KB) + L1i L#6 (64KB) + Core L#10 + PU L#10 (P#6)
      L2 L#3 (3072KB) + L1d L#7 (48KB) + L1i L#7 (64KB) + Core L#11 + PU L#11 (P#7)
      L1d L#8 (32KB) + L1i L#8 (64KB) + Core L#12 + PU L#12 (P#9)
      L1d L#9 (32KB) + L1i L#9 (64KB) + Core L#13 + PU L#13 (P#11)
      L1d L#10 (32KB) + L1i L#10 (64KB) + Core L#14 + PU L#14 (P#13)
      L1d L#11 (32KB) + L1i L#11 (64KB) + Core L#15 + PU L#15 (P#15)
      L2 L#4 (4096KB)
        L1d L#12 (32KB) + L1i L#12 (64KB) + Core L#16 + PU L#16 (P#16)
        L1d L#13 (32KB) + L1i L#13 (64KB) + Core L#17 + PU L#17 (P#17)
        L1d L#14 (32KB) + L1i L#14 (64KB) + Core L#18 + PU L#18 (P#18)
        L1d L#15 (32KB) + L1i L#15 (64KB) + Core L#19 + PU L#19 (P#19)
      L2 L#5 (4096KB)
        L1d L#16 (32KB) + L1i L#16 (64KB) + Core L#20 + PU L#20 (P#20)
        L1d L#17 (32KB) + L1i L#17 (64KB) + Core L#21 + PU L#21 (P#21)
        L1d L#18 (32KB) + L1i L#18 (64KB) + Core L#22 + PU L#22 (P#22)
        L1d L#19 (32KB) + L1i L#19 (64KB) + Core L#23 + PU L#23 (P#23)
HostBridge
  PCIBridge
    PCI 01:00.0 (NVMeExp)
      Block(Disk) "nvme0n1"
  PCI 00:02.0 (VGA)
  PCIBridge
    PCI 02:00.0 (VGA)
  PCIBridge
    PCI 2c:00.0 (NVMeExp)
      Block(Disk) "nvme1n1"
  PCI 00:0b.0 (ProcessingAccelerator)
HostBridge
  PCI 80:14.5 (Other)
  PCIBridge
    PCI 81:00.0 (Network)
      Net "wlp129s0f0"
  PCIBridge
    PCI 82:00.0 (Ethernet)
      Net "enp130s0"

Switching to more recent hwloc versions (2.13.0 or 2.14.0) doesn't fix the issue.

My CPU is Intel Core i9 275HX.

I assume the hybrid architecture is poorly recognized by the kernel, right?

I have a subscription to Ubuntu Pro on my Ubuntu 26.04 desktop. A 'pro status' enquiry shows 'esm-apps', 'esm-infra' and 'livepatch' all enabled. I have also run a software update. When I run a 'pro cves' scan several things puzzle me. First, 11 vulnerabilities show up marked as critical and 6 of these occur in 12 different packages.

For example:

linux-headers-7.0.0-27-generic              critical    -       CVE-2026-31608
linux-headers-7.0.0-27-generic              critical    -       CVE-2026-43501
linux-headers-7.0.0-27-generic              critical    -       CVE-2026-45988
linux-headers-7.0.0-27-generic              critical    -       CVE-2026-46043
linux-headers-7.0.0-27-generic              critical    -       CVE-2026-46135
linux-headers-7.0.0-27-generic              critical    -       CVE-2026-52955
linux-headers-7.0.0-27-generic              critical    -       CVE-2026-52989
linux-headers-7.0.0-27-generic              critical    -       CVE-2026-52993
linux-headers-7.0.0-27-generic              critical    -       CVE-2026-53002
linux-headers-7.0.0-27-generic              critical    -       CVE-2026-53215
linux-headers-7.0.0-27-generic              critical    -       CVE-2026-53260

When I run 'pro fix CVE-2026-XXXXX' on each vulnerability I get a result saying all except for the last 2 of them are fixed (or at least that's how I interpret the message).

For example:

CVE-2026-31608: Linux kernel vulnerabilities
 - https://ubuntu.com/security/CVE-2026-31608

1 affected source package is installed: linux
(1/1) linux:
A fix is available in Ubuntu standard updates.
The update is already installed.

✔ CVE-2026-31608 is resolved.

The message for the remaining 2 vulnerabilities (CVE-2026-53215 and -53260) says an update is coming tomorrow.

After a reboot the pro cves scan results are exactly the same.

Another thing, why is there no information under the 'Origin' column? Does my machine have a CVE problem or not?

On every distribution where I've ever used Emacs before (including my old Ubuntu 20.04 install), when I resize the Emacs window, there's a little label that pops up that shows the size of the window (in lines and columns) as I'm resizing the window.

This is really useful (almost essential) because when I'm editing code, I often want to set the window to a specific width, in columns.

However, I recently installed Kubuntu 26.04, and emacs no longer displays the number of lines and columns as I resize. This is a big problem, because I'm just guessing how wide the window is.

This seems to be limited to Emacs, because if I resize a Konsole window, it does show the number of lines and columns, as I would expect.

I'm using Emacs 30.2 from the emacs-pgtk package. (I installed this package because it claims to work best with Wayland, and Kubuntu 26.04 seems to be using Wayland.)

How do I get the number of lines/columns to be displayed when I'm resizing Emacs on Kubuntu 26.04?

Ubuntu 24.04

Unable to remove repository in GUI nor command line.

In Software Updater = Failed to download repository information, Check your Internet connection

then tried:

sudo apt-add-repository -r https://ppa.launchpadcontent.net/audio-recorder/ppa/ubuntu/
Repository: 'deb https://ppa.launchpadcontent.net/audio-recorder/ppa/ubuntu/ resolute main'
Description:
This is a new package archive for Audio-recorder.
It has packages for Ubuntu 15.x, 16.x, 17.x, 18.x, 19.x, 20.x, 21.x and 22.x and Linux Mint 18.x - 20.x.
This PPA belongs to the team.

Linux Mint 20.x is based on Ubuntu 20.04 LTS (Focal Fossa).
Linux Mint 19.x is based on Ubuntu 18.04 LTS (Bionic Beaver).
Linux Mint 18.x is based on Ubuntu 16.04 LTS (Xenial Xerus).

Installation:
0) Remove the OLD, PRIVATE PPA that belonged to the developer.  Run:
sudo add-apt-repository --remove ppa:osmoma/audio-recorder

1) Add new PPA.
Then update your package list and Install the latest version of audio-recorder.  Run:
sudo add-apt-repository  ppa:audio-recorder/ppa
sudo apt-get -y update 
sudo apt-get install --reinstall audio-recorder

-------

Older packages for Ubuntu 14.10, 14.04 and earlier, see  
https://launchpad.net/~osmoma/+archive/audio-recorder
This includes audio-recorder for Linux-Mint 13, 17 and 17.x.

Source code: 
https://launchpad.net/~audio-recorder

Bem-vindo, 
You are welcome ! 

More info: https://launchpad.net/~audio-recorder/+archive/ubuntu/ppa
Removing repository.
Press [ENTER] to continue or Ctrl-c to cancel.
Hit:1 http://us.archive.ubuntu.com/ubuntu resolute InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu resolute-updates InRelease                                    
Hit:3 http://security.ubuntu.com/ubuntu resolute-security InRelease                                     
Hit:4 http://us.archive.ubuntu.com/ubuntu resolute-backports InRelease
Ign:5 https://ppa.launchpadcontent.net/audio-recorder/ppa/ubuntu resolute InRelease
Ign:6 https://ppa.launchpadcontent.net/ubuntuhandbook1/audio-recorder/ubuntu resolute InRelease
Err:7 https://ppa.launchpadcontent.net/audio-recorder/ppa/ubuntu resolute Release
  404  Not Found [IP: 185.125.189.186 443]
Err:8 https://ppa.launchpadcontent.net/ubuntuhandbook1/audio-recorder/ubuntu resolute Release
  404  Not Found [IP: 185.125.189.186 443]
Reading package lists... Done
E: The repository 'https://ppa.launchpadcontent.net/audio-recorder/ppa/ubuntu resolute Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'https://ppa.launchpadcontent.net/ubuntuhandbook1/audio-recorder/ubuntu resolute Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

ptosis@HP17:~$ sudo apt update && sudo apt upgrade -y
Hit:1 http://us.archive.ubuntu.com/ubuntu resolute InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu resolute-updates InRelease                                                        
Hit:3 http://us.archive.ubuntu.com/ubuntu resolute-backports InRelease                                                      
Hit:4 http://security.ubuntu.com/ubuntu resolute-security InRelease                                     
Ign:5 https://ppa.launchpadcontent.net/audio-recorder/ppa/ubuntu resolute InRelease
Ign:6 https://ppa.launchpadcontent.net/ubuntuhandbook1/audio-recorder/ubuntu resolute InRelease
Err:7 https://ppa.launchpadcontent.net/audio-recorder/ppa/ubuntu resolute Release
  404  Not Found [IP: 185.125.189.187 443]
Err:8 https://ppa.launchpadcontent.net/ubuntuhandbook1/audio-recorder/ubuntu resolute Release
  404  Not Found [IP: 185.125.189.187 443]
Error: The repository 'https://ppa.launchpadcontent.net/audio-recorder/ppa/ubuntu resolute Release' does not have a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.
Error: The repository 'https://ppa.launchpadcontent.net/ubuntuhandbook1/audio-recorder/ubuntu resolute Release' does not have a Release file.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.

Next command:

sudo add-apt-repository --remove ppa:osmoma/audio-recorder

Repository: 'Types: deb
URIs: https://ppa.launchpadcontent.net/osmoma/audio-recorder/ubuntu/
Suites: resolute
Components: main
'
Description:
Audio-recorder project.
For latest versions, please go to
https://launchpad.net/~audio-recorder/+archive/ubuntu/ppa 


Here are older packages:

* PACKAGES FOR UBUNTU 14.10, 14.04 AND EARLIER UBUNTU VERSIONS:
* INCLUDES PACKAGES FOR LINUX-MINT 13, 17, 17.x.

Notice: This repository will not be updated after April 2015 !

Notice:
Linux Mint 17, 17.1, 17.2 and 17.3 are based on Ubuntu 14.04 LTS (Trusty Tahr).
Linux Mint 13 is based on Ubuntu 12.04 LTS (Precise Pangolin).

More info: https://launchpad.net/~osmoma/+archive/ubuntu/audio-recorder
Removing repository.
Press [ENTER] to continue or Ctrl-c to cancel.

Recently installed Firefox (v. 153) doesn't play embed videos mp4. It shows this error:

no video with supported format and mime type found

ffmpeg is up to date, settings at firefox untouched. What should I do ?

I am trying to install Ubuntu 26.04 on a new PC with an AMD Ryzen 7 7700X. There is no dedicated GPU so I am using the integrated graphics.

At the login screen the screen goes black every few seconds. If it is enough time to log in, the screen goes black after a few seconds and I am back at the login screen.

The recurring error is:

amdgpu 0000:11:00.0: ring gfx_0.1.0 timeout, signaled seq=15, emitted seq=16 
amdgpu 0000:11:00.0: Process gnome-shell pid 10912 thread gnome-shel:cs0 pid 10209 
amdgpu 0000:11:00.0: Starting gfx_0.1.0 ring reset 
amdgpu 0000:11:00.0: Ring gfx_0.1.0 reset failed 
amdgpu 0000:11:00.0: [drm] *ERROR* Failed to initialize parser -125!

Reading some related errors, I have tried a couple of things so far:

1. Update the BIOS

2. Run memtest -> 25 passes overnight all clear

3. Change UMA Frame Buffer size to 2GB in the BIOS

4. Tried regressing the kernel, but wasn't able to (only 7.x.x versions are listed by mainline:

   sudo mainline --install 6.12.0

   Kernel "6.12.0" not found

5. Several grub settings

   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.gfxoff=0 amdgpu.runpm=0 pcie_aspm=off"

   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.dcdebugmask=0x10" GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.dcfeaturemask=0x2 amdgpu.ppfeaturemask=0xfffd7fff"

6. And finally use a live USB to try Ubuntu 24.04, which also freezes immediately (no black screen but blurry display)

7. Tried DP and HDMI cables.

The only think that works is to boot into save graphics or apply GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset", but it's not a long-term solution.

Any ideas for further troubleshooting? To me the issue seems to be the integrated graphics on the CPU, but could it be anything else?

Would greatly appreicate any suggestions!

I'm unable to automount my HD2, but when running this command to mount it sudo mount -t ntfs-3g /dev/sdc1 /mnt/disk2 it works and can be accessed. How can get back to automounting?

I have a Dell e7470 with 26.04 that is stuck at full brightness. Booting a live instance of 24.04 works properly. I just tried the 26.04 live instance and it works properly. There must have been an update that killed that feature but unsure where to check to fix it.

Also noticed that the laptop will not come out of suspend. Powers back up but no screen. I think this happened at the same time as the brightness issue.

To extract an archive at a certain location (which may not exist yet), I like to use the --one-top-level option, e.g.

tar xzf ARCHIVE.tar.gz --one-top-level=/my/folder

This has always worked fine, but recently (looking at logs of docker build actions) it just produces errors:

tar: /my/folder: Cannot mkdir: Invalid cross-device link
tar: /my/folder/somefile: Cannot open: Invalid cross-device link

I can reproduce the error on my WSL installation, so it doesn't seem to be specific to the environment where I build docker containers. It started happening on July 7th, and happens Ubuntu 22.04, 24.04 and 26.04.

Did something change to tar or the one-top-level option? Currently running version `1.35+dfsg-4ubuntu0.4` on my WSL installation which is affected.

I have a fresh install of Kubuntu 26.04 on my MSI Katana 15 HX B14WFK laptop, installed with dual booting with Windows 11. While on Windows my fans work fine, on Linux my laptop overheats frequently, the following output of sudo sensors reveals why:

leona@leonardo-katana15hxb14wfk:~$ sudo sensors
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +48.0°C  

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +62.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +56.0°C  (high = +100.0°C, crit = +100.0°C)
Core 4:        +55.0°C  (high = +100.0°C, crit = +100.0°C)
Core 8:        +57.0°C  (high = +100.0°C, crit = +100.0°C)
Core 12:       +56.0°C  (high = +100.0°C, crit = +100.0°C)
Core 16:       +57.0°C  (high = +100.0°C, crit = +100.0°C)
Core 20:       +57.0°C  (high = +100.0°C, crit = +100.0°C)
Core 24:       +55.0°C  (high = +100.0°C, crit = +100.0°C)
Core 28:       +56.0°C  (high = +100.0°C, crit = +100.0°C)
Core 32:       +61.0°C  (high = +100.0°C, crit = +100.0°C)
Core 33:       +60.0°C  (high = +100.0°C, crit = +100.0°C)
Core 34:       +60.0°C  (high = +100.0°C, crit = +100.0°C)
Core 35:       +60.0°C  (high = +100.0°C, crit = +100.0°C)
Core 36:       +59.0°C  (high = +100.0°C, crit = +100.0°C)
Core 37:       +59.0°C  (high = +100.0°C, crit = +100.0°C)
Core 38:       +59.0°C  (high = +100.0°C, crit = +100.0°C)
Core 39:       +59.0°C  (high = +100.0°C, crit = +100.0°C)

BAT1-acpi-0
Adapter: ACPI interface
in0:          16.89 V  
curr1:         1.22 A  

msi_wmi_platform-virtual-0
Adapter: Virtual device
fan1:        2448 RPM
fan2:           0 RPM
fan3:           0 RPM
fan4:           0 RPM

nvme-pci-e100
Adapter: PCI adapter
Composite:    +45.9°C  (low  =  -5.2°C, high = +85.8°C)
                       (crit = +87.8°C)
Sensor 1:     +45.9°C  (low  = -273.1°C, high = +65261.8°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +63.0°C  

It appears only fan1 is working for some reason. I tried installing fancontrol but it requires pmwconfig to work correctly, which gives me the following output:

/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed

I tried troubleshooting this problem and online I found that adding the line acpi_enforce_resources=lax to /etc/default/grub might solve the problem but it did not help.

I also attach the output of sensors-detect:

leona@leonardo-katana15hxb14wfk:~$ sudo sensors-detect
# sensors-detect version 3.6.2
# System: Micro-Star International Co., Ltd. Katana 15 HX B14WFK [REV:1.0] (laptop)
# Board: Micro-Star International Co., Ltd. MS-1587
# Kernel: 7.0.0-28-generic x86_64
# Processor: Intel(R) Core(TM) i7-14650HX (6/183/1)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): YES
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
AMD Family 19h thermal sensors...                           No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): YES
/dev/port: Operation not permitted

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): yes
/dev/port: Operation not permitted

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): 
Found unknown SMBus adapter 8086:7a23 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.

Next adapter: Synopsys DesignWare I2C adapter (i2c-0)
Do you want to scan it? (YES/no/selectively): 
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: SMBus I801 adapter at 0000:00:1f.4 (i2c-1)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x48
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Probing for `SMSC EMC1023'...                               No
Probing for `SMSC EMC1043'...                               No
Probing for `SMSC EMC1053'...                               No
Probing for `SMSC EMC1063'...                               No
Client found at address 0x4a
Probing for `National Semiconductor LM75'...                No
Probing for `National Semiconductor LM75A'...               No
Probing for `Dallas Semiconductor DS75'...                  No
Probing for `National Semiconductor LM77'...                No
Probing for `Analog Devices ADT7410/ADT7420'...             No
Probing for `Analog Devices ADT7411'...                     No
Probing for `Maxim MAX6642'...                              No
Probing for `Texas Instruments TMP435'...                   No
Probing for `National Semiconductor LM73'...                No
Probing for `National Semiconductor LM92'...                No
Probing for `National Semiconductor LM76'...                No
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Probing for `NXP/Philips SA56004'...                        No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No

Next adapter: i915 gmbus dpa (i2c-2)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpb (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus dpc (i2c-4)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc1 (i2c-5)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc2 (i2c-6)
Do you want to scan it? (yes/NO/selectively): yes     

Next adapter: i915 gmbus tc3 (i2c-7)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc4 (i2c-8)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc5 (i2c-9)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: i915 gmbus tc6 (i2c-10)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: AUX A/DDI A/PHY A (i2c-11)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: DP-1 (i2c-12)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: eDP-2 (i2c-13)
Do you want to scan it? (YES/no/selectively): 


Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/kmod start'
to load them.

Unloading cpuid... OK

This changes nothing. Online I have seen that solutions are motherboard-specific, but no online solution I could find for MSI laptops helped.

Is anybody able to help? Thank you in advance!

EDIT: As Andrei suggested in the comments I tried installing the msi-ec driver that should support my system. This is the install output:

leona@leonardo-katana15hxb14wfk:~/Downloads$ uname -r
7.0.0-28-generic
leona@leonardo-katana15hxb14wfk:~/Downloads$ sudo apt install build-essential linux-headers-generic
build-essential is already the newest version (12.12ubuntu2.26.04.2).
linux-headers-generic is already the newest version (7.0.0-28.28).
Summary:                    
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 3
leona@leonardo-katana15hxb14wfk:~/Downloads$ git clone https://github.com/BeardOverflow/msi-ec && cd msi-ec
Cloning into 'msi-ec'...
remote: Enumerating objects: 2406, done.
remote: Counting objects: 100% (539/539), done.
remote: Compressing objects: 100% (54/54), done.
remote: Total 2406 (delta 515), reused 486 (delta 485), pack-reused 1867 (from 1)
Receiving objects: 100% (2406/2406), 4.27 MiB | 5.44 MiB/s, done.
Resolving deltas: 100% (1397/1397), done.
leona@leonardo-katana15hxb14wfk:~/Downloads/msi-ec$ which dkms
/usr/sbin/dkms
leona@leonardo-katana15hxb14wfk:~/Downloads/msi-ec$ sudo make dkms-install
dkms-3.2.2
mkdir -p /usr/src/msi_ec-0.13
cp /home/leona/Downloads/msi-ec/dkms.conf /usr/src/msi_ec-0.13
cp /home/leona/Downloads/msi-ec/Makefile /usr/src/msi_ec-0.13
cp /home/leona/Downloads/msi-ec/Makefile.vars /usr/src/msi_ec-0.13
cp /home/leona/Downloads/msi-ec/msi-ec.c /usr/src/msi_ec-0.13
cp /home/leona/Downloads/msi-ec/ec_memory_configuration.h /usr/src/msi_ec-0.13
sed -e "s/@VERSION@/0.13/" \
    -i /usr/src/msi_ec-0.13/dkms.conf
dkms add msi_ec/0.13
Creating symlink /var/lib/dkms/msi_ec/0.13/source -> /usr/src/msi_ec-0.13
dkms build msi_ec/0.13
Sign command: /usr/bin/kmodsign
Signing key: /var/lib/shim-signed/mok/MOK.priv
Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module(s)... done.
Signing module /var/lib/dkms/msi_ec/0.13/build/msi-ec.ko
dkms install msi_ec/0.13
Found pre-existing /lib/modules/7.0.0-28-generic/kernel/drivers/platform/x86/msi-ec.ko.zst, archiving for uninstallation
Installing /lib/modules/7.0.0-28-generic/updates/dkms/msi-ec.ko.zst
Running depmod... done.
echo msi-ec > /etc/modules-load.d/msi-ec.conf

And after that I reboot. Everything seems in order, when I go to edit my preferences for the driver in /sys/devices/platform/msi-ec the folder isn't there.

I also tried installing MControlCenter for a GUI version of the program, but it claims msi-ec is not installed.

Does anybody know if anything went wrong in the installation of the driver? Thank you!

I recently installed Kubuntu 26.04 on my Framework 16 laptop. When I installed Kubuntu, I created a user, foo, and set it to log in automatically on boot. Since then, I have created another user, bar. (Both foo and bar are administrative users.)

I would now like bar to be the user which is logged in automatically on boot, rather than foo. However, I can't find any way to change this. This article says to go to the "Startup and Shutdown" item in the left sidebar of System Settings. However, on my computer, there is no "Startup and Shutdown" item present in the left sidebar:

I've looked at other items that seem promising, such as "Screen Locking", "Users", "Autostart", and "Session", but none of them have a way to change the auto-login behavior.

How can I change it to log in "bar" instead of "foo"?

I'm using Xubuntu 26.04. The display brightness slider in the upper panel area is not working anymore. Moving it has no effect.

I added this command line:

xrandr --output eDP1 --brightness 0.7

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

Does anyone has an advice for this issue?

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

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

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

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

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

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

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

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

If I press F12 on boot to bring up the boot menu, Kubuntu is present. But when I press enter on it, the screen just blinks and nothing happens.

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

Output of efibootmgr from live USB is:

kubuntu@kubuntu:~$ efibootmgr 

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

Taking hints from the comments and from google AI mode, I figured that I need to install kubuntu on the new drive, but point to the efi partition on the original drive for mounting /boot/efi.

So this time, my install summary looks like this: Kubuntu install summary

Now, after restart, grub pops up, but still does not show me the boot options. This is the screen after restart: Grub Screen

What next?

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

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

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

Results of journalctl:

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

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

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

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

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

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

Suggested packages:
  bluez-meshd

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

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

I have disabled Secure Boot and run Bluetoothctl show:

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

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

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

iw reg get with both dongles in:

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

server@server-z87hd3:~$ 

iw reg get with only 6.0

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

server@server-z87hd3:~$ 

iw reg get with neither:

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

server@server-z87hd3:~$ 

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

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

This is the attempt after following your steps exactly.

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

Make file looks like this:

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

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

I'm having a problem with Ubuntu 26.04 LTS. After updating from 25.10 to 26.04 beta at first then to the 26.04 LTS and it started freezing, meaning it runs for about 10 seconds and then freezes for about 0.5 seconds. I watch YouTube and it freezes regularly. I do a speed test on the website, and it freezes for 0.5 sec after around 5-10 sec. I play on Steam and it freezes, but I can hear that the graphics card isn't working at the moment—it doesn't make the same noises it normally does. When watching YouTube or running speed tests on the website, the CPU temperature is a maximum of 70 degrees Celsius, and the GPU is 30 degrees Celsius. Everything works fine except for the freezing. My question is, how can I approach this? How can I diagnose the problem? Or what could be the cause?

Command result:

lspci -k | grep -A 3 -E 'VGA|3D|Display'
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 48 [Radeon RX 9070/9070 XT/9070 GRE] (rev c0)
    Subsystem: XFX Limited Device 8811
    Kernel driver in use: amdgpu
    Kernel modules: amdgpu

Update:

After reinstalling Ubuntu 26.04 LTS (clean install), the stutters still occur, i.e. the GPU and VRAM clock speeds drop to zero.

Best regards

Marek

I have installed the newest Ubuntu 26.04 LTF. I have activated my PRO version. And I have followed the Surface 7 Pro instructions on Zorins forum (They were the newest I could find, and have worked for me on other Ubuntu based instalations until now.)

You can see the setup here: https://help.zorin.com/docs/getting-started/set-up-microsoft-surface-device/

But when I follow those instuctions, and reboot my computer, I just get a text based login screen. And I can't get to the Ubuntu GUI from there.

What do I do wrong.

Would it be possible, that the Ubuntu install, checks for a Surface computer, and automatically sets up the kernal on install?

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?

I'm looking for help to get my Arvox AX900 USB wifi + BT 5.4 adapter to work on a fresh install of Ubuntu Server 25.10 (Kernel 6.17). I could not find vendor specific drivers, but I did find out that this specific hardware i.e. AIC 8800D80 has generic drivers that should work. In my case, I have tried downloading the drivers from Tenda's website as well as a git. Initially, they did not install because the OS was missing some basic packages primarily because I did not have a wired internet connection to my workstation. So, I downloaded the required packages on a different laptop and then copied them over and installed them. Post this, the driver did get installed successfully but even after a reboot, Ubuntu does not show an available Wifi adapter. I followed a blog to download the source files (which I did from the git), compile them on my Ubuntu and then installed them. However, the end result was the same. The Network Manager does not show any new Wifi adapter. Here are additional steps I have taken to check configurations:

• lsusb - shows the adapter as soon as I connect it
• dmesg - shows that the firmware was loaded on boot
• sudo iw list - does not give any output

I have also referred to various posts on serverfault, askubuntu, stackoverflow etc. to identify what I may be doing incorrectly and as per their comments, the adapter should work after following those steps. However, it hasn't helped in my case. Hence, I'm posting here for help. I'm new to the Linux world and am trying to learn to find my way around it. It will be very helpful if someone can guide me here as I want to avoid purchasing another wifi dongle (available ones are quite expensive).

Asking for my partner! We're both new to Linux, but I've never encountered this issue before on Ubuntu. We've managed to finally fulfill the Java dependency error we were getting, but haven't managed to figure this one out just yet. We've gotten this in the terminal, and are stumped from here:

The following packages have unmet dependencies: minecraft-launcher: Depends: libgdk-pixbuf2.0-0 (>= 2.22.0) but it is not installable

Unsure if it's any help, but they're working on a Framework laptop, and I'm troubleshooting from far away at the moment!

I've been informed to provide more information & while I'm not 100% sure what to provide here, I think this is probably one of the things we're looking for? (Do let me know if something else is needed! I'm a bit scrambled from staring at terminal errors for the last few hours.)

Unsatisfied dependencies:
minecraft-launcher : Depends: libgdk-pixbuf2.0-0 (>= 2.22.0) but it is not installable.
Error: Unable to satisfy dependencies. Reached two conflicting decisions:
1. minecraft-launcher:amd64=2.1.3 is selected for install
2. minecraft-launcher:amd64 Depends libgdk-pixbuf2.0-0(>= 2.22.0)
but none of the choices are installable:
[no choices]

Specs:

   OS: Ubuntu 25.10
   Firmware version: 03.04
   OS Type: 64-bit
   GNOME version: 49
   Hardware model: Framework laptop 12
   Processor: 13th Gen Intel Core i5-1334U x 12

Libby is an app to borrow ebooks and audiobooks from libraries. It is available for Android, iOS and Amazon appstore.

I installed Ubuntu in a convertible touchscreen laptop, and want to use it to read books from my library.

How to install Libby in Ubuntu?

I'm working remotely via SSH connection and need to use some GUI applications on the remote machine. I do not have an X-Server for X forwarding on my local machine, but a RDP client.

Can I somehow enable RDP via command line?

Usually one would do this in the Settings app in the "Sharing" tab.

I've installed the gnome-software package using apt (in Ubuntu 23.10, where gnome-software isn't the default software manager) and I've also installed gnome-software-plugin-flatpak that allows me to install flatpak packages using the gnome-software. Now I want to install apt packages using gnome-software, how can I do that? (snap and deb were there by default in gnome-software)

PROBLEM: can't connect to my Ubuntu server through RDP.

MSTSC RETURNS:

[Window Title] Remote Desktop Connection

[Content] Remote Desktop can't connect to the remote computer for one of these reasons:

1. Remote access to the server is not enabled
2. The remote computer is turned off
3. The remote computer is not available on the network

Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.

[Expanded Information] Error code: 0x204 Extended error code: 0x0

XRDP INSTALLATION PROCESS I USED:

1. sudo apt-get update
2. sudo apt install xfce4 xfce4-goodies xrdp net-tools xorg dbus-x11 x11-xserver-utils #I followed different installation guides in case the problem was caused by lacking some packages + I installed net-tools to check stuff with netstat
3. sudo systemctl status #checked that xrdp was running
4. sudo adduser xrdp ssl-cert
5. sudo systemctl restart xrdp
6. sudo ufw allow from any to any port 3389
7. sudo ufw allow 3389

SOLUTIONS I TRIED:

1. made sure that xrdp was listening to 3389 using netstat
2. made sure that 3389 port was opened
3. made sure that the VM port was opened in the VM hosting service I use
4. made sure that the xrdp.ini file didn't have incorrect setting inside
5. made sure use_vsocket was set to =false
6. made sure that automatic login was turned off
7. tried logging out and connecting through mstsc, got the same result
8. tried rebooting :)
9. went through xrdp logs with journalctl xrdp - seems like there was no connection

INFORMATION THAT MIGHT BE VALUABLE:

1. for connection I'm trying to use the default user "ubuntu" with sudo privileges which was created during VM set up
2. I'm new

My Lenovo computer offers SGX as an option in the BIOS menu. I am wondering if I should enable it on my on my Ubuntu 22.04 system.

Does Ubuntu utilize Intel's SGX feature?

Should I enable SGX for my Ubuntu system?

Currently I am using a Wi-Fi 6 PCIe card (Intel(R) Wi-Fi 6 AX200 160MHz) with the firmware 46.3cfab8da.0 op_mode iwlmvm loaded.

My connection's link speed shows as 54 Mb/s (5.7 GHz), even though it should be much faster. When I boot my computer to Windows 10 for example, I get a link speed of 833 Mb/s with a speed test clocking in at roughly 500-700 MB/s. On Ubuntu 20.04, the download speed is consistently capped at 22-23 Mb/s. My kernel version is 5.5 (I've also tried 5.4 and it did not change anything).

If there is any additional information I can provide, please let me know. Please also let me know if I should format my question/system information in a certain way to make it easier to troubleshoot.

Here is the output to 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 9 Series Chipset Family USB xHCI Controller
00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1
00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller
00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0)
00:1c.2 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 3 (rev d0)
00:1c.3 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 (rev d0)
00:1c.4 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 5 (rev d0)
00:1c.5 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 6 (rev d0)
00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1
00:1f.0 ISA bridge: Intel Corporation Z97 Chipset LPC Controller
00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
00:1f.3 SMBus: Intel Corporation 9 Series Chipset Family SMBus Controller
01:00.0 VGA compatible controller: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GP102 HDMI Audio Controller (rev a1)
03:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10)
04:00.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 41)
06:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller (rev 12)
07:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)

Things that I have tried so far

1. sudo modprobe iwlwifi 11n_disable=1
2. Changing the MTU of my wireless connection from 1500 to 1492 using ifconfig wlp7s0 mtu 1492 (without rebooting, only disconnect/reconnect). sudo ip link set dev wlp7s0 mtu 1492 also did not work (except switching my connection from 5.7ghz to 2.4 ghz).

I recently found an old disk with files in my ecryptfs-encrypted home folder that I want to recover. However I cannot boot into the system as it does not boots not. I need to attach the old disk to my new computer and recover the files from the CLI.

How can I get access to my old files?

I was having some problems booting into Ubuntu. After trying to reboot for sometime, I eventually opened the 4.4.0-31 recovery mode. while it was booting into recovery mode, it said that /dev/ubuntu-gnome-vg needs to fsck manually.

While this was going on the touchscreen for the computer was connecting and disconnecting repeatedly.

The screen was showing this:

usb 2-7: new full-speed USB device number 42 using using xchi_hcd
usb 2-7: New USB device found, idVendor=04f3, idproduct=016f
usb 2-7: New USB device strings: Mfr=4, Product =14, SerialNumber=0
usb 2-7: Product: Touchscreen
usb 2-7: Manufacturer: ELAN
usb 2-7: ep 0x2 - rounding interval to 64 microframes, ep desc
says 80 microframes 
usb 2-7: USB disconnect, device number 42. 

and then this repeats with the device being 43.

How do I stop this so that I can actually try and fix the problem on the disk. Also if you guys have some advice regarding /dev/ubuntu-gnome-vg needing to be fsck'd that be great.

I have Dolby Virtual Surround Sound 5.1 speakers with Tuba CineBass Subwoofer on Acer laptop (mine is 5951G but there is also bunch of models with similar configuration of speakers with/without subwoofer). In Windows it works and sounds amazingly after installing both Realtek drivers and Dolby software from Acer support site. In Ubuntu only 2-channel sound is working.

How can I enable virtual 5.1 sound or at least subwoofer?

This question exists as it fills a specific criterion. While you are encouraged to help maintain its answers, please understand that "big list" questions are not generally allowed on Ask Ubuntu and will likely be closed per the FAQ. More information on the software-recommendation tag.

What download managers are available for Ubuntu? Can you provide the link as well?