Hello,

Qubes OS in version 2 and 3 comes with a modified Knsapshoot (screenshot tool).
The Qubes OS Ksnapshoot tool has an additional "Send to/Other Application" option.
After pressing a window with all VMs and enabled applications pops up.
Than it is possible to select one of the applications.

I have tried it with Eye Of Gnome, Firefox and GIMP. But it does not work.
The tool executes for example following command:

qvm-run -q --tray -a personal -- 'qubes-desktop-run /usr/share/applications/gimp.desktop'

Has everybody used Ksnapshot "Sent to" successfully?

Best regards
  J. Eppler

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Jul 07, 2015 at 06:32:03AM -0700, Jeremias E. wrote:
> Hello,
>
> Qubes OS in version 2 and 3 comes with a modified Knsapshoot (screenshot
> tool).
>
> The Qubes OS Ksnapshoot tool has an additional "Send to/Other Application"
> option.

It isn't modified, it is a standard feature.

> After pressing a window with all VMs and enabled applications pops up.
> Than it is possible to select one of the applications.
>
> I have tried it with Eye Of Gnome, Firefox and GIMP. But it does not work.
> The tool executes for example following command:
>
> qvm-run -q --tray -a personal -- 'qubes-desktop-run
> /usr/share/applications/gimp.desktop'

An application running in VM have no access to dom0 filesystem, so no
able to read just created screenshot. I think the proper solution would
be to write a tool, which will send an image to selected VM and open it
there. Then ensure that this tool is the only listed in ksnapshot menu
(instead of all those VM entries).

This feature request is already registered here:
https://github.com/QubesOS/qubes-issues/issues/953

But we had no time to implement it. Anybody willing to help?

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

iQEcBAEBAgAGBQJVm9jbAAoJENuP0xzK19csgJIH/j1VSkeQvsUS/MhAK8P2j34t
E3j+uuYaz+9QRKlwK0GnzEnU2f5LuMm17cjQYUSCxT832G9qHp4UcT4Lm8TEh5LJ
5ehXxs0B8WLR4CnQHRlzmX9N4IvzQn0q1xYular8WSbUfX4RpKS5IcQZ+yHG+KLv
TwHrTZ1rU8Aw2a7d8xKf6feZB9HDxf5F7x1Xez6h+oQ+aXldyKxzGXkbuHPu4PJ0
WenUg2q34peOdEBL05A38EuNAlgH/dLt8fiopu0vQLEuCamVfMPKlHMbBot6IoCG
TDoxfkXmuqtWwqp2SgvFpiGxr/rrSAYXpAKh4PuLF0H+8S7I10VInvngbhmQcYk=
=F58y
-----END PGP SIGNATURE-----

Though its not a proper integration that is suggested above, its easy to
write a script that saves bundles of snapshots that are stacked on your
screen, and then pushes them into an appvm.

Something like this...


===
#!/bin/bash

dest=$1
mypid=$(pidof ksnapshot |tac -s " ")

for p in $mypid; do
   qdbus org.kde.ksnapshot-$p /KSnapshot org.kde.ksnapshot.slotSave
   qdbus org.kde.ksnapshot-$p /KSnapshot org.kde.ksnapshot.exit
done

if [ "$dest" > "" ]; then
   tar --remove-files -cvf - snapshot*.jpeg |qvm-run --pass-io $dest \
   'tar -xf -'
fi

===

You could also add a timed outer loop so it would periodically save any
additional snapshots you make.