Bug 879946

Summary: AUTOSTART FOLDERS - non compliance to freedesktop.org standards
Product: [Fedora] Fedora Reporter: Andrei ILIE <andrei.ilie>
Component: distributionAssignee: Bill Nottingham <notting>
Status: CLOSED WONTFIX QA Contact: Bill Nottingham <notting>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: dennis, ltinkl, mclasen, rdieter, rstrode, rvokal, than
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 05:44:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andrei ILIE 2012-11-25 16:59:23 UTC
We have too many autostart directories...

freedesktop.org clearly states: "By placing an application's .desktop file in one of the autostart directories the application will be automatically launched during startup of the user's desktop environment after the user has logged in. [...] The autostart directories are:
    ~/.config/autostart/    (personal autostart directory)
    /etc/xdg/autostart/     (system wide autostart directory)"

In practice, however, there's at least six folders, which creates, let's say, a bit of confusion:
    ~/.kde/Autostart/
    ~/.kde/share/autostart/
    ~/.config/autostart/
    ~/.local/share/autostart/
    /etc/xdg/autostart/
    /usr/share/autostart/

Please see the related KDE bug report: https://bugs.kde.org/show_bug.cgi?id=310657

Comment 1 Matthias Clasen 2012-11-26 20:39:58 UTC
For the GNOME side, we only use /etc/xdg/autostart, /usr/share/gnome/autostart and ~/.config/autostart

Comment 2 Rex Dieter 2012-11-28 19:26:36 UTC
KDE likewise makes use of /etc/xdg/autostart, /usr/share/autostart (kde-specific) and ~/.config/autostart, ~/.kde/share/autostart (kde-specific)

~/.kde/Autostart is very much legacy (from kde3 days).


I'm not sure what the point of this bug is really, but I don't see much anything actionable here.

Comment 3 Fedora End Of Life 2013-07-04 01:22:59 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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.

Comment 4 Fedora End Of Life 2013-08-01 05:44:31 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.