[Touch-packages] [Bug 1667014] Re: If no pixel format is set for a window it hangs when requesting a buffer
so if the previous code looked like this: MirWindowSpec *spec = mir_create_normal_window_spec(connection, width, *height); mir_window_spec_set_pixel_format(spec, pixel_format); MirWindow* window = mir_create_window_sync(spec); EGLSurface eglsurface = eglCreateWindowSurface(egldisplay, eglconfig, (EGLNativeWindowType) mir_buffer_stream_get_egl_native_window(mir_window_get_buffer_stream(window)), NULL); the new code looks like this (as of date of posting) MirRenderSurface* rs = mir_connection_create_render_surface_sync(connection, width, height); MirBufferStream* bs = mir_render_surface_get_buffer_stream(rs, width, height, format); EGLSurface eglsurface = eglCreateWindowSurface(egldisplay, eglconfig, (EGLNativeWindowType) mir_buffer_stream_get_egl_native_window(bs), NULL); MirWindowSpec *spec = mir_create_normal_window_spec(connection, width, height); mir_window_spec_add_render_surface(spec, width, height, 0, 0); mir_window_spec_set_event_handler(spec, [] (MirWindow* w, MirEvent* e, void* c) { MirRenderSurface* rs = (MirRenderSurface*) c; if (event == resize) //psuedocode { mir_render_surface_set_size(rs, new_width, new_height); //notify driver of clients choice auto spec = mir_create_window_spec(connection); //notify server of clients choice mir_window_spec_add_render_surface(spec, rs, new_width, new_height, 0, 0); mir_window_apply_spec(window, spec); mir_window_spec_release(); } } rs); MirWindow* window = mir_create_window_sync(spec); -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1667014 Title: If no pixel format is set for a window it hangs when requesting a buffer Status in Mir: Invalid Status in mir package in Ubuntu: New Bug description: If no pixel format is set when creating a window the request for a buffer hangs. An example would be to comment out setting the pixel format in eglapp.c then running any egl client demo. http://paste.ubuntu.com/24047858/ To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1667014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667014] Re: If no pixel format is set for a window it hangs when requesting a buffer
after the drivers transition to supporting MirRenderSurface, the egl creation starts to look like this: MirRenderSurface* rs = mir_connection_create_render_surface_sync(connection, width, height); EGLSurface eglsurface = eglCreateWindowSurface(egldisplay, eglconfig, rs, NULL); And, since the majority of use cases that are transitioning were probably relying on implicit resize messages affecting the buffer stream, could probably come up with a helper function for the single MirSurface in the MirWindow case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1667014 Title: If no pixel format is set for a window it hangs when requesting a buffer Status in Mir: Invalid Status in mir package in Ubuntu: New Bug description: If no pixel format is set when creating a window the request for a buffer hangs. An example would be to comment out setting the pixel format in eglapp.c then running any egl client demo. http://paste.ubuntu.com/24047858/ To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1667014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667014] Re: If no pixel format is set for a window it hangs when requesting a buffer
** Changed in: mir Milestone: 0.26.2 => None ** Changed in: mir Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1667014 Title: If no pixel format is set for a window it hangs when requesting a buffer Status in Mir: Invalid Status in mir package in Ubuntu: New Bug description: If no pixel format is set when creating a window the request for a buffer hangs. An example would be to comment out setting the pixel format in eglapp.c then running any egl client demo. http://paste.ubuntu.com/24047858/ To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1667014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667014] Re: If no pixel format is set for a window it hangs when requesting a buffer
So this has to do about transitioning from creating a window with a 'default' surface to creating both the surface and then coordinating it with the window. In this example its using the 'default' surface/bstream creation that we're phasing out. The proper transition would be to create MirRenderSurface, and then create a MirWindow with that surface in its spec. The resize events also are no longer automatic, so they have to be handled as well (will come up with a helper fn for this) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1667014 Title: If no pixel format is set for a window it hangs when requesting a buffer Status in Mir: New Status in mir package in Ubuntu: New Bug description: If no pixel format is set when creating a window the request for a buffer hangs. An example would be to comment out setting the pixel format in eglapp.c then running any egl client demo. http://paste.ubuntu.com/24047858/ To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1667014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1663062] Re: [regression] Software clients of nested servers are all black in Mir 0.25.0 and later
Its even a bit more narrow than that, software clients of android work (its just ShmBuffer-backed software clients that would be affected). Furthermore, the nested compositor had to select GL rendering instead of pasthrough (which is probably common in the wild), and the surface had to be larger than 480x480. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir 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: In Progress Status in Mir 0.25 series: Won't Fix Status in Mir 0.26 series: Fix Committed Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1663062] Re: [regression] Software clients of nested servers are all black in Mir 0.25.0 and later
** Tags added: mesa -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661521] Re: [regression] Windowed clients of nested servers are all black
** Branch linked: lp:~kdub/mir/fix-1661521-0.26.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1661521 Title: [regression] Windowed clients of nested servers are all black Status in Mir: Triaged Status in Mir 0.26 series: Triaged Status in mir package in Ubuntu: Invalid Bug description: [regression] Windowed clients of nested servers are all black FAILING: lp:mir r4008 lp:mir/0.26 r4005 WORKING: Mir 0.26.0 zesty binaries (lp:mir/0.26 r3994) lp:mir/0.25 r3822 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661521] Re: [regression] Windowed clients of nested servers are all black
pixel format was not communicated properly all the way back to the client buffers. This resulted in the nested server's EGLClientBuffer image import failing, only in the mesa platform. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1661521 Title: [regression] Windowed clients of nested servers are all black Status in Mir: Triaged Status in Mir 0.26 series: Triaged Status in mir package in Ubuntu: Invalid Bug description: [regression] Windowed clients of nested servers are all black FAILING: lp:mir r4008 lp:mir/0.26 r4005 WORKING: Mir 0.26.0 zesty binaries (lp:mir/0.26 r3994) lp:mir/0.25 r3822 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
Why this crashes sometimes and other times spams is that wait_for_all() is sometimes called on a nullptr MirWaitHandle. The first thing that fn does is grab a lock. Some libc's seem smart enough to recognize that the memory isn't there and throw system_error, but its pretty conceivable that this could segfault if libc wasn't able to detect the memory issue and throw. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Triaged Status in Mir 0.26 series: In Progress Status in mir package in Ubuntu: Triaged Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661508] Re: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what
yep, was the removal-of waithandle MP. needed some more checks before waiting for interval configuration. ** Changed in: mir/0.26 Assignee: (unassigned) => Kevin DuBois (kdub) ** Changed in: mir/0.26 Status: Triaged => In Progress ** Branch linked: lp:~kdub/mir/fix-1661508 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1661508 Title: [regression] Nested server segfaults or rapidly logs exceptions when a fullscreen client starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what: Operation not permitted] Status in Mir: Triaged Status in Mir 0.26 series: In Progress Status in mir package in Ubuntu: Triaged Bug description: Nested server segfaults when a fullscreen client starts Using Mir 0.26.0 (zesty release): The client dies: [2017-02-03 15:05:44.315444] Mesa/NativeSurface: Caught exception at Mir/EGL driver boundary (in advance_buffer): /build/mir-1Sl_GZ/mir-0.26.0+17.04.20170126.3/src/client/no_tls_future-inl.h(76): Throw in function void mir::client::PromiseStateBase::break_promise() [with T = std::shared_ptr] Dynamic exception type: boost::exception_detail::error_info_injector std::exception::what: broken_promise Because the server died: Segmentation fault (core dumped) (gdb) bt #0 __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:67 #1 0x7fcceb7b4003 in ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #2 0x7fcceb7d1961 in mir_presentation_chain_set_dropping_mode () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #3 0x7fccec0e3a7a in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #4 0x7fccec09fd2d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #5 0x7fccec09f018 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #6 0x7fccec0e2c79 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.43 #7 0x7fccebcfab2f in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fcce95326ca in start_thread (arg=0x7fccde2b4700) at pthread_create.c:333 #9 0x7fccec4710ff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 However in development builds the server does not die and just floods the log instead: [2017-02-03 16:52:44.382460] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.399142] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.415823] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted [2017-02-03 16:52:44.432504] mirclient: Caught exception at client library boundary (in mir_presentation_chain_set_dropping_mode): Dynamic exception type: std::system_error std::exception::what: Operation not permitted *** WORKAROUND *** Start your nested server with --nested-passthrough=OFF Which works on the 0.26.0 release, but not on anything newer because you'll then hit the more recent regression bug 1661521. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1661508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654536] Re: unity-system-compositor crashed with src/platforms/android/server/gl_context.cpp(233): ... android::FramebufferGLContext::swap_buffers() ... std::exception::what: eg
It could be that /etc/init/keep-display-on-during-boot.conf needs to be ported to the systemd services. Not quite sure I understand enough about the v+o to x+o (and upstart to systemd) to quickly diagnose if the startup power situation is correct at time of error during bootup. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1654536 Title: unity-system-compositor crashed with src/platforms/android/server/gl_context.cpp(233): ... android::FramebufferGLContext::swap_buffers() ... std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d) Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Invalid Bug description: unity-system-compositor sometimes aborts on latest xenial/arm64 on frieza: $ system-image-cli -i current build number: 116 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2017-01-06 09:43:26 version version: 116 version ubuntu: 20170106 version device: 20161014.0 version custom: 20170106 /var/log/lightdm/unity-system-compositor.log has: ERROR: /build/mir-2omL3o/mir-0.25.0+16.04.20161203/src/platforms/android/server/gl_context.cpp(233): Throw in function virtual void mir::graphics::android::FramebufferGLContext::swap_buffers() const Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d) ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-system-compositor 0.8.0+16.04.20161206-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: arm64 Date: Fri Jan 6 10:20:54 2017 Disassembly: => 0x7fa41dd5e8: Cannot access memory at address 0x7fa41dd5e8 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1480992789 GraphicsCard: ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 11 --to-dm-fd 14 --vt 1 ProcCwd: / ProcEnviron: SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: unity-system-compositor StacktraceTop: () std::__exception_ptr::exception_ptr::_M_release() (this=0x7fa5647b20 <_ZN12_GLOBAL__N_121termination_exceptionE.lto_priv.2774>) at ../../../../src/libstdc++-v3/libsupc++/eh_ptr.cc:121 __cxa_finalize (d=0x7fa5646498) at cxa_finalize.c:56 __do_global_dtors_aux () at /usr/lib/aarch64-linux-gnu/libmirserver.so.42 _dl_fini () at dl-fini.c:235 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.67-1ubuntu0.16.04.2 version.lightdm: lightdm 1.18.3-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1654536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654536] Re: unity-system-compositor crashed with src/platforms/android/server/gl_context.cpp(233): ... android::FramebufferGLContext::swap_buffers() ... std::exception::what: eg
Was able to see the error on startup in the bug in USC. Confirmed that the quirk affecting fb bits don't affect operation, and that both the overlay path and gl-rendered path work with the demo servers and USC (after the system has come up fully). This only seems to happen when the device is booting up (haven't seen this on 'service lightdm restart') Just a hunch that there's something in the system at large that hasn't finished powered up correctly, when USC tries to GL-draw a frame. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1654536 Title: unity-system-compositor crashed with src/platforms/android/server/gl_context.cpp(233): ... android::FramebufferGLContext::swap_buffers() ... std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d) Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Invalid Bug description: unity-system-compositor sometimes aborts on latest xenial/arm64 on frieza: $ system-image-cli -i current build number: 116 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2017-01-06 09:43:26 version version: 116 version ubuntu: 20170106 version device: 20161014.0 version custom: 20170106 /var/log/lightdm/unity-system-compositor.log has: ERROR: /build/mir-2omL3o/mir-0.25.0+16.04.20161203/src/platforms/android/server/gl_context.cpp(233): Throw in function virtual void mir::graphics::android::FramebufferGLContext::swap_buffers() const Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d) ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-system-compositor 0.8.0+16.04.20161206-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: arm64 Date: Fri Jan 6 10:20:54 2017 Disassembly: => 0x7fa41dd5e8: Cannot access memory at address 0x7fa41dd5e8 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1480992789 GraphicsCard: ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 11 --to-dm-fd 14 --vt 1 ProcCwd: / ProcEnviron: SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: unity-system-compositor StacktraceTop: () std::__exception_ptr::exception_ptr::_M_release() (this=0x7fa5647b20 <_ZN12_GLOBAL__N_121termination_exceptionE.lto_priv.2774>) at ../../../../src/libstdc++-v3/libsupc++/eh_ptr.cc:121 __cxa_finalize (d=0x7fa5646498) at cxa_finalize.c:56 __do_global_dtors_aux () at /usr/lib/aarch64-linux-gnu/libmirserver.so.42 _dl_fini () at dl-fini.c:235 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.67-1ubuntu0.16.04.2 version.lightdm: lightdm 1.18.3-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1654536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654536] Re: unity-system-compositor crashed with src/platforms/android/server/gl_context.cpp(233): ... android::FramebufferGLContext::swap_buffers() ... std::exception::what: eg
Is the frieza_arm64 channel in a sane state? (I remember it being usable about a month or so ago) I can't seem to even get to the dash. The mir demo stuff is seems to work though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1654536 Title: unity-system-compositor crashed with src/platforms/android/server/gl_context.cpp(233): ... android::FramebufferGLContext::swap_buffers() ... std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d) Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in mir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: Invalid Bug description: unity-system-compositor sometimes aborts on latest xenial/arm64 on frieza: $ system-image-cli -i current build number: 116 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2017-01-06 09:43:26 version version: 116 version ubuntu: 20170106 version device: 20161014.0 version custom: 20170106 /var/log/lightdm/unity-system-compositor.log has: ERROR: /build/mir-2omL3o/mir-0.25.0+16.04.20161203/src/platforms/android/server/gl_context.cpp(233): Throw in function virtual void mir::graphics::android::FramebufferGLContext::swap_buffers() const Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d) ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-system-compositor 0.8.0+16.04.20161206-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: arm64 Date: Fri Jan 6 10:20:54 2017 Disassembly: => 0x7fa41dd5e8: Cannot access memory at address 0x7fa41dd5e8 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1480992789 GraphicsCard: ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 11 --to-dm-fd 14 --vt 1 ProcCwd: / ProcEnviron: SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: unity-system-compositor StacktraceTop: () std::__exception_ptr::exception_ptr::_M_release() (this=0x7fa5647b20 <_ZN12_GLOBAL__N_121termination_exceptionE.lto_priv.2774>) at ../../../../src/libstdc++-v3/libsupc++/eh_ptr.cc:121 __cxa_finalize (d=0x7fa5646498) at cxa_finalize.c:56 __do_global_dtors_aux () at /usr/lib/aarch64-linux-gnu/libmirserver.so.42 _dl_fini () at dl-fini.c:235 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.67-1ubuntu0.16.04.2 version.lightdm: lightdm 1.18.3-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1654536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654536] Re: unity-system-compositor crashed with src/platforms/android/server/gl_context.cpp(233): ... android::FramebufferGLContext::swap_buffers() ... std::exception::what: eg
re the 600mb available, it could be some other resource than system memory that the driver cannot access, given the limited enums the gl driver can return. ** Changed in: mir Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1654536 Title: unity-system-compositor crashed with src/platforms/android/server/gl_context.cpp(233): ... android::FramebufferGLContext::swap_buffers() ... std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d) Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in mir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: Invalid Bug description: unity-system-compositor sometimes aborts on latest xenial/arm64 on frieza: $ system-image-cli -i current build number: 116 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2017-01-06 09:43:26 version version: 116 version ubuntu: 20170106 version device: 20161014.0 version custom: 20170106 /var/log/lightdm/unity-system-compositor.log has: ERROR: /build/mir-2omL3o/mir-0.25.0+16.04.20161203/src/platforms/android/server/gl_context.cpp(233): Throw in function virtual void mir::graphics::android::FramebufferGLContext::swap_buffers() const Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d) ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-system-compositor 0.8.0+16.04.20161206-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: arm64 Date: Fri Jan 6 10:20:54 2017 Disassembly: => 0x7fa41dd5e8: Cannot access memory at address 0x7fa41dd5e8 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1480992789 GraphicsCard: ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 11 --to-dm-fd 14 --vt 1 ProcCwd: / ProcEnviron: SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: unity-system-compositor StacktraceTop: () std::__exception_ptr::exception_ptr::_M_release() (this=0x7fa5647b20 <_ZN12_GLOBAL__N_121termination_exceptionE.lto_priv.2774>) at ../../../../src/libstdc++-v3/libsupc++/eh_ptr.cc:121 __cxa_finalize (d=0x7fa5646498) at cxa_finalize.c:56 __do_global_dtors_aux () at /usr/lib/aarch64-linux-gnu/libmirserver.so.42 _dl_fini () at dl-fini.c:235 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.67-1ubuntu0.16.04.2 version.lightdm: lightdm 1.18.3-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1654536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654536] Re: unity-system-compositor crashed EGL_BAD_SURFACE
I somewhat doubt that quirk would help, iirc, it was added after reports that it helped from the bringup (but by the time it got released it didn't seem to do anything in my local testing) 0x505 is GL_OUT_OF_MEMORY, perhaps a leak? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1654536 Title: unity-system-compositor crashed EGL_BAD_SURFACE Status in Canonical System Image: Confirmed Status in Mir: New Status in mir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Bug description: unity-system-compositor sometimes aborts on latest xenial/arm64 on frieza: $ system-image-cli -i current build number: 116 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2017-01-06 09:43:26 version version: 116 version ubuntu: 20170106 version device: 20161014.0 version custom: 20170106 /var/log/lightdm/unity-system-compositor.log has: ERROR: /build/mir-2omL3o/mir-0.25.0+16.04.20161203/src/platforms/android/server/gl_context.cpp(233): Throw in function virtual void mir::graphics::android::FramebufferGLContext::swap_buffers() const Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d) ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-system-compositor 0.8.0+16.04.20161206-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: arm64 Date: Fri Jan 6 10:20:54 2017 Disassembly: => 0x7fa41dd5e8: Cannot access memory at address 0x7fa41dd5e8 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1480992789 GraphicsCard: ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 11 --to-dm-fd 14 --vt 1 ProcCwd: / ProcEnviron: SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: unity-system-compositor StacktraceTop: () std::__exception_ptr::exception_ptr::_M_release() (this=0x7fa5647b20 <_ZN12_GLOBAL__N_121termination_exceptionE.lto_priv.2774>) at ../../../../src/libstdc++-v3/libsupc++/eh_ptr.cc:121 __cxa_finalize (d=0x7fa5646498) at cxa_finalize.c:56 __do_global_dtors_aux () at /usr/lib/aarch64-linux-gnu/libmirserver.so.42 _dl_fini () at dl-fini.c:235 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.67-1ubuntu0.16.04.2 version.lightdm: lightdm 1.18.3-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1654536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1613257] Re: oxide-qt fails to build on yakkety due to missing hybris dependencies
affects mir 0.24 landing too: https://launchpadlibrarian.net/279042110/buildlog_ubuntu-yakkety-armhf.mir_0.24.0+16.10.20160815-0ubuntu1_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1613257 Title: oxide-qt fails to build on yakkety due to missing hybris dependencies Status in libhybris package in Ubuntu: Confirmed Status in oxide-qt package in Ubuntu: Invalid Bug description: As seen here: https://launchpad.net/ubuntu/+source/oxide- qt/1.16.7-0ubuntu1 That means webbrowser-app is also unbuildable on yakkety when using proposed, and that the oxide-qt cannot migrate to release pocket. --- Depends: libmedia-hub-dev but it is not going to be installed Depends: libhybris-dev but it is not going to be installed --- Laney observes: libhybris-common1 : Depends: libc6 (< 2.24) but 2.24-0ubuntu1 is to be installed Note that the bug was originally filed against oxide-qt while the problem probably lies in those unfulfille dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/1613257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1262116] Re: Nested servers prevent overlays or fullscreen bypass from working
Have a spike-prototype working of bypassing buffers. Still more work to do with atomic multi-bufferstream updates, and sorting out the nested platform, but goal is within reach... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1262116 Title: Nested servers prevent overlays or fullscreen bypass from working Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: Nested servers prevent fullscreen bypass from working. This would explain why nesting fullscreen clients is measurably slower than non-nesting: Direct (bypass) 2600 Direct (bypass off) 2400 Nested (bypass) 2450 Nested (bypass off) 2330 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1262116/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578159] Re: Performance loss with NBS and overlays on
hmm, seems that I can't target to a released milestone -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1578159 Title: Performance loss with NBS and overlays on Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: If you run a server with overlays enabled on android devices with a client, sporadically, the performance will dip between 1/2 vsync rate and vsync rate. The dip is dependent on load, (it seems loads that tax the system at near-vsync rates seem to cause the problem). Should be fixed before 0.23 is published, so tagging as critical. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1578159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578159] Re: Performance loss with NBS and overlays on
right, this was in 0.23, doesnt affect 0.24. ** No longer affects: mir/0.23 ** Changed in: mir Milestone: 0.24.0 => None ** Changed in: mir Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1578159 Title: Performance loss with NBS and overlays on Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: If you run a server with overlays enabled on android devices with a client, sporadically, the performance will dip between 1/2 vsync rate and vsync rate. The dip is dependent on load, (it seems loads that tax the system at near-vsync rates seem to cause the problem). Should be fixed before 0.23 is published, so tagging as critical. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1578159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607047] [NEW] unity8-dash hang after UbuntuOne authentication when trying to install app 1st time
Public bug reported: install fresh image click through or disable welcome wizard/edges intro, setup network navigate to the Ubuntu Store click on an application, click to install (eg Telegram) enter username, password, 2fa details u8-dash hangs at this point (screenshot attached during hang) u8 is still responsive. logging on and killing unity8-dash will respawn it. The second time one tries to go through the app-install process, the application is installed. (no login details requested the 2nd time around) was testing on flo (ubuntu-touch/rc-proposed/ubuntu) : rev 492 does not have this problem rev 495 does have the problem ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dash-when-stuck-during-install.png" https://bugs.launchpad.net/bugs/1607047/+attachment/4708261/+files/dash-when-stuck-during-install.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1607047 Title: unity8-dash hang after UbuntuOne authentication when trying to install app 1st time Status in unity8 package in Ubuntu: New Bug description: install fresh image click through or disable welcome wizard/edges intro, setup network navigate to the Ubuntu Store click on an application, click to install (eg Telegram) enter username, password, 2fa details u8-dash hangs at this point (screenshot attached during hang) u8 is still responsive. logging on and killing unity8-dash will respawn it. The second time one tries to go through the app-install process, the application is installed. (no login details requested the 2nd time around) was testing on flo (ubuntu-touch/rc-proposed/ubuntu) : rev 492 does not have this problem rev 495 does have the problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1607047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607047] Re: unity8-dash hang after UbuntuOne authentication when trying to install app 1st time
** Attachment added: "unity8-dash.log" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1607047/+attachment/4708262/+files/unity8-dash.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1607047 Title: unity8-dash hang after UbuntuOne authentication when trying to install app 1st time Status in unity8 package in Ubuntu: New Bug description: install fresh image click through or disable welcome wizard/edges intro, setup network navigate to the Ubuntu Store click on an application, click to install (eg Telegram) enter username, password, 2fa details u8-dash hangs at this point (screenshot attached during hang) u8 is still responsive. logging on and killing unity8-dash will respawn it. The second time one tries to go through the app-install process, the application is installed. (no login details requested the 2nd time around) was testing on flo (ubuntu-touch/rc-proposed/ubuntu) : rev 492 does not have this problem rev 495 does have the problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1607047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590765] Re: OSK flickers and buttons are sometimes invisble
Explanation of targetting: 0.23.1 contained the initial workaround 0.23.5 will contains the cherry pick of the proper workaround from the 0.24.0 series, released along with the new feature. 0.24.0 contains the proper workaround. ** Changed in: mir Milestone: 0.24.0 => 0.23.5 ** Also affects: mir/0.24 Importance: Undecided Status: New ** Changed in: mir/0.24 Milestone: None => 0.24.0 ** Changed in: mir/0.24 Assignee: (unassigned) => Kevin DuBois (kdub) ** Changed in: mir/0.24 Importance: Undecided => High ** Changed in: mir/0.24 Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1590765 Title: OSK flickers and buttons are sometimes invisble Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.23 series: Fix Released Status in Mir 0.24 series: Fix Committed Status in mir package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often invisible (pressing white part will refresh it and buttons are visible again) and OSK flickers a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1606324] Re: unity8 autopilot failures (44 failed)
seems like a problem where one problem in setup causes a lot of test failures, not sure what the one problem could be though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1606324 Title: unity8 autopilot failures (44 failed) Status in unity8 package in Ubuntu: New Bug description: When running through the u8 autopilot testing on a fresh install (krillin, system image 392), I encountered 44 errors in autopilot. (full log attached). Followed instructions here: https://wiki.ubuntu.com/Touch/Testing/Autopilot/TestRunners u8 autopilot testing is recommended during the mir release process, we'll probably start doing the u8 manual integration tests until the AP tests get back into order. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1606324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1606324] [NEW] unity8 autopilot failures (44 failed)
Public bug reported: When running through the u8 autopilot testing on a fresh install (krillin, system image 392), I encountered 44 errors in autopilot. (full log attached). Followed instructions here: https://wiki.ubuntu.com/Touch/Testing/Autopilot/TestRunners u8 autopilot testing is recommended during the mir release process, we'll probably start doing the u8 manual integration tests until the AP tests get back into order. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "autopilot-0.23.4-results" https://bugs.launchpad.net/bugs/1606324/+attachment/4707255/+files/autopilot-0.23.4-results -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1606324 Title: unity8 autopilot failures (44 failed) Status in unity8 package in Ubuntu: New Bug description: When running through the u8 autopilot testing on a fresh install (krillin, system image 392), I encountered 44 errors in autopilot. (full log attached). Followed instructions here: https://wiki.ubuntu.com/Touch/Testing/Autopilot/TestRunners u8 autopilot testing is recommended during the mir release process, we'll probably start doing the u8 manual integration tests until the AP tests get back into order. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1606324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1593655] Re: Servers based on Mir need a hook to execute code when the server is closing
** Changed in: mir Milestone: 0.25.0 => 0.24.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1593655 Title: Servers based on Mir need a hook to execute code when the server is closing Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: There are multiple ways that a server can be closed because we hook into SIGINT & SIGTERM to stop the Mir server and the client code can call stop() directly. There should be an "on_stop(function)" facility to run client cleanup code before the server shuts down. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1593655/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599867] Re: usage of std:call_once in mirclient causes TLS collisions with some android devices
** Changed in: mir Milestone: 0.25.0 => 0.24.0 ** No longer affects: mir/0.24 ** Branch unlinked: lp:~kdub/mir/0.24-1599867 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1599867 Title: usage of std:call_once in mirclient causes TLS collisions with some android devices Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.23 series: Fix Released Status in mir package in Ubuntu: New Bug description: usage of std:call_once in src/client/error_connections.cpp in libmirclient causes TLS collisions with some android devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1599867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603080] Re: mirtest-dev provides an incorrect .pc file
** Changed in: mir Milestone: 0.25.0 => 0.24.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603080 Title: mirtest-dev provides an incorrect .pc file Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: In (e.g. /usr/lib/x86_64-linux-gnu/pkgconfig/mirtest.pc) there are missing library dependencies: -lboost_filesystem -lboost_system To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1603080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603091] Re: mir_test_framework::server_platform_path(), mir_test_framework::server_platform() don't support use in a downstream test built against mir-test-assist
** Changed in: mir Milestone: 0.25.0 => 0.24.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603091 Title: mir_test_framework::server_platform_path(), mir_test_framework::server_platform() don't support use in a downstream test built against mir-test-assist Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: These functions assume the platform path/library is built or installed relative to the executable. This is not the case for a downstream executable being built against an installed version of Mir. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1603091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards
** Changed in: mir Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1565236 Title: AltGr not working on external keyboards Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in mir package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Bug description: Using my keyboard with Spanish layout: - PC: Everything works perfect. - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú). Extra info: - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 (http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2) - Ubuntu Desktop: 12.04 - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579866] Re: Android graphics platform doesn't get packaged for arm64
** Changed in: mir Milestone: 0.25.0 => 0.24.0 ** No longer affects: mir/0.24 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1579866 Title: Android graphics platform doesn't get packaged for arm64 Status in Mir: Fix Committed Status in Mir 0.23 series: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: The android platform code is currently gated to i386,amd64,armhf because the libhybris upstream dependency is gated to these architectures. Upstream recently added builds for arm64, so it would be good to enable our android code on this arch as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1579866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603114] Re: mir_acceptance_tests.bin: double free or corruption (fasttop)
** Changed in: mir Milestone: 0.25.0 => 0.24.0 ** No longer affects: mir/0.24 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603114 Title: mir_acceptance_tests.bin: double free or corruption (fasttop) Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Seen a few times, typical thing seen is a memory issue in the acceptance tests: https://launchpadlibrarian.net/272973212/buildlog_ubuntu-yakkety- i386.mir_0.24.0+16.10.20160714-0ubuntu1_BUILDING.txt.gz 8: CMakeFiles CTestTestfile.cmake Makefile cmake_install.cmake mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags precompiled.hpp.compileflags.processed throwback Error in `/«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin': double free or corruption (fasttop): 0x0a1b5e40 CMakeFiles CTestTestfile.cmake Makefile cmake_install.cmake mir_acceptance_tests_precompiled.hpp.gch precompiled.hpp.compileflags precompiled.hpp.compileflags.processed throwback 8: === Backtrace: = 8: /lib/i386-linux-gnu/libc.so.6(+0x672d7)[0xf70872d7] 8: /lib/i386-linux-gnu/libc.so.6(+0x6d227)[0xf708d227] 8: /lib/i386-linux-gnu/libc.so.6(+0x6dae1)[0xf708dae1] 8: /usr/lib/i386-linux-gnu/libstdc++.so.6(_ZdlPv+0x18)[0xf72884b8] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZNSt6vectorISt8weak_ptrIN3mir5input11InputDeviceEESaIS4_EED2Ev+0x8b)[0x86213bb] 8: /lib/i386-linux-gnu/libc.so.6(+0x2e933)[0xf704e933] 8: /lib/i386-linux-gnu/libc.so.6(+0x2e98f)[0xf704e98f] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN18mir_test_framework28InterprocessClientServerTestD1Ev+0x12a)[0x8615eda] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin[0x8352b85] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing4Test11DeleteSelf_Ev+0x28)[0x8647494] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal38HandleSehExceptionsInMethodIfSupportedINS_4TestEvEET0_PT_MS4_FS3_vEPKc+0x45)[0x86536f9] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal35HandleExceptionsInMethodIfSupportedINS_4TestEvEET0_PT_MS4_FS3_vEPKc+0x50)[0x864ddff] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8TestInfo3RunEv+0x13b)[0x86318a7] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8TestCase3RunEv+0x103)[0x8631ffd] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal12UnitTestImpl11RunAllTestsEv+0x2e7)[0x8639a51] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal38HandleSehExceptionsInMethodIfSupportedINS0_12UnitTestImplEbEET0_PT_MS4_FS3_vEPKc+0x45)[0x8654bd7] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8internal35HandleExceptionsInMethodIfSupportedINS0_12UnitTestImplEbEET0_PT_MS4_FS3_vEPKc+0x50)[0x864ed4f] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN7testing8UnitTest3RunEv+0xc6)[0x86383c2] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(_ZN18mir_test_framework4mainEiPPc+0x3c)[0x82822dc] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin(main+0x6d)[0x828250d] 8: /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf7)[0xf70385f7] 8: /«BUILDDIR»/mir-0.24.0+16.10.20160714/obj-i686-linux-gnu/bin/mir_acceptance_tests.bin[0x828267e] 8: === Memory map: To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1603114/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1601810] Re: ftbfs in linking libmir-test-assist.a in xenial+overlay and yakkety+overlay
** No longer affects: mir/0.24 ** Changed in: mir Milestone: 0.25.0 => 0.24.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1601810 Title: ftbfs in linking libmir-test-assist.a in xenial+overlay and yakkety+overlay Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase::MatchAndExplain(char const*, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::PolymorphicMatcher, std::allocator > > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::internal::AnyMatcherImpl const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase::MatchAndExplain(char const*, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::PolymorphicMatcher, std::allocator > > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::internal::AnyMatcherImpl const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase::MatchAndExplain(char const*, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::PolymorphicMatcher, std::allocator > > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::internal::AnyMatcherImpl const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase::MatchAndExplain(char const*, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::PolymorphicMatcher, std::allocator > > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::internal::AnyMatcherImpl const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase const&>::DescribeTo(std::ostream*) const': /usr/include/gmock/gmock-matchers.h:242: undefined reference to `testing::internal::AnyMatcherImpl const&>::DescribeTo(std::ostream*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase::MatchAndExplain(char const*, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::PolymorphicMatcher, std::allocator > > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::internal::AnyMatcherImpl const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const' collect2: error: ld returned 1 exit status full log: https://launchpadlibrarian.net/272328456/buildlog_ubuntu-xenial-amd64.mir_0.24.0+16.04.20160711-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1601810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1602966] Re: [regression] The Super/Windows key doesn't work any more
** No longer affects: mir/0.24 ** Changed in: mir Milestone: 0.25.0 => 0.24.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1602966 Title: [regression] The Super/Windows key doesn't work any more Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: [regression] Zoom/contrast/negative desktop effects don't work any more in mir_proving_server on lp:mir. That's Super + mousewheel,C,N respectively To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1602966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1601810] Re: ftbfs in linking libmir-test-assist.a in xenial+overlay and yakkety+overlay
The problem would only occur when using dpkg-buildpackage. (slightly different link order was generated). The symbols that were missing were templates from gmock that were generated and in the mock_egl.cpp.o file. Given the right link order (namely, mirserver.so before libmir-test-assist.a), things would resolve correctly. If mirserver.so came after libmir-test-assist.a, then the egl functions would get resolved, but for whatever reason, the weak symbols generated as part of the gmock stuff wouldn't get pulled in again before getting to the end of the linkage list. The proper solution seems to be to use -Wl,--whole-archive to make sure that the symbols generated from the gmock templates are still available despite linkage order ** Changed in: mir Assignee: (unassigned) => Kevin DuBois (kdub) ** Branch linked: lp:~kdub/mir/fix-1601810 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1601810 Title: ftbfs in linking libmir-test-assist.a in xenial+overlay and yakkety+overlay Status in Mir: New Status in Mir 0.24 series: In Progress Status in mir package in Ubuntu: New Bug description: snippet: ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase::MatchAndExplain(char const*, testing::MatchResultListener*) const': /usr/include/gmock/gmock-matchers.h:232: undefined reference to `testing::PolymorphicMatcher, std::allocator > > >::MonomorphicImpl::MatchAndExplain(char const*, testing::MatchResultListener*) const' ../libmir-test-assist.a(mock_egl.cpp.o): In function `testing::internal::MatcherBase const&>::MatchAndExplain(std::tuple const&, testing::MatchResultListener*) const': full log: https://launchpadlibrarian.net/272328456/buildlog_ubuntu-xenial-amd64.mir_0.24.0+16.04.20160711-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1601810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462033] Re: [testsfail] NestedInput.nested_event_filter_receives_keyboard_from_host failure in CI
https://launchpadlibrarian.net/272331980/buildlog_ubuntu- vivid-i386.mir_0.24.0+15.04.20160711-0ubuntu1_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1462033 Title: [testsfail] NestedInput.nested_event_filter_receives_keyboard_from_host failure in CI Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: https://jenkins.qa.ubuntu.com/job/mir-wily-amd64-ci/166/consoleFull 7: [ RUN ] NestedInput.nested_event_filter_receives_keyboard_from_host 7: [1433432727.674278] mirserver: Starting 7: [1433432727.675137] mirserver: Selected driver: dummy (version 0.14.0) 7: [1433432727.679338] mirserver: Using software cursor 7: [1433432727.681407] mirserver: Mir version 0.14.0 7: [1433432727.732641] mirserver: Starting 7: [1433432727.733449] mirserver: Selected driver: dummy (version 0.14.0) 7: [1433432727.894537] mirserver: Mir version 0.14.0 7: [1433432738.076193] mirserver: Stopping 7: /tmp/buildd/mir-0.14.0bzr2624pkg0wily166/tests/acceptance-tests/test_nested_input.cpp:149: Failure 7: Actual function call count doesn't match EXPECT_CALL(*nested_mir.mock_event_filter, handle(_))... 7: Expected: to be called at least once 7: Actual: never called - unsatisfied and active 7: [1433432738.154764] mirserver: Stopping 7: [ FAILED ] NestedInput.nested_event_filter_receives_keyboard_from_host (10518 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1462033/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462033] Re: [testsfail] NestedInput.nested_event_filter_receives_keyboard_from_host failure in CI
hmm, seen again in CI, perhaps from different causes. will file a new bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1462033 Title: [testsfail] NestedInput.nested_event_filter_receives_keyboard_from_host failure in CI Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: https://jenkins.qa.ubuntu.com/job/mir-wily-amd64-ci/166/consoleFull 7: [ RUN ] NestedInput.nested_event_filter_receives_keyboard_from_host 7: [1433432727.674278] mirserver: Starting 7: [1433432727.675137] mirserver: Selected driver: dummy (version 0.14.0) 7: [1433432727.679338] mirserver: Using software cursor 7: [1433432727.681407] mirserver: Mir version 0.14.0 7: [1433432727.732641] mirserver: Starting 7: [1433432727.733449] mirserver: Selected driver: dummy (version 0.14.0) 7: [1433432727.894537] mirserver: Mir version 0.14.0 7: [1433432738.076193] mirserver: Stopping 7: /tmp/buildd/mir-0.14.0bzr2624pkg0wily166/tests/acceptance-tests/test_nested_input.cpp:149: Failure 7: Actual function call count doesn't match EXPECT_CALL(*nested_mir.mock_event_filter, handle(_))... 7: Expected: to be called at least once 7: Actual: never called - unsatisfied and active 7: [1433432738.154764] mirserver: Stopping 7: [ FAILED ] NestedInput.nested_event_filter_receives_keyboard_from_host (10518 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1462033/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506358] Re: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()
** Changed in: mir Milestone: 0.24.0 => 0.25.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1506358 Title: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit() Status in Canonical System Image: Confirmed Status in Mir: Confirmed Status in mir package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Bug description: Under heavy resizing (stress testing under Valgrind), my Mir client (Xmir) crashed with: [1444895332.392862] MirBufferStreamAPI: Caught exception at client library boundary (in mir_buffer_stream_swap_buffers): /build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169): Throw in function virtual MirWaitHandle* {anonymous}::ExchangeSemantics::submit(const std::function&, mir::geometry::Size, MirPixelFormat, int) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: disconnected: no new buffers The strange thing is it's only the client that died. The server survived and I can connect new clients to it. Duplicate bug reports now show Unity8 is another such client suffering from this crash. It's occurring on phones in the wild. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552371] Re: Unexpected display on
** Changed in: mir Milestone: 0.24.0 => 0.25.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1552371 Title: Unexpected display on Status in Canonical System Image: Incomplete Status in Mir: New Status in Unity System Compositor: New Status in bluez package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: NOTE: kgunn suggests this bug be about 1) not 2) here 1) I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI I also see the tablet display turn on while lying idle on the desk. Freiza & Arale 2) I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended. I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer. The proximity sensor is also not honored when this happens, if its covered the screen still comes on. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
** Changed in: mir Milestone: 0.24.0 => 0.25.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Triaged Status in mir package in Ubuntu: New Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1262116] Re: Nested servers prevent overlays or fullscreen bypass from working
** Changed in: mir Milestone: 0.24.0 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1262116 Title: Nested servers prevent overlays or fullscreen bypass from working Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: Nested servers prevent fullscreen bypass from working. This would explain why nesting fullscreen clients is measurably slower than non-nesting: Direct (bypass) 2600 Direct (bypass off) 2400 Nested (bypass) 2450 Nested (bypass off) 2330 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1262116/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame
** Changed in: mir Milestone: 0.24.0 => 0.25.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1570698 Title: CI failure in TestClientInput.receives_one_touch_event_per_frame Status in Mir: Triaged Status in mir package in Ubuntu: Triaged Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull 02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame 02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting 02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy (version 0.22.0) 02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor 02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display configuration: 02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm 02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 60.00Hz 02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 60.00Hz 02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0 02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: mir:stub-input (version: 0.22.0) 02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0 02:44:44 11: 02:44:44 11: GMOCK WARNING: 02:44:44 11: Uninteresting mock function call - returning directly. 02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 (133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1)) 02:44:44 11: Stack trace: 02:44:44 11: /��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639: Failure 02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 0.2400953674316, which exceeds 0.2f, where 02:44:44 11: 1.0f evaluates to 1, 02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, and 02:44:44 11: 0.2f evaluates to 0.2000298023224. 02:44:44 11: 02:44:44 11: GMOCK WARNING: 02:44:44 11: Uninteresting mock function call - returning directly. 02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 (10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1)) 02:44:45 11: Stack trace: 02:44:45 11: 02:44:45 11: GMOCK WARNING: 02:44:45 11: Uninteresting mock function call - returning directly. 02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 (14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1)) 02:44:45 11: Stack trace: 02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping 02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame (4083 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1570698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1537389] Re: Unity8 never loads and just stays on a black screen [unity8.log: ERROR: QMirServer - Mir failed to start]
** Changed in: mir Milestone: 0.24.0 => 0.25.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1537389 Title: Unity8 never loads and just stays on a black screen [unity8.log: ERROR: QMirServer - Mir failed to start] Status in Mir: Confirmed Status in mir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: The cursor is also not shown, neither is the Unity 8 Lock Screen or Indicators. Ubuntu 16.04 Daily ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8-desktop-session-mir 1.0.12+15.10.20150609-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.3-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 23 18:44:45 2016 InstallationDate: Installed on 2016-01-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) PackageArchitecture: all SourcePackage: unity8-desktop-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1537389/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563287] Re: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened
** Changed in: libhybris Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1563287 Title: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened Status in Canonical System Image: Fix Released Status in libhybris: Invalid Status in Mir: Fix Released Status in Mir 0.20 series: Fix Released Status in Mir 0.21 series: Fix Released Status in QtMir: Invalid Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Regression in OTA-10: tested on krillin and arale on rc-proposed. also I tried the fix for bug 1556763 but that's not related to this as well. The right edge switcher on both krillin and arale stutter when I drag it from the right edge and then swipe through the list of opened windows. This was not the case a few months ago, so we clearly regressed here. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565236] Re: AltGr not working on external keyboards
** No longer affects: mir/0.23 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1565236 Title: AltGr not working on external keyboards Status in Canonical System Image: Fix Committed Status in Mir: In Progress Status in mir package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Bug description: Using my keyboard with Spanish layout: - PC: Everything works perfect. - Ubuntu Touch: I can't write accented characters (dead acute, áéíóú). Extra info: - Keyboard: https://goo.gl/photos/xZUE8kRsReW1VKPA6 (http://www.logitech.com/en-hk/product/wireless-touch-keyboard-k400r2) - Ubuntu Desktop: 12.04 - Ubuntu Touch: bq Aquaris E4.5 15.04 (r305) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1565236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1583536] Re: mirtest-dev is hard to use as the objects used are compiled with LTO
** No longer affects: mir/0.23 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1583536 Title: mirtest-dev is hard to use as the objects used are compiled with LTO Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Linking against mirtest-dev in a downstream project fails as no symbols are not found in the archive. nm -gC /usr/lib/x86_64-linux-gnu/libmir-test-assist.a gives lots of "nm: FOO.cpp.o: plugin needed to handle lto object" errors Replacing the archive with one built without LTO fixes the problems. Adding LTO to the downstream project didn't. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1583536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590765] Re: OSK flickers and buttons are sometimes invisble
** Branch linked: lp:~kdub/mir/fix-1590765 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1590765 Title: OSK flickers and buttons are sometimes invisble Status in Canonical System Image: Fix Committed Status in Mir: In Progress Status in Mir 0.23 series: Fix Released Status in mir package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often invisible (pressing white part will refresh it and buttons are visible again) and OSK flickers a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590765] Re: OSK flickers and buttons are sometimes invisble
** Changed in: mir Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1590765 Title: OSK flickers and buttons are sometimes invisble Status in Canonical System Image: Fix Committed Status in Mir: In Progress Status in Mir 0.23 series: Fix Released Status in mir package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often invisible (pressing white part will refresh it and buttons are visible again) and OSK flickers a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590765] Re: OSK flickers and buttons are sometimes invisble
Seems the sequence that's happening is: many resize events happen, with the last resize event resizing to the same size as the keyboard started with. This triggers a reallocation of a buffer with the same size. The new buffer goes into the driver, and comes out unfilled. So, its looking like the driver is perhaps making a false assumption about buffer ordering... A good way to resolve might be to only trigger buffer allocation/freeing once we're sure that a size change has happened and a buffer is needed. (this would be more efficient in terms of reducing alloc/free anyways) ** Tags added: krillin -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1590765 Title: OSK flickers and buttons are sometimes invisble Status in Canonical System Image: Fix Committed Status in Mir: In Progress Status in Mir 0.23 series: Fix Released Status in mir package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often invisible (pressing white part will refresh it and buttons are visible again) and OSK flickers a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590765] Re: OSK flickers and buttons are sometimes invisble
workaround committed to mir 0.23.1 and released to images. Now working on proper fix for lp:mir ** Changed in: mir Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1590765 Title: OSK flickers and buttons are sometimes invisble Status in Canonical System Image: Fix Committed Status in Mir: In Progress Status in Mir 0.23 series: Fix Released Status in mir package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often invisible (pressing white part will refresh it and buttons are visible again) and OSK flickers a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590765] Re: OSK flickers and buttons are sometimes invisble
** Changed in: mir/0.23 Status: In Progress => Fix Released ** Changed in: mir Assignee: (unassigned) => Kevin DuBois (kdub) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1590765 Title: OSK flickers and buttons are sometimes invisble Status in Canonical System Image: Fix Committed Status in Mir: Confirmed Status in Mir 0.23 series: Fix Released Status in mir package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often invisible (pressing white part will refresh it and buttons are visible again) and OSK flickers a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590765] Re: OSK flickers and buttons are sometimes invisble
siloed in https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-043/+packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1590765 Title: OSK flickers and buttons are sometimes invisble Status in Canonical System Image: Confirmed Status in Mir: Confirmed Status in Mir 0.23 series: In Progress Status in mir package in Ubuntu: Confirmed Status in ubuntu-keyboard package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often invisible (pressing white part will refresh it and buttons are visible again) and OSK flickers a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590765] Re: OSK flickers and buttons are sometimes invisble
most reliable way to see: start camera and message app. Transition from camera app to message app. Swipe up to compose a new message. Tap the keyboard to see flickering. Problem is not permanent; rotating the screen will get the keyboard back into a good state. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1590765 Title: OSK flickers and buttons are sometimes invisble Status in Canonical System Image: Confirmed Status in Mir: Confirmed Status in ubuntu-keyboard package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often invisible (pressing white part will refresh it and buttons are visible again) and OSK flickers a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590765] Re: OSK flickers and buttons are sometimes invisble
Alright, so plan is to land the workaround in lp:~mir-team/mir/nbs- off-1590765 in mir 0.23.1 In the meantime, changing the options in the unity8.conf file so that MIR_SERVER_NBUFFERS=3 will correct affected images. ** Branch linked: lp:~mir-team/mir/nbs-off-1590765 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1590765 Title: OSK flickers and buttons are sometimes invisble Status in Canonical System Image: Confirmed Status in Mir: Confirmed Status in ubuntu-keyboard package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often invisible (pressing white part will refresh it and buttons are visible again) and OSK flickers a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590765] Re: OSK flickers and buttons are sometimes invisble
** Changed in: mir Milestone: None => 0.23.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1590765 Title: OSK flickers and buttons are sometimes invisble Status in Canonical System Image: Confirmed Status in Mir: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often invisible (pressing white part will refresh it and buttons are visible again) and OSK flickers a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590765] Re: OSK flickers and buttons are sometimes invisble
** Also affects: mir Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1590765 Title: OSK flickers and buttons are sometimes invisble Status in Canonical System Image: Confirmed Status in Mir: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often invisible (pressing white part will refresh it and buttons are visible again) and OSK flickers a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590765] Re: OSK flickers and buttons are sometimes invisble
We did change some buffering operations in the mir 0.23.0 release. A good way to test it would be to set initctl set-env MIR_SERVER_NBUFFERS=3 in the unity8.conf upstart file. If it goes away, we'll probably have to turn that option back off. (will prepare a branch to that effect) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1590765 Title: OSK flickers and buttons are sometimes invisble Status in Canonical System Image: Confirmed Status in ubuntu-keyboard package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: Latest rc-propoced image r348 for BQ E5, OSK kb buttons are often invisible (pressing white part will refresh it and buttons are visible again) and OSK flickers a lot. Also seen on MX4 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1566747] Re: Mir server with QtUbuntu client can cause system crash or Android GPU driver stall (Qualcomm)
Might be worth trying again in 0.23.0. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1566747 Title: Mir server with QtUbuntu client can cause system crash or Android GPU driver stall (Qualcomm) Status in Mir: Confirmed Status in qtubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Bug description: While investigating new surface occlusion work in unity8 I've noticed that resizing a client multiple times can cause the system to either crash or a kworker process to cycle at 100% while attempting to reset the GPU. Only seems to occur on Qualcomm devices To Reproduce: I've written an extension for the demo server which can be found @ https://code.launchpad.net/~nick-dedekind/mir/occlusion-test-failures Server: mir_demo_server --test-resize [--test-resize-timeout=200] Client: QT_QPA_PLATFORM=ubuntumirclient qmlscene Test.qml - [Test.qml] Item { width: 700 height: 1000 } - To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1566747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame
Another instance: https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1221/consoleFull -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1570698 Title: CI failure in TestClientInput.receives_one_touch_event_per_frame Status in Mir: Triaged Status in mir package in Ubuntu: Triaged Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull 02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame 02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting 02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy (version 0.22.0) 02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor 02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display configuration: 02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm 02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 60.00Hz 02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 60.00Hz 02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0 02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: mir:stub-input (version: 0.22.0) 02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0 02:44:44 11: 02:44:44 11: GMOCK WARNING: 02:44:44 11: Uninteresting mock function call - returning directly. 02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 (133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1)) 02:44:44 11: Stack trace: 02:44:44 11: /��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639: Failure 02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 0.2400953674316, which exceeds 0.2f, where 02:44:44 11: 1.0f evaluates to 1, 02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, and 02:44:44 11: 0.2f evaluates to 0.2000298023224. 02:44:44 11: 02:44:44 11: GMOCK WARNING: 02:44:44 11: Uninteresting mock function call - returning directly. 02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 (10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1)) 02:44:45 11: Stack trace: 02:44:45 11: 02:44:45 11: GMOCK WARNING: 02:44:45 11: Uninteresting mock function call - returning directly. 02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 (14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1)) 02:44:45 11: Stack trace: 02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping 02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame (4083 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1570698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584784] Re: Using NBS, X apps under Unity8 need interaction to start in pocket-desktop
** Changed in: mir/0.23 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: Using NBS, X apps under Unity8 need interaction to start in pocket- desktop Status in Mir: Fix Committed Status in Mir 0.23 series: Fix Committed Status in Mir 0.24 series: Fix Committed Status in QtMir: Invalid Status in mir package in Ubuntu: In Progress Status in qtmir package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: With Mir 0.23.0, X apps under Unity8 need some interaction to get the applications to start. 0.23.0 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506358] Re: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()
I targeted to 0.24, should probably have a look, especially if we're getting error reports from the 'field' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1506358 Title: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit() Status in Canonical System Image: Confirmed Status in Mir: Confirmed Status in mir package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Bug description: Under heavy resizing (stress testing under Valgrind), my Mir client (Xmir) crashed with: [1444895332.392862] MirBufferStreamAPI: Caught exception at client library boundary (in mir_buffer_stream_swap_buffers): /build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169): Throw in function virtual MirWaitHandle* {anonymous}::ExchangeSemantics::submit(const std::function&, mir::geometry::Size, MirPixelFormat, int) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: disconnected: no new buffers The strange thing is it's only the client that died. The server survived and I can connect new clients to it. Duplicate bug reports now show Unity8 is another such client suffering from this crash. It's occurring on phones in the wild. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506358] Re: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()
If there's an issue in the transport in mclr::MirProtobufRpcChannel::send_message during the sending of the message, it will trigger the disconnection code. If the client happens to be mid-mir_buffer_stream_swap_buffers at the same time that the the connection error trips the disconnection notification, we'll see that error. In the case of a true disconnection, the only reasonable thing the client code can do is to throw, as it can no longer appropriately fulfil the mir_buffer_stream_swap_buffers requirement. Also, iirc, there are certain things that the client can try to do that will cause the server to disconnect it, maybe its an issue like that? ** Changed in: mir Milestone: None => 0.24.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1506358 Title: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit() Status in Canonical System Image: Confirmed Status in Mir: Confirmed Status in mir package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Bug description: Under heavy resizing (stress testing under Valgrind), my Mir client (Xmir) crashed with: [1444895332.392862] MirBufferStreamAPI: Caught exception at client library boundary (in mir_buffer_stream_swap_buffers): /build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169): Throw in function virtual MirWaitHandle* {anonymous}::ExchangeSemantics::submit(const std::function&, mir::geometry::Size, MirPixelFormat, int) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: disconnected: no new buffers The strange thing is it's only the client that died. The server survived and I can connect new clients to it. Duplicate bug reports now show Unity8 is another such client suffering from this crash. It's occurring on phones in the wild. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506358] Re: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()
Hmm, if the server isn't dying, perhaps we're getting a false disconnection signal from the rpc code? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1506358 Title: libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit() Status in Canonical System Image: Confirmed Status in Mir: Confirmed Status in mir package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Invalid Bug description: Under heavy resizing (stress testing under Valgrind), my Mir client (Xmir) crashed with: [1444895332.392862] MirBufferStreamAPI: Caught exception at client library boundary (in mir_buffer_stream_swap_buffers): /build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169): Throw in function virtual MirWaitHandle* {anonymous}::ExchangeSemantics::submit(const std::function&, mir::geometry::Size, MirPixelFormat, int) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: disconnected: no new buffers The strange thing is it's only the client that died. The server survived and I can connect new clients to it. Duplicate bug reports now show Unity8 is another such client suffering from this crash. It's occurring on phones in the wild. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580774] Re: mouse is getting stuck on a phantom edge
** Branch unlinked: lp:mir/0.23 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1580774 Title: mouse is getting stuck on a phantom edge Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.22 series: Fix Released Status in Mir 0.23 series: Fix Committed Status in mir package in Ubuntu: Fix Committed Status in qtmir package in Ubuntu: Invalid Status in unity-system-compositor package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: frieza build 101/rc-proposed Steps: 1. connect mouse & keyboard to M10 2. launch xchat 3. go full screen 4. mouse move around across the entirety of the screen (landscape) expected: mouse can range over entire screen actual: gets stuck moving right note: i noticed it happening on xchat, but when changing focus to dash it was also continuing to happen So, i kinda suspect this may be related to rotation maybe. I do admit i did the full OOBE in portrait mode Problem is also persisting across reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584784] Re: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop
fix is wip, still testing... hope to get it out the door Tuesday (Monday is US holiday) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in QtMir: Invalid Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: With Mir 0.23.0, X apps under Unity8 need some interaction to get the applications to start. 0.23.0 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584784] Re: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop
** Changed in: qtmir Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in QtMir: Invalid Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: With Mir 0.23.0, X apps under Unity8 need some interaction to get the applications to start. 0.23.0 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584784] Re: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop
I didn't include an Xmir stack trace yesterday because it didn't appear stuck, it was submitting buffers (black frames) repeatedly. I compiled Xmir and added some logs. I caught swap_buffers blocking up in Xmir (in the pocket desktop scenario only, seems to be a racy, perhaps on how big the frame size is) but it seems the block triggers the scenario. And from poking around Xmir when the problem occurs, it seems like the "BlockHandler" is only called once, and the system stuck submitting frames repeatedly, instead of servicing the WM+Xapp connection requests. And furthermore, I think that the system only got in this case with libertine+UAL+unity8+pocketdesktop because when UAL's involved, Xmir+WM+Xapp get launched in very close sucession, whereas with the desktop test plan, they're manually launched, so they start "far" apart. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in QtMir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: With Mir 0.23.0, X apps under Unity8 need some interaction to get the applications to start. 0.23.0 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584784] Re: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop
seems matchbox is getting jammed trying to connect to the server too... I'm guessing this is why the map/realize isn't happing. ** Attachment added: "matchbox.txt" https://bugs.launchpad.net/mir/+bug/1584784/+attachment/4670915/+files/matchbox.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in QtMir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: With Mir 0.23.0, X apps under Unity8 need some interaction to get the applications to start. 0.23.0 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584784] Re: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop
Its very difficult to get backtraces for X apps when running in pocket desktop (had to rewrite puritine scripts to break out of confinement), but got a bt from Xeyes when the problem is occurring; bt is attached. ** Attachment added: "xeyes.txt" https://bugs.launchpad.net/mir/+bug/1584784/+attachment/4670897/+files/xeyes.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in QtMir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: With Mir 0.23.0, X apps under Unity8 need some interaction to get the applications to start. 0.23.0 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584784] Re: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop
Its also interesting that this only happens in pocket desktop mode. The applications start up successfully when in phone-mode. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: With Mir 0.23.0, X apps under Unity8 need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in QtMir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: With Mir 0.23.0, X apps under Unity8 need some interaction to get the applications to start. 0.23.0 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584784] Re: 0.23 xapps need interaction to start in pocket-desktop
Well, for some reason, this appears to be where the (gedit) window gets realized in our existing release: Atom _NET_WM_NAME = 267 Atom _NET_WM_WINDOW_TYPE = 295 Realize window 0xabaa7a98 "": 985x1093 +0+0 parent=0xab8dadc8 depth=24 redir=0 type=0 class=1 visibility=3 viewable=1 override=1 _NET_WM_WINDOW_TYPE=0 WM_TRANSIENT_FOR=(nil) Atom UTF8_STRING = 268 Realize window 0xabaadca0 "gedit": 985x1093 +0+0 parent=0xabaa7a98 depth=24 redir=0 type=0 class=1 visibility=3 viewable=1 override=0 _NET_WM_WINDOW_TYPE=254 WM_TRANSIENT_FOR=(nil) Realize window 0xabaadfa0 "": 1x1 -1-1 parent=0xabaadca0 depth=0 redir=0 type=2 class=2 visibility=3 viewable=0 override=0 _NET_WM_WINDOW_TYPE=0 WM_TRANSIENT_FOR=(nil) Atom _NET_WM_WINDOW_TYPE_NORMAL = 254 which doesn't happen in the 0.23 silo. The server will continue to schedule redraws, and resizing the window seems to cause it to realize. What events lead up to a window being realized on startup? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: 0.23 xapps need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in mir package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: in 0.23 the xapps need some interaction to get the applications to start. 0.23 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584784] Re: 0.23 xapps need interaction to start in pocket-desktop
also, havent been able to reproduce the behavior with the demo servers, just qtmir+Xmir on pocket desktop (where its easy to reproduce) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: 0.23 xapps need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in mir package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: in 0.23 the xapps need some interaction to get the applications to start. 0.23 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1584784] Re: 0.23 xapps need interaction to start in pocket-desktop
I think it might be something going on with the focus causing the window not to be realized (perhaps). I've checked that the buffers aren't getting 'stuck' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1584784 Title: 0.23 xapps need interaction to start in pocket-desktop Status in Mir: In Progress Status in Mir 0.23 series: In Progress Status in Mir 0.24 series: In Progress Status in mir package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: in 0.23 the xapps need some interaction to get the applications to start. 0.23 is blocked pending fix. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1584784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1537389] Re: The Desktop Never Loads and just stays on a black screen
right, which is a hybris bug, so 'incomplete' (or making this bug a dup of 1578461) seems appropriate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1537389 Title: The Desktop Never Loads and just stays on a black screen Status in Mir: Incomplete Status in mir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Status in unity8-desktop-session package in Ubuntu: Incomplete Bug description: The cursor is also not shown, neither is the Unity 8 Lock Screen or Indicators. Ubuntu 16.04 Daily ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8-desktop-session-mir 1.0.12+15.10.20150609-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.3-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 23 18:44:45 2016 InstallationDate: Installed on 2016-01-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160122.2) PackageArchitecture: all SourcePackage: unity8-desktop-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1537389/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578461] Re: Black screen: Mir servers (unity8, unity-system-compositor, mir_demo*) all crash on start-up in libhybris [linker.c:27: android_dlopen: Assertion `0' failed.']
untargetted to mir milestones, as the problem is being fixed in hybris ** Changed in: mir Milestone: 0.24.0 => None ** Changed in: mir/0.22 Milestone: 0.22.1 => None ** Changed in: mir/0.23 Milestone: 0.23.0 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1578461 Title: Black screen: Mir servers (unity8, unity-system-compositor, mir_demo*) all crash on start-up in libhybris [linker.c:27: android_dlopen: Assertion `0' failed.'] Status in Canonical System Image: In Progress Status in Mir: Invalid Status in Mir 0.22 series: Invalid Status in Mir 0.23 series: Invalid Status in libhybris package in Ubuntu: In Progress Status in mir package in Ubuntu: Invalid Status in unity-system-compositor package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Having mir-graphics-drivers-android9:amd64 installed prevents unity- system-compositor starting: [2016-05-05 10:19:09.118354] mirplatform: Found graphics driver: mir:mesa-kms (version 0.22.0) android_dlopen called but not implemented! unity-system-compositor: linker.c:27: android_dlopen: Assertion `0' failed. which was caused by: sudo apt-add-repository ppa:ci-train-ppa-service/stable-phone-overlay WORKING: hybris 0.1.0+git20151016+6d424c9-0ubuntu7 FAILING: hybris 0.1.0+git20151016+6d424c9-0ubuntu11 WORKAROUNDS: * Remove ppa:ci-train-ppa-service/stable-phone-overlay from your system to completely solve the problem; or * Don't use Unity8 -- other Mir servers will work after you remove package mir-graphics-drivers-android9:amd64 which is their last remaining dependency on libhybris. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557442] Re: NBS causes sudden loss of performance after un-fullscreening a swap interval zero client
*** This bug is a duplicate of bug 1579076 *** https://bugs.launchpad.net/bugs/1579076 ** This bug has been marked a duplicate of bug 1579076 Potential NBS performance loss after resize -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1557442 Title: NBS causes sudden loss of performance after un-fullscreening a swap interval zero client Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: NBS causes loss of frame dropping after un-fullscreening a window. When this occurs, the client only ever sees 2 buffers instead of 3, and so starts getting incorrectly sync'd to the screen: [2016-03-15 18:29:08.885810] perf: mir_demo_client_camera.bin: 186.81 FPS, render time 5.16ms, buffer lag 9.79ms (3 buffers) [2016-03-15 18:29:09.889336] perf: mir_demo_client_camera.bin: 187.43 FPS, render time 5.21ms, buffer lag 10.06ms (3 buffers) [2016-03-15 18:29:10.892904] perf: mir_demo_client_camera.bin: 187.43 FPS, render time 5.13ms, buffer lag 9.99ms (3 buffers) [2016-03-15 18:29:11.896299] perf: mir_demo_client_camera.bin: 187.43 FPS, render time 5.22ms, buffer lag 9.91ms (3 buffers) [2016-03-15 18:29:12.906866] perf: mir_demo_client_camera.bin: 170.29 FPS, render time 4.80ms, buffer lag 11.10ms (15 buffers) [2016-03-15 18:29:13.907306] perf: mir_demo_client_camera.bin: 60.00 FPS, render time 0.16ms, buffer lag 33.12ms (20 buffers) [2016-03-15 18:29:14.908295] perf: mir_demo_client_camera.bin: 60.00 FPS, render time 0.12ms, buffer lag 33.23ms (4 buffers) [2016-03-15 18:29:15.908972] perf: mir_demo_client_camera.bin: 60.00 FPS, render time 0.12ms, buffer lag 33.23ms (2 buffers) [2016-03-15 18:29:16.909945] perf: mir_demo_client_camera.bin: 60.00 FPS, render time 0.12ms, buffer lag 33.24ms (2 buffers) [2016-03-15 18:29:17.910827] perf: mir_demo_client_camera.bin: 60.00 FPS, render time 0.13ms, buffer lag 33.23ms (2 buffers) [2016-03-15 18:29:18.911693] perf: mir_demo_client_camera.bin: 60.00 FPS, render time 0.13ms, buffer lag 33.22ms (2 buffers) [2016-03-15 18:29:19.912521] perf: mir_demo_client_camera.bin: 60.00 FPS, render time 0.13ms, buffer lag 33.22ms (2 buffers) [2016-03-15 18:29:20.913369] perf: mir_demo_client_camera.bin: 60.00 FPS, render time 0.13ms, buffer lag 33.22ms (2 buffers) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1557442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1262116] Re: Nested servers prevent overlays or fullscreen bypass from working
** Changed in: mir Milestone: 0.23.0 => 0.24.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1262116 Title: Nested servers prevent overlays or fullscreen bypass from working Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: Nested servers prevent fullscreen bypass from working. This would explain why nesting fullscreen clients is measurably slower than non-nesting: Direct (bypass) 2600 Direct (bypass off) 2400 Nested (bypass) 2450 Nested (bypass off) 2330 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1262116/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame
** Changed in: mir Milestone: 0.23.0 => 0.24.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1570698 Title: CI failure in TestClientInput.receives_one_touch_event_per_frame Status in Mir: Triaged Status in mir package in Ubuntu: Invalid Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull 02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame 02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting 02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy (version 0.22.0) 02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor 02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display configuration: 02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm 02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800 60.00Hz 02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800 60.00Hz 02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0 02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver: mir:stub-input (version: 0.22.0) 02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0 02:44:44 11: 02:44:44 11: GMOCK WARNING: 02:44:44 11: Uninteresting mock function call - returning directly. 02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318 (133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger, x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1)) 02:44:44 11: Stack trace: 02:44:44 11: /��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639: Failure 02:44:44 11: The difference between 1.0f and client_input_events_per_frame is 0.2400953674316, which exceeds 0.2f, where 02:44:44 11: 1.0f evaluates to 1, 02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684, and 02:44:44 11: 0.2f evaluates to 0.2000298023224. 02:44:44 11: 02:44:44 11: GMOCK WARNING: 02:44:44 11: Uninteresting mock function call - returning directly. 02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976 (10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger, x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1)) 02:44:45 11: Stack trace: 02:44:45 11: 02:44:45 11: GMOCK WARNING: 02:44:45 11: Uninteresting mock function call - returning directly. 02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128 (14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger, x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1)) 02:44:45 11: Stack trace: 02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping 02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame (4083 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1570698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552371] Re: Unexpected display on
** Changed in: mir Milestone: 0.23.0 => 0.24.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1552371 Title: Unexpected display on Status in Canonical System Image: Confirmed Status in Mir: New Status in Unity System Compositor: New Status in bluez package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: NOTE: kgunn suggests this bug be about 1) not 2) here 1) I have been noticing my phone and tablet occasionally turning on without interaction. Several times with my phone in my pocket I found it in the emergency call UI I also see the tablet display turn on while lying idle on the desk. Freiza & Arale 2) I have reproduced one case such that turning on a BT device (headset) causes the phone to light up and display the volume slider. Similarly turning on the BT keyboard while the tablet screen is off caused the display to turn on.These may be as intended. I suspect other BT events can similarly resume the device and/or turn on the display if it happens to be awake due to the 5 min polling timer. The proximity sensor is also not honored when this happens, if its covered the screen still comes on. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
** Changed in: mir Status: In Progress => Triaged ** Changed in: mir Milestone: 0.23.0 => 0.24.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Triaged Status in mir package in Ubuntu: New Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563287] Re: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened
** Branch linked: lp:~kdub/mir/avert-1563287 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1563287 Title: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened Status in Canonical System Image: Confirmed Status in libhybris: New Status in Mir: Triaged Status in Mir 0.20 series: Triaged Status in Mir 0.21 series: Triaged Status in QtMir: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Regression in OTA-10: tested on krillin and arale on rc-proposed. also I tried the fix for bug 1556763 but that's not related to this as well. The right edge switcher on both krillin and arale stutter when I drag it from the right edge and then swipe through the list of opened windows. This was not the case a few months ago, so we clearly regressed here. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563287] Re: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened
@duflu, If you're testing with rev3297 you're likely to see the same sort of slowdown on arale. We disabled the fences in arale in 0.20.1, so our current images, as well as trunk should be fine (with this bug) on arale by now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1563287 Title: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened Status in Canonical System Image: Confirmed Status in libhybris: New Status in Mir: Triaged Status in Mir 0.20 series: Triaged Status in Mir 0.21 series: Triaged Status in QtMir: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Regression in OTA-10: tested on krillin and arale on rc-proposed. also I tried the fix for bug 1556763 but that's not related to this as well. The right edge switcher on both krillin and arale stutter when I drag it from the right edge and then swipe through the list of opened windows. This was not the case a few months ago, so we clearly regressed here. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563287] Re: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened
arale should not be using egl sync fences. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1563287 Title: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened Status in Canonical System Image: Confirmed Status in libhybris: New Status in Mir: Triaged Status in Mir 0.20 series: Triaged Status in Mir 0.21 series: Triaged Status in QtMir: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Regression in OTA-10: tested on krillin and arale on rc-proposed. also I tried the fix for bug 1556763 but that's not related to this as well. The right edge switcher on both krillin and arale stutter when I drag it from the right edge and then swipe through the list of opened windows. This was not the case a few months ago, so we clearly regressed here. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563287] Re: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened
@we can live without the synchronization... This was the suggestion to roll back the use of the sync extensions on mali. The current plan is to see how far we can get with hybris before OTA-11, and if we can't fix the performance in time, we'll roll back the sync extensions. The synchronization should be lightweight, and it should be done even with hardware clients. I think we're just fortunate that the commands are getting serialized between the clients and the server in the GPU. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1563287 Title: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened Status in Canonical System Image: Confirmed Status in libhybris: New Status in Mir: Triaged Status in Mir 0.20 series: Triaged Status in Mir 0.21 series: Triaged Status in QtMir: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Regression in OTA-10: tested on krillin and arale on rc-proposed. also I tried the fix for bug 1556763 but that's not related to this as well. The right edge switcher on both krillin and arale stutter when I drag it from the right edge and then swipe through the list of opened windows. This was not the case a few months ago, so we clearly regressed here. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563287] Re: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened
Its looking like the use of the eglCreateImageSyncKHR extension is causing thread activity (creation/destruction/TLS). Once mir started using these functions, it caused this timing increase in Mali cores, and lp: #1524414 in powervr ones. Linked to hybris, as its looking like this is a hybris/glibc threading issue. For mir, we can disable the use of these sync extensions on mali, until we can fix the deeper TLS problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1563287 Title: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened Status in Canonical System Image: Confirmed Status in libhybris: New Status in Mir: Triaged Status in Mir 0.20 series: Triaged Status in Mir 0.21 series: New Status in QtMir: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Regression in OTA-10: tested on krillin and arale on rc-proposed. also I tried the fix for bug 1556763 but that's not related to this as well. The right edge switcher on both krillin and arale stutter when I drag it from the right edge and then swipe through the list of opened windows. This was not the case a few months ago, so we clearly regressed here. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563287] Re: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened
** Also affects: libhybris Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1563287 Title: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened Status in Canonical System Image: Confirmed Status in libhybris: New Status in Mir: Triaged Status in Mir 0.20 series: Triaged Status in Mir 0.21 series: New Status in QtMir: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Regression in OTA-10: tested on krillin and arale on rc-proposed. also I tried the fix for bug 1556763 but that's not related to this as well. The right edge switcher on both krillin and arale stutter when I drag it from the right edge and then swipe through the list of opened windows. This was not the case a few months ago, so we clearly regressed here. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563287] Re: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened
Delving a bit deeper, it seems that we're wasting a fair amount of time in the mali driver during this operation with threading operations, including some calls to pthread_getspecific (ie, TLS), so it could be a cost of hybris -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1563287 Title: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened Status in Canonical System Image: Confirmed Status in Mir: Triaged Status in Mir 0.20 series: Triaged Status in Mir 0.21 series: New Status in QtMir: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Regression in OTA-10: tested on krillin and arale on rc-proposed. also I tried the fix for bug 1556763 but that's not related to this as well. The right edge switcher on both krillin and arale stutter when I drag it from the right edge and then swipe through the list of opened windows. This was not the case a few months ago, so we clearly regressed here. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563287] Re: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened
So to restate simply, the egl synchronization is costing 500us/client. (which is unreasonable, but a cost we cannot control without MTK/arm help). Trying to figure out alternatives. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1563287 Title: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened Status in Canonical System Image: Confirmed Status in Mir: Triaged Status in Mir 0.20 series: Triaged Status in Mir 0.21 series: New Status in QtMir: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Regression in OTA-10: tested on krillin and arale on rc-proposed. also I tried the fix for bug 1556763 but that's not related to this as well. The right edge switcher on both krillin and arale stutter when I drag it from the right edge and then swipe through the list of opened windows. This was not the case a few months ago, so we clearly regressed here. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563287] Re: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened
bit of measuring... the increase seems to average ~500us per map -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1563287 Title: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened Status in Canonical System Image: Confirmed Status in Mir: Triaged Status in Mir 0.20 series: Triaged Status in Mir 0.21 series: New Status in QtMir: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Regression in OTA-10: tested on krillin and arale on rc-proposed. also I tried the fix for bug 1556763 but that's not related to this as well. The right edge switcher on both krillin and arale stutter when I drag it from the right edge and then swipe through the list of opened windows. This was not the case a few months ago, so we clearly regressed here. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371146] Re: packaging bug in ubuntu-location-service-2/com/ubuntu/location/units/units.h
** Changed in: location-service (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1371146 Title: packaging bug in ubuntu-location- service-2/com/ubuntu/location/units/units.h Status in location-service package in Ubuntu: Fix Released Bug description: units.h contains this include: #include http://bazaar.launchpad.net/~phablet-team/location-service/trunk/view/head:/include/location_service/com/ubuntu/location/units/units.h#L21 which is only available in the libboost-dev package: $ apt-file search boost/units/cmath.hpp libboost1.54-dev: /usr/include/boost/units/cmath.hpp libboost1.55-dev: /usr/include/boost/units/cmath.hpp which are not in the build dependencies of the location service dev package. This causes problems for downstreams like platform-api, which only averts the build problem by including other dependencies that rely on boost (mir specifically) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1371146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488232] Re: server shutdown failure (segfault)
** Changed in: mir Assignee: Kevin DuBois (kdub) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488232 Title: server shutdown failure (segfault) Status in Mir: Confirmed Status in mir package in Ubuntu: New Bug description: Occasional shutdown segfault seen: Program received signal SIGSEGV, Segmentation fault. 0xb6e3f3c6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6 (gdb) bt #0 0xb6e3f3c6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6 #1 0xb6b5f94e in __gnu_cxx::new_allocator, (__gnu_cxx::_Lock_policy)2> >::deallocate (this=, __p=) at /usr/arm-linux-gnueabihf/include/c++/4.9.2/ext/new_allocator.h:110 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Happens more often when a client is actively sending messages (eg, swapping rapidly), and the server gets a SIGTERM. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1488232/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1563287] Re: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened
The 'buffering/GL' logic changes were installation of EGL sync points during GL draws so that software clients (eg, Xmir) have synchronized buffer releases. (fix https://bugs.launchpad.net/mir/+bug/1517205). Poking around this today, it seems that the actual installation of the sync points has some time cost (we have more cost on each buffer mapping with that proper synchronization). So, if many buffers need mapping, the time cost adds up. It is unreasonable that the driver should have any cost when calling eglCreateSyncFence, but that's mali code we don't have much control over. We have quirks that allow for disabling the synchronization, but we should avoid that if possible. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1563287 Title: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened Status in Canonical System Image: Confirmed Status in Mir: Triaged Status in Mir 0.20 series: Triaged Status in Mir 0.21 series: New Status in QtMir: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Regression in OTA-10: tested on krillin and arale on rc-proposed. also I tried the fix for bug 1556763 but that's not related to this as well. The right edge switcher on both krillin and arale stutter when I drag it from the right edge and then swipe through the list of opened windows. This was not the case a few months ago, so we clearly regressed here. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1563287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
Don't actually know of a currently supported device that does this. I suppose this is in progress with the NBS transition. ** Changed in: mir Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
Can be managed more easily with NBS, might be worth working on post 0.23 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1495974 Title: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues Status in Mir: Confirmed Status in mir package in Ubuntu: New Bug description: Some drivers will call android's perform hook with: NATIVE_WINDOW_SET_BUFFERS_FORMAT. In the case that the pixel formats are the same depth, we accommodate this by just setting the format to the newly-requested format. (ie, mir_pixel_format_rgbx_ to mir_pixel_format_rgba_ is accommodated, as no reallocation is needed). However, we've encountered a device that will try to set the format to HAL_PIXEL_FORMAT_RGB_888 when mir has selected HAL_PIXEL_FORMAT_RGBX_. Since we're going from a 32 bit format to a 24 bit format, the stride information becomes incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1495974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554635] Re: Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer'
So, it seems logging the problem and not throwing is an acceptable solution, although IMO, it merits further investigation as to why the driver is generating this error during certain scenarios. Will propose attached branch to lp:mir, and its looking like it'll ride along in 0.20.3 mir release. ** Branch unlinked: lp:~kdub/mir/potential-fix-1554635 ** Branch linked: lp:~kdub/mir/fix-1554635 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1554635 Title: Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer' Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in Mir 0.20 series: Incomplete Status in mir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Steps: Open Dekko or Telegram Go to import contacts Make sure you have a substantial amount of contacts in your phone When the contacts app is open in import mode, select all contact and press Tick Expected: contacts are imported succesfully Actual: Unity restarts (goes back to the ubuntu dot screen) and the contact import is interrupted To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554635] Re: Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer'
Was able to do a bit of remote debugging with mzanetti today, latest attempt packages are here: https://private-fileshare.canonical.com/~kdub/mir-debs-1554635-attempt3.tar.gz Seems the driver is failing with EGL_BAD_ALLOC when trying to install the sync point. Possibly a resource leak, or a loss of current egldisplay. The debs and updated branch will attempt to ignore the problem when it happens. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1554635 Title: Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer' Status in Canonical System Image: Confirmed Status in Mir: Incomplete Status in Mir 0.20 series: Incomplete Status in mir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Steps: Open Dekko or Telegram Go to import contacts Make sure you have a substantial amount of contacts in your phone When the contacts app is open in import mode, select all contact and press Tick Expected: contacts are imported succesfully Actual: Unity restarts (goes back to the ubuntu dot screen) and the contact import is interrupted To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554635] Re: Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer'
debs are at https://private-fileshare.canonical.com/~kdub/mir- debs-1554635.tar.gz. The subdirectory android-mir-1554635 contains the debs needed by the phone for the upgrade. Also, can I see the dmesg and /system/bin/logcat logs from when the crash occurs? Seeing if the driver is logging errors to these places will help diagnose the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1554635 Title: Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer' Status in Canonical System Image: Confirmed Status in Mir: Incomplete Status in Mir 0.20 series: Incomplete Status in mir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Steps: Open Dekko or Telegram Go to import contacts Make sure you have a substantial amount of contacts in your phone When the contacts app is open in import mode, select all contact and press Tick Expected: contacts are imported succesfully Actual: Unity restarts (goes back to the ubuntu dot screen) and the contact import is interrupted To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554635] Re: Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer'
Attached a branch that will at least ignore the exception. Without being able to reproduce myself (mir team doesn't have a turbo) or without seeing dmesg and logcat, its hard to tell if masking the exception is an appropriate response. Best guess though with information at this point in time is that its a transient problem that can be ignored. Could someone who can reproduce the problem try with the attached branch? ** Branch linked: lp:~kdub/mir/potential-fix-1554635 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1554635 Title: Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer' Status in Canonical System Image: Confirmed Status in Mir: Incomplete Status in Mir 0.20 series: Incomplete Status in mir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Steps: Open Dekko or Telegram Go to import contacts Make sure you have a substantial amount of contacts in your phone When the contacts app is open in import mode, select all contact and press Tick Expected: contacts are imported succesfully Actual: Unity restarts (goes back to the ubuntu dot screen) and the contact import is interrupted To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554635] Re: Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer'
@Lorn, could you collect the logs from /system/bin/logcat and dmesg when this happens? This would help figure out if its a resource leak or some other transient driver problem that we could potentially fix or ignore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1554635 Title: Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer' Status in Canonical System Image: Confirmed Status in Mir: Incomplete Status in Mir 0.20 series: Incomplete Status in mir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Steps: Open Dekko or Telegram Go to import contacts Make sure you have a substantial amount of contacts in your phone When the contacts app is open in import mode, select all contact and press Tick Expected: contacts are imported succesfully Actual: Unity restarts (goes back to the ubuntu dot screen) and the contact import is interrupted To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554635] Re: importing contacts trigger unity restart
which device? can a dmesg and logcat be attached? how many contacts are necessary? This could be a system resource exhaustion issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1554635 Title: importing contacts trigger unity restart Status in Canonical System Image: Confirmed Status in Mir: New Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Steps: Open Dekko or Telegram Go to import contacts Make sure you have a substantial amount of contacts in your phone When the contacts app is open in import mode, select all contact and press Tick Expected: contacts are imported succesfully Actual: Unity restarts (goes back to the ubuntu dot screen) and the contact import is interrupted To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1544878] Re: Mir servers crash if I press the side mouse button (thumb)
** Changed in: mir/0.20 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1544878 Title: Mir servers crash if I press the side mouse button (thumb) Status in Mir: Fix Committed Status in Mir 0.19 series: Won't Fix Status in Mir 0.20 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Mir servers crash if I press the side mouse button (thumb). There are two of them on the side of my Intellimouse Explorer 3.0. The kernel calls them BTN_SIDE and BTN_EXTRA. And X calls them buttons 8 and 9. When the crash happens I see in unity8.log: [1455268365.782990] MirSurfaceAPI: Caught exception at client library boundary (in mir_surface_release): /build/mir-wMQ7xO/mir-0.19.2+16.04.20160210/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector&, const std::vector&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to send message to server: Broken pipe 32, "Broken pipe" *** Error in `unity8': free(): invalid size: 0x7fcb4c03fe90 *** Also happens with the Mir demo servers; they segfault but without a usable stack trace due to exception handling. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1544878/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp