Created attachment 1841237 [details] Screenshot of the message in GNOME Software Description of problem: When I open GNOME Software, the popup "Enable Third Party Software Repositories" is shown. When I click on enable, enter my password and click on Authenticate the message disappears. However, the next time I log into GNOME and open GNOME Software, the message is shown again and I have to repeat to procedure. Somehow, the preference isn't saved. System: Fedora Linux 35.20211104.0 *Silverblue* GNOME Software 41.1 When I run the command "fedora-third-party query" I get: Third-party repositories are disabled (no selection has been made). When I run the command "pkexec fedora-third-party enable" I get: Traceback (most recent call last): File "/usr/bin/fedora-third-party", line 33, in <module> sys.exit(load_entry_point('fedora-third-party==0.8', 'console_scripts', 'fedora-third-party')()) File "/usr/lib/python3.10/site-packages/click/core.py", line 1137, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3.10/site-packages/click/core.py", line 1062, in main rv = self.invoke(ctx) File "/usr/lib/python3.10/site-packages/click/core.py", line 1668, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/lib/python3.10/site-packages/click/core.py", line 1404, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3.10/site-packages/click/core.py", line 763, in invoke return __callback(*args, **kwargs) File "/usr/lib/python3.10/site-packages/click/decorators.py", line 84, in new_func return ctx.invoke(f, obj, *args, **kwargs) File "/usr/lib/python3.10/site-packages/click/core.py", line 763, in invoke return __callback(*args, **kwargs) File "/usr/lib/python3.10/site-packages/fedora_third_party/cli.py", line 38, in enable cfg.enable() File "/usr/lib/python3.10/site-packages/fedora_third_party/config.py", line 66, in enable self._write_state() File "/usr/lib/python3.10/site-packages/fedora_third_party/config.py", line 44, in _write_state with open(self.state_path, 'w') as f: FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/fedora-third-party/state' When I look in the directory "/var/lib/" I don't see a sub-folder with the name "fedora-third-party" (!?). Let me know if you need more information!
Strange this directory should have been created by the tmpfiles services on boot. Is there a line: === d /var/lib/fedora-third-party 0755 root root - - === in /usr/lib/tmpfiles.d/rpm-ostree-1-autovar.conf? Are there any errors in your system logs about fedora-third-party or tmpfiles? Thanks!
Created attachment 1841435 [details] Result of the command 'journalctl | grep fedora-third-party'
Hello Owen, I looked in the file '/usr/lib/tmpfiles.d/rpm-ostree-1-autovar.conf' and can confirm that the line 'd /var/lib/fedora-third-party 0755 root root - -' does exist. I also ran the command 'journalctl | grep fedora-third-party > fedora-third-party.log.txt' and attached the resulting file to this issue report. Reading the content of the file I have the impression that it's a SELinux issue? Lines like 'Oct 27 17:45:32 fedora systemd-tmpfiles[766]: Failed to set SELinux security context system_u:object_r:fedoratp_var_lib_t:s0 for /var/lib/fedora-third-party: Invalid argument' are probably the most interesting? Let me know if there is something else I could test!
Was the output helpful?
I am also seeing this issue pretty much exactly as described here after upgrade to Silverblue 35. pkexec fedora-third-party enable gives: [Errno 2] No such file or directory: '/var/lib/fedora-third-party/state' And the directory /var/lib/fedora-third-party does not exist. Cannot seen any errors in /usr/lib/tmpfiles.d/rpm-ostree-1-autovar.conf but the directory is in rpm-ostree-1-autovar.conf $ cat /usr/lib/tmpfiles.d/rpm-ostree-1-autovar.conf | grep third d /var/lib/fedora-third-party 0755 root root - -
A few weeks ago I did a fresh install of Fedora Silverblue 35 on my work laptop and I didn't encounter the issue so I think it has something to do with the update process of Fedora Silverblue 34 to 35.
I have two machines, both upgraded from 34 to 35. One is effected and one is not.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.