Activity for laur
-
laur posted a comment on ticket #147
Any chance it's related to https://sourceforge.net/p/vcxsrv/bugs/85/?
-
Bump, still looking for a solution.
-
@marha any hope you'd be willing to look into this issue again?
-
Managed to compile debug build from 5c535d5a5228b8810e25c86e5fc2e7b5663d41b4. Added a bit logging (see my git stash, apply with $git apply /path/to/file), and defined WIN_DEBUG_MESSAGES=1 environment variable. vcxsrv is launched using -keyhook -logfile C:\Users\layr\file.log -logverbose 4 options. For Super+H, which works fine, we get following output in log: (note in all log excerpts below, different button event blocks have been separated by an empty line) winKeyboardMessageHook: vkCode: 0000005b...
-
Managed to compile debug build from 5c535d5a5228b8810e25c86e5fc2e7b5663d41b4. Added a bit logging (see my git stash, apply with $git apply /path/to/file), and defined WIN_DEBUG_MESSAGES=1 environment variable. vcxsrv is launched using -keyhook -logfile C:\Users\layr\file.log -logverbose 4 options. For Super+H, which works fine, we get following output in log: (note in all log excerpts below, different button event blocks have been separated by newline) winKeyboardMessageHook: vkCode: 0000005b scanCode:...
-
Managed to compile debug build from 5c535d5a5228b8810e25c86e5fc2e7b5663d41b4. Added a bit logging (see my git stash, apply with $git apply /path/to/file), and defined WIN_DEBUG_MESSAGES=1 environment variable. For Super+H, which works fine, we get following output in log: (note in all log excerpts below, different button event blocks have been separated by newline) winKeyboardMessageHook: vkCode: 0000005b scanCode: 0000005b !! fPassKeystroke = TRUE winWindowProc - Message WM_KEYDOWN hwnd 0x0000000000C308A2...
-
Managed to compile debug build from 5c535d5a5228b8810e25c86e5fc2e7b5663d41b4. Added a bit logging (see my git stash, apply with $git apply /path/to/file), and defined WIN_DEBUG_MESSAGES=1 environment variable. For Super+H, we get following output in log: (note in all log excerpts below, different button event blocks have been separated by newline) winKeyboardMessageHook: vkCode: 0000005b scanCode: 0000005b !! fPassKeystroke = TRUE winWindowProc - Message WM_KEYDOWN hwnd 0x0000000000C308A2 wParam...
-
This too needs debug installation. Ticket closed.
-
Looks like this is duplicate of #104
-
running debug version fails
-
Turns out nsis is always called by buildall.sh via packageall.bat, and it's hardcoded to specific VS version which i didn't have. Changed the version in packageall.bat and installer creation worked fine. This issue can be closed.
-
Compiled debug ver dir listing: layr@WH5005264:~/vcxsrv4/xorg-server/obj64/servdebug$ ls -lt total 27064 -rwxr-xr-x 1 layr Domain Users 7313415 Aug 12 18:25 vcxsrv.map -rwxr-xr-x 1 layr Domain Users 13873152 Aug 12 18:25 vcxsrv.pdb -rwxr-xr-x 1 layr Domain Users 6442496 Aug 12 18:25 vcxsrv.exe -rwxr-xr-x 1 layr Domain Users 30692 Aug 12 18:25 vcxsrv.lib -rwxr-xr-x 1 layr Domain Users 18469 Aug 12 18:25 vcxsrv.exp -rwxr-xr-x 1 layr Domain Users 28480 Aug 12 18:25 XWin.res
-
missing dlls when running compiled exe
-
Right... should python be uninstalled on the host? So far, I 1. created link to python.exe pointing at the cygwin one, got past the error 2. got an error on missing gperf - installed w/ cygwin (needs to be added to bulding.txt?) 3. got an error about missing python3.6m.exe - solved same way as 1); Now getting this err
-
Right... should python be uninstalled on the host? So far, I 1. created link to python.exe pointing at the cygwin one, got past the error 2. got an error on missing gperf - installed w/ cygwin (needs to be added to bulding.txt?) 3. got an error about missing python3.6m.exe - solved same way as 1); Now getting this err: Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch. Build started 24/09/2018 21:02:02. Project "C:\tools\cygwin\home\layr\vcxsrv\tools\mhmake\mhmakevc10.sln"...
-
Right... should python be uninstalled on the host? So far, I 1. created link to python.exe pointing at the cygwin one, got past the error 2. got an error on missing gperf - installed w/ cygwin (needs to be added to bulding.txt?) 3. got an error about missing python3.6m.exe - solved same way as 1); Now getting this err:
-
Doesn't sound like a vcxsrv issue. Can you reproduce this issue if you click on the 'Settings' menu button, and 1. highlight 'Repositories' using arrow keys -> press Enter; 2. highlight any item in the opened drop-down menu -> press 'R' key?
-
Any pointers? Still trying to get to compile in order to debug the super+L issue.
-
Could you also verify it doesn't reproduce with previous tag?
-
Note C:\tools\cygwin\home\layr\vcxsrv\xcb-util-errors\obj64\debug\extensions.c doesn't exist. Only file by that name is in mesalib/src/mesa/main/extensions.c
-
Note C:\tools\cygwin\home\layr\vcxsrv\xcb-util-errors\obj64\debug\extensions.c doesn't exist.
-
Note C:\tools\cygwin\home\laliste\vcxsrv\xcb-util-errors\obj64\debug\extensions.c doesn't exist.
-
vcxsrv compilation err - xcb-util-errors\obj64\debug\extensions.c fails
-
buildall.sh: vcxsrv compilation failure - mhmake ran from incorrect directory
-
m4 ver the same as well. Linefeed format is a good call. I do recall having to change buildall.sh to unix format. Do you have core.autocrlf explicitly configured in your gitconfig? Edit: that was it - on windows, git's core.autocrlf (check with git config --get core.autocrlf) is set to true, meaning files are checked-out in windows format. Either change git config, or convert all files to unix format via find . -type f -print0 | xargs -0 dos2unix mhmake compiles, can be closed now.
-
m4 ver the same as well. Linefeed format is a good call. I do recall having to change buildall.sh to unix format. Do you have core.autocrlf explicitly configured in your gitconfig? Edit: that was it - on windows, git's core.autocrlf (check with git config --get core.autocrlf) is set to true, meaning files are checked-out in windows format. Either change git config, or convert all files to unix format via find . -type f -print0 | xargs -0 dos2unix
-
m4 ver the same as well. Linefeed format is a good call. I do recall having to change buildall.sh to unix format. Do you have core.autocrlf explicitly configured in your gitconfig?
-
-logfile param not respected
-
How important is it to have perl installed exactly under C:? Already had required perl on my PATH, but just noticed instructions say it needs to be a portable edition and living right under C. Edit: tried now also w/ portable ver insalled, still the same: $ ls -lt /cygdrive/c/perl total 36 drwxrwx---+ 1 layr Domain Users 0 Sep 1 12:41 win32 drwxrwx---+ 1 layr Domain Users 0 Sep 1 12:40 perl drwxrwx---+ 1 layr Domain Users 0 Sep 1 12:40 licenses drwxrwx---+ 1 layr Domain Users 0 Sep 1 12:40 cpan drwxrwx---+...
-
Yes, I had edited buildall.sh hot to require that installation path. Any suggestion re. that /usr/bin/m4:src/bisondata/lalr1.cc:389: ERROR: end of file in string exception?
-
How important is it to have perl installed exactly under C:? Already had required perl on my PATH, but just noticed instructions say it needs to be a portable edition and living right under C. Edit: tried now also w/ portable ver insalled, same: $ ls -lt /cygdrive/c/perl total 36 drwxrwx---+ 1 layr Domain Users 0 Sep 1 12:41 win32 drwxrwx---+ 1 layr Domain Users 0 Sep 1 12:40 perl drwxrwx---+ 1 layr Domain Users 0 Sep 1 12:40 licenses drwxrwx---+ 1 layr Domain Users 0 Sep 1 12:40 cpan drwxrwx---+...
-
How important is it to have perl installed exactly under C:? Already had required perl on my PATH, but just noticed instructions say it needs to be a portable edition and living right under C.
-
Yes, can confirm I have exact same versions of flex & bison.
-
Ah, wasn't obvious from the error. Got to new error now: Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch. Build started 30/08/2018 01:44:22. Project "C:\Users\layr\Documents\dev\vcxsrv-code\tools\mhmake\mhmakevc10.sln" on node 1 (Build target(s)). ValidateSolutionConfiguration: Building solution configuration "Release|x64". Project "C:\Users\layr\Documents\dev\vcxsrv-code\tools\mhmake\mhmakevc10.sln" (1) is building "C:\Users\layr\Documents\dev\vcxsrv-code\tools\mhmake\mhmake.vcxproj"...
-
Saw it got already updated, great work. How can we close tickets in SF?
-
I already looket at this, but I do not see any filtering on the Super+L key. in the code. The key is seen by the keyboard hook that is installed. So you see no reason in the code why super+L should act any different than say super+E? Any idea what my problem might be caused by? Are you able to reproduce (assuming you're willing to edit your registry in order to disable widows' hook)? Off topic - would it be possible to force vcxsrv hook be installed after other hooks like AHK? In that case it would...
-
mhmake compilation error
-
change sdk ver to 10.0.17134.0
-
I already looket at this, but I do not see any filtering on the Super+L key. in the code. The key is seen by the keyboard hook that is installed. So you see no reason in the code why super+L should act any different than say super+E? Any idea what my problem might be caused by? Are you able to reproduce (assuming you're willing to edit your registry in order to disable widows' hook)? Off topic - would it be possible to force vcxsrv hook be installed after other hooks like AHK? In that case it would...
-
I already looket at this, but I do not see any filtering on the Super+L key. in the code. The key is seen by the keyboard hook that is installed. So you see no reason in the code why super+L should act any different than say super+E? Any idea what my problem might be caused by? Are you able to reproduce (assuming you're willing to edit your registry in order to disable widows' hook)? Off topic - would it be possible to force vcxsrv hook be installed after other hooks like AHK? In that case it would...
-
I already looket at this, but I do not see any filtering on the Super+L key. in the code. The key is seen by the keyboard hook that is installed. So you see no reason in the code why super+L should act any different than say super+E? Any idea what this might be caused by? Are you able to reproduce (assuming you're willing to edit your registry in order to disable widows' hook)? Off topic - would it be possible to force vcxsrv hook be installed after other hooks like AHK? In that case it would be...
-
Suspect we should be looking in hw/xwin/winkeyhook.c. Any suggestions on how to debug it? -logverbose with values of 3 or 4 didn't change anything in logs.
-
Super+L not passed through and getting stuck with VcXsrv
1