By "not working" I mean that the call to qrexec-client-vm gives me a "Request refused".
This includes calls to qvm-copy as well, since it uses the qubes.Filecopy RPC call.
Is this a known problem?
Regards,
Elias
I can't say if anything else in the Nautilus instance worked after that, as I closed the window after that.
Not the kind of error message I was expecting, but it does look like it can't find the files. Since it was $ that was removed in the update today, which with my poor understanding of code, seems to be location related?
Perhaps it's not a coincidence that qvm-copy can't find the location, a typo in the code perhaps?
However, I will try again in the morning and report back.
> On another bright side or bonus, Qubes
> even seem more smooth now. It's like old
> creeky wheels has gotten some oil and
> it's running more smooth. It can
> definitely be felt, at least on my
> system. For example one noticeable
> difference is how fast VM's shutdown is
> after use.
>
> Can you reproduce this fix Elias?
I did try to update and reboot today, but
the problem remained.
I also noted that "open in dispvm" doesn't
work, but I presume that's a consequence
of qvm-copy not working.
It is funny that qvm-copy-to-vm works. I
wonder what the difference is between
these.
> This is really weird indeed... there somehow seems to be a time or random
> factor involved? I believe there were a few before us too, who also had
> problems for a while even after a restart, but it was resolved eventually on
> its own? (At least that's the impression I got from reading those posts). Now
> the same happened to me, it just went away on its own. Then the question is,
> what is triggering this "delay"?
>
> Could it be some system cache of sorts? also did you install current-testing?
> That's the one I used today. I also sometimes have to do 'clean all' or
> restart sys-net and sys-firewall, for the updater to work properly, which
> either can't find the updates or return PGP check errors. Sometimes I need to
> do both, but typically the VM restart is just needed when PGP errors come up
> during downloads. if I don't do that once in a while, especially if the
> system has been running for a while, then I've frequently run into these
> issues the last 14 days or so. It may be a long shot, but you can try these
> things out too. For example I use qubes-dom0-update --action='clean all' and
> then clean all in the respective template too.
I figured it out.
The problem was indeed that the template had not been updated to testing. This was caused by the repositories file being reverted back to its original (non-testing) state. I believe this was caused by me executing the wrong Salt state when I was experimenting with that previously.
Thanks a lot for the help, both you and Marek.
Guess I'll draw the long straw, and just get rid of RC-3 and install RC-4 without confirmation whether it'd any good to do so. I'll probably never find out the reason, but it's starting to make me a bit uneasy whether it could have been due to Qubes RC-3 or not.