Fluxbox is not a full "Desktop Environment" -> It is only a "Window
Manager"; and therefore it does not conform to the XDG Autostart
standard. The ~/.fluxbox/startup is the only thing that is executed on
startup, so it is the appropriate place to start daemons that are not
started automatically by the parent process, be it GDM, KDM, Slim or
startx.
Thus Phil's workaround ('gnome-keyring-daemon -s' in ~/.fluxbox/startup)
is indeed an appropriate solution.
Another possible solution is to run a 3rd-party app like lxsession (Part
of the LXDE: http://lxde.sf.net) that can already take care of XDG
Autostart initialization, and instruct it to run fluxbox as the Window
Manager.
There are a few specific things that could probably be done to improve
Fluxbox itself and its integration with an ever-increasing number of
/etc/xdg/autostart/* services:
1) Find out why, as stated in the original bug report, fluxbox's
~/.fluxbox/startup does not have access to the login session.
Now, I'm not exactly sure what "login session" means here, but if it has
something to do with consolekit or policykit permissions not propagating
down to ~/.fluxbox/startup, this would be a real problem! It would imply
that fluxbox itself (and therefore any application started by fluxbox,
say via the fluxbox menu) will also have no access to this "login
session".
2) Write or find some code (maybe some kind of desktop-agnostic XDG
autostart script?) to deal with things in /etc/xdg/autostart properly,
and change the default ~/.fluxbox/startup script to run this.
It would probably be nice if this were a separate (ie, not part of
fluxbox) script or application, as it could be shared by many different
non-DE WMs (openbox, wmii, etc)
--
xdg .desktop files don't recognize "fluxbox"
https://bugs.launchpad.net/bugs/581296
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
