Has liveusb-creator been replaced by Fedora Media Writer? I'm having difficulty installing Knoppix on a stick with the latter, although I had no problem installing an older version of Knoppix on the same USB stick with liveusb-creator some time ago.
The copy now completes without error, but the stick is not seen as a bootable device, and re-booting my ThinkPad T510 ignores the USB stick, and goes to the usual kernel menu.
I read that Fedora Media Writer is able to restore a USB stick to factory setting, but I see no way to do this.
Any suggestions gratefully received.
On 04/29/16 06:26, Timothy Murphy wrote:
Has liveusb-creator been replaced by Fedora Media Writer? I'm having difficulty installing Knoppix on a stick with the latter, although I had no problem installing an older version of Knoppix on the same USB stick with liveusb-creator some time ago.
The copy now completes without error, but the stick is not seen as a bootable device, and re-booting my ThinkPad T510 ignores the USB stick, and goes to the usual kernel menu.
I read that Fedora Media Writer is able to restore a USB stick to factory setting, but I see no way to do this.
Any suggestions gratefully received.
Not sure I understand your query....
[egreshko@meimei ~]$ dnf whatprovides /usr/bin/liveusb-creator Last metadata expiration check: 1 day, 19:40:46 ago on Wed Apr 27 11:11:05 2016. liveusb-creator-3.93.3-1.fc23.noarch : Fedora Media Writer Repo : @System
So, isn't liveusb-creator=Fedora Media Writer ?
Ed Greshko wrote:
Has liveusb-creator been replaced by Fedora Media Writer?
Not sure I understand your query....
[egreshko@meimei ~]$ dnf whatprovides /usr/bin/liveusb-creator Last metadata expiration check: 1 day, 19:40:46 ago on Wed Apr 27 11:11:05 2016. liveusb-creator-3.93.3-1.fc23.noarch : Fedora Media Writer Repo : @System
So, isn't liveusb-creator=Fedora Media Writer ?
But it doesn't look anything like the old liveusb-creator, and in my case it doesn't create a bootable USB stick. Does it work for you?
On Fri, 29 Apr 2016 10:13:56 +0200, Timothy Murphy gayleard@eircom.net wrote:
Ed Greshko wrote:
Has liveusb-creator been replaced by Fedora Media Writer?
Not sure I understand your query....
[egreshko@meimei ~]$ dnf whatprovides /usr/bin/liveusb-creator Last metadata expiration check: 1 day, 19:40:46 ago on Wed Apr 27 11:11:05 2016. liveusb-creator-3.93.3-1.fc23.noarch : Fedora Media Writer Repo : @System
So, isn't liveusb-creator=Fedora Media Writer ?
But it doesn't look anything like the old liveusb-creator, and in my case it doesn't create a bootable USB stick. Does it work for you?
Yes, it was rewritten. Now it uses only dd to write to a flash drive and it indeed is capable of restoring a flash drive containing Fedora to its factory settings. Using it to write other distributions is not a tested use case (at least as of now) - the iso you used probably has a different layout than Fedora iso's which could be the cause of it not detecting your drive for restoring.
I'm the guy responsible for the rewrite so please hit me with any issue or suggestion you have, either directly or through bugzilla or even the upstream github repo [1]
Martin
On Fri, Apr 29, 2016 at 10:20:13 +0200, Martin Bříza mbriza@redhat.com wrote:
Yes, it was rewritten. Now it uses only dd to write to a flash drive and it indeed is capable of restoring a flash drive containing Fedora to its factory settings.
How does it know what the factory settings were? I get the impression it just creates a vfat file system on the device using all of the available space.
On 04/29/2016 11:40 AM, Bruno Wolff III wrote:
How does it know what the factory settings were? I get the impression it just creates a vfat file system on the device using all of the available space.
Isn't that what the factory settings are? When was the last time that you checked a new flash drive that wasn't like that?
On Fri, Apr 29, 2016 at 12:01:45 -0700, Joe Zeff joe@zeff.us wrote:
On 04/29/2016 11:40 AM, Bruno Wolff III wrote:
How does it know what the factory settings were? I get the impression it just creates a vfat file system on the device using all of the available space.
Isn't that what the factory settings are? When was the last time that you checked a new flash drive that wasn't like that?
Factory settings could be anything. It seems weird for a program to claim to set things back to factory settings unless it has some way to look up device ID and find out what they were. Otherwise it would seem to be better to say the drive will be reformatted with a vfat file system or whatever is really going on.
Certainly some drives come with specific data on them. I have gotten some promo ones with logos and some data relevant to the company handing them out.
On Fri, Apr 29, 2016 at 12:40 PM, Bruno Wolff III bruno@wolff.to wrote:
On Fri, Apr 29, 2016 at 10:20:13 +0200, Martin Bříza mbriza@redhat.com wrote:
Yes, it was rewritten. Now it uses only dd to write to a flash drive and it indeed is capable of restoring a flash drive containing Fedora to its factory settings.
How does it know what the factory settings were? I get the impression it just creates a vfat file system on the device using all of the available space.
Factory settings means it will wipe all the isohybrid and bootloader stuff, wipe the ISO 9660 magic, creator a new MBR partition map with a single partition and format that partition as vfat.
On Fri, Apr 29, 2016 at 07:17:57PM -0600, Chris Murphy wrote:
How does it know what the factory settings were? I get the impression it just creates a vfat file system on the device using all of the available space.
Factory settings means it will wipe all the isohybrid and bootloader stuff, wipe the ISO 9660 magic, creator a new MBR partition map with a single partition and format that partition as vfat.
It does seem like there might be a better term than "factory settings".
On Sat, 2016-04-30 at 10:11 -0400, Matthew Miller wrote:
It does seem like there might be a better term than "factory settings".
We used to call that reformatting...
If you want to avoid calling it that, I don't know what a better term will be. Reseting? Erasing.
It's not just being pedantic, but computing requires accuracy *and* the avoidance of inaccuracy. You can't possibly restore some of my USB memory sticks to factory settings unless you restore the files that came on the drive.
To nearly *everybody* restoring to factory settings means exactly a return to how it was when you got it, and that's what they expect. When software does not do what it says, and what people expect, that does cause problems. It also makes the authors look a complete pratt to make ludicrous claims about what their software does.
On Sat, 30 Apr 2016 18:37:21 +0200, Tim ignored_mailbox@yahoo.com.au wrote:
On Sat, 2016-04-30 at 10:11 -0400, Matthew Miller wrote:
It does seem like there might be a better term than "factory settings".
We used to call that reformatting...
If you want to avoid calling it that, I don't know what a better term will be. Reseting? Erasing.
It's not just being pedantic, but computing requires accuracy *and* the avoidance of inaccuracy. You can't possibly restore some of my USB memory sticks to factory settings unless you restore the files that came on the drive.
To nearly *everybody* restoring to factory settings means exactly a return to how it was when you got it, and that's what they expect. When software does not do what it says, and what people expect, that does cause problems. It also makes the authors look a complete pratt to make ludicrous claims about what their software does.
Hi,
I chose "factory settings" because usually when you get a new flash drive, it's FAT formatted. While this is a big simplification, I thought it would be a good one for a user who is not very technically savvy - because that's the person who would be using the tool. Of course, I'm open to discussion about nearly anything regarding FMW so if there is a general consensus we should rewrite some strings inside the app, I'll be glad to do so.
So if you guys agree "reformatting" would be a better choice, I'll go ahead and change the text.
Martin
On Mon, May 02, 2016 at 11:36:24AM +0200, Martin Bříza wrote:
I chose "factory settings" because usually when you get a new flash drive, it's FAT formatted. While this is a big simplification, I thought it would be a good one for a user who is not very technically savvy - because that's the person who would be using the tool. Of course, I'm open to discussion about nearly anything regarding FMW so if there is a general consensus we should rewrite some strings inside the app, I'll be glad to do so.
So if you guys agree "reformatting" would be a better choice, I'll go ahead and change the text.
I guess my inclination would be to just drop this feature entirely. If people want to reformat the drive, they can use whatever regular OS feature to do it. This doesn't need to be a general-purpose drive utility.
On Mon, May 2, 2016 at 9:05 AM, Matthew Miller mattdm@fedoraproject.org wrote:
On Mon, May 02, 2016 at 11:36:24AM +0200, Martin Bříza wrote:
I chose "factory settings" because usually when you get a new flash drive, it's FAT formatted. While this is a big simplification, I thought it would be a good one for a user who is not very technically savvy - because that's the person who would be using the tool. Of course, I'm open to discussion about nearly anything regarding FMW so if there is a general consensus we should rewrite some strings inside the app, I'll be glad to do so.
So if you guys agree "reformatting" would be a better choice, I'll go ahead and change the text.
I guess my inclination would be to just drop this feature entirely. If people want to reformat the drive, they can use whatever regular OS feature to do it. This doesn't need to be a general-purpose drive utility.
The purpose of that feature is to deal with some utilities and OS's that get confused about the distinctly non-standard partition arrangement on the stick and can't fix it themselves.
Certainly on OS X, while it can be fixed by manually finding the less obvious partition option and changing it to 1 partition, most users just want to erase it. But for erasing, three partitions show up in Disk Utility, and all partitions are far less than the size of the stick. So the appearance is that the USB stick is permanently shrunk in a busted way.
On Mon, May 2, 2016 at 4:59 PM, Chris Murphy lists@colorremedies.com wrote:
On Mon, May 2, 2016 at 9:05 AM, Matthew Miller mattdm@fedoraproject.org
wrote:
On Mon, May 02, 2016 at 11:36:24AM +0200, Martin Bříza wrote:
I chose "factory settings" because usually when you get a new flash drive, it's FAT formatted. While this is a big simplification, I thought it would be a good one for a user who is not very technically savvy - because that's the person who would be using the tool. Of course, I'm open to discussion about nearly anything regarding FMW so if there is a general consensus we should rewrite some strings inside the app, I'll be glad to do so.
So if you guys agree "reformatting" would be a better choice, I'll go ahead and change the text.
I guess my inclination would be to just drop this feature entirely. If people want to reformat the drive, they can use whatever regular OS feature to do it. This doesn't need to be a general-purpose drive utility.
The purpose of that feature is to deal with some utilities and OS's that get confused about the distinctly non-standard partition arrangement on the stick and can't fix it themselves.
Certainly on OS X, while it can be fixed by manually finding the less obvious partition option and changing it to 1 partition, most users just want to erase it. But for erasing, three partitions show up in Disk Utility, and all partitions are far less than the size of the stick. So the appearance is that the USB stick is permanently shrunk in a busted way.
I just tried this on OS X 10.11.4, which is the latest version and has a totally different UI in Disk Utility that's the opposite of past Disk Utilities. Erase in fact creates a new single partition and new file system, so the stick works fine. Meanwhile the partitioning UI is really a shrink/grow UI and it gets things totally wrong and confused.
Older versions, you were stuck having to go to partition UI and know to change the popup from Current partition scheme to 1 partition, then click erase.
-- Chris Murphy
On Mon, 02 May 2016 17:05:52 +0200, Matthew Miller mattdm@fedoraproject.org wrote:
On Mon, May 02, 2016 at 11:36:24AM +0200, Martin Bříza wrote:
I chose "factory settings" because usually when you get a new flash drive, it's FAT formatted. While this is a big simplification, I thought it would be a good one for a user who is not very technically savvy - because that's the person who would be using the tool. Of course, I'm open to discussion about nearly anything regarding FMW so if there is a general consensus we should rewrite some strings inside the app, I'll be glad to do so.
So if you guys agree "reformatting" would be a better choice, I'll go ahead and change the text.
I guess my inclination would be to just drop this feature entirely. If people want to reformat the drive, they can use whatever regular OS feature to do it. This doesn't need to be a general-purpose drive utility.
There are platforms where restoring the flash drive is not straightforward and even in Fedora, it's not as simple as it seems. For example, GParted spits a whole bunch of error messages about the flash drive and it also sees it as 4 times bigger than it really is. On the other hand, I think Gnome Disks does its job alright. On Windows, when you click the drive and select "Format", you can only format the first partition of the flash drive which is about 5MB. You would have to open a pretty much hidden drive and partition manager that can do the job but it's not really easy to use.
Over all, I think this functionality is a necessary part of the tool which won't make a regular user feel punished for sacrificing a flash drive for trying Fedora.
On Tue, May 03, 2016 at 01:05:38PM +0200, Martin Bříza wrote:
Over all, I think this functionality is a necessary part of the tool which won't make a regular user feel punished for sacrificing a flash drive for trying Fedora.
Thanks for the explanation. That seems fair enough.
Martin Bříza:
So if you guys agree "reformatting" would be a better choice, I'll go ahead and change the text.
Matthew Miller:
I guess my inclination would be to just drop this feature entirely. If people want to reformat the drive, they can use whatever regular OS feature to do it. This doesn't need to be a general-purpose drive utility.
I think reformat (entire device) is useful, something like that would be a self-descriptive term. Since, as others point out, you can have a multi-partitioned USB device, and dealing with that can be less than obvious without using partitioning software.
While it would be nice to not need another utility, but Fedora makes reformatting things like external drives harder than other OSs, where you can right-click and format a USB drive from the desktop, so I think we do need it. Likewise with renaming drives/partitions (Fedora doesn't let you do it easily, particularly DOS/Windows ones).
Yes, I understand the point of making these an admin/wheel-group restriction, but that ought to be do-able from a right-click and reformat option, not requiring another program to do the job, just pop-up an authentication prompt.
On Fri, 2016-04-29 at 10:20 +0200, Martin Bříza wrote:
I'm the guy responsible for the rewrite so please hit me with any issue or suggestion you have,
Since you asked...
This thread prodded me into opening liveusb-creator, or trying to. I had used it within the last few weeks to create a bootable SD card so I know it was working then.
Now I get a core dump. I have tried opening it via the menu pull down, via command line as user root. In all cases it cores. A sample from a root command line attempt is: # liveusb-creator file:///usr/lib64/qt5/qml/QtQuick/Controls/ComboBox.qml:560:5: QML Menu: Binding loop detected for property "__selectedIndex" QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram::uniformLocation( pixelSize ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram::uniformLocation( pixelSize ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( qt_Matrix ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram::uniformLocation( pixelSize ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( qt_Matrix ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( qt_Matrix ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( textureScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( color ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMin ): shader program is not linked QOpenGLShaderProgram::uniformLocation( alphaMax ): shader program is not linked QOpenGLShaderProgram::uniformLocation( fontScale ): shader program is not linked QOpenGLShaderProgram::uniformLocation( vecDelta ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram::uniformLocation( pixelSize ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram::uniformLocation( pixelSize ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QSGMaterialShader: Shader compilation failed: "" QOpenGLShaderProgram::uniformLocation( matrix ): shader program is not linked QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked QOpenGLShaderProgram::uniformLocation( pixelSize ): shader program is not linked Segmentation fault (core dumped)
On Sat, Apr 30, 2016 at 12:10 AM, Doug H. fedoraproject.org@wombatz.com wrote:
On Fri, 2016-04-29 at 10:20 +0200, Martin Bříza wrote:
I'm the guy responsible for the rewrite so please hit me with any issue or suggestion you have,
Since you asked...
This thread prodded me into opening liveusb-creator, or trying to. I had used it within the last few weeks to create a bootable SD card so I know it was working then.
Now I get a core dump. I have tried opening it via the menu pull down, via command line as user root. In all cases it cores. A sample from a root command line attempt is: # liveusb-creator file:///usr/lib64/qt5/qml/QtQuick/Controls/ComboBox.qml:560:5: QML Menu: Binding loop detected for property "__selectedIndex" QOpenGLShaderProgram: could not create shader program QOpenGLShader: could not create shader QOpenGLShader: could not create shader shader compilation failed: [...]
[...] Segmentation fault (core dumped)
Don't do like this again. If error log is too long, paste it to pastebin services, and provide a link to it.
On Sat, 2016-04-30 at 01:09 +0300, Egor Zaharov wrote:
Don't do like this again. If error log is too long, paste it to pastebin services, and provide a link to it.
Seriously?
A 29K e-mail (20K of body text) is too long in this millennium?
I am happy to adhere to group standards but note that you did not give anything to quantify "too long". I did consider the size of the text pasted and figured it was well within "too" anything.
On Sat, Apr 30, 2016 at 1:34 AM, Doug H. fedoraproject.org@wombatz.com wrote:
I am happy to adhere to group standards but note that you did not give anything to quantify "too long". I did consider the size of the text pasted and figured it was well within "too" anything.
https://fedoraproject.org/wiki/Mailing_list_guidelines#Keep_it_Short
Log outputs is also unpleasant in Mailing lists, because most Email clients will automatically wrap the lines to about 80 column width before sending, using newlines. And I needed to scroll about 5-6 pages to skip your log output in my Gmail.
On Tue, 2016-05-03 at 16:29 +0300, Egor Zaharov wrote:
On Sat, Apr 30, 2016 at 1:34 AM, Doug H. <fedoraproject.org@wombatz.c om> wrote:
I am happy to adhere to group standards but note that you did not give anything to quantify "too long". I did consider the size of the text pasted and figured it was well within "too" anything.
https://fedoraproject.org/wiki/Mailing_list_guidelines#Keep_it_Short
Log outputs is also unpleasant in Mailing lists, because most Email clients will automatically wrap the lines to about 80 column width before sending, using newlines. And I needed to scroll about 5-6 pages to skip your log output in my Gmail.
+1
Even including the log output as an attachment would be better than just dumping it directly into the mail body.
poc
On Fri, Apr 29, 2016 at 3:10 PM, Doug H. fedoraproject.org@wombatz.com wrote:
On Fri, 2016-04-29 at 10:20 +0200, Martin Bříza wrote:
I'm the guy responsible for the rewrite so please hit me with any issue or suggestion you have,
Since you asked...
This thread prodded me into opening liveusb-creator, or trying to. I had used it within the last few weeks to create a bootable SD card so I know it was working then.
Now I get a core dump. I have tried opening it via the menu pull down, via command line as user root. In all cases it cores. A sample from a root command line attempt is:
Could you file a bug against component liveusb-creator and include this output as an attached file, and also attach dmesg output as a file also? Thanks.
Also include in description these versions: uname -r rpm -q liveusb-creator rpm -q qt5-qtquickcontrols
Thanks!
On Fri, 2016-04-29 at 19:25 -0600, Chris Murphy wrote:
On Fri, Apr 29, 2016 at 3:10 PM, Doug H. <fedoraproject.org@wombatz.c om> wrote:
On Fri, 2016-04-29 at 10:20 +0200, Martin Bříza wrote:
I'm the guy responsible for the rewrite so please hit me with any issue or suggestion you have,
Since you asked...
This thread prodded me into opening liveusb-creator, or trying to. I had used it within the last few weeks to create a bootable SD card so I know it was working then.
Now I get a core dump. I have tried opening it via the menu pull down, via command line as user root. In all cases it cores. A sample from a root command line attempt is:
Could you file a bug against component liveusb-creator and include this output as an attached file, and also attach dmesg output as a file also? Thanks.
Also include in description these versions: uname -r rpm -q liveusb-creator rpm -q qt5-qtquickcontrols
Got it opened.
Bug 1331957: https://bugzilla.redhat.com/show_bug.cgi?id=1331957
On Sat, 30 Apr 2016 17:06:15 +0200, Doug H. fedoraproject.org@wombatz.com wrote:
On Fri, 2016-04-29 at 19:25 -0600, Chris Murphy wrote:
On Fri, Apr 29, 2016 at 3:10 PM, Doug H. <fedoraproject.org@wombatz.c om> wrote:
On Fri, 2016-04-29 at 10:20 +0200, Martin Bříza wrote:
I'm the guy responsible for the rewrite so please hit me with any issue or suggestion you have,
Since you asked...
This thread prodded me into opening liveusb-creator, or trying to. I had used it within the last few weeks to create a bootable SD card so I know it was working then.
Now I get a core dump. I have tried opening it via the menu pull down, via command line as user root. In all cases it cores. A sample from a root command line attempt is:
Could you file a bug against component liveusb-creator and include this output as an attached file, and also attach dmesg output as a file also? Thanks.
Also include in description these versions: uname -r rpm -q liveusb-creator rpm -q qt5-qtquickcontrols
Got it opened. Bug 1331957: https://bugzilla.redhat.com/show_bug.cgi?id=1331957
Thank you, I replied in the bugreport.
On 04/28/2016 04:26 PM, Timothy Murphy wrote:
Has liveusb-creator been replaced by Fedora Media Writer? I'm having difficulty installing Knoppix on a stick with the latter, although I had no problem installing an older version of Knoppix on the same USB stick with liveusb-creator some time ago.
The copy now completes without error, but the stick is not seen as a bootable device, and re-booting my ThinkPad T510 ignores the USB stick, and goes to the usual kernel menu.
I read that Fedora Media Writer is able to restore a USB stick to factory setting, but I see no way to do this.
Any suggestions gratefully received.
You can compile it from source. Download from: ftp://bo.mirror.garr.it/1/fedora/linux/updates/testing/24/SRPMS/l/liveusb-creator-3.93.3-1.fc24.src.rpm
On Thu, Apr 28, 2016 at 4:26 PM, Timothy Murphy gayleard@eircom.net wrote:
Has liveusb-creator been replaced by Fedora Media Writer?
Yes, it's undergoing a rewrite so there may be some confusion and bugs in 3.93.3 still.
I'm having difficulty installing Knoppix on a stick with the latter, although I had no problem installing an older version of Knoppix on the same USB stick with liveusb-creator some time ago.
One big thing different right now with the tool is it only uses dd. So any images that expected copying and setup/changing bootloader configuration, isn't happening. There were lots of problems with UEFI and Macs just depending on file copying and reconfiguring the bootloader stuff, so now it's using dd to image the iso file directly to the stick. The two additional consequences of this: a.) no persistent overlay option right now, you'd need to use livecd-iso-to-disk --overlay-size-mb option to create the stick; and b.) it is always destructive, you can't point to a partition on the stick, it will always use the entire stick.
The copy now completes without error, but the stick is not seen as a bootable device, and re-booting my ThinkPad T510 ignores the USB stick, and goes to the usual kernel menu.
I'm not familiar with Knoppix image files so I don't know if they expect the USB tool to do some bootloader configuration. This is actually all a lot harder than it might seem. For example ISO 9660 doesn't use MBR or GPT partitioning, has no boot sector, has 2K sector size, and there's no reliable bootloader for it, so the images actually end up using El Torito to make all of this discoverable and bootable. But that's only going to work with optical drives. If you image that ISO directly to a USB stick, it's not bootable. So Fedora ISO's use isohybrid to write a simultaneously crazy and badass, coherent yet Frankenstein (the monster) MBR+APM+GPT+bootloader jump code that supports BIOS, UEFI, and Apple EFI firmwares on x86_64. It's...amazing.
So it might be that the image you want to use requires more post-write setup than the tool currently supports.
I read that Fedora Media Writer is able to restore a USB stick to factory setting, but I see no way to do this.
I'm pretty sure on Fedora, the tool will only offer this option if it sees the effect of isohybrid in the first few sectors of the stick. This is actually consistent with the image you're using not being made for direct USB writing with dd, it's probably strictly optical, and expects a USB writing tool to make the necessary modification, adding MBR and/or GPT and bootloader.
You can check the image with:
dd if=path/to/iso count=65 2>/dev/null | hexdump -C
If you see zeros through 0x8000, where the values are 01 43 44 30 30 31 01 00 4c 49 4e 55 58 20 20 20 |.CD001..LINUX | then yes it's a strictly ISO 9660 (probably also El Torito).
-
Bruno Wolff III -
Chris Murphy -
Doug H. -
Ed Greshko -
Egor Zaharov -
JD -
Joe Zeff -
Martin Bříza -
Matthew Miller -
Patrick O'Callaghan -
Tim -
Timothy Murphy