ubiquity: Starting up '['/usr/share/ubiquity/clock-setup']' for
ubiquity.components.clock_setup.ClockSetup
/usr/bin/os-prober: line 27: /bin/mapdevfs: cannot execute binary file
/usr/bin/os-prober: line 27: /bin/mapdevfs: cannot execute binary file
/usr/bin/os-prober: line 27: /bin/mapdevfs: cannot execute binary file
/usr/bin/os-prober: line 27: /bin/mapdevfs: cannot execute binary file
/usr/bin/os-prober: line 27: /bin/mapdevfs: cannot execute binary file
/usr/bin/os-prober: line 62: /bin/mapdevfs: cannot execute binary file
ubiquity: ['/usr/share/ubiquity/clock-setup'] exited with code 126
Freaky; /bin/mapdevfs is just broken, and there's no good reason why
that would happen under normal operation. Looks like a badly burned CD
or a dirty CD drive to me. Denis, have you tried (a) a CD integrity
check and (b) cleaning your CD drive?
** Changed in: ubiquity (Ubuntu)
Assignee: Ubuntu Installer Team => (unassigned)
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Needs Info
--
Installer crashed
https://launchpad.net/bugs/55489
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
