I recently experienced a complete system freeze on my notebook (with no mouse or keyboard response), and the only solution was a forced shutdown. To avoid potential filesystem corruption, I formatted the machine and performed a clean installation of Ubuntu 20.04.6 LTS from Dell’s official website.

Installation details:

• ISO: Ubuntu 20.04

• USB drive: SanDisk Generic

• Bootable media created using Rufus

• Installed on SSD

• Installation finished normally with errors about reading files, e exactly 4 files

After reinstalling, the system runs perfectly during normal use. However, every time I shutdown or reboot, I consistently get these messages:

Failed to unmount /oldroot: Device or resource busy

Failed to unmount /oldroot/dev/**

Failed to finalize file systems; ignoring

This issue did not happen before the reinstall.

Commands I have already tried:

• sudo touch /forcefsck && sudo reboot

• systemd-analyze blame

• systemd-analyze critical-chain

• mount | grep oldroot

• Even after these tests, the error continues to appear during shutdown.

My questions:

1. What might be preventing /oldroot from being unmounted during shutdown?

2. Could the installation USB created by Rufus be responsible?

3. Should I recreate the boot media using Startup Disk Creator / Balena Etcher / dd and reinstall?

4. Which log files should I collect to find what is holding the mount?

5. Does this issue pose any real risk to my SSD or filesystem integrity?

Any help or guidance will be greatly appreciated. Thank you!

I am trying to upgrade my Kubuntu 25.04 to 25.10.

I am doing it through the command line, using sudo do-release-upgrade.

I am getting this error message:

...
Calculating the changes

Not enough free disk space 

The upgrade has aborted. The upgrade needs a total of 6,819 M free 
space on disk '/var/cache/apt/archives'. Please free at least an 
additional 534 M of disk space on '/var/cache/apt/archives'. 

My /var partition (ext4) has a size of 119 GiB, of which 33 GiB are used. So there is plenty of space available. Why am I getting this error?

Could this be an issue of the upgrade option? Should I do a clean installation?

These are my partitions:

~> df -h
Filesystem       Size  Used Avail Use% Mounted on
tmpfs            5.4G  3.3M  5.4G   1% /run
efivarfs         148K  144K     0 100% /sys/firmware/efi/efivars
/dev/nvme0n1p1   300G   62G  239G  21% /
tmpfs             27G  232M   27G   1% /dev/shm
tmpfs            5.0M   12K  5.0M   1% /run/lock
tmpfs            1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs            1.0M     0  1.0M   0% /run/credentials/systemd-resolved.service
/dev/nvme0n1p4   2.0G  327M  1.5G  18% /tmp
/dev/nvme0n1p3   9.8G   24K  9.3G   1% /extra
/dev/nvme0n1p7    20G   24K   19G   1% /crypt
/dev/nvme0n1p9   117G   34G   77G  31% /var
/dev/nvme0n1p6   100G  9.1G   91G  10% /opt
/dev/nvme0n1p5   787G   61G  686G   9% /home
package_archive  6.0G  151M  5.9G   3% /var/cache/apt/archives
systemd_journal  6.0G   40M  6.0G   1% /var/log/journal
/dev/nvme0n1p8  1022M  6.3M 1016M   1% /boot/efi
tmpfs            5.4G  200K  5.4G   1% /run/user/1000

After using Ubuntu for a year on my laptop, I wanted to upgrade my Windows desktop too. However, when I booted with Linux (in a dual boot, to recover some old files), I was greeted with a working mouse, but no main click.

I tried three different mice (HyperX that requires drivers, DELL and tinb that don't), and for all the tracking worked. Obviously, the gaming mouse didn't work furtier than that, but the other two managed to register right clicks, but no left clicks. This problem does not occur on Windows, but what's wierd (on Linux) is that when I switch the main mouse button to the right, the left click now works, but not the right... I tried this on two distros (Fedora and Ubuntu) and I got the same results...

Thanks in advance !

if we do github authentication with github cli https://cli.github.com/ , then can i make normal git command like git push , git pull or any other normal command which used to require ssh setup ? And should we install cli github just by sudo apt install gh or by following the official docs setup

(type -p wget >/dev/null || (sudo apt update && sudo apt install wget -y)) \
    && sudo mkdir -p -m 755 /etc/apt/keyrings \
    && out=$(mktemp) && wget -nv -O$out https://cli.github.com/packages/githubcli-archive-keyring.gpg \
    && cat $out | sudo tee /etc/apt/keyrings/githubcli-archive-keyring.gpg > /dev/null \
    && sudo chmod go+r /etc/apt/keyrings/githubcli-archive-keyring.gpg \
    && sudo mkdir -p -m 755 /etc/apt/sources.list.d \
    && echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" | sudo tee /etc/apt/sources.list.d/github-cli.list > /dev/null \
    && sudo apt update \
    && sudo apt install gh -y

To upgrade:

sudo apt update
sudo apt install gh

Is there any difference between these two methods ?

Integrated web camera on my Dell Latitude 5550 is not working. Cheese shows a picture of a camera with a slash through it. Discord also does not find the camera. This is where I have gotten with respect to debugging the problem:

ls /dev/video*
/dev/video0  /dev/video1

lsusb | grep -i web
Bus 003 Device 003: ID 0bda:557b Realtek Semiconductor Corp. Integrated_Webcam_FHD

“lsusb -t” for Bus 003 Device 003:
    |__ Port 003: Dev 003, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 003: Dev 003, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 003: Dev 003, If 2, Class=Application Specific Interface, Driver=[none], 480M

What does the "If x" mean?

lsmod | grep uvcvideo
uvcvideo              139264  0
videobuf2_vmalloc      20480  1 uvcvideo
uvc                    12288  1 uvcvideo
videobuf2_v4l2         36864  1 uvcvideo
videodev              352256  2 videobuf2_v4l2,uvcvideo
videobuf2_common       81920  4 videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops
mc                     81920  4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common

It appears that uvcvideo driver is loaded.

I checked in BIOS and the camera is enabled there.

In "syslog" is the following information related to the camera: 
2025-11-16T07:31:54.707023-05:00 Latitude-5550 wireplumber[4076]: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?


2025-11-16T07:31:54.707048-05:00 Latitude-5550 wireplumber[4076]: PipeWire's libcamera SPA missing or broken. libcamera not supported.


2025-11-16T07:31:54.822825-05:00 Latitude-5550 wireplumber[4076]: <WpPortalPermissionStorePlugin:0x653a79b70b60> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camerasyslog:
2025-11-16T07:31:54.707023-05:00 Latitude-5550 wireplumber[4076]: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?


2025-11-16T07:31:54.707048-05:00 Latitude-5550 wireplumber[4076]: PipeWire's libcamera SPA missing or broken. libcamera not supported.


2025-11-16T07:31:54.822825-05:00 Latitude-5550 wireplumber[4076]: <WpPortalPermissionStorePlugin:0x653a79b70b60> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera

Searching for that error on the internet, it says to install the following packages:

1. libcamera-ipa

2. pipewire-libcamera

but neither of these packages exist in the repository.

Next I tried to install pipewire:

sudo apt install pipewire
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
pipewire is already the newest version (1.0.5-1ubuntu3).
pipewire set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Where do I go from here?

I installed wine using the instructions on https://gitlab.winehq.org/wine/wine/-/wikis/Debian-Ubuntu

wine --version gives me wine-10.0

wine --help gives me nothing

wine PROGRAM gives me

Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found.

According to the instructions I can run this: wine setup_hotpot_7030.exe

I get this :

0138:fixme:msg:ChangeWindowMessageFilter c04b 00000001 0138:fixme:win:DisableProcessWindowsGhosting : stub

setup_hotpot_7030 or hot patotoes is rather old freeware, it is set of didactic exercises found on https://hotpot.uvic.ca/

I've run wine setup_hotpot_7030.exe in the downloads folder where the exe file can be found. I've also run it from the home folder.

I can see a hot potatoes configuration window appear asking me what language I want the application to use. I choose 'English' hit 'OK' and the window disappears. And that's it.

I've tried to install via graphical installers, doesn't work. I haven't yet tried out the tar.xz file but then I would have to remove this installation first. Makes me nervous.

I'm running this on a laptop. I made a partition myself (my first ever) and installed ubuntu 22.04 on it and then upgraded it later to 24.04 (noble nombat).

I really don't know what to do. Thank you and greetings,

Karin Meersman

I need to dual boot my Windows 11 system with Ubuntu 22.04.5 LTS (Jammy Jellyfish) to run ROS2, Gazebo and Docker natively. I tried following YT tutorials and yet ran into some errors. I'll be eternally grateful if anyone could guide me through this :)

Note: I'm a CS engineering undergrad and use Ubuntu on ThinkVision extensively at my university labs. I'm comfortable with Bash, the command line and Linux as a whole. However, I have zero experience with dual-booting a Linux distro when an existing closed-source OS is running. I used Perplexity to word my post properly.

1. Search Effort

Several hours on Ubuntu forums, Reddit, and YouTube tutorials about 22.04 dual‑boot and NVIDIA login loop issues.

2. System & Issue

• OS: Ubuntu 22.04.5 LTS Desktop, dual boot with Windows 11 Home SL

• Hardware: Acer Predator Helios Neo 16S AI – Intel Core Ultra 7 255HX, NVIDIA RTX 5050, 16 GB RAM, 1 TB Micron NVMe

• Partitions for Ubuntu: 80 GB ext4 /, 200 GB ext4 /home, 20 GB swap

• Boot: GRUB present; Windows Boot Manager in EFI partition

• Symptom:

  • Ubuntu reaches GUI login screen, then loops back after password.

  • Adding nomodeset at GRUB → black screen with blinking underscore.

  • Windows 11 boots and runs normally.

3. Dual‑Boot Setup (Windows + BIOS steps condensed)

• Disabled Windows Fast Startup.

• Suspended BitLocker (Suspend-BitLocker -MountPoint C:), confirmed protection off.

• Booted Windows into Safe Mode using bcdedit /set {current} safeboot minimal, then reverted.

• In BIOS: disabled Intel VMD controller, left UEFI mode, enabled F12 boot menu, disabled Fast Boot and Secure Boot.

• Confirmed Windows now uses “Standard NVM Express Controller” and C: is visible.

• Shrunk C: in Disk Management and created 300 GB unallocated space for Ubuntu.

• Wrote ubuntu-22.04.5-desktop-amd64.iso to a SanDisk 32 GB USB with Rufus (GPT, UEFI).

4. Ubuntu Install Choices (where things likely went wrong)

• Booted USB with “Try or Install Ubuntu” (not “Ubuntu (safe graphics)”) despite NVIDIA discrete GPU.

• Chose “Normal installation” and checked “Install third‑party software (graphics/Wi‑Fi etc.)”.

• In “Something else” partitioning: created 80G /, 200G /home, 20G swap on the Micron NVMe.

• Bootloader target set to entire disk /dev/nvme0n1 instead of the EFI entry /dev/nvme0n1p1 Windows Boot Manager**.**

After install:

• First and subsequent boots → login loop.

• nomodeset test instead leads to black screen with blinking underscore.

• Recovery mode and new user creation did not restore a working desktop.

5. Current Question

• Install is reproducibly broken from first boot onward.

• ISO checksum is verified correct.

• Windows, BitLocker, and all partitions appear healthy.

• Seeking advice on whether to:

  • Reinstall Ubuntu over existing /, /home, and swap (possibly using “Ubuntu (safe graphics)” and targeting the EFI “Windows Boot Manager” for GRUB), or

  • Attempt repair in place (e.g., reinstall GRUB to EFI and clean up NVIDIA/Nouveau drivers) instead of reinstalling.

  • Uninstall and restart all over again.

6. Tutorials Followed

• How to Dual Boot Ubuntu 22.04 LTS and Windows 11 [ 2022 ]

• How to Dual Boot Ubuntu 22.04 LTS and Windows 10 | Step by Step Tutorial - UEFI Linux

• How to Enable AHCI Mode Without Reinstalling Windows, INACCESSABLE_BOOT_DEVICE Error 💻🛠️🤔

• Changing SATA mode to AHCI (Optane with RAID to AHCI) Acer Predator Helios 300

• How to Fix Ubuntu Linux Freezing on Boot

I purchased a laptop with windows installed. I shrunk the windows partition and created several new ext4 partitions. I installed Ubuntu on one of them. Everything was cool until I goofed and messed up a PAM file and could no longer signin. So I installed a second copy of Ubuntu on another partition. Booted it and was able to fix the file I goofed. Now I want to make the original Ubuntu partition bootable in addition to the second one. BIOS sees windows and the second Ubuntu install as bootable. How can I tell the UEFI system that it can also boot the original Ubuntu partition.

I need to get my Cintiq 13HD working on Ubuntu to even consider the possibility of moving away from Windows for good. But I cannot find the solution to my problem anywhere (I've seen other users ask the same question on this site without any answers):

The tablet "works" on Ubuntu, insofar a it recognizes it, and the pen works. The settings even show a Wacom Tablet tab, letting me "calibrate" it and everything, except the tablet's screen doesn't show anything and remains black. It only shows "No Input Signal" when I turn it on, and shortly goes back to sleep.

On Windows, the tablet works fine (I have dual boot windows/ubuntu) so I know that it's not a cable problem.

I've followed this website's steps to install the wacom to ubuntu, if it helps: https://linuxvox.com/blog/wacom-drivers-linux/

My terminal shows this when I use "xsetwacom --list devices":

Wacom Cintiq 13HD Pad pad id: 11 type: PAD

Wacom Cintiq 13HD Pen stylus id: 12 type: STYLUS

Wacom Cintiq 13HD Pen eraser id: 25 type: ERASER

OS: Ubuntu 20.04.2 LTS and Gnome version 3.36.8

Any answer would be welcome!

I installed the kubuntu desktop environment to test it and, since I am a bit busy to customize it in a way familiar to my previous gnome desktop style and gestures, I decided to uninstalled it for the meantime by selecting all the installed KDE related packages in Synaptic Package Manager. After doing this, and restarting my machine, I get always to tty1 (and I can only move from there to tty 2-6) from which I need to manually restart the gdm3 via

/etc/init.d/gdm3 restart

After this, everything works nicely. So, is there anyway to make it that gdm3 starts by itself like it used to? It is not a system breaking issue, but is quite bothersome to login 3 times to enter my desktop's graphical environment when I had to do it just once, before this. Also, I really, really don't like the idea of reinstalling Ubuntu (since I don't have the time to install everything again and I fear loosing my files) so if I can avoid it it would be great.

Thank you!

I have problems with my wacom, when using a wayland session. Now that X11 is no longer in ubuntu 25.10 this is really a problem.

The most immediately noticeable is that whenever I use my wacom tablet in blender, the mouse-cursor is invisible. This makes it practically unusable.

I also have other weird issues, that never happen when I use blender under X11.

Note: a similar problem occurs when using krita. No mouse pointer visible, for example when selecting a new brush. Makes it very hard to know what you're selecting.

So I just installed xfce, in order to be able to use blender, but I would prefer to use just the default ubuntu-session.

Are there any plans to improve the wacom support under wayland?

I installed on Ubintu 24.04 using
sudo apt-get -y install gnucash
which gave me version 5.5, and this version seems to not work.
Is there a .deb file somewhere that I can get the latest instead?
I don't want to have to build it.

When I start Firefox from Applications or from the Dash, Firefox starts as expected. All my settings are applied. If I start Firefox from "Startup Applications" it looks different. From the System Monitor I find this command line:

/snap/firefox/7355/usr/lib/firefox/firefox

I put it into Startup Applications and Firefox asks me to select one from four profiles and it looks different from what I expect in all four profiles.

When I start Firefox from Applications/Dash I see only one profile named "Original profile".

How to start Firefox from Startup Applications to behave the same as starting it from Applications/Dash?

I'm running Ubuntu Server 24.04.3 LTS on a mini PC as my home network server. It is connected via a Unifi rack-mount switch (US-16-150W, latest firmware) to my OPNsense router (25.7.2).

I typically access the Ubuntu server via SSH from my desktop computer to run updates and maintenance. Periodically (seems to be required more and more as of late...), when I log in to the sever it tells me a reboot is needed. So after I update, I sudo reboot and wait for the SSH terminal to reconnect.

More often than not, the SSH connection never comes back up. So then I dig into my network rack and directly access the server, where I find it sitting at the login screen. If I log in and try to ping a WAN or LAN address, it times out. The LED for the port on the switch that the server is plugged into is either off or solid green (seems to vary), but it is never blinking as if it is transmitting data. No amount of rebooting the server will fix the connectivity, but simply moving the network cable from the server to a different port on the switch will instantly restore network connectivity, after which rebooting the server works without issues for a time.

This initially made me think that specific port on the switch might be bad, but then the issue recurred on another switch port, and I was able to resolve it by swapping the cable back to the previously "bad" switch port. I'm wondering if this might be an issue with the switch itself? Maybe the hardware has gone bad? The Unifi network controller software does run on the Ubuntu server, but even when the server is rebooting, the switch should still function as a "dumb" switch.

The rest of my network seems to be working just fine, which makes me less convinced the issue is the switch and something with the server itself. Any suggestions on how I can troubleshoot this before spending money unnecessarily to replace the switch?

UPDATE: Replaced the network patch cable and this happened again the next time I was forced to reboot, so this wasn't the issue. Here's the outputs from the commands recommended below (might be typos, had to convert from picture to text)

For sudo journalctl -b 0 -u NetworkManager while unable to connect to network:

Nov 30 17:38:57 coruscant systemd[1]: Starting NetworkManager.service - Network Manager... 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524337.9583] NetworkManager (version 1.46.0) is starting... (boot:ac37b8ec-503c-40e2-81f4-c15b3e10ab14)
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524337.9583] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 10-globally-managed-devices.conf, no-mac-addr-change.conf) (etc: default-wifi-powersa 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524337.9711] manager (0x56acbf26f200): monitoring kernel firmware directory '/lib/firmware'. 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524337.9711] monitoring ifupdown state file /run/network/ifstate'. 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0228] hostname: hostname: using hostnamed
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0228] hostname: static hostname changed from (none) to "coruscant"
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0238] dns-mgr: init: dns-systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0258] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi) 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0260] manager (0x56acbf26f200): rfkill: Wi-Fi hardware radio set enabled 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0261] manager [0x56acbf26f200): rfkill: WWAN hardware radio set enabled 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0314] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-wwan.so) 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0334] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-team.so) 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0350] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-wifi.so) 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0381] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-bluetooth.so) 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0391] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-ads1.so) 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0394] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0395] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0396] manager: Networking is enabled by state file
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0420] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-settings-plugin-Ifupdown.so") 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0420] settings: Loaded settings plugin: keyfile (internal)
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0420) Ifupdown: management mode: unmanaged
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.0422] ifupdown: interfaces file /etc/network/interfaces doesn't exist 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.5834] dhcp: init: Using DHCP client 'internal' 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.5836) manager: (1o): new Loopback device (/org/freedesktop/NetworkManager/Devices/1) 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.5842] manager: (eno1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.5847] device (wlp2s0): driver supports Access Point (AP) mode 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.5850) manager: (wlp2s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3) 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.5852] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.6619] failed to open /run/network/ifstate
Nov 30 17:38:58 coruscant systemd[1]: Started NetworkManager.service - Network Manager. 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.6624] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.6649] modem-manager: ModemManager available 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.7082] device (wlp2se): supplicant interface state: internal-starting -> disconnected 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.7083] Wi-Fi P2P device controlled by interface w1p2so created
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.7084] manager: (p2p-dev-wlp2s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4) 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.7086] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524339.5027] device (eno1): carrier: link connected 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524342.1030) manager: startup complete
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524350.3772] manager: (dockero): new Bridge device (/org/freedesktop/NetworkManager/Devices/5) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524350.4140) manager: (br-f514ce707438): new Bridge device (/org/freedesktop/NetworkManager/Devices/6) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.1409] manager: (vethe@abb64): new Veth device (/org/freedesktop/NetworkManager/Devices/7) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.2032] device (vethe@abb64): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.2033] device (br-f514ce707438): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.2174] manager: (veth3ffcf3b): new Veth device (/org/freedesktop/NetworkManager/Devices/8) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.2453] manager: (vethb3f30de): new Veth device (/org/freedesktop/NetworkManager/Devices/9) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.3133] manager: (vethe27b9c1): new Veth device (/org/freedesktop/NetworkManager/Devices/10) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.3180] device (veth3ffcf3b): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.3461] manager: (veth855dea0): new Veth device (/org/freedesktop/NetworkManager/Devices/11) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.3468] device (vethb3f30de): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.3647] device (vethe27b9c1): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.3749] manager: (vethd8691e8): new Veth device (/org/freedesktop/NetworkManager/Devices/12) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.3920] manager: (vetha4c2ea2): new Veth device (/org/freedesktop/NetworkManager/Devices/13) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.4001] device (veth855dea0): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.4237] manager: (veth9578338): new Veth device (/org/freedesktop/NetworkManager/Devices/14) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.4330] device (vethd8691e8): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.4515] device (vetha4c2ea2): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.4573] manager: (veth7ffb054): new Veth device (/org/freedesktop/NetworkManager/Devices/15) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.4773] device (veth9578338): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.4854] manager: (veth1ed4cef): new Veth device (/org/freedesktop/NetworkManager/Devices/16) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.5058] manager: (veth315aeb3): new Veth device (/org/freedesktop/NetworkManager/Devices/17) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.5191] device (veth7ffb054): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.5329] device (veth1ed4cef): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.5546] manager: (veth8ff2d6d): new Veth device (/org/freedesktop/NetworkManager/Devices/18) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.5819] manager: (veth7b37bc6): new Veth device (/org/freedesktop/NetworkManager/Devices/19) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.5826] device (veth315aeb3): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.6003] device (veth8ff2d6d): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.6236] manager: (veth81a08b8): new Veth device (/org/freedesktop/NetworkManager/Devices/20) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.6586] manager: (veth5f86a40): new Veth device (/org/freedesktop/NetworkManager/Devices/21) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.6589] device (veth7b37bc6): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.6914] device (veth81a08b8): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.7061] manager: (veth4c036e4): new Veth device (/org/freedesktop/NetworkManager/Devices/22) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.7260] manager: (veth03f74bb): new Veth device (/org/freedesktop/NetworkManager/Devices/23) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.7434] device (veth5f86a40): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.7564] device (veth4c036e4); carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.7587] manager; (veth17b295a); new Veth device (/org/freedesktop/NetworkManager/Devices/24) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.7796] device (veth03f74bb); carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.7895] manager; (veth20eab21); new Veth device (/org/freedesktop/NetworkManager/Devices/25)
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.8295] device (veth17b295a); carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.8332] manager; (veth56b76b3); new Veth device (org/freedesktop/NetworkManager/Devices/26) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524851.8645] device (veth20eab21); carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.8673] manager; (vethc9b27f4); new Veth device (/org/freedesktop/NetworkManager/Devices/27) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.8873] device (veth56b76b3); carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.9502] device (vethc9b27f4); carrier: link connected

For sudo journalctl -b 0 -u NetworkManager once reconnected to network:

Nov 30 17:38:57 coruscant systemd[1]: Starting NetworkManager.service - Network Manager... 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524337.9583] NetworkManager (version 1.46.0) is starting... (boot:ac37b8ec-503c-40e2-81f4-c15b3e10ab14)
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524337.9583] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 10-globally-managed-devices.conf, no-mac-addr-change.conf) (etc: default-wifi-powersa 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524337.9711] manager (0x56acbf26f200): monitoring kernel firmware directory '/lib/firmware'. 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524337.9711] monitoring ifupdown state file /run/network/ifstate'. 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0228] hostname: hostname: using hostnamed
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0228] hostname: static hostname changed from (none) to "coruscant"
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0238] dns-mgr: init: dns-systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0258] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi) 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0260] manager (0x56acbf26f200): rfkill: Wi-Fi hardware radio set enabled 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0261] manager [0x56acbf26f200): rfkill: WWAN hardware radio set enabled 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0314] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-wwan.so) 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0334] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-team.so) 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0350] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-wifi.so) 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0381] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-bluetooth.so) 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0391] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-device-plugin-ads1.so) 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0394] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0395] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0396] manager: Networking is enabled by state file
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0420] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.46.0/libnm-settings-plugin-Ifupdown.so") 
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0420] settings: Loaded settings plugin: keyfile (internal)
Nov 30 17:38:57 coruscant NetworkManager [811]: <info> [1764524338.0420) Ifupdown: management mode: unmanaged
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.0422] ifupdown: interfaces file /etc/network/interfaces doesn't exist 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.5834] dhcp: init: Using DHCP client 'internal' 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.5836) manager: (1o): new Loopback device (/org/freedesktop/NetworkManager/Devices/1) 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.5842] manager: (eno1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.5847] device (wlp2s0): driver supports Access Point (AP) mode 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.5850) manager: (wlp2s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3) 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.5852] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.6619] failed to open /run/network/ifstate
Nov 30 17:38:58 coruscant systemd[1]: Started NetworkManager.service - Network Manager. 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.6624] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.6649] modem-manager: ModemManager available 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.7082] device (wlp2se): supplicant interface state: internal-starting -> disconnected 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.7083] Wi-Fi P2P device controlled by interface w1p2so created
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.7084] manager: (p2p-dev-wlp2s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4) 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524338.7086] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524339.5027] device (eno1): carrier: link connected 
Nov 30 17:38:58 coruscant NetworkManager [811]: <info> [1764524342.1030) manager: startup complete
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524350.3772] manager: (dockero): new Bridge device (/org/freedesktop/NetworkManager/Devices/5) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524350.4140) manager: (br-f514ce707438): new Bridge device (/org/freedesktop/NetworkManager/Devices/6) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.1409] manager: (vethe@abb64): new Veth device (/org/freedesktop/NetworkManager/Devices/7) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.2032] device (vethe@abb64): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.2033] device (br-f514ce707438): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.2174] manager: (veth3ffcf3b): new Veth device (/org/freedesktop/NetworkManager/Devices/8) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.2453] manager: (vethb3f30de): new Veth device (/org/freedesktop/NetworkManager/Devices/9) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.3133] manager: (vethe27b9c1): new Veth device (/org/freedesktop/NetworkManager/Devices/10) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.3180] device (veth3ffcf3b): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.3461] manager: (veth855dea0): new Veth device (/org/freedesktop/NetworkManager/Devices/11) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.3468] device (vethb3f30de): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.3647] device (vethe27b9c1): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.3749] manager: (vethd8691e8): new Veth device (/org/freedesktop/NetworkManager/Devices/12) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.3920] manager: (vetha4c2ea2): new Veth device (/org/freedesktop/NetworkManager/Devices/13) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.4001] device (veth855dea0): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.4237] manager: (veth9578338): new Veth device (/org/freedesktop/NetworkManager/Devices/14) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.4330] device (vethd8691e8): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.4515] device (vetha4c2ea2): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.4573] manager: (veth7ffb054): new Veth device (/org/freedesktop/NetworkManager/Devices/15) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.4773] device (veth9578338): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.4854] manager: (veth1ed4cef): new Veth device (/org/freedesktop/NetworkManager/Devices/16) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.5058] manager: (veth315aeb3): new Veth device (/org/freedesktop/NetworkManager/Devices/17) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.5191] device (veth7ffb054): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.5329] device (veth1ed4cef): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.5546] manager: (veth8ff2d6d): new Veth device (/org/freedesktop/NetworkManager/Devices/18) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.5819] manager: (veth7b37bc6): new Veth device (/org/freedesktop/NetworkManager/Devices/19) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.5826] device (veth315aeb3): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.6003] device (veth8ff2d6d): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.6236] manager: (veth81a08b8): new Veth device (/org/freedesktop/NetworkManager/Devices/20) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.6586] manager: (veth5f86a40): new Veth device (/org/freedesktop/NetworkManager/Devices/21) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.6589] device (veth7b37bc6): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.6914] device (veth81a08b8): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.7061] manager: (veth4c036e4): new Veth device (/org/freedesktop/NetworkManager/Devices/22) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.7260] manager: (veth03f74bb): new Veth device (/org/freedesktop/NetworkManager/Devices/23) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.7434] device (veth5f86a40): carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.7564] device (veth4c036e4); carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.7587] manager; (veth17b295a); new Veth device (/org/freedesktop/NetworkManager/Devices/24) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.7796] device (veth03f74bb); carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.7895] manager; (veth20eab21); new Veth device (/org/freedesktop/NetworkManager/Devices/25)
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.8295] device (veth17b295a); carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.8332] manager; (veth56b76b3); new Veth device (org/freedesktop/NetworkManager/Devices/26) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524851.8645] device (veth20eab21); carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.8673] manager; (vethc9b27f4); new Veth device (/org/freedesktop/NetworkManager/Devices/27) 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.8873] device (veth56b76b3); carrier: link connected 
Nov 30 17:39:02 coruscant NetworkManager [811]: <info> [1764524351.9502] device (vethc9b27f4); carrier: link connected

service NetworkManager status is the same in either case:

NetworkManager service - Network Manager
    Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: enabled) 
    Active: active (running) since Sun 2025-11-30 17:10:29 UTC; 7min ago
    Docs: man:NetworkManager (8)
    Main PID: 809 (NetworkManager)
    Tasks: 4 (limit: 38011) 
    Memory: 27.4M (peak: 49.7M)
    CPU: 403ms
    CGroup: /system.slice/NetworkManager.service
        809 /usr/sbin/NetworkManager --no-daemon

Nov 30 17:12:32 coruscant NetworkManager[809]: <info> [1764522752.1531] manager: (vethf029d56): new Veth device (/org/freedesktop/NetworkManager/Devices/25) 
Nov 30 17:12:32 coruscant NetworkManager[809]: <info> [1764522752.1761] device (veth560baf3): carrier: link connected 
Nov 30 17:12:32 coruscant NetworkManager[809]: <info> [1764522752.1834] manager: (veth3b80a9b): new Veth device (/org/freedesktop/NetworkManager/Devices/26) 
Nov 30 17:12:32 coruscant NetworkManager[809]: <info> [1764522752.2032] device (vethf029d56): carrier: link connected 
Nov 30 17:12:32 coruscant NetworkManager[809]: <info> [1764522752.2127] manager: (veth4a7e3d7): new Veth device (/org/freedesktop/NetworkManager/Devices/27) 
Nov 30 17:12:32 coruscant NetworkManager[809]: <info> [1764522752.2404] device (veth3b80a9b): carrier: link connected 
Nov 30 17:12:32 coruscant NetworkManager[809]: <info> [1764522752.2729] device (veth4a7e3d7): carrier: link connected 
Nov 30 17:17:35 coruscant NetworkManager[809]: <info> [1764523055.5280] manager: (veth7ad470e): new Veth device (/org/freedesktop/NetworkManager/Devices/28) 
Nov 30 17:17:35 coruscant NetworkManager[809]: <info> [1764523055.7279] manager: (veth4605096): new Veth device (/org/freedesktop/NetworkManager/Devices/29) 
Nov 30 17:17:35 coruscant NetworkManager[809]: <info> [1764523055.7733] device (veth4605096): carrier: link connected

I'll try to be as specific as I can be, let me start:

I'm new to Linux, still fresh off the boat as I been using it for a month already. At first I installed Mint Cinnamon because everyone recommends it as the most suitable option for merging from Windows. Somewhere during its installation, I must have clicked the option to encrypt my /home folder, without realizing.

Since I didn't like some Mint native apps lack features I used a lot on Windows, I started researching into other distros to end up with Kubuntu due to Plasma. Yesterday I removed Mint and installed Kubuntu 24.04 LTS instead, this is how I did it:

1. Loaded into the live session.
2. Loaded the Install process
3. Nanually removed all 3 Mint partitions - boot, swap and root
4. Recreated them with the proper settings - boot at fat32 with /boot mounting point and boot flag, swap at linuxswap and root at ext4 with / mounting point and root flag, just the way I did it on Mint the first time.
5. Kubuntu didnt want to create / at first outputting "Failed to create a new partition on "dev/nvme0np3 (aka /)
6. Installed GParted and made the partition myself there
7. This let Kubuntu install this time - I have no idea why its own installer failed to create the partition...
8. All went well and it installed successfully
9. From then on when I opened Dolphin and headed to /home, I was met with "Access-Your-Private-Data.desktop" and a "README" file, both empty. All files there, just cant access them.
10. Immediately started searching for solution and asking around what to do - took me hours to figure out what to do with the help of some good folks from the community.
11. Ended up decrypting and mounting /home and I can see and browse my files, however
12. Instead of /home being placed in Dolphin file manager in Home on the left side panel, the files now reside in /tmp/ecryptfs.random-numbers-and-letters/, not in the usual way you can access them
13. My question here is: how I can remove the encryption without damaging the files, revert it how it used to be, just pop up the file manager, click on Home on the left panel and boom, there are your files?

NOTE: I have OS installed on a 150 GB partition and /Home on 1.6 TB partition, both form one SSD disk, leaving me with no room where else to move or copy the files beside an external drive, which is quite a hassle.

NOTE 2: I been stuck with this issue for 12 hours already and I cant use the PC properly at all not to break something. Afraid to even reboot now not to lose access. This is kind of a wild cry for help, lol.

NOTE 3: Described the issue better in the title cause I forgot to mention its eCryptFS related.

FINAL EDIT: As pointed out in this post it seems to be a rather general problem with the NVIDIA driver 390.xxx due to the fact that this driver became incompatible with Linux Kernel since the 6.0 version. The only "solution" I see is rolling back to a previous kernel version, which to my (limited) experience means in the long run using an older, potentially outdated and vulnerable version of Ubuntu or aother distro. Still, it seems a better solution than using Windows with paid security updates...

I am running 24.04.1 LTS on my old Asus laptop (ASUSTeK Computer Inc. K53SD). I am trying to install a firmware driver for my old Nvidia GF119M GeForce 610M GPU. When I select the proprietary NVIDIA driver in "Additional Drivers" window I am met with the following error prompt.

I have followed this Ubuntu site guide for installing this driver through commands. The output I get is `All the available drivers are already installed.

I should also mention that I have tried and failed to manually install this driver following a guide from this the official NVIDIA site that asked me to run sh ./NVIDIA-Linux-x86_64-390.157.run as root. I've followed a long sequence of errors and command prompts from the internet to fix these errors that I don't recall and don't understand and eventually gave up.

I then managed to get my "Additional Drivers" GUI to show me my proprietary driver which brought me to this stage.

When typing sudo apt-get upgrade I am prompted with this long message that appears to be a more verbose version of the aforementioned error prompt in the GUI:

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following upgrades have been deferred due to phasing:
  python3-distupgrade ubuntu-release-upgrader-core ubuntu-release-upgrader-gtk
0 to upgrade, 0 to newly install, 0 to remove and 3 not to upgrade.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up nvidia-dkms-390 (390.157-0ubuntu7) ...
update-initramfs: deferring update (trigger activated)
INFO:Enable nvidia
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
Removing old nvidia-390.157 DKMS files...
Deleting module nvidia-390.157 completely from the DKMS tree.
Loading new nvidia-390.157 DKMS files...
Building for 6.8.0-51-generic
Building for architecture x86_64
Building initial module for 6.8.0-51-generic
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-dkms-390.0.crash'
Error! Bad return status for module build on kernel: 6.8.0-51-generic (x86_64)
Consult /var/lib/dkms/nvidia/390.157/build/make.log for more information.
dpkg: error processing package nvidia-dkms-390 (--configure):
 installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-driver-390:
 nvidia-driver-390 depends on nvidia-dkms-390 (<= 390.157-1); however:
  Package nvidia-dkms-390 is not configured yet.
 nvidia-driver-390 depends on nvidia-dkms-390 (>= 390.157); however:
  Package nvidia-dkms-390 is not configured yet.

dpkg: error processing package nvidia-driver-390 (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates it's a follow-up error from a previous failure.
                                                                                                            Processing triggers for initramfs-tools (0.142ubuntu25.4) ...
update-initramfs: Generating /boot/initrd.img-6.8.0-51-generic
Errors were encountered while processing:
 nvidia-dkms-390
 nvidia-driver-390
E: Sub-process /usr/bin/dpkg returned an error code (1)

The complete /var/lib/dkms/nvidia/390.157/build/make.log log is too long to submit here and is completely opaque to me. With my level of experience I don't understand what I am looking at and where I should search for the problem.

I tried to use a Linux virtual machine for the very first time. So I downloaded the VirtualBox and the Ubuntu 24.04 LTS. I found some tutorials how should I finish this process. Everything went well untill the intallation process, it started intalling but its never finished. Now it runs for almos 40 minutes, is it normal? I just see this:

Please somebody help me! I gave for cpu and 8gb of ram and 25 gb storage, my computer is not slow(imo)

I have created a shared folder in Ubuntu and made 2 users i gave all the permissions in smb.cfg . My windows machine can find the shared folder when i double click it it asks for credentials and on the bottom left it says access denied. i use my credentials and the a pop up message says that i have to ask my network administrator for permission. also i open 445 port on windows firewall and active all inbound and outbound that are smb related please advise.

The incomplete output of testparm is this:

[Personal] 
comment = "My Samba File Server" 
path = /share_folder 
read list = usermarios 
valid users = usermarios usernatali 
write list = usermarios

The usershares are this:

[Personal] 
path=/home/morfeas/Desktop/Personal 
comment= 
usershare_acl=Everyone:F, guest_ok=y 

[windows_share] 
path=/home/morfeas/windows_share 
comment= 
usershare_acl=Everyone:F, guest_ok=y
 
[shared_folder] 
path=/home/morfeas/shared_folder 
comment= 
usershare_acl=Everyone:F, guest_ok=n

Trying to use Ubuntu server for a minecraft server with friends. Not had much luck. Basically when it gets to the DHCP part of the install for the network configuration, there is no IP address and the box above it eth0 says not connected. I don't know how to make it connect. I've tried several options such as using the sudo nano command thing (DHCP is set to true), and when I try to use the resolvconf command it won't let me and says I need to download it, which I can't because of no connection to the internet. I'm using an old laptop, not a desktop, to do this server, and I know it said somewhere a direct connection with an ethernet cable is better, but that's not an option for me. Laptop is an HP Pavilion dm4.

I'm a former windows user and completly new to linux and ubuntu (I had no idea what kernel, or booted, or distro was until a day ago). I just installed it to try it out. I am however not able to change the keyboard layout in the log in screen (I had to click on many keys to finally be able to get the password that I wanted). It was not obvious for me which keyboard to choose during the installation process (I tried French AZERTY, since there was no Belgian AZERTY option, and the French AZERTY was also different from my keyboard, so I went for USA English).

However, later after the intallation of ubuntu, I was able to change in settings to Belgian keyboard layout. So, now I can type normally with my Belgian AZERTY keyboard on the browser or in the Terminal. However, this change was not applied to the log in screen.

The Log-in screen is now in AZERTY, but not the Belgian format of my keyboard (but the Belgian keyboard is activated once I log-in).

Can someone guide me? Thank you for your help!

I would like to install Ubuntu 22.04 on a PC with an NVMe solid-state drive for the OS and a traditional hard drive for /home, using full disk encryption.

Before I buy the hardware, I have been trying to experiment with installing Ubuntu 22.04 on a virtual machine with two SATA drives to emulate this setup. As the machine will be used as a desktop, I have been using the desktop installer.

If I choose full disk encryption during installation, the installer seems to want to install everything to a single drive and I don't get any control over partitioning.

If I choose the advanced option, I get some manual partitioning options but it's not obvious to me how things should be set up for encryption. The closest I got to a working configuration was something like:

I couldn't figure out how to add any swap, which I would want to be encrypted as well. I wasn't actually able to proceed with the install in this case as the "Install Now" button was greyed out.

I have put the biosgrub, EFI and /boot partitions on the hard drive because the BIOS on the fairly old system I'd be using almost certainly won't be able to boot from the NVMe SSD. This is obviously not an issue with the virtual machine I'm testing with.

Is this configuration possible or am I asking too much? It's actually worse than this, as I would really like to use bcache as well and have part of the SSD set aside to cache the /home partition, but I haven't put that in the title of the question as I thought it might be more helpful to ask about this without adding bcache into the mix.

Would it be better to use the server installer? Would it be simplest to let the desktop installer put everything on a single drive then try to fix things up afterwards?

Looking at existing questions:

• I found How to install Ubuntu with LVM & LUKS on a SSD and use an LUKS encrypted HDD for data on a Dell Inspiron 7580 but this seems to relate to Ubuntu 19.04 and it's not clear to me that the advice is still applicable.
• How to install Ubuntu with both disk encryption AND SSD caching looks like it's exactly what I want, but it's from 2015 so I'm not sure it's still applicable.

Any advice would be greatly appreciated, even if it's just "don't do that!". :-)

I am running ubuntu on macbook pro (2013) and it is getting overheating compared to MACOS even with the mbpfan enabled. Are there any other ways to further reduce the running temperature? I see back in 2010 there is a way to manually set the fan rule with this https://bbs.archlinux.org/viewtopic.php?id=71187

I have a Mac book pro with Intel/Nvidia graphic card and I enabled the Nvidia graphic card Nvidia GPU usage

I have installed the mbpfan with the following temperature configuration:

[general]
# see https://ineed.coffee/3838/a-beginners-tutorial-for-mbpfan-under-ubuntu for the values
# 
# mbpfan will load the max / min speed of from the files produced by the applesmc driver. If these files are not found it will set all fans to the default of min_speed = 2000 and max_speed = 6200
# by setting the values for the speeds in this config it will override whatever it finds in:
# /sys/devices/platform/applesmc.768/fan*_min
# /sys/devices/platform/applesmc.768/fan*_max
# or the defaults.
#
# multiple fans can be configured by using the config key of min_fan*_speed and max_fan*_speed
# the number used will correlate to the file number of the fan in the applesmc driver that are used to control the fan speed.
#
#min_fan1_speed = 2000  # put the *lowest* value of "cat /sys/devices/platform/applesmc.768/fan*_min"
#max_fan1_speed = 6200  # put the *highest* value of "cat /sys/devices/platform/applesmc.768/fan*_max"
#low_temp = 63          # try ranges 55-63, default is 63
low_temp = 55           # try ranges 55-63, default is 63
#high_temp = 66         # try ranges 58-66, default is 66
high_temp = 58          # try ranges 58-66, default is 66
max_temp = 86           # take highest number returned by "cat /sys/devices/platform/coretemp.*/hwmon/hwmon*/temp*_max", divide by 1000
polling_interval = 1    # default is 1 seconds

