** Changed in: kdebase (Ubuntu)
Status: Invalid => New
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@li
I also encountered this bug, after upgrading Hardy -> Jaunty.
I compared the output of dpkg -L kdebase-bin on this upgraded machine,
to one which had Jaunty installed from scratch. Although the file list
from the upgraded machine includes:
/etc/X11/Xsession.d/80ubuntu-xmodmap
The freshly-inst
** Changed in: kdebase (Ubuntu)
Sourcepackagename: None => kdebase
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PRO
What is the status of this?
Also, the KDE keyboard changes are applied when KDE starts, i.e. after all the
X stuff.
** Changed in: kdebase (Ubuntu)
Status: New => Incomplete
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because y
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
I also experience this bug. However, renaming 80ubuntu-xmodmap to
999ubuntu-xmodmap does not remedy the problem for me. Is there some
other process that is stomping on the modmap later, something not in
/etc/X11/Xsession.d?
I'm running up-to-date hardy
--
xmodmap fails in Xsession.d
https://bugs
Unfortunately copying it so that it runs under both 80ubuntu-xmodmap and
999ubuntu-xmodmap also does not fix this for me. Perhaps there's
actually something else that you did that fixed the problem for you? I
also added "set -x" into my /etc/X11/Xsession just so that I could
actually *see* in .xess
Ok, after more searches and poking around I believe I have discovered
what is wiping out the xmodmap. I went into "Regional & Language ==>
Keyboard Layout" and then select the "Xkb Options" tab. I noticed a
checkbox on that tab: "Enable xkb options". The checkbox was checked,
but down below in the
** Changed in: kdebase (Ubuntu)
Sourcepackagename: None => kdebase
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PRO
What is the status of this?
Also, the KDE keyboard changes are applied when KDE starts, i.e. after all the
X stuff.
** Changed in: kdebase (Ubuntu)
Status: New => Incomplete
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because y
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
I also experience this bug. However, renaming 80ubuntu-xmodmap to
999ubuntu-xmodmap does not remedy the problem for me. Is there some
other process that is stomping on the modmap later, something not in
/etc/X11/Xsession.d?
I'm running up-to-date hardy
--
xmodmap fails in Xsession.d
https://bugs
Unfortunately copying it so that it runs under both 80ubuntu-xmodmap and
999ubuntu-xmodmap also does not fix this for me. Perhaps there's
actually something else that you did that fixed the problem for you? I
also added "set -x" into my /etc/X11/Xsession just so that I could
actually *see* in .xess
Ok, after more searches and poking around I believe I have discovered
what is wiping out the xmodmap. I went into "Regional & Language ==>
Keyboard Layout" and then select the "Xkb Options" tab. I noticed a
checkbox on that tab: "Enable xkb options". The checkbox was checked,
but down below in the
** Changed in: kdebase (Ubuntu)
Status: Invalid => New
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@li
I also encountered this bug, after upgrading Hardy -> Jaunty.
I compared the output of dpkg -L kdebase-bin on this upgraded machine,
to one which had Jaunty installed from scratch. Although the file list
from the upgraded machine includes:
/etc/X11/Xsession.d/80ubuntu-xmodmap
The freshly-inst
** Changed in: kdebase (Ubuntu)
Sourcepackagename: None => kdebase
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PRO
What is the status of this?
Also, the KDE keyboard changes are applied when KDE starts, i.e. after all the
X stuff.
** Changed in: kdebase (Ubuntu)
Status: New => Incomplete
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because y
I also experience this bug. However, renaming 80ubuntu-xmodmap to
999ubuntu-xmodmap does not remedy the problem for me. Is there some
other process that is stomping on the modmap later, something not in
/etc/X11/Xsession.d?
I'm running up-to-date hardy
--
xmodmap fails in Xsession.d
https://bugs
Unfortunately copying it so that it runs under both 80ubuntu-xmodmap and
999ubuntu-xmodmap also does not fix this for me. Perhaps there's
actually something else that you did that fixed the problem for you? I
also added "set -x" into my /etc/X11/Xsession just so that I could
actually *see* in .xess
Ok, after more searches and poking around I believe I have discovered
what is wiping out the xmodmap. I went into "Regional & Language ==>
Keyboard Layout" and then select the "Xkb Options" tab. I noticed a
checkbox on that tab: "Enable xkb options". The checkbox was checked,
but down below in the
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
What is the status of this?
Also, the KDE keyboard changes are applied when KDE starts, i.e. after all the
X stuff.
** Changed in: kdebase (Ubuntu)
Status: New => Incomplete
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because y
** Changed in: kdebase (Ubuntu)
Status: Invalid => New
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@li
I also encountered this bug, after upgrading Hardy -> Jaunty.
I compared the output of dpkg -L kdebase-bin on this upgraded machine,
to one which had Jaunty installed from scratch. Although the file list
from the upgraded machine includes:
/etc/X11/Xsession.d/80ubuntu-xmodmap
The freshly-inst
What is the status of this?
Also, the KDE keyboard changes are applied when KDE starts, i.e. after all the
X stuff.
** Changed in: kdebase (Ubuntu)
Status: New => Incomplete
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because y
I also experience this bug. However, renaming 80ubuntu-xmodmap to
999ubuntu-xmodmap does not remedy the problem for me. Is there some
other process that is stomping on the modmap later, something not in
/etc/X11/Xsession.d?
I'm running up-to-date hardy
--
xmodmap fails in Xsession.d
https://bugs
Unfortunately copying it so that it runs under both 80ubuntu-xmodmap and
999ubuntu-xmodmap also does not fix this for me. Perhaps there's
actually something else that you did that fixed the problem for you? I
also added "set -x" into my /etc/X11/Xsession just so that I could
actually *see* in .xess
Ok, after more searches and poking around I believe I have discovered
what is wiping out the xmodmap. I went into "Regional & Language ==>
Keyboard Layout" and then select the "Xkb Options" tab. I noticed a
checkbox on that tab: "Enable xkb options". The checkbox was checked,
but down below in the
** Changed in: kdebase (Ubuntu)
Sourcepackagename: None => kdebase
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PRO
** Changed in: kdebase (Ubuntu)
Sourcepackagename: None => kdebase
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PRO
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
I also experience this bug. However, renaming 80ubuntu-xmodmap to
999ubuntu-xmodmap does not remedy the problem for me. Is there some
other process that is stomping on the modmap later, something not in
/etc/X11/Xsession.d?
I'm running up-to-date hardy
--
xmodmap fails in Xsession.d
https://bugs
Unfortunately copying it so that it runs under both 80ubuntu-xmodmap and
999ubuntu-xmodmap also does not fix this for me. Perhaps there's
actually something else that you did that fixed the problem for you? I
also added "set -x" into my /etc/X11/Xsession just so that I could
actually *see* in .xess
Ok, after more searches and poking around I believe I have discovered
what is wiping out the xmodmap. I went into "Regional & Language ==>
Keyboard Layout" and then select the "Xkb Options" tab. I noticed a
checkbox on that tab: "Enable xkb options". The checkbox was checked,
but down below in the
** Changed in: kdebase (Ubuntu)
Status: Invalid => New
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@li
I also encountered this bug, after upgrading Hardy -> Jaunty.
I compared the output of dpkg -L kdebase-bin on this upgraded machine,
to one which had Jaunty installed from scratch. Although the file list
from the upgraded machine includes:
/etc/X11/Xsession.d/80ubuntu-xmodmap
The freshly-inst
** Changed in: kdebase (Ubuntu)
Status: Invalid => New
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@li
I also encountered this bug, after upgrading Hardy -> Jaunty.
I compared the output of dpkg -L kdebase-bin on this upgraded machine,
to one which had Jaunty installed from scratch. Although the file list
from the upgraded machine includes:
/etc/X11/Xsession.d/80ubuntu-xmodmap
The freshly-inst
What is the status of this?
Also, the KDE keyboard changes are applied when KDE starts, i.e. after all the
X stuff.
** Changed in: kdebase (Ubuntu)
Status: New => Incomplete
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because y
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
** Changed in: kdebase (Ubuntu)
Sourcepackagename: None => kdebase
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PRO
I also experience this bug. However, renaming 80ubuntu-xmodmap to
999ubuntu-xmodmap does not remedy the problem for me. Is there some
other process that is stomping on the modmap later, something not in
/etc/X11/Xsession.d?
I'm running up-to-date hardy
--
xmodmap fails in Xsession.d
https://bugs
Unfortunately copying it so that it runs under both 80ubuntu-xmodmap and
999ubuntu-xmodmap also does not fix this for me. Perhaps there's
actually something else that you did that fixed the problem for you? I
also added "set -x" into my /etc/X11/Xsession just so that I could
actually *see* in .xess
Ok, after more searches and poking around I believe I have discovered
what is wiping out the xmodmap. I went into "Regional & Language ==>
Keyboard Layout" and then select the "Xkb Options" tab. I noticed a
checkbox on that tab: "Enable xkb options". The checkbox was checked,
but down below in the
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
** Changed in: kdebase (Ubuntu)
Status: Invalid => New
--
xmodmap fails in Xsession.d
https://bugs.launchpad.net/bugs/251247
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@li
I also encountered this bug, after upgrading Hardy -> Jaunty.
I compared the output of dpkg -L kdebase-bin on this upgraded machine,
to one which had Jaunty installed from scratch. Although the file list
from the upgraded machine includes:
/etc/X11/Xsession.d/80ubuntu-xmodmap
The freshly-inst
On Friday, Aug 29th 2008 at 04:18 -, quoth Jens Jorgensen:
=>I also experience this bug. However, renaming 80ubuntu-xmodmap to
=>999ubuntu-xmodmap does not remedy the problem for me. Is there some
=>other process that is stomping on the modmap later, something not in
=>/etc/X11/Xsession.d?
=>
On Sunday, Aug 31st 2008 at 21:55 -, quoth Jens Jorgensen:
=>Ok, after more searches and poking around I believe I have discovered
=>what is wiping out the xmodmap. I went into "Regional & Language ==>
=>Keyboard Layout" and then select the "Xkb Options" tab. I noticed a
=>checkbox on that tab
On Friday, Aug 29th 2008 at 04:18 -, quoth Jens Jorgensen:
=>I also experience this bug. However, renaming 80ubuntu-xmodmap to
=>999ubuntu-xmodmap does not remedy the problem for me. Is there some
=>other process that is stomping on the modmap later, something not in
=>/etc/X11/Xsession.d?
=>
On Sunday, Aug 31st 2008 at 21:55 -, quoth Jens Jorgensen:
=>Ok, after more searches and poking around I believe I have discovered
=>what is wiping out the xmodmap. I went into "Regional & Language ==>
=>Keyboard Layout" and then select the "Xkb Options" tab. I noticed a
=>checkbox on that tab
On Friday, Aug 29th 2008 at 04:18 -, quoth Jens Jorgensen:
=>I also experience this bug. However, renaming 80ubuntu-xmodmap to
=>999ubuntu-xmodmap does not remedy the problem for me. Is there some
=>other process that is stomping on the modmap later, something not in
=>/etc/X11/Xsession.d?
=>
On Sunday, Aug 31st 2008 at 21:55 -, quoth Jens Jorgensen:
=>Ok, after more searches and poking around I believe I have discovered
=>what is wiping out the xmodmap. I went into "Regional & Language ==>
=>Keyboard Layout" and then select the "Xkb Options" tab. I noticed a
=>checkbox on that tab
On Friday, Aug 29th 2008 at 04:18 -, quoth Jens Jorgensen:
=>I also experience this bug. However, renaming 80ubuntu-xmodmap to
=>999ubuntu-xmodmap does not remedy the problem for me. Is there some
=>other process that is stomping on the modmap later, something not in
=>/etc/X11/Xsession.d?
=>
On Sunday, Aug 31st 2008 at 21:55 -, quoth Jens Jorgensen:
=>Ok, after more searches and poking around I believe I have discovered
=>what is wiping out the xmodmap. I went into "Regional & Language ==>
=>Keyboard Layout" and then select the "Xkb Options" tab. I noticed a
=>checkbox on that tab
On Friday, Aug 29th 2008 at 04:18 -, quoth Jens Jorgensen:
=>I also experience this bug. However, renaming 80ubuntu-xmodmap to
=>999ubuntu-xmodmap does not remedy the problem for me. Is there some
=>other process that is stomping on the modmap later, something not in
=>/etc/X11/Xsession.d?
=>
On Sunday, Aug 31st 2008 at 21:55 -, quoth Jens Jorgensen:
=>Ok, after more searches and poking around I believe I have discovered
=>what is wiping out the xmodmap. I went into "Regional & Language ==>
=>Keyboard Layout" and then select the "Xkb Options" tab. I noticed a
=>checkbox on that tab
On Friday, Aug 29th 2008 at 04:18 -, quoth Jens Jorgensen:
=>I also experience this bug. However, renaming 80ubuntu-xmodmap to
=>999ubuntu-xmodmap does not remedy the problem for me. Is there some
=>other process that is stomping on the modmap later, something not in
=>/etc/X11/Xsession.d?
=>
On Sunday, Aug 31st 2008 at 21:55 -, quoth Jens Jorgensen:
=>Ok, after more searches and poking around I believe I have discovered
=>what is wiping out the xmodmap. I went into "Regional & Language ==>
=>Keyboard Layout" and then select the "Xkb Options" tab. I noticed a
=>checkbox on that tab
60 matches
Mail list logo
