pxes keyboard|rdesktop|X problem

------=_Part_18766_33158578.1133269881065
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi list!

I have about 20 pxes thin clients (and counting), all on different hardware
(from brand-new VIA mini boxes to old P166 :), everything works fine on
default pxes images and a bit customized configs. pxes/pxesconfig version i=
s
old 1.0.7. Environment -- rdesktop to Win2003. However, i got strange
problem with one particular person. The symptoms are: after booting and
starting rdesktop neither keyboard nor mouse works (keyboard leds inactive,
as keypresses, and mouse pointer stuck to the center of the screen). After
sshing and killing X i can log in locally, therefore keyboard works. No
rdesktop or X errors present -- correct drivers and settings.
I tried several hardware configurations, switched mouse/keyboard/network
cable/thin client itself -- after two-three days of normal working the same
symptoms. And displaced hardware works fine in other departments and in my
office. Tried erasing and creating special-for-this-client conf file --
still no hope.
Guys, i mean, i _really_ dont want to blame this on karma, but i'm starting
to think i'm paranoid ;)

the dmesg output is no different than on working thin clients, exept there
is
------
xsetleds: error in reading keyboard indicator states
------
when this client is already dead. I get the box to my office, power on, and
everything works.
I just don't know what kind of information/logs supply to you, if you need
any -- i'll send it.

Can someone point me to the right direction exept killing the fsck outta
this secretary??


regards,
if

------=_Part_18766_33158578.1133269881065
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi list!<br>
<br>
I have about 20 pxes thin clients (and counting), all on different
hardware (from brand-new VIA mini boxes to old P166 :), everything
works fine on default pxes images and a bit customized configs.
pxes/pxesconfig version is old 1.0.7. Environment -- rdesktop to
Win2003. However, i got strange problem with one particular person. The
symptoms are: after booting and starting rdesktop neither keyboard nor
mouse works (keyboard leds inactive, as keypresses, and mouse pointer
stuck to the center of the screen). After sshing and killing X i can
log in locally, therefore keyboard works. No rdesktop or X errors
present -- correct drivers and settings.<br>
I tried several hardware configurations, switched
mouse/keyboard/network cable/thin client itself -- after two-three days
of normal working the same symptoms. And displaced hardware works fine
in other departments and in my office. Tried erasing and creating
special-for-this-client conf file -- still no hope.<br>
Guys, i mean, i _really_ dont want to blame this on karma, but i'm starting=
 to think i'm paranoid ;)<br>
<br>
the dmesg output is no different than on working thin clients, exept there =
is<br>
------<br>
xsetleds: error in reading keyboard indicator states<br>
------<br>
when this client is already dead. I get the box to my office, power on, and=
 everything works.<br>
I just don't know what kind of information/logs supply to you, if you need =
any -- i'll send it.<br>
<br>
Can someone point me to the right direction exept killing the fsck outta th=
is secretary??<br>
<br>
<br>
regards,<br>
if<br>

------=_Part_18766_33158578.1133269881065--


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click