This is a continuation of my previous topic "Codeblocks over ssh -Y with Trixie"
I have tried a pi4 and pi5 running Trixie.
Previously with bookworm I could ssh -Y from my big-screen Apple Mac onto them, and run codeblocks as an ide for c++. The codeblocks windows would appear on the Mac.
With Trixie, the first problem I hit was that the codeblocks windows would not appear. thagrol helpfully suggested that I switch from Wayland to X11 and that fixed that problem.
My new problem is that when I type "8" or "*" (i.e. shifted-8) in a codeblocks source-code editor window, instead a carriage-return happens.
This doesn't happen on the first command-window, nor within any xterms I open from that command-window, nor within dialog-boxes inside codeblocks. So the 8 keypress is correctly getting through to codeblocks.
Things that do work are:
Typing 8 or * on the numeric keypad.
Running codeblocks directly on the pi (not convenient as I don't have a big screen I can plug that into).
When I used to run codeblocks (20.0.x I think) on bookworm
This happens with new projects on a fresh install of Codeblocks as well as my existing big project.
Codeblocks is 25.03-r13644
Trixie version from uname -a is
Linux RobinPi5 6.12.47+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 (2025-09-16) aarch64 GNU/Linux
I haven't exhaustively tested every key on the keyboard, so there might be other keys that don't map properly.
I imagine there won't be much effort to fix this, given that we're encouraged to go to Raspberry Pi Connect. And I don't know where the problem is, whether it's inside codeblocks or in one of the layers that are under the control of Raspberry Pi. Nor whether a fix can be applied at a different layer.
How might I diagnose / fix this?
I have tried a pi4 and pi5 running Trixie.
Previously with bookworm I could ssh -Y from my big-screen Apple Mac onto them, and run codeblocks as an ide for c++. The codeblocks windows would appear on the Mac.
With Trixie, the first problem I hit was that the codeblocks windows would not appear. thagrol helpfully suggested that I switch from Wayland to X11 and that fixed that problem.
My new problem is that when I type "8" or "*" (i.e. shifted-8) in a codeblocks source-code editor window, instead a carriage-return happens.
This doesn't happen on the first command-window, nor within any xterms I open from that command-window, nor within dialog-boxes inside codeblocks. So the 8 keypress is correctly getting through to codeblocks.
Things that do work are:
Typing 8 or * on the numeric keypad.
Running codeblocks directly on the pi (not convenient as I don't have a big screen I can plug that into).
When I used to run codeblocks (20.0.x I think) on bookworm
This happens with new projects on a fresh install of Codeblocks as well as my existing big project.
Codeblocks is 25.03-r13644
Trixie version from uname -a is
Linux RobinPi5 6.12.47+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 (2025-09-16) aarch64 GNU/Linux
I haven't exhaustively tested every key on the keyboard, so there might be other keys that don't map properly.
I imagine there won't be much effort to fix this, given that we're encouraged to go to Raspberry Pi Connect. And I don't know where the problem is, whether it's inside codeblocks or in one of the layers that are under the control of Raspberry Pi. Nor whether a fix can be applied at a different layer.
How might I diagnose / fix this?
Statistics: Posted by ClassicRover — Fri Dec 26, 2025 12:01 pm — Replies 1 — Views 31