More release 2.3.0 problems
More release 2.3.0 problems
- Subject: More release 2.3.0 problems
- From: Tom Lane <email@hidden>
- Date: Tue, 22 Jul 2008 12:45:35 -0400
I installed 2.3.0 last night, but I'm about to revert back to 2.2.3,
because 2.3.0 has broken command-click :-(. Command key plus mouse
down in an X11 Tk window causes the expected right-mouse-button menu
to pop up for maybe a tenth of a second, and then go away again.
I need this often enough that I can't continue using 2.3.0.
Experimentation with xev proves that indeed a ButtonRelease event
is being sent immediately, even though my finger is still on the
trackpad button. (If it matters, this is an early-2008 Macbook Pro.)
Sent on command key down:
KeyPress event, serial 29, synthetic NO, window 0x1600001,
root 0x45, subw 0x0, time 1269108072, (102,85), root:(678,168),
state 0x0, keycode 63 (keysym 0xffe7, Meta_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
*All* of these are sent on click:
KeyRelease event, serial 29, synthetic NO, window 0x1600001,
root 0x45, subw 0x0, time 1269110401, (102,85), root:(678,168),
state 0x10, keycode 63 (keysym 0xffe7, Meta_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
ButtonPress event, serial 29, synthetic NO, window 0x1600001,
root 0x45, subw 0x0, time 1269110401, (102,85), root:(678,168),
state 0x0, button 3, same_screen YES
ButtonRelease event, serial 29, synthetic NO, window 0x1600001,
root 0x45, subw 0x0, time 1269110401, (102,85), root:(678,168),
state 0x400, button 3, same_screen YES
KeyPress event, serial 29, synthetic NO, window 0x1600001,
root 0x45, subw 0x0, time 1269110401, (102,85), root:(678,168),
state 0x0, keycode 63 (keysym 0xffe7, Meta_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
*Nothing* is sent on click release
Sent on command key up:
KeyRelease event, serial 29, synthetic NO, window 0x1600001,
root 0x45, subw 0x0, time 1269131129, (102,85), root:(678,168),
state 0x10, keycode 63 (keysym 0xffe7, Meta_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
Some other issues:
* very shortly after installing 2.3.0, I had a crash-like event wherein
all my X11 windows disappeared. I didn't get anything about "X11
unexpectedly quit", though, so I'm not sure if X11 actually died or if
it somehow interpreted what I was typing as a close-all-windows command.
(If there is such a keyboard shortcut, it seems like a really bad
idea...) I'm not the world's best typist so I can't swear as to what
I'd actually hit, but it was *intended* to be command-N to pop up a
new xterm window.
* Awhile after that I had a strange episode in which an xterm seemed to
be misbehaving in response to typed input. It was very late and I was
too tired to try to characterize the problem; it might have been just
pilot error, but it was not like anything I'd seen before. One thing I
remember is that it allowed text to be entered above the bottom line
of the window.
Sorry for not being clearer, but between this and Ralph Martin's
report it seems like 2.3.0 has some issues in input-event handling.
regards, tom lane
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden