[Bug 740382] Re: gtk-logout-helper crashed with SIGABRT in __libc_start_main()
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/740382 Title: gtk-logout-helper crashed with SIGABRT in __libc_start_main() To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/740382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 910183] Re: Ubuntu 12.04 System Settings indicator menu does not show hibernate option but pm-hibernate works correctly
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 Settings indicator menu does not show hibernate option but pm-hibernate works correctly To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/910183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365881] Re: wubi installer's pyrun.exe says no disk
** 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/365881 Title: wubi installer's pyrun.exe says no disk To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/365881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 405175] Re: wubi installer won't work on Vista Home Basic
*** 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/405175 Title: wubi installer won't work on Vista Home Basic To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/405175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
@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 from the latest Oneiric wubi.exe and removed wubildr - now it goes past my ext4 partition and reports cannot find grldr on all devices. Press CTRL-ALT-DELETE to restart. So it looks like your fix is working great. I'll do more tests when alpha 2 comes out as well. -- 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 partition other than Windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/610898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 947748] [NEW] Brightness control not working after latest update
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 the difference before and after the update. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94-0ubuntu1 Architecture: amd64 CheckboxSubmission: dd7f729683fa7fd3f2e256ba311e86cb CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Mon Mar 5 21:36:12 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111006) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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 latest update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/947748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 947748] Re: Brightness control not working after latest update
** 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. https://bugs.launchpad.net/bugs/947748 Title: Brightness control not working after latest update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/947748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 947748] Re: Brightness control not working after latest update
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/947748 Title: Brightness control not working after latest update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/947748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 888281] Re: Boot from FAT32 error and return to grub menu
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 /target/usr/share/grub/grub_mkconfig_lib (/target/usr is the mount point for /dev/loop4 which is for the usr.disk virtual disk). And root.disk was mounted as /dev/loop2 on /target. The grub.cfg that was generated during the install is attached, and it shows that usr.disk will be mounted on loop4 by grub and root.disk is mounted as loop2: insmod part_msdos insmod fat set root='(hd1,msdos5)' search --no-floppy --fs-uuid --set=root 2dab-fe25 loopback loop4 /ubuntu/disks/usr.disk set root=(loop4) if loadfont /share/grub/unicode.pf2 ; then set gfxmode=auto load_video insmod gfxterm insmod part_msdos insmod fat set root='(hd1,msdos5)' search --no-floppy --fs-uuid --set=root 2dab-fe25 loopback loop2 /ubuntu/disks/root.disk set root=(loop2) set locale_dir=($root)/boot/grub/locale set lang=en_US insmod gettext fi ... After rebooting and selecting the Wubi install, there was no error or return to the menu. Then running sudo update-grub resulted in grub.cfg changing the loop device for usr.disk to loop1 and root.disk to loop0 (as expected): insmod part_msdos insmod fat set root='(hd1,msdos5)' search --no-floppy --fs-uuid --set=root 2dab-fe25 loopback loop1 /ubuntu/disks/usr.disk set root=(loop1) if loadfont /share/grub/unicode.pf2 ; then set gfxmode=auto load_video insmod gfxterm insmod part_msdos insmod fat set root='(hd1,msdos5)' search --no-floppy --fs-uuid --set=root 2dab-fe25 loopback loop0 /ubuntu/disks/root.disk set root=(loop0) set locale_dir=($root)/boot/grub/locale set lang=en_US insmod gettext fi ** Attachment added: Grub generated during the installation (ubiquity) https://bugs.launchpad.net/wubi/+bug/888281/+attachment/2832360/+files/grub.cfg.at.install -- 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 return to grub menu To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/888281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 888281] Re: Boot from FAT32 error and return to grub menu
** 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. https://bugs.launchpad.net/bugs/888281 Title: Boot from FAT32 error and return to grub menu To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/888281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 888281] Re: Boot from FAT32 error and return to grub menu
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 return to grub menu To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/888281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 916209] [NEW] Recovery mode incorrect on wubi installs
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 {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos8)'
search --no-floppy --fs-uuid --set=root
02d7ccaf-7f53-4364-9ffa-2cb288f1b124
echo 'Loading Linux 3.2.0-1-generic ...'
linux /vmlinuz-3.2.0-1-generic
root=UUID=ba591735-99eb-40da-9160-6778fe07860b ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.2.0-1-generic
}
And this is the Wubi one:
menuentry 'Ubuntu, with Linux 3.2.0-1-generic (recovery mode)' --class
ubuntu --class gnu-linux --class gnu --class os {
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ntfs
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set=root 18B4B7BBB4B799A8
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
echo 'Loading Linux 3.2.0-1-generic ...'
linux /boot/vmlinuz-3.2.0-1-generic root=UUID=18B4B7BBB4B799A8
loop=/ubuntu/disks/root.disk ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-1-generic
}
Anyway... I was trying to boot the wubi recovery and it just kept getting
stuck, displaying only Loading initial ramdisk Nothing i did made a
change except when I hit ESC it continued to the lightdm logon. And after
removing set gfxpayload=$linux_gfx_mode it booted correctly into the
Read-only recovery menu (which it does on the normal install).
Looking at the scripts, 10_linux has:
if ! ${recovery} ; then
save_default_entry | sed -e s/^/\t/
cat EOF
set gfxpayload=\$linux_gfx_mode
EOF
fi
whereas 10_lupin has:
if ! ${recovery} ; then
save_default_entry | sed -e s/^/\t/
fi
cat EOF
set gfxpayload=\$linux_gfx_mode
EOF
Thanks
** Affects: lupin (Ubuntu)
Importance: Undecided
Status: New
** Tags: oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/916209
Title:
Recovery mode incorrect on wubi installs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/916209/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 918401] Re: Unity-greeter installed by default on Lubuntu, crashing on start
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/918401 Title: Unity-greeter installed by default on Lubuntu, crashing on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/918401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 365881] Re: wubi installer's pyrun.exe says no disk
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 that it can't write to drive E:. Drive E isn't mounted, so I assume it's trying to write to the SDCARD drive which it thinks is there. I've attached the install log, hope it helps a little. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/365881 Title: wubi installer's pyrun.exe says no disk To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/365881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 830851] [NEW] Cannot see window header (no minimize, maximize etc)
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: New ** Tags: compiz-testing-0.9.5.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/830851 Title: Cannot see window header (no minimize, maximize etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/830851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 830851] Re: Cannot see window header (no minimize, maximize etc)
** 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. https://bugs.launchpad.net/bugs/830851 Title: Cannot see window header (no minimize, maximize etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/830851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 762833] Re: Incorrect version of wubi.exe on http://www.ubuntu.com/desktop/get-ubuntu/windows-installer
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 downloading the desktop CD ISO and burning it to CD - in this case the wubi.exe always matches the release you downloaded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/762833 Title: Incorrect version of wubi.exe on http://www.ubuntu.com/desktop/get- ubuntu/windows-installer -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 653478] Re: 10.10 RC wubi install fails on Windows XP SP3
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 758411] Re: Upgrade from 10.10 to Natty results in system freeze
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 the daily alternate CD (checking online as well for later updates) For this test: (a) I did a fresh install, (b) ran all available 10.10 updates, and (c) ran the update using the update manager. I've been meaning to rerun the upgrade to see if I can duplicate it, but haven't yet had the time. Will do it again soon and post back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/758411 Title: Upgrade from 10.10 to Natty results in system freeze -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 758411] Re: Upgrade from 10.10 to Natty results in system freeze
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/758411 Title: Upgrade from 10.10 to Natty results in system freeze -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 762833] Re: Incorrect version of wubi.exe on http://www.ubuntu.com/desktop/get-ubuntu/windows-installer
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 ( http://www.ubuntu.com/desktop/get-ubuntu/windows-installer ) was set at Maverick Meerkat 10.10 up until late last week. This was changed without notice (and nowhere on the page does it state the release that will be downloaded.) Since that time, everyone running it will find it downloads the 10.04.2 Desktop ISO (700MB download) and then rejects it with: 10.04.2 != 10.04.1 We've been seeing a number of these on ubuntuforums.org already. It is quite urgent (and a simple fix) to: 1) replace it with a working version for either 10.04.2 or 10.10 2) state on the page which release it is so users know what they are installing On Tue, Apr 19, 2011 at 8:07 AM, Ellen Arnold 762...@bugs.launchpad.netwrote: Is it okay to close this bug now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/762833 Title: Incorrect version of wubi.exe on http://www.ubuntu.com/desktop/get- ubuntu/windows-installer -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 568611] Re: Screen brightness control fails on Dell Studio 1558
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 dell_backlight intel_backlight bcbc@ubuntu:~$ The only thing is that when the function keys are pressed, the popup display show a computer with a solid bar underneath that doesn't change, however, if I go to System settings, Screen, the slider works appropriately. As far as I am concerned, this is working great. Thank you for your effort to get this fixed and also providing the ppa's. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/568611 Title: Screen brightness control fails on Dell Studio 1558 To manage notifications about this bug go to: https://bugs.launchpad.net/null/+bug/568611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 894617] [NEW] package libqt4-declarative 4:4.7.4-1ubuntu4 failed to install/upgrade: './usr/share/doc/libqt4-declarative/LGPL_EXCEPTION.txt' is different from the same file on the system
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 same file on the system './usr/share/doc/libqt4-xmlpatterns/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-network/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-xmlpatterns/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-network/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqtgui4/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-xmlpatterns/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-network/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqtgui4/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-xmlpatterns/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-network/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-xmlpatterns/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-network/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-declarative/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-xmlpatterns/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-network/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-declarative/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-xmlpatterns/LGPL_EXCEPTION.txt' is different from the same file on the system './usr/share/doc/libqt4-network/LGPL_EXCEPTION.txt' is different from the same file on the system ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libqt4-declarative 4:4.7.4-1ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-1.3-generic 3.2.0-rc2 Uname: Linux 3.2.0-1-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Nov 24 10:04:49 2011 DuplicateSignature: Unpacking replacement libqt4-declarative ... dpkg: error processing /var/cache/apt/archives/libqt4-declarative_4%3a4.7.4-1ubuntu4_amd64.deb (--unpack): './usr/share/doc/libqt4-declarative/LGPL_EXCEPTION.txt' is different from the same file on the system ErrorMessage: './usr/share/doc/libqt4-declarative/LGPL_EXCEPTION.txt' is different from the same file on the system InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111006) SourcePackage: qt4-x11 Title: package libqt4-declarative 4:4.7.4-1ubuntu4 failed to install/upgrade: './usr/share/doc/libqt4-declarative/LGPL_EXCEPTION.txt' is different from the same file on the system UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- 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 different from the same file on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/894617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 894617] Re: package libqt4-declarative 4:4.7.4-1ubuntu4 failed to install/upgrade: './usr/share/doc/libqt4-declarative/LGPL_EXCEPTION.txt' is different from the same file on the system
-- 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 different from the same file on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/894617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 896933] [NEW] software center crashed - won't allow me to report - says glib-networking not latest
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 ia32-libs-multiarch:i386 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. What I was trying to do - remove an old kernel. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: software-center 5.1.2.1 ProcVersionSignature: Ubuntu 3.2.0-1.3-generic 3.2.0-rc2 Uname: Linux 3.2.0-1-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 CheckboxSubmission: dd7f729683fa7fd3f2e256ba311e86cb CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Sun Nov 27 10:07:27 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111006) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- 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: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/896933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 896933] Re: software center crashed - won't allow me to report - says glib-networking not latest
-- 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: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/896933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 889650] Re: 11.10 wubi - recovery mode incorrect
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 gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos8)'
search --no-floppy --fs-uuid --set=root
02d7ccaf-7f53-4364-9ffa-2cb288f1b124
echo'Loading Linux 3.2.0-1-generic ...'
linux /vmlinuz-3.2.0-1-generic
root=UUID=ba591735-99eb-40da-9160-6778fe07860b ro recovery nomodeset
echo'Loading initial ramdisk ...'
initrd /initrd.img-3.2.0-1-generic
}
And this is the Wubi one:
menuentry 'Ubuntu, with Linux 3.2.0-1-generic (recovery mode)' --class
ubuntu --class gnu-linux --class gnu --class os {
set gfxpayload=$linux_gfx_mode
insmod part_msdos
insmod ntfs
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set=root 18B4B7BBB4B799A8
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
echo'Loading Linux 3.2.0-1-generic ...'
linux /boot/vmlinuz-3.2.0-1-generic root=UUID=18B4B7BBB4B799A8
loop=/ubuntu/disks/root.disk ro recovery nomodeset
echo'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-1-generic
}
Anyway... I was trying to boot the wubi recovery and it just kept getting
stuck, displaying only Loading initial ramdisk Nothing i did made a
change except when I hit ESC it continued to the lightdm logon. And after
removing set gfxpayload=$linux_gfx_mode it booted correctly into the
Read-only recovery menu (which it does on the normal install).
Looking at the scripts, 10_linux has:
if ! ${recovery} ; then
save_default_entry | sed -e s/^/\t/
cat EOF
set gfxpayload=\$linux_gfx_mode
EOF
fi
whereas 10_lupin has:
if ! ${recovery} ; then
save_default_entry | sed -e s/^/\t/
fi
cat EOF
set gfxpayload=\$linux_gfx_mode
EOF
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/889650
Title:
11.10 wubi - recovery mode incorrect
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/889650/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 613288] Re: wubi installation failed - boot configuration store could not be opened
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 system cannot find the file specified.” Look for the following registry key HKEY_LOCAL_MACHINE\BCD If we check under HKLM you will not find the key BCD Cause If some 3rd party storage Disk or Storage Management software is installed it may bring all the volume without drive letter offline Generally 100 MB partition is system partition which contains Boot configuration Database and does not have a drive letter assigned. Solution From adminstrator command prompt: C:\Diskpart C:\Diskpart List volume C:\Diskpart Select volume 1 (Considering this is 100 MB system partition) C:\Diskpart Online volume C:\Diskpart exit This has been confirmed to work here http://ubuntuforums.org/showthread.php?t=1871823 Note the Microsoft solution also mentions the solution Jason Tucker provided in #27 - but I think it's probably better not to have to assign a drive letter to the system boot partition. I don't think therefore this is caused by Wubi/Ubuntu -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ubiquity in Ubuntu. https://bugs.launchpad.net/bugs/613288 Title: wubi installation failed - boot configuration store could not be opened To manage notifications about this bug go to: https://bugs.launchpad.net/ubiquity/+bug/613288/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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, and update grub-pc through synaptic (not running other updates) Expected result: === 1. wubildr on /dev/sda2 will be updated (that's C:) 2. grub modules added to /boot/grub 3. /boot/grub/grub.cfg changes as expected with new modules present. 4. No prompt to install grub to /dev/sda Results: = 1. wubildr on /dev/sda2 not updated 2. grub modules not added to /boot/grub 3. /boot/grub/grub.cfg not changed 4. There was no prompt to install grub to /dev/sda (grub is now version 1.98-1ubuntu12) Conclusion: This will stop this bug (installing grub to drive MBR). But I expected wubildr to be updated. Maybe my expectation is incorrect, but there is still a distinct difference between wubi installed to the same partition as windows (/host/wubildr exists), and when it doesn't. -- 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 partition other than Windows -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 734595] Re: Launcher should be clickable when mouse over menu button
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 in itself is buggy. if you enter a random string it doesn't show anything, and the only way to get out is to click on the top panel bar. Even click on popup messages is ignored while the run app window sits there hidden. ** Attachment added: Screenshot-3.png https://bugs.launchpad.net/ubuntu/+source/unity/+bug/734595/+attachment/2011391/+files/Screenshot-3.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 Title: Launcher should be clickable when mouse over menu button -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 734595] Re: Launcher should be clickable when mouse over menu button
** 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 Title: Launcher should be clickable when mouse over menu button -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 756802] [NEW] Activation region for overlay scrollbar difficult to find
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 orange' part and get your mouse all the way over to that. See attached screenshot: the orange part is on the bottom right. Another irritation is that when the scroll-bar activation part appears, it isn't always under the mouse, so you have to move your mouse to the orange to get the scrollbar, then move it again before clicking on it. It should always appear right under the mouse. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: overlay-scrollbar 0.1.6-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Sun Apr 10 12:18:26 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110326) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: overlay-scrollbar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: overlay-scrollbar (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty running-unity -- 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 region for overlay scrollbar difficult to find -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 756802] Re: Activation region for overlay scrollbar difficult to find
** 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 region for overlay scrollbar difficult to find -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 756802] Re: Activation region for overlay scrollbar difficult to find
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 combine. I just tested it on gedit and it has the same characteristics: you cannot page up/down; the only option is to mouse over to the orange part, and then after the slider appears, mouse a little over to it before selecting. -- 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 region for overlay scrollbar difficult to find -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 762833] Re: wubi fails to install all the files properly.
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 the release of 10.04.2 (there is a separate bug 722955 that the wubi.exe on http://releases.ubuntu.com/lucid/ is the incorrect version). ** Changed in: ubuntu Status: Incomplete = Confirmed ** Also affects: ubuntu-website-content Importance: Undecided Status: New ** Changed in: ubuntu-website-content Status: New = Confirmed ** Also affects: wubi Importance: Undecided Status: New ** Changed in: ubuntu Status: Confirmed = Invalid ** Changed in: wubi Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/762833 Title: wubi fails to install all the files properly. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 762833] Re: Incorrect version of wubi.exe on http://www.ubuntu.com/desktop/get-ubuntu/windows-installer
** 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. https://bugs.launchpad.net/bugs/762833 Title: Incorrect version of wubi.exe on http://www.ubuntu.com/desktop/get- ubuntu/windows-installer -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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 grub-pc --- install-devices: blank Test method: Add Proposed to sources,through synaptic (not running other updates) Latest version of grub-pc shown as 1.98-1ubuntu12 Latest version of lupin-support is 0.29.1 Select grub-pc (which includes) grub-common and lupin-support and applied updates. Expected result: === 1. wubildr on /dev/sda2 will be updated (that's C:) 2. grub modules added to /boot/grub 3. /boot/grub/grub.cfg changes as expected with new modules present. 4. No prompt to install grub to /dev/sda Results: = 1. wubildr on /dev/sda2 updated to 1.98-1ubuntu12 2. grub modules added to /boot/grub as expected 3. /boot/grub/grub.cfg changed as expected 4. There was no prompt to install grub to /dev/sda (grub is now version 1.98-1ubuntu12) Conclusion: The test was successful. PS I will try and run the maverick failed test case next. The same partition tests will be run last, probably later this evening (pacific time). -- 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 partition other than Windows -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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 to mention this) -- Repeat of testcase 1 follows... Testcase 1: Maverick 10.10 on E: drive (ntfs partition /dev/sda3) = Grub version in wubildr at install 1.98+20100804-5ubuntu2 Grub version in Ubuntu at install 1.98+20100804-5ubuntu3 Lupin-support version is 0.32 debconf-show grub-pc --- install-devices: blank Only grub.cfg and grubenv in /boot/grub No wubildr on /host Test method: Add Proposed to sources,through synaptic (not running other updates) Latest available version of grub-pc shown as 1.98+20100804-5ubuntu3.3 Latest available version of lupin-support is 0.32.1 Select grub-pc (which includes grub-common) and lupin-support and applied updates. Expected result: === 1. wubildr on /dev/sda2 will be updated (that's on C:) 2. grub modules added to /boot/grub 3. /boot/grub/grub.cfg changed as expected with new modules present. 4. No prompt to install grub to /dev/sda Results: = 1. wubildr on /dev/sda2 updated to 1.98+20100804-5ubuntu3.3 and no /host/wubildr (expected) 2. grub modules added to /boot/grub as expected 3. /boot/grub/grub.cfg changed as expected 4. There was no prompt to install grub to /dev/sda (grub is now version 1.98+20100804-5ubuntu3.3 on Ubuntu) 5. debconf-show grub-pc install-devices: /dev/loop0 6. Rebooting into Ubuntu worked Conclusion: The test was successful. PS as mentioned before - the same partition tests will be done later this evening. They probably aren't as critical since they worked before the lupin update anyway. But I'll do them to make sure there's no regression. -- 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 partition other than Windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/610898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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 lupin-support deliver identical results regardless of where wubi is installed. I'll probably do one more test with Wubi installed on an external drive. But as far as I can see - this is working exactly as intended. Good job! -- 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 partition other than Windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/610898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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 partition other than Windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/610898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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 grub-install? -- 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 partition other than Windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/610898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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 version of grub-pc. That's good. -- 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 partition other than Windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/610898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 742967] Re: Natty Wubi grub prompt on install
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: Incidentally, my note in comment 11 that 10.04 doesn't have this bug was in error. It's just that in that version the problematic code was in an Ubuntu-specific patch rather than upstream ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742967 Title: Wubi grub prompt on install -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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). This is not likely a problem for typical Wubi users but people that test Wubi will run into this. You mentioned replacing grub4dos on another bug - this would resolve that. Regarding hibernation - if Windows is hibernated it's not possible to boot Wubi (the windows boot manager boots straight into windows) so that shouldn't be an issue except perhaps if there are multiple versions of Windows (not sure how that would work). -- 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 partition other than Windows -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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 an external or logical drive it increases the likelihood that an ext4 could be encountered. I think a version of grub4dos that is later than the one wubi users (2007?) should be able to read ext4 fine. On Wed, Apr 6, 2011 at 1:13 AM, Colin Watson cjwat...@canonical.com wrote: ext4: Thanks. I'll see if I can add this to my tests. Is it only ext4, or ext3 as well? And does anyone actually care about wubildr.mbr being able to read data from an ext[234] filesystem? I suspect that the easiest fix may be to disable ext[234] support in wubildr.mbr altogether. (While I do want to replace grub4dos with grub2 ntldr-img, this is too invasive for a change to lucid/maverick, so I'll need to figure out a small patch to grub4dos for this anyway.) -- 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 partition other than Windows -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742967] Re: Wubi grub prompt on install
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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742967 Title: Wubi grub prompt on install -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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 where to install Grub and gave me two choices: /dev/sda (checkbox not selected) and /dev/loop0 (checkbox selected). I left /dev/loop0 selected and proceeded. Reboot worked successfully. This may not be a great test case as that Natty was a bit beaten. I'm going to run a maverick to natty upgrade test on the non-windows partition soon and I'll report back on what I find. I'll confirm whether the /dev/sda prompt is given on upgrade. But in terms of the wubildr update on the different partition - it worked perfectly!. -- 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 partition other than Windows -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742967] Re: Wubi grub prompt on install
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. https://bugs.launchpad.net/bugs/742967 Title: Wubi grub prompt on install -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
Did a fresh maverick install and then upgrade to Natty on a non-Windows partition. No prompt on where to install grub, and it updated wubildr correctly. After booting into Natty I could run grub-install and it correctly updated wubildr on the windows partition without any prompts and did not allow 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:~$ mount | grep /dev/sda2 bcbc@ubuntu:~$ sudo mount /dev/sda2 /mnt bcbc@ubuntu:~$ ls -l /mnt/wubildr -rwxrwxrwx 1 root root 148091 2011-04-06 22:43 /mnt/wubildr bcbc@ubuntu:~$ date Wed Apr 6 22:43:33 PDT 2011 bcbc@ubuntu:~$ sudo grub-install /dev/sda Installation finished. No error reported. bcbc@ubuntu:~$ ls -l /mnt/wubildr -rwxrwxrwx 1 root root 148092 2011-04-06 22:44 /mnt/wubildr bcbc@ubuntu:~$ sudo debconf-show grub-pc [sudo] password for bcbc: grub-pc/kopt_extracted: false grub2/kfreebsd_cmdline: grub2/device_map_regenerated: * grub-pc/install_devices: /dev/loop0 grub-pc/postrm_purge_boot_grub: false grub-pc/install_devices_failed_upgrade: true grub-pc/disk_description: * grub2/linux_cmdline: grub-pc/install_devices_empty: false grub2/kfreebsd_cmdline_default: quiet grub-pc/partition_description: grub-pc/install_devices_failed: false grub-pc/install_devices_disks_changed: * grub2/linux_cmdline_default: quiet splash grub-pc/chainload_from_menu.lst: true grub-pc/hidden_timeout: true grub-pc/mixed_legacy_and_grub2: true grub-pc/timeout: 10 -- 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 partition other than Windows -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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 in the list, so I'll note that (although I suspect it will be unnecessary to ever do this if everything is working as it should). In terms of there being another grub update on Maverick prior to providing this fix - that will likely cause problems. If at all possible they should be combined as any grub update will break a Wubi install (so far Maverick has remained safe excluding the upgrade from Lucid). Anyway - I'm happy to see the fix come out. Thanks for the effort. On Thu, Apr 7, 2011 at 4:26 AM, Colin Watson cjwat...@canonical.com wrote: Thanks for testing. I'm glad to hear confirmation that this saga may finally be nearing its end. For the record, I wouldn't recommend propagating the idea that 'sudo grub-install /dev/sda2' is a good thing to run on Wubi. The correct command is: sudo grub-install /dev/loop0 As it happens, it makes no difference right now, because lupin-support overrides everything with a large hammer so that it makes absolutely no difference what device you tell grub-install to use - /dev/loop0, /dev/sda2, /dev/sda, etc. will all behave the same way. In the future, though, we may change this, so please don't assume that anything other than /dev/loop0 will work. -- -- 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 partition other than Windows -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738274] Re: wubi sets wrong locale
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 location is Vancouver. So in my case, it seems to have ignored the UTC instruction, and translated the computer clock from UTC to Vancouver time. Yet the /var/log/installer/debug seems to show that it is set to UTC false: Mar 19 15:13:27 debconf (filter): -- GET clock-setup/utc debconf (developer): -- GET clock-setup/utc debconf (developer): -- 1 false -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/738274 Title: wubi sets wrong locale -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738345] Re: Grub2 entries to boot Wubi incorrect... Error: file not found, Press any key to continue at boot
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 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778735] Re: Cannot install using Wubi on Intel RST RAID
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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778735 Title: Cannot install using Wubi on Intel RST RAID -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742967] Re: Natty Wubi grub prompt on install
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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742967 Title: Natty Wubi grub prompt on install -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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. /wubildr on C: 'drive' (/dev/sda2) would be updated 2. No prompt to suggest installing grub2 bootloader to /dev/sda 3. New grub modules placed in /boot/grub 4. Different grub.cfg Results == 1. /wubildr on C: 'drive' was not updated. Remains at version 1.98+20100804-5ubuntu2 Grub2 version (grub-install -v) shows 1.98+20100804-5ubuntu3.3 debconf-show grub-pc shows grub-install devices are blank. 2. There was no prompt to suggest installing grub2 bootloader on /dev/sda2 3. No additional files in /boot/grub 4. No difference in grub.cfg (except the addition of the new kernel in proposed) Comments: a. Positive that there is no prompt that user could select to install grub bootloader to drive MBR b. OK that wubildr isn't updated, because the grub.cfg also doesn't contain the instructions that cause the loopback memory corruption. c. But result not quite as expected (or is my understanding incorrect?) -- 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 partition other than Windows -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 762833] Re: http://www.ubuntu.com/desktop/get-ubuntu/windows-installer offers lucid wubi.exe and claims it's the most recent version
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 39F805CAE8BE546747C492935CE0FCDD so that matches what you have. On Thu, Apr 28, 2011 at 11:18 AM, jweaver28 762...@bugs.launchpad.netwrote: It's afternoon on 4/28 in the US and though I downloaded wubi.exe, I can't find an authenticated md5 hash. My amd64 version of Natty, though, checksummed just fine. FYI, googling wubi.exe and checksum brought links to a few bug reports like this, but googling the hash I made today, 39f805cae8be546747c492935ce0fcdd produced nothing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/762833 Title: http://www.ubuntu.com/desktop/get-ubuntu/windows-installer offers lucid wubi.exe and claims it's the most recent version -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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 couldn't get a bunch of new ones). Added Proposed to the sources. Updated grub-pc and grub-common in Synaptic. Expected result === 1. /wubildr on C: 'drive' (/dev/sda2) would be updated 2. New grub modules placed in /boot/grub 3. Different grub.cfg Results == 1. /wubildr on C: 'drive' was updated. debconf-show grub-pc now shows grub-install devices: /dev/loop0 There was no prompt to suggest installing grub2 bootloader (as expected) 3. All grub modules added to /boot/grub 4. grub.cfg was different (matching normal install) Comments: This shows a big difference between Wubi installed on the Windows partition (/host/wubildr exists) and wubi installed on the non-windows partition (no /host/wubildr). -- 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 partition other than Windows -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259540] Re: Wubi - No root file system is defined Error
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 data. Again, likely Ubiquity problem. You cannot install on Windows 7 dynamic disks - because some of these are not in the partition table at all. Windows 7 actually rejects that within the Wubi install (Windows part) when you try and add a boot manager entry to BCD that refers to a dynamic disk. I believe it should work on any partition that is in the MBR (e.g. the partition for C:), but I would think it's dangerous to have C: mounted as a single partition in Ubuntu, whereas in Windows it's actually a number of separate dynamic partitions. There are probably other causes of this error as well. In general I recommend running the bootinfoscript ( http://bootinfoscript.sourceforge.net/ ) - see what it reports in terms of raid info, and it's fdisk output should show any leftover GPT information causing conflict. But since these errors are being generated out of Ubiquity that's probably the project that needs to included. However since the bug is around since 2008 with no fix - and since there may be many separate problems with the same symptom, it's better to identify what your problem is and then create a new ubiquity bug for it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/259540 Title: Wubi - No root file system is defined Error -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738345] [NEW] Grub2 entries to boot Wubi incorrect... Error: file not found, Press any key to continue at boot
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 23b0f259-6cdd-4cd2-bc50-8febbcb784b0
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.38-7-generic root=UUID=80E4E195E4E18DAA
loop=/ubuntu/disks/root.disk ro quiet splash
initrd /boot/initrd.img-2.6.38-7-generic
}
The UUID 23bf... is the loop device /dev/loop0. The file
/ubuntu/disks/root.disk is not on the loop device, it's on the host
(UUID=80E4...). So to 1) set root to /dev/loop0 which it should be,
override to /dev/loop0 by uuid, and then try to loop mount
/ubuntu/disks/root.disk won't work.
I'm not sure exactly what the cause of the message is - but after selecting to
boot, the next screen you get a blank screen with:
Error: file not found.
Press any key to continue
After pressing a key it then boots normally.
This did not happen on the initial install, so I assume it's changed since
running updates.
I also noticed a flashed 'Error: file not found' just before the grub menu
displays. This also did not happen on the initial install.
Just for reference here is a copy of a Lucid version of a lupin
menuentry for Wubi. Note the differences of insmod ntfs, and setting
root to the partition (not loop device).
On a lucid wubi it looks similar to this:
### BEGIN /etc/grub.d/10_lupin ###
menuentry Ubuntu, Linux 2.6.32-27-generic {
insmod ntfs
set root='(hd0,2)'
search --no-floppy --fs-uuid --set 80E4E195E4E18DAA
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.32-27-generic root=/dev/sda2
loop=/ubuntu/disks/root.disk ro quiet splash
initrd /boot/initrd.img-2.6.32-27-generic
}
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: lupin-support 0.33
ProcVersionSignature: Ubuntu 2.6.38-7.36-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Sat Mar 19 10:52:15 2011
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110314)
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: lupin
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: lupin (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 natty running-unity
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738345] Re: Grub2 entries to boot Wubi incorrect... Error: file not found, Press any key to continue at boot
-- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738345] Re: Grub2 entries to boot Wubi incorrect... Error: file not found, Press any key to continue at boot
** 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 ###
menuentry Ubuntu, Linux 2.6.38-7-generic {
- insmod ext2
- set root='(/dev/loop0)'
- search --no-floppy --fs-uuid --set=root
23b0f259-6cdd-4cd2-bc50-8febbcb784b0
- loopback loop0 /ubuntu/disks/root.disk
- set root=(loop0)
- linux /boot/vmlinuz-2.6.38-7-generic root=UUID=80E4E195E4E18DAA
loop=/ubuntu/disks/root.disk ro quiet splash
- initrd /boot/initrd.img-2.6.38-7-generic
+ insmod ext2
+ set root='(/dev/loop0)'
+ search --no-floppy --fs-uuid --set=root 23b0f259-6cdd-4cd2-bc50-8febbcb784b0
+ loopback loop0 /ubuntu/disks/root.disk
+ set root=(loop0)
+ linux /boot/vmlinuz-2.6.38-7-generic root=UUID=80E4E195E4E18DAA
loop=/ubuntu/disks/root.disk ro quiet splash
+ initrd /boot/initrd.img-2.6.38-7-generic
}
The UUID 23bf... is the loop device /dev/loop0. The file
/ubuntu/disks/root.disk is not on the loop device, it's on the host
(UUID=80E4...). So to 1) set root to /dev/loop0 which it should be,
override to /dev/loop0 by uuid, and then try to loop mount
/ubuntu/disks/root.disk won't work.
+ I'm not sure exactly what the cause of the message is - but after selecting
to boot, the next screen you get a blank screen with:
+ Error: file not found.
+ Press any key to continue
+ After pressing a key it then boots normally.
+
+ This did not happen on the initial install, so I assume it's changed since
running updates.
+ I also noticed a flashed 'Error: file not found' just before the grub menu
displays. This also did not happen on the initial install.
+
+ Just for reference here is a copy of a Lucid version of a lupin
+ menuentry for Wubi. Note the differences of insmod ntfs, and setting
+ root to the partition (not loop device).
+
On a lucid wubi it looks similar to this:
### BEGIN /etc/grub.d/10_lupin ###
menuentry Ubuntu, Linux 2.6.32-27-generic {
- insmod ntfs
- set root='(hd0,1)'
- search --no-floppy --fs-uuid --set 80E4E195E4E18DAA
- loopback loop0 /ubuntu/disks/root.disk
- set root=(loop0)
- linux /boot/vmlinuz-2.6.32-27-generic root=/dev/sda1
loop=/ubuntu/disks/root.disk ro quiet splash
- initrd /boot/initrd.img-2.6.32-27-generic
+ insmod ntfs
+ set root='(hd0,2)'
+ search --no-floppy --fs-uuid --set 80E4E195E4E18DAA
+ loopback loop0 /ubuntu/disks/root.disk
+ set root=(loop0)
+ linux /boot/vmlinuz-2.6.32-27-generic root=/dev/sda2
loop=/ubuntu/disks/root.disk ro quiet splash
+ initrd /boot/initrd.img-2.6.32-27-generic
}
- I'm not sure exactly what the cause of the message is - but after selecting
to boot, the next screen you get a blank screen with:
- Error: file not found.
- Press any key to continue
- After pressing a key it then boots normally.
-
- This did not happen on the initial install, so I assume it's changed
- since running updates.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: lupin-support 0.33
ProcVersionSignature: Ubuntu 2.6.38-7.36-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Sat Mar 19 10:52:15 2011
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110314)
ProcEnviron:
- LANGUAGE=en_US:en
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ LANGUAGE=en_US:en
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
SourcePackage: lupin
UpgradeStatus: No upgrade log present (probably fresh install)
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738361] [NEW] Screen does not reappear 'going to sleep' - just the mouse
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 if I go to the Applications it renders correctly, but if I then click on Show all installed then the screen does not render (blank) but if I move the mouse around the icons appear underneath the mouse and remain once it's gone past. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.6.6-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.36-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480 edid-base64: AP///wAOFKYTABAQAQOAIRV4CoBtmVdPjyYhUFQBAQEBAQEBAQEBAQEBAQEB6hoAgFAgEDAVIBMAS88QAAAZDwAAACBuBQ8A/gBGRDE2MzExNTRXQjQK/gAvQlJagcTq/wEBCiAgAFA= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: Date: Sat Mar 19 11:12:20 2011 DistUpgraded: Fresh install DistroCodename: natty DistroVariant: ubuntu GraphicsCard: ATI Technologies Inc M52 [Mobility Radeon X1300] [1002:7149] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:2003] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110314) InstallationMedia_: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110314) InstallationMedia__: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110314) Lsusb: Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. MM061 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=80E4E195E4E18DAA loop=/hostname/disks/root.disk ro quiet splash ProcVersionSignature_: Ubuntu 2.6.38-7.36-generic 2.6.38 ProcVersionSignature__: Ubuntu 2.6.38-7.36-generic 2.6.38 Renderer: Unknown SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XD720 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: MM061 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.4-0ubuntu7 version.libdrm2: libdrm2 2.4.23-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu11 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 natty running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/738361 Title: Screen does not reappear 'going to sleep' - just the mouse -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738361] Re: Screen does not reappear 'going to sleep' - just the mouse
** 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. https://bugs.launchpad.net/bugs/738361 Title: Screen does not reappear 'going to sleep' - just the mouse -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738274] Re: wubi sets wrong locale
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 America/Vancouver This file is removed after the install, so you would have to reinstall to see it. The question is, is Wubi providing the incorrect instruction to Ubiquity or is Ubiquity failing to set it correctly. ** Attachment added: preseed.cfg https://bugs.launchpad.net/ubuntu/+bug/738274/+attachment/1921666/+files/preseed.cfg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/738274 Title: wubi sets wrong locale -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738274] Re: wubi sets wrong locale
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 https://bugs.launchpad.net/ubuntu/+bug/738274/+attachment/1922130/+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/738274 Title: wubi sets wrong locale -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738274] Re: wubi sets wrong locale
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/738274 Title: wubi sets wrong locale -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738274] Re: wubi sets wrong locale
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 https://bugs.launchpad.net/ubuntu/+bug/738274/+attachment/1922381/+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/738274 Title: wubi sets wrong locale -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738345] Re: Grub2 entries to boot Wubi incorrect... Error: file not found, Press any key to continue at boot
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 --set=root 8654915254914639
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.38-6-generic root=UUID=8654915254914639
loop=/ubuntu/disks/root.disk ro quiet splash
initrd /boot/initrd.img-2.6.38-6-generic
}
Apart from changing the target partition it shows that the grub.cfg changed
after the install - the original entry looks like the traditional wubi entry,
but then running sudo update-grub changes it to this:
### BEGIN /etc/grub.d/10_lupin ###
menuentry Ubuntu, Linux 2.6.38-6-generic {
insmod ext2
set root='(/dev/loop0)'
search --no-floppy --fs-uuid --set=root
b4c80465-f6f6-4e88-a1dc-0321acfe292f
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.38-6-generic root=UUID=8654915254914639
loop=/ubuntu/disks/root.disk ro quiet splash
initrd /boot/initrd.img-2.6.38-6-generic
}
So I don't think this is a lupin script issue, but rather a grub2 issue.
--
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738345] Re: Grub2 entries to boot Wubi incorrect... Error: file not found, Press any key to continue at boot
** 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 any key to continue at boot -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 693671] Re: wubi install will not boot - phase 2 stops with: Try (hd0, 0): NTFS5
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 Grub2 after it's already created. -- 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 693671] Re: wubi install will not boot - phase 2 stops with: Try (hd0, 0): NTFS5
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.) -- 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 713395] Re: Ubiquity tight loop No root file System on Natty Alpha2 Wubi install
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/713395 Title: Ubiquity tight loop No root file System on Natty Alpha2 Wubi install -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 770256] Re: Reboots after Wubi install via ubiquity asks to uninstall
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 afterwards. It should be adding it as a Runonce to the windows registry which is supposed to automatically be removed. ** Also affects: ubiquity Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Changed in: ubiquity Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/770256 Title: Reboots after Wubi install via ubiquity asks to uninstall -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 770256] Re: Reboots after Wubi install via ubiquity repeatedly ask to uninstall
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/770256 Title: Reboots after Wubi install via ubiquity repeatedly ask to uninstall -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 770256] Re: Reboots after Wubi install via ubiquity repeatedly ask to uninstall
@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 Windows install detected, it then offers the option to Install Ubuntu inside Microsoft Windows XP Home Edition. ( http://ubuntuforums.org/attachment.php?attachmentid=189969d=1303732484) 2 When you select this it copies the wubi.exe from the CDROM to the Windows partition and instructs the user to reboot (more or less, the screen is a little confusing: http://ubuntuforums.org/attachment.php?attachmentid=189970d=1303732484 ) 3. The next time the user boots into Windows, it automatically runs wubi.exe. Problems == a. Wubi.exe has been copied into the Common Startup folder so it runs for all users each time you boot into Windows. b. If you choose, not to install Wubi, it will keep prompting you each subsequent time you boot into Windows c. If you choose to install Wubi, it will run again and prompt you to UNINSTALL/Reinstall the next time you boot Windows. This goes on until you physically find and delete the entry. For XP the actual entry is in C:\Documents and Settings\All Users\Start Menu\Programs\Startup\wubi.exe You can either browse to that location to delete it, or run Microsoft's msconfig utility. But in Erick's case he had some permissions issues and it would not let him uninstall (that part I am unclear on the exact reasons). But even if the user can remove this entry easily there are some additional problems: 1. It doesn't inform the user that by inserting the Ubuntu CD in the drive, it will use that image. If the user does not put the CD in, wubi.exe will instead download a new image. (If the user put the CD in while running Windows, it would prompt to install Ubuntu anyway). So in summary: Wubi.exe will run each time the user boots into Window prompting to install Ubuntu each/time or prompting to Uninstall/reinstall Ubuntu (if already installed) until the user physically finds and deletes Wubi.exe. This may result in some confusion. The locations that wubi.exe may be copied to are: For Windows 7 'ProgramData/Microsoft/Windows/Start Menu/Programs/Startup', For Windows XP 'Documents and Settings/All Users/Start Menu/Programs/Startup', For Windows NT 'Winnt/Profiles/All Users/Start Menu/Programs/Startup', A better solution, would be to add wubi.exe to the Windows registry as a RunOnce entry. Then it would only run on the first boot into Windows after the attempted Ubuntu install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/770256 Title: Reboots after Wubi install via ubiquity repeatedly ask to uninstall -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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 update grub-pc through synaptic (not running other updates) Expected result: === 1. wubildr on /host (/dev/sda2) will be updated 2. grub modules added to /boot/grub 3. grub.cfg contains extra code (similar to normal install) Results == 1. wubildr on /host updated 2. grub modules added to /boot/grub 3. grub.cfg contains extra code grub is now 1.98-1ubuntu12 debconf-show grub-pc -- install devices changed to /dev/loop0 Conclusion Results as expected, but there is still a distinct difference between wubi not installed to the same partition as windows. PS Grub menu (from wubildr) now shows 1.98-1ubuntu12 (as expected) NOTE: I don't plan to do any more tests at this point, unless the code changes. Although I expected the code to work more like Natty (updating wubildr no matter which partition it is installed to), on the positive side, it doesn't prompt to install grub to the MBR. And when it does update the grub.cfg to the state that caused the memory corruption on recreating the loopback device, it also updates the wubildr - to prevent the booting problem. Although the same bad wubildr will exist on the non windows partition installs, the bug shouldn't be triggered. However, installs with a bad wubildr where it is still booting (I've seen cases where the corruption only occurs following a subsequent kernel update) might still have problems. Also, it seems that the grub-install-devices is a factor in whether the wubildr is updated on non-windows partition installs, but not on windows partition installs. -- 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 partition other than Windows -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742967] Re: Natty Wubi grub prompt on install
Yes, I imagine it would be a pain. Most 10.04.x wubi users have already locked grub-* packages by now anyway. I've tested the fix and it works... with some caveats because my installs were from a daily-live image with grub prior to version -8ubuntu1. In previous releases, updating grub on Wubi would regenerate the wubildr (this only worked when Wubi was on the same partition as Windows). In 11.04 beta it does not attempt to update the wubildr. Therefore, I was still being dropped at the grub prompt and had to manually recreate wubildr by running: sudo grub-install /dev/sda2 This fixed the problem, but note that it populates all the grub modules in /boot/grub which is not standard for a Wubi install. But the end result was that it worked as indicated by your notes. It was a slightly different story for my install on the non-windows partition. The one positive was that it does not prompt you to install grub to the MBR (the grub-install trigger has been suppressed? due to grub-install devices being empty?) So that's a positive that takes care of bug 610898 (at least in Natty). But the issue is, there is no easy way to upgrade wubildr to -8ubuntu1. If I try the method 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, but this is required for cross-disk install. I can fool it as follows: bcbc@ubuntu:~$ touch /host/wubildr bcbc@ubuntu:~$ sudo grub-install /dev/sda3 Installation finished. No error reported. bcbc@ubuntu:~$ ls -l /host/wubildr -rwxrwxrwx 1 root root 143810 2011-04-02 13:02 /host/wubildr bcbc@ubuntu:~$ But then I still have to mount and copy the generated wubildr to /dev/sda2 (as that's the one that wubildr.mbr finds first). Instead I deleted the one on /dev/sda2 and it boots fine now. So... in summary, the fix works. But not sure how it will work on upgrade from 10.10 to 11.04 (I guess we'll find out soon enough). But that's good work finding those tricky errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742967 Title: Natty Wubi grub prompt on install -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742967] Re: Natty Wubi grub prompt on install
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:~$ sudo /usr/share/lupin-support/grub-mkimage --test; echo $? [sudo] password for bcbc: 0 bcbc@ubuntu:~$ sudo grub-probe --target=device /boot /dev/loop0 bcbc@ubuntu:~$ sudo losetup $(sudo grub-probe --target=device /boot) /dev/loop0: [0802]:119065 (/host/ubuntu/disks/root.disk) bcbc@ubuntu:~$ cat /proc/mounts rootfs / rootfs rw 0 0 none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 none /proc proc rw,nosuid,nodev,noexec,relatime 0 0 none /dev devtmpfs rw,relatime,size=505408k,nr_inodes=126352,mode=755 0 0 none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 /dev/sda2 /host fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0 /dev/loop0 / ext4 rw,relatime,errors=remount-ro,commit=600,barrier=1,data=ordered 0 0 none /sys/kernel/debug debugfs rw,relatime 0 0 none /sys/kernel/security securityfs rw,relatime 0 0 none /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0 none /var/run tmpfs rw,nosuid,relatime,mode=755 0 0 none /var/lock tmpfs rw,nosuid,nodev,noexec,relatime 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0 gvfs-fuse-daemon /home/bcbc/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0 bcbc@ubuntu:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742967 Title: Natty Wubi grub prompt on install -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 742967] Re: Natty Wubi grub prompt on install
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. https://bugs.launchpad.net/bugs/742967 Title: Natty Wubi grub prompt on install -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 742967] Re: Natty Wubi grub prompt on install
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 1.98+20100804-5ubuntu2. 2. /boot/grub remained empty except for three files: grubenv, grub.cfg and unicode.pf 3. Despite differences in grub.cfg with maverick it booted fine. 4. Ran sudo update-grub - rebooted fine 5. Ran sudo dpkg-reconfigure grub-pc - no change to /host/wubildr or /boot/grub and rebooted fine 6. Reinstalled same version of grub-pc using synaptic - no change to /host/wubildr or /boot/grub. This time I was interrupted and windows booted in the meantime. On rebooting into Ubuntu it ended up at the grub prompt. So... in summary: grub-install does not run anymore as a postinst trigger when installing or reconfiguring grub-pc, and /host/wubildr is not updated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742967 Title: Natty Wubi grub prompt on install -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742967] Re: Natty Wubi grub prompt on install
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 populated the files in the /boot/grub)... and now it's booting again. So... it looks like it's a manual regeneration of wubildr that's required on both 'windows-partition' installs as well as 'non-windows- partition' installs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742967 Title: Natty Wubi grub prompt on install -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 762833] Re: Incorrect version of wubi.exe on http://www.ubuntu.com/desktop/get-ubuntu/windows-installer
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 correct either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/762833 Title: Incorrect version of wubi.exe on http://www.ubuntu.com/desktop/get- ubuntu/windows-installer -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 568611] Re: Screen brightness control fails on Dell Studio 1558
I'm running Oneiric, Dell 14R N4010 Since applying the patch, the brightness keys work, but only to toggle the screen off and on. I tried adding the boot option dell_laptop.backlight=0 but it didn't make a difference. Before I added that boot option I had a dell_backlight entry in /sys/class/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@ubuntu:~$ Here is the line from my grub.cfg: linux /boot/vmlinuz-3.0.0-8-generic root=UUID=18B4B7BBB4B799A8 loop=/ubuntu/disks/root.disk ro crashkernel=384M-2G:64M,2G-:128M quiet splash dell_laptop.backlight=0 vt.handoff=7 PS your Natty patch worked great on this computer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/568611 Title: Screen brightness control fails on Dell Studio 1558 To manage notifications about this bug go to: https://bugs.launchpad.net/null/+bug/568611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 826135] Re: installation problem
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: %temp%\wubi-11.04-rev211.log In some cases, Wubi completes successfully but the computer still boots into Windows without offering a choice between Ubuntu and Wubi. Please describe in detail what happened during the install and any errors e.g. popup error messages - to help figure out what issue you are having. ** Changed in: wubi Status: New = Invalid ** Converted to question: https://answers.launchpad.net/wubi/+question/167939 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/826135 Title: installation problem To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/826135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 826378] Re: Oneiric Alpha3 - Wubi grub menu not hidden
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 and break things). That was just my interpretation of the one-line entry in the blueprint - so that was why I filed the bug. So... I guess it should do whatever you intended it to do :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/826378 Title: Oneiric Alpha3 - Wubi grub menu not hidden To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/826378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576724] Re: Ubuntu Lucid grub2 dist-upgrades result in confusion
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 accessed over 26,000 times, so that speaks to the number of people affected by this. In my opinion, this would be a higher priority than maverick. I'll go back to my hole now. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 653134] Re: Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
@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 grub.cfg in the process, and this morning the computer failed to boot again, dropping at the grub prompt. So long story. Basically I've seen other users on the forums whose maverick has been working and then suddenly: grub prompt. Which points to lupin destroying wubildr, even on 10.10 installs. So I change grub-mkimage in lupin to revert back to the last version (just removed those 3 additional modules), ran 'grub-install /dev/sdaY' and... it works again. So, my point is - it's been 3 weeks since release. There have been many affected users on the forums. Is it possible to just revert the lupin change and prevent this problem from reoccurring? Thanks PS clearly my tests are not comprehensive, if you need some additional testing to confirm this on, say, a fresh 10.10 install, let me know. I just think the change is fairly minor and, it's pretty clear the new lupin is breaking wubildr, so... it makes sense to me ;) -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 653134] Re: Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
@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 grub will do it. Then I reapplied the fix, ran grub-install /dev/sdaY again - and it works fine again. So the modules in my /usr/share/lupin-support/grub-mkimage looks like this now... # Watch the modules order! modules= \ loadenv biosdisk part_msdos part_gpt fat ntfs ext2 ntfscomp iso9660 loopback \ search linux boot minicmd cat cpuid chain halt help ls reboot \ echo test configfile normal sleep memdisk tar -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 653134] Re: Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
@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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 653134] Re: Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
@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 Extracts from bootinfoscript (fyi /dev/sda is a USB stick): = Grub 2 is installed in the MBR of /dev/sdb and looks on the same drive in partition #5 for /boot/grub. ... sdb5: _ File system: ntfs Boot sector type: Grub 2 Boot sector info: Grub 2 is installed in the boot sector of sdb5 and looks at sector 296660197 of the same hard drive for core.img, but core.img can not be found at this location. According to the info in the boot sector, sdb5 starts at sector 63. Operating System: Boot files/dirs: /ubuntu/winboot/wubildr.mbr /ubuntu/winboot/wubildr /ubuntu/disks/root.disk /ubuntu/disks/swap.disk /boot/grub/core.img sdb5/Wubi: _ File system: ext4 Boot sector type: Grub 2 Boot sector info: Grub 2 is installed in the boot sector of sdb5/Wubi and looks at sector 21424016 of the same hard drive for core.img, but core.img can not be found at this location. Operating System: Ubuntu 10.10 Boot files/dirs: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 653134] Re: Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
@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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629239] Re: wubi 10.04 contains incorrect versions
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 image 3 times, then checks that it's not 10.04.1 and rejects it. This seems like a relatively easy fix for a wubi developer (Evan?) and since ubuntu.com is still offering wubi.exe at release 10.04.1 it's still affecting users. Maybe the easiest fix is just to update ubuntu.com to have wubi.exe for 10.10. -- wubi 10.04 contains incorrect versions https://bugs.launchpad.net/bugs/629239 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581760] Re: [Wubi] when updating it advices to install grub on all partitions
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581760] Re: [Wubi] when updating it advices to install grub on all partitions
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 this for an update that really does nothing. For instance a message like the following: Hi all, Just updated using the update manager and unfortunately can no longer load wubi. Get an error message saying: error: unknown command 'loadfont' error: file not found Seems people in the past have had problems with this happening to wubi. Not a huge deal since I have everything backed up but just want people to be aware of this as I don't think it will be just me? Going to partition and make a proper ubuntu install now -- [Wubi] when updating it advices to install grub on all partitions https://bugs.launchpad.net/bugs/581760 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 653134] Re: Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 620028] Re: Wubi installs but no Ubuntu entry in Grub
** 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 French) and then rebooted. I selected Windows (I have other Ubuntu partitions so using grub), then I select Ubuntu from the Windows Boot Manager. - The only options were to select Windows, or my other Ubuntu installations. No entries were present for the Wubi install that had just completed. + Pressing the SKIP button in Ubiquity during a WUBI install stops the package lupin being installed with the result that grub cannot detect the loopmounted install. + After completing the installation, wubildr still retrieves the grub menu from the root.disk but only the external OS's are available (usually just Windows). - Looking in /etc/grub.d/ I see there is no 10_lupin entry which would - explain the missing Wubi entries. - - I forgot to mention that I clicked on the SKIP button towards the end of - the Installation. I did this on the spur of the moment to see what would - happen. I ran it again this time in Spanish. Clicking on SKIP - (whatever it says in Spanish) near the end of the install results in the - same issue. - - I am going to repeat in English, see what I am skipping, and confirm - that it's reproducible: there are two SKIP buttons presented. If you - click on the second - the text Checking for packages to install shows - briefly and then disappears, then it results in the problem (I guess - this is where it installs lupin-support). - - I haven't tried clicking on the first SKIP button, which refers to - Configuring Apt, Scanning local repositories, and Security updates (it - flashes by pretty fast). - - It seems that it shouldn't offer to skip something that is important. I - assumed it was something like looking up the network time (and since not - connected, thought it was ok to skip). + When you chroot into the wubi install you can see that everything is + there except not the lupin packages and the 10_lupin scripts in + /etc/grub.d/ that are required to get the wubi install added to + 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581760] Re: [Wubi] when updating it advices to install grub on all partitions
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 to loop mount the root.disk and edit the grub.cfg manually. Replacing the updated wubildr with the old one doesn't help at all. Again, I have to ask - since this update is specific to Wubi... did anyone actually test it on 10.04.1? And if it isn't actually achieving anything... why? -- [Wubi] when updating it advices to install grub on all partitions https://bugs.launchpad.net/bugs/581760 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
@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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 610898] Re: grub-pc upgrade renders computer unbootable when Wubi is installed to partition other than Windows
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 on ubuntuforums.org and answers.launchpad.net/wubi. Although this fortunately still allows users to boot Windows, I do not know of a fix to the problem other than the workaround to loop mount and edit grub.cfg by hand. It appears that this patch was not tested before releasing it, because a fresh install of Ubuntu 10.04.1 on 'drive C:' with the update applied does not boot. This problem is almost identical in nature to the symptoms of bug 653134 (it appears to me that it's due to the same code patch but it was released on Maverick first) to which their has been no futher investigation by developers since the release of Maverick. If it is the same code patch that was known to break wubi installs on upgrade to Maverick, it is highly irresponsible that this was then released on 10.04.1 without addressing the problem. All in all, I am dismayed by the poor development support Wubi receives and question whether Canonical should be making it available when these grub updates break it so easily. -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 653134] Re: Can't boot Ubuntu after an upgrade from 10.04.1 to 10.10
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 --fs-uuid --set 80e4e195e4e18daa loopback loop0 /ubuntu/disks/root.disk set root=(loop0) if loadfont /usr/share/grub/unicode.pf2 ; then set gfxmode=640x480 load_video insmod gfxterm fi terminal_output gfxterm insmod part_msdos insmod ntfs set root='(hd0,msdos2)' search --no-floppy --fs-uuid --set 80e4e195e4e18daa loopback loop0 /ubuntu/disks/root.disk set root=(loop0) set locale_dir=($root)/boot/grub/locale set lang=en insmod gettext 140,155d116 } So... this is probably the root cause of the issue. I've been seeing reports on ubuntuforums.org that commenting out the loopback lines (the two in the diff shown above) gets wubi booting. But surely the cause is that all these lines are different between the base install, and reinstalling grub-pc i.e. one of the scripts in /etc/grub.d is being changed from the default install. This is likely also the problem then with the 10.04.1 installs that are breaking. -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
