Issue fixed in release 1.4.1.1

The following issue is addressed in this release: