I installed Lubuntu on an Acer laptop a while ago. It is not dual booted, though it had Windows on it before Lubuntu. It is also encrypted if that matters.

I am unable to access any boot functions other than grub. I have tried every button, even the combination to factory reset the computer, but it does not work. Grub and Lubuntu boot fine.

Using grub to access Recovery mode I tried systemctl reboot --firmware-setup to which I got the response: Cannot indicate to EFI to boot into setup mode: Firmware does not support boot into firmware.

I searched online for a while, and the only forum I found with something I could try had this command: [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS to which I got the response BIOS, which is likely my problem, but as the OP of that forum did not get that response, I am unsure of what to do from here.

I'm running Ubuntu 20.04 on a SanDisk 2 TB External SDD.

I'm trying to install Ubuntu 26.04 to both new SanDisk 2 TB and 4 TB external SDDs using the live version on the installation media.

The installation media is a 128 GB PNY USB thumb drive. I'm using the provided install application.

The drive successfully installs to the internal 1 TB SDD on my OMEN laptop.

When I try to install to the new out of the box SanDisks, I get the following error shown in curtain-install.log files:

For the 2 TB:

Disk /dev/sdb: 1.82 TiB, 2000365371904 bytes, 3906963617 sectors
Disk model: Extreme Pro 55AF
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 2097152 bytes

>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 9E39D798-C9A3-400C-A979-C3C238C5E55F).
/dev/sdb1: Sector 2048 already used.
Failed to add #1 partition: Numerical result out of range
Leaving.

And for the 4 TB drive:

Running command ['sfdisk', '--no-reread', '/dev/sda', '--no-tell-kernel'] with allowed return codes [0] (capture=False)
Disk /dev/sda: 3.64 TiB, 4000753467904 bytes, 7813971617 sectors
Disk model: Extreme Pro 55AF
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 2097152 bytes

>>> Script header accepted.
>>> Created a new GPT disklabel (GUID: 2DACFC5F-1F5E-448E-B73D-CA48ECCD5962).
/dev/sda1: Sector 2048 already used.
Failed to add #1 partition: Numerical result out of range
Leaving.

Any help would be appreciated. Or do I just buy a different brand of SDD?

I am trying to run a Windows 10 VM through VirtualBox. When I try to run it, I get an error message telling me the kernel driver is not set up or installed, and to run modprobe vboxdrv as root. Doing so gives me an error message saying that

'vboxdrv' could not be inserted because the key was rejected by the service.

Unfortunately, I can't seem to find any info on how to sign the keys on Ubuntu 26.04, so any help is appreciated.

The VM starts and runs just fine if I disable Secure Boot, but I'm not proficient enough with computers to know if leaving that off is safe for my system.

I downloaded a bootable Ubuntu for my HP ProDesk 600 G3, however it doesn't load. It keeps getting stuck during package get 5. Can someone please let me know which version will work with my mini PC? I am not installing Ubuntu. I'm using it to install Home Assistant on a bare storage drive.

Upgraded from 20.04 -> 22.04 -> 24.04
All browsers are SNAFU
Chrome and Opera display is a totally cocked. They're flickering or all pixeled out randomly. It barely works. I try typing anything into the search field, and I barely can type anything.

Firefox works mostly except a few times a day the entire display goes black and then acts as if I'm logged out and I log back in. Or it just stay black for over 5 minutes, so I unplug the power and battery and wait another 5 minutes to turn the entire laptop back on.

I did this:

whereis firefox

firefox: /usr/bin/firefox /snap/bin/firefox

firefox removes

whereis firefox 
/usr/bin/firefox

sudo snap remove --purge firefox
snap "firefox" is not installed

sudo apt install firefox
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
firefox is already the newest version (1:1snap1-0ubuntu5).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

sudo apt autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

sudo apt clean

snap install firefox  
firefox 152.0.5-1 from Mozilla✓ installed  

I guess I just have to put up with the display blanking out daily. At least now can read a window and type.

I have a Dell Latitude X200 Model PP03S.

It is currently running Ubuntu 2.6.38-8-generic. Is there a download available that I can use to boot from USB?

I tried to update my UEFICA and it says I don't have permission. I have tried a bunch of things I saw online but im not a computer guy like that. Please someone help I think it's slowing my pc down

I have an HP Victus 15-fb3xxx (Ryzen 7 7445HS, RTX 3050 laptop, BIOS F.14) running Ubuntu 26.04 (kernel 7.0.0-27-generic). The system freezes completely (hard freeze, requires forced shutdown) consistently when booting with the charger connected, even without any heavy workload.

In journalctl -b -1 -p err from the boot right before the freeze, I consistently see this:

kernel: No irq handler for 1.55
kernel: No irq handler for 2.55
[...]
kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Index (0x000000032) is beyond end of object (length 0x32) (20251212/exoparg2-393)
kernel: ACPI Error: Aborting method \_SB.WMID.WQBZ due to previous error (AE_AML_BUFFER_LIMIT) (20251212/psparse-529)
kernel: ACPI Error: Aborting method \_SB.WMID.WQBE due to previous error (AE_AML_BUFFER_LIMIT) (20251212/psparse-529)

WQBZ/WQBE appear to be HP-proprietary WMI methods related to temperature/power-mode reporting (also queried by the NVIDIA driver via PlatformRequestHandler, which in a separate log reports failed to get target temp from SBIOS).

I've already ruled out the WiFi driver (RTL8852BE-VT, rtw89_8852bte module) as the cause of this specific freeze — it had a separate, unrelated power-save-mode bug that I already fixed with rtw89_core.disable_ps_mode=1 via GRUB, and it no longer shows up in recent logs.

Concrete questions:

• Has anyone with an HP laptop (Victus, Omen, or similar) seen this exact AE_AML_BUFFER_LIMIT error on the WQBZ/WQBE methods, and correlated it with freezes specifically when the charger is connected/detected?
• Is there a kernel parameter or a way to blacklist the hp_wmi module that mitigates this without losing critical functionality (fan control, function keys)?
• Has HP fixed this ACPI table bug in any BIOS version newer than F.14 for this laptop line?

Happy to attach a full acpidump if that helps diagnose it further.

Update (July 10):

Some important corrections and new findings since posting:

• The charger is NOT the trigger. I initially correlated the freeze with the charger, but it also happens on battery, with no charger connected, after ~40 minutes of normal uptime. So the charger connection was a red herring — please disregard that part of the title.

• NVIDIA D3 power-state failure found. On one freeze I caught this on screen: nvidia 0000:01:00.0: Unable to change power state from D3hot to D0, device inaccessible (plus the same for snd_hda_intel and an nvidia-modeset HDMI-0 pixel clock error). I mitigated it with nvidia.NVreg_DynamicPowerManagement=0x00 in GRUB (confirmed Runtime D3 status: Disabled), but the freeze still occurs, so this was a symptom, not the root cause.

• The freeze leaves no trace in the local journal. journalctl -b -1 simply cuts off mid-activity with no error, oops, or panic — a silent hard hang. To capture it, I've set up netconsole / live journal streaming to a second machine over the network. Still waiting to catch a freeze with usable output.

• The ACPI AE_AML_BUFFER_LIMIT errors on WQBZ/WQBE remain present in every boot regardless of the mitigations above.

Current GRUB cmdline: rtw89_core.disable_ps_mode=1 rtw89_pci.disable_aspm_l1=1 rtw89_pci.disable_aspm_l1ss=1 pcie_aspm=off nvidia.NVreg_DynamicPowerManagement=0x00

Will update again once I capture the hang over netconsole and/or after testing noapic and a BIOS update to F.15.

Update 2 (July 10, later):

Caught a hard freeze with actual output on screen this time (previously it was a silent hang with nothing in the local journal). The screen showed:

kernel: nvidia 0000:01:00.0: Unable to change power state from D3hot to D0, device inaccessible kernel: snd_hda_intel 0000:01:00.1: Unable to change power state from D3hot to D0, device inaccessible nvidia-modeset: ERROR: GPU:0: Failure reading maximum pixel clock value for display device HDMI-0. kernel: BUG: unable to handle page fault for address: ffffcb14037700d0

So the D3hot→D0 resume failure I mentioned in Update 1 isn't just a cosmetic error — it culminates in a real kernel page fault (likely nvidia-modeset dereferencing an invalid pointer after the device dropped off the PCI bus), which is what causes the full hang.

Root cause of the gap: nvidia.NVreg_DynamicPowerManagement=0x00 (which I'd already set) only disables NVIDIA's own internal power management — it does NOT disable the kernel's generic PCI runtime power management, which is a separate control. Checking:

cat /sys/bus/pci/devices/0000:01:00.0/power/control

returned auto, meaning the kernel could still autosuspend the GPU independently of the NVIDIA driver setting.

Fix applied: forced it to on and made it persistent via udev:

echo on | sudo tee /sys/bus/pci/devices/0000:01:00.0/power/control

/etc/udev/rules.d/99-nvidia-no-pm.rules: SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{power/control}="on"

Currently monitoring to see if this closes the gap. Also using netconsole/live journal streaming to a second machine to catch any future freeze with full context, since local journalctl doesn't survive a hang this violent.

I have A Laptop

Lenovo ThinkPad Xi Yoga 3rd Model 20LD001GCA

Bus 001 Device 004: ID 06cb:009a Synaptics, Inc. Metallica MIS Touch Fingerprint Reader

and ubuntu dose'nt see the reader...???

Please help me it was working with Windows. What to do to get it to work...

~~I've set up my IP and Gateway but can't ping my router or get to the internet.~~

Having used Xenix, Unix and Linux for many years, why is it harder now?

My screen resolution has defaulted to 800 x 600 after an update and I cannot change it. I have an Nvidia 3060 GPU.

i installed ubuntu 24.4.04 on my lenovo yoga 7a and it doesn't recognize the touchscreen. the only thing that happens when i flip the screen is that the physical keypad isn't working anymore I couldn't find anything on this device + my ubuntu version:/

My random cheap USB mouse (cabled not Bluetooth) stops working for a second or two when I flick too much. It doesn't seem to be due to load because it happens even right after boot.

I've been using Ubuntu 24.04 for some time, but it didn't have this issue until now.

It gives errors like this when using dmesg.

[   33.495875] usb 1-2: reset low-speed USB device number 2 using xhci_hcd
[   42.341612] usb 1-2: reset low-speed USB device number 2 using xhci_hcd

I tried:

• Disabling autosuspend

• Cleaning the mouse

• Switching to Wayland and back

• Switching USB ports

• Lowering polling rate

Does anyone has idea on how to fix it, or should I just reinstall Ubuntu and switch to Ubuntu 26.04 while I'm at it?

How do increase Bash argument buffer size? I do want to pass 2 million files in a directory as a file and I'm getting the `too many arguments' error:

<any-program> \
  "${PWD}/"*

So, I'm looking at starting to transition over to a linux system on my MacBook Air which uses an M3 chip. On the hard drive of the computer I have more than 20 GB left of storage, and I've heard Linux is pretty lightweight so dual booting is actually more feasible than, say, macOS+Windows. Is it possible to install Ubuntu without affecting anything on my macOS disk, so that the only difference is that at power-on I get a choice between macOS and Ubuntu and if I choose macOS it would be exactly the same as it is right now? How do I do that? (For context, I currently have Sonoma 14.3 installed).

Is a better option to download Ubuntu on a different hard drive or USB stick and run it from there so I don't have to deal with partitioning?

This a physical system running Ubuntu 26.04 Desktop (GNOME/Wayland). It has been regularly upgraded every six months through every Ubuntu Desktop release from 18.10 to 26.04. I also have a similar Ubuntu Desktop virtual machine running in VirtualBox with a similar configuration, and it exhibits the same behavior.

This does not appear to be caused by a user-specific configuration, as I reproduced the problem with a newly created user account. Finally, I also tested in a live Ubuntu 26.04 session by booting a VirtualBox virtual machine from the Ubuntu 26.04 ISO image, and the problem persists.

I do not remember exactly when the problem started, but I strongly suspect it is related to the transition from X.Org to Wayland, which occurred several non-LTS releases ago.

I have tested many Qt applications (krename, notepadqq, one custom of my own, etc.). Under Wayland, all Qt application windows and dialogs are rendered without the expected window borders or drop shadows. As a result, they blend into the background and are difficult to distinguish. In contrast, GNOME/GTK applications have the expected window borders and shadows and stand out clearly from the background.

If I set the QT_QPA_PLATFORM=xcb environment variable before starting a Qt application, the windows are displayed as expected, with the same borders and shadows as GTK applications.

The screenshot below shows krename started as

$ krename &

on the left, and

$ QT_QPA_PLATFORM=xcb krename &

on the right.

Is this a known bug? Is there something that can be done on top of the default system installation or configuration that will solve this problem?

System info:

• Framework 13 AMD (Ryzen), Wayland session (GNOME on Ubuntu 26.04 "resolute")
• Fresh Ubuntu install, ~1 week old
• Issue previously occurred on Ubuntu 24.04 on the same laptop and was "fixed" only by a full OS reinstall — it has now returned identically on the fresh install

Symptoms:

• Icons in the GNOME app grid duplicate themselves repeatedly (seen 20-40+ copies of the same app)
• Confirmed NOT caused by duplicate .desktop files on disk — checked both ~/.local/share/applications/ and /usr/share/applications/, only one file exists per affected app
• Happens specifically after (re)installing/launching certain apps — most recently reproduced by installing Steam via the official .deb (steam-installer package), which caused ~24 duplicate Steam icons to appear immediately after first launch
• Previous occurrence (on the old install) affected a custom GNOME extension I built, plus two other apps installed via .desktop files in ~/.local/share/applications/

What I've tried:

• Confirmed dpkg --print-foreign-architectures / apt install completed with no errors
• Checked for duplicate .desktop files (none found)
• About to try: dconf reset -f /org/gnome/shell/app-picker-layout (have not yet confirmed if this fixes it or just temporarily clears it)

Question: Is there a known root cause for org/gnome/shell/app-picker-layout duplicating entries on re-registration of an app, rather than just deduplicating? And is there a way to prevent this from recurring, since a full OS wipe did NOT permanently fix it (it returned after restoring my home folder from backup) — I suspect the corrupted dconf database itself got carried over in the restore rather than being regenerated fresh. Is app-picker-layout stored anywhere outside ~/.config/dconf/user that I should be excluding from backups?

Any pointers to the relevant GNOME Shell bug tracker issue (if this is already known) would also help.

I'm running Ubuntu 22.04.5 LTS and recently installed FireFox 152 through the apt install channel.

When I open Settings/About Firefox, I see the Firefox updates is set to "Updates are managed by your operating system." There doesn't seem to any longer be a setting to check for updates manually or to notify me that an update is available so that I can chose when to do the update.

I opened about:config and changed app.update.auto from True to False, but that had no effect.

I would like to be able to disable the automatic updates so that I have control over when the updates happen. What are the steps to do this?

Additional info: Prior to today I was using Snap to update Firefox. Something went haywire with the auto update that broke Firefox, so I no longer care to use Snap.

More info: I added a config file to /etc/apt/preferences.d so that firefox should no longer be using snap.

$ apt policy firefox
firefox:
  Installed: 152.0.4+build1-0ubuntu0.22.04.1~mt1
  Candidate: 152.0.4+build1-0ubuntu0.22.04.1~mt1
  Version table:
     1:1snap1-0ubuntu2 -1
        500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
 *** 152.0.4+build1-0ubuntu0.22.04.1~mt1 1001
       1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status

The only information I'm looking for is: "How can I configure firefox so that it will notify me when updates are available so that I can choose when to apply the updates." It's just that simple. If there are config setting changes to allow that behavior, that will be the perfect solution.

Something went wrong when updating Synergy app and now it's impossible to do anything with the package: the dreaded (at least for me)

Sub-process /usr/bin/dpkg returned an error code (1)

I copy the log when trying to purge it:

(Reading database… 250720 files and directories currently installed.)
Removing synergy (3.6.1)…
production build
[dotenv@17.2.4] injecting env (0) from root/.config/Synergy/.env -- tip: 🛠️  run anywhere with `dotenvx run -- yourcommand`
loaded .env from: /root/.config/Synergy/.env
.env file parsed:  {}
[env] SYNERGY_LOGGER: not set
[env] SYNERGY_FORCE_CORE_LOG_LEVEL: not set
[env] SYNERGY_FORCE_SERVICE_LOG_LEVEL: not set
using log level: INFO
using logger: /root/.local/state/Synergy/synergy.log
skipping node version check in production (current: v22.22.2)
exiting process with code: 1
dpkg: error processing package synergy (--remove):
 old synergy package prerm maintainer script subprocess failed with exit status 1
dpkg: too many errors, stopping
production build
[dotenv@17.2.4] injecting env (0) from root/.config/Synergy/.env -- tip: ⚙️  write to custom object with { processEnv: myObject }
loaded .env from: /root/.config/Synergy/.env
.env file parsed:  {}
[env] SYNERGY_LOGGER: not set
[env] SYNERGY_FORCE_CORE_LOG_LEVEL: not set
[env] SYNERGY_FORCE_SERVICE_LOG_LEVEL: not set
using log level: INFO
using logger: /root/.local/state/Synergy/synergy.log
skipping node version check in production (current: v22.22.2)
exiting process with code: 1
Errors were encountered while processing:
 synergy
Processing was halted because there were too many errors.
Error: Sub-process /usr/bin/dpkg returned an error code (1)

I tried all the basic troubleshooting stuff like dpkg --configure -a, sudo apt -f install, apt-clean and several forms of deletion without success.

EDIT:
Sorry for the delay. I ended up leaving the city for several days.
I got this:

~$ export SYNERGY_LOGGER=DEBUG
~$ cat /var/lib/dpkg/info/synergy.prerm
#!/usr/bin/env sh

sudo ./opt/Synergy/synergy-service --uninstall

I don't know if this is of help.

I'm setting up a local AI stack with Ollama and Open WebUI using rootless podman-compose on Ubuntu 24.04. Both containers share a network, but when I started testing, I noticed the Ollama container was falling back to CPU inference — even though native Ollama on the host accesses the RTX 4060 Laptop GPU just fine.

My setup:

• Ubuntu 24.04
• NVIDIA GeForce RTX 4060 Laptop GPU, driver 595.71.05
• Podman 4.9.3
• podman-compose 1.5.0 (pip)
• nvidia-container-toolkit installed, CDI spec at /etc/cdi/nvidia.yaml

My short debugging:

# Checked the CDI devices
nvidia-ctk cdi list
: '
INFO[0000] Found 3 CDI devices                          
nvidia.com/gpu=0
nvidia.com/gpu=GPU-3cb61464-c22f-067b-dcb8-ea32dda1197d
nvidia.com/gpu=all
'

ollama run ministral-3:8b "Hi"
# Hello! How can I assist you today? 😊

# Checks if CDI spec exists
head -20 /etc/cdi/nvidia.yaml

: '

cdiVersion: 0.7.0
kind: nvidia.com/gpu
devices:
    - name: "0"
      containerEdits:
        deviceNodes:
            - path: /dev/nvidia0
              major: 195
              fileMode: 438
              permissions: rwm
            - path: /dev/dri/card0
              major: 226
              fileMode: 432
              permissions: rwm
              gid: 44
            - path: /dev/dri/renderD129
              major: 226
              minor: 129
              fileMode: 432
'

Bare podman run

podman run --rm --device nvidia.com/gpu=all --security-opt=label=disable ubuntu nvidia-smi -L
# Error: setting up CDI devices: unresolvable CDI devices nvidia.com/gpu=all

podman-compose run

podman-compose -f compose.yaml --profile gpu-podman up -d ollama-gpu-podman
# Error: unable to start container "5f5fd11ffa125aef013245690ba61e088460aee7a22c562af7326e12a43d1fec": setting up CDI devices: unresolvable CDI devices nvidia.com/gpu=all

My compose.yaml for the Ollama service:

services:
  ollama-gpu-podman:
    image: ollama/ollama:latest
    container_name: ollama-container
    profiles:
      - gpu-podman
    restart: unless-stopped
    networks:
      - ollama-network
    devices:
      - nvidia.com/gpu=all
    security_opt:
      - label=disable

How do I fix it?

My Lenovo Yoga 9 14IRP8 often does not recognize stylus strokes from the Precision Pen 2 when drawing in (mainly vertical, but occasionally also horizontal) tablet/2-in-1 mode, as shown in the picture. I have a hard time to find the origin of this issue. It occurs in different desktop environments (KDE and GNOME) and different distributions (Fedora, Ubuntu 26.04, Ubuntu 24.04). The bugs only happen when my palm rests on the display, but persist when I disable the touchscreen via udev rule:

ACTION=="add|change", SUBSYSTEM=="input", ENV{ID_INPUT_TOUCHSCREEN}=="1", ENV{LIBINPUT_IGNORE_DEVICE}="1"

Kernel: 7.0.0-22-generic

libinput: 1.31.1

Running libinput debug-events reports ultra-short time windows where the pen is detected to be lifted and set back down. Note that the timespans seem too short for a human to lift the pen out of the proximity reach and set it back down, as illustrated by the following snippet:

event6   TABLET_TOOL_TIP              +11.969s      185.73*/103.15* tilt: -12.00 /9.00  pressure: 0.00* up
 event6   TABLET_TOOL_PROXIMITY        +11.971s     185.73 /103.15  tilt: -12.00 /9.00  pressure: 0.00  pen      ('AES Pen', 0x80a32bf2, id 0x846b) proximity-out
 event6   TABLET_TOOL_PROXIMITY        +12.064s     187.33*/104.03* tilt: -11.00*/3.00* pressure: 0.00* pen      ('AES Pen', 0x80a32bf2, id 0x846b) proximity-in    axes:pt btn:S
 event6   TABLET_TOOL_TIP              +12.066s     187.33 /104.03  tilt: -11.00 /3.00  pressure: 0.31* down

Does anyone have a similar issue? What is the most likely cause for this?

Stylus behavior in horizontal and vertical tablet mode:

I had updated Ubuntu from 25.10 to 26.04.

Now, when booting into kernel 7.0.0-15, the system freezes while on login screen, goes black, then login screen is displayed again. Keeps occurring in an endless loop. If I select kernel 6.17.0-29-generic instead, the laptop runs fine, and I can log in without issue.

I ran the command sudo journalctl -b -1 -p err, and "Kernel Out of Memory error"s were present.
Are there known issues with the 7.0.0-15 kernel?

System specifications on 2026-05-25 20:39:59:

Hardware Model: Dell Inc. Inspiron 16 5625
Memory: 8.0 GiB
Processor: AMD Ryzen™ 5 5625U with Radeon™ Graphics × 12
Graphics: AMD Radeon™ Graphics
Disk Capacity: 512.1 GB
Firmware Version: 1.27.0
OS Name: Ubuntu 26.04 LTS
OS Build: (null)
OS Type: 64-bit
GNOME Version: 50
Windowing System: Wayland

EDIT Jun 07 2026, 08:15 EDT

Currently running kernel 7.0.0-22, and I am seeing the same freezing issue as with kernel 7.0.0-15. Output of sudo journalctl -b -1 -p err is below. Please let me know if more data is needed. Thank you.

$sudo journalctl -b -1 -p err
[sudo: authenticate] Password:         
Jun 07 08:02:52 user-Inspiron-16-5625 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0], AE_NOT_FOUND (20251212/dswload2-162)
Jun 07 08:02:52 user-Inspiron-16-5625 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20251212/psobject-220)
Jun 07 08:02:53 user-Inspiron-16-5625 kernel: leds platform::micmute: Setting an LED's brightness failed (-5)
Jun 07 08:02:55 user-Inspiron-16-5625 kernel: leds platform::micmute: Setting an LED's brightness failed (-5)
Jun 07 08:02:55 user-Inspiron-16-5625 kernel: leds platform::micmute: Setting an LED's brightness failed (-5)
Jun 07 08:02:55 user-Inspiron-16-5625 kernel: leds platform::micmute: Setting an LED's brightness failed (-5)
Jun 07 08:02:55 user-Inspiron-16-5625 kernel: leds platform::micmute: Setting an LED's brightness failed (-5)
Jun 07 08:02:56 user-Inspiron-16-5625 kernel: leds platform::micmute: Setting an LED's brightness failed (-5)
Jun 07 08:02:56 user-Inspiron-16-5625 kernel: amdgpu 0000:04:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 07 08:02:59 user-Inspiron-16-5625 kernel: leds platform::micmute: Setting an LED's brightness failed (-5)
Jun 07 08:02:59 user-Inspiron-16-5625 kernel: leds platform::micmute: Setting an LED's brightness failed (-5)
Jun 07 08:02:59 user-Inspiron-16-5625 bluetoothd[1791]: Failed to set mode: Failed (0x03)
Jun 07 08:03:04 user-Inspiron-16-5625 kernel: Out of memory: Killed process 2665 (pipewire) total-vm:99844kB, anon-rss:12kB, file-rss:160kB, shmem-rss:0kB, UID:60578 pgtables:88kB oom_score_adj:200
Jun 07 08:03:04 user-Inspiron-16-5625 kernel: Out of memory: Killed process 2667 (pipewire-pulse) total-vm:108296kB, anon-rss:12kB, file-rss:96kB, shmem-rss:0kB, UID:60578 pgtables:104kB oom_score_adj:200
Jun 07 08:03:04 user-Inspiron-16-5625 kernel: Out of memory: Killed process 2711 (gnome-keyring-d) total-vm:185780kB, anon-rss:0kB, file-rss:8kB, shmem-rss:0kB, UID:60578 pgtables:112kB oom_score_adj:200
Jun 07 08:03:04 user-Inspiron-16-5625 kernel: Out of memory: Killed process 2763 (gnome-session-s) total-vm:320132kB, anon-rss:4kB, file-rss:12kB, shmem-rss:0kB, UID:60578 pgtables:128kB oom_score_adj:200
Jun 07 08:03:04 user-Inspiron-16-5625 kernel: Out of memory: Killed process 2713 (ssh-agent) total-vm:10480kB, anon-rss:4kB, file-rss:8kB, shmem-rss:0kB, UID:60578 pgtables:64kB oom_score_adj:200
Jun 07 08:03:04 user-Inspiron-16-5625 kernel: Out of memory: Killed process 2710 (gcr-ssh-agent) total-vm:97552kB, anon-rss:0kB, file-rss:8kB, shmem-rss:0kB, UID:60578 pgtables:84kB oom_score_adj:200
Jun 07 08:03:04 user-Inspiron-16-5625 kernel: Out of memory: Killed process 2666 (pipewire) total-vm:87932kB, anon-rss:4kB, file-rss:8kB, shmem-rss:0kB, UID:60578 pgtables:80kB oom_score_adj:200
Jun 07 08:03:04 user-Inspiron-16-5625 kernel: Out of memory: Killed process 2664 (dbus-daemon) total-vm:8592kB, anon-rss:20kB, file-rss:36kB, shmem-rss:0kB, UID:60578 pgtables:60kB oom_score_adj:200
Jun 07 08:03:04 user-Inspiron-16-5625 kernel: Out of memory: Killed process 2712 (gnome-session-c) total-vm:89808kB, anon-rss:0kB, file-rss:8kB, shmem-rss:0kB, UID:60578 pgtables:84kB oom_score_adj:200
Jun 07 08:03:04 user-Inspiron-16-5625 kernel: Out of memory: Killed process 2681 (mpris-proxy) total-vm:7560kB, anon-rss:8kB, file-rss:72kB, shmem-rss:0kB, UID:60578 pgtables:56kB oom_score_adj:200
Jun 07 08:03:04 user-Inspiron-16-5625 kernel: Out of memory: Killed process 2235 (systemd) total-vm:23832kB, anon-rss:8kB, file-rss:32kB, shmem-rss:0kB, UID:60578 pgtables:96kB oom_score_adj:100
Jun 07 08:03:04 user-Inspiron-16-5625 kernel: Out of memory: Killed process 2244 ((sd-pam)) total-vm:23392kB, anon-rss:0kB, file-rss:0kB, shmem-rss:0kB, UID:60578 pgtables:76kB oom_score_adj:100
Jun 07 08:03:04 user-Inspiron-16-5625 kernel: Out of memory: Killed process 1801 (littlesnitch) total-vm:1892560kB, anon-rss:4kB, file-rss:536kB, shmem-rss:0kB, UID:0 pgtables:376kB oom_score_adj:0
Jun 07 08:03:13 user-Inspiron-16-5625 canonical-livepatch.canonical-livepatchd[2083]: refresh patch failed: livepatch check failed: POST request to "https://livepatch.canonical.com/v1/client/5047702a3e134442936e10fb8d830de2/upda>
Jun 07 08:03:13 user-Inspiron-16-5625 canonical-livepatch.canonical-livepatchd[2083]: Task "refresh" returned an error: livepatch check failed: POST request to "https://livepatch.canonical.com/v1/client/5047702a3e134442936e10fb8>
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 4270 (xdg-desktop-por) total-vm:559032kB, anon-rss:4kB, file-rss:8kB, shmem-rss:0kB, UID:60579 pgtables:180kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3540 (ibus-daemon) total-vm:388568kB, anon-rss:4kB, file-rss:8kB, shmem-rss:0kB, UID:60579 pgtables:124kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3178 (pipewire) total-vm:105844kB, anon-rss:100kB, file-rss:388kB, shmem-rss:0kB, UID:60579 pgtables:100kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3180 (pipewire-pulse) total-vm:109092kB, anon-rss:56kB, file-rss:212kB, shmem-rss:0kB, UID:60579 pgtables:108kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3543 (gsd-media-keys) total-vm:546832kB, anon-rss:4kB, file-rss:8kB, shmem-rss:0kB, UID:60579 pgtables:172kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3553 (gsd-sharing) total-vm:470256kB, anon-rss:4kB, file-rss:8kB, shmem-rss:0kB, UID:60579 pgtables:148kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3550 (gsd-power) total-vm:478688kB, anon-rss:4kB, file-rss:8kB, shmem-rss:0kB, UID:60579 pgtables:156kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 4237 (ibus-engine-sim) total-vm:171772kB, anon-rss:84kB, file-rss:764kB, shmem-rss:0kB, UID:60579 pgtables:92kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3709 (ibus-dconf) total-vm:245592kB, anon-rss:88kB, file-rss:820kB, shmem-rss:0kB, UID:60579 pgtables:108kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3713 (ibus-portal) total-vm:311096kB, anon-rss:68kB, file-rss:660kB, shmem-rss:0kB, UID:60579 pgtables:112kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3177 (dbus-daemon) total-vm:9192kB, anon-rss:180kB, file-rss:136kB, shmem-rss:0kB, UID:60579 pgtables:56kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3262 (gnome-session-s) total-vm:468284kB, anon-rss:0kB, file-rss:8kB, shmem-rss:0kB, UID:60579 pgtables:148kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3541 (gsd-a11y-settin) total-vm:256652kB, anon-rss:16kB, file-rss:168kB, shmem-rss:0kB, UID:60579 pgtables:128kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3556 (gsd-smartcard) total-vm:388568kB, anon-rss:24kB, file-rss:236kB, shmem-rss:0kB, UID:60579 pgtables:124kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3221 (gnome-keyring-d) total-vm:185780kB, anon-rss:64kB, file-rss:332kB, shmem-rss:0kB, UID:60579 pgtables:116kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3558 (gsd-usb-protect) total-vm:540600kB, anon-rss:32kB, file-rss:184kB, shmem-rss:0kB, UID:60579 pgtables:148kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3551 (gsd-rfkill) total-vm:459524kB, anon-rss:68kB, file-rss:228kB, shmem-rss:0kB, UID:60579 pgtables:132kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3490 (at-spi2-registr) total-vm:168680kB, anon-rss:120kB, file-rss:504kB, shmem-rss:0kB, UID:60579 pgtables:88kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3512 (xdg-permission-) total-vm:309964kB, anon-rss:96kB, file-rss:544kB, shmem-rss:0kB, UID:60579 pgtables:112kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3480 (at-spi-bus-laun) total-vm:381384kB, anon-rss:84kB, file-rss:500kB, shmem-rss:0kB, UID:60579 pgtables:104kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 4282 (xdg-document-po) total-vm:542228kB, anon-rss:92kB, file-rss:496kB, shmem-rss:0kB, UID:60579 pgtables:144kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3542 (gsd-keyboard) total-vm:385992kB, anon-rss:56kB, file-rss:392kB, shmem-rss:0kB, UID:60579 pgtables:120kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3229 (ssh-agent) total-vm:10480kB, anon-rss:4kB, file-rss:8kB, shmem-rss:0kB, UID:60579 pgtables:64kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 4435 (dconf-service) total-vm:165220kB, anon-rss:84kB, file-rss:324kB, shmem-rss:0kB, UID:60579 pgtables:80kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3220 (gcr-ssh-agent) total-vm:97552kB, anon-rss:0kB, file-rss:8kB, shmem-rss:0kB, UID:60579 pgtables:84kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3179 (pipewire) total-vm:87932kB, anon-rss:4kB, file-rss:8kB, shmem-rss:0kB, UID:60579 pgtables:76kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3487 (dbus-daemon) total-vm:8548kB, anon-rss:16kB, file-rss:64kB, shmem-rss:0kB, UID:60579 pgtables:68kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3222 (gnome-session-c) total-vm:89808kB, anon-rss:0kB, file-rss:8kB, shmem-rss:0kB, UID:60579 pgtables:84kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 4332 (fusermount3) total-vm:4416kB, anon-rss:4kB, file-rss:8kB, shmem-rss:0kB, UID:0 pgtables:48kB oom_score_adj:200
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3268 (gnome-shell) total-vm:9182312kB, anon-rss:20kB, file-rss:16kB, shmem-rss:0kB, UID:60579 pgtables:1676kB oom_score_adj:100
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 2970 (systemd) total-vm:23968kB, anon-rss:32kB, file-rss:80kB, shmem-rss:0kB, UID:60579 pgtables:84kB oom_score_adj:100
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 3006 ((sd-pam)) total-vm:23388kB, anon-rss:24kB, file-rss:104kB, shmem-rss:0kB, UID:60579 pgtables:76kB oom_score_adj:100
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 4283 (littlesnitch) total-vm:1958096kB, anon-rss:0kB, file-rss:536kB, shmem-rss:0kB, UID:0 pgtables:388kB oom_score_adj:0
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: Out of memory: Killed process 1806 (networkd-dispat) total-vm:55096kB, anon-rss:4kB, file-rss:8kB, shmem-rss:0kB, UID:0 pgtables:140kB oom_score_adj:0
Jun 07 08:03:38 user-Inspiron-16-5625 kernel: amdgpu 0000:04:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jun 07 08:03:39 user-Inspiron-16-5625 systemd-logind[1840]: Failed to start user service 'user-runtime-dir@60580.service': Transaction for user-runtime-dir@60580.service/start is destructive (nss-lookup.target has 'stop' job que>
Jun 07 08:03:39 user-Inspiron-16-5625 systemd-logind[1840]: Failed to start user service 'user@60580.service': Transaction for user@60580.service/start is destructive (systemd-fsck@dev-disk-by\x2duuid-044F\x2d1AC7.service has 's>
Jun 07 08:03:39 user-Inspiron-16-5625 gdm-password][4678]: pam_unix(gdm-password:auth): conversation failed
Jun 07 08:03:39 user-Inspiron-16-5625 gdm-password][4678]: pam_unix(gdm-password:auth): auth could not identify password for [user]
Jun 07 08:03:39 user-Inspiron-16-5625 canonical-livepatch.canonical-livepatchd[2083]: daemon shutting down