While my Macbook temperature is still very high, anyone knows how to further control the overheating issue on macbook-ubuntu?

$ sensors
applesmc-isa-0300
Adapter: ISA adapter
Left side  : 3474 RPM  (min = 2160 RPM, max = 5940 RPM)
Right side : 3042 RPM  (min = 2000 RPM, max = 5499 RPM)
TB0T:         +36.0°C  
TB1T:         +36.0°C  
TB2T:         +34.5°C  
TC0E:         +65.5°C  
TC0F:         +67.5°C  
TC0P:         +51.5°C  
TC1C:         +63.0°C  
TC2C:         +63.0°C  
TC3C:         +63.0°C  
TC4C:         +61.0°C  
TCGC:         +63.0°C  
TCSA:         +58.0°C  
TCTD:          -0.2°C  
TCXC:         +65.2°C  
TG0D:         +61.8°C  
TG0P:         +56.0°C  
TG1D:         +64.0°C  
TG1F:         +63.2°C  
TG1d:         +58.0°C  
TH0A:         +37.8°C  
TH0B:         +40.8°C  
TH0V:         +41.0°C  
TH0a:         +37.8°C  
TH0b:         +40.8°C  
TH0c:        -127.0°C  
TH0x:         +40.8°C  
TM0P:         +52.0°C  
TM0S:         +51.2°C  
TMBS:         +51.0°C  
TP0P:         +53.5°C  
TPCD:         +56.0°C  
TS0D:        -127.0°C  
TS0P:        -127.0°C  
TS1D:        -127.0°C  
TS1P:        -127.0°C  
TW0P:         +47.5°C  
Ta0P:         +42.8°C  
TaSP:         +40.0°C  
Th1H:         +44.2°C  
Th2H:         +53.0°C  
Ts0P:         +33.0°C  
Ts0S:         +40.0°C  
Ts1S:         +41.0°C  

