Wyng for Noobs

Community Guides
81

@Mirai Thanks for following-up. I re-opened the issue and posted a workaround in fix08.

I’m unsure how introducing a tty/login shell will impact remote access, so I went with a simpler solution which is to prefix the command with sh -c.

82

@tasket thanks for the quick response.

Unfortunately it still fails


Wyng-util-qubes v0.9 beta rel 20251105

Wyng 0.8.1 (fix08) release 20260427


XXXXXXXXX)'.
mkdir -p -m 777 /tmp/wyngrpc/  && tdir=$(mktemp -d /tmp/wyngrpc/tmpXXXXXXXXXXXX)  && echo && echo $tdir && cat >$tdir/dest_helper.py
                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
[0, 127]


StorageError: (5, 'Destination not ready to receive commands.')
83

@Mirai Seems to be an odd artifact of ssh and its shell invocation. But this new workaround I just posted works on my Ubuntu server when its set to use fish. Hopefully it works for you, too.

84

@tasket :frowning: fish is version 4.2 on fedora 33 in both the sending and receiving qube.

Wyng-util-qubes v0.9 beta rel 20251105

Wyng 0.8.1 (fishpass) release 20260430


.1 (fishpass) release 20260430
warning: An error occurred while redirecting file '/tmp/wyngrpc/tmpnojr7lxm'
warning: Path '/tmp/wyngrpc' does not exist
/bin/sh: /tmp/wyngrpc/tmpnojr7lxm: No such file or directory
[0, 127]


StorageError: (5, 'Destination not ready to receive commands.')
85

@Mirai OK, I left out a necessary mkdir before creating the script at that path. Error doesn’t occur if the /tmp/wyngrpc dir already exists.

The fishpass branch has been updated with the necessary changes.

1 Like
86

@tasket thank you no problems now <3

Wyng is fantastic