After install completed bar wasn't all green and installer hung

This has happened a second time when I was installing it. The dialog says "Installation Complete" the bar extends approximately between the "back" and "close" buttons and the CD drive has ejected. After clicking the close button the "Ubuntu Setup" application is indicating it is not responding.

I can confirm that, but it does not seem to have any implication for the installation. In my case the last steps (after ISO is downloaded/extracted/checked) are quite quick and before the bar reaches the end you are shown the reboot window.

The progress status is calculated directly by nsis, so changing that might not be that easy.

As mentioned the progress is calculated directly by nsis and changing that would be too invasive.

Testing today with daily build 20080411 the installer got hung up at the same point. I'll attach a screenshot and the log. Could this happen if Wubi did not have internet access? After killing the hung Wubi process I noticed a message about authorizing Wubi's internet access.

Brian, the (last) log indicates that the installation completed successfully. I noticed that in the previous logs you might have experience a segfault (with Wubi not showing at all). I am wondering whether the missing reboot page is linked to the same issue.

Can you please try with http://wubi-installer.org/devel/minefield/Wubi-8.04-beta-rev487sh.exe

I tested with Kubuntu AMD64 daily build from 20080417.1 which has rev 487 and ran into the bug again.

Brian reported that new builds work well

Yes, rev 488 exited well for me.

In rev 495 the green bar wasn't all the way full and it entered a Not Responding state again.

I take it back. My last comment should be expunged from the record.

For some reason if I run rev 495 off a USB stick on the Windows system it works fine and gives me the reboot dialog. However, if I run rev 495 off the 20080423 daily build of Kubuntu KDE4 it doesn't and I get this bug.

Brian, can you post the 495 log? Are the eject CD lines at the bottom reasonable? is it the right drive? Does the disk actually eject? Does it work with an emulated CD (Daemon Tools and such) or another CD drive?

I've been thinking about the testing I did yesterday and here is some more information:

With 495 from the CD the disk does eject but the app enters the Not Responding state. Additionally, the only way I have been able to successfully exit Wubi was by reinserting the CD and running Windows task manager. If the CD is ejected I can not force Wubi to exit. Additionally, task manager gives an error message regarding "disk" and isn't usable. I could grab the exact error message if necessary.

With 495 from a USB stick the CD ejects and then I'm shown the Wubi screen about rebooting.

That's probably because the wubi executable is on the CD which you are ejecting and the system needs to access it. And since I'd assume you run 488 off the CD that would explain why it worked then. Also in my testing I used emulated CDs...

There are 2 possible workarounds:

1) Run wubi from the Vista system and not the CD

2) A bit messy
a) After the CD is ejected, reinsert the CD.
b) click "Close" in the Installation Complete dialog of Wubi that shows "Not Responding" in the title bar
c) you'll be presented with a "Microsoft Windows" dialog saying "Windows based UBuntu Installer is not responding"
d) click "Close the program"
e) the Wubi program will end and you can reboot and then choose Ubuntu in the Windows boot loader to complete the installation

At step "d" I've also chosen wait for the program to respond and nothing happens.

Simply using upx-ucl to repackage the executable should address the issue. I will also postpone the CD ejection just before the reboot command.

To test:

1) unpack the ISO (mount -o loop /path/to/iso /path/to/unpacked/iso && cp -a)
2) replace wubi.exe with the file attached
3) repack the ISO

mkisofs -r -V 'Ubuntu 8.04 i386' -o hardy-i386-hacked.iso -cache-inodes -J -l -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table /path/to/unpacked/iso

4) burn CD and run wubi.exe from the CD with the argument "--skipmd5check"

Note that Vista has to be fully updated and Wubi must be run from within the CD.

Every which way I try to burn this the wubi.exe fails I'll report the fail text tomorrow.

davmor2, I can confirm that upx and wubi.exe do not go hand in hand. I will have to provide a new binary.

davmor2 can you pls try with the above build when you have a couple of minutes?

Other go

The wubi-selfextract.exe didn't work. It restarted the machine correctly however the wubi-mbr didn't work correctly I couldn't select Ubuntu from the mbr screen.

davmor2, if the machine gets to reboot then wubi-selfextract has worked. The mbr is a different issue.

I tested the wubi-selfextract.exe, revision 504 I believe, by downloading it and running it from my desktop with an Ubuntu 8.04 i386 disc in the drive and was presented with the reboot screen. Subsequently, I believe this bug is fixed!

To test this bug wubi-selfextract.exe (rev 503) has to be on a CD. Running wubi.exe from hard disk will always work (thus invalidating the test)

At the time of writing rev 495 ships with the CD, until wubi is updated on the daily ISO, you will need to create your own CD by unpacking, replacing wubi.exe and packing back the ISO, then burning the CD.

That also requires vista with latest patches, since it is the only set-up that triggered the problem in the first place

So basically same procedure as in https://bugs.edge.launchpad.net/wubi/+bug/204128/comments/19
But you have to replace wubi.exe with http://wubi-installer.org/devel/minefield/wubi-selfextract.exe

This is now fixed with wubi-self-extractor.

Tested using Ubuntu 20080620.1 and adding Wubi-self-extract rev 504.

No issues with the installer part at all.

Only issue comes after the install but is known.