I got it again - not consistently - but here's the log anyway
** Attachment added: valgrind.log
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/740382/+attachment/2448673/+files/valgrind.log
--
You received this bug notification because you are a member of Ubuntu
Bugs,
See http://askubuntu.com/questions/94754/how-to-modify-policykit-to-
allow-hibernation-in-upower for a workaround
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/910183
Title:
Ubuntu 12.04 System
** Branch linked: lp:~bcbc/wubi/lp-365881
** Changed in: wubi
Status: New = Confirmed
** Changed in: ubuntu
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
*** This bug is a duplicate of bug 365881 ***
https://bugs.launchpad.net/bugs/365881
** This bug is no longer a duplicate of bug 427424
WINDOWS- NO DISK ERROR
** This bug has been marked a duplicate of bug 365881
wubi installer's pyrun.exe says no disk
--
You received this bug
@Colin,
This was a problem I had noticed cropping up every now and then on the
forums. I made the assumption that it was ext4 and not the inode size. I had
confirmed it on ext4 but haven't done extensive testing to figure out the
exact problem.
Anyway - I just did a test with the wubildr.mbr
Public bug reported:
After today's update my brightness controls aren't working anymore.
After checking the System Settings, Brightness and Lock there is no
longer any brightness slider bar shown for manual setting either. So my
screen is fixed on full brightness. I'll attach screen shots showing
** Attachment added: After update pic of brightness and lock settings
https://bugs.launchpad.net/bugs/947748/+attachment/2820806/+files/brightness2.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Before today's update pic of Brightness and Lock settings
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/947748/+attachment/2820809/+files/brightness.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've just tested the patch on a FAT32 wubi install and it worked as
intended.
In order to test it, I manually edited the /usr/share/grub/grub-
mkconfig_lib file during the installation (patch wasn't installed), used
'diff' to confirm it matched the patch, and then copied it to
** Attachment added: Grub.cfg after running sudo update-grub following
installation
https://bugs.launchpad.net/wubi/+bug/888281/+attachment/2832362/+files/grub.cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Okay, I see the difference in the diff -u output, and my ordering mistake. I'll
make a note of that.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/888281
Title:
Boot from FAT32 error and
Public bug reported:
The fix from bug 889650 introduced a new bug (see final comment from
that bug):
Anyway, there is a slight difference still. This is the real install:
menuentry 'Ubuntu, with Linux 3.2.0-1-generic (recovery mode)' --class
ubuntu --class gnu-linux --class gnu --class os {
I got a grey blank screen - logged in blind - system reported a crash in
package colord but wouldn't report it. Probably not related but thought
I'd mention it just in case. Using latest daily (19th) and wubi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
That sounds like bug 862003 which means the install is likely
successful.
On Sun, Dec 4, 2011 at 4:22 AM, David Boden
365...@bugs.launchpad.netwrote:
Unfortunately, if I click Continue the 30 or so times required to get
the installation to progress, it ultimately ends up with an error
stating
Public bug reported:
I can't grab windows, move them, minimize/maximize etc. because the
header area is not visible. I've attached a screenshot. I'm running with
an ATI X1300 mobility graphics card. See attached screenshot.
** Affects: compiz (Ubuntu)
Importance: Undecided
Status:
** Attachment added: Screenshot at 2011-08-21 21:42:40.png
https://bugs.launchpad.net/bugs/830851/+attachment/2298477/+files/Screenshot%20at%202011-08-21%2021%3A42%3A40.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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 (
I've just updated on Oneiric 14R N4010. The brightness keys are now
working without any kernel boot options:
bcbc@ubuntu:~$ uname -a
Linux ubuntu 3.0.0-8-generic #11+kamal~mjgbacklight5-Ubuntu SMP Fri Aug 12
23:53:11 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
bcbc@ubuntu:~$ ls /sys/class/backlight
Public bug reported:
I've been getting package update errors. On LGPL_EXCEPTION.txt and
changelog.Debian.gz. To get around it I just delete the file shown in
the error. Seems to work. !?
$ cat /var/log/apt/term.log | grep LGPL
'./usr/share/doc/libqtgui4/LGPL_EXCEPTION.txt' is different from the
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894617
Title:
package libqt4-declarative 4:4.7.4-1ubuntu4 failed to install/upgrade:
'./usr/share/doc/libqt4-declarative/LGPL_EXCEPTION.txt' is
Public bug reported:
But glib-networking not available:
$ sudo apt-get dist-upgrade
[sudo] password for bcbc:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
glib-networking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/896933
Title:
software center crashed - won't allow me to report - says glib-
networking not latest
To manage notifications about this bug go to:
Thanks for that speedy fix. I didn't get around to testing it though :(
Anyway, there is a slight difference still. This is the real install:
menuentry 'Ubuntu, with Linux 3.2.0-1-generic (recovery mode)' --class
ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod
According to http://support.microsoft.com/kb/2419286 :
Problem: “The boot configuration data store could not be opened. The system
cannot find the file specified.”
Symptoms
When you run Bcdedit /enum all you get the following error
“The boot configuration data store could not be opened. The
Testcase 3: Lucid 10.04.2 on E: drive (ntfs partition /dev/sda3)
=
Grub version in wubildr at install 1.98-1ubuntu5
Grub version in Ubuntu at install 1.98-1ubuntu10
debconf-show grub-pc --- install-devices: blank
Test method:
Add Proposed to sources,
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
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.
Repeat of Lucid testcase 3 (different partition than windows' main
drive):
Testcase 3: Lucid 10.04.2 on E: drive (ntfs partition /dev/sda3)
=
Grub version in wubildr at install 1.98-1ubuntu5
Grub version in Ubuntu at install 1.98-1ubuntu10
debconf-show
PS should have mentioned in Results of last testcase (repeat testcase 3)
1. After update, debconf-show grub-pc shows installed-devices: /dev/loop0
2. No wubildr on /host before or after test (expected)
3. Also, I rebooted into Ubuntu following the updates to confirm it worked
(kind of
important
Reran testcases 2 and 4 (Maverick and Lucid install on same partition as
Windows). The test case involved adding -Proposed and just upgrading
packages grub-pc, grub-common, and lupin-support. The results were the
same as reported before.
Conclusion
===
Grub updates with the latest
Wubi 10.04.2 on external drive worked the same. So I'm 5 for 5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/610898
Title:
grub-pc upgrade renders computer unbootable when Wubi is installed to
I'm wondering what happens to users who've locked grub-pc and grub-
common, but who might allow the update to lupin-support to be processed.
These are mostly 10.04 users, or those who upgraded to 10.10 and were
burned with booting problems.
Will the postinst script for lupin-support do a
Re. my last comment, I just tested it and it appears that the Update
Manager won't allow you to select the new lupin-support when an older
version of grub-pc is locked. Trying to do it manually in synaptic
causes synaptic to want to uninstall grub-pc. So there is a hard
dependency on the latest
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).
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.
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
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
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
Thanks for your report. I'd include the installer logs and then assign it to
Ubiquity (Ubuntu) as this is likely the correct project. To collect the logs
you can drop to a terminal CTRL+ALT+F2 and run:
sudo sh /host/ubuntu/install/custom-installation/hooks/failure-command.sh
--
You received
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
Testcase 1: Maverick install on non-windows partition
Installed Wubi maverick 10.10 on my E: 'drive' (ntfs partition /dev/sda3).
Ran all standard updates.
Added Proposed to the sources.
Processed all proposed updates.
Expected result
===
1.
The wubi.exe I downloaded from
http://ubuntu.com/desktop/get-ubuntu/windows-installer just now is signed
by Canonical UK Ltd. and is revision 211 for release 11.04.
I'm not aware of the hash for this being published, but then I've never
looked for it either. The md5 checksum I get
is
Testcase 2: Maverick install on windows partition
Installed Wubi maverick 10.10 on my C: 'drive' (ntfs partition /dev/sda2).
Checked debconf-show grub-pc beforehand: grub-install devices was blank.
Ran most 10.10 standard updates (servers are very busy so
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
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
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
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
This isn't so much a bug in Wubi - this is the normal action. If you run
it the first time it prompts to install. When you run it after
installing, it prompts to uninstall first.
So the bug is that ubiquity is placing Wubi in the Windows startup
programs list and there's no way to remove it
I marked Ubiquity as invalid because I picked the wrong project - I
meant ubiquity (Ubuntu) but instead I chose Ubiquity (upstream), which
I believe is the correct project, not Wubi. But the devs can sort that
out ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@Kate Stewart, Erick asked me to comment on this. I can't speak for the
particular issue he is having deleting the startup option, but I know
enough to point out some flaws in this approach.
1. When Ubiquity detects that there are 4 primary partitions already used and
there is also an existing
Testcase 4: Lucid 10.04.2 on C: drive (ntfs partition /dev/sda2)
=
Grub version in wubildr at install 1.98-1ubuntu5
Grub version in Ubuntu at install 1.98-1ubuntu10
debconf-show grub-pc -- install-devices: blank
Test method:
Add proposed to sources and
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
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.
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
The webpage does actually say that it's the latest version of Ubuntu:
Click the big orange button to download the latest version of Ubuntu. This
Windows installer (Wubi) will help you to run Ubuntu within your current
system.
So the change to point at lucid from maverick doesn't appear to be
/backlight along with intel_backlight,
but it's now I only see the intel_backlight entry.
bcbc@ubuntu:~$ uname -a
Linux ubuntu 3.0.0-8-generic #11+kamal~mjgbacklight5-Ubuntu SMP Fri Aug 12
23:53:11 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
bcbc@ubuntu:~$ ls /sys/class/backlight
intel_backlight
bcbc
That's not a bug file - it's the wubildr.mbr which is used to boot
Ubuntu that is installed through Wubi.
There is a Wubi log file that provides information on the install
attempt and diagnostics on why it may have been unsuccessful. To check
this, hit the windows start key and enter:
I don't have a personal preference on whether the grub menu should be
hidden or not (in a way it's good to familiarize windows users with what
it will look like when they switch to a normal dual boot; on the other
hand, it can irritate users having two boot menus and that drives them
to mess about
Colin Watson wrote: There's no need to shout, scream, talk about how
people should resign, etc., as some people have been doing in this bug
log; that sort of thing is entirely unproductive.
Agreed, but in my defence, it seemed no one was listening. Meierfra's
bootsector web page fix has been
@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 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,
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
@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
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
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
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
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.
** 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
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
@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
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
1 - 100 of 247 matches
Mail list logo
