No. It needs to be fixed.
The wrong version of wubi.exe (10.04.1) is on
http://releases.ubuntu.com/lucid/ and the same version is now on
http://www.ubuntu.com/desktop/get-ubuntu/windows-installer and this one is
the one most people download.
The main one (
FYI for users running into this problem:
The wubi.exe for 10.10 Maverick Meerkat can be obtained at
http://releases.ubuntu.com/maverick/wubi.exe
The wubi.exe for 10.04 Lucid Lynx can only be obtained at
http://people.canonical.com/~evand/wubi/lucid/wubi-r191.exe
You can also get wubi.exe by
Simon H., please see bug 762833
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/653478
Title:
10.10 RC wubi install fails on Windows XP SP3
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I had previously run a couple of upgrade tests on April 6 to test some lupin
changes (bug 610898) - and I didn't have any problems then.
There were some minor differences in the way I did the upgrade for those
tests:
(a) I did the upgrade from a fresh 10.10 install, and
(b) ran the upgrade from
I just completed another upgrade test. No issues this time.
Minor variation in test method to save a bit of time:
a) fresh 10.10 install
b) all available 10.10 updates
c) ran cdromupgrade using the current daily alternate ISO, also checking
online for latest packages (to save time)
--
You
Someone has updated the version of Wubi.exe on
http://www.ubuntu.com/desktop/get-ubuntu/windows-installer to the old
wubi 10.04.1 - and this update must have been very recent. Prior to this
it was downloading 10.10 wubi.exe.
Thsi version of wubi.exe (10.04.1) does not work at all anymore since
** Summary changed:
- wubi fails to install all the files properly.
+ Incorrect version of wubi.exe on
http://www.ubuntu.com/desktop/get-ubuntu/windows-installer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It took me forever to figure out that my mouse pointer has to be *right
in the top left corner* to get Unity to show. I kept putting it on the
Ubuntu icon at the left, in which case you get the opaque half showing
Unity. Now if you click on that you get the application search screen
instead.
That
** Attachment added: Screenshot-4.png
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/734595/+attachment/2011396/+files/Screenshot-4.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734595
Public bug reported:
Binary package hint: overlay-scrollbar
When there is a lot of content in the window, the scrollbar activation
area is very small. You move your mouse to the right of the screen to
pick up the scrollbar, but it doesn't show (just the window resize). You
have to find the 'tiny
** Attachment added: Screenshot-5.png
https://bugs.launchpad.net/bugs/756802/+attachment/2012033/+files/Screenshot-5.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/756802
Title:
Activation
I realised that it's similar to a normal scrollbar (the slider gets
smaller depending on the amount of content) - however on those you can
still click on the track and page down/up without navigating to the
slider. This may be a bug in the way the log file viewer and the
overlay-scrollbars
install to the drive MBR.
The following showed my tests :
bcbc@ubuntu:~$ mount | grep '/host'
/dev/sda3 on /host type fuseblk
(rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
bcbc@ubuntu:~$ sudo grub-install /dev/sda2
Installation finished. No error reported.
bcbc@ubuntu
I don't think anyone is doing the grub-install on Wubi intentionally -
sometimes they will follow bad instructions and do it. So the sledgehammer
approach is good (that's what I was testing). I wasn't aware of
grub-install /dev/loop0 being useful - thought it was more a glitch that
grub had that
Only ext4 as far as I know - it hangs when it tries to read them (hard
reboot required). This only affects users whose Ubuntu partition is prior to
window e.g. /dev/sda1 = ext4. Most Windows users have windows on /dev/sda1
or /dev/sda2. But this is not always the case. And if you install Wubi to
I just did an upgrade from 10.10 (fresh install on the same partition as
Windows) and it successfully upgraded and updated the /host/wubildr. Reboot
showed the latest version of grub 1.99_rc1-8ubuntu2.
Perfect.
I'm going to test the non-windows partition upgrade next.
--
You received this
I updated my current non-windows Natty install and it updated lupin-
support to the latest version. So I reran dpkg-reconfigure grub-pc. It
ran grub-install and it updated my wubildr on the Windows partition
/dev/sda2 correctly (install is on /dev/sda3). The only downside is
that it prompted me
Upgrade on non-windows partition worked perfectly as well. No prompts
regarding installing Grub and it updated the wubildr on the windows
partition. Excellent job!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK glad to hear you've reproduced this - I couldn't get to my test computer
for a few hours anyway to get you that info.
Also great that you've identified the issues in 10.04 as well. Thanks for
the hard work.
On Tue, Apr 5, 2011 at 11:37 AM, Colin Watson
cjwat...@canonical.comwrote:
One issue... if wubildr is only on the target partition then it will
grub4dos fail in some cases e.g. if you install to a partition that falls
after an ext4 partition (the version of grub4dos that wubi uses gets stuck
on these - probably a more recent version of grub4dos version would solve
this).
The upgrade worked. I did a fresh Maverick install on the windows partition
and used today's alternate image to run the upgrade. The upgrade worked
successfully.
1. the /host/wubildr was not modified at all (I used diff to compare before
an after). The Grub Menu showed version
Maddy, maybe i wasn't clear. It worked (initially) but the wubildr
wasn't updated and finally it dropped me at a grub prompt. (That was
buried a bit in my analysis).
Anyway... to continue:
I ran sudo grub-install /dev/sda2 (My /host is /dev/sda2) and it regenerated
the /host/wubildr (also
I confirmed a fresh wubi install on today's daily live desktop image, but
using wubi.exe rev206 (separately downloaded) works. I'll test the upgrade
soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
that worked on the Windows-partition install, it fails:
bcbc@ubuntu:~$ sudo grub-install /dev/sda3
[sudo] password for bcbc:
/usr/sbin/grub-setup: warn: Attempting to install GRUB to a partitionless disk
or to a partition. This is a BAD idea..
/usr/sbin/grub-setup: error: embedding is not possible
Yes lupin-support is installed. I believe that's always included with
wubi - you could previously prevent it by hitting the skip button during
the ubiquity install (bug 620028), but the latest ubiquity doesn't have
a skip button (that I've noticed). I've got version 0.33 installed.
bcbc@ubuntu
Good work!
It seems likely this is the same problem that's caused boot problems on
10.04 after grub updates and the upgrade from 10.04 to 10.10 (bug
653134, bug 682337).
Any chance that - if there is a grub update on 10.04 and/or 10.10 in the
future - this can be included?
--
You received this
Thanks for the quick fix. I can confirm that it is working. It wasn't in
my daily-live image, but after running the latest updates, it was fixed
(and grub-install -v shows 1.99~rc1-5ubuntu1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Based on the documentation here:
http://d-i.alioth.debian.org/manual/en.i386/apbs04.html#preseed-time
and the preseed file:
## CLOCK AND TIME ZONE
d-i clock-setup/utc boolean false
d-i time/zone string America/Vancouver
it's supposed to say that the computer time is not in UTC format, and
the
I reinstalled (Natty test). It sets my location correctly to Vancouver,
however it looks like it assumes that the computer clock is set to UTC
as the time was displayed as 3:36PM (instead of 10:36PM). As soon as I
connected to the net it fixed itself.
** Attachment added: debug
I reinstalled the same version of Wubi and checked grub.cfg. The lupin entry
looks like this:
### BEGIN /etc/grub.d/10_lupin ###
menuentry Ubuntu, Linux 2.6.38-6-generic {
insmod part_msdos
insmod ntfs
set root='(/dev/sda,msdos3)'
search --no-floppy --fs-uuid
** Also affects: lupin
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738345
Title:
Grub2 entries to boot Wubi incorrect... Error: file not found, Press
There is another issue with grub.cfg on Wubi. Not on the initial install
but after running update-grub. I created a new bug 738345 under lupin,
but realised it's not the lupin script after all, but grub that must be
causing it. I wanted to mention it here as I have no idea how to assign
a bug to
Public bug reported:
The 10_lupin script generates menu entries to boot Wubi installs. The following
entry has been created:
### BEGIN /etc/grub.d/10_lupin ###
menuentry Ubuntu, Linux 2.6.38-7-generic {
insmod ext2
set root='(/dev/loop0)'
search --no-floppy --fs-uuid --set=root
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/738345
Title:
Grub2 entries to boot Wubi incorrect... Error: file not found, Press
any key to continue at boot
--
ubuntu-bugs mailing list
** Attachment added: grub.cfg
https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/738345/+attachment/1921266/+files/grub.cfg
** Description changed:
The 10_lupin script generates menu entries to boot Wubi installs. The
following entry has been created:
### BEGIN /etc/grub.d/10_lupin
Public bug reported:
Binary package hint: unity
Left computer for a while, screensaver activated and then I assume the display
went to sleep. Upon moving the mouse and hitting some keys, the display did not
reappear, just the mouse. Eventually I rebooted (Alt+SysRq REISUB).
I also noticed that
** Attachment added: Application window after I click on Installed. Show 73
more results
https://bugs.launchpad.net/bugs/738361/+attachment/1921360/+files/Screenshot-1.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
When you install Wubi - before you reboot it sets up a file
C:\ubuntu\install\custom-installation\preseed.cfg which contains
instructions to ubiquity on how to install (including the timezone).
e.g. in mine it shows:
## CLOCK AND TIME ZONE
d-i clock-setup/utc boolean false
d-i time/zone string
I did get an /var/log/installer/debug file (I don't know if this is
always created - I ran my install in Verbose mode). And as far as I
can see it doesn't refer to the preseed file's location.
** Attachment added: debug
I forgot to mention that the debug file above was from an installation
that failed for another (unrelated reason). So it might be that it
didn't get to the timezone part. I'll look out for this the next time I
do a fresh install and see if I can get some better info
--
You received this bug
Installing Wubi on some raid setups seem to work fine. Others not. This is not
likely a Wubi issue - maybe Ubiquity?
In some cases, there is raid metadata present even if there is no raid in use.
This also seems to confuse things.
Another issue can be the mixture of GPT and MBR partition table
It works great for me too!
I get one error message prior to the grub menu being displayed... '
error: prefix is not set'
But after that it worked flawlessly. The installer seemed quicker, the
bootup was very speedy, and I was surprised that Unity even worked on my
machine (never did before.)
--
Just reran a Wubi install with the version available in bug 693671. The
ubiquity installer problem is no longer happening - it ran without any
exceptions. So this bug is no longer relevant.
** Changed in: ubiquity (Ubuntu)
Status: New = Invalid
--
You received this bug notification
** Changed in: wubi
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/709952
Title:
Update won't boot
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Please supply more details about the error message. The message The
root.disk does not exist is clearly incorrect, because you can still
boot the older kernel. Is dropping you at a busybox prompt? This has
been a fairly common problem with the post-install procedures resulting
in a bad initrd.img
This is a failure in the post install procedure for the 2.6.35-25 kernel
to generate an initial ram disk correctly. Boot the working kernel, go
to a terminal (CTRL+ALT+t) and recreate it using the command I showed.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
That's odd. Did you specify '-k all'? Maybe you do have a problem with
the root.disk. This is what I suggest - use this tool
http://ext2read.blogspot.com/ to recover any important data you have off
the root.disk, and then reinstall.
If you can't view the root.disk using that tool it may be
Yes, definitely a reinstall is the best option if that's the case.
But note that running another operating system is way more risky than
installing a little tool like ext2read, if you're concerned about your
wife's computer.
On Mon, Feb 28, 2011 at 12:59 PM, Lyle Paciorek
You misunderstood me. ext2read is only useful if you want to recover
important data before uninstalling/reinstalling Ubuntu. You said that there
is no important data, so there's no need to use it.
The attempt to repair it already failed, and the only other methods are
through chroot that are too
I did a comparison of the po directory from bazaar. The following are included
with WUBI but not in Ubiquity:
af.po, as.po, br.po, crh.po, csb.po, various flavours of english (en_AU/CA/GB),
fa.po, fy.po, is.po, jv.po, kab.po, kn.po, mo.po, ms.po, mt.po, nb.po, nn.po,
te.po, tw.po, ur.po, uz.po,
@Barry, from my understanding, wubildr.mbr is grub4dos's bootloader, and
it looks on the root of all partitions until it finds the 'rest of
itself': the wubildr file. (Standard grub4dos is the grldr.mbr and
grldr but you can rename these, as has been done for wubi).
The Try (hd0,0): file system:
There've been a number cases of this particular error. There may be
different causes but the ones I have seen are not wubi-specific:
sometimes when the kernel is updated the initial ram disk is not
generated correctly. You can tell If this is the problem by booting a
previous kernel - if it works
Public bug reported:
Binary package hint: ubiquity
Fresh wubi install of Wubi Natty Alpha 2.
Apply workaround to kickoff install by replacing wubildr file (see bug 693671).
The install dialog box starts: Install and the text Verifying the
installation
Then an error box pops up entitled: No
@Jean-Baptiste,
No problem... I created bug 713395 for this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/693671
Title:
wubi install will not boot - phase 2 stops with: Try (hd0,0): NTFS5
--
It doesn't go into a tight loop right away. I restarted the install in
Verbose mode and dropped to a terminal CTRL-ALT-F2 when I got the first
No root file system is denied. I captured the logs and then hit CTRL-
ALT-F7 back to GUI and hit OK to continue. Took logs again. Did that 4
times.
The
Just tried an upgrade to Natty from Maverick using what I guess will be
Alpha2. The grub.cfg generation no longer fails as script
/etc/grub.d/00_header now inserts true into the empty load_video
function. So that's good.
The upgrade doesn't clutter /boot/grub with the grub modules known to
break
@elliot, locking grub-pc and grub-common works to prevent boot problems caused
by updating those packages. e.g. on a fresh install of Wubi. If you've already
updated grub-pc or upgraded to 10.10, then the /boot/grub directory contains
all the grub modules - and that results in the buggy
I've been looking at how wubildr.mbr works - it finds and uses the first
wubildr by scanning the root of all partitions, in BIOS order. On my
computer the C: drive is the second partition and it never uses
C:\WUBILDR. It always uses the one on my recovery partition /dev/sda1.
So Grub2 is using
Update - users affected by this bug and have fixed it by patching their
MBR may then go on to be affected by bug 682337 (choosing Ubuntu either
results in reboot, hang, or grub prompt).
The fix is describe in the Wubi megathread
(http://ubuntuforums.org/showthread.php?t=1639198) Problem #2,
I've been doing some paperwork today - linking Questions from
answers.launchpad.net to the relevant bug. For those people that are
receiving emails today many of whom solved the problems a month ago -
please ignore - bugs are treated as higher priority when more people are
affected so this is an
I think this bug is more to do with the fact that Wubi offers languages
that aren't supported by Ubiquity - not so much that Afrikaans is not
supported (I just picked the first one on the list). It may be that the
fix is to provide an Afrikaans translation... but there might be other
mismatches.
Further info...
New Wubi installs only contain two files in /boot/grub: grubenv and grub.cfg
The problem is that when grub.cfg is generated, it fails with syntax
errors. The load_video function is empty. This is because the script
references a file /boot/grub/video.lst and this does not exist.
Actually Wubi doesn't use the MBR to boot - it uses the windows boot
manager.
Describe in more details the symptoms you are seeing. Check the Startup
Recovery settings (system properties, advance tab, click on settings
under Startup Recovery). Check the timeout is not zero, and confirm
that
You can get it to install by replacing the wubildr file that comes with
Natty, by one from Maverick. You have to replace the wubildr on the
first partition that contains it, not just the one on your windows
partition.
There are other issues getting the Natty Alpha 1 to boot:
Bootloader install
PS that bootloader install failed message occurs near the end of the
Installer slideshow. That's why I added Ubiquity as an affected project.
I'll leave that to someone to confirm or remove as appropriate.
In summary...
1. bad wubildr shipped with wubi.exe,
2. an exception installing grub
** Summary changed:
- wubi-r200 install will not boot
+ Natty 11.04 Alpha 1 - wubi-r200 install will not boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/693671
Title:
Natty 11.04 Alpha 1 -
@sflitman,
Wubi - windows ubuntu installer - can be run from a CD under windows, or using
wubi.exe and the .iso in the same folder under windows, or just wubi.exe alone.
They all result in the same wubi-thing that can be uninstalled.
Beware: there are some serious issues with grub at the moment
I forgot bug 682337 - this is the one that is about grub updates
breaking a fresh 10.04.1 install. (610898 and 609815 I listed before are
likely the same issue).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Laurens-Jan,
I never install with an internet connection. So I don't think that has anything
to do with this bug. The only instances I've seen of it are when the user
clicking the SKIP button, and it seems - based on feedback - that reinstalling
is always successful.
So perhaps you have some
@Mayukh,
It sounds like you have a different problem, perhaps specific to your computer.
This bug is specifically related to grub updates that result in the grub
bootloader being installed over the windows bootloader. I'm guilty too of
bringing up a recent grub issue but only because I
@Arolk, re. your email, you need to reinstall the windows bootloader. See
Problem #1, Solution #1 or #2 in
http://ubuntuforums.org/showthread.php?t=1639198 (not Problem #2)
If you have any issues you can post on that thread for help. Hope that helps.
--
You received this bug notification
PS.
To install 10.04 netbook or xubuntu, use
http://people.canonical.com/~evand/wubi/lucid/wubi-r189.exe
To install 10.10 (any version) use http://releases.ubuntu.com/maverick/wubi.exe
Or, burn the .iso you want to CD and run it from there
--
You received this bug notification because you are
The reason these extra files get placed in /boot/grub is that grub-
install is called to update the wubildr file, and grub-install calls
grub-install.real (for wubi) and that copies the files (in the following
code grubdir is /boot/grub and pkglibdir is /usr/lib/grub/target
cpu/):
for file in
OK I have the permanent fix for 10.10 Probably works on 10.04.1 too.
First back up /boot/grub
sudo cp -r /boot/grub /boot/grubbackup
Then delete all the stuff in /boot/grub that isn't supposed to be there
(everything added after fresh wubi install)
cd /boot/grub
sudo rm *.mod
sudo rm *.img
The permanent fix to the grub problem for 10.04.1 installs on the same
partition as windows is described here:
http://ubuntuforums.org/showpost.php?p=10180622postcount=13
It's the same for 10.10 wubi installs to the same partition described in
bug 653134.
This is a manual workaround that allows
Eric this fix has already been released . If it has broken your install
the fix involves getting Wubi to boot, and then manually repairing it.
At ubuntuforums.org we are working on a single thread to explain all
this in a clear and concise way, but in the meantime, you can do this.
Boot a live
Jordan,
It's great you have a patch, but Wubi has an even bigger problem right now. The
same grub update that is causing a spike in the overwritten bootloader problem
(bug 581760) is also breaking Wubi installs that are on the same partition as
windows (c:)
I am seeing a large number of these
I installed a fresh 10.10 Maverick using Wubi. Then I went into synaptic and
reinstalled grub-pc. This is the diff file from grub.cfg before reinstalling
and after.
35,36d34
insmod vbe
insmod vga
39,59d36
insmod part_msdos
insmod ntfs
set root='(hd0,msdos2)'
search --no-floppy
** Attachment added: After reinstalling grub-pc
https://bugs.launchpad.net/wubi/+bug/653134/+attachment/1749378/+files/grub.cfg
--
Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
https://bugs.launchpad.net/bugs/653134
You received this bug notification because you are a member of
** Attachment added: Grub.cfg that comes with new 10.10 install
https://bugs.launchpad.net/wubi/+bug/653134/+attachment/1749379/+files/grub.cfg
--
Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
https://bugs.launchpad.net/bugs/653134
You received this bug notification because you
Actually there were no differences in /etc/grub.d
There were a lot of differences in /boot/grub (all the .mod files aren't there
on a default wubi install, but are added when reinstalling grub-pc).
--
Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
Updated to the latest Maverick kernel = grub prompt on reboot.
So... conclusion. Updating grub-pc on a wubi install breaks wubi. I will
now do a reinstall and diff the entire installation to see what else
changes.
--
Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
This is the full diff of a new wubi 10.10 install before and after
reinstalling grub-pc
** Attachment added: full_wubi_diffs_after_grub_reinstall
https://bugs.launchpad.net/wubi/+bug/653134/+attachment/1749421/+files/full_wubi_diffs_after_grub_reinstall
--
Can't boot Ubuntu after an upgrade
@Lucas, reinstall the windows bootloader to fix.
--
grub-pc upgrade renders computer unbootable when Wubi is installed to partition
other than Windows
https://bugs.launchpad.net/bugs/610898
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
1. Install Wubi Ubuntu 10.04.1 on same partition as Windows
2. Run all updates listed by update manager (210MB) including grub-pc and
grub-common
3. Reboot.
Result, Ubuntu does not boot. Selecting ubuntu from the Windows boot manager
causes computer to reboot.
The only workaround I can find is
Even for users who installed on the same partition as windows, the wubildr
update is failing. So we have wubi users who installed on the same partition
can't start Ubuntu. And wubi users who installed on a different partition
installing grub and not booting either windows or ubuntu.
And all
pity about users who didn't install on the same partition as windows.
let the borkage commence. is it me or does it appear 1 test case was
enough to verify?
--
[Wubi] when updating it advices to install grub on all partitions
https://bugs.launchpad.net/bugs/581760
You received this bug
** Description changed:
Binary package hint: ubiquity
- Installed Ubuntu 10.04.1 during iso testing using the Wubi installer. I
select French as the language of choice and visibility aid 3. The installation
proceeded normally, rebooting, and Ubiquity proceeded normally (all screens in
One month since release...
Riddle: what do you call an operating system that won't boot?
--
Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
https://bugs.launchpad.net/bugs/653134
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Some affected users:
http://ubuntuforums.org/showthread.php?t=1613473
http://ubuntuforums.org/showthread.php?t=1564392
http://ubuntuforums.org/showthread.php?t=1600859
http://ubuntuforums.org/showthread.php?t=1563031
The first link reports that the wubi installer downloaded the netbook
10.04
@hpp3, did you install a fresh wubi 10.10 or upgrade to 10.10 from
10.04?
--
Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
https://bugs.launchpad.net/bugs/653134
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
@Colin,
I can't break a fresh wubi 10.10 install using the above method (grub-install
/dev/sdaY and update-grub). So it appears only upgrades are affected - perhaps
missing/corrupt module?
--
Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
https://bugs.launchpad.net/bugs/653134
You
@Colin,
So I've been running maverick with the 'fix' (copying the wubildr out of
winboot) and made a few changes (not the least of which is moving to Natty). I
noticed the invalid mode command flashing by since then, but still worked.
But then I removed the old maverick kernel, regenerating
@Colin,
Confirmed this fix... I changed grub-mkimage back to original, ran
grub-install /dev/sdaY. Reboot, still worked but now I am seeing the No
suitable mode found messages flash by. Then I run sudo update-grub and
reboot grub prompt.
So, updating wubildr followed by a regeneration of
@colin,
I've noticed cases where grub is being installed to windows partitions
again. Not sure if related to the current wubi probs but thought I'd
mention it. It's a little different than the old one that used to refer
to partition #256. e.g. http://ubuntuforums.org/showthread.php?t=1603958
Any update on this?
Some users reported copying the wubildr from the c:\ubuntu\winboot\ directory
over c:\wubildr fixed the problem for them - which doesn't make much sense to
me - but I've seen 3 comments stating that this worked. My own broken wubi
install is still the same (error: no
well blow me down, I just copied my old \ubuntu\winboot\wubildr and it
worked. haha. I'd love to hear an explanation.
--
Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
https://bugs.launchpad.net/bugs/653134
You received this bug notification because you are a member of Ubuntu
Bugs,
@Colin, OK thanks for the info. FYI on the one broken upgrade to 10.10 I
updated the wubildr and regenerated grub.cfg but it then gave me a
different error: invalid mode.
I still think it's worthwhile to put in some sort of workaround to
preventing problems for wubi installs to a different
Public bug reported:
Binary package hint: update-manager
Update manager in 10.10 RC up to date, pops up an authenticate window.
You enter your password and hit Authenticate and the window just stays
there (now without the password option). Clicking on Authenticate or
Cancel does nothing. If you
** Attachment added: Screenshot.png
https://bugs.launchpad.net/bugs/656975/+attachment/1679052/+files/Screenshot.png
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/656975/+attachment/1679053/+files/Dependencies.txt
--
Update-manager Authenticate window stuck
101 - 200 of 253 matches
Mail list logo
