Ubuntu 25.10 / Wayland / KiCad 9.0.5

Software
1

image
image1797Ɨ1000 191 KB

There are graphical issues.
1: please notice how resizing the window does not resize the contents.

2: I cannot click/edit any of the numeric values of the pad

I have also tried to use : flatpak run --env=GDK_BACKEND=x11 org.kicad.KiCad to run it, the issues vary, not always reproducible at first time, but they are there.

2
  1. Which GPU model?
  2. Which GPU driver?
  3. Does it work when using llvmpipe (software) mesa driver?
  4. Wayland is not officially supported by KiCad (it might be better to ask on Ubuntu/GNOME forums)
1 Like
3

1:Intel UHD Graphics 630 (CFL GT2)

2: i915

$ sudo lshw -c video
[sudo: authenticate] Password:
*-display
description: VGA compatible controller
product: CoffeeLake-S GT2 [UHD Graphics 630]
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
logical name: /dev/fb0
version: 02
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
configuration: depth=32 driver=i915 latency=0 resolution=2560,1440
resources: irq:156 memory:90000000-90ffffff memory:80000000-8fffffff ioport:4000(size=64) memory:c0000-dffff

3: thank you, on this computer, using flatpak run --env=LIBGL_ALWAYS_SOFTWARE=1 --env=MESA_LOADER_DRIVER_OVERRIDE=llvmpipe org.kicad.KiCad seems to make everything work fine.

4

You may try reporting this to Mesa then first:

5

Can you also open any editor, then share the full version info from Help ā†’ About KiCad when running normally (using the Intel GPU)?

6

Please note that running in software mode does not fix everything, I can get some ghosting around windows, footprints may not be grabbable unless I close/open PCB editor, and menus disappeared, some items cannot be clicked etc. I plan to get Nvidia GPU on the workstation (as home, where everything works fine)

Application: KiCad Schematic Editor x86_64 on x86_64

Version: 9.0.5, release build

Libraries:
wxWidgets 3.2.8
FreeType 2.14.1
HarfBuzz 11.4.5
FontConfig 2.17.1
libcurl/8.15.0 OpenSSL/3.5.3 zlib/1.3.1 zstd/1.5.7 libidn2/2.3.8 libpsl/0.21.5 nghttp2/1.66.0

Platform: Freedesktop SDK 25.08 (Flatpak runtime), 64 bit, Little endian, wxGTK, X11, ubuntu, wayland
OpenGL: Intel, Mesa Intel(R) UHD Graphics 630 (CFL GT2), 4.6 (Compatibility Profile) Mesa 25.2.2 (git-22ded5f256)

Build Info:
Date: Nov 11 2011 11:11:11
wxWidgets: 3.2.8 (wchar_t,wx containers) GTK+ 3.24
Boost: 1.89.0
OCC: 7.9.1
Curl: 8.15.0
ngspice: 45.2
Compiler: GCC 15.2.0 with C++ ABI 1020
KICAD_IPC_API=ON

Locale:
Lang: en_US
Enc: UTF-8
Num: 1,234.5
Encoded ŠŗĪ©äøˆ: D0BACEA9E4B888 (sys), D0BACEA9E4B888 (utf8)

7

You may try asking on Ubuntu/GNOME forums then.

1 Like
8

I just discovered that this happens as well on Nvidia :

$ sudo lshw -c video
[sudo: authenticate] Password: 
  *-display                 
       description: VGA compatible controller
       product: AD102 [GeForce RTX 4070 Ti SUPER]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: /dev/fb0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom fb
       configuration: depth=32 driver=nvidia latency=0 mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080
       resources: iomemory:400-3ff iomemory:400-3ff irq:159 memory:90000000-90ffffff memory:4000000000-400fffffff memory:4010000000-4011ffffff ioport:3000(size=128) memory:c0000-dffff

and the environment variable fixes it, kind of, for a short while

GDK_BACKEND=x11 kicad

9

Please note this super-strange behaviour:
I can open and close the About window, or just interact with it - but at some point (0:57) in this video, you can see all tabs unresponsive and ā€œdisabledā€ they are not responding to mouseover, and do ot respond to clicks - but then I move mouse down to the text area, and scroll! - then the last clicked tab may work.

I do not longer believe this is related to the X11 variable.

10

Same issue on my end. The issue seems to be linked to capturing the mouse input. I have a similar issue in PCB Editor and during Schematic entry. After some time, mouse inputs just stop working. It seems that at some point the mouse events (e.g. movement) stops working. i.e. the crosshair is not following the mouse anymore. Also selecting things doesnt work (e.g. click, then drag an area, then let go).

11

I am aware of mouse button gremlinsā€¦ I was close to buy a new mouse due to that :woozy_face:, but it disappeared ! If the button stops to work as expected, then it is not related to KiCad. But I donā€™t know the guilty.

For Wayland, you must provide the compositor (Gnome, KDE). X11, Wayland, and kernel have tools to debug/log inputs.

12

Running on a stock Ubuntu 25.10 with Gnome. At the end of the post you can find the version string from the About dialog. Next to mouse issues, there is also a rendering problem as pointed out earlier. At some point the redraw/update of widgets and canvases doesnt work anymore. This also happens with standard wxWidgets widgets, i.e. in the project manager. When it is in that state, you can still interact with Widgets as also described earlier. I.e. in the about dialog you can clock buttons but the GUI simply doesnt render the resulting appearance.

Application: KiCad x86_64 on x86_64
Version: 9.0.6-rc2-202510282351~1b20a932ad~ubuntu25.10.1, release build
Libraries:
    wxWidgets 3.2.8
    FreeType 2.13.3
    HarfBuzz 10.2.0
    FontConfig 2.15.0
    libcurl/8.14.1 OpenSSL/3.5.3 zlib/1.3.1 brotli/1.1.0 zstd/1.5.7 libidn2/2.3.8 libpsl/0.21.2 libssh2/1.11.1 nghttp2/1.64.0 librtmp/2.3 OpenLDAP/2.6.10
Platform: Ubuntu 25.10, 64 bit, Little endian, wxGTK, X11, ubuntu, wayland
Build Info:
    Date: Oct 28 2025 23:51:50
    wxWidgets: 3.2.8 (wchar_t,wx containers) GTK+ 3.24
    Boost: 1.88.0
    OCC: 7.8.1
    Curl: 8.14.1
    ngspice: 44.2
    Compiler: GCC 15.2.0 with C++ ABI 1020
    KICAD_IPC_API=ON
Locale: 
    Lang: en_US
    Enc: UTF-8
    Num: 1,234.5
    Encoded ŠŗĪ©äøˆ: D0BACEA9E4B888 (sys), D0BACEA9E4B888 (utf8)

i have investigated this further and this is a wxWidgets issue in the wxAui part. If you install wxWidgets 3.28 and build an AUI example, i.e. as from the website below, it shows the exat same issue. A basline wxWidgets app without AUI doesnt seem to have the problem

13

I now see that PrusaSlicer ā€˜s Preferences menu has the same issue. For all other applications I tried, this works fine. It could be that this is something that KiCad and PrusaSlicer does something differently that triggers this bug. (not necessarily that the bug is in those two applications)

14

This is liked to wxAui. Apps that donā€™t use wxAui donā€™t show the issue

15

Actually, it is mandatory to describe the full stack. For example, you have a GTK version that implement a Wayland protocol v1 and KDE is already implementing v2 thus it cannot workā€¦ And the bug happens because you are using a different setup that the one used by the developer.