Failed to execute child process "pragha" (No such file or directory)

popped up on screen not exactly sure why,  maybe something to do with kb volume buttons?  dunno.

raah...@gmail.com:

> Failed to execute child process "pragha" (No such file or directory)
>
> popped up on screen not exactly sure why,  maybe something to do with kb volume buttons?  dunno.
>

Not a volume button; you must have hit the "back" or "rewind" button.
You can bind these kinds of keys to whatever you want in Dom0, or you
can remove their Dom0 bindings so that these events will be handled by
whichever AppVM is in focus (just like any other keystroke).

Actually, Dom0 should probably not have these kinds of keys bound by
default...

Andrew

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
When done properly it may be really useful. For example play/pause
button bound to appropriate "qvm-run music-vm some-command". Then it works
regardless of currently focused application.

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

iQEcBAEBCAAGBQJXATfaAAoJENuP0xzK19csna4H/0GFmnV3gc8YNlkzriVh+IUt
OVaJIB5kUV8VBoyxrLCxWldyEfgaH7xQ805A5JylQnTUOo4I0gBcY3Za8ZgtCWwd
u9/TQeMlrjHr5Cp5d0KKHT+50xIdTsZblTvaGQA1gENQFNVcIytvYcry7pTKZP+C
kZ3BIPMhZKbhsaVSEucTY0fiVEOFuMCf/ukHkxl58D6UJy+5A2co9FgbZM40NPV9
Y1clusMmheglvXPCVL9sEBaw/Nk5fRcl28mMZOgVkTfG+FjKUE767qxjDKqvgJkg
kHQyT5O9++JQk2f+oAK8zZ3duWoifY92yxw9Sp+1A7hEeoDfCLACLSAqMfvENvg=
=46H/
-----END PGP SIGNATURE-----

Marek Marczykowski-Górecki:

> On Sun, Apr 03, 2016 at 03:13:22PM +0000, Andrew wrote:
>> raah...@gmail.com:
>>> Failed to execute child process "pragha" (No such file or
>>> directory)
>>>
>>> popped up on screen not exactly sure why,  maybe something to
>>> do with kb volume buttons?  dunno.
>>>
>
>> Not a volume button; you must have hit the "back" or "rewind"
>> button. You can bind these kinds of keys to whatever you want in
>> Dom0, or you can remove their Dom0 bindings so that these events
>> will be handled by whichever AppVM is in focus (just like any
>> other keystroke).
>
>> Actually, Dom0 should probably not have these kinds of keys bound
>> by default...
>
> When done properly it may be really useful. For example play/pause
> button bound to appropriate "qvm-run music-vm some-command". Then
> it works regardless of currently focused application.
>
>

Definitely true, but I feel like Qubes is difficult enough to set up
as it is, and that requires some user-specific setup.

By not binding the keys in Dom0, they go from "not working at all, and
giving an ugly error message" to "working, so long as the relevant
domain is in focus".  I think the latter is also predictable to
someone (getting) used to the Qubes model.

Of course, anyone who wants to go through the setup can still bind
those keys in Dom0; it's just a small extra step.

Andrew

I've decided to stick with kde,   but tks for the info, good to know.

just realized this tks!