xmodmap fails in Xsession.d

Bug #251247 reported by Steven Orr
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I have a .Xmodmap in my $HOME. When I log in, the xmodmap command does not 'take'. I use my .Xmodmap to switch the CAPSLOCK and CTRL keys. I have worked around the problem by renaming 80ubuntu-xmodmap to 999ubuntu-xmodmap in /etc/X11/Xsession.d

root@vma-sorr3:/etc/X11/Xsession.d# dpkg -S 80ubuntu-xmodmap
kdebase-bin: /etc/X11/Xsession.d/80ubuntu-xmodmap
root@vma-sorr3:/etc/X11/Xsession.d#

Please let me know if I can provide more info.

Revision history for this message
Jens Jorgensen (jorgensen) wrote :

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

Revision history for this message
Steven Orr (steveo-syslang) wrote : Re: [Bug 251247] Re: xmodmap fails in Xsession.d

On Friday, Aug 29th 2008 at 04:18 -0000, 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?
=>
=>I'm running up-to-date hardy
=>

Instead of renaming, try copying. It seems to work if both are there.

:-(

cp 80ubuntu-xmodmap 999ubuntu-xmodmap

=>--
=>xmodmap fails in Xsession.d
=>https://bugs.launchpad.net/bugs/251247
=>You received this bug notification because you are a direct subscriber
=>of the bug.
=>
=>Status in ?kdebase? source package in Ubuntu: New
=>
=>Bug description:
=>I have a .Xmodmap in my $HOME. When I log in, the xmodmap command does not 'take'. I use my .Xmodmap to switch the CAPSLOCK and CTRL keys. I have worked around the problem by renaming 80ubuntu-xmodmap to 999ubuntu-xmodmap in /etc/X11/Xsession.d
=>
=>root@vma-sorr3:/etc/X11/Xsession.d# dpkg -S 80ubuntu-xmodmap
=>kdebase-bin: /etc/X11/Xsession.d/80ubuntu-xmodmap
=>root@vma-sorr3:/etc/X11/Xsession.d#
=>
=>Please let me know if I can provide more info.
=>

--
Time flies like the wind. Fruit flies like a banana. Stranger things have .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net

Revision history for this message
Jens Jorgensen (jorgensen) wrote :

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 .xession-errors that xmodmap is running for me. And indeed it is running just fine. I'm suspecting there is something in the kde stuff that is clobbering the xmodmap settings. Trouble is I'm not too sure how I could be able to trace through to get anything like that.

The "System Settings" does have a section for "X Modifier Mapping" so maybe when that is applied it wipes anything that's set instead of just merging in the settings? I don't see anything that would allow you to turn this off or anything to let you add your own.

The interesting thing for me is that I was using my own xmodmap to make it so my "multimedia keys" on my keyboard work. I noticed quite a while ago (though I don't remember exactly when unfortunately) these keys used to work and then just stopped. Well, once I started poking around with /etc/X11/Xsession.d I see that the 80ubuntu-xmodmap /already/ has the entries I need to turn on the volume up/down keys etc. So my belief is that there wasn't something that I broke but rather something in kubuntu (upstream, kde perhaps?) that "enhanced" its behavior and broke this feature.

Revision history for this message
Jens Jorgensen (jorgensen) wrote :

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 Xkb Options there were a whole slew of options to select but not a one of them was selected. So I unchecked the "Enable xkb options", logged out, logged back in, and voila! Now my xmodmap settings are back. I am fairly certain that I never went in and turned on the "Enable xkb options" box. This is especially annoying since no options were checked.

Since it seems that running setxkbmap will wipe out any xmodmap settings perhaps This should be run earlier, like in an earlier entry in Xsession.d?

Revision history for this message
Steven Orr (steveo-syslang) wrote :

On Sunday, Aug 31st 2008 at 21:55 -0000, 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: "Enable xkb options". The checkbox was checked,
=>but down below in the Xkb Options there were a whole slew of options to
=>select but not a one of them was selected. So I unchecked the "Enable
=>xkb options", logged out, logged back in, and voila! Now my xmodmap
=>settings are back. I am fairly certain that I never went in and turned
=>on the "Enable xkb options" box. This is especially annoying since no
=>options were checked.
=>
=>Since it seems that running setxkbmap will wipe out any xmodmap settings
=>perhaps This should be run earlier, like in an earlier entry in
=>Xsession.d?

I will give this a shot when I get back to my machine.

=>
=>--
=>xmodmap fails in Xsession.d
=>https://bugs.launchpad.net/bugs/251247
=>You received this bug notification because you are a direct subscriber
=>of the bug.
=>
=>Status in ?kdebase? source package in Ubuntu: New
=>
=>Bug description:
=>I have a .Xmodmap in my $HOME. When I log in, the xmodmap command does not 'take'. I use my .Xmodmap to switch the CAPSLOCK and CTRL keys. I have worked around the problem by renaming 80ubuntu-xmodmap to 999ubuntu-xmodmap in /etc/X11/Xsession.d
=>
=>root@vma-sorr3:/etc/X11/Xsession.d# dpkg -S 80ubuntu-xmodmap
=>kdebase-bin: /etc/X11/Xsession.d/80ubuntu-xmodmap
=>root@vma-sorr3:/etc/X11/Xsession.d#
=>
=>Please let me know if I can provide more info.
=>

--
steveo at syslang dot net TMMP1 http://frambors.syslang.net/
Do you have neighbors who are not frambors? Steven W. Orr

Revision history for this message
Harald Sitter (apachelogger) wrote :

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:
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

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 the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdebase:
status: Incomplete → Invalid
Changed in kdebase (Ubuntu):
status: Invalid → New
Revision history for this message
NickW (e-launchpad-wu-lee-noodlefactory-co-uk) wrote :

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-installed machine's did not.

I then tried removing /etc/X11/Xsession.d/80ubuntu-xmodmap, and reinstalling kdebase-bin, like this:

  sudo aptitude reinstall kdebase-bin

The file did not come back, and dpkg -L kdebase-bin now no longer included it!

The error from 80ubuntu-xmodmap which tipped me off to this, that reports that '/usr/share/apps/kxkb/ubuntu.xmodmap' could not be be found, has gone from my .xsession-errors log.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We no longer ship this modmap by default.

Changed in kdebase (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.