Btw, for my kernel Xorg starts with using intel driver only with additional linux kernel boot parameter: i915.modeset=1 It's not a problem, I think =) Of course I wrote above about linux booted with this parameter.
I found what it is: < OpenGL vendor string: VMware, Inc. < OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x300) It's not VMware virtual machine specific driver (as I thought before) as I can understand now. llvmpipe is specific library (driver??) which is created for compatibility with graphic cards which can not normally support Ubuntu Unity 3D. It is started in case of normal is failed. I found this package: libllvm3.0. I tried to uninstall it, but libgl1-mesa-dri depends from it. Then I found library in this package: /usr/lib/i386-linux-gnu/libLLVM-3.0.so.1 And run: sudo rm /usr/lib/i386-linux-gnu/libLLVM-3.0.so.1 Then reboot my system. Tried to login as simple user in Ubuntu Unity 3D and it can't, I had error about "GL vertex buffer object". Then logined as root to Ubuntu Unity 3D with success as expected =) Under the root: # /usr/lib/nux/unity_support_test -p OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) G33 x86/MMX/SSE2 OpenGL version string: 1.4 Mesa 8.0.4 Not software rendered: yes Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program: yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object: yes GL version is 1.4+: yes Unity 3D supported: yes But under the any other simple user: $ /usr/lib/nux/unity_support_test -p OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) G33 x86/MMX/SSE2 OpenGL version string: 1.4 Mesa 8.0.4 Not software rendered: yes Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program: yes GL fragment program: yes GL vertex buffer object: no GL framebuffer object: yes GL version is 1.4+: yes Unity 3D supported: no I can't understand it, really =) Non supported before "Not software rendered" changed to non supported now "GL vertex buffer object". OpenGL renderer now are the same for root and non-root users. Before it was such for non-root users: OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x300) OpenGL version string: 2.1 Mesa 8.0.4 With different OpengGL renderer and OpenGL version! As I can understand, if "Mesa DRI Intel(R) G33 x86/MMX/SSE2" failed then "Gallium 0.4 on llvmpipe (LLVM 0x300)" tried to start automatically (if /usr/lib/i386-linux-gnu/libLLVM-3.0.so.1 present in the system), and Unity 3D + Compiz have blinking black and other described in this bug. Of course I switched to force Ubuntu Unity 3D start by option: UNITY_FORCE_START=1 in /etc/environment (I used other file but don't remember which now). I have only one explanation: "Mesa DRI Intel(R) G33 x86/MMX/SSE2" can't access to something because of limited privileges of simple non-root user. P. S. : I reinstalled libllvm3.0 and have black and other blinking again in forced started Ubuntu Unity 3D. In the second part of the video which I uploaded you can see how Ubuntu Ubuntu 3D normally works under root user :) I can't understand it: same computer, same video card (I have only one video card and only one monitor), same hard disk, same Ubuntu Linux, same kernel, but root and non-root users can start Ununtu Unity 3D with different results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071482 Title: everything is black and blinks (flashes) when using unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1071482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
