Re: [qubes-users] Qubes-manager refuses to launch

2016-12-14 Thread harhorg
Yes, this is the exit for now (thanks for mentioning q-m-backups! I didn't know 
that), but not an answer for all)

-- 
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/1e6f3ec2-64c1-4e0c-be69-45d8314e1b1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

2016-12-14 Thread Reg Tiangha
On Wednesday, December 14, 2016 at 4:02:31 PM UTC-7, Foppe de Haan wrote:
> On Wednesday, December 14, 2016 at 11:19:45 PM UTC+1, rtia...@gmail.com wrote:
> > On Wednesday, December 14, 2016 at 2:22:57 PM UTC-7, Foppe de Haan wrote:
> > 
> > > Thanks. When building this in d9-t, I get 'recipe failed' "Error 2" 
> > > pretty soon after starting the build process. No idea why, as there is no 
> > > log, and I don't see an option to provide one (or to provide verbose 
> > > output).
> > 
> > Hmm, I haven't had time to try it under Debian 9 yet and might not for a 
> > while.
> > 
> > In the meantime, peeking at their build script, what you can try to do 
> > (haven't tried it myself though) is to comment out the spinner code around 
> > the build_kernel part and the '> /dev/null 2>&1' part in the build.sh file 
> > and perhaps that would throw the verbose compile output to the terminal to 
> > give some hints on where or why it fails.
> > 
> > So find this section in build.sh:
> > 
> >  start_spinner "Building coldkernel..."
> >  build_kernel > /dev/null 2>&1
> >  stop_spinner $?
> > 
> > And change it to be
> > 
> >  build_kernel
> > 
> > and try to compile (make qubes-guest) again. If the output isn't enough to 
> > give any hints, you may need to run 'make clean' to get rid of anything 
> > that was pre-compiled and to start again from scratch.
> 
> Thanks for that hint. Seems there was an issue with gcc not supporting 
> plugins, even though supposedly all the required packages were installed and 
> updated. Worked around it, it's building now.

Glad to hear. For future reference, what exactly did you have to do? Was it

sudo apt install gcc-6-plugin-dev

or something else?

-- 
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/1ac615ae-49fd-4f63-a96b-4ead808b5dad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

2016-12-14 Thread Foppe de Haan
On Wednesday, December 14, 2016 at 11:19:45 PM UTC+1, rtia...@gmail.com wrote:
> On Wednesday, December 14, 2016 at 2:22:57 PM UTC-7, Foppe de Haan wrote:
> 
> > Thanks. When building this in d9-t, I get 'recipe failed' "Error 2" pretty 
> > soon after starting the build process. No idea why, as there is no log, and 
> > I don't see an option to provide one (or to provide verbose output).
> 
> Hmm, I haven't had time to try it under Debian 9 yet and might not for a 
> while.
> 
> In the meantime, peeking at their build script, what you can try to do 
> (haven't tried it myself though) is to comment out the spinner code around 
> the build_kernel part and the '> /dev/null 2>&1' part in the build.sh file 
> and perhaps that would throw the verbose compile output to the terminal to 
> give some hints on where or why it fails.
> 
> So find this section in build.sh:
> 
>start_spinner "Building coldkernel..."
>build_kernel > /dev/null 2>&1
>stop_spinner $?
> 
> And change it to be
> 
>build_kernel
> 
> and try to compile (make qubes-guest) again. If the output isn't enough to 
> give any hints, you may need to run 'make clean' to get rid of anything that 
> was pre-compiled and to start again from scratch.

Thanks for that hint. Seems there was an issue with gcc not supporting plugins, 
even though supposedly all the required packages were installed and updated. 
Worked around it, it's building now.

-- 
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/4026d5cf-fd18-47a9-8818-dcbce319d747%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

2016-12-14 Thread rtiangha
On Wednesday, December 14, 2016 at 2:22:57 PM UTC-7, Foppe de Haan wrote:

> Thanks. When building this in d9-t, I get 'recipe failed' "Error 2" pretty 
> soon after starting the build process. No idea why, as there is no log, and I 
> don't see an option to provide one (or to provide verbose output).

Hmm, I haven't had time to try it under Debian 9 yet and might not for a while.

In the meantime, peeking at their build script, what you can try to do (haven't 
tried it myself though) is to comment out the spinner code around the 
build_kernel part and the '> /dev/null 2>&1' part in the build.sh file and 
perhaps that would throw the verbose compile output to the terminal to give 
some hints on where or why it fails.

So find this section in build.sh:

 start_spinner "Building coldkernel..."
 build_kernel > /dev/null 2>&1
 stop_spinner $?

And change it to be

 build_kernel

and try to compile (make qubes-guest) again. If the output isn't enough to give 
any hints, you may need to run 'make clean' to get rid of anything that was 
pre-compiled and to start again from scratch.

-- 
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/02907625-5c0d-4380-b5d5-db5a0f50e2e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - Razer Blade Stealth (Late 2016 Model)

2016-12-14 Thread Krasi
On Wednesday, December 14, 2016 at 4:09:07 PM UTC-6, rtia...@gmail.com wrote:
> On Wednesday, December 14, 2016 at 3:03:48 PM UTC-7, Krasi wrote:
> > 
> > Trackpad:
> > Its working but you cannot mouse click without physically pressing the pad. 
> > I am guessing gestures are not working.
> > 
> 
> 
> Make sure to double-check the Mouse and Trackpad system settings. I don't 
> know about gesture support, but there was a box I had to enable under the 
> Touchpad section labeled "Tap touchpad to click" before tapping to click 
> worked.


Awesome, that fixed it :) Thank you

-- 
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/e7ee90da-5275-4555-b4ce-595b5c88d760%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - Razer Blade Stealth (Late 2016 Model)

2016-12-14 Thread rtiangha
On Wednesday, December 14, 2016 at 3:03:48 PM UTC-7, Krasi wrote:
> 
> Trackpad:
> Its working but you cannot mouse click without physically pressing the pad. I 
> am guessing gestures are not working.
> 


Make sure to double-check the Mouse and Trackpad system settings. I don't know 
about gesture support, but there was a box I had to enable under the Touchpad 
section labeled "Tap touchpad to click" before tapping to click worked.

-- 
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/b080fab7-3dd3-4509-8aa2-d50848fc0184%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] HCL - Razer Blade Stealth (Late 2016 Model)

2016-12-14 Thread Krasi
I have tested Qubes Release 3.2 on Razer Blade Stealth (no model number). Here 
are some details other then the HCL report.

Installation and BIOS/UEFI:

I had to disable secure boot in the firmware before my USB stick would boot. 

I was able to install in UEFI mode only, in legacy mode I had some problems 
with the graphics and Qubes would load the text installer which was unable to 
partition drives with encryption.

Graphics and resolution:

First book was good but the resolution was only 800x600, had to update kernel 
to 4.8 and then edit the xen.cfg file inside the EFI system partition. The 
kernel boot files had to be copied from /boot to the EFI partition under the 
qubes directory to force it to use the 4.8 kernel but after that the graphics 
work great and the sound got fixed.

LAN/WLAN:

Was unable to test LAN, no LAN port but wifi was broken initially, had to use a 
USB adapter to update the kernel, after the update wifi is working correctly.


Webcam:

Not working, the device is not found by cheese.

Sound:
Sounds appears to be working, have not testes the microphone but the speakers 
are working.

Trackpad:
Its working but you cannot mouse click without physically pressing the pad. I 
am guessing gestures are not working.

Keyboard:
Everything appears to be working, backlight is on, and the function (FN) keys 
are working, can change volume and so on...

Suspend/sleep/poweroff:
Suspending/sleeping when the lid is closed appears to be broken, when I open 
the laptop I can see the keyboard light-up but the screen in black. No problem 
rebooting and turning off.


Summary:
Most things work with the new kernel (4.8), camera is not working and the 
sleep/suspend function are broken.


Let me know if you have any questions :) I should be getting updates from this 
post.

-- 
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/028096bb-e581-4437-bd96-3ae3a469ba05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-Razer-Blade_Stealth-20161214-110949.yml
Description: Binary data


[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

2016-12-14 Thread Foppe de Haan
On Wednesday, December 14, 2016 at 4:33:24 PM UTC+1, Reg Tiangha wrote:
> On 12/14/2016 06:03 AM, Foppe de Haan wrote:
> > To clarify: this has to be done in every template in which you want to use 
> > this? Or can I just copy the whole dir after compiling (seems necessary for 
> > the make install-deb step?), install whatever packages I need to perform 
> > the post-build steps, and perform those? 
> > (thinking of D8-template, D9-, Whonix-gw/ws)
> >
> For Debian systems, you only need to follow the coldhak instructions
> once to create the kernel deb packages. If you want to take your work
> and install it on other Debian templates without having to set up the
> dev environment again, just install the qubes-kernel-vm-support and
> grub2-common packages on them (and you'll probably want paxctl too to
> help with managing the pax stuff until you've figured out what you want
> your pax ruleset to look like), then copy over the linux-headers and
> linux-image packages that you had just made and install them in that
> order (headers first, then image). Install the firmware packages only if
> you need them. That seemed to work for me.
> 
> Make sure to clone the templates you want to try this on for testing
> purposes if you don't want to lose your originals; for example, by
> default, you won't be able to connect to a Whonix template running
> coldkernel as qrexec won't start up properly (but if you switch back to
> a normal kernel, it'll work fine again). And if you enable this on a
> service vm like sys-net, no machine configured to use it as a net vm
> will start up. I don't know how to troubleshoot this or fix this, so if
> anyone out there figures that part out, please share.
> 
> Don't forget to follow the rest of the coldhak instructions to install
> and configure paxctld, set up grub, and to add the relevant grsecurity
> groups!
> 
> sudo groupadd -g 9001 grsecproc
> sudo groupadd -g 9002 tpeuntrusted
> sudo groupadd -g 9003 denysockets

Thanks. When building this in d9-t, I get 'recipe failed' "Error 2" pretty soon 
after starting the build process. No idea why, as there is no log, and I don't 
see an option to provide one (or to provide verbose output).

-- 
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/419170d5-1082-4117-acb0-57d76b72%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: HCL - Custom AMD APU build

2016-12-14 Thread superlative
On Saturday, December 10, 2016 at 1:44:58 PM UTC-8, superlative wrote:
> I got Tor browser on Whonix vm to work by updating the whonix-ws template vm

I'm considering adding the HCL support files .cpio.gz, but it the instructions 
say there are risks with adding the serial number in them. Can someone please 
tell me what are those risks before I post them?

By the way, I thought I updated the Whonix template before saying it didn't 
work, but apparently I only updated the Whonix-gw template, and I really needed 
to update the Whonix-ws template. Once I did that I got anon-whonix Tor Browser 
to work.

-- 
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/d782a37e-81fb-4cba-a445-d0fd0cb93c56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Nvidia drivers in dom0 still works? (need to get a GTX 1070 off the ground)

2016-12-14 Thread Foppe de Haan
On Wednesday, December 14, 2016 at 5:48:37 PM UTC+1, johny...@sigaint.org wrote:
> On a side note, one of Qubes strengths is the fast vchan-based gui/guid
> system.  Using shared memory, it updates the screen a lot faster than,
> say, VNC (the typical way of using Xen), allowing playing videos and such,
> even under nouveau.

Well, playing videos at ~1080p max, on a ~1080p screen. 1080p on a 2160p screen 
is quite laggy already, never even mind 2160p@2160p. :)

