I can reproduce this. It is coming from the k-point set. Just have a look into the kpts.xml file and you will immediately see the problem. Somehow the z-coordinates get messed up. This obviously shouldn't happen and obviously is a bug. I'll investigate this, but here is a quick fix.

1. Replace the content of your kpts.xml file with

         <kPointLists>
            <kPointList name="default" count="1" nx="1" ny="1" nz="1" type="mesh">
               <kPoint weight="     1.0000000000000"> 0.0  0.0 0.0</kPoint>
            </kPointList>
         </kPointLists>
 
 

This will give you a trivial parsable k-point set.

2. Invoke the input generator with

inpgen -inp.xml -kpt
 
 

This will generate another default k-point set. The new default k-point set has correct entries.

3. Change the selected k-point set in the inp.xml file to the newly generated k-point set. The name will probably be "default-2".

I made an issue for this ( https://iffgit.fz-juelich.de/fleur/fleur/-/issues/635 ) so that we don't forget to fix the problem and you can see when it gets fixed. Thank you for reporting this problem!