Version: (using KDE KDE 3.5.5) Installed from: Gentoo Packages Compiler: gcc (GCC) 4.1.1 Gentoo 4.1.1-r1 OS: Linux Hi. I've got 2 screens: Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 Screen 1 "Screen1" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Section "Screen" Identifier "Screen1" Device "Card1" Monitor "TV" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection Section "Device" Identifier "Card0" Driver "nvidia" VendorName "nVidia Corporation" BusID "PCI:1:0:0" EndSection Section "Device" Identifier "Card1" Driver "nvidia" BusID "PCI:1:0:0" Option "TVStandard" "NTSC-M" Option "UseDisplayDevice" "TV" Option "TVOutFormat" "COMPOSITE" Option "TVOverScan" "0.65" EndSection The problem is, that any window any time can loose focus. Like this: 1. open kmail on screen :0.1 2. select message 3. press shift+delete 4. confirm 5. kmail lost focus 6. press alt+F2 to open "Run Command" dialog. It appears on screen :0.1 and not :0.0 This happens too many time, not only when runnig kmail, but also when you searching for something (ctrl+F) and you close "Find Text" dialog. It works when I swith to beryl, as a window manager. So I think, this is kwin related feature. X: /usr/bin/X -br -nolisten tcp -dpi 96 :0 vt7 -auth /var/run/xauth/A:0-DZsaq7
I see a big improvement in 3.5.6 version. CTRL+F is working, no more nonactive window. Thanx But there are still some situations, where I've got problems. Suppose I've got one konsole and one ICQ chat window in kopete. So there are only 2 windows and chat one is active. When I close it, konsole window is sometimes active, sometimes not. It looks like dialog doesn't deactivate parent window anymore, but when there are 2 (maybe more) separated windows and I close one, there's a chance that KDE (kwin or whatever) change active screen from :0.0 to :0.1.
*** This bug has been marked as a duplicate of 134677 ***