If the installer fails or is aborted, users can end up in Live CD Desktop, which is confusing

Bug #217593 reported by Agostino Russo
62
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Wubi
Invalid
Medium
Agostino Russo
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

If the installer fails users can end up in Live CD Desktop, which is confusing. Strangely enough they also seem to end up there after a reboot, I would have expected that rebooting after an unfinished installer session would start the installer again which should fail because an existing installation is detected... Possibly the last event does not trigger a failure-command.

Revision history for this message
Agostino Russo (ago) wrote :

Two of the duplicates had issues with hal initialization

Changed in wubi:
assignee: nobody → ago
importance: Undecided → Medium
status: New → Confirmed
Agostino Russo (ago)
description: updated
Revision history for this message
cpascual (isnot4u) wrote :

Hi Agostino,

In the thread of Bug #217588 (now a duplicate of this one) you asked me to send
c:\document and settings\[your-username]\Wubi-8.04-beta-rev487.log
which I couldn't find.
However,I have just found it, elsewhere:
C:\Documents and Settings\[myusername]\Local Settings\Temp\Wubi-8.04-beta-rev487.log
(attached)

From that same thread:
> So in the previous case you aborted the installation, correct?

Correct

> And landed in a Live Session, correct?

Correct

>What happens when you rebooted and selected "Ubuntu" after the Live Session?
> Would the installer run again, or would you boot the Live CD Session.

Not sure.
I got the timezone setting screen again (does that mean it was the installer?), and after it, I got a desktop without having to log-in for the "ubuntu" user (which looks to me as live-CD session)

> /var/log/syslog is always welcome in such cases...

Yes, but the var/sys/log related to that failed installation is no longer present. The current one contains only the info from the successful installation.

Revision history for this message
JC (jcsaintpo) wrote :

hi agostino

>The logs look good. Also I can see that with 482 you
installed/uninstalled a few times and did not have to redownload.

i did not ask to redownload, it just did on his own!
I wanted to reinstall everytime because i kept having problems with HAL and always ended up in a live-session!

>Only happened with 487. Can you pls try uninstalling and then
installing+uninstalling using 487 and then check if you have a folder
called c:\ubuntu-bacup with the ISO in there?

I have a backup-folder, but wubi does not use it and downloads new iso!
i searched my computer, no logs found from 487! eventhough i istalled and uninstalled!

Revision history for this message
Agostino Russo (ago) wrote :

Having the following in preseed.cfg should avoid that (thanks to Evan Dandrea for the tip)

ubiquity ubiquity/automation_failure_command [ -x /custom-installation/hooks/failure-command.sh ] && /custom-installation/hooks/failure-command.sh

Agostino Russo (ago)
Changed in wubi:
status: Confirmed → Fix Committed
Revision history for this message
Agostino Russo (ago) wrote :

Fix commented out on Evan Dandrea suggestion

Changed in wubi:
status: Fix Committed → In Progress
Revision history for this message
StraightShootinComputin (straightshootincomputin) wrote :

had the same problem

was able to add a user via Users and Groups and then log out and log into it, but it still suffered from LiveCD syndrome, and allowed sudo/gksudo without a password.

trying a second install

Revision history for this message
StraightShootinComputin (straightshootincomputin) wrote :

Second wubi install is progressing correctly. the only thing I can think of that I did differently is that I picked a longer password. In the first instance, I used a single digit for the password. In the second, I used an 8 digit long password.

Could this have anything to do with the problem?

Revision history for this message
Agostino Russo (ago) wrote :

I wouldn't think so. If that happens it would help to see the logs (particularly when booting in verbose mode). To generate the log press ctrl+alt+f2 and run: sudo sh /custom-installation/hooks/failure-command/sh

Revision history for this message
StraightShootinComputin (straightshootincomputin) wrote :

sorry, a little late for that. already using the 2nd (successful) install.

Evan (ev)
Changed in ubiquity:
assignee: nobody → evand
status: New → Confirmed
Changed in wubi:
status: In Progress → Invalid
Evan (ev)
Changed in ubiquity (Ubuntu):
assignee: Evan Dandrea (ev) → nobody
Revision history for this message
Siegfried Wörner (sigi-woerner) wrote :

The Installer is crashed (CD from the magazine ct)

for error analysis, I will send two files.

Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.