genpaku has quit [Remote host closed the connection]
genpaku has joined #crux-devel
SiFuh has quit [Ping timeout: 250 seconds]
fishe has joined #crux-devel
fishe has quit [Quit: Connection closed for inactivity]
SiFuh has joined #crux-devel
ivandi has quit [Quit: WeeChat 3.6]
ivandi has joined #crux-devel
SiFuh has quit [Ping timeout: 265 seconds]
SiFuh has joined #crux-devel
<jaeger>
Somehow a sysup on my laptop (on 3.7) has caused a breakage that prevents me from logging in but creates no errors in the syslog. I see the usual "opened session" message followed immediately by "closed session" with no errors in between. Anyone else experience this?
<beerman>
not me, anything specific about the host?
<beerman>
during upgrade? or "just now"?
<jaeger>
Nothing different about it or unusual from my other setups
<jaeger>
during the sysup. Not sure which package because I left it unattended... but I had a sway session running and after it happened I could not open any new foot/xterm terminals, any new tmux panes, or log in via the console
<jaeger>
I've tried a few things like other shells, rebuilding shadow (login), pam, bash, etc.
<jaeger>
I'll run another upgrade from the release ISO if I can't figure out what caused it, just trying to learn that before I fix it
<beerman>
i mean
<beerman>
this awfully looks like a pam issue to me
<beerman>
but thats mostly a gut feeling here
<beerman>
so you login via tty and start sway like that, no manager like greetd?
<jaeger>
yes
<beerman>
anyway, I'd like to see if common-{account,auth,password,session} or any other pam stack in question got corrupted somehow
<jaeger>
Not as far as I can see, they look completely normal
<beerman>
no idea then, how far back have the sysup updates been?
<jaeger>
Not sure I fully understand the question but it was completely up to date on 3.6, then upgraded to 3.7 via the release ISO
<jaeger>
Reinstalling ISO packages again now and I'll update one by one to see when it breaks, if it does again
<jaeger>
unrelated to that, rust also installs a file into /usr/libexec
<pitillo>
jaeger: something similar here. I wasn't able to run some terminals (the only one working was terminology which wasn't affected by the 3.6 -> 3.7 upgrade). I was able to login to tty and then make a full core ports rebuild. I thought it was my fault, so I didn't disturbed here (I still have some specific problems with some ports... the webkitgtk-40 and a mess with ffmpeg dependent ports (mplayer was
<pitillo>
built finally, but I'm not able to build mpv) but as always, I believe it must be my fault
<jaeger>
very odd
<jaeger>
I wasn't able to log in via tty, even :/
<pitillo>
I was able, but behavior was strange... it took around 50sec to give me the prompt... but at least it let me do it on tty
<jaeger>
weird
<pitillo>
well, mpv is built disabling vulkan... it was autodetected and breaking the build... now time to dig into webkitgtk (this will be harder)
jue has joined #crux-devel
<jue>
jaeger: guess your login problem should be fixed with latest readline/bash update