Version: (using KDE KDE 3.1.4) Installed from: Slackware Packages I created an Application Button on my Kicker, that executes the following command: LC_ALL=zh_HK.big5hkscs gaim In order to run Gaim under the Big5 locale. (I start my KDE with a UTF-8 locale). Log out, log back in. Gaim is started, but with the default locale. I have to shut it down and restart it. I suspect that the KDE Session Manager forgets the environment variables the application runs under. Is there a way to restore them?
It should be the application that asks the session manager to remember its environment variables, and it doesn't look like GNOME apps actually do that (neither KDE ones). But also ksmserver doesn't support it. I suggest you simply create a small wrapper script placed in $PATH before the real application that which does 'LC_ALL=zh_HK.big5hkscs exec /real/path/gaim'.
Yes it will work as a workaround - is there any plan to remember environment variables in future versions of the session manager?
That's why I kept this bugreport open. But as you can see from the priority, I don't think it's really that useful - I don't know any app that uses that anyway.
*** Bug 113350 has been marked as a duplicate of this bug. ***
Using a wrapper script does _not_ work. That's what I've been doing from the beginning. So the real problem is that some applications claim to be session managable, which really aren't, and shoundn't be restarted? There seem to be quite some. For instance gqview, which gets restarted, but doesn't reload the image. Perhaps (apart from fixing the programs) the solution would be to make it configurable which applications get session managed; perhaps as an option in the extended window settings. (The ones reachable via the little button on the left of the top window bar.)
No, the real problem is how much (the applications can handle) to restore. It's the application's job to restore all its data and its up to it how much (if any) it tries to save and restore. You can disable specific application from session management in the session manager kcontrol module.
Closing this is outdated and KDE 3.x is not maintained anymore.
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.