Known System Related Issues
This page contains a number of known KiCad issues that are specific to a certain platform or hardware configuration.
Linux Specific Issues
Wayland
KiCad does not support Wayland.
|
People using Wayland with KiCad will experience crashes, slow performance, and other issues that cannot be addressed by the KiCad project. These issues do not exist when using the X11 window system. |
Issues or bugs encountered while using Wayland or the XWayland compatibility layer must be reproduced under X11 before they will be addressed by KiCad. Bugs that cannot be reproduced on X11 should be reported to the Wayland bug tracker.
MATE
Some versions of MATE (on Ubuntu or Linux Mint) together with GTK3 and wxWidgets can lead to rendering problems and keyboard keys that do not work or can freeze the GUI input. They are potentially caused by the ibus. To solve it, install the packages ibus-gtk and ibus-gtk3, and restart the computer (or log out).
Alternatively, you can quit the ibus calling in a terminal 'ibus exit' before starting KiCad. More details can be found in GitLab Bug# 4547.
Windows Specific Issues
Graphical Artifacts with Intel GPUs
Users with Intel integrated GPUs running outdated drivers may experience graphical artifacts (usually horizontal lines) covering the editing canvases. These artifacts are caused by bugs in the graphics driver. To solve this issue, update to the latest version of the Intel graphics driver for your system. Note that you may need to manually download and install an updated driver on some systems; Windows Update does not always have a driver version new enough to resolve this issue.
Network Shares
Editing projects located on Windows networks shares provided by samba servers (non-Windows Server, i.e. Synology, FreeNAS) may result in crashes due to samba generating bad file change events and our cross-platform toolkit asserting the invalid event rather than ignoring it. Windows Server hosted shares should not encounter this issue.
You will have to work on a local drive if you encounter crashes working from a network drive for now. More details can be found in GitLab Bug #5740.
Maximum Path Length Limitation
Prior to and including Windows 10 build 1607, the maximum path length was limited to 260 characters. This would cause problems primarily when creating project back up archives when saving schematic and board files. As of KiCad version 8.0.8, a path length fix was introduced that resolves the issue when creating project back up archives. If you are still having issues saving other files due to path length issues, see the Microsoft help on how to enable long paths.