Re: [Ltsp-discuss] One client going nuts randomly

[Rolf-Werner E. <eil...@t-...>]

Am 11.02.2011 00:22, schrieb Rob Owens:
> On Thu, Feb 10, 2011 at 10:35:50AM +0100, Rolf-Werner Eilert wrote:
>> Am 10.02.2011 02:41, schrieb Rob Owens:
>>> On Wed, Feb 09, 2011 at 12:09:09PM +0100, Rolf-Werner Eilert wrote:
>>>> Hi everyone,
>>>>
>>>> This is just the case when I don't know where to start :-)
>>>>
>>>> We are still running an older system with 4.2 based on a Suse 10.3.
>>>>
>>>> One of our clients (unfortunately, it's the one on the teacher's desk in
>>>> one of the computer labs) sometimes (i. e. randomly) runs bust. Suddenly
>>>> all available applications will open and close, the screen being swamped
>>>> with windows, and no mouse and keyboard reacts. It seems as if every
>>>> mouse movement triggers another instance of a program or another
>>>> program. After a minute or so, everything is quiet again.
>>>>
>>>> Of course, I swapped the client hardware and network connection, and
>>>> yesterday we thought everything be clear. But today, 10 minutes ago, the
>>>> thing got mad again.
>>>>
>>>> Now, where or how would you look for such a problem? No one else has
>>>> this problem, nowhere on any of the 50+ clients in the house. And I
>>>> could never reproduce this error to see it myself, I only know it from
>>>> the tales our IT teacher is telling me about it ;-) In fact, when she
>>>> logs in at a student's client, she has never had this problem so far.
>>>>
>>> Besides changing the mouse, as someone else suggested, I'd try a
>>> different user on that client.  I'd also look at lts.conf and see if
>>> there are any settings that are unique to that client.
>>>
>>> -Rob
>>
>> Yep, there are other users logging in, and yes, they did experience
>> similar issues. So I think this is not a user-specific issue.
>>
>> The lts.conf settings are the same, as there is the same client hardware
>> all over the room, even for the teacher.
>>
> Next I would try moving that client hardware to a different network
> jack/cable.  I'd be surprised if a bad network connection would cause
> anything but a lockup, but I'm not an expert.
>
> -Rob

You're right, this is one of the things we've tried, but it didn't help.

Rolf