-- 
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/3a0a2811-36f8-40e3-bc3d-294f2e84bbc1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Intel HD 620 graphics drivers, how to install in dom0 ?

2016-12-14 Thread Krasi
On Tuesday, December 13, 2016 at 3:21:28 PM UTC-6, Krasi wrote:
> Hi everyone, I am having trouble with the graphics and only have 800x600 
> resolution, tried to add more resolutions using xrandr but I get an error 
> "Failed to get size of gamma for output default" which I figured is due to 
> not having the correct drivers.
> 
> Intel appears to have a tool for Fedora to install their drivers but I am not 
> sure how to install it under dom0 considering there is no network access:
> https://01.org/linuxgraphics/downloads/intel-graphics-update-tool-linux-os-v2.0.2
> 
> Is that my best chance to get my graphics card working and get some higher 
> resolution ? Would you suggest something else or do you know how I can 
> accomplish this ?
> 
> I am using Intel Kaby Lake i7-7500U with the integrated HD 620 graphics.
> 
> 
> Any help would be appreciated.
> 
> Thanks


Actually I got this resolved. I had to update to kernel 4.8.12 and then edit 
the EFI partition. I copied the kernel files from /boot to the EFI partition 
and then modified the xen.cfg file to boot into the 4.8.12 kernel and the 
graphics are working now.

-- 
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/cd6c64cd-04f2-4de1-a1a1-6779e9f4258e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Change screen dimension in qubes

2016-12-14 Thread pl11ty
Hi
Is there a guide to change screen resolution in qubes? I mean that
"fingerprint" the sites track and can see on whoer.net

Thank you in advance

-- 
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/7575032573455a08f94c77e0b0351e95.webmail%40localhost.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Fwd: I recently installed Qubes and I now have several problems

2016-12-14 Thread explodingbee .
-- Forwarded message --
From: explodingbee . 
Date: Wed, Dec 14, 2016 at 12:22 PM
Subject: Fwd: I recently installed Qubes and I now have several problems
To: dumbcyber , Andrew David Wong ,
Foppe de Haan <0spinbo...@gmail.com>



-- Forwarded message --
From: explodingbee . 
Date: Wed, Dec 14, 2016 at 11:15 AM
Subject: Re: I recently installed Qubes and I now have several problems
To: dumbcyber 




*Hi dubmcyber,*
*See my comment below.*

On Wed, Dec 14, 2016 at 6:29 AM, dumbcyber  wrote:

> On Tuesday, 13 December 2016 21:29:28 UTC-5, explodingbee .  wrote:
> > Hi folks,
> >
> > I installed qubes several days ago.  I now have several problems and I
> would appreciate some help:
> >
> > 1) How can I open WIndows 7 again?  First, I intended to install Qubes
> beside Windows 7, which was working fine.  Instead I can only boot to Qubes
> now.  How can I have a dual-boot setup so that I can also go to Windows 7?
> (Note: my files from Windows 7 were apparently not damaged and I have
> recently managed to get apparently all of them off of the computer and onto
> an external hard drive so they should be safe.)  (I did read this file [
> https://www.qubes-os.org/doc/multiboot/] but it seems to say that one
> needs to wipe out everything and reinstall Windows 7 and then reinstall
> Qubes.  Can't I fix the GRUB file somehow so that I can use my existing
> installations and programs?)
> >
> > 2) In Qubes the computer often gets slow as molasses.  I get error
> messages saying "Warning: unresponsive script" sometimes.  When I try to
> open a VM it says that there is not enough memory and that I should close a
> VM first.  When the computer gets like this sometimes I click on things and
> nothing happens or it takes forever for something to happen; sometimes I
> can't even close windows because they don't respond.  (I am using an HP
> Elitebook 8540w laptop.  It has 4 GB of RAM and an i7 CPU.)  Also, when I
> shut down the computer sometimes it gets stuck and does not shut down all
> the way.  It freezes with the Qubes splash screen there and the progress
> bar indicating partial or complete progress.
> >
> >
> > 3) Problem relating to program installation:  When I install programs in
> the Fedora or Debian templates they don't appear in the list of available
> programs in the templates or in the VMs based on those templates so I don't
> see how I can create shortcuts for programs in my VMs.
> >
> >
> > 4) Problem in getting a video player to work:  I have installed four
> different video players (Snappy, Budgie, Banshee and Parole) and none of
> them seem to be able to play videos I have downloaded (with Video Download
> Helper and Firefox in an App VM).  (I can get the video players to launch
> not with the proper shortcuts but in another, awkward way, by going to
> Domain: personal -> personal: Software and then clicking around until I get
> to the right app which was previously installed and then clicking on
> "launch.")  Also, the default player, apparently called "Videos," doesn't
> work.  Am I missing something here?
> >
> >
> >
> > This paragraph shows the problems which arise when I try to use each of
> the above mentioned video players.  You may (or may not) want to skip this
> paragraph.  (I am including these video player error descriptions partly
> because they may give a clue as to an overall problem here.)
> >  (a) Snappy: The video player shows that a video has loaded but then
> when I click play it does nothing.
> >  (b) Parole: When I try to play a video I get the following error
> message: "Error   GStreamer backend error   Could not intialize Xv
> output."  The only button to click on the error message dialogue box says:
> "Close."
> >  (c) Banshee: This video player doesn't play videos when I click
> play.  It sometimes causes an error message which reads: "Additional
> multimedia codecs requires.  An application is requesting additional
> multimedia codecs."  Then there is a button which reads "find in
> software."  (Other times when I click play after selecting a video the
> video player just does nothing.)
> >  (d) Budgie: This videos player does nothing when I click play after
> a video which has been loaded into the program is selected.
> >  (e) Videos:  (Apparently this video player is called "Videos."  It
> is the default player.)  When I select a video and then select "Play with
> Videos" an error message comes up.  It says: "H.264 (Constrained Baseline
> Profile) decoder, MPEG-4 AAC decoder are required to play the file, but are
> not installed."  Then there is a button which says "Find in software."
> When I click that button I get another error message which says
> "Unfortunately, the H.264 (Constrained Baseline Profile) decoder and MPEG-4
> AAC decoder you were searching for could not be found.  

[qubes-users] Fwd: I recently installed Qubes and I now have several problems

2016-12-14 Thread explodingbee .
-- Forwarded message --
From: explodingbee . 
Date: Wed, Dec 14, 2016 at 12:21 PM
Subject: Fwd: I recently installed Qubes and I now have several problems
To: Foppe de Haan <0spinbo...@gmail.com>, Andrew David Wong <
a...@qubes-os.org>, dumbcyber 



-- Forwarded message --
From: explodingbee . 
Date: Wed, Dec 14, 2016 at 11:15 AM
Subject: Re: I recently installed Qubes and I now have several problems
To: Foppe de Haan <0spinbo...@gmail.com>




*Hi Foppe de Haan:*
*See my comments below:*

On Wed, Dec 14, 2016 at 3:13 AM, Foppe de Haan <0spinbo...@gmail.com> wrote:

> re: 1, can you boot to windows from the bios boot menu (usually accessed
> via f9/f11)? If you can, that's a rather easier solution.
>
> re: 3, do you mean the list of available programs in the 'add more
> shortcuts' view?
>

*Yes, that is what I mean.*


>
> re: 4, this has to do with the licensing for modern codecs, which is
> non-free. Instructions to add a repository which contains those here:
> https://unitedrpms.github.io/


*Ok.  Thanks.  When I reinstall Qubes I will try that (if necessary).  *

>
>
> re: 5, try this: "sudo dnf --releasever=25 
> --enablerepo=qubes-vm-r3.2-current-testing
> update"




*Thanks, when I reinstall I may try that.  But two of the other people who
responded said or implied that maybe I should use Fedora 24 instead.  So
maybe I will try Fedora 24.*


*Regards,*
*Vincent*

-- 
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/CAEgwnuQ7gCURhb87p5kj8rW7bXpKWXQhT9wUi0KMb%3DmWdHJuLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Fwd: [qubes-users] I recently installed Qubes and I now have several problems

2016-12-14 Thread explodingbee .
-- Forwarded message --
From: explodingbee . 
Date: Wed, Dec 14, 2016 at 12:23 PM
Subject: Fwd: [qubes-users] I recently installed Qubes and I now have
several problems
To: Andrew David Wong , Foppe de Haan <
0spinbo...@gmail.com>, dumbcyber 



-- Forwarded message --
From: explodingbee . 
Date: Wed, Dec 14, 2016 at 11:17 AM
Subject: Re: [qubes-users] I recently installed Qubes and I now have
several problems
To: Andrew David Wong 




*Hi Andrew Wong,*
*See my comments below.*

On Wed, Dec 14, 2016 at 9:20 AM, Andrew David Wong  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2016-12-13 18:29, explodingbee . wrote:
> > [...]
> >
> > 2) *In Qubes the computer often gets slow as molasses.*  I get
> > error messages saying "Warning: unresponsive script" sometimes.
> > When I try to open a VM it says that there is not enough memory and
> > that I should close a VM first.  When the computer gets like this
> > sometimes I click on things and nothing happens or it takes forever
> > for something to happen; sometimes I can't even close windows
> > because they don't respond.  (I am using an HP Elitebook 8540w
> > laptop.  It has 4 GB of RAM and an i7 CPU.)  Also, when I shut down
> > the computer sometimes it gets stuck and does not shut down all the
> > way.  It freezes with the Qubes splash screen there and the
> > progress bar indicating partial or complete progress.
> >
>
> I think this is just due to a lack of RAM. 4 GB is the bare minimum.
> Any chance you can add some more?
>

*I have not had any problems with lack of RAM in Windows 7.  Maybe Qubes
needs more RAM than Windows 7?  If you are correct I can certainly get more
RAM.  After I reinstall Qubes if the problem persists I may get more RAM.*

>
> > 3) *Problem relating to program installation:*  When I install
> > programs in the Fedora or Debian templates they don't appear in the
> > list of available programs in the templates or in the VMs based on
> > those templates so I don't see how I can create shortcuts for
> > programs in my VMs.
> >
>
> Are you installing these programs from the Fedora and Debian repos? If
> so, are you fully shutting down the template after installing the
> program? This should trigger qvm-sync-appmenus, but you can try to run
> it manually from dom0:
>
> qvm-sync-appmenus 
>

*Yes, I was installing from within the Fedora VM (which is what I think you
mean).  Yes, I fully shut everything down, including the whole computer,
after installing the programs and then at no time did the installed
programs appear on the list of available programs in the Fedora VM or in
the AppVMs.  If the problem persists after I reinstall Qubes I may try to
manually enter the phrase you provided above.*

