Onboard

onboard crashes on launch - raspberry pi

Asked by Tom Russell

I am running Raspberry Pi 4 on Bullseye and OS is up to date. I installed onboard using sudo apt install onboard. During the install, I get:
Setting up onboard (1.4.1-5) ...
Installing new version of config file /etc/xdg/autostart/onboard-autostart.desktop ...
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
  raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \

When I try to run onboard it will not start. Launching from the command line I get:

(onboard:1323): dbind-WARNING **: 12:55:11.841: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files

(onboard:1323): dbind-ERROR **: 12:55:11.841: AT-SPI: Couldn't connect to accessibility bus. Is at-spi-bus-launcher running?
Trace/breakpoint trap

I have been able to run onboard under Buster.

Any help would be very appreciated.

Thanks

Question information

Language:
English Edit question
Status:
Expired
For:
Onboard Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Tom Russell (tcr000) said : 		#1

A bit more info:
After a fresh install of either Buster or Bullseye, Onboard will start normally but crashes as soon as I select the option to start automatically when editing a field. When you click that choice it asks about enabling accessibility and when I check that it immediately crashes (window disappears) and from then on will not boot, even if I uninstall and re-install it. Looks like it is enabling or installing some other package incorrectly and when I uninstall onboard, I am not restoring whatever it just did. I don't know why it is working on my other Buster image, perhaps I had already installed some package it needed without knowing it.

Thanks,
Tom

Revision history for this message
Tom Russell (tcr000) said : 		#2

I installed at-spi2.core and this keeps it from crashing although I get a WARNING and a CRITICAL message on launching from the console.

19:23:06.678 WARNING HardwareSensorTracker: Failed to connect to acpid, SW_TABLET_MODE detection disabled. ('/var/run/acpid.socket': [Errno 2] No such file or directory)

(onboard:9277): Gdk-CRITICAL **: 19:23:07.341: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed

Revision history for this message
Launchpad Janitor (janitor) said : 		#3

This question was expired because it remained in the 'Open' state without activity for the last 15 days.