Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keyla needs restart after screen locking in Windows 8 #33

Open
GoogleCodeExporter opened this issue Apr 25, 2016 · 5 comments
Open

Keyla needs restart after screen locking in Windows 8 #33

GoogleCodeExporter opened this issue Apr 25, 2016 · 5 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Install and start Keyla on a Windows 8 box (no special treatment here);
2. Observe that switching works just fine, then lock the screen using Win+L;
3. Unlock the screen, and find that switching no longer works.

Original issue reported on code.google.com by ulid...@gmail.com on 14 Mar 2013 at 12:14

@GoogleCodeExporter
Copy link
Author

Having read the sources, I can say that they should handle the 
WM_WTSESSION_CHANGE message: 
http://msdn.microsoft.com/en-us/library/windows/desktop/aa383828%28v=vs.85%29.as
px

Unfortunately, I can't produce a working patch right now.

Original comment by ulid...@gmail.com on 25 Jul 2013 at 10:02

@GoogleCodeExporter
Copy link
Author

Thanks for filing this bug report.  Judging from the behaviour, seems that 
Windows no longer calls keyla after locking and unlocking the screen.  If you 
indeed want to hack the code, you may try to remove and attach again the 
keyla's hook after you receive the message that the screen has been unlocked.  
By the way, are you sure the message we need is WM_WTSESSION_CHANGE?  In the 
MSDN article you linked it's under Remote Services API that does not seem 
related to me.

Original comment by earshi...@gmail.com on 28 Jul 2013 at 8:39

@GoogleCodeExporter
Copy link
Author

I also observe a behavior where the switching no longer works - on Windows 7.

It does apparently happen consistently on Win+L, but also often happen when the 
"screensaver" lock screen kicks in - but evidently not always..

It is EXTREMELY annoying. Is it easy to fix? I have been thinking of 
auto-killing it every minute or so, and just restarting it..!

Original comment by stolsvik on 29 Oct 2013 at 11:25

@GoogleCodeExporter
Copy link
Author

Any chance of fixing this RSN? Would US$50 be an incentive?  (Windows 7)

Original comment by stolsvik on 7 Feb 2014 at 8:50

@GoogleCodeExporter
Copy link
Author

Maybe it's common bug with #27, see for patched version in comments.

Original comment by vapaam...@yandex.ru on 5 Jun 2014 at 2:19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant