Comment 11 for bug 531164

I see you are the same person answering in the upstream bug tracker as well. I assume you know what you are doing, but I have to admit I did not understand your explanation there. All I can say is that I experience unexpected behaviour. If this is not a kernel bug then please suggest or reassign a package which is likely the one to cause this bug. I simply don't know. Thank you for your work.