Rolf Leggewie , Papercuts are supposed to be issue which are reproducible bugs
in all systems.
Apart from myself[tested in a laptop and desktop],
I'v confirmed with a couple of other members that this is not a bug affecting
all systems.
So i'm not pulling stuff out of thin air when i say , it
Thank you for bringing this bug to our attention. However, a paper cut
should be a small usability issue, in the default Ubuntu 9.10 install,
that affects many people and is quick and easy to fix. So this bug can't
be addressed as part of this project.
- This seems to be a hardware specific
Mac_v, the comments right above yours clearly state that this bug *does*
exist in Jaunty and Karmic.
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Rolf Leggewie, Oh! missed that...
But i'm unable to reproduce this problem. This seems hardware specific ,and
hardware specific issues are not papercuts.
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification
** Tags added: jaunty karmic
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
mac_v, may I kindly suggest you are more careful with your inferences?
There have been a number of theories about what specifically triggers
this bug. But your the first to suggest this may be a hardware-specific
issue. How did you come to that conclusion? How do you know for sure?
As you have
** Changed in: hundredpapercuts
Status: New = Confirmed
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
i have this exact problem on Jaunty.
During boot the LED is on the the numpad produces numbers.
this continues to the Gnome login screen (can login using the numpad
with the light still on).
Then as soon as i have logged in and ahve a desktop - the LED is off but
the numlock is actually on.
Using Karmic now, and the LED can be out of sync in certain situations.
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Same problem with debian/lenny ; numlockx 1.1-7 and icewm 1.2.35-1 :
async between leds status and real numlock status.
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are a member of Ubuntu
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Bug watch added: Debian Bug tracker #482592
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482592
** Also affects: numlockx (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482592
Importance: Unknown
Status: Unknown
** Tags added: numlockx
--
[hardy] numlockx
** Changed in: numlockx (Debian)
Status: Unknown = New
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Cipher_no1's fix also works for me (in Hardy) but ONLY if I install
numlockx FIRST.
Thanks, Cipher_no1.
mike
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are a member of Ubuntu
Bugs, which is
While I still have numlock issues here in Jaunty Gnome (bug 182421), at
least for me, the LED seems to be in sync with the real situation.
How is everybody else doing? If you are not on Jaunty, can you please
test with a live CD or USB?
--
[hardy] numlockx does not turn num lock keyboard light
While I still have numlock issues here in Jaunty Gnome (bug 182421), at
least for me, the LED seems to be in sync with the real situation.
How is everybody else doing? If you are not on Jaunty, can you please
test with a live CD or USB?
--
[hardy] numlockx does not turn num lock keyboard light
Confirmation here that it affects Kubuntu Hardy, using KDM as a manager,
and kde 3.5 (that is num pad works, starts in the right mode (on), but
the light is inverted); It worked in previous versions (and I followed
the upgrade route from previous versions, this is not a fresh install)
However,
The workaround posted by cprise on 2008-07-17 works for me. But I need
to reboot rather than only restart kdm to let it take effect. Thanks.
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are a
I see that the numlockx package is not working for me - I'm using Ubuntu
8.04.1 under LTSP - the thin-clients do not seem to see the '55numlockx'
script in /etc/X11/Xsession.d/ -- Just wanted to note that. I'm using
Gnome, not XFCE or KDE, and this is happening. My users all have
numbered
I am on Ubuntu (GDM/Gnome) Hardy Heron (upgraded from Gutsy). I confirm
that the Numlock LED has been operating opposite of the keypad behavior
on my machine since one of the last Hardy updates.
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
I can verify Wouter's experience: For KDE the NUMLOCK light operates
backwards or opposite the actual keypad behavior.
A workaround is to manually edit /etc/kde3/kdm/kdmrc and immediately
after [X-*-Greeter] add NumLock=On. Save and restart KDM.
--
[hardy] numlockx does not turn num lock
Sorry for misinformation in my previous comment. Editing
/etc/gdm/Init/Default is still needed, otherwise Num Lock won't
activate on log off.
However, I've noticed strange behaviour of led light with custom
rebuild (it turns off after pressing key after logging in). I will do
more research on this
I had the same issue than you using lxde with openbox in hardy on a Pentium II:
the Num Lock worked but the led did not work correctly.
I solved this issue in my system by just adding the following line at the end
of the /etc/init.d/rc.local file:
numlockx on
It seems that numlockx firstly
I can confirm this bug on Ubuntu (GDM/Gnome) Hardy (upgraded from Gutsy). I
didn't have this problem on Gutsy, it has appeared probably after few upgrades
on Hardy.
Rebuilding the numlockx package - as Martin-Éric recommends - fix this problem.
See eg. this page for how to:
Debian has an updated package which should be imported into Intrepid and
backported to Hardy.
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I see similar 'out of sync' behavior on two Kubuntu Hardy machines, both
updated from Gutsy. After a boot:
* the numlock LED is off
* the numpad is active
Pressing the numlock-button on the keyboard switches both: LED on,
numpad inactive...
I only have access to one of the machines at the
This package would need to be rebuilt against current X.org dependencies
to be fixed.
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In kubuntu hardy if num lock led is off numpad works, if num lock is on
numpad does not works.
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Just another confirmation on Kubuntu 8.04 with all the latest updates
Alfred
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This seems to be an XFCE4 -specific issue. Reassigning to xfce4
metapackage.
** Changed in: xfce4 (Ubuntu)
Sourcepackagename: numlockx = xfce4
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification because you are
This seems to be an XFCE4 -specific issue. Reassigning to xfce4
metapackage.
Martin-Eric, it would certainly be nice if you looked back more than 24
hours. Reversing your changes. This has absolutely nothing to do with
XFCE.
** Changed in: numlockx (Ubuntu)
Sourcepackagename: xfce4 =
I tried some more and while numlockx on/off does not change the LED in
any way, it does indeed toggle the numpad on and off.
The numlock key itself toggles both the LED and the function of the
numpad.
So, when starting with a computer that has the LED in sync with the real
state of the numpad
Rolf, I have looked at the whole thread. The point is, it works fine on
GNOME and, according to someone at work, also on KDE. So, yes, it is an
XFCE issue.
--
[hardy] numlockx does not turn num lock keyboard light on.
https://bugs.launchpad.net/bugs/218202
You received this bug notification
well, you haven't looked closely enough.
Take this hint: I don't use XFCE
BTW, comment 5 from darthanubis was a bit hard to read, so I will admit
that I overlooked that he, too, experiences this only on XFCE.
Removing triaged tag and setting to confirmed. It looks like we are not
100% sure
On Fri, May 2, 2008 at 4:32 PM, Rolf Leggewie wrote:
BTW, comment 5 from darthanubis was a bit hard to read, so I will admit
that I overlooked that he, too, experiences this only on XFCE.
Hence why I am veering towards blaming XFCE for skipping the X startup
script.
Removing triaged tag
Martin-Éric Racine wrote:
Hence why I am veering towards blaming XFCE for skipping the X startup
script.
I don't think that XFCE is skipping the startup script: After I
installed numlockx on Xubuntu, the numeric keypad did become functional
upon login--but the keyboard LED did not get lit.
It
On Fri, May 2, 2008 at 10:07 PM, luvr wrote:
Martin-Éric Racine wrote:
Hence why I am veering towards blaming XFCE for skipping the X startup
script.
The issue is that XCFE will not turn the keyboard LED on. You can easily
verify this by running the command numlockx on manually from a
Note: The same issue happens under Kubuntu (the KDE3 generation; haven't
tested with Kubuntu Remix yet).
Thus:
- Under Ubuntu (GNOME), numlockx handles the keyboard LED just fine;
- Under Xubuntu (xfce), numlockx will not control the LED; however, you can run
numlockx on from the
When are you guys going to listen?
- Under Ubuntu (GNOME), numlockx handles the keyboard LED just fine;
For you and apparently a number of other people, good for you. But this
is *NOT* generally the case, OK?
--
[hardy] numlockx does not turn num lock keyboard light on.
For me, numlockx *does* correctly handle the keyboard led, at least
under Ubuntu.
Under *Xubuntu* however, the led will NOT get lit. This has the rather strange
effect that:
- If I use numlockx to turn NumLock on, then the numeric keypad will become
functional, but the led will remain off;
- If
On Thu, 01 May 2008 18:56:19 -
luvr [EMAIL PROTECTED] wrote:
For me, numlockx *does* correctly handle the keyboard led, at least
under Ubuntu.
Under *Xubuntu* however, the led will NOT get lit. This has the
rather strange effect that:
- If I use numlockx to turn NumLock on, then the
The suggestion made by Cipher_no1 above, does work: Turning on NumLock from
/etc/gdm/Init/Default *will* turn on the keyboard LED.
Once the xfce environment is loaded, however, the numlockx utility will no
longer touch the LED.
For me, this is an acceptable work-around for this issue--NumLock
try this to have it auto start:
open a terminal window and type:
sudo gedit /etc/gdm/Init/Default
press enter
look for the line that says, “exit 0” and above this line add these
extra lines:
if [ -x /usr/bin/numlockx ]; then
/usr/bin/numlockx on
fi
save the file and close gedit. Next time
43 matches
Mail list logo
