On Wed, Jul 16, 2003 at 06:08:41PM +0200, Olivier Chapuis wrote: > On Sat, Jul 05, 2003 at 10:06:34AM -0400, Tessa Lau wrote: > > I'm installing Debian unstable and the latest GNOME2 desktop on a > > friend's system, and I'm trying to convince him to see the light and > > switch from sawfish to fvwm2. However I'm running into a few bugs with > > the GNOME2 integration. I'm using a freshly built fvwm 2.5.7. > > > > I switch to fvwm by killing sawfish and running fvwm2, then saving my > > session. The first time after I log out and log back in with fvwm, the > > GNOME menu panel, which is always at the top of the screen, has been > > relocated to the bottom of the screen. The bottom edge panel has been > > relocated to the top of the screen. The menu panel cannot be moved. If > > I move the bottom edge panel down to the bottom of the screen where it > > belongs, it gets hidden behind the menu panel, and is lost forever. > > > > It is a fvwm bug. I hope that we will be able to fix it soon. > > I switch to the fvwm-workers list. > > The problem is simple: all gnome panels have the same name, icon name, > res name and class name! So when we restore the window state fvwm/session.c > is unable to make the distinction between all the gnome panels. > > Any idea for a fix? >
The obvious idea after reading the SM spec (and the ICCCM2) is to use the SM_CLIENT_ID property (on a possible WM_CLIENT_LEADER window) But, at first view the gnome panels have no SM_CLIENT_ID set!! I think that sawfish, metacity, icewm and kwin simply ignore window without the SM_CLIENT_ID property set (on the client leader) regarding session management. I think we should add the SM_CLIENT_ID as the main identifier in the session code and either: - do not reset "session state" for windows with an identifier (sm client id, name ...etc) with two matching identifiers in the session window list. or - simply do not save/restore state for window without SM_CLIENT_ID. Regards, Olivier -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
