"Alt" key is "Alt Window Deactivated" #33831

Closed
opened 2013-01-11 10:58:31 +01:00 by Jeroen Bakker · 40 comments
Member

%%%--- Operating System, Graphics card ---

Linux 12.04, Laptop with US keyboard

- Blender version with error, and version that worked ---

2.65a works as expected. Trunk fails.

- Short description of error ---

Pressing Alt-A does nothing, Shift-Alt-A does reverse playback. When going into the preferences and reset the Play animation key to Alt-A the text "Alt Window Deactivated - A" appears. Even now animation playback does not work.

Tried a clean build. Restored factory settings, but Alt key is not working.

My keyboard layout Has Alt to the left and Alt-GR to the right of the spacebar.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

Start Blender.
Press Alt-A.

It has been reported that commit 53658 breaks the Alt-key%%%

%%%--- Operating System, Graphics card --- Linux 12.04, Laptop with US keyboard - Blender version with error, and version that worked --- 2.65a works as expected. Trunk fails. - Short description of error --- Pressing Alt-A does nothing, Shift-Alt-A does reverse playback. When going into the preferences and reset the Play animation key to Alt-A the text "Alt Window Deactivated - A" appears. Even now animation playback does not work. Tried a clean build. Restored factory settings, but Alt key is not working. My keyboard layout Has Alt to the left and Alt-GR to the right of the spacebar. - Steps for others to reproduce the error (preferably based on attached .blend file) --- Start Blender. Press Alt-A. It has been reported that commit 53658 breaks the Alt-key%%%
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Member

%%%There must be a program sending de-activate events to windows... which is of course very bad.
If that's common in linux installs we should look for a bypass hack.

ALT+A is reportedly to work fine for many linux users.%%%

%%%There must be a program sending de-activate events to windows... which is of course very bad. If that's common in linux installs we should look for a bypass hack. ALT+A is reportedly to work fine for many linux users.%%%

%%%Could this be todo with the window manager? - using Sawfish here and Alt+A works, could you try see if another window manager works? (Openbox or TWM for eg).%%%

%%%Could this be todo with the window manager? - using Sawfish here and Alt+A works, could you try see if another window manager works? (Openbox or TWM for eg).%%%
Member

%%%One user in irc said his Unity plugin was doing it ... unconfirmed, and confusing mesage...%%%

%%%One user in irc said his Unity plugin was doing it ... unconfirmed, and confusing mesage...%%%
Author
Member

%%%I use Unity3d on Ubuntu 12.04.

Shift-Alt-A works, Alt-Shift-A does not.

Unity3d renders by default the application menu outside the application window (just like a mac on top of the screen). Pressing Alt looses focus to the application window and the focus is received by the application menu. This is normal behaviour in Unity3d and some other windowmanager.

Blender does not has its Application Menu made public to the OS. I wouldn't say this is a Blender issue, but more a Linux issue.
I would suggest to add a user preference to eliminate the alt=0 assignment in the commit. because it is complicated to turn this feature off in a default installation of ubuntu. (additional packages needs to be installed for it).%%%

%%%I use Unity3d on Ubuntu 12.04. Shift-Alt-A works, Alt-Shift-A does not. Unity3d renders by default the application menu outside the application window (just like a mac on top of the screen). Pressing Alt looses focus to the application window and the focus is received by the application menu. This is normal behaviour in Unity3d and some other windowmanager. Blender does not has its Application Menu made public to the OS. I wouldn't say this is a Blender issue, but more a Linux issue. I would suggest to add a user preference to eliminate the alt=0 assignment in the commit. because it is complicated to turn this feature off in a default installation of ubuntu. (additional packages needs to be installed for it).%%%
Member

%%%It was especially for ALT that this was added.
Bug was that ALT was hanging on window-deactivates, and then gets handled for scrollwheels in inactive windows on mouse-over. (changing values)

Are you using Unity3d (game engine) or the Unity desktop environment?

If its the Unity desktop, it should just not send window-deactivates for this topbar. Many more programs would run badly wich such a hack.%%%

%%%It was especially for ALT that this was added. Bug was that ALT was hanging on window-deactivates, and then gets handled for scrollwheels in inactive windows on mouse-over. (changing values) Are you using Unity3d (game engine) or the Unity desktop environment? If its the Unity desktop, it should just not send window-deactivates for this topbar. Many more programs would run badly wich such a hack.%%%

%%%In compizconfig-settings-manager go to Ubuntu Unity Plugin, deactivate Key to show the HUB or assign another short cut.%%%

%%%In compizconfig-settings-manager go to Ubuntu Unity Plugin, deactivate Key to show the HUB or assign another short cut.%%%
Member

%%%Why do you call it a plugin, isnt Unity the name of the desktop environment? Is this optional, default?%%%

%%%Why do you call it a plugin, isnt Unity the name of the desktop environment? Is this optional, default?%%%
Author
Member

%%%Unity3d is the default desktop manager of Ubuntu. It is based on the GNome and Compiz (an OpenGL compositing manager that enhanced the desktop with OpenGL goodies).

From the settings manager it is called a plugin. Since Ubuntu 12.04 it is mandatory. If you run a default installation of Ubuntu (like installed on the workstation at BI) the Alt key sends Window deactivated events. If we are not going to fix this. We should make it a big bullet in the release notes otherwise All Ubuntu users will start to complain. We should also send a bug report to Ubuntu/compiz.

The option I proposed (user settings) will only be a temporarily solution until it gets fixed by them.%%%

%%%Unity3d is the default desktop manager of Ubuntu. It is based on the GNome and Compiz (an OpenGL compositing manager that enhanced the desktop with OpenGL goodies). From the settings manager it is called a plugin. Since Ubuntu 12.04 it is mandatory. If you run a default installation of Ubuntu (like installed on the workstation at BI) the Alt key sends Window deactivated events. If we are not going to fix this. We should make it a big bullet in the release notes otherwise All Ubuntu users will start to complain. We should also send a bug report to Ubuntu/compiz. The option I proposed (user settings) will only be a temporarily solution until it gets fixed by them.%%%
Member

%%%I would rather see someone checking the X11 event stream in Ghost, to see if this de-activate event has special properties we can catch.

Another hack could be to not send de-activates, if the previous event was an ALT.
Such errors should be tackled as close as possible to the source, not inside the Blender UI.%%%

%%%I would rather see someone checking the X11 event stream in Ghost, to see if this de-activate event has special properties we can catch. Another hack could be to not send de-activates, if the previous event was an ALT. Such errors should be tackled as close as possible to the source, not inside the Blender UI.%%%
Member

%%%BTW!

this is Unity: http://unity.ubuntu.com/
this is Unity3d: http://www.unity3d.com/

Both are commonly used in Blender world. :) Let's not confuse ourselves even more!%%%

%%%BTW! this is Unity: http://unity.ubuntu.com/ this is Unity3d: http://www.unity3d.com/ Both are commonly used in Blender world. :) Let's not confuse ourselves even more!%%%

%%%Committed fix r53798. thanks to Patrick Zulke%%%

%%%Committed fix r53798. thanks to Patrick Zulke%%%

%%%Reopening, r53798 caused bug [#33921]%%%

%%%Reopening, r53798 caused bug [#33921]%%%
Author
Member

%%%Yes, I can reproduce the issue. (linux64 ubuntu 12.04 unity desktop manager)
%%%

%%%Yes, I can reproduce the issue. (linux64 ubuntu 12.04 unity desktop manager) %%%
Member

%%%Come on Linux devs, this is really not hard to fix! Just add an Altkey keypress exception in Ghost X11 that swallows the two "de-activate/activate" events that follow immediate after.

Then submit an angry report at Ubuntu tracker for such an abusive bad coded feature.%%%

%%%Come on Linux devs, this is really not hard to fix! Just add an Altkey keypress exception in Ghost X11 that swallows the two "de-activate/activate" events that follow immediate after. Then submit an angry report at Ubuntu tracker for such an abusive bad coded feature.%%%

%%%I have a new patch that simply breaks on FocusOut events (on ubuntu 12.10). I've tested against #33921, #33831, #33992 and all are resolved. To date haven't found any breakage on blenders side and Alt key behaviour on unity's side in "normal" and "llvm-pipe" mode also works as expected (Alt-tap, Alt-Tab, Ctl-Alt-Arrowkeys, etc). I don't know if anything breaks on other linux/wm systems because i can't test other systems atm for technical reasons (broken MBR). Also regarding #33921, i couldn't reproduce that one with my initial patch (r53798) with mentioned system.

Obviously this needs testing on other X11 system combo's so i've attached the diff. If the problem persists i'm willing to dig deeper into this matter (along the course Ton mentioned regarding swallowing events on Alt)

%%%

%%%I have a new patch that simply breaks on FocusOut events (on ubuntu 12.10). I've tested against #33921, #33831, #33992 and all are resolved. To date haven't found any breakage on blenders side and Alt key behaviour on unity's side in "normal" and "llvm-pipe" mode also works as expected (Alt-tap, Alt-Tab, Ctl-Alt-Arrowkeys, etc). I don't know if anything breaks on other linux/wm systems because i can't test other systems atm for technical reasons (broken MBR). Also regarding #33921, i couldn't reproduce that one with my initial patch (r53798) with mentioned system. Obviously this needs testing on other X11 system combo's so i've attached the diff. If the problem persists i'm willing to dig deeper into this matter (along the course Ton mentioned regarding swallowing events on Alt) %%%

%%%for some reason attach doesn't work for me so here is pasteall link

http://www.pasteall.org/39155%%%

%%%for some reason attach doesn't work for me so here is pasteall link http://www.pasteall.org/39155%%%
Member

%%%Patrick, your patch seems to disturb XIM's FocusIn/Out event handling.
After FocusOut and FocusIn, IBus indicator doesn't work and IBus conversion window doesn't appear.
%%%

%%%Patrick, your patch seems to disturb XIM's FocusIn/Out event handling. After FocusOut and FocusIn, IBus indicator doesn't work and IBus conversion window doesn't appear. %%%

%%%Ok, thank you for testing. Will investigate further then%%%

%%%Ok, thank you for testing. Will investigate further then%%%

%%%irie, would you try this please?

This patch executes the xim specific code before breaking out off event. Still works for me that way, really hope it works for you.

pasteall -> http://www.pasteall.org/39156%%%

%%%irie, would you try this please? This patch executes the xim specific code before breaking out off event. Still works for me that way, really hope it works for you. pasteall -> http://www.pasteall.org/39156%%%
Member

%%%At least the second patch doesn't affect XIM behavior, though it's still a bit strange.

I'm not sure if the XIM behavior can be corrected on Blender's side...
%%%

%%%At least the second patch doesn't affect XIM behavior, though it's still a bit strange. I'm not sure if the XIM behavior can be corrected on Blender's side... %%%
Member

%%%Window focus in and out are important events, and should always be passed on, except for the case it follows an ALT key press.
I haven't investigated the queue for X11 though, but my impression was that on ALT press, immediately two events (focus in, out) follow.%%%

%%%Window focus in and out are important events, and should always be passed on, except for the case it follows an ALT key press. I haven't investigated the queue for X11 though, but my impression was that on ALT press, immediately two events (focus in, out) follow.%%%
Member

%%%I got the X event logs.

(1) Alt+A

FocusOut event, serial 26, synthetic NO, window 0x5e00002,

  mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 26, synthetic NO, window 0x5e00002,

  mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 26, synthetic NO, window 0x5e00002,

  mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 26, synthetic NO, window 0x0,

  keys:  4294967200 0   0   0   0   0   0   0   1   0   0   0   0   0   0   0   
       0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

KeyRelease event, serial 26, synthetic NO, window 0x5e00002,

  root 0x2a0, subw 0x0, time 25462702, (548,610), root:(4437,634),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

KeyPress event, serial 26, synthetic NO, window 0x5e00002,

  root 0x2a0, subw 0x0, time 25462702, (548,610), root:(4437,634),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

FocusOut event, serial 26, synthetic NO, window 0x5e00002,

  mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 26, synthetic NO, window 0x5e00002,

  mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 26, synthetic NO, window 0x5e00002,

  mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 26, synthetic NO, window 0x0,

  keys:  4294967200 0   0   0   64  0   0   0   1   0   0   0   0   0   0   0   
       0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

KeyRelease event, serial 26, synthetic NO, window 0x5e00002,

  root 0x2a0, subw 0x0, time 25462894, (548,610), root:(4437,634),
  state 0x18, keycode 38 (keysym 0x61, a), same_screen YES,
  XLookupString gives 1 bytes: (61) "a"
  XFilterEvent returns: False

KeyPress event, serial 26, synthetic NO, window 0x5e00002,

  root 0x2a0, subw 0x0, time 25462894, (548,610), root:(4437,634),
  state 0x18, 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 26, synthetic NO, window 0x5e00002,

  root 0x2a0, subw 0x0, time 25463030, (548,610), root:(4437,634),
  state 0x18, keycode 38 (keysym 0x61, a), same_screen YES,
  XLookupString gives 1 bytes: (61) "a"
  XFilterEvent returns: False

KeyRelease event, serial 26, synthetic NO, window 0x5e00002,

  root 0x2a0, subw 0x0, time 25463054, (548,610), root:(4437,634),
  state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

(2) Alt + Ctrl + right (actual focus out)

KeyRelease event, serial 24, synthetic NO, window 0x5e00002,

  root 0x2a0, subw 0x0, time 26119878, (465,303), root:(4354,327),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

KeyPress event, serial 24, synthetic NO, window 0x5e00002,

  root 0x2a0, subw 0x0, time 26119878, (465,303), root:(4354,327),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

KeyRelease event, serial 24, synthetic NO, window 0x5e00002,

  root 0x2a0, subw 0x0, time 26119878, (465,303), root:(4354,327),
  state 0x18, keycode 102 (keysym 0xffe3, Control_L), same_screen YES,
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

KeyPress event, serial 24, synthetic NO, window 0x5e00002,

  root 0x2a0, subw 0x0, time 26119878, (465,303), root:(4354,327),
  state 0x18, keycode 102 (keysym 0xffe3, Control_L), same_screen YES,
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

FocusOut event, serial 24, synthetic NO, window 0x5e00002,

  mode NotifyGrab, detail NotifyAncestor

LeaveNotify event, serial 24, synthetic NO, window 0x5e00002,

  root 0x2a0, subw 0x0, time 26120177, (465,303), root:(4354,327),
  mode NotifyGrab, detail NotifyNonlinear, same_screen YES,
  focus YES, state 28

ConfigureNotify event, serial 24, synthetic YES, window 0x5e00002,

  event 0x5e00002, window 0x5e00002, (-1871,24), width 1871, height 1056,
  border_width 0, above 0xfde776, override NO

FocusOut event, serial 24, synthetic NO, window 0x5e00002,

  mode NotifyWhileGrabbed, detail NotifyNonlinear

PropertyNotify event, serial 24, synthetic NO, window 0x5e00002,

  atom 0x160 (_NET_WM_STATE), time 26120780, state PropertyNewValue

PropertyNotify event, serial 24, synthetic NO, window 0x5e00002,

  atom 0x157 (_NET_FRAME_EXTENTS), time 26120780, state PropertyNewValue

PropertyNotify event, serial 24, synthetic NO, window 0x5e00002,

  atom 0x1c6 (_NET_WM_ICON_GEOMETRY), time 26120782, state PropertyNewValue

In the case (1), successive FocusOut-FocusOut events can be translated to single FocusOut event, and FocusOut-FocusIn events can be discarded.
%%%

%%%I got the X event logs. (1) Alt+A FocusOut event, serial 26, synthetic NO, window 0x5e00002, ``` mode NotifyGrab, detail NotifyAncestor ``` FocusOut event, serial 26, synthetic NO, window 0x5e00002, ``` mode NotifyUngrab, detail NotifyPointer ``` FocusIn event, serial 26, synthetic NO, window 0x5e00002, ``` mode NotifyUngrab, detail NotifyAncestor ``` KeymapNotify event, serial 26, synthetic NO, window 0x0, ``` keys: 4294967200 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 ``` 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 KeyRelease event, serial 26, synthetic NO, window 0x5e00002, ``` root 0x2a0, subw 0x0, time 25462702, (548,610), root:(4437,634), state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ``` KeyPress event, serial 26, synthetic NO, window 0x5e00002, ``` root 0x2a0, subw 0x0, time 25462702, (548,610), root:(4437,634), state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False ``` FocusOut event, serial 26, synthetic NO, window 0x5e00002, ``` mode NotifyGrab, detail NotifyAncestor ``` FocusOut event, serial 26, synthetic NO, window 0x5e00002, ``` mode NotifyUngrab, detail NotifyPointer ``` FocusIn event, serial 26, synthetic NO, window 0x5e00002, ``` mode NotifyUngrab, detail NotifyAncestor ``` KeymapNotify event, serial 26, synthetic NO, window 0x0, ``` keys: 4294967200 0 0 0 64 0 0 0 1 0 0 0 0 0 0 0 ``` 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 KeyRelease event, serial 26, synthetic NO, window 0x5e00002, ``` root 0x2a0, subw 0x0, time 25462894, (548,610), root:(4437,634), state 0x18, keycode 38 (keysym 0x61, a), same_screen YES, XLookupString gives 1 bytes: (61) "a" XFilterEvent returns: False ``` KeyPress event, serial 26, synthetic NO, window 0x5e00002, ``` root 0x2a0, subw 0x0, time 25462894, (548,610), root:(4437,634), state 0x18, 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 26, synthetic NO, window 0x5e00002, ``` root 0x2a0, subw 0x0, time 25463030, (548,610), root:(4437,634), state 0x18, keycode 38 (keysym 0x61, a), same_screen YES, XLookupString gives 1 bytes: (61) "a" XFilterEvent returns: False ``` KeyRelease event, serial 26, synthetic NO, window 0x5e00002, ``` root 0x2a0, subw 0x0, time 25463054, (548,610), root:(4437,634), state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ``` (2) Alt + Ctrl + right (actual focus out) KeyRelease event, serial 24, synthetic NO, window 0x5e00002, ``` root 0x2a0, subw 0x0, time 26119878, (465,303), root:(4354,327), state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ``` KeyPress event, serial 24, synthetic NO, window 0x5e00002, ``` root 0x2a0, subw 0x0, time 26119878, (465,303), root:(4354,327), state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False ``` KeyRelease event, serial 24, synthetic NO, window 0x5e00002, ``` root 0x2a0, subw 0x0, time 26119878, (465,303), root:(4354,327), state 0x18, keycode 102 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ``` KeyPress event, serial 24, synthetic NO, window 0x5e00002, ``` root 0x2a0, subw 0x0, time 26119878, (465,303), root:(4354,327), state 0x18, keycode 102 (keysym 0xffe3, Control_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False ``` FocusOut event, serial 24, synthetic NO, window 0x5e00002, ``` mode NotifyGrab, detail NotifyAncestor ``` LeaveNotify event, serial 24, synthetic NO, window 0x5e00002, ``` root 0x2a0, subw 0x0, time 26120177, (465,303), root:(4354,327), mode NotifyGrab, detail NotifyNonlinear, same_screen YES, focus YES, state 28 ``` ConfigureNotify event, serial 24, synthetic YES, window 0x5e00002, ``` event 0x5e00002, window 0x5e00002, (-1871,24), width 1871, height 1056, border_width 0, above 0xfde776, override NO ``` FocusOut event, serial 24, synthetic NO, window 0x5e00002, ``` mode NotifyWhileGrabbed, detail NotifyNonlinear ``` PropertyNotify event, serial 24, synthetic NO, window 0x5e00002, ``` atom 0x160 (_NET_WM_STATE), time 26120780, state PropertyNewValue ``` PropertyNotify event, serial 24, synthetic NO, window 0x5e00002, ``` atom 0x157 (_NET_FRAME_EXTENTS), time 26120780, state PropertyNewValue ``` PropertyNotify event, serial 24, synthetic NO, window 0x5e00002, ``` atom 0x1c6 (_NET_WM_ICON_GEOMETRY), time 26120782, state PropertyNewValue ``` In the case (1), successive FocusOut-FocusOut events can be translated to single FocusOut event, and FocusOut-FocusIn events can be discarded. %%%
Member

%%%Attached a patch workaround_bug33831_r54108.patch.

In this patch, unnecessary FocusOut events are discarded as follows:

  • Successive FocusOut events is translated to single FocusOut event
  • A FocusOut event just before a FocusIn event is ignored

Necessary events for actual focus out should be passed.

Note that the short time waits (100msec) are needed to detect the unnecessary events. The waits can stop UI updating for a short time. I'm not sure if they cause another problem and if 100msec is sufficient to avoid the problem.

So far it works fine for me.
%%%

%%%Attached a patch workaround_bug33831_r54108.patch. In this patch, unnecessary FocusOut events are discarded as follows: - Successive FocusOut events is translated to single FocusOut event - A FocusOut event just before a FocusIn event is ignored Necessary events for actual focus out should be passed. Note that the short time waits (100msec) are needed to detect the unnecessary events. The waits can stop UI updating for a short time. I'm not sure if they cause another problem and if 100msec is sufficient to avoid the problem. So far it works fine for me. %%%

%%%Just updated to r54115, and this problem seems solved (again).%%%

%%%Just updated to r54115, and this problem seems solved (again).%%%
Member

%%%Alt key is still not working. r54134

For testing, I applied my patch to deb packages (r54115) in PPA (https://launchpad.net/~irie/+archive/blender) and it works.
%%%

%%%Alt key is still not working. r54134 For testing, I applied my patch to deb packages (r54115) in PPA (https://launchpad.net/~irie/+archive/blender) and it works. %%%
Member

%%%I've reported this problem in Unity's bug tracker:

https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1108064
%%%

%%%I've reported this problem in Unity's bug tracker: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1108064 %%%

%%%Not working on my end either:

Ubuntu 12.04
Blender r54156

Alt - H does not unhide all, and Alt - A is not playing back in timeline.

Most recent version it worked for me is

Blender r53912

After that version it has stopped working. No changes have been made to the system or in Unity.%%%

%%%Not working on my end either: Ubuntu 12.04 Blender r54156 Alt - H does not unhide all, and Alt - A is not playing back in timeline. Most recent version it worked for me is Blender r53912 After that version it has stopped working. No changes have been made to the system or in Unity.%%%
Member

%%%KeymapNotify event is always received just after FocusIn evnt. Blender should be able to restore the modifier states from its key_vector[].
%%%

%%%KeymapNotify event is always received just after FocusIn evnt. Blender should be able to restore the modifier states from its key_vector[]. %%%
Member

%%%Made another patch (SystemX11_handle_KeymapNotify.patch):

http://projects.blender.org/tracker/index.php?func=detail&aid=34039&group_id=9&atid=127

This patch uses KeymapNotify event to correct modifier key states after FocusIn and EnterNotify events. All FocusOut/FocusIn events are still passed on, but modifier keys should work.
%%%

%%%Made another patch (SystemX11_handle_KeymapNotify.patch): http://projects.blender.org/tracker/index.php?func=detail&aid=34039&group_id=9&atid=127 This patch uses KeymapNotify event to correct modifier key states after FocusIn and EnterNotify events. All FocusOut/FocusIn events are still passed on, but modifier keys should work. %%%

%%%Thanks Shinsuke, committed patch #34039.%%%

%%%Thanks Shinsuke, committed patch #34039.%%%

%%%On my Ubuntu 12.04 x64 with Unity desktop manager (3D version) I used gconf-editor to change the "mouse_button_modifier" from to , so everything was fine in 2.65a, but with builds like buildbot r54076, I noticed that:
Alt-A / Alt-D don't work, but Ctrl-Shift-Alt-C still does (Alt-Ctrl-Shift-C and Shift-Ctrl-Alt-C don't work in contrast to 2.65a), Ctrl-Alt-C also still works (Alt-Ctrl-C doesn't work in contrast to 2.65a).

Now I tested this patch (blender-2.65-r54201-linux-glibc211-x86_64) and Alt-A/Alt-D/Ctrl-Alt-Shift-C work, but viewport navigation has stopped working although I can still select objects and change values in the other editors as well as in the tool shelf and the properties. Changing the size of editors with the mouse has also stopped working. In 2.65a everything works fine.

Another strange effect:
After starting, A selects all, Alt-A plays the animation, but after effortlessly trying to resize an editor with the mouse (or using MMB to navigate in the 3D view or using a shortcut involving the Alt key or just Alt), A alone will start playback - all keypresses are interpreted as if I would press Alt as well. Also, value fields react in a strange way: just by moving the cursor over, they change their values (like the Alt key would be pressed).%%%

%%%On my Ubuntu 12.04 x64 with Unity desktop manager (3D version) I used gconf-editor to change the "mouse_button_modifier" from <Alt> to <Super>, so everything was fine in 2.65a, but with builds like buildbot r54076, I noticed that: Alt-A / Alt-D don't work, but Ctrl-Shift-Alt-C still does (Alt-Ctrl-Shift-C and Shift-Ctrl-Alt-C don't work in contrast to 2.65a), Ctrl-Alt-C also still works (Alt-Ctrl-C doesn't work in contrast to 2.65a). Now I tested this patch (blender-2.65-r54201-linux-glibc211-x86_64) and Alt-A/Alt-D/Ctrl-Alt-Shift-C work, but viewport navigation has stopped working although I can still select objects and change values in the other editors as well as in the tool shelf and the properties. Changing the size of editors with the mouse has also stopped working. In 2.65a everything works fine. Another strange effect: After starting, A selects all, Alt-A plays the animation, but after effortlessly trying to resize an editor with the mouse (or using MMB to navigate in the 3D view or using a shortcut involving the Alt key or just Alt), A alone will start playback - all keypresses are interpreted as if I would press Alt as well. Also, value fields react in a strange way: just by moving the cursor over, they change their values (like the Alt key would be pressed).%%%
Member

%%%Campbell, I guess the multiple-windows issue in my patch is caused by checking EnterNotify event. Checking the EnterNotify event is, however, unnecessary for solving the Alt-key glitch on Unity desktop, so it can be removed.

Attached fix_Unity_workaround.patch .
%%%

%%%Campbell, I guess the multiple-windows issue in my patch is caused by checking EnterNotify event. Checking the EnterNotify event is, however, unnecessary for solving the Alt-key glitch on Unity desktop, so it can be removed. Attached fix_Unity_workaround.patch . %%%
Member

%%%Attached a patch fix_Unity_workaround_v2.patch.

If the window is active, Blender should get KeyPress or KeyRelease event immediately after the FocusIn and KeymapNotify events.
In this patch, the modifier key states are corrected only when KeyPress or KeyRelease event was received.
%%%

%%%Attached a patch fix_Unity_workaround_v2.patch. If the window is active, Blender should get KeyPress or KeyRelease event immediately after the FocusIn and KeymapNotify events. In this patch, the modifier key states are corrected only when KeyPress or KeyRelease event was received. %%%

%%%Thanks Shinsuke, the patch fixes the issue with modifier keys staying held.%%%

%%%Thanks Shinsuke, the patch fixes the issue with modifier keys staying held.%%%

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

%%%I'm not really sure if it's related to this issue, but ALT key in object mode has been broken in Ubuntu for the last few builds from Buildbot. ALT-R, ALT-S and ALT-A don't work at all...%%%

%%%I'm not really sure if it's related to this issue, but ALT key in object mode has been broken in Ubuntu for the last few builds from Buildbot. ALT-R, ALT-S and ALT-A don't work at all...%%%

%%%Forgot to mention this: ALT was working in r54201 but are broken as of r54287.%%%

%%%Forgot to mention this: ALT was working in r54201 but are broken as of r54287.%%%

%%%Juan USE_UNITY_WORKAROUND was re-enabled r54288%%%

%%%Juan USE_UNITY_WORKAROUND was re-enabled r54288%%%

%%%Thank you, Campbell!! =) I will wait for next buildbot build to test it.%%%

%%%Thank you, Campbell!! =) I will wait for next buildbot build to test it.%%%
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
10 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#33831
No description provided.