On Mon, Dec 15, 2003 at 07:16:56PM +0200, stu wrote: > On Mon, 15 Dec 2003 13:59:11 +0000 > Mikhael Goikhman <[EMAIL PROTECTED]> wrote: > > or ask konsole developers to add XSMP support that konsole > > seems to lack (otherwise there would be the unique id for each konsole > > window and no heuristical guess-by-name is needed). > > xwininfo returns the following id's for my konsole windows : > > xwininfo: Window id: 0x2400005 "Shell No. 2 - Konsole" > xwininfo: Window id: 0x1200005 "Shell No. 3 - Konsole" > xwininfo: Window id: 0x1400005 "[EMAIL PROTECTED]:/home/stu/meerrs - Shell No. > 6 - Konsole" > > AFAICS they all have unique window id's (or am I looking in the wrong > place maybe?)
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. > > It is also possible that something just does not work well together > > (fvwm, ksmserver, konsole etc). > > Possibly. As I stated above, I don't use any kind of session manager > with fvwm, but 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. > > In this case you may debug the problem if possible and report your > > results. > > As a beginning I started up window-maker, started 3 konsole sessions on > 3 different desktops, numbered each one and restarted window-maker a few > times. Each session was on the correct desktop after the restarts. > > I will try closing down all apps except konsole (when work is over) and > then checking if the problem persists. Do you have any advice as to how > I may further debug this problem, if this route is required? 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. Ciao Dominik ^_^ ^_^ -- 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 [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