>
> > 4) *Problem in getting a video player to work:*  I have installed
> > four different video players (Snappy, Budgie, Banshee and Parole)
> > and none of them seem to be able to play videos I have downloaded
> > (with Video Download Helper and Firefox in an App VM).  (I can get
> > the video players to launch not with the proper shortcuts but in
> > another, awkward way, by going to Domain: personal -> personal:
> > Software and then clicking around until I get to the right app
> > which was previously installed and then clicking on "launch.")
> > Also, the default player, apparently called "Videos," doesn't work.
> > Am I missing something here?
> >
>
> I haven't had any problems with VLC. I'd recommend giving that a try,
> if you're willing. You can easily enable the RPMFusion repos to get it:
>
> https://www.qubes-os.org/doc/software-update-vm/#rpmfusion-for-a-fedora-
> templatevm
>

*I have also used VLC before in Windows and I liked it.  It is a video
player which can play almost any type of video file.  After I reinstall
Qubes if I am still having video problems I will probably try to install
it.  Thanks for sending the page to help with that.*

>
> > [...]
> >
> > 5) *I can't update Fedora:*  I have tried to update Fedora 23 to
> > Fedora 25.  I am able to download the update but then I click
> > "Install" and nothing happens.  I also click "restart and install"
> > just below that and again nothing happens.  What is going on with
> > that?  (I just tried that again and I got the following error
> > message this time:  *"Sorry this did not work  Upgrade to Fedora
> > failed.  DetailsDetailed errors from the package manager
> > follow:**  Error running transaction: installing package
> > filesystem-3.2-37.fc24.x86_64 needs 135168 on the /rw
> > filesystem")*
> >
>
> Instead of trying to upgrade to Fedora 25, I'd recommend upgrading to
> Fedora 24 for now (unless you specifically require 25 for some
> reason). Fedora 24 templates are supported (assuming you're running
> Qubes 3.2), whereas Fedora 25 is not yet supported:
>
> 

Re: [qubes-users] I recently installed Qubes and I now have several problems

2016-12-14 Thread explodingbee .
*Hi Andrew,*
*See my comments below:*

On Wed, Dec 14, 2016 at 11:33 AM, Andrew David Wong 
wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> (Please keep the list CCed.)
>

*Ok.  I thought that was automatically happening.  I guess it was not.  I
will cc qubes-users@googlegroups.com  in
future correspondence.*

>
> On 2016-12-14 08:17, explodingbee . wrote:
> > *Hi Andrew Wong,* *See my comments below.*
> >
> > On Wed, Dec 14, 2016 at 9:20 AM, Andrew David Wong
> >  wrote:
> >
> > On 2016-12-13 18:29, explodingbee . wrote:
>  [...]
> 
>  2) *In Qubes the computer often gets slow as molasses.*  I
>  get error messages saying "Warning: unresponsive script"
>  sometimes. When I try to open a VM it says that there is not
>  enough memory and that I should close a VM first.  When the
>  computer gets like this sometimes I click on things and
>  nothing happens or it takes forever for something to happen;
>  sometimes I can't even close windows because they don't
>  respond.  (I am using an HP Elitebook 8540w laptop.  It has
>  4 GB of RAM and an i7 CPU.)  Also, when I shut down the
>  computer sometimes it gets stuck and does not shut down all
>  the way.  It freezes with the Qubes splash screen there and
>  the progress bar indicating partial or complete progress.
> 
> >
> > I think this is just due to a lack of RAM. 4 GB is the bare
> > minimum. Any chance you can add some more?
> >
> >
> >> *I have not had any problems with lack of RAM in Windows 7. Maybe
> >> Qubes needs more RAM than Windows 7?  If you are correct I can
> >> certainly get more RAM.  After I reinstall Qubes if the problem
> >> persists I may get more RAM.*
> >
>
> Yes. Windows 7 requires a minimum of 1 GB for 32-bit and 2 GB for
> 64-bit, whereas Qubes requires a minimum of 4 GB (and is available
> only as a 64-bit operating system). Take a look at our system
> requirements:
>
> https://www.qubes-os.org/doc/system-requirements/


*Yes, I see that 4 Gb is the minimum RAM requirement.  I suspect though
that there may have been some problem with the Qubes installation file
which was causing this issue.  But if the problem persists after I
reinstall Qubes I can get more RAM.*

>
>
> >
>  3) *Problem relating to program installation:*  When I
>  install programs in the Fedora or Debian templates they
>  don't appear in the list of available programs in the
>  templates or in the VMs based on those templates so I don't
>  see how I can create shortcuts for programs in my VMs.
> 
> >
> > Are you installing these programs from the Fedora and Debian
> > repos? If so, are you fully shutting down the template after
> > installing the program? This should trigger qvm-sync-appmenus, but
> > you can try to run it manually from dom0:
> >
> > qvm-sync-appmenus 
> >
> >
> >> *Yes, I was installing from within the Fedora VM (which is what
> >> I think you mean).  Yes, I fully shut everything down, including
> >> the whole computer, after installing the programs and then at no
> >> time did the installed programs appear on the list of available
> >> programs in the Fedora VM or in the AppVMs.  If the problem
> >> persists after I reinstall Qubes I may try to manually enter the
> >> phrase you provided above.*
> >
>
> How were you installing them? Were you using a command like `sudo dnf
> install ` in a Fedora TemplateVM, or were you installing
> them in some other way, instead?
>

*I was installing programs by going to the "software" link in the Fedora
domain and then clicking around until I found the video or other program I
wanted and then clicking on "install."  I did not use any command lines.*

>
> In any case, in order to have a menu entry, there has to be an
> appropriate .desktop file for the program. You can write one yourself
> if necessary, but usually programs installed through a package manager
> like dnf or apt-get do this for you.
>
> >
>  4) *Problem in getting a video player to work:*  I have
>  installed four different video players (Snappy, Budgie,
>  Banshee and Parole) and none of them seem to be able to play
>  videos I have downloaded (with Video Download Helper and
>  Firefox in an App VM).  (I can get the video players to
>  launch not with the proper shortcuts but in another, awkward
>  way, by going to Domain: personal -> personal: Software and
>  then clicking around until I get to the right app which was
>  previously installed and then clicking on "launch.") Also,
>  the default player, apparently called "Videos," doesn't work.
>  Am I missing something here?
> 
> >
> > I haven't had any problems with VLC. I'd recommend giving that a
> > try, if you're willing. You can easily enable the RPMFusion repos
> > to get it:
> >
> > https://www.qubes-os.org/doc/software-update-vm/#rpmfusion-for-a-
> > fedora-templatevm
> >
> 

Re: [qubes-users] Re: Nvidia drivers in dom0 still works? (need to get a GTX 1070 off the ground)

2016-12-14 Thread johnyjukya
TomL Wrote:
> I believe that Nvidia binary drivers do not work under Xen. I spent a
> while trying unsuccessfully before reading some documentation to that
> effect which I considered reliable at the time, but can't immediately
> recall. If you find credible evidence that there's some workaround, I'd
> love to see it (and get my own Nvidia card working under Xen in Qubes!).
> Unfortunately, I currently believe that it is impossible.

Sorry I can't give you direct advice, as I haven't tried it on Qubes yet
(don't want to upset my working configuration, nor increase attack surface
using proprietary drivers), but...

I have installed the nvidia drivers (304 version) on Xen/Debian and it
worked fine.  Same version of Xen, so it should be possible to get the
nvidia drivers working, and I have heard of others having success on
Qubes.

In installing the "alternative" drivers, if you install the wrong one
(some older cards need the 304 version, not the newer 340 version, I
think), and try to recover, the configuration can get messy.

I still don't fully understand why mesa (free version of glx) adds another
layer of alternative redirection on top of things, nor necessarily how it
all is supposed to work.  (There's the alternatives system, then mesa also
redirects things somehow, so it's hard to know what drivers are active at
times.)

Oh yeah, when I did successfully install the nvidia drivers, once a day or
so, when running an accelerated program, things would freeze and crash. 
Even though the default nouveau drivers are slower, they do seem to be a
more reliable.

On a side note, one of Qubes strengths is the fast vchan-based gui/guid
system.  Using shared memory, it updates the screen a lot faster than,
say, VNC (the typical way of using Xen), allowing playing videos and such,
even under nouveau.

Cheers,

-jj

-- 
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/29f2e2fe42b37cb89f0340a7e8139941.webmail%40localhost.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates

2016-12-14 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-14 07:08, jasonwalshismyn...@gmail.com wrote:
> After running this process a couple times :
> 
> https://www.qubes-os.org/doc/upgrade-to-r3.2/
> 
> I think I was able to upgrade to 3.2, but with new problems
> 
> Here's the results for "yum info qubes-core-dom0" :
> 
> Redirecting to '/usr/bin/dnf info qubes-core-dom0' (see 'man yum2dnf')
> 
> Failed to synchonize cache for repo 'updates', disabling.
> Failed to synchonize cache for repo 'fedora', disabling.
> Failed to synchonize cache for repo 'qubes-templates-itl', disabling.
> Failed to synchonize cache for repo 'qubes-dom0-current', disabling.
> Installed Packages:
> Name: qubes-core-dom0
> Arch: x86_64
> Version : 3.2.12
> Release : 1.fc23
> Size: 1.7 M
> Repo: @System
> Summary : The Qubes core files (Dom0-side)
> URL : http://www.qubes-os.org
> License : GPL
> Description : The Qubes core files for installation on Dom0.
> 
> I also notice that there is no more wifi network.
> 
> And when I try to start a VM i get this message :
> 
> "Error starting VM 'email': Error: Failed to connect to qmemman: [errno 2] no 
> such file or directory"
> 
> Anyone can help to properly finish this upgrade to 3.2 process ?
> 

Did you proceed to upgrade your TemplateVMs according to the instructions after 
upgrading dom0?

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYUXUoAAoJENtN07w5UDAweBEP/igz1PgdnzY+DKhTjDiAZmj/
KTIM52T7oL+eF2xnQs/cYV+NHNgPzcQTvVEC2+Wkhus7cXBRqK9vI9RL1uVo6nAe
8aQpib0uCwPiGhhCXP65NLb+BFxafslpJhqyoz9SEZ3k9DVpknR/GrRM4/r63qBj
8fuWdaBDT+3AZtwXRsSyh/ic+hzcw6+UKKY3NZg+mnF3THOQh+699PkeXiuHVW6l
UMpASV6W+HJbKikCXUCJI8QdD603WOI4qgM6uIzrxKUlW/jcNKlOYJ4eylZ1Csvc
6EPJt4NqjsLm+N+MMH90tr6aMiW5Cy6FQcOTWGS/KTRzUxLqNtSoMxpaoxIybZ7q
Y/CiSq4THgS1AUoqsLsW4uti5cuAPgThh3cXnpkXhITnNafGQ2Uiu45GmTH0bstz
9NqT7HHsue6lg0EDDH1ug0WlsGmGrr2OdqTkDHLxDbZGGmHuEqHohzEqQwdSWe3a
ngVMdl7wTGl6hDUjwwYKLKHGJyrlNenQ5kjNp+wg4jz1bfXr26FcM59AHsIPM5je
6XSHfQRY5OBp/63VbodBhmTyG2JgMtUyLTj6l8B+87zDsai8f05EceFWNE2+gS5B
jBEy5AeDJSKFOYwYeVuQH9veoDY+YmYa97bUfslVDONAJ1VOjIZIBaecfktcI8jx
aY6jYJJa8tkyTP4CRm4S
=NZ5p
-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/d754e0e5-5bce-18b4-1084-df0dbc47bc64%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] I recently installed Qubes and I now have several problems

2016-12-14 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

(Please keep the list CCed.)

On 2016-12-14 08:17, explodingbee . wrote:
> *Hi Andrew Wong,* *See my comments below.*
> 
> On Wed, Dec 14, 2016 at 9:20 AM, Andrew David Wong 
>  wrote:
> 
> On 2016-12-13 18:29, explodingbee . wrote:
 [...]
 
 2) *In Qubes the computer often gets slow as molasses.*  I 
 get error messages saying "Warning: unresponsive script" 
 sometimes. When I try to open a VM it says that there is not 
 enough memory and that I should close a VM first.  When the 
 computer gets like this sometimes I click on things and 
 nothing happens or it takes forever for something to happen; 
 sometimes I can't even close windows because they don't 
 respond.  (I am using an HP Elitebook 8540w laptop.  It has
 4 GB of RAM and an i7 CPU.)  Also, when I shut down the 
 computer sometimes it gets stuck and does not shut down all 
 the way.  It freezes with the Qubes splash screen there and 
 the progress bar indicating partial or complete progress.
 
> 
> I think this is just due to a lack of RAM. 4 GB is the bare 
> minimum. Any chance you can add some more?
> 
> 
>> *I have not had any problems with lack of RAM in Windows 7. Maybe
>> Qubes needs more RAM than Windows 7?  If you are correct I can
>> certainly get more RAM.  After I reinstall Qubes if the problem
>> persists I may get more RAM.*
> 

Yes. Windows 7 requires a minimum of 1 GB for 32-bit and 2 GB for
64-bit, whereas Qubes requires a minimum of 4 GB (and is available
only as a 64-bit operating system). Take a look at our system
requirements:

https://www.qubes-os.org/doc/system-requirements/

> 
 3) *Problem relating to program installation:*  When I 
 install programs in the Fedora or Debian templates they
 don't appear in the list of available programs in the
 templates or in the VMs based on those templates so I don't
 see how I can create shortcuts for programs in my VMs.
 
> 
> Are you installing these programs from the Fedora and Debian
> repos? If so, are you fully shutting down the template after
> installing the program? This should trigger qvm-sync-appmenus, but
> you can try to run it manually from dom0:
> 
> qvm-sync-appmenus 
> 
> 
>> *Yes, I was installing from within the Fedora VM (which is what
>> I think you mean).  Yes, I fully shut everything down, including 
>> the whole computer, after installing the programs and then at no 
>> time did the installed programs appear on the list of available 
>> programs in the Fedora VM or in the AppVMs.  If the problem 
>> persists after I reinstall Qubes I may try to manually enter the 
>> phrase you provided above.*
> 

How were you installing them? Were you using a command like `sudo dnf
install ` in a Fedora TemplateVM, or were you installing
them in some other way, instead?

In any case, in order to have a menu entry, there has to be an
appropriate .desktop file for the program. You can write one yourself
if necessary, but usually programs installed through a package manager
like dnf or apt-get do this for you.

> 
 4) *Problem in getting a video player to work:*  I have 
 installed four different video players (Snappy, Budgie, 
 Banshee and Parole) and none of them seem to be able to play 
 videos I have downloaded (with Video Download Helper and 
 Firefox in an App VM).  (I can get the video players to 
 launch not with the proper shortcuts but in another, awkward 
 way, by going to Domain: personal -> personal: Software and 
 then clicking around until I get to the right app which was 
 previously installed and then clicking on "launch.") Also, 
 the default player, apparently called "Videos," doesn't work.
 Am I missing something here?
 
> 
> I haven't had any problems with VLC. I'd recommend giving that a 
> try, if you're willing. You can easily enable the RPMFusion repos 
> to get it:
> 
> https://www.qubes-os.org/doc/software-update-vm/#rpmfusion-for-a- 
> fedora-templatevm
> 
> 
>> *I have also used VLC before in Windows and I liked it.  It is a 
>> video player which can play almost any type of video file.
>> After I reinstall Qubes if I am still having video problems I
>> will probably try to install it.  Thanks for sending the page to
>> help with that.*
> 

You're very welcome!

> 
 [...]
 
 5) *I can't update Fedora:*  I have tried to update Fedora
 23 to Fedora 25.  I am able to download the update but then
 I click "Install" and nothing happens.  I also click
 "restart and install" just below that and again nothing
 happens.  What is going on with that?  (I just tried that
 again and I got the following error message this time:
 *"Sorry this did not work  Upgrade to Fedora failed.  Details
 Detailed errors from the package manager follow:**  Error
 running transaction: installing package
 filesystem-3.2-37.fc24.x86_64 

Re: [qubes-users] Qubes-manager refuses to launch

2016-12-14 Thread johnyjukya
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Wed, Dec 14, 2016 at 06:44:35AM -0800, Andrew David Wong wrote:
>> On 2016-12-14 06:31, harh...@gmail.com wrote:
>> > I did that already, so...
>> >
>> > That's the point - I can't run any command, cause vm-manager (and
>> > the process itself) seems to do not run, "dnf remove" reports of
>> > not-existing packets (cant match the arguments
>> > "qubes-template-fedora-24" and so on.. It is a record within *file
>> > where this VM mentioned and vm-manager checks it..)
>> >
>> > #. Yes, I have a Backup, but wish to repair this state... if it
>> > is impossible -> then ok, I'll do backup#
>> >
>>
>> I understand. I'm afraid I don't know how to fix the broken state your
>> system is currently in, but maybe someone else does. My message was
>> mainly about how to avoid this situation from recurring in the future.
>
> At every system startup backup of qubes.xml is created in
> /var/lib/qubes/backup - you can restore it from there, then remove
> template using correct tools.

I have had cases when it appears that QubesManager appears like it will
not start, but the reason is because it sees another one running so holds
off (but sticks around).  The other instance is windowless and usually
wedged somehow (typically on libvirt--I'm not a big fan of that layer).

As root, do a "ps ax | grep qubes-manager" to find the running process (a
python process).  kill (or kill -9 if needed) that process #.  All of
them, if there's more than one.  Then re-run qubes-manager with
"qubes-manager".

If libvirtd is being stupid, a "sudo systemctl restart libvirtd".  That
often wakes up a non-responsive system for me.  (If that's the problem,
kill qubes-manager, restart libvirtd, then run qubes-manager.)

-JJ

-- 
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/8230d4fa65d9b187c916b1a2a268e8da.webmail%40localhost.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: I recently installed Qubes and I now have several problems

2016-12-14 Thread explodingbee .
Hi folks,

Thank you all for your responses.  There is some significant new
information at this point:

Last night I was able to install Linux Mint beside the other operating
systems.  It is not that I wanted to use Mint, it is just that by
installing it it redid the GRUB file so now I can boot to Windows 7 or
Qubes (or Mint).  So that solves the first problem.  (I had tried to do
this previously but was unable to.  Last night I deleted most of the files
[which I was able to copy to an external hard drive] from the hard drive
and apparently that made a difference.)

However, now for some reason Qubes doesn't work right at all.  The Dom0
domain doesn't load.  (I can see that this is true because it isn't there
and also I could read one of the error messages while the program was
loading.  It said something like "FAIL.  Dom0 did not load.")  So I am
going to download a fresh copy of Qubes and then reinstall it.

So it may be that after I reinstall Qubes some of these problems I have
been having will be resolved.  Nonetheless, I will answer the questions
where appropriate that each of you posed because I appreciate your help and
also because I may have the same issues when I reinstall.

(Note: I am going out of town later today so it may be several days before
I can reinstall Qubes.)

Best regards,

Vincent

On Tue, Dec 13, 2016 at 9:29 PM, explodingbee . 
wrote:

> Hi folks,
>
> I installed qubes several days ago.  I now have several problems and I
> would appreciate some help:
>
> 1) *How can I open WIndows 7 again?*  First, I intended to install Qubes
> beside Windows 7, which was working fine.  Instead I can only boot to Qubes
> now.  How can I have a dual-boot setup so that I can also go to Windows 7?
> (Note: my files from Windows 7 were apparently not damaged and I have
> recently managed to get apparently all of them off of the computer and onto
> an external hard drive so they should be safe.)  (I did read this file [
> https://www.qubes-os.org/doc/multiboot/] but it seems to say that one
> needs to wipe out everything and reinstall Windows 7 and then reinstall
> Qubes.  Can't I fix the GRUB file somehow so that I can use my existing
> installations and programs?)
>
> 2) *In Qubes the computer often gets slow as molasses.*  I get error
> messages saying "Warning: unresponsive script" sometimes.  When I try to
> open a VM it says that there is not enough memory and that I should close a
> VM first.  When the computer gets like this sometimes I click on things and
> nothing happens or it takes forever for something to happen; sometimes I
> can't even close windows because they don't respond.  (I am using an HP
> Elitebook 8540w laptop.  It has 4 GB of RAM and an i7 CPU.)  Also, when I
> shut down the computer sometimes it gets stuck and does not shut down all
> the way.  It freezes with the Qubes splash screen there and the progress
> bar indicating partial or complete progress.
>
> 3) *Problem relating to program installation:*  When I install programs
> in the Fedora or Debian templates they don't appear in the list of
> available programs in the templates or in the VMs based on those templates
> so I don't see how I can create shortcuts for programs in my VMs.
>
> 4) *Problem in getting a video player to work:*  I have installed four
> different video players (Snappy, Budgie, Banshee and Parole) and none of
> them seem to be able to play videos I have downloaded (with Video Download
> Helper and Firefox in an App VM).  (I can get the video players to launch
> not with the proper shortcuts but in another, awkward way, by going to
> Domain: personal -> personal: Software and then clicking around until I get
> to the right app which was previously installed and then clicking on
> "launch.")  Also, the default player, apparently called "Videos," doesn't
> work.  Am I missing something here?
>
> *This paragraph shows the problems which arise when I try to use each of
> the above mentioned video players*.  You may (or may not) want to skip
> this paragraph.  (I am including these video player error descriptions
> partly because they may give a clue as to an overall problem here.)
>  (a) *Snappy*: The video player shows that a video has loaded but
> then when I click play it does nothing.
>  (b) *Parole*: When I try to play a video I get the following error
> message: "Error   GStreamer backend error   Could not intialize Xv
> output."  The only button to click on the error message dialogue box says:
> "Close."
>  (c) *Banshee*: This video player doesn't play videos when I click
> play.  It sometimes causes an error message which reads: "Additional
> multimedia codecs requires.  An application is requesting additional
> multimedia codecs."  Then there is a button which reads "find in
> software."  (Other times when I click play after selecting a video the
> video player just does nothing.)
>  (d) *Budgie*: This videos player does nothing when I click play
> after a 

