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.

If I add a line in top of the file to point it to sh like this:

#!/bin/sh
xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"

This gives me the same error message plus a very similar message to the
one I get when I run the command twice.

But this is really beginnign to feel like a detour to get numlock working

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:
> Tim wrote:
[..]
> If I add a line in top of the file to point it to sh like this:

> #!/bin/sh
> xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"

> This gives me the same error message plus a very similar message to the
> one I get when I run the command twice.

> But this is really beginnign to feel like a detour to get numlock working

Only used gnome once, accidentally without really mentioning,
wondered why I had no icon for KDE Control Center, but
kcontrol came up fine from xterm, so I didn't bothered at
first, the thing I really disliked was that the most important
icon, start xterm/kvt was that hidden...

From a short google search it looks like there are some problems
with numlock and gnome, perhaps they address your problem:

http://www.linuxgazette.com/node/view/395
http://www.linuxquestions.org/questi...hreadid=180272

Failing that, I'd check the gnome docs, which files it really
uses, or 'strace' the thing (man strace) logged in from another
box via ssh.

Good luck

--
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)

iD8DBQFAzNh3AkPEju3Se5QRAr7xAJ9jt8fcTv/C86thSXPCRY6cn0PYtQCfWCIo
1ZwvIpJ1Ks3Mkag/JKY11kA=
=aAUE
-----END PGP SIGNATURE-----

"Michael Heiming" <michael+USENET@www.heiming.de> wrote
> In comp.os.linux.setup Tim <it2gati@ituniv.se> suggested:
> > Tim wrote:
> [..]
> > If I add a line in top of the file to point it to sh like this:
>
> > #!/bin/sh
> > xmodmap -e "keysym Pointer_EnableKeys = Num_Lock"
>
> > This gives me the same error message plus a very similar message to the
> > one I get when I run the command twice.
>
> > But this is really beginnign to feel like a detour to get numlock
working
>
> Only used gnome once, accidentally without really mentioning,
> wondered why I had no icon for KDE Control Center, but
> kcontrol came up fine from xterm, so I didn't bothered at
> first, the thing I really disliked was that the most important
> icon, start xterm/kvt was that hidden...
>
> From a short google search it looks like there are some problems
> with numlock and gnome, perhaps they address your problem:
>
> http://www.linuxgazette.com/node/view/395
> http://www.linuxquestions.org/questi...hreadid=180272
>
> Failing that, I'd check the gnome docs, which files it really
> uses, or 'strace' the thing (man strace) logged in from another
> box via ssh.
>

Interesting, I hadn't thought about it as a gnome issue but a linux issue,
I'll read upp on the links you mentioned.

Thanks

Tim