[Kernel-packages] [Bug 1408495] Re: Ubiquity crashes prior to keyboard configuration in 15.04

2015-01-17 Thread jerrylamos
*** This bug is a duplicate of bug 1410480 *** https://bugs.launchpad.net/bugs/1410480 Problem is the file permissions for /etc/default/keyboard on the vivid .iso are ls -l /etc/default/keyboard c- Won't work. No way ubiquity can use the file. On previous vivid, tahr, etc. file

[Kernel-packages] [Bug 1408495] Re: Ubiquity crashes prior to keyboard configuration in 15.04

2015-01-17 Thread jerrylamos
*** This bug is a duplicate of bug 1410480 *** https://bugs.launchpad.net/bugs/1410480 bug #1410480, overlayfs v1: renaming existing file uses chardev whiteout (should be symlink) seems to have nothing at all to do with ubiquity install failures which is this bug here. I've verified tahr

[Kernel-packages] [Bug 1408495] Re: Ubiquity crashes prior to keyboard configuration in 15.04

2015-01-16 Thread Mathieu Trudel-Lapierre
It looks like any moving of a file which comes from the read-only underlying filesystem. It doesn't behave the same when one deletes a file instead of moving. It seems like it's probably a bug in overlayfs, so I'm adding a task for linux so the kernel team can take a look. ** Also affects: linux

[Kernel-packages] [Bug 1408495] Re: Ubiquity crashes prior to keyboard configuration in 15.04

2015-01-16 Thread Mathieu Trudel-Lapierre
ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2119 F pulseaudio CasperVersion: 1.347 DistroRelease: Ubuntu 15.04 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity

[Kernel-packages] [Bug 1408495] Re: Ubiquity crashes prior to keyboard configuration in 15.04

2015-01-16 Thread Mathieu Trudel-Lapierre
*** This bug is a duplicate of bug 1410480 *** https://bugs.launchpad.net/bugs/1410480 This seems like a duplicate of bug 1410480. ** This bug has been marked a duplicate of bug 1410480 overlayfs v1: renaming existing file uses chardev whiteout (should be symlink) -- You received this