[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

2016-12-14 Thread Reg Tiangha
On 12/14/2016 06:03 AM, Foppe de Haan wrote:
> To clarify: this has to be done in every template in which you want to use 
> this? Or can I just copy the whole dir after compiling (seems necessary for 
> the make install-deb step?), install whatever packages I need to perform the 
> post-build steps, and perform those? 
> (thinking of D8-template, D9-, Whonix-gw/ws)
>
For Debian systems, you only need to follow the coldhak instructions
once to create the kernel deb packages. If you want to take your work
and install it on other Debian templates without having to set up the
dev environment again, just install the qubes-kernel-vm-support and
grub2-common packages on them (and you'll probably want paxctl too to
help with managing the pax stuff until you've figured out what you want
your pax ruleset to look like), then copy over the linux-headers and
linux-image packages that you had just made and install them in that
order (headers first, then image). Install the firmware packages only if
you need them. That seemed to work for me.

Make sure to clone the templates you want to try this on for testing
purposes if you don't want to lose your originals; for example, by
default, you won't be able to connect to a Whonix template running
coldkernel as qrexec won't start up properly (but if you switch back to
a normal kernel, it'll work fine again). And if you enable this on a
service vm like sys-net, no machine configured to use it as a net vm
will start up. I don't know how to troubleshoot this or fix this, so if
anyone out there figures that part out, please share.

Don't forget to follow the rest of the coldhak instructions to install
and configure paxctld, set up grub, and to add the relevant grsecurity
groups!

sudo groupadd -g 9001 grsecproc
sudo groupadd -g 9002 tpeuntrusted
sudo groupadd -g 9003 denysockets


-- 
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/o2ronl%24t1s%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] help updating dom0 - no network - stuck with lots of pending updates

2016-12-14 Thread jasonwalshismyname
After running this process a couple times :

https://www.qubes-os.org/doc/upgrade-to-r3.2/

I think I was able to upgrade to 3.2, but with new problems

Here's the results for "yum info qubes-core-dom0" :

Redirecting to '/usr/bin/dnf info qubes-core-dom0' (see 'man yum2dnf')

Failed to synchonize cache for repo 'updates', disabling.
Failed to synchonize cache for repo 'fedora', disabling.
Failed to synchonize cache for repo 'qubes-templates-itl', disabling.
Failed to synchonize cache for repo 'qubes-dom0-current', disabling.
Installed Packages:
Name: qubes-core-dom0
Arch: x86_64
Version : 3.2.12
Release : 1.fc23
Size: 1.7 M
Repo: @System
Summary : The Qubes core files (Dom0-side)
URL : http://www.qubes-os.org
License : GPL
Description : The Qubes core files for installation on Dom0.

I also notice that there is no more wifi network.

And when I try to start a VM i get this message :

"Error starting VM 'email': Error: Failed to connect to qmemman: [errno 2] no 
such file or directory"

Anyone can help to properly finish this upgrade to 3.2 process ?

-- 
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/40e9124a-4f3e-447a-9025-3d5f8b206ba2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes-manager refuses to launch

2016-12-14 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Dec 14, 2016 at 06:44:35AM -0800, Andrew David Wong wrote:
> On 2016-12-14 06:31, harh...@gmail.com wrote:
> > I did that already, so...
> > 
> > That's the point - I can't run any command, cause vm-manager (and
> > the process itself) seems to do not run, "dnf remove" reports of
> > not-existing packets (cant match the arguments
> > "qubes-template-fedora-24" and so on.. It is a record within *file
> > where this VM mentioned and vm-manager checks it..)
> > 
> > #. Yes, I have a Backup, but wish to repair this state... if it
> > is impossible -> then ok, I'll do backup#
> > 
> 
> I understand. I'm afraid I don't know how to fix the broken state your
> system is currently in, but maybe someone else does. My message was
> mainly about how to avoid this situation from recurring in the future.

At every system startup backup of qubes.xml is created in
/var/lib/qubes/backup - you can restore it from there, then remove
template using correct tools.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJYUV+2AAoJENuP0xzK19csEcQIAJrpPsb/z1YaG5bbQvQMiudH
f9BdzJz9qhGCVw2XWglMz0oyR5IcUutw0+26Ilbp/w1SMHJeq4n+pua+qmK6b69/
Xx1hWktKgIXYJmSJ3j8vAjbRLWPRrE9vTwW2oWZB8p0wHg4mQ3O+uounR1Cv/oNv
KGA3UjnQpuayRUp/QvYbVTJLfRg2pX7+GLccNPO6EKk5RCS2IkmcA3ToSypW1qAE
bnwoloI1COjQw4QE4TTLxVU8oPQBl1dTsvDXjr4ggY6efdWANWnKDdDM7mGukBYJ
RXhb1pvtt0U0vd9fvNkcOBp58tRai9M5RGvlDBXmBcwVSdUMFZd8WbuJbaX23Jc=
=Soyy
-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/20161214150526.GA15090%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes-manager refuses to launch

2016-12-14 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-14 06:31, harh...@gmail.com wrote:
> I did that already, so...
> 
> That's the point - I can't run any command, cause vm-manager (and
> the process itself) seems to do not run, "dnf remove" reports of
> not-existing packets (cant match the arguments
> "qubes-template-fedora-24" and so on.. It is a record within *file
> where this VM mentioned and vm-manager checks it..)
> 
> #. Yes, I have a Backup, but wish to repair this state... if it
> is impossible -> then ok, I'll do backup#
> 

I understand. I'm afraid I don't know how to fix the broken state your
system is currently in, but maybe someone else does. My message was
mainly about how to avoid this situation from recurring in the future.

P.S. - Please don't top-post.

> среда, 14 декабря 2016 г., 16:02:19 UTC+2 пользователь Andrew David
> Wong написал: On 2016-12-14 04:19, harh...@gmail.com wrote:
 Hi there! Got a problem with a qubes-manager after updating
 and removing templateVM. Upgrading from fedora-24 to
 fedora-25 was successful, but I couldn't remove TVM
 fedora-24, because TVM was used by some AppVm as manager said
 (and it's not true, I changed default template as well as
 templates in any AppVms). I removed whole record in
 /var/lib/qubes/qubes.xml  and now vm manager gives me import
 error (Unknown template with QID:x) or "Error: 2, 
 '\xd0\xd9\.. ..\xb0')..." if I add a line manually (just
 copy line of another TVM and change QID, name, etc.., but I
 guess it's wrong, while that line requires uuid or smth else
 to be correct, and what I can't know).
 
 Is there any way to deny qubes-manager to check that QID or
 change the list of TVMs?
 
 Thanks...
 
> 
> You shouldn't try to remove a template manually that way, since
> it's likely to cause problems like the ones you're experiencing.
> There are two supported ways:
> 
> 1. In Qubes Manager, right click on the TemplateVM -> "Remove VM"
> 
> Or, if the template cannot be removed in this way because it's 
> RPM-managed:
> 
> 2. In dom0: `sudo dnf remove `
> 
> For example: `sudo dnf remove qubes-template-fedora-24`
> 
> 

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYUVrQAAoJENtN07w5UDAw5mEP/07QpRjqK2WS38aEggblWAxM
mQGBi//ig2pKW8lTbJGHiZ11eENzmbBoQ4Wg99hNcna8htNonBiI/27wLbI8ccFt
h3bggmYSKwxOcvBgrMRgsFe0jsxEk2SXz8/IJNju4QvgB0bbss9HiF08G073ZKBw
jl3I+Q95wvzloV9jTr2P4qMKPE8qA+QfWAd8FRHiC2LcVGYKXT225ynoVZsY8Xu0
npw1M3qH/g7vG64Cig/iM5EcgIXVtRfI+ORu+EbaLApgO/6FRI0EcSIpcqPDhvBv
CIEtLgGcK3sGAyah/CW9C6yTxR14WmREOB9QPxH4K20lAv9jMbxKuNXbKi6EFfVt
6TtQkyYaghg1vdBwWYvDgqnIE7yCHHmryAVOLRHCEo2TQcs4VxEs3BNOVoBShPYE
M6lKCs0Dh27ev7VFYbZAzZCsHoMcwuQQAY776kfI8APEK/kRYtBOk+bNJ1S1Kqen
yE0vLf+UVxp1hrpuTq/soZkI3FyFxFuJhuuB0/3fsia5nCdu9BRE+TsU+OBZtcCF
lMO6zgNm1WwjJZ+7smYAoMHqTHFywPmoMc7s2Ql9cksCXB1FlpfVv/D/b+t5408f
ROTO7mYrbfNhWpNE6WILKL+0HnsocAZBIp9ogx15SCl2GI0sRjg+T5OVpN5dCbJ6
gO7wc3GkfdR4QK0Y8S3+
=Ri2/
-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/31d0e9a4-dfe9-5bf0-a55a-fdc351056c6b%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] "Cannot find unused qid!" when restoring backup

2016-12-14 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-13 12:56, Jeremy Rand wrote:
> Andrew David Wong:
>> On 2016-12-12 21:30, Jeremy Rand wrote:
>>> I just tried to restore 5 VM's from a backup.  The backup was 
>>> made on Qubes 3.0; I'm restoring to Qubes 3.2.  All 5 VM's
>>> fail to restore with this error (although of course the name of
>>> the VM in the error message varies depending on what VM I'm
>>> trying to restore):
> 
>>> -> Restoring QubesAppVm iso-linux... ERROR: Cannot find unused 
>>> qid! *** Skipping VM: iso-linux
> 
>>> The error was copied by hand since copying from dom0 to an
>>> AppVM is difficult, so there might be a typo.  Based on the
>>> error message, I infer that maybe this has something to do with
>>> my Qubes 3.2 system having too many VM's on it already?  Is
>>> that an accurate guess, or is there a different reason for this
>>> error? Is there any workaround?
> 
>>> Cheers, -Jeremy
> 
> 
>> The only other case in which I've seen this happen is when a user
>>  surpassed the maximum number of Qubes VMs (254):
> 
>> https://groups.google.com/d/topic/qubes-users/Zw5XjZndrDo/discussion
>
>>  Did you do the same?
> 
> Looks like it.  I just checked and the highest final IP address
> octet is 253; add 1 for dom0 and it looks like I'm at the limit.
> 
> I realize I'm probably much more gluttonous with VM's than most
> users, but is there by any chance any progress on increasing that
> limit?
> 
> Cheers, -Jeremy
> 

We can see if anyone's interested in providing a patch:

https://github.com/QubesOS/qubes-issues/issues/2519