BAT0-acpi-0
Adapter: ACPI interface
in0:          12.40 V  
temp:         +36.3°C  
curr1:         0.00 A  (avg =  +0.00 A)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +64.0°C  (high = +87.0°C, crit = +105.0°C)
Core 0:        +64.0°C  (high = +87.0°C, crit = +105.0°C)
Core 1:        +64.0°C  (high = +87.0°C, crit = +105.0°C)
Core 2:        +64.0°C  (high = +87.0°C, crit = +105.0°C)
Core 3:        +64.0°C  (high = +87.0°C, crit = +105.0°C)

BAT0-virtual-0
Adapter: Virtual device
temp1:        +36.3°C  

https://www.wps.com/office/linux/

this used to run fine, now nothing happens when I run WPS office.

I'm on Ubuntu 20.10, and I like desktop launcers. Yes, they are a pain to make now that gnome-desktop-item-edit is a thing of the past, but I manage. Most often I copy a .desktop file from another machine, or I create a new one by hand... But where is the setting stored that makes it launchable? It is NOT stored in the launcher file itself (no changes after it is made launchable), it is also NOT stored in the file permission bits. To launch the program I have to right-click on the launcher and select allow launching. I hate it! This changes something somewhere in my directory structure, but what? I haven't done a recursive grep to search for this – I don't know what to look for in that case. Hoping for a pointer here instead, so I can make the thing launchable when I create it. Thanks!

I've recently bought a new laptop (Dell Venue 11 Pro), which can also be turned into a tablet with a removable keyboard and touchpad.

However, the touchpad isn't working and also the cursor is not shown. I have to use the touch screen for all of my work.

I really need assistance in setting up SNMP to work with Zabbix on my dashboard. I have set up an Ubuntu 18.04 Zabbix server and have added over 18 agents. All virtual machines with Zabbix agents and they are working great!

Now I have gotten to the point where I need to have the AP's set up for Zabbix. I have followed the instructions and did the following so far:

sudo apt-get update
sudo apt-get install snmp snmp-mibs-downloader
sudo apt-get update
sudo apt-get install snmpd

I opened sudo nano /etc/snmp/snmp.conf and commented the following line:

#mibs :

Then I went into the configuration file:

sudo nano /etc/snmp/snmpd.conf

And from there I made changes to the following lines:

Listen for connections from the local system only
agentAddress  udp:127.0.0.1:161  <--- commented this part.
Listen for connections on all interfaces (both IPv4 and IPv6)
agentAddress udp:161,udp6:[::1]:161  <--remove the comment from this line to make it work.

Then I set up the Zabbix dashboard side. I will attach pictures of the set-up.

1st zabbix dashboard menu:

2nd dashboard set-up menu:

