[openbox] 3.3 rc2---major bug!

Clay Barnes clay.barnes at gmail.com
Sun Oct 1 16:26:59 EDT 2006


On 9/30/06, Clay Barnes <clay.barnes at gmail.com> wrote:
> > > > > > On Fri, 29 Sep 2006, Clay Barnes wrote:
> > > > > > > I'm using 3.3, rc2, and I have an extensive set of keybindings in my
> > > > > > > rc.xml.  I developed them on an earlier version of OB, and I have not
> > > > > > > changed them in a while.  I upgraded OB, and now they are mostly
> > > > > > > disabled.  I think the thing all the disabled bindings have in common
> > > > > > > is they use the "Windows" (Meta4/Super) key.  I know the XML is valid,
> > > > > > > so I assume that either the syntax is broken or changed.  I'm
> > > > > > > attaching my rc.xml file in hopes that you can instruct me on how to
> > > > > > > fix the issue.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Clay
> > > > > > >
>
> > > > > On 9/29/06, Mikael Magnusson <mangosoft at comhem.se> wrote:
> > > > > > Please check that the output of "xmodmap" and what you get when you press
> > > > > > the win key in xev agree.
> > > > > >
> > > > > > For example on my computer:
> > > > > > % xmodmap
> > > > > > ...
> > > > > > mod4        Meta_L (0x73)
> > > > > >
> > > > > > % xev
> > > > > > ...
> > > > > > state 0x10, keycode 115 (keysym 0xffe7, Meta_L), same_screen YES,
> > > > > >
> > > > > > Also check if the state field changes when you hold down the win key while
> > > > > > pressing other keys, it should add 0x40 to whatever the value is without
> > > > > > it (at least that is what happens here).
> > > > > >
> > > > > > I would of course also suggest upgrading to the latest version but it
> > > > > > should be unrelated in this case.
>
> > > > On Fri, 29 Sep 2006, Clay Barnes wrote:
> > > > > This is what I'm getting from xev:
> > > > > state 0x10, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
> > > > >
> > > > > That is what I had before (I think), but is it no longer valid?
> > > > > Should I modify my xmodmap file?
> > > > >
> > > > > It seems to not be modifying my state.
> > > > >
> > > > > Ideas?
>
> > > On 9/29/06, Mikael Magnusson <mangosoft at comhem.se> wrote:
> > > > You only followed half of my suggestions, what I want to do is compare the
> > > > output of xev with the output of xmodmap.
> > > > But I also tried your rc.xml and noticed some warnings about
> > > > move/resizerelativehorz/vert actions, is it only them that don't work? Do
> > > > any bindings with the win key work for you? I'm not exactly sure why they
> > > > wouldn't work, but you can upgrade to 3.3.1 and use move/resizerelative
> > > > (no horz/vert) instead.
> > > >
>
> > On Fri, 29 Sep 2006, Clay Barnes wrote:
> > > Any function bound to the window key is broken.  No others are, however.
> > >
> > > I don't see what I skipped in your suggestions, though.  Do you want
> > > my xmodmap input file?  More context from my xev?  (I've gotten about
> > > 12 hours of sleep in the last week (literally), so I'm a bit
> > > intellectually sloppy at the moment).
>
> On 9/29/06, Mikael Magnusson <mangosoft at comhem.se> wrote:
> > In my original reply i said this:
> >
> > Please check that the output of "xmodmap" and what you get when you press
> > the win key in xev
> > agree.
> >
> > For example on my computer:
> > % xmodmap
> > ..
> > mod4        Meta_L (0x73)
> >
> > I'm not sure how it could be said any clearer. Of course, if you stopped
> > top posting I wouldn't have to throw away the whole thread every time.
> >
>
> 1)  Sorry about the top-posting.  I just got seriouslt flamed for
> *not* top posting somewhere else, and I let that "correction" slop
> into this list.  (for ease of reference I've reconstructed the
> exchange in this mail)
>
> 2)  My error in misreading "Please check that the output of "xmodmap"
> and what you get when you press the win key in xev agree." was to miss
> two words "Please check ___ the output of "xmodmap" and what you get
> when you press the win key in xev ____."  I'm a phrase reader, so when
> I have sub-consious expectations about what I'm about to read, I
> sometimes miss words that make it differ from that.
>
> 3)  I'll get the relevant (correct) information when I get home.  I'd
> test through ssh, but I don't have any systems capable of X tunneling
> at my girlfriend's house.
>
> 4)  I'd appreciate a friendly reminder of "no top posts!" or whatever
> is relevant next time I make a list faux pau.  I am perfectly capable
> of altering my behaviour before it becomes an accute issue.  (and if
> you look at my past postings, they are nearly always done correctly)
>

Here is the output of xmodmap -pm
0 ~ $ xmodmap -pm
xmodmap:  up to 3 keys per modifier, (keycodes in parentheses):

shift       Shift_L (0x32),  Shift_R (0x3e)
lock        Caps_Lock (0x42)
control     Control_L (0x25),  Control_R (0x6d)
mod1        Alt_L (0x40),  Alt_L (0x7d),  Meta_L (0x9c)
mod2        Num_Lock (0x4d)
mod3
mod4        Super_L (0x7f),  Hyper_L (0x80)
mod5        Mode_switch (0x5d),  ISO_Level3_Shift (0x7c)



Excerpt from the output of xmodmap -pk
0 ~ $ xmodmap -pk
...
    114    	
    115    	0xffeb (Super_L)	
    116    	0xffec (Super_R)	0xff20 (Multi_key)	
    117    	0xff67 (Menu)	
...

Output of the xev output of the sequence a-down, a-up, [Windows]-down,
[Windows]-up, [Windows]-down, a-down, a-up,[Windows]-up:

KeyPress event, serial 30, synthetic NO, window 0x1400001,
    root 0x44, subw 0x0, time 92595579, (284,-177), root:(285,683),
    state 0x0, keycode 38 (keysym 0x61, a), same_screen YES,
    XLookupString gives 1 bytes: (61) "a"
    XmbLookupString gives 1 bytes: (61) "a"
    XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x1400001,
    root 0x44, subw 0x0, time 92595747, (284,-177), root:(285,683),
    state 0x0, keycode 38 (keysym 0x61, a), same_screen YES,
    XLookupString gives 1 bytes: (61) "a"
    XFilterEvent returns: False

KeyPress event, serial 30, synthetic NO, window 0x1400001,
    root 0x44, subw 0x0, time 92598563, (284,-177), root:(285,683),
    state 0x0, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x1400001,
    root 0x44, subw 0x0, time 92598667, (284,-177), root:(285,683),
    state 0x0, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 30, synthetic NO, window 0x1400001,
    root 0x44, subw 0x0, time 92599882, (284,-177), root:(285,683),
    state 0x0, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 30, synthetic NO, window 0x1400001,
    root 0x44, subw 0x0, time 92600426, (284,-177), root:(285,683),
    state 0x0, keycode 38 (keysym 0x61, a), same_screen YES,
    XLookupString gives 1 bytes: (61) "a"
    XmbLookupString gives 1 bytes: (61) "a"
    XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x1400001,
    root 0x44, subw 0x0, time 92600570, (284,-177), root:(285,683),
    state 0x0, keycode 38 (keysym 0x61, a), same_screen YES,
    XLookupString gives 1 bytes: (61) "a"
    XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x1400001,
    root 0x44, subw 0x0, time 92601067, (284,-177), root:(285,683),
    state 0x0, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False


As you can see, the keycodes/keysyms match between xmodmap and xev.
However, for some reason my state field isn't changing.  Do you have
any idea what's up?

--Clay



More information about the openbox mailing list