Please understand that since this falls far outside of normal usage
patterns and affects only a small minority of users, it's going to be
a relatively low-priority issue. Therefore, it's unlikely that this
will be changed soon, unless it either turns out to be trivial to
change, or we receive a patch from the community.

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYUVn6AAoJENtN07w5UDAwTVQQALhZlGJXic7b7PqF5Wh7Cugl
PEr789MPzb2B0ticm6cNypJ2xvpvfY9+9SpK/FzAOv2KwIpOt1TCqUFAVoO9nlEk
BmcOYOoOpYRHF4ll4/rpjn0KcH155sHFKtVnm4ZQg4wBsx40zAGAxizb1yLcrHpA
SA61hRTb1Qpplwzykn03CkgZ+hAXyLZzDv548k80ImmuPeX+7Dlm+m6qXfgJEQ9a
fQ9dsznOsQC84RdYdEt5e6HuT4R8Hwyube8e26PLz61xhJa2AcHFHuhHaL8lpVNN
W38ZrpmQJu8vzeBt/eHm76k/xksYdJKE+KgRqHX1hat7APaD+n1qdBBrXz+oOyZY
M6/wlopzrdaG4jGKBjg4NFsq7ZGJV5arAI7k61KubEEjl+r+WiWby3RrLzapBJQK
yJRyfM7QfkJlhOVkjdHiGEcEe5HCBmQ4LXEaqOHiRRuZqBKQV+vKESft4byNnmLC
P9G+rzXD7IXM8XGf5wkuGXwMcZw61FlOS+q9IrjobLA0BNJg++VB1RMAp7Ja4Fek
TkzZEI1YHtXvX4Nk1skmEqAjHtfeDpwaMOYxdSqEu3mMwBXbVDufqQaBzWeJmgFm
sqP5hGB3sLB+RRC2PpBYPbnWiFkSebh87Fhuc1myHt7FnxBy1a/x+7OQVawCsSI8
705HBTP0V+vzXyB0Ygtu
=btTZ
-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/1fe0aafd-f1be-1114-0cc3-bde266a0b0b8%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes-manager refuses to launch

2016-12-14 Thread harhorg
I did that already, so...

That's the point - I can't run any command, cause vm-manager (and the process 
itself) seems to do not run, "dnf remove" reports of not-existing packets (cant 
match the arguments "qubes-template-fedora-24" and so on.. It is a record 
within *file where this VM mentioned and vm-manager checks it..)

#. Yes, I have a Backup, but wish to repair this state... if it is 
impossible -> then ok, I'll do backup#

среда, 14 декабря 2016 г., 16:02:19 UTC+2 пользователь Andrew David Wong 
написал:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On 2016-12-14 04:19, harh...@gmail.com wrote:
> > Hi there! Got a problem with a qubes-manager after updating and
> > removing templateVM. Upgrading from fedora-24 to fedora-25 was
> > successful, but I couldn't remove TVM fedora-24, because TVM was
> > used by some AppVm as manager said (and it's not true, I changed
> > default template as well as templates in any AppVms). I removed
> > whole record in /var/lib/qubes/qubes.xml  and now vm manager gives
> > me import error (Unknown template with QID:x) or "Error: 2,
> > '\xd0\xd9\.. ..\xb0')..." if I add a line manually (just copy
> > line of another TVM and change QID, name, etc.., but I guess it's
> > wrong, while that line requires uuid or smth else to be correct,
> > and what I can't know).
> > 
> > Is there any way to deny qubes-manager to check that QID or change
> > the list of TVMs?
> > 
> > Thanks...
> > 
> 
> You shouldn't try to remove a template manually that way, since it's
> likely to cause problems like the ones you're experiencing. There are
> two supported ways:
> 
> 1. In Qubes Manager, right click on the TemplateVM -> "Remove VM"
> 
> Or, if the template cannot be removed in this way because it's
> RPM-managed:
> 
> 2. In dom0: `sudo dnf remove `
> 
> For example: `sudo dnf remove qubes-template-fedora-24`
> 
> - -- 
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
> -BEGIN PGP SIGNATURE-
> 
> iQIbBAEBCgAGBQJYUVDPAAoJENtN07w5UDAwceAP90rNqrz4muKS1crboRc62SJT
> IZa44C0Pcvx8wIHkrZ3MUvDcze6tjKqfLygZlxaDz/aFah8TtMifYw5e7ycSAXmS
> KL+OAzWJolyScf+lH8N6ydDddAgJTrvaZY+DGYa8xatuQ/bqfGeduGbTQrnCxVHb
> A+Rt665H9AvvCrgbi2d5xSu4ouT9ZqaWrD/xYWvt9epCBBQWQQ/F+yS0JV413Y+I
> TuoCH84+8EYsFYrUVmbj5rqNUgPFixQd0zmSA1G7g6o0Ax1VxV+z26+r5d2IulRY
> ORn379ZCv23K20cZCSwQhQD/aG58c+9CUY68YiYM2X0swavpvMjR+muaZYYAFCzW
> 34wbDgtP+x/mF5ZEEg5qslNsZNHnHKxquWCRaHjUQznPHpBgkhnNcxkydVxKVlWw
> eAqLp4Qi9akRkGBD4vwTeiwrMl/6Fvf1LMbDYKjzURxH3Uc+507GJNaF+Z3gEuiu
> mNkvxKMLTjjhvmikjT6xvKJXMzPE+MQv4chzKvTsztVZn8caJaK7hDrKOOzAaQsB
> fwqqfB40dwJxF3DSKBWv7tub08fvxKqif6I5MgNfGwGqKMBhX7UR3VSsuriO4+ug
> cr89JQTzpsAeGtytswaEsXDT0aIbweHU40Gnu0vA3e3/VXQ+2/XJfP95hD/m4pMN
> NUebgFGTgafCQ58j+dY=
> =d6Db
> -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/64d3065d-ea65-47df-9c07-10c1a7ed84a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] I recently installed Qubes and I now have several problems

2016-12-14 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-13 18:29, explodingbee . wrote:
> [...]
> 
> 2) *In Qubes the computer often gets slow as molasses.*  I get
> error messages saying "Warning: unresponsive script" sometimes.
> When I try to open a VM it says that there is not enough memory and
> that I should close a VM first.  When the computer gets like this
> sometimes I click on things and nothing happens or it takes forever
> for something to happen; sometimes I can't even close windows
> because they don't respond.  (I am using an HP Elitebook 8540w
> laptop.  It has 4 GB of RAM and an i7 CPU.)  Also, when I shut down
> the computer sometimes it gets stuck and does not shut down all the
> way.  It freezes with the Qubes splash screen there and the
> progress bar indicating partial or complete progress.
> 

I think this is just due to a lack of RAM. 4 GB is the bare minimum.
Any chance you can add some more?

> 3) *Problem relating to program installation:*  When I install
> programs in the Fedora or Debian templates they don't appear in the
> list of available programs in the templates or in the VMs based on
> those templates so I don't see how I can create shortcuts for
> programs in my VMs.
> 

Are you installing these programs from the Fedora and Debian repos? If
so, are you fully shutting down the template after installing the
program? This should trigger qvm-sync-appmenus, but you can try to run
it manually from dom0:

qvm-sync-appmenus 

> 4) *Problem in getting a video player to work:*  I have installed
> four different video players (Snappy, Budgie, Banshee and Parole)
> and none of them seem to be able to play videos I have downloaded
> (with Video Download Helper and Firefox in an App VM).  (I can get
> the video players to launch not with the proper shortcuts but in
> another, awkward way, by going to Domain: personal -> personal:
> Software and then clicking around until I get to the right app
> which was previously installed and then clicking on "launch.")
> Also, the default player, apparently called "Videos," doesn't work.
> Am I missing something here?
> 

I haven't had any problems with VLC. I'd recommend giving that a try,
if you're willing. You can easily enable the RPMFusion repos to get it:

https://www.qubes-os.org/doc/software-update-vm/#rpmfusion-for-a-fedora-
templatevm

> [...]
> 
> 5) *I can't update Fedora:*  I have tried to update Fedora 23 to
> Fedora 25.  I am able to download the update but then I click
> "Install" and nothing happens.  I also click "restart and install"
> just below that and again nothing happens.  What is going on with
> that?  (I just tried that again and I got the following error
> message this time:  *"Sorry this did not work  Upgrade to Fedora
> failed.  DetailsDetailed errors from the package manager
> follow:**  Error running transaction: installing package 
> filesystem-3.2-37.fc24.x86_64 needs 135168 on the /rw
> filesystem")*
> 

Instead of trying to upgrade to Fedora 25, I'd recommend upgrading to
Fedora 24 for now (unless you specifically require 25 for some
reason). Fedora 24 templates are supported (assuming you're running
Qubes 3.2), whereas Fedora 25 is not yet supported:

https://www.qubes-os.org/doc/supported-versions/#templatevms

Here are instructions on upgrading an existing Fedora 23 template to
Fedora 24:

https://www.qubes-os.org/doc/template/fedora/upgrade-23-to-24/

If you just want a fresh Fedora 24 template, it's much easier:

$ sudo qubes-dom0-update qubes-template-fedora-24

> So I am frustrated.  I had a whole life on Windows 7 and now I
> can't do most of what I used to do.  (Do you think that maybe I
> downloaded and installed a bad copy of Qubes?)  Help would be
> appreciated.
> 

You really should verify the ISO before installing from it:

https://www.qubes-os.org/doc/verifying-signatures/

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYUVTtAAoJENtN07w5UDAwwwkP/39LVJl2M+LdNK/Ga953H+33
3XSkxqvg87rTBb/3QogkQlll077TVUXKvKvlEwqbGJN1EJKyQrnjBQ02OYUSuIXA
8UcLo+q33Yf+rENTDeTLrHBMNpSxju4B1S3aCX30ZqtMQXanf01k+Y9p6yGBDRtZ
KJnJhBxI+A9NO9K/hBPk6X1YesFE8tXYdpmTiug0iAC+1BkaCqix4XcKLUMbKeza
keLUVO8ZCgzo7tl7IxLrrEZA9mnfIA0Gs7fJq6fDF+Bg1kitqgVHS2/PWhX343Ao
57MmvKpb2mPTdcj6cDDlt2fAZ2Ub3qov4puqtLnYph63KirwFrK59+4h9upvTk/g
SB5sHz3GFZBZcQW+VYfXKLuOOfvgHhrYv5pkjQqSCRkDni0tIz09M8lJPZ4RrfKr
iNPxrQPz+E3n/+PQt3jC1QB0fxy4ztPwF5Vl3r3MoHhyx4aoAhEuKAI7kSi1rg2m
LVXUPW+lv46BU74c0SP0LxWskKIrE0uTcH6Kp5Ld+W4X5B24qnJUFZ0VO6SwOmh9
YKklN8XCEQJE7kZxOxirnZoGGfZ+D4/KLXTouzxbQ6eU7XihwcXVISTvBxTaPkr3
6ZGGPtmIQhB/fLBs3FfrwpgUQGpGZSEOQIgk7MfmsXIGvljLiQXpBHY6/XlQYGP3
+VG6InfKq+cuyEHQ7al9
=9oH3
-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, 

