I have been using codeblocks successfully for several years, running codeblocks 20.something on a Raspberry Pi running Linux Bookworm. I would connect to it using ssh -Y pi@192.168.1.whatever from a big-screen Apple Mac and then launch codeblocks. The C::B windows would appear on the Mac as XQuartz windows and all would be well.
Raspberry Pi has now been upgraded to Linux Trixie, and the version of codeblocks installed by sudo apt install codeblocks is 25.03. Trixie defaults to Wayland, so the command-line I now need to use is GDK_BACKEND=x11 codeblocks &
This largely works, but one strange thing is that when I type 8 or shifted-8 (which should give me *) into a codeblocks source-code editor window, instead it is as if I had typed a carriage-return. But I do get 8 or * if I type it into e.g. the file-browser or the find dialog box. Or the xterm command prompt. Also if I type 8 or * on the numeric keypad, this does work under all circumstances. (I have not checked every key to know if there are any more funny key mappings).
Now there's a lot of things that I do this then that then the other. So I don't know if this is a problem inside codeblocks (although the fact that it behaves normally in a find window inside codeblocks might suggest so). And it might relate to my particular locale or keyboard mapping (UK English i.e. en-gb)
Are there any diagnostics I might do to e.g. find out what key-code is being received by codeblocks to tell if it is an error inside codeblocks (i.e. a bug that should be reported to you) or one that should be reported elsewhere. So far no-one on the Raspberry-Pi forum has taken it up. (They did tell me how to select X11 rather than Wayland; without which the Codeblocks windows would appear on my small R-Pi screen, not what I want).