Still experiencing freeze issue after upgrading to kernel 7.0.0-27. Some dmesg output below:

[   16.589403] kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-60578.slice/user@60578.service/session.slice/pipewire-pulse.service,task=pipewire-pulse,pid=2829,uid=60578
[   16.589433] kernel: Out of memory: Killed process 2829 (pipewire-pulse) total-vm:108296kB, anon-rss:4kB, file-rss:8kB, shmem-rss:0kB, UID:60578 pgtables:108kB oom_score_adj:200
[   16.589457] kernel: littlesnitch invoked oom-killer: gfp_mask=0xc2cc0(GFP_KERNEL|__GFP_NOWARN|__GFP_COMP|__GFP_NOMEMALLOC), order=0, oom_score_adj=0
[   16.589485] kernel: CPU: 5 UID: 0 PID: 2182 Comm: littlesnitch Not tainted 7.0.0-27-generic #27-Ubuntu PREEMPT(lazy) 
[   16.589499] kernel: Hardware name: Dell Inc. Inspiron 16 5625/0TGWG4, BIOS 1.28.1 05/12/2026
[   16.589522] kernel: Call Trace:
[   16.589540] kernel:  <TASK>
[   16.589558] kernel:  show_stack+0x49/0x60
[   16.589575] kernel:  dump_stack_lvl+0x5f/0x90
[   16.589611] kernel:  dump_stack+0x10/0x18
[   16.589626] kernel:  dump_header+0x48/0x1c7
[   16.589645] kernel:  oom_kill_process.cold+0x8/0xac
[   16.589666] kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[   16.589684] kernel:  out_of_memory+0xff/0x2b0
[   16.589698] kernel:  __alloc_pages_may_oom+0x10a/0x1d0
[   16.589721] kernel:  __alloc_pages_slowpath.constprop.0+0x3e0/0x9b0
[   16.589736] kernel:  __alloc_frozen_pages_noprof+0x327/0x360
[   16.589762] kernel:  allocate_slab+0x1f3/0x430
[   16.589776] kernel:  refill_objects+0xe9/0x150
[   16.589790] kernel:  __pcs_replace_empty_main+0x146/0x3c0
[   16.589804] kernel:  __kmalloc_cache_noprof+0x3d9/0x4b0
[   16.589828] kernel:  ? copy_verifier_state+0x218/0x2c0
[   16.589847] kernel:  copy_verifier_state+0x218/0x2c0
[   16.589865] kernel:  ? push_stack+0x3c/0x100
[   16.589889] kernel:  push_stack+0x85/0x100
[   16.589910] kernel:  check_cond_jmp_op+0x43f/0xb40
[   16.589928] kernel:  do_check_insn+0x453/0x6e0
[   16.589946] kernel:  do_check+0x32b/0x630
[   16.589968] kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[   16.589981] kernel:  do_check_common+0x1b5/0x6d0
[   16.590019] kernel:  bpf_check+0xbb4/0x13e0
[   16.590054] kernel:  bpf_prog_load+0x645/0xb90
[   16.590068] kernel:  __sys_bpf+0x97c/0xcd0
[   16.590084] kernel:  __x64_sys_bpf+0x1d/0x30
[   16.590098] kernel:  x64_sys_call+0x1182/0x2390
[   16.590118] kernel:  do_syscall_64+0x105/0x5a0
[   16.590146] kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[   16.590164] kernel:  ? handle_pte_fault+0x1cb/0x1f0
[   16.590192] kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[   16.590210] kernel:  ? __handle_mm_fault+0x493/0x720
[   16.590235] kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[   16.590255] kernel:  ? count_memcg_events+0x103/0x250
[   16.590282] kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[   16.590299] kernel:  ? handle_mm_fault+0x1c0/0x2e0
[   16.590314] kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[   16.590327] kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[   16.590347] kernel:  ? arch_exit_to_user_mode_prepare.isra.0+0xd/0x100
[   16.590375] kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[   16.590393] kernel:  ? irqentry_exit+0x97/0x5a0
[   16.590414] kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
[   16.590428] kernel:  ? exc_page_fault+0x94/0x1e0
[   16.590448] kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[   16.590466] kernel: RIP: 0033:0x7fb79a334d0d
[   16.590479] kernel: Code: Unable to access opcode bytes at 0x7fb79a334ce3.
[   16.590493] kernel: RSP: 002b:00007fb76b7fa3a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
[   16.590533] kernel: RAX: ffffffffffffffda RBX: 00007fb76b7fa470 RCX: 00007fb79a334d0d
[   16.590550] kernel: RDX: 0000000000000098 RSI: 00007fb76b7fa5c8 RDI: 0000000000000005
[   16.590565] kernel: RBP: 0000000000000005 R08: 0000000000000100 R09: 0000000000000000
[   16.590579] kernel: R10: 00007fb71c004b20 R11: 0000000000000246 R12: 0000000000000001
[   16.590596] kernel: R13: 00000000000003d6 R14: 00007fb76b7fa5c8 R15: 0000000000000000
[   16.590614] kernel:  </TASK>
[   16.590629] kernel: Mem-Info:
[   16.590642] kernel: active_anon:18 inactive_anon:168 isolated_anon:0
                        active_file:6 inactive_file:162 isolated_file:0
                        unevictable:4898 dirty:9 writeback:38
                        slab_reclaimable:9984 slab_unreclaimable:1548786
                        mapped:3407 shmem:112 pagetables:2925
                        sec_pagetables:775 bounce:0
                        kernel_misc_reclaimable:0
                        free:25295 free_pcp:309 free_cma:0
