[Lucid]Ubiquity appears to crash in Kubuntu Live CD environment but then runs successfully after error dialogs closed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity |
Invalid
|
Undecided
|
Unassigned | ||
ubiquity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Installing Kubuntu 32bit from the desktop. Ubiquity crashes
because it
can not write data to the live filesystem.
What does not work:
Boot the live Kubuntu system
Once live system boots, attempt to run Ubiquity by clicking on
the
Install desktop link.
This fails because the live environment is mounted read-only (or
ubiquity is not running with the correct permissions)
Once ubiquity tries to run, it appears to crash with the
following error
in a KDialog popup:
not
writable. Please contact your system administrator.
which is followed by another popup that says:
writable.
Please contact your system administrator.
By the way, writable should be writeable... but that's a minor
point.
After clicking OK on that second KDialog popup, I get yet
another popup
that says:
We are sorry, KDialog closed unexpectedly. The detail section
says:
Executable kdialog PID: 2669 Signal: 6 (Aborted)
After closing that box, Ubiquity actually DOES start and seems
to
function as planned.
The two error popups make it seem as though Ubiquity has
crashed, and
the KDialog crash afterwards is pretty frightening.
Now, If I choose "Install Kubuntu" from the boot menu instead of
"Try
the Live Version", I do not see any issues at all. These errors
only
appear when running Ubiquity from inside the live system.
System is a VirtualBox VM with 1 processor, 1GB ram and 8GB hard
disk
configured.
I'm using the daily build as of 12 March, with Ubiquity 2.1.35
affects ubiquity
Moving to the ubiquity package in Ubuntu; we don't use the upstream project for bug reporting.
The use of "writable" is intentional; the OED lists it (and not "writeable", at least not at www.askoxford.com although I haven't checked against my paper copy).
I think this is probably bug 538142, but I'll check with Jonathan.