Closed daniejstriata closed 2 years ago
Were you running lfs in a very thin terminal ?
@Canop no. It was a normal ssh session. I load lfs from my motd.sh inside /etc/profile.d/
I'm puzzled there. I have no idea how this can happen.
Can you check the version of lfs you're using ?
It is on 1.3.0. The only thing wrong / different here was that the one drive was full. When I grew the disk lfs worked again.
The only thing that could come to my mind to explain this with a full drive is linux not being able to correctly answer api call for the fd of the virtual console, or ssh who need to handle it but fail if disk is full for the same reason. But that a random guess.
The error is in Termimad. And I just notice the version of termimad included in lfs is quite old. I thought I had updated the dependency but it seems I forgot.
It seems impossible to have an error on this line, though: https://github.com/Canop/termimad/blob/3c143bddefa20988f621beb78256ce7c775ce1d1/src/tbl.rs#L214
@daniejstriata Please, what were the launch arguments ?
I added the binary output.
lfs --units binary
As I removed that section of code, I declare the bug "solved".
Hi,
I got this error on what I believe was a full drive.
Growing drive took the error away. Setting backtrace did not make any difference.