[   16.590664] kernel: Node 0 active_anon:72kB inactive_anon:672kB active_file:24kB inactive_file:648kB unevictable:19592kB isolated(anon):0kB isolated(file):0kB mapped:13628kB dirty:36kB writeback:152kB shmem:448kB shmem_thp:0kB shmem_pmdmapped:0kB anon_thp:0kB kernel_stack:8164kB pagetables:11700kB sec_pagetables:3100kB all_unreclaimable? no Balloon:0kB
[   16.590680] kernel: Node 0 DMA free:14336kB boost:0kB min:148kB low:184kB high:220kB reserved_highatomic:0KB free_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB zspages:0kB present:15992kB managed:15360kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB

EDIT Jul 10 2026, 08:45 EDT

I have my main site https://mysite.com in nextjs and wordpress blog on subdomain https://blog.mysite.com. They both are hosted on different servers and diff hostings.

I need my blog to be accessible via subdirectory in main site - https://mysite.com/blog

I have successfully proxied nextjs https://mysite.com/blog to see blog but blog's internal links, pages, posts, media is still pointing to subdomain.

async rewrites() {
return [
  {
    source: '/blog',
    destination: 'https://blog.mysite.com/',
  },
  {
    source: '/blog/:slug',
    destination: 'https://blog.mysite.com/:slug', // Matched parameters can be used in the destination
  },
]

},

I have tried many solutions but end up breaking wordpress config

Need help

solutions tried

• https://medium.com/one-weekend-at-a-time/how-to-reverseproxy-wordpress-at-blog-from-any-sub-domain-ec8e5159e305
• https://proxyscrape.com/blog/using-a-reverse-proxy-to-install-a-wordpress-blog-for-enhanced-seo

When I am trying to connect to remote ssh in vscode I am getting log like this

[23:15:44.114] Log Level: 2
[23:15:44.116] remote-ssh@0.90.1
[23:15:44.116] linux x64
[23:15:44.127] SSH Resolver called for "ssh-remote+172.16.26.73", attempt 1
[23:15:44.128] "remote.SSH.useLocalServer": true
[23:15:44.129] "remote.SSH.path": undefined
[23:15:44.129] "remote.SSH.configFile": undefined
[23:15:44.130] "remote.SSH.useFlock": true
[23:15:44.130] "remote.SSH.lockfilesInTmp": false
[23:15:44.130] "remote.SSH.localServerDownload": auto
[23:15:44.130] "remote.SSH.remoteServerListenOnSocket": false
[23:15:44.131] "remote.SSH.showLoginTerminal": false
[23:15:44.131] "remote.SSH.defaultExtensions": []
[23:15:44.131] "remote.SSH.loglevel": 2
[23:15:44.131] "remote.SSH.enableDynamicForwarding": true
[23:15:44.132] "remote.SSH.enableRemoteCommand": false
[23:15:44.132] "remote.SSH.serverPickPortsFromRange": {}
[23:15:44.132] "remote.SSH.serverInstallPath": {}
[23:15:44.148] SSH Resolver called for host: 172.16.26.73
[23:15:44.148] Setting up SSH remote "172.16.26.73"
[23:15:44.153] Acquiring local install lock: /tmp/vscode-remote-ssh-c6eecf9c-install.lock
[23:15:44.159] Looking for existing server data file at /home/sinanck/.config/Code/User/globalStorage/ms-vscode-remote.remote-ssh/vscode-ssh-host-c6eecf9c-d045a5eda657f4d7b676dedbfa7aab8207f8a075-0.90.1/data.json
[23:15:44.159] Using commit id "d045a5eda657f4d7b676dedbfa7aab8207f8a075" and quality "stable" for server
[23:15:44.165] Install and start server if needed
[23:15:44.171] PATH: /home/sinanck/.local/bin:/home/sinanck/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin
[23:15:44.171] Checking ssh with "ssh -V"
[23:15:44.208] > OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022

[23:15:44.216] askpass server listening on /run/user/1000/vscode-ssh-askpass-71e437fc181e2f9984902492aa901cc6d17248dd.sock
[23:15:44.216] Spawning local server with {"serverId":1,"ipcHandlePath":"/run/user/1000/vscode-ssh-askpass-d8d3a51da8df9c70d2191a15cbc3bf8ea4922d52.sock","sshCommand":"ssh","sshArgs":["-v","-T","-D","34539","-o","ConnectTimeout=15","172.16.26.73"],"serverDataFolderName":".vscode-server","dataFilePath":"/home/sinanck/.config/Code/User/globalStorage/ms-vscode-remote.remote-ssh/vscode-ssh-host-c6eecf9c-d045a5eda657f4d7b676dedbfa7aab8207f8a075-0.90.1/data.json"}
[23:15:44.217] Local server env: {"SSH_AUTH_SOCK":"/run/user/1000/keyring/ssh","SHELL":"/bin/bash","DISPLAY":":0","ELECTRON_RUN_AS_NODE":"1","SSH_ASKPASS":"/home/sinanck/.vscode/extensions/ms-vscode-remote.remote-ssh-0.90.1/out/local-server/askpass.sh","VSCODE_SSH_ASKPASS_NODE":"/snap/code/111/usr/share/code/code","VSCODE_SSH_ASKPASS_EXTRA_ARGS":"--ms-enable-electron-run-as-node","VSCODE_SSH_ASKPASS_MAIN":"/home/sinanck/.vscode/extensions/ms-vscode-remote.remote-ssh-0.90.1/out/askpass-main.js","VSCODE_SSH_ASKPASS_HANDLE":"/run/user/1000/vscode-ssh-askpass-71e437fc181e2f9984902492aa901cc6d17248dd.sock"}
[23:15:44.227] Spawned 477089
[23:15:44.496] > local-server-1> Spawned ssh, pid=477098
[23:15:44.503] stderr> OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022
[23:15:44.542] stderr> debug1: Server host key: ssh-ed25519 SHA256:ZYvzW+Upd0FIkDzmOcNVB2yCWZCHQN8GqKZRybC7QZQ
[23:15:44.839] Got askpass request: {"request":"muhammed_1901cs38@172.16.26.73's password:"}
[23:15:44.840] Showing password prompt
[23:15:44.841] Listening for interwindow password on /run/user/1000/vscode-ssh-askpass-1742cf921041d3dcec39277056d239200013e310.sock
[23:15:44.841] Writing password prompt to globalState
[23:15:47.444] Got password response
[23:15:47.445] Interactor gave response: *********
[23:15:47.446] Cleaning up other-window auth server
[23:15:47.500] stderr> Authenticated to 172.16.26.73 ([172.16.26.73]:22) using "password".
[23:15:48.066] > Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.11.0-37-generic x86_64)
> 
>  * Documentation:  https://help.ubuntu.com
>  * Management:     https://landscape.canonical.com
>  * Support:        https://ubuntu.com/advantage
> 
> 458 updates can be applied immediately.
> 298 of these updates are standard security updates.
> To see these additional updates run: apt list --upgradable
> 
> 
> The list of available updates is more than a week old.
> To check for new updates run: sudo apt update
> Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings
> 
> Your Hardware Enablement Stack (HWE) is supported until April 2025.
[23:15:48.217] > ready: 5db122392114
[23:15:48.235] > Linux 5.11.0-37-generic #41~20.04.2-Ubuntu SMP Fri Sep 24 09:06:38 UTC 2021
[23:15:48.236] Platform: linux
[23:15:48.243] > /bin/bash
[23:15:48.244] Shell: bash
[23:15:48.244] Creating bash subshell inside "bash"
[23:15:48.294] > bash version:  5.0.17(1)-release
[23:15:48.312] > 5db122392114: running
[23:15:48.463] > Acquiring lock on /home/muhammed_1901cs38/.vscode-server/bin/d045a5eda657f4d7b676dedbfa7aab8207f8a075/vscode-remote-lock.muhammed_1901cs38.d045a5eda657f4d7b676dedbfa7aab8207f8a075
[23:15:48.468] > Installation already in progress...
[23:15:48.473] > If you continue to see this message, you can try toggling the remote.SSH.useFlock setting
> 5db122392114: start
> exitCode==24==
> listeningOn====
> osReleaseId==ubuntu==
> arch==x86_64==
> tmpDir==/run/user/1055==
> platform==linux==
> unpackResult====
> didLocalDownload==0==
> downloadTime====
> installTime====
> extInstallTime====
> serverStartTime====
> 5db122392114: end
[23:15:48.474] Received install output: 
exitCode==24==
listeningOn====
osReleaseId==ubuntu==
arch==x86_64==
tmpDir==/run/user/1055==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
extInstallTime====
serverStartTime====

