Extra cursor and tiling problem https://askubuntu.com/questions/1567679/extra-cursor-and-tiling-problem

I am facing the same problem, whereas i don't use an external tablet, I have a touchscreen display, the tiling is a problem where when i shrink back the windows it automatically snaps it to the top left corner, this voids me of the ability to move the windows to my desired location. Also the extra cursor in the top left constantly bugs me. I reinstalled ubuntu from scratch and it still is right there. I use a lenovo yoga 7 with amd ryzen 7 and in built amd graphics

ubuntu OS/Kernel logging - system freeze/hung https://askubuntu.com/questions/1567677/ubuntu-os-kernel-logging-system-freeze-hung

We are encountering an issue where a server becomes completely unresponsive, with no clear indication of what caused the hang. example:

/var/log/syslog:

Jun 12 15:45:02 k-w16 weka-agent[12000]: DEBUG:  requested_actions.d:189  <17422> [REQ_ACTION] Monitoring requested action needed info for container client: has_lease=true, action=NONE, state=ACTIVE, has_requested_action_failure=false, is_inactive=false
Jun 12 20:38:14 k-w16 kernel: Linux version 5.15.0-1063-nvidia (buildd@lcy02-amd64-007) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #64-Ubuntu SMP Fri Aug 9 17:13:45 UTC 2024 (Ubuntu 5.15.0-1063.64-nvidia 5.15.160)
Jun 12 20:38:14 k-w16 kernel: Command line: BOOT_IMAGE=images/d-os-6.3-h10-image/vmlinuz initrd=images/d-os-6.3-h10-image/initrd  cgroup_enable=memory swapaccount=1 nouveau.blacklist=yes nouveau.modeset=0 iommu=pt namespace.unpriv_enable=1 user_namespace.enable=1 systemd.unified_cgroup_hierarchy=1 systemd.legacy_systemd_cgroup_controller intel_cpufreq.enable=1 intel_pstate=active crashkernel=8G console=tty0 ip=10.67.32.164:10.67.32.100:10.67.33.254:255.255.254.0 BOOTIF=01-58-a2-e1-76-03-98
Jun 12 20:38:14 k-w16 kernel: KERNEL supported cpus:

/var/log/kern.log

Jun 12 15:41:54 k-w16 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): cali9d766d49d92: link becomes ready
Jun 12 15:42:07 k-w16 kernel: wekafsio: [__wmp_add_recovery_inode:134]R[5:0xf8e07cea16470144] VC(i=677,d=c0:8,a=d) o=1/1w N[1249120_35832653_10112184.wav] sz=0x8802c m=100644 st[] |wekafs_file_open:366] recovery_inodes_count=4 le(0)
Jun 12 20:38:14 k-w16 kernel: Linux version 5.15.0-1063-nvidia (buildd@lcy02-amd64-007) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #64-Ubuntu SMP Fri Aug 9 17:13:45 UTC 2024 (Ubuntu 5.15.0-1063.64-nvidia 5.15.160)
Jun 12 20:38:14 k-w16 kernel: Command line: BOOT_IMAGE=images/d-os-6.3-h10-image/vmlinuz initrd=images/d-os-6.3-h10-image/initrd  cgroup_enable=memory swapaccount=1 nouveau.blacklist=yes nouveau.modeset=0 iommu=pt namespace.unpriv_enable=1 user_namespace.enable=1 systemd.unified_cgroup_hierarchy=1 systemd.legacy_systemd_cgroup_controller intel_cpufreq.enable=1 intel_pstate=active crashkernel=8G console=tty0 ip=10.167.32.164:10.167.32.100:10.167.33.254:255.255.254.0 BOOTIF=03-88-a2-e1-76-03-98

As shown above, there are no log entries between 15:45:02 and the subsequent boot at 20:38:14. During this period, the node was completely unresponsive and we were unable to SSH into the server, and there was no useful information visible on the console.

After the reboot, we were also unable to find any relevant messages in the system logs that would help identify the cause of the hang.

we do have following setting:

root@k-w16:~# cat /proc/sys/kernel/hung_task_panic
1
root@k-w16:~# cat /proc/sys/kernel/sysrq
0

kernel.hung_task_timeout_secs = 120

Given that kernel.hung_task_panic=1, we expected to see a hung-task stack trace or kernel panic information if tasks were blocked for longer than the configured timeout. However, no such information was captured in the logs.

i am primarily looking to understand if there additional boot/kernel settings ( sysctl) or debugging mechanisms (SysRq, NMI watchdog etc) that should be enabled to capture diagnostic information during such hangs? - just like exception handler printing stack trace before crashing out.

also, under what circumstances a system can become completely unresponsive without generating hung-task traces or panic logs?

this issue occured with 3 out of 8 servers today within a span of 1 hour.

Bricked laptop won't start https://askubuntu.com/questions/1567675/bricked-laptop-wont-start

Without any warning sign when I last cleanly shut down my laptop running Ubuntu 26.04, it simply won't start again: the screen stays off, all lights are on (power button, ESC key, Shift Lock and Num Lock) and it stays non responsive

Hitting ESC repeatedly does nothing, and I can't book on a USB stick (Fn+F12 is unresponsive). Other known keys (Fn+F2, Fn+F8) do nothing.

Anything else to try?

Lenovo IdeaPad Slim 3 15ABR8

Trouble pairing iPhone (iOS 26.5) to Ubuntu 26.04 over USB https://askubuntu.com/questions/1567674/trouble-pairing-iphone-ios-26-5-to-ubuntu-26-04-over-usb

I have a Framework 13 laptop (AMD cpu) with Ubuntu 26.04 freshly installed and updated. I plug in my iPhone 16 Pro (iOS 26.5) via USB-C cable, and Ubuntu shows an "Untrusted Device" dialog, and the phone shows a "Trust This Computer?" dialog.

Before I can click "Trust" on the iPhone, the dialog is dismissed. After 3-4 seconds, Ubuntu overlays another "Untrusted Device" dialog, and the iPhone again flashes the "Trust This Computer?" dialog.

It keeps repeating this endlessly, and never gives me enough time to click "Trust" on the iPhone and type in the pairing code.

The USB-C cable is a known working cable from Apple, which works fine to pair/tether the phone to a MacBook. I believe I've also paired this phone and laptop on a previous install of ubuntu, but I hadn't used this laptop in a year, and did a fresh 26.04 install recently, and I'm traveling, and surprised that I can't seem to pair the two to share my phone's internet.

The workaround is to use a wireless tethering method (bluetooth or wifi), but I can't plug my phone in to charge off the laptop without it making both the phone and laptop pop up a dialog every 3-4 seconds.

I spent a couple hours this morning with Claude to see if it could help me track down the issue, and I asked it to summarize what we tried, and here's the relevant bits from that summary:

Root-cause isolation. Verbose usbmuxd logging showed a consistent per-cycle pattern: the device enumerates cleanly, usbmuxd connects, the configuration is switched (0 → 4), preflight begins, reaches "Waiting for user to trust this computer," and then ~0.6–0.8 seconds later the device drops (Device RX aborted due to error or disconnect / Removed device) and re-enumerates. The disconnect timing is fixed and regular, and occurs with nothing on the host actively tearing down the connection — usbmuxd is idle in the trust-wait state when the drop happens. This points to the USB connection being torn down below userspace, at the USB host-controller/xHCI or device level, rather than a pairing-software failure.

What we ruled out (no effect on the drop). Different USB-C ports; the Apple cable (works on macOS); stale host trust state (cleared /var/lib/lockdown, and did Reset Location & Privacy on the phone); the udev rule 39-usbmuxd.rules (masked it entirely — no change); GNOME gvfs/gvfsd-afc contention (masked the volume monitors — the gvfs storm stopped but the ~0.8s drop persisted unchanged); daemon lifecycle (ran a single persistent usbmuxd --foreground so no socket/udev respawn could interfere); and the ipheth kernel module (unloaded it with modprobe -r ipheth — the device still dropped at the same ~0.8s mark with the driver entirely absent).

When starting Ubuntu with dock plugged in, external monitors don’t work https://askubuntu.com/questions/1567673/when-starting-ubuntu-with-dock-plugged-in-external-monitors-don-t-work

When I restart my laptop if I leave the dock plugged in, then the external monitors aren’t recognized. I can unplug and replug in the dock to the laptop, and I can lock/logout then re-login, but nothing fixes the problem.

When I restart, but unplug the dock so that Ubuntu starts without the dock plugged in, I can plug in the dock at the login screen or after I'm logged in and my external monitors are recognized and work just fine.

I'm using Ubuntu 24.04.4 LTS. The laptop is a Dell pro 16 PC16250 (though this happened with my last Dell laptop also, when I was using the same Ubuntu version). The dock is a Dell Pro thunderbolt 4 SD25TB4. I'm using the display port connections from dock to monitors.

It's a minor annoyance. Is there a configuration file that I need to change, or is there a library that I need to update?

Unattended Upgrade Emails with msmtp https://askubuntu.com/questions/1567670/unattended-upgrade-emails-with-msmtp

I do not want to install a complete mail stack on my server as we have a mailserver in our network that can deliver emails already. I have a very simple and functioning msmtp setup but it seems that unattended upgrades wants specific packages that procure a program called mailx, mail and sendmail.

I have already tried to just symlink sendmail and mail to msmtp as I remember these programs to have the same command line arguments but running a dry-run with the reporting set to "always" doesn't deliver any mail.

Is there some simple way to set something up that doesn't require me to install the entire emailing stack that comes with bsd-mailx (which includes postfix) and similar packages?

Need help installing Wine https://askubuntu.com/questions/1567669/need-help-installing-wine

I can't install wine. I put in sudo dpkg --add-architecture i386 and it says error: unknown command: sudo. How do I fix this? I have checked the spelling and even tried using l386 instead as another post suggested, but nothing worked.

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/*

I tried the 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/ ...

I hope you have some good ideas.

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

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.

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?

Cannot retore files in a Deja Dup Archive 26.04 generated from same on 26.04 https://askubuntu.com/questions/1567582/cannot-retore-files-in-a-deja-dup-archive-26-04-generated-from-same-on-26-04

Cannot restore files in a Deja-dup v50 Archive 26.04 generated from same on 26.04.

My understanding is that you now cannot restore files directly from nautilus. However, when I attempt to restore a file, I select my archive (from Deja-dup archive selection) and it goes into nautilus. Is this right? It is a file selector of some sort, anyway, but there is no mechanism to initiate a restore. Right and left click does not reveal anything and I cannot see any more buttons

I use a 24.04 and 26.04 with a common /home. So when it was installed on 26.04 it would have inherited the 24.04 customization files if there are any. I know there is something in `~/.cache` but I couldn't identify anything relevant to this.

I have also looked in dconf editor and I couldn't find anything relevant in there.

I now assume that Deja Dup v50 is not compatible with Deja Dup (current version in 24.04) as when I logged into 24.04 it could not identify any archives at all. I did check it was pointing to the same place as in 26.04.

Questions. Can you fix the restore?

Should I keep 24.04 and 26.04 completely separate? Note: I suspect the two versions are sharing the setup data that dconf editor is pointing to which will make this a little tricky.

System Details Report
  Report details
    Date generated:                              2026-06-08 18:51:15
      Hardware Information:

      Hardware Model:                              Advent DT4102
      Memory:                                      8.0 GiB
      Processor:                                   Intel® Pentium® G2030 × 2
      Graphics:                                    Intel® HD Graphics 2500 (IVB GT1)
      Disk Capacity:                               2.0 TB
      Software Information:

      Firmware Version:                            4.6.5
      OS Name:                                     Ubuntu 26.04 LTS
      OS Build:                                    (null)
      OS Type:                                     64-bit
      GNOME Version:                               50
      Windowing System:                            Wayland
      Kernel Version:                              Linux 7.0.0-22-generic

Thanks for any help given.


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 !

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 in x11 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.

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

Unable to update "Secure Boot dbx Configuration Update" https://askubuntu.com/questions/1437350/unable-to-update-secure-boot-dbx-configuration-update

New Ubuntu 22.10 install. GUI update shows "Secure Boot dbx Configuration Update 77-217". When update is attempted (from GUI) error is displayed "Unable to update "Secure Boot dbx Configuration Update": failed to write data to efivarfs: Error writing to file descriptor: Invalid argument"

When update attempted with "fwupdmgr update" then error is: "failed to write data to efivarfs: Error writing to file descriptor: Invalid argument"

Help please.

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?
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.

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.

Insmod error in grub: symbol not found:grub_realidt https://askubuntu.com/questions/284898/insmod-error-in-grub-symbol-not-foundgrub-realidt

I have a dual boot PC with Windows 7 and Ubuntu. I upgraded from 12.04 to 12.10 and then to 13.04 and since then I have not been able to boot because the PC goes into grub rescue with the error "File not found".

I have tried the following steps:

set prefix=(hd0,msdos5)/usr/lib/grub/i386-pc
set root=(hd0,msdos5)
insmod linux

I get error:

symbol not found : 'grub_realidt'.

if I do insmod normal, I get error

symbol not found : 'grub_disk_dev_list'

I have two partitions containing linux file system: (hd0,msdos5) and (hd0,msdos6). They were mountpoints for / and /boot respectively.

I have searched for this error, and found some "solved" threads. But all of them are using Live USB to get in grub prompt. I don't have access to one, and was hoping to be able to solve the issue without a flash drive.

Please help... Thanks in advance.