Bug 70043 - Cannot close windows with keyboard (e.g. Alt+F4) when using VMWare
Summary: Cannot close windows with keyboard (e.g. Alt+F4) when using VMWare
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2003-12-10 21:01 UTC by Dima Ryazanov
Modified: 2018-10-21 05:03 UTC (History)
3 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 Dima Ryazanov 2003-12-10 21:01:10 UTC
Version:            (using KDE KDE 3.1.4)
Installed from:    Compiled From Sources
Compiler:          gcc 3.2.3 20030422 
OS:          Linux

After I start VMWare (running Windows XP), I cannot use Alt+F4 to close windows. If I run Control Center and set another combination or remove Alt+F4, apply changes, and add it again, it works - until I switch to VMWare. When I leave it, it stops working again.

KDE detects the combination Alt+F4, etc., but it just doesn't close windows.
Comment 1 Thiago Macieira 2003-12-10 22:45:35 UTC
When I used to use VMWare, this behaviour worked. It was HEAD at least 6 months ago, using both VMWare 3.2 and 4.0.
Comment 2 Dima Ryazanov 2004-07-17 05:16:46 UTC
Ok, now I'm using KDE 3.2.3, VMWare 4.5.2 build-8848.
Everything is the same. Alt+F4 stops working as soon as I switch to the host OS and back.
Comment 3 Dima Ryazanov 2004-07-17 05:19:58 UTC
Well, if I restart kwin, it's working again...
Comment 4 Lubos Lunak 2004-07-19 12:09:04 UTC
I see you have KDE compiled from sources. Do you have debug output working? Could you enable debug area 125 and attach debug output while switching to VMWare and back?
Comment 5 Dima Ryazanov 2004-08-02 00:17:27 UTC
Ok, I used the shortcut "Win-Alt-F4" for moving a window to the fourth 
desktop, and that affected "Alt-F4". You should be able to reproduce the bug 
now (if you have VMWare) - just assign the Win-Alt-F4 shortcut to a "Window 
to Desktop *" action.

If you still need the debug output:
> I see you have KDE compiled from sources. Do you have debug output working?
> Could you enable debug area 125 and attach debug output while switching to
> VMWare and back?
I'm recompiling kdebase with debug enabled... Where will I see the debug 
output? Should I run kwin from a terminal window?

Comment 6 Lubos Lunak 2004-08-03 11:23:41 UTC
You can start KWin from Konsole as 'kwin --replace', and after you're done, start it again from Alt+F2 as 'kwin --replace'. Don't try to kill the running instance, or you'll be unable to handle focus.
Comment 7 Dima Ryazanov 2004-08-12 06:19:10 UTC
Well, I can't see any useful output from KWin... That is, here's what I get 
after "kwin --replace":

kwin: RULES:0
kwin: User timestamp, initial:1395056
kwin: User timestamp, ASN:1395056
kwin: User timestamp, final:'ID:23068678;WMCLASS:kdesktop:kdesktop;Caption:KDE 
Desktop':1395056
kwin: Activation: No client active, allowing
kwin: User timestamp, initial:1432184
kwin: User timestamp, ASN:1432184
kwin: User timestamp, 
final:'ID:29360133;WMCLASS:konqueror:konqueror;Caption:Conquer your Desktop! 
- Konqueror':1432184
kwin: Activation: No client active, allowing
kwin: User timestamp, initial:4294967295
kwin: User timestamp, ASN:4294967295
kwin: User timestamp, final:'ID:41943049;WMCLASS:vmware:vmware;Caption:VMware 
Workstation':4294967295
kwin: Activation: No client active, allowing
kwin: User timestamp, initial:1496420
kwin: User timestamp, ASN:1496420
kwin: User timestamp, 
final:'ID:39845893;WMCLASS::qt-subapplication;Caption:dima@dima:~ - Shell - 
Konsole':1496420
kwin: Activation: No client active, allowing
kwin: User timestamp, initial:1426549
kwin: User timestamp, ASN:1426549
kwin: User timestamp, 
final:'ID:25165829;WMCLASS:kicker:kicker;Caption:kicker':1426549
kwin: Activation: No client active, allowing

Then I switch to VMWare, and back, and nothing more appears. Only when I stop 
it, I get two dialog boxes that generate this:

kwin: User timestamp, initial:4294967295
kwin: User timestamp, ASN:4294967295
kwin: User timestamp, 
final:'ID:41946327;WMCLASS:vmware:vmware;Caption:Warning':1506021
kwin: Activation: Belongs to active application
kwin: User timestamp, initial:4294967295
kwin: User timestamp, ASN:4294967295
kwin: User timestamp, final:'ID:41946348;WMCLASS:vmware:vmware;Caption:Hint 
Question':1508766
kwin: Activation: Belongs to active application

Also, I was doing this with 3.3beta2 - I though it would be more useful than 
with 3.2.

Comment 8 Lubos Lunak 2004-08-12 12:34:11 UTC
You forgot to enable the debug area 125 using 'kdebugdialog'. And please use attachments for large amounts of data.
Comment 9 Dima Ryazanov 2004-08-17 06:15:49 UTC
Sorry.
I enabled area 125. Still no output when I switch to the OS in VMWare and 
back. But, after that, when I press Alt+F4, I get this output _only_ when the 
mouse pointer is _not_ inside the active window:

kdecore (KAccel): Workspace::keyPress( Alt_L )
kdecore (KAccel): Workspace::keyPress( Alt+F4 )

Normally, however, I should always get this output, right?

Does the application itself get the keystroke?.. When I press Alt+F4 in a 
Konsole window, it prints the "^[^[OS".

Comment 10 Lubos Lunak 2004-08-17 12:46:21 UTC
This seems to be a VMWare bug. Could you try running some other window manager instead of KWin and see if it has a similar problem? For example use KDEWM=metacity before running KDE (see http://ktown.kde.org/~seli/kdewm/ for details).
Comment 11 Dima Ryazanov 2004-08-18 07:06:13 UTC
Everything works fine in Gnome and in KDE with metacity. And even in Gnome, 
when I replace metacity with KWin, the problem appears.

Comment 12 Philip Rodrigues 2006-09-09 11:38:16 UTC
Does this problem still occur with KDE 3.5?
Comment 13 Dima Ryazanov 2006-09-09 12:03:46 UTC
Yep...
Comment 14 Mike Williams 2007-01-08 18:59:36 UTC
Could you be more specific in the steps about how to reproduce this? I'm trying, and I can't make it fail.
Comment 15 Dima Ryazanov 2007-01-09 03:44:35 UTC
Well, everything I needed to reproduce it was:
1. Make Win-Alt-F4 a shortcut to switch to the fourth desktop.
2. Start a virtual machine
3. Click on it, so VMWare grabs the mouse and the keyboard, then leave it.

The "Win-Al-F4" shortcut makes all the difference.

(Also, I haven't used VMWare lately, so it's possible that it doesn't happen in KDE 3.5.5 anymore... I'll try again.)
Comment 16 Dima Ryazanov 2007-01-20 07:34:14 UTC
Yep, still happens with KDE 3.5.5.
Comment 17 Yoav Weiss 2007-09-23 04:51:12 UTC
The problem still reproduces and breaks more hotkeys.  For example, if you set Ctrl-Up (or any other arrow key) to do something in kde, start vmware and quit it, these hotkeys stop working.  "kcmshell keys" does show them but they don't work until you change them to something else and back to the desired value.  Easy to reproduce.
Comment 18 Jonas Vejlin 2009-04-04 15:53:57 UTC
Do you stil have this problem with recent version of kwin?
Comment 19 Martin Flöser 2009-12-19 14:32:59 UTC
(In reply to comment #18)
> Do you stil have this problem with recent version of kwin?
Does not seem so, setting to needsinfo
Comment 20 Andrew Crouthamel 2018-09-20 03:16:20 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 21 Andrew Crouthamel 2018-10-21 05:03:41 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!