After installing Dapper Flight 5 on my laptop (a Dell Latitude D600), I had encountered a few times the trouble you are mentionning, however, at that time I was not using Wi-Fi. Then, after the kernel upgrade (2.6.15-19) I did not encounter the problem until:
- I have been using Wi-Fi and I was on battery (I was using the latest updates as of 14th of April).
In this configuration, I just have to wait about 10 minutes for the bug to occur. I thought this could a bug in the proprietary ATI driver (which gave me lost of troubles), so I set-up my X Server to use the open source driver. I still had the bug.
However, if I am not connected to a wireless network, I do not have the problem.
After installing Dapper Flight 5 on my laptop (a Dell Latitude D600), I had encountered a few times the trouble you are mentionning, however, at that time I was not using Wi-Fi. Then, after the kernel upgrade (2.6.15-19) I did not encounter the problem until:
- I have been using Wi-Fi and I was on battery (I was using the latest updates as of 14th of April).
In this configuration, I just have to wait about 10 minutes for the bug to occur. I thought this could a bug in the proprietary ATI driver (which gave me lost of troubles), so I set-up my X Server to use the open source driver. I still had the bug.
However, if I am not connected to a wireless network, I do not have the problem.
Huygens