Is anyone else having trouble with liveusb-creator gui. It downloads ok but it will not show up afterwards. Help will be greatly appreciated.
On Sun, 25 Sep 2016 06:58:33 -0600 Lawrence E Graves lgraves95@gmail.com wrote:
Is anyone else having trouble with liveusb-creator gui. It downloads ok but it will not show up afterwards. Help will be greatly appreciated.
I assume that you want to make a bootable livecd iso? If not, then ignore. If yes, then you could consider using the simpler and more reliable commandline option:
# in order to make a bootable cd, etc, on the commandline:
sudo dd if=path-to-iso.iso of=/dev/sdb bs=1M
# In the above, if (input file) has path-to-iso.iso is the location of your iso. For example: /tmp/Fedora.iso
# Note: only the letter-drive is to be included in the of (output file) i.e. /dev/sdb not inclusive of the numeral /dev/sdb1.
HTH, Ranjan
____________________________________________________________ FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family! Visit http://www.inbox.com/photosharing to find out more!
On 09/25/2016 08:10 AM, Ranjan Maitra wrote:
On Sun, 25 Sep 2016 06:58:33 -0600 Lawrence E Graves lgraves95@gmail.com wrote:
Is anyone else having trouble with liveusb-creator gui. It downloads ok but it will not show up afterwards. Help will be greatly appreciated.
I assume that you want to make a bootable livecd iso? If not, then ignore. If yes, then you could consider using the simpler and more reliable commandline option:
# in order to make a bootable cd, etc, on the commandline:
sudo dd if=path-to-iso.iso of=/dev/sdb bs=1M
# In the above, if (input file) has path-to-iso.iso is the location of your iso. For example: /tmp/Fedora.iso
# Note: only the letter-drive is to be included in the of (output file) i.e. /dev/sdb not inclusive of the numeral /dev/sdb1.
HTH, Ranjan
FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family! Visit http://www.inbox.com/photosharing to find out more!
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
No. I trying to use my liveusb-creator to make a bootable usb drive. The liveusb-creator will flash on desktop and then dissapear. I am trying to solve that problem.
On 09/25/16 20:58, Lawrence E Graves wrote:
Is anyone else having trouble with liveusb-creator gui. It downloads ok but it will not show up afterwards. Help will be greatly appreciated.
Haven't used it recently.... But starting it from the command line produces some output for me ending in ....
QOpenGLShaderProgram::uniformLocation( vecDelta ): 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)
This on a fully updated F24 system.
On 09/25/2016 08:31 AM, Ed Greshko wrote:
On 09/25/16 20:58, Lawrence E Graves wrote:
Is anyone else having trouble with liveusb-creator gui. It downloads ok but it will not show up afterwards. Help will be greatly appreciated.
Haven't used it recently.... But starting it from the command line produces some output for me ending in ....
QOpenGLShaderProgram::uniformLocation( vecDelta ): 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)
This on a fully updated F24 system.
Now that you have showed me this, what is my next move. I am not as tech savvy as you are therefore I need to know exactly what is need to make my liveusb-creator appear on my desktop to be used. Thank you.
On Sun, 25 Sep 2016 08:15:38 -0600 Lawrence E Graves lgraves95@gmail.com wrote:
On 09/25/2016 08:10 AM, Ranjan Maitra wrote:
On Sun, 25 Sep 2016 06:58:33 -0600 Lawrence E Graves lgraves95@gmail.com wrote:
Is anyone else having trouble with liveusb-creator gui. It downloads ok but it will not show up afterwards. Help will be greatly appreciated.
I assume that you want to make a bootable livecd iso? If not, then ignore. If yes, then you could consider using the simpler and more reliable commandline option:
# in order to make a bootable cd, etc, on the commandline:
sudo dd if=path-to-iso.iso of=/dev/sdb bs=1M
# In the above, if (input file) has path-to-iso.iso is the location of your iso. For example: /tmp/Fedora.iso
# Note: only the letter-drive is to be included in the of (output file) i.e. /dev/sdb not inclusive of the numeral /dev/sdb1.
No. I trying to use my liveusb-creator to make a bootable usb drive. The liveusb-creator will flash on desktop and then dissapear. I am trying to solve that problem.
My suggestion will create a bootable usb drive.
Ranjan
____________________________________________________________ FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth
On 09/25/2016 09:07 AM, Ranjan Maitra wrote:
On Sun, 25 Sep 2016 08:15:38 -0600 Lawrence E Graves lgraves95@gmail.com wrote:
On 09/25/2016 08:10 AM, Ranjan Maitra wrote:
On Sun, 25 Sep 2016 06:58:33 -0600 Lawrence E Graves lgraves95@gmail.com wrote:
Is anyone else having trouble with liveusb-creator gui. It downloads ok but it will not show up afterwards. Help will be greatly appreciated.
I assume that you want to make a bootable livecd iso? If not, then ignore. If yes, then you could consider using the simpler and more reliable commandline option:
# in order to make a bootable cd, etc, on the commandline:
sudo dd if=path-to-iso.iso of=/dev/sdb bs=1M
# In the above, if (input file) has path-to-iso.iso is the location of your iso. For example: /tmp/Fedora.iso
# Note: only the letter-drive is to be included in the of (output file) i.e. /dev/sdb not inclusive of the numeral /dev/sdb1.
No. I trying to use my liveusb-creator to make a bootable usb drive. The liveusb-creator will flash on desktop and then dissapear. I am trying to solve that problem.
My suggestion will create a bootable usb drive.
Ranjan
FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
I don't deny that it will work but it doesn't make any sense to me. I am not technical enough to do that. I don't understand.
On Sun, 25 Sep 2016 09:10:54 -0600 Lawrence E Graves lgraves95@gmail.com wrote:
On 09/25/2016 09:07 AM, Ranjan Maitra wrote:
On Sun, 25 Sep 2016 08:15:38 -0600 Lawrence E Graves lgraves95@gmail.com wrote:
On 09/25/2016 08:10 AM, Ranjan Maitra wrote:
On Sun, 25 Sep 2016 06:58:33 -0600 Lawrence E Graves lgraves95@gmail.com wrote:
Is anyone else having trouble with liveusb-creator gui. It downloads ok but it will not show up afterwards. Help will be greatly appreciated.
I assume that you want to make a bootable livecd iso? If not, then ignore. If yes, then you could consider using the simpler and more reliable commandline option:
# in order to make a bootable cd, etc, on the commandline:
sudo dd if=path-to-iso.iso of=/dev/sdb bs=1M
# In the above, if (input file) has path-to-iso.iso is the location of your iso. For example: /tmp/Fedora.iso
# Note: only the letter-drive is to be included in the of (output file) i.e. /dev/sdb not inclusive of the numeral /dev/sdb1.
No. I trying to use my liveusb-creator to make a bootable usb drive. The liveusb-creator will flash on desktop and then dissapear. I am trying to solve that problem.
My suggestion will create a bootable usb drive.
Ranjan
FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop! Check it out at http://www.inbox.com/earth
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
I don't deny that it will work but it doesn't make any sense to me. I am not technical enough to do that. I don't understand.
Hi,
Unless I have misunderstood what you are trying to do, the steps are exactly what I have written down. The only two things you have to fill out in the commandline are the if= and the of= arguments. If you need help with that, please post back and we shall see if we can help.
Best wishes, Ranjan
____________________________________________________________ FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family! Visit http://www.inbox.com/photosharing to find out more!
On Sun, 25 Sep 2016 08:45:21 -0600 Lawrence E Graves lgraves95@gmail.com wrote:
Now that you have showed me this, what is my next move. I am not as tech savvy as you are therefore I need to know exactly what is need to make my liveusb-creator appear on my desktop to be used. Thank you.
You might be running the wrong OS if you aren't tech savvy or interested in becoming so. :-) But that is your choice.
The program liveusb-creator is a python script. The python package that provides the shader functionality is python2-pyopengl. You could try installing that package, and see if liveusb-creator will then work. It's possible that the dependencies for the package liveusb-creator aren't correct, so that all the needed dependencies weren't installed along with it when you installed it. The package maintainer probably never noticed because he or she had them already installed. If installing python2-pyopengl works, you should open a bugzilla at https://bugzilla.redhat.com/ against liveusb-creator and let them know that there is this error in their package dependencies (for the next non-technical person who tries to use this package). If it doesn't work, I'm at a loss. You could try starting it from the command line (in a terminal, in X, as root), type /usr/bin/liveusb-creator and hit enter. The error will then put a traceback to the terminal, telling you what went wrong. Post it here.
Are you running this as root? I see in the script that it won't run as a user.
For what it's worth, it runs fine here when I run it as root, but I have lots of development, and other, packages installed, so I might have finessed the problem you are having.
On 09/25/2016 09:57 AM, stan wrote:
On Sun, 25 Sep 2016 08:45:21 -0600 Lawrence E Graves lgraves95@gmail.com wrote:
Now that you have showed me this, what is my next move. I am not as tech savvy as you are therefore I need to know exactly what is need to make my liveusb-creator appear on my desktop to be used. Thank you.
You might be running the wrong OS if you aren't tech savvy or interested in becoming so. :-) But that is your choice.
The program liveusb-creator is a python script. The python package that provides the shader functionality is python2-pyopengl. You could try installing that package, and see if liveusb-creator will then work. It's possible that the dependencies for the package liveusb-creator aren't correct, so that all the needed dependencies weren't installed along with it when you installed it. The package maintainer probably never noticed because he or she had them already installed. If installing python2-pyopengl works, you should open a bugzilla at https://bugzilla.redhat.com/ against liveusb-creator and let them know that there is this error in their package dependencies (for the next non-technical person who tries to use this package). If it doesn't work, I'm at a loss. You could try starting it from the command line (in a terminal, in X, as root), type /usr/bin/liveusb-creator and hit enter. The error will then put a traceback to the terminal, telling you what went wrong. Post it here.
Are you running this as root? I see in the script that it won't run as a user.
For what it's worth, it runs fine here when I run it as root, but I have lots of development, and other, packages installed, so I might have finessed the problem you are having. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
This the results of what you just told me. Hope it makes sense to you.
[root@Jehovah ~]# /usr/bin/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:""
On 09/25/2016 07:15 AM, Lawrence E Graves wrote:
No. I trying to use my liveusb-creator to make a bootable usb drive. The liveusb-creator will flash on desktop and then dissapear. I am trying to solve that problem.
In that case, try running it from a terminal to see what errors it's reporting.
On 09/25/2016 10:42 AM, Joe Zeff wrote:
On 09/25/2016 07:15 AM, Lawrence E Graves wrote:
No. I trying to use my liveusb-creator to make a bootable usb drive. The liveusb-creator will flash on desktop and then dissapear. I am trying to solve that problem.
In that case, try running it from a terminal to see what errors it's reporting. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
I just did that and posted it.Thank you for your concern.
On 25 September 2016 at 18:06, Lawrence E Graves lgraves95@gmail.com wrote:
This the results of what you just told me. Hope it makes sense to you.
[root@Jehovah ~]# /usr/bin/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:""
A shot in the dark, try running it as user, not root: liveusb-creator_polkit
this should show a polkit dialogue where you have to type your root password to authenticate.
On 09/25/2016 12:45 PM, Ahmad Samir wrote:
On 25 September 2016 at 18:06, Lawrence E Graves lgraves95@gmail.com wrote:
This the results of what you just told me. Hope it makes sense to you.
[root@Jehovah ~]# /usr/bin/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:""
A shot in the dark, try running it as user, not root: liveusb-creator_polkit
this should show a polkit dialogue where you have to type your root password to authenticate. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
This is what happen when I did what you asked.
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::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 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 /usr/bin/liveusb-creator_polkit: line 6: 5163 Segmentation fault (core dumped) pkexec --disable-internal-agent "/usr/bin/liveusb-creator" "$@" [lawrence69@Jehovah ~]$
On 09/25/2016 12:50 PM, Lawrence E Graves wrote:
On 09/25/2016 12:45 PM, Ahmad Samir wrote:
On 25 September 2016 at 18:06, Lawrence E Graves lgraves95@gmail.com wrote:
This the results of what you just told me. Hope it makes sense to you.
[root@Jehovah ~]# /usr/bin/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:""
A shot in the dark, try running it as user, not root: liveusb-creator_polkit
this should show a polkit dialogue where you have to type your root password to authenticate. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
This is what happen when I did what you asked.
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::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 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 /usr/bin/liveusb-creator_polkit: line 6: 5163 Segmentation fault (core dumped) pkexec --disable-internal-agent "/usr/bin/liveusb-creator" "$@" [lawrence69@Jehovah ~]$
When I run liveusb-creator as root:
# liveusb-creator Qt: Session management error: None of the authentication protocols specified are supported /org/freedesktop/UDisks2/block_devices/sdb
and the GUI interface pops up and it works.
On 09/25/2016 01:01 PM, jd1008 wrote:
On 09/25/2016 12:50 PM, Lawrence E Graves wrote:
On 09/25/2016 12:45 PM, Ahmad Samir wrote:
On 25 September 2016 at 18:06, Lawrence E Graves lgraves95@gmail.com wrote:
This the results of what you just told me. Hope it makes sense to you.
[root@Jehovah ~]# /usr/bin/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:""
A shot in the dark, try running it as user, not root: liveusb-creator_polkit
this should show a polkit dialogue where you have to type your root password to authenticate. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
This is what happen when I did what you asked.
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::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 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 /usr/bin/liveusb-creator_polkit: line 6: 5163 Segmentation fault (core dumped) pkexec --disable-internal-agent "/usr/bin/liveusb-creator" "$@" [lawrence69@Jehovah ~]$
When I run liveusb-creator as root:
# liveusb-creator Qt: Session management error: None of the authentication protocols specified are supported /org/freedesktop/UDisks2/block_devices/sdb
and the GUI interface pops up and it works. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
I get the same results. It doesn't make sense to me. I have never had any trouble with it before.
On 09/25/2016 01:14 PM, Lawrence E Graves wrote:
On 09/25/2016 01:01 PM, jd1008 wrote:
On 09/25/2016 12:50 PM, Lawrence E Graves wrote:
On 09/25/2016 12:45 PM, Ahmad Samir wrote:
On 25 September 2016 at 18:06, Lawrence E Graves lgraves95@gmail.com wrote:
This the results of what you just told me. Hope it makes sense to you.
[root@Jehovah ~]# /usr/bin/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:""
A shot in the dark, try running it as user, not root: liveusb-creator_polkit
this should show a polkit dialogue where you have to type your root password to authenticate. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
This is what happen when I did what you asked.
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: ...
When I run liveusb-creator as root:
# liveusb-creator Qt: Session management error: None of the authentication protocols specified are supported /org/freedesktop/UDisks2/block_devices/sdb
and the GUI interface pops up and it works. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
I get the same results. It doesn't make sense to me. I have never had any trouble with it before.
I think the problem might be that liveusb-creator is trying to communicate with /bin/dbus-daemon and fails.
On 09/25/2016 01:38 PM, jd1008 wrote:
On 09/25/2016 01:14 PM, Lawrence E Graves wrote:
On 09/25/2016 01:01 PM, jd1008 wrote:
On 09/25/2016 12:50 PM, Lawrence E Graves wrote:
On 09/25/2016 12:45 PM, Ahmad Samir wrote:
On 25 September 2016 at 18:06, Lawrence E Graves lgraves95@gmail.com wrote:
This the results of what you just told me. Hope it makes sense to you.
[root@Jehovah ~]# /usr/bin/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:""
A shot in the dark, try running it as user, not root: liveusb-creator_polkit
this should show a polkit dialogue where you have to type your root password to authenticate. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
This is what happen when I did what you asked.
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: ...
When I run liveusb-creator as root:
# liveusb-creator Qt: Session management error: None of the authentication protocols specified are supported /org/freedesktop/UDisks2/block_devices/sdb
and the GUI interface pops up and it works. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
I get the same results. It doesn't make sense to me. I have never had any trouble with it before.
I think the problem might be that liveusb-creator is trying to communicate with /bin/dbus-daemon and fails. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Is there a way to fix that or will I have to wait until they fix it with an update?
On 09/25/2016 01:41 PM, Lawrence E Graves wrote:
On 09/25/2016 01:38 PM, jd1008 wrote:
On 09/25/2016 01:14 PM, Lawrence E Graves wrote:
On 09/25/2016 01:01 PM, jd1008 wrote:
On 09/25/2016 12:50 PM, Lawrence E Graves wrote:
On 09/25/2016 12:45 PM, Ahmad Samir wrote:
On 25 September 2016 at 18:06, Lawrence E Graves lgraves95@gmail.com wrote: > This the results of what you just told me. Hope it makes sense > to you. > > [root@Jehovah ~]# /usr/bin/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:"" > A shot in the dark, try running it as user, not root: liveusb-creator_polkit
this should show a polkit dialogue where you have to type your root password to authenticate. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
This is what happen when I did what you asked.
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: ...
When I run liveusb-creator as root:
# liveusb-creator Qt: Session management error: None of the authentication protocols specified are supported /org/freedesktop/UDisks2/block_devices/sdb
and the GUI interface pops up and it works. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
I get the same results. It doesn't make sense to me. I have never had any trouble with it before.
I think the problem might be that liveusb-creator is trying to communicate with /bin/dbus-daemon and fails. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Is there a way to fix that or will I have to wait until they fix it with an update?
What version of fedora are you using?
On 09/25/2016 01:41 PM, Lawrence E Graves wrote:
On 09/25/2016 01:38 PM, jd1008 wrote:
On 09/25/2016 01:14 PM, Lawrence E Graves wrote:
On 09/25/2016 01:01 PM, jd1008 wrote:
On 09/25/2016 12:50 PM, Lawrence E Graves wrote:
On 09/25/2016 12:45 PM, Ahmad Samir wrote:
On 25 September 2016 at 18:06, Lawrence E Graves lgraves95@gmail.com wrote: > This the results of what you just told me. Hope it makes sense > to you. > > [root@Jehovah ~]# /usr/bin/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:"" > A shot in the dark, try running it as user, not root: liveusb-creator_polkit
this should show a polkit dialogue where you have to type your root password to authenticate. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
This is what happen when I did what you asked.
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: ...
When I run liveusb-creator as root:
# liveusb-creator Qt: Session management error: None of the authentication protocols specified are supported /org/freedesktop/UDisks2/block_devices/sdb
and the GUI interface pops up and it works. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
I get the same results. It doesn't make sense to me. I have never had any trouble with it before.
I think the problem might be that liveusb-creator is trying to communicate with /bin/dbus-daemon and fails. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Is there a way to fix that or will I have to wait until they fix it with an update?
I should have also asked: are you at liberty to say in more detail what you want to put on the USB? For example, is it an iso file? a directory of software including the boot sector, ...etc
On 09/25/2016 01:54 PM, jd1008 wrote:
On 09/25/2016 01:41 PM, Lawrence E Graves wrote:
On 09/25/2016 01:38 PM, jd1008 wrote:
On 09/25/2016 01:14 PM, Lawrence E Graves wrote:
On 09/25/2016 01:01 PM, jd1008 wrote:
On 09/25/2016 12:50 PM, Lawrence E Graves wrote:
On 09/25/2016 12:45 PM, Ahmad Samir wrote: > On 25 September 2016 at 18:06, Lawrence E Graves > lgraves95@gmail.com wrote: >> This the results of what you just told me. Hope it makes sense >> to you. >> >> [root@Jehovah ~]# /usr/bin/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:"" >> > A shot in the dark, try running it as user, not root: > liveusb-creator_polkit > > this should show a polkit dialogue where you have to type your root > password to authenticate. > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-leave@lists.fedoraproject.org This is what happen when I did what you asked.
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: ...
When I run liveusb-creator as root:
# liveusb-creator Qt: Session management error: None of the authentication protocols specified are supported /org/freedesktop/UDisks2/block_devices/sdb
and the GUI interface pops up and it works. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
I get the same results. It doesn't make sense to me. I have never had any trouble with it before.
I think the problem might be that liveusb-creator is trying to communicate with /bin/dbus-daemon and fails. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Is there a way to fix that or will I have to wait until they fix it with an update?
I should have also asked: are you at liberty to say in more detail what you want to put on the USB? For example, is it an iso file? a directory of software including the boot sector, ...etc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Yes, I was trying to load a usb drive with Fedora 25 Alpha to try it out.
On 09/25/2016 01:53 PM, jd1008 wrote:
On 09/25/2016 01:41 PM, Lawrence E Graves wrote:
On 09/25/2016 01:38 PM, jd1008 wrote:
On 09/25/2016 01:14 PM, Lawrence E Graves wrote:
On 09/25/2016 01:01 PM, jd1008 wrote:
On 09/25/2016 12:50 PM, Lawrence E Graves wrote:
On 09/25/2016 12:45 PM, Ahmad Samir wrote: > On 25 September 2016 at 18:06, Lawrence E Graves > lgraves95@gmail.com wrote: >> This the results of what you just told me. Hope it makes sense >> to you. >> >> [root@Jehovah ~]# /usr/bin/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:"" >> > A shot in the dark, try running it as user, not root: > liveusb-creator_polkit > > this should show a polkit dialogue where you have to type your root > password to authenticate. > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-leave@lists.fedoraproject.org This is what happen when I did what you asked.
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: ...
When I run liveusb-creator as root:
# liveusb-creator Qt: Session management error: None of the authentication protocols specified are supported /org/freedesktop/UDisks2/block_devices/sdb
and the GUI interface pops up and it works. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
I get the same results. It doesn't make sense to me. I have never had any trouble with it before.
I think the problem might be that liveusb-creator is trying to communicate with /bin/dbus-daemon and fails. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Is there a way to fix that or will I have to wait until they fix it with an update?
What version of fedora are you using? _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Fedora 24
On 09/25/2016 02:17 PM, Lawrence E Graves wrote:
On 09/25/2016 01:54 PM, jd1008 wrote:
On 09/25/2016 01:41 PM, Lawrence E Graves wrote:
On 09/25/2016 01:38 PM, jd1008 wrote:
On 09/25/2016 01:14 PM, Lawrence E Graves wrote:
On 09/25/2016 01:01 PM, jd1008 wrote:
On 09/25/2016 12:50 PM, Lawrence E Graves wrote: > > > On 09/25/2016 12:45 PM, Ahmad Samir wrote: >> On 25 September 2016 at 18:06, Lawrence E Graves >> lgraves95@gmail.com wrote: >>> This the results of what you just told me. Hope it makes sense >>> to you. >>> >>> [root@Jehovah ~]# /usr/bin/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:"" >>> >> A shot in the dark, try running it as user, not root: >> liveusb-creator_polkit >> >> this should show a polkit dialogue where you have to type your >> root >> password to authenticate. >> _______________________________________________ >> users mailing list -- users@lists.fedoraproject.org >> To unsubscribe send an email to >> users-leave@lists.fedoraproject.org > This is what happen when I did what you asked. > > 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: > ... When I run liveusb-creator as root:
# liveusb-creator Qt: Session management error: None of the authentication protocols specified are supported /org/freedesktop/UDisks2/block_devices/sdb
and the GUI interface pops up and it works. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
I get the same results. It doesn't make sense to me. I have never had any trouble with it before.
I think the problem might be that liveusb-creator is trying to communicate with /bin/dbus-daemon and fails. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Is there a way to fix that or will I have to wait until they fix it with an update?
I should have also asked: are you at liberty to say in more detail what you want to put on the USB? For example, is it an iso file? a directory of software including the boot sector, ...etc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Yes, I was trying to load a usb drive with Fedora 25 Alpha to try it out.
In that case, assuming your USB has enough room, all you need to do is sudo dd if=<full-path-name-fedora25-iso> of=/dev/sd?? bs=16M
where /dev/sd?? is the pathname to the usb device. Notice that '<' and '>' are not part of the iso file pathname.
If some time later you want to make use of the USB as an ordinary disk (for read and write), all you need do is sudo dd if=/dev/zero of=/dev/sd?? bs=16M where /dev/sd?? is the pathname to the usb device.
Reason why you neeed to dd /dev/zero into the usb device if you want to read/write it as a regular disk, is that after you dd the iso image into it, fedora will only recognize it as a read only optical device.
Good luck
On 09/25/2016 02:27 PM, jd1008 wrote:
On 09/25/2016 02:17 PM, Lawrence E Graves wrote:
On 09/25/2016 01:54 PM, jd1008 wrote:
On 09/25/2016 01:41 PM, Lawrence E Graves wrote:
On 09/25/2016 01:38 PM, jd1008 wrote:
On 09/25/2016 01:14 PM, Lawrence E Graves wrote:
On 09/25/2016 01:01 PM, jd1008 wrote: > > On 09/25/2016 12:50 PM, Lawrence E Graves wrote: >> >> >> On 09/25/2016 12:45 PM, Ahmad Samir wrote: >>> On 25 September 2016 at 18:06, Lawrence E Graves >>> lgraves95@gmail.com wrote: >>>> This the results of what you just told me. Hope it makes >>>> sense to you. >>>> >>>> [root@Jehovah ~]# /usr/bin/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:"" >>>> >>> A shot in the dark, try running it as user, not root: >>> liveusb-creator_polkit >>> >>> this should show a polkit dialogue where you have to type your >>> root >>> password to authenticate. >>> _______________________________________________ >>> users mailing list -- users@lists.fedoraproject.org >>> To unsubscribe send an email to >>> users-leave@lists.fedoraproject.org >> This is what happen when I did what you asked. >> >> 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: >> ... > When I run liveusb-creator as root: > > # liveusb-creator > Qt: Session management error: None of the authentication > protocols specified are supported > /org/freedesktop/UDisks2/block_devices/sdb > > and the GUI interface pops up > and it works. > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-leave@lists.fedoraproject.org I get the same results. It doesn't make sense to me. I have never had any trouble with it before.
I think the problem might be that liveusb-creator is trying to communicate with /bin/dbus-daemon and fails. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Is there a way to fix that or will I have to wait until they fix it with an update?
I should have also asked: are you at liberty to say in more detail what you want to put on the USB? For example, is it an iso file? a directory of software including the boot sector, ...etc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Yes, I was trying to load a usb drive with Fedora 25 Alpha to try it out.
In that case, assuming your USB has enough room, all you need to do is sudo dd if=<full-path-name-fedora25-iso> of=/dev/sd?? bs=16M
where /dev/sd?? is the pathname to the usb device. Notice that '<' and '>' are not part of the iso file pathname.
If some time later you want to make use of the USB as an ordinary disk (for read and write), all you need do is sudo dd if=/dev/zero of=/dev/sd?? bs=16M where /dev/sd?? is the pathname to the usb device.
Reason why you neeed to dd /dev/zero into the usb device if you want to read/write it as a regular disk, is that after you dd the iso image into it, fedora will only recognize it as a read only optical device.
Good luck _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Unless I did something wrong, that didn't work either. This the results:
[root@Jehovah ~]# dd if=<full-path-name-fedora25-iso> of=/dev/sd?? bs=16M -bash: full-path-name-fedora25-iso: No such file or directory [root@Jehovah ~]# dd if= full-path-name-fedora25-iso of=/dev/sd?? bs=16M dd: unrecognized operand ‘full-path-name-fedora25-iso’ Try 'dd --help' for more information. [root@Jehovah ~]# dd if=<full-path-name-fedora25-iso> of=/home/lawrence69/Downloads bs=16M -bash: full-path-name-fedora25-iso: No such file or directory [root@Jehovah ~]# [root@Jehovah ~]# dd if=<full-path-name-fedora25-iso> of=/home/lawrence69/Downloads bs=16M -bash: full-path-name-fedora25-iso: No such file or directory [root@Jehovah ~]# dd if= full-path-name-fedora25-iso of=/home/lawrence69/Downloads bs=16M dd: unrecognized operand ‘full-path-name-fedora25-iso’ Try 'dd --help' for more information. [root@Jehovah ~]# dd if=/dev/zero of=/dev/sd?? bs=16M dd: error writing '/dev/sd??': No space left on device 751+0 records in 750+0 records out 12598886400 bytes (13 GB, 12 GiB) copied, 3.37454 s, 3.7 GB/s [
On 09/25/2016 02:59 PM, Lawrence E Graves wrote:
On 09/25/2016 02:27 PM, jd1008 wrote:
On 09/25/2016 02:17 PM, Lawrence E Graves wrote:
On 09/25/2016 01:54 PM, jd1008 wrote:
On 09/25/2016 01:41 PM, Lawrence E Graves wrote:
On 09/25/2016 01:38 PM, jd1008 wrote:
On 09/25/2016 01:14 PM, Lawrence E Graves wrote: > > > On 09/25/2016 01:01 PM, jd1008 wrote: >> >> On 09/25/2016 12:50 PM, Lawrence E Graves wrote: >>> >>> >>> On 09/25/2016 12:45 PM, Ahmad Samir wrote: >>>> On 25 September 2016 at 18:06, Lawrence E Graves >>>> lgraves95@gmail.com wrote: >>>>> This the results of what you just told me. Hope it makes >>>>> sense to you. >>>>> >>>>> [root@Jehovah ~]# /usr/bin/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:"" >>>>> >>>> A shot in the dark, try running it as user, not root: >>>> liveusb-creator_polkit >>>> >>>> this should show a polkit dialogue where you have to type >>>> your root >>>> password to authenticate. >>>> _______________________________________________ >>>> users mailing list -- users@lists.fedoraproject.org >>>> To unsubscribe send an email to >>>> users-leave@lists.fedoraproject.org >>> This is what happen when I did what you asked. >>> >>> 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: >>> ... >> When I run liveusb-creator as root: >> >> # liveusb-creator >> Qt: Session management error: None of the authentication >> protocols specified are supported >> /org/freedesktop/UDisks2/block_devices/sdb >> >> and the GUI interface pops up >> and it works. >> _______________________________________________ >> users mailing list -- users@lists.fedoraproject.org >> To unsubscribe send an email to >> users-leave@lists.fedoraproject.org > I get the same results. It doesn't make sense to me. I have > never had any trouble with it before. > I think the problem might be that liveusb-creator is trying to communicate with /bin/dbus-daemon and fails. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Is there a way to fix that or will I have to wait until they fix it with an update?
I should have also asked: are you at liberty to say in more detail what you want to put on the USB? For example, is it an iso file? a directory of software including the boot sector, ...etc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Yes, I was trying to load a usb drive with Fedora 25 Alpha to try it out.
In that case, assuming your USB has enough room, all you need to do is sudo dd if=<full-path-name-fedora25-iso> of=/dev/sd?? bs=16M
where /dev/sd?? is the pathname to the usb device. Notice that '<' and '>' are not part of the iso file pathname.
If some time later you want to make use of the USB as an ordinary disk (for read and write), all you need do is sudo dd if=/dev/zero of=/dev/sd?? bs=16M where /dev/sd?? is the pathname to the usb device.
Reason why you neeed to dd /dev/zero into the usb device if you want to read/write it as a regular disk, is that after you dd the iso image into it, fedora will only recognize it as a read only optical device.
Good luck _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Unless I did something wrong, that didn't work either. This the results:
[root@Jehovah ~]# dd if=<full-path-name-fedora25-iso> of=/dev/sd?? bs=16M -bash: full-path-name-fedora25-iso: No such file or directory [root@Jehovah ~]# dd if= full-path-name-fedora25-iso of=/dev/sd?? bs=16M dd: unrecognized operand ‘full-path-name-fedora25-iso’ Try 'dd --help' for more information. [root@Jehovah ~]# dd if=<full-path-name-fedora25-iso> of=/home/lawrence69/Downloads bs=16M -bash: full-path-name-fedora25-iso: No such file or directory [root@Jehovah ~]# [root@Jehovah ~]# dd if=<full-path-name-fedora25-iso> of=/home/lawrence69/Downloads bs=16M -bash: full-path-name-fedora25-iso: No such file or directory [root@Jehovah ~]# dd if= full-path-name-fedora25-iso of=/home/lawrence69/Downloads bs=16M dd: unrecognized operand ‘full-path-name-fedora25-iso’ Try 'dd --help' for more information. [root@Jehovah ~]# dd if=/dev/zero of=/dev/sd?? bs=16M dd: error writing '/dev/sd??': No space left on device 751+0 records in 750+0 records out 12598886400 bytes (13 GB, 12 GiB) copied, 3.37454 s, 3.7 GB/s [
You did NOT read and UNDERSTAND my message. <full-path-name-fedora25-iso> means that you are to substitute it for the ACTUAL full pathname of the ACTUAL iso file. For example, on my machine, the pathname to a sample iso file is: /sdd1/Linux/Fedora/fc24/Fedora-Workstation-Live-x86_64-24-1.2.iso
and the pathname to the usb flash drive is /dev/sdd
So, you need to understand a little more about Linux lingo.
On 09/25/2016 03:40 PM, jd1008 wrote:
On 09/25/2016 02:59 PM, Lawrence E Graves wrote:
On 09/25/2016 02:27 PM, jd1008 wrote:
On 09/25/2016 02:17 PM, Lawrence E Graves wrote:
On 09/25/2016 01:54 PM, jd1008 wrote:
On 09/25/2016 01:41 PM, Lawrence E Graves wrote:
On 09/25/2016 01:38 PM, jd1008 wrote: > > > On 09/25/2016 01:14 PM, Lawrence E Graves wrote: >> >> >> On 09/25/2016 01:01 PM, jd1008 wrote: >>> >>> On 09/25/2016 12:50 PM, Lawrence E Graves wrote: >>>> >>>> >>>> On 09/25/2016 12:45 PM, Ahmad Samir wrote: >>>>> On 25 September 2016 at 18:06, Lawrence E Graves >>>>> lgraves95@gmail.com wrote: >>>>>> This the results of what you just told me. Hope it makes >>>>>> sense to you. >>>>>> >>>>>> [root@Jehovah ~]# /usr/bin/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:"" >>>>>> >>>>> A shot in the dark, try running it as user, not root: >>>>> liveusb-creator_polkit >>>>> >>>>> this should show a polkit dialogue where you have to type >>>>> your root >>>>> password to authenticate. >>>>> _______________________________________________ >>>>> users mailing list -- users@lists.fedoraproject.org >>>>> To unsubscribe send an email to >>>>> users-leave@lists.fedoraproject.org >>>> This is what happen when I did what you asked. >>>> >>>> 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: >>>> ... >>> When I run liveusb-creator as root: >>> >>> # liveusb-creator >>> Qt: Session management error: None of the authentication >>> protocols specified are supported >>> /org/freedesktop/UDisks2/block_devices/sdb >>> >>> and the GUI interface pops up >>> and it works. >>> _______________________________________________ >>> users mailing list -- users@lists.fedoraproject.org >>> To unsubscribe send an email to >>> users-leave@lists.fedoraproject.org >> I get the same results. It doesn't make sense to me. I have >> never had any trouble with it before. >> > I think the problem might be that liveusb-creator > is trying to communicate with /bin/dbus-daemon > and fails. > _______________________________________________ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-leave@lists.fedoraproject.org Is there a way to fix that or will I have to wait until they fix it with an update?
I should have also asked: are you at liberty to say in more detail what you want to put on the USB? For example, is it an iso file? a directory of software including the boot sector, ...etc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Yes, I was trying to load a usb drive with Fedora 25 Alpha to try it out.
In that case, assuming your USB has enough room, all you need to do is sudo dd if=<full-path-name-fedora25-iso> of=/dev/sd?? bs=16M
where /dev/sd?? is the pathname to the usb device. Notice that '<' and '>' are not part of the iso file pathname.
If some time later you want to make use of the USB as an ordinary disk (for read and write), all you need do is sudo dd if=/dev/zero of=/dev/sd?? bs=16M where /dev/sd?? is the pathname to the usb device.
Reason why you neeed to dd /dev/zero into the usb device if you want to read/write it as a regular disk, is that after you dd the iso image into it, fedora will only recognize it as a read only optical device.
Good luck _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Unless I did something wrong, that didn't work either. This the results:
[root@Jehovah ~]# dd if=<full-path-name-fedora25-iso> of=/dev/sd?? bs=16M -bash: full-path-name-fedora25-iso: No such file or directory [root@Jehovah ~]# dd if= full-path-name-fedora25-iso of=/dev/sd?? bs=16M dd: unrecognized operand ‘full-path-name-fedora25-iso’ Try 'dd --help' for more information. [root@Jehovah ~]# dd if=<full-path-name-fedora25-iso> of=/home/lawrence69/Downloads bs=16M -bash: full-path-name-fedora25-iso: No such file or directory [root@Jehovah ~]# [root@Jehovah ~]# dd if=<full-path-name-fedora25-iso> of=/home/lawrence69/Downloads bs=16M -bash: full-path-name-fedora25-iso: No such file or directory [root@Jehovah ~]# dd if= full-path-name-fedora25-iso of=/home/lawrence69/Downloads bs=16M dd: unrecognized operand ‘full-path-name-fedora25-iso’ Try 'dd --help' for more information. [root@Jehovah ~]# dd if=/dev/zero of=/dev/sd?? bs=16M dd: error writing '/dev/sd??': No space left on device 751+0 records in 750+0 records out 12598886400 bytes (13 GB, 12 GiB) copied, 3.37454 s, 3.7 GB/s [
You did NOT read and UNDERSTAND my message.
<full-path-name-fedora25-iso> means that you are to substitute it for the ACTUAL full pathname of the ACTUAL iso file. For example, on my machine, the pathname to a sample iso file is: /sdd1/Linux/Fedora/fc24/Fedora-Workstation-Live-x86_64-24-1.2.iso
and the pathname to the usb flash drive is /dev/sdd
So, you need to understand a little more about Linux lingo. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
That is what I have been saying from the beginning. I am good with the hardware and simple install software after that it become hard. If I am taken step by step I get it but I will not waste anyone's time trying to do that so I try to get a simple command or commands and pray it works. I truly thank you for your time today.
On 09/25/16 22:45, Lawrence E Graves wrote:
On 09/25/2016 08:31 AM, Ed Greshko wrote:
On 09/25/16 20:58, Lawrence E Graves wrote:
Is anyone else having trouble with liveusb-creator gui. It downloads ok but it will not show up afterwards. Help will be greatly appreciated.
Haven't used it recently.... But starting it from the command line produces some output for me ending in ....
QOpenGLShaderProgram::uniformLocation( vecDelta ): 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)
This on a fully updated F24 system.
Now that you have showed me this, what is my next move. I am not as tech savvy as you are therefore I need to know exactly what is need to make my liveusb-creator appear on my desktop to be used. Thank you.
Are you nVidia hardware and the nVidia drivers from rpmfusion?
Yes.
On 09/25/2016 03:56 PM, Ed Greshko wrote:
On 09/25/16 22:45, Lawrence E Graves wrote:
On 09/25/2016 08:31 AM, Ed Greshko wrote:
On 09/25/16 20:58, Lawrence E Graves wrote:
Is anyone else having trouble with liveusb-creator gui. It downloads ok but it will not show up afterwards. Help will be greatly appreciated.
Haven't used it recently.... But starting it from the command line produces some output for me ending in ....
QOpenGLShaderProgram::uniformLocation( vecDelta ): 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)
This on a fully updated F24 system.
Now that you have showed me this, what is my next move. I am not as tech savvy as you are therefore I need to know exactly what is need to make my liveusb-creator appear on my desktop to be used. Thank you.
Are you nVidia hardware and the nVidia drivers from rpmfusion?
On Sun, Sep 25, 2016 at 02:59:59PM -0600, Lawrence E Graves wrote:
Unless I did something wrong, that didn't work either. This the results:
[root@Jehovah ~]# dd if=<full-path-name-fedora25-iso> of=/dev/sd?? bs=16M -bash: full-path-name-fedora25-iso: No such file or directory
Lawrence, this has nothing to do with hardware vs software. Nor command line inexperience. It has to do with common sense.
If I told you to address an US Mail envelope as
<name of recipient> <address of recipient>
Would you literally write that on the envelope?
What about
John Doe 1234 Main St
I suspect you would also recognize those as placeholders for your actual data which we have no way of knowing.
Jon
On 09/25/2016 04:23 PM, Jon LaBadie wrote:
On Sun, Sep 25, 2016 at 02:59:59PM -0600, Lawrence E Graves wrote:
Unless I did something wrong, that didn't work either. This the results:
[root@Jehovah ~]# dd if=<full-path-name-fedora25-iso> of=/dev/sd?? bs=16M -bash: full-path-name-fedora25-iso: No such file or directory
Lawrence, this has nothing to do with hardware vs software. Nor command line inexperience. It has to do with common sense.
If I told you to address an US Mail envelope as
<name of recipient> <address of recipient>Would you literally write that on the envelope?
What about
John Doe 1234 Main StI suspect you would also recognize those as placeholders for your actual data which we have no way of knowing.
Jon
[root@Jehovah Downloads]# ls '~' Fedora-Workstation-Live-x86_64-25_Alpha-2.iso VMware-Workstation-Full-12.5.0-4352439.x86_64.bundle [root@Jehovah Downloads]# dd if=Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda1 bs=16M dd: error writing '/dev/sda1': No space left on device 32+0 records in 31+0 records out 524288000 bytes (524 MB, 500 MiB) copied, 1.26722 s, 414 MB/s [root@Jehovah Downloads]# dd if= Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda1 bs=16M dd: unrecognized operand ‘Fedora-Workstation-Live-x86_64-25_Alpha-2.iso’ Try 'dd --help' for more information. [
On 09/26/16 06:07, Lawrence E Graves wrote:
Yes.
On 09/25/2016 03:56 PM, Ed Greshko wrote:
On 09/25/16 22:45, Lawrence E Graves wrote:
On 09/25/2016 08:31 AM, Ed Greshko wrote:
On 09/25/16 20:58, Lawrence E Graves wrote:
Is anyone else having trouble with liveusb-creator gui. It downloads ok but it will not show up afterwards. Help will be greatly appreciated.
Haven't used it recently.... But starting it from the command line produces some output for me ending in ....
QOpenGLShaderProgram::uniformLocation( vecDelta ): 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)
This on a fully updated F24 system.
Now that you have showed me this, what is my next move. I am not as tech savvy as you are therefore I need to know exactly what is need to make my liveusb-creator appear on my desktop to be used. Thank you.
Are you nVidia hardware and the nVidia drivers from rpmfusion?
OK.... I'm pretty sure therein lies the problem.
Works fine for me on a VBox Virtual Machine but not on any nVidia/rpmfusion system. The clue being "OpenGLShade".
Not sure if they will accept a bugzilla in this case.
So, 3 choices....
1. Revert to nouveau for your video driver. 2. Run liveusb-creator in a Virtual Machine. 3. Use dd as others have suggested
On Sun, 25 Sep 2016 10:06:01 -0600 Lawrence E Graves lgraves95@gmail.com wrote:
On 09/25/2016 09:57 AM, stan wrote:
The program liveusb-creator is a python script. The python package that provides the shader functionality is python2-pyopengl. You could try installing that package, and see if liveusb-creator will then work.
Did you do this? You didn't say in your response.
This the results of what you just told me. Hope it makes sense to you.
[root@Jehovah ~]# /usr/bin/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:""
If you installed the python2-pyopengl package and you are still getting the same errors, that isn't the solution to your shader problem. I don't know how to help at this point, but I see you are receiving lots of other help. It's possible that Ed has hit the nail on the head, and it is the proprietary Nvidia driver causing the problem. Did liveusb-creator ever work with the Nvidia driver as you have it set up now (in an earlier Fedora)? I'm using the radeon driver, so would not hit any error due to nvidia.
[root@Jehovah Downloads]# dd if=Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda1 bs=16M dd: error writing '/dev/sda1': No space left on device 32+0 records in 31+0 records out 524288000 bytes (524 MB, 500 MiB) copied, 1.26722 s, 414 MB/s
Lawrence, for installing based on the information above try:
dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda bs=1M status=progress
for your understanding... the "./" in front of the filename notes your location to the system as "in my current directory" but irregardless the illegal operand came from the space between the "=" and the "F" in your second attempt. The first failure of running out of space is because dd was directed to a partition sda1. Also, be sure this is your usb drive, my experience is that sda is usually the hard drive. Broken down sda1 is: "sd"=serial device,"a" [or b,c,d,e,f, etc] is the devices in sequence as discovered, "1" [or 2,3,4, etc] are the partitions on the device. With that try the following command WITHOUT the usb plugged in:
ls /dev/sd*
which should give you something like:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3
Then re-run the same command WITH the usb plugged in which should give you something like:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sdb /dev/sdb1
This last letter to appear is the one you want and without the number. So be REAL sure you have your usb device letter correct and:
dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sdb bs=1M status=progress
will work.
If you want to easily understand the command line I suggest you go through this quick course:
It is a great primer for understanding all we are talking about and can be done in about an evening.
Caution: "dd" is an aggressive program so be sure of the variables you writing to in the "of=" parts of the command. Also, the "status=progress" part is optional, lets you see your progress of the command.
HTH
Fred
Hi Lawrence.
I had the same problem.
My personal solution is based on this discussion from th PYQT mailing list
https://riverbankcomputing.com/pipermail/pyqt/2014-January/033681.html
Basically, you have to add a line to the file /usr/bin/liveusb-creator It is in /usr/bin, therefore you will have to open it up with a text editor from ruot or sudo
Around the 22nd line, between import sys
from liveusb import _
you have to add the line "from OpenGL import GL"
It will look like
import os import sys from OpenGL import GL from liveusb import _
Save it and use as normal. It works well for me, I have been able to use livesusb-creator several time after that. Just a reminder, you will have to do that everytime you reinstall or update liveusb-creator until the the problem is fixed on the mainstream code.
JP
On Sun, Sep 25, 2016 at 9:15 PM, fred roller fredroller66@gmail.com wrote:
[root@Jehovah Downloads]# dd if=Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda1 bs=16M dd: error writing '/dev/sda1': No space left on device 32+0 records in 31+0 records out 524288000 bytes (524 MB, 500 MiB) copied, 1.26722 s, 414 MB/s
Lawrence, for installing based on the information above try:
dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda bs=1M status=progress
for your understanding... the "./" in front of the filename notes your location to the system as "in my current directory" but irregardless the illegal operand came from the space between the "=" and the "F" in your second attempt. The first failure of running out of space is because dd was directed to a partition sda1. Also, be sure this is your usb drive, my experience is that sda is usually the hard drive. Broken down sda1 is: "sd"=serial device,"a" [or b,c,d,e,f, etc] is the devices in sequence as discovered, "1" [or 2,3,4, etc] are the partitions on the device. With that try the following command WITHOUT the usb plugged in:
ls /dev/sd*
which should give you something like:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3
Then re-run the same command WITH the usb plugged in which should give you something like:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sdb /dev/sdb1
This last letter to appear is the one you want and without the number. So be REAL sure you have your usb device letter correct and:
dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sdb bs=1M status=progress
will work.
If you want to easily understand the command line I suggest you go through this quick course:
It is a great primer for understanding all we are talking about and can be done in about an evening.
Caution: "dd" is an aggressive program so be sure of the variables you writing to in the "of=" parts of the command. Also, the "status=progress" part is optional, lets you see your progress of the command.
HTH
Fred
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 09/26/16 12:15, Javier Perez wrote:
you have to add the line "from OpenGL import GL"
It will look like
import os import sys from OpenGL import GL from liveusb import _
Save it and use as normal. It works well for me, I have been able to use livesusb-creator several time after that.
I can confirm that it also works on my nVidia systems as well.
Thanks...
Thank you very much. It works. Have a blessed day
From: Javier Perez [mailto:pepebuho@gmail.com] Sent: September 25, 2016 10:15 PM To: Community support for Fedora users users@lists.fedoraproject.org Subject: Re: liveusb-creator
Hi Lawrence.
I had the same problem.
My personal solution is based on this discussion from th PYQT mailing list
https://riverbankcomputing.com/pipermail/pyqt/2014-January/033681.html
Basically, you have to add a line to the file /usr/bin/liveusb-creator
It is in /usr/bin, therefore you will have to open it up with a text editor from ruot or sudo
Around the 22nd line, between
import sys
from liveusb import _
you have to add the line "from OpenGL import GL"
It will look like
import os import sys from OpenGL import GL from liveusb import _
Save it and use as normal.
It works well for me, I have been able to use livesusb-creator several time after that.
Just a reminder, you will have to do that everytime you reinstall or update liveusb-creator until the the problem is fixed on the mainstream code.
JP
On Sun, Sep 25, 2016 at 9:15 PM, fred roller <fredroller66@gmail.com mailto:fredroller66@gmail.com > wrote:
[root@Jehovah Downloads]# dd if=Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda1 bs=16M dd: error writing '/dev/sda1': No space left on device 32+0 records in 31+0 records out 524288000 bytes (524 MB, 500 MiB) copied, 1.26722 s, 414 MB/s
Lawrence, for installing based on the information above try:
dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda bs=1M status=progress
for your understanding... the "./" in front of the filename notes your location to the system as "in my current directory" but irregardless the illegal operand came from the space between the "=" and the "F" in your second attempt. The first failure of running out of space is because dd was directed to a partition sda1. Also, be sure this is your usb drive, my experience is that sda is usually the hard drive. Broken down sda1 is: "sd"=serial device,"a" [or b,c,d,e,f, etc] is the devices in sequence as discovered, "1" [or 2,3,4, etc] are the partitions on the device. With that try the following command WITHOUT the usb plugged in:
ls /dev/sd*
which should give you something like:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3
Then re-run the same command WITH the usb plugged in which should give you something like:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sdb /dev/sdb1
This last letter to appear is the one you want and without the number. So be REAL sure you have your usb device letter correct and:
dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sdb bs=1M status=progress
will work.
If you want to easily understand the command line I suggest you go through this quick course:
It is a great primer for understanding all we are talking about and can be done in about an evening.
Caution: "dd" is an aggressive program so be sure of the variables you writing to in the "of=" parts of the command. Also, the "status=progress" part is optional, lets you see your progress of the command.
HTH
Fred
_______________________________________________ users mailing list -- users@lists.fedoraproject.org mailto:users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org mailto:users-leave@lists.fedoraproject.org
On Sun, 25 Sep 2016 16:31:44 +0200, Ed Greshko ed.greshko@greshko.com wrote:
On 09/25/16 20:58, Lawrence E Graves wrote:
Is anyone else having trouble with liveusb-creator gui. It downloads ok but it will not show up afterwards. Help will be greatly appreciated.
Haven't used it recently.... But starting it from the command line produces some output for me ending in ....
QOpenGLShaderProgram::uniformLocation( vecDelta ): 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)
This on a fully updated F24 system.
Hello, using Qt applications with closed-source graphics drivers is currently not possible unfortunately. I think there is some work going on to enable it in Qt but that's generally not a setup we support in Fedora.
Please also note that the "liveusb-creator" package will get deprecated in favor of "mediawriter" that looks virtually the same as the previous tool and provides the same set of features but is will be supported in the future.
On Mon, 26 Sep 2016 11:42:45 +0200, Martin Bříza mbriza@redhat.com wrote:
On Sun, 25 Sep 2016 16:31:44 +0200, Ed Greshko ed.greshko@greshko.com wrote:
On 09/25/16 20:58, Lawrence E Graves wrote:
Is anyone else having trouble with liveusb-creator gui. It downloads ok but it will not show up afterwards. Help will be greatly appreciated.
Haven't used it recently.... But starting it from the command line produces some output for me ending in ....
QOpenGLShaderProgram::uniformLocation( vecDelta ): 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)
This on a fully updated F24 system.
Hello, using Qt applications with closed-source graphics drivers is currently not possible unfortunately. I think there is some work going on to enable it in Qt but that's generally not a setup we support in Fedora.
Please also note that the "liveusb-creator" package will get deprecated in favor of "mediawriter" that looks virtually the same as the previous tool and provides the same set of features but is will be supported in the future. _______________________________________________
Also from what I've seen from the other emails in this thread, this issue may be related only to Python applications. mediawriter is C++ so it could work better for you.
Den 2016-09-26 kl. 11:47, skrev Martin Bříza:
On Mon, 26 Sep 2016 11:42:45 +0200, Martin Bříza mbriza@redhat.com wrote:
Please also note that the "liveusb-creator" package will get deprecated in favor of "mediawriter" that looks virtually the same as the previous tool and provides the same set of features but is will be supported in the future.
Also from what I've seen from the other emails in this thread, this issue may be related only to Python applications. mediawriter is C++ so it could work better for you. _______________________________________________
Just one question regarding "mediawriter" and "liveusb-creator". can they coexist or need I to remove "liveusb-creator" if I want to install "mediawriter"?
On Mon, 26 Sep 2016 12:34:58 +0200, Jon Ingason jon.ingason@telia.com wrote:
Den 2016-09-26 kl. 11:47, skrev Martin Bříza:
On Mon, 26 Sep 2016 11:42:45 +0200, Martin Bříza mbriza@redhat.com wrote:
Please also note that the "liveusb-creator" package will get deprecated in favor of "mediawriter" that looks virtually the same as the previous tool and provides the same set of features but is will be supported in the future.
Also from what I've seen from the other emails in this thread, this issue may be related only to Python applications. mediawriter is C++ so it could work better for you. _______________________________________________
Just one question regarding "mediawriter" and "liveusb-creator". can they coexist or need I to remove "liveusb-creator" if I want to install "mediawriter"?
They definitely can coexist. It'll be just a bit confusing that both are called "Fedora Media Writer" in the application menu and have the same icon. This is the reason mediawriter is basically a rewrite of liveusb-creator.
Don't know if it's related but there is a bug in Qt with the Nvidia drivers that break liveusb-creator.
On 09/25/2016 08:15 PM, fred roller wrote:
[root@Jehovah Downloads]# dd if=Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda1 bs=16M dd: error writing '/dev/sda1': No space left on device 32+0 records in 31+0 records out 524288000 bytes (524 MB, 500 MiB) copied, 1.26722 s, 414 MB/s
Lawrence, for installing based on the information above try:
dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda bs=1M status=progress
for your understanding... the "./" in front of the filename notes your location to the system as "in my current directory" but irregardless the illegal operand came from the space between the "=" and the "F" in your second attempt. The first failure of running out of space is because dd was directed to a partition sda1. Also, be sure this is your usb drive, my experience is that sda is usually the hard drive. Broken down sda1 is: "sd"=serial device,"a" [or b,c,d,e,f, etc] is the devices in sequence as discovered, "1" [or 2,3,4, etc] are the partitions on the device. With that try the following command WITHOUT the usb plugged in:
ls /dev/sd*
which should give you something like:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3
Then re-run the same command WITH the usb plugged in which should give you something like:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sdb /dev/sdb1
This last letter to appear is the one you want and without the number. So be REAL sure you have your usb device letter correct and:
dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sdb bs=1M status=progress
will work.
If you want to easily understand the command line I suggest you go through this quick course:
It is a great primer for understanding all we are talking about and can be done in about an evening.
Caution: "dd" is an aggressive program so be sure of the variables you writing to in the "of=" parts of the command. Also, the "status=progress" part is optional, lets you see your progress of the command.
HTH
Fred
Problem in your example and in OP's failed attempt, is using sda. sda is the first drive in the system. Is it the usb flash disk? R U sure? If it is not the USB flash, then the system (which according to the OP) was running fc24, is now hosed because it would have been on /dev/sdaX (X=[1|2|3|4...]).
-JD
On 09/25/16 22:15, fred roller wrote:
[root@Jehovah Downloads]# dd if=Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda1 bs=16M dd: error writing '/dev/sda1': No space left on device 32+0 records in 31+0 records out 524288000 bytes (524 MB, 500 MiB) copied, 1.26722 s, 414 MB/s
Lawrence, for installing based on the information above try:
dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda bs=1M status=progress
for your understanding... the "./" in front of the filename notes your location to the system as "in my current directory" but irregardless the illegal operand came from the space between the "=" and the "F" in your second attempt. The first failure of running out of space is because dd was directed to a partition sda1. Also, be sure this is your usb drive, my experience is that sda is usually the hard drive. Broken down sda1 is: "sd"=serial device,"a" [or b,c,d,e,f, etc] is the devices in
Err, ah, sd=scsi disk. A long time ago, the ATA drivers (and Serial ATA driver) were re-written to use the same SCSI disk interface as SCSI disks were using. And, as it turns out, USB disks too. Thus, we have no more "hd" disks (where the "hd" stood for "hard disk"). Every disk is an "sd" these days.
sequence as discovered, "1" [or 2,3,4, etc] are the partitions on the device. With that try the following command WITHOUT the usb plugged in:
ls /dev/sd*
which should give you something like:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3
Then re-run the same command WITH the usb plugged in which should give you something like:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sdb /dev/sdb1
This last letter to appear is the one you want and without the number. So be REAL sure you have your usb device letter correct and:
dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sdb bs=1M status=progress
will work.
If you want to easily understand the command line I suggest you go through this quick course:
It is a great primer for understanding all we are talking about and can be done in about an evening.
Caution: "dd" is an aggressive program so be sure of the variables you writing to in the "of=" parts of the command. Also, the "status=progress" part is optional, lets you see your progress of the command.
HTH
Fred
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 09/26/2016 11:27 AM, Kevin Cummings wrote:
On 09/25/16 22:15, fred roller wrote:
[root@Jehovah Downloads]# dd if=Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda1 bs=16M dd: error writing '/dev/sda1': No space left on device 32+0 records in 31+0 records out 524288000 bytes (524 MB, 500 MiB) copied, 1.26722 s, 414 MB/s
Lawrence, for installing based on the information above try:
dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda bs=1M status=progress
for your understanding... the "./" in front of the filename notes your location to the system as "in my current directory" but irregardless the illegal operand came from the space between the "=" and the "F" in your second attempt. The first failure of running out of space is because dd was directed to a partition sda1. Also, be sure this is your usb drive, my experience is that sda is usually the hard drive. Broken down sda1 is: "sd"=serial device,"a" [or b,c,d,e,f, etc] is the devices in
Err, ah, sd=scsi disk. A long time ago, the ATA drivers (and Serial ATA driver) were re-written to use the same SCSI disk interface as SCSI disks were using. And, as it turns out, USB disks too. Thus, we have no more "hd" disks (where the "hd" stood for "hard disk"). Every disk is an "sd" these days.
sequence as discovered, "1" [or 2,3,4, etc] are the partitions on the device. With that try the following command WITHOUT the usb plugged in:
ls /dev/sd*
which should give you something like:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3
Then re-run the same command WITH the usb plugged in which should give you something like:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sdb /dev/sdb1
This last letter to appear is the one you want and without the number. So be REAL sure you have your usb device letter correct and:
dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sdb bs=1M status=progress
will work.
If you want to easily understand the command line I suggest you go through this quick course:
It is a great primer for understanding all we are talking about and can be done in about an evening.
Caution: "dd" is an aggressive program so be sure of the variables you writing to in the "of=" parts of the command. Also, the "status=progress" part is optional, lets you see your progress of the command.
I'd also recommend using a smaller block size--even though it will take longer to do the operation. The actual block size of an ISO image is 2048 bytes (2KiB). However, as most ISO images are in multiples of 1MiB, using a 1MiB block size gives you a cleaner operation (IMHO) and doesn't put as much strain on your memory (a 1MiB buffer versus a 16MiB buffer).
I also tend to use "oflag=direct" for direct I/O rather than buffered. Thus, my standard mechanism for this is:
dd if=/path/to/iso/image.iso of=/dev/sdX bs=1M oflag=direct
That uses a 1MiB block size. dd's use of multipliers can be odd, so "man dd" to read up on those.
It's worked well for me. Your mileage may vary. Batteries not included, etc., etc. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - Careful! Ugly strikes 9 out of 10 people! - ----------------------------------------------------------------------
On Mon, Sep 26, 2016 at 02:04:05PM +0200, Martin Bříza wrote:
On Mon, 26 Sep 2016 12:34:58 +0200, Jon Ingason jon.ingason@telia.com
Just one question regarding "mediawriter" and "liveusb-creator". can they coexist or need I to remove "liveusb-creator" if I want to install "mediawriter"?
They definitely can coexist. It'll be just a bit confusing that both are called "Fedora Media Writer" in the application menu and have the same icon. This is the reason mediawriter is basically a rewrite of liveusb-creator.
Just an FYI. I had neither liveusb-creator nor mediawriter installed on my F24 system. I installed mediawriter and see no menu entry using either the Mate or gnome desktop managers.
I then installed liveusb-creator and again no menu entry. As i have nVidia video, liveusb-creator failed on startup. Thus I removed it.
Jon
On 09/26/2016 01:18 PM, Rick Stevens wrote:
On 09/26/2016 11:27 AM, Kevin Cummings wrote:
On 09/25/16 22:15, fred roller wrote:
[root@Jehovah Downloads]# dd if=Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda1 bs=16M dd: error writing '/dev/sda1': No space left on device 32+0 records in 31+0 records out 524288000 bytes (524 MB, 500 MiB) copied, 1.26722 s, 414 MB/s
Lawrence, for installing based on the information above try:
dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sda bs=1M status=progress
for your understanding... the "./" in front of the filename notes your location to the system as "in my current directory" but irregardless the illegal operand came from the space between the "=" and the "F" in your second attempt. The first failure of running out of space is because dd was directed to a partition sda1. Also, be sure this is your usb drive, my experience is that sda is usually the hard drive. Broken down sda1 is: "sd"=serial device,"a" [or b,c,d,e,f, etc] is the devices in
Err, ah, sd=scsi disk. A long time ago, the ATA drivers (and Serial ATA driver) were re-written to use the same SCSI disk interface as SCSI disks were using. And, as it turns out, USB disks too. Thus, we have no more "hd" disks (where the "hd" stood for "hard disk"). Every disk is an "sd" these days.
sequence as discovered, "1" [or 2,3,4, etc] are the partitions on the device. With that try the following command WITHOUT the usb plugged in:
ls /dev/sd*
which should give you something like:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3
Then re-run the same command WITH the usb plugged in which should give you something like:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sdb /dev/sdb1
This last letter to appear is the one you want and without the number. So be REAL sure you have your usb device letter correct and:
dd if=./Fedora-Workstation-Live-x86_64-25_Alpha-2.iso of=/dev/sdb bs=1M status=progress
will work.
If you want to easily understand the command line I suggest you go through this quick course:
It is a great primer for understanding all we are talking about and can be done in about an evening.
Caution: "dd" is an aggressive program so be sure of the variables you writing to in the "of=" parts of the command. Also, the "status=progress" part is optional, lets you see your progress of the command.
I'd also recommend using a smaller block size--even though it will take longer to do the operation. The actual block size of an ISO image is 2048 bytes (2KiB). However, as most ISO images are in multiples of 1MiB, using a 1MiB block size gives you a cleaner operation (IMHO) and doesn't put as much strain on your memory (a 1MiB buffer versus a 16MiB buffer).
I also tend to use "oflag=direct" for direct I/O rather than buffered. Thus, my standard mechanism for this is:
dd if=/path/to/iso/image.iso of=/dev/sdX bs=1M oflag=direct
That uses a 1MiB block size. dd's use of multipliers can be odd, so "man dd" to read up on those.
It's worked well for me. Your mileage may vary. Batteries not included, etc., etc.
But Rick, the OP was trying to dd into /dev/sda
How can it be that the system boots off of some disk that is not /dev/sda, and /dev/sda is empty? and is a usb flash???
Also, why would the op get a message to the effect "disk is full" when it is a 32GB flash?
My suspicion is that it is not a USB disk, and that it is a very old and small IDE disk.
-JD
On Mon, Sep 26, 2016 at 11:14 PM, jd1008 jd1008@gmail.com wrote:
But Rick, the OP was trying to dd into /dev/sda
How can it be that the system boots off of some disk that is not /dev/sda, and /dev/sda is empty? and is a usb flash???
Also, why would the op get a message to the effect "disk is full" when it is a 32GB flash?
My suspicion is that it is not a USB disk, and that it is a very old and small IDE disk.
-JD
If you look at my reply, he dd'd into a partition which I suspect was only 524Mb. Odds are, as you mentioned, the system is probably hosed if in fact the it was a system drive. An IDE would show as a "hd" [a,b,c,d]; hence the "ls" command to find the USB. If in fact he does have an IDE drive and it shows as "hd*" then it would explain the how the USB would be "sda" Alternatively he could use:
df -h
but I felt the output would have been too confusing until the OP could better understand.
Kevin, thanks for the clarification, was just keeping it simple.
-- Fred
This is an annoying thread.
Ranjan, jd1008, Jon LaBadie - consider yourselves lucky the OP did not experience data loss as a result of obviously bad advice. Even my house plant recognized what treacherously bad advice it contained.
The OP very clearly, without any ambiguity, expressed reluctance to use the CLI. And even after demonstrating dangerous lack of understanding with the dd command, you guys kept on pushing him forward. Seriously, it makes you three jerks. You're the guys who take the bunny slope skier on a blue/black run, and then when they get stuck or hurt you blame them for it. What is wrong with you? All three of you were also condescending, the bad advice wasn't enough apparently.
I think Lawrence's thanks is pure charity. Next time someone clearly expresses such aversion, maybe consider having no advice at all? For all you know he could have rebooted at any point, and /dev/sda would have been enumerated as some other drive, and your advice would have resulted in data loss. All of your advice was unqualified.
Honestly, hindsight being 20/20 you three really should realize how you just dodged a bullet, and so did Lawrence.
Chris Murphy
On 09/27/2016 07:20 AM, fred roller wrote:
On Mon, Sep 26, 2016 at 11:14 PM, jd1008 <jd1008@gmail.com mailto:jd1008@gmail.com> wrote:
But Rick, the OP was trying to dd into /dev/sda How can it be that the system boots off of some disk that is not /dev/sda, and /dev/sda is empty? and is a usb flash??? Also, why would the op get a message to the effect "disk is full" when it is a 32GB flash? My suspicion is that it is not a USB disk, and that it is a very old and small IDE disk. -JDIf you look at my reply, he dd'd into a partition which I suspect was only 524Mb. Odds are, as you mentioned, the system is probably hosed if in fact the it was a system drive. An IDE would show as a "hd" [a,b,c,d]; hence the "ls" command to find the USB. If in fact he does have an IDE drive and it shows as "hd*" then it would explain the how the USB would be "sda" Alternatively he could use:
df -h
but I felt the output would have been too confusing until the OP could better understand.
Kevin, thanks for the clarification, was just keeping it simple.
-- Fred
Sometimes, it is hard to guide newbies because they do not understand the symbolic or place-holder kinds of command arguments, just as an example. He claimed he was running F24 - which could have been on sdb, and bootable from the boot sector of sda via the grub config file on sdb?/boot/grub2/grub.cfg . As far as I know F24 does not create /dev/hd.. entries. Thanx for clarifying
Why did you not step up to the plate and provide the OP with your two cent's worth? We did all we could. The OP is a newbie and did not understand the lingo we use to express command arguments. His GUI was not working, so we provided an alternative... Why did you not provide a perfectly working solution to his GUI problem? The kettle calling the pot .....etc....
On 09/27/2016 09:32 AM, Chris Murphy wrote:
This is an annoying thread.
Ranjan, jd1008, Jon LaBadie - consider yourselves lucky the OP did not experience data loss as a result of obviously bad advice. Even my house plant recognized what treacherously bad advice it contained.
The OP very clearly, without any ambiguity, expressed reluctance to use the CLI. And even after demonstrating dangerous lack of understanding with the dd command, you guys kept on pushing him forward. Seriously, it makes you three jerks. You're the guys who take the bunny slope skier on a blue/black run, and then when they get stuck or hurt you blame them for it. What is wrong with you? All three of you were also condescending, the bad advice wasn't enough apparently.
I think Lawrence's thanks is pure charity. Next time someone clearly expresses such aversion, maybe consider having no advice at all? For all you know he could have rebooted at any point, and /dev/sda would have been enumerated as some other drive, and your advice would have resulted in data loss. All of your advice was unqualified.
Honestly, hindsight being 20/20 you three really should realize how you just dodged a bullet, and so did Lawrence.
Chris Murphy _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 09/26/2016 05:51 PM, Ed Greshko wrote:
On 09/27/16 07:21, Patrick O'Callaghan wrote:
On Tue, 2016-09-27 at 06:44 +0800, Ed Greshko wrote:
On 09/27/16 00:19, jd1008 wrote:
In case you are using the Nvidia proprietary driver proprietary driver, then as Ed Greshko pointed out
I have not been involved in this thread and I made no such recommendation in regards to hibernation.
I thought I must have missed something.
You didn't. I have never used "suspend" or "hibernation" in the Linux environment. So, I know less than nothing about them. So, if you read anything from me where I use words like "hibernate" or "suspend" chances are that I'm talking about bears or inter-galactic travel.
My bad - a mis-attribution. Please see below:
On 09/26/2016 06:16 AM, jack smith wrote:
Don't know if it's related but there is a bug in Qt with the Nvidia drivers that break liveusb-creator.
https://bugzilla.redhat.com/show_bug.cgi?id=1356677 _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 09/27/2016 09:32 AM, Chris Murphy wrote:
This is an annoying thread.
Ranjan, jd1008, Jon LaBadie - consider yourselves lucky the OP did not experience data loss as a result of obviously bad advice. Even my house plant recognized what treacherously bad advice it contained.
The OP very clearly, without any ambiguity, expressed reluctance to use the CLI. And even after demonstrating dangerous lack of understanding with the dd command, you guys kept on pushing him forward. Seriously, it makes you three jerks. You're the guys who take the bunny slope skier on a blue/black run, and then when they get stuck or hurt you blame them for it. What is wrong with you? All three of you were also condescending, the bad advice wasn't enough apparently.
I think Lawrence's thanks is pure charity. Next time someone clearly expresses such aversion, maybe consider having no advice at all? For all you know he could have rebooted at any point, and /dev/sda would have been enumerated as some other drive, and your advice would have resulted in data loss. All of your advice was unqualified.
Honestly, hindsight being 20/20 you three really should realize how you just dodged a bullet, and so did Lawrence.
Chris Murphy
I had stopped following this thread, but came across this accidentally. Btw, here is what my original post (after the OP expressed reluctance) said:
"Hi,
Unless I have misunderstood what you are trying to do, the steps are exactly what I have written down. The only two things you have to fill out in the commandline are the if= and the of= arguments. If you need help with that, please post back and we shall see if we can help.
Best wishes, Ranjan"
The OP never responded back.
Here is the original commandline steps mentioned in this e-mail:
********begin cut-and-paste
# in order to make a bootable cd, etc, on the commandline:
sudo dd if=path-to-iso.iso of=/dev/sdb bs=1M
# In the above, if (input file) has path-to-iso.iso is the location of your iso. For example: /tmp/Fedora.iso
# Note: only the letter-drive is to be included in the of (output file) i.e. /dev/sdb not inclusive of the numeral /dev/sdb1.
********end cut-and-paste
Perhaps you were just jumping in, but as far as I am concerned, I have been much helped on this forum since the days of Fedora Core 1, so I was only trying to help and offer encouragement for someone who was newer to Linux. This is how I learnt stuff in the first place.
I am sorry my post was interpreted otherwise.
And I missed his thanks, but I am grateful for that.
Best wishes, Ranjan
____________________________________________________________ Can't remember your password? Do you need a strong and secure password? Use Password manager! It stores your passwords & protects your account. Check it out at http://mysecurelogon.com/manager
-
Ahmad Samir -
Chris Murphy -
Ed Greshko -
fred roller -
jack smith -
Javier Perez -
JD -
Joe Zeff -
Jon Ingason -
Jon LaBadie -
Kevin Cummings -
Lawrence E Graves -
Martin Bříza -
Ranjan Maitra -
Rick Stevens -
stan