Hi,
Josselin Mouette wrote:
Le vendredi 30 novembre 2007 à 17:03 +0100, Manuel Bilderbeek a écrit :
The hint was to look at .xsession-errors, which contained complaints
about programs not knowing about -sm style options, meaning they are not
going to register to the session manager, indeed.
I'm also still puzzled how/why these things end up in the session file
when saving a session, while they're not even compatible with the GNOME
session manager system.
These are definitely bugs in these programs, as gnome-session only
records what the programs say about their restart options.
But, how can those non-GNOME programs (like yarssr) end up in the
session if they're not even GNOME compliant and thus cause the splash
screen to hang?
I even found out that after removing them and letting them (e.g. yarssr)
start again by using the 'start up programs' option of the session
management GUI and then using Save Session, they will end up in the
session again, causing the 'splash screen hangs' effect.
In other words: when using these start up programs (yarssr), there is no
way to save the session without editing the session file manually
afterwards to prevent this splash bug/effect.
--
Grtjs, Manuel
PS: MSX FOR EVER! (Questions? http://faq.msxnet.org/ )
PPS: Visit my homepage at http://manuel.msxnet.org/
