From freenx-knx  Thu Mar 16 16:23:58 2006
From: Fabian Franz <FabianFranz () gmx ! de>
Date: Thu, 16 Mar 2006 16:23:58 +0000
To: freenx-knx
Subject: Re: [FreeNX-kNX] Keyboard mapping problem
Message-Id: <200603161724.02646.FabianFranz () gmx ! de>
X-MARC-Message: https://marc.info/?l=freenx-knx&m=114252636811934
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1700967495=="

--===============1700967495==
Content-Type: multipart/signed;
  boundary="nextPart2401333.VaAkf5Nodj";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2401333.VaAkf5Nodj
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Am Mittwoch, 15. M=E4rz 2006 22:19 schrieb Jani Huhtanen:
> Hi!
>
> After the upgrade from xorg6 to xorg7, keyboard mappings didn't work
> anymore under NX session (i.e. I was stuck to pc101 and us). I came up wi=
th
> a temporary solution,=20

WOW! You are great! I really mean it, because you "solved" all the problems=
 at=20
least, where most of us were stuck.

> #setxkbmap -model pc105 -layout fi -rules xorg
> Couldn't interpret _XKB_RULES_NAMES property
> Use defaults: rules - 'xorg' model - 'pc101' layout - 'us'
> *** glibc detected *** double free or corruption (out): 0x4000afa0 ***
> Aborted

At least under SuSE 10 this is a known problem, which also applies to xGL.

> #xprop -root | grep XKB
>
> (i.e. nothing changed and setxkbmap strangely crashed)
>
> The only "solution" to this problem so far has been to manually insert
> _XKB_RULES_NAMES property.
>
> I do this under NX session:
> #xprop -root -f _XKB_RULES_NAMES 8s -set _XKB_RULES_NAMES xorg
> #setxkbmap -model pc105 -layout fi
>
> Now layout is correctly set
> #xprop -root | grep XKB
> _XKB_RULES_NAMES(STRING) =3D "xorg", "pc105", "fi", "", ""
>
> But the question is: What causes this problem and how to fix it?

I think its that setkbmap NEEDs this property in newer versions, so the fix=
=20
would be to set that property from NX Agent.

>
> I hope you guys can help me out here.

You might want to add that line to your NODE_AUTOSTART function, though the=
=20
display is not set, so you might want to use 0.5.0 snapshot >=3D 5, to alwa=
ys=20
enable your workaround.

cu

=46abian

=2D-=20
      *** Consulting - Training - Workshops - Troubleshooting ***
   @@@ LiveCDs (Knoppix), Debian, Remote Desktop Access (FreeNX) @@@

=2D-- Fabian Franz --- www.fabian-franz.de --- consulting@fabian-franz.de

--nextPart2401333.VaAkf5Nodj
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBEGZEiI0lSH7CXz7MRAkWGAJ9ElCkSSMtAcNHgE5NkXfviKrA6vwCfRvRg
lp8HYjk7Xe47bTdCZesD+pE=
=kQWf
-----END PGP SIGNATURE-----

--nextPart2401333.VaAkf5Nodj--

--===============1700967495==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
FreeNX-kNX mailing list
FreeNX-kNX@kde.org
https://mail.kde.org/mailman/listinfo/freenx-knx

--===============1700967495==--