[23:15:48.476] Server installation process already in progress - waiting and retrying
[23:15:48.477] Terminating local server
[23:15:48.494] Local server exit: 15
[23:15:49.485] askpass server listening on /run/user/1000/vscode-ssh-askpass-63095919f2fd495c76329ec9ee199fdc4db10c0e.sock
[23:15:49.485] Spawning local server with {"serverId":2,"ipcHandlePath":"/run/user/1000/vscode-ssh-askpass-968db2b9bd48590c4ec997d199ca9aec30e5be83.sock","sshCommand":"ssh","sshArgs":["-v","-T","-D","34539","-o","ConnectTimeout=15","172.16.26.73"],"serverDataFolderName":".vscode-server","dataFilePath":"/home/sinanck/.config/Code/User/globalStorage/ms-vscode-remote.remote-ssh/vscode-ssh-host-c6eecf9c-d045a5eda657f4d7b676dedbfa7aab8207f8a075-0.90.1/data.json"}
[23:15:49.486] Local server env: {"SSH_AUTH_SOCK":"/run/user/1000/keyring/ssh","SHELL":"/bin/bash","DISPLAY":":0","ELECTRON_RUN_AS_NODE":"1","SSH_ASKPASS":"/home/sinanck/.vscode/extensions/ms-vscode-remote.remote-ssh-0.90.1/out/local-server/askpass.sh","VSCODE_SSH_ASKPASS_NODE":"/snap/code/111/usr/share/code/code","VSCODE_SSH_ASKPASS_EXTRA_ARGS":"--ms-enable-electron-run-as-node","VSCODE_SSH_ASKPASS_MAIN":"/home/sinanck/.vscode/extensions/ms-vscode-remote.remote-ssh-0.90.1/out/askpass-main.js","VSCODE_SSH_ASKPASS_HANDLE":"/run/user/1000/vscode-ssh-askpass-63095919f2fd495c76329ec9ee199fdc4db10c0e.sock"}
[23:15:49.492] Spawned 477115
[23:15:49.706] > local-server-2> Spawned ssh, pid=477123
[23:15:49.711] stderr> OpenSSH_8.9p1 Ubuntu-3, OpenSSL 3.0.2 15 Mar 2022
[23:15:49.784] stderr> debug1: Server host key: ssh-ed25519 SHA256:ZYvzW+Upd0FIkDzmOcNVB2yCWZCHQN8GqKZRybC7QZQ
[23:15:50.066] Got askpass request: {"request":"muhammed_1901cs38@172.16.26.73's password:"}
[23:15:50.067] Showing password prompt
[23:15:50.068] Listening for interwindow password on /run/user/1000/vscode-ssh-askpass-a5b7bc9fb6026360e91b2ea2838c42d95db8d022.sock
[23:15:50.068] Writing password prompt to globalState

I am trying to install Lubuntu on a machine that has Ubuntu on it (BOTH LATEST VERSION)

When I boot with ISO disk it says loading Lubuntu for a long then it says: OK Finished Plymouth boot OK Finished Set Console scheme FAILED Failed to start Snap Daemon

Then the machine is locked up and I must turn it off to reboot

I used another Lununtu DVD but same result

Can you help me??????

I'm lately having slow startup times (90sec vs 20sec in the past) since I upgraded from Ubuntu 18.04 to 20.04.

I'm on Ubuntu 20.04.1 LTS 64-bit. I'm working on a hybrid SSD (120GB) + HHD (500GB) system, Intel Core i3-6100U CPU @ 2.30GHz × 4 and 8GB of RAM DDR4. My partitions are: SSD: 249MB EFI (/boot/efi), 40GB FileSystem (/), 8GB Swap and 72 GB FileSystem (/home). The HDD is not mounted.

I've formatted my system and re-installed Ubuntu, but the booting time is pretty much the same. I also tried to Open /etc/fstab (as superuser), remove (or comment out) the line contains old swap partition, set up a new swap:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdc2 during installation
UUID=cf116583-5203-458c-855e-6f412a1ba35d /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sdc1 during installation
UUID=4C04-C9BD  /boot/efi       vfat    umask=0077      0       1
# /home was on /dev/sdc4 during installation
UUID=a5f9b844-bb2a-49e0-9a8e-d88c76eeb832 /home           ext4    defaults        0       2
# swap was on /dev/sdc3 during installation
# UUID=3bd915e8-cdd5-4ffd-a477-b355a73d53b3 none            swap    sw              0       0

And, I also cancelled the Press Ctrl+C to cancel all filesystem checks in progress message at the booting by adding fsck.mode=skip to /etc/default/grub.

Here are some commands I ran for troubleshooting along with their respective output:

$ systemd-analyze time
Startup finished in 23.446s (firmware) + 9.900s (loader) + 5.114s (kernel) + 41.224s (userspace) = 1min 19.686s 
graphical.target reached after 40.975s in userspace

$ systemd-analyze blame
24.614s plymouth-quit-wait.service                                                               
11.743s dev-sdb2.device                                                                          
10.361s snapd.service                                                                            
 9.676s NetworkManager-wait-online.service                                                       
 6.549s dev-loop8.device                                                                         
 6.492s dev-loop10.device                                                                        
 6.460s dev-loop9.device                                                                         
 6.413s dev-loop11.device                                                                        
 4.894s dev-loop0.device                                                                         
 4.856s dev-loop4.device                                                                         
 4.707s dev-loop2.device                                                                         
 4.705s dev-loop1.device                                                                         
 4.693s dev-loop6.device                                                                         
 4.688s dev-loop3.device                                                                         
 4.582s dev-loop7.device                                                                         
 4.526s dev-loop5.device                                                                         
 3.761s upower.service                                                                           
 3.310s systemd-rfkill.service                                                                   
 2.588s udisks2.service                                                                          
 2.232s fwupd.service                                                                            
 2.108s systemd-logind.service                                                                   
 2.025s accounts-daemon.service                                                                  
 1.931s networkd-dispatcher.service                                                              
 1.497s user@1000.service                                                                        
 1.383s polkit.service                                                                           
 1.264s avahi-daemon.service                                                                     
 1.223s bluetooth.service                                                                        
 1.214s NetworkManager.service                                                                   
 1.119s systemd-resolved.service                                                                 
 1.037s switcheroo-control.service                                                               
 1.022s apport.service                                                                           
 1.009s keyboard-setup.service                                                                   
  954ms systemd-timesyncd.service                                                                
  900ms systemd-journald.service                                                                 
  868ms snapd.apparmor.service                                                                   
  826ms systemd-udev-trigger.service                                                             
  822ms grub-common.service

In the following command the time when unit became active or started is printed after the @ character. The time the unit took to start is printed after the + character.

$ systemd-analyze critical-chain
graphical.target @40.975s
└─multi-user.target @40.956s
  **└─kerneloops.service @25.596s +293ms**
    └─network-online.target @25.548s
      **└─NetworkManager-wait-online.service @15.866s +9.676s
        └─NetworkManager.service @14.638s +1.214s**
          └─dbus.service @14.590s
            └─basic.target @14.444s
              └─sockets.target @14.443s
                **└─snapd.socket @14.434s +6ms**
                  └─sysinit.target @14.374s
                    **└─snapd.apparmor.service @13.504s +868ms**
                      └─apparmor.service @13.042s +452ms
                        └─local-fs.target @13.032s
                          └─run-user-1000-doc.mount @30.724s
                            └─run-user-1000.mount @18.199s
                              └─swap.target @12.881s
                                **└─dev-sdb3.swap @12.750s +114ms**
                                  └─dev-sdb3.device @12.730s

Please, take into account that I'm a general user of Ubuntu, so practical solutions will be appreciated.

EDIT 16:35 2020/10/06

Screenshots and info asked by @heynnema:

$ grep -i swap /etc/fstab
# swap was on /dev/sdc3 during installation
UUID=316dc5cd-e888-48b8-868a-0e5d6072e480 none            swap    sw              0       0

