On Wednesday, November 8, 2017 at 8:12:14 AM UTC, Frédéric Pierret (fepitre) wrote: > > Thank you for your feedback > > Le mercredi 8 novembre 2017 06:20:12 UTC+1, Yuraeitha a écrit : >> >> Does that mean the qvm-run issues run on freshly started AppVMs and >> Templates, isn't related to the original topic issue with qvm-open-in-vm? >> >> All the VM domains start just fine, and even if shutting down and >> starting again, it rarely fixes the issue, some never even work despite >> restart. It's also really, really weird and puzzling that this only applies >> to some Templates and AppVMs. >> >> My apologies if this isn't related to the original topic, at which case >> my post was off-topic. But if there is any chance its related information, >> then I'll post it here. >> > No problem, for me it is related. I also experience "random" behavior and > such problems you described in your previous post. So there is something to > dig in. > >> >> I've just tried running Qubes 4 on my other hardware system, which seems >> not to have this issue. Perhaps it's hardware specific or software >> condition specific. Either way, just attempting to add information to the >> original post, not to hijack it. >> >> >> On Tuesday, November 7, 2017 at 7:27:48 PM UTC, Marek >> Marczykowski-Górecki wrote: >>> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA256 >>> >>> On Tue, Nov 07, 2017 at 04:33:27AM -0800, Frédéric Pierret (fepitre) >>> wrote: >>> > Hi, >>> > I'm experiencing something strange in Qubes 4.0rc2: when I try to >>> > qvm-open-in-vm several images in the same vm it seems to does not >>> work. For >>> > e.g. from work appvm: >>> > >>> > qvm-open-in-vm '$default' appel.jpg (then I choose e.g. personal), It >>> opens >>> > great and I keep the image open in personal, and then I do the same >>> with >>> > appel2.jpg but the image does not appear and does not exist in >>> /tmp/work-* >>> > >>> > Doing this with two differents targets VM or with e.g. PDF or TXT >>> works >>> > great. Can someone test it please (just before trying to eventually >>> deeply >>> > debug...)? >>> >>> I can confirm this behavior. (I guess) it is because the opening the >>> second file in fact open it in the same viewer/editor instance. And that >>> command exit immediately after sending a message to main (first) >>> instance. So qvm-open-in-vm (in fact, /usr/lib/qubes/vm-file-editor) >>> thinks you already closed the file and remove it from the target VM. >>> This is very similar to more general issue we have with gnome-terminal >>> in DispVM - the command you use to open app/file do not wait until you >>> close app/file. >>> >>> - -- >>> 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 >>> >>> iQEcBAEBCAAGBQJaAgksAAoJENuP0xzK19csi/AH+gOZ1aUZVuLv6cKAjNBSckdK >>> o7hwZBhdwwyeeBJ3NYdl0R1VDXWOSK+RMdh5jPXnXVdJHjJb2CXJ2nwrofWwP8C0 >>> Kv4O3scER6Iq7iFOns/0C9pvXAVs9FI0T9rZ98kGy9isIugDDIJJR2ie7hvKBhg1 >>> BeSXLFIBNPv3TERRxOqiZpOkWh7+YmDZWsIpTX1nldsEZDzWxvkbKbOK+fg7RhY1 >>> AkBJFjNTbNPIhwIqXVBIBBB7Ygu4J0TNP6k7f9eWYqCJrGgc4ykAglK/UhUf4Cwx >>> 4lyhRWveNt4td5bGBOCslnIQNQYdztViIN/ubxAcQMcIk4kaXHaqR19zc1MxNEE= >>> =M00S >>> -----END PGP SIGNATURE----- >>> >> > It's good to know I'm not alone with this issue, although at the same time I wish it was only my machine so no one else had to experience this stressing issue. I feel like its frankly the most annoying Qubes 4 bug to date, nothing else I experienced is as annoying as this one >.< It's like putting a big yummy carrot in front of you on a stick, it's allmoooost working, but nope, not getting it. Frustrating when that close after hours of trying to fix it, and it fails at the last step, especially, and indeed, given its random nature, haha
No disrespect meant to the developers, I'm aware this is a big job, a lot of fundamental code was changed between 3.2 and 4, and that Qubes 4 is still in testing phase as well. Obviously bugs like these are natural to happen, and I'm definitely not complaining (if anything, Qubes 4 is an amazing job done), it's just a natural to expect, but frustrating kind of bug to encounter. -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/d9510db9-e2f8-445c-9911-d9086467c497%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
