reassign 443690 xfwm4 found 443690 4.4.1-3 thank you
Yves-Alexis Perez wrote: >> I've been running xfce4 for awhile now using a multi-head disply >> configuration (:0.0 and :0.1, no Xinerama). Most of my menu items have >> "Use startup notification" checked. Up until a recent update (I assume >> the update to 4.4.1-3 today when I ran an update), this wasn't an issue >> as any application I would start up would end up displaying on the >> display from which I clicked on the menu item initially. >> >> Now, however, when I try to open an application from the menu >> which has startup notification enabled, the application always starts on >> display :0.0 even though my mouse and the menu itself is displayed on >> :0.1. Unchecking the option in the menu editor allows all of the >> applications I try to open on :0.1 to show up correctly on that >> particular display. >> [...] > Anyway, dual-head and xinerama are dead now that xserver 1.4 is out, it's > replaced by randr 1.2 (not for every drivers but...).non-xinerama dual head is > dead completely, AFAIK, so it may be your problem. Maybe your driver isn't > randr-aware but there was some changes in the xserver. > The window manager takes care of placing windows, so I am reassigning back to xfwm4. Mark, please describe precisely your X config (which xserver-xorg-core, which driver, which dual-head config in xorg.conf, ...). If you're using a RandR 1.2 driver (Intel 2.x, ATI 6.7.x, mga 1.9.x or nv 2.1.x on a G80), the problem is probably that xfwm4 doesn't know yet how to use multiple RandR 1.2 outputs. If using a old-style dual-head (with independent :0.0 and :0.1 screens, without a way to move windows across them), then xfwm4 seems to have problems managing these multiple screens. But I don't see what could have broken xfwm4 recently. Even with xserver 1.4, it should just work the same for old-style drivers (while it doesn't work anymore with RandR 1.2 drivers). I am waiting for more information from Mark about this. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
