[Touch-packages] [Bug 1671370] Re: zesty clang 4.0 builds fail: /usr/include/capnp/layout.h:129:65: error: value of type 'bool' is not implicitly convertible to 'capnp::Kind'
Note capnp has been fixed upstream: https://github.com/sandstorm- io/capnproto/commit/0f1fd1938b19dccdb5dbfe9cb5177c4342a2a5b5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to capnproto in Ubuntu. https://bugs.launchpad.net/bugs/1671370 Title: zesty clang 4.0 builds fail: /usr/include/capnp/layout.h:129:65: error: value of type 'bool' is not implicitly convertible to 'capnp::Kind' Status in Mir: Incomplete Status in Mir 0.26 series: Incomplete Status in capnproto package in Ubuntu: New Status in llvm-defaults package in Ubuntu: New Bug description: 06:55:29 In file included from /<>/mir-0.26.0+zesty4262bzr4078/obj-x86_64-linux-gnu/src/capnproto/mir_event.capnp.c++:4: 06:55:29 In file included from /<>/mir-0.26.0+zesty4262bzr4078/obj-x86_64-linux-gnu/src/capnproto/mir_event.capnp.h:7: 06:55:29 In file included from /usr/include/capnp/generated-header-support.h:31: 06:55:29 /usr/include/capnp/layout.h:129:65: error: value of type 'bool' is not implicitly convertible to 'capnp::Kind' 06:55:29 template struct ElementSizeForType> { 06:55:29 ^ [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=zesty/4212/console] [https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=clang,platform=mesa,release=zesty/4211/console] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1671370/+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 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/
So actually, fontconfig does not cache conf files at all... it caches fonts but not conf files... fontconfg needs support to also cache the result of the parsing of the xml config file parsing. It seems a low priority effort for less than a 35ms improvement in startup. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1590804 Title: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/ Status in Canonical System Image: In Progress Status in fontconfig package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: Invalid Bug description: While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I noticed that a significant amount of time (around 35ms) was spent solely on parsing the XML configuration files in /etc/fonts/conf.d/ There seems to be around 40 files on Ubuntu Phone in that directory. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590804/+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 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/
Also FcInitReinitialize and FcInitBringUptoDate both will do the same thing the first time is called in the process, so wouldn't help for startup either. ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1590804 Title: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/ Status in Canonical System Image: In Progress Status in fontconfig package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: Invalid Bug description: While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I noticed that a significant amount of time (around 35ms) was spent solely on parsing the XML configuration files in /etc/fonts/conf.d/ There seems to be around 40 files on Ubuntu Phone in that directory. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590804/+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 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/
>From the attached backtrace, It seems that Qt calls FcInitReinitialize when populating its font database (a QGenericUnixFontDatabase instance provided by Qtubuntu) - that explains why re-parses the conf files everytime. See http://code.qt.io/cgit/qt/qtbase.git/tree/src/platformsupport/fontdatabases/fontconfig/qfontconfigdatabase.cpp?h=v5.4.1#n439 ** Attachment added: "backtrace.txt" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1590804/+attachment/4689148/+files/backtrace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1590804 Title: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/ Status in Canonical System Image: New Status in fontconfig package in Ubuntu: New Bug description: While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I noticed that a significant amount of time (around 35ms) was spent solely on parsing the XML configuration files in /etc/fonts/conf.d/ There seems to be around 40 files on Ubuntu Phone in that directory. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590804/+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 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/
I tried fc-cache, but starting a qml app still continues to open up the conf files. Digging through Qt source to understand where these calls are coming from. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1590804 Title: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/ Status in Canonical System Image: New Status in fontconfig package in Ubuntu: New Bug description: While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I noticed that a significant amount of time (around 35ms) was spent solely on parsing the XML configuration files in /etc/fonts/conf.d/ There seems to be around 40 files on Ubuntu Phone in that directory. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590804/+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 1554572] Re: [testsfail] ClientLatency.throttled_input_rate_yields_lower_latency
** 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/1554572 Title: [testsfail] ClientLatency.throttled_input_rate_yields_lower_latency Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/384/consoleFull 15:05:36 10: [ RUN ] ClientLatency.throttled_input_rate_yields_lower_latency 15:05:36 10: [2016-03-08 15:05:36.539365] mirserver: Starting 15:05:36 10: [2016-03-08 15:05:36.539747] mirserver: Selected driver: dummy (version 0.20.0) 15:05:36 10: [2016-03-08 15:05:36.541785] mirserver: Initial display configuration: 15:05:36 10: [2016-03-08 15:05:36.542037] mirserver: Using software cursor 15:05:36 10: [2016-03-08 15:05:36.543676] mirserver: Selected input driver: mir:stub-input (version: 0.20.0) 15:05:36 10: [2016-03-08 15:05:36.543864] mirserver: Mir version 0.20.0 15:05:38 10: [ debug ] 98 frames sampled, averaging 1.9 frames latency 15:05:38 10: [ debug ] 0: 0 1 1 1 2 2 2 2 2 2 15:05:38 10: [ debug ] 10: 2 2 2 2 2 2 2 2 2 2 15:05:38 10: [ debug ] 20: 2 2 2 2 2 2 2 2 2 2 15:05:38 10: [ debug ] 30: 2 2 2 2 2 2 2 2 2 2 15:05:38 10: [ debug ] 40: 2 2 2 2 2 2 2 2 2 2 15:05:38 10: [ debug ] 50: 2 2 2 2 2 2 2 2 2 2 15:05:38 10: [ debug ] 60: 2 2 2 2 2 2 2 2 2 2 15:05:38 10: [ debug ] 70: 2 2 2 2 2 2 2 2 2 2 15:05:38 10: [ debug ] 80: 2 2 2 2 2 2 2 2 2 2 15:05:38 10: [ debug ] 90: 2 2 2 2 2 2 2 2 15:05:38 10: /��BUILDDIR��/mir-0.20.1+16.04.20160225.1+vivid397bzr3374/tests/acceptance-tests/test_latency.cpp:350: Failure 15:05:38 10: Value of: observed_latency 15:05:38 10: Expected: is <= 1.4 15:05:38 10: Actual: 1.94898 (of type float) 15:05:38 10: [2016-03-08 15:05:38.301041] mirserver: Stopping 15:05:38 10: [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency (1777 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1554572/+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 1563278] Re: surface creation with non-default buffer streams is ignored by server
** 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/1563278 Title: surface creation with non-default buffer streams is ignored by server Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: If you create a Surface with a spec containing non-default BufferStreams/PresentationChains, the spec is ignored by the server. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1563278/+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 1557962] Re: NBS fullscreen overlay benchmark performance is much lower than BufferQueue
** 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/1557962 Title: NBS fullscreen overlay benchmark performance is much lower than BufferQueue Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: NBS fullscreen benchmark performance is much lower than BufferQueue. $ sudo bin/mir_proving_server --nbuffers=0 & $ sudo env MIR_CLIENT_PERF_REPORT=log glmark2-mir --fullscreen -b texture === glmark2 2014.03+git20150611.fa71af2d === OpenGL Information GL_VENDOR: Intel Open Source Technology Center GL_RENDERER: Mesa DRI Intel(R) Haswell Desktop GL_VERSION:3.0 Mesa 11.1.2 === [texture] :[2016-03-16 16:47:48.337501] perf: : 1270.00 FPS, render time 0.50ms, buffer lag 1.84ms (3 buffers) [2016-03-16 16:47:49.337541] perf: : 1284.00 FPS, render time 0.44ms, buffer lag 1.88ms (3 buffers) [2016-03-16 16:47:50.338014] perf: : 1311.00 FPS, render time 0.45ms, buffer lag 1.83ms (3 buffers) [2016-03-16 16:47:51.338506] perf: : 1299.00 FPS, render time 0.45ms, buffer lag 1.85ms (3 buffers) [2016-03-16 16:47:52.338721] perf: : 1309.00 FPS, render time 0.45ms, buffer lag 1.84ms (3 buffers) [2016-03-16 16:47:53.338970] perf: : 1296.00 FPS, render time 0.44ms, buffer lag 1.86ms (3 buffers) [2016-03-16 16:47:54.339363] perf: : 1300.00 FPS, render time 0.45ms, buffer lag 1.85ms (3 buffers) [2016-03-16 16:47:55.339693] perf: : 1299.00 FPS, render time 0.44ms, buffer lag 1.86ms (3 buffers) [2016-03-16 16:47:56.339954] perf: : 1300.00 FPS, render time 0.44ms, buffer lag 1.85ms (3 buffers) [2016-03-16 16:47:57.340275] perf: : 1306.00 FPS, render time 0.44ms, buffer lag 1.85ms (3 buffers) FPS: 1300 FrameTime: 0.769 ms === glmark2 Score: 1300 === $ sudo bin/mir_proving_server & $ sudo env MIR_CLIENT_PERF_REPORT=log glmark2-mir --fullscreen -b texture === glmark2 2014.03+git20150611.fa71af2d === OpenGL Information GL_VENDOR: Intel Open Source Technology Center GL_RENDERER: Mesa DRI Intel(R) Haswell Desktop GL_VERSION:3.0 Mesa 11.1.2 === [texture] :[2016-03-16 16:48:06.510089] perf: : 1795.00 FPS, render time 14238.16ms, buffer lag 1.68ms (4 buffers) [2016-03-16 16:48:07.510343] perf: : 1884.00 FPS, render time 0.44ms, buffer lag 1.67ms (4 buffers) [2016-03-16 16:48:08.510718] perf: : 1898.00 FPS, render time 0.44ms, buffer lag 1.66ms (4 buffers) [2016-03-16 16:48:09.511066] perf: : 1894.00 FPS, render time 0.44ms, buffer lag 1.66ms (4 buffers) [2016-03-16 16:48:10.511537] perf: : 1877.00 FPS, render time 0.44ms, buffer lag 1.68ms (4 buffers) [2016-03-16 16:48:11.511716] perf: : 1844.00 FPS, render time 0.44ms, buffer lag 1.72ms (4 buffers) [2016-03-16 16:48:12.511879] perf: : 1862.00 FPS, render time 0.44ms, buffer lag 1.69ms (4 buffers) [2016-03-16 16:48:13.512307] perf: : 1842.00 FPS, render time 0.45ms, buffer lag 1.71ms (4 buffers) [2016-03-16 16:48:14.512818] perf: : 1847.00 FPS, render time 0.44ms, buffer lag 1.71ms (4 buffers) [2016-03-16 16:48:15.513197] perf: : 1854.00 FPS, render time 0.45ms, buffer lag 1.70ms (4 buffers) FPS: 1863 FrameTime: 0.537 ms === glmark2 Score: 1863 === To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1557962/+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 1555074] Re: CI failure in NestedServer.display_orientation_changes_are_forwarded_to_host
** 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/1555074 Title: CI failure in NestedServer.display_orientation_changes_are_forwarded_to_host Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/385/consoleFull Seen on CI on an unrelated branch. Could not reproduce locally. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1555074/+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 1562340] Re: mir_demo_client_target does not quit after SIGTERM/SIGINT
** 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/1562340 Title: mir_demo_client_target does not quit after SIGTERM/SIGINT Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: mir_demo_client_target does not quit after SIGTERM/SIGINT. It hangs at pthread_cond_wait. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1562340/+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: 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/1563287 Title: [regression] [OTA-10] Spread animation stutters badly with only a few apps opened Status in Canonical System Image: In Progress Status in libhybris: New Status in Mir: Fix Released Status in Mir 0.20 series: Fix Committed Status in Mir 0.21 series: Fix Committed 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 1570357] Re: nested mir_demo_server crashes on mouse move when --print-input-events active
** 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/1570357 Title: nested mir_demo_server crashes on mouse move when --print-input-events active Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: The example code lacks handling of pointer events, and aborts. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1570357/+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 1563148] Re: ClientLogging.reports_performance fails under moderate load, is badly named
** 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/1563148 Title: ClientLogging.reports_performance fails under moderate load, is badly named Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Two problems: 1) The ClientLogging.reports_performance test is badly named, as it fails if performance is lower than expected. Leading to.. 2) The ClientLogging.reports_performance uses real-time and spuriously fails on a moderately-loaded system. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1563148/+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 1541188] Re: [regression] Tests fail with: std::exception::what: Failed to read from device: /dev/random after: 30 seconds
** 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/1541188 Title: [regression] Tests fail with: std::exception::what: Failed to read from device: /dev/random after: 30 seconds Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Tests fail with: std::exception::what: Failed to read from device: /dev/random after: 30 seconds Test case: 1. Reboot your system 2. mir_acceptance_tests --gtest_filter="PromptSessionClientAPI.*" Expected: Tests either pass or fail quickly (see bug 1540731) Observed: Tests hang for a long time and eventually report: ERROR: /build/mir-UeyFew/mir-0.19.0+16.04.20160128/src/cookie/authority.cpp(112): Throw in function mir::cookie::Secret get_random_data(unsigned int) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to read from device: /dev/random after: 30 seconds unknown file: Failure C++ exception with description "Failed to start server thread" thrown in SetUp(). Workaround: Log in to your system, move the mouse around and use it for a while before running tests. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1541188/+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 1568966] Re: [regression] mir_integration_tests take significantly longer (27x longer) when running with ctest
** 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/1568966 Title: [regression] mir_integration_tests take significantly longer (27x longer) when running with ctest Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: ran with bin/mir_integration_tests: [==] 268 tests from 39 test cases ran. (1636 ms total) ran with ctest: Start 11: mir_integration_tests 1/3 Test #11: mir_integration_tests Passed 44.79 sec To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1568966/+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 1570362] Re: nested mir_demo_server crashes on startup
** 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/1570362 Title: nested mir_demo_server crashes on startup Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Launch a mir_demo_server sudo ./bin/mir_demo_server --vt 2 --arw-file --file /tmp/test-mir --window-manager system-compositor and a nested one: ./bin/mir_demo_server --window-manager fullscreen --file /tmp/yada --host-socket /tmp/test-mir The nested server receives the input devices and attempts to access the Touchpad and Mouse configurations but does not ensure that the configuration is actually available. So it aborts in an attempt to access the content of the optional value. The configuration is missing since the client API for that has not yet been proposed.. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1570362/+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 1549701] Re: Sometimes devices don't suspend - display turns back on immediately
** 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/1549701 Title: Sometimes devices don't suspend - display turns back on immediately Status in Canonical System Image: Fix Committed Status in Mir: Fix Released Status in Mir 0.21 series: Fix Released Status in mir package in Ubuntu: Fix Released Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: current build number: 267 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en it happens also on arale. sometimes the screen lock timeout is not honoured and the devices don't suspend when the lock timeout expires (display doesn' t turn off) $ sudo powerd-cli list [sudo] password for phablet: System State Requests: Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1 Steps to reproduce on arale: 1. Turn on the screen 2. Touch the circular touch button at the lower part of the device 3. Press/release the power button to turn off screen 4. Release the circular touch button Expected results: The screen turns off and further on/off cycles work properly Actual results: The screen stays on and attempts to turn it off fail The touchscreen is handling the circular button and emits a key down event. When turning the screen of the touch screen device is turned off too. Mir is not aware of the touchscreen being off. So meanwhile the repeat handling kicks in and emits key events. This makes USC turn the screen back on again. The touchscreen driver does not notice that the circular button is still held. So still no release event is sent. We could fix this by: - fixing the touchscreen driver to release any touch contacts or buttons pressed, when the device is turned off (something the bluetooth stack seems to do on some devices) - sidestep the problem by making usc only react to press events as a wake trigger and make repeat and release events only reset the inactivity timer - give mir the knowledge that the disabled output also disables the touchscreen (a connection we need to be aware of to get the mapping of touch screen coordinates onto scene coordinates right), hence remove the device and thus turn of any repeat key handling attached to that device. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549701/+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 1550371] Re: Webbrowser slow scroll and artifact rendering on freiza
** 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/1550371 Title: Webbrowser slow scroll and artifact rendering on freiza Status in Canonical System Image: Fix Committed Status in Mir: Fix Released Status in Mir 0.20 series: Fix Committed Status in Mir 0.21 series: Fix Committed Status in Oxide: Invalid Status in mir package in Ubuntu: Triaged Status in webbrowser-app package in Ubuntu: Invalid Bug description: Copied from private avila bug: https://bugs.launchpad.net/avila-private/+bug/1547569 STEPS: 1. Install the latest image 2. Open the browser 3. Goto ubuntu.com 4. Wait for the page to load 5. Scroll the page EXPECT Smooth scrolling and rendering as seen on arale and krillin ACTUAL: Very slow render time on most site with a lot of content Scrolling is glitchy and seems to want to fresh render each page as it is scrolled This is most prominently seen on ubuntu.com but also ebay and amazon webapps. Webbrowser seems to display the issue the most although I beleive it is more likely to be the graphics stack somewhere, tvoss believe that perfservice will hopefully solve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550371/+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 1560943] Re: Racy shutdown in mir_demo_client_scroll causes SEGFAULT
** 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/1560943 Title: Racy shutdown in mir_demo_client_scroll causes SEGFAULT Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: This example responds to SIGTERM (and SIGINT) by calling exit() - without taking any precaution to prevent other threads running simultaneously. This can lead to a SEGFAULT. I got a core by running: $ while bin/mir_demo_server --test-timeout 1 --test-client bin/mir_demo_client_scroll ; do :; done Which eventually failed this way. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1560943/+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 1573782] Re: Virtual display output configuration is set to LVDS
** Changed in: mir/0.22 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/1573782 Title: Virtual display output configuration is set to LVDS Status in Mir: Fix Committed Status in Mir 0.22 series: Fix Released Status in mir package in Ubuntu: New Bug description: The display output type associated with a virtual display is set to mir_display_output_type_lvds. Ideally a new type "mir_display_output_type_virtual" should be added and the virtual output should use it to as its type. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1573782/+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 1342092] Re: mir_acceptance_tests & mir_unit_tests dump core files (even when everything passes)
** 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/1342092 Title: mir_acceptance_tests & mir_unit_tests dump core files (even when everything passes) Status in Mir: Fix Released Status in mir package in Ubuntu: Triaged Bug description: :~$ mir_acceptance_tests Running main() from command_line_server_configuration.cpp [==] Running 116 tests from 29 test cases. [--] Global test environment set-up. [--] 6 tests from ServerConfigurationWrapping [ RUN ] ServerConfigurationWrapping.surface_coordinator_is_of_wrapper_type [ OK ] ServerConfigurationWrapping.surface_coordinator_is_of_wrapper_type (1 ms) [ RUN ] ServerConfigurationWrapping.can_override_surface_coordinator_methods [ OK ] ServerConfigurationWrapping.can_override_surface_coordinator_methods (0 ms) [ RUN ] ServerConfigurationWrapping.returns_same_surface_coordinator_from_cache [ OK ] ServerConfigurationWrapping.returns_same_surface_coordinator_from_cache (0 ms) [ RUN ] ServerConfigurationWrapping.session_coordinator_is_of_wrapper_type [ OK ] ServerConfigurationWrapping.session_coordinator_is_of_wrapper_type (1 ms) [ RUN ] ServerConfigurationWrapping.can_override_session_coordinator_methods [ OK ] ServerConfigurationWrapping.can_override_session_coordinator_methods (0 ms) [ RUN ] ServerConfigurationWrapping.returns_same_session_coordinator_from_cache [ OK ] ServerConfigurationWrapping.returns_same_session_coordinator_from_cache (0 ms) [--] 6 tests from ServerConfigurationWrapping (2 ms total) [--] 17 tests from ClientLibrary [ RUN ] ClientLibrary.client_library_connects_and_disconnects [ OK ] ClientLibrary.client_library_connects_and_disconnects (3 ms) [ RUN ] ClientLibrary.synchronous_connection [ OK ] ClientLibrary.synchronous_connection (1 ms) [ RUN ] ClientLibrary.creates_surface [ OK ] ClientLibrary.creates_surface (1 ms) [ RUN ] ClientLibrary.can_set_surface_types [ OK ] ClientLibrary.can_set_surface_types (24 ms) [ RUN ] ClientLibrary.can_set_surface_state [ OK ] ClientLibrary.can_set_surface_state (22 ms) [ RUN ] ClientLibrary.receives_surface_dpi_value [ OK ] ClientLibrary.receives_surface_dpi_value (1 ms) [ RUN ] ClientLibrary.surface_scanout_flag_toggles [ OK ] ClientLibrary.surface_scanout_flag_toggles (2 ms) [ RUN ] ClientLibrary.gets_buffer_dimensions [ OK ] ClientLibrary.gets_buffer_dimensions (1 ms) [ RUN ] ClientLibrary.creates_multiple_surfaces [ OK ] ClientLibrary.creates_multiple_surfaces (3 ms) [ RUN ] ClientLibrary.client_library_accesses_and_advances_buffers [ OK ] ClientLibrary.client_library_accesses_and_advances_buffers (4 ms) [ RUN ] ClientLibrary.fully_synchronous_client [ OK ] ClientLibrary.fully_synchronous_client (0 ms) [ RUN ] ClientLibrary.highly_threaded_client [ OK ] ClientLibrary.highly_threaded_client (6 ms) [ RUN ] ClientLibrary.accesses_platform_package [ OK ] ClientLibrary.accesses_platform_package (1 ms) [ RUN ] ClientLibrary.accesses_display_info [ OK ] ClientLibrary.accesses_display_info (1 ms) [ RUN ] ClientLibrary.connect_errors_handled [ OK ] ClientLibrary.connect_errors_handled (0 ms) [ RUN ] ClientLibrary.connect_errors_dont_blow_up [ OK ] ClientLibrary.connect_errors_dont_blow_up (1 ms) [ RUN ] ClientLibrary.MultiSurfaceClientTracksBufferFdsCorrectly [ OK ] ClientLibrary.MultiSurfaceClientTracksBufferFdsCorrectly (76 ms) [--] 17 tests from ClientLibrary (149 ms total) [--] 2 tests from ClientLibraryThread [ RUN ] ClientLibraryThread.HandlesNoSignals [ OK ] ClientLibraryThread.HandlesNoSignals (11 ms) [ RUN ] ClientLibraryThread.DoesNotInterfereWithClientSignalHandling [ OK ] ClientLibraryThread.DoesNotInterfereWithClientSignalHandling (7 ms) [ RUN ] ClientLibraryThread.HandlesNoSignals [--] 2 tests from ClientLibraryThread (18 ms total) [--] 2 tests from ClientSurfaceEvents [ RUN ] ClientSurfaceEvents.surface_receives_state_events [ OK ] ClientSurfaceEvents.surface_receives_state_events (18 ms) [ RUN ] ClientSurfaceEvents.client_can_query_current_orientation [ OK ] ClientSurfaceEvents.client_can_query_current_orientation (5 ms) [--] 2 tests from ClientSurfaceEvents (23 ms total) [--] 3 tests from CustomInputDispatcher [ RUN ] CustomInputDispatcher.receives_input [ OK ] CustomInputDispatcher.receives_input (12 ms) [ RUN ] CustomInputDispatcher.gets_started_and_stop
[Touch-packages] [Bug 1557442] Re: NBS causes sudden loss of performance after un-fullscreening a swap interval zero client
** 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/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 1560900] Re: server crashes when shutting down in smoke tests
** 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/1560900 Title: server crashes when shutting down in smoke tests Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: The "smoke tests" run each of the demo clients for 3 seconds and ensure they and the server all exit cleanly. But we've seen an instance where this fails: https://mir-jenkins.ubuntu.com/job/device-runtests- mir/device_type=krillin/240/consoleFull 05:09:56 Starting 05:09:56 libevdev error in fix_invalid_absinfo: BUG: Device "mtk-tpd" has invalid ABS_MT_TRACKING_ID rangeConnected 05:09:56 Mir chose pixel format 1 05:09:56 Surface created 05:09:59 Signal 15 received. Good night. 05:10:08 /home/phablet/mir-testrunner/mir-smoke-test-runner.sh: line 23: 10047 Segmentation fault (core dumped) ${root}mir_demo_server --test-timeout=$timeout --test-client $root$client 05:10:08 I: [FAILED] mir_demo_client_scroll This looks like the server crashed between signalling the client and shutting down. All 21 of the other smoke tests pass: 05:11:48 I: The following clients failed to execute successfully: 05:11:48 I: mir_demo_client_scroll 05:11:48 I: Smoke testing complete with returncode -1 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1560900/+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 1573572] Re: Virtual output is not removed when screencast client disappears
** Changed in: mir/0.22 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/1573572 Title: Virtual output is not removed when screencast client disappears Status in Canonical System Image: New Status in Mir: Fix Committed Status in Mir 0.22 series: Fix Released Status in mir package in Ubuntu: New Bug description: With WiFi Display we're using the screencast API from our management service aethercast to create an virtual display which is then used by Unity 8. If aethercast crashes the virtual output seems to stay as Unity 8 never switches back from the virtual touchpad its displaying since the virtual output is use. When aethercast terminates the screencast connection Unity 8 switches correctly back to the phone interface. I suspect this is reproducible with mirscreencast too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1573572/+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 1499229] Re: [regression] [testsfail] failure in CI on ThreadedDispatcherSignalTest.keeps_dispatching_after_signal_interruption under Valgrind
** 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/1499229 Title: [regression] [testsfail] failure in CI on ThreadedDispatcherSignalTest.keeps_dispatching_after_signal_interruption under Valgrind Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Opening a new bug, rather than recycling lp:1441620 9: [ RUN ] ThreadedDispatcherSignalTest.keeps_dispatching_after_signal_interruption 9: ==26614== 9: ==26614== FILE DESCRIPTORS: 2 open at exit. 9: ==26614== Open file descriptor 2: 9: ==26614== 9: ==26614== 9: ==26614== Open file descriptor 1: 9: ==26614== 9: ==26614== 9: ==26614== 9: ==26614== HEAP SUMMARY: 9: ==26614== in use at exit: 95,523 bytes in 757 blocks 9: ==26614== total heap usage: 843,952 allocs, 843,195 frees, 135,376,735 bytes allocated 9: ==26614== 9: ==26614== LEAK SUMMARY: 9: ==26614== definitely lost: 0 bytes in 0 blocks 9: ==26614== indirectly lost: 0 bytes in 0 blocks 9: ==26614== possibly lost: 852 bytes in 22 blocks 9: ==26614== still reachable: 94,179 bytes in 729 blocks 9: ==26614== of which reachable via heuristic: 9: ==26614== newarray : 1,244 bytes in 39 blocks 9: ==26614== suppressed: 0 bytes in 0 blocks 9: ==26614== Reachable blocks (those to which a pointer was found) are not shown. 9: ==26614== To see them, rerun with: --leak-check=full --show-leak-kinds=all 9: ==26614== 9: ==26614== For counts of detected and suppressed errors, rerun with: -v 9: ==26614== Use --track-origins=yes to see where uninitialised values come from 9: ==26614== ERROR SUMMARY: 2443 errors from 8 contexts (suppressed: 129883 from 41) 9: /tmp/buildd/mir-0.18.0bzr3187pkg0xenial129+autopilot0/tests/unit-tests/dispatch/test_threaded_dispatcher.cpp:382: Failure 9: Value of: result.succeeded() 9: Actual: false 9: Expected: true 9: [ FAILED ] ThreadedDispatcherSignalTest.keeps_dispatching_after_signal_interruption (2710 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1499229/+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 1528109] Re: [regression] Cursor mostly does not move at all in response to slow mouse movement, but then sometimes jumps
** 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/1528109 Title: [regression] Cursor mostly does not move at all in response to slow mouse movement, but then sometimes jumps Status in Mir: Fix Released Status in Mir 0.18 series: Won't Fix Status in Mir 0.20 series: Triaged Status in Mir 0.21 series: Fix Committed Status in libinput package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Starting in Mir 0.18 I've noticed with a Microsoft Intellimouse Explorer 3.0 that moving it slowly does not move the cursor. That is unless I move it slowly for a while, and then the cursor jumps. Xorg and Mir 0.17 do not have this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1528109/+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 1536662] Re: [regression] Black screen: Mir hangs and then crashes on startup/login due to reading from /dev/random
** 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/1536662 Title: [regression] Black screen: Mir hangs and then crashes on startup/login due to reading from /dev/random Status in Mir: Fix Released Status in Mir 0.19 series: Won't Fix Status in Mir 0.20 series: Won't Fix Status in Mir 0.21 series: Triaged Status in Unity System Compositor: Fix Committed Status in mir package in Ubuntu: Triaged Status in unity-system-compositor package in Ubuntu: Fix Released Bug description: cookie_factory attempts to read data from /dev/random at boot, and blocks until it has enough random data or timesout after 30 seconds. How I can reproduce 1. Run the Unity8 greeter as a mir server 2. Reboot Expected behavior: Greeter is displayed as mir && USC run happily Actual behavior: Mir throws an exception after 30 seconds Work-around: Before logging in, move the mouse around lots, for at least 20 seconds. And after logging in, while you're looking at a black screen, move the mouse around furiously. This will populate the kernel entropy pool sufficiently to avoid the hang and crash. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1536662/+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 1560415] Re: CI test failures on xenial amd64 due to valgrind errors following system upgrade to ld-2.23
** 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/1560415 Title: CI test failures on xenial amd64 due to valgrind errors following system upgrade to ld-2.23 Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: We started seeing failures in all our xenial amd64 CI jobs after an upgrade to ld-2.23. The error causing valgrind to fail is: 06:50:15 11: ==4076== Conditional jump or move depends on uninitialised value(s) 06:50:15 11: ==4076== at 0x401B8E8: index (in /lib/x86_64-linux-gnu/ld-2.23.so) 06:50:15 11: ==4076== by 0x4007BDC: fillin_rpath (in /lib/x86_64-linux-gnu/ld-2.23.so) 06:50:15 11: ==4076== by 0x4008609: _dl_init_paths (in /lib/x86_64-linux-gnu/ld-2.23.so) 06:50:15 11: ==4076== by 0x40032F7: dl_main (in /lib/x86_64-linux-gnu/ld-2.23.so) 06:50:15 11: ==4076== by 0x4019521: _dl_sysdep_start (in /lib/x86_64-linux-gnu/ld-2.23.so) 06:50:15 11: ==4076== by 0x4004E79: _dl_start (in /lib/x86_64-linux-gnu/ld-2.23.so) 06:50:15 11: ==4076== by 0x4000CC7: ??? (in /lib/x86_64-linux-gnu/ld-2.23.so) 06:50:15 11: ==4076== by 0x1: ??? 06:50:15 11: ==4076== by 0xFFF00038A: ??? 06:50:15 11: ==4076== by 0xFFF0003EA: ??? Examples: https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial/561/ https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial/562/ ... To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1560415/+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 1543495] Re: [FHD] boot splash not in native orientation
** No longer affects: unity-system-compositor/0.5 -- 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/1543495 Title: [FHD] boot splash not in native orientation Status in The Avila project: Confirmed Status in Canonical System Image: Fix Released Status in Unity System Compositor: Fix Committed Status in Unity System Compositor 0.4 series: Fix Committed Status in unity-system-compositor package in Ubuntu: Fix Released Bug description: When the frieza is booted, the 'ubuntu + dots' splash from unity is displayed in portrait. The natural (out of the box) orientation for this device is landscape. I expected the splash to display in landscape. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1543495/+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: None => 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/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 1495974] Re: [android] renogotiation of pixel formats is not supported, leading to potential stride/pixelformat issues
** Changed in: mir Milestone: 0.22.0 => 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/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 1262116] Re: Nested servers prevent overlays or fullscreen bypass from working
** Changed in: mir Milestone: 0.22.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 1549701] Re: Sometimes devices don't suspend - display turns back on immediately
** Changed in: mir Importance: Undecided => High ** Changed in: mir/0.21 Importance: Undecided => High -- 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/1549701 Title: Sometimes devices don't suspend - display turns back on immediately Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in Mir 0.21 series: Fix Committed Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: current build number: 267 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en it happens also on arale. sometimes the screen lock timeout is not honoured and the devices don't suspend when the lock timeout expires (display doesn' t turn off) $ sudo powerd-cli list [sudo] password for phablet: System State Requests: Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1 Steps to reproduce on arale: 1. Turn on the screen 2. Touch the circular touch button at the lower part of the device 3. Press/release the power button to turn off screen 4. Release the circular touch button Expected results: The screen turns off and further on/off cycles work properly Actual results: The screen stays on and attempts to turn it off fail The touchscreen is handling the circular button and emits a key down event. When turning the screen of the touch screen device is turned off too. Mir is not aware of the touchscreen being off. So meanwhile the repeat handling kicks in and emits key events. This makes USC turn the screen back on again. The touchscreen driver does not notice that the circular button is still held. So still no release event is sent. We could fix this by: - fixing the touchscreen driver to release any touch contacts or buttons pressed, when the device is turned off (something the bluetooth stack seems to do on some devices) - sidestep the problem by making usc only react to press events as a wake trigger and make repeat and release events only reset the inactivity timer - give mir the knowledge that the disabled output also disables the touchscreen (a connection we need to be aware of to get the mapping of touch screen coordinates onto scene coordinates right), hence remove the device and thus turn of any repeat key handling attached to that device. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549701/+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 1549701] Re: Sometimes devices don't suspend - display turns back on immediately
** Also affects: mir Importance: Undecided Status: New ** Changed in: mir Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny) ** Changed in: mir Status: New => In Progress ** Also affects: mir/0.21 Importance: Undecided Status: New ** Changed in: mir/0.21 Status: New => Fix Committed ** Changed in: mir/0.21 Milestone: None => 0.21.0 ** Changed in: mir Milestone: None => 0.22.0 -- 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/1549701 Title: Sometimes devices don't suspend - display turns back on immediately Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in Mir 0.21 series: Fix Committed Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: current build number: 267 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en it happens also on arale. sometimes the screen lock timeout is not honoured and the devices don't suspend when the lock timeout expires (display doesn' t turn off) $ sudo powerd-cli list [sudo] password for phablet: System State Requests: Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1 Steps to reproduce on arale: 1. Turn on the screen 2. Touch the circular touch button at the lower part of the device 3. Press/release the power button to turn off screen 4. Release the circular touch button Expected results: The screen turns off and further on/off cycles work properly Actual results: The screen stays on and attempts to turn it off fail The touchscreen is handling the circular button and emits a key down event. When turning the screen of the touch screen device is turned off too. Mir is not aware of the touchscreen being off. So meanwhile the repeat handling kicks in and emits key events. This makes USC turn the screen back on again. The touchscreen driver does not notice that the circular button is still held. So still no release event is sent. We could fix this by: - fixing the touchscreen driver to release any touch contacts or buttons pressed, when the device is turned off (something the bluetooth stack seems to do on some devices) - sidestep the problem by making usc only react to press events as a wake trigger and make repeat and release events only reset the inactivity timer - give mir the knowledge that the disabled output also disables the touchscreen (a connection we need to be aware of to get the mapping of touch screen coordinates onto scene coordinates right), hence remove the device and thus turn of any repeat key handling attached to that device. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549701/+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 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)
@Peter, that would explain the behavior then. "So, is this maybe a hardware defect? In a series of devices of the same model?" That's a possibility; A look at the proximity device driver and/or sensor stack wouldn't hurt though... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1493574 Title: [vegeta] Phone app makes screen stay black during call (so you can't hang up) Status in Canonical System Image: Incomplete Status in powerd package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: A similar, if not the same bug, has been reported to be fixed for OTA6. This bug report explains that it's no necessary to wait for a minute or so on the phone call, but the screen turns black immediately, and doesn't turn back on again to allow hanging up via a screen control. Potential duplicate: https://bugs.launchpad.net/canonical-devices- system-image/+bug/1483127 Device: Aquaris E5 HD Ubuntu Edition OS version: 15.04 (r5) A) Incoming phone call: - Accept the incoming call by sliding the grey middle button to the green button - Watch the screen turning black - Bring the phone to your ear, speak (as in a normal phone call) - Take the phone away from your ear, note that the screen stays black How to hang up anyway: (workaround) - (continued from above, screen stays black after taking it away from your ear) - Press the screen lock/unlock button (= button above volume control) - Screen with phone app shows for about half a second, then turns black again - Press the screen lock/unlock button again, and try to press the red hangup button quickly - Repeat the previous step until hanging up succeeds B) Outbound phone call: - Open the phone app - Slide up Recent calls list from bottom edge, select a phone number - Press green dial button to initiate the call - Watch the phone dialling and the screen turning black - Bring the phone to your ear, speak (as in a normal phone call) - Take the phone away from your ear, note that the screen stays black How to hang up anyway: (workaround) - (same procedure as in A. above) - Difference in behavior: * In some calls after pressing the lock/unlock button for the first time the screen stays alight (doesn't turn black again after half a second). Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list: In both cases, covering/uncovering the proximity sensor should turn the screen on, if the screen has not been turned off with the power button. (This is not happening.) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493574/+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'
** Changed in: mir/0.20 Status: Incomplete => 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/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: Fix Committed Status in Mir 0.20 series: Fix Committed 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'
** Changed in: mir Status: Incomplete => 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/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 1262116] Re: Nested servers prevent overlays or fullscreen bypass from working
** Changed in: mir Milestone: 0.21.0 => 0.22.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 1342092] Re: mir_acceptance_tests & mir_unit_tests dump core files (even when everything passes)
** Changed in: mir Milestone: 0.21.0 => 0.22.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/1342092 Title: mir_acceptance_tests & mir_unit_tests dump core files (even when everything passes) Status in Mir: In Progress Status in mir package in Ubuntu: Triaged Bug description: :~$ mir_acceptance_tests Running main() from command_line_server_configuration.cpp [==] Running 116 tests from 29 test cases. [--] Global test environment set-up. [--] 6 tests from ServerConfigurationWrapping [ RUN ] ServerConfigurationWrapping.surface_coordinator_is_of_wrapper_type [ OK ] ServerConfigurationWrapping.surface_coordinator_is_of_wrapper_type (1 ms) [ RUN ] ServerConfigurationWrapping.can_override_surface_coordinator_methods [ OK ] ServerConfigurationWrapping.can_override_surface_coordinator_methods (0 ms) [ RUN ] ServerConfigurationWrapping.returns_same_surface_coordinator_from_cache [ OK ] ServerConfigurationWrapping.returns_same_surface_coordinator_from_cache (0 ms) [ RUN ] ServerConfigurationWrapping.session_coordinator_is_of_wrapper_type [ OK ] ServerConfigurationWrapping.session_coordinator_is_of_wrapper_type (1 ms) [ RUN ] ServerConfigurationWrapping.can_override_session_coordinator_methods [ OK ] ServerConfigurationWrapping.can_override_session_coordinator_methods (0 ms) [ RUN ] ServerConfigurationWrapping.returns_same_session_coordinator_from_cache [ OK ] ServerConfigurationWrapping.returns_same_session_coordinator_from_cache (0 ms) [--] 6 tests from ServerConfigurationWrapping (2 ms total) [--] 17 tests from ClientLibrary [ RUN ] ClientLibrary.client_library_connects_and_disconnects [ OK ] ClientLibrary.client_library_connects_and_disconnects (3 ms) [ RUN ] ClientLibrary.synchronous_connection [ OK ] ClientLibrary.synchronous_connection (1 ms) [ RUN ] ClientLibrary.creates_surface [ OK ] ClientLibrary.creates_surface (1 ms) [ RUN ] ClientLibrary.can_set_surface_types [ OK ] ClientLibrary.can_set_surface_types (24 ms) [ RUN ] ClientLibrary.can_set_surface_state [ OK ] ClientLibrary.can_set_surface_state (22 ms) [ RUN ] ClientLibrary.receives_surface_dpi_value [ OK ] ClientLibrary.receives_surface_dpi_value (1 ms) [ RUN ] ClientLibrary.surface_scanout_flag_toggles [ OK ] ClientLibrary.surface_scanout_flag_toggles (2 ms) [ RUN ] ClientLibrary.gets_buffer_dimensions [ OK ] ClientLibrary.gets_buffer_dimensions (1 ms) [ RUN ] ClientLibrary.creates_multiple_surfaces [ OK ] ClientLibrary.creates_multiple_surfaces (3 ms) [ RUN ] ClientLibrary.client_library_accesses_and_advances_buffers [ OK ] ClientLibrary.client_library_accesses_and_advances_buffers (4 ms) [ RUN ] ClientLibrary.fully_synchronous_client [ OK ] ClientLibrary.fully_synchronous_client (0 ms) [ RUN ] ClientLibrary.highly_threaded_client [ OK ] ClientLibrary.highly_threaded_client (6 ms) [ RUN ] ClientLibrary.accesses_platform_package [ OK ] ClientLibrary.accesses_platform_package (1 ms) [ RUN ] ClientLibrary.accesses_display_info [ OK ] ClientLibrary.accesses_display_info (1 ms) [ RUN ] ClientLibrary.connect_errors_handled [ OK ] ClientLibrary.connect_errors_handled (0 ms) [ RUN ] ClientLibrary.connect_errors_dont_blow_up [ OK ] ClientLibrary.connect_errors_dont_blow_up (1 ms) [ RUN ] ClientLibrary.MultiSurfaceClientTracksBufferFdsCorrectly [ OK ] ClientLibrary.MultiSurfaceClientTracksBufferFdsCorrectly (76 ms) [--] 17 tests from ClientLibrary (149 ms total) [--] 2 tests from ClientLibraryThread [ RUN ] ClientLibraryThread.HandlesNoSignals [ OK ] ClientLibraryThread.HandlesNoSignals (11 ms) [ RUN ] ClientLibraryThread.DoesNotInterfereWithClientSignalHandling [ OK ] ClientLibraryThread.DoesNotInterfereWithClientSignalHandling (7 ms) [ RUN ] ClientLibraryThread.HandlesNoSignals [--] 2 tests from ClientLibraryThread (18 ms total) [--] 2 tests from ClientSurfaceEvents [ RUN ] ClientSurfaceEvents.surface_receives_state_events [ OK ] ClientSurfaceEvents.surface_receives_state_events (18 ms) [ RUN ] ClientSurfaceEvents.client_can_query_current_orientation [ OK ] ClientSurfaceEvents.client_can_query_current_orientation (5 ms) [--] 2 tests from ClientSurfaceEvents (23 ms total) [--] 3 tests from CustomInputDispatcher [ RUN ] CustomInputDispatcher.receives_input [ OK ] CustomInputDispatcher.receives_input (12 ms) [ RUN ] CustomInputDispatcher.gets_started_and_stopped [
[Touch-packages] [Bug 1536662] Re: [regression] Black screen: Mir hangs and then crashes on startup/login due to reading from /dev/random
** Changed in: mir Milestone: 0.21.0 => 0.22.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/1536662 Title: [regression] Black screen: Mir hangs and then crashes on startup/login due to reading from /dev/random Status in Mir: In Progress Status in Mir 0.19 series: Won't Fix Status in Mir 0.20 series: Triaged Status in Unity System Compositor: Fix Committed Status in mir package in Ubuntu: Triaged Status in unity-system-compositor package in Ubuntu: Fix Released Bug description: cookie_factory attempts to read data from /dev/random at boot, and blocks until it has enough random data or timesout after 30 seconds. How I can reproduce 1. Run the Unity8 greeter as a mir server 2. Reboot Expected behavior: Greeter is displayed as mir && USC run happily Actual behavior: Mir throws an exception after 30 seconds Work-around: Before logging in, move the mouse around lots, for at least 20 seconds. And after logging in, while you're looking at a black screen, move the mouse around furiously. This will populate the kernel entropy pool sufficiently to avoid the hang and crash. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1536662/+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 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)
Hi Peter, I have a suspicion your proximity sensor may not be working correctly. Could you install this ProximityCheck app in your phone: https://uappexplorer.com/app/proximitycheck.albaguirre and record a video of what you see? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1493574 Title: [vegeta] Phone app makes screen stay black during call (so you can't hang up) Status in Canonical System Image: Incomplete Status in powerd package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: A similar, if not the same bug, has been reported to be fixed for OTA6. This bug report explains that it's no necessary to wait for a minute or so on the phone call, but the screen turns black immediately, and doesn't turn back on again to allow hanging up via a screen control. Potential duplicate: https://bugs.launchpad.net/canonical-devices- system-image/+bug/1483127 Device: Aquaris E5 HD Ubuntu Edition OS version: 15.04 (r5) A) Incoming phone call: - Accept the incoming call by sliding the grey middle button to the green button - Watch the screen turning black - Bring the phone to your ear, speak (as in a normal phone call) - Take the phone away from your ear, note that the screen stays black How to hang up anyway: (workaround) - (continued from above, screen stays black after taking it away from your ear) - Press the screen lock/unlock button (= button above volume control) - Screen with phone app shows for about half a second, then turns black again - Press the screen lock/unlock button again, and try to press the red hangup button quickly - Repeat the previous step until hanging up succeeds B) Outbound phone call: - Open the phone app - Slide up Recent calls list from bottom edge, select a phone number - Press green dial button to initiate the call - Watch the phone dialling and the screen turning black - Bring the phone to your ear, speak (as in a normal phone call) - Take the phone away from your ear, note that the screen stays black How to hang up anyway: (workaround) - (same procedure as in A. above) - Difference in behavior: * In some calls after pressing the lock/unlock button for the first time the screen stays alight (doesn't turn black again after half a second). Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list: In both cases, covering/uncovering the proximity sensor should turn the screen on, if the screen has not been turned off with the power button. (This is not happening.) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493574/+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 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)
Hi Peter, So I just tried to replicate this in my E5 but haven't been able to. How frequently do you encounter this issue? Like every 10 times you receive a call, how many of those do you encounter the issue reported? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1493574 Title: [vegeta] Phone app makes screen stay black during call (so you can't hang up) Status in Canonical System Image: Incomplete Status in powerd package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: A similar, if not the same bug, has been reported to be fixed for OTA6. This bug report explains that it's no necessary to wait for a minute or so on the phone call, but the screen turns black immediately, and doesn't turn back on again to allow hanging up via a screen control. Potential duplicate: https://bugs.launchpad.net/canonical-devices- system-image/+bug/1483127 Device: Aquaris E5 HD Ubuntu Edition OS version: 15.04 (r5) A) Incoming phone call: - Accept the incoming call by sliding the grey middle button to the green button - Watch the screen turning black - Bring the phone to your ear, speak (as in a normal phone call) - Take the phone away from your ear, note that the screen stays black How to hang up anyway: (workaround) - (continued from above, screen stays black after taking it away from your ear) - Press the screen lock/unlock button (= button above volume control) - Screen with phone app shows for about half a second, then turns black again - Press the screen lock/unlock button again, and try to press the red hangup button quickly - Repeat the previous step until hanging up succeeds B) Outbound phone call: - Open the phone app - Slide up Recent calls list from bottom edge, select a phone number - Press green dial button to initiate the call - Watch the phone dialling and the screen turning black - Bring the phone to your ear, speak (as in a normal phone call) - Take the phone away from your ear, note that the screen stays black How to hang up anyway: (workaround) - (same procedure as in A. above) - Difference in behavior: * In some calls after pressing the lock/unlock button for the first time the screen stays alight (doesn't turn black again after half a second). Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list: In both cases, covering/uncovering the proximity sensor should turn the screen on, if the screen has not been turned off with the power button. (This is not happening.) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1493574/+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
If 1) happens without keyboard or mouse attached that definitely counts as a bug As for proximity - the main issue is there's no API to query the current state of the sensor (as Alexandros mentioned). However done properly the power drain should be minimal as it should only be turned on during an off to on transition (at least to handle the cases described here). -- 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 bluez package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New 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 1528384] Re: unity-system-compositor crashed with std::runtime_error in mir::compositor::CompositingFunctor::wait_until_started() from usc::MirScreen::set_screen_power_mode (mir_
** Also affects: mir/0.19 Importance: Undecided Status: New ** Also affects: mir/0.20 Importance: Undecided Status: New ** Changed in: mir/0.19 Status: New => Fix Released -- 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/1528384 Title: unity-system-compositor crashed with std::runtime_error in mir::compositor::CompositingFunctor::wait_until_started() from usc::MirScreen::set_screen_power_mode (mir_power_mode_on) Status in Canonical System Image: Confirmed Status in Mir: Fix Committed Status in Mir 0.19 series: Fix Released Status in Mir 0.20 series: New Status in Unity System Compositor: In Progress Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: Top crash over past week (ww02) on errors.u.c for rc-proposed channels. Started with u-s-c 0.2.0+15.04.20151216.1-0ubuntu1 The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with version 0.2.0+15.04.20151216.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/7bcfcf599b35b264c0be45d5290ad9ae3c50adcf contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1528384/+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 1532607] Re: Phone not usable while a call comes in - followed by "restart"
** Changed in: mir/0.19 Status: New => Fix Committed ** Changed in: mir/0.20 Status: New => Fix Committed -- 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/1532607 Title: Phone not usable while a call comes in - followed by "restart" Status in Canonical System Image: Confirmed Status in Mir: Fix Committed Status in Mir 0.19 series: Fix Committed Status in Mir 0.20 series: Fix Committed Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: My system: current build number: 225 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-09 06:52:53 version version: 225 version ubuntu: 20160109 version device: 20151216-378d4f3 version custom: 2015--36-46-vivid What happened: Someone called me and I wanted to take the call on the phone (nothing attached to the phone). The screen was locked and I pressed the power button to unlock the screen. The phone did not react on any pushed buttons. The phone continued ringing but I was not able to do anything with the phone during this time. During the next minute the phone was blocked. After this period a "restart" followed. "Restart": The restart was not a real reset. The phone screen was black. Then approx. 1 - 2 minutes after the call was gone, the screen went on again and the ubuntu logo with the dots appeared (same screen when you start the phone but without the "bq"-screen). I did not need to enter the PIN code of the SIM card. The phone was again fully operational. This happened on January, 10th at approx. 13:30 h. I have attached the sys.log for your review and hopefully for tracing back the issue to the root cause. Matthias To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+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 1543594] Re: unity-system-compositor locked up in __libc_do_syscall()
lp:mir r3288 -- 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/1543594 Title: unity-system-compositor locked up in __libc_do_syscall() Status in Mir: Fix Committed Status in Mir 0.19 series: Fix Committed Status in Mir 0.20 series: Fix Committed Status in Unity System Compositor: New Status in unity-system-compositor package in Ubuntu: New Bug description: This happened when I got an incoming call, couldn't wake the screen up, even though the phone worked fine otherwise. powerd-cli list took ~20s to return https://paste.ubuntu.com/15001777/ for u-s-c trace https://paste.ubuntu.com/15001805/ tamer powerd trace ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity-system-compositor 0.4.1+15.04.20160203-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Tue Feb 9 15:06:13 2016 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1454530118 GraphicsCard: InstallationDate: Installed on 2016-02-06 (3 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160206-020305) ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 10 --to-dm-fd 13 --vt 1 ProcCwd: / ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 __lll_lock_wait (futex=futex@entry=0x6402fc, private=0) at lowlevellock.c:46 __GI___pthread_mutex_lock (mutex=0x6402fc) at pthread_mutex_lock.c:80 __gthread_mutex_lock (__mutex=0x6402fc) at /usr/include/arm-linux-gnueabihf/c++/4.9/bits/gthr-default.h:748 lock (this=0x6402fc) at /usr/include/c++/4.9/mutex:135 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.60-2 version.lightdm: lightdm 1.14.4-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1543594/+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 1543594] Re: unity-system-compositor locked up in __libc_do_syscall()
** Changed in: mir/0.20 Status: New => Fix Committed -- 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/1543594 Title: unity-system-compositor locked up in __libc_do_syscall() Status in Mir: Fix Committed Status in Mir 0.19 series: Fix Committed Status in Mir 0.20 series: Fix Committed Status in Unity System Compositor: New Status in unity-system-compositor package in Ubuntu: New Bug description: This happened when I got an incoming call, couldn't wake the screen up, even though the phone worked fine otherwise. powerd-cli list took ~20s to return https://paste.ubuntu.com/15001777/ for u-s-c trace https://paste.ubuntu.com/15001805/ tamer powerd trace ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity-system-compositor 0.4.1+15.04.20160203-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Tue Feb 9 15:06:13 2016 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1454530118 GraphicsCard: InstallationDate: Installed on 2016-02-06 (3 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160206-020305) ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 10 --to-dm-fd 13 --vt 1 ProcCwd: / ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 __lll_lock_wait (futex=futex@entry=0x6402fc, private=0) at lowlevellock.c:46 __GI___pthread_mutex_lock (mutex=0x6402fc) at pthread_mutex_lock.c:80 __gthread_mutex_lock (__mutex=0x6402fc) at /usr/include/arm-linux-gnueabihf/c++/4.9/bits/gthr-default.h:748 lock (this=0x6402fc) at /usr/include/c++/4.9/mutex:135 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.60-2 version.lightdm: lightdm 1.14.4-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1543594/+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 1532607] Re: Phone not usable while a call comes in - followed by "restart"
** Branch linked: lp:mir/0.19 -- 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/1532607 Title: Phone not usable while a call comes in - followed by "restart" Status in Canonical System Image: Confirmed Status in Mir: New Status in Mir 0.19 series: New Status in Mir 0.20 series: New Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: My system: current build number: 225 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-09 06:52:53 version version: 225 version ubuntu: 20160109 version device: 20151216-378d4f3 version custom: 2015--36-46-vivid What happened: Someone called me and I wanted to take the call on the phone (nothing attached to the phone). The screen was locked and I pressed the power button to unlock the screen. The phone did not react on any pushed buttons. The phone continued ringing but I was not able to do anything with the phone during this time. During the next minute the phone was blocked. After this period a "restart" followed. "Restart": The restart was not a real reset. The phone screen was black. Then approx. 1 - 2 minutes after the call was gone, the screen went on again and the ubuntu logo with the dots appeared (same screen when you start the phone but without the "bq"-screen). I did not need to enter the PIN code of the SIM card. The phone was again fully operational. This happened on January, 10th at approx. 13:30 h. I have attached the sys.log for your review and hopefully for tracing back the issue to the root cause. Matthias To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+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 1532607] Re: Phone not usable while a call comes in - followed by "restart"
@Daniel, The OP also reports a "restart", whose description match what would happen if USC restarts... so we are going by our suspicion that it's related to the failure to start the compositor threads. The error logs in unity8 (USC's client) are irrelevant in that case. -- 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/1532607 Title: Phone not usable while a call comes in - followed by "restart" Status in Canonical System Image: Confirmed Status in Mir: New Status in Mir 0.19 series: New Status in Mir 0.20 series: New Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: My system: current build number: 225 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-09 06:52:53 version version: 225 version ubuntu: 20160109 version device: 20151216-378d4f3 version custom: 2015--36-46-vivid What happened: Someone called me and I wanted to take the call on the phone (nothing attached to the phone). The screen was locked and I pressed the power button to unlock the screen. The phone did not react on any pushed buttons. The phone continued ringing but I was not able to do anything with the phone during this time. During the next minute the phone was blocked. After this period a "restart" followed. "Restart": The restart was not a real reset. The phone screen was black. Then approx. 1 - 2 minutes after the call was gone, the screen went on again and the ubuntu logo with the dots appeared (same screen when you start the phone but without the "bq"-screen). I did not need to enter the PIN code of the SIM card. The phone was again fully operational. This happened on January, 10th at approx. 13:30 h. I have attached the sys.log for your review and hopefully for tracing back the issue to the root cause. Matthias To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+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 1543594] Re: unity-system-compositor locked up in __libc_do_syscall()
** Also affects: mir/0.19 Importance: Undecided Status: New ** Also affects: mir/0.20 Importance: Undecided Status: New ** Changed in: mir/0.19 Milestone: None => 0.19.2 ** Changed in: mir/0.20 Milestone: None => 0.20.0 -- 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/1543594 Title: unity-system-compositor locked up in __libc_do_syscall() Status in Mir: New Status in Mir 0.19 series: New Status in Mir 0.20 series: New Status in unity-system-compositor package in Ubuntu: New Bug description: This happened when I got an incoming call, couldn't wake the screen up, even though the phone worked fine otherwise. powerd-cli list took ~20s to return https://paste.ubuntu.com/15001777/ for u-s-c trace https://paste.ubuntu.com/15001805/ tamer powerd trace ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity-system-compositor 0.4.1+15.04.20160203-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Tue Feb 9 15:06:13 2016 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1454530118 GraphicsCard: InstallationDate: Installed on 2016-02-06 (3 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160206-020305) ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 10 --to-dm-fd 13 --vt 1 ProcCwd: / ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46 __lll_lock_wait (futex=futex@entry=0x6402fc, private=0) at lowlevellock.c:46 __GI___pthread_mutex_lock (mutex=0x6402fc) at pthread_mutex_lock.c:80 __gthread_mutex_lock (__mutex=0x6402fc) at /usr/include/arm-linux-gnueabihf/c++/4.9/bits/gthr-default.h:748 lock (this=0x6402fc) at /usr/include/c++/4.9/mutex:135 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.60-2 version.lightdm: lightdm 1.14.4-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1543594/+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 1532607] Re: Phone not usable while a call comes in - followed by "restart"
** Changed in: mir Milestone: None => 0.19.2 ** Also affects: mir/0.20 Importance: Critical Status: New ** Also affects: mir/0.19 Importance: Undecided Status: New ** Changed in: mir/0.20 Milestone: 0.19.2 => 0.20.0 ** Changed in: mir/0.19 Milestone: None => 0.19.2 -- 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/1532607 Title: Phone not usable while a call comes in - followed by "restart" Status in Canonical System Image: Confirmed Status in Mir: New Status in Mir 0.19 series: New Status in Mir 0.20 series: New Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: My system: current build number: 225 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-09 06:52:53 version version: 225 version ubuntu: 20160109 version device: 20151216-378d4f3 version custom: 2015--36-46-vivid What happened: Someone called me and I wanted to take the call on the phone (nothing attached to the phone). The screen was locked and I pressed the power button to unlock the screen. The phone did not react on any pushed buttons. The phone continued ringing but I was not able to do anything with the phone during this time. During the next minute the phone was blocked. After this period a "restart" followed. "Restart": The restart was not a real reset. The phone screen was black. Then approx. 1 - 2 minutes after the call was gone, the screen went on again and the ubuntu logo with the dots appeared (same screen when you start the phone but without the "bq"-screen). I did not need to enter the PIN code of the SIM card. The phone was again fully operational. This happened on January, 10th at approx. 13:30 h. I have attached the sys.log for your review and hopefully for tracing back the issue to the root cause. Matthias To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+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 1538632] Re: ui freezes when simultaneously moving mouse & plug/unplug hdmi
** Changed in: mir Milestone: 0.20.0 => 0.19.2 ** Also affects: mir/0.20 Importance: Critical Assignee: Andreas Pokorny (andreas-pokorny) Status: Fix Committed ** Changed in: mir/0.20 Milestone: 0.19.2 => 0.20.0 ** Also affects: mir/0.19 Importance: Undecided Status: New ** Changed in: mir/0.19 Milestone: None => 0.19.2 -- 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/1538632 Title: ui freezes when simultaneously moving mouse & plug/unplug hdmi Status in Canonical Pocket Desktop: In Progress Status in Mir: Fix Committed Status in Mir 0.19 series: New Status in Mir 0.20 series: Fix Committed Status in mir package in Ubuntu: In Progress Bug description: confirmed to happen in latest image with usc0.3 and previous images with usc0.2 steps 1) flash ubuntu-touch/rc-proposed/ubuntu-pd 2) connect bt mouse and see unity8 go into windowed mode 3) move mouse about screen while at the same time connect slimport hdmi cable ui will then freeze but seems content, let it sit for 30 min no reboot or restart, no crash files, power button does not do anything. It's also possible to have the slimport already connected - move mouse around disconnect, the ui will freeze altho in this case unity8 always seems to restart. There are no usc crash files. The problem is a dead lock on the Display/DisplaySyncGroup mutexes between CompositingFunctor->SystemWindowManager->GraphicsDisplayLayout and DisplayInputRegion. Thread 6 (Thread 0xb0dff3d0 (LWP 1530)): #0 0xb6cd5d44 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0 No symbol table info available. #1 0xb6cd395c in __lll_lock_wait () from /lib/arm-linux-gnueabihf/libpthread.so.0 No symbol table info available. #2 0xb6ccf19e in pthread_mutex_lock () from /lib/arm-linux-gnueabihf/libpthread.so.0 No symbol table info available. #3 0xb6426f02 in __gthread_mutex_lock (__mutex=0x1b34f14) at /usr/include/arm-linux-gnueabihf/c++/4.9/bits/gthr-default.h:748 No locals. #4 lock (this=0x1b34f14) at /usr/include/c++/4.9/mutex:135 No locals. #5 lock_guard (__m=..., this=0xb0dfeaf0) at /usr/include/c++/4.9/mutex:377 No locals. #6 mir::graphics::android::Display::configuration (this=0x1b34ef8) at /build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/platforms/android/server/display.cpp:231 lock = {_M_device = @0x1b34f14} #7 0xb6e656ca in mir::shell::GraphicsDisplayLayout::place_in_output (this=, id=..., rect=...) at /build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/shell/graphics_display_layout.cpp:72 config = std::unique_ptr containing 0xb6eb69c8 placed = false #8 0xb6e6a888 in mir::shell::SystemCompositorWindowManager::add_display (this=0x1d07b24) at /build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/shell/system_compositor_window_manager.cpp:1 output_id = rect = {top_left = {x = {value = 0}, y = {value = 0}}, size = {width = {value = 768}, height = { value = 1280}}} surface = std::shared_ptr (count 3, weak 4) 0x0 __for_range = lock = {_M_device = @0x1d07b3c} #9 0xb6e1ab32 in operator() (buffer=..., __closure=) at /build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:96 No locals. #10 std::_Function_handler::_M_invoke(std::_Any_data const&, mir::graphics::DisplayBuffer&) (__functor=..., __args#0=...) at /usr/include/c++/4.9/functional:2039 No locals. #11 0xb64288a8 in operator() (__args#0=..., this=0xb0dfeca0) at /usr/include/c++/4.9/functional:2439 No locals. #12 mir::graphics::android::DisplayGroup::for_each_display_buffer(std::function const&) (this=0x1b35024, f=...) at /build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/platforms/android/server/display_group.cpp:51 __for_range = std::map with 1 elements = { [mir::graphics::android::DisplayName::primary] = std::unique_ptr containing 0x1c0db40} lk = {_M_device = 0x1b35028, _M_owns = true} #13 0xb6e1b896 in operator() (__closure=) at /build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:96 No locals. #14 PairedCalls (deleter=, creator=, this=0xb0dfec84) at /build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/include/common/mir/raii.h:33 No locals. #15 paired_calls, mir::compositor::CompositingFunctor::operator()():: > (deleter=, creator=) at /build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/include/common/mir/raii.h:66 No locals. #16 mir::compositor::CompositingFunctor::operator() (this=0x1d112d8) at /build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:98 disp_listener = std::shared_ptr
[Touch-packages] [Bug 1535297] Re: Unity8 crashes on session logout on desktop
Ooops s/libmirprotobuf/libprotobuf (typo) -- 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/1535297 Title: Unity8 crashes on session logout on desktop Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: This is happening on a fresh setup, which is basically: Xenial 17Jan iso + unity8-desktop-session-mir package When I logout, I get a black screen. Turns out unity8 is crashing with a "double free or linked list corruption" Please find unity8.log attached To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1535297/+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 1535297] Re: Unity8 crashes on session logout on desktop
Right, so somehow unity8 loads libmirprotobuf (a plugin perhaps?) Not much we can do from mir side. It's a consequence of loading libprotobuf and libprotobuf-lite in the same process, as the library symbols will have name collisions (a protobuf issue). -- 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/1535297 Title: Unity8 crashes on session logout on desktop Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: This is happening on a fresh setup, which is basically: Xenial 17Jan iso + unity8-desktop-session-mir package When I logout, I get a black screen. Turns out unity8 is crashing with a "double free or linked list corruption" Please find unity8.log attached To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1535297/+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 1535297] Re: Unity8 crashes on session logout on desktop
** Changed in: mir (Ubuntu) Status: New => Invalid ** 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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1535297 Title: Unity8 crashes on session logout on desktop Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: This is happening on a fresh setup, which is basically: Xenial 17Jan iso + unity8-desktop-session-mir package When I logout, I get a black screen. Turns out unity8 is crashing with a "double free or linked list corruption" Please find unity8.log attached To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1535297/+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 1535297] Re: Unity8 crashes on session logout on desktop
An strace log would be helpful to see what's loading libprotobuf. -- 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/1535297 Title: Unity8 crashes on session logout on desktop Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: This is happening on a fresh setup, which is basically: Xenial 17Jan iso + unity8-desktop-session-mir package When I logout, I get a black screen. Turns out unity8 is crashing with a "double free or linked list corruption" Please find unity8.log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1535297/+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 1535297] Re: Unity8 crashes on session logout on desktop
It's a protobuf problem really. The issue is Mir's libmirprotobuf links against libprotobuf-lite; the call to ShutdownProtobufLibrary is expected to be resolved by libprotobuf-lite; in this case presumably libprotobuf was also loaded and the linker is resolving "ShutdownProtobufLibrary" to libmirprotobuf instead hence the crash. -- 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/1535297 Title: Unity8 crashes on session logout on desktop Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: This is happening on a fresh setup, which is basically: Xenial 17Jan iso + unity8-desktop-session-mir package When I logout, I get a black screen. Turns out unity8 is crashing with a "double free or linked list corruption" Please find unity8.log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1535297/+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 1524131] Re: /usr/bin/mediaplayer-app:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write
The stack trace points to: ss << "type='" << lut.at(d->type) << "'" << comma; where lut is a static const std::map. So perhaps the dbus::Object instance is destroyed after unloading the libdbus-cpp.so. Is libdbus-cpp.so being loaded dynamically? Or I guess a library linking to libdbus-cpp is loaded dynamically. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1524131 Title: /usr/bin/mediaplayer- app:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write Status in Canonical System Image: Confirmed Status in dbus-cpp package in Ubuntu: New Status in mediaplayer-app package in Ubuntu: New Bug description: Top 3 over the past week on errors.u.c. mediaplayer has not been updated for a while and the frequency increased significantly around mid-december, probably due to a change in an underlying component (gstreamer has been updated on Dec. 12th or it could be the major dbus match rules changes as the stacktrace would suggest) The Ubuntu Error Tracker has been receiving reports about a problem regarding mediaplayer-app. This problem was most recently seen with version 0.20.5+15.04.20150701-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a649a8d64746c3cce478208950c51611a06323cb contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1524131/+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 1161206] Re: Mir EGL apps output worrying but harmless error: libEGL warning: unsupported platform (null)
I cannot reproduce this anymore. ** Changed in: mir Status: Triaged => Incomplete ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- 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/1161206 Title: Mir EGL apps output worrying but harmless error: libEGL warning: unsupported platform (null) Status in Mir: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: It seems all the EGL demo clients trigger this message to appear on stderr: libEGL warning: unsupported platform (null) Looks like a small change in libEGL has been overlooked. I am using: ii libegl1-mesa:amd649.1~rc2-0ubuntu0+mir2-jenkins19 amd64free implementation of the EGL API -- runtime ii libegl1-mesa-dbg:amd649.1~rc2-0ubuntu0+mir2-jenkins19 amd64free implementation of the EGL API -- debugging symbols ii libegl1-mesa-dev 9.1~rc2-0ubuntu0+mir2-jenkins19 amd64free implementation of the EGL API -- development files ii libegl1-mesa-drivers:amd649.1~rc2-0ubuntu0+mir2-jenkins19 amd64free implementation of the EGL API -- hardware drivers ii libegl1-mesa-drivers-dbg:amd649.1~rc2-0ubuntu0+mir2-jenkins19 amd64free implementation of the EGL API -- driver debugging symbols To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1161206/+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 1513450] Re: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false
Looking at callgrind output on the desktop, there are no obvious mir hotspots we could single out and optimize. It's similar to the output of perf, in that quite a bit time is just spent in the GL + dri driver code. One more point, using the interactive governor (which we should be defaulting to anyway) the N4 cpu usage reported by top is around 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/1513450 Title: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false Status in Canonical System Image: In Progress Status in canonical-pocket-desktop: New Status in Mir: In Progress Status in QtMir: New Status in Online Accounts setup for Ubuntu Touch: New Status in Ubuntu UI Toolkit: New Status in ubuntu-system-settings package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: running in window mode, open u-s-s, run top unity8 running at ~40% cpu on N7 cpu freq ~1GHz no monitor attached note: testing with silo 18 of mir containing lp:~albaguirre/mir/fix-1499039 (equivalent for 0.17) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513450/+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 1513450] Re: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false
Also worth noting that the 40% figure is with the default "ondemand" governor, which changes cpu clock "ondemand" and can potentially also change gpu clocks. Using the "performance" governor (which fixes the cpu clock and potentially the gpu clock) the figure is closer to 10% cpu load on an N7. On a vegetahd, with the default cpu governor, the server cpu load is around 20%. With the performance governor, the cpu load is around 11%. -- 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/1513450 Title: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false Status in Canonical System Image: In Progress Status in canonical-pocket-desktop: New Status in Mir: In Progress Status in QtMir: New Status in Online Accounts setup for Ubuntu Touch: New Status in Ubuntu UI Toolkit: New Status in ubuntu-system-settings package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: running in window mode, open u-s-s, run top unity8 running at ~40% cpu on N7 cpu freq ~1GHz no monitor attached note: testing with silo 18 of mir containing lp:~albaguirre/mir/fix-1499039 (equivalent for 0.17) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513450/+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 1513450] Re: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false
I'm trying to get perf to return a more complete picture, but from the attached flame graph (one mir_demo_server, one mir_demo_client_egltriangle in Nexus 4): Of the time spent in mir (29%) roughly 50-60% of that is spent in the driver/kernel code (related to gpu/display) ** Attachment added: "1 client, 1 server" https://bugs.launchpad.net/mir/+bug/1513450/+attachment/4514301/+files/perf.svg -- 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/1513450 Title: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false Status in Canonical System Image: In Progress Status in canonical-pocket-desktop: New Status in Mir: In Progress Status in QtMir: New Status in Online Accounts setup for Ubuntu Touch: New Status in Ubuntu UI Toolkit: New Status in ubuntu-system-settings package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: running in window mode, open u-s-s, run top unity8 running at ~40% cpu on N7 cpu freq ~1GHz no monitor attached note: testing with silo 18 of mir containing lp:~albaguirre/mir/fix-1499039 (equivalent for 0.17) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513450/+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 1513450] Re: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false
Nexus 4 perf flamegraph, 1 mir_demo_server, 5 mir_demo_client_egltriangle instances ** Attachment added: "perf.svg" https://bugs.launchpad.net/mir/+bug/1513450/+attachment/4513846/+files/perf.svg -- 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/1513450 Title: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false Status in canonical-pocket-desktop: New Status in Mir: In Progress Status in QtMir: New Status in Online Accounts setup for Ubuntu Touch: New Status in Ubuntu UI Toolkit: New Status in unity8 package in Ubuntu: Invalid Bug description: running in window mode, open u-s-s, run top unity8 running at ~40% cpu on N7 cpu freq ~1GHz no monitor attached note: testing with silo 18 of mir containing lp:~albaguirre/mir/fix-1499039 (equivalent for 0.17) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1513450/+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 1511538] Re: 1/2 screen on external monitor
** Changed in: mir/0.17 Importance: Undecided => High ** Changed in: mir Importance: Undecided => High -- 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/1511538 Title: 1/2 screen on external monitor Status in canonical-pocket-desktop: New Status in Mir: Fix Committed Status in Mir 0.17 series: Fix Committed Status in mir package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Bug description: using N7 latest PD image connect bt mouse and keyboard connected to monitor opened several apps (clock, msg, phone, browser, twitter, u-s-s, terminal, camera, gallery, calculator, pathwind) - did quite a bit of window moving, max, min, close, relaunch after a while, disconnected n7 from monitor, then reconnected only 1/2 the screen on the monitor was used disconnected, reconnected, still only 1/2 the screen used, possible low mem ? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511538/+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 1513225] Re: libmircookie1 package does not list libnettle as dependency
** Changed in: mir/0.17 Importance: Undecided => High -- 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/1513225 Title: libmircookie1 package does not list libnettle as dependency Status in Mir: In Progress Status in Mir 0.17 series: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: libmircookie1 package declaration is missing a shlibs:Depends entry on the Dependencies list. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1513225/+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 1513450] Re: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false
** Changed in: mir Assignee: (unassigned) => Alberto Aguirre (albaguirre) ** 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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1513450 Title: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false Status in canonical-pocket-desktop: New Status in Mir: In Progress Status in QtMir: New Status in Online Accounts setup for Ubuntu Touch: New Status in Ubuntu UI Toolkit: New Status in unity8 package in Ubuntu: Invalid Bug description: running in window mode, open u-s-s, run top unity8 running at ~40% cpu on N7 cpu freq ~1GHz no monitor attached note: testing with silo 18 of mir containing lp:~albaguirre/mir/fix-1499039 (equivalent for 0.17) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1513450/+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 1511095] Re: unity-system-compositor crash, no interaction on windowed mode
** Also affects: mir/0.17 Importance: Undecided Status: New ** Changed in: mir/0.17 Milestone: None => 0.17.1 ** Changed in: mir/0.17 Importance: Undecided => High -- 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/1511095 Title: unity-system-compositor crash, no interaction on windowed mode Status in canonical-pocket-desktop: New Status in Mir: Fix Committed Status in Mir 0.17 series: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: I am seeing this occur with Nexus7 (i haven't tested with nexus4 enough to say) but I regularly see N7 reboot with me having interacted with it I will have usually connected the BT mouse and have maybe u-s-s open as well as dash (i think i've even seen it do so after just being rebooted with me not touching it before the next reboot). the screen will be on or off from being idel, no interaction per se and the device will suddenly display the "spinner" screen which is actually ubuntu dot-dot-dots I have seen it enough to confirm there are no crash files generated/associated with it lastly, i have seen this mostly while i have added silo21 (unity8 improvements) on top of the latest pd image. attached is a syslog To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511095/+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 1513225] Re: libmircookie1 package does not list libnettle as dependency
** Changed in: mir/0.17 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/1513225 Title: libmircookie1 package does not list libnettle as dependency Status in Mir: In Progress Status in Mir 0.17 series: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: libmircookie1 package declaration is missing a shlibs:Depends entry on the Dependencies list. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1513225/+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 1513225] Re: libmircookie1 package does not list libnettle as dependency
** Changed in: mir/0.17 Status: Fix Committed => 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/1513225 Title: libmircookie1 package does not list libnettle as dependency Status in Mir: In Progress Status in Mir 0.17 series: In Progress Status in mir package in Ubuntu: Triaged Bug description: libmircookie1 package declaration is missing a shlibs:Depends entry on the Dependencies list. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1513225/+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 1499039] Re: compositing never stops when external monitor is connected
** Changed in: mir/0.17 Status: New => 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/1499039 Title: compositing never stops when external monitor is connected Status in canonical-pocket-desktop: In Progress Status in Mir: Fix Committed Status in Mir 0.17 series: Fix Committed Status in mir package in Ubuntu: Confirmed Bug description: Start the following with no external display: sudo mir_demo_server --arw-file --display-config=sidebyside --window-manager system-compositor --hwc-report log mir_demo_server --host-socket /tmp/mir_socket -f /tmp/nested_mir --display-config=sidebyside After hotplugging an external display, the compositor loop never stops compositing as evidenced by the root server hwc logs. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1499039/+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 1513225] Re: libmircookie1 package does not list libnettle as dependency
** Changed in: mir/0.17 Status: New => 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/1513225 Title: libmircookie1 package does not list libnettle as dependency Status in Mir: In Progress Status in Mir 0.17 series: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: libmircookie1 package declaration is missing a shlibs:Depends entry on the Dependencies list. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1513225/+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 1510218] Re: mir_connection_get_egl_pixel_format() crashes if libEGL is loaded RTLD_LAZY
** Changed in: mir/0.17 Status: New => 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/1510218 Title: mir_connection_get_egl_pixel_format() crashes if libEGL is loaded RTLD_LAZY Status in Mir: Fix Committed Status in Mir 0.17 series: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: mir_connection_get_egl_pixel_format() crashes on Android (at least) when used in QtUbuntu. There might be some specific conditions triggering the issue there because I haven't been able to reproduce it in a standalone test [1] trying to follow the same initialisation process. This is strange because if I directly call "eglGetConfigAttrib(display, config, EGL_NATIVE_VISUAL_ID, &visual)" it works perfectly fine. Here's a QtUbuntu branch [2] using the function. [1] http://bazaar.launchpad.net/~loic.molinari/+junk/ubuntu-touch-test/view/head:/ubuntu-touch-test.c [2] lp:~loic.molinari/qtubuntu/requested-surface-format-fix-use-mir_connection_get_egl_pixel_format To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1510218/+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 1511538] Re: 1/2 screen on external monitor
** Changed in: mir/0.17 Status: New => 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/1511538 Title: 1/2 screen on external monitor Status in canonical-pocket-desktop: New Status in Mir: Fix Committed Status in Mir 0.17 series: Fix Committed Status in mir package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Bug description: using N7 latest PD image connect bt mouse and keyboard connected to monitor opened several apps (clock, msg, phone, browser, twitter, u-s-s, terminal, camera, gallery, calculator, pathwind) - did quite a bit of window moving, max, min, close, relaunch after a while, disconnected n7 from monitor, then reconnected only 1/2 the screen on the monitor was used disconnected, reconnected, still only 1/2 the screen used, possible low mem ? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511538/+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 1513225] Re: libmircookie1 package does not list libnettle as dependency
** Summary changed: - libmircookie1 does not have a shlibs:Depends in its Dependencies list + libmircookie1 package does not list libnettle as dependency -- 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/1513225 Title: libmircookie1 package does not list libnettle as dependency Status in Mir: In Progress Status in Mir 0.17 series: New Status in mir package in Ubuntu: Triaged Bug description: libmircookie1 package declaration is missing a shlibs:Depends entry on the Dependencies list. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1513225/+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 1513225] Re: libmircookie1 does not have a shlibs:Depends in its Dependencies list
** Summary changed: - libmircookie-dev does not depend on nettle-dev in debian/control + libmircookie1 does not have a shlibs:Depends in its Dependencies list ** Description changed: - libmircookie-dev needs to depend on nettle-dev in debian/control + libmircookie1 package declaration is missing a shlibs:Depends entry on + the Dependencies list. -- 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/1513225 Title: libmircookie1 package does not list libnettle as dependency Status in Mir: In Progress Status in Mir 0.17 series: New Status in mir package in Ubuntu: Triaged Bug description: libmircookie1 package declaration is missing a shlibs:Depends entry on the Dependencies list. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1513225/+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 1510218] Re: mir_connection_get_egl_pixel_format() crashes if libEGL is loaded RTLD_LAZY
** Also affects: mir/0.17 Importance: Undecided Status: New ** Changed in: mir/0.17 Milestone: None => 0.17.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/1510218 Title: mir_connection_get_egl_pixel_format() crashes if libEGL is loaded RTLD_LAZY Status in Mir: Fix Committed Status in Mir 0.17 series: New Status in mir package in Ubuntu: Triaged Bug description: mir_connection_get_egl_pixel_format() crashes on Android (at least) when used in QtUbuntu. There might be some specific conditions triggering the issue there because I haven't been able to reproduce it in a standalone test [1] trying to follow the same initialisation process. This is strange because if I directly call "eglGetConfigAttrib(display, config, EGL_NATIVE_VISUAL_ID, &visual)" it works perfectly fine. Here's a QtUbuntu branch [2] using the function. [1] http://bazaar.launchpad.net/~loic.molinari/+junk/ubuntu-touch-test/view/head:/ubuntu-touch-test.c [2] lp:~loic.molinari/qtubuntu/requested-surface-format-fix-use-mir_connection_get_egl_pixel_format To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1510218/+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 1513225] Re: libmircookie-dev does not depend on nettle-dev in debian/control
** Changed in: mir Milestone: None => 0.18.0 ** Also affects: mir/0.17 Importance: Undecided Status: New ** Changed in: mir/0.17 Milestone: None => 0.17.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/1513225 Title: libmircookie-dev does not depend on nettle-dev in debian/control Status in Mir: In Progress Status in Mir 0.17 series: New Status in mir package in Ubuntu: Triaged Bug description: libmircookie-dev needs to depend on nettle-dev in debian/control To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1513225/+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 1499039] Re: compositing never stops when external monitor is connected
** Also affects: mir/0.17 Importance: Undecided Status: New ** Changed in: mir/0.17 Importance: Undecided => High ** Changed in: mir/0.17 Milestone: None => 0.17.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/1499039 Title: compositing never stops when external monitor is connected Status in canonical-pocket-desktop: In Progress Status in Mir: Fix Committed Status in Mir 0.17 series: New Status in mir package in Ubuntu: Confirmed Bug description: Start the following with no external display: sudo mir_demo_server --arw-file --display-config=sidebyside --window-manager system-compositor --hwc-report log mir_demo_server --host-socket /tmp/mir_socket -f /tmp/nested_mir --display-config=sidebyside After hotplugging an external display, the compositor loop never stops compositing as evidenced by the root server hwc logs. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1499039/+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 1511538] Re: 1/2 screen on external monitor
** Also affects: mir/0.17 Importance: Undecided Status: New ** Changed in: mir/0.17 Milestone: None => 0.17.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/1511538 Title: 1/2 screen on external monitor Status in canonical-pocket-desktop: New Status in Mir: Fix Committed Status in Mir 0.17 series: New Status in mir package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Bug description: using N7 latest PD image connect bt mouse and keyboard connected to monitor opened several apps (clock, msg, phone, browser, twitter, u-s-s, terminal, camera, gallery, calculator, pathwind) - did quite a bit of window moving, max, min, close, relaunch after a while, disconnected n7 from monitor, then reconnected only 1/2 the screen on the monitor was used disconnected, reconnected, still only 1/2 the screen used, possible low mem ? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511538/+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 1511538] Re: 1/2 screen on external monitor
This seems to be addressed by lp:mir r3056 ** Changed in: mir Status: New => Fix Committed ** Changed in: mir Milestone: None => 0.18.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/1511538 Title: 1/2 screen on external monitor Status in canonical-pocket-desktop: New Status in Mir: Fix Committed Status in mir package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Bug description: using N7 latest PD image connect bt mouse and keyboard connected to monitor opened several apps (clock, msg, phone, browser, twitter, u-s-s, terminal, camera, gallery, calculator, pathwind) - did quite a bit of window moving, max, min, close, relaunch after a while, disconnected n7 from monitor, then reconnected only 1/2 the screen on the monitor was used disconnected, reconnected, still only 1/2 the screen used, possible low mem ? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511538/+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 1511538] Re: 1/2 screen on external monitor
It's probably this: https://bugs.launchpad.net/mir/+bug/1506846 -- 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/1511538 Title: 1/2 screen on external monitor Status in canonical-pocket-desktop: New Status in Mir: New Status in mir package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Bug description: using N7 latest PD image connect bt mouse and keyboard connected to monitor opened several apps (clock, msg, phone, browser, twitter, u-s-s, terminal, camera, gallery, calculator, pathwind) - did quite a bit of window moving, max, min, close, relaunch after a while, disconnected n7 from monitor, then reconnected only 1/2 the screen on the monitor was used disconnected, reconnected, still only 1/2 the screen used, possible low mem ? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1511538/+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 1511357] Re: CPU hogging when external screen connected
*** This bug is a duplicate of bug 1499039 *** https://bugs.launchpad.net/bugs/1499039 I meant lp:1499039 above. -- 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/1511357 Title: CPU hogging when external screen connected Status in Mir: New Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: CPU usage of u-s-c goes to around 40% when an external screen is connected, as long as the display is on. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-system-compositor 0.2.0+15.04.20151008.1-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.4.0-5-flo armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Thu Oct 29 12:40:04 2015 GraphicsCard: InstallationDate: Installed on 2015-10-29 (0 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20151029-020304) SourcePackage: unity-system-compositor UpgradeStatus: No upgrade log present (probably fresh install) version.libdrm: libdrm2 2.4.60-2 version.lightdm: lightdm 1.14.2-0ubuntu1.1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1511357/+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 1511357] Re: CPU hogging when external screen connected
*** This bug is a duplicate of bug 1499039 *** https://bugs.launchpad.net/bugs/1499039 Yep, duplicate of lp:499039, fixing lp:499039, USC cpu consumption (as reported by top) goes down to normal when an external display is connected. ** This bug has been marked a duplicate of bug 1499039 compositing never stops when external monitor is connected -- 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/1511357 Title: CPU hogging when external screen connected Status in Mir: New Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: CPU usage of u-s-c goes to around 40% when an external screen is connected, as long as the display is on. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-system-compositor 0.2.0+15.04.20151008.1-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.4.0-5-flo armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Thu Oct 29 12:40:04 2015 GraphicsCard: InstallationDate: Installed on 2015-10-29 (0 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20151029-020304) SourcePackage: unity-system-compositor UpgradeStatus: No upgrade log present (probably fresh install) version.libdrm: libdrm2 2.4.60-2 version.lightdm: lightdm 1.14.2-0ubuntu1.1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1511357/+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 1499039] Re: compositing never stops when external monitor is connected
The issue is the following, taking just one active surface only visible in display A not display B - compositor A consumes surface ready buffer. The buffer queue associated with the surface now has put that ready buffer into a "current compositor buffer" - i.e. it's the buffer that the compositor will use if there's another compositing pass and no other ready buffers are available. -- compositor A asks if there are any more ready buffers. --- BufferQueue returns 0 ready buffers. a. compositor B runs, figures out there are no visible surfaces for its area so doesn't consume anything from the buffer queue. b. compositor B asks buffer queue if there are more ready buffers c. buffer queue says 1 buffer is available - because it didn't consume the ready buffer as it wasn't visible on it. d. repeat a-c indefinitely until surface actually is visible in display B -- 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/1499039 Title: compositing never stops when external monitor is connected Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: Start the following with no external display: sudo mir_demo_server --arw-file --display-config=sidebyside --window-manager system-compositor --hwc-report log mir_demo_server --host-socket /tmp/mir_socket -f /tmp/nested_mir --display-config=sidebyside After hotplugging an external display, the compositor loop never stops compositing as evidenced by the root server hwc logs. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1499039/+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 1499039] Re: compositing never stops when external monitor is connected
Happens with mesa too with a side-by-side display config. ** Summary changed: - [android] compositing never stops when external monitor is connected + compositing never stops when external monitor is connected ** Tags removed: android -- 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/1499039 Title: compositing never stops when external monitor is connected Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: Start the following with no external display: sudo mir_demo_server --arw-file --display-config=sidebyside --window-manager system-compositor --hwc-report log mir_demo_server --host-socket /tmp/mir_socket -f /tmp/nested_mir --display-config=sidebyside After hotplugging an external display, the compositor loop never stops compositing as evidenced by the root server hwc logs. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1499039/+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 1499039] Re: [android] compositing never stops when external monitor is connected
** Changed in: mir Assignee: (unassigned) => Alberto Aguirre (albaguirre) ** 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 mir in Ubuntu. https://bugs.launchpad.net/bugs/1499039 Title: [android] compositing never stops when external monitor is connected Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: Start the following with no external display: sudo mir_demo_server --arw-file --display-config=sidebyside --window-manager system-compositor --hwc-report log mir_demo_server --host-socket /tmp/mir_socket -f /tmp/nested_mir --display-config=sidebyside After hotplugging an external display, the compositor loop never stops compositing as evidenced by the root server hwc logs. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1499039/+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 1511357] Re: CPU hogging when external screen connected
It's probably this: https://bugs.launchpad.net/mir/+bug/1499039 -- 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/1511357 Title: CPU hogging when external screen connected Status in Mir: New Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: CPU usage of u-s-c goes to around 40% when an external screen is connected, as long as the display is on. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-system-compositor 0.2.0+15.04.20151008.1-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.4.0-5-flo armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Thu Oct 29 12:40:04 2015 GraphicsCard: InstallationDate: Installed on 2015-10-29 (0 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20151029-020304) SourcePackage: unity-system-compositor UpgradeStatus: No upgrade log present (probably fresh install) version.libdrm: libdrm2 2.4.60-2 version.lightdm: lightdm 1.14.2-0ubuntu1.1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1511357/+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 1471858] Re: Android: rotated display config not applied when an external monitor is hot-plugged
** Changed in: mir/0.14 Status: New => Won't Fix -- 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/1471858 Title: Android: rotated display config not applied when an external monitor is hot-plugged Status in Mir: Fix Released Status in Mir 0.13 series: Won't Fix Status in Mir 0.14 series: Won't Fix Status in mir package in Ubuntu: Fix Released Bug description: Hardware: Android (Nexus 7), using slimport cable to drive external monitor. Using Mir 0.13 The intention is to configure USC to clone the contents of the internal display to the external display (id=1), but with those contents rotated 90 degrees. Check out revision 220 of lp:~unity-team/unity-system-compositor /toggle-cursor2/ I am implementing a DisplayConfigurationPolicy like this: http://pastebin.ubuntu.com/11830210/ I've got some print statements in there too. On testing this, there are 2 cases: 1. Slimport cable connected at server startup Here, the external monitor comes up rotated correctly. I see the debug statements print. 2. Slimport cable *not* connected at server startup First off, I do not see my debug statement print at server start. Secondly, when I do plug in the slimport cable, while I see my debug prints, the external monitor does not get rotated. You can explicitly tell USC to rotate the external display with dbus (install qdbus-qt5 first): qdbus --system com.canonical.Unity.Screen / com.canonical.Unity.Screen.overrideOrientation 1 90 so rotation does work. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1471858/+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 1471909] Re: MultiThreadedCompositor::destroy_compositing_threads hangs/deadlocks on shutdown or display reconfiguration
** Changed in: mir/0.14 Status: Triaged => Won't Fix -- 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/1471909 Title: MultiThreadedCompositor::destroy_compositing_threads hangs/deadlocks on shutdown or display reconfiguration Status in Mir: Fix Released Status in Mir 0.13 series: Won't Fix Status in Mir 0.14 series: Won't Fix Status in mir package in Ubuntu: Fix Released Bug description: Try revision 211 of lp:~unity-team/unity-system-compositor/toggle- cursor2/ The desire was to resize all surfaces to the size of the smallest attached display. usc::WindowManager implements the mir::shell::WindowManagement interface. I thought it logical to implement this resizing in add_display. However it causes a deadlock when plugging in a second display, while the compositor is stopping, see this backtrace: http://pastebin.ubuntu.com/11831907/ I suspect Threads 8 and Thread 1 are blocking eachother. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1471909/+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 1482274] Re: GLibMainLoopTest.propagates_exception_from_server_action fails with GCC 5 in armhf
** Changed in: mir Milestone: 0.16.0 => 0.15.0 ** No longer affects: mir/0.15 -- 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/1482274 Title: GLibMainLoopTest.propagates_exception_from_server_action fails with GCC 5 in armhf Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Using -02 (which is turned on when building the mir packages or use_debflags=ON) with GCC 5 on armhf results in the following test failure: bin/mir_unit_tests --gtest_filter=GLibMainLoopTest.propagates_exception_from_server_action Running main() from main.cpp Note: Google Test filter = GLibMainLoopTest.propagates_exception_from_server_action [==] Running 1 test from 1 test case. [--] Global test environment set-up. [--] 1 test from GLibMainLoopTest [ RUN ] GLibMainLoopTest.propagates_exception_from_server_action terminate called after throwing an instance of 'std::runtime_error' what(): server action error /home/alberto/source/mir/0.15/tests/unit-tests/test_glib_main_loop.cpp:78: Failure Value of: result.succeeded() Actual: false Expected: true [ FAILED ] GLibMainLoopTest.propagates_exception_from_server_action (677 ms) [--] 1 test from GLibMainLoopTest (677 ms total) [--] Global test environment tear-down [==] 1 test from 1 test case ran. (679 ms total) [ PASSED ] 0 tests. [ FAILED ] 1 test, listed below: [ FAILED ] GLibMainLoopTest.propagates_exception_from_server_action To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1482274/+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 1480755] Re: [regression] Some Mir EGL demos don't get bypassed any more in fullscreen
** Changed in: mir Milestone: 0.16.0 => 0.15.0 -- 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/1480755 Title: [regression] Some Mir EGL demos don't get bypassed any more in fullscreen Status in Mir: Fix Committed Status in mesa package in Ubuntu: New Bug description: [regression] Fullscreen GL apps don't get bypassed any more. As you can see in compositor report from any of our demo servers: [1438572052.621854] compositor: Display 0x7faea4306fa0 averaged 60.537 FPS, 0.506 ms/frame, latency 15.669 ms, 61 frames over 1.007 sec, 0% bypassed [1438572053.622668] compositor: Display 0x7faea4306fa0 averaged 59.950 FPS, 0.551 ms/frame, latency 15.814 ms, 60 frames over 1.000 sec, 0% bypassed [1438572054.623370] compositor: Display 0x7faea4306fa0 averaged 59.958 FPS, 0.613 ms/frame, latency 15.721 ms, 60 frames over 1.000 sec, 0% bypassed I think this is only "medium" though, because it's a transparent optimization so its absence is very hard to notice in most cases. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1480755/+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 1479224] Re: The mesa-x11 driver is not packaged yet
** No longer affects: mir/0.15 ** Changed in: mir Milestone: 0.16.0 => 0.15.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/1479224 Title: The mesa-x11 driver is not packaged yet Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: The mesa-x11 driver is not packaged yet. No mention of it in debian/ To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1479224/+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 1480654] Re: [regression] Input focus delay after switching app back into focus since OTA5 (Mir 0.14)
** Changed in: mir Milestone: 0.16.0 => 0.15.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/1480654 Title: [regression] Input focus delay after switching app back into focus since OTA5 (Mir 0.14) Status in Mir: Fix Committed Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: i am not sure if it started with OTA4 or OTA5 but since one of the recent OTA upgrades my arale takes between half a second and one second before an app takes input again when one switches it from background back into focus. i'm talking about apps that were only sigstopped, not OOM killed here (i.e. no restart involved, just sigcont). this used to be instant before and gives a weird feeling of sluggishness. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1480654/+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 1482274] Re: GLibMainLoopTest.propagates_exception_from_server_action fails with GCC 5 in armhf
** Branch unlinked: lp:mir/0.15 -- 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/1482274 Title: GLibMainLoopTest.propagates_exception_from_server_action fails with GCC 5 in armhf Status in Mir: Fix Committed Status in Mir 0.15 series: Fix Committed Status in mir package in Ubuntu: New Bug description: Using -02 (which is turned on when building the mir packages or use_debflags=ON) with GCC 5 on armhf results in the following test failure: bin/mir_unit_tests --gtest_filter=GLibMainLoopTest.propagates_exception_from_server_action Running main() from main.cpp Note: Google Test filter = GLibMainLoopTest.propagates_exception_from_server_action [==] Running 1 test from 1 test case. [--] Global test environment set-up. [--] 1 test from GLibMainLoopTest [ RUN ] GLibMainLoopTest.propagates_exception_from_server_action terminate called after throwing an instance of 'std::runtime_error' what(): server action error /home/alberto/source/mir/0.15/tests/unit-tests/test_glib_main_loop.cpp:78: Failure Value of: result.succeeded() Actual: false Expected: true [ FAILED ] GLibMainLoopTest.propagates_exception_from_server_action (677 ms) [--] 1 test from GLibMainLoopTest (677 ms total) [--] Global test environment tear-down [==] 1 test from 1 test case ran. (679 ms total) [ PASSED ] 0 tests. [ FAILED ] 1 test, listed below: [ FAILED ] GLibMainLoopTest.propagates_exception_from_server_action To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1482274/+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 1481279] Re: GCC5: Phone restarts if you click on anything in the first page of welcome wizard
Also "test_ubuntu_haptic_device" which calls the same ua_sensors_haptic_vibrate_once api runs without crashing. Some package versions: http://pastebin.ubuntu.com/12003474/ -- 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/1481279 Title: GCC5: Phone restarts if you click on anything in the first page of welcome wizard Status in unity8 package in Ubuntu: New Bug description: STEPS: 1. Install the latest gcc5 test image 2. Get to the welcome wizard 3. Tap the language drop down 4. Reboots 5. Tap the Continue Button 6. Reboots EXPECTED: I expect the welcome wizard to work the same as it does on vivid ACTUAL: Any option you tap on as soon as the signal is received it reboots the phone. VERSIONS: Image 3 Logs to follow once I can strip them out of the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1481279/+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 1481279] Re: GCC5: Phone restarts if you click on anything in the first page of welcome wizard
Stack trace: #0 0xad3daf98 in deallocate (this=, __p=) at /usr/include/c++/5/ext/new_allocator.h:110 #1 deallocate (__a=..., __n=, __p=) at /usr/include/c++/5/bits/alloc_traits.h:386 #2 _M_destroy (__size=, this=) at /usr/include/c++/5/bits/basic_string.h:185 #3 _M_dispose (this=0xbe8fd794) at /usr/include/c++/5/bits/basic_string.h:180 #4 ~basic_string (this=0xbe8fd794, __in_chrg=) at /usr/include/c++/5/bits/basic_string.h:544 #5 interface_name () at /usr/include/core/dbus/traits/service.h:34 #6 invoke_method_synchronously (this=) at /usr/include/core/dbus/impl/object.h:71 #7 ua_sensors_haptic_vibrate_once (sensor=, duration=) at /build/platform-api-qm_L3b/platform-api-3.0.0+15.10.20150730/src/ubuntu/application/common/application/sensors/service.cpp:93 #8 0xa8600e8e in QFeedbackHapticsEffect::setState(QFeedbackEffect::State) () from /usr/lib/arm-linux-gnueabihf/libQt5Feedback.so.5 #9 0xa7d2deb6 in ?? () from /usr/lib/arm-linux-gnueabihf/qt5/qml/QtFeedback/libdeclarative_feedback.so -- 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/1481279 Title: GCC5: Phone restarts if you click on anything in the first page of welcome wizard Status in unity8 package in Ubuntu: New Bug description: STEPS: 1. Install the latest gcc5 test image 2. Get to the welcome wizard 3. Tap the language drop down 4. Reboots 5. Tap the Continue Button 6. Reboots EXPECTED: I expect the welcome wizard to work the same as it does on vivid ACTUAL: Any option you tap on as soon as the signal is received it reboots the phone. VERSIONS: Image 3 Logs to follow once I can strip them out of the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1481279/+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 1475994] Re: mir fails to build with GCC 5
** Changed in: mir/0.14 Milestone: 0.14.1 => None ** Changed in: mir/0.14 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/1475994 Title: mir fails to build with GCC 5 Status in Mir: Fix Committed Status in Mir 0.14 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: as seen in silo16: https://launchpadlibrarian.net/212029958/buildlog_ubuntu-wily- amd64.mir_0.14.0%2B15.10.20150715-0ubuntu2~gcc5.1_BUILDING.txt.gz make[3]: Entering directory '/«BUILDDIR»/mir-0.14.0+15.10.20150715/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_report /«BUILDDIR»/mir-0.14.0+15.10.20150715/obj-x86_64-linux-gnu/CMakeFiles [ 10%] Building CXX object src/protobuf/CMakeFiles/mirprotobuf.dir/google_protobuf_guard.cpp.o cd /«BUILDDIR»/mir-0.14.0+15.10.20150715/obj-x86_64-linux-gnu/src/protobuf && /usr/bin/x86_64-linux-gnu-g++ -DLOG_NDEBUG=1 -DMESA_EGL_NO_X11_HEADERS -DMIR_VERSION_MAJOR=0 -DMIR_VERSION_MICRO=0 -DMIR_VERSION_MINOR=14 -Dmirprotobuf_EXPORTS -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing -pedantic -Wnon-virtual-dtor -Wextra -fPIC -fPIC -I/«BUILDDIR»/mir-0.14.0+15.10.20150715/include/common -I/«BUILDDIR»/mir-0.14.0+15.10.20150715/src/include/common -I/«BUILDDIR»/mir-0.14.0+15.10.20150715/obj-x86_64-linux-gnu/src/protobuf-o CMakeFiles/mirprotobuf.dir/google_protobuf_guard.cpp.o -c /«BUILDDIR»/mir-0.14.0+15.10.20150715/src/protobuf/google_protobuf_guard.cpp In file included from /«BUILDDIR»/mir-0.14.0+15.10.20150715/src/protobuf/google_protobuf_guard.cpp:19:0: /«BUILDDIR»/mir-0.14.0+15.10.20150715/src/include/common/mir/protobuf/google_protobuf_guard.h:37:6: error: '{anonymous}::force_google_protobuf_init' defined but not used [-Werror=unused-variable] bool force_google_protobuf_init{(mir::protobuf::google_protobuf_guard(), true)}; ^ /usr/bin/cmake -E cmake_progress_report /«BUILDDIR»/mir-0.14.0+15.10.20150715/obj-x86_64-linux-gnu/CMakeFiles cc1plus: all warnings being treated as errors make[3]: *** [src/protobuf/CMakeFiles/mirprotobuf.dir/google_protobuf_guard.cpp.o] Error 1 [ 10%] src/protobuf/CMakeFiles/mirprotobuf.dir/build.make:75: recipe for target 'src/protobuf/CMakeFiles/mirprotobuf.dir/google_protobuf_guard.cpp.o' failed make[3]: Leaving directory '/«BUILDDIR»/mir-0.14.0+15.10.20150715/obj-x86_64-linux-gnu' CMakeFiles/Makefile2:2622: recipe for target 'src/protobuf/CMakeFiles/mirprotobuf.dir/all' failed make[2]: *** [src/protobuf/CMakeFiles/mirprotobuf.dir/all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1475994/+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 1240909] Re: [performance] Restore support for double-buffering by default
** Changed in: mir Milestone: 0.15.0 => 0.16.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/1240909 Title: [performance] Restore support for double-buffering by default Status in Mir: In Progress Status in Mir 0.5 series: Won't Fix Status in mir package in Ubuntu: Triaged Bug description: We really should restore support for double-buffering where possible. Presently we're on triple-buffering all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1240909/+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 1425307] Re: [regression] Exception when running phablet-screenshot [std::exception::what: Attempt to set swap interval on screencast is invalid]
** Changed in: mir/0.14 Milestone: 0.15.0 => None ** Changed in: mir Milestone: 0.13.1 => 0.16.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/1425307 Title: [regression] Exception when running phablet-screenshot [std::exception::what: Attempt to set swap interval on screencast is invalid] Status in Mir: Confirmed Status in Mir 0.12 series: Confirmed Status in Mir 0.13 series: Confirmed Status in Mir 0.14 series: Confirmed Status in mir package in Ubuntu: Confirmed Status in phablet-tools package in Ubuntu: New Bug description: current build number: 110 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2015-02-24 22:35:35 version version: 110 version ubuntu: 20150224 version device: 20150210 version custom: 20150224 rsalveti@evasys:~$ phablet-screenshot /tmp/foo.png I: Dumping fb0 ... [1424817826.846470] Loader: Loading modules from: /usr/lib/arm-linux-gnueabihf/mir/client-platform/ [1424817826.847569] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so [1424817826.848393] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so [1424817826.849583] Loader: Loading module: /usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so [1424817826.944654] mircommon: Caught exception at Mir/EGL driver boundary (in setSwapInterval): /build/buildd/mir-0.11.0+15.04.20150209.1/src/client/buffer_stream.cpp(283): Throw in function virtual void mir::client::BufferStream::request_and_wait_for_configure(MirSurfaceAttrib, int) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt11logic_error std::exception::what: Attempt to set swap interval on screencast is invalid 3004 KB/s (3932160 bytes in 1.278s) I: Done phablet-tools - 1.1+15.04.20150218-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1425307/+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 1373696] Re: Android overlay mode ping-pongs constantly with touchspots or software cursor enabled, causing stuttering and lag
** Changed in: mir Milestone: 0.15.0 => 0.16.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/1373696 Title: Android overlay mode ping-pongs constantly with touchspots or software cursor enabled, causing stuttering and lag Status in Mir: Triaged Status in mir package in Ubuntu: Triaged Bug description: Bypass/overlay mode ping-pongs constantly during touches with touchspots enabled, or when using a mouse (software cursor on Android). This visibly means the screen is stuttering and jerky. This is a lesser form of bug 1373689, which has a workaround about to land... $ bin/mir_demo_server_minimal --enable-touchspots --compositor-report=log # (and also start a fullscreen client from elsewhere) [1411611407.207459] (II) compositor: Started [1411611407.230898] (II) compositor: Added display 0x1123d48: 768x1280 +0+0 [1411611407.236148] (II) compositor: Display 0x1123d48 bypass OFF [1411611410.060412] (II) compositor: Display 0x1123d48 bypass ON [1411611410.996746] (II) compositor: Display 0x1123d48 averaged 56.652 FPS, 11.493 ms/frame, latency 0.741 ms, 57 frames over 1.006 sec, 98% bypassed [1411611411.998852] (II) compositor: Display 0x1123d48 averaged 59.875 FPS, 10.765 ms/frame, latency 0.305 ms, 60 frames over 1.002 sec, 100% bypassed [1411611412.584721] (II) compositor: Display 0x1123d48 bypass OFF [1411611412.599981] (II) compositor: Display 0x1123d48 bypass ON [1411611412.677534] (II) compositor: Display 0x1123d48 bypass OFF [1411611412.683699] (II) compositor: Display 0x1123d48 bypass ON [1411611412.771628] (II) compositor: Display 0x1123d48 bypass OFF [1411611412.783500] (II) compositor: Display 0x1123d48 bypass ON [1411611412.874756] (II) compositor: Display 0x1123d48 bypass OFF [1411611412.883577] (II) compositor: Display 0x1123d48 bypass ON [1411611412.972513] (II) compositor: Display 0x1123d48 bypass OFF [1411611412.983714] (II) compositor: Display 0x1123d48 bypass ON To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1373696/+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