No reason for such a bug to be introduced in a new version of aMSN.. can you check if the aMSN upgrade introduced a change in the tcl/tk version installed ? I'd guess the issue is a badly compiled version of tcl/tk or something like that.
No reason for such a bug to be introduced in a new version of aMSN.. can you check if the aMSN upgrade introduced a change in the tcl/tk version installed ? I'd guess the issue is a badly compiled version of tcl/tk or something like that.