** Changed in: numlockx (Ubuntu)
Status: Fix Committed = Fix Released
--
Deinstalling numlockx breaks X startup
https://bugs.launchpad.net/bugs/116528
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
David, did you get a chance to try either of the above solutions?
--
Deinstalling numlockx breaks X startup
https://bugs.launchpad.net/bugs/116528
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
It booted just fine with
if test -x /usr/bin/numlockx; then
/usr/bin/numlockx on
fi
which sems to be the best solution to me (clear and readable, without
side effects).
--
Deinstalling numlockx breaks X startup
https://bugs.launchpad.net/bugs/116528
You received this bug notification because
Fixed as of Debian 1.1-6 (should spread into Gutsy fairly soon).
** Changed in: numlockx (Ubuntu)
Assignee: (unassigned) = Martin-Éric Racine
Status: Unconfirmed = Fix Committed
--
Deinstalling numlockx breaks X startup
https://bugs.launchpad.net/bugs/116528
You received this bug
Actually, removal only removes binaries. Purge is what also removes
configuration files and scripts. Anyhow, the script tests for the
presence of numlockx, before trying to execute it, so I really don't see
how this could be happening.
--
Deinstalling numlockx breaks X startup
On Thursday 24 May 2007, Martin-Éric Racine wrote:
Actually, removal only removes binaries. Purge is what also removes
configuration files and scripts. Anyhow, the script tests for the
presence of numlockx, before trying to execute it, so I really don't see
how this could be happening.
That's
Does adding || before the true statement fix it for you?
Here, I modified the content of the script to:
( test -x /usr/bin/numlockx /usr/bin/numlockx on ) || /bin/true
This works for me. Can you confirm whether it fixes the issue for you?
--
Deinstalling numlockx breaks X startup
On Thursday 24 May 2007, Martin-Éric Racine wrote:
Does adding || before the true statement fix it for you?
Here, I modified the content of the script to:
( test -x /usr/bin/numlockx /usr/bin/numlockx on ) || /bin/true
This works for me. Can you confirm whether it fixes the issue for
I can wait until you get home and have a few minutes to test this,
before uploading. :)
--
Deinstalling numlockx breaks X startup
https://bugs.launchpad.net/bugs/116528
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Of course, an even safer way to implement this could be:
if [ -x /usr/bin/numlockx ]; then /usr/bin/numlockx on; fi
I'm curious as to which one is preferable. Feedback on this issue is
welcome.
--
Deinstalling numlockx breaks X startup
https://bugs.launchpad.net/bugs/116528
You received this
Bug report wizard didn't ask me, but this is about kubuntu edgy, I
haven't upgraded that machine to feisty yet.
--
Deinstalling numlockx breaks X startup
https://bugs.launchpad.net/bugs/116528
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
11 matches
Mail list logo