Re: [qubes-users] Clone qubes machine - any options other than backup and build again?

2016-12-14 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-14 03:19, dumbcyber wrote:
> Hello, I am running Qubes from a 64Gb USB stick.
> 
> I am running R3.2 on my Macbook 11,1, and have built several 
> template VMs, for example Windows.
> 
> What I want to do now is clone the entire USB stick to another USB 
> external SSD drive. In other words I want to be able to stop using 
> the USB stick and move to the SSD drive without building Qubes from
> again scratch and then performing backup/restore all my VMs.
> 
> Is this even possible? Am i dreaming?
> 
> Thanks in advance.
> 

I reckon there's nothing to lose by trying, as long as you keep the
original USB stick. You can try with dd or any program that makes a
bitwise identical image from the USB stick and faithfully writes it
onto the SDD drive.

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYUVIDAAoJENtN07w5UDAwzAwP/0w1+2cu9qFizHAVfApng01g
SPwqL9Gt+lNdYRoUUjSIsBHe2bpY1DDllpiZnTVc1EmK6daq9XjSMs1dVlceUNeV
01uJ2mN68vY6PqZZ0DrREdmK3EteFRo/761qwr+gvQ1A7BqT3gJZjIACauizQ1EC
Jlk0Mr5BO34j9b3zj4bv43M+7fM2tL1kB0i1ISELCeiRF8IHcqd3IQMwF8GD7OfC
iCAXiVj+pBbp7FojUhqrzHYmBj6YK35MmX6BAzwc6L/Zh3XcQsGuBy2SzPPmodgM
kWJ6uRsKCY7k7hCM3nauDfrIeweOr0d4vhOUivx7CjdayCh/W1Z47A1hbId7E+i7
RqSqx/l3ZgEWkgnj5XOM/Pv3CrKIRnBr55fe5EDpgFeAasluGd4XFWHhx/Sx73mt
iqVsk7KzBvvWL7AjThBWLqbwfk2FU0ajE0DJw3/XsGyJxscap8BXiGCPkTi4NaRd
Z4Iy/VJ6RRVTSBbqZ87B28qZmZ/dYYJX7Rll//5OZcEI2XzSGopE882rdmaYG62v
M6fQgpjsBh1QMC36Fe0nlFAN1FPoe2Aneg73wziA1+XKoZRo7iK/rQSb+vL3h9vq
2vZfBDbYkplWonJ6LhukGK4LozpuuaL2AK1Q4xhF8b/LZZII7/MWvkhHUDCMAY6t
nDiTseM0toT5Gp48rPJw
=GoBG
-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/6ec27419-f9d0-7c45-d60b-ece0aa65cf8a%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes-manager refuses to launch

2016-12-14 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-14 04:19, harh...@gmail.com wrote:
> Hi there! Got a problem with a qubes-manager after updating and
> removing templateVM. Upgrading from fedora-24 to fedora-25 was
> successful, but I couldn't remove TVM fedora-24, because TVM was
> used by some AppVm as manager said (and it's not true, I changed
> default template as well as templates in any AppVms). I removed
> whole record in /var/lib/qubes/qubes.xml  and now vm manager gives
> me import error (Unknown template with QID:x) or "Error: 2,
> '\xd0\xd9\.. ..\xb0')..." if I add a line manually (just copy
> line of another TVM and change QID, name, etc.., but I guess it's
> wrong, while that line requires uuid or smth else to be correct,
> and what I can't know).
> 
> Is there any way to deny qubes-manager to check that QID or change
> the list of TVMs?
> 
> Thanks...
> 

You shouldn't try to remove a template manually that way, since it's
likely to cause problems like the ones you're experiencing. There are
two supported ways:

1. In Qubes Manager, right click on the TemplateVM -> "Remove VM"

Or, if the template cannot be removed in this way because it's
RPM-managed:

2. In dom0: `sudo dnf remove `

For example: `sudo dnf remove qubes-template-fedora-24`

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIbBAEBCgAGBQJYUVDPAAoJENtN07w5UDAwceAP90rNqrz4muKS1crboRc62SJT
IZa44C0Pcvx8wIHkrZ3MUvDcze6tjKqfLygZlxaDz/aFah8TtMifYw5e7ycSAXmS
KL+OAzWJolyScf+lH8N6ydDddAgJTrvaZY+DGYa8xatuQ/bqfGeduGbTQrnCxVHb
A+Rt665H9AvvCrgbi2d5xSu4ouT9ZqaWrD/xYWvt9epCBBQWQQ/F+yS0JV413Y+I
TuoCH84+8EYsFYrUVmbj5rqNUgPFixQd0zmSA1G7g6o0Ax1VxV+z26+r5d2IulRY
ORn379ZCv23K20cZCSwQhQD/aG58c+9CUY68YiYM2X0swavpvMjR+muaZYYAFCzW
34wbDgtP+x/mF5ZEEg5qslNsZNHnHKxquWCRaHjUQznPHpBgkhnNcxkydVxKVlWw
eAqLp4Qi9akRkGBD4vwTeiwrMl/6Fvf1LMbDYKjzURxH3Uc+507GJNaF+Z3gEuiu
mNkvxKMLTjjhvmikjT6xvKJXMzPE+MQv4chzKvTsztVZn8caJaK7hDrKOOzAaQsB
fwqqfB40dwJxF3DSKBWv7tub08fvxKqif6I5MgNfGwGqKMBhX7UR3VSsuriO4+ug
cr89JQTzpsAeGtytswaEsXDT0aIbweHU40Gnu0vA3e3/VXQ+2/XJfP95hD/m4pMN
NUebgFGTgafCQ58j+dY=
=d6Db
-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/c332f775-30f1-8c12-73c2-2f7ea0c51c9c%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Qubes Canary #10

2016-12-14 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Qubes Community,

We have just published Qubes Canary #10. The current text of this
canary is reproduced below. The latest version, including any future
corrections, will always be available in the Qubes Security Pack
(qubes-secpack).

View Canary #10 in the qubes-secpack:

https://github.com/QubesOS/qubes-secpack/blob/master/canaries/canary-010-2016.txt

Learn about the qubes-secpack, including how to obtain, verify, and read it:

https://www.qubes-os.org/doc/security-pack/

View all past canaries:

https://www.qubes-os.org/doc/canaries/

- 


---===[ Qubes Canary #10 ]===---


Statements
- ---

The Qubes core developers who have digitally signed this file [1]
state the following:

1. The date of issue of this canary is December  13, 2016.

2. There have been 27 Qubes Security Bulletins published so far.

3. The Qubes Master Signing Key fingerprint is:

427F 11FD 0FAA 4B08 0123  F01C DDFA 1A3E 3687 9494

4. No warrants have ever been served to us with regard to the Qubes OS
Project (e.g. to hand out the private signing keys or to introduce
backdoors).

5. We plan to publish the next of these canary statements in the first
two weeks of March 2017. Special note should be taken if no new canary
is published by that time or if the list of statements changes without
plausible explanation.

Special announcements
- --

* We would like to remind you that Qubes OS has been designed under
the assumption that all relevant infrastructure is permanently
compromised.  This means that we assume NO trust in any of the servers
or services which host or provide any Qubes-related data, in
particular, software updates, source code repositories, and Qubes ISO
downloads.

Disclaimers and notes
- --

This canary scheme is not infallible. Although signing the declaration
makes it very difficult for a third party to produce arbitrary
declarations, it does not prevent them from using force or other
means, like blackmail or compromising the signers' laptops, to coerce
us to produce false declarations.

The news feeds quoted below (Proof of freshness) serves to demonstrate
that this canary could not have been created prior to the date stated.
It shows that a series of canaries was not created in advance.

This declaration is merely a best effort and is provided without any
guarantee or warranty. It is not legally binding in any way to
anybody. None of the signers should be ever held legally responsible
for any of the statements made here.

Proof of freshness
- ---

$ date -R -u
Tue, 13 Dec 2016 10:43:25 +

$ feedstail -1 -n5 -f '{title}' -u 
https://www.spiegel.de/international/index.rss
Unchained: The Man Behind Football Leaks
Money, Money, Money: Football Leaks Shows Us that Football Is Sick
'A Wretched Image': Why Özil Had To Pay 2.8 Million in Back Taxes
Germany's Divided Conservatives: Merkel Critics Deal a Blow to Chancellor
Shell Game: Ronaldo, Mourinho and the Paper Trail to the Caribbean

$ feedstail -1 -n5 -f '{title}' -u 
http://rss.nytimes.com/services/xml/rss/nyt/InternationalHome.xml
Split Over Donald Trump Threatens to Tilt Republican States
Donald Trump Berates Paul Ryan and ‘Disloyal’ Republicans
Donald Trump Faltering? Die-Hard Fans Refuse to Buy It
Group’s Tactic on Hillary Clinton: Sue Her Again and Again
The 2016 Race: How One 19-Year-Old Illinois Man Is Distorting National Polling 
Averages

$ feedstail -1 -n5 -f '{title}' -u http://feeds.bbci.co.uk/news/world/rss.xml
Aleppo civilians 'shot on the spot' - UN
Donald Trump: 'No new business deals' during presidency
Indonesia blasphemy case: Emotional scenes as Ahok trial begins
Venezuela closes border with Colombia 'to destroy mafia'
Burmese army linked to Rohingya village arson, rights group says

$ feedstail -1 -n5 -f '{title}' -u http://feeds.reuters.com/reuters/worldnews
Syrian army takes over Aleppo areas quit by rebels: military source
U.S. says 'one China' policy should not be used as bargaining chip
Exclusive: Top U.S. spy agency has not embraced CIA assessment on Russia 
hacking - sources
Russia's opposition leader Navalny plans to run for president in 2018
Netanyahu says Israel 'mightier' as first F-35 fighter jets arrive


Footnotes
- --

[1] This file should be signed in two ways: (1) via detached PGP
signatures by each of the signers, distributed together with this
canary in the qubes-secpack.git repo, and (2) via digital signatures
on the corresponding qubes-secpack.git repo tags. [2]

[2] Don't just trust the contents of this file blindly! Verify the
digital signatures!

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYUUwnAAoJENtN07w5UDAw7GMP/2O6PKZPrvsTh1/dV2uoWul/
bksxAhr8AH/nZmn5j7BLCYuj4TS2MwrBqpdqKvsalxpDsI9pNSr5N0RaWniy2IQE

[qubes-users] Re: HP PRINTER PROBLEM

2016-12-14 Thread higginsonjim2

Have finally managed to get it working! 

Fedora (which I had not used before) was OK but Debian(my normal OS) was a 
problem! An issue for me was that the relevant drivers were in HPLIP version 
3.15.11 onwards. Standard Fedora in Qubes uses 3.16.3 whereas Debian in QUBES 
uses 3.14.6. This in itself was not a major issue in that I've installed a 
newer version of HPLIP in my normal Debian setup - but replicating that here 
caused problems. I won't summarise endless failures but try and summarise how I 
eventually succeeded.

Started with ETHERNET connection from ROUTER to PRINTER.
 With Fedora I installed yumex-dnf and system-config-printer. A look at yumex 
showed that HPLIP was already there - v 3.16.3. Then in terminal i used 
system-config-printer which opened up the add printer menu. Went for the 
network option and entered Network Connected IP from Printer in host field. 
This gave sub -menu where I think JetDirect and App Socket/HP Jetdirect fields 
were needed. A list of all HP printers appeared from where I could select 
Colorjet MFP M477fdw. Enter a couple of times and it all worked.

With Debian, i installed SYNAPTIC - a check there shows no HPLIP installed and 
offers 3.14.6. I then googled HP LINUX IMAGING AND PRINTING . Followed steps 1 
to 7 - but not step 8. Latter worked fine on normal Debian setup - but didn't 
seem to work here - this was the major frustration.
Instead I keyed "sudo hp-setup -i PRINTERIP" in terminal. Interactive process 
installed additional plugin - but this was straightforward - basically just 
accepting defaults. The process recognised my printer and everything worked. 
However when trying to get access to printer in a new VM I had problems and got 
in a mess with references to "shared", "enabled" in printer dialogue box on PC 
screen. Printer IP keeps changing - which maybe the problem or not . At this 
stage I was still happy because at least I'd seen something print. THEN went 
for another option - went back to USB connection between printer and PC. On 
printer screen I went to SETUP/NETWORK SETUP/ IP4 CONFIG METHOD and chose 
MANUAL option - and went with the default offered - 192.169.xxx.xxx.Having done 
the 1st 7 steps of the HP LINUX IMAGING AND PRINTING NOTE already with DEBIAN 
QUBES, I simply had to key "sudo hp-setup -i 192.168.xxx.xxx" in terminal.
It all flowed through again to successful conclusion.
EVERYTHING APPEARS TO WORK 

Presumably my printer IP ADDRESS is now static. Whether or not I opened up any 
security weakness in QUBES I'm not sure but at the moment I don't care -my 
printer is working! Intend to do more reading from an old UBUNTU manual - on 
networking and PRINTING WITH CUPS - the experience of the last few days might 
enable me to understand the relevant chapters a bit better. As a pensioner I 
have a bit time on my hands - so I can experiment endlessly on the spare hard 
drive I'm using - before committing to moving to QUBES completely. Am likely to 
do this - but want to get to feel at ease with QUBES in a test environment 
first - so will probably convert in NEW YEAR. Hope this note is useful for 
anyone else with PRINTER problems and THANKS AGAIN FOR COMMENTS.

-- 
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/1c017e09-9814-4d14-bf9b-46dfe25a5ea9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: FYI: Experimental Qubes coldkernel support now available

2016-12-14 Thread Foppe de Haan
To clarify: this has to be done in every template in which you want to use 
this? Or can I just copy the whole dir after compiling (seems necessary for the 
make install-deb step?), install whatever packages I need to perform the 
post-build steps, and perform those? 
(thinking of D8-template, D9-, Whonix-gw/ws)

-- 
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/8df80ea2-672d-4039-b7b8-9888d6dd8ae9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Qubes-manager refuses to launch

2016-12-14 Thread harhorg
Hi there! Got a problem with a qubes-manager after updating and removing 
templateVM. Upgrading from fedora-24 to fedora-25 was successful, but I 
couldn't remove TVM fedora-24, because TVM was used by some AppVm as manager 
said (and it's not true, I changed default template as well as templates in any 
AppVms). I removed whole record in /var/lib/qubes/qubes.xml  and now vm manager 
gives me import error (Unknown template with QID:x) or "Error: 2, 
'\xd0\xd9\.. ..\xb0')..." if I add a line manually (just copy line of 
another TVM and change QID, name, etc.., but I guess it's wrong, while that 
line requires uuid or smth else to be correct, and what I can't know).

