Re: abiword segfaults immediately

2020-12-14 Thread George Koehler
On Tue, 15 Dec 2020 01:15:35 +
James Cook  wrote:

> FYI I tried setting LC_CTYPE to a supported value (en_US.UTF-8) while
> keeping LANG at the unsupported en_CA.UTF-8 but that wasn't enough.
> 
> Admittedly I had read that FAQ entry and ignored the recommendation,
> based on some wishful thinking. Now I will take it more seriously.

The FAQ [1] recommends en_US.UTF-8, but en_CA.UTF-8 should also work,
because man locale [2] says,

| If the value of LC_CTYPE ends in ‘.UTF-8’, programs in the OpenBSD
| base system ignore the beginning of it, treating for example
| zh_CN.UTF-8 exactly like en_US.UTF-8.

I don't know why en_CA.UTF-8 would crash abiword; I wonder if abiword
is confused because en_CA.UTF-8 and en_US.UTF-8 are not really
different locales in OpenBSD's libc.--George

[1] https://www.openbsd.org/faq/faq8.html#locales
[2] https://man.openbsd.org/man1/locale.1



Re: abiword segfaults immediately

2020-12-14 Thread James Cook
Thanks, Ed.

I just emailed the port maintainer separately to ask if they have any
ideas. I think it would be better if abiword didn't crash even if the
locale is unsupported.

FYI I tried setting LC_CTYPE to a supported value (en_US.UTF-8) while
keeping LANG at the unsupported en_CA.UTF-8 but that wasn't enough.

Admittedly I had read that FAQ entry and ignored the recommendation,
based on some wishful thinking. Now I will take it more seriously.

Off-topic: I'm curious if there's a clean way to convey my language
preference to software from ports, or I should just accept that en_US
is going to be my default. Not a big deal for en_CA, but what do
French/Japanese/etc speakers do?

On Mon, Dec 14, 2020 at 02:36:57PM +, Ed Gray wrote:
> Hi James,
> 
> I've noticed that in openbsd utf-8 is not universally supported like on
> other open source systems.
> 
> As far as I know you have to use en_US.UTF-8 or C for LC_CTYPE and I'm not
> sure if the LANG environment variable is used either.
> 
> Whether it should segfault in this case I don't know.
> 
> Perhaps once you are running abiword it will have its own native language
> support for documents and you won't need to set the LANG variable?
> 
> See this FAQ:
> 
> https://www.openbsd.org/faq/faq8.html
> 
> Regards
> Ed Gray
> 
> On Sun, 13 Dec 2020, 11:03 pm James Cook,  wrote:
> 
> > On Thu, Dec 03, 2020 at 04:48:04PM +, James Cook wrote:
> > > I just installed abiword and also just upgraded to the latest snapshot
> > > (and ran pkg_add -u). abiword immediately crashes when I run it. I have
> > > never tried running abiword on OpenBSD before. Is it broken for others
> > > or just for me?
> >
> > I just discovered it works if I set LANG to en_US.UTF-8 (in ksh,
> > LANG=en_US.UTF-8 abiword). Normally I have LANG set to en_CA.UTF-8.
> > Similar behaviour was reported in 2015:
> >
> > https://marc.info/?l=openbsd-ports=143301697319210=2
> >
> > This works as a workaround, but I wonder what the problem is.
> >
> > --
> > James

-- 
James



Re: abiword segfaults immediately

2020-12-14 Thread Ed Gray
Hi James,

I've noticed that in openbsd utf-8 is not universally supported like on
other open source systems.

As far as I know you have to use en_US.UTF-8 or C for LC_CTYPE and I'm not
sure if the LANG environment variable is used either.

Whether it should segfault in this case I don't know.

Perhaps once you are running abiword it will have its own native language
support for documents and you won't need to set the LANG variable?

See this FAQ:

https://www.openbsd.org/faq/faq8.html

Regards
Ed Gray

On Sun, 13 Dec 2020, 11:03 pm James Cook,  wrote:

> On Thu, Dec 03, 2020 at 04:48:04PM +, James Cook wrote:
> > I just installed abiword and also just upgraded to the latest snapshot
> > (and ran pkg_add -u). abiword immediately crashes when I run it. I have
> > never tried running abiword on OpenBSD before. Is it broken for others
> > or just for me?
>
> I just discovered it works if I set LANG to en_US.UTF-8 (in ksh,
> LANG=en_US.UTF-8 abiword). Normally I have LANG set to en_CA.UTF-8.
> Similar behaviour was reported in 2015:
>
> https://marc.info/?l=openbsd-ports=143301697319210=2
>
> This works as a workaround, but I wonder what the problem is.
>
> --
> James
>
>


Re: abiword segfaults immediately

2020-12-13 Thread James Cook
On Thu, Dec 03, 2020 at 04:48:04PM +, James Cook wrote:
> I just installed abiword and also just upgraded to the latest snapshot
> (and ran pkg_add -u). abiword immediately crashes when I run it. I have
> never tried running abiword on OpenBSD before. Is it broken for others
> or just for me?

I just discovered it works if I set LANG to en_US.UTF-8 (in ksh,
LANG=en_US.UTF-8 abiword). Normally I have LANG set to en_CA.UTF-8.
Similar behaviour was reported in 2015:

https://marc.info/?l=openbsd-ports=143301697319210=2

This works as a workaround, but I wonder what the problem is.

-- 
James



Re: abiword segfaults immediately

2020-12-03 Thread James Cook
On Thu, Dec 03, 2020 at 04:48:04PM +, James Cook wrote:
> I just installed abiword and also just upgraded to the latest snapshot
> (and ran pkg_add -u). abiword immediately crashes when I run it. I have
> never tried running abiword on OpenBSD before. Is it broken for others
> or just for me?

Sorry, should probably include uname:

falsifian angel ~ $ uname -a
OpenBSD angel.falsifian.org 6.8 GENERIC.MP#206 amd64

and here's dmesg output in case it's helpful.

OpenBSD 6.8-current (GENERIC.MP) #206: Wed Dec  2 17:47:17 MST 2020
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17161912320 (16366MB)
avail mem = 16626487296 (15856MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf0100 (59 entries)
bios0: vendor Award Software International, Inc. version "F7" date 11/20/2009
bios0: Gigabyte Technology Co., Ltd. GA-MA790XT-UD4P
acpi0 at bios0: ACPI 1.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT HPET MCFG TAMG APIC
acpi0: wakeup devices PCI0(S5) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) 
USB5(S3) USB6(S3) SBAZ(S4) P2P_(S5) PCE2(S4) PCE3(S4) PCE4(S4) PCE5(S4) 
PCE6(S4) PCE7(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpihpet0 at acpi0: 14318180 Hz
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Phenom(tm) II X3 710 Processor, 2612.29 MHz, 10-04-02
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 
16-way L2 cache, 6MB 64b/line 48-way L3 cache
cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative
cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative
cpu0: AMD erratum 721 detected and fixed
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 200MHz
cpu0: mwait min=64, max=64, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD Phenom(tm) II X3 710 Processor, 2611.92 MHz, 10-04-02
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC
cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 
16-way L2 cache, 6MB 64b/line 48-way L3 cache
cpu1: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative
cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative
cpu1: AMD erratum 721 detected and fixed
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: AMD Phenom(tm) II X3 710 Processor, 2611.93 MHz, 10-04-02
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC
cpu2: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 
16-way L2 cache, 6MB 64b/line 48-way L3 cache
cpu2: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative
cpu2: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative
cpu2: AMD erratum 721 detected and fixed
cpu2: smt 0, core 2, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins, remapped
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 4 (P2P_)
acpiprt2 at acpi0: bus 1 (PCE2)
acpiprt3 at acpi0: bus -1 (PCE3)
acpiprt4 at acpi0: bus 2 (PCE4)
acpiprt5 at acpi0: bus -1 (PCE5)
acpiprt6 at acpi0: bus -1 (PCE6)
acpiprt7 at acpi0: bus -1 (PCE7)
acpiprt8 at acpi0: bus -1 (PCE8)
acpiprt9 at acpi0: bus -1 (PCE9)
acpiprt10 at acpi0: bus 3 (PCEA)
acpiprt11 at acpi0: bus -1 (PCEB)
acpiprt12 at acpi0: bus -1 (PCEC)
acpibtn0 at acpi0: PWRB
acpipci0 at acpi0 PCI0
acpicmos0 at acpi0
"PNP0C14" at acpi0 not configured
acpicpu0 at acpi0: C1(@1 halt!), PSS
acpicpu1 at acpi0: C1(@1 halt!), PSS
acpicpu2 at acpi0: C1(@1 halt!), PSS
cpu0: 2612 MHz: speeds: 2600 1900 1400 800 MHz
pci0 at mainbus0 bus 0
0:0:0: mem address conflict 0xe000/0x2000
pchb0 at pci0 dev 0 function 0 "ATI RD780 HT-PCIE" rev 0x00
ppb0 at pci0 dev 2 function 0 "ATI RD790 PCIE" rev 0x00
pci1 at ppb0 bus 1
radeondrm0 at pci1 dev 0 function 0 "ATI Radeon HD 5450" rev 0x00
drm0 at radeondrm0
radeondrm0: msi
azalia0 at pci1 dev 0 function 1 "ATI Radeon HD 5470 Audio" rev 0x00: msi
azalia0: no supported codecs
ppb1 at pci0 dev 4 function 0 "ATI RD790 PCIE" rev 0x00
pci2 at ppb1 bus 2
jmb0 at pci2 dev 0 function 0 "JMicron JMB363