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.
- [Trisquel-users] synaptic troubles donh824
- [Trisquel-users] Re : synaptic troubles magicbanana
- Re: [Trisquel-users] synaptic troubles lutheroto
- Re: [Trisquel-users] synaptic troubles liuyazhen_1987
- Re: [Trisquel-users] synaptic troubles nasrullah1983
- [Trisquel-users] Re : synaptic troubles magicbanana
- Re: [Trisquel-users] synaptic troubles nasrullah1983
- Re: [Trisquel-users] synaptic troubles lutheroto
- Re: [Trisquel-users] synaptic troubles janeandreas