Is there any way to deny qubes-manager to check that QID or change the list of 
TVMs? 

Thanks...

-- 
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/0b51d205-1a8e-4c38-a25f-f10e400c6ba0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Clone qubes machine - any options other than backup and build again?

2016-12-14 Thread Franz
On Wed, Dec 14, 2016 at 8:19 AM, dumbcyber  wrote:

> Hello, I am running Qubes from a 64Gb USB stick.
>
> I am running R3.2 on my Macbook 11,1, and have built several template VMs,
> for example Windows.
>
> What I want to do now is clone the entire USB stick to another USB
> external SSD drive. In other words I want to be able to stop using the USB
> stick and move to the SSD drive without building Qubes from again scratch
> and then performing backup/restore all my VMs.
>
> Is this even possible? Am i dreaming?
>
>
A couple of times I had success cloning entire hard disks using clonezilla
under linux. It was easy and fast. But I do not know if it runs under MAC.
Also I doubt it will work under Qubes if you boot it directly from the USB
stick you want to clone. But if you have another computer with linux it
should work.
Best
Fran

Thanks in advance.
>
> --
> 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/96c75461-a5b7-4318-973b-03e47d6bbbfd%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAPzH-qCineLGdT8ZHmTbspcwPBeookKeyzo_aLAbWBZg%3DebZag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Installing on macOS Macbook

2016-12-14 Thread dumbcyber
On Wednesday, 7 December 2016 09:31:36 UTC-5, Chibi  wrote:
> I tried to install QubesOS in Virtualbox on my Macbook and get the following 
> error:
> http://imgur.com/a/dx9oM
> I can't fix it somehow. Is there any way to fix it?

I am reading and responding to this thread on a Macbook Pro 11,1 running Qubes 
R3.2.  Andrew and others are right: yes it works, but you need to work hard to 
make it work. I had the keyboard not working issue and in fact i had to build 
my Qubes disk on a Lenovo to get past the install issues the Macbook was giving 
me.

Re Virtualbox, I don't think either VB or Qubes are designing to work in the 
way you are trying. 

-- 
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/618c40bf-4fff-43b2-a0bf-6f250bcc245c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: I recently installed Qubes and I now have several problems

2016-12-14 Thread dumbcyber
On Tuesday, 13 December 2016 21:29:28 UTC-5, explodingbee .  wrote:
> Hi folks,
> 
> I installed qubes several days ago.  I now have several problems and I would 
> appreciate some help:
> 
> 1) How can I open WIndows 7 again?  First, I intended to install Qubes beside 
> Windows 7, which was working fine.  Instead I can only boot to Qubes now.  
> How can I have a dual-boot setup so that I can also go to Windows 7?  (Note: 
> my files from Windows 7 were apparently not damaged and I have recently 
> managed to get apparently all of them off of the computer and onto an 
> external hard drive so they should be safe.)  (I did read this file 
> [https://www.qubes-os.org/doc/multiboot/] but it seems to say that one needs 
> to wipe out everything and reinstall Windows 7 and then reinstall Qubes.  
> Can't I fix the GRUB file somehow so that I can use my existing installations 
> and programs?)  
> 
> 2) In Qubes the computer often gets slow as molasses.  I get error messages 
> saying "Warning: unresponsive script" sometimes.  When I try to open a VM it 
> says that there is not enough memory and that I should close a VM first.  
> When the computer gets like this sometimes I click on things and nothing 
> happens or it takes forever for something to happen; sometimes I can't even 
> close windows because they don't respond.  (I am using an HP Elitebook 8540w 
> laptop.  It has 4 GB of RAM and an i7 CPU.)  Also, when I shut down the 
> computer sometimes it gets stuck and does not shut down all the way.  It 
> freezes with the Qubes splash screen there and the progress bar indicating 
> partial or complete progress.
> 
> 
> 3) Problem relating to program installation:  When I install programs in the 
> Fedora or Debian templates they don't appear in the list of available 
> programs in the templates or in the VMs based on those templates so I don't 
> see how I can create shortcuts for programs in my VMs.
> 
> 
> 4) Problem in getting a video player to work:  I have installed four 
> different video players (Snappy, Budgie, Banshee and Parole) and none of them 
> seem to be able to play videos I have downloaded (with Video Download Helper 
> and Firefox in an App VM).  (I can get the video players to launch not with 
> the proper shortcuts but in another, awkward way, by going to Domain: 
> personal -> personal: Software and then clicking around until I get to the 
> right app which was previously installed and then clicking on "launch.")  
> Also, the default player, apparently called "Videos," doesn't work.  Am I 
> missing something here?  
> 
> 
> 
> This paragraph shows the problems which arise when I try to use each of the 
> above mentioned video players.  You may (or may not) want to skip this 
> paragraph.  (I am including these video player error descriptions partly 
> because they may give a clue as to an overall problem here.)
>  (a) Snappy: The video player shows that a video has loaded but then when 
> I click play it does nothing.  
>  (b) Parole: When I try to play a video I get the following error 
> message: "Error   GStreamer backend error   Could not intialize Xv output."  
> The only button to click on the error message dialogue box says: "Close."  
>  (c) Banshee: This video player doesn't play videos when I click play.  
> It sometimes causes an error message which reads: "Additional multimedia 
> codecs requires.  An application is requesting additional multimedia codecs." 
>  Then there is a button which reads "find in software."  (Other times when I 
> click play after selecting a video the video player just does nothing.)  
>  (d) Budgie: This videos player does nothing when I click play after a 
> video which has been loaded into the program is selected.  
>  (e) Videos:  (Apparently this video player is called "Videos."  It is 
> the default player.)  When I select a video and then select "Play with 
> Videos" an error message comes up.  It says: "H.264 (Constrained Baseline 
> Profile) decoder, MPEG-4 AAC decoder are required to play the file, but are 
> not installed."  Then there is a button which says "Find in software."  When 
> I click that button I get another error message which says "Unfortunately, 
> the H.264 (Constrained Baseline Profile) decoder and MPEG-4 AAC decoder you 
> were searching for could not be found.  Please see this website for more 
> information."
> 
> 
> 5) I can't update Fedora:  I have tried to update Fedora 23 to Fedora 25.  I 
> am able to download the update but then I click "Install" and nothing 
> happens.  I also click "restart and install" just below that and again 
> nothing happens.  What is going on with that?  (I just tried that again and I 
> got the following error message this time:  "Sorry this did not work  Upgrade 
> to Fedora failed.  Details    Detailed errors from the package manager 
> follow:  Error running transaction: installing package 
> filesystem-3.2-37.fc24.x86_64 needs 135168 on the /rw filesystem")

[qubes-users] Clone qubes machine - any options other than backup and build again?

2016-12-14 Thread dumbcyber
Hello, I am running Qubes from a 64Gb USB stick.

I am running R3.2 on my Macbook 11,1, and have built several template VMs, for 
example Windows.

What I want to do now is clone the entire USB stick to another USB external SSD 
drive. In other words I want to be able to stop using the USB stick and move to 
the SSD drive without building Qubes from again scratch and then performing 
backup/restore all my VMs.

Is this even possible? Am i dreaming?

Thanks in advance.

-- 
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/96c75461-a5b7-4318-973b-03e47d6bbbfd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.