Re: [qubes-users] Moving dom0 screenshots immediately to VMs

[Jean-Philippe Ouellet]

On Fri, Jan 19, 2018 at 3:55 AM,   wrote:
> I've been working on a solution for this, but unfortunately there are too 
> many factors that I'm not familiar with.
>
> My goal is to to able to:
>
> 1) Take a screenshot using the dom0 hotkey
> 2) In the "Screenshot" dialogue, select a script from the "Open with:" option
> 3) A text entry box that prompts me for the destination VM
> 4) The screenshot is sent to the indicated VM
>
> I think this can be accomplished with
>
> .desktop application file
> zenity
> qvm-move-to-vm/qvm-copy-to-vm/qvm-open-in-vm
>
> but I'm lost in the details.
>
> Current problems
>
> - I can't get dom0 to include my .desktop application files as "Open with:" 
> options in the "Screenshot" dialogue
> - I'm not sure what format the screenshot is in initially... will the 
> .desktop application receive a bunch of bits? Or the path to a temporary file?
> - I can figure out how to pipe the screenshot if it's a file, but I don't 
> know how to handle a "bunch of bits" scenario
>
> Has anyone done this already? I'm aware of qvm-screenshot-tool.sh, which 
> looks great, but the code is too complicated for me to review and I just need 
> basic functionality anyway. 
> https://github.com/evadogstar/qvm-screenshot-tool/blob/master/qvm-screenshot-tool.sh

This problem has already been solved, but upstreaming it was stalled
for some policy reasons. See here:
https://github.com/QubesOS/qubes-issues/issues/953

My implementation can be found here:
https://github.com/jpouellet/qubes-screenshot-helper

Regards,
Jean-Philippe

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

Re: [qubes-users] Re: Moving dom0 screenshots immediately to VMs

[Yethal]

