After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 520103 - Gnome-schedule doesn't match FreeDesktop directories specs
Gnome-schedule doesn't match FreeDesktop directories specs
Status: RESOLVED OBSOLETE
Product: gnome-schedule
Classification: Other
Component: general
2.1.1
Other All
: Normal normal
: ---
Assigned To: GNOME Schedule Maintainers
GNOME Schedule Maintainers
: 616170 (view as bug list)
Depends on:
Blocks: 523057
 
 
Reported: 2008-03-03 14:20 UTC by antistress
Modified: 2021-05-25 11:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description antistress 2008-03-03 14:20:29 UTC
Please describe the problem:
I've tried the latest release of gnome-schedule (2.0.2) on Ubuntu Hardy alpha 5 and i've seen that gnome-schedule places its files in /.gnome directory.

Whereas there are specs about that, by freedesktop.org :
The default for $XDG_CONFIG_HOME is $HOME/.config, the default for $XDG_DATA_HOME is $HOME/.local/share. So all applications should look for those environment variables and use those default vaulues if the variables are not set.

See http://www.freedesktop.org/wiki/Specifications/basedir-spec
See also http://ploum.frimouvy.org/?184-cleaning-user-preferences-keeping-user-data (main post and comment#8)

PS : i like the new UI, thank you for that piece of software

Steps to reproduce:
Install gnome-schedule from synaptic with Ubuntu Hardy

Actual results:
The directories structure used by gnome-schedule doesn't match freedesktop.org specs 

Expected results:
gnome-schedule should not use /.gnome directory for its files but should match these specs http://standards.freedesktop.org/basedir-spec/latest/ar01s02.html

Does this happen every time?
yes

Other information:
Comment 1 Christian Persch 2010-04-19 14:40:50 UTC
*** Bug 616170 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2021-05-25 11:34:54 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/gnome-schedule/-/issues/

Thank you for your understanding and your help.