As to the original bug, I experience this off a fresh dapper install as of yesterday, and have had it in every dapper install since midway through the dapper dev process.
As to the original bug, I experience this off a fresh dapper install as of yesterday, and have had it in every dapper install since midway through the dapper dev process.