| 1 |
> I keep having a problem where the OS becomes inaccessable after |
| 2 |
> running in X for a while. I haven't noticed a time pattern yet but it |
| 3 |
> doesn't take long sometimes. |
| 4 |
|
| 5 |
> I see no problem when starting X and I see nothing in |
| 6 |
> /var/log/messages that gives a clue about what is happening. |
| 7 |
> |
| 8 |
> I'm running fairly up to date Desktop profile on kernel: |
| 9 |
> |
| 10 |
> I'm not sure how to track down the problem since I'm not seeing any |
| 11 |
> give away clues in /var/log/messages |
| 12 |
> |
| 13 |
> So far, once the lockup has happened it appears there is no way in |
| 14 |
> other than the reboot switch. |
| 15 |
|
| 16 |
Can you read through the recent thread titled " ~amd64 : X11 (?) |
| 17 |
crashing"? Myself and others post many trouble-shooting ideas for |
| 18 |
buggy X operation. |
| 19 |
|
| 20 |
It could be any number of things, but I think at least 4-5 different |
| 21 |
suggestions were posted. That'd be a good place to start. If all |
| 22 |
that's tried, then let us know and we can consider other options. |
| 23 |
|
| 24 |
On that thread, and maybe another, there is discussion about FF and |
| 25 |
youtube. I found I had to recompile FF after updating the kernel for |
| 26 |
audioout on flash, since there must have been some changes to ALSA. |
| 27 |
|
| 28 |
Regards, |
| 29 |
daid |
Archives