No I haven't seen this again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980338
Title:
gcompris crashed with SIGABRT in mem_error()
To manage notifications about this bug go to:
** Branch linked: lp:~noorez-kassam/ubuntu/utopic/initramfs-tools/fix-
for-1317437
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317437
Title:
wubi kernel option rw required
To manage
Same thing happened to me. I just did a test 14.04 install on the same
computer so it's not a local issue.
The Fdisk output is odd - looks like it's trying to partition the 6GB
root.disk so that it has an efi partition:
Disk /dev/loop0: 1.1 GiB, 1162936320 bytes, 2271360 sectors
Units: sectors
** Attachment added: /var/log/installer/debug
https://bugs.launchpad.net/wubi/+bug/1385930/+attachment/4249641/+files/debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1385930
Title:
14.10
This historically happened with the ubuntu installer (ubiquity) if parted
returns errors (both normal and wubi installs). Seen it before when there
is leftover GPT data on a MBR formatted disk. Try booting from the USB and
going to a terminal (or hit Ctrl+Alt+F1 during the installation) and run:
** Package changed: ubuntu = wubi
** Changed in: wubi
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1134770
Title:
Wubi fails to detect 12.04.2 and 13.04
I haven't yet been able to duplicate the kernel oops.
I can get the computer to Suspend while Shutting down on the latest
Ubuntu kernel, and I get the same behaviour using the Mainline build,
but so far no kernel oops.
Reproducible:
If I shut the lid immediately after shutting down, it proceeds
: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bcbc 1914 F pulseaudio
Date: Sun Jun 30 21:23:54 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=9b959dc9-7784-4b26-8506-ca98c00a5eb8
InstallationDate
An update on this bug... I have two raring installs. For one of them the
brightness controls work, one doesn't.
The one that doesn't work is a vanilla upgrade to Raring 13.04 from
Quantal 12.10.
The one that works is also an upgrade from 12.10, but there are two major
differences:
1. I
Just noticed my brightness controls are working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1105604
Title:
Brightness control stopped working
To manage notifications about this bug go
Retested this. The problem doesn't occur on 12.10 or 13.04.
It still happens on 12.04.2, which is using with nautilus 3.4.2.
Actually 12.10 is also using nautilus 3.4.2. So maybe this isn't a
nautilus bug after all. In 12.04.2 the window pops up but nothing
changes in the Unity bar.
In 12.10,
Here is another: http://askubuntu.com/questions/269720/cant-start-
windows-after-installing-ubuntu
And another:
http://ubuntuforums.org/showthread.php?t=1769482p=12560337viewfull=1#post12560337
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: grub2 (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079482
Title:
Windows 7 Not Booting after Grub installed to bootsector
To manage
Latest update... the brightness control keys 'work'. The slider moves up
and down, but there is no impact to the actual brightness. I'm
controlling the brightness manually by setting it automatically after
bootup and resume|thaw via scripts.
I'm running raring with the Mir ppa, but I have another
Now on Raring, the backlight is off after resuming from suspend. I have to run
the following (blind type) after resuming each time:
echo 978 | sudo tee /sys/class/backlight/intel_backlight/brightness
Also, the function keys to control the brightness setting still don't
work. They do on Quantal.
Here is the syslog during the suspend/wake. This maybe a separate bug...
but will move later if nec:
Mar 8 18:49:30 malraux kernel: [ 593.626366] composite sync not supported
Mar 8 18:49:31 malraux kernel: [ 593.787884] composite sync not supported
Mar 8 18:49:31 malraux
PS here is another one: http://askubuntu.com/questions/263606/windows-8
-no-longer-boots-after-grub-wiped-out-the-windows-bootsector
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079482
Title:
Phillip Susi,
There seem to many a number of issues here, but the fact is that Grub
installed itself over the windows boot sector, not the MBR. Wiping out
the partition boot sector prevents Windows from booting, whereas
replacing the bootloader in the MBR is normal (obviously). The bug I
reported
Public bug reported:
Just ran latest raring updates. Screen on full brightness, Fn keys
didn't move the slider. Going to the Brightness settings I can move the
slider but it has no effect.
Setting it manually still works: echo 978
/sys/class/backlight/intel_backlight/brightness
ProblemType:
Grub2 was fixed to prevent offering to install on any windows partition. This
seems to be a regression if it's offering Windows partitions now. I've noticed
a couple of similar cases on askubuntu.com:
http://askubuntu.com/questions/230775/problem-with-dual-boot-windows-xp-ubuntu-12-04
Here's the bug I was referring to: bug 576724
This is a comment from that bug:
This bug was fixed in the package grub2 - 1.98+20100614-2ubuntu4
---
grub2 (1.98+20100614-2ubuntu4) maverick; urgency=low
* Rearrange postinst install_devices logic so that preparatory code is run
This has been happening to me for a couple of weeks. Raring is unusable
with continual crashes. If there's any info I can contribute, please let
me know. I'm running a Dell Inspiron N4010 with an Intel Arrandale gpu.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I downgraded to confirm the old version was working (it was). Upgraded
again and this time the Fn keys weren't working, but the brightness
slider was present. There is also so much general instability (multiple
crash reports and lockups) I couldn't confirm that the problem is
related to g-s-d.
--
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.
The same thing happened during
** Package changed: ubuntu = ubuntustudio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070682
Title:
wubi and ubuntu studio
To manage notifications about this bug go to:
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.
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
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 still fail to see why this is a bug in wubi or ntfs-3g. The way I see it is
that Windows8 chooses to hibernate by default on shutdown (unless fast-start is
disabled), without the knowledge of the user. The fact that the user is unaware
of it, doesn't change the fact that it's hibernated. So
Okay, I hadn't noticed (or heard about) the bit about 'hybrid sleep'.
I switched it on, used the sleep, and then woke up from the sweep.
Then I hit Restart and tried to boot into Wubi, but it didn't work. I can't
mount the windows partition except in read-only mode.
bcbc@neptune:~$ head -c 30
For a Windows 8 shutdown and booting (non-wubi) Ubuntu, I get:
bcbc@neptune:~$ head -c 30 '/mnt/$LogFile' | tail -c 4 | od -t x1
000 00 00 02 00
004
But it won't mount it, except read-only so, in that sense, it's safe.
But it would be a pain for a user trying to boot from an Ubuntu USB
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
it just boots straight into Windows)
It's different when I shut down Windows 8 and then boot the non-Wubi install
(12.04.1). Then when I try to mount the windows partition I get:
bcbc@neptune:~$ sudo mount /dev/sda1 /mnt
Windows is hibernated, refused to mount.
Failed to mount '/dev/sda1
*** This bug is a duplicate of bug 1009247 ***
https://bugs.launchpad.net/bugs/1009247
** This bug has been marked a duplicate of bug 1009247
Windows installer (wubi.exe) download link doesn't work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Elijah, open a new issue or look for an existing issue e.g. I think bug
776590 covers this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/947748
Title:
Brightness control not working after
Bug 541595 is marked as 'fix released'. So it's no longer active. Also,
that bug was to do with an incorrect report that a package was already
installed. The other bug 996379 is marked as invalid.
This bug is to do with update-manager checking the space required for
the release-upgrade
I think this is a Unity action, not Nautilus
** Package changed: nautilus (Ubuntu) = unity
** Summary changed:
- Unable to open a folder for 10 GB Filesystem, No application is registered
as handling this file... Nautilus pops browser on bash partition mount
+ Unable to open a folder for 10 GB
** Summary changed:
- Nautilus pops browser on bash partition mount
+ Unable to open a folder for 10 GB Filesystem, No application is registered
as handling this file... Nautilus pops browser on bash partition mount
** Description changed:
I first noticed this behaviour in Ubuntu 11.10. When
Public bug reported:
I first noticed this behaviour in Ubuntu 11.10. When I run my bash
script that mounts partitions on my hard drive (e.g /dev/sda5), Nautilus
pops up with a browser window. This is an illogical action, since I've
not 'inserted a drive', it's already there, and it's just been
Public bug reported:
I ran an upgrade from 11.10 to 12.04 with 1.9GB free space. No warning
was given about insufficient free space. I received two popup windows
during the upgrade informing me that I was low on space and this went
down to less than 100MB (as I manually freed up space).
The
** Attachment added: dist-upgrade.zip
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/986272/+attachment/3096685/+files/dist-upgrade.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
2012-04-18 22:18:42,171 DEBUG Free space on /: 1856667648
2012-04-18 22:18:45,900 DEBUG dir '/var/cache/apt/archives' needs '987733436'
of 'DistUpgradeCache.FreeSpace object at 0xae731cc' (1856667648.00)
2012-04-18 22:18:45,901 DEBUG dir '/usr' needs '211730432' of
Public bug reported:
I ran a wubi upgrade from 10.04.4 to 12.04. I created a separate bug
report for the upgrade in bug 984593. I guess some of the errors I saw
are reporting themselves ;) so I'll pass them on
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: memtest86+ 4.20-1.1ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984598
Title:
package memtest86+ 4.20-1.1ubuntu1 failed to install/upgrade:
ErrorMessage: subprocess installed post-installation script returned
Public bug reported:
Upgraded a wubi install from 10.04.4 to 12.04. I reported the errors
(and attached logs) in bug 984593. This is one of those errors that is
self-reporting.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: friendly-recovery 0.2.25
ProcVersionSignature: Ubuntu
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bcbc 1752 F pulseaudio
Card0.Amixer.info:
Card
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984601
Title:
package friendly-recovery 0.2.25 failed to install/upgrade:
ErrorMessage: subprocess installed post-installation script returned
error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984599
Title:
package linux-image-3.2.0-23-generic 3.2.0-23.36 failed to
install/upgrade: ErrorMessage: subprocess installed post-installation
*** This bug is a duplicate of bug 984474 ***
https://bugs.launchpad.net/bugs/984474
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984602
Title:
initctl
Joseph Salisbury,
The bug is about an error I received during the upgrade from 10.04.4 to 12.04.
As I said in the description, the error was likely false, since the upgrade
worked (and the kernel booted fine). I was testing the Upgrade process at the
time (it's a throwaway install). So I'm not
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980338
Title:
gcompris crashed with SIGABRT in mem_error()
To manage notifications about this bug go to:
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
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.
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
*** 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
** 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
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
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
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 {
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
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
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:
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
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
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,
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.
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
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
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:
/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
@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
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
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
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
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
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,
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
@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
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,
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
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
1 - 100 of 247 matches
Mail list logo
