Yes, some modules run other Yast modules, because of this we cannot simply check at start for some global Yast lock and the user needs to take care of this. To handle this properly we would need passing an additional parameter for _all_ Yast modules (incl. the 3rd party yast modules)... :-(