Solus 4.6 ISO Testing: "Failed to start flatpak-enable-flathub.service - Add flathub flatpak repositories." when no lan connection on boot in live session

sebo505 commented 1 month ago

Please confirm there isn't an existing open bug report

[X] I have searched open bugs for this issue

Summary

So, I don't know if it is worth reporting, but the last thing user sees before starting of Budgie session when booting into live session is an error: Failed to start flatpak-enable-flathub.service - Add flathub flatpak repositories. This only occurs when there is no lan connection during boot. When booting into GNOME live session, this message is not visible, but you see in when powering off at the end of GNOME session.

output of journalctl -b0 --grep flatpak-enable-flathub:

Oct 12 00:02:10 solus systemd[1]: Starting flatpak-enable-flathub.service - Add flathub flatpak repositories...
Oct 12 00:02:10 solus systemd[1]: flatpak-enable-flathub.service: Main process exited, code=exited, status=1/FAILURE
Oct 12 00:02:10 solus systemd[1]: flatpak-enable-flathub.service: Failed with result 'exit-code'.
Oct 12 00:02:10 solus systemd[1]: Failed to start flatpak-enable-flathub.service - Add flathub flatpak repositories.
Oct 12 00:02:10 solus kernel: audit: type=1130 audit(1728691330.422:148): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=flatpak-enable-flathub comm="systemd>

Might make sense that this is failing without internet connection. Maybe this error can be silenced to not confuse users.

Steps to reproduce

boot into Solus 4.6 Budgie live session

Expected result

no error messages during boot

Actual result

error message during boot

Environment

[X] Is system up to date?

Repo

Shannon (stable)

Desktop Environment

Budgie

System details

Hardware-Modell: Hewlett-Packard HP EliteBook 6930p Speicher: 8,0 GiB Prozessor: Intel® Core™2 Duo T9550 × 2 Grafik: AMD RV620 Festplattenkapazität: 250,1 GB

Other comments

No response

sebo505 commented 1 month ago

1000059740

BuzzPCSOS commented 4 weeks ago

I have the same issue on two fully updated Solus Plasma laptops. One updated from Solus 4.5, the other a fresh install from 4.6. Tried running suggested fix sudo flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo but this made no difference. When the laptops are running I have no trouble installing or running Flatpak programs.

joebonrichie commented 4 weeks ago

Hmm we have

Wants=network-online.target
After=network-online.target

in the .service file, so i'm not sure why it's attempting to run before then.

Does the /var/lib/flatpak/.flathub-initialized file exist on your system when the .service fails?

When flatpak 1.16.x is released we can re-work how we vendor enable the flathub repo as we enable it via the /usr/share/flatpak/remotes.d/ path instead of providing a .service file.

BuzzPCSOS commented 4 weeks ago

Does the /var/lib/flatpak/.flathub-initialized file exist on your system when the .service fails?

Could not see that file even with 'show hidden files' enabled. Looking forward to flatpak 1.16.x release. Thank you for your very quick response.

TraceyC77 commented 5 days ago

Adding to the 4.7 milestone as part of the effort to polish the software centers

getsolus / packages