In my case it is the up-key that acts as printscreen. This means that I
can actually not use the up-key at all. In the console it behaves as
normal.
xev says this, but it might be cluttered by the start of me closing the
print-screen window with alt+f4:
PropertyNotify event, serial 32, synthetic NO, window 0x3e00001,
atom 0x169 (_NET_WM_ICON_GEOMETRY), time 4965659, state PropertyNewValue
FocusOut event, serial 33, synthetic NO, window 0x3e00001,
mode NotifyGrab, detail NotifyAncestor
FocusIn event, serial 33, synthetic NO, window 0x3e00001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 33, synthetic NO, window 0x0,
keys: 64 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
FocusOut event, serial 33, synthetic NO, window 0x3e00001,
mode NotifyNormal, detail NotifyNonlinear
PropertyNotify event, serial 33, synthetic NO, window 0x3e00001,
atom 0x169 (_NET_WM_ICON_GEOMETRY), time 4977254, state PropertyNewValue
--
SysReq keyboard key acts as Print Screen
https://bugs.launchpad.net/bugs/276056
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
