SEO

I have a fresh install of Fedora Core 2 and numlock is not working. When
I press the buttin (shift ScrLk) nothing happens.

I know this should be fixable with xkb and / or xmodmap but I spent a
lot of time on that a couple of weeks ago with another computer but
didn't get it to work so I figured it should be easily fixable with a
mini hack this time.

If I run this command:
xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"

In xterm Numlock magically starts working so I figured the easy way
would be to put that exact line in one of the initfiles.

The init file I found that seemed appropriate was /etc/rc.local so I
added the line to that file wich now looks like this (I am not sure what
the last line does but it was there already).

#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"
touch /var/lock/subsys/local

Unfortunatley that didnt help. Numlock still doesn't work (unless I
write the command in xterm).

I don't know why but a hunch is that maybe the small Keyboard layout
indicator applet for GNOME, Keyboard Indicator 2.6.0 is started after
this file is run and that it messes something up?

Any ideas about where I could enter that mysterious line to get NumLock
working would be much apreciated.

Tim

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
> I have a fresh install of Fedora Core 2 and numlock is not working. When
> I press the buttin (shift ScrLk) nothing happens.
[..]

> If I run this command:
> xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"

> In xterm Numlock magically starts working so I figured the easy way
> would be to put that exact line in one of the initfiles.

I'd try out ~/.xinitrc at first and see if that improve things,
simply create this file, if you don't have it.

--
Michael Heiming (GPG-Key ID: 0xEDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAzErkAkPEju3Se5QRArydAJ0fLrNwwVo9tmRzjf2zb3 p8TjrbFgCdH8QJ
7YnAlK3BsWRO+BpoJjK0WSg=
=xgI/
-----END PGP SIGNATURE-----

"Michael Heiming" <michael+USENET@www.heiming.de
> In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
> > I have a fresh install of Fedora Core 2 and numlock is not working. When
> > I press the buttin (shift ScrLk) nothing happens.

> > If I run this command:
> > xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"
>
> > In xterm Numlock magically starts working so I figured the easy way
> > would be to put that exact line in one of the initfiles.
>
> I'd try out ~/.xinitrc at first and see if that improve things,
> simply create this file, if you don't have it.

Sounded like a plan but it did unfortunatley not help.
I didn't have the file in my homedir so I created it and let it contain only
that one line.

I did have one file called .bashrc I also tried adding it there, that worked
but of course only after I have started an xterm window which is
unfortunatley not an option in this case (this is not a computer for me but
for someone that will never use the comand prompt).

Can I check, in anyway if (and when), the .xinitrc is run? Or does anyone
have a better suggestion of what could be the last script that is run before
the controll is given back tothe user?

Or could I maybe be tricksy and add a command in .xinitrc that tells the
computer to to postpone the running of this particular line with 30sec
(while beeing backgrounded so the rest of the scripts can do their things).

I know this is an ugly hack but it feels like it would work atleast.

Tim

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
> "Michael Heiming" <michael+USENET@www.heiming.de
>> In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
>> > I have a fresh install of Fedora Core 2 and numlock is not working. When
[..]

>> > If I run this command:
>> > xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"
>>
>> > In xterm Numlock magically starts working so I figured the easy way
>> > would be to put that exact line in one of the initfiles.
>>
>> I'd try out ~/.xinitrc at first and see if that improve things,
>> simply create this file, if you don't have it.

> Sounded like a plan but it did unfortunatley not help.
> I didn't have the file in my homedir so I created it and let it contain only
> that one line.

Mh, you are using kdm/xdm to login to your favorite wm? Then try
using ~/.xsession, change permissions 'chmod 755 ~/.xsession',
and retry not sure if those perms a really need, but it doesn't
hurt anyway.

--
Michael Heiming (GPG-Key ID: 0xEDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAzKVMAkPEju3Se5QRAiMPAKDBYjpeEQsYfTZwZ9jMNu fbyAYzXQCdE4/U
XM7a6+ZZ/eBDflqCvcOxUr0=
=OOuQ
-----END PGP SIGNATURE-----

Michael Heiming wrote:
> In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
>>"Michael Heiming" <michael+USENET@www.heiming.de
>>>In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
>>>>I have a fresh install of Fedora Core 2 and numlock is not working. When
>>>>If I run this command:
>>>>xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"
>>>
>>>>In xterm Numlock magically starts working so I figured the easy way
>>>>would be to put that exact line in one of the initfiles.
>>>
>>>I'd try out ~/.xinitrc at first and see if that improve things,
>>>simply create this file, if you don't have it.
>
>
>>Sounded like a plan but it did unfortunatley not help.
>>I didn't have the file in my homedir so I created it and let it contain only
>>that one line.
>
>
> Mh, you are using kdm/xdm to login to your favorite wm? Then try
> using ~/.xsession, change permissions 'chmod 755 ~/.xsession',
> and retry not sure if those perms a really need, but it doesn't
> hurt anyway.


I am not sure, I am using a standard Fedora Core 2 I see refferences to
both xdm and xmodmap and I have the Keyboard layout indicator applet for
GNOME, Keyboard Indicator 2.6.0.

And I really don't know how the keyboardlayout works in X, except that
you can change it with the applet or by running xmodmap. And I actually
also know that the mysterious command:

xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"

Makes numlock working, if I run the command twice I get this error message:

xmodmap: commandline:0: bad keysym target keysym 'Pointer_EnableKeys',
no corresponding keycodes
xmodmap: 1 error encountered, aborting.

But the numlock button still keeps working.

I am cluless, but it should be possible to postpone the running of the
command right? Somehow sleep it for one minut untill the rest of the
programs have initialized themself. That is ofcourse really ugly but It
would be nice to get this to work

Tim

Michael Heiming wrote:
> In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
>>"Michael Heiming" <michael+USENET@www.heiming.de
>>>In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
>>>>I have a fresh install of Fedora Core 2 and numlock is not working. When
>>>>If I run this command:
>>>>xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"
>>>>In xterm Numlock magically starts working so I figured the easy way
>>>>would be to put that exact line in one of the initfiles.
>>>I'd try out ~/.xinitrc at first and see if that improve things,
>>>simply create this file, if you don't have it.
>
>>Sounded like a plan but it did unfortunatley not help.
>>I didn't have the file in my homedir so I created it and let it contain only
>>that one line.
>
> Mh, you are using kdm/xdm to login to your favorite wm? Then try
> using ~/.xsession, change permissions 'chmod 755 ~/.xsession',
> and retry not sure if those perms a really need, but it doesn't
> hurt anyway.

Replying to the same message again here since I apperently forgott half
of it in my last reply.

What I also meant to say was that if I make a file .xsession containing
the same line nothing happens at all unless I chmod it as you said to
755. But if I chmod it I cannot even get back into X. Almost imediatley
after I log in (from the graphical loginsceen) I get an errormessage
saying that I was logged in less then 10 seconds and something was
probably wrong. Then I get thrown back to the login screen.

The computer also says that it put an error message in the
..xsession-error file, but that file doesnt exist and nothing shows up in
dmesg.

Anyway the error message, I could read it from the screen was similar to
the one I get when I run the command twice.

Tim

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
> Michael Heiming wrote:
>> In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
>>>"Michael Heiming" <michael+USENET@www.heiming.de
>>>>In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
>>>>>xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"
[..]
>> Mh, you are using kdm/xdm to login to your favorite wm? Then try
>> using ~/.xsession, change permissions 'chmod 755 ~/.xsession',
>> and retry not sure if those perms a really need, but it doesn't
>> hurt anyway.

> I am not sure, I am using a standard Fedora Core 2 I see refferences to
> both xdm and xmodmap and I have the Keyboard layout indicator applet for
> GNOME, Keyboard Indicator 2.6.0.

Great, but did you try putting your command in ~/.xsession and
change the permissions?

--
Michael Heiming (GPG-Key ID: 0xEDD27B94)
mail: echo zvpunry@urvzvat.qr | perl -pe 'y/a-z/n-za-m/'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAzMsWAkPEju3Se5QRAvxZAJ9vc/Q0vc/cPs4pZDxgrrEggK44nACgxwwR
R2Talr5U9JKm+SIltBxsP6Q=
=gLKW
-----END PGP SIGNATURE-----

Tim wrote:
> Michael Heiming wrote:
>
>> In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
>>
>>> "Michael Heiming" <michael+USENET@www.heiming.de
>>>
>>>> In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
>>>>
>>>>> I have a fresh install of Fedora Core 2 and numlock is not working.
>>>>> When
>>>>> If I run this command:
>>>>> xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"
>>>>> In xterm Numlock magically starts working so I figured the easy way
>>>>> would be to put that exact line in one of the initfiles.
>>>>
>>>> I'd try out ~/.xinitrc at first and see if that improve things,
>>>> simply create this file, if you don't have it.
>>
>>
>>> Sounded like a plan but it did unfortunatley not help.
>>> I didn't have the file in my homedir so I created it and let it
>>> contain only
>>> that one line.
>>
>>
>> Mh, you are using kdm/xdm to login to your favorite wm? Then try
>> using ~/.xsession, change permissions 'chmod 755 ~/.xsession',
>> and retry not sure if those perms a really need, but it doesn't
>> hurt anyway.
>
>
> Replying to the same message again here since I apperently forgott half
> of it in my last reply.
>
> What I also meant to say was that if I make a file .xsession containing
> the same line nothing happens at all unless I chmod it as you said to
> 755. But if I chmod it I cannot even get back into X. Almost imediatley
> after I log in (from the graphical loginsceen) I get an errormessage
> saying that I was logged in less then 10 seconds and something was
> probably wrong. Then I get thrown back to the login screen.
>
> The computer also says that it put an error message in the
> .xsession-error file, but that file doesnt exist and nothing shows up in
> dmesg.
>
> Anyway the error message, I could read it from the screen was similar to
> the one I get when I run the command twice.

Just in case it is important, here comes the error message the
supposedly should have been in the .xsession-error file.

/etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/X11/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w
/var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l
":0" "tim"
warning: /etc/X11/xinit/xinitrc.d xinput does not end in sh.

These things may be mistyped since I couldn't find them in any files but
had to retyp them.

Tim

Michael Heiming wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> NotDashEscaped: You need GnuPG to verify this message
>
> In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
>
>>Michael Heiming wrote:
>>
>>>In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
>>>
>>>>"Michael Heiming" <michael+USENET@www.heiming.de
>>>>
>>>>>In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
>>>>>
>>>>>>xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"
>
> [..]
>
>>>Mh, you are using kdm/xdm to login to your favorite wm? Then try
>>>using ~/.xsession, change permissions 'chmod 755 ~/.xsession',
>>>and retry not sure if those perms a really need, but it doesn't
>>>hurt anyway.
>
>
>>I am not sure, I am using a standard Fedora Core 2 I see refferences to
>>both xdm and xmodmap and I have the Keyboard layout indicator applet for
>>GNOME, Keyboard Indicator 2.6.0.
>
>
> Great, but did you try putting your command in ~/.xsession and
> change the permissions?


Yes, sorry I forgot half of the mail. But I tried it with some strange
errors so that I couldnt even start X.

Tim

Tim wrote:
> Tim wrote:
>
>> Michael Heiming wrote:
>>
>>> In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
>>>
>>>> "Michael Heiming" <michael+USENET@www.heiming.de
>>>>
>>>>> In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
>>>>>
>>>>>> I have a fresh install of Fedora Core 2 and numlock is not
>>>>>> working. When
>>>>>> If I run this command:
>>>>>> xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"
>>>>>> In xterm Numlock magically starts working so I figured the easy way
>>>>>> would be to put that exact line in one of the initfiles.
>>>>>
>>>>>
>>>>> I'd try out ~/.xinitrc at first and see if that improve things,
>>>>> simply create this file, if you don't have it.
>>>
>>>
>>>
>>>> Sounded like a plan but it did unfortunatley not help.
>>>> I didn't have the file in my homedir so I created it and let it
>>>> contain only
>>>> that one line.
>>>
>>>
>>>
>>> Mh, you are using kdm/xdm to login to your favorite wm? Then try
>>> using ~/.xsession, change permissions 'chmod 755 ~/.xsession',
>>> and retry not sure if those perms a really need, but it doesn't
>>> hurt anyway.
>>
>>
>>
>> Replying to the same message again here since I apperently forgott
>> half of it in my last reply.
>>
>> What I also meant to say was that if I make a file .xsession
>> containing the same line nothing happens at all unless I chmod it as
>> you said to 755. But if I chmod it I cannot even get back into X.
>> Almost imediatley after I log in (from the graphical loginsceen) I get
>> an errormessage saying that I was logged in less then 10 seconds and
>> something was probably wrong. Then I get thrown back to the login screen.
>>
>> The computer also says that it put an error message in the
>> .xsession-error file, but that file doesnt exist and nothing shows up
>> in dmesg.
>>
>> Anyway the error message, I could read it from the screen was similar
>> to the one I get when I run the command twice.
>
>
> Just in case it is important, here comes the error message the
> supposedly should have been in the .xsession-error file.
>
> /etc/X11/gdm/PreSession/Default: Registering your session with wtmp and
> utmp
> /etc/X11/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w
> /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l
> ":0" "tim"
> warning: /etc/X11/xinit/xinitrc.d xinput does not end in sh.
>
> These things may be mistyped since I couldn't find them in any files but
> had to retyp them.

Just for the fun of it I also tried to ad a completley empty file called
..xsession file in my homedir. That gave me the same error, so I couldnt
boot into X.

Tim