On Tuesday, February 20, 2018 at 7:26:16 PM UTC+1, Marek Marczykowski-Górecki wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On Tue, Feb 20, 2018 at 09:07:34AM -0800, Yuraeitha wrote: > > - The GUI copy to VM now works, but the terminal qvm-copy still doesn't > > work. > > qvm-copy command takes only filename, the VM name you give in qrexec > confirmation prompt. > > - -- > 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----- > > iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAlqMaBcACgkQ24/THMrX > 1yxRQgf/YtF1OCeg/iwryngYe+4PI0tv6x9h+ZZISzL1ppVCTEyWa2PJouDZ9GeB > OVZSlGnu/0hmEd4CsXzGsu011PHRYK5dPeQFMq3EmywJQy9gXQh72ifkqZbYscO3 > WuXYHf8NK/OzxlUZHCKrpurjFtOLZpZTXa79UMd1lkscmnpS0PAI72Nqi0xd6mJf > DQ81u0tzh57QQmM3qJJSFBMMac6TR9i0zSvEWVacYVuzdIeFSMEf1v4GqPRG2lsQ > 3xNQvm76JQ/WU0s886qNCl0Q3M7kZ41OlH7gy1PhG9QINBUW1aacnxLXrKP3zNu6 > psvUm9UaEu2cFpLLRF5FV2FBE0xHNA== > =/if3 > -----END PGP SIGNATURE-----
ah I see, that really simplifies the command compared to the old, or maybe it was always like that in VM's and I didn't realize. Either way though, the issue is still there without putting the VM name in the command, but now the "Request refused." is back in the place of the error. It strikes me as a little odd that it changed on its own this time without me doing anything new (I did nothing special except restarting the VM in question, perhaps it was that). It's the same changed feedback (from error to missing permission) if applying the VM name in the command. This is a peculiar oddball error. Multiple of full system restarts, and it just won't go away despite careful maintenance procedures, or so I would like to think anyway. (i.e. I don't just recklessly update with wrong repositories between dom0/templates, plug the power, etc.). This is not a personal issue for me though, not yet at least. I'll wait and see if something new happens, right now I don't think I can add anything new. Now that full 10-12 second long system-wide freeze that happened earlier today after the update, worries me a bit more. But it hasn't happened since then though. It wasn't too long after returning from suspend, and occurred immediately after starting a another VM. I had little spare RAM left at the time (8GB total) and more VM's running than normal, so maybe that's part of the issue, but normally it would just not start if not enough RAM is left and not cause a freeze like that. I don't expect a personal followup on this, I'm only mentioning this one time incident for awareness. At the time of the system-wide freeze, it had only been restarted once after the update. If a second restart could fix something like that, then maybe it's gone now *shrug* -- 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/ca684ebb-c9e6-4d6f-80b8-2a0c2a9904c7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
