[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
The cloning version of usb-creator introduced with Ubuntu Xenial (16.04 LTS) should work also in Trusty. Other cloning tools work, so if you want to bother with this bug, I suggest that you port that version to Trusty. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1798562] Re: After a side by side installation, resized filesystem is corrupted
I did both testcases. There was no error detected in in testcase #1, and no error detected in testcase #2, so things seem to work :-) Details: - There was a test installation of Ubuntu 18.04.1 LTS in a Toshiba laptop with an SSD. - I cloned a Lubuntu 18.10 iso file to a USB pendrive and installed the necessary program packages. - I installed Lubuntu alongside Ubuntu (testcase #2) - I ran testcase #1 - Then I rebooted into the old Ubuntu, and it worked - Finally I rebooted into the new Lubuntu and ran 'sudo e2fsck -f /dev/sda1' and, as expected, there was no complaint. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1798562 Title: After a side by side installation, resized filesystem is corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1767072] Re: At LVM with encryption, there is no text telling to enter the passphrase in the boxes
** Description changed: Installing Kubuntu Bionic 32bit (i386), at LVM with encryption, there is no text telling to enter the passphrase in the boxes, at least not when - using Swedish. This is illustrated with the attached screenshot. + using Swedish. This is illustrated with the attached screenshot, + + how-to-know-to-enter-passphrase.png No showstopper, but I think this makes it hard for a beginner, and I suggest that it can be fixed before the first point release. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.12 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CurrentDesktop: KDE Date: Thu Apr 26 10:40:49 2018 InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash --- LiveMediaBuild: Kubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180425.1) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1767072 Title: At LVM with encryption, there is no text telling to enter the passphrase in the boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767072/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1767072] Re: At LVM with encryption, there is no text telling to enter the passphrase in the boxes
** Description changed: - At LVM with encryption, there is no text telling to enter the passphrase - in the boxes, at least not when using Swedish. This is illustrated with - the attached screenshot. + Installing Kubuntu Bionic 32bit (i386), at LVM with encryption, there is + no text telling to enter the passphrase in the boxes, at least not when + using Swedish. This is illustrated with the attached screenshot. No showstopper, but I think this makes it hard for a beginner, and I suggest that it can be fixed before the first point release. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.12 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CurrentDesktop: KDE Date: Thu Apr 26 10:40:49 2018 InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash --- LiveMediaBuild: Kubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180425.1) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1767072 Title: At LVM with encryption, there is no text telling to enter the passphrase in the boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767072/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1767072] [NEW] At LVM with encryption, there is no text telling to enter the passphrase in the boxes
Public bug reported: At LVM with encryption, there is no text telling to enter the passphrase in the boxes, at least not when using Swedish. This is illustrated with the attached screenshot. No showstopper, but I think this makes it hard for a beginner, and I suggest that it can be fixed before the first point release. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.12 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CurrentDesktop: KDE Date: Thu Apr 26 10:40:49 2018 InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash --- LiveMediaBuild: Kubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180425.1) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 iso-testing kubuntu ubiquity-18.04.12 ** Attachment added: "how-to-know-to-enter-passphrase.png" https://bugs.launchpad.net/bugs/1767072/+attachment/5127498/+files/how-to-know-to-enter-passphrase.png ** Description changed: - At LVM with encryption, there is no text telling to enter the passphrase - in the boxes, at least not when using Swedish. This is illustrated with - the attached screenshot. + In Kubuntu Bionic i386, at LVM with encryption, there is no text telling + to enter the passphrase in the boxes, at least not when using Swedish. + This is illustrated with the attached screenshot. No showstopper, but I think this makes it hard for a beginner, and can it be fixed before the first point release. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.12 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CurrentDesktop: KDE Date: Thu Apr 26 10:40:49 2018 InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash --- LiveMediaBuild: Kubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180425.1) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - In Kubuntu Bionic i386, at LVM with encryption, there is no text telling - to enter the passphrase in the boxes, at least not when using Swedish. - This is illustrated with the attached screenshot. + At LVM with encryption, there is no text telling to enter the passphrase + in the boxes, at least not when using Swedish. This is illustrated with + the attached screenshot. - No showstopper, but I think this makes it hard for a beginner, and can - it be fixed before the first point release. + No showstopper, but I think this makes it hard for a beginner, and I + suggest that it can be fixed before the first point release. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.12 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CurrentDesktop: KDE Date: Thu Apr 26 10:40:49 2018 InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash --- LiveMediaBuild: Kubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180425.1) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1767072 Title: At LVM with encryption, there is no text telling to enter the passphrase in the boxes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767072/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1359689] Re: cryptsetup password prompt not shown
Is this problem depending on the nvidia proprietary graphics driver for new nvidia graphics chips/cards, that some versions of the nvidia drivers will make the system run without the plymouth screen? In that case there is not much we can do except suggesting that you try the free 'nouveau' driver, or try the newest version of Ubuntu, 16.10 (Yakkety Yak) with the newest kernel series and its corresponding graphics drivers. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-debug-installer in Ubuntu. https://bugs.launchpad.net/bugs/1359689 Title: cryptsetup password prompt not shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-debug-installer/+bug/1359689/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1617037] Re: ubiquity crashes in kubuntu beta1
I installed in Swedish and used Swedish time (CET) -- 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/1617037 Title: ubiquity crashes in kubuntu beta1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1617037/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1617037] [NEW] ubiquity crashes in kubuntu beta1
Public bug reported: iso-testing: trying to install kubuntu, into the whole drive, when the installer crashes. Maybe this is a known bug, but I cannot find it right now. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubiquity 16.10.7 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.377 CurrentDesktop: KDE Date: Thu Aug 25 21:03:31 2016 InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash --- LiveMediaBuild: Kubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160819) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu ubiquity-16.10.7 yakkety -- 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/1617037 Title: ubiquity crashes in kubuntu beta1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1617037/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
Yes ndorf, this is the intended behaviour now. The Ubuntu Startup Disk Creator is *cloning* the iso file, which is a much more robust process that the previous method. The easiest method to restore the pendrive to a 'normal' data drive (for storage and transfer of files) is to create a new partition table and file system, for example with mkusb according to the following link https://help.ubuntu.com/community/mkusb/wipe or with gparted according to the following link https://wiki.ubuntu.com/Win32DiskImager/iso2usb/FormatHelp -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
Please take the opportunity to SRU usb-creator-gtk: to replace the current version in Trusty and Wily with version 0.3.2 (which comes with Xenial and should be tested enough to be considered stable now). I think it is a good time to do it now, well in time before making the 'final point release' 14.04.5 LTS and before the Wily end of life, when we can expect many people to try to install the new version(s). The problems with the current version in Trusty and Wily affect booting in BIOS mode, where syslinux is used. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
@lotuspsychje, If you run the Startup Disk Creator in a 16.04 host system, you are running a new version, that should not be affected by this bug, whatever version of the target system you select. But if you run the Startup Disk Creator in a previous version of Ubuntu (host), and try to install a newer version of Ubuntu (target), for example 16.04, you can still be affected, because you are running an old version of the Startup Disk Creator. -o- If my description is wrong, please describe with as much detail as possible how to reproduce the bug in 16.04! -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
You can use another tool until the usb disk creator is debugged and works again. See this link and links from it, https://help.ubuntu.com/community/Installation/FromUSBStick -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
@ Mathieu Trudel-Lapierre "How about instead we just fix the bugs, given that it mostly works for people?" It is very obvious that this is what you want. Maybe the suggestion from Marc Deslauriers at Canonical is the way to go. (You have probably read his post in the ubuntu-quality mailing list) "... I believe a simple way to eliminate every one of these issues at once in UDC would be to get rid of the persistence functionality. All of the currently supported images can now be written directly to a usb device as-is ... Perhaps in the future persistence could be added back by creating a partition in the free space left over after copying over the image." This is pretty much what I do with mkusb. I would be very happy with such things under the hood of the SDC. It will be easy for you to implement cloning. If you want to implement my method to make persistent live drives, I am willing to help and explain. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
@ Mathieu Trudel-Lapierre Does the attached spreadsheet answer some of your questions? And I have filed a bug report about old versions of Unetbootin in the Ubuntu repos: https://bugs.launchpad.net/ubuntu/+source/unetbootin/+bug/1497604 If I missed a question, please ask again :-) ** Attachment added: "SDC-test.ods" https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1325801/+attachment/4469409/+files/SDC-test.ods -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
"That's simply false. Sure, there are some gotchas, but it largely works modulo this bug report. You're not answering the question I asked." Well, there are shades of grey between white and black. Sure, there are several cases, where it works well to use the Startup Disk Creator ;-) I will try to answer your questions, but it will take some time (to test what works and what does not work in and between the currently supported versions of Ubuntu). Let us hope that the SDC is much better now than we think at the Ubuntu Forums :-) "Architecture matching is unfortunately an unavoidable issue." Yes, for the SDC. But it does not create any problems at all for tools which use cloning with dd or cp under the hood (like mkusb and Disks). And I think the other tools in our poll can manage this issue. At least Unetbootin from the developer's PPA can manage it, and I recently added 'making persistent live drives' to mkusb, and I have tested that it works for all the current Ubuntu versions, flavours and also several re-spins based on Ubuntu. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
'Opinion' from the Ubuntu Forums: S-D-C is borked - it's useless to create live USB's of either older or newer versions of Ubuntu than the version you're running S-D-C on. And the proposed fix that made it into Vivid and got backported into Utopic resulted in S-D-C being able to only produce live USB's of the same architecture. My comment: This is not only a corner case, it is a severe bug. But the main problem is not a few single bugs, red or grey (at the iso qa tracker), but the never ending stream of bugs that is affecting this poor piece of software. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
If I understand correctly, the current release (in the trusty/proposed ppa) should not be made official. Yu Ning's patch, now available via their own account at Launchpad should be tested by some more people and then uploaded. See post #138. It means that I would '+1' for that patch, but not for the current release(in the trusty/proposed ppa). -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
I see, and I agree :-) So let us wait for comments from other people. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
So it works with the patch according to case b) in the previous post (#138), and you think it will work for all combinations of i386 and amd64 architectures according to case c). Are you able / have you got time enough to make a patch for case c) too, or should we ask someone else to make it? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
Yes, I was trying to flash the Lubuntu 15.04 desktop i386 iso file (that I iso-tested recently) from an Ubuntu 14.04.2 LTS amd64 installed system and I expected that it should work too :-P I'll check if it works to flash an amd64 iso file from my Ubuntu 14.04.2 LTS amd64 installed system with the Startup Disk Creator. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
Comment #117: Hello shijing, or anyone else affected, Accepted usb-creator into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/usb- creator/0.2.56.3ubuntu0.2 in a few hours, and then in the -proposed repository. Comment #130: ello shijing, or anyone else affected, Accepted usb-creator into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/usb-creator/0.2.38.3ubuntu0.2 - The version numbers are confusing. Is version 0.2.38.3ubuntu0.2 newer (and improved) compared to version 0.2.56.3ubuntu0.2 ? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
I tried Yu Ning's bug-fix in the live Ubuntu 14.04.2 LTS system, but it failed too (like the result in comment #119). -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
I tried Yu Ning's bug-fix, but it did not help me. usb-creater-gtk failed with the same error message (running an installed Ubuntu 14.04.2 LTS system as in comment #118). Something is different between our systems. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
Let us hope that Yu Ning's fix and Erick Bunzell's old bug report address the same problem, and that there is only this bug to squash to get this poor bug-ridden program working again. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
I tried also from a live session of Ubuntu 14.04.2 LTS booted from ubuntu-14.04.2-desktop-amd64.iso where I made the proposed repository available and installed usb- creator-gtk from it. 'Nothing else' was changed from the content of the iso file. It still fails to install the bootloader and exits with the same message window (as when trying in the installed system), "Failed to install the bootloader. [Quit]" -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
Computer: http://www.toshiba.se/laptops/satellite-pro/c850/satellite- pro-c850-19w/ I have used it for iso-testing of trusty, utopic and vivid - so I know that it is compatible with Ubuntu and Lubuntu. I tested to install Lubuntu 15.04 from the desktop 32-bit bit iso file with usb-creator-gtk in a system installed from ubuntu-14.04.2-desktop-amd64.iso added deb http://archive.ubuntu.com/ubuntu/ trusty-proposed restricted main multiverse universe to /etc/apt/sources.list and updated/dist-upgraded to make the system completely up to date. This bug affected the installation before adding the proposed repository. The version of usb-creator-gtk from 'proposed' fails to install the bootloader. The version that comes with 14.04.2 LTS could install the bootloader but suffers from this bug (1325801). I tried again after wiping the drive separately (new partition table and new FAT32 partition), unmount, un-plug and re-plug the pendrive for usb- creator-gtk to work, but it failed again. I started with the installed system running via USB 3, which works with Unetbootin and mkusb. I moved the SSD to the internal bay, and tried again, but I still had the same problem. Maybe this is a problem with the authentication method? Or a problem with chroot (if that is used)? Anyway, I tried to boot from the pendrive, which seems to have 'all the files' but not the bootloader. But it does not work, I get a flashing cursor at the top left corner of the screen. Finally I tried to create a pendrive without persistence. But usb- creator-gtk still fails when trying to install the bootloader. I do not feel authorized to change any tag. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
I've tried 'Disks' alias gnome-disks in Lubuntu 14.04.1 and Vivid. I could make it create an iso file from a partition, but not from the whole drive. Trying from the whole drive gave me an error both running as a regular user and with sudo. (I tested with a Tiny Core iso file, which is small so it was fast.) When I restored from the image of the partition I got a working boot drive. (I cloned the Ubuntu mini.iso in between so that the pendrive was changed.) I think this is not logical (and not corresponding to how dd is used). Restoring a partition should not restore the whole drive, but I guess it is intended to work this way. I could make it flash, clone alias 'restore' a boot USB drive from another iso file (I tested with the Ubuntu mini.iso (because it is small so it was fast). -o- Conclusion: I'm glad that I learned about this feature of 'Disks'. It is certainly possible to use in order to make a USB boot drive. There is an extra 'final warning window', so it should be safe enough to use. And best of all, it offers a working solution, when the Startup Disk Creator suffers from this really bad bug (# 1325801) plus several minor bugs. -o- But of course, I still think that my mkusb is better ;-) One important extra feature of mkusb is the ability to use general compressed image files (an iso file often contains the compressed container squashfs, but is not itself compressed). Another extra feature of mkusb is the ability to check if the content of the iso file matches that of the pendrive, and suggest updating for iso-testing. And there are several informative windows including a final warning with red background. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
Hi Marc (mbbs) In the cases where dd does not make a bootable drive for you, there is another problem. This bug does not affect the dd method. Please describe your problem in detail at the Ubuntu Forums and I think you can receive help from there. -o- I tried a couple of days ago. Unetbootin worked. This bug was still there in updated 12.04.5 and 14.04.1 systems affecting attempts to boot 14.10 with pendrives prepared with the Ubuntu Startup Disk Creator. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
@pa_card: If you got this error with the dd method: 'no syslinux.bin', I think you copied/flashed/cloned the iso file to a partition rather than to the whole drive. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:
I checked that the current 'utopic-desktop-i386.iso' works when flashed to USB with mkusb., which it should according to comment #49 by elfy - dd works. -o- What about the alternatives from Windows? If there are problems with Unetbootin, I would guess that http://sourceforge.net/projects/win32diskimager/ will work (because it copies/flashes/clones the iso file in the same way as dd in linux). -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1325801 Title: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1325801/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
