> Try doing that on existing process (strace -fp `pidof qrexec-agent`)
> instead of new one. This one looks like waiting for qrexec-daemon to
> connect to it (there is no automatic reconnect if you restart
> qrexec-agent).
Perfect! It seems like that put me on the right track and a few new leads have
emerged.
So stracing qrexec-agent led me to qrexec-fork-server:
> connect(8, {sa_family=AF_FILE,
> path="/var/run/qubes/qrexec-server.user.sock"}, 40) = -1 ENOENT (No such file
> or directory)
Running `/usr/bin/qrexec-fork-server` as `user` fails with "bind() failed". I
`chmod g+w /var/run/qubes`'ed and it let me run the process.
ls -la /var/run/qubes
...
srwxrwxr-x 1 user user 0 Oct 25 10:14 qrexec-server.user.sock
--
`qvm-run lfsgo 'touch /tmp/hi'` strace output from dom0:
https://pastebin.com/5FrnAhUg
`journalctl -u qubes-qrexec-agent` output: https://pastebin.com/nKxLxidx
--
Feels like I'm doing some really hacky, non-systematic approaches to get things
going, so I know I must've missed a few things.
1) how does qrexec-fork-server typically init'ed?
2) qvm-run still doesn't run the command, but attempting it does push this to
"user"'s terminal: "executed QUBESRPC qubes.WaitForSession dom0 pid 679" and
the dom0 side process stalls indefinitely.
control-C killing the process pushes "pid 679 exited with -1" on domU's side.
Looking at qubes.WaitForSession, I'm now suspicious that this is now an X
issue--maybe surrounding the X session owner--is this a possibility?
--
Other details
# ls -la /tmp
prw-rw-r-- 1 user user 0 Oct 25 10:37 qrexec-rpc-stderr-return.679
prw-rw-r-- 1 user user 0 Oct 25 10:37 qrexec-rpc-stderr.679
-rw-rw-r-- 1 user user 4 Oct 25 10:37 qubes-session-waiter
None of the rpc files have any content in them.
Any guidance would be greatly appreciated!
Will
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-devel+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-devel@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/9a363bee-e8e4-4d93-99b7-57ebaa660dd0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
