On Mon, 15 Dec 2003 16:41:53 +0100
Dominik Vogt <fvwm_at_fvwm.org> wrote:
> Of course all windows have a unique window id, but these are given
> by the X server and can be used by a different application if the
> window dies in the mean time. Therefore, they need a special SM
> id too.
How would one get the SM id for a window, or determine whether or not
one exists?
> > > It is also possible that something just does not work well
> > > together(fvwm, ksmserver, konsole etc).
> >
> > loading konsole causes the following kde related
> > processes to run (output from 'ps afx'):
> >
> > 19720 ? S 0:00 kdeinit: Running...
> > 19723 ? S 0:00 kdeinit: dcopserver --nosid --suicide
> > 19726 ? S 0:00 kdeinit: klauncher
> > 9572 ? S 0:01 kdeinit: knotify
> >
> > Could any one of these be causing this problem?
>
> I'm really just guessing, but klauncher sounds as if it might do
> session management.
No, klauncher works with dcop for KDE's inter-process communication.
> To verify whether it's a SM problem or not, ./configure fvwm with
> the --disable-sm option. If the problem goes away, it has
> something to do with session menagement.
Although I don't have any kind of session-manager running, I will
give this a try.
> Ciao
>
> Dominik ^_^ ^_^
Thanks
--
Stuart Logie
Programmer
UNIVERSAL COMPUTER SERVICES (PTY) LTD
A member of South Africa's largest retail software vendor, the UCS Group
Tel : (011) 712 1371 Cell : 082 902 5632
Fax : (011) 339 3421
Internet : http://ucs.co.za
"I am the Unconquerable Spirit."
-- Poet Unknown
Powered by Debian GNU/Linux - testing/unstable
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Dec 17 2003 - 10:26:37 GMT