Bug 2902 - for every kde session numlock is off
Summary: for every kde session numlock is off
Status: RESOLVED DUPLICATE of bug 1136
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-02 11:43 CEST by episteme promeneur
Modified: 2011-10-16 01:18 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description episteme promeneur 2011-10-02 11:43:10 CEST
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. at kdm template numlock is on
2. open a kde session
3. numlock is off

this is true for every kde session
Comment 1 D Morgan 2011-10-02 11:44:42 CEST
is the numlock rpm installed ?

CC: (none) => dmorganec

Comment 2 episteme promeneur 2011-10-02 12:01:57 CEST
yes the 2.1.2-5
Comment 3 Manuel Hiebel 2011-10-02 12:38:49 CEST
maybe related to bug 1136, bug 1099 or bug 2194
Comment 4 episteme promeneur 2011-10-02 13:52:19 CEST
here is the contents of /etc/X11/Giveconsole

#!/bin/sh
# Assign ownership of the console to the invoking user
# $XConsortium: GiveConsole,v 1.2 93/09/28 14:29:20 gildea Exp $
#
# By convention, both xconsole and xterm -C check that the
# console is owned by the invoking user and is readable before attaching
# the console output.  This way a random user can invoke xterm -C without
# causing serious grief.
#
chown $USER /dev/console
Comment 5 episteme promeneur 2011-10-02 14:02:11 CEST
i add in giveconsole

if [ -x /etc/X11/xinit.d/numlock ]; then
    /etc/X11/xinit.d/numlock &
fi

there si no more problem
Comment 6 Manuel Hiebel 2011-10-16 01:18:09 CEST
(In reply to comment #5)
> i add in giveconsole
> 
> if [ -x /etc/X11/xinit.d/numlock ]; then
>     /etc/X11/xinit.d/numlock &
> fi
> 
> there si no more problem

ok thanks, so closing as duplicate

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

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


Note You need to log in before you can comment on or make changes to this bug.