Ubuntu 22.04 / cron-service / disable mail globally https://askubuntu.com/questions/1567668/ubuntu-22-04-cron-service-disable-mail-globally

i would like to disable mail globally for all cron-jobs in /etc/cron.d/*

Tried following different approaches without success:

  1. /etc/environment: Added MAILTO=""
  2. /etc/crontab: Added MAILTO=""
  3. /etc/systemd/system/crond.service.d/override.conf:
[Service]
Environment="MAILTO="

sudo systemctl daemon-reload

sudo systemctl restart cron


I would like to avoid setting MAILTO in every cron-file in /etc/cron.d/ ...

Hope you have some cool ideas :-)

Best Regards

No focus, no paste in Ubuntu https://askubuntu.com/questions/1567667/no-focus-no-paste-in-ubuntu

Recently I got problems with my Ubuntu 22.04 using Gnome: I can’t paste with the mouse middle button. New windows didn’t get focus or remained hidden. I tried several suggestions from the web but to no avail. I installed 25.04 and 26.04 on the side using the same home directory. The same problems. A new user with a fresh home on any of the installations has no problems. My experiments shows that the problems are associated with the home/.config directory. My .config is, however, huge and I have difficulties finding the culprit file or files. Can anyone pls help me. Any tip is appreciated. Håkan

GNOME Panel & Activities Overview workspace thumbnails flickering issue https://askubuntu.com/questions/1567665/gnome-panel-activities-overview-workspace-thumbnails-flickering-issue

GNOME Activities Overview workspace thumbnails begin flickering after several hours of uptime on Ubuntu 26.04 LTS with GNOME Shell 50.1 running on Wayland and Intel Alder Lake-N integrated graphics (i915 driver).

System:

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

Symptoms:

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

I’ve tried:

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

Observations:

  • The issue does not affect application rendering or the desktop outside of Activities Overview.
  • It appears only after extended uptime (hours), not immediately after login.
  • The issue is reproducible across reboots and kernel versions.
  • No relevant errors in journalctl related to i915, DRM, or GPU resets.

Question:

Has anyone seen GNOME Activities Overview workspace thumbnail flickering or corruption on GNOME Shell 50 / Mutter 50 under Wayland, particularly on Intel integrated graphics? Are there known issues, workarounds, or logs that I should investigate further?

Epson L220 scanner is not getting detected in Ubuntu 24.04 https://askubuntu.com/questions/1567664/epson-l220-scanner-is-not-getting-detected-in-ubuntu-24-04

Epson L220 scanner is not getting detected in Ubuntu 24.04. I installed the official linux drivers for the device from epson website and it is working fine. Previously if i remember correctly, the epson l220 scanner would get detected automatically in onlder versions of ubuntu. requesting help to resolve this from the community. Thank you.

Root filesystem mount failure (Gave up waiting) on NVMe - Dell Latitude 7200 https://askubuntu.com/questions/1567661/root-filesystem-mount-failure-gave-up-waiting-on-nvme-dell-latitude-7200

I’m struggling with a persistent boot issue on my Dell Latitude 7200 2-in-1. I am trying to install and run Ubuntu (the latest LTS release), but I consistently hit the Gave up waiting for root file system device error during the boot process.

Hardware & Setup:

  • Laptop: Dell Latitude 7200 2-in-1.

  • Processor: Intel Core i3-8145U.

  • RAM: 4.00 GB.

  • Drive: 119 GB NVMe SSD (The drive is fully functional as the laptop boots Windows 10/11 without any issues).

  • BIOS Configuration: BIOS Storage mode is set to default (RAID mode).

What I've tried so far:

  • Attempted to resolve the boot delay by adding rootdelay=10 and nvme_core.default_ps_max_latency_us=0 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub.

  • Performed update-initramfs -u -k all and update-grub via chroot after mounting the EFI partition.

  • Even attempted manual PCI rescan via init-premount scripts, but the issue persists.

It seems the kernel isn't initializing the NVMe controller fast enough to detect the root partition UUID at the early boot stage. Since the hardware works perfectly under Windows, I suspect a specific timing issue or a missing power management quirk for this model.

Has anyone encountered this specific behavior on a Latitude 7200? Is there a known kernel parameter or a specific firmware tweak that I'm missing?

How to unlock custom refresh rate https://askubuntu.com/questions/1567657/how-to-unlock-custom-refresh-rate

I have asus monitor and it supports overclock to 270 hz. but ubuntu 26.04 only can recognize 240hz, if I install nvidia rtx 3060 gpu and it's drivers I can get 270hz, but for some reason my AMD rx 9070xt gpu and display can only give me 240hz, I've tried to make some changes through xrandr but no luck, changes I make are not applying and my custom options not showing up, I've also tried to use software Linux_CRU-x86_64 but still no dice. Can someone assist me?

Ethernet connection fails after 20 seconds https://askubuntu.com/questions/1567655/ethernet-connection-fails-after-20-seconds

My Ethernet connection on my 26.04 computer drops after ~20 seconds and won't come back on. I was having intermittent Ethernet issues on 24.04 and I thought upgrading to 26.04 would fix it. After a fresh install, my internet connection works briefly after each reboot, but it drops very shortly after.

My connection was rock solid until I updated my Ubiquiti OS a few days ago. This box was the only box on my network that was affected.

I tried many different ways to fix it, to no avail:

Hardware:

  • Gigabyte B650 Aorus Elite ax ice

  • TP link TX201 2.5 Gb PCIe network adapter card

Why is my MediaTek MT7902 (14c3:7902) Wi-Fi not working on Ubuntu 26.04 even though it’s detected but shows as UNCLAIMED? https://askubuntu.com/questions/1567650/why-is-my-mediatek-mt7902-14c37902-wi-fi-not-working-on-ubuntu-26-04-even-tho

I’m having a Wi-Fi issue on my ASUS Vivobook (X1504ZA) running Ubuntu 26.04 LTS. I don’t really know much about this kind of Linux/driver/network stuff, so I’ve been trying to figure it out step by step.

Hardware info

My Wi-Fi card shows up as:

  • MediaTek MT7902 802.11ax (Filogic 310)

  • PCI ID: 14c3:7902


What works

  • Internet works fine using USB tethering from my phone

  • System is updated (kernel: 7.0.0-22-generic)

  • Everything else on the system seems normal


What doesn’t work

  • No Wi-Fi option appears in network settings

  • nmcli shows no Wi-Fi device at all

  • The Wi-Fi hardware is detected by the system but marked as UNCLAIMED

  • The mt7921e driver loads, but it does not attach to this device


What I found (with help)

I honestly don’t know much about drivers or kernel stuff, so I used an AI assistant to help me troubleshoot step by step. We checked logs, drivers, and kernel modules together.

From what we found:

  • The Linux mt76 / mt792x drivers are installed

  • But they don’t seem to support my exact chip (14c3:7902)

  • So the system detects the hardware, but no driver actually connects to it


Current situation

It looks like the Wi-Fi chip is not supported (or not fully supported yet) in my current Linux setup.


Workaround

I’m currently just using USB tethering from my phone, which works fine for internet.


Why I’m posting

Since I don’t really understand this technical stuff deeply, I thought I’d ask here in case someone knows a fix, patch, or workaround for this specific Wi-Fi chip.

Any help would be really appreciated 🙏 Should i install windows now?

Can I use eGalax touchscreen without proprietary driver on Ubuntu 24.04? https://askubuntu.com/questions/1567647/can-i-use-egalax-touchscreen-without-proprietary-driver-on-ubuntu-24-04

I'm trying to get eGalax touchscreen to run on Ubuntu 24.04 without proprietary driver from https://www.eeti.com/drivers_Linux.html. The touchscreen controller is properly detected:

paul@cube:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 003 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 003 Device 005: ID 0573:1573 Zoran Co. Personal Media Division (Nogatech) USB Audio and HID
Bus 003 Device 006: ID 2516:0004 Cooler Master Co., Ltd. Storm QuickFire Rapid Mechanical Keyboard
Bus 003 Device 007: ID 0eef:0001 D-WAV Scientific Co., Ltd Titan6001 Surface Acoustic Wave Touchscreen Controller [eGalax]
Bus 003 Device 008: ID 1c4f:0034 SiGma Micro XM102K Optical Wheel Mouse
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
paul@cube:~$ xinput --list
⎡ Virtual core pointer                      id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ eGalax Inc. USB TouchController           id=14   [slave  pointer  (2)]
⎜   ↳ SIGMACHIP Usb Mouse                       id=10   [slave  pointer  (2)]
⎣ Virtual core keyboard                     id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
    ↳ Power Button                              id=8    [slave  keyboard (3)]
    ↳ Sleep Button                              id=9    [slave  keyboard (3)]
    ↳ CM Storm QuickFire Rapid keyboard         id=11   [slave  keyboard (3)]
    ↳ CM Storm QuickFire Rapid keyboard Consumer Control    id=12   [slave  keyboard (3)]
    ↳ CM Storm QuickFire Rapid keyboard System Control  id=13   [slave  keyboard (3)]
    ↳ Intel HID events                          id=15   [slave  keyboard (3)]
paul@cube:~$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 16384 x 16384
HDMI-1 connected primary 1280x1024+0+0 (normal left inverted right x axis y axis) 360mm x 290mm
   1280x1024     75.02*+  60.02  
...

As suggested by AI, I did:

sudo apt install xserver-xorg-input-evdev xinput-calibrator
sudo modprobe usbtouchscreen usbhid
xinput --map-to-output "eGalax Inc. USB TouchController" HDMI-1

but xinput_calibrator app responds only to the mouse not to the touchscreen. Is there anything else I need to install or configure?

Unable to install Ubuntu 24.04 when Secure Boot is enabled https://askubuntu.com/questions/1567642/unable-to-install-ubuntu-24-04-when-secure-boot-is-enabled

I'm trying to install Ubuntu 24.04 desktop using a bootable USB with Secure Boot enabled. I'm getting the error message: Selected boot image did not authenticate. How can I resolve this issue?

I have checked platform supported. The same bootable media works with Secure Boot disabled.

converting RTL PDF to text https://askubuntu.com/questions/1567631/converting-rtl-pdf-to-text

I have scanned pdf and I want to convert it to text. I have Ubuntu 24.04.
I installed ocrmypdf and made my pdf file searchable.
Then I tried to install pdf2txt:

$ python3 --version 
Python 3.12.3  
$ pip install pdfminer.rtl
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.
    
    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.
    
    If you wish to install a non-Debian packaged Python application,
    it may be easiest to use pipx install xyz, which will manage a
    virtual environment for you. Make sure you have pipx installed.
    
    See /usr/share/doc/python3.12/README.venv for more information.

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
$ sudo apt install python3-pdfminer.rtl
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package python3-pdfminer.rtl
E: Couldn't find any package by glob 'python3-pdfminer.rtl'

How can I make it work?
Maybe I have to install another package?

I succeeded to do this with Google Drive:
uploaded the PDF to Google Drive and opened it with 'Open with > Google Docs'.
High resolution helps.

Still, is there a Linux way to do this?

Laptop battery percentage stays at 80% even after powering off https://askubuntu.com/questions/1567630/laptop-battery-percentage-stays-at-80-even-after-powering-off

I have Preserve Battery Health option enabled on Ubuntu 25.10. It is limiting the battery charging capacity at around 80% level but even after shutting down the laptop and turning it on next morning, I see the battery level at 80%.

Doesn't it suppose to start at 100% and go down to %80 and stay there? Since OS have no control on the battery after shut down, it should be charged to the maximum level.

What am I missing?

Ubuntu Studio 26.04 and intermittent GUI-lockup https://askubuntu.com/questions/1567599/ubuntu-studio-26-04-and-intermittent-gui-lockup

On installing Ubuntu Studio 26.04 from scratch, I ended-up with an unusable system due to the screen getting scrambled+lockup at random moments several times per day. I have likewise experience on Ubuntu 25.10. This scramble+lockup was not there on earlier versions. HW has - amongst others - a Geforce RTX card driving my monitor. Googling around suggests that there is an incompatibility-issue against wayland. Before I ditch this (not exactly cheap) video-card, what options do I have? I know that I can workaround back to Xorg to some point, however, that can only be a temp workaround as all distro's seem to be forced to move to wayland. So Xorg is likely to become a narrower path every day.

Video card = GeForce RTX 2060 Rev. A I Installed Ubuntu from scratch and have not added anything related to Nvidia, manually.

This morning, I found that when logging in on the GUI desktop, it logs me out after some thing like 10 seconds. ssh-access is OK.

Update: installed 595 nvidia-driver + reboot. Desktop GUI is now usable. Have to wait and see if issues around stability are fixed by this.

Ubuntu 26.04 - After copying a file, nautilus selects all files in the folder https://askubuntu.com/questions/1567399/ubuntu-26-04-after-copying-a-file-nautilus-selects-all-files-in-the-folder

Does anyone know why nautilus selects all files in the folder after you copy a file into the folder? Is there a way to avoid that?

How to run properly Xen 4.20 over Ubuntu 26.04LTS to provide to VMs passthrough access to GPU? https://askubuntu.com/questions/1567362/how-to-run-properly-xen-4-20-over-ubuntu-26-04lts-to-provide-to-vms-passthrough

By the old guide for Xen 4.11 and Ubuntu 14.04, the:

$ sudo apt install xen-hypervisor-amd64
$ sudo reboot

lead to booting into:

Loading Xen 4.20-amd64... 
Loading Linux 7.0.0-22-generic... 
Loading initial ramdisk...

This is a dead-lock state when the OS gets stuck. By the reboot it is possible to enter via GRUB menu into regular Ubuntu and configure the environment.

Using this and this guides, which are also very old, these lines are added into /etc/default/grub instead of default similar lines:

GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=10
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noirqbalance i915.enable_guc=0 intel_iommu=on xen-pciback.hide=(0000:00:02.0) module_blacklist=i915"
GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=8192M,max:8192M dom0_max_vcpus=4 iommu=on,no-igfx,verbose"

Then sudo update-grub && sudo update-initramfs -c -k 7.0.0-22-generic && sudo reboot . In Ubuntu 26.04 LTS and Xen 4.20 this also leads into getting stuck on Loading initial ramdisk...

Running these "guards" under root permissions is considered to reserve the GPU for Xen:

tee /etc/modprobe.d/blacklist-i915.conf << EOF
blacklist i915
EOF

tee /etc/modprobe.d/xen-pciback.conf << EOF
options xen-pciback hide=(0000:00:02.0)
EOF

update-initramfs -u
reboot

However, this does not help either. The boot gets stuck on Loading initial ramdisk...

I am struggling to find up-to-date documentation for Xen. Last official manuals are ending at Xen 4.9, now we're at 4.20.

I tried to install Ubuntu with SSD encryption and without, with Intel TXT enabled and disabled. The result is the same.

This solution was also tried. It results in total skip of Xen boot and loading plain Ubuntu, as expected by the solution but not clear how did it help in that case.

Xen Gurus, what else should be set, changed, deleted, updated in the Ubuntu 26.04 to run Xen 4.20 and provide to VMs passthrough access to GPU?

openssh-server post-installation script error (exit status 10) and SSH not working https://askubuntu.com/questions/1566463/openssh-server-post-installation-script-error-exit-status-10-and-ssh-not-worki

I’m encountering an issue where openssh-server fails during configuration, and SSH is currently not working on my system.

This error appears during package operations, even when I’m not explicitly trying to install openssh-server.

What happens

During apt/dpkg operations, I see:

Setting up openssh-server (1:9.6p1-3ubuntu13.16) ...
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess returned error exit status 10
Errors were encountered while processing:
 openssh-server

What I’ve tried

  1. Re-running configuration:
sudo dpkg --configure -a

Same error persists.


  1. Running the post-install script manually with debugging:
sudo bash -x /var/lib/dpkg/info/openssh-server.postinst configure

This didn’t produce any obvious error output, and the last line is `exec /usr/share/debconf/frontend /var/lib/dpkg/info/openssh-server.postinst configure which tells me that something to do with package configuration is failing.


  1. Regenerating SSH host keys:
sudo rm -f /etc/ssh/ssh_host_*
sudo ssh-keygen -A

Keys were generated successfully, but the issue remains.

  1. Restore ssh config:
sudo cp /usr/share/openssh/sshd_config /etc/ssh/sshd_config

Observations

  • SSH into this machine is not functioning.

  • The openssh-server package is broken.

  • The post-installation script consistently exits with status 10.


Research

I found that post-installation script failures can be caused by misconfiguration or missing files, but most solutions suggest reinstalling or purging the package. I haven’t found a clear explanation for exit status 10 specifically or how to resolve it without risking further issues.

Previously, I have used this sequence of commands to fix similar errors:

rm -rf /var/lib/dpkg/info/<packagename>* (in this case openssh*)

dpkg --configure -a

Fix package post-installation script subprocess returned error exit status 10 for libpaper1:amd64

Error reinstalling isc-dhcp-server "post installation script returned error exit status 255"

Like in the above posts, which has fixed the error temporarily, but probably messed up the dpkg package lists or something.

The issue keeps coming back, it's a different package or packages every time so it seems like an issue with dpkg or a corrupt filesystem.

Any ideas what is causing this issue, and how I can resolve it without reinstalling the system?

Update: I got ssh server working again, but still seeing the error on install/configure. getting closer. these are the commands that fixed it and my logic behind them

sudo cp /usr/share/openssh/sshd_config /etc/ssh/sshd_config

-- there was no sshd config until i copied it from here

--- then uncommented the host keys in that file, and generated them. made sshd user

grep -n "HostKey" /etc/ssh/sshd_config
ls -l /etc/ssh/sshd_config.d
sshd -T | grep hostkey
sudo nano /etc/ssh/sshd_config
sshd -t
ls -l /etc/ssh/ssh_host_*
namei -l /etc/ssh/ssh_host_rsa_key
sudo ssh-keygen -lf /etc/ssh/ssh_host_rsa_key
sshd -T | head -50
lsattr /etc/ssh/ssh_host_rsa_key
mount | grep " / "
sudo rm -f /etc/ssh/ssh_host_*
sudo ssh-keygen -A
sudo ls -l /etc/ssh/ssh_host_*
sudo /usr/sbin/sshd -t -f /etc/ssh/sshd_config
getent passwd sshd
id sshd

--- no sshd user??

sudo adduser --system --no-create-home --group sshd
getent passwd sshd
sudo sshd -t -f /etc/ssh/sshd_config
sudo mkdir -p /run/sshd
sudo chmod 755 /run/sshd
sudo sshd -t -f /etc/ssh/sshd_config
sudo systemctl restart ssh
systemctl status ssh --no-pager
sudo dpkg --configure -a
sudo apt -f install

--- still seeing the error here but the server is up and i can connect from another machine

edit:

ssh has been working fine for weeks, now seeing the same error with libreoffice (I haven't installed them recently, but I did a package upgrade).

Setting up libreoffice-base (4:24.2.7-0ubuntu0.24.04.5) ...
dpkg: error processing package libreoffice-base (--configure):
 installed libreoffice-base package post-installation script subprocess returned error exit status 10
Setting up libreoffice-math (4:24.2.7-0ubuntu0.24.04.5) ...

ok another edit:

I've been reading in the post-install scripts, including adding 'set -x' at the top, and I noticed openssh and gdm3 now both fail at or near a line involving ucf. I tried this purge command on ucf, still failed. Reinstalling got rid of the error for now. I hope this helps!

sudo nano /var/lib/dpkg/info/openssh-server.postinst # (adding set -x to see the error, then reconfigured with dpkg)
sudo ucf --purge /etc/ssh/sshd_config
sudo ucf --purge /etc/gdm3/greeter.dconf-defaults
sudo apt-get install --reinstall ucf debconf debconf-i18n
Ubuntu 24.04.4 LTS linux kernel 6.17.0-23-generic boots to initramfs alert UUID does not exist https://askubuntu.com/questions/1566364/ubuntu-24-04-4-lts-linux-kernel-6-17-0-23-generic-boots-to-initramfs-alert-uuid

initramfs_alert_uuid

available kernets

I can't do much on busybox / initramfs because listing the partions / blocks returns nothing (I tested the ls /dev/sd* /dev/nvme* /dev/vd* 2>/dev/null I saw from this post

Same ending when starting on kernel 6.17.0-23-generic in recovery mode. Happily, kernel 6.17.0-22-generic still works (this is what I am currently using to write this post)

Can someone help me ?

What I did before getting this error : (I think) I was able to work on kernel 6.17.0-23-generic at least one time. But got some troubles to have my laptop HDMI output working. However, the HDMI on my USBC hub was working. So I decided to change the driver from X.org to NVIDIA driver 595-open. Reboot was needed, and since, I have this error message. Using older kernel 6.17.0-22-generic, I switched back to Xorg, but does not solved my initramfs alert.

I booted to my windows boot, to perform some update (included a lot of DELL bios updates) after getting this error. Still did not magically solved my error.

Ouput of sudo blkid :

/dev/nvme0n1p7: UUID="bd26295c-ba4d-4842-825a-f6d18d9e39aa" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="43b443de-457b-4c3b-a703-b809df0b8b23"
/dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop29: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop19: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/nvme0n1p5: LABEL="Image" BLOCK_SIZE="512" UUID="26260B4A260B1B07" TYPE="ntfs" PARTUUID="8ab846ce-c954-4df8-8446-2bc7e2f49f34"
/dev/nvme0n1p3: TYPE="BitLocker" PARTLABEL="Basic data partition" PARTUUID="9f5503c2-21a4-4912-985a-8b1754fceee3"
/dev/nvme0n1p1: LABEL_FATBOOT="ESP" LABEL="ESP" UUID="9C91-0681" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="7996296c-826a-4e45-b14b-bde50ed1b8b4"
/dev/nvme0n1p6: LABEL="DELLSUPPORT" BLOCK_SIZE="512" UUID="62B0AC18B0ABF129" TYPE="ntfs" PARTUUID="5e1e97fe-6cbc-4f07-9437-d0a3aad4f2be"
/dev/nvme0n1p4: LABEL="WINRETOOLS" BLOCK_SIZE="512" UUID="5E160B09160AE1BF" TYPE="ntfs" PARTUUID="2507d349-09cc-49c9-84fe-851a5a54d498"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="4b84bd57-13e9-46d9-a74c-32ec46221756"
/dev/loop37: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop27: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop17: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop8: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop35: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop25: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop15: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop6: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop33: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop23: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop13: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop41: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop4: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop31: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop21: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop11: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop2: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop38: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop28: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop18: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop9: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop36: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop26: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop16: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop7: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop34: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop24: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop14: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop5: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop32: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop22: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop12: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop40: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop3: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop30: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop20: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop10: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop39: BLOCK_SIZE="131072" TYPE="squashfs"

Edit 5th Mai 07h14 (Paris time)

@heynnema

On older kernel 6.17.0-22-generic, on ubuntu with gnome DE

sudo dpkg --configure -a returns nothing

dkms status returns nothing. Neither dkms status --verbose nor dkms status -k 6.17.0-23-generic etc. dkms --version returns dkms-3.2.1 (remark : being on ubuntu 24.04, I was expecting version 3.0.11)

ls -al /boot returns

total 295378
drwxr-xr-x  4 root root     4096 mai    5 06:17 .
drwxr-xr-x 23 root root     4096 févr. 16  2025 ..
-rw-r--r--  1 root root   296189 nov.  20 09:36 config-6.14.0-37-generic
-rw-r--r--  1 root root   302833 mars  25 19:31 config-6.17.0-22-generic
-rw-r--r--  1 root root   302833 avril 14 16:36 config-6.17.0-23-generic
drwxr-xr-x  4 root root     2048 janv.  1  1970 efi
drwxr-xr-x  5 root root     4096 mai    5 06:17 grub
lrwxrwxrwx  1 root root       28 mai    3 14:08 initrd.img -> initrd.img-6.17.0-23-generic
-rw-r--r--  1 root root 82368452 mai    3 14:23 initrd.img-6.14.0-37-generic
-rw-r--r--  1 root root 83048783 mai    3 15:22 initrd.img-6.17.0-22-generic
-rw-r--r--  1 root root 56362952 mai    5 06:17 initrd.img-6.17.0-23-generic
lrwxrwxrwx  1 root root       28 mai    3 14:08 initrd.img.old -> initrd.img-6.17.0-22-generic
-rw-r--r--  1 root root   142796 avril  8  2024 memtest86+ia32.bin
-rw-r--r--  1 root root   143872 avril  8  2024 memtest86+ia32.efi
-rw-r--r--  1 root root   147744 avril  8  2024 memtest86+x64.bin
-rw-r--r--  1 root root   148992 avril  8  2024 memtest86+x64.efi
-rw-------  1 root root  9159323 nov.  20 09:36 System.map-6.14.0-37-generic
-rw-------  1 root root 10475441 mars  25 19:31 System.map-6.17.0-22-generic
-rw-------  1 root root 10475441 avril 14 16:36 System.map-6.17.0-23-generic
lrwxrwxrwx  1 root root       25 mai    3 14:08 vmlinuz -> vmlinuz-6.17.0-23-generic
-rw-------  1 root root 15571336 nov.  20 09:38 vmlinuz-6.14.0-37-generic
-rw-------  1 root root 16734280 mars  25 20:06 vmlinuz-6.17.0-22-generic
-rw-------  1 root root 16738376 avril 14 16:41 vmlinuz-6.17.0-23-generic
lrwxrwxrwx  1 root root       25 mai    3 14:08 vmlinuz.old -> vmlinuz-6.17.0-22-generic

On newer kernel 6.17.0-23-generic during initramfs

sudo is not found so running only fsck -f /dev/nvme0n1p7. It returns :

fsck from util-linux 2.39.3
fsck: error 2 (No such file or directory) while executingfsck.ext2 for /dev/nvme0n1p7

It returns the same after calling exit once on initramfs (and getting the error message on the picture of orginal post) and recalling fsck -f /dev/nvme0n1p7.

[SOLVED] 5th Mai 16h26 (Paris time)

Before fixing the problem here is what I got, following Mauru's post here

$ modinfo -k 6.17.0-23-generic vmd
modinfo: ERROR: Module vmd not found.

$ modinfo -k 6.17.0-22-generic vmd
filename:       /lib/modules/6.17.0-22-generic/kernel/drivers/pci/controller/vmd.ko.zst
version:        0.6
license:        GPL v2
description:    Volume Management Device driver
author:         Intel Corporation
srcversion:     70500AB0DE14E7FDA57546E
alias:          pci:v00008086d0000B07Fsv*sd*bc*sc*i*
alias:          pci:v00008086d0000B06Fsv*sd*bc*sc*i*
alias:          pci:v00008086d0000B60Bsv*sd*bc*sc*i*
alias:          pci:v00008086d00009A0Bsv*sd*bc*sc*i*
alias:          pci:v00008086d0000AD0Bsv*sd*bc*sc*i*
alias:          pci:v00008086d00007D0Bsv*sd*bc*sc*i*
alias:          pci:v00008086d0000A77Fsv*sd*bc*sc*i*
alias:          pci:v00008086d00004C3Dsv*sd*bc*sc*i*
alias:          pci:v00008086d0000467Fsv*sd*bc*sc*i*
alias:          pci:v00008086d000028C0sv*sd*bc*sc*i*
alias:          pci:v00008086d0000201Dsv*sd*bc*sc*i*
depends:        
intree:         Y
name:           vmd
retpoline:      Y
vermagic:       6.17.0-22-generic SMP preempt mod_unload modversions 
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        1C:15:2C:3C:7F:DD:E1:AA:E4:66:2B:B6:9E:E8:B3:66:58:1F:CE:F2
sig_hashalgo:   sha512
signature:      47:E0:A1:04:85:20:32:10:3F:FA:F7:04:4E:33:7D:BC:1A:0E:79:BA:
        FC:A9:92:FB:7B:F7:D9:BE:BC:EC:8C:80:8C:7F:E0:2B:CC:BE:B1:15:
        C4:82:EA:5E:60:B3:54:AB:C9:58:12:0A:F9:F8:BA:4E:19:0A:EC:56:
        8C:7E:55:86:8C:AC:B3:0F:C2:7A:8B:7D:B1:0A:D2:CF:41:81:D6:61:
        1D:47:E2:FD:D3:6A:10:76:00:69:2E:4B:1F:3F:9F:B1:15:C8:BD:10:
        C6:52:05:F3:09:0C:19:DA:D3:16:28:3F:03:F0:56:7A:7F:71:DB:28:
        F0:C0:A6:AD:23:89:19:D4:D9:16:E0:05:C8:EF:0B:86:F6:22:B7:FA:
        37:25:FA:6A:A8:50:57:F4:90:3B:DC:2A:A9:8A:1D:63:1A:E5:1E:25:
        CA:74:4A:CF:F2:5F:E6:89:A3:22:57:AF:A9:9D:0B:5E:BF:73:64:78:
        6E:0E:DC:2C:D5:09:FA:F1:3D:21:99:62:5D:36:89:F3:8A:21:45:83:
        56:77:C2:8C:CF:FB:29:C8:4C:E8:FA:28:3C:94:F0:DF:EF:81:52:A6:
        3D:39:CD:B3:37:0B:10:E6:D4:59:76:90:D8:3B:10:0F:78:3F:95:35:
        46:0D:F3:02:70:0C:6C:A3:3F:B5:4C:CD:E4:EC:5C:FF:68:7A:E3:AF:
        A3:05:EF:F2:96:4B:6E:A0:14:8E:BA:C8:CD:93:1F:BC:49:B2:E6:05:
        DB:9F:C8:25:D9:F8:98:3D:C5:29:B2:96:42:58:D6:F5:41:F9:C9:D0:
        70:D4:30:9A:11:C4:DF:AE:22:55:68:DB:C4:34:FB:6D:AA:B6:A5:95:
        A0:89:3B:92:74:93:E3:1E:C6:60:5E:7D:78:59:54:A2:86:EE:9E:F0:
        4D:03:47:45:C6:79:E5:D2:0D:13:64:D1:24:E7:AA:0F:07:72:7D:40:
        7A:D2:76:0B:24:55:22:99:3A:29:9A:05:9A:93:B9:81:E0:C4:F4:8D:
        91:D5:CB:1E:1C:43:57:AE:20:57:25:29:2B:60:9E:F4:7C:FF:50:B0:
        BC:B7:D9:76:3A:DA:5D:83:A6:15:0E:03:F4:12:DE:C3:11:04:3B:5F:
        77:3C:86:56:CA:B9:EA:36:0A:69:81:A4:89:64:83:29:29:CC:DB:26:
        91:95:F7:D6:FC:27:93:EF:FA:F7:5C:A8:9C:03:CB:44:D9:4E:36:7E:
        4E:BA:29:58:E2:D6:3B:ED:2A:56:98:89:F4:65:61:D0:10:57:D8:AE:
        DB:86:7B:3E:D2:D9:6F:BD:8D:18:A0:E0:F3:AA:CC:41:7F:DE:D0:C3:
        E8:3E:F4:CC:64:07:CB:38:51:91:6E:77

So I did what Mauru's post proposed here

sudo apt install linux-modules-extra-6.17.0-23-generic
sudo update-initramfs -c -k 6.17.0-23-generic
sudo update-grub

Then rebooting and now it boots until working gnome D.E. with kernel 6.17.0-23-generic. Thank you all for your support !

Ubuntu 24.04.4 on RISCV64 unable to detect Wacom Intuos Drawing Tablet connected by USB https://askubuntu.com/questions/1566097/ubuntu-24-04-4-on-riscv64-unable-to-detect-wacom-intuos-drawing-tablet-connected

My new CPU of RISCV64 architecture running on Ubuntu 24.4 is not able to detect the WACOM Intuos drawing tablet using the default GNOME drivers.

I've tried a backgrade of the GNOME starting the login with the "GNOME on XORG" option but the attempt was not successful as the Linux started very slow and showed blockings at access of the setup functions. I also was not able to run an X based diagnostics due to slowness.

My debug shows that the GNOME tablet window is active but does not show any device information. Back to default GNOME login, I see the following error:

rangepi@orangepirv2:~$ xsetwacom --list devices
Wayland devices found but this tool is incompatible with Wayland. See
https://github.com/linuxwacom/xf86-input-wacom/wiki/Wayland

The tablet is visible at ID 06, but does not interact with the Linux mouse (pointer) function.

orangepi@orangepirv2:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 002 Device 003: ID 046d:c077 Logitech, Inc. Mouse
Bus 002 Device 004: ID 258a:0049 BY Tech Gaming Keyboard
Bus 002 Device 005: ID 056a:033c Wacom Co., Ltd CTH-490 [Intuos Art/Photo/Comic (S)]
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I appreciate a guidance how to make it visible to the default Wayland & GNOME drivers.

How to use VNC server in KDE Wayland? https://askubuntu.com/questions/1565787/how-to-use-vnc-server-in-kde-wayland

I used to use VNC but it does not work with Wayland.

How can I connect to my Kubuntu 26.04 (Wayland) computer from another computer in another network so that I can access its GUI, just like in VNC?

Being able to access Wayland with VNC is important because KDE's support for X.Org is going away in 1 year.

/dev/ttyACM0 permission denied on Ubuntu 24.04 https://askubuntu.com/questions/1531140/dev-ttyacm0-permission-denied-on-ubuntu-24-04

I'm struggling to access an MCU connected to the USB and presented as a serial port: /dev/ttyACM0. What worked well in Ubuntu 22.04 does not work in 24.04. Whenever I connect the device, the only way to have it access is to chmod 666 it, but that works only temporarily.

The user I'm working on is already added to the dialout group, and ls -l /dev/ttyACM0 returns: crw-rw---- 1 root dialout 166, 0 Oct 25 15:33 /dev/ttyACM0 , so as I can understand it, it is the root who has r/w and any dialout group member. Am I missing anything here to configure/add? enter image description here

Edit: The driver seems to be correct so that is not the case of invalid UDEV rule triggered:

[21856.363341] usb 3-6: new full-speed USB device number 6 using xhci_hcd
[21856.761217] usb 3-6: New USB device found, idVendor=2e8a, idProduct=0005, bcdDevice= 1.00
[21856.761236] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[21856.761240] usb 3-6: Product: Board in FS mode
[21856.761244] usb 3-6: Manufacturer: MicroPython
[21856.761247] usb 3-6: SerialNumber: e6614c311b7f8c38
[21857.365083] cdc_acm 3-6:1.0: ttyACM0: USB ACM device
[21857.365219] usbcore: registered new interface driver cdc_acm
[21857.365225] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
mp4 codecs missing after upgrading to Ubuntu 24.04.1 LTS https://askubuntu.com/questions/1527252/mp4-codecs-missing-after-upgrading-to-ubuntu-24-04-1-lts

HW Info:

  • HW Model: Dell Inc. Latitude E6540
  • MEM: 4,0 GiB
  • Processor: Intel® Core™ i5-4300M × 4
  • Graphics: Intel® HD Graphics 4600 (HSW GT2)
  • SSD: 256,1 GB

SW Information:

  • firmware: A09
  • OS: Ubuntu 24.04.1 LTS
  • Built OS: (null)
  • Type OS: 64bit
  • Version GNOME: 46
  • window system: Wayland
  • Kernel: Linux 6.8.0-45-generic

Ubuntu cannot open MP4 files after upgrade over Ubuntu 22 LTS Codecs are missing and the searching machine dindn't find any suitable codec.

Everything run before upgrade.

Many thanks for any suggestion.

Jouza


Many thanks for your support and for your time Archisman.

I tried both commands: sudo apt install ubuntu-restricted-extras and sudo apt install --reinstall ubuntu-desktop^

Installation was successful but without any result.

Additionally I realized that Ubuntu cannot open only mp4 from my drone DJI Mini4 PRO before processing in video editor. There is no problem after video processing and also with other mp4 files.

The issue with mp4 from drone before processing in video editor persists: enter image description here
Missing:

meta/x-gst-fourcc-dbgi and
meta/x-gst-fourcc-djmd

I found only discussion about similar issue: https://stackoverflow.com/questions/76305443/gstreamer-missing-decoder-meta-x-gst-fourcc-mebx but didn't find any suitable SW for my codecs.

As said I had no problem before Ubuntu upgrade.

Any idea please?

Cheers! Josef

No network access from within Docker container https://askubuntu.com/questions/1445229/no-network-access-from-within-docker-container

I can't access the Internet or even the local network (a network printer) from within a container. For example, pinging google.com's IP:

docker run --rm busybox ping -c 2 142.250.186.142

outputs:

PING 142.250.186.142 (142.250.186.142): 56 data bytes

--- 142.250.186.142 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss

With --network=host, it works:

docker run --rm --network=host busybox ping -c 2 142.250.186.142

Host is Ubuntu 22.10. And it used to work until last week. My colleagues using Windows as an host can ping fine.

I tried:

More details:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.10
Release:        22.10
Codename:       kinetic

$ docker info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Docker Buildx (Docker Inc., v0.9.1-docker)
  compose: Docker Compose (Docker Inc., v2.12.2)
  scan: Docker Scan (Docker Inc., v0.21.0)

Server:
 Containers: 1
  Running: 0
  Paused: 0
  Stopped: 1
 Images: 1
 Server Version: 20.10.21
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: a05d175400b1145e5e6a735a6710579d181e7fb0
 runc version: v1.1.4-0-g5fd4c4d
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.19.0-26-generic
 Operating System: Ubuntu 22.10
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 15.4GiB
 Name: boris-ThinkPad-T480
 ID: ZN24:57QW:KT4M:J5H6:BIHZ:BF6I:KDV2:EAM6:CESL:UWNE:43AL:LUAJ
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 24
  Goroutines: 34
  System Time: 2022-12-12T20:08:42.528459605+01:00
  EventsListeners: 0
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

$ docker version
Client: Docker Engine - Community
 Version:           20.10.21
 API version:       1.41
 Go version:        go1.18.7
 Git commit:        baeda1f
 Built:             Tue Oct 25 18:01:58 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.21
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.18.7
  Git commit:       3056208
  Built:            Tue Oct 25 17:59:49 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.12
  GitCommit:        a05d175400b1145e5e6a735a6710579d181e7fb0
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

$ cat /proc/sys/net/ipv4/ip_forward
1

$ iptables -Z && iptables -nvL > before.txt && docker run --rm busybox ping -c 3 142.250.186.142 > ping.txt  &&  iptables -nvL > after.txt && cat before.txt && cat ping.txt && diff before.txt after.txt
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 LIBVIRT_INP  all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 DOCKER-USER  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
    0     0 DOCKER-ISOLATION-STAGE-1  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     all  --  *      docker0  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
    0     0 DOCKER     all  --  *      docker0  0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     all  --  docker0 !docker0  0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     all  --  docker0 docker0  0.0.0.0/0            0.0.0.0/0           
    0     0 LIBVIRT_FWX  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
    0     0 LIBVIRT_FWI  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
    0     0 LIBVIRT_FWO  all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 LIBVIRT_OUT  all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain DOCKER (1 references)
 pkts bytes target     prot opt in     out     source               destination         

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 DOCKER-ISOLATION-STAGE-2  all  --  docker0 !docker0  0.0.0.0/0            0.0.0.0/0           
    0     0 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain DOCKER-ISOLATION-STAGE-2 (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 DROP       all  --  *      docker0  0.0.0.0/0            0.0.0.0/0           
    0     0 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain DOCKER-USER (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain LIBVIRT_FWI (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     all  --  *      virbr0  0.0.0.0/0            192.168.122.0/24     ctstate RELATED,ESTABLISHED
    0     0 REJECT     all  --  *      virbr0  0.0.0.0/0            0.0.0.0/0            reject-with icmp-port-unreachable

Chain LIBVIRT_FWO (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     all  --  virbr0 *       192.168.122.0/24     0.0.0.0/0           
    0     0 REJECT     all  --  virbr0 *       0.0.0.0/0            0.0.0.0/0            reject-with icmp-port-unreachable

Chain LIBVIRT_FWX (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     all  --  virbr0 virbr0  0.0.0.0/0            0.0.0.0/0           

Chain LIBVIRT_INP (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     udp  --  virbr0 *       0.0.0.0/0            0.0.0.0/0            udp dpt:53
    0     0 ACCEPT     tcp  --  virbr0 *       0.0.0.0/0            0.0.0.0/0            tcp dpt:53
    0     0 ACCEPT     udp  --  virbr0 *       0.0.0.0/0            0.0.0.0/0            udp dpt:67
    0     0 ACCEPT     tcp  --  virbr0 *       0.0.0.0/0            0.0.0.0/0            tcp dpt:67

Chain LIBVIRT_OUT (1 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     udp  --  *      virbr0  0.0.0.0/0            0.0.0.0/0            udp dpt:53
    0     0 ACCEPT     tcp  --  *      virbr0  0.0.0.0/0            0.0.0.0/0            tcp dpt:53
    0     0 ACCEPT     udp  --  *      virbr0  0.0.0.0/0            0.0.0.0/0            udp dpt:68
    0     0 ACCEPT     tcp  --  *      virbr0  0.0.0.0/0            0.0.0.0/0            tcp dpt:68
PING 142.250.186.142 (142.250.186.142): 56 data bytes

--- 142.250.186.142 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
1c1
< Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
---
> Chain INPUT (policy ACCEPT 220 packets, 56220 bytes)
3c3
<     0     0 LIBVIRT_INP  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
---
>   220 56220 LIBVIRT_INP  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
5c5
< Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
---
> Chain FORWARD (policy ACCEPT 3 packets, 252 bytes)
7,8c7,8
<     0     0 DOCKER-USER  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
<     0     0 DOCKER-ISOLATION-STAGE-1  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
---
>     6   504 DOCKER-USER  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
>     6   504 DOCKER-ISOLATION-STAGE-1  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
11c11
<     0     0 ACCEPT     all  --  docker0 !docker0  0.0.0.0/0            0.0.0.0/0           
---
>     3   252 ACCEPT     all  --  docker0 !docker0  0.0.0.0/0            0.0.0.0/0           
13,15c13,15
<     0     0 LIBVIRT_FWX  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
<     0     0 LIBVIRT_FWI  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
<     0     0 LIBVIRT_FWO  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
---
>     3   252 LIBVIRT_FWX  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
>     3   252 LIBVIRT_FWI  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
>     3   252 LIBVIRT_FWO  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
17c17
< Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
---
> Chain OUTPUT (policy ACCEPT 267 packets, 34045 bytes)
19c19
<     0     0 LIBVIRT_OUT  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
---
>   267 34045 LIBVIRT_OUT  all  --  *      *       0.0.0.0/0            0.0.0.0/0           
26,27c26,27
<     0     0 DOCKER-ISOLATION-STAGE-2  all  --  docker0 !docker0  0.0.0.0/0            0.0.0.0/0           
<     0     0 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0           
---
>     3   252 DOCKER-ISOLATION-STAGE-2  all  --  docker0 !docker0  0.0.0.0/0            0.0.0.0/0           
>     6   504 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0           
32c32
<     0     0 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0           
---
>     3   252 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0           
36c36
<     0     0 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0           
---
>     6   504 RETURN     all  --  *      *       0.0.0.0/0            0.0.0.0/0

$ sudo iptables -L -v -n -t  nat
Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
  129 46233 DOCKER     all  --  *      *       0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type LOCAL

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 DOCKER     all  --  *      *       0.0.0.0/0           !127.0.0.0/8          ADDRTYPE match dst-type LOCAL

Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    6   504 MASQUERADE  all  --  *      !docker0  172.17.0.0/16        0.0.0.0/0           
18336 2849K LIBVIRT_PRT  all  --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain DOCKER (2 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 RETURN     all  --  docker0 *       0.0.0.0/0            0.0.0.0/0           

Chain LIBVIRT_PRT (1 references)
 pkts bytes target     prot opt in     out     source               destination         
   29  2852 RETURN     all  --  *      *       192.168.122.0/24     224.0.0.0/24        
    0     0 RETURN     all  --  *      *       192.168.122.0/24     255.255.255.255     
    2   120 MASQUERADE  tcp  --  *      *       192.168.122.0/24    !192.168.122.0/24     masq ports: 1024-65535
    6  3810 MASQUERADE  udp  --  *      *       192.168.122.0/24    !192.168.122.0/24     masq ports: 1024-65535
    2    64 MASQUERADE  all  --  *      *       192.168.122.0/24    !192.168.122.0/24
kernel panic not syncing: Attempted to kill init! exitcode=0x00000100 (ubuntu 18.04lts) https://askubuntu.com/questions/1390355/kernel-panic-not-syncing-attempted-to-kill-init-exitcode-0x00000100-ubuntu-18

I'm a newbie in ubuntu.

I want to get help because I'm facing a kernel panic problem like below.

enter image description here

So I googled and found some solutions and tried.

Solution1. Tried another version of kernel and its recovery mode.

enter image description here

I tried all of them. And they showed same kernel panic and exitcode=0x00000100.

Solution2. Made Ubuntu 18.04 LTS Live USB and tried to boot with USB.

But my computer displayed nothing then.

Solution3. Tried to boot manually in grub2 command line following this link. https://www.linux.com/training-tutorials/how-rescue-non-booting-grub-2-linux/

But in grub, I couldn't found any sda or other device in /dev directory enter image description here

Thanks for reading and apologize for my poor English.

Linux file manager similar to Windows File Explorer (directory tree + file list)? https://askubuntu.com/questions/1291745/linux-file-manager-similar-to-windows-file-explorer-directory-tree-file-list

Which Linux file manager has a UI that mimics Windows File Explorer in a way that it supports a split view with:

  • a directory tree on the left, and
  • a file list on the right?
Help with installing boot grub in Windows 10 https://askubuntu.com/questions/1224848/help-with-installing-boot-grub-in-windows-10

I'm having a hard time trying to install on my Windows 10 the Grub bootloader. I downloaded the Ubuntu 18.04.4-desktop-amd64 ISO then ran the Ubuntu live session, then I ran this command sudo fdisk -l

SSD:

Image of my SSD

According to some internet articles I need to shrink my current SSD at least by 400 MB in order to format a boot partition as EFI FAT32 with a proper flag, and with that I will be able to install GRUB there. I have never used a Linux distro before.

Would someone here give me guidance me with proper commands in order to shrink my current drive which has 223 size, but only has a free space of 33 GIB? I only need a 400 MB boot partition.

Once I have installed Grub, finally I would be able to ran the grub configuration to finally fix the HPET of my motherboard firmware among other things.

With GRUB booting Windows, I can access to the configuration of the motherboard firmware allowed in Asrock, and with that force High Event Precision Timing to Disable Cause in a regular way my motherboard firmware is causing issues with HPET forced enable even if I disabled it, so with the GRUB there is a configuration to force HPET to disable, and force the Windows timer to 3.580 MHz.

Why are upgradable packages not upgraded? https://askubuntu.com/questions/1181852/why-are-upgradable-packages-not-upgraded

Executing sudo apt update ended with

Reading package lists... Done
Building dependency tree       
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.

Executing apt list --upgradable gave me

Listing... Done
onionshare/bionic,bionic 2.2.ppa1-1 all [upgradable from: 2.1-1]
ring-all/unknown 20190927.2.c2af011~dfsg1-1 amd64 [upgradable from: 20190629.2.c07ef23~dfsg1-1]

But executing sudo apt upgrade does not upgrade the upgradable packages:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1. Why is that? Unmet dependencies possibly?
  2. Can I (manually) upgrade the listed packages, and if so: how?

Update: See this pastebin for a full transcript.

How do I set my keyboard layout to work like the Windows mnemonic Russian keyboard? https://askubuntu.com/questions/1011428/how-do-i-set-my-keyboard-layout-to-work-like-the-windows-mnemonic-russian-keyboa

This is the mnemonic Russian keyboard in Windows.

This

while this is the phonetic Russian layout in Ubuntu.

this

In Windows there are some Russian characters mapped in different keys and also:

From Wikipedia:

Windows 10 includes its own implementation of a mnemonic QWERTY-based input method for Russian, which does not fully rely on assigning a key to every Russian letter, but uses the sh, sc, ch, ya (ja), yu (ju), ye (je), yo (jo) combinations to input ш, щ, ч, я, ю, э and ё respectively.

Error at startup "No module named 'six'" https://askubuntu.com/questions/963964/error-at-startup-no-module-named-six

I am running Ubuntu 17.04 and for some time now, every time I start my machine I get an error about the package-data-downloader that crashed because of No module named 'six'. See this screenshot:
enter image description here

I am wondering if it might have something to do with my Python3.6 and Anaconda installs. When I run python -V && which python I get:

Python 3.6.2 :: Anaconda, Inc.
/home/user/anaconda3/bin/python

So when I saw that the InterpreterPath was pointing to python3.5, I wondered if it might be related.

If anyone can help me out it would be appreciated.

Ubuntu 16.04: display manager fails to start https://askubuntu.com/questions/833466/ubuntu-16-04-display-manager-fails-to-start

Reposting the question from: https://unix.stackexchange.com/q/314129/193223

I recently upgraded from Ubuntu 14.04 to 16.04 after which the display manager stopped working.

Assuming it's due to the init systems, I tried to switch back to upstart by following the instructions given on this page:

https://wiki.ubuntu.com/SystemdForUpstartUsers

It didn't work.

newton@gravity:~$ sudo systemctl status lightdm
● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; enabled; vendor preset: enabled)
  Drop-In: /lib/systemd/system/display-manager.service.d
           └─xdiagnose.conf
   Active: inactive (dead) (Result: exit-code) since Mon 2016-10-03 19:04:26 EDT; 13min ago
     Docs: man:lightdm(1)
  Process: 3533 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
  Process: 3528 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, status=0/SUCCESS)
 Main PID: 3533 (code=exited, status=1/FAILURE)

Oct 03 19:04:26 newton systemd[1]: lightdm.service: Failed with result 'exit-code'.
Oct 03 19:04:26 newton systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Oct 03 19:04:26 newton systemd[1]: Stopped Light Display Manager.
Oct 03 19:04:26 newton systemd[1]: lightdm.service: Start request repeated too quickly.
Oct 03 19:04:26 newton systemd[1]: Failed to start Light Display Manager.
Oct 03 19:09:02 newton systemd[1]: Stopped Light Display Manager.

journalctl shows issues with PAM kwallet.

$ sudo journalctl -e -u lightdm
...
systemd[1]: Starting Light Display Manager...
systemd[1]: Started Light Display Manager.
lightdm[26952]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
lightdm[26952]: PAM adding faulty module: pam_kwallet.so
lightdm[26952]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
lightdm[26952]: PAM adding faulty module: pam_kwallet5.so
lightdm[26952]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0)
systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: lightdm.service: Unit entered failed state.
systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
systemd[1]: lightdm.service: Failed with result 'exit-code'.

...

Here's the content of /var/log/lightdm/lightdm.log;

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.18.2, UID=0 PID=26937
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registered seat module xlocal
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Monitoring logind for seats
[+0.00s] DEBUG: New seat added from logind: seat0
[+0.00s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.00s] DEBUG: Seat seat0: Starting
[+0.00s] DEBUG: Seat seat0: Creating greeter session
[+0.00s] DEBUG: Seat seat0: Creating display server of type x
[+0.01s] DEBUG: Using VT 7
[+0.01s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.01s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log
[+0.01s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0
[+0.01s] DEBUG: DisplayServer x-0: Launching X Server
[+0.01s] DEBUG: Launching process 26944: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.01s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.01s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1007 added
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1009 added
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1006 added
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1005 added
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1002 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1011 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1008 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1003 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1004 added
[+0.02s] DEBUG: User /org/freedesktop/Accounts/User1010 added
[+0.23s] DEBUG: Got signal 10 from process 26944
[+0.23s] DEBUG: DisplayServer x-0: Got signal from X server :0
[+0.23s] DEBUG: DisplayServer x-0: Connecting to XServer :0
[+0.23s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.23s] DEBUG: Session pid=26952: Started with service 'lightdm-greeter', username 'lightdm'
[+0.25s] DEBUG: Session pid=26952: Authentication complete with return value 0: Success
[+0.25s] DEBUG: Seat seat0: Session authenticated, running command
[+0.25s] DEBUG: Session pid=26952: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter
[+0.25s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+0.25s] DEBUG: Session pid=26952: Logging to /var/log/lightdm/seat0-greeter.log
[+0.27s] DEBUG: Activating VT 7
[+0.27s] DEBUG: Activating login1 session c17
[+0.27s] DEBUG: Seat seat0 changes active session to c17
[+0.27s] DEBUG: Session c17 is already active
[+0.37s] DEBUG: Greeter closed communication channel
[+0.37s] DEBUG: Session pid=26952: Exited with return value 0
[+0.37s] DEBUG: Seat seat0: Session stopped
[+0.37s] DEBUG: Seat seat0: Stopping; failed to start a greeter
[+0.37s] DEBUG: Seat seat0: Stopping
[+0.37s] DEBUG: Seat seat0: Stopping display server
[+0.37s] DEBUG: Sending signal 15 to process 26944
[+0.50s] DEBUG: Process 26944 exited with return value 0
[+0.50s] DEBUG: DisplayServer x-0: X server stopped
[+0.50s] DEBUG: Releasing VT 7
[+0.50s] DEBUG: DisplayServer x-0: Removing X server authority /var/run/lightdm/root/:0
[+0.50s] DEBUG: Seat seat0: Display server stopped
[+0.50s] DEBUG: Seat seat0: Stopped
[+0.50s] DEBUG: Required seat has stopped
[+0.50s] DEBUG: Stopping display manager
[+0.50s] DEBUG: Display manager stopped
[+0.50s] DEBUG: Stopping daemon
[+0.50s] DEBUG: Exiting with return value 1

Any other debugging tips that I need to try?
Overscanning picture problem using HDMI with Intel Graphics https://askubuntu.com/questions/508358/overscanning-picture-problem-using-hdmi-with-intel-graphics

When I use my laptops HDMI on a TV the TV overscales the picture (~5-10% is missing at the edges). There is no option on the TV (sporting a 720p resolution btw). The comp is running Intel HD Graphics 4000.

There is no options to compensate for this in the Ubuntu Settings and I been playing around with xrandr (using transform/scale) but nothing seems to work. The plethora of guides on this subject using transform doesn't work me. This is so annoying since it seems to be so easy to fix ("compressing"/resizing the image to fit the screen) but I have run out of ideas. Setting custom resolutions doesn't help (still parts out of the screen). Its basically 2 clicks away to fix in windows but in ubuntu it seems impossible...

Would be really happy if someone could help me out or have any ideas what I could try! Thanks.