RE: Wubi
There is also some logic in Ubiquity that will copy Wubi.exe to the Windows startup folder, when it finds 4 primary partitions already in use on an MBR formatted disk. It asks Install Ubuntu inside Windows? as the first option. e.g. http://askubuntu.com/q/536075/14916 When this happens, Wubi will run automatically the next time Windows starts - in standalone mode - which means it will download the whole ISO and try to install. So it is *inaccurate* to say that Wubi is serving only as a greeter in Windows. It is broken and needs to be fixed or removed. Here is the Ubiquity code in case you're interested: https://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/view/head:/ubiquity/plugins/ubi-partman.py#L2333 If you'll notice, the logic depends on whether Wubi.exe has been shipped on the ISO or not. Remove Wubi and the logic is disabled. Also I find it a bit rich for you to say ...if one wants to brick their windows. Remember that Wubi.exe is signed and certified by Canonical. They probably won't find it amusing that the team in charge of Wubi are making comments like that. One would hope. On that subject (on being in charge of Wubi), you do realise that there are in fact patches supplied to fix Wubi? So if you wanted to you could just promote them. For example: https://code.launchpad.net/~hakuna-matata/wubi/upstart (merge requested in May) https://code.launchpad.net/~hakuna-matata/wubi/UEFI https://code.launchpad.net/~hakuna-matata/wubi/lp1385930 https://code.launchpad.net/~hakuna-matata/wubi/lp1317437 If you need help with these I'm pretty sure hakuna-matata would be happy to assist. Regards, bcbc *On 21 August 2015 at 13:53, Dimitri John Ledkov xnox at ubuntu.com http://ubuntu.com wrote: * *On 21 August 2015 at 13:53, Alan Pope alan.pope at canonical.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss wrote: ** On 21 August 2015 at 13:45, Michael Hall mhall119 at ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss wrote: ** Modern Windows releases broke Wubi, so we stopped shipping and ** supporting it a while back. As far as I know it's a dead-end now. ** We didn't stop shipping it. I just downloaded the 15.04 desktop iso. **but it's only used in greeter mode on windows which shows a GUI window and offers one to reboot. launching wubi.exe off the cd doesn't start wubi installer. if one moves the wubi.exe off the disk however, it still shows the installer mode if one wants to brick their windows Regards, Dimitri.* -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
[Bug 980338] Re: gcompris crashed with SIGABRT in mem_error()
No I haven't seen this again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980338 Title: gcompris crashed with SIGABRT in mem_error() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcompris/+bug/980338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317437] Re: wubi kernel option rw required
** Branch linked: lp:~noorez-kassam/ubuntu/utopic/initramfs-tools/fix- for-1317437 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317437 Title: wubi kernel option rw required To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1317437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385930] Re: 14.10 dual boot win 7 64-bit cannot with wubi installing
Same thing happened to me. I just did a test 14.04 install on the same computer so it's not a local issue. The Fdisk output is odd - looks like it's trying to partition the 6GB root.disk so that it has an efi partition: Disk /dev/loop0: 1.1 GiB, 1162936320 bytes, 2271360 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x4a022e4f Device Boot Start End Sectors Size Id Type /dev/loop0p1 * 0 2271359 2271360 1.1G 0 Empty /dev/loop0p2 2250448 22549914544 2.2M ef EFI (FAT-12/16/32) Disk /dev/loop1: 1 GiB, 1115594752 bytes, 2178896 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop2: 5.6 GiB, 6023020544 bytes, 11763712 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sda: 698.7 GiB, 750156374016 bytes, 1465149168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x00071c89 Device Boot StartEndSectors Size Id Type /dev/sda1 * 2048 681983 679936 332M 7 HPFS/NTFS/exFAT /dev/sda2 681984 177782783 177100800 84.5G 7 HPFS/NTFS/exFAT /dev/sda4177784830 1465147391 1287362562 613.9G 5 Extended /dev/sda5177784832 960141311 782356480 373.1G 83 Linux /dev/sda6960143360 1389404159 429260800 204.7G 7 HPFS/NTFS/exFAT /dev/sda7 1452785664 1465147391 12361728 5.9G 82 Linux swap / Solaris Partition 5 does not start on physical sector boundary. ** Summary changed: - 14.10 dual boot win 7 64-bit cannot with wubi installing + 14.10 dual boot Win 7 64-bit - cannot install with Wubi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385930 Title: 14.10 dual boot Win 7 64-bit - cannot install with Wubi To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/1385930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385930] Re: 14.10 dual boot Win 7 64-bit - cannot install with Wubi
** Attachment added: /var/log/installer/debug https://bugs.launchpad.net/wubi/+bug/1385930/+attachment/4249641/+files/debug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385930 Title: 14.10 dual boot Win 7 64-bit - cannot install with Wubi To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/1385930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1385930] [NEW] 14.10 dual boot win 7 64-bit cannot with wubi installing
This historically happened with the ubuntu installer (ubiquity) if parted returns errors (both normal and wubi installs). Seen it before when there is leftover GPT data on a MBR formatted disk. Try booting from the USB and going to a terminal (or hit Ctrl+Alt+F1 during the installation) and run: sudo parted -l and sudo fdisk -l See what errors you get (PS those are lower case L's). If it complains about GPT data on a MBR formatted disk or returns other errors, then you'll need to clean them up before the installer will let you continue. There's a possibility this is something new but I'd rule the above out first. On Sun, Oct 26, 2014 at 10:19 AM, Ilian Zhelyazov iliani...@gmail.com wrote: Public bug reported: Мy computer is with windows 7 ultimate 64-bit quad core pentium, 6 GiGs RAM and 1TB harddisk, and i decide to try new ubuntu 14.10 64-bit, download the iso from ubuntu site and install with wubi, reboot and installation stop with:''failed to partition the selected disk/this probably happened because are too many/primary/ partitions in the partition table/. After clicking OK stopped with error No root file system is defined each clicking on this error continious repeated endless this label.Please help me to decide these error! ** Affects: wubi Importance: Undecided Status: New ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** Also affects: debian-installer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to Wubi. https://bugs.launchpad.net/bugs/1385930 Title: 14.10 dual boot win 7 64-bit cannot with wubi installing Status in Wubi, Windows Ubuntu Installer: New Status in “debian-installer” package in Ubuntu: New Bug description: Мy computer is with windows 7 ultimate 64-bit quad core pentium, 6 GiGs RAM and 1TB harddisk, and i decide to try new ubuntu 14.10 64-bit, download the iso from ubuntu site and install with wubi, reboot and installation stop with:''failed to partition the selected disk/this probably happened because are too many/primary/ partitions in the partition table/. After clicking OK stopped with error No root file system is defined each clicking on this error continious repeated endless this label.Please help me to decide these error! To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/1385930/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385930 Title: 14.10 dual boot win 7 64-bit cannot with wubi installing To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/1385930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1134770] Re: Wubi fails to detect 12.04.2 and 13.04 AMD64 ISO
** Package changed: ubuntu = wubi ** Changed in: wubi Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1134770 Title: Wubi fails to detect 12.04.2 and 13.04 AMD64 ISO To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/1134770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196392] Re: [Dell Inc. Inspiron N4010] suspend/resume failure
I haven't yet been able to duplicate the kernel oops. I can get the computer to Suspend while Shutting down on the latest Ubuntu kernel, and I get the same behaviour using the Mainline build, but so far no kernel oops. Reproducible: If I shut the lid immediately after shutting down, it proceeds to shut down, but if I wait until the screen backlight is switched off and then shut the lid, it Suspends - and then after opening the lid resumes Shut down. I will try it with different timing to see if that makes a difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196392 Title: [Dell Inc. Inspiron N4010] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196392] [NEW] [Dell Inc. Inspiron N4010] suspend/resume failure
Public bug reported: I shut down my computer... waited long enough I figured - and closed the lid. Came back hours later to find it had suspended instead of shutting down. I think this is probably the bug, not the resume failure. In any case, after opening the lid, it sort of resumed and then continued to shut down as originally intended. IMO,once the shutdown signal is received it should override a suspend signal from the lid closing. Otherwise you have to sit and stare at the computer to make sure it does what it's asked - and that's... not good. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-1-generic 3.10.0-1.8 ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7 Uname: Linux 3.10.0-1-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bcbc 1914 F pulseaudio Date: Sun Jun 30 21:23:54 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=9b959dc9-7784-4b26-8506-ca98c00a5eb8 InstallationDate: Installed on 2011-10-08 (631 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111006) InterpreterPath: /usr/bin/python3.3 MachineType: Dell Inc. Inspiron N4010 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=18B4B7BBB4B799A8 loop=/ubuntu/disks/raring.disk ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.10.0-1-generic N/A linux-backports-modules-3.10.0-1-generic N/A linux-firmware1.110 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: [Dell Inc. Inspiron N4010] suspend/resume failure UpgradeStatus: Upgraded to saucy on 2013-05-04 (57 days ago) UserGroups: dmi.bios.date: 03/31/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 021CN3 dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A13 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/31/2011:svnDellInc.:pnInspironN4010:pvrA13:rvnDellInc.:rn021CN3:rvrA13:cvnDellInc.:ct8:cvrA13: dmi.product.name: Inspiron N4010 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume saucy suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196392 Title: [Dell Inc. Inspiron N4010] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105604] Re: Brightness control stopped working
An update on this bug... I have two raring installs. For one of them the brightness controls work, one doesn't. The one that doesn't work is a vanilla upgrade to Raring 13.04 from Quantal 12.10. The one that works is also an upgrade from 12.10, but there are two major differences: 1. I installed Gnome Shell 2. I am running the Mir PPA I have no idea which of the above might account for the brightness controls working, but installing Gnome shell should be harmless and it's not a bad desktop - so I'd recommend to try that. I don't recommend using the Mir PPA. There is a question on Askubuntu that I provided the brightness settings you can use (manually) to work around the issue: http://askubuntu.com/a/289177/14916 (specific to a Dell Inspiron N4010) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1105604 Title: Brightness control stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1105604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105604] Re: Brightness control stopped working
Just noticed my brightness controls are working again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1105604 Title: Brightness control stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1105604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Intention to drop Wubi from 13.04 release
Dmitrijs, I've provided a patch for Wubi does not check if Windows boots using UEFI https://bugs.launchpad.net/wubi/+bug/694242 so that Wubi checks for an EFI boot and exits with an error message Wubi does not currently support EFI. It does this prior to downloading any ISOs and there's no subsequent uninstall required. Getting Wubi to actually work on an EFI system won't be as easy. I'll investigate it further, though. Regards, bcbc On Fri, Apr 19, 2013 at 9:02 PM, bcbc bcbc openb...@gmail.com wrote: Thanks for merging. I'll take a look at the UEFI issues. Regards, bcbc On Fri, Apr 19, 2013 at 6:38 AM, Dmitrijs Ledkovs dmitrij.led...@ubuntu.com wrote: On 8 April 2013 18:01, bcbc bcbc openb...@gmail.com wrote: Re. the bugs. I had a look at Wubi fails to detect 12.04.2 and 13.04 AMD64 ISO https://bugs.launchpad.net/wubi/+bug/1134770 and found that the fix is a one-liner configuration file change (in data/isolist.ini). The fix for 13.04 installer doesn't create user account https://bugs.launchpad.net/wubi/+bug/1155704 could be to simply remove the disk-image installs from 13.04. This again is a two line removal from the same configuration file. I've patched and tested both 12.04.2 and 13.04 with these changes to confirm they work. Thanks a lot for your branches. I have merge all of your fixes, tested it with window7 and they work correctly. For 13.04 we have disabled and stopped building disk-images, so those are gone. And the isolist.ini is correct as per your patches to match reality. I have pinged Evan, to publish a release and request the wubi.exe builds for Precise and Raring be signed such that we can release them. I am not sure how long the delay is but hopefully we will be able to release wubi for precise raring soon. Re. Windows 8: that may not be solvable right now, but I expect there are still many more BIOS-based computers out there than UEFI. And the regular dual boot for UEFI has many problems as well. Wubi could probably be smarter about checking whether Windows is booting through UEFI and exit gracefully prior to downloading the ISO/diskimage. Would you be able to contribute safe-guards (e.g. bail out, disable hibernation) and or Windows8 UEFI boot integration for wubi? The first one will prevent people from getting disappointed, while the later will potentially make wubi fully supperted yet again. Regards, Dmitrijs. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Intention to drop Wubi from 13.04 release
Thanks for merging. I'll take a look at the UEFI issues. Regards, bcbc On Fri, Apr 19, 2013 at 6:38 AM, Dmitrijs Ledkovs dmitrij.led...@ubuntu.com wrote: On 8 April 2013 18:01, bcbc bcbc openb...@gmail.com wrote: Re. the bugs. I had a look at Wubi fails to detect 12.04.2 and 13.04 AMD64 ISO https://bugs.launchpad.net/wubi/+bug/1134770 and found that the fix is a one-liner configuration file change (in data/isolist.ini). The fix for 13.04 installer doesn't create user account https://bugs.launchpad.net/wubi/+bug/1155704 could be to simply remove the disk-image installs from 13.04. This again is a two line removal from the same configuration file. I've patched and tested both 12.04.2 and 13.04 with these changes to confirm they work. Thanks a lot for your branches. I have merge all of your fixes, tested it with window7 and they work correctly. For 13.04 we have disabled and stopped building disk-images, so those are gone. And the isolist.ini is correct as per your patches to match reality. I have pinged Evan, to publish a release and request the wubi.exe builds for Precise and Raring be signed such that we can release them. I am not sure how long the delay is but hopefully we will be able to release wubi for precise raring soon. Re. Windows 8: that may not be solvable right now, but I expect there are still many more BIOS-based computers out there than UEFI. And the regular dual boot for UEFI has many problems as well. Wubi could probably be smarter about checking whether Windows is booting through UEFI and exit gracefully prior to downloading the ISO/diskimage. Would you be able to contribute safe-guards (e.g. bail out, disable hibernation) and or Windows8 UEFI boot integration for wubi? The first one will prevent people from getting disappointed, while the later will potentially make wubi fully supperted yet again. Regards, Dmitrijs. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Intention to drop Wubi from 13.04 release
I think the point in the original post was that Wubi 13.04 was broken and doesn't work with Windows 8 UEFI, not that there's a risk of data loss. There's also no evidence that I have seen to indicate that Wubi causes data loss in Windows 8. The Windows boot manager won't give you any choice if you have hibernated Windows, and therefore it's not possible to boot Wubi with normal hibernation. And if fast-start is enabled the Windows 8 boot manager also removes this hibernated system session prior to booting Wubi. This is more of a problem on a normal dual boot, and even then, unless you force-mount the NTFS partition you shouldn't see any data loss. You can refer to this bug report for more info: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1043149 The only issue shown there is if you enable hybrid-sleep (not switched on by default), and even then there's no data loss - just the partition can't be mounted so Wubi doesn't boot. So, if we go back to the original point, given that Wubi 13.04 is easily fixable, are your guesstimates of usage high or low? Are they based on the downloads of Wubi.exe? Any numbers on that? Regards, bcbc On Tue, Apr 9, 2013 at 8:09 AM, Dmitrijs Ledkovs dmitrij.led...@ubuntu.comwrote: On 8 April 2013 18:01, bcbc bcbc openb...@gmail.com wrote: It's hard to make an informed decision without knowing the usage stats of Wubi. If it's quite low then I expect there'd be little impact, but if it's popular then it's taking a low-risk installation method away from users who might otherwise not have tried Ubuntu. Does Canonical have any statistics on this? The point that it's not low-risk any more. It can cause data-loss on windows 8 side when it's hibernated. W.r.t. statistics - we don't have them, as with all open-source software it's free to distribute and we do not have any central point to measure install base. And we will not be introducing one either, as it is against our project. We can guesstimate, but it will be guesstimates. Re. the bugs. I had a look at Wubi fails to detect 12.04.2 and 13.04 AMD64 ISO https://bugs.launchpad.net/wubi/+bug/1134770 and found that the fix is a one-liner configuration file change (in data/isolist.ini). The fix for 13.04 installer doesn't create user account https://bugs.launchpad.net/wubi/+bug/1155704 could be to simply remove the disk-image installs from 13.04. This again is a two line removal from the same configuration file. I've patched and tested both 12.04.2 and 13.04 with these changes to confirm they work. Re. Windows 8: that may not be solvable right now, but I expect there are still many more BIOS-based computers out there than UEFI. And the regular dual boot for UEFI has many problems as well. Wubi could probably be smarter about checking whether Windows is booting through UEFI and exit gracefully prior to downloading the ISO/diskimage. Window 8 + Wubi is dangerous regardless of BIOS/UEFI boot. Regards, Dmitrijs. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Intention to drop Wubi from 13.04 release
This is an often repeated argument against Wubi, but there are some problems with it. 1. Wubi isn't supposed to compete head-to-head with a normal install. I've seen cases of people that aren't even aware they are using Wubi or what the differences are, and this is definitely an issue. So I raised this bug: https://bugs.launchpad.net/wubi/+bug/1078959 2. If point #1 is not understood then, yes, I can understand why people would get upset about Wubi. But imagine if every time someone burned a live CD and it failed and then we decided it was a problem and we should get rid of live CDs because it was making Ubuntu look bad. No, I don't believe that argument holds. 3. Wubi does in fact work well. I could forgive a newcomer to Ubuntu thinking why do a normal install when Wubi works so well. I can hear you laughing, but this is actually stated often[*]. Yes there are bugs. Yes people have problems. But these need to be looked at without emotion and used to make a rational decision. Saying I have a friend who... or I couldn't even get it working so... or Windows is unstable therefore... just doesn't add anything of value. So to answer your main point... the journalist did make a mistake recommending Wubi. I haven't seen anyone in mainstream put forward Wubi as a viable long-term alternative or a production system. There should indeed be warnings. But we should IMO go further to understand what real positives and real negatives they are, and arrive at a reasoned decision. And I'm fine with that decision either way. Regards, bcbc [*] References 1. Comments in the same article you referenced 2. http://ubuntuforums.org/showthread.php?t=2131454 (Wubi is no more) 3. http://ubuntuforums.org/showthread.php?t=2093840 (Is WUBI worth it) 4. http://ubuntuforums.org/showthread.php?t=1982669 (Wubi opinion/usage survey) On Tue, Apr 9, 2013 at 12:31 PM, Robert Bruce Park robert.p...@canonical.com wrote: On Tue, Apr 09, 2013 at 04:09:35PM +0100, Dmitrijs Ledkovs wrote: On 8 April 2013 18:01, bcbc bcbc openb...@gmail.com wrote: It's hard to make an informed decision without knowing the usage stats of Wubi. If it's quite low then I expect there'd be little impact, but if it's popular then it's taking a low-risk installation method away from users who might otherwise not have tried Ubuntu. Does Canonical have any statistics on this? The point that it's not low-risk any more. It can cause data-loss on windows 8 side when it's hibernated. I can't find the original article right now, but I recently read a gaming blog where some random journalist had attempted to install Steam inside of a Wubi Ubuntu installation. His readers mercilessly flamed him as being essentially a total idiot (because everybody just knows that Wubi is *incredibly* terrible), and so he was forced to try it again without Wubi. Had he not been a journalist, he would have simply given up on Wubi and written Ubuntu off as an unstable product. The unfortunate reality is that if Wubi is your first experience with Ubuntu, you're likely to come to the conclusion that Ubuntu is an unstable mess, when really it's the fact that Windows is an unstable base underneath your Ubuntu that is causing the problems (but you don't know that). Wubi is basically a disaster and is generating a lot of negative associations with Ubuntu in novice's minds. Here's an alternate page where Don't use Wubi is given as the number one piece of advice for getting Steam to run on Ubuntu: http://forums.steampowered.com/forums/showthread.php?t=3079968 In short, Wubi needs to die a quick and painless death so we can get on with providing positive experiences to new users of Ubuntu. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Bug 986269] Re: Unable to open a folder for 10 GB Filesystem, No application is registered as handling this file... or Nautilus pops browser when partition is mounted in bash script
Retested this. The problem doesn't occur on 12.10 or 13.04. It still happens on 12.04.2, which is using with nautilus 3.4.2. Actually 12.10 is also using nautilus 3.4.2. So maybe this isn't a nautilus bug after all. In 12.04.2 the window pops up but nothing changes in the Unity bar. In 12.10, there is a drive icon for the partition being mounted which disappears when I mount it on /mnt. and reappears when I unmount it. So... now I'm thinking this is actually a Unity bug in 12.04.2. ** Package changed: nautilus (Ubuntu) = 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/986269 Title: Unable to open a folder for 10 GB Filesystem, No application is registered as handling this file... or Nautilus pops browser when partition is mounted in bash script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/986269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Intention to drop Wubi from 13.04 release
It's hard to make an informed decision without knowing the usage stats of Wubi. If it's quite low then I expect there'd be little impact, but if it's popular then it's taking a low-risk installation method away from users who might otherwise not have tried Ubuntu. Does Canonical have any statistics on this? Re. the bugs. I had a look at Wubi fails to detect 12.04.2 and 13.04 AMD64 ISO https://bugs.launchpad.net/wubi/+bug/1134770 and found that the fix is a one-liner configuration file change (in data/isolist.ini). The fix for 13.04 installer doesn't create user account https://bugs.launchpad.net/wubi/+bug/1155704 could be to simply remove the disk-image installs from 13.04. This again is a two line removal from the same configuration file. I've patched and tested both 12.04.2 and 13.04 with these changes to confirm they work. Re. Windows 8: that may not be solvable right now, but I expect there are still many more BIOS-based computers out there than UEFI. And the regular dual boot for UEFI has many problems as well. Wubi could probably be smarter about checking whether Windows is booting through UEFI and exit gracefully prior to downloading the ISO/diskimage. Regards, bcbc On Tue, Apr 2, 2013 at 5:00 AM, ubuntu-devel-requ...@lists.ubuntu.comwrote: Date: Mon, 1 Apr 2013 12:59:35 -0700 From: Steve Langasek steve.langa...@ubuntu.com To: ubuntu-devel@lists.ubuntu.com Subject: Intention to drop Wubi from 13.04 release Message-ID: 20130401195935.ga8...@virgil.dodds.net Content-Type: text/plain; charset=us-ascii Dear developers, Recent bug reports suggest that the Ubuntu installer for Windows, Wubi, is not currently in very good shape for a release: 13.04 installer doesn't create user account https://bugs.launchpad.net/wubi/+bug/1155704 Wubi fails to detect 12.04.2 and 13.04 AMD64 ISO https://bugs.launchpad.net/wubi/+bug/1134770 Combined with the fact that Wubi has not been updated to work with Windows 8 (bug #1125604), and the focus on mobile client over desktop, the Foundations team does not expect Wubi to be in a releasable state for 13.04. I am therefore proposing to drop Wubi from the 13.04 release, starting immediately with the upcoming Beta. This will save our testers from spending their time testing an image that will not have developers working on fixing the bugs they find, and spares our users from using an image for 13.04 that is not up to Ubuntu's standards of quality. If someone is interested in taking over the maintenance of Wubi so that it can be released with 13.04 (or if not with 13.04, then with a future release), I would encourage them to start by looking at the abovementioned bugs and preparing patches, then talking to the release team. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: https://lists.ubuntu.com/archives/ubuntu-devel/attachments/20130401/b059d08c/attachment-0001.pgp -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Bug 1079482] Re: Windows 7 Not Booting after Grub installed to bootsector
Here is another: http://askubuntu.com/questions/269720/cant-start- windows-after-installing-ubuntu And another: http://ubuntuforums.org/showthread.php?t=1769482p=12560337viewfull=1#post12560337 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1079482 Title: Windows 7 Not Booting after Grub installed to bootsector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1079482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1079482] Re: Windows 7 Not Booting after Grub installed to bootsector
** Changed in: grub2 (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1079482 Title: Windows 7 Not Booting after Grub installed to bootsector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1079482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105604] Re: Brightness control stopped working
Latest update... the brightness control keys 'work'. The slider moves up and down, but there is no impact to the actual brightness. I'm controlling the brightness manually by setting it automatically after bootup and resume|thaw via scripts. I'm running raring with the Mir ppa, but I have another non-Mir raring install if you need any information sans-mir ** Description changed: - Just ran latest raring updates. Screen on full brightness, Fn keys - didn't move the slider. Going to the Brightness settings I can move the - slider but it has no effect. + Just ran latest raring updates. Screen on full brightness, Fn keys didn't move the slider. Going to the Brightness settings I can move the slider but it has no effect. + [Update March 13]The Fn keys work to move the slider after the latest updates, but it has no effect on the brightness[Update March 13] Setting it manually still works: echo 978 /sys/class/backlight/intel_backlight/brightness ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-settings-daemon 3.6.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Fri Jan 25 17:22:04 2013 InstallationDate: Installed on 2011-10-08 (475 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111006) MarkForUpload: True SourcePackage: gnome-settings-daemon 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/1105604 Title: Brightness control stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1105604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105604] Re: Brightness control stopped working
Now on Raring, the backlight is off after resuming from suspend. I have to run the following (blind type) after resuming each time: echo 978 | sudo tee /sys/class/backlight/intel_backlight/brightness Also, the function keys to control the brightness setting still don't work. They do on Quantal. ** Tags added: regression -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1105604 Title: Brightness control stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1105604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105604] Re: Brightness control stopped working
Here is the syslog during the suspend/wake. This maybe a separate bug... but will move later if nec: Mar 8 18:49:30 malraux kernel: [ 593.626366] composite sync not supported Mar 8 18:49:31 malraux kernel: [ 593.787884] composite sync not supported Mar 8 18:49:31 malraux NetworkManager[1067]: info sleep requested (sleeping: no enabled: yes) Mar 8 18:49:31 malraux NetworkManager[1067]: info sleeping or disabling... Mar 8 18:49:31 malraux NetworkManager[1067]: info (wlan0): device state change: activated - unmanaged (reason 'sleeping') [100 10 37] Mar 8 18:49:31 malraux NetworkManager[1067]: info (wlan0): deactivating device (reason 'sleeping') [37] Mar 8 18:49:31 malraux NetworkManager[1067]: info (wlan0): canceled DHCP transaction, DHCP client pid 1400 Mar 8 18:49:31 malraux avahi-daemon[999]: Withdrawing address record for fe80::8ea9:82ff:fe4b:1e68 on wlan0. Mar 8 18:49:31 malraux avahi-daemon[999]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::8ea9:82ff:fe4b:1e68. Mar 8 18:49:31 malraux avahi-daemon[999]: Interface wlan0.IPv6 no longer relevant for mDNS. Mar 8 18:49:31 malraux kernel: [ 594.489654] wlan0: deauthenticating from 38:60:77:e9:54:81 by local choice (reason=3) Mar 8 18:49:31 malraux kernel: [ 594.50] cfg80211: Calling CRDA to update world regulatory domain Mar 8 18:49:31 malraux avahi-daemon[999]: Withdrawing address record for 192.168.0.13 on wlan0. Mar 8 18:49:31 malraux avahi-daemon[999]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.13. Mar 8 18:49:31 malraux NetworkManager[1067]: warn DNS: plugin dnsmasq update failed Mar 8 18:49:31 malraux NetworkManager[1067]: info Removing DNS information from /sbin/resolvconf Mar 8 18:49:31 malraux dnsmasq[1431]: setting upstream servers from DBus Mar 8 18:49:31 malraux avahi-daemon[999]: Interface wlan0.IPv4 no longer relevant for mDNS. Mar 8 18:49:31 malraux wpa_supplicant[1219]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3 Mar 8 18:49:31 malraux kernel: [ 594.521001] cfg80211: World regulatory domain updated: Mar 8 18:49:31 malraux kernel: [ 594.521006] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Mar 8 18:49:31 malraux kernel: [ 594.521009] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) Mar 8 18:49:31 malraux kernel: [ 594.521012] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) Mar 8 18:49:31 malraux kernel: [ 594.521014] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) Mar 8 18:49:31 malraux kernel: [ 594.521016] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) Mar 8 18:49:31 malraux kernel: [ 594.521018] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) Mar 8 18:49:31 malraux NetworkManager[1067]: info (wlan0): cleaning up... Mar 8 18:49:31 malraux NetworkManager[1067]: info (wlan0): taking down device. Mar 8 18:49:31 malraux NetworkManager[1067]: info (eth0): device state change: unavailable - unmanaged (reason 'sleeping') [20 10 37] Mar 8 18:49:31 malraux NetworkManager[1067]: info (eth0): cleaning up... Mar 8 18:49:31 malraux NetworkManager[1067]: info (eth0): taking down device. Mar 8 18:49:31 malraux dbus[867]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Mar 8 18:49:32 malraux dbus[867]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Mar 8 18:49:32 malraux anacron[2998]: Anacron 2.3 started on 2013-03-08 Mar 8 18:49:32 malraux anacron[2998]: Normal exit (0 jobs run) Mar 8 18:49:34 malraux kernel: [ 596.724466] PM: Syncing filesystems ... done. Mar 8 18:56:42 malraux kernel: [ 597.409494] Freezing user space processes ... (elapsed 0.01 seconds) done. Mar 8 18:56:42 malraux kernel: [ 597.425135] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. Mar 8 18:56:42 malraux kernel: [ 597.441106] Suspending console(s) (use no_console_suspend to debug) Mar 8 18:56:42 malraux kernel: [ 597.441533] sd 0:0:0:0: [sda] Synchronizing SCSI cache Mar 8 18:56:42 malraux kernel: [ 597.441823] sd 0:0:0:0: [sda] Stopping disk Mar 8 18:56:42 malraux kernel: [ 597.824795] PM: suspend of devices complete after 383.759 msecs Mar 8 18:56:42 malraux kernel: [ 597.824941] PM: late suspend of devices complete after 0.144 msecs Mar 8 18:56:42 malraux kernel: [ 597.856858] ehci-pci :00:1d.0: System wakeup enabled by ACPI Mar 8 18:56:42 malraux kernel: [ 597.904672] PM: noirq suspend of devices complete after 79.771 msecs Mar 8 18:56:42 malraux kernel: [ 597.904885] ACPI: Preparing to enter system sleep state S3 Mar 8 18:56:42 malraux kernel: [ 597.917295] PM: Saving platform NVS memory Mar 8 18:56:42 malraux kernel: [ 597.919021] Disabling non-boot CPUs ... Mar 8 18:56:42 malraux kernel: [ 598.020550] smpboot: CPU 1 is now offline Mar 8
[Bug 1079482] Re: Windows 7 Not Booting after Grub installed to bootsector
PS here is another one: http://askubuntu.com/questions/263606/windows-8 -no-longer-boots-after-grub-wiped-out-the-windows-bootsector -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1079482 Title: Windows 7 Not Booting after Grub installed to bootsector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1079482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1079482] Re: Windows 7 Not Booting after Grub installed to bootsector
Phillip Susi, There seem to many a number of issues here, but the fact is that Grub installed itself over the windows boot sector, not the MBR. Wiping out the partition boot sector prevents Windows from booting, whereas replacing the bootloader in the MBR is normal (obviously). The bug I reported was supposed to *PREVENT* grub from ever installing to the Windows partition (this used to be offered in the drop down box as the target for Grub2 while installing - in Ubiquity) but should not be offered now. But if it's not offered, then the question is how does Grub get installed to the Windows partition? The only way I know is to manually do it with grub-install /dev/sda1 --force but clearly new users are not doing this. Therefore my point about the possible regression. Running FIXMBR won't do a thing in this case. Until the bootsector is repaired Windows cannot boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1079482 Title: Windows 7 Not Booting after Grub installed to bootsector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1079482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105604] [NEW] Brightness control stopped working
Public bug reported: Just ran latest raring updates. Screen on full brightness, Fn keys didn't move the slider. Going to the Brightness settings I can move the slider but it has no effect. Setting it manually still works: echo 978 /sys/class/backlight/intel_backlight/brightness ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-settings-daemon 3.6.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Fri Jan 25 17:22:04 2013 InstallationDate: Installed on 2011-10-08 (475 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111006) MarkForUpload: True 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 raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1105604 Title: Brightness control stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1105604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1079482] Re: Windows 7 Not Booting
Grub2 was fixed to prevent offering to install on any windows partition. This seems to be a regression if it's offering Windows partitions now. I've noticed a couple of similar cases on askubuntu.com: http://askubuntu.com/questions/230775/problem-with-dual-boot-windows-xp-ubuntu-12-04 http://askubuntu.com/questions/227670/unable-to-boot-windows-7-after-grub-overwrote-the-windows-bootsector -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1079482 Title: Windows 7 Not Booting after Grub installed to bootsector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1079482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1079482] Re: Windows 7 Not Booting
Here's the bug I was referring to: bug 576724 This is a comment from that bug: This bug was fixed in the package grub2 - 1.98+20100614-2ubuntu4 --- grub2 (1.98+20100614-2ubuntu4) maverick; urgency=low * Rearrange postinst install_devices logic so that preparatory code is run only once and the while loop only encloses actual asking of questions, and so that the question being asked is always marked for redisplay when going round the while loop again (LP: #580408). * Only offer partitions containing /, /boot, or /boot/grub for grub-install; installing to other partitions may have harmful effects such as making Windows unbootable, and installing GRUB to every single partition is likely to result in confusion anyway (LP: #576724). -- Colin Watson cjwat...@ubuntu.com Thu, 01 Jul 2010 18:26:37 +0100 ** Summary changed: - Windows 7 Not Booting + Windows 7 Not Booting after Grub installed to bootsector ** Description changed: My computer came with Windows 7 installed on it. I wanted to try Ubuntu, so I installed it alongside Windows 7 and everything was fine. I needed more space on my Windows 7 partition, so I deleted the Ubuntu partition from the hard drive. When I went to restart I got a blank screen. I reinstalled Ubuntu allongside Windows 7 and was able to restart and boot Windows. The next day I got the same blank screen, so I reinstalled Ubuntu over Ubuntu, leaving the Windows 7 partition alone. After that, when I try to boot Windows 7 it keeps sending me back to the select an OS page. I get an error that says: The NTFS partition is hibernated. Please resume and shutdown Windows properly, or mount the volume read-only with the 'ro' mount option, or mount the volume read-write with the 'remove_hiberfile' mount option. For example type on the command line: mount -t ntfs-3g -o remove_hiberfile /dev/sda3 /media/OS whenever I try to access the Windows OS portion of the hard drive. When I try the command it does not work and I get a message saying that only root can do that I can not resume Windows to shut it down properly though, because I must first unhibernate Windows. I believe this may be a bug. + + This is what the bootinfoscript reports, showing that Grub has overwritten the bootsector, which prevents Windows from booting: + sda2: __ + + File system: ntfs + Boot sector type: Grub2 (v1.99) + Boot sector info: Grub2 (v1.99) is installed in the boot sector of sda2 +and looks at sector 1456312560 of the same hard drive +for core.img. core.img is at this location and looks +for (,msdos6)/boot/grub on this drive. No errors found +in the Boot Parameter Block. + Operating System: + Boot files: /bootmgr /Boot/BCD -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1079482 Title: Windows 7 Not Booting after Grub installed to bootsector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1079482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1082544] Re: [raring] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
This has been happening to me for a couple of weeks. Raring is unusable with continual crashes. If there's any info I can contribute, please let me know. I'm running a Dell Inspiron N4010 with an Intel Arrandale gpu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1082544 Title: [raring] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1082841] Re: Brightness control not working after latest update
I downgraded to confirm the old version was working (it was). Upgraded again and this time the Fn keys weren't working, but the brightness slider was present. There is also so much general instability (multiple crash reports and lockups) I couldn't confirm that the problem is related to g-s-d. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1082841 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/1082841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1082841] [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. The same thing happened during precise development - for reference that was bug 947748 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-settings-daemon 3.6.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6 Uname: Linux 3.7.0-3-generic x86_64 ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CheckboxSubmission: dd7f729683fa7fd3f2e256ba311e86cb CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Sat Nov 24 23:21:16 2012 InstallationDate: Installed on 2011-10-08 (413 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111006) MarkForUpload: True 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 raring running-unity ** Description changed: After today's update my brightness controls aren't working anymore. After checking the System Settings, Brightness and Lock there is no longer any brightness slider bar shown for manual setting either. So my screen is fixed on full brightness. + + The same thing happened during precise development - for reference that + was bug 947748 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-settings-daemon 3.6.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6 Uname: Linux 3.7.0-3-generic x86_64 ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CheckboxSubmission: dd7f729683fa7fd3f2e256ba311e86cb CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Sat Nov 24 23:21:16 2012 InstallationDate: Installed on 2011-10-08 (413 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111006) MarkForUpload: True SourcePackage: gnome-settings-daemon 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/1082841 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/1082841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070682] Re: wubi and ubuntu studio
** Package changed: ubuntu = ubuntustudio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070682 Title: wubi and ubuntu studio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntustudio/+bug/1070682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067580] Re: Closed windows appear as phantom desktop overlay
This happened again today after thawing from hibernation - this time the terminal was part of the phantom desktop image - so it's not just happening to the chrome browser. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067580 Title: Closed windows appear as phantom desktop overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1067580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 694242] Re: Wubi does not check if Windows boots using UEFI
Any update on this bug? Here's a recent request: http://ubuntuforums.org/showthread.php?t=2070760 It seems like this will become a bigger issue soon when Windows 8 is released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/694242 Title: Wubi does not check if Windows boots using UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/wubi/+bug/694242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067580] [NEW] Closed windows appear as phantom desktop overlay
Public bug reported: I'm running Quantal development release up to date. I brought my computer out of sleep to find that the Chrome browser appeared in all four desktop workspaces. I closed the actual open chrome application, but the image of the browser still shows in all four workspaces. I don't know if it affects anything other than chrome and I'm not sure whether it's compiz/unity/whatever so I'm logging this on unity. My first report was marked invalid as I didn't include system info (bug 1067227). I'm including a new snapshot of what my desktop workspace looks like. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CheckboxSubmission: dd7f729683fa7fd3f2e256ba311e86cb CheckboxSystem: d00f84de8a555815fa1c4660280da308 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Tue Oct 16 18:52:25 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0456] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111006) MachineType: Dell Inc. Inspiron N4010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=18B4B7BBB4B799A8 loop=/ubuntu/disks/root.disk ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 021CN3 dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A13 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/31/2011:svnDellInc.:pnInspironN4010:pvrA13:rvnDellInc.:rn021CN3:rvrA13:cvnDellInc.:ct8:cvrA13: dmi.product.name: Inspiron N4010 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 quantal running-unity ubuntu ** Attachment added: phantomdesktop.png https://bugs.launchpad.net/bugs/1067580/+attachment/3400948/+files/phantomdesktop.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067580 Title: Closed windows appear as phantom desktop overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1067580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067227] [NEW] Closed windows appear as phantom desktop overlay
Public bug reported: I'm running Quantal development release up to date. Sometimes application windows that I close appear to be still open, but it's an 'image overlay' on the desktop (on all desktop spaces). I'm including a snapshot as this doesn't make a lot of sense. Basically, it looks like the application window is still there, but it's not. In the attached picture, I am showing all desktop spaces and it appears that a chrome browse window with a google search is present in all of them... but there is no open browser window anywhere and clicking on any of them does nothing. Also, I can open new browser windows that work fine, so it's not a chrome problem. I have seen the same behaviour with other applications than chrome so I believe it's not app specific. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: quantal ** Attachment added: phantomwindows.png https://bugs.launchpad.net/bugs/1067227/+attachment/3399846/+files/phantomwindows.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067227 Title: Closed windows appear as phantom desktop overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1067227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043149] Re: [regression since 12.04] ntfs-3g refuses to mount Windows8 not using hibernation
I still fail to see why this is a bug in wubi or ntfs-3g. The way I see it is that Windows8 chooses to hibernate by default on shutdown (unless fast-start is disabled), without the knowledge of the user. The fact that the user is unaware of it, doesn't change the fact that it's hibernated. So it's correct for ntfs-3g to refuse to mount it. Also, the fact that Microsoft consider Restart a true restart and Shut down a hidden, system hibernation is not intuitive or logical (to me). The problem with Wubi and hybrid sleep, is in my mind a windows 8 bug. Since in this case, it's Shutdown (not restart) that cleans up the mess left behind by the hybrid sleep. Now suddenly Restart is the inferior option that leaves a quasi-hibernated state. Why would it be up to ntfs-3g to try to interpret this mess and what should it do with a system-hibernated state versus a user-hibernated state? For Wubi, it's probably easy enough to check and switch off 'hybrid sleep' to get around the issue, but I think it's unlikely that Microsoft intended this and maybe they'll fix it. References: 1. this shows that Windows 8 shut down is intentionally hibernating http://blogs.msdn.com/b/b8/archive/2011/09/08/delivering-fast-boot-times-in-windows-8.aspx Now here’s the key difference for Windows 8: as in Windows 7, we close the user sessions, but instead of closing the kernel session, we hibernate it. Compared to a full hibernate, which includes a lot of memory pages in use by apps, session 0 hibernation data is much smaller, which takes substantially less time to write to disk. If you’re not familiar with hibernation, we’re effectively saving the system state and memory contents to a file on disk (hiberfil.sys) and then reading that back in on resume and restoring contents back to memory. Using this technique with boot gives us a significant advantage for boot times, since reading the hiberfile in and reinitializing drivers is much faster on most systems (30-70% faster on most systems we’ve tested). 2. That same link talks about Restart being the full reset (which is not the case after hybrid sleep): Also, choosing Restart from the UI will do a full shutdown, followed by a cold boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043149 Title: [regression since 12.04] ntfs-3g refuses to mount Windows8 not using hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1043149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043149] Re: [regression since 12.04] ntfs-3g refuses to mount Windows8 not using hibernation
Okay, I hadn't noticed (or heard about) the bit about 'hybrid sleep'. I switched it on, used the sleep, and then woke up from the sweep. Then I hit Restart and tried to boot into Wubi, but it didn't work. I can't mount the windows partition except in read-only mode. bcbc@neptune:~$ head -c 30 '/mnt/$LogFile' | tail -c 4 | od -t x1 000 01 00 01 00 004 After that I performed a Shutdown from Windows, Wubi boots fine, including on subsequent Restarts from Windows. bcbc@neptune:~$ head -c 30 '/host/$LogFile' | tail -c 4 | od -t x1 000 01 00 01 00 004 After going in to Win8 and doing another Sleep, followed by another Restart, then Wubi won't boot again. So it seems easily reproducible. PS in case it matters, this is what hiberfil.sys looks like: bcbc@neptune:~$ head -c 8 /mnt/hiberfil.sys | od -t x1 000 48 49 42 52 09 00 00 00 010 I'll guess I'll be turning off 'hybrid sleep' now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043149 Title: [regression since 12.04] ntfs-3g refuses to mount Windows8 not using hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1043149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043149] Re: [regression since 12.04] ntfs-3g refuses to mount Windows8 not using hibernation
For a Windows 8 shutdown and booting (non-wubi) Ubuntu, I get: bcbc@neptune:~$ head -c 30 '/mnt/$LogFile' | tail -c 4 | od -t x1 000 00 00 02 00 004 But it won't mount it, except read-only so, in that sense, it's safe. But it would be a pain for a user trying to boot from an Ubuntu USB and trying to partition and install, or someone using Grub. bcbc@neptune:~$ sudo umount /mnt bcbc@neptune:~$ sudo mount /dev/sda1 /mnt Windows is hibernated, refused to mount. Failed to mount '/dev/sda1': Operation not permitted The NTFS partition is hibernated. Please resume and shutdown Windows properly, or mount the volume read-only with the 'ro' mount option, or mount the volume read-write with the 'remove_hiberfile' mount option. For example type on the command line: mount -t ntfs-3g -o remove_hiberfile /dev/sda1 /mnt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043149 Title: [regression since 12.04] ntfs-3g refuses to mount Windows8 not using hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1043149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043149] Re: [regression since 12.04] ntfs-3g refuses to mount Windows8 not using hibernation
I haven't noticed any problems using Wubi or mounting NTFS from normal dual boot (12.04.1) with Windows 8 - fast start is enabled. The following is from a fresh Quantal install using Wubi: bcbc@ubuntu:~$ ls -la /host/hiberfil.sys -rwxrwxrwx 1 root root 5065179136 Sep 19 22:49 /host/hiberfil.sys bcbc@ubuntu:~$ head -c 8 /host/hiberfil.sys | od -t x1 000 57 41 4b 45 09 00 00 00 010 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/1043149 Title: [regression since 12.04] ntfs-3g refuses to mount Windows8 not using hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1043149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043149] Re: [regression since 12.04] ntfs-3g refuses to mount Windows8 not using hibernation
My previous post was after Restarting the computer from Windows 8 and booting into Wubi. The next test was to Shut down from Windows 8 and boot Wubi. That also worked, but I've observed a different behaviour when booting Wubi from Windows 8 manager as compared to Win 7 and that is: 1. Computer starts, BIOS screen 2. Windows boot manager, select Ubuntu(Wubi) 3. Computer restarts, BIOS reappears, boots directly into Ubuntu(Wubi) So it appears that Windows is taking care of the 'fast-start' hibernated image from the Windows Boot Manager when required. (Of course when it's really hibernated it just boots straight into Windows) It's different when I shut down Windows 8 and then boot the non-Wubi install (12.04.1). Then when I try to mount the windows partition I get: bcbc@neptune:~$ sudo mount /dev/sda1 /mnt Windows is hibernated, refused to mount. Failed to mount '/dev/sda1': Operation not permitted bcbc@neptune:~$ sudo mount -r /dev/sda1 /mnt bcbc@neptune:~$ head -c 8 /mnt/hiberfil.sys | od -t x1 000 48 49 42 52 09 00 00 00 010 bcbc@neptune:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043149 Title: [regression since 12.04] ntfs-3g refuses to mount Windows8 not using hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1043149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1009697] Re: Wubi download is in a loop
*** This bug is a duplicate of bug 1009247 *** https://bugs.launchpad.net/bugs/1009247 ** This bug has been marked a duplicate of bug 1009247 Windows installer (wubi.exe) download link doesn't work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1009697 Title: Wubi download is in a loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-website/+bug/1009697/+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
Elijah, open a new issue or look for an existing issue e.g. I think bug 776590 covers this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/947748 Title: Brightness control not working after 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 986272] Re: Update manager doesn't calculate free space correctly for distribution upgrade
Bug 541595 is marked as 'fix released'. So it's no longer active. Also, that bug was to do with an incorrect report that a package was already installed. The other bug 996379 is marked as invalid. This bug is to do with update-manager checking the space required for the release-upgrade incorrectly. Then proceeding with the upgrade only to fail due to lack of free space. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986272 Title: Update manager doesn't calculate free space correctly for distribution upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/986272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986269] Re: Unable to open a folder for 10 GB Filesystem, No application is registered as handling this file... Nautilus pops browser on bash partition mount
I think this is a Unity action, not Nautilus ** Package changed: nautilus (Ubuntu) = unity ** Summary changed: - Unable to open a folder for 10 GB Filesystem, No application is registered as handling this file... Nautilus pops browser on bash partition mount + Unable to open a folder for 10 GB Filesystem, No application is registered as handling this file... or Nautilus pops browser when partition is mounted in bash script ** Description changed: I first noticed this behaviour in Ubuntu 11.10. When I run my bash script that mounts partitions on my hard drive (e.g /dev/sda5), Nautilus pops up with a browser window. This is an illogical action, since I've not 'inserted a drive', it's already there, and it's just been manually mounted. This Nautilus action will interfere with the scripts operation since, when the script tries to unmount the drive (rapidly) it finds that Nautilus is still busy with it, producing it's browser window. If I run chmod 700 on the mountpoint prior to mounting (root only access), then I get a popup message stating: Unable to open a folder for 10 GB Filesystem, No application is registered as handling this file. This is because the mountpoint is not accessible to the logged in user. You wouldn't expect this if you mount a partition from the terminal - and for the most part this is correct (Nautilus does nothing), but not all the time. I've managed to trigger Nautilus to pop just with a simple terminal mount. I have a workaround in my bash script that creates a udev rule and runs udevadm trigger to hide the partition, but this seems extreme. I believe - it's a bug in Nautilus in how it responds to the signal that a partition - has been mounted. + it's a bug in Unity(?) (maybe Nautilus?) in how it responds to the + signal that a partition has been mounted. Please see this for complete details and discussion of possible solutions (and the bash script code): http://askubuntu.com/questions/121569/prevent-nautilus-showing- partition-mounted-in-bash-script I understand you can prevent Nautilus responding to inserted drives etc., but this is definitely not the case here - the drive is already there, just the partition is being mounted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986269 Title: Unable to open a folder for 10 GB Filesystem, No application is registered as handling this file... or Nautilus pops browser when partition is mounted in bash script To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/986269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986269] Re: Unable to open a folder for 10 GB Filesystem, No application is registered as handling this file... Nautilus pops browser on bash partition mount
** Summary changed: - Nautilus pops browser on bash partition mount + Unable to open a folder for 10 GB Filesystem, No application is registered as handling this file... Nautilus pops browser on bash partition mount ** Description changed: I first noticed this behaviour in Ubuntu 11.10. When I run my bash script that mounts partitions on my hard drive (e.g /dev/sda5), Nautilus pops up with a browser window. This is an illogical action, since I've not 'inserted a drive', it's already there, and it's just been manually mounted. This Nautilus action will interfere with the scripts operation since, when the script tries to unmount the drive (rapidly) it finds that Nautilus is still busy with it, producing it's browser window. + + If I run chmod 700 on the mountpoint prior to mounting (root only + access), then I get a popup message stating: Unable to open a folder + for 10 GB Filesystem, No application is registered as handling this + file. This is because the mountpoint is not accessible to the logged in + user. You wouldn't expect this if you mount a partition from the terminal - and for the most part this is correct (Nautilus does nothing), but not all the time. I've managed to trigger Nautilus to pop just with a simple terminal mount. I have a workaround in my bash script that creates a udev rule and runs udevadm trigger to hide the partition, but this seems extreme. I believe it's a bug in Nautilus in how it responds to the signal that a partition has been mounted. Please see this for complete details and discussion of possible solutions (and the bash script code): http://askubuntu.com/questions/121569/prevent-nautilus-showing- partition-mounted-in-bash-script I understand you can prevent Nautilus responding to inserted drives etc., but this is definitely not the case here - the drive is already there, just the partition is being mounted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986269 Title: Unable to open a folder for 10 GB Filesystem, No application is registered as handling this file... Nautilus pops browser on bash partition mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/986269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986269] [NEW] Nautilus pops browser on bash partition mount
Public bug reported: I first noticed this behaviour in Ubuntu 11.10. When I run my bash script that mounts partitions on my hard drive (e.g /dev/sda5), Nautilus pops up with a browser window. This is an illogical action, since I've not 'inserted a drive', it's already there, and it's just been manually mounted. This Nautilus action will interfere with the scripts operation since, when the script tries to unmount the drive (rapidly) it finds that Nautilus is still busy with it, producing it's browser window. You wouldn't expect this if you mount a partition from the terminal - and for the most part this is correct (Nautilus does nothing), but not all the time. I've managed to trigger Nautilus to pop just with a simple terminal mount. I have a workaround in my bash script that creates a udev rule and runs udevadm trigger to hide the partition, but this seems extreme. I believe it's a bug in Nautilus in how it responds to the signal that a partition has been mounted. Please see this for complete details and discussion of possible solutions (and the bash script code): http://askubuntu.com/questions/121569/prevent-nautilus-showing- partition-mounted-in-bash-script I understand you can prevent Nautilus responding to inserted drives etc., but this is definitely not the case here - the drive is already there, just the partition is being mounted. ** Affects: nautilus (Ubuntu) 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/986269 Title: Nautilus pops browser on bash partition mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/986269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986272] [NEW] Update manager doesn't calculate free space correctly for distribution upgrade
Public bug reported: I ran an upgrade from 11.10 to 12.04 with 1.9GB free space. No warning was given about insufficient free space. I received two popup windows during the upgrade informing me that I was low on space and this went down to less than 100MB (as I manually freed up space). The problem may be: 1. ~1800 packages are downloaded (this could be the amount of free space it thinks it needs 2. After upgrading and removing old packages it uses a net amount of ~500MB (this could be the free space it thinks) 3. During unpacking and installing 1800 packages it uses 2GB+ == this is definitely not the amount of space it thinks it needs. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986272 Title: Update manager doesn't calculate free space correctly for distribution upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/986272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986272] Re: Update manager doesn't calculate free space correctly for distribution upgrade
** Attachment added: dist-upgrade.zip https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/986272/+attachment/3096685/+files/dist-upgrade.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986272 Title: Update manager doesn't calculate free space correctly for distribution upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/986272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986272] Re: Update manager doesn't calculate free space correctly for distribution upgrade
2012-04-18 22:18:42,171 DEBUG Free space on /: 1856667648 2012-04-18 22:18:45,900 DEBUG dir '/var/cache/apt/archives' needs '987733436' of 'DistUpgradeCache.FreeSpace object at 0xae731cc' (1856667648.00) 2012-04-18 22:18:45,901 DEBUG dir '/usr' needs '211730432' of 'DistUpgradeCache.FreeSpace object at 0xae731cc' (868934212.00) 2012-04-18 22:18:45,901 DEBUG dir '/usr' needs '52428800' of 'DistUpgradeCache.FreeSpace object at 0xae731cc' (657203780.00) 2012-04-18 22:18:45,901 DEBUG dir '/boot' needs '22345536' of 'DistUpgradeCache.FreeSpace object at 0xae731cc' (604774980.00) 2012-04-18 22:18:45,901 DEBUG dir '/tmp' needs '5242880' of 'DistUpgradeCache.FreeSpace object at 0xae731cc' (582429444.00) 2012-04-18 22:18:45,901 DEBUG dir '/' needs '10485760' of 'DistUpgradeCache.FreeSpace object at 0xae731cc' (577186564.00) 2012-04-18 22:18:45,901 DEBUG dir '/tmp' needs '0.0' of 'DistUpgradeCache.FreeSpace object at 0xae731cc' (566700804.00) 2012-04-18 22:18:45,901 DEBUG dir '/usr' needs '0.0' of 'DistUpgradeCache.FreeSpace object at 0xae731cc' (566700804.00) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986272 Title: Update manager doesn't calculate free space correctly for distribution upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/986272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984598] [NEW] package memtest86+ 4.20-1.1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: I ran a wubi upgrade from 10.04.4 to 12.04. I created a separate bug report for the upgrade in bug 984593. I guess some of the errors I saw are reporting themselves ;) so I'll pass them on ProblemType: Package DistroRelease: Ubuntu 12.04 Package: memtest86+ 4.20-1.1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 ApportVersion: 2.0.1-0ubuntu4 Architecture: i386 Date: Tue Apr 17 23:06:34 2012 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 10.04.4 LTS Lucid Lynx - Release i386 (20120214.2) SourcePackage: memtest86+ Title: package memtest86+ 4.20-1.1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-04-18 (0 days ago) ** Affects: memtest86+ (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984598 Title: package memtest86+ 4.20-1.1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/984598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984598] Re: package memtest86+ 4.20-1.1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984598 Title: package memtest86+ 4.20-1.1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/984598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984601] [NEW] package friendly-recovery 0.2.25 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: Upgraded a wubi install from 10.04.4 to 12.04. I reported the errors (and attached logs) in bug 984593. This is one of those errors that is self-reporting. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: friendly-recovery 0.2.25 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 ApportVersion: 2.0.1-0ubuntu4 Architecture: i386 Date: Tue Apr 17 23:01:16 2012 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 10.04.4 LTS Lucid Lynx - Release i386 (20120214.2) PackageArchitecture: all SourcePackage: friendly-recovery Title: package friendly-recovery 0.2.25 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-04-18 (0 days ago) ** Affects: friendly-recovery (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984601 Title: package friendly-recovery 0.2.25 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/984601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984599] [NEW] package linux-image-3.2.0-23-generic 3.2.0-23.36 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: Upgraded a wubi install from 10.04.4 to 12.04. Got the above error during the install (as I reported in bug 984593). I think this error/bug is probably a false report since I am typing this from the upgraded install and it's running the 3.2.0-23 kernel. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-23-generic 3.2.0-23.36 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu4 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bcbc 1752 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 45' Mixer name : 'SigmaTel STAC9200' Components : 'HDA:83847690,102801bd,00102201 HDA:14f12bfa,14f100c3,0009' Controls : 13 Simple ctrls : 6 Date: Tue Apr 17 23:05:39 2012 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=861537b8-afe7-40c7-8933-13724307c3af InstallationMedia: Ubuntu 10.04.4 LTS Lucid Lynx - Release i386 (20120214.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 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 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Dell Inc. MM061 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=80E4E195E4E18DAA loop=/hostname/disks/root.disk ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 1.99-21ubuntu3 SourcePackage: linux Title: package linux-image-3.2.0-23-generic 3.2.0-23.36 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-04-18 (0 days ago) 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. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984599 Title: package linux-image-3.2.0-23-generic 3.2.0-23.36 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/984599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984601] Re: package friendly-recovery 0.2.25 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984601 Title: package friendly-recovery 0.2.25 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/984601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984599] Re: package linux-image-3.2.0-23-generic 3.2.0-23.36 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984599 Title: package linux-image-3.2.0-23-generic 3.2.0-23.36 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/984599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984602] Re: initctl crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 984474 *** https://bugs.launchpad.net/bugs/984474 ** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984602 Title: initctl crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/984602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984599] Re: package linux-image-3.2.0-23-generic 3.2.0-23.36 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Joseph Salisbury, The bug is about an error I received during the upgrade from 10.04.4 to 12.04. As I said in the description, the error was likely false, since the upgrade worked (and the kernel booted fine). I was testing the Upgrade process at the time (it's a throwaway install). So I'm not sure what running those commands will do to resolve the bug (the point is more that there was an error during an upgrade). So, I'll leave it as 'incomplete' but please explain further if I missed something as to why I need to run those commands and only mark it 'confirmed' if they 'don't fix' something (that I don't think is really broken.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984599 Title: package linux-image-3.2.0-23-generic 3.2.0-23.36 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/984599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980338] Re: gcompris crashed with SIGABRT in mem_error()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980338 Title: gcompris crashed with SIGABRT in mem_error() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcompris/+bug/980338/+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 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 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 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
[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 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 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
[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
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
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 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
[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 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
[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 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 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 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 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 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
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 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 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 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
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
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
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 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
[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 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
