On feisty since few days (maybe since the last update of the kernel from security) the bug came back ...
On feisty since few days (maybe since the last update of the kernel from security) the bug came back ...