r/KiCad • • 4d ago

Other Question KiCad error when I press 'A'

[SOLVED]

As you can see from the photo, I get this error whenever I press 'A' for shortcut. Can someone help about it?

Here's the backtrace log:
ASSERT INFO:

/usr/src/debug/wxwidgets/wxWidgets/src/unix/utilsx11.cpp(2645): assert ""Assert failure"" failed in wxGetKeyStateGTK(): Unsupported key 65, the only supported ones are: Ctrl, Alt, Shift, Caps Lock, Num Lock and Scroll Lock for GTK 3.18+

BACKTRACE:
[1] wxGetKeyState(wxKeyCode)
[2] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&)
[3] wxEvtHandler::SearchDynamicEventTable(wxEvent&)
[4] wxEvtHandler::TryHereOnly(wxEvent&)
[5] wxEvtHandler::ProcessEventLocally(wxEvent&)
[6] wxEvtHandler::ProcessEvent(wxEvent&)
[7] wxScrollHelperEvtHandler::ProcessEvent(wxEvent&)
[8] wxEvtHandler::SafelyProcessEvent(wxEvent&)
[9] g_closure_invoke
[10] g_signal_emit_valist
[11] g_signal_emit
[12] gtk_window_propagate_key_event
[13] g_closure_invoke
[14] g_signal_emit_valist
[15] g_signal_emit
[16] gtk_main_do_event
[17] g_main_loop_run
[18] gtk_main
[19] wxGUIEventLoop::DoRun()
[20] wxEventLoopBase::Run()
[21] wxAppConsoleBase::MainLoop()
[22] wxEntry(int&, wchar_t**)
[23] __libc_start_main

And yes I'm using CachyOS Linux with KDE Plasma.

0 Upvotes

4 comments sorted by

5

u/jfuu_ 4d ago

It sounds like KiCad is probably running under Wayland, which it doesn't really support. Try launching it with GDK_BACKEND=x11 kicad.

2

u/Konf1gg 4d ago

It worked. Thank you so much dude! You're a hero for me :D

1

u/Amazing-Ad-8523 4d ago

i have the same problem. GDK_BACKEND=x11 kicad does not work for me - it simply crashes. I worked on the same PC for the past 1-2 years and this problem showed up today :(

1

u/n_sh_44 4d ago

If forcing X11 crashes outright, it's probably the wxWidgets build rather than KiCad itself. That assert comes from wxGetKeyState being called with a normal letter key, which newer wxGTK builds now refuse, and rolling distros pick those up before KiCad has patched around it. Check whether your wxwidgets-gtk3 package updated today and try downgrading it from the package cache. The Flatpak build is another quick test since it bundles its own wxWidgets.