** 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
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
@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
@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:
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,
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
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
** 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
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
I have started seeing wubi users overwriting their MBR with grub2 after
running the latest updates - probably this patch. It's not clear yet
whether they are prompted to select the drive or it's doing it
automatically - I am trying to get feedback - but either way this seems
to be a continuation
Thanks Erick.
I don't have my test computer with me, and I don't want to try it on my
netbook (I need it functional for work while I am away) until I can
confirm that there is a grub prompt involved. The only feedback I've had
couldn't recall selecting any drives, so I am not sure if this runs
From what I can gather, the users are not selecting to install grub to
the MBR. They recall a grub popup during the updates, but did not click
on any checkboxes. Haven't been able to figure out if it's always a
'separate partition install' but that's my suspicion.
--
Ubuntu Lucid grub2
They're coming slow, but steady...
http://ubuntuforums.org/showthread.php?t=1540744
http://ubuntuforums.org/showthread.php?t=1540772
http://ubuntuforums.org/showthread.php?t=1539672
The person with the netbook is affected worse as they can't just insert
their windows dvd to repair.
I think it's
I created a new bug https://bugs.launchpad.net/wubi/+bug/610898
--
Ubuntu Lucid grub2 dist-upgrades result in confusion
https://bugs.launchpad.net/bugs/576724
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
11:15 /host/wubildr
b...@ubuntu:~$ sudo grub-install /dev/sda2
[sudo] password for bcbc:
Installation finished. No error reported.
b...@ubuntu:~$ ls -l /host/wubildr
-rwxrwxrwx 1 root root 88171 2010-07-11 17:02 /host/wubildr
b...@ubuntu:~$
b...@ubuntu:~$ sudo grub-install /dev/sda
Installation
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/51750132/Dependencies.txt
--
grub-install wrapper inconsistencies
https://bugs.launchpad.net/bugs/604417
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
= /host/ubuntu/disks ]
+ read DEV MTPT FSTYPE OPTS REST
+ [ /proc/sys/fs/binfmt_misc = /host/ubuntu/disks ]
+ read DEV MTPT FSTYPE OPTS REST
+ [ /home/bcbc/.gvfs = /host/ubuntu/disks ]
+ read DEV MTPT FSTYPE OPTS REST
+ [ /media/E25A-9F70 = /host/ubuntu/disks ]
+ read DEV MTPT FSTYPE OPTS REST
+ [ /media
It also affects non-wubi installs, by replacing the grub bootloader with
what it figures is the correct target, but it sometimes gets it wrong.
In one case, the uuid was invalid. In another, it seemed to be pointing
at the right partition (but bootinfoscript is not clear on this - it
says
@takkat - in any case, this is splitting hairs, more typical of a
bureaucracy - the same developer is responsible and can see the issue
whether it came in duplicate with a shiny red stamp or not. At the end
of the day, my job (as I see it) is to let them know they've made a
mistake. Then they can
I finally got to test the grub update. Before with wubi, when it
prompted the checkbox 'skip installing grub' you had to check the box to
go forward. Now, if you don't check the box, when you click on Forward,
it goes back to the select a device to install grub screen that had been
suppressed, and
@Takkat - I agree, let's change the help text... but let's get it done
quickly: we are still seeing people affected by this on a daily basis.
And no, it's not just inexperienced users. I've seen long-term ubuntu
users upgrading from 8.04 get hit by this. To be more precise it's users
that don't
Quote from bug #1
2. Ubuntu should be marketed in a way such that its amazing features and
benefits would be apparent and known by all.
3. The system shall become more and more user friendly as time passes.
Quote from http://ubuntuforums.org/showthread.php?t=1505663
Lessons I've learned:
1.
Just to add to Erick's comment, I am still seeing users being hit by
this problem on a daily basis. Although this report says 9 people
affected I can assure you it's much higher. Unfortunately most of these
people are new users attracted to Ubuntu and it's not very good
advertising.
So, isn't it
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,
There are a few real cases (not testing) where this problem has occurred:
http://ubuntuforums.org/showthread.php?t=1546788
http://ubuntuforums.org/showthread.php?t=1556655
** Description changed:
Binary package hint: ubiquity
Installed Ubuntu 10.04.1 during iso testing using the Wubi
Public bug reported:
Binary package hint: gnome-keyring
Running upgrade from 10.04.1 to 10.10 using the alternate daily .iso
(running the cdromupgrade).
A couple of errors related to the keyring popped up - the Take screen
shot tool didn't work as it said .png file type unknown and terminated
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/650790/+attachment/1651633/+files/Dependencies.txt
** Attachment added: VarLogDistupgradeAptlog.gz
https://bugs.launchpad.net/bugs/650790/+attachment/1651634/+files/VarLogDistupgradeAptlog.gz
** Attachment added:
** Description changed:
Binary package hint: gnome-keyring
Running upgrade from 10.04.1 to 10.10 using the alternate daily .iso
(running the cdromupgrade).
- A couple of errors related to the keyring popped up - the Take screen
- shot tool didn't work as it said .png file type unknown
FYI, I ran a successful upgrade since the fix was released - the fix
obviously didn't make it into the release candidate .iso, so running the
upgrade from RC alternate cd (using cdromupgrade) gives the same gnome
keyring error, however allowing cdromupgrade to pull the latest packages
from the net
I should add that this was a wubi upgrade... and the wubi failed to
start following the upgrade (rebooted without showing any error messages
or grub menu). I am considering this to be unrelated since my previous
upgrade of wubi that showed the gnome-keyring error and specifically
stated that the
@Colin,
I don't really understand enough about what you are trying to accomplish... is
it that you have to update the wubildr? I ask because I've never seen wubildr
updated by a grub-pc update on any wubi install I've had, despite the fact that
grub-install has the ability to do this.
If the
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
** Attachment added: dist-upgrade.tar
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/656975/+attachment/1679088/+files/dist-upgrade.tar
--
Update-manager Authenticate window stuck
https://bugs.launchpad.net/bugs/656975
You received this bug notification because you are a
@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
Just did a fresh install from maverick daily live - works perfectly.
It's really fast to connect and no need to modprobe ndiswrapper on
reboot. It's the -22 kernel.
Good Job!
--
ndiswrapper can scan for SSIDs but cannot connect on any kernel newer than
2.6.34-5.14
The computer that requires ndiswrapper does not have an ethernet
connection available so I always use the ndiswrapper that comes with the
.iso. The versions from my latest install are: 1.56-2 (and ndisgtk is
0.8.5-1)
(It also shows 1.56-2 as being the latest available version in synaptic.
)
--
@requestedRerun, see the https://wiki.ubuntu.com/WubiGuide on how to
loop mount a wubi root.disk. (Section 15. How can I access my Wubi
install and repair my install if it 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
@Colin, what about the 10.04.1 users having the same problem? Is the fix
to run grub-install /dev/sdaY to update the wubildr? If that is the
case, how do you fix it if the wubi is installed to a partition other
than windows. At the moment I am giving them the workaround but no fix.
Please advise
I just ran updates, picked up the lupin fix, but system still 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.
--
ubuntu-bugs
The same thing happens with the Netbook edition which is also at 10.04
still. Users report that wubi.exe downloads the full .iso, then checks
it and when it detects the version mismatch, it starts downloading the
same image again.
Correction could be to either release 10.04.1 in all supported
Grub2 also ignores request to not install boot loader.
I installed lucid 10.04 beta 1 to external USB (/sdb). Selected 'Advanced' and
deselected 'Install boot loader' (as I use grub2 with my karmic install to boot
into lucid). It prompted me - are you sure etc...
It then installed a boot loader
I have the same problem using Lucid Beta1 - except that it's
intermittent. It's been happening since Beta1 and with updates done
daily. I do the normal boot, usually works fine. Every now and then it
freezes. I removed 'quiet spash' and it ends as described above at
Checking battery status
I
Same thing happened to me after adding 5 new locations. Not using amd64.
I couldn't reproduce the bug, either by adding additional locations, or
removing all but the default and adding back the ones that caused the
first crash.
--
clock-applet crashed with SIGSEGV in g_main_context_dispatch()
The patch works for me.
I installed the .debs from Leann's link first. It worked, but then I purged all
ndiswrapper-* since they were installed from Julian's ppa and reinstalled
ndiswrapper-common, -utils and ndisgtk from the beta maverick desktop image I
initially installed from.
However
I installed maverick alpa3 brand new install on my computer. I installed
ndiswrapper-common, -utils and ndisgtk from the alpa3 CD, and then added my
windows wireless driver.
Trying to connect to my wireless using ndiswrapper generated a 'kernel oops'.
I have no problems using the above
I didn't install dkms (hadn't seen this before) - tried it later when I
couldn't get connected but it complained about dependencies required to build
source, so didn't bother.
I always just install, -common, -utils, and then ndisgtk.
--
ndiswrapper can scan for SSIDs but cannot connect on any
** Attachment added: crash report
https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/613796/+attachment/1490508/+files/linux-image-2.6.35-14-generic.158937.crash
--
ndiswrapper can scan for SSIDs but cannot connect on any kernel newer than
2.6.34-5.14
I think this is also a duplicate of
https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/604417 which is a problem
in the lupin overrides of grub, as it relies on the existence of the file
/host/wubildr to determine if it's a wubi install.
If you don't install wubi on the same partition as
@Alex, I had the same issue when testing the MBR issue with the latest
updates: choosing Ubuntu ends up at a grub prompt.I am assuming your
wubi is on /dev/sda3 based on your comments:
This is the easy way but may not work:
grub configfile (hd0,3)/ubuntu/winboot/wubildr.cfg
This is the long way:
@ buBoo2Age:
based on xissburg's comment above, I'd say his root.disk was on E:, so /host
did not contain wubildr. So I do think the issue is the same. I should probably
clarify: I think the end result is the same as bug 604417 (as it should have
prevented the damage), however, I don't think
', 'en']
08-18 01:03 DEBUG WinuiInstallationPage: target_drive=C:,
installation_size=3000MB, distro_name=Ubuntu, language=af_ZA,
locale=af_ZA.UTF-8, username=bcbc
08-18 01:03 INFO root: Received settings
08-18 01:03 INFO WinuiPage: appname=wubi,
localedir=C:\DOCUME~1\Admin\LOCALS~1\Temp
\Temp\pylC.tmp\translations,
languages=['en_CA', 'en']
08-18 01:03 DEBUG WinuiInstallationPage: target_drive=C:,
installation_size=3000MB, distro_name=Ubuntu, language=af_ZA,
locale=af_ZA.UTF-8, username=bcbc
08-18 01:03 INFO root: Received settings
08-18 01:03 INFO WinuiPage: appname
Public bug reported:
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
French) and
** Attachment added: partman
https://bugs.launchpad.net/bugs/620028/+attachment/1498348/+files/partman
--
Wubi installs but no Ubuntu entry in Grub
https://bugs.launchpad.net/bugs/620028
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/620028/+attachment/1498349/+files/syslog
--
Wubi installs but no Ubuntu entry in Grub
https://bugs.launchpad.net/bugs/620028
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: grub.cfg
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/620028/+attachment/1498350/+files/grub.cfg
--
Wubi installs but no Ubuntu entry in Grub
https://bugs.launchpad.net/bugs/620028
You received this bug notification because you are a member of Ubuntu
Bugs,
** 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
Confirmed problem exists with an upgrade from 10.04.1 to maverick.
Wireless working before upgrade, but not afterwards. Same kernel oops.
** Tags added: iso-testing
--
ndiswrapper can scan for SSIDs but cannot connect on any kernel newer than
2.6.34-5.14
https://bugs.launchpad.net/bugs/613796
@Julian, thanks this worked for me too!
--
ndiswrapper can scan for SSIDs but cannot connect on any kernel newer than
2.6.34-5.14
https://bugs.launchpad.net/bugs/613796
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This is happening to a number of people with the -24 kernel. e.g.
http://ubuntuforums.org/showthread.php?t=1565714
It's a problem for those using a fresh 10.04.1 install as they only have
the -24 kernel.
--
linux-image-2.6.32-24-generic cannot find root filesystem
** Changed in: ubiquity (Ubuntu)
Status: New = Confirmed
--
Wubi installs but no Ubuntu entry in Grub
https://bugs.launchpad.net/bugs/620028
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
@Erick, sorry can't help you with your wubi problem. It's always just
worked for me - on a variety of machines. While I can and do pass on
known fixes to others, I haven't come across a known fix or workaround
to your issue. I suppose you could install 9.10 wubi and upgrade to
10.04. It's a pain,
Here are a few from the last week that I've personally been involved
with.
http://ubuntuforums.org/showthread.php?t=1494021
http://ubuntuforums.org/showthread.php?t=1491780
http://ubuntuforums.org/showthread.php?t=1492209
http://ubuntuforums.org/showthread.php?t=1490763
A search of ubuntuforums.org with the following search string: Boot
sector info: Grub 2 is installed in the boot sector (quotes included)
returned 154 results.
--
Ubuntu grub2 dist-upgrades result in confusion
https://bugs.launchpad.net/bugs/576724
You received this bug notification because you
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.
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.
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
@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.
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
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
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 -
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
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
@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
@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
Any update on this bug? Here's a recent request:
http://ubuntuforums.org/showthread.php?t=2070760
It seems like this will become a bigger issue soon when Windows 8 is
released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I'm running Quantal development release up to date. I brought my
computer out of sleep to find that the Chrome browser appeared in all
four desktop workspaces. I closed the actual open chrome application,
but the image of the browser still shows in all four workspaces.
I
This happened again today after thawing from hibernation - this time the
terminal was part of the phantom desktop image - so it's not just
happening to the chrome browser.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I'm running Quantal development release up to date. Sometimes
application windows that I close appear to be still open, but it's an
'image overlay' on the desktop (on all desktop spaces). I'm including a
snapshot as this doesn't make a lot of sense.
Basically, it looks like
I haven't noticed any problems using Wubi or mounting NTFS from normal
dual boot (12.04.1) with Windows 8 - fast start is enabled.
The following is from a fresh Quantal install using Wubi:
bcbc@ubuntu:~$ ls -la /host/hiberfil.sys
-rwxrwxrwx 1 root root 5065179136 Sep 19 22:49 /host/hiberfil.sys
101 - 200 of 247 matches
Mail list logo
