Re: xlock Does Not Unlock (Snapshot)
Chris Wojo wrote: > I feel like these two issues could be related; but I'm not aware of any way > to diagnose why it won't accept my password or yubikey. > The yubikey authentication works on login; just not on screen locks. this depends on login.conf i believe, but for xlock you may have to type "yubikey:" followed by the otp.
Re: xlock Does Not Unlock (Snapshot)
After disabling the yubikey authentication in /etc/login.conf it appears that xlock is now working. Side note, when I had yubikey enabled and ran xlock from the command line with messages or errors. Same with logs. I'll look at running ktrace on it next. Thank you! -chris On Wed, Mar 21, 2018 at 09:42:16PM +0100, Paul de Weerd wrote: > Hi Chris, > > I updated this morning to the latest snap: > > kern.version=OpenBSD 6.3 (GENERIC.MP) #82: Tue Mar 20 11:28:30 MDT 2018 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > This is what I see in syslog upon start and succesful unlock of xlock > (note that I also use openbox): > > 2018-03-21T20:35:06.950Z pom xlock[95795]: Start: weerd, weerd, :0 > 2018-03-21T20:35:20.380Z pom xlock[95795]: xlock: root unlocked screen > 2018-03-21T20:35:20.381Z pom xlock[95795]: Stop: weerd, weerd, :0, 0m 14s > > Does xlock log anything for you? If you start xlock from a terminal > (say, xterm), does it output anything when you try to unlock but are > not succesful? (which you would see after killing xlock from another > tty) Have you tried running xlock under ktrace(1)? > > Are you running any other programs that might be grabbing your > keyboard and/or mouse? > > You mention using yubikey. I don't think that works out-of-the-box > without any further configuration. Can you undo that configuration > and see if that makes a difference for unlocking with your password? > Compare kdump output from a yubikey enabled attempt and a non-yubi > attempt. That may give some more information to help diagnose the > issue further. > > Cheers, > > Paul 'WEiRD' de Weerd > > On Wed, Mar 21, 2018 at 12:59:14PM -0700, Chris Wojo wrote: > | Hello: > | > | I've found that when I run xlock to lock the screen, I cannot log back in. > I must switch to a different tty and `kill -9 xlock`. > | > | I've tested this several with a few different snapshots since the 6.3 > version change in both xfce and openbox. > | Since xlock isn't working, I started using xflock4 and found that it will > not accept my Yubikey for unlocking the screen; but requires my password. > | > | I feel like these two issues could be related; but I'm not aware of any way > to diagnose why it won't accept my password or yubikey. > | The yubikey authentication works on login; just not on screen locks. > | > | Here's the uname: > | OpenBSD celestra 6.3 GENERIC.MP#89 amd64 > | > | Any insight or ways for me to help debug would be greatly appreciated. > | > | Thanks! > | > | > > -- > >[<++>-]<+++.>+++[<-->-]<.>+++[<+ > +++>-]<.>++[<>-]<+.--.[-] > http://www.weirdnet.nl/ >
Re: xlock Does Not Unlock (Snapshot)
Hi Chris, I updated this morning to the latest snap: kern.version=OpenBSD 6.3 (GENERIC.MP) #82: Tue Mar 20 11:28:30 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP This is what I see in syslog upon start and succesful unlock of xlock (note that I also use openbox): 2018-03-21T20:35:06.950Z pom xlock[95795]: Start: weerd, weerd, :0 2018-03-21T20:35:20.380Z pom xlock[95795]: xlock: root unlocked screen 2018-03-21T20:35:20.381Z pom xlock[95795]: Stop: weerd, weerd, :0, 0m 14s Does xlock log anything for you? If you start xlock from a terminal (say, xterm), does it output anything when you try to unlock but are not succesful? (which you would see after killing xlock from another tty) Have you tried running xlock under ktrace(1)? Are you running any other programs that might be grabbing your keyboard and/or mouse? You mention using yubikey. I don't think that works out-of-the-box without any further configuration. Can you undo that configuration and see if that makes a difference for unlocking with your password? Compare kdump output from a yubikey enabled attempt and a non-yubi attempt. That may give some more information to help diagnose the issue further. Cheers, Paul 'WEiRD' de Weerd On Wed, Mar 21, 2018 at 12:59:14PM -0700, Chris Wojo wrote: | Hello: | | I've found that when I run xlock to lock the screen, I cannot log back in. I must switch to a different tty and `kill -9 xlock`. | | I've tested this several with a few different snapshots since the 6.3 version change in both xfce and openbox. | Since xlock isn't working, I started using xflock4 and found that it will not accept my Yubikey for unlocking the screen; but requires my password. | | I feel like these two issues could be related; but I'm not aware of any way to diagnose why it won't accept my password or yubikey. | The yubikey authentication works on login; just not on screen locks. | | Here's the uname: | OpenBSD celestra 6.3 GENERIC.MP#89 amd64 | | Any insight or ways for me to help debug would be greatly appreciated. | | Thanks! | | -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
Re: xlock Does Not Unlock (Snapshot)
On 03/21/18 20:23, Chris Wojtyna wrote: I regularly run snapshots myself. I did a fresh install to move to full disk encryption. No custom Xorg conf dmesg: OpenBSD 6.3 (GENERIC.MP) #89: Wed Mar 21 02:14:53 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 21331415040 (20343MB) avail mem = 20677857280 (19719MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x9cbfd000 (65 entries) bios0: vendor LENOVO version "JBET54WW (1.19 )" date 11/06/2015 bios0: LENOVO 20BXCTO1WW acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI DMAR acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.63 MHz 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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache acpihpet0: recalibrated TSC frequency 2594002659 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz 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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz 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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz cpu3: 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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus -1 (EXP3) acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1 acpipwrres1 at acpi0: NVP3, resource for PEG_ acpipwrres2 at acpi0: NVP2, resource for PEG_ acpitz0 at acpi0: critical temperature is 128 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "LEN0071" at acpi0 not configured "LEN200F" at acpi0 not configured acpibat0 at acpi0: BAT0 model "45N1773" serial 20427 type LION oem "SANYO" acpibat1 at acpi0: BAT1 model "45N1775" serial 2659 type LION oem "SANYO" acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "INT340F" at acpi0 not configured acpivideo0 at acpi0: VID_ acpivout at acpivideo0 not configured
Re: xlock Does Not Unlock (Snapshot)
I regularly run snapshots myself. I did a fresh install to move to full disk encryption. No custom Xorg conf dmesg: OpenBSD 6.3 (GENERIC.MP) #89: Wed Mar 21 02:14:53 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 21331415040 (20343MB) avail mem = 20677857280 (19719MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x9cbfd000 (65 entries) bios0: vendor LENOVO version "JBET54WW (1.19 )" date 11/06/2015 bios0: LENOVO 20BXCTO1WW acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI DMAR acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.63 MHz 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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache acpihpet0: recalibrated TSC frequency 2594002659 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz 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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz 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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2494.23 MHz cpu3: 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,SMX,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,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus -1 (EXP3) acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1 acpipwrres1 at acpi0: NVP3, resource for PEG_ acpipwrres2 at acpi0: NVP2, resource for PEG_ acpitz0 at acpi0: critical temperature is 128 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "LEN0071" at acpi0 not configured "LEN200F" at acpi0 not configured acpibat0 at acpi0: BAT0 model "45N1773" serial 20427 type LION oem "SANYO" acpibat1 at acpi0: BAT1 model "45N1775" serial 2659 type LION oem "SANYO" acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "INT340F" at acpi0 not configured acpivideo0 at acpi0: VID_ acpivout at acpivideo0 not configured cpu0: Enhanced SpeedStep 2494 MHz: speeds:
Re: xlock Does Not Unlock (Snapshot)
On Wed, Mar 21, 2018 at 12:59:14PM -0700, Chris Wojo wrote: > Hello: > > I've found that when I run xlock to lock the screen, I cannot log back in. I > must switch to a different tty and `kill -9 xlock`. > > I've tested this several with a few different snapshots since the 6.3 version > change in both xfce and openbox. > Since xlock isn't working, I started using xflock4 and found that it will not > accept my Yubikey for unlocking the screen; but requires my password. > > I feel like these two issues could be related; but I'm not aware of any way > to diagnose why it won't accept my password or yubikey. > The yubikey authentication works on login; just not on screen locks. > > Here's the uname: > OpenBSD celestra 6.3 GENERIC.MP#89 amd64 > > Any insight or ways for me to help debug would be greatly appreciated. > > Thanks! > > Howdy. Can you provide more information? Examples of such information would be: * dmesg * X config (if not autogenerated) * X log As another data point, I'm a daily user of xlock and regularly run the latest snapshot(s)/pkgs and have not experienced what you have on an Intel NUC (Skull Canyon) or a Thinkpad E475. +--+ Carlos
xlock Does Not Unlock (Snapshot)
Hello: I've found that when I run xlock to lock the screen, I cannot log back in. I must switch to a different tty and `kill -9 xlock`. I've tested this several with a few different snapshots since the 6.3 version change in both xfce and openbox. Since xlock isn't working, I started using xflock4 and found that it will not accept my Yubikey for unlocking the screen; but requires my password. I feel like these two issues could be related; but I'm not aware of any way to diagnose why it won't accept my password or yubikey. The yubikey authentication works on login; just not on screen locks. Here's the uname: OpenBSD celestra 6.3 GENERIC.MP#89 amd64 Any insight or ways for me to help debug would be greatly appreciated. Thanks!
