I am a newbie to Linux. Trying to find a compatible monochrome laser printer for Ubuntu 24.04 LTS. Have been on the following websites and have chatted with their reps:

• Lexmark
• Xerox
• HP
• Brother
• Kyocera

With the exception of Kyocera (didn't chat), all reps either told me none of their monochrome laser printers would work on Ubuntu 24.04 LTS or didn't answer any of my questions (only interested in meeting their sales quota).

I am perplexed at this point. It just doesn't make sense that the major printer manufacturers either don't train their sales force well or don't keep up with new distros.

What am I doing wrong?

Thanks All, Pascal

I downloaded it from the broadcom website followed all the rules i go to make the installer executable and i get this.

Since buying a new Ubuntu 26.04 LTS laptop I find that I cannot record a video online. At first I could not record videos for longer than 1 second, now I have got it to record video but there is no sound. I have tried VokscreenNG, Simple Screen Recorder, Kooha and the built-in system but nothing works. This is most annoying as I do a lot of online recording and now nothing. I wish I hadn't upgraded my system to 26.04, 22 was much easier. But please can anyone help with this basic requirement for screen recorders when using Wayland. It will be much appreciated for the whole community going by the other requests for similar problems.

I am fairly new to Linux. I'm running Ubuntu 26.04. Yesterday there was an update to Ubuntu which I was asked to install and restart. When I restarted, all apps had disappeared from my Show Apps screen.

The apps are all still there when I search for them, and I can run them all, they just don't show on the Show Apps screen.

I tried sudo update-desktop-database and sudo update-desktop-database -v. The terminal output is pasted below.

Search path is now: [/usr/share/ubuntu/applications, /usr/share/gnome/applications, /home/ashok/.local/share/flatpak/exports/share/applications, /var/lib/flatpak/exports/share/applications, /usr/local/share/applications, /usr/share/applications, /var/lib/snapd/desktop/applications]
File "/usr/share/ubuntu/applications/info.desktop" lacks MimeType key
File "/usr/share/ubuntu/applications/gnome-initial-setup.desktop" lacks MimeType key
File "/usr/share/ubuntu/applications/texdoctk.desktop" lacks MimeType key
Could not create cache file in "/usr/share/ubuntu/applications": Permission denied
Could not create cache file in "/usr/share/gnome/applications": Error opening directory ?/usr/share/gnome/applications?: No such file or directory
Could not create cache file in "/home/ashok/.local/share/flatpak/exports/share/applications": Error opening directory ?/home/ashok/.local/share/flatpak/exports/share/applications?: No such file or directory
File "/var/lib/flatpak/exports/share/applications/org.jellyfin.JellyfinServer.desktop" lacks MimeType key
File "/var/lib/flatpak/exports/share/applications/org.jellyfin.JellyfinDesktop.desktop" lacks MimeType key
File "/var/lib/flatpak/exports/share/applications/com.github.ADBeveridge.Raider.desktop" lacks MimeType key
Could not create cache file in "/var/lib/flatpak/exports/share/applications": Permission denied
Could not create cache file in "/usr/local/share/applications": Error opening directory ?/usr/local/share/applications?: No such file or directory
File "/usr/share/applications/kcm_bolt.desktop" lacks MimeType key
File "/usr/share/applications/gnome-printers-panel.desktop" lacks MimeType key
File "/usr/share/applications/nvidia-settings.desktop" lacks MimeType key
File "/usr/share/applications/gnome-notifications-panel.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.kiod6.desktop" lacks MimeType key
File "/usr/share/applications/kcm_kwindecoration.desktop" lacks MimeType key
File "/usr/share/applications/fortune.desktop" lacks MimeType key
File "/usr/share/applications/kcm_colors.desktop" lacks MimeType key
File "/usr/share/applications/nemo-autostart.desktop" lacks MimeType key
File "/usr/share/applications/kcm_mobile_wired.desktop" lacks MimeType key
File "/usr/share/applications/csd-automount.desktop" lacks MimeType key
File "/usr/share/applications/gnome-network-panel.desktop" lacks MimeType key
File "/usr/share/applications/gnome-language-selector.desktop" lacks MimeType key
File "/usr/share/applications/gnome-display-panel.desktop" lacks MimeType key
File "/usr/share/applications/gnome-color-panel.desktop" lacks MimeType key
File "/usr/share/applications/kcm_energyinfo.desktop" lacks MimeType key
File "/usr/share/applications/gnome-system-panel.desktop" lacks MimeType key
File "/usr/share/applications/gnome-privacy-panel.desktop" lacks MimeType key
File "/usr/share/applications/kcm_webshortcuts.desktop" lacks MimeType key
File "/usr/share/applications/kcm_solid_actions.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.partitionmanager.desktop" lacks MimeType key
File "/usr/share/applications/simple-scan.desktop" lacks MimeType key
File "/usr/share/applications/kcm_clock.desktop" lacks MimeType key
File "/usr/share/applications/kcm_mobile_hotspot.desktop" lacks MimeType key
File "/usr/share/applications/gnome-sharing-panel.desktop" lacks MimeType key
File "/usr/share/applications/balena-etcher.desktop" lacks MimeType key
File "/usr/share/applications/kcm_mobile_power.desktop" lacks MimeType key
File "/usr/share/applications/gnome-online-accounts-panel.desktop" lacks MimeType key
File "/usr/share/applications/kcm_baloofile.desktop" lacks MimeType key
File "/usr/share/applications/kcmspellchecking.desktop" lacks MimeType key
File "/usr/share/applications/geoclue-demo-agent.desktop" lacks MimeType key
File "/usr/share/applications/xdg-desktop-portal-xapp.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.Tecla.desktop" lacks MimeType key
File "/usr/share/applications/kcm_filetypes.desktop" lacks MimeType key
File "/usr/share/applications/org.freedesktop.Xwayland.desktop" lacks MimeType key
File "/usr/share/applications/kcm_virtualkeyboard.desktop" lacks MimeType key
File "/usr/share/applications/kcm_smserver.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.kdialog.desktop" lacks MimeType key
File "/usr/share/applications/kcm_touchscreen.desktop" lacks MimeType key
File "/usr/share/applications/gnome-sound-panel.desktop" lacks MimeType key
File "/usr/share/applications/kcm_mouse.desktop" lacks MimeType key
File "/usr/share/applications/kcm_activities.desktop" lacks MimeType key
File "/usr/share/applications/kcm_keys.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.klipper.desktop" lacks MimeType key
File "/usr/share/applications/kcm_trash.desktop" lacks MimeType key
File "/usr/share/applications/kcm_wallpaper.desktop" lacks MimeType key
File "/usr/share/applications/gnome-background-panel.desktop" lacks MimeType key
File "/usr/share/applications/yad-icon-browser.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.baloorunner.desktop" lacks MimeType key
File "/usr/share/applications/io.snapcraft.SessionAgent.desktop" lacks MimeType key
File "/usr/share/applications/kcm_kwin_effects.desktop" lacks MimeType key
File "/usr/share/applications/net.nokyan.Resources.desktop" lacks MimeType key
File "/usr/share/applications/kcm_networkmanagement.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.plasma-systemmonitor.desktop" lacks MimeType key
File "/usr/share/applications/kcm_keyboard.desktop" lacks MimeType key
File "/usr/share/applications/kcm_cellular_network.desktop" lacks MimeType key
File "/usr/share/applications/kcm_kgamma.desktop" lacks MimeType key
File "/usr/share/applications/gnome-search-panel.desktop" lacks MimeType key
File "/usr/share/applications/xdg-desktop-portal-gnome.desktop" lacks MimeType key
File "/usr/share/applications/hplj1020.desktop" lacks MimeType key
File "/usr/share/applications/gnome-keyboard-panel.desktop" lacks MimeType key
File "/usr/share/applications/kcm_animations.desktop" lacks MimeType key
File "/usr/share/applications/kcm_style.desktop" lacks MimeType key
File "/usr/share/applications/xdg-desktop-portal-gtk.desktop" lacks MimeType key
File "/usr/share/applications/kcm_plasmasearch.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.tweaks.desktop" lacks MimeType key
File "/usr/share/applications/kcm_cursortheme.desktop" lacks MimeType key
File "/usr/share/applications/kcm_sddm.desktop" lacks MimeType key
File "/usr/share/applications/cinnamon-display-panel.desktop" lacks MimeType key
File "/usr/share/applications/gnome-region-panel.desktop" lacks MimeType key
File "/usr/share/applications/kcm_kded.desktop" lacks MimeType key
File "/usr/share/applications/remmina-gnome.desktop" lacks MimeType key
File "/usr/share/applications/kcm_mobile_wifi.desktop" lacks MimeType key
File "/usr/share/applications/kcm_componentchooser.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.plasma.emojier.desktop" lacks MimeType key
File "/usr/share/applications/usb-creator-gtk.desktop" lacks MimeType key
File "/usr/share/applications/gnome-wacom-panel.desktop" lacks MimeType key
File "/usr/share/applications/kcm_kwin_scripts.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.kded6.desktop" lacks MimeType key
File "/usr/share/applications/kcm_about-distro.desktop" lacks MimeType key
File "/usr/share/applications/kcm_qtquicksettings.desktop" lacks MimeType key
File "/usr/share/applications/breezestyleconfig.desktop" lacks MimeType key
File "/usr/share/applications/gnome-about-panel.desktop" lacks MimeType key
File "/usr/share/applications/bluetooth-sendto.desktop" lacks MimeType key
File "/usr/share/applications/kcm_desktoppaths.desktop" lacks MimeType key
File "/usr/share/applications/system-config-printer.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.plasma.browser_integration.host.desktop" lacks MimeType key
File "/usr/share/applications/gnome-datetime-panel.desktop" lacks MimeType key
File "/usr/share/applications/update-manager.desktop" lacks MimeType key
File "/usr/share/applications/user-dirs-update-gtk.desktop" lacks MimeType key
File "/usr/share/applications/rygel.desktop" lacks MimeType key
File "/usr/share/applications/gparted.desktop" lacks MimeType key
File "/usr/share/applications/kcm_recentFiles.desktop" lacks MimeType key
File "/usr/share/applications/kcm_kwinxwayland.desktop" lacks MimeType key
File "/usr/share/applications/io.github.cboxdoerfer.FSearch.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.ksecretd.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.qrca.wifi.desktop" lacks MimeType key
File "/usr/share/applications/kaccess.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.Papers-previewer.desktop" lacks MimeType key
File "/usr/share/applications/gnome-online-accounts-gtk.desktop" lacks MimeType key
File "/usr/share/applications/org.cinnamon.ScreenSaver.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.keditbookmarks.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.goa-daemon.desktop" lacks MimeType key
File "/usr/share/applications/orca.desktop" lacks MimeType key
File "/usr/share/applications/gnome-wifi-panel.desktop" lacks MimeType key
File "/usr/share/applications/gnome-universal-access-panel.desktop" lacks MimeType key
File "/usr/share/applications/org.freedesktop.IBus.Panel.Extension.Gtk3.desktop" lacks MimeType key
File "/usr/share/applications/info.desktop" lacks MimeType key
File "/usr/share/applications/debian-xterm.desktop" lacks MimeType key
File "/usr/share/applications/gnome-applications-panel.desktop" lacks MimeType key
File "/usr/share/applications/gnome-initial-setup.desktop" lacks MimeType key
File "/usr/share/applications/kcm_splashscreen.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.Snapshot.desktop" lacks MimeType key
File "/usr/share/applications/org.freedesktop.IBus.Panel.Wayland.Gtk3.desktop" lacks MimeType key
File "/usr/share/applications/dropbox.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.bluedevilwizard.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.kcolorschemeeditor.desktop" lacks MimeType key
File "/usr/share/applications/kcm_landingpage.desktop" lacks MimeType key
File "/usr/share/applications/python3.14.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.knetattach.desktop" lacks MimeType key
File "/usr/share/applications/ibus-setup-table.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.Characters.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.Evolution-alarm-notify.desktop" lacks MimeType key
File "/usr/share/applications/kcm_pulseaudio.desktop" lacks MimeType key
File "/usr/share/applications/kcm_notifications.desktop" lacks MimeType key
File "/usr/share/applications/gnome-wellbeing-panel.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.kmenuedit.desktop" lacks MimeType key
File "/usr/share/applications/timeshift-gtk.desktop" lacks MimeType key
File "/usr/share/applications/kcm_kwin_virtualdesktops.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.discover.notifier.desktop" lacks MimeType key
File "/usr/share/applications/kwalletmanager5-kwalletd.desktop" lacks MimeType key
File "/usr/share/applications/kcm_fonts.desktop" lacks MimeType key
File "/usr/share/applications/kdesystemsettings.desktop" lacks MimeType key
File "/usr/share/applications/debian-uxterm.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.polkit-kde-authentication-agent-1.desktop" lacks MimeType key
File "/usr/share/applications/kcm_feedback.desktop" lacks MimeType key
File "/usr/share/applications/systemsettings.desktop" lacks MimeType key
File "/usr/share/applications/kcm_access.desktop" lacks MimeType key
File "/usr/share/applications/kcm_workspace.desktop" lacks MimeType key
File "/usr/share/applications/kcm_regionandlang.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.ksshaskpass.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.Logs.desktop" lacks MimeType key
File "/usr/share/applications/gnome-power-panel.desktop" lacks MimeType key
File "/usr/share/applications/org.freedesktop.IBus.Setup.desktop" lacks MimeType key
File "/usr/share/applications/gcr-prompter.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.qrca.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.Ptyxis.desktop" lacks MimeType key
File "/usr/share/applications/gnome-bluetooth-panel.desktop" lacks MimeType key
File "/usr/share/applications/gnome-users-panel.desktop" lacks MimeType key
File "/usr/share/applications/kcm_tablet.desktop" lacks MimeType key
File "/usr/share/applications/gnome-wwan-panel.desktop" lacks MimeType key
File "/usr/share/applications/kcm_touchpad.desktop" lacks MimeType key
File "/usr/share/applications/kcm_krunnersettings.desktop" lacks MimeType key
File "/usr/share/applications/kcm_powerdevilprofilesconfig.desktop" lacks MimeType key
File "/usr/share/applications/kcm_kwinoptions.desktop" lacks MimeType key
File "/usr/share/applications/gnome-multitasking-panel.desktop" lacks MimeType key
File "/usr/share/applications/cinnamon-network-panel.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.Terminal.desktop" lacks MimeType key
File "/usr/share/applications/org.freedesktop.impl.portal.desktop.kde.desktop" lacks MimeType key
File "/usr/share/applications/kcm_gamecontroller.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.plasma-interactiveconsole.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.Calculator.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.plasmashell.desktop" lacks MimeType key
File "/usr/share/applications/synaptic.desktop" lacks MimeType key
File "/usr/share/applications/kcm_kwintabbox.desktop" lacks MimeType key
File "/usr/share/applications/kcm_bluetooth.desktop" lacks MimeType key
File "/usr/share/applications/kcm_firewall.desktop" lacks MimeType key
File "/usr/share/applications/kcm_icons.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.plasmawindowed.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.Settings.desktop" lacks MimeType key
File "/usr/share/applications/kcm_screenlocker.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.Mahjongg.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.clocks.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.secretprompter.desktop" lacks MimeType key
File "/usr/share/applications/nm-connection-editor.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.plasma-fallback-session-save.desktop" lacks MimeType key
File "/usr/share/applications/gnome-mouse-panel.desktop" lacks MimeType key
File "/usr/share/applications/kcm_netpref.desktop" lacks MimeType key
File "/usr/share/applications/kcm_users.desktop" lacks MimeType key
File "/usr/share/applications/software-properties-drivers-lxqt.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.kwin.killer.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.knighttimed.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.kinfocenter.desktop" lacks MimeType key
File "/usr/share/applications/kcm_soundtheme.desktop" lacks MimeType key
File "/usr/share/applications/kcm_autostart.desktop" lacks MimeType key
File "/usr/share/applications/kcm_nighttime.desktop" lacks MimeType key
File "/usr/share/applications/kcm_desktoptheme.desktop" lacks MimeType key
File "/usr/share/applications/kcm_proxy.desktop" lacks MimeType key
File "/usr/share/applications/cinnamon-wacom-panel.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.Shell.Extensions.desktop" lacks MimeType key
File "/usr/share/applications/im-config.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.DiskUtility.desktop" lacks MimeType key
File "/usr/share/applications/kcm_lookandfeel.desktop" lacks MimeType key
File "/usr/share/applications/org.freedesktop.IBus.Panel.Emojier.desktop" lacks MimeType key
File "/usr/share/applications/kcm_nightlight.desktop" lacks MimeType key
File "/usr/share/applications/cinnamon-color-panel.desktop" lacks MimeType key
File "/usr/share/applications/org.kde.keditfiletype.desktop" lacks MimeType key
File "/usr/share/applications/kcm_breezedecoration.desktop" lacks MimeType key
File "/usr/share/applications/gnome-ubuntu-panel.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.Zenity.desktop" lacks MimeType key
File "/usr/share/applications/kcm_kscreen.desktop" lacks MimeType key
File "/usr/share/applications/org.gnome.Terminal.Preferences.desktop" lacks MimeType key
File "/usr/share/applications/muffin.desktop" lacks MimeType key
File "/usr/share/applications/slicksddm-customize.desktop" lacks MimeType key
File "/usr/share/applications/kcm_kwinrules.desktop" lacks MimeType key
File "/usr/share/applications/kcm_fontinst.desktop" lacks MimeType key
Could not create cache file in "/usr/share/applications": Permission denied
File "/var/lib/snapd/desktop/applications/snap-store_packagekit-session-installer.desktop" lacks MimeType key
File "/var/lib/snapd/desktop/applications/desktop-security-center_desktop-security-center.desktop" lacks MimeType key
File "/var/lib/snapd/desktop/applications/snapd-desktop-integration_snapd-desktop-integration.desktop" lacks MimeType key
File "/var/lib/snapd/desktop/applications/converternow_converternow.desktop" lacks MimeType key
File "/var/lib/snapd/desktop/applications/firmware-updater_firmware-updater.desktop" lacks MimeType key
File "/var/lib/snapd/desktop/applications/snap-store_show-updates.desktop" lacks MimeType key
File "/var/lib/snapd/desktop/applications/prompting-client_daemon.desktop" lacks MimeType key
File "/var/lib/snapd/desktop/applications/localsend_localsend.desktop" lacks MimeType key
File "/var/lib/snapd/desktop/applications/firmware-updater_firmware-updater-app.desktop" lacks MimeType key
File "/var/lib/snapd/desktop/applications/whatsapp-linux-app_whatsapp-linux-app.desktop" lacks MimeType key
Could not create cache file in "/var/lib/snapd/desktop/applications": Permission denied
The databases in [/usr/share/ubuntu/applications, /usr/share/gnome/applications, /home/ashok/.local/share/flatpak/exports/share/applications, /var/lib/flatpak/exports/share/applications, /usr/local/share/applications, /usr/share/applications, /var/lib/snapd/desktop/applications] could not be updated.

I'm pretty new to Ubuntu and haven't had any issues so far, until now. Around a week ago I was just playing some games on Steam, charged my laptop, and after it charged to 100% it hasn't moved one bit. I just watched a movie for 1 hour and a half, and it's still stuck at 100%. I checked for any battery issues with a terminal command and nothing seems out of the ordinary either. I'm just really confused, if anyone has any advice pls help

My laptop is a Lenovo ThinkPad E14 Gen 7

Update: I used the sudo apt install tlp and sudo tlp start commands, and right after restart I was already at 99%

Hello Ubuntu community.

I am currently following the course "LFS101" from linuxfoundation.org, but I am having trouble replicating the exercise from Lab 10.3 of Chapter 10 showing how to archive and back things up:

For example, the instruction commands are:

student:/tmp> tar cf /tmp/doc.tar /usr/share/doc
student:/tmp> tar zcf /tmp/doc.tar.gz /usr/share/doc
student:/tmp> tar jcf /tmp/doc.tar.bz2 /usr/share/doc
student:/tmp> tar Jcf /tmp/doc.tar.xz /usr/share/doc

student:/tmp> ls -lh /tmp/doc.tar*
-rw-rw-r-- 1 student student 85M Apr 17 10:34 /tmp/doc.tar
-rw-rw-r-- 1 student student 31M Apr 17 10:35 /tmp/doc.tar.bz2
-rw-rw-r-- 1 student student 34M Apr 17 10:34 /tmp/doc.tar.gz
-rw-rw-r-- 1 student student 28M Apr 17 10:36 /tmp/doc.tar.xz

On my Ubuntu 26.04 (server) VM the output of tar cf /tmp/doc.tar /usr/share/doc is:

tar: Removing leading '/' from member names
tar: /tmp/doc.tar: Cannot write: Disk quota exceeded
tar: Error is not recoverable: exiting now

The output of tar zcf /tmp/doc.tar.gz /usr/share/doc is similar but has additional messages:

tar: Removing leading '/' from member names
gzip: stdout: Disk quota exceeded
tar: /tmp/doc.tar.gz: Cannot write: Broken pipe
tar: Child returned status 1
tar: Error is not recoverable: exiting now

The output of tar jcf /tmp/doc.tar.bz2 /usr/share/doc in turn has:

tar: Removing leading '/' from member names
tar: Removing leading '/' from hard link targets
bzip2: I/O or other error, bailing out. Possible reason follows.
bzip2: Disk quota exceeded
        Input file = (stdin), output file = (stdout)
tar: /tmp/doc.tar.bz2: Wrote only 8192 out of 10240 bytes
tar: Child returned status 1
tar: Error is not recoverable: exiting now

And finally, the output of tar Jcf /tmp/doc.tar.xz /usr/share/doc is:

tar: Removing leading '/' from member names
tar: Removing leading '/' from hard link targets
xz: (stdout): Write error: Disk quota exceeded
tar: /tmp/doc.tar.xz: Wrote only 8192 out of 10240 bytes
tar: Child returned status 1
tar: Error is not recoverable: exiting now

Could someone help me figure out what this means? Something is failing even though I'm doing the exact thing the course is instructing me to, and I'm confused. Thanks!

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?

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!

EDIT 2: Installing msi-ec along with MControlCenter worked. Thank you for your help!

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?

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

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

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

I tried fixing the Intel power-saving stuff:

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

Forced deep sleep:

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

Enabled early KMS for the graphics driver:

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

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

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

System Details Report

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

Hardware Information:

• Hardware Model: Dell Inc. Latitude E7450

• Memory: 16.0 GiB

• Processor: Intel Core i7-5600U × 4

• Graphics: Intel HD Graphics 5500 (BDW GT2)

• Disk Capacity: 512.1 GB

Software Information:

• Firmware Version: A24

• OS: Ubuntu 26.04

• OS Build: (null)

• OS Type: 64-bit

• GNOME Version: 50

• Windowing System: Wayland

• Kernel Version: Linux 7.0.0-28-generic

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

After a few updates last week my pc wont shutdown. just stays on a black screen but hardware is on. I can dual boot to win10 and it shutdown or restarts just fine. Also, my wife has same exact hardware and software and she doesn't have same problem. Her PC reboots flawlessly.

Edit: the problem was with my motherboard's boost, not with kubuntu. Kubuntu will shutdown kubuntu, but some thing in the boost would mess with the final hardware shutdown and would stay hanging.

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.

Left speaker silent on Packard Bell Senna (Acer Gadget e10 ETBook) under Ubuntu 24.04

It is dual boot. Booting into windows, both speakers work fine.

How to fix so both speakers work?

Information below.

Hardware

• Model: Packard Bell Senna i5 AMG (internal codename: Acer Gadget e10 ETBook)
• Audio codec: Realtek ALC269VC
• Subsystem ID: 0x1e507036 (Acer vendor space; Packard Bell is an Acer subsidiary)
• HDA controller: Intel Alder Lake PCH-P HD Audio (8086:51c8, rev 01)
• Kernel: 6.17.0-35-generic (Ubuntu 24.04.4 HWE)
• OS: Ubuntu 24.04 LTS, default audio stack: PipeWire + WirePlumber

Symptoms

• The right internal speaker works normally.
• The headphone output (jack on right side) works normally.
• The left internal speaker produces no sound under any circumstances.
• This is a fresh Linux install; the right speaker and headphones work in the same dual-boot Windows install on the same hardware, so the speaker itself is functional. The issue is purely the Linux audio driver / routing.
• System is dual boot with windows. On windows all speakers work fine.

Codec layout (the root of the issue)

The ALC269VC in this chassis uses an asymmetric routing: the right speaker and the left speaker live on two completely separate paths that share neither DACs nor mixers. There is no single "Speaker" DAC.

DAC 0x03 (stereo) ---> mixer 0x0d (stereo) ---> pin 0x14  [right speaker, works]
DAC 0x02 (stereo) ---> mixer 0x0c (stereo) ---> pin 0x15  [headphone jack, works]
DAC 0x02 (stereo) ---> mixer 0x0f (MONO)  ---> pin 0x17  [left speaker, SILENT]

Key facts from cat /proc/asound/card0/codec\#0:

• Pin 0x17 is a Mono Amp-Out widget (wcaps 0x40050c).
• Pin 0x17 has a BIOS default of 0x40000000 ("[N/A] Line Out at Ext N/A", DefAssociation = 0x0) — i.e. the BIOS has it disabled.
• Pin 0x17 has Pincap 0x00000010: OUT only — no EAPD bit.
• Mixer 0x0f is Mono with two inputs: 0x02 (DAC 0x02) and 0x0b (vendor widget, used for routing mic/line-in to output).
• The right speaker pin 0x14's Connection: list is 0x0c 0x0d* — by default the driver selects mixer 0x0d (DAC 0x03).
• The "Speaker" ALSA control corresponds to DAC 0x03, the "Headphone" ALSA control corresponds to DAC 0x02.

What has been tried

1. model= quirks (Phase 1 of original plan)

/etc/modprobe.d/snd-hda-intel.conf:

options snd-hda-intel model=acer-aspire-8930g

After update-initramfs -u and reboot: only the right speaker plays. amixer still shows a single "Speaker" control; no new control is created for pin 0x17. The model= binds the codec but the path through pin 0x17 remains silent.

2. Runtime hda-verb fix (the verbs that the codec path needs)

With PipeWire stopped, the following script was run via sudo:

#!/usr/bin/env bash
set -eu
DEV=/dev/snd/hwC0D0
SYSFS=/sys/class/sound/hwC0D0

# Tell parser pin 0x17 is a speaker
echo "0x17 0x90170110" > "$SYSFS/user_pin_configs"
echo 1                 > "$SYSFS/reconfig"
sleep 2

# Enable pin 0x17
hda-verb "$DEV" 0x17 0x707 0x40    # Pin-ctls: OUT
hda-verb "$DEV" 0x17 0x3a8 0x00    # Amp-Out: unmuted

# Route DAC 0x02 to mono mixer 0x0f
hda-verb "$DEV" 0x0f 0x701 0x00    # Select input 0 (DAC 0x02)
hda-verb "$DEV" 0x0f 0x3a8 0x00    # Amp-In: unmuted

Result:

• The user_pin_configs + reconfig is accepted (no EBUSY once PipeWire is stopped).
• The codec state changes as expected:
  • Pin 0x17: Pin-ctls: 0x40: OUT, Amp-Out vals: [0x00]
  • Mixer 0x0f: input 0 (DAC 0x02) unmuted.
• A new ALSA mixer control appears: Simple mixer control 'Bass Speaker',0.
• speaker-test -c2 -t sine -f440 -l1 plays on the right speaker only. The left speaker is still silent.

3. Re-routing pin 0x14 to share DAC 0x02

To test whether the failure is that DAC 0x02 is not bound to the "Speaker" PCM stream, the script additionally does:

hda-verb "$DEV" 0x14 0x701 0x00    # Pin 0x14 connection: input 0 (mixer 0x0c, DAC 0x02)

After this, both pin 0x14 (right) and pin 0x15 (headphone) connect to mixer 0x0c, which is fed by DAC 0x02. Pin 0x17 already connects via mixer 0x0f to DAC 0x02. So a single stereo stream into DAC 0x02 would drive both speakers and the headphone.

Result: the right speaker still plays but only one channel, the left speaker remains silent.

What this tells us

The ALC269VC codec hardware is capable of driving both speakers; the runtime verbs do configure the pin 0x17 path correctly. The remaining question is which DAC receives audio during "Speaker" playback under the standard snd-hda-intel driver.

For this codec, a stereo "Speaker" stream is bound to DAC 0x03 (the "Speaker" DAC). DAC 0x02 is bound only to the "Headphone" output. No matter how the codec is re-routed, audio sent to the "Speaker" PCM reaches DAC 0x03 only, leaving DAC 0x02 — and therefore pin 0x17 — silent.

The "Speaker" PCM needs to be reconfigured to drive both DACs (e.g. as a 4-channel output with channel map to both DACs), or a PipeWire combined sink needs to fan audio to both Speaker and Bass Speaker simultaneously. The first option requires a kernel-side fixup; the second is a userspace configuration.

How to reproduce

1. Boot Ubuntu 24.04.4 with kernel 6.17.0-35-generic.
2. Confirm the right speaker works, left doesn't: speaker-test -c2 -t sine -f440 -l1
3. Confirm the codec layout: sudo cat /proc/asound/card0/codec\#0 | grep -E "0x14 |0x15 |0x17 |0x0c |0x0d |0x0f "
4. (Optional) Apply the runtime script above to see the Bass Speaker control appear and confirm the codec path can be enabled.

Information that would help debug

• The PCM stream binding during playback: cat /proc/asound/card0/stream0 while speaker-test is running.
• The DAC 0xf01 response during playback: sudo hda-verb /dev/snd/hwC0D0 0x02 0xf01 0x00 and the same for 0x03.
• Whether any existing model= quirk (e.g. acer-aspire-8930g for 2.1 speaker setups) is supposed to set up multi-DAC routing for this ALC269VC variant, and why it doesn't.

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:

• Ubuntu 26.04 (upgraded from 24.04)
• GNOME Shell 50.1 / Mutter 50.1
• Wayland session (no Xorg session available)
• Intel Alder Lake-N UHD Graphics (i915 driver)
• Three displays (all 1920×1080 @ 60Hz)

Symptoms:

• After about 10 minutes of uptime, GNOME Activities Overview becomes visually corrupted.
• Specifically, workspace thumbnails flicker immediately upon entering Overview (Super key or hot corner).
• The flickering is limited to Overview workspace thumbnails and GNOME top bar. Normal desktop, application windows remain stable and unaffected.
• Exiting Overview immediately returns the desktop to normal. Logging out and back in resolves the issue temporarily, but it returns in a few minutes, rebooting it returns after 10 or 15 minutes. No GPU resets, hangs, or DRM errors appear in journalctl.

I’ve tried:

• Kernel parameter: intel_idle.max_cstate=1 Appears to delay or partially change the symptoms, but the issue still occurs.
• Kernel parameter: i915.enable_dc=0 Initially seemed to reduce symptoms, but the issue still returned.
• Tested different kernels (including older kernel) No change in long-term behavior.
• Disabled a couple of third-party GNOME extensions (still using default Ubuntu extensions).

Observations:

• The issue does not affect application rendering or the desktop outside of Activities Overview.
• It appears only after extended uptime (hours), not immediately after login. - Update - this occurs sporadically, sometimes 10 minutes and some boots it would take a few hours.
• The issue is reproducible across reboots and kernel versions.
• No relevant errors in journalctl related to i915, DRM, or GPU resets.

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.

Update (Aug 1st):

After recent kernel and system updates the workaround in my last update quit being viable for me as the issue started returning after about 15 minutes. I read somewhere that changing from fixed to VRR on one or all of your displays might help, only one of my displays supports VRR so I tried that and noticed it immediately stopped the 3003/gbm error flood and flickering and lasted about 17 hours before recurring. When it did, I simply toggled it back off and got another 10 hours or so of error/flicker free uptime. So I then worked with ChatGPT and Google AI to create a script to automate the toggling of VRR for my one monitor that supports it. After several trials and failures I finally got a script that automates this for me and provides a workaround I don't have to manage, I simply let it run in a terminal and check the output to see how many times it has had to execute, I'm currently at 2 days of uptime and the script has executed 6 times sporadically, keeping the canvas stable and flicker free.

To bypass modern GNOME 50 D-Bus sandbox restrictions and resolve the MetaDrmBufferGbm leak without dropping the desktop session, you can force a full hardware graphics pipeline modeset by simultaneously re-asserting your entire multi-monitor coordinate matrix.Below is an automated Bash script that monitors journalctl for the gbm_surface_lock_front_buffer failed flood strings. Once triggered, it uses gdctl to instantly toggle between an equivalent VRR and Fixed refresh rate canvas matrix layout. This forces a clean hardware flush and releases the stale color buffers seamlessly without any visual panel blinks or interface stutter. Adjust the gdctl screen strings to match your unique hardware topology.

#!/bin/bash
START_TIME=$(date +"%b %d %H:%M:%S")
echo "$START_TIME 🚀 Auto-Purge Service started. Monitoring for pesky Mutter 50 buffer floods..."

TOGGLE_STATE=0
COUNT=0
THRESHOLD=3

# We stream live into a reading descriptor
exec 3< <(journalctl -b -f -n 0 | grep --line-buffered "gbm_surface_lock_front_buffer failed")

while read -r line <&3
do
    ((COUNT++))
    
    if [ $COUNT -ge $THRESHOLD ]; then
        LOG_TIME=$(date +"%b %d %H:%M:%S")
        echo "$LOG_TIME 🚨 Buffer leak flood detected ($COUNT errors)! Curses!!! Triggering REAL hardware pipeline reset..."
        
        if [ $TOGGLE_STATE -eq 0 ]; then
            gdctl set --logical-monitor --monitor HDMI-2 --mode "1920x1080@60.000" --scale 1.0 --x 1920 --y 1080 --logical-monitor --monitor HDMI-1 --mode "3840x2160@60.000" --scale 2.0 --x 916 --y 0 --logical-monitor --monitor DP-1 --mode "3840x2160@59.997" --scale 2.0 --x 0 --y 1080 --primary > /dev/null 2>&1
            TOGGLE_STATE=1
            echo "$LOG_TIME 🔄 gdctl: Entire layout flipped to FIXED mode -> Buffers Purged!"
        else
            gdctl set --logical-monitor --monitor HDMI-2 --mode "1920x1080@60.000" --scale 1.0 --x 1920 --y 1080 --logical-monitor --monitor HDMI-1 --mode "3840x2160@60.000" --scale 2.0 --x 916 --y 0 --logical-monitor --monitor DP-1 --mode "3840x2160@59.997+vrr" --scale 2.0 --x 0 --y 1080 --primary > /dev/null 2>&1
            TOGGLE_STATE=0
            echo "$LOG_TIME 🔄 gdctl: Entire layout flipped to VRR mode -> Buffers Purged!"
        fi
        
        echo "$LOG_TIME ⏳ Entering a 30 second Cool Breeze Mode..."
        sleep 30
        
        # GHOST PURGE: Read and immediately throw away any backlog lines left over from the flood
        while read -t 0.1 -r ghost_line <&3; do
            : # Doing nothing dumps the line directly into the trash bin
        done
        
        COUNT=0
        RESUME_TIME=$(date +"%b %d %H:%M:%S")
        echo "$RESUME_TIME 🟢 Cool Breeze Mode finished. Resuming fresh active monitoring..."
    fi
done

Use code with caution.

If one of the displays does not support VRR the same result might be achieved by simply changing one display between 60.000 Hz and 59.940 Hz but I haven't tried that as the script above is working great for my situation.

If this quits working for me after additional kernel/system updates or if this is no longer needed I will update this thread, but for now this works great for me.

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

Something strange.

2 days ago, I used Startup Disk Creator (SDC) to prepare a USB Drive for an Ubuntu 24.04.1 install (on my 22.04). The USB stick is a USB-C (USB 3) 64GB drive.

That created the usual bootable Ubuntu install partition + another ext4 partition named writable using the remaining space, that's convenient to move data using that extra partition.

Today I used again SDC on a USB-A (USB 3) 32 GB drive (still on my 22.04). But this time it didn't use the remaining space (~23GB) to create a writable partition. The 23 GB is lost.

So I thought it's maybe because 32 GB is too "small", or maybe because it's USB-A...

To be sure, I erased the initial 64 GB USB-C drive (dd...) and run SDC again ...

This time it didn't create the writable partition anymore...

Are there other criteria to consider (or it's random??)

-- edit --

1. I realize that maybe (don't remember) I only mounted the USB drive on the newly installed 24.04.1 system (thanks to that drive), and 24.04 may show a partition that 22.04 doesn't?

2. Or, another possibility, the writable partition is created on the USB drive during the install?

Can someone please confirm 1. or 2. (or ...)

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)

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?

I tried to uninstall Audio Recorder by doing: sudo apt-get remove audio recorder or audiorecorder but I got the following message:

'Unable to locate package audiorecorder'

Could you help please.

The way it was install was sudo apt-get install audio recorder.

Thank you, Selda

I recently got Lambda Tensorbook with Ubuntu 20.04. I have audio devices installed (screenshots below), but the audio does not work, unfortunately.

I noticed that it's a known issue, so while I didn't understand most of the codes, I tried all the potential solutions I could find online - from sudo apt update to reset/reboot ALSA and PulseAudio to changing element speaker in analog-output-lineout.conf from off to on through /usr/share/pulseaudio/alsa-mixer/paths/, but to no avail.

Whenever I play the audio now, I do see the soundbar move in pavucontrol, but I still don't receive the sound with or without earphones/HDMI cable (photo below). I have spent days trying to work on this problem, but I still could not figure out any solution; thus, I will appreciate any leads on this. Thank you!

Audio driver (1/2):

Audio driver (2/2):

Pavucontrol:

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'm on vanilla Ubuntu 18.04.3 LTS.

I just got a CadMouse Pro Wireless. This mouse has two modes - it can be used in wireless mode via a USB receiver dongle, or it can be used in wired mode by plugging it directly into the computer via a microUSB cable.

In wireless mode, it works fine.

In wired mode, after plugging it in, the following happens:

• For the first 2 - 3 seconds, it works fine.
  • When I physically move the mouse, the cursor on the screen moves appropriately.
  • When I physically click the buttons, the on-screen interface elements (buttons, menus, etc) respond appropriately.
• After 2 - 3 seconds, it stops working.
  • When I physically move the mouse, the cursor on the screen doesn't move.
  • When I physically click the buttons, on-screen interface elements don't respond at all.

I've verified the mouse works fine in both modes in Windows 10 and macOS.

Here's the dmesg output when plugging in the mouse:

daniel@ubuntu:~$ dmesg -w
[10758.269137] usb 1-3: new full-speed USB device number 10 using xhci_hcd
[10758.608911] usb 1-3: New USB device found, idVendor=256f, idProduct=c654, bcdDevice= 1.06
[10758.608913] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[10758.608915] usb 1-3: Product: CadMouse Pro Wireless
[10758.608916] usb 1-3: Manufacturer: 3Dconnexion
[10758.635675] input: 3Dconnexion CadMouse Pro Wireless as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3/1-3:1.0/0003:256F:C654.001C/input/input44
[10758.636070] hid-generic 0003:256F:C654.001C: input,hidraw0: USB HID v1.11 Mouse [3Dconnexion CadMouse Pro Wireless] on usb-0000:03:00.0-3/input0
[10758.648184] input: 3Dconnexion CadMouse Pro Wireless as /devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3/1-3:1.1/0003:256F:C654.001D/input/input45
[10758.648408] hid-generic 0003:256F:C654.001D: input,hiddev0,hidraw1: USB HID v1.11 Multi-Axis Controller [3Dconnexion CadMouse Pro Wireless] on usb-0000:03:00.0-3/input1

No further messages appear after the mouse stops working.

Here's the lsusb output after plugging in the mouse:

daniel@ubuntu:~$ lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 005: ID 05ac:024f Apple, Inc. 
Bus 005 Device 004: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
Bus 005 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 005 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 013: ID 256f:c654  
Bus 001 Device 003: ID 1b1c:0c04 Corsair 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

256f:c654 is the CadMouse Pro.

(the Logitech receiver is for a different, unrelated mouse that works fine. I observe the same behavior for the CadMouse whether or not the Logitech receiver is plugged in).

I've also been trying to approach this via the HID API via cadmousectl, but haven't had much success there because HID API can see but not open the CadMouse - see GitHub issue for more information.

Any ideas how I can get the mouse to not stop responding after 2 - 3 sec? Thanks.

I have cloned from the Ubuntu family iso files to USB pendrives, and the result has been live (live-only) drives, where nothing can be saved past shutdown and reboot.

But an Ubuntu 19.10 live drive cloned from the iso file creates and writes to a casper-rw partition. It seems to be a new feature.

• How can this happen and how can I avoid that and get a live-only drive?

“No Wi-Fi adapter found” is the message I got after installing Ubuntu 17.10.

With the following command line lspci -nnk | grep -iA3 net, I got the following message. How could I fix that issue?

Here is the error shown in the settings:

Is it possible to open MS OneNote files under Linux?

At least read-only?

I have a problem where if I turn on the computer I tried to boot to Kubuntu, it just takes me to a black screen. It sticks there with no output and no hint of what's going on except that the Caps Lock indicator light on my keyboard flashes on and off (weird, right?)

If I then turn off the computer (by holding down the power button for a few seconds), and turn it back on, I get a boot menu where I can choose 'Advanced options for Ubuntu', and that lists different versions, recovery modes, some of which work just fine.

That's what I've bee doing for the two weeks or so I've had this problem, and it worked until just now. The alternative options only booted me into the command line. I was able to fix this with this solution, so now I'm typing this from my desktop.

I'm reluctant to turn off the computer in case it happens again, and I'd like to just tear out the root of the problem.

Kubuntu boots to a black screen with the following error messages.

[    0.528611] EDD information not available.
[    0.530345] PM: Hibernation image not present or could not be loaded.
[    0.532079] md: Waiting for all devices to be available before autodetect
[    0.533721] md: If you don't use raid, use raid=noautodetect
[    0.535830] md: Autodetecting RAID arrays.
[    0.537468] md: Scanned 0 and added 0 devices.
[    0.539110] md: autorun ...
[    0.540769] md: ... autorun DONE.
[    0.542435] VFS: Cannot open root device "mapper/kubuntu--vg-root" or unknown-block(0,0): error -6
[    0.544121] Please append a correct "root=" boot option; here are the available partitions:
[    0.545812] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    0.547512] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.4.0-65-generic #86-Ubuntu
[    0.549222] Hardware name: LENOVO 80G0/Lancer 5A6, BIOS A7CN40WW 07/18/2014
[    0.550945]  0000000000000086 000000009b7de47d ffff88017a403de8 ffffffff813f8743
[    0.552706]  ffffffff81ca4618 ffff88017a403e80 ffff88017a403e70 ffffffff8118d367
[    0.554481]  ffff880100000010 ffff88017a403e80 ffff88017a403e18 000000009b7de47d
[    0.556229] Call Trace:
[    0.557931]  [<ffffffff813f8743>] dump_stack+0x63/0x90
[    0.559674]  [<ffffffff8118d367>] panic+0xd3/0x215
[    0.561400]  [<ffffffff81f5e576>] mount_block_root+0x201/0x294
[    0.563126]  [<ffffffff81f5e66e>] mount_root+0x65/0x68
[    0.564842]  [<ffffffff81f5e7ab>] prepare_namespace+0x13a/0x172
[    0.566557]  [<ffffffff81f5e21b>] kernel_init_freeable+0x1e9/0x212
[    0.568263]  [<ffffffff8182ff40>] ? rest_init+0x80/0x80
[    0.569959]  [<ffffffff8182ff4e>] kernel_init+0xe/0xe0
[    0.571625]  [<ffffffff8183ca0f>] ret_from_fork+0x3f/0x70
[    0.573263]  [<ffffffff8182ff40>] ? rest_init+0x80/0x80
[    0.574951] Kernel Offset: disabled
[    0.576541] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I have deleted a USB disk using GParted. I am trying to create a new disk using the unallocated space, and I found this message.

Can't write to /dev/sdb, because it is opened read-only.