a possible fix for bug #460662 part 2