Onboard bug, or just me?
Does anyone have any problems with the onboard program when a mouse curser goes over to click the keyboard or just goes over it than the program crashes or shuts down?
I tried starting it with the command line after I tested the launcher and it showed
Segmentation fault
when I tried to go over it, so I do not know if that is because of a missing config file, something in the program, something in a library, or something else.
I do not need the program, I was just testing it to see how an onscreen keyboard could be used with a mouse.
I'm using the mate desktop at this time, I do not know if that affects anything.
This looks similar: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/2063041.
Trisquel 12 is based on Ubuntu 24.04, so it is probably using the same version of Onboard.
Please open an issue to do proper follow up.
I noticed something similar on Trisquel 12, but I have not gotten around to opening an issue about it. The onboard seems to crash immediately. Pretty surprising to me that the bug seems to be unfixed for years in Ubuntu, assuming I am reading the bug page correctly. Actually, I'm surprised the bug is affecting more than just me; my first guess was that it had something to do with my particular PC or particular setup (live boot + persistence). I shouldn't really be that surprised, but I would have expected an issue that completely prevents a program from working to be fixed pretty quickly.
Given a lack of people who use this feature and would report that it broke, it would probably be good to have some sort of testing list with all the things to test before a Trisquel release. Maybe something like that already exists, but there's so many things that one could test.
https://cdimage.trisquel.info/trisquel-images/trisquel_11.0.1_sources.tar.torrent
has all sources and dpkg --list can help you see what programs are on your system so you can see a list what is on a system, though maybe not all build dependencies.
Maybe testing the programs that have a menu launcher, than command line programs, than other things may help.
There are a lot of programs in the Trisquel 12 release, though maybe in another form post the users of this forum can make suggestions about what should be tested next, and what iso image should be used to test those programs.
I think before a release is made there may be testing images also.
https://cdimage.trisquel.info/trisquel-images/trisquel_12.0_sources.tar.torrent
for Trisquel 12 sources.
https://gitlab.trisquel.org/explore
can help show things for testing.
I too can confirm that onboard crashes on Trisquel 12, and that there is a workaround: run onboard-settings in a terminal and select GTK instead of Xinput, as suggested in https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/2063041/comments/12.
Thank you for the help everyone.
An issue is now at
https://gitlab.trisquel.org/trisquel/package-helpers/-/issues/280
The main menu also has the System menu, than the Preferences menu, than the Personel menu, than Onboard settings. This way the onboard settings can be changed with a mouse.
The issue is already fixed!
Thank you Ark74.