add installer status message for "Wiping Swap Space"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Invalid
|
Wishlist
|
Evan | ||
Lucid |
Invalid
|
Wishlist
|
Evan | ||
Maverick |
Invalid
|
Wishlist
|
Evan | ||
user-setup (Ubuntu) |
Fix Released
|
Wishlist
|
Dustin Kirkland | ||
Lucid |
Fix Released
|
Wishlist
|
Evan | ||
Maverick |
Fix Released
|
Wishlist
|
Dustin Kirkland |
Bug Description
Please allow a UI freeze exception for the following change. This provides a new progress message for the already-existing behavior of user-setup dding over any swap devices because the encrypt-home option was selected.
http://
Original report follows:
Binary package hint: ubiquity
steps to reproduce:
- run karmic alpha 6 desktop live session
- install Ubuntu with encrypted $HOME (and manual partitioning)
- the installer progress bar stops at 83% for a very long time
- installation finished successfully
at 83% gnome-system-
(I think wiping partition or something)
the Problem is: There is NO FEEDBACK at all during that command.
(Is the machine alive or dead?)
ProblemType: Bug
Architecture: amd64
Date: Fri Sep 18 13:14:27 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: ubiquity (not installed)
ProcEnviron:
LANG=de_AT.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: ubiquity
Uname: Linux 2.6.31-10-generic x86_64
Changed in ubiquity (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | added: iso-testing |
Changed in ubiquity (Ubuntu Lucid): | |
milestone: | none → ubuntu-10.04-beta-1 |
Changed in user-setup (Ubuntu Lucid): | |
milestone: | none → ubuntu-10.04-beta-1 |
Changed in user-setup (Ubuntu Lucid): | |
status: | Triaged → Fix Committed |
Changed in ubiquity (Ubuntu Lucid): | |
status: | Triaged → Invalid |
Changed in user-setup (Ubuntu Maverick): | |
status: | Fix Released → In Progress |
milestone: | ubuntu-10.04-beta-1 → none |
assignee: | Evan Dandrea (ev) → Dustin Kirkland (kirkland) |
Is /dev/sda1 your swap partition? Can you please attach /var/log/ installer/ syslog and /var/log/ installer/ partman to this bug report?
Thanks!