Christopher, thanks for the explanation. However, I was under the impression that the automatic response was due to the fact that I changed state of this bug to 'new' (because it was set to 'expired' and I suffered from the same problem).
I'm currently awaiting the problem but I haven't encountered it since I installed the latest kernel version in 16.04: 4.4.0-16-generic. If it occurs again, I will file a new report rather than post here. Thanks again.
Christopher, thanks for the explanation. However, I was under the impression that the automatic response was due to the fact that I changed state of this bug to 'new' (because it was set to 'expired' and I suffered from the same problem).
I'm currently awaiting the problem but I haven't encountered it since I installed the latest kernel version in 16.04: 4.4.0-16-generic. If it occurs again, I will file a new report rather than post here. Thanks again.