Bug Unity in tiling windows manager

I tried Unity Editor on Archlinux. If I use Gnome then it works fine, but with awesome WM, it crashes.
This is log

Code (csharp):

1.  
2. ATTENTION: default value of option force_s3tc_enable overridden by environment.
3. [0902/220201:ERROR:gpu_process_transport_factory.cc(402)] Failed to establish GPU channel.
4. [0902/220220:ERROR:browser_main_loop.cc(207)] Gtk: gtk_file_chooser_default_set_current_name: assertion 'impl->action == GTK_FILE_CHOOSER_ACTION_SAVE || impl->action == GTK_FILE_CHOOSER_ACTION_CREATE_FOLDER' failed
5. /home/dynamo/Three Kingdom
6. UpdateMenuTitleForLanguage: 10
7. Receiving unhandled NULL exception
8. Launching bug reporter
9. #0  0x007ffde5a449c0 in funlockfile
10. #1  0x007ffde5a44e30 in XCreateIC
11. #2  0x007ffde5a44f30 in InitX11ToSDL()
12. #3  0x007ffde5a456c0 in InputInit()
13. #4  0x007ffde5a456d0 in InitializeEngineNoGraphics()
14. #5  0x007ffde5a45710 in Application::InitializeProject()
15. #6  0x007ffde5a45cb0 in InitializeUnity(void*)
16. #7  0x007ffde5a45d00 in g_source_get_time
17. #8  0x007ffde5a45d20 in g_main_context_dispatch
18. #9  0x007ffde5a45db0 in g_main_context_dispatch
19. #10 0x007ffde5a45e10 in g_main_loop_run
20. #11 0x007ffde5a45e40 in gtk_main
21. #12 0x007ffde5a45ec0 in main
22. #13 0x007ffde5a461e0 in __libc_start_main
23. #14 0x007ffde5a462a0 in _start
24.  

My OpenGL info:

Code (csharp):

1.  
2.   Version:  OpenGL 2.1 [2.1 Mesa 10.6.5]
3.   Renderer: Mesa DRI Intel(R) Ironlake Mobile
4.   Vendor:  Intel Open Source Technology Center
5.   VRAM:  1536 MB
6.  

 

It's failing very early in xlib initialization, trying to create an input context.
Maybe this is something unsupported in awesomewm?

Or possibly something we're expecting to be synchronous has suddenly become async (and so something else we're expecting to have finished initializing has not) - the following from their 'about' seems a bit indicative:

 

The editor runs fine for me in awesome v3.5.6. I'm also using Arch Linux. There's also another thread (http://forum.unity3d.com/threads/some-feedback-arch-awesomewm.350763/) where the poster says it's working well with Awesome.

Perhaps it's something specific to your configuration. Have you tried with different layouts? Perhaps try with the default rc.lua?

 

Freaky that i used my awesome configuration at 2 laptop, one of them use second monitor. Multi monitor computer works fine. :|
All layouts of awesome is provide by awful class. I tried with default configuration and nothing gonna change.