Build Fail - gvfs problem in chroot environment

Bug #657689 reported by Carlos Eduardo Alves
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Customization Kit
Fix Released
Undecided
Unassigned

Bug Description

During the installation of some applications, a gvfs file system is mounted on "/root/.gvfs". Thus, the directory "/root" can't be umounted in the "unmount_pseudofilesystems" routine.

I solve this problem by adding an "if" clause in the "/usr/lib/uck/remaster-live-cd.sh" script in the "unmount_pseudofilesystems".
It is like this:
--
function unmount_pseudofilesystems()
{
  if [ -n "$REMASTER_DIR" ]; then
    if [ -d "$REMASTER_DIR/root/.gvfs" ]; then
      echo "Cleaning up /root/.gvfs..."
      # Need to be umounted as chroot, because it is mounted in chroot environment
      chroot "$REMASTER_DIR" sh -c "umount /root/.gvfs 2>&1"
      chroot "$REMASTER_DIR" sh -c "umount /root/.gvfs 2>&1"
      chroot "$REMASTER_DIR" sh -c "rm -rfv /root/.gvfs 2>&1"
      echo "Umounting other mount points..."
    fi
    unmount_directory "$REMASTER_DIR/lib/modules/*/volatile"
    unmount_directory "$REMASTER_DIR/tmp/customization-scripts"
    unmount_directory "$REMASTER_DIR/var/cache/apt"
    unmount_directory "$REMASTER_DIR/root"
    unmount_directory "$REMASTER_DIR/tmp"
    unmount_directory "$REMASTER_DIR/var/run"
    unmount_directory "$REMASTER_DIR/dev/pts"
    unmount_directory "$REMASTER_DIR/sys"
    unmount_directory "$REMASTER_DIR/proc"
  fi
}
--
I don't know if it is the best solution, but solve my issue and finalize the customization.
Please think about it. This can be solved in the "Run console application" option during customization and doing the "umount /root/.gvfs; rm -rfv /root/.gvfs" commands manually, but these facilities can be appreciated by end-users :P

Bye! Good job guys.

Revision history for this message
Fabrizio Balliano (fabrizio-balliano) wrote :

please provice uck version and build.log

Changed in uck:
status: New → Incomplete
Revision history for this message
jyanix (jyanix) wrote :
Download full text (15.1 KiB)

Maverick 10.10 -- I have been unable to use the "Run console application" option during build due to user permission errors during boot. I isolated this issue to using the "Run console application" function. Using Carlos' commands of "umount /root/.gvfs; rm -rfv /root/.gvfs" manually inside of the console, the boot error disappeared. I did not have any build issues before or after using the commands. UCK 2.2.1 and UCK 2.3.3 have the same issues with this.

I have attached my casper.log file from a failed boot.

My (successful) build.log is below:

Build (/usr/bin/uck-gui --wait-before-exit) started at 2010-10-28 10:46:55
Ubuntu Customization Kit 2.3.3
Starting CD remastering on Thu Oct 28 10:46:59 CEST 2010
Customization dir=/home/ubuntu/tmp/customization-scripts
Mounting ISO image...
Unpacking ISO image...
Unmounting ISO image...
Mounting SquashFS image...
Unpacking SquashFS image...
Unmounting SquashFS image...
Removing win32 files...
Creating root home...
Mounting /proc
Mounting /sys
Mounting /dev/pts
Mounting /var/run
Mounting /tmp
Mounting /home/ubuntu/tmp/remaster-root-home
Mounting /home/ubuntu/tmp/remaster-apt-cache
Mounting /home/ubuntu/tmp/customization-scripts
Copying resolv.conf...
Creating DBUS uuid...
Deactivating initctl...
Hit http://archive.canonical.com maverick Release.gpg
Ign http://archive.canonical.com/ubuntu/ maverick/partner Translation-en
Hit http://archive.ubuntu.com maverick Release.gpg
Ign http://archive.ubuntu.com/ubuntu/ maverick/main Translation-en
Ign http://archive.ubuntu.com/ubuntu/ maverick/multiverse Translation-en
Hit http://security.ubuntu.com maverick-security Release.gpg
Ign http://security.ubuntu.com/ubuntu/ maverick-security/main Translation-en
Ign http://archive.ubuntu.com/ubuntu/ maverick/restricted Translation-en
Ign http://archive.ubuntu.com/ubuntu/ maverick/universe Translation-en
Hit http://archive.ubuntu.com maverick-updates Release.gpg
Ign http://archive.ubuntu.com/ubuntu/ maverick-updates/main Translation-en
Ign http://archive.ubuntu.com/ubuntu/ maverick-updates/multiverse Translation-en
Ign http://archive.ubuntu.com/ubuntu/ maverick-updates/restricted Translation-en
Ign http://archive.ubuntu.com/ubuntu/ maverick-updates/universe Translation-en
Hit http://archive.canonical.com maverick Release
Hit http://archive.ubuntu.com maverick Release
Hit http://archive.ubuntu.com maverick-updates Release
Hit http://archive.canonical.com maverick/partner Sources
Hit http://archive.ubuntu.com maverick/main i386 Packages
Hit http://archive.ubuntu.com maverick/restricted i386 Packages
Hit http://archive.ubuntu.com maverick/universe i386 Packages
Hit http://archive.ubuntu.com maverick/multiverse i386 Packages
Hit http://archive.canonical.com maverick/partner i386 Packages
Hit http://archive.ubuntu.com maverick-updates/main i386 Packages
Hit http://archive.ubuntu.com maverick-updates/restricted i386 Packages
Hit http://archive.ubuntu.com maverick-updates/universe i386 Packages
Hit http://archive.ubuntu.com maverick-updates/multiverse i386 Packages
Ign http://security.ubuntu.com/ubuntu/ maverick-security/multiverse Translation-en
Ign http://security.ubuntu.com/ubuntu/ maverick-security/restricted Translat...

Revision history for this message
Fabrizio Balliano (fabrizio-balliano) wrote :

@jyanix: what you're writing seems not related to this bug, please post another one.

Revision history for this message
Fabrizio Balliano (fabrizio-balliano) wrote :

@carlos: should be done in SVN, could you give it a try?

Changed in uck:
status: Incomplete → Fix Committed
Revision history for this message
Fabrizio Balliano (fabrizio-balliano) wrote :

fix released with 2.4.0

Changed in uck:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.