Is this EFL 1.7.5 & E 0.17.1 or EFL trunk & E18?
does this also happen with E apart from terminology?
do you have curl 7.29?
if the last 2 are a yes then it is most likely a known upstream curl
issue (which is by now fixed in their repos and either needs
backporting or a whole new release for the
On Tue, Feb 12, 2013 at 10:38 AM, wrote:
> Terminology keeps giving this error when I close it:
>
> ichi@go ~ $ cat Terminology.log
> Error Signal Information:
> terminology was interrupted by a Segmentation Fault.
>
> Output Data:
> There was no output
>
> Error Logs:
> There was no error mes
On Mon, 11 Feb 2013 20:38:53 -0500 ich...@amuro.net said:
> Terminology keeps giving this error when I close it:
>
> ichi@go ~ $ cat Terminology.log
> Error Signal Information:
> terminology was interrupted by a Segmentation Fault.
>
> Output Data:
> There was no output
>
> Error Logs:
> The
Terminology keeps giving this error when I close it:
ichi@go ~ $ cat Terminology.log
Error Signal Information:
terminology was interrupted by a Segmentation Fault.
Output Data:
There was no output
Error Logs:
There was no error message
Pretty descriptive isn't it?
--
