I’ve been playing with both 4r2 and 3.2 in the last week and my main problem was a lack of information. A VM fails to attach to the qrexec daemon? All the user sees is that his app fails to start.
As such, a GUI that can show queued and past events would be nice to have. But me and Python don’t get along. At all. So after reading the github sourcetree and finding no way to hook into the system, I’m asking here. Is there a way to talk to the qubes system without using python? As an example, it would be nice if there was some socket-based API that can be used to query the qubes-daemon. Thanks for reading! -- Tom Zander Blog: https://zander.github.io Vlog: https://vimeo.com/channels/tomscryptochannel -- 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/1846625.2K8LXnFUeA%40strawberry. For more options, visit https://groups.google.com/d/optout.