I get the following error:

I will also attach picture that shows my meraki access point set-up.

Meraki AP SNMP set-up:

Lastly, I will add a picture that shows the Linux Zabbix server terminal set up on that config file.

Linux Zabbix Server:

I am stumped and cannot figure out why Zabbix still throwing out that error.

I have gone thru the Zabbix documentation but cannot find a solution to my problem.

As the title states the mouse cursor on my laptop isn't moving but the mouse buttons still work. I'm not sure what to do. I have tested the touchpad on Windows and it works fine.

My laptop is a HP Envy

Xinput output xinput list

Virtual core pointer    id=2 [master pointer (3)]
Virtual core XTEST pointer    id =4 [slave pointer (2)]
SynPS/2 synaptics TouchPad id=12 [slave pointer (2)]

uname -r

3.16.0-49-generic

lspci -K | grep -EA2 'VGA|3D'

00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
    Subsystem: Hewlett-Packard Company Device 1966
    Kernel driver in use: i915

01:00.0 3D controller: NVIDIA Corporation GK208M [Geoforce GT 740M] (rev a1)
    Subsystem: Hewlett-Packard company device 219c

lspci -k | grep -EA2 'VGA|3D' after driver install

00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
    Subsystem: Hewlett-Packard Company Device 1966
    Kernel driver in use: i915

01:00.0 3D controller: NVIDIA Corporation GK208M [Geoforce GT 740M] (rev a1)
    Subsystem: Hewlett-Packard company device 219c
    Kernel driver in use: nvidia

Edit

Turns out that a USB Mouse does work but I have yet to find out why my TrackPad stopped working.

I recently installed Ubuntu successfully instead of Windows 7 and it was working very good. Suddenly while I was working, it restarted my computer and after I chose Ubuntu from grub it give me this error

mount: mounting/dev/disk/by-uuid/85a771fc-3df4-40e0-8e3d-b01d76019d5f on/root
failed: Invalid argument
mount: mounting/dev on/root/dev failed: No such file or directory
mount: mounting/sys on/root/sys failed: No such file or directory
mount: mounting/proc on/root/proc failed: No such file or directory
Target filesystem doesn't have requested/sbin/init.
No init found. Try passing init=bootarg.

BusyBox v1.21.1 (ubuntu 1:1.21.0-1ubuntu1) built-in shell(ash)
Enter 'help' for a list of built-in commands.
(initramfs)

I need to get to the sound settings and change the output to HDMI.

From the menu, bottom left, I can choose System Tools or Preferences but neither contains a link to sound settings, which apparently is where I change it.

On occasion, my laptop has become stuck so I've used the magic key combination of Alt + SysRq + REISUB to perform a safe reboot. However, it doesn't seem to work for me as when I press the B key to complete the magic key command it simply says, "resetting..." and doesn't do anything.

All of the other keys seem to work fine as it resets the keyboard layout, kills all tasks etc., but it doesn't seem to complete with a reboot.

I was under the impression that my laptop should reboot after the magic keys have all been pressed in the order of REISUB.