$ sudo blkid
/dev/sdb2: UUID="cf116583-5203-458c-855e-6f412a1ba35d" TYPE="ext4" PARTUUID="8767a42b-380a-45af-87f9-84c9fe0a6bc4"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/sda1: LABEL="HDD" UUID="42365cfd-df11-4b02-9f9b-9047da487338" TYPE="ext4" PARTUUID="ee264f0e-6367-4360-9216-a3b24c63d56b"
/dev/sdb1: UUID="4C04-C9BD" TYPE="vfat" PARTUUID="8648f750-04c5-4508-8b4e-82f7b947e6b9"
/dev/sdb3: UUID="316dc5cd-e888-48b8-868a-0e5d6072e480" TYPE="swap" PARTLABEL="lol" PARTUUID="86bf4b4a-0d1e-4341-94fb-c674c1c39b88"
/dev/sdb4: UUID="a5f9b844-bb2a-49e0-9a8e-d88c76eeb832" TYPE="ext4" PARTUUID="3833323d-93a2-4961-9ba8-a3aee724153e"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"

$ ls -al /var/crash
total 8
drwxrwsrwt  2 root whoopsie 4096 jul 31 18:31 .
drwxr-xr-x 14 root root     4096 jul 31 18:35 ..

Screenshots from GParted and Disks (SMART):

EDIT 18:07 2020-10-06

@heynnema here are the last requests:

$ systemctl status plymouth-quit-wait
     Loaded: loaded (/lib/systemd/system/plymouth-quit-wait.service; stat>
     Active: inactive (dead) since Tue 2020-10-06 17:11:13 CEST; 42min ago
     Process: 1056 ExecStart=/bin/plymouth --wait (code=exited, status=0/S>   
   Main PID: 1056 (code=exited, status=0/SUCCESS)

oct 06 17:10:48 matheus-Vostro-15-3568 systemd[1]: Starting Hold until bo>
oct 06 17:11:13 matheus-Vostro-15-3568 systemd[1]: plymouth-quit-wait.ser>
oct 06 17:11:13 matheus-Vostro-15-3568 systemd[1]: Finished Hold until bo>

$ free -h
              total        used        free      shared  buff/cache   available
Mem:          7,6Gi       1,9Gi       3,9Gi       196Mi      1,9Gi       5,3Gi
Swap:         7,4Gi          0B       7,4Gi

$ sysctl vm.swappiness
vm.swappiness = 60

$ ls -al /
total 84 
drwxr-xr-x 20 root root   4096 oct 5 23:57 . 
drwxr-xr-x 20 root root   4096 oct 5 23:57 .. 
lrwxrwxrwx 1 root root       7 oct 5 23:49 bin -> usr/bin 
drwxr-xr-x 4 root root    4096 oct 6 00:09 boot 
drwxrwxr-x 2 root root    4096 oct 5 23:57 cdrom 
drwxr-xr-x 21 root root   4540 oct 6 17:10 dev 
drwxr-xr-x 127 root root 12288 oct 6 16:20 etc 
drwxr-xr-x 4 root root    4096 oct 5 23:58 home 
lrwxrwxrwx 1 root root       7 oct 5 23:49 lib -> usr/lib 
lrwxrwxrwx 1 root root       9 oct 5 23:49 lib32 -> usr/lib32 
lrwxrwxrwx 1 root root       9 oct 5 23:49 lib64 -> usr/lib64 
lrwxrwxrwx 1 root root      10 oct 5 23:49 libx32 -> usr/libx32 
drwx------ 2 root root   16384 oct 5 23:48 lost+found 
drwxr-xr-x 3 root root    4096 oct 6 16:49 media 
drwxr-xr-x 2 root root    4096 jul 31 18:27 mnt 
drwxr-xr-x 2 root root    4096 jul 31 18:27 opt 
dr-xr-xr-x 251 root root     0 oct 6 17:10 proc 
drwx------ 6 root root    4096 oct 6 00:19 root 
drwxr-xr-x 34 root root    880 oct 6 17:11 run 
lrwxrwxrwx 1 root root       8 oct 5 23:49 sbin -> usr/sbin 
drwxr-xr-x 12 root root   4096 oct 6 02:15 snap 
drwxr-xr-x 2 root root    4096 jul 31 18:27 srv 
dr-xr-xr-x 13 root root      0 oct 6 17:10 sys 
drwxrwxrwt 21 root root   4096 oct 6 17:57 tmp 
drwxr-xr-x 14 root root   4096 jul 31 18:28 usr 
drwxr-xr-x 14 root root   4096 jul 31 18:35 var

$ sudo dmidecode -s bios-version
2.6.0

Exact make/model # of my computer/motherboard: DELL vVstro 15 3568, i3-6100u

EDIT 18:05 2020-10-08

Messages shown when pressing Esc at boot:

         Starting Permit User Sessions...
[  OK  ] Finished OpenVPN service.
[  OK  ] Started Switcheroo Control Proxy service.
[  OK  ] Finished Permit User Sessions.
[  OK  ] Started Authorization Manager.
         Starting Modem Manager...
         Starting Save/Restore Sound Card State...
         Starting GNOME Display Manager...
         Starting Hold until boot process finishes up...
         Starting Hostname Service...
[  OK  ] Started Dispatcher daemon for systemd-networkd.
[  OK  ] Started Accounts Service.
[  OK  ] Finished Save/Restore Sound Card State.
[  OK  ] Reached target Sound Card.
[  OK  ] Started Login Service.
[  OK  ] Started Unattended Upgrades Shutdown.
[  OK  ] Started GNOME Display Manager.
[  OK  ] Started Modem Manager.
rsyslog.service
bluetooth.service
thermald.service
wpa_supplicant.service
avahi-daemon.service
[  OK  ] Started LSB: automatic crash report generation.
[  OK  ] Started LSB: Record successful boot for GRUB.
cups-browsed.service
NetworkManager.service
openvpn.service
switcheroo-control.service
systemd-user-sessions.service
polkit.service
networkd-dispatcher.service
accounts-daemon.service
alsa-restore.service
systemd-logind.service
unattended-upgrades.service
gdm.service
ModemManager.service
apport.service
grub-common.service
[   22.370810] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[   22.376896] pcieport 0000:00:1c.0: AER:   device [8086:9d14] error status/mask=00000081/00002000
[   22.383223] pcieport 0000:00:1c.0: AER:    [ 0] RxErr
[   22.389376] pcieport 0000:00:1c.0: AER:    [ 7] BadDLLP
[   22.404935] pcieport 0000:00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[   22.410805] pcieport 0000:00:1c.0: AER:   device [8086:9d14] error status/mask=00000001/00002000
[   22.417034] pcieport 0000:00:1c.0: AER:    [ 0] RxErr

For some reason, Scroll Lock is not enabled by default. I submit this bug as an enhancement, since as of this moment, I have no idea why Scroll Lock is not already enabled by default. That is the behavior that I expect.

My laptop keyboard does not have a key for Scroll Lock, so I did not notice anything was amiss. It is not until I purchased a keyboard with LED lighting that I noticed that when I pressed the Scroll Lock key, nothing was happening. I was expecting that if I pressed the Scroll Lock key, then the Scroll Lock indicator LED would turn on and the LED in my keyboard would turn on as well, but none of those actions happen. The LED indicator for Caps Lock and Num Lock worked fine, but not for Scroll Lock.

How can I make the Scroll Lock key to work?

I have Ubuntu 14.04 dual boot with Windows 7 HB. I had (had since it's no visible in the Windows directory) a folder in Windows whose path was D:/Edu/MS/Semester 3 Summer. I have Windows 7 partitioned into 2 drives: C and Drive.

I accessed the Semester 3 Summer folder from Ubuntu by clicking the 316 OS Volume(which I believe is the D Drive of my Windows). Now, when I logged back into the Windows, I can no longer see the folder. It has (or had) all my assignments.

How do I get the folder back?

I want to know if is there any way to play German Truck Simulator in Ubuntu 12.04? With Wine, it doesn't works. (The installation worked fine, but when I launch GTS, it says me this:

German Truck Simulator unable to find any graphic card driver on your system. 
Please install the correct driver to your graphic card and try start the game again.

If I try to install the Windows drivers, it says me this:

There is no graphic card on your PC which is comptible with this driver. 
Please install the correct drivers and start the installer again.

So, is there a Linux version of GTS? (or a .deb package?)

I recently got a backlit keyboard, and I LOVE to write late at night.

But I cannot for the life of me figure out how to light it up...It lights up when first plugged in, but nothing happens after that....

It is an 'XtremeIT' keyboard. There is a video of someone on Ubuntu who managed to activate it...