Bug 237055 - Alt key toggles maximization
Summary: Alt key toggles maximization
Status: RESOLVED DUPLICATE of bug 222100
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2010-05-10 03:17 UTC by Ali Shah
Modified: 2010-06-10 22:09 UTC (History)
0 users

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 Ali Shah 2010-05-10 03:17:05 UTC
Version:            (using KDE 4.4.2)
Compiler:          GCC G++ 4.4.3 
OS:                Linux
Installed from:    Ubuntu Packages

Pressing the ALT key in Ubuntu 10.04 sometimes cause the currently focused window to un-maximize.
Comment 1 Christoph Feck 2010-05-10 23:39:19 UTC
Are you actually using KWin (KDE window manager) and not Compiz or MetaCity (Gnome window manager)? You can check by right-click on window title bar. Selecting "Configure Window Behavior..." there should open the KWin configuration dialog.
Comment 2 Thomas Lübking 2010-05-10 23:52:40 UTC
sounds like the window also receives an active mousemove event.
iff you're using kwin and opened the config dialog, enter the "screen edges" dialog and check whether "Maximize Windows by draggin them..." ("quick maximization" aka aero-snap) is checked.
In case uncheck and see whether the problem remains.

Sure you didn't accidently also pressed the left mouse button and moved the pointer (eg. accidently on a touchpad)
Comment 3 Ali Shah 2010-05-11 01:14:59 UTC
(In reply to comment #1)
> Are you actually using KWin (KDE window manager) and not Compiz or MetaCity
> (Gnome window manager)? You can check by right-click on window title bar.
> Selecting "Configure Window Behavior..." there should open the KWin
> configuration dialog.

Yes I am using KWin, right clicking on the window title bar and selecting "Configure Window Behavior" opens up the KWin configuration dialog.
Comment 4 Ali Shah 2010-05-11 01:18:09 UTC
(In reply to comment #2)
> sounds like the window also receives an active mousemove event.
> iff you're using kwin and opened the config dialog, enter the "screen edges"
> dialog and check whether "Maximize Windows by draggin them..." ("quick
> maximization" aka aero-snap) is checked.
> In case uncheck and see whether the problem remains.
> 
> Sure you didn't accidently also pressed the left mouse button and moved the
> pointer (eg. accidently on a touchpad)

I will try this and report back, might take a while since it doesn't happen often.
Comment 5 Martin Flöser 2010-05-23 16:39:23 UTC
any news?
Comment 6 Ali Shah 2010-05-28 16:31:26 UTC
Still happens :( I'm wondering if my keyboard / track pad might be malfunctioning. There have been cases where I have only one hand on the keyboard when I press the alt key, when the window I am working in de-maximizes. But it usually after I have used the mouse- so it could be that my track pad is offering up some bogus movement. Anyway to test this?
Comment 7 Ali Shah 2010-06-08 23:02:48 UTC
I've been able to reproduce this more successfully. 

1. I load up a firefox page thats larger than my vertical screen resolution so I can scroll up and down. 
2. I then use right most portion of my mouse trackpad to scroll up and down. 
3. I stop touching the track pad and quickly press the alt button. 

This causes the window to unmaximize. These steps cause this problem to occur 3/5 times I do it- and it is clear from my experiments that I am not actively touching the trackpad.
Comment 8 Thomas Lübking 2010-06-08 23:14:33 UTC
still sounds related to the touchpad usage, thus a hardware or touchpad driver bug.
did you disbale quick maximization at all?
(in case this is in a way related to bugs #222100 & #240024)
Comment 9 Martin Flöser 2010-06-10 22:09:39 UTC
sound very much like bug #222100. If you have disabled quick maximization and the problem still occurs, please reopen.

*** This bug has been marked as a duplicate of bug 222100 ***