Re: [Pan-users] segmentation fault trying to use Pan 0.146:will abandon using pan

[Steve Davies]

In case it helps, the Win64 build requires the following patch:

in pan/general/e-util.cc, around line 210

 EvolutionDateMaker :: EvolutionDateMaker (time_t now)
 {
   // build the locale strings
-  locale_recent = g_locale_from_utf8 (_("%l∶%M %p"), -1, NULL, NULL, NULL);
-  locale_today = g_locale_from_utf8 (_("Today %l∶%M %p"), -1, NULL, NULL, NULL);
-  locale_this_week = g_locale_from_utf8 (_("%a %l∶%M %p"), -1, NULL, NULL, NULL);
-  locale_this_year = g_locale_from_utf8 (_("%b %d %l∶%M %p"), -1, NULL, NULL, NULL);
+  locale_recent = g_locale_from_utf8 (_("%l:%M %p"), -1, NULL, NULL, NULL);
+  locale_today = g_locale_from_utf8 (_("Today %l:%M %p"), -1, NULL, NULL, NULL);
+  locale_this_week = g_locale_from_utf8 (_("%a %l:%M %p"), -1, NULL, NULL, NULL);
+  locale_this_year = g_locale_from_utf8 (_("%b %d %l:%M %p"), -1, NULL, NULL, NULL);
   locale_old = g_locale_from_utf8 (_("%b %d %Y"), -1, NULL, NULL, NULL);
 
   // set the current time

Basically, the 4 lines above contain a "non-space" "space" character, or it might be the ':' character - I don't remember, which the patch replaces with a normal character.

I had presumed that this was a Win64-only patch and was in no hurry to submit a patch which might break normal Pan operation.

Cheers,

Steve

On Sun, 1 Dec 2019 at 21:06, Per Hedeland <address@hidden> wrote:

On 2019-12-01 18:25, Julien Michielsen wrote:
> Rhialto schreef op 01-12-2019 16:02:
>> On Sun 01 Dec 2019 at 15:46:41 +0100, Julien Michielsen wrote:
>>> my locale, would anyone be able to see something that is not accepted
>>> by pan?
>>>
>>> LANG=nl_NL.UTF-8@euro
>>> LANGUAGE=
>>> LC_CTYPE="C"
>>> LC_NUMERIC="C"
>>> LC_TIME="C"
>>> LC_COLLATE="C"
>>> LC_MONETARY="C"
>>> LC_MESSAGES="C"
>>> LC_PAPER="C"
>>> LC_NAME="C"
>>> LC_ADDRESS="C"
>>> LC_TELEPHONE="C"
>>> LC_MEASUREMENT="C"
>>> LC_IDENTIFICATION="C"
>>> LC_ALL=C
>>
>> Looks very much like https://gitlab.gnome.org/GNOME/pan/issues/1 .
>> I'm pretty sure I had a similar bug report but I can't find it right
>> now.
>>
>> -Olaf.
>
> Unfortunately I don't know (and understand) usage of the local variables
> well enough to adjust them to the set pan accepts.

Did you try my suggestions in a previous message:

>>> You could try starting Pan with
>>>
>>> env LANG=C pan
>>>
>>> and see if it helps. If not, try also 'unset LANGUAGE' (assuming
>>> sh-style shell) before that.

> But for years I used my computer without problems, and I'll continue to
> do so, but like all these years without pan.  If it is so hard to use it,
> I'll live without it.

Well, although it isn't a lot of help for you, I would say that it
isn't really Pan as such that causes this problem, but rather a Gnome
"rule" in combination with a bug in a library used by Pan.

Worst case, since you already built Pan from source, you could try
changing those non-ascii colons in pan/general/e-util.cc to proper
ascii ones and rebuild.

--Per

_______________________________________________
Pan-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/pan-users