Closed 8bitbuddhist closed 6 months ago
Hey @8bitbuddhist,
Are you tracking main
or a release?
Hey @8bitbuddhist,
Are you tracking
main
or a release?
I'm using v0.2.0
I just tried booting a build without onActivation
and the service started up just fine. And I have daily updates configured anyway, so it's not like this is a major issue for me. Thanks for your work on this!
I'm also seeing this issue.
I did some more testing, and I get the bellow when I have nothing in services.flatpak.update...
set:
[FAILED] Failed to start flatpak-managed-install.service.
See `systemctl status flatpak-managed-install.service` for details.
but when I have anything set in services.flatpak.update...
then I also get:
[FAILED] Failed to start Home Manager environment for reedclanton.
See `systemctl status home-manager-reedclanton.service` for details.
I was able to replicate on a nixos 23.11 vm. Working on a fix.
Hey @8bitbuddhist @ReedClanton. I think the issue was an incorrect dependency
on systemd unit boot order. I required the flatpak-managed-install
to start after network.target
was
reached, but that alone does not guarantee that connectivity has been established.
There a tentative fix in the linked PR (#37). Tagged as WIP since I'd like to do a bit more testing.
@gmodena Stupid question, how would I test this in my setup? What URL would I change inputs.nix-flatpak.url
to in my flake.nix?
@gmodena Stupid question, how would I test this in my setup? What URL would I change
inputs.nix-flatpak.url
to in my flake.nix?
nvm, figured it out. I used inputs.nix-flatpak.url = "hithub:gnodena/nix-flatpak/fix-boot-activation";
@gmodena & @8bitbuddhist No more failures during boot! Seems like it fixed it. Also, pretty sure that getting ride of those failures decrease my boot time!
thanks for testing the patch @ReedClanton !
When starting up my laptop, I get an error that
flatpak-managed-install.service
fails to start. When I pull up the service logs, it says it couldn't reach dl.flathub.org. My first guess is that it was trying to start before the network was active (I'm on a laptop with Wi-Fi), but the same thing happened in a virtual machine. Restarting the service using systemctl fixes the issue.My config:
systemd logs: