*** 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 14.
*** 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 p
*** 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 b
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
initrd=/casper/ini
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
** Changed in: ubiquity (Ubuntu Vivid)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1408495
Title:
Ubiquity crashes prior to keyb
On 2015-01-14 04:47 PM, jerrylamos wrote:
> Permissions on /etc/default/keyboard were:
> c
>
> while on the default were
> -rw-r--r--r
>
> So workaround copying resulted in
> -rw-r--r--
> so install completed.
Confirmation of successful install of Vivid using Martin's keyboard
worka
Permissions on /etc/default/keyboard were:
c
while on the default were
-rw-r--r--r
So workaround copying resulted in
-rw-r--r--
so install completed.
BTW, this is US so this is what keyboard looked like:
ubuntu@ubuntu:~$ cat /etc/default/keyboard
# Check /usr/share/doc/keyboard-con
I added a workaround to the description to prevent the complete failure
at the end.
** Description changed:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displ
Confirmed that the broken /etc/default/keyboard does NOT happen when
starting the live system, but happens when ubiquity is about to
configure keyboard.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/14
Indeed this looks strange on the live CD:
c 1 root root 0, 0 Jan 14 18:21 keyboard
c 1 root root 0, 0 Jan 14 18:21 keyboard.pre-ubiquity
An inaccessible character device is certainly not intended here?
--
You received this bug notification because you are a member of Ubu
confirm the comment in post #4 with xubuntu
If I 'try again' install appears to then proceed correctly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1408495
Title:
Ubiquity crashes prior to keyboar
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1408495
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Also happens on Ubuntu Kylin daily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
To manage notifications about this bug go
There's also this:
Jan 7 23:36:01 ubuntu ubiquity: setupcon: None of /etc/default/keyboard
nor /root/.console-setup exists.
** Also affects: ubiquity (Ubuntu Vivid)
Importance: High
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Reproduced with Xubuntu daily. It only seems to happen if you choose
"install now" rather than "try xubuntu".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1408495
Title:
Ubiquity crashes prior to k
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1408495
Title:
U
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1408495
Title:
Ubiquity crashes prior to keyboard configuration in 15.04
To manage no
Exception during installation:
Jan 7 23:36:01 ubuntu /plugininstall.py: Traceback (most recent call last):
Jan 7 23:36:01 ubuntu /plugininstall.py: File
"/usr/share/ubiquity/plugininstall.py", line 1765, in
Jan 7 23:36:01 ubuntu /plugininstall.py: install.run()
Jan 7 23:36:01 ubuntu /pl
** Description changed:
As best as I can tell, if anything other than a US keyboard layout is
selected from the boot menu, ubi-console-setup will crash prior to the
keyboard configuration. The dialogue displayed says:
- ubi-console-setup failed with exit code 2. Firther information ma
20 matches
Mail list logo
