oh thanks for the confirmation. so my educated guess was spot on.
I actually saw a similar problem in the past... but it's soo weird why this is happening.
It's most likely a driver problem, but the problem is that it doesn't seem to happen all the time with new installations (not even all the time with a specific ubuntu system/version etc).
It seems that the Intel OpenCL Runtime gets hold of the stdin file descriptor and hashcat can't read from the pipe/stdin anymore after this happens... but this shouldn't happen of course !
We would really need to debug this further and try to see where and why the stdin reading fails exactly, but without an affected installation it's of course very difficult for the devs to troubleshoot this.
Maybe in the future whenever you have some spare minutes and your GPUs are not busy cracking (AND you are still able to get the same problem again), you could contact a dev/mod on #hashcat IRC and we could try to debug/troubleshoot this together. Not sure what else to say here, it's a very, very weird bug and most probably not a hashcat-related problem (but you never know for sure, but it seems to happen to a very small amount of installations that it's not really easy to get hold of such a system/problem. You are lucky !)
I actually saw a similar problem in the past... but it's soo weird why this is happening.
It's most likely a driver problem, but the problem is that it doesn't seem to happen all the time with new installations (not even all the time with a specific ubuntu system/version etc).
It seems that the Intel OpenCL Runtime gets hold of the stdin file descriptor and hashcat can't read from the pipe/stdin anymore after this happens... but this shouldn't happen of course !
We would really need to debug this further and try to see where and why the stdin reading fails exactly, but without an affected installation it's of course very difficult for the devs to troubleshoot this.
Maybe in the future whenever you have some spare minutes and your GPUs are not busy cracking (AND you are still able to get the same problem again), you could contact a dev/mod on #hashcat IRC and we could try to debug/troubleshoot this together. Not sure what else to say here, it's a very, very weird bug and most probably not a hashcat-related problem (but you never know for sure, but it seems to happen to a very small amount of installations that it's not really easy to get hold of such a system/problem. You are lucky !)