gajim does not start from a saved GNOME session.
Bug description
gajim does not start from a saved GNOME session.
When saving the current session in GNOME (either via the GUI or using gnome-session-save(1)), GNOME stores an entry (a .desktop file in ~/.config/gnome-session/saved-session for GNOME 2.30) that calls gajim using command line arguments like --sm-config-prefix /gajim.py-XXXXXX/ --sm-client-id XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX --screen 0 . Gajim however does not handle these command line arguments and thus does not start from that saved session. If one manually edits the session removing the command line arguments, gajim properly starts on login.
Apparently gajim does use some GNOME functionality that tells GNOME it supported session management, but does not use the functionality that takes care of the session management commandline argumentes.
gajim should ompletely handle GNOME session management or at least (as a hack) silently ignore the corresponding command line arguments.
Software versions
OS version: Debian GNU/Linux squeeze
GTK version: 2.20.1
PyGTK version: 2.17.0