Bug 35368 - fullscreen focus mouse flashing
Summary: fullscreen focus mouse flashing
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 0.2
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 58450 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-11-26 15:03 UTC by Axel Kittenberger
Modified: 2004-01-20 17:16 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Kittenberger 2001-11-26 14:59:25 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           konsole
Version:           1.0.2 (using KDE 2.2.2 )
Severity:          normal
Installed from:    Compiled From Sources
Compiler:          gcc 2.95.3
OS:                Linux
OS/Compiler notes: Not Specified

If you configure the windowsmanager for focus follows mouse (+ autoraise) and set a konsole to fullscreen mode but happen to slip of with the mouse pointer to another window you'll find your screen flashing wildy as it seems the two windows are fighting each other for the focus.

(Submitted via bugs.kde.org)
Comment 1 Max Howell 2003-02-24 17:29:23 UTC
I can confirm this bug. To replicate launch an app from the konsole:

# Konqueror &

Then move the mouse! You can "rescue" the konqueror instance by ALT-TAB and if
your mouse is in the right place you can use Konqueror.

I'm using current CVS HEAD.
Comment 2 Stephan Binner 2003-05-17 12:52:51 UTC
*** Bug 58450 has been marked as a duplicate of this bug. ***
Comment 3 Lubos Lunak 2003-09-17 13:01:34 UTC
I cannot reproduce the problem with current CVS HEAD version. Please reopen the bugreport if 
the problem still persists. 
 
Comment 4 Joao S . O . Bueno 2004-01-16 00:54:46 UTC
Hi there,

I am afraid I will ask for you to reopen this.

While it doesn't seen to happen with pure KDE apps,
I got this problem with HEAD version of The GIMP.
While the GIMP is not a KDE application, the call
 that causes the problem is a  standard GTK call
for a window to become full screen. I think that 
you could take a look at it, as it seens only to be
fixable on the KDE side. 

I will paste my repot on this bug I made to bug.gimp.org
, followed by The GIMP code that causes the missbehavior.

+------- Additional Comments From gwidion@mpc.com.br  2004-01-15 13:13 -------
+Hi there, 
+ 
+I reproduced it here, and it is indeed quite ugly. 
+ 
+It has to do with "focus follow mouse" under KDE. (I tested - it 
+doesn't happen with "click to focus"), and will oftenly 
+leave the screen blinking between full screen and normal view 
+without stopping. 
+ 
+I could figure out the reasons why that happens: 
+ 
+It seens that the current image window is hidden when one hits F11, 
+before the screen state goes to full screen. That will expose the  
+underlying windows in the X11. With Focus follow mouse, KDE changes 
+the focus to another application or to other GIMP window - that has 
+the effect of taking the screen off the full screen view. When it 
+comes off, the original image window is redisplayed, and is given 
+focus --- the system them tries to switch to full screen again, 
+running in a pavorous flicking loop. 
+ 
+If there are no other windows under the mouse pointer when F11 is 
+hit, full screen works fine. (Actually it is also the only condition 
+that will take the flickering off once it starts) 
+ 
Now, the GIMP code, a single GTK call:
in app/display/gimpdisplayshell-appearance.c
(...)
void
gimp_display_shell_set_fullscreen (GimpDisplayShell *shell,
                                   gboolean          fullscreen)
{
 (...)
      if (fullscreen)
         gtk_window_fullscreen (GTK_WINDOW (shell));
 (...)

---

regards, and I hope it can be fixed for 3.2
Comment 5 Lubos Lunak 2004-01-16 17:36:45 UTC
Duplicate of bug #69238 actually. Could you please retest with 3.2RC1? (And for bugreports from elsewhere, it's much better to provide URL for them.)
Comment 6 Joao S . O . Bueno 2004-01-20 17:16:16 UTC
I finally got someone running a newer KDE that could test it for me.
It is indeed fixed. Thanks.