Re: [qubes-users] Few Issues With Qubes R3.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-06-22 19:04, raahe...@gmail.com wrote: > When I recreate the dispvm template. First i remove the dvm using > qubes-manager. I select view and to show internal vms. Then I > right click on it and hit remove. Then I do the command from dom0 > terminal qvm-create-default-dvm fedora23. > > Or substitute what template you want to use instead of fedora23. > > I'm not sure what --default-template or --default-scripts mean? > maybe thats the old way? I've never done that. > "--default-template" bases the DVM template on your default TemplateVM (by default, fedora-23 in R3.1). "--default-script" is no longer required in R3.1 (but it doesn't hurt to use it). - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXa4arAAoJENtN07w5UDAwhCgP/359NERwmW5bm0P98UojcEzy tM5oF3bdjLew5skAhVGLg78WrM3cRM7ZJC7RR+JdqpQwq2UhrnkB/MVfu0CJ4L0Y S0cXeq+rtSOSSeC7IRN3qdV7k31QELvRPkXy5NtmSJncDrkorZgxq7a3agDYKIAK d1J5sghYQQGalGj+P+LVN8Tauc3lp4M03/6GbDq6P3Wny6gtmkfURLk092Nx5Uwh V70Dz4mcbs/L32jNwgCtwDwtUHtmrXLHhauwQa2XB9ZmyB7QaGqvfVbxwSU5Lnp9 1kjLJPG7HS8m/g+eFq8Ko7e7G1slZ4Cff4Ko2wWzoB3N9+mkaagdud2t/v48DW1H BMlziaREfzgNjeg2TIu3gWmwctbjs2k3Ja44ZQajUXBnvOOQisaJGFJR2VOuW8W+ Y0VWbD8yAevJZDdcF9G4klz73YBpslvFuFv6HpbWZ6qZks9Ht36bqOMPt3Soa6lm SQg/5LFIQdPm2wkAWmls6/lYQqQH5yV0Lt5UoRrJTGXVAU+/wZu7Cu+AQHNONzJ5 ABkOceY0EUD+YaAPt18KytY+z3mUefoP45rrRS886UCuq2jMKqII0dWVU8OG7qE/ tzwr/4B5c4cd5ur4xryo1jBsePA/3q0JcpOkMThSqGJ648eYgbfzob6zAElNveZu qt0+RaAVF25lYSFIdyE4 =k3CI -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9d8c0d67-4adf-3882-526a-5a5abed498ed%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Few Issues With Qubes R3.1
When I recreate the dispvm template. First i remove the dvm using qubes-manager. I select view and to show internal vms. Then I right click on it and hit remove. Then I do the command from dom0 terminal qvm-create-default-dvm fedora23. Or substitute what template you want to use instead of fedora23. I'm not sure what --default-template or --default-scripts mean? maybe thats the old way? I've never done that. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/78684516-6a25-47b4-b27a-5abb567c5155%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Few Issues With Qubes R3.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-06-21 23:49, CANNON NATHANIEL CIOTA wrote:
>
>> Ok, that looks normal. When you say DispVMs "do not launch,"
>> does that just mean that nothing happens when you click the
>> DispVM shortcuts in the KDE launcher?
>>
>> Is your default template fedora-23? Have you made any
>> modifications to it?
>>
>> What happens if you execute this command in dom0?
>>
>> $ sh -c 'echo xterm | /usr/lib/qubes/qfile-daemon-dvm \
>> qubes.VMShell dom0 DEFAULT red'
>>
>
> Hello yes nothing happens when I click the launcher. When I click
> the launcher it looks like DispVM is starting up, but never comes
> up.
>
> As follows is the output after running the command sh -c 'echo
> xterm | /usr/lib/qubes/qfile-daemon-dvm \qubes.VMShell dom0
> DEFAULT red' as you asked.
>
> To answer your question on if I have customized my disposable vm or
> anything. Only thing I did really, was three things when trying to
> get it to work. First thing I did was qvm-prefs -s fedora-23-dvm
> maxmem 2048 (since I have read that in past disposable VM cannot
> handle more than 4GB RAM. I have 16 GB of ram) Second thing I did
> was remove it using command: qvm-remove fedora-23-dvm Then third
> thing I did was re-generate it using command:
> qvm-create-default-dvm --default-template --default-script
>
> Also, can you please inform me exactly was this command you had me
> type is doing? Thank you
>
That command just attempts to start a new DispVM and launch xterm (a
terminal emulator) in the new DispVM. If you take a look at the
preexisting shortcut to start, e.g., Firefox in a DispVM, you can see
that it's the same command (but with "xterm" substituted for "firefox").
>
> [user@dom0 Documents]$ sh -c 'echo xterm |
> /usr/lib/qubes/qfile-daemon-dvm \qubes.VMShell dom0 DEFAULT red'
> time=1466576745.19, qfile-daemon-dvm init time=1466576745.2,
> creating DispVM time=1466576745.25, collection loaded
> time=1466576745.26, VM created time=1466576745.36, VM starting
> time=1466576745.36, creating config file time=1466576745.57,
> calling restore Traceback (most recent call last): File
> "/usr/lib/qubes/qfile-daemon-dvm", line 191, in main()
> File "/usr/lib/qubes/qfile-daemon-dvm", line 178, in main dispvm =
> qfile.get_dvm() File "/usr/lib/qubes/qfile-daemon-dvm", line 150,
> in get_dvm return self.do_get_dvm() File
> "/usr/lib/qubes/qfile-daemon-dvm", line 103, in do_get_dvm
> dispvm.start() File
> "/usr/lib64/python2.7/site-packages/qubes/modules/
> 01QubesDisposableVm.py", line 193, in start domain_config,
> libvirt.VIR_DOMAIN_SAVE_PAUSED) File
> "/usr/lib64/python2.7/site-packages/libvirt.py", line 4405, in
> restoreFlags if ret == -1: raise libvirtError
> ('virDomainRestoreFlags() failed', conn=self)
> libvirt.libvirtError: internal error: libxenlight failed to restore
> domain 'disp1'
>
Marek, any idea what's going on here? (Sorry about the bad rewrapping.
Thunderbird/Enigmail plain text inline PGP limitation.)
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJXakL4AAoJENtN07w5UDAw98kP/2CUdFmywkQcNAGNL1Yyqzzb
wQgWhMwdGgHwYlVwdbv32DqyPB3ToQwIU3iaxHd8b0oYl0gmd6+Mp1BrRm2593E+
8OCCaKz5q+Ww51bd9S46Id5UEfvWdB2bEKC/8Z9QyAgbS3yqifcHUS+RNDUCj1ls
epCvCtKY7E11q6i4q4Ea3isvSDEbBSLfNsFMFXB9hp2x/fLSuj3HJr4IeaG3E48O
OLdmAfbMtGmC0G0o0pOb1+qTZMVqFQCNdNED8z59Y0iQyhsS+a1qG7uH2Tuh2szt
RE8JwS8DPqoEYI4ugGawbIiD4fHeBDfaZi7J9SD1xBpYimvGBUa1Sr+mTWqP8JZu
qAgfUcwSeFw/QFqO/K4JxaGk7FYHEuQcTpcObyNdKdJUd9aOiljN2UAE/YXFStAP
7jfq+I5TUDla5iTBBfFRde7E8etB9XvlQhHMyjlj7qjvTox7Nv0oC/F9EfOCF03k
x6t0o4pPrGLROmYeAJiVDe2KcIgdFFyFC2Caiq4VVtb4MkNtZfoO0EsLyX9OrVxU
nAa7DAtR5lhbSKWNAbvYxKH8d7TOByVW96w5Lf4R9seKg+MflR4fjkfHaJi6i5zo
tKk2o+HWgDX910wuw/xbyL6Hq+/hoiJQnsr2tUHLZaOrH90k5RzSke85Jex7/sqg
kySZoy/XexyvhZqSi1ki
=V818
-END PGP SIGNATURE-
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/b80a92c9-143c-6eea-9d84-0702e7fc6fdb%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Few Issues With Qubes R3.1
Ok, that looks normal. When you say DispVMs "do not launch," does that
just mean that nothing happens when you click the DispVM shortcuts in
the KDE launcher?
Is your default template fedora-23? Have you made any modifications to
it?
What happens if you execute this command in dom0?
$ sh -c 'echo xterm | /usr/lib/qubes/qfile-daemon-dvm \
qubes.VMShell dom0 DEFAULT red'
- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
Hello yes nothing happens when I click the launcher. When I click the
launcher it looks like DispVM is starting up, but never comes up.
As follows is the output after running the command
sh -c 'echo xterm | /usr/lib/qubes/qfile-daemon-dvm \qubes.VMShell dom0
DEFAULT red'
as you asked.
To answer your question on if I have customized my disposable vm or
anything.
Only thing I did really, was three things when trying to get it to work.
First thing I did was qvm-prefs -s fedora-23-dvm maxmem 2048 (since I
have read that in past disposable VM cannot handle more than 4GB RAM. I
have 16 GB of ram)
Second thing I did was remove it using command: qvm-remove fedora-23-dvm
Then third thing I did was re-generate it using command:
qvm-create-default-dvm --default-template --default-script
Also, can you please inform me exactly was this command you had me type
is doing?
Thank you
[user@dom0 Documents]$ sh -c 'echo xterm |
/usr/lib/qubes/qfile-daemon-dvm \qubes.VMShell dom0 DEFAULT red'
time=1466576745.19, qfile-daemon-dvm init
time=1466576745.2, creating DispVM
time=1466576745.25, collection loaded
time=1466576745.26, VM created
time=1466576745.36, VM starting
time=1466576745.36, creating config file
time=1466576745.57, calling restore
Traceback (most recent call last):
File "/usr/lib/qubes/qfile-daemon-dvm", line 191, in
main()
File "/usr/lib/qubes/qfile-daemon-dvm", line 178, in main
dispvm = qfile.get_dvm()
File "/usr/lib/qubes/qfile-daemon-dvm", line 150, in get_dvm
return self.do_get_dvm()
File "/usr/lib/qubes/qfile-daemon-dvm", line 103, in do_get_dvm
dispvm.start()
File
"/usr/lib64/python2.7/site-packages/qubes/modules/01QubesDisposableVm.py",
line 193, in start
domain_config, libvirt.VIR_DOMAIN_SAVE_PAUSED)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4405, in
restoreFlags
if ret == -1: raise libvirtError ('virDomainRestoreFlags() failed',
conn=self)
libvirt.libvirtError: internal error: libxenlight failed to restore
domain 'disp1'
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/d912f89d85fe0d000a8dd1e174083b9f%40cannon-ciota.info.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Few Issues With Qubes R3.1
Andrew David Wong: > On 2016-06-19 00:09, CANNON NATHANIEL CIOTA wrote: > >>> On 2016-06-17 23:17, CANNON NATHANIEL CIOTA wrote: Hello thank you for the reply... > What is the output when you run this command in a dom0 > terminal? > > $ qvm-create-default-dvm --default-template I have already tried this before re-installing Qubes which made no difference. >>> >>> Can you be more specific when you say it "made no difference"? >>> For example, can you tell us the exact output when you attempted >>> to run that command? (Even if there was no output at all, that >>> would be helpful to know.) > >> Here is output (I am manually typing this output, so there might >> be slight typos): [...] > > > Ok, that looks normal. When you say DispVMs "do not launch," does that > just mean that nothing happens when you click the DispVM shortcuts in > the KDE launcher? > > Is your default template fedora-23? Have you made any modifications to > it? > > What happens if you execute this command in dom0? > > $ sh -c 'echo xterm | /usr/lib/qubes/qfile-daemon-dvm \ > qubes.VMShell dom0 DEFAULT red' > Also try removing the pre-existing fedora-23-dvm first, then recreate it with the above command. I've had issues before that were solved by removing the old *-dvm first, then creating a new one. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/052bbbd0-32aa-a8bf-d3df-5a1cd88eea3c%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Few Issues With Qubes R3.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-06-19 00:09, CANNON NATHANIEL CIOTA wrote: > >> On 2016-06-17 23:17, CANNON NATHANIEL CIOTA wrote: >>> Hello thank you for the reply... >>> What is the output when you run this command in a dom0 terminal? $ qvm-create-default-dvm --default-template >>> >>> I have already tried this before re-installing Qubes which made >>> no difference. >> >> Can you be more specific when you say it "made no difference"? >> For example, can you tell us the exact output when you attempted >> to run that command? (Even if there was no output at all, that >> would be helpful to know.) > > Here is output (I am manually typing this output, so there might > be slight typos): [...] > Ok, that looks normal. When you say DispVMs "do not launch," does that just mean that nothing happens when you click the DispVM shortcuts in the KDE launcher? Is your default template fedora-23? Have you made any modifications to it? What happens if you execute this command in dom0? $ sh -c 'echo xterm | /usr/lib/qubes/qfile-daemon-dvm \ qubes.VMShell dom0 DEFAULT red' - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXZqtFAAoJENtN07w5UDAw5NEQANDfy4Su/MqwKa7Z5Oc47mRA 96pVohUyTE3PGnHxzd2zPfG7gJTcnCyFJzGSqjueN9Elibl2w1vEs3nTE/3oM/V6 jco+6GTa40ogBervDyVD5NSlJM0fi4FWcGGl5rvzSzG+7tEjXylBJehVrNlzN00p 5vhnWKBoT8ceMInECL+e51Rexoz0V5xK5TX1JfacR1r1mHV+pj4tifcB4f4d7W7d ROslfjRXxyA1KBRnaoRnLY09UJxtKLuu69oKSmzTIJQ/Yc+XTbx6mBIaDNHAq6xv zb4xtYM9FKuxMhSv50SIpxL9HvQN0mI0jtICpFmk9WUiVSTKAkr2uKZLsVQRaYSe sipfMTFw/h6vE9lDPpmmhrwq4G2D6rwocoftXFMUoYBEOqcO/HCcEtkzzxDVJaIf kKgiRAcSDINgrUWRh7qvGXiFsM9E/zG+osi99fyYB/9Ol+ULfSbboiR+/ZvdiQ4g UM3tqzouW5wcCOtXJOrs/D6YbzJ+wMMG7yH9u1G9XMGoCHTalNdQxi4qOeVzglL1 KrS2yXImZS17TXdAtR/Ir02PRrvt53rcZRg1ScFHMI6b4nZa1HisYDw+3OqirNyt IW9/alAD+qN4TRx2pQzMUZeqx4n4sbl9MpAYj4ayNJ9/vobJDNIsBpF6WhANT6/s UQJkeYAgU9t+kcy6Hbnd =y2Wx -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0221c3d3-c300-2f96-cf5c-885198a0eec9%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Few Issues With Qubes R3.1
On 2016-06-17 23:17, CANNON NATHANIEL CIOTA wrote: Hello thank you for the reply... What is the output when you run this command in a dom0 terminal? $ qvm-create-default-dvm --default-template I have already tried this before re-installing Qubes which made no difference. Can you be more specific when you say it "made no difference"? For example, can you tell us the exact output when you attempted to run that command? (Even if there was no output at all, that would be helpful to know.) Here is output (I am manually typing this output, so there might be slight typos): --BEGIN of OUTPUT-- [user@dom0 ~]$ qvm-create-default-dvm --default-template --> Creating volatile image: /var/lib/qubes/appvms/fedora-23-dvm/volatile.img... --> Loading the VM (type = AppVM).. --> Starting Qubes DB... --> Setting Qubes DB info for the VM... --> Updating firewall rules... --> Starting the VM... --> Starting Qubes GUId... Connecting to VM's GUI agent: ..connected Waiting for DVM fedora-23-dvm ... /qubes-used-mem Disk detached successfully DVM boot complete, memory used=316760. saving image... Domain fedora-23-dvm saved to /var/lib/qubes/appvms/fedora-23-dvm/dvm-savefile --END OF OUTPUT-- I saw in another post where someone did that same command but with --default-script added to that command. I can try qvm-create-default-dvm --default-template --default-script to see what happens. Are you on Qubes R3.1? If so, --default-script is no longer necessary (but it does not hurt to use it). Yes I am on Qubes R3.1 You should be able to change this in KDE's settings. System Tools -> System Settings -> Power Management -> Energy Saving - -> Screen Brightness I have tried this, The Fn keys activate the brightness slider on the screen but do not actually change brightness. Hm, in that case, it might be a hardware-specific issue. What is the exact brand and model of your laptop. (Also, if you know the exact GPU/IGP you have, please provide that.) HP Notebook 15-ba079dx customized with replacing harddrive for 500GB Samsung Evo solid state drive -- Cannon N. Ciota PGP Fingerprint: E7FB 0605 1BD4 8B88 B7BC 91A4 7DF7 76C7 25A6 AEE2 Website: www.cannon-ciota.info Email: can...@cannon-ciota.info Bitmessage: BM-2cVaTbC8fJ5UDDaBBs4jPQoFNp1PfNhxqU Instant Messaging: ricochet:hfddt2csxnsb2mdq -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6f6412075338df6849cce300c2ac742d%40cannon-ciota.info. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Few Issues With Qubes R3.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-06-17 23:17, CANNON NATHANIEL CIOTA wrote: > Hello thank you for the reply... > >> What is the output when you run this command in a dom0 terminal? >> >> $ qvm-create-default-dvm --default-template > > I have already tried this before re-installing Qubes which made no > difference. Can you be more specific when you say it "made no difference"? For example, can you tell us the exact output when you attempted to run that command? (Even if there was no output at all, that would be helpful to know.) > I saw in another post where someone did that same command but with > --default-script added to that command. I can try > qvm-create-default-dvm --default-template --default-script to see > what happens. > Are you on Qubes R3.1? If so, --default-script is no longer necessary (but it does not hurt to use it). > >> You should be able to change this in KDE's settings. >> >> System Tools -> System Settings -> Power Management -> Energy >> Saving - -> Screen Brightness > > I have tried this, The Fn keys activate the brightness slider on > the screen but do not actually change brightness. > Hm, in that case, it might be a hardware-specific issue. What is the exact brand and model of your laptop. (Also, if you know the exact GPU/IGP you have, please provide that.) > >> >> It could be that your GPU does not support this. You can try >> changing the Compositing type from OpenGL to something else (if >> you have any other options). > > The compositing type is already different than OpenGL, I am not > able to get it to switch to OpenGL. > In that case, I have no idea. Knowing your hardware specs (as mentioned above) would help tremendously in helping you diagnose this, but it sounds like you'll probably have more luck asking on the KDE forums/mailing list, since this is a KDE-provided feature. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXZOvuAAoJENtN07w5UDAwzyUP/06EbeKRZpQPJw0FRjUdW24a Q0FL/Z4t5qbqm1aQJ66xc95WArNf0mNKtKflC9+77hKs/MlDOaW7spJSxbbxTgdy QHc7DPzSxBebulUZHZk4E3wsQpbwLTg0jOclID+zbSYGFFabrHqtKGEeY1/zhoBj gC8/i7cKnJeycGqb99oVQUMtrvu93wZwomILsDnmafB5xjRuHOZANSfa8YBnFsAc siweu+jzlvEZcznPzmwtGCqos5+2zx5jGv8JFQtzLnuMu8HJN7TSHRlWxht2T0FC ffiPEhtryFHA5vXbC2jXJtv9lDGezfKZkV0VugWGYTtzEDwUitvzaCMYb+v+ALMu wWTWUXKvkjzgdBJ8a3Qt5secD0mqHuyzzSVrXh9RnNgDZXXvx0yGhmXT4MO960/I 2OFWxP9LJkjSEpEDQfb4rHf8ItJH2B2brSKeRK5FjP3zdn7/Mh87SZheVIMfpBsb RmpXB1SiLogsJtnfoR6lITtC61G3B7rkublOWozq8aoRc+/ynLFXSV9yuNguwu0m DZ9I1ChNGrnEl67rt8D3XQa4FDyIWT9XZpzVOZICQ8FCJV+Mk4+v2r0+RZddKA/O KZ0z4BItDYlPv+Vq2GL7rZYdZtJ/PU2VmOVNsCuaWH7Vjyw1GAP0dVgJEPcp+avX StrYYwJfn0P7VL5+7kop =vWFp -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/15d3dd03-3a6e-25d2-62ca-506b8bdbc373%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Few Issues With Qubes R3.1
On 2016-06-18 01:09, Andrew David Wong wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-06-17 22:05, CANNON NATHANIEL CIOTA wrote: I have installed Qubes R3.1 on a laptop. I have a couple issues as noted below. I tested this both before and after updates, and have also re-burned an installation media and re-installed Qubes OS which problems persist. If anyone could give any pointers that would be much appreciated. Issue#1 Disposable VM does not launch What is the output when you run this command in a dom0 terminal? $ qvm-create-default-dvm --default-template Issue#2 Screen is super bright, I am unable to dim the screen. Neither keyboard Fn keys or software screen brightness slider makes any changes. You should be able to change this in KDE's settings. System Tools -> System Settings -> Power Management -> Energy Saving - -> Screen Brightness Issue#3 Some desktop effects do not work, such as 3D cube. When I try to enable I get error message about requiring OpenGL. It could be that your GPU does not support this. You can try changing the Compositing type from OpenGL to something else (if you have any other options). System Tools -> System Settings -> Desktop Effects -> Advanced -> Compositing type Thanks - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXZOWgAAoJENtN07w5UDAw5GEP/iBTFV0tgfED2fR4ENCluvS8 dZLPJ/tkg99jveic1ejM7033evo7NRn9LHFcHkv/flpAZdLrAF1XjTgCSWqj9En+ 2IWlGgTCeay+30dRqFo1l6PzlXKf2ZMipewIqCZXJ/YKJvG1tgTqpbEg1Cn5dLHF 1EJlkka246OmHmIA93dyjM0ARU6JwcnmfbvyFswe7JQY3ojJQjBFbJhdsnq8xvey 2SFRtLB5126y/KySCe7YozGsJ0ETB4wdALHRenZFi1AwFW8iOX2DYYG8qtxZhWJh e+24ftndT8L8skMup6cp0T6kTEWV5jYDnORfqw5xs3gfxJzQgVjuO1gOxa44jKDm dFZhtnsVN37xWsNsVg9ecEI2MGngmWUTbgRfw3B+M/PpV5akobZhCgbW9S30qDq0 ts8MqfQsfApYn2OjtwuV/PoddlatMARgFK101CGjaKfyi4mlWLnJOCWMxkXA+UE+ MIc/pXjeFHtSGR/s54NlB8cD/I3BVFr3Ypi6sJ0FZNe0kdDQ8rPNqDZXp7O1iokS 2MyNr78nN92XC8/H9lGbhFMxMzvqYIxwp4MZj/wXQlJCQ4XdlVMpeZ1x4sy733hq cFZCHksnQPe0sBlHY9wXH/Cr1Gov1T9gqKtIdk99jDZ/vHVbpAQd/wRc28AdjcC8 pTMsprKpLGj4+wy6F2Yz =Be9r -END PGP SIGNATURE- Hello thank you for the reply... What is the output when you run this command in a dom0 terminal? $ qvm-create-default-dvm --default-template I have already tried this before re-installing Qubes which made no difference. I saw in another post where someone did that same command but with --default-script added to that command. I can try qvm-create-default-dvm --default-template --default-script to see what happens. You should be able to change this in KDE's settings. System Tools -> System Settings -> Power Management -> Energy Saving - -> Screen Brightness I have tried this, The Fn keys activate the brightness slider on the screen but do not actually change brightness. It could be that your GPU does not support this. You can try changing the Compositing type from OpenGL to something else (if you have any other options). The compositing type is already different than OpenGL, I am not able to get it to switch to OpenGL. -- Cannon N. Ciota PGP Fingerprint: E7FB 0605 1BD4 8B88 B7BC 91A4 7DF7 76C7 25A6 AEE2 Website: www.cannon-ciota.info Email: can...@cannon-ciota.info Bitmessage: BM-2cVaTbC8fJ5UDDaBBs4jPQoFNp1PfNhxqU Instant Messaging: ricochet:hfddt2csxnsb2mdq -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bb9b18e93686b3acda41122b9fd9af02%40cannon-ciota.info. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Few Issues With Qubes R3.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-06-17 22:05, CANNON NATHANIEL CIOTA wrote: > I have installed Qubes R3.1 on a laptop. I have a couple issues as > noted below. I tested this both before and after updates, and have > also re-burned an installation media and re-installed Qubes OS > which problems persist. If anyone could give any pointers that > would be much appreciated. > > Issue#1 Disposable VM does not launch > What is the output when you run this command in a dom0 terminal? $ qvm-create-default-dvm --default-template > Issue#2 Screen is super bright, I am unable to dim the screen. > Neither keyboard Fn keys or software screen brightness slider makes > any changes. > You should be able to change this in KDE's settings. System Tools -> System Settings -> Power Management -> Energy Saving - -> Screen Brightness > Issue#3 Some desktop effects do not work, such as 3D cube. When I > try to enable I get error message about requiring OpenGL. > It could be that your GPU does not support this. You can try changing the Compositing type from OpenGL to something else (if you have any other options). System Tools -> System Settings -> Desktop Effects -> Advanced -> Compositing type > Thanks > - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXZOWgAAoJENtN07w5UDAw5GEP/iBTFV0tgfED2fR4ENCluvS8 dZLPJ/tkg99jveic1ejM7033evo7NRn9LHFcHkv/flpAZdLrAF1XjTgCSWqj9En+ 2IWlGgTCeay+30dRqFo1l6PzlXKf2ZMipewIqCZXJ/YKJvG1tgTqpbEg1Cn5dLHF 1EJlkka246OmHmIA93dyjM0ARU6JwcnmfbvyFswe7JQY3ojJQjBFbJhdsnq8xvey 2SFRtLB5126y/KySCe7YozGsJ0ETB4wdALHRenZFi1AwFW8iOX2DYYG8qtxZhWJh e+24ftndT8L8skMup6cp0T6kTEWV5jYDnORfqw5xs3gfxJzQgVjuO1gOxa44jKDm dFZhtnsVN37xWsNsVg9ecEI2MGngmWUTbgRfw3B+M/PpV5akobZhCgbW9S30qDq0 ts8MqfQsfApYn2OjtwuV/PoddlatMARgFK101CGjaKfyi4mlWLnJOCWMxkXA+UE+ MIc/pXjeFHtSGR/s54NlB8cD/I3BVFr3Ypi6sJ0FZNe0kdDQ8rPNqDZXp7O1iokS 2MyNr78nN92XC8/H9lGbhFMxMzvqYIxwp4MZj/wXQlJCQ4XdlVMpeZ1x4sy733hq cFZCHksnQPe0sBlHY9wXH/Cr1Gov1T9gqKtIdk99jDZ/vHVbpAQd/wRc28AdjcC8 pTMsprKpLGj4+wy6F2Yz =Be9r -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/149fb026-4c91-c163-5a8a-ed28b49108de%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Few Issues With Qubes R3.1
I have installed Qubes R3.1 on a laptop. I have a couple issues as noted below. I tested this both before and after updates, and have also re-burned an installation media and re-installed Qubes OS which problems persist. If anyone could give any pointers that would be much appreciated. Issue#1 Disposable VM does not launch Issue#2 Screen is super bright, I am unable to dim the screen. Neither keyboard Fn keys or software screen brightness slider makes any changes. Issue#3 Some desktop effects do not work, such as 3D cube. When I try to enable I get error message about requiring OpenGL. Thanks -- Cannon N. Ciota PGP Fingerprint: E7FB 0605 1BD4 8B88 B7BC 91A4 7DF7 76C7 25A6 AEE2 Website: www.cannon-ciota.info Email: can...@cannon-ciota.info Bitmessage: BM-2cVaTbC8fJ5UDDaBBs4jPQoFNp1PfNhxqU Instant Messaging: ricochet:hfddt2csxnsb2mdq -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f31142395976c5a3423c0a37215be817%40cannon-ciota.info. For more options, visit https://groups.google.com/d/optout.
