I can add that when trying a job from luban it seems to go and start but then just raises itself up and doesnt do anything. Even though the job is still running.
I had that issue (Artisan, 10W laser module) when I tried to have a really tight laser pattern with tiny shapes that were apparently interpretated wrong. Luban created a gcode that didnt have any commands to turn on the laser or move the machine. So it kinda ran trough the file within a second and then didn’t show a completed job. Perhaps it would be helpful to share what you were trying to cut or an example file and settings where this occured to you.
I also figured out that sometimes Luban halts after the auto-thickness detection without any errors but without proceeding, for those situations a manual thickness entry made the job go for me.