Bug 180146 - alt-up shortcut interferes with eclipse
Summary: alt-up shortcut interferes with eclipse
Status: RESOLVED FIXED
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-09 16:33 UTC by Luca Tettamanti
Modified: 2009-02-03 17:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luca Tettamanti 2009-01-09 16:33:06 UTC
Version:           4.1.86+svn902162 (using Devel)
OS:                Linux
Installed from:    Compiled sources

I'm currently testing SVN snapshot 4.1.86+svn902162 packages from kde42.debian.net.
I'm having troubles using the alt-up (move lines up) shortcut in eclipse 3.4; I saw that this combination is actually a predefined shortcut for "Up" under:

System Settings -> Keyboard & Mouse -> Standard Keyboard Shortcuts

I've set "Up" shortcut to "None" and restarted eclipse (and the whole KDE - just in case), but eclipse is still not reacting to the shortcut.
xev for alt-up show two strange (as in "I don't know where they come from")  grab/ungrab events:

KeyPress event, serial 34, synthetic NO, window 0x3000001,
    root 0x7e, subw 0x0, time 18986320, (40,-12), root:(1015,13),
    state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

FocusOut event, serial 34, synthetic NO, window 0x3000001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 34, synthetic NO, window 0x3000001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 34, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   0   1   0   0   0   0   4294967168 0   0
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

KeyRelease event, serial 34, synthetic NO, window 0x3000001,
    root 0x7e, subw 0x0, time 18986526, (40,-12), root:(1015,13),
    state 0x8, keycode 111 (keysym 0xff52, Up), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x3000001,
    root 0x7e, subw 0x0, time 18986590, (40,-12), root:(1015,13),
    state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

for comparison alt-down (which works as expected):

KeyPress event, serial 34, synthetic NO, window 0x3000001,
    root 0x7e, subw 0x0, time 19103897, (-705,574), root:(270,599),
    state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x3000001,
    root 0x7e, subw 0x0, time 19104020, (-705,574), root:(270,599),
    state 0x8, keycode 116 (keysym 0xff54, Down), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x3000001,
    root 0x7e, subw 0x0, time 19104084, (-705,574), root:(270,599),
    state 0x8, keycode 116 (keysym 0xff54, Down), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x3000001,
    root 0x7e, subw 0x0, time 19104177, (-705,574), root:(270,599),
    state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

Is it possible that somehow the shortcut hasn't been unset?
Comment 1 Dario Andres 2009-01-09 16:35:14 UTC
After a restart (the whole PC) the behaviour is still the same?
Comment 2 Luca Tettamanti 2009-01-12 15:32:10 UTC
(In reply to comment #1)
> After a restart (the whole PC) the behaviour is still the same?

Yes, situation is unchanged.
Comment 3 Luca Tettamanti 2009-02-03 17:57:01 UTC
I'm currently running KDE 4.2 (Debian/experimental) and the issue seems to be fixed (I didn't touch the configuration).
I'm marking the bug as fixed.