There was a weird bug when Trisquel 5.5 was released and, as far as I remember, this was provoking this exact error when Synaptic was executed. The fix was to disable (and then re-enable?) the visual alerts in the accessibility menu.

Reply via email to