giseldo/neodataset huggingface dataset:
Cross probing highlight in eeschema is missing (lp:#1801414)

[Original report](https://bugs.launchpad.net/bugs/1801414) created by **Nick Østergaard (nickoe)**
```
After the new GAL canvas in eeschema the crosshair that appeared on top of
a part when cross-probing from pcbnew to eeschema is gone. eeschema do
center properly over the part, so this but is not about the same as
described in https://bugs.launchpad.net/kicad/+bug/1766950

How to:
1. open a project which has a matching schematic and board file (you may
like to zoom far in in eeschema)
2. click a footprint in pcbnew
3. observe that you no form of marking is used in pcbnew to highlight a
selected footprint

Expected:
With the legacy canvas a small crosshair would appear on the center of the
symbol in eeschema. I would like to see this feature or a similar
implementation back in eeschema gal.

As we got the gal canvas, maybe it is better draw an opaque box around the
symbol, sort of similar to what is done with InteractiveHtmlBom, see
https://openscopeproject.org/InteractiveHtmlBomDemo/ . Don't be confused
with me thinking this is how it should look in pcbnew. All I am trying to
say with this is that a possible implementation is to have a red box with a
faint red background fill to highlight a symbol.

Application: kicad
Version: (6.0.0-rc1-dev-1119-gd465af65a), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.34.0
Platform: Linux 4.18.16-arch1-1-ARCH x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.1 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=OFF
    KICAD_SCRIPTING_MODULES=OFF
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=OFF
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema gal missing-gal-tool

Story points: 6.0
Magnetic pads don't work anymore in other than routing mode (lp:#1801377)

[Original report](https://bugs.launchpad.net/bugs/1801377) created by **eelik (eelik)**
```
I don't know if it's accidental or on purpose after snapping points was
introduced, but Magnetic pads: always doesn't work anymore in other than
track tool. I already filed a report about snapping points not snapping,
but right now it's impossible to set e.g. User origin to the center of a
pad in Measure tool mode.
```
Original tags: pcbnew

Story points: 6.0
It's impossible to set the Grid origin graphically to certain point (lp:#1801373)

[Original report](https://bugs.launchpad.net/bugs/1801373) created by **eelik (eelik)**
```
When the Grid origin tool is selected the cursor doesn't snap to grid or
anything else. It's practically impossible to set the grid origin to some
wanted coordinates. It can be done in a very tedious way by copying x and y
coordinates and setting them as text in Grid Settings but I would prefer
having the ability to snap to important points (centers of pads and
footprints). Otherwise the Grid origin doesn't even have much sense for me.

Another solution, wider in scope but more applicable for general purposes,
would be to add the the top level context menu "Coordinates" item which
would have subitems:

- Go to User origin
- Go to Grid origin
(- Go to somewhere else useful?)
- Set Grid origin here
(- Set something else useful here?)

That would solve the problem as long as User origin can still be set to a
wanted point graphically. Then I could go there with the menu item, open
the context menu again (carefully without moving the mouse) and set the
grid origin there.

(EDIT: actually just "Set grid origin here" would be enough as long as I
can snap to some point and open the menu from there, my thinking was too
complicated...)
```
Original tags: pcbnew

Story points: 6.0
Cursor doesn't snap when snapping point is active (lp:#1801369)

[Original report](https://bugs.launchpad.net/bugs/1801369) created by **eelik (eelik)**
```
The coordinates (seen in the bottom status bar) don't change and the cursor
doesn't really snap when I move the cursor for example in Measure tool mode
and a snap point is activated when it doesn't happen to be in the current
grid. Therefore it's impossible to set for example user origin to the
center of a pad.


Application: kicad
Version: (6.0.0-rc1-dev-1071-gb88121e37), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6
libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit,
Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: pcbnew

Story points: 6.0
Block copy not on grid (lp:#1801346)

[Original report](https://bugs.launchpad.net/bugs/1801346) created by **Ron Burkey (rburkey)**
```
A block cut-and-paste operation in eeschema moves objects off of the grid.

I've attached a schematic file that shows the bug in operation.  Using a
25-mil grid, I manually placed two 30-mil thick parallel graphic lines on
it.  The endpoints are (of course) on the 25-mil grid. I then block-copied
the pair of lines.  It was impossible to put the pasted pair on the 25-mil
grid.

Application: kicad
Version: 6.0.0-rc1-unknown-8be3471~66~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.11 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-53-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema

Story points: 14.0
"Edit Text and Graphics  Properties" for eeschema (lp:#1801150)

[Original report](https://bugs.launchpad.net/bugs/1801150) created by **Art (diametrix)**
```
Some of the symbols in the library have datasheet field visibility on as a
default.  After I'm done capturing schematic, I try to populate all the
datasheets for all the symbols using "Edit Symbol Fields" option.  However,
it kind of defeats the purpose of the tool, because there is no way to
affect visibility of the field in the "Edit Symbol Fields" tool.  So
afterword you have to go through each individual component and uncheck the
visibility check mark.  There needs to be visibility check marks right
there in the tool.  You can add the checkmarks easily in the left pane,
right next to Show and Group By columns.

Application: kicad
Version: (6.0.0-rc1-dev-1027-g90233e5ec), release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1
librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.60.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.54.1
    Compiler: GCC 7.1.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema feature.request

Story points: 28.0
GTK3 scrollbars cause repaint (lp:#1801135)

[Original report](https://bugs.launchpad.net/bugs/1801135) created by **Seth Hillbrand (sethh)**
```
GTK3 implements a new feature called "Overlay Scrolling".  This mimics the
Mac show/hide scrollbars when the cursor is near the edge.

Unfortunately, when the scrollbar is shown or hidden, it triggers a refresh
of the screen.  This happens once for the horizontal, once for the
vertical, then once for the set cursor position, then the scrollbars hide
themselves, triggering two more refreshes.

This happens for anything that has a scrollbar option.

The quick/dirty way is to set the environmental variable
GTK_OVERLAY_SCROLLING=0 before starting KiCad.  But this seems hack-y.  I
can't seem to find a way to programatically disable this option.

The better option would be to read where on the screen the repaint is
happening and just deal with that section instead of hitting the full
refresh.



Application: kicad
Version: (6.0.0-rc1-dev-1111-gad9998367-dirty), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.34.0 librtmp/2.3
Platform: Linux 4.18.0-2-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.62.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.0
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: gtk3

Story points: 6.0
Invalid wxPython version string passed to CMake find_package (lp:#1801109)

[Original report](https://bugs.launchpad.net/bugs/1801109) created by **Stefan Hamminga (stefanhamminga)**
```
CMake reports this error:

-- KiCad install dir: </usr>
-- Check for installed GLEW -- found
-- Boost version: 1.68.0
-- Check for installed Python Interpreter -- found
-- Python module install path: lib/python2.7/site-packages
-- wxPython/Phoenix version 4.0.0b1/gtk2 found.
CMake Error at CMakeLists.txt:822 (find_package):
  find_package called with invalid argument "4.0.0b1"


CMake Error at CMakeLists.txt:825 (include):
  include called with wrong number of arguments.  include() only takes one
  file.


-- S3DSG version: 2.0.0
-- Boost version: 1.68.0
-- Found the following Boost libraries:
--   unit_test_framework
-- Boost version: 1.68.0
-- Found the following Boost libraries:
--   unit_test_framework
-- Boost version: 1.68.0
-- Found the following Boost libraries:
--   unit_test_framework
-- Configuring incomplete, errors occurred!

This is caused by passing a version string into the CMake "find_package"
function not matching the required numerical format:
"[0-9]+(\.[0-9]+){0,3}".

Adding, at line 817 of CMakeLists.txt, a string filter will remove the
illegal characters from the version string:

string( REGEX MATCH "[0-9]+(\\.[0-9]+){0,3}" wxWidgets_REQ_VERSION
"${wxWidgets_REQ_VERSION}" )

But the real problem is how that "b1" suffix ended up in the requested
version in the first place, of course.
```

Story points: 6.0
Special point highlight/snap doesn't work with a selected item (lp:#1801089)

[Original report](https://bugs.launchpad.net/bugs/1801089) created by **eelik (eelik)**
```
Nowadays there's the feature with which certain special points, endpoints
or center points, are highlighted and the cursor is snapped to them. I
tried to use the Measure tool but noticed that if a footprint is selected,
that feature doesn't work. Points in other footprints work, but not in the
selected footprint.

By the way, what's the name of that feature and those special points?
```
Original tags: pcbnew

Story points: 6.0
V6 r11680 Footprint library huge issue (lp:#1801080)

[Original report](https://bugs.launchpad.net/bugs/1801080) created by **Sebastian Kulik (sebastiankulik1)**
```
Hi guys,
trying to make new footprint KiCad first hangs on, than quit.
Win10-Prox64 (newest, updated)......
Any ideas?
Cheers,
Seb
```
Original tags: pcbnew

Story points: 6.0
Image export in symbol editor broken, add to footprint editor (lp:#1801058)

[Original report](https://bugs.launchpad.net/bugs/1801058) created by **Thomas Pointhuber (pointhi)**
```
# HowTo reproduce

1. Symbol Editor -> File -> Export PNG...

No image is exported

Export PNG/SVG should be added to the Footprint Editor as well, because
this is a standard action when submitting a footprint to the official
library. It would be nice to have those shortcuts for eeschema/pcbnew as
well.

# Version Information

Application: kicad
Version: (6.0.0-rc1-dev-1108-g8be3471ba), debug build
Libraries:
    wxWidgets 3.1.1
    libcurl/7.61.1 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.34.0
Platform: Linux 4.18.16-arch1-1-ARCH x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.1.1 (wchar_t,wx containers) GTK+ 2.24
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: Clang 7.0.0 with C++ ABI 1002

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema

Story points: 6.0
Pcbnew: net names not shown unless very zoomed in or footprint selected (lp:#1801056)

[Original report](https://bugs.launchpad.net/bugs/1801056) created by **John Beard (john-j-beard)**
```
On latest master, net names are not shown on the traces or pads unless very
zoomed in or the footprint/trace is selected.

-----

Application: pcbnew
Version: (6.0.0-rc1-dev-1108-g8be3471ba), debug build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.34.0
Platform: Linux 4.18.16-arch1-1-ARCH x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.1 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: gal pcbnew

Story points: 14.0
User-defined "favourite" zoom regions (lp:#1800870)

[Original report](https://bugs.launchpad.net/bugs/1800870) created by **John Beard (john-j-beard)**
```
Often when designing a board, it's useful to be able to flip back and forth
between different regions of the board. For a simple example, the "PSU" and
the "MCU". Currently to do this, you need to either zoom out/press Home,
maybe flip, and then rezoom on the desired area, or use "Find" to warp to a
component you know is in the area.

It would be good if you could define a list of "favourite" regions of the
board (defined by a region of the board to fit on the screen and a flip/no
flip boolean). Then you can zoom to those areas with a set of hotkeys.

The same can apply to schematics (without the flip), though there is
already a sheet-change dialog.

This would need a file format change as you need to be able to store these
regions in the PCB file.
```
Original tags: feature.request pcbnew

Story points: 6.0
Cannot drag text in eeschema (lp:#1800845)

[Original report](https://bugs.launchpad.net/bugs/1800845) created by **John Beard (john-j-beard)**
```
In the current master, it's impossible to drag text in the schematic.

This makes sense in a way, as text is not connected, but it feels a bit
inconsistent when dragging other items - unconnected "connectables" act
like they are being moved in this case.

This patch does the same for text.

This also stops blocks that contain text from "leaving behind" the text
when a block drag is performed.
```
Original tags: eeschema

Story points: 6.0
Ctrl-number not allowed in Hotkey Editor on Windows (lp:#1800720)

[Original report](https://bugs.launchpad.net/bugs/1800720) created by **Morgan Feldon (feldon30)**
```
The Hotkey Editor in PCBNew on KiCad 5.0 release version running on Windows
10 will not accept certain characters with the Ctrl modifier. The following
keys cannot be assigned in the Hotkey Editor: Ctrl-0, Ctrl-1, Ctrl-2
through Ctrl-9, Ctrl-`, Ctrl-., Ctrl-\, etc.. They can be assigned only
through exporting the hotkey file and editing it manually and then
importing the changed file.
```
Original tags: hotkeys ui windows

Story points: 10.0
Symbol Library Editor: Weird behavior of pin length field (lp:#1800718)

[Original report](https://bugs.launchpad.net/bugs/1800718) created by **Fabián Inostroza (fabianinostroza)**
```
Selecting the first digit of the pin length in the library editor and
pressing a number in the keyboard causes the removal of one of the digits.
Removing the first digit using the backspace or supr key replaces the field
with the value "0".

Also if you remove any other digit the caret cursor is moved to the start.

See the attached video.

Application: kicad
Version: (6.0.0-rc1-dev-1063-g7b1049025), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.0 GnuTLS/3.5.19 zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.34.0 librtmp/2.3
Platform: Linux 4.18.0-2-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.0
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=OFF
```

Story points: 6.0
Cancelling a dialog should be allowed even when value is not allowed (lp:#1800711)

[Original report](https://bugs.launchpad.net/bugs/1800711) created by **eelik (eelik)**
```
Some dialogs check that a value is within bounds and give warning dialog,
like:

"Warning
Via diameter must be larger than 0,001 mm or equal."

It's not possible to cancel that kind of dialog without first giving some
valid value, which may be tedious if for example the value was changed by
accident. This can happen with several dialogs, for example with Pad
clearance value. I can't find them all, I hope there's some automatic way
to find them all or to fix them centralized.
```

Story points: 6.0
Scrollbars don't work in eeschema nightly build (lp:#1800647)

[Original report](https://bugs.launchpad.net/bugs/1800647) created by **Ron Burkey (rburkey)**
```
Several weeks ago (I'm not sure when, because I update from the nightly
build almost every day), scrollbars stopped working in the eeschema nightly
build running on Linux Mint.  For example, today I have version listed
below my sig.

The symptom is that the scrollbars still appear at the right-hand side and
bottom, but you can't use them to pan the drawing.  You can still use the
F4 hotkey to pan.

--Ron

Application: kicad
Version: 6.0.0-rc1-unknown-eabae68~66~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.11 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-53-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: eeschema

Story points: 6.0
Kicad cannot start due to missing file (lp:#1800560)

[Original report](https://bugs.launchpad.net/bugs/1800560) created by **swulf (swulf)**
```
On attempting to start Kicad following an installation of Windows Nightly
kicad-r11665.eabae68ab-x86_64.exe a dialog box appears with the message:

'kicad.exe - System Error

The program can't start because libcrypto-1_1-x64.dll is missing from your
computer. Try reinstalling the program to fix this problem.'

Reinstalling the program had no effect.
```

Story points: 6.0
Footprint Editor status bar shows wrong layer for selected graphical lines (lp:#1800556)

[Original report](https://bugs.launchpad.net/bugs/1800556) created by **Seth Hillbrand (sethh)**
```
See attached image.  The F.Silk layer item is selected but the layer shown
is F.Cu.

Application: kicad
Version: (6.0.0-rc1-dev-1056-gc6a971d97), release build
Libraries:
    wxWidgets 3.0.4
Platform: Linux 4.9.0-8-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    OpenCASCADE Community Edition: 6.8.0
    Compiler: GCC 6.3.0 with C++ ABI 1010

Build settings:
    USE_WX_GRAPHICS_CONTEXT=ON
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=OFF
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```

Story points: 6.0