← Back to team overview

debcrafters-packages team mailing list archive

[Bug 2122474] Re: Directory /run contains unexpected files and directories in the live image, causing potential issues

 

** Description changed:

  Description of the Bug's Symptoms
  
  When booting into the Ubuntu 25.04 live image, it has been observed that
  the /run directory is not empty. The directory is intended for temporary
  files and should be empty at boot time.
  
  This suggests an error in the live image creation process, where files
  are left behind in the directory.
- 
- This can also lead to different symptoms depending on the system's
- configuration, such as systemd's run-lock.mount warning: Directory
- /run/lock to mount over is not empty, mounting anyway. The occurrence of
- this warning is not consistent across all environments, but it is a
- direct consequence of the /run/lock subdirectory not being empty.
  
  How to Repeat the Problem
  
  Boot the computer using the Ubuntu live image.
  
  Open a terminal in the live environment.
  
  The live system's /run directory is already mounted in RAM. To access
  the original contents of the / root directory, you need to create a new
  mount point and use the mount --bind command. Run the following
  commands:
  
  sudo mkdir /mnt/root
  sudo mount --bind / /mnt/root
  sudo ls -la /mnt/root/run
  
  Expected Outcome: The ls -la /mnt/root/run command should show an empty
  directory (only . and .. files).
  
  Actual Outcome: The directory contains one or more files or
  subdirectories that were left behind in the live image.
  
  Environment Details
  
  Ubuntu version: 25.04, 25.10
- Environment: Live image 
+ Environment: Live image
  Tested Versions: 25.04 Desktop, 25.10 Desktop, 25.10 Server

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/2122474

Title:
  Directory /run contains unexpected files and directories in the live
  image, causing potential issues

Status in Ubuntu:
  New
Status in base-files package in Ubuntu:
  New

Bug description:
  Description of the Bug's Symptoms

  When booting into the Ubuntu 25.04 live image, it has been observed
  that the /run directory is not empty. The directory is intended for
  temporary files and should be empty at boot time.

  This suggests an error in the live image creation process, where files
  are left behind in the directory.

  How to Repeat the Problem

  Boot the computer using the Ubuntu live image.

  Open a terminal in the live environment.

  The live system's /run directory is already mounted in RAM. To access
  the original contents of the / root directory, you need to create a
  new mount point and use the mount --bind command. Run the following
  commands:

  sudo mkdir /mnt/root
  sudo mount --bind / /mnt/root
  sudo ls -la /mnt/root/run

  Expected Outcome: The ls -la /mnt/root/run command should show an
  empty directory (only . and .. files).

  Actual Outcome: The directory contains one or more files or
  subdirectories that were left behind in the live image.

  Environment Details

  Ubuntu version: 25.04, 25.10
  Environment: Live image
  Tested Versions: 25.04 Desktop, 25.10 Desktop, 25.10 Server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2122474/+subscriptions