Bug 1136

I quickly made numlock packages using numlockx instead of enable_X11_numlock.
the rpms can be found here for tests:
i586
http://web.supagro.inra.fr/partage/menut/numlock-2.1.2-5.0.1.mga1.i586.rpm

x86_64
http://web.supagro.inra.fr/partage/menut/numlock-2.1.2-5.0.1.mga1.x86_64.rpm

srpms
http://web.supagro.inra.fr/partage/menut/numlock-2.1.2-5.0.1.mga1.src.rpm

of course, the definitive replacement of enable_X11_numlock should be done more cleanly!!!

Source RPM: (none) => numlock-2.1.2-5.mga1.src.rpm

*** Bug 317 has been marked as a duplicate of this bug. ***

CC: (none) => jarillon

This bug is a duplicate of #317, not the other way around. Thanks.

*** This bug has been marked as a duplicate of bug 317 ***

Status: NEW => RESOLVED
CC: (none) => remco
Resolution: (none) => DUPLICATE

as you want(In reply to comment #3)
> This bug is a duplicate of #317, not the other way around. Thanks.
> 

if you want, but we lost explanation of why it's not working, and all references on mandriva bugs.

Reopening.

Status: RESOLVED => REOPENED
Resolution: DUPLICATE => (none)

*** Bug 317 has been marked as a duplicate of this bug. ***

Any news on this bug?

CC: (none) => marja11

we have a patch here https://bugs.mageia.org/show_bug.cgi?id=2194#c5
and it's confirmed that it's work here; https://bugs.mageia.org/show_bug.cgi?id=2902#c5

*** Bug 2902 has been marked as a duplicate of this bug. ***

CC: (none) => epistemepromeneur

Still don't work with KDE... and I have spent few hours on the problem.

1- /usr/bin/enable_X11_numlock don't work correctly.
    Usage : enable_X11_numlock [on|off|switch]
    on     - sets NumLock on in X (default) -> toggles as without argument.
    off    - sets NumLock off in X
    switch - changes NumLock state in X

2- /etc/X11/xinit.d/numlock is called too early.
    To verify, I have a added && play [a sound] after /usr/bin/enable_X11_numlock
    The numlock LED and the sound occur at the begining of the X session.

    If I rename /etc/X11/xinit.d/numlock in /etc/X11/xinit.d/xx_numlock then it
    is shown with ls after
        s2u
        xdg-user-dirs-update
        xdg-user-dirs-update-gtk
    and now it works.
    I have tried this with success on two machines with Mageia 1.

Reassign the bug to bugsquad. I will try to found maintainers of low level packages.

Assignee: dmorganec => bugsquad

(In reply to comment #11)
> Reassign the bug to bugsquad. I will try to found maintainers of low level
> packages.

@ Manuel
Do you still remember whom you asked and whom you didn't ask, yet?

I have ask to nobody :/

Maybe we should have a day/week to fix all bugs with the keyword PATCH and/or Junior_job...

(In reply to comment #13)
> I have ask to nobody :/
> 
> Maybe we should have a day/week to fix all bugs with the keyword PATCH and/or
> Junior_job...

Well, something to discuss in next meeting? :þ

@ Oliver

Maybe meanwhile you can give your vision about modifying the numlockx manpages or dropping them.

Feel free to put doc-bugs in the cc if that is needed

(In reply to comment #0)
...................
> 
> so I suggest we replace enable_X11_numlock by numlockx in our numlock package.
> WDYT?
> 
> we provide man page for enable_X11_numlock
> http://svnweb.mageia.org/soft/numlock/trunk/man/
> 
> numlockx doesn't provide any man pages. Should we modify our manpage for
> numlockx, or drop the manpages?
> 
> Version-Release number of selected component (if applicable):
> numlock-2.1.2-5.mga1.src.rpm

CC: (none) => oliver.bgr

I've uploaded in cauldron numlock-2.1.2-6.mga2: it includes the proposed changes in comment 0.

To all users affected by this bug and using cauldron: after removing all previous workarounds, please, could you test numlock-2.1.2-6.mga2 and report here the results.
Could you precise the desktop environment(s) you use to test (because various DE don't init exactly in the same way and in the same order).

I have installed a fresh Mageia2 alpha 3.
Numlock is working fine without any xorkaround.

So we can close this bugs ? (no to check for the other also related to numlock)

IMO, it can be closed!  
I hope this old bug definitively closed for Mageia (Mandriva has still 5 open bugs about numlock).

(In reply to comment #17)
> So we can close this bugs ?

nope, this bug was opened for cauldron mga 1, and is still valid in mga 1.
If the fix works fine with most of the desktop environments, I will make an update for mga1.

(In reply to comment #16)
> I have installed a fresh Mageia2 alpha 3.
> Numlock is working fine without any xorkaround.

1) what desktop environment(s) do you use to test?

2) if you call many times numlockx (in a terminal) does it always turn numlock on (= stay always numlocked), or does it switch the numlock (on, then off, then on, ...)?

Keywords: (none) => NEEDINFO
Version: Cauldron => 1

@ Pierre

Can you please answer Luc's questions in comment 19 ?

Now numlock works fine in Cauldron but nothing is changed for Mageia1.

One of my machines is running with the workaround in comment 10 : numlock is set.
Another machine is a pure and updated Mageia1 : numlock is unset.

Now numlock works fine in Cauldron but nothing is changed for Mageia1.

One of my machines is running with the workaround in comment 10 : numlock is set.
Another machine is a pure and updated Mageia1 : numlock is unset.

@ Pierre

Thanks for the feedback, but please answer Luc's questions in comment 19

I use 3 machines Intel with Mageia 1 x86_64 and the default configuration with all available updates.
I use kdm and KDE. Gnome is not installed.

The status of numlock follows this sequence at boot:
BIOS -  LED ON
Grub -  LED ON - When grub is closed, during few seconds, the LED is OFF
KDM  -  LED ON
When KDE starts, just after kdm, the LED is switched off
KDE  -  LED OFF

Each time I press the button NumLock, the state of the LED is inversed. The numpad works according the status indicated by the LED. 
Now, the LED indicates always the right state of the numpad.


Note: If I rename /etc/X11/xinit.d/numlock into xx_numlock, Numlock is switched OFF when KDM starts and ON when kdm launches KDE.

@ Pierre

Thx for answering Luc's questions :)

assigning to Luc

Keywords: NEEDINFO => (none)
Assignee: bugsquad => lmenut

3-monthly ping

@ Luc

Please set status to ASSIGNED if this bug was assigned correctly, or put "OK" on the whiteboard instead.

sorry for the delay, I don't have time currently, but I will try to prepare an update in coming weeks.

Luc

Keywords: PATCH => (none)
Status: REOPENED => ASSIGNED

I submitted numlock-2.1.2-5.1.mga1 in updates_testing.
update request: bug 6725.

regards,
Luc

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

Pierre Jarillon, could you test the update candidate given in bug 6725 (if you still happen to have a MGA1 64 bits system) and report if it fixes your problem?

Best regards

CC: (none) => stormi

I don't understand... On my mga1
$ rpm -qa "numlock*" said numlock-2.1.2-5.mga1 is installed

enable_X11_numlock is there and there is no numlockx as said in Bug 6725 

Now the numlock function seems to work fine. I have perhaps made a workaround but I can't found it again.

As you can see at http://mageia.madb.org/package/show/release/1/application/0/name/numlock the update candidate is numlock-2.1.2-5.1.mga1.i586.rpm in the core/updates_testing media

I mean, numlock-2.1.2-5.1.mga1.x86_64.rpm for mga1 64 bits