Red Hat Bugzilla – Bug 1466226
newsbeuter falls back to $HOME/.newsbeuter if xdg data dir doesn't exist
Last modified: 2017-11-17 00:55:43 EST
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 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):
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'
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.