| Summary: | xmodmap in ~/.xinitrc not working anymore | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Konstantin Kletschke <konsti> |
| Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> |
| Status: | RESOLVED MOVED | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | normal | ||
| Priority: | high | CC: | brice.goglin, esigra, harri, konsti, mail |
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Bug Depends on: | |||
| Bug Blocks: | 16364 | ||
|
Description
Konstantin Kletschke
2007-09-22 09:16:29 UTC
Same problem reported by Henrik Enberg at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443044 and by Harald Dunkel at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443473 It could have been related to the server resetting after xmodmap is called from the startup script since there are no X clients anymore at this point, but Henrik said that passing -noreset to the server didn't help. On further thought, I've just updated it now, so please grab and test it again if you already got it before. Works for me. (patch applied to Debian's xorg-server_1.4-2, built on amd64) Pushed to master and my input fixes branch for 1.4, thanks. The proposed URL for patch gives 404 now... Yep, it was pushed into master as 27ad5d74c20f01516a1bff73be283f8982fcf0fe. I suppose this is a git bisect (or how this is called)... So instead of testing this I have to wait for this included in upstream because I have no experience with this. Okay, it's back at that URL now. Applied and fixes the problem :) good to hear. when the new package will come to debian unstable? thanks (In reply to comment #12) > when the new package will come to debian unstable? > thanks > it will be in 2:1.4-3 (next upload). (In reply to comment #13) > (In reply to comment #12) > > when the new package will come to debian unstable? > > thanks > > > it will be in 2:1.4-3 (next upload). > I upgraded the debian unstable packege, and I admit that .Xmodmap is loaded from .xinitrc and for example swapping of Ctrl and Caps_lock is ok, however now I have problems with polish letters iso-8859-2 (such as ąężó etc.). Namely if I don't load .Xmodmap from .xinitrc and load .Xmodmap manually, everything is ok, that is I have Ctrl and Caps_lock swapping and polish diacritics, but if I load .Xmodmap from .xinitrc, I cannot enter polish letters. Any idea? (In reply to comment #14) > (In reply to comment #13) > > (In reply to comment #12) > > > when the new package will come to debian unstable? > > > thanks > > > > > it will be in 2:1.4-3 (next upload). > > > I upgraded the debian unstable packege, and I admit that .Xmodmap is loaded > from .xinitrc and for example swapping of Ctrl and Caps_lock is ok, however now > I have problems with polish letters iso-8859-2 (such as ąężó etc.). Namely > if I don't load .Xmodmap from .xinitrc and load .Xmodmap manually, everything > is ok, that is I have Ctrl and Caps_lock swapping and polish diacritics, but if > I load .Xmodmap from .xinitrc, I cannot enter polish letters. Any idea? This looks like an instance of bug #16364 or #24552. It is back after updating from xorg-server-1.7.4 to xorg-server-1.7.4.901. Please tell me if it is okay to reopen this one instead of filing a new one... After reinstalling Debian Unstable the problem went away for me. Some local Hiccup I would guess. Painful workaround; http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584502#45 -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/356. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.