Apparently creating a post for help is like replacing something you've lost,
only to find it immediately after replacing it.
Here's the solution to this problem:
Apparently Emacs will trick you into thinking you've changed the
epa-gpg-program variable, but it won't actually honor that change
On Sunday, January 28, 2018 at 6:10:36 PM UTC, [799] wrote:
> Hello Rumsey,
>
> >> I can now send email using emacs/mu4e
> >> and Qubes split gpg
>
> I am also interested in this setup. Can you give me some more information
> what needs to be done to start from a plain installation?
>
On Monday, August 13, 2018 at 6:28:22 PM UTC, awokd wrote:
> Do not reboot. Backup everything immediately. It is bad if your thin pool
> is running low, and may have caused the issue. Once that's done, it's
> probably safest to reinstall...
Too late not to reboot. No lost information though, so
Have had Qubes 4 running smoothly until just now.
Upon startup Qube Manager no longer loads, and when I try to start it from the
menu I get an error:
"QubesDaemonCommunicationError: Failed to connect to qubesd service: [Errno 2]
No such file or directory at line 9 of file
I've been using Qubes for about 1 year now, and I wanted to try using a minimal
template on my Dell XPS 13 laptop for the sake of conserving space.
I've installed the packages recommended at
https://www.qubes-os.org/doc/templates/fedora-minimal/ for sys-net and
sys-firewall and I also had to
On Friday, January 11, 2019 at 6:48:06 PM UTC, 799 wrote:
> I was running into the same issues and have already open a question here.
> Strangely it will work if you use the FAT fedora-29 template out of the box
> ... so it seems we are missing some packages/settings.
Thanks for the reply. I
On Friday, January 11, 2019 at 7:49:36 PM UTC, Ivan Mitev wrote:
> Not sure it'll help but here's a git below with a list of the rpms
> installed in the templateVM of my sys-{net,firewall} vms so you can
> compare and check if you're missing something; the templateVM is a
> minimal fedora install
Thanks to Ivan, I figured it out (with a bit of luck).
After comparing packages in his working template to my own, I first tried to
install:
dbus-glib
ipcalc
iproute
iproute-tc
iputils
That fixed it as far as I can tell. I now have a working sys-net and
sys-firewall with the fedora-29-minimal