W dniu piątek, 19 stycznia 2018 21:16:10 UTC+1 użytkownik Alex Dubois napisał:
> On Friday, 19 January 2018 19:37:43 UTC, Yethal  wrote:
> > W dniu piątek, 19 stycznia 2018 20:00:27 UTC+1 użytkownik Alex Dubois 
> > napisał:
> > > On Friday, 19 January 2018 17:52:41 UTC, Alex Dubois  wrote:
> > > > On Friday, 19 January 2018 12:05:36 UTC, Tom Zander  wrote:
> > > > > On Friday, 19 January 2018 12:48:27 CET wordswithn...@gmail.com wrote:
> > > > > > Qubes already has built-in the capability to screenshot the entire 
> > > > > > desktop
> > > > > > (Printscreen)  or the current window (Ctrl+Printscreen).
> > > > > 
> > > > > Yes, it does.
> > > > > 
> > > > > But this is not something you should use and then send to a VM 
> > > > > becuase that 
> > > > > VM then suddenly gets knowledge about all the other windows on screen 
> > > > > that 
> > > > > may be from another VM.
> > > > 
> > > > Default should prevent, but user should have choice.
> > > > 
> > > > > 
> > > > > Imagine having your Vault VM window open with all your passwords and 
> > > > > then 
> > > > > you auto-upload a screenshot of that into a compromised VM which then 
> > > > > causes 
> > > > > the screenshot to be uploaded to a server.
> > > > > 
> > > > > I'm not aware of any way to avoid this data-leakage using the 
> > > > > screenshot 
> > > > > application in dom0.
> > > > > -- 
> > > > > Tom Zander
> > > > > Blog: https://zander.github.io
> > > > > Vlog: https://vimeo.com/channels/tomscryptochannel
> > > > 
> > > > XFCE (default Qubes Windows manager) provides a screenshot application 
> > > > (Menu/System Tools/Screenshot activated with the PrintScreen Key as 
> > > > well)
> > > > This launch a windows with:
> > > > - Region to capture (radio selection)
> > > >   - Entire screen (selected by default)
> > > >   - Active window
> > > >   - Select a region
> > > > - Delay before capturing
> > > >   - X seconds (default is 1)
> > > > - Capture mouse pointer
> > > >   - Y/N (default Y)
> > > > 
> > > > What I think needs to be done:
> > > > - Change the default for region to capture to "active window"
> > > > - Also
> > > >   - hook into screenshot so that either
> > > > - when OK (or Enter key) is pressed
> > > >   - the Save As dialog is replace by another one where you put the 
> > > > VM name (and it goes into QubesIncoming in that VM, for Dom0 into 
> > > > /home/user/screenshots)
> > > > - Dom0 Confirmation pop-up appear (same as usual copy/move 
> > > > file) with a preview (TBC)?
> > > >OR - the Save As dialog has a kind of "network drive list" which is 
> > > > the list of VMs that are running, and saving there save to 
> > > > QubesIncoming for that VM. You have to prevent the create directory and 
> > > > other stuff probably. Benefit is that it is probably re-usable for any 
> > > > Dom0 apps which use the Save As window.
> > > 
> > > OK for the impatient, this will send a screenshot of the current window 
> > > to a VM (no selection of target VM for the moment):
> > > 
> > > 1- Bind shortcut key:
> > > Click on: Menu/System Tools/Keyboard
> > > Click on: Application Shortcuts tab
> > > Click on Add
> > > Command: xfce4-screenshooter -w -o /usr/local/bin/screenshooter.sh
> > > Bind to Ctrl + Shift + PrintScreen (or whatever you want)
> > > 
> > > 2- Create script that will copy the file to the target VM
> > > in Dom0 terminal
> > > sudo vi /usr/local/screenshooter.sh
> > > 
> > > #!/bin/bash
> > > cat $1  qvm-run --pass-io  "cat > /home/user/`echo $1 | awk -F'/' 
> > > '{print $3}'`"
> > > 
> > > where  is the started VM that will receive the screenshot. You 
> > > can obviously choose a path that user has write access to. You may want 
> > > to clean the file that is save by default in /tmp by adding this line
> > > rm /tmp/`echo $1 | awk -F'/' '{print $3}'`"
> > > 
> > > 3- Make the script executable
> > > sudo chmod a+x /usr/local/bin/screenshooter.sh
> > 
> > there is the qvm-screenshot-tool. Is that not enough?
> 
> Never heard of it. In which package is-it?

https://groups.google.com/forum/#!msg/qubes-users/rb3lQvcXkOY/sEQpsAFSAQAJ;context-place=forum/qubes-users

-- 
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/0379dbda-1cb0-474f-8148-d11f24aff821%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] GPU?

[Demi Obenour]

I think that Qubes needs 3 things to really take off:

1. It Just Works.  Even on new systems with new hardware.  That means an
up-to-date kernel and drivers.  Probably not an LTS.  It also means getting
UEFI to work out of the box — it doesn't for me.  That also means recent
installers that are aware of the quirks of different kinds of firmware.

2. GPU acceleration.  A big use for Qubes IMO is running games in a
sandboxed environment.  But games need hardware-accelerated graphics.  In
fact, recent games often require dedicated graphics cards to get acceptable
performance.  That means GPU virtualization for ALL GPUs.  Not just Intel
integrated graphics.

And it's not just games.  Firefox’s WebRender makes heavy use of the GPU.
So does QT5.  And I suspect Chromium will follow suit.  GPUs are quickly
becoming a requirement, not an option.

I think that the solution is to implement OpenGL on WebGL inside the VMs,
and expose WebGL from GUIVM.  That's what browsers do.

3. Windows support that Just Works.  One should not need to know anything
about Linux or Xen to use Qubes.  Even though they are what Qubes is built
on, they should be implementation details that one need not be familiar
with.

On Jan 18, 2018 5:56 PM, "'Tom Zander' via qubes-users" <
qubes-users@googlegroups.com> wrote:

On Sunday, 14 January 2018 08:12:24 CET r...@tuta.io wrote:
> Is qubes able to use the computing power of the gpu or is the type of gpu
> installed a waste in this issue?

Relevant here is an email I wrote recently;
https://groups.google.com/forum/#!msg/qubes-devel/40ImS390sAw/Z7M0E8RiAQAJ

The context is a GSoC proposal proposal to modernize the painting
pipeline of Qubes.

Today GL using software uses [llvmpipe] to compile and render GL inside of
a Qube, completely in software and then push the 2d image to dom0.
This indeed wastes the GPU.


[llvmpipe]: https://groups.google.com/forum/#!msg/qubes-devel/
40ImS390sAw/Z7M0E8RiAQAJ

--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel


--
You received this message because you are subscribed to a topic in the
Google Groups "qubes-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/qubes-users/l2oqYEWpY-A/unsubscribe.
To unsubscribe from this group and all its topics, 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/1970768.QL1Wn2a4Hl%40mail.
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/CAJEMUN_e%3D6cU-wAczH-ZoRHBtzASzwyrkhfOWfWQv7cDfCDN%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

AW: Re: [qubes-users] Created new fedora-26 dvm, how to delete old dvm

['[799]' via qubes-users]

> I tried to remove the default DVM, but it didn't > work. What do I need to 
> do, to get rid of the
> old (Fedora 25 based) DVM which comes with > the default Qubes 4rc3 
> isntallation ?

After some trial and error I found out what was causing the problem, deleting 
the default fedora-25-dvm and the fedora-25 template.

I had not only to migrate all AppVMs to the new fedora-26 template, I also had 
to edit /var/lib/qubes/qubes.xml and change the entries default_template and 
default_dispvm from fedora-25 to fedora_26.

After that I was able to qvm-remove the fedora-25-dvm and also the fedora-25 
template via sudo dnf remove qubes-template-fedora-25

[799]

-- 
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/_wbkzGY79kVeiPvZCdx5yvLLWLA_Xz4df_VLCSAZOPZs7eGsnulKxvtRWenKCQCLn9eJxAJpR6IfKiJrScjcFdj7JxDxwc4yEu49g8GVOeI%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No network (HELP)

['Tom Zander' via qubes-users]

On Friday, 19 January 2018 16:38:54 CET Marek Marczykowski-Górecki wrote:
> Specifically qmemman was broken in qubes-core-dom0 in 4.0.16 and 4.0.17.

Can confirm it works much better 4.0.18 than it ever did before :)

-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel


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

AW: Re: AW: [qubes-users] Alt-Tab not passed through

['[799]' via qubes-users]

Hello,

[799] wrote:
>> Is there anything I can do, so that Alt+Tab is
>> not (!) working in dom0 but in the AppVM
>> window / in the virtual desktop connection?

mossy-nw answered:
> I'm not sure you want to do this, e.g. if your
> virtual desktop ever ends up in full-screen
> mode, there are security reasons why you
> want alt-tab as a sanity check to be sure
> you're in direct communication with dom0.
> Could you assign a different shortcut
> (SHIFT-CTRL tab?) within the VM?

I haven't thought about the Alt+Tab behaviour as a (security) feature - thank 
you for the interesting view.
I have chosen to come up with a workarround as solution to switch my Apps in my 
virtual desktop window:

1) Download Autohotkey in the virtual desktop

2) Create a my-autohotkey.ahk configuration file with the following entries:

LAlt & w::AltTab
LAlt & q::ShiftAltTab

3) run Autohotkey with the above configuration

I am now able to switch windows back & forward using Alt + Q and Alt + W, which 
is good enough.

[799]

-- 
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/aaGK4T9a58873cage7VERtwbNHqFKUGtknfEIWJUWTKcN0250jE8xx0f0FHdPOraCNRnjyk5lE6g6d8fI4JuObqrk-A3f91kEse50T0-SgE%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Moving dom0 screenshots immediately to VMs

[Alex Dubois]

On Friday, 19 January 2018 19:37:43 UTC, Yethal  wrote:
> W dniu piątek, 19 stycznia 2018 20:00:27 UTC+1 użytkownik Alex Dubois napisał:
> > On Friday, 19 January 2018 17:52:41 UTC, Alex Dubois  wrote:
> > > On Friday, 19 January 2018 12:05:36 UTC, Tom Zander  wrote:
> > > > On Friday, 19 January 2018 12:48:27 CET wordswithn...@gmail.com wrote:
> > > > > Qubes already has built-in the capability to screenshot the entire 
> > > > > desktop
> > > > > (Printscreen)  or the current window (Ctrl+Printscreen).
> > > > 
> > > > Yes, it does.
> > > > 
> > > > But this is not something you should use and then send to a VM becuase 
> > > > that 
> > > > VM then suddenly gets knowledge about all the other windows on screen 
> > > > that 
> > > > may be from another VM.
> > > 
> > > Default should prevent, but user should have choice.
> > > 
> > > > 
> > > > Imagine having your Vault VM window open with all your passwords and 
> > > > then 
> > > > you auto-upload a screenshot of that into a compromised VM which then 
> > > > causes 
> > > > the screenshot to be uploaded to a server.
> > > > 
> > > > I'm not aware of any way to avoid this data-leakage using the 
> > > > screenshot 
> > > > application in dom0.
> > > > -- 
> > > > Tom Zander
> > > > Blog: https://zander.github.io
> > > > Vlog: https://vimeo.com/channels/tomscryptochannel
> > > 
> > > XFCE (default Qubes Windows manager) provides a screenshot application 
> > > (Menu/System Tools/Screenshot activated with the PrintScreen Key as well)
> > > This launch a windows with:
> > > - Region to capture (radio selection)
> > >   - Entire screen (selected by default)
> > >   - Active window
> > >   - Select a region
> > > - Delay before capturing
> > >   - X seconds (default is 1)
> > > - Capture mouse pointer
> > >   - Y/N (default Y)
> > > 
> > > What I think needs to be done:
> > > - Change the default for region to capture to "active window"
> > > - Also
> > >   - hook into screenshot so that either
> > > - when OK (or Enter key) is pressed
> > >   - the Save As dialog is replace by another one where you put the VM 
> > > name (and it goes into QubesIncoming in that VM, for Dom0 into 
> > > /home/user/screenshots)
> > > - Dom0 Confirmation pop-up appear (same as usual copy/move file) 
> > > with a preview (TBC)?
> > >OR - the Save As dialog has a kind of "network drive list" which is 
> > > the list of VMs that are running, and saving there save to QubesIncoming 
> > > for that VM. You have to prevent the create directory and other stuff 
> > > probably. Benefit is that it is probably re-usable for any Dom0 apps 
> > > which use the Save As window.
> > 
> > OK for the impatient, this will send a screenshot of the current window to 
> > a VM (no selection of target VM for the moment):
> > 
> > 1- Bind shortcut key:
> > Click on: Menu/System Tools/Keyboard
> > Click on: Application Shortcuts tab
> > Click on Add
> > Command: xfce4-screenshooter -w -o /usr/local/bin/screenshooter.sh
> > Bind to Ctrl + Shift + PrintScreen (or whatever you want)
> > 
> > 2- Create script that will copy the file to the target VM
> > in Dom0 terminal
> > sudo vi /usr/local/screenshooter.sh
> > 
> > #!/bin/bash
> > cat $1  qvm-run --pass-io  "cat > /home/user/`echo $1 | awk -F'/' 
> > '{print $3}'`"
> > 
> > where  is the started VM that will receive the screenshot. You can 
> > obviously choose a path that user has write access to. You may want to 
> > clean the file that is save by default in /tmp by adding this line
> > rm /tmp/`echo $1 | awk -F'/' '{print $3}'`"
> > 
> > 3- Make the script executable
> > sudo chmod a+x /usr/local/bin/screenshooter.sh
> 
> there is the qvm-screenshot-tool. Is that not enough?

Never heard of it. In which package is-it?

-- 
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/6eee5e16-6440-428a-82ac-919ed3f7405a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Moving dom0 screenshots immediately to VMs

[Yethal]

W dniu piątek, 19 stycznia 2018 20:00:27 UTC+1 użytkownik Alex Dubois napisał:
> On Friday, 19 January 2018 17:52:41 UTC, Alex Dubois  wrote:
> > On Friday, 19 January 2018 12:05:36 UTC, Tom Zander  wrote:
> > > On Friday, 19 January 2018 12:48:27 CET wordswithn...@gmail.com wrote:
> > > > Qubes already has built-in the capability to screenshot the entire 
> > > > desktop
> > > > (Printscreen)  or the current window (Ctrl+Printscreen).
> > > 
> > > Yes, it does.
> > > 
> > > But this is not something you should use and then send to a VM becuase 
> > > that 
> > > VM then suddenly gets knowledge about all the other windows on screen 
> > > that 
> > > may be from another VM.
> > 
> > Default should prevent, but user should have choice.
> > 
> > > 
> > > Imagine having your Vault VM window open with all your passwords and then 
> > > you auto-upload a screenshot of that into a compromised VM which then 
> > > causes 
> > > the screenshot to be uploaded to a server.
> > > 
> > > I'm not aware of any way to avoid this data-leakage using the screenshot 
> > > application in dom0.
> > > -- 
> > > Tom Zander
> > > Blog: https://zander.github.io
> > > Vlog: https://vimeo.com/channels/tomscryptochannel
> > 
> > XFCE (default Qubes Windows manager) provides a screenshot application 
> > (Menu/System Tools/Screenshot activated with the PrintScreen Key as well)
> > This launch a windows with:
> > - Region to capture (radio selection)
> >   - Entire screen (selected by default)
> >   - Active window
> >   - Select a region
> > - Delay before capturing
> >   - X seconds (default is 1)
> > - Capture mouse pointer
> >   - Y/N (default Y)
> > 
> > What I think needs to be done:
> > - Change the default for region to capture to "active window"
> > - Also
> >   - hook into screenshot so that either
> > - when OK (or Enter key) is pressed
> >   - the Save As dialog is replace by another one where you put the VM 
> > name (and it goes into QubesIncoming in that VM, for Dom0 into 
> > /home/user/screenshots)
> > - Dom0 Confirmation pop-up appear (same as usual copy/move file) 
> > with a preview (TBC)?
> >OR - the Save As dialog has a kind of "network drive list" which is the 
> > list of VMs that are running, and saving there save to QubesIncoming for 
> > that VM. You have to prevent the create directory and other stuff probably. 
> > Benefit is that it is probably re-usable for any Dom0 apps which use the 
> > Save As window.
> 
> OK for the impatient, this will send a screenshot of the current window to a 
> VM (no selection of target VM for the moment):
> 
> 1- Bind shortcut key:
> Click on: Menu/System Tools/Keyboard
> Click on: Application Shortcuts tab
> Click on Add
> Command: xfce4-screenshooter -w -o /usr/local/bin/screenshooter.sh
> Bind to Ctrl + Shift + PrintScreen (or whatever you want)
> 
> 2- Create script that will copy the file to the target VM
> in Dom0 terminal
> sudo vi /usr/local/screenshooter.sh
> 
> #!/bin/bash
> cat $1  qvm-run --pass-io  "cat > /home/user/`echo $1 | awk -F'/' 
> '{print $3}'`"
> 
> where  is the started VM that will receive the screenshot. You can 
> obviously choose a path that user has write access to. You may want to clean 
> the file that is save by default in /tmp by adding this line
> rm /tmp/`echo $1 | awk -F'/' '{print $3}'`"
> 
> 3- Make the script executable
> sudo chmod a+x /usr/local/bin/screenshooter.sh

there is the qvm-screenshot-tool. Is that not enough?

-- 
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/99833c61-b238-4f7b-9469-5a5078cd8fb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Moving dom0 screenshots immediately to VMs

[Alex Dubois]

On Friday, 19 January 2018 17:52:41 UTC, Alex Dubois  wrote:
> On Friday, 19 January 2018 12:05:36 UTC, Tom Zander  wrote:
> > On Friday, 19 January 2018 12:48:27 CET wordswithn...@gmail.com wrote:
> > > Qubes already has built-in the capability to screenshot the entire desktop
> > > (Printscreen)  or the current window (Ctrl+Printscreen).
> > 
> > Yes, it does.
> > 
> > But this is not something you should use and then send to a VM becuase that 
> > VM then suddenly gets knowledge about all the other windows on screen that 
> > may be from another VM.
> 
> Default should prevent, but user should have choice.
> 
> > 
> > Imagine having your Vault VM window open with all your passwords and then 
> > you auto-upload a screenshot of that into a compromised VM which then 
> > causes 
> > the screenshot to be uploaded to a server.
> > 
> > I'm not aware of any way to avoid this data-leakage using the screenshot 
> > application in dom0.
> > -- 
> > Tom Zander
> > Blog: https://zander.github.io
> > Vlog: https://vimeo.com/channels/tomscryptochannel
> 
> XFCE (default Qubes Windows manager) provides a screenshot application 
> (Menu/System Tools/Screenshot activated with the PrintScreen Key as well)
> This launch a windows with:
> - Region to capture (radio selection)
>   - Entire screen (selected by default)
>   - Active window
>   - Select a region
> - Delay before capturing
>   - X seconds (default is 1)
> - Capture mouse pointer
>   - Y/N (default Y)
> 
> What I think needs to be done:
> - Change the default for region to capture to "active window"
> - Also
>   - hook into screenshot so that either
> - when OK (or Enter key) is pressed
>   - the Save As dialog is replace by another one where you put the VM 
> name (and it goes into QubesIncoming in that VM, for Dom0 into 
> /home/user/screenshots)
> - Dom0 Confirmation pop-up appear (same as usual copy/move file) with 
> a preview (TBC)?
>OR - the Save As dialog has a kind of "network drive list" which is the 
> list of VMs that are running, and saving there save to QubesIncoming for that 
> VM. You have to prevent the create directory and other stuff probably. 
> Benefit is that it is probably re-usable for any Dom0 apps which use the Save 
> As window.

OK for the impatient, this will send a screenshot of the current window to a VM 
(no selection of target VM for the moment):

1- Bind shortcut key:
Click on: Menu/System Tools/Keyboard
Click on: Application Shortcuts tab
Click on Add
Command: xfce4-screenshooter -w -o /usr/local/bin/screenshooter.sh
Bind to Ctrl + Shift + PrintScreen (or whatever you want)

2- Create script that will copy the file to the target VM
in Dom0 terminal
sudo vi /usr/local/screenshooter.sh

#!/bin/bash
cat $1  qvm-run --pass-io  "cat > /home/user/`echo $1 | awk -F'/' 
'{print $3}'`"

where  is the started VM that will receive the screenshot. You can 
obviously choose a path that user has write access to. You may want to clean 
the file that is save by default in /tmp by adding this line
rm /tmp/`echo $1 | awk -F'/' '{print $3}'`"

3- Make the script executable
sudo chmod a+x /usr/local/bin/screenshooter.sh


-- 
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/476d0c3b-7cff-4245-802f-a77815f15cbd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Moving dom0 screenshots immediately to VMs

[Alex Dubois]

On Friday, 19 January 2018 12:05:36 UTC, Tom Zander  wrote:
> On Friday, 19 January 2018 12:48:27 CET wordswithn...@gmail.com wrote:
> > Qubes already has built-in the capability to screenshot the entire desktop
> > (Printscreen)  or the current window (Ctrl+Printscreen).
> 
> Yes, it does.
> 
> But this is not something you should use and then send to a VM becuase that 
> VM then suddenly gets knowledge about all the other windows on screen that 
> may be from another VM.

Default should prevent, but user should have choice.

> 
> Imagine having your Vault VM window open with all your passwords and then 
> you auto-upload a screenshot of that into a compromised VM which then causes 
> the screenshot to be uploaded to a server.
> 
> I'm not aware of any way to avoid this data-leakage using the screenshot 
> application in dom0.
> -- 
> Tom Zander
> Blog: https://zander.github.io
> Vlog: https://vimeo.com/channels/tomscryptochannel

XFCE (default Qubes Windows manager) provides a screenshot application 
(Menu/System Tools/Screenshot activated with the PrintScreen Key as well)
This launch a windows with:
- Region to capture (radio selection)
  - Entire screen (selected by default)
  - Active window
  - Select a region
- Delay before capturing
  - X seconds (default is 1)
- Capture mouse pointer
  - Y/N (default Y)

What I think needs to be done:
- Change the default for region to capture to "active window"
- Also
  - hook into screenshot so that either
- when OK (or Enter key) is pressed
  - the Save As dialog is replace by another one where you put the VM name 
(and it goes into QubesIncoming in that VM, for Dom0 into 
/home/user/screenshots)
- Dom0 Confirmation pop-up appear (same as usual copy/move file) with a 
preview (TBC)?
   OR - the Save As dialog has a kind of "network drive list" which is the list 
of VMs that are running, and saving there save to QubesIncoming for that VM. 
You have to prevent the create directory and other stuff probably. Benefit is 
that it is probably re-usable for any Dom0 apps which use the Save As window.

-- 
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/debe5877-ca0e-4d90-a4d4-f637f82c395d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No network (HELP)

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, Jan 19, 2018 at 06:53:55AM -0800, aaq via qubes-users wrote:
> Den fredag den 19. januar 2018 kl. 15.48.08 UTC+1 skrev a...@it-minds.dk:
> > Which setting exactly disables dynamic memory allocation, because I can't 
> > seem to figure it out. If I set maxmem to 0, will it disable it?
> > 
> > The GUI is broken. It comes up with an error if I try to start it, no 
> > matter how I try to start it. It complains about a bug, but that isn't 
> > really important right now.

It's a bit obscure, see qvm-service. "meminfo-writer" service is
responsible for memory balancing. But it should be already in "off"
state for sys-net.

> I set the maxmem to 1 (cannot set it to 0) and initial mem to 800.

This is maximum memory size in MB. Setting it to 1 doesn't sounds like a
good idea, but... for VMs with PCI devices it is ignored and "memory"
property is used instead (because of Xen limitation, namely
populate-on-demand being incompatible with PCI-passthrough).

400MB should be enough for sys-net, in some cases even lower number
should suffice.

> sys-net starts now.
> 
> I am updating my system now, hopefully this will disappear on its own.

There were a bunch of fixes yesterday (late) evening, including one for
qmemman, and GUI stuff. Make sure you have:

qubes-core-dom0 4.0.18
qubes-core-admin-client 4.0.13
qubes-manager 4.0.11
qubes-dbus 1.0.4

Specifically qmemman was broken in qubes-core-dom0 in 4.0.16 and 4.0.17.

- -- 
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-

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlpiEQ4ACgkQ24/THMrX
1ywPywf/Tl8SsGq0NQ5zQC2uiMIWrkEipbRj0hMkeeqIIQQpgzn101bDlLgoud+w
JzbBUfRqA1tO2KUWhOG0XRcuUiRQszOhR95p13hMsoEm4Nnxu0chFietPe7aOQZx
sMQqr3BjHkJxtYh780F6reke9Ec0fvkxANnKC4J53YocEQSIGtqX7GSUuxdEYM0K
T02DpNJJseocFO6s2G8aTqQpTiorl+mWVvdL8PjzlJ7XOduLVtHna3sZL5LrbP18
3SsTWZQ5bhRfk/3Elt0t26UYe+Aeyeyxric/HCbe7nmWqxrNqqnZkjpNXkFZi+9F
oDHvHUm5N834oxlidhG2gGwr0u2bCw==
=w6SK
-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/20180119153854.GE12450%40mail-itl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No network (HELP)

['awokd' via qubes-users]

On Fri, January 19, 2018 2:53 pm, aaq via qubes-users wrote:

>
> I set the maxmem to 1 (cannot set it to 0) and initial mem to 800.

> sys-net starts now.

Good! In theory it should work too if you leave maxmem at 4000.

> I am updating my system now, hopefully this will disappear on its own.
>
>
> Any deeper insight as to the 'why'?
> I am kind of confused..

Zander?


-- 
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/1cda744977ce902ad165299c0f13b189.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: -> Backing up files: 78%... ERROR: Failed to perform backup: error in addproc

[cooloutac]

On Friday, January 19, 2018 at 6:41:51 AM UTC-5, Holger Levsen wrote:
> hi,
> 
> I was just doing a backup (using the qvm-backup cli tool on 3.2) which then
> suddenly crashed with this line:
> 
> -> Backing up files: 78%... ERROR: Failed to perform backup: error in addproc
> 
> I couldn't investigate further yet, but I suppose it failed to backup a
> specific VM - which is bad - and this then crashed qvm-backup completly
> instead of just continueing with the next VM - which is worse.
> 
> Is it worth filing an issue with this little information? (or is this a
> know bug? I'm on low bandwidth atm, so I don't wanna check...)
> 
> 
> -- 
> cheers,
>   Holger

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

-- 
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/55ed54f0-812b-4d5f-8d1b-cce217d64d13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No network (HELP)

[aaq via qubes-users]

Den fredag den 19. januar 2018 kl. 15.48.08 UTC+1 skrev a...@it-minds.dk:
> Den fredag den 19. januar 2018 kl. 15.44.35 UTC+1 skrev awokd:
> > On Fri, January 19, 2018 2:33 pm, aaq via qubes-users wrote:
> > > Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd:
> > >
> > >> On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote:
> > >>
> > >>> Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev
> > >>> a...@it-minds.dk:
> > >>>
> > >>>
> >  Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander:
> > 
> > 
> > > On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users
> > > wrote:
> > >
> > >
> > >>
> > > Try turning off memory-management and give the sys-net an initial
> > >  amount of something like 800MB.
> > >>
> > >> Go into sys-net's VM Settings, Advanced tab. Uncheck "include in memory
> > >>  balancing" and increase initial memory to 800.
> > >>
> > >> See if there are any other errors in dom0 with "sudo journalctl -b"
> > >> when you start the VM.
> > >
> > > Can I disable it through qvm-prefs? Because my qubes manager (the GUI is
> > > back again now) is broken..
> > 
> > Yes, type qvm-prefs sys-net to see a list of settings. qubes-vm-settings
> > sys-net should also give you the gui.
> 
> Sorry.
> 
> Which setting exactly disables dynamic memory allocation, because I can't 
> seem to figure it out. If I set maxmem to 0, will it disable it?
> 
> The GUI is broken. It comes up with an error if I try to start it, no matter 
> how I try to start it. It complains about a bug, but that isn't really 
> important right now.

Okay!

I set the maxmem to 1 (cannot set it to 0) and initial mem to 800.

sys-net starts now.

I am updating my system now, hopefully this will disappear on its own.

Any deeper insight as to the 'why'?
I am kind of confused..

Without your guys' suggestions I would have been lost..

Thanks a bunch!

-- 
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/59912f3c-476f-494d-9bc8-5a77a8f379f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No network (HELP)

[aaq via qubes-users]

Den fredag den 19. januar 2018 kl. 15.44.35 UTC+1 skrev awokd:
> On Fri, January 19, 2018 2:33 pm, aaq via qubes-users wrote:
> > Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd:
> >
> >> On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote:
> >>
> >>> Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev
> >>> a...@it-minds.dk:
> >>>
> >>>
>  Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander:
> 
> 
> > On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users
> > wrote:
> >
> >
> >>
> > Try turning off memory-management and give the sys-net an initial
> >  amount of something like 800MB.
> >>
> >> Go into sys-net's VM Settings, Advanced tab. Uncheck "include in memory
> >>  balancing" and increase initial memory to 800.
> >>
> >> See if there are any other errors in dom0 with "sudo journalctl -b"
> >> when you start the VM.
> >
> > Can I disable it through qvm-prefs? Because my qubes manager (the GUI is
> > back again now) is broken..
> 
> Yes, type qvm-prefs sys-net to see a list of settings. qubes-vm-settings
> sys-net should also give you the gui.

Sorry.

Which setting exactly disables dynamic memory allocation, because I can't seem 
to figure it out. If I set maxmem to 0, will it disable it?

The GUI is broken. It comes up with an error if I try to start it, no matter 
how I try to start it. It complains about a bug, but that isn't really 
important right 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/71be7916-6e82-4265-8844-ca25d5c1106b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No network (HELP)

['awokd' via qubes-users]

On Fri, January 19, 2018 2:33 pm, aaq via qubes-users wrote:
> Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd:
>
>> On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote:
>>
>>> Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev
>>> a...@it-minds.dk:
>>>
>>>
 Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander:


> On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users
> wrote:
>
>
>>
> Try turning off memory-management and give the sys-net an initial
>  amount of something like 800MB.
>>
>> Go into sys-net's VM Settings, Advanced tab. Uncheck "include in memory
>>  balancing" and increase initial memory to 800.
>>
>> See if there are any other errors in dom0 with "sudo journalctl -b"
>> when you start the VM.
>
> Can I disable it through qvm-prefs? Because my qubes manager (the GUI is
> back again now) is broken..

Yes, type qvm-prefs sys-net to see a list of settings. qubes-vm-settings
sys-net should also give you the gui.

-- 
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/e4a8eb7ce62c2569bc5cdf9338b1b4c3.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No network (HELP)

[aaq via qubes-users]

Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd:
> On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote:
> > Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev a...@it-minds.dk:
> >
> >> Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander:
> >>
> >>> On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users wrote:
> >>>
> 
> >>> Try turning off memory-management and give the sys-net an initial
> >>> amount of something like 800MB.
> 
> Go into sys-net's VM Settings, Advanced tab. Uncheck "include in memory
> balancing" and increase initial memory to 800.
> 
> See if there are any other errors in dom0 with "sudo journalctl -b" when
> you start the VM.

Can I disable it through qvm-prefs? Because my qubes manager (the GUI is back 
again now) is broken..

-- 
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/3b0badb7-cb9e-4e59-b7d7-4f9fa897e5da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No network (HELP)

['awokd' via qubes-users]

On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote:
> Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev a...@it-minds.dk:
>
>> Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander:
>>
>>> On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users wrote:
>>>

>>> Try turning off memory-management and give the sys-net an initial
>>> amount of something like 800MB.

Go into sys-net's VM Settings, Advanced tab. Uncheck "include in memory
balancing" and increase initial memory to 800.

See if there are any other errors in dom0 with "sudo journalctl -b" when
you start the VM.

-- 
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/53335dad85efbad2d215fb489dd7d4e1.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No network (HELP)

[aaq via qubes-users]

Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev a...@it-minds.dk:
> Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander:
> > On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users wrote:
> > > What can I do 
> > 
> > Could this have something to do with the broken qmemman?
> > 
> > Try turning off memory-management and give the sys-net an initial amount of 
> > something like 800MB.
> > 
> > also check if xentop has anything weird in the first line with memory usage.
> > 
> > Good luck!
> 
> 
> Can you give me specific instructions to where I can do these things :S
> 
> Sorry!
> 
> I know there is something in the grub config for dom0 memory management, is 
> it that?
> 
> Where do I find xentop?
> 
> I can see in /var/log/xen/console/hypervisor.log that it complains about 
> "initial memory low", but I dunno if that's new..
> 
> I tried awokds recommendations:
> switching template to debian yields same message about memory being too low.
> virt_mode already is hvm.
> 
> Thanks for your time and help.

Sorry, I didn't release xentop was a tool like top/htop...
My laptop has 8gb of RAM, Qubes has reserved 4gb to dom0 through grub config.

Xentop says that approx. 3.8gb is free.

So I really don't think the issues lies there.

-- 
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/898e2d6f-cba3-4142-bbae-152a13ff2bde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No network (HELP)

[aaq via qubes-users]

Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander:
> On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users wrote:
> > What can I do 
> 
> Could this have something to do with the broken qmemman?
> 
> Try turning off memory-management and give the sys-net an initial amount of 
> something like 800MB.
> 
> also check if xentop has anything weird in the first line with memory usage.
> 
> Good luck!


Can you give me specific instructions to where I can do these things :S

Sorry!

I know there is something in the grub config for dom0 memory management, is it 
that?

Where do I find xentop?

I can see in /var/log/xen/console/hypervisor.log that it complains about 
"initial memory low", but I dunno if that's new..

I tried awokds recommendations:
switching template to debian yields same message about memory being too low.
virt_mode already is hvm.

Thanks for your time and help.

-- 
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/1fd6f7cc-3941-458d-aa71-ef7f275932e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Please help with 8th Generation Intel i5

[Krišjānis Gross]

@ Foppe de Haan
>Most likely due to lacking hardware support (in the kernel) for the CL 
>>graphics chip (even though it's little more than a rebrand of KL's). Try 
>>installing a more recent (ideally 4.14-based) kernel. Iow, it's sort of 
>>related, because the issues you

Please suggest how to install Qubes with different Kernel version. I have not 
idea how that can be done :)



>Can you get sys-usb started? If so, use qvm-copy-to-vm in dom0 to copy the 
>logs to a VM, then to the flash drive. Otherwise, you could boot with a 
>live image of some type, mount the hard drive and copy out the logs. 
This was a /tmp log of installation process. Not sure that dom0 as such is 
available during the installation. 


>Both seem unhappy with your video card. What's in that laptop? Please post 
>Debian's boot log (redact hardware serial numbers & MAC addresses), and 
>Qubes' xl dmesg log if you can get it. 

The setup is not a laptop. It is a desktop see HW details below. Will try to 
get the Debian's boot log.
> Here is the hardware details:
>MB: ASRock Z370 Pro4 https://www.asrock.com/MB/Intel/Z370%20Pro4/index.asp
>CPU: Intel® Core™ i5-8600K 
> https://ark.intel.com/products/126685/Intel-Core-i5-8600K-Processor-9M-Cache-up-to-4_30-GHz
>RAM: 16 GB DDR4

-- 
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/0b0601c0-460e-4fad-b80f-5a9b989ba86c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No network (HELP)

['awokd' via qubes-users]

On Fri, January 19, 2018 12:43 pm, awokd wrote:
> On Fri, January 19, 2018 10:48 am, aaq via qubes-users wrote:
>
>> Qubes 4 RC3
>>
>>
>>
>> So, I updated using current testing yesterday, and there was an update
>> to qubes core dom0 and other changes..
>>
>> Network worked fine before I shutdown my machine, but now when I try to
>>  start sys-net I get an error saying "Not enough memory to start domain
>>  'sys-net'"
>>
>
> Try switching sys-net's template to debian-9?

Check out this issue too:
https://github.com/QubesOS/qubes-issues/issues/3474 . See if your
virt_mode is pvh and try to change it to hvm.

-- 
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/51586233497c4fb84def3da33843a673.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No network (HELP)

['Tom Zander' via qubes-users]

On Friday, 19 January 2018 11:48:56 CET aaq via qubes-users wrote:
> What can I do 

Could this have something to do with the broken qmemman?

Try turning off memory-management and give the sys-net an initial amount of 
something like 800MB.

also check if xentop has anything weird in the first line with memory usage.

Good luck!

-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel


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

Re: [qubes-users] HOWTO install boot-loader for Q4.0 RC3 separately on USB?

['awokd' via qubes-users]

On Tue, January 16, 2018 7:54 pm, edalva...@riseup.net wrote:
> I've tried to install Q4.0 RC3 two times on my system with the
> bootloader on a separate USB. However, two times after shutdown, the system
> refuses to start (I get past the FDE-prompt, then it hangs). I've
> reinstalled two times now, but its not encouraging.
>
> Am I doing anything wrong in my setup? During install, the "only" thing
> I do "ekstra" apart from following defaults, is to select the ekstra
> USB-device as bootloader. I haven't done anything fancy with manual
> partitioning so far, just point-and-click during install. It seems like
> this setup installs part of the actual system into the USB and then
> continues onto the SSD / main drive of the machine when it runs out of
> space.
>
> Is this an bug connected to 4.0 or is it a general problem?
>
>
> Any suggestions? Anybody got it running effortless who has anything to
> share?

Does Qubes boot properly if you install it all to your hard drive? Am
wondering if the hang is related to the separate boot-loader. I think 4.0
mostly uses the Fedora 25 installer, so you might also want to see if
there are related bugs.

-- 
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/892fddf53a965feb4f79106d4a275bf9.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] No network (HELP)

['awokd' via qubes-users]

On Fri, January 19, 2018 10:48 am, aaq via qubes-users wrote:
> Qubes 4 RC3
>
>
> So, I updated using current testing yesterday, and there was an update to
> qubes core dom0 and other changes..
>
> Network worked fine before I shutdown my machine, but now when I try to
> start sys-net I get an error saying "Not enough memory to start domain
> 'sys-net'"

Try switching sys-net's template to debian-9?

-- 
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/d54e0db7800169aa66ca10c1042966d3.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Please help with 8th Generation Intel i5

['awokd' via qubes-users]

On Fri, January 19, 2018 11:32 am, Krišjānis Gross wrote:
> On Thursday, 18 January 2018 20:56:10 UTC, donoban  wrote:

>>
>> (EE) VESA(0): V_BIOS address 0xaa7a0 out of range

>>> A side question- how can I copy the logs in /tmp to a flash drive or
>>> something in order to post those here?

Can you get sys-usb started? If so, use qvm-copy-to-vm in dom0 to copy the
logs to a VM, then to the flash drive. Otherwise, you could boot with a
live image of some type, mount the hard drive and copy out the logs.

> Thank You for the suggestion! Will check that out.
> I tried to install Debian 9 on this hardware and all went fine. Only thing
> that I noticed when installation was finished was that there was a
> notification that system is running a " software emulated graphics" and
> therefore CPU usage might be considerably higher. Not sure whether that
> is relevant though.

Both seem unhappy with your video card. What's in that laptop? Please post
Debian's boot log (redact hardware serial numbers & MAC addresses), and
Qubes' xl dmesg log if you can get it.

-- 
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/b519c85a88c014b796bfd0fea7a4eb50.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Please help with 8th Generation Intel i5

[Foppe de Haan]

On Friday, January 19, 2018 at 12:32:32 PM UTC+1, Krišjānis Gross wrote:
> On Thursday, 18 January 2018 20:56:10 UTC, donoban  wrote:
> > On 01/18/2018 11:15 AM, Krišjānis Gross wrote:> I did navigate to /tmp
> > and looked at some logs. Unfortunately I do not know what to look for
> > there. Took some screen shots (attached). Does that ring any bells?
> > 
> > I think the problem is:
> > 
> > (EE) VESA(0): V_BIOS address 0xaa7a0 out of range
> > 
> > I've searched a little but I didn't find anything useful. I hope someone
> > could help you on this.
> > 
> > > 
> > > A side question- how can I copy the logs in /tmp to a flash drive or 
> > > something in order to post those here? 
> > > 
> > > Which Linux distribution should I try to run in order to do a reasonable 
> > > comparison?
> > > 
> > 
> > Ideally same as dom0, fedora-24?? I would try to guess what kernel
> > version starts to work fine with it and compare with built-in the qubes iso.
> 
> Thank You for the suggestion! Will check that out. 
> I tried to install Debian 9 on this hardware and all went fine. Only thing 
> that I noticed when installation was finished was that there was a 
> notification that system is running a " software emulated graphics" and 
> therefore CPU usage might be considerably higher. Not sure whether that is 
> relevant though.

Most likely due to lacking hardware support (in the kernel) for the CL graphics 
chip (even though it's little more than a rebrand of KL's). Try installing a 
more recent (ideally 4.14-based) kernel. Iow, it's sort of related, because the 
issues you ran into while installing qubes were most likely also related to 
that.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9cf4df9f-8b0c-449f-b672-31e9b3268d80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Moving dom0 screenshots immediately to VMs

['Tom Zander' via qubes-users]

On Friday, 19 January 2018 12:48:27 CET wordswithn...@gmail.com wrote:
> Qubes already has built-in the capability to screenshot the entire desktop
> (Printscreen)  or the current window (Ctrl+Printscreen).

Yes, it does.

But this is not something you should use and then send to a VM becuase that 
VM then suddenly gets knowledge about all the other windows on screen that 
may be from another VM.

Imagine having your Vault VM window open with all your passwords and then 
you auto-upload a screenshot of that into a compromised VM which then causes 
the screenshot to be uploaded to a server.

I'm not aware of any way to avoid this data-leakage using the screenshot 
application in dom0.
-- 
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel


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

[qubes-users] Re: Moving dom0 screenshots immediately to VMs

[wordswithnemo]

On Friday, January 19, 2018 at 6:48:28 AM UTC-5, wordsw...@gmail.com wrote:
> On Friday, January 19, 2018 at 6:32:33 AM UTC-5, Alex Dubois wrote:
> > On Friday, 19 January 2018 08:55:27 UTC, wordsw...@gmail.com  wrote:
> > > I've been working on a solution for this, but unfortunately there are too 
> > > many factors that I'm not familiar with.
> > > 
> > > My goal is to to able to:
> > > 
> > > 1) Take a screenshot using the dom0 hotkey
> > > 2) In the "Screenshot" dialogue, select a script from the "Open with:" 
> > > option
> > > 3) A text entry box that prompts me for the destination VM
> > > 4) The screenshot is sent to the indicated VM
> > > 
> > > I think this can be accomplished with
> > > 
> > > .desktop application file
> > > zenity
> > > qvm-move-to-vm/qvm-copy-to-vm/qvm-open-in-vm
> > > 
> > > but I'm lost in the details.
> > > 
> > > Current problems
> > > 
> > > - I can't get dom0 to include my .desktop application files as "Open 
> > > with:" options in the "Screenshot" dialogue
> > > - I'm not sure what format the screenshot is in initially... will the 
> > > .desktop application receive a bunch of bits? Or the path to a temporary 
> > > file?
> > > - I can figure out how to pipe the screenshot if it's a file, but I don't 
> > > know how to handle a "bunch of bits" scenario
> > > 
> > > Has anyone done this already? I'm aware of qvm-screenshot-tool.sh, which 
> > > looks great, but the code is too complicated for me to review and I just 
> > > need basic functionality anyway. 
> > > https://github.com/evadogstar/qvm-screenshot-tool/blob/master/qvm-screenshot-tool.sh
> > 
> > This could be useful feature. Happy to help for the dev part...
> > 
> > What do you think about the default behavior being to:
> > - screen-shot only a VM window? Is it available?
> > - screen-shot an area that you lasso?
> > 
> > I'm suggesting these because the Qubes default should always be the safest 
> > that can be implemented...
> 
> Qubes already has built-in the capability to screenshot the entire desktop 
> (Printscreen)  or the current window (Ctrl+Printscreen).
> 
> Lasso would be nice I suppose, but might open up some way to exploit.

Just so I'm clearer - I'm just talking about a simple solution, not building 
any new application. We could use a .desktop file similar to this

[Desktop Entry]
Encoding=UTF-8
Name=BrowserVM
Exec=qvm-open-in-vm APPVMNAME %u
Terminal=false
X-MultipleArgs=false
Type=Application
Categories=Network;WebBrowser;
MimeType=x-scheme-handler/unknown

as documented in 
https://www.qubes-os.org/doc/tips-and-tricks/#opening-links-in-your-preferred-appvm

I've gotten this done so far

[Desktop Entry]
Encoding=UTF-8
Name=Open Screenshot in VM
Exec=zenity --entry --text="Enter destination domain name:" | qvm-open-in-vm %u
Terminal=false
X-MultipleArgs=false
Type=Application
Categories=Network;WebBrowser;
MimeType=x-scheme-handler/unknown

-- 
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/ef593abc-d71e-4cb5-8940-c12b06a6262d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Moving dom0 screenshots immediately to VMs

[wordswithnemo]

On Friday, January 19, 2018 at 6:32:33 AM UTC-5, Alex Dubois wrote:
> On Friday, 19 January 2018 08:55:27 UTC, wordsw...@gmail.com  wrote:
> > I've been working on a solution for this, but unfortunately there are too 
> > many factors that I'm not familiar with.
> > 
> > My goal is to to able to:
> > 
> > 1) Take a screenshot using the dom0 hotkey
> > 2) In the "Screenshot" dialogue, select a script from the "Open with:" 
> > option
> > 3) A text entry box that prompts me for the destination VM
> > 4) The screenshot is sent to the indicated VM
> > 
> > I think this can be accomplished with
> > 
> > .desktop application file
> > zenity
> > qvm-move-to-vm/qvm-copy-to-vm/qvm-open-in-vm
> > 
> > but I'm lost in the details.
> > 
> > Current problems
> > 
> > - I can't get dom0 to include my .desktop application files as "Open with:" 
> > options in the "Screenshot" dialogue
> > - I'm not sure what format the screenshot is in initially... will the 
> > .desktop application receive a bunch of bits? Or the path to a temporary 
> > file?
> > - I can figure out how to pipe the screenshot if it's a file, but I don't 
> > know how to handle a "bunch of bits" scenario
> > 
> > Has anyone done this already? I'm aware of qvm-screenshot-tool.sh, which 
> > looks great, but the code is too complicated for me to review and I just 
> > need basic functionality anyway. 
> > https://github.com/evadogstar/qvm-screenshot-tool/blob/master/qvm-screenshot-tool.sh
> 
> This could be useful feature. Happy to help for the dev part...
> 
> What do you think about the default behavior being to:
> - screen-shot only a VM window? Is it available?
> - screen-shot an area that you lasso?
> 
> I'm suggesting these because the Qubes default should always be the safest 
> that can be implemented...

Qubes already has built-in the capability to screenshot the entire desktop 
(Printscreen)  or the current window (Ctrl+Printscreen).

Lasso would be nice I suppose, but might open up some way to exploit.

-- 
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/b1ab8852-4873-4ea5-92a6-a98c6d8e282e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Moving dom0 screenshots immediately to VMs

[Krišjānis Gross]

On Friday, 19 January 2018 11:32:33 UTC, Alex Dubois  wrote:
> On Friday, 19 January 2018 08:55:27 UTC, wordsw...@gmail.com  wrote:
> > I've been working on a solution for this, but unfortunately there are too 
> > many factors that I'm not familiar with.
> > 
> > My goal is to to able to:
> > 
> > 1) Take a screenshot using the dom0 hotkey
> > 2) In the "Screenshot" dialogue, select a script from the "Open with:" 
> > option
> > 3) A text entry box that prompts me for the destination VM
> > 4) The screenshot is sent to the indicated VM
> > 
> > I think this can be accomplished with
> > 
> > .desktop application file
> > zenity
> > qvm-move-to-vm/qvm-copy-to-vm/qvm-open-in-vm
> > 
> > but I'm lost in the details.
> > 
> > Current problems
> > 
> > - I can't get dom0 to include my .desktop application files as "Open with:" 
> > options in the "Screenshot" dialogue
> > - I'm not sure what format the screenshot is in initially... will the 
> > .desktop application receive a bunch of bits? Or the path to a temporary 
> > file?
> > - I can figure out how to pipe the screenshot if it's a file, but I don't 
> > know how to handle a "bunch of bits" scenario
> > 
> > Has anyone done this already? I'm aware of qvm-screenshot-tool.sh, which 
> > looks great, but the code is too complicated for me to review and I just 
> > need basic functionality anyway. 
> > https://github.com/evadogstar/qvm-screenshot-tool/blob/master/qvm-screenshot-tool.sh
> 
> This could be useful feature. Happy to help for the dev part...
> 
> What do you think about the default behavior being to:
> - screen-shot only a VM window? Is it available?
> - screen-shot an area that you lasso?
> 
> I'm suggesting these because the Qubes default should always be the safest 
> that can be implemented...

Could be a very useful feature! Current means of taking a screen shot are very 
very clumsy :)

-- 
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/4faa1a1e-e3ff-41a7-a5fd-3bd8354f0f03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] -> Backing up files: 78%... ERROR: Failed to perform backup: error in addproc

[Holger Levsen]

hi,

I was just doing a backup (using the qvm-backup cli tool on 3.2) which then
suddenly crashed with this line:

-> Backing up files: 78%... ERROR: Failed to perform backup: error in addproc

I couldn't investigate further yet, but I suppose it failed to backup a
specific VM - which is bad - and this then crashed qvm-backup completly
instead of just continueing with the next VM - which is worse.

Is it worth filing an issue with this little information? (or is this a
know bug? I'm on low bandwidth atm, so I don't wanna check...)


-- 
cheers,
Holger

-- 
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/20180119114142.tsb3npdqwevse22f%40layer-acht.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

[qubes-users] Re: Moving dom0 screenshots immediately to VMs

[Alex Dubois]

On Friday, 19 January 2018 08:55:27 UTC, wordsw...@gmail.com  wrote:
> I've been working on a solution for this, but unfortunately there are too 
> many factors that I'm not familiar with.
> 
> My goal is to to able to:
> 
> 1) Take a screenshot using the dom0 hotkey
> 2) In the "Screenshot" dialogue, select a script from the "Open with:" option
> 3) A text entry box that prompts me for the destination VM
> 4) The screenshot is sent to the indicated VM
> 
> I think this can be accomplished with
> 
> .desktop application file
> zenity
> qvm-move-to-vm/qvm-copy-to-vm/qvm-open-in-vm
> 
> but I'm lost in the details.
> 
> Current problems
> 
> - I can't get dom0 to include my .desktop application files as "Open with:" 
> options in the "Screenshot" dialogue
> - I'm not sure what format the screenshot is in initially... will the 
> .desktop application receive a bunch of bits? Or the path to a temporary file?
> - I can figure out how to pipe the screenshot if it's a file, but I don't 
> know how to handle a "bunch of bits" scenario
> 
> Has anyone done this already? I'm aware of qvm-screenshot-tool.sh, which 
> looks great, but the code is too complicated for me to review and I just need 
> basic functionality anyway. 
> https://github.com/evadogstar/qvm-screenshot-tool/blob/master/qvm-screenshot-tool.sh

This could be useful feature. Happy to help for the dev part...

What do you think about the default behavior being to:
- screen-shot only a VM window? Is it available?
- screen-shot an area that you lasso?

I'm suggesting these because the Qubes default should always be the safest that 
can be implemented...

-- 
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/356b8415-4788-4b7e-bc7d-6a552706fb47%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Please help with 8th Generation Intel i5

[Krišjānis Gross]

On Thursday, 18 January 2018 20:56:10 UTC, donoban  wrote:
> On 01/18/2018 11:15 AM, Krišjānis Gross wrote:> I did navigate to /tmp
> and looked at some logs. Unfortunately I do not know what to look for
> there. Took some screen shots (attached). Does that ring any bells?
> 
> I think the problem is:
> 
> (EE) VESA(0): V_BIOS address 0xaa7a0 out of range
> 
> I've searched a little but I didn't find anything useful. I hope someone
> could help you on this.
> 
> > 
> > A side question- how can I copy the logs in /tmp to a flash drive or 
> > something in order to post those here? 
> > 
> > Which Linux distribution should I try to run in order to do a reasonable 
> > comparison?
> > 
> 
> Ideally same as dom0, fedora-24?? I would try to guess what kernel
> version starts to work fine with it and compare with built-in the qubes iso.

Thank You for the suggestion! Will check that out. 
I tried to install Debian 9 on this hardware and all went fine. Only thing that 
I noticed when installation was finished was that there was a notification that 
system is running a " software emulated graphics" and therefore CPU usage might 
be considerably higher. Not sure whether that is relevant though.

-- 
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/dcfd1e6e-a845-4ecf-ac87-d9b2e3329ce1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: sys-usb / template install yubikey tools ?

[Alex Dubois]

On Friday, 19 January 2018 05:57:16 UTC, ThierryIT  wrote:
> Not familiar with this ... Will need procediure to follow.
> 
> 
> Le mercredi 17 janvier 2018 23:03:31 UTC+2, Alex Dubois a écrit :
> > On Wednesday, 17 January 2018 15:15:45 UTC, ThierryIT  wrote:
> > > No, I am still under R3.2
> > > 
> > > Le mercredi 17 janvier 2018 16:54:58 UTC+2, awokd a écrit :
> > > > On Wed, January 17, 2018 2:09 pm, ThierryIT wrote:
> > > > > "https://github.com/adubois/qubes-app-linux-yubikey;
> > > > >
> > > > >
> > > > > Le mercredi 17 janvier 2018 16:05:52 UTC+2, awokd a écrit :
> > > > >
> > > > >> On Wed, January 17, 2018 1:09 pm, ThierryIT wrote:
> > > > >>
> > > > >>> Nobody ?
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> Le mercredi 17 janvier 2018 09:23:34 UTC+2, ThierryIT a écrit :
> > > > >>>
> > > > >>>
> > > >  Hi,
> > > > 
> > > > 
> > > > 
> > > >  I am going to install a new sys-usb.
> > > >  I have before to install all what I need to the template 
> > > >  (fedora-26)
> > > >   first. When following your procedure:
> > > > 
> > > > 
> > > >  ykpers has been installed but: I cannot do the same for
> > > >  qubes-yubikey-vm and qubes-yubikey-dom0 :
> > > > 
> > > >  no match for argument
> > > > 
> > > >  ideas ?
> > > > >>
> > > > >> Not quite sure what you are trying to do here. What procedure? What
> > > > >> command are you entering?
> > > > 
> > > > Are you trying this on Qubes 4.0? Those Yubikey packages might not be in
> > > > the Qubes repo yet.
> > 
> > Hi,
> > 
> > I have not maintained this for some time. So long that I can't remember if 
> > the packages had been created/tested, I don't think they have.
> > 
> > Best is you follow the steps to build it on a new temporary VM, don't be 
> > afraid it should not be too hard:
> > - Execute the yum command in "Build dependancies"
> > - Also install pam-devel
> > - Follow the steps in preparing the build and build
> > - Deploy the code in Dom0 and the USB VM.
> > 
> > I am about to upgrade to Qubes 4.0 rc4 (when released) so won't probably be 
> > able to help until this is done.
> > 
> > Any help from someone who is used to packaging under Fedora would be nice.
> > 
> > Alex

Sure, I'll update the doc and post here. However as I said don't want to touch 
my Qubes set-up before my upgrade to 4.0 rc4. So might be in 2-3weeks

-- 
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/3db55a51-80e2-4c00-94ba-5d3938bc3e95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] No network (HELP)

[aaq via qubes-users]

Qubes 4 RC3

So, I updated using current testing yesterday, and there was an update to qubes 
core dom0 and other changes..

Network worked fine before I shutdown my machine, but now when I try to start 
sys-net I get an error saying "Not enough memory to start domain 'sys-net'"

I have tried rebooting, and I have tried upscaling and downscaling the initial 
memory to sys-net with qvm-prefs sys-net memory XX

I can start my templateVM's with no issue (eg fedora-26 which is my template 
for sys-net/sys-firewall, and I have tried starting my debian 9 template).

What can I do :S

Needless to say it is pretty fatal for me that I have no network.

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/34fa87a3-eedc-4c6a-982e-16c61257e769%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] split gpg failing after moving appvm from debian 8 to debian 9

[cubit]

Hello qubes-users

I am migrating all my AppVM from Debian 8 template to Debian 9 template  but I 
am running into little problem with split GPG.

Split GPG has been working on my computer okay with Debian 8 and two appVM;   
"work" which has thunderbird and enigmail and "vault" which has my gpg keys.

The issue seems to be if I set the vault to Debian 9,  my work appVM complains 
that it can not find my private key.  Even though if I run "qubes-gpg-client 
-K" on the work appVM it shows my keys.  Looking at an encrypted email when 
"vault" appVM is not running will force it to be started.   The problem exists 
if even I set work appVM to d8 or d9. Work VM with Debian9  and vault VM 
with debian 8 works okay.

I have gone over https://www.qubes-os.org/doc/split-gpg to make sure everything 
is set up correctly after template change and at each step it is.

Can anyone know how to fix this?

Cubit


-- 
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/L3CjLGJ--3-0%40tutanota.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Moving dom0 screenshots immediately to VMs

[wordswithnemo]

I've been working on a solution for this, but unfortunately there are too many 
factors that I'm not familiar with.

My goal is to to able to:

1) Take a screenshot using the dom0 hotkey
2) In the "Screenshot" dialogue, select a script from the "Open with:" option
3) A text entry box that prompts me for the destination VM
4) The screenshot is sent to the indicated VM

I think this can be accomplished with

.desktop application file
zenity
qvm-move-to-vm/qvm-copy-to-vm/qvm-open-in-vm

but I'm lost in the details.

Current problems

- I can't get dom0 to include my .desktop application files as "Open with:" 
options in the "Screenshot" dialogue
- I'm not sure what format the screenshot is in initially... will the .desktop 
application receive a bunch of bits? Or the path to a temporary file?
- I can figure out how to pipe the screenshot if it's a file, but I don't know 
how to handle a "bunch of bits" scenario

Has anyone done this already? I'm aware of qvm-screenshot-tool.sh, which looks 
great, but the code is too complicated for me to review and I just need basic 
functionality anyway. 
https://github.com/evadogstar/qvm-screenshot-tool/blob/master/qvm-screenshot-tool.sh

-- 
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/977360d2-8b7f-49b3-b1cb-772a52385089%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.