Description of problem: Numlock not set on until after login. Version-Release number of selected component (if applicable): numlockx-1.2-2.fc17.x86_64 How reproducible: always Steps to Reproduce: 1. install Fedora-17-TC5-x86_64-DVD.iso, 2. log in innstall numlockx 3. http://www.my-guides.net/en/content/view/125/26/1/3/ yum install numlockx if [ -x /usr/bin/numlockx ]; then /usr/bin/numlockx on fi Save and exit. Now restart X server and check if num lock light is on. Actual results: numlock is set on after login Expected results: numlock on before log in Additional info: this is tow or tree weaks old in F17. This work in F17 - beta an in F10 to F16 See similar bug Bug 806947 - numlockx sets the num lock too late, it should run before gdm
Same problem with numlockx... I added if [ -x /usr/bin/numlockx ]; then /usr/bin/numlockx on fi in /etc/gdm/Init/Default as usual but it does not work with FC17 final.
The same.... Looks /etc/gdm/Init/Default does not start. Added following echo GDM Init Default>>/public/xxx /bin/logger GDM Init Default /bin/ps axjf>>/public/xxx /usr/bin/numlockx Nothing..... But, if to set SELinux=permisive everything works for me. Supose the problem is /etc/gdm/Init/Default does not start when SELinux is ENFORCE.
Same... I added if [ -x /usr/bin/numlockx ]; then /usr/bin/numlockx on fi in /etc/gdm/Init/Default as usual but it does not work with FC17
Same I am having exactly the same result in my F17.
I have no problem. I have followed earlier solution of installing of numlockx and editing /etc/gdm/Init/Default by way of adding at end if [ -x /usr/bin/numlockx ]; then /usr/bin/numlockx on fi and it works for me. I may state that i am using autologin and i have installed three interface( Gnome, Kde & Cinnamon). I wanted numlock on always and this served my purpose. One problem i noticed is when i logout for some reason and re-login, numlock was off. Not a big deal.
above applies to fedora17 32 bit (In my office comp) and fedfora17 64 bit (My home comp)
Hi I have CONFIRMED that this is a 'selinux' issue. If I put selinux to permissive the code referred to herein works. If I leave it to 'enforcing' it fails to put the numlock on at the login prompt. Could this bug be moved to 'selinux'? Thank you Robert
(In reply to comment #7) > Hi > I have CONFIRMED that this is a 'selinux' issue. If I put selinux to > permissive the code referred to herein works. If I leave it to 'enforcing' > it fails to put the numlock on at the login prompt. > Could this bug be moved to 'selinux'? Thank you > Robert Yes.
What avc messages are you seeing?
(In reply to comment #9) > What avc messages are you seeing? Sorry to whom are you directing this question?
Hello, I have looked at the problem: here the responsible AVC (I presume): type=AVC msg=audit(1343118306.360:84): avc: denied { search } for pid=746 comm="gdm-simple-slav" name="Init" dev="sda1" ino=30991 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:xdm_unconfined_exec_t:s0 tclass=dir For the inode: # ll -i /etc/gdm/Init/ -d 30991 drwxr-xr-x. 2 root root 4096 2 juil. 17:04 /etc/gdm/Init/ # ll -Z /etc/gdm/Init/ -d drwxr-xr-x. root root system_u:object_r:xdm_unconfined_exec_t:s0 /etc/gdm/Init/ So, it looks like gdm cannot read its initialisation directory.
Works in F18 RC2 live.
(In reply to comment #12) > Works in F18 RC2 live. Yes, We added fixes. Thanks for testing.
i have the same problem, numlock doesn't start in GDM