Re: Firefox extension broken in -current's v71.0

2019-12-26 Thread George Koehler
On Thu, 26 Dec 2019 19:58:31 -0600
myportslist20190...@nym.hush.com wrote:

> >Synopsis:"1Password X" extension on Firefox shows 0 passwords
> >When logging into the 1Password X extension, you'll see a brief flash
> > of your vault items (passwords), but after ~100ms they 
> >disappear and are replaced with the text "No items in this vault."
> 
> I had this problem until I changed /etc/login.conf default class to use
> datasize-max=7000M: and datasize-cur=7000M and rebooted. I have
> 8GB RAM and haven't tried lower values yet for datasize-max and -cur.
> 
> ...
> 
> If I go to about:debugging# and This Firefox and UBlock Origin, I
> see 
> "WebAssembly.Memory failed to reserve a large virtual memory region. 
> This may be due to low configured virtual memory limits on this system."

WebAssembly in Firefox is broken because it allocates too much memory.
A Reddit comment from /u/brynet [1] suggests to disable WebAssembly.
"You need to manually set `javascript.options.wasm;false` in Firefox
`about:config`."  I have never tried this and don't know whether it
would fix anything.

I run my amd64 desktop with datasize-cur=8G, though I have only 4G total
RAM.  (I'm in the staff class, says `userinfo kernigh`.)  This is enough
for Firefox to run some small WebAssembly demos [2], but doesn't fix
Twitch video.

[1] 
https://www.reddit.com/r/openbsd/comments/dlps5a/what_are_the_required_aboutconfig_settings_on/f4txe1c?utm_source=share_medium=web2x
[2] https://docs.assemblyscript.org/examples

-- George



Re: Firefox extension broken in -current's v71.0

2019-12-26 Thread myportslist20190323
>Synopsis:  "1Password X" extension on Firefox shows 0 passwords
>When logging into the 1Password X extension, you'll see a brief flash
> of your vault items (passwords), but after ~100ms they 
>disappear and are replaced with the text "No items in this vault."

I had this problem until I changed /etc/login.conf default class to use
datasize-max=7000M: and datasize-cur=7000M and rebooted. I have
8GB RAM and haven't tried lower values yet for datasize-max and -cur.

I am using only three extensions: 1Password X, Firefox Containers, and UBlock
Origin. For me, 1Password X will not work until I disable UBlock Origin and 
then 
restart Firefox. I then sign in to 1 Password X. At that point, I can 
re-enable UBlock Origin and everything works. 

The problem started with 1Password's new version 1.17.0. This workaround
does work on all my -current machines.

If I go to about:debugging# and This Firefox and UBlock Origin, I
see 
"WebAssembly.Memory failed to reserve a large virtual memory region. 
This may be due to low configured virtual memory limits on this system."

I don't know how to fix this, and my increased datasize-max and -cur don't
change this. But if UBlock Origin starts before 1Password X, my guess is 
that this memory error stops 1Password X from working.

As a side note, I have to start Firefox from the Downloads folder if I want
to be able to upload files from it.



Re: Compiling ncurses-6.1 on OpenBSD

2019-12-26 Thread Thomas Dickey
On Thu, Dec 26, 2019 at 01:13:11PM +, Stuart Henderson wrote:
> On 2019/12/25 16:23, Thomas Dickey wrote:
> > Since my message to bugs@openbsd.org was ignored,
> > I'll have to assume that they're not interested in discussing it,
> > and will keep in mind to document it as a pitfall in upcoming releases.
> 
> The toolchain isn't my area, but I suspect there's little enthusiasm
> for fixing a gcc-related problem especially one reported on amd64 - it's
> pretty much only still built there so that developers have an easy way
> to run it if they need to fix things in the base OS on the non-clang
> platforms which many developers don't have direct access to.
> 
> If the problem remains with /usr/bin/cc (which is clang on
> amd64/i386/arm/aarch64/mips64) then it would be useful to include the
> full steps to repeat the problem - the script is mentioned but not
> included in the bugs@openbsd.org mail.

I took a quick look at the clang (cc) build, but don't see that problem.
I haven't investigated the i386 configuration for a while - probably should...

> > > > > I revisited this, and can see half of the problem, which offers a 
> > > > > different
> > > > > workaround.  Comparing the specs files for the compiler in 6.2 and 
> > > > > 6.5,
> > > > > I see that someone added a fallback for -L/usr/lib, apparently to 
> > > > > compensate
> > > > > for some other change.
> 
> The commit log was "Pass -L/usr/lib to the linker in preparation for
> switching to lld, which does not have a default search path."
> 

-- 
Thomas E. Dickey 
https://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: PGP signature


Re: Firefox extension broken in -current's v71.0

2019-12-26 Thread Evan Tann
On Thu Dec 26, 2019 at 6:12 PM, Stuart Henderson wrote:
> On 2019/12/26 07:53, open...@evantann.com wrote:
> > >Synopsis:  "1Password X" extension on Firefox shows 0 passwords
> > >Category:
> > >Environment:
> > System  : OpenBSD 6.6
> > Details : OpenBSD 6.6-current (GENERIC.MP) #565: Tue Dec 24 
> > 13:18:50 MST 2019
> >  
> > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > 
> > Architecture: OpenBSD.amd64
> > Machine : amd64
> > >Description:
> > When logging into the 1Password X extension, you'll see a brief flash
> > of your vault items (passwords), but after ~100ms they disappear and
> > are replaced with the text "No items in this vault." As a result I'm
> > unable to access any of my passwords on any OpenBSD device running
> > -current.
> > 
> > After communicating with a 1Password dev, he confirmed that all
> > 1Password X storage is within Firefox's cache visible in about:cache.
> > 
> > If it helps debug, Chrome also experiences this same issue, but it has
> > been a problem in Chrome for longer.
> > >How-To-Repeat:
> > Install Firefox and the 1Password X extension. Save a password (vault
> > item) into the extension. Log into the extension. You'll see the vault
> > item briefly flash onto the screen then disappear.
> > >Fix:
> > Unknown. Initially I thought this could be related to the unveil
> > changes that happened around the same time, since Chrome also has the
> > same issue. I modified the /etc/firefox/unveil.main file to have
> > `/ rwc` for testing but that did not change the behavior. I found no
> > indications of a pledge-permission problem in dmesg.
>
> 
> Perhaps it is not in the main process - try unveil.content?
>
> 
> Running firefox under ktrace -di may also give clues but it's very
> noisy,
> I would usually get it started and to the point just before I trigger
> the
> behaviour, then "ktrace -di -p " - the parent
> process
> is the one just named "/usr/local/bin/firefox" in the ps(1) listing.

Adding `/ rwc` to unveil.content and unveil.main did not fix the problem.

ktrace was indeed very noisy. I grepped the kdump with

$ kdump | grep RET -C4 | grep "\-1" -C4

to focus on -1 exit codes and searched the resulting output for
"1password". I found 2 errors. The first with the mem address
substituted:

CALL  futex($MEM_ADDRESS,0x82,1,0,0)
RET   write 1
RET   futex -1 errno 1 Operation not permitted

And the second with my cache folder and hash substituted:

NAMI  "$CACHE_FOLDER/entries/$HEX_HASH"
RET   sendmsg 32/0x20
RET   acess -1 errno 2 No such file or directory

I checked and indeed that cache entry does not exist on my filesystem.

Just searching kdump for 1password reveals many http requests, however
it's not clear to me if there's any errors surrounding those.



Re: Firefox extension broken in -current's v71.0

2019-12-26 Thread Stuart Henderson
On 2019/12/26 07:53, open...@evantann.com wrote:
> >Synopsis:"1Password X" extension on Firefox shows 0 passwords
> >Category:
> >Environment:
>   System  : OpenBSD 6.6
>   Details : OpenBSD 6.6-current (GENERIC.MP) #565: Tue Dec 24 
> 13:18:50 MST 2019
>
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> 
>   Architecture: OpenBSD.amd64
>   Machine : amd64
> >Description:
>   When logging into the 1Password X extension, you'll see a brief flash
>   of your vault items (passwords), but after ~100ms they disappear and
>   are replaced with the text "No items in this vault." As a result I'm
>   unable to access any of my passwords on any OpenBSD device running
>   -current.
> 
>   After communicating with a 1Password dev, he confirmed that all
>   1Password X storage is within Firefox's cache visible in about:cache.
> 
>   If it helps debug, Chrome also experiences this same issue, but it has
>   been a problem in Chrome for longer.
> >How-To-Repeat:
>   Install Firefox and the 1Password X extension. Save a password (vault
>   item) into the extension. Log into the extension. You'll see the vault
>   item briefly flash onto the screen then disappear.
> >Fix:
>   Unknown. Initially I thought this could be related to the unveil
>   changes that happened around the same time, since Chrome also has the
>   same issue. I modified the /etc/firefox/unveil.main file to have
>   `/ rwc` for testing but that did not change the behavior. I found no
>   indications of a pledge-permission problem in dmesg.

Perhaps it is not in the main process - try unveil.content?

Running firefox under ktrace -di may also give clues but it's very noisy,
I would usually get it started and to the point just before I trigger the
behaviour, then "ktrace -di -p " - the parent process
is the one just named "/usr/local/bin/firefox" in the ps(1) listing.



December 26th snapshot bsd.rd is panic'ing

2019-12-26 Thread pjp
>Synopsis:  december 26th macppc snapshot panics
>Category:  powerpc
>Environment:
System  : OpenBSD 6.6
Details : OpenBSD 6.6 (GENERIC.MP) #603: Fri Oct  4 13:45:51 MDT 
2019
 
dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/GENERIC.MP

Architecture: OpenBSD.macppc
Machine : macppc
>Description:
The new snapshot panics in bsd.rd it goes so fast that I cannot see
where nor debug it, the box reboots.  I tried bsd (not mp) and it
doesn't panic, but complains about a new ABI (I guess), It shouldn't
run this old userland anyhow.
>How-To-Repeat:
An older current is tried to be updated.  I have in the meanwhile since
october added a few external USB cards and Ethernet quad card.  I have
also added a DVI-to-HDMI converter, I'm not sure if this could be the
cause.
>Fix:
Not known yet, I wanted to get this out there, in case anyone knows
where the problem may lie based on the dmesg.


dmesg:
OpenBSD 6.6 (GENERIC.MP) #603: Fri Oct  4 13:45:51 MDT 2019
dera...@macppc.openbsd.org:/usr/src/sys/arch/macppc/compile/GENERIC.MP
real mem = 0 (0MB)
avail mem = 2020229120 (1926MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root: model PowerMac7,3
cpu0 at mainbus0: 970FX (Revision 0x300): 1800 MHz
cpu1 at mainbus0: 970FX (Revision 0x300): 1800 MHz
mem0 at mainbus0
spdmem0 at mem0: 1GB DDR SDRAM non-parity PC3200CL2.5
spdmem1 at mem0: 1GB DDR SDRAM non-parity PC3200CL2.5
spdmem2 at mem0: 1GB DDR SDRAM non-parity PC3200CL2.5
spdmem3 at mem0: 1GB DDR SDRAM non-parity PC3200CL2.5
memc0 at mainbus0: u3 rev 0xb3
kiic0 at memc0 offset 0xf8001000
iic0 at kiic0
lmtemp0 at iic0 addr 0x4a: ds1775
maxtmp0 at iic0 addr 0x4c: max6690
maxtmp1 at iic0 addr 0x4e: max6690
"cy28508" at iic0 addr 0x69 not configured
"cy2213" at iic0 addr 0x65 not configured
fcu0 at iic0 addr 0xaf
"pca9556" at iic0 addr 0x18 not configured
adc0 at iic0 addr 0x2c: ad7417
"24256" at iic0 addr 0x50 not configured
"pca9556" at iic0 addr 0x19 not configured
adc1 at iic0 addr 0x2d: ad7417
"24256" at iic0 addr 0x51 not configured
"dart" at memc0 offset 0xf8033000 not configured
"mpic" at memc0 offset 0xf804 not configured
mpcpcibr0 at mainbus0 pci: u3-agp
pci0 at mpcpcibr0 bus 0
pchb0 at pci0 dev 11 function 0 "Apple U3 AGP" rev 0x00
appleagp0 at pchb0
agp0 at appleagp0: aperture at 0x0, size 0x1000
vgafb0 at pci0 dev 16 function 0 "NVIDIA GeForce FX 5200 Ultra" rev 0xa1
wsdisplay0 at vgafb0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
ht0 at mainbus0: u3-ht, 6 devices
pci1 at ht0 bus 0
hpb0 at pci1 dev 1 function 0 "Apple U3" rev 0x00: 85 sources
pci2 at hpb0 bus 1
macobio0 at pci2 dev 7 function 0 "Apple K2 Macio" rev 0x60
openpic0 at macobio0 offset 0x4: version 0x4614 feature 770302 LE
macgpio0 at macobio0 offset 0x50
"pmu-interrupt" at macgpio0 offset 0x9 not configured
"programmer-switch" at macgpio0 offset 0x11 not configured
"modem-reset" at macgpio0 offset 0x1d not configured
"modem-power" at macgpio0 offset 0x1e not configured
"fcu-interrupt" at macgpio0 offset 0x15 not configured
"fcu-hw-reset" at macgpio0 offset 0x3a not configured
"slewing-done" at macgpio0 offset 0x23 not configured
"codec-input-data-mux" at macgpio0 offset 0xb not configured
"line-input-detect" at macgpio0 offset 0xc not configured
"codec-error-irq" at macgpio0 offset 0xd not configured
"dig-hw-reset" at macgpio0 offset 0x14 not configured
"line-output-detect" at macgpio0 offset 0x16 not configured
"headphone-detect" at macgpio0 offset 0x17 not configured
"codec-irq" at macgpio0 offset 0x18 not configured
"headphone-mute" at macgpio0 offset 0x1f not configured
"amp-mute" at macgpio0 offset 0x20 not configured
"hw-reset" at macgpio0 offset 0x24 not configured
"line-output-mute" at macgpio0 offset 0x25 not configured
"codec-clock-mux" at macgpio0 offset 0x26 not configured
"escc-legacy" at macobio0 offset 0x12000 not configured
zs0 at macobio0 offset 0x13000: irq 22,23
zstty0 at zs0 channel 0
zstty1 at zs0 channel 1
kiic1 at macobio0 offset 0x18000
iic1 at kiic1
aoa0 at macobio0 offset 0x1: irq 30,1,2
"timer" at macobio0 offset 0x15000 not configured
adb0 at macobio0 offset 0x16000
apm0 at adb0: battery flags 0x9, 0% charged
piic0 at adb0
iic2 at piic0
"fans" at macobio0 offset 0x4c not configured
audio0 at aoa0
ohci0 at pci2 dev 8 function 0 "Apple K2 USB" rev 0x00: irq 27, version 1.0, 
legacy support
ohci1 at pci2 dev 9 function 0 "Apple K2 USB" rev 0x00: irq 28, version 1.0, 
legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0 configuration 1 interface 0 "Apple OHCI root hub" rev 1.00/1.00 
addr 1
usb1 at ohci1: USB revision 1.0
uhub1 at usb1 configuration 1 interface 0 "Apple OHCI root hub" rev 1.00/1.00 
addr 1
ppb0 at pci1 dev 2 function 0 "Apple U3" rev 0x00
pci3 at ppb0 bus 5
bwi0 at pci3 dev 1 function 0 "Broadcom BCM4306" rev 

Firefox extension broken in -current's v71.0

2019-12-26 Thread openbsd
>Synopsis:  "1Password X" extension on Firefox shows 0 passwords
>Category:
>Environment:
System  : OpenBSD 6.6
Details : OpenBSD 6.6-current (GENERIC.MP) #565: Tue Dec 24 
13:18:50 MST 2019
 
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Architecture: OpenBSD.amd64
Machine : amd64
>Description:
When logging into the 1Password X extension, you'll see a brief flash
of your vault items (passwords), but after ~100ms they disappear and
are replaced with the text "No items in this vault." As a result I'm
unable to access any of my passwords on any OpenBSD device running
-current.

After communicating with a 1Password dev, he confirmed that all
1Password X storage is within Firefox's cache visible in about:cache.

If it helps debug, Chrome also experiences this same issue, but it has
been a problem in Chrome for longer.
>How-To-Repeat:
Install Firefox and the 1Password X extension. Save a password (vault
item) into the extension. Log into the extension. You'll see the vault
item briefly flash onto the screen then disappear.
>Fix:
Unknown. Initially I thought this could be related to the unveil
changes that happened around the same time, since Chrome also has the
same issue. I modified the /etc/firefox/unveil.main file to have
`/ rwc` for testing but that did not change the behavior. I found no
indications of a pledge-permission problem in dmesg.


dmesg:
OpenBSD 6.6-current (GENERIC.MP) #565: Tue Dec 24 13:18:50 MST 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17098555392 (16306MB)
avail mem = 16567906304 (15800MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x8f9a8000 (94 entries)
bios0: vendor American Megatrends Inc. version "3801" date 03/14/2018
bios0: ASUSTeK COMPUTER INC. Z170-AR
acpi0 at bios0: ACPI 6.0
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT TPM2 MCFG SSDT FIDT SSDT SSDT HPET SSDT SSDT 
UEFI SSDT LPIT WSMT SSDT SSDT DBGP DBG2
acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4) 
SIO1(S3) PS2K(S4) PS2M(S4) UAR1(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) 
RP11(S4) PXSX(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz, 3510.83 MHz, 06-5e-03
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 24MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz, 3509.52 MHz, 06-5e-03
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz, 3509.52 MHz, 06-5e-03
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 0, core 2, package 0
cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz, 3509.52 MHz, 06-5e-03
cpu3: 

Re: Compiling ncurses-6.1 on OpenBSD

2019-12-26 Thread Stuart Henderson
On 2019/12/25 16:23, Thomas Dickey wrote:
> Since my message to bugs@openbsd.org was ignored,
> I'll have to assume that they're not interested in discussing it,
> and will keep in mind to document it as a pitfall in upcoming releases.

The toolchain isn't my area, but I suspect there's little enthusiasm
for fixing a gcc-related problem especially one reported on amd64 - it's
pretty much only still built there so that developers have an easy way
to run it if they need to fix things in the base OS on the non-clang
platforms which many developers don't have direct access to.

If the problem remains with /usr/bin/cc (which is clang on
amd64/i386/arm/aarch64/mips64) then it would be useful to include the
full steps to repeat the problem - the script is mentioned but not
included in the bugs@openbsd.org mail.

> > > > I revisited this, and can see half of the problem, which offers a 
> > > > different
> > > > workaround.  Comparing the specs files for the compiler in 6.2 and 6.5,
> > > > I see that someone added a fallback for -L/usr/lib, apparently to 
> > > > compensate
> > > > for some other change.

The commit log was "Pass -L/usr/lib to the linker in preparation for
switching to lld, which does not have a default search path."