Description of problem: When starting newsbeuter the following message is displayed XDG: configuration directory '/home/sassmann/.config/newsbeuter' not accessible, using '/home/sassmann/.newsbeuter' instead. Fine, I move my /home/sassmann/.newsbeuter directory to /home/sassmann/.config/newsbeuter Now starting newsbeuter again I see XDG: data directory '/home/sassmann/.local/share/newsbeuter' not accessible, using '/home/sassmann/.newsbeuter' instead. Starting newsbeuter 2.9... Loading configuration...done. Opening cache...done. Loading URLs from /home/sassmann/.newsbeuter/urls...done. Error: no URLs configured. Please fill the file /home/sassmann/.newsbeuter/urls with RSS feed URLs or import an OPML file. Which means after reading /home/sassmann/.config/newsbeuter/config the xdg data dir is probed and if it doesn't exist everything falls back to .newsbeuter. But the urls haven't been read yet and are now being looked for in .newsbeuter instead of .config/newsbeuter. Silly workaround: mkdir /home/sassmann/.local/share/newsbeuter Suggestion on how to fix this: If .config/newsbeuter exists but .local/share/newsbeuter does not, then try to create .local/share/newsbeuter. or to phrase this more generic if xdg config dir exists but xdg data dir does not, try to create xdg data dir. Version-Release number of selected component (if applicable): newsbeuter-2.9-2.fc24.x86_64
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.