not an X bug, reassigning
and my use case for getting "<|>" on an US layout is actually already
available via altgr-shift-{8,9,i}, so I don't need hacks anymore
but I think you can drop your custom layouts in /etc/X11/xkb(/symbols?),
clean up the cache in /var/lib/xkb and restart the server..
For anyone who is interested, i just made script version of Xmodmap
(e.g., xmodmap -e "code", then registered it as start up application. It
works great with my chromebook and crouton setup :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Hello,
Not sure if this is relevant, but my .Xmodmap is loaded (using "xmodmap
/home/$USER/.Xmodmap" in .xsessionrc) *only* when I’m logging into a TTY
shell (non graphical shell).
When I login to Mate/Unity, something, somewhere appears to be reversing
the Xmodmap instructions.
A work around
@Hélio, only thing I did was upgrade to 16.04 (clean install), copy my
xkb file over and load it (xkbcomp $HOME/.xkb/xkb-map $DISPLAY). That's
it.
Well, it *does* get loaded on each boot via .bashrc (as noted in post
14) when a terminal is auto-opened (put in startup prefs) so not sure it
will
Uriel,
it does not work for me.
Please, post the details of what you did.
Thank you.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1243642
Title:
.Xmodmap not automatically loaded
Bug is gone in 16.04!
.Xmodmap (which IS deprecated) still needs to be converted to xkb (post
14,
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1243642/comments/14),
but then everything works as before: keyboard map reloads automatically
after any number of suspend/hibernate cycles.
Alexander, the script I posted (#6) still working. I did not found any
other solution to this "feature". The evil is the gnome keyboard
configuration itself. As told in
https://bugzilla.gnome.org/show_bug.cgi?id=721873, this is not a bug,
but a side effect of using the gnome interface.
The script
@Nick: it is based on Debian all right. Only they added stuff on top that
overrides pre-existing things. I'm in exactly the same boat as you.
Xmodmap still works and it can be run from the startup applications, but
something else overrides the keymap immediately after executing the startup
I just switched to Ubuntu from Debian (using xfce not gnome). .Xmodmap
has worked on Debian since ... forever. I can't do without it. I thought
Ubuntu was based on Debian?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
My use case: remap the ALT and CMD keys on a Macbook so that I get the
ALT and SUPER keys on the place where I am used to find them on a
"normal" keyboard.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
this annoys me enough so that I want at least a somewhat hacky thing
installed by default..
usecase; remap a single key on US layout kbd so that I can use FI still
being able to get "<>|"
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this
Reading the bugzilla bug linked in #16, we are asked to not use gnome if
we want to be able to tweak one or the other key on our keyboard,
because they are not able to build a working UI on top of xmodmap. At
least this is what I read from it.
--
You received this bug notification because you
Suggest changing the title to “Need a per-user method of remapping keys
(.Xmodmap, .Xkbmap don't work)”
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1243642
Title:
.Xmodmap not
One thing to add (I'm shocked nobody mentioned yet): edits in anything
in /usr/... will be lost next time the respective package is updated.
So, even on single-user machines, a per-user (or at least /etc) option
is *needed*.
--
You received this bug notification because you are a member of
Modifying /usr/share/X11/xkb/symbols/pc has the side effect that SDL is
unable to recognize the keyboard layout, and most keys do not work in
SDL applications if a modified keymap is used.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I'm seeing the same behaviour after an upgrade from Precise to Trusty,
and it is disheartening to see that the bug was reported during an
upgrade between intermediate versions with very little traction. I've
added logic to my shell rc script to run xmodmap when I log in, but this
does not address
I concluded there are two solutions: swap to a different distro or to a
different method. I've resorted to the second, and am now tweaking with
xkb's infrastructure to arrive at the same remappings (caps becomes escape,
escape becomes caps, left alt becomes ctrl, left ctrl becomes alt). It is
more
There is a gnome ticket for this problem, please add your use cases
there:
https://bugzilla.gnome.org/show_bug.cgi?id=721873
** Bug watch added: GNOME Bug Tracker #721873
https://bugzilla.gnome.org/show_bug.cgi?id=721873
--
You received this bug notification because you are a member of
Well,
% find /usr/share/X11/xkb/ -type f|wc -l
273
there are 273 files in this folder a I would definitively need a whole
tutorial to change keyboard settings. My hunch is that changing xkb is a
developer's job, while .Xmodmap is just great to change these one or two
odd keys on the keyboard.
You are right. And though you don't have to change all of the 273 files
in there, it would be desireable for there to exist a user-level change
like was the case with .Xmodmap. I've seen a few explanations on the web
as to why Canonical would have wanted to break the old behavior, but
I'm still
Yes, different. Editing those system-level files affects keyboard
mapping for ALL users. But this bug is about .Xmodmap, which is
per-user. My post noted that even xkb maps are lost on suspend/sleep.
Converting .Xmodmap files to xkb is straightforward. After manually
loading the desired
I did it differently. I went about editing the relevant files in that
directory I mentioned in my other message.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1243642
Title:
.Xmodmap
Finally I got so fed up with gnome that I switched to XFCE and never
looked back. Despite all the other benefits I personally think it has,
.Xmodmap works as expected again, in particular also when waking up from
sleep.
--
You received this bug notification because you are a member of Desktop
I also got fed up, but adopted an alternative solution. I've migrated my
remappings to XKB. I plan to write out a tutorial explaining how to go
about using XKB to implement remappings. But who knows when... The internet
is, however, plenty of resources on how to go about it.
On Sat, Feb 28, 2015
I don't think we are talking about the same thing when we talk of XKB. To
clarify what I am talking about, I meant editing the files under
/usr/share/X11/xkb/
On Sat, Feb 28, 2015, 23:00 Uriel Tunz 1243...@bugs.launchpad.net
wrote:
This bug remains, and the problem is just as bad after
This bug remains, and the problem is just as bad after converting from
an .Xmodmap file to an xkb map: THE FILE MUST BE MANUALLY RELOADED ON
AWAKENING.
- A script in /etc/pm/sleep.d does not work.
- A script on the desktop does not work.
- Tearing hair out does not work.
Auto-loading the map
If you force the load of the .Xmodmap by adding the command 'xmodmap
~/.Xmodmap' in the Startup Applications, all is reverted if you
suspend/resume or if you change the user and get back etc. So I managed
to adapt some snippets I found, using the python dbus interface to
reissue the command when
man-year-wasting indeed :-(
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1243642
Title:
.Xmodmap not automatically loaded on start
Status in “xorg” package in Ubuntu:
Confirmed
Your work-around works because it doesn't rely on any modifications done
by /usr/sbin/lightdm-session where it loads the modifications found in
either ~/.Xkbmap or ~/.xmodmap. The modifications to the keyboard layout
found in these files are run, but are immediately reverted by some
other process
** Attachment removed: BootDmesg.txt
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1243642/+attachment/3888439/+files/BootDmesg.txt
** Attachment removed: BootLog.txt
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1243642/+attachment/3888440/+files/BootLog.txt
** Attachment
Hi,
Ryan gave me a hint, how to find a workaround without using ~/.Xmodmap.
I describe the solution of my specific problem here, so it might be
helpful for someone with a similar problem.
These links helped a lot:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1243642
32 matches
Mail list logo
