[Desktop-packages] [Bug 1670717] Re: Unity8/mir working on VMware due to bypass not working
FWIW, the new EGL backend for Mir shouldn't suffer from this issue as it respects the config selected by the app. Here's the PPA if someone wants to try [1]. https://launchpad.net/~cemil-azizoglu/+archive/ubuntu/mesa-rs [1] Note that the new EGL will NOT work with the old (existing) EGL apps yet. You need to port your app (in a trivial way) to use it. Once ported, the old and new EGLs will coexist (i.e. you don't need to port all Mir apps to use the new EGL). Let me know (camako@IRC). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1670717 Title: Unity8/mir working on VMware due to bypass not working Status in mesa package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Related to this bug (bug #1480755) - this is the issue preventing unity8/mir working in VMware. Bringing it out into its own issue to improve visibility. Choice quotes from previous bug: The problem is (annoyingly) that Mesa 10.5.9 on wily (Intel Haswell) returns 7 compatible EGLConfigs for EGL_ALPHA_SIZE=0 but all of them have EGL_ALPHA_SIZE == 8 set. Added a Mesa task. RAOF has suggested we should just fix Mesa. When asking for RGBA of 8880 it should provide at least one EGLConfig that is 8880 instead of always . This should be possible. It's not entirely clear why we're not getting XRGB visuals currently, but it's fixable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1670717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1663062] Re: [regression] Software clients of nested servers are all black in Mir 0.25.0 and later
** Changed in: mir/0.26 Status: Triaged => Fix Committed ** Changed in: mir/0.26 Assignee: (unassigned) => Kevin DuBois (kdub) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1663062 Title: [regression] Software clients of nested servers are all black in Mir 0.25.0 and later Status in Mir: Triaged Status in Mir 0.25 series: Won't Fix Status in Mir 0.26 series: Fix Committed Status in mesa package in Ubuntu: Invalid Bug description: GPU apps seem to work. CPU apps all get black screen. To repro : Under unity7 using mir-on-x: 1- In a terminal, run : mir_demo_server -f /tmp/mysock 2- In another terminal, run : mir_demo_server --host-socket /tmp/mysock 3- In another terminal, run : mir_demo_client_progressbar Under Unity8 : In another terminal, run : mir_demo_client_progressbar Observe that, the window is black. Whereas, egl clients run fine. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1663062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1663062] Re: [regression] Software clients of nested servers are all black in Mir 0.25.0 and later
** Description changed: GPU apps seem to work. CPU apps all get black screen. + + To repro using mir-on-x: + + 1- In a terminal, run : + mir_demo_server -f /tmp/mysock + + 2- In another terminal, run : + mir_demo_server --host-socket /tmp/mysock + + 3- In another terminal, run : + mir_demo_client_progressbar + + Observe that, the window is black. + + Whereas, egl clients run fine. ** Description changed: GPU apps seem to work. CPU apps all get black screen. - To repro using mir-on-x: + To repro : + Under unity7 using mir-on-x: 1- In a terminal, run : mir_demo_server -f /tmp/mysock 2- In another terminal, run : mir_demo_server --host-socket /tmp/mysock 3- In another terminal, run : mir_demo_client_progressbar + Under Unity8 : + In another terminal, run : + mir_demo_client_progressbar + Observe that, the window is black. Whereas, egl clients run fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1663062 Title: [regression] Software clients of nested servers are all black in Mir 0.25.0 and later Status in Mir: Triaged Status in Mir 0.25 series: Won't Fix Status in Mir 0.26 series: Triaged Status in mesa package in Ubuntu: Invalid Bug description: GPU apps seem to work. CPU apps all get black screen. To repro : Under unity7 using mir-on-x: 1- In a terminal, run : mir_demo_server -f /tmp/mysock 2- In another terminal, run : mir_demo_server --host-socket /tmp/mysock 3- In another terminal, run : mir_demo_client_progressbar Under Unity8 : In another terminal, run : mir_demo_client_progressbar Observe that, the window is black. Whereas, egl clients run fine. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1663062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1196239] Re: Add support for fake modes on laptop screens which only have one
Upping the priority since this is needed for Ubuntu personal. ** Changed in: mir Importance: Wishlist => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1196239 Title: Add support for fake modes on laptop screens which only have one Status in Canonical System Image: Triaged Status in Mir: Triaged Status in xorg-server package in Ubuntu: Won't Fix Bug description: Reproduce: run mirout What happens: I only see one resolution supported. What should happen: I should see more resolutions, like I do on unity7. I guess, if in doubt, “support” the same ones as xrandr. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1196239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1543952] Re: Mesa EGL platform Mir does not implement environment variable LIBGL_ALWAYS_SOFTWARE
I took a look at implementing LIBGL_ALWAYS_SOFTWARE=1, and it shouldn't be that difficult to do. You're right it will need to go in platform- mir. Only thing missing is a good motivation, or use-case to implement this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1543952 Title: Mesa EGL platform Mir does not implement environment variable LIBGL_ALWAYS_SOFTWARE Status in Mir: Triaged Status in mesa package in Ubuntu: Triaged Bug description: Mir binaries ignore Mesa setting LIBGL_ALWAYS_SOFTWARE=1 and only ever try hardware acceleration. See: http://mesa3d.org/envvars.html To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1543952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly
I could not reproduce on xenial. Both mir-on-x and mesa worked for me. Note that there is a known issue with the nested server not being able to detect the platform (lp:1515558) so a '--vt' switch is needed on the server for correct behaviour. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1526209 Title: [regression] Clients of nested Mir servers silently crash/exit instantly Status in Mir: Triaged Status in Mir 0.18 series: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Bug description: Clients of nested Mir servers silently crash/exit instantly (on xenial) This happens in Mir trunk lp:mir and lp:mir/0.18, but not in lp:mir/0.17 sudo bin/mir_demo_server_minimal -f /tmp/outside & sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside & sudo bin/mir_demo_client_egltriangle -m /tmp/inside And the client silently exits with return code 139. Valgrind or gdb show the problem though: ==16515== Process terminating with default action of signal 11 (SIGSEGV) ==16515== Access not within mapped region at address 0x123460A8 ==16515==at 0x6EA16E0: XGetXCBConnection (in /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0) ==16515==by 0x517AC73: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174ADE: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174B98: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5170B31: eglInitialize (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x4031A9: mir_eglapp_init (eglapp.c:350) ==16515==by 0x4024EC: main (egltriangle.c:85) #0 0x75b6e6e0 in XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 #1 0x77893c74 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #2 0x7788dadf in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #3 0x7788db99 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #4 0x77889b32 in eglInitialize () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #5 0x004031aa in mir_eglapp_init (argc=3, argv=0x7fffe548, width=0x7fffdd48, height=0x7fffdd4c) at /home/dan/bzr/mir/0.18/examples/eglapp.c:350 #6 0x004024ed in main (argc=3, argv=0x7fffe548) at /home/dan/bzr/mir/0.18/examples/egltriangle.c:85 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526209] Re: [regression] Clients of nested Mir servers silently crash/exit instantly
duflu, could you also try 1. with the '--vt' option ? 2. on another machine with a different GPU? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1526209 Title: [regression] Clients of nested Mir servers silently crash/exit instantly Status in Mir: Incomplete Status in Mir 0.18 series: Incomplete Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Incomplete Bug description: Clients of nested Mir servers silently crash/exit instantly (on xenial) This happens in Mir trunk lp:mir and lp:mir/0.18, but not in lp:mir/0.17 sudo bin/mir_demo_server_minimal -f /tmp/outside & sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside & sudo bin/mir_demo_client_egltriangle -m /tmp/inside And the client silently exits with return code 139. Valgrind or gdb show the problem though: ==16515== Process terminating with default action of signal 11 (SIGSEGV) ==16515== Access not within mapped region at address 0x123460A8 ==16515==at 0x6EA16E0: XGetXCBConnection (in /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1.0.0) ==16515==by 0x517AC73: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174ADE: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5174B98: ??? (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x5170B31: eglInitialize (in /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1.0.0) ==16515==by 0x4031A9: mir_eglapp_init (eglapp.c:350) ==16515==by 0x4024EC: main (egltriangle.c:85) #0 0x75b6e6e0 in XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 #1 0x77893c74 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #2 0x7788dadf in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #3 0x7788db99 in ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #4 0x77889b32 in eglInitialize () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 #5 0x004031aa in mir_eglapp_init (argc=3, argv=0x7fffe548, width=0x7fffdd48, height=0x7fffdd4c) at /home/dan/bzr/mir/0.18/examples/eglapp.c:350 #6 0x004024ed in main (argc=3, argv=0x7fffe548) at /home/dan/bzr/mir/0.18/examples/egltriangle.c:85 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1526209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1487637] [NEW] Unable to resize/move window after XGrabKeyboard
Public bug reported: I'm experiencing this as described here : http://stackoverflow.com/questions/14555703/x11-unable-to-move-window- after-xgrabkeyboard Move/resize both suffer from the same problem. This is on Wily. ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1487637 Title: Unable to resize/move window after XGrabKeyboard Status in unity package in Ubuntu: New Bug description: I'm experiencing this as described here : http://stackoverflow.com/questions/14555703/x11-unable-to-move-window- after-xgrabkeyboard Move/resize both suffer from the same problem. This is on Wily. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1487637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1441951] Re: Enable DRI3
Vulkan needs DRI3 support. It'd be good to have this enabled despite the caveats. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1441951 Title: Enable DRI3 Status in xserver-xorg-video-intel package in Ubuntu: Triaged Bug description: DRI3 is the replacement for DRI2. We should enable it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1441951/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1289072] Re: Nested servers need cursor support
** Changed in: unity-system-compositor Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1289072 Title: Nested servers need cursor support Status in Light Display Manager: Fix Released Status in Mir: Incomplete Status in Unity Mir: Invalid Status in Unity System Compositor: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “unity-system-compositor” package in Ubuntu: Fix Released Status in “unity8-desktop-session” package in Ubuntu: In Progress Bug description: Nested servers lack functional cursor support. The code just returns a null pointer. One of the symptoms of this is that it is not possible to use a mouse or trackpad when running Unity8 as the desktop shell. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1289072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
