#
#asahi · 2026-04-18 07:17
barusuOkay, I got access to a shell through systemd. apparently it's not faillock
#asahi · 2026-04-18 07:10
barusuI'd say around 20 so weird
#asahi · 2026-04-18 07:10
twbFAR might have distro-specific defaults that are different though -- I don't know
#asahi · 2026-04-18 07:09
barusuIt's been more than 10 minutes
#asahi · 2026-04-18 07:09
twbAnd it explicitly says rebooting clears the state
#asahi · 2026-04-18 07:09
twbif faillock *is* the problem you ran into, faillock by default stores its state in /run (wiped on reboot) but unlocks after 10 minutes
#asahi · 2026-04-18 07:09
barusuYeah, it does not persist the state to a file, so I need chroot
#asahi · 2026-04-18 07:07
twbAh it's not sudo it's pam_faillock
#asahi · 2026-04-18 07:07
twbif it's just /etc/shadow then I don't know a way to do it without chroot
#asahi · 2026-04-18 07:06
twbwhere does sudo faillock get saved to? Maybe you can do something like 'mount -o remount,rw /; rm /var/lib/sudo/faillock.state; exit"
#asahi · 2026-04-18 07:04
barusuthanks for helping though
#asahi · 2026-04-18 07:04
barususad, I hope someone chimes in later because I don't know how long the lock has been set for and I don't want to lose my data.
#asahi · 2026-04-18 07:00
twbI haven't got any suggestions for that :-(
#asahi · 2026-04-18 07:00
twboh hrm
#asahi · 2026-04-18 07:00
barususo I can't use faillock in my instal
#asahi · 2026-04-18 06:59
barusuwith rd.break, I get the shell, but it doesn't have the chroot binary
#asahi · 2026-04-18 06:59
twbnext to rd.break
#asahi · 2026-04-18 06:59
barusuwhere do I add this?
#asahi · 2026-04-18 06:58
twb# FIXME On some failures dracut drops to a rescue shell; this NEVER has a valid root password, even on Fedora! But if you add "SYSTEMD_SULOGIN_FORCE=yes", after the wrong password fails, login(8) will crash to a root shell ANYWAY.
#asahi · 2026-04-18 06:57
twboh let me find the workaround for dracut people...
#asahi · 2026-04-18 06:55
barusuThe root account also seems to be locked
#asahi · 2026-04-18 06:52
barusurd.break spawned a functional shell, but no chroot
#asahi · 2026-04-18 06:49
barusuWill try. Another quirk I'm seeing in grub is that the cursor does not appear at all, so I have to spam right arrow key and type/delete to guess the position haha
#asahi · 2026-04-18 06:49
twbDepends on the distro and the rd stack, but sometimes bypasses weirdness because the break happens earlier
#asahi · 2026-04-18 06:48
twbI personally prefer to do rd.break and then "chroot /target passwd root" or similar, rather than init=/bin/sh
#asahi · 2026-04-18 06:41
barusuOkay, weirdness galore, the last time I edited boot entry with init=/bin/bash, the shell launched and I was able to type stuff. Now, for some reason, the shell spawns but the keyboard is not working (caps lock doesn't do anything too). :(
#asahi · 2026-04-18 06:39
chadmedthe default is 10 minutes, and yes as root you can do faillock --user ${username} --reset to clear it
#asahi · 2026-04-18 06:39
barusucan i clear is as root? if not then how long does it usually lock for?
#asahi · 2026-04-18 06:38
barusudoes it not show how long the lock has been applied for?
#asahi · 2026-04-18 06:38
chadmedif you typed your password wrong into sudo three times, faillock kickedi n
#asahi · 2026-04-18 06:35
barusuI think greetd is not able to authenticate for some reason -_-
#asahi · 2026-04-18 06:34
barusuweird, had to log in through grub as root to re set the password
#asahi · 2026-04-18 06:28
barusufew of my sudo attempts failed during my last login before I rebooted, could that have something to do with a timeout?
#asahi · 2026-04-18 06:21
barusuweird, I can't seem to log into my account using the TTY. I know I am putting the username and password correctly, but it's not logging in. says login incorrect
#asahi · 2026-04-18 06:16
barusuawesome, just what I wanted to hear. so all the magic is taken care of before login
#asahi · 2026-04-18 06:16
chadmednothing we do is specifically tied to kde, its just the first class supported DE
#asahi · 2026-04-18 06:13
barusuCool, I plan to use dwm on my asahi because muscle memory. Are there any special non-systemd services that KDE runs?
#asahi · 2026-04-18 06:11
chadmedsddm is on its deathbed anyway
#asahi · 2026-04-18 06:11
chadmedit doesnt really matter
#asahi · 2026-04-18 06:05
barusuWould I be going against the grain if I install greetd and tuigreet instead of SDDM on asahi?
#asahi · 2026-04-18 05:06
chadmedwe cant even escape broadcom here :P
#asahi · 2026-04-18 05:05
twbI guess I could see people saying that about Nvidia and Broadcom components :-)
#asahi · 2026-04-18 05:05
chadmed"thank you so much for getting linux to work on my ryzen PC!" sounds kinda silly, no?
#asahi · 2026-04-18 05:04
chadmedhell lenovo *ships* thinkpads with ubuntu if you buy direct
#asahi · 2026-04-18 05:03
chadmedprobably because linux has mostly Just Worked on x86 machines for like 20 years now, by and large has vendor support, and is trivial from a user perspective
#asahi · 2026-04-18 05:01
twbHm, wikipedia says of laptops, 1/4 are lenovo and 1/10 are apple
#asahi · 2026-04-18 05:01
twbI find it interesting how often people pop up and say "thanks for making linux on mac". Is it just different expectations? Surely a lot more thinkpads are sold than macbooks, right?
#asahi · 2026-04-17 23:43
areofylHello! This is my first time using IRC! I'm messaging from an MBA M1 running Gentoo! Thank you so much Asahi team!
#asahi · 2026-04-17 10:48
chaos_princessbarusu: touch id requires a "sacrificial" machine that you don't mind constantly wiping and reinstalling the os on. dp is partially done already, it is just not in a shippable state yet. (only one port supports DP, and there are issues around hotplug)
#asahi · 2026-04-17 10:30
twbyay

plus ›