[Touch-packages] [Bug 1674389] Re: Session Indicator's "Suspend" button has no effect in Unity 8
** Changed in: repowerd (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: repowerd (Ubuntu) Status: Fix Released => Fix Committed ** Changed in: repowerd (Ubuntu) Status: Fix Committed => Fix Released -- 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/1674389 Title: Session Indicator's "Suspend" button has no effect in Unity 8 Status in Canonical System Image: New Status in indicator-session package in Ubuntu: In Progress Status in repowerd package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: New Bug description: Testing Unity 8 from a Zesty nightly iso install on March 17 2017. When clicking on the "Suspend" button in the session indicator, nothing happens. This may or may not be an indicator-session issue. I need to triage this and see where the breakage is, e.g. does it work in Unity 7 on Zesty, and are there are any DBus signatures that have changed in Zesty that would cause this To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674389/+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 1679591] Re: Laptop suspends when closing lid with an external display plugged
** Also affects: mir Importance: Undecided Status: New ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Importance: Undecided => High ** Changed in: mir Importance: Undecided => High ** Changed in: mir Assignee: (unassigned) => Alexandros Frantzis (afrantzis) ** Changed in: mir (Ubuntu) Assignee: (unassigned) => Alexandros Frantzis (afrantzis) ** Changed in: mir Status: New => In Progress ** Changed in: mir (Ubuntu) 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/1679591 Title: Laptop suspends when closing lid with an external display plugged Status in Canonical System Image: New Status in Mir: In Progress Status in repowerd: New Status in mir package in Ubuntu: In Progress Bug description: Story: when an external display is connected, and the lid is closed the system is suspended like if there were no external display. Environment: unity8-deb on zesty STEPS: 1. Connect external display(hdmi in this case) 2. Close the lid 3. Check the external display Current result: session locks and you get the unity8 login page Expected result: session does not lock when an external display is connected To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1679591/+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 1674389] Re: Session Indicator's "Suspend" button has no effect in Unity 8
repowerd, or some other process that acquires logind suspend inhibitions, could be involved in this. It's easy to find out if this is the case by running: $ systemd-inhibit and checking if any inhibitions with parameters What:sleep Mode:block are active. Note that repowerd acquiring such an inhibition just means that another program has requested a suspend inhibition from repowerd. In any case, as discussed in bug 1668596, repowerd will soon stop acquiring logind suspend inhibitions. ** Changed in: repowerd (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1674389 Title: Session Indicator's "Suspend" button has no effect in Unity 8 Status in Canonical System Image: New Status in indicator-session package in Ubuntu: In Progress Status in repowerd package in Ubuntu: Fix Committed Status in unity8 package in Ubuntu: New Bug description: Testing Unity 8 from a Zesty nightly iso install on March 17 2017. When clicking on the "Suspend" button in the session indicator, nothing happens. This may or may not be an indicator-session issue. I need to triage this and see where the breakage is, e.g. does it work in Unity 7 on Zesty, and are there are any DBus signatures that have changed in Zesty that would cause this To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674389/+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 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync
I have attached a protobuf debdiff fix for this issue. It's a backport from upstream (more details in the debian patch metadata). ** Patch added: "protobuf package fix debdiff" https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/1667352/+attachment/4839390/+files/protobuf-zesty-fix-1667352.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1667352 Title: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync Status in Canonical System Image: In Progress Status in Mir: In Progress Status in Mir 0.26 series: Triaged Status in libsdl2 package in Ubuntu: Confirmed Status in neverball package in Ubuntu: Invalid Status in protobuf package in Ubuntu: In Progress Bug description: ubuntu 17.04 unity8, trying to run neverball game Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting ubuntu-app-launch-application-legacy-neverball-1487864803635991.service... Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL (Failed to connect to the mir server: std::bad_alloc) Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main process exited, code=exited, status=1/FAI Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start ubuntu-app-launch-application-legacy-neverball-1487864803635991.service. Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit entered failed state. Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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 1660438] Re: display brightness & slider follows hw keys or mousing, but jumps about & brightness flickers at low end
** Changed in: repowerd (Ubuntu) Status: Incomplete => Triaged -- 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/1660438 Title: display brightness & slider follows hw keys or mousing, but jumps about & brightness flickers at low end Status in Canonical System Image: New Status in repowerd package in Ubuntu: Triaged Status in unity8 package in Ubuntu: New Bug description: using unity8 deb session, zesty to reproduce, reveal the "battery" indicator panel on a pc with brightness hw keys. play around intermittently with decreasing/increasing brightness with the hw keys. Then attempt to increase/decrease brightness with the slider. It becomes especially interesting when the slider & actual brightness are at their max/mins. fwiw, i was using an older dell studio laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1660438/+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 1233988] Re: With Mir enabled: platform-api apps crash with SIGABRT in __gnu_cxx::__verbose_terminate_handler(), thrown from mir::client::DisplayConfiguration::copy_to_client()
** Changed in: qtubuntu Status: Fix Committed => Fix Released ** Changed in: platform-api 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/1233988 Title: With Mir enabled: platform-api apps crash with SIGABRT in __gnu_cxx::__verbose_terminate_handler(), thrown from mir::client::DisplayConfiguration::copy_to_client() Status in Mir: Fix Released Status in platform-api: Fix Released Status in qtubuntu: Fix Released Status in maliit-framework package in Ubuntu: Fix Committed Status in mir package in Ubuntu: Fix Released Status in platform-api package in Ubuntu: Fix Released Status in qtubuntu package in Ubuntu: Fix Released Bug description: This crash file is in /var/crash/ with Mir is enabled. TEST CASE: 1. Flash a device with latest build 2. Enable Mir support 3. Reboot -> Verify that /var/crash is empty ACTUAL RESULT: This crash TEST CASE 2: (from 1236705) 1. Load some songs on the device 2. Go to the Music scope and play a song 3. Don't stop playing and switch back to the music scope 4. While music is still playing, play another song ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: maliit-framework 0.99.0+git20130615+97e8335-0ubuntu3 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.5-0ubuntu1 Architecture: armhf Date: Wed Oct 2 05:46:34 2013 ExecutablePath: /usr/bin/maliit-server InstallationDate: Installed on 2013-10-01 (0 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20131001.3) LocalLibraries: /android/system/lib/libgccdemangle.so /android/system/lib/egl/libGLESv2_adreno200.so /android/system/lib/libdsyscalls.so /android/system/lib/libgsl.so /android/system/lib/libc.so /android/system/lib/libstdc++.so /android/system/lib/libGLESv2.so /android/system/lib/libcutils.so /android/system/lib/liblog.so /android/system/lib/libm.so /android/system/lib/egl/libEGL_adreno200.so /android/system/lib/libEGL.so /android/system/lib/libcorkscrew.so /android/system/lib/libGLES_trace.so /android/system/lib/libz.so /android/system/lib/libstlport.so /android/system/lib/egl/libGLESv1_CM_adreno200.so /android/system/lib/libhardware.so /android/system/lib/libutils.so /android/system/lib/libgenlock.so MarkForUpload: True ProcCmdline: maliit-server Signal: 6 SourcePackage: maliit-framework StacktraceTop: ?? () from /lib/arm-linux-gnueabihf/libc.so.6 raise () from /lib/arm-linux-gnueabihf/libc.so.6 abort () from /lib/arm-linux-gnueabihf/libc.so.6 __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 Title: maliit-server crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1233988/+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
** Changed in: unity-system-compositor/0.4 Status: Fix Committed => Fix Released ** Changed in: unity-system-compositor Status: Fix Committed => 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/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 Released Status in Unity System Compositor 0.4 series: Fix Released 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 1667001] Re: [amd] screen-unblanking seems to flicker backlight on/off 5 times before display resumes
Could you please attach /var/log/repowerd.log at the time of the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1667001 Title: [amd] screen-unblanking seems to flicker backlight on/off 5 times before display resumes Status in Canonical System Image: Incomplete Status in Mir: Incomplete Status in repowerd: Incomplete Status in mir package in Ubuntu: Incomplete Status in repowerd package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: I've a Lenovo Flex 2-14D which has an AMD GPU. I'm using the free driver. I have unity8 installed. If I let the screen blank, and hit a key to unblank, it takes about 5 seconds until screen turns on properly. During those 5 seconds, I see the display backlight turn on & off about 5 times, all the while with a black picture. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667001/+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 1660438] Re: display brightness & slider follows hw keys, but brightness does not follow slider unity8 zesty
Kevin, I can't reproduce this issue on an older dell latitude laptop. When pressing the brightness hardware keys (actually Fn + up/down arrow) the brightness slider moves accordingly, and then moving the slider correctly changes the brightness. Note that I am running zesty with a locally fixed systemd package (see bug 1661568). I wonder if what you are seeing is a side-effect of the aforementioned systemd issue. My proposal is to try again in a few days, when the fixed systemd package will have landed to zesty (hopefully). If the problem persists we can investigate further. ** Changed in: repowerd (Ubuntu) Status: New => Incomplete -- 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/1660438 Title: display brightness & slider follows hw keys, but brightness does not follow slider unity8 zesty Status in Canonical System Image: New Status in repowerd package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: New Bug description: using unity8 deb session, zesty to reproduce, reveal the "battery" indicator panel on a pc with brightness hw keys. play around intermittently with decreasing/increasing brightness with the hw keys. Then attempt to increase/decrease brightness with the slider. It becomes especially interesting when the slider & actual brightness are at their max/mins. fwiw, i was using an older dell studio laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1660438/+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 1595947] Re: brightness not changing from either u-s-s or hardkey on unity8-desktop
** Changed in: repowerd (Ubuntu) Status: Fix Committed => 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/1595947 Title: brightness not changing from either u-s-s or hardkey on unity8-desktop Status in Canonical System Image: Fix Released Status in Mir: Invalid Status in unity8-desktop-session: Fix Released Status in mir package in Ubuntu: Invalid Status in repowerd package in Ubuntu: Fix Released Status in unity-system-compositor package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Status in unity8-desktop-session package in Ubuntu: Fix Released Bug description: Running unity8-desktop session on my macbookpro which has a hard display brightness key, currently it makes no effect. Also, opened ubuntu-sytstem-settings and changing the brightness slider also makes no effect. sorry for spamming projects, not sure which to log against. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595947/+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 1663106] Re: [regression] Logging in to Unity8 takes 25 seconds (the default DBus timeout)
unity-system-compositor 0.9.1 (the aforementioned silo) is unlikely to be causing this, since: 1. I had a zesty system I hadn't updated in a week or so, which did not exhibit the bug. After updating only USC to 0.9.1, I still couldn't reproduce the bug. However, after doing a subsequent dist-upgrade the issue appeared, which indicates that one of the dist-upgraded packages is involved. I have uploaded the full dist-upgraded package list at: https://pastebin.canonical.com/178774/. 2. In a fully updated zesty system exhibiting the issue, downgrading USC to 0.9.0 does not fix the problem. -- 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/1663106 Title: [regression] Logging in to Unity8 takes 25 seconds (the default DBus timeout) Status in Canonical System Image: New Status in qtmir package in Ubuntu: Confirmed Status in ubuntu-app-launch package in Ubuntu: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: [regression] Logging in to Unity8 takes 25 seconds (at least on the first login after a fresh boot) ... [2017-02-09:11:35:05.263] Empty ualAppId result for "qterminal_drop" [2017-02-09:11:35:05.263] Failed to get app info for app "qterminal_drop" [2017-02-09:11:35:05.308] Failed to get all properties for "com.ubuntu.location.providers.here.AccountsService" : "No such interface" [2017-02-09:11:35:05.310] CursorImageProvider: "" not found (nor its fallbacks, if any). Going for "left_ptr" as a last resort. [2017-02-09:11:35:05.328] qtmir.applications: applicationManagerSingleton - engine= 0x56395e4119b0 scriptEngine= 0x56395e4119b0 [2017-02-09:11:35:05.330] qtmir.surfaces: MirSurfaceItem::setSurface surface=QObject(0x0) [2017-02-09:11:35:05.333] ubuntu-app-launch threw an exception getting app info for appId: "address-book-app" : Invalid app ID: address-book-app [2017-02-09:11:35:05.334] Empty ualAppId result for "com.ubuntu.camera_camera" [2017-02-09:11:35:05.334] Empty ualAppId result for "com.ubuntu.gallery_gallery" [2017-02-09:11:35:30.682] qtmir.surfaces: MirSurfaceItem::setSurface surface=QObject(0x0) [2017-02-09:11:35:30.682] qtmir.surfaces: MirSurfaceItem::setSurface surface=QObject(0x0) [2017-02-09:11:35:30.687] qtmir.mir.keymap: SET KEYMAP "us" [2017-02-09:11:35:30.688] qtmir.mir.keymap: Applying keymap "us" "" on 4 "Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint" [2017-02-09:11:35:30.688] qtmir.mir.keymap: Keymap applied [2017-02-09:11:38:19.249] qtmir.surfaces: MirSurfaceItem::setSurface surface=QObject(0x0) [2017-02-09:11:38:19.252] ubuntu-app-launch threw an exception getting app info for appId: "address-book-app" : Invalid app ID: address-book-app [2017-02-09:11:38:19.253] Empty ualAppId result for "com.ubuntu.camera_camera" [2017-02-09:11:38:19.253] Empty ualAppId result for "com.ubuntu.gallery_gallery" [2017-02-09:11:38:44.677] qtmir.surfaces: MirSurfaceItem::setSurface surface=QObject(0x0) [2017-02-09:11:38:44.677] qtmir.surfaces: MirSurfaceItem::setSurface surface=QObject(0x0) [2017-02-09:11:38:44.680] qtmir.mir.keymap: SET KEYMAP "us" [2017-02-09:11:38:44.680] qtmir.mir.keymap: Applying keymap "us" "" on 4 "Lite-On Technology Corp. ThinkPad USB Keyboard with TrackPoint" [2017-02-09:11:38:44.680] qtmir.mir.keymap: Keymap applied To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663106/+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 1661568] Re: logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property
I have proposed a fix for this issue upstream (merged into master at [1]) and have cherry-picked the fix as a patch for the zesty systemd package in the attached debdiff. [1] https://github.com/systemd/systemd/commit/7d049e304e8c9f6478bd3c6dc1781adf21d03e80 ** Patch added: "systemd-fix-1661568.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1661568/+attachment/4812524/+files/systemd-fix-1661568.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1661568 Title: logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property Status in systemd package in Ubuntu: In Progress Bug description: logind fails to emit a DBus PropertiesChanged signal for the org.freedesktop.login1.Seat.ActiveSession DBus property. See https://github.com/systemd/systemd/issues/5210. This breaks repowerd on zesty since repowerd depends on this signal to track the active session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1661568/+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 1661568] [NEW] logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property
Public bug reported: logind fails to emit a DBus PropertiesChanged signal for the org.freedesktop.login1.Seat.ActiveSession DBus property. See https://github.com/systemd/systemd/issues/5210. This breaks repowerd on zesty since repowerd depends on this signal to track the active session. ** Affects: systemd (Ubuntu) Importance: High Assignee: Alexandros Frantzis (afrantzis) Status: In Progress ** Changed in: systemd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1661568 Title: logind fails to emit change signal for org.freedesktop.login1.Seat.ActiveSession DBus property Status in systemd package in Ubuntu: In Progress Bug description: logind fails to emit a DBus PropertiesChanged signal for the org.freedesktop.login1.Seat.ActiveSession DBus property. See https://github.com/systemd/systemd/issues/5210. This breaks repowerd on zesty since repowerd depends on this signal to track the active session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1661568/+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 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
... I *suspect* this value may ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: Invalid Status in repowerd package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+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 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
Thanks for the information. I don't see anything wrong in the attached files. Both repowerd and the indicator use the value set in the config-default.xml file as the minimum value (5 out of max 255 => ~2%). I suspend this value may be too low for this device. Note that '5' is also the value used for dimming the screen. If you set the normal brightness value at a normal or high level, do you notice the screen dimming a bit before the inactivity timeout expires, or do you just see the screen blanking without dimming first? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: Invalid Status in repowerd package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+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 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
Repowerd reads the min/max values from the device config xml file shipped with the device. Does this file contain sane values? Could someone with an E5 device paste the contents of: 1. /usr/share/powerd/device_configs/config-default.xml 2. /var/log/repowerd.log Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: Invalid Status in repowerd package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+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 1588526] Re: [mako] Alarm doesn't ring when screen locked
I have prepared a PPA containing a new repowerd with a potential fix for the issue here: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2276 IMPORTANT CAVEAT: The changes are experimental. Only try the PPA packages on a development device, not one you care about keeping stable. You may need to reflash a clean image if things go very wrong. To try the updated packages follow the instructions from the link below: https://wiki.ubuntu.com/Process/Merges/TestPlans/repowerd Let me know if/how the fix works for you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1588526 Title: [mako] Alarm doesn't ring when screen locked Status in Canonical System Image: Fix Committed Status in repowerd: In Progress Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: Fix Released Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1588526] Re: [mako] Alarm doesn't ring when screen locked
** Also affects: repowerd Importance: Undecided Status: New ** Changed in: repowerd Assignee: (unassigned) => Alexandros Frantzis (afrantzis) ** Changed in: repowerd Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1588526 Title: [mako] Alarm doesn't ring when screen locked Status in Canonical System Image: Fix Committed Status in repowerd: In Progress Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: Fix Released Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1642360] Re: Display occasionally stays on forever after boot in rc-proposed
** Changed in: ubuntu-touch-session (Ubuntu)
Assignee: (unassigned) => Alexandros Frantzis (afrantzis)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-session in
Ubuntu.
https://bugs.launchpad.net/bugs/1642360
Title:
Display occasionally stays on forever after boot in rc-proposed
Status in Canonical System Image:
Confirmed
Status in ubuntu-touch-session package in Ubuntu:
New
Bug description:
Occasionally the display stays on forever after boot in rc-proposed,
due to a keep display on request.
The problem seems to be that the keep-display-on-request introduced to
fix bug 1623853, sometimes doesn't get released due to races in the
upstart scripts. This happens if the lightdm job starts before the
keep-display-on-during-boot job starts, in which case the keep-
display-on-during-boot job never gets the signal it needs to stop
("stop on started lightdm").
This issue can be reproduced easily by changing the related upstart
script timings, for example, by inserting a "sleep 10" at the end of
the repowerd.conf pre-start stanza (or post-start stanza, it has the
same effect).
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642360/+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 1642360] Re: Display occasionally stays on forever after boot in rc-proposed
** Description changed:
Occasionally the display stays on forever after boot in rc-proposed, due
to a keep display on request.
The problem seems to be that the keep-display-on-request introduced to
fix bug 1623853, sometimes doesn't get released due to races in the
upstart scripts. This happens if the lightdm job starts before the keep-
display-on-during-boot job starts, in which case the keep-display-on-
during-boot job never gets the signal it needs to stop ("stop on started
lightdm").
This issue can be reproduced easily by changing the related upstart
script timings, for example, by inserting a "sleep 10" at the end of the
- repowerd.conf post-start stanza.
+ repowerd.conf pre-start stanza (or post-start stanza, it has the same
+ effect).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-session in
Ubuntu.
https://bugs.launchpad.net/bugs/1642360
Title:
Display occasionally stays on forever after boot in rc-proposed
Status in Canonical System Image:
Confirmed
Status in ubuntu-touch-session package in Ubuntu:
New
Bug description:
Occasionally the display stays on forever after boot in rc-proposed,
due to a keep display on request.
The problem seems to be that the keep-display-on-request introduced to
fix bug 1623853, sometimes doesn't get released due to races in the
upstart scripts. This happens if the lightdm job starts before the
keep-display-on-during-boot job starts, in which case the keep-
display-on-during-boot job never gets the signal it needs to stop
("stop on started lightdm").
This issue can be reproduced easily by changing the related upstart
script timings, for example, by inserting a "sleep 10" at the end of
the repowerd.conf pre-start stanza (or post-start stanza, it has the
same effect).
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642360/+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 1642360] Re: Display occasionally stays on forever after boot in rc-proposed
** Description changed:
Occasionally the display stays on forever after boot in rc-proposed, due
to a keep display on request.
The problem seems to be that the keep-display-on-request introduced to
fix bug 1623853, sometimes doesn't get released due to races in the
upstart scripts. This happens if the lightdm job starts before the keep-
display-on-during-boot job starts, in which case the keep-display-on-
during-boot job never gets the signal it needs to stop ("stop on started
lightdm").
This issue can be reproduced easily by changing the related upstart
script timings, for example, by inserting a "sleep 10" at the end of the
- repowerd.conf pre-start stanza.
+ repowerd.conf post-start stanza.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-session in
Ubuntu.
https://bugs.launchpad.net/bugs/1642360
Title:
Display occasionally stays on forever after boot in rc-proposed
Status in Canonical System Image:
Confirmed
Status in ubuntu-touch-session package in Ubuntu:
New
Bug description:
Occasionally the display stays on forever after boot in rc-proposed,
due to a keep display on request.
The problem seems to be that the keep-display-on-request introduced to
fix bug 1623853, sometimes doesn't get released due to races in the
upstart scripts. This happens if the lightdm job starts before the
keep-display-on-during-boot job starts, in which case the keep-
display-on-during-boot job never gets the signal it needs to stop
("stop on started lightdm").
This issue can be reproduced easily by changing the related upstart
script timings, for example, by inserting a "sleep 10" at the end of
the repowerd.conf pre-start stanza (or post-start stanza, it has the
same effect).
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642360/+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 1633108] [NEW] syslog deleted after reaching 20M limit
Public bug reported: Due to logrotate rules in lxc-android-config, when /var/log/syslog reaches 20M it is deleted and logging continues in a brand new empty file. If the timing is unfortunate users may lose all syslog information pertaining to a bug or other event of interest soon after the bug/event occurs (e.g., see [1]). [1] https://bugs.launchpad.net/repowerd/+bug/1632573/comments/5 ** Affects: lxc-android-config (Ubuntu) Importance: Undecided Assignee: Alexandros Frantzis (afrantzis) Status: In Progress ** Branch linked: lp:~afrantzis/lxc-android-config/fix-1633108-logrotate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1633108 Title: syslog deleted after reaching 20M limit Status in lxc-android-config package in Ubuntu: In Progress Bug description: Due to logrotate rules in lxc-android-config, when /var/log/syslog reaches 20M it is deleted and logging continues in a brand new empty file. If the timing is unfortunate users may lose all syslog information pertaining to a bug or other event of interest soon after the bug/event occurs (e.g., see [1]). [1] https://bugs.launchpad.net/repowerd/+bug/1632573/comments/5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1633108/+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 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
The repowerd part of the fix has landed in repowerd 2016.10. Now waiting for the upstart script addition to land: https://code.launchpad.net/~afrantzis/ubuntu-touch-session/keep-display- on-during-boot ** Changed in: repowerd (Ubuntu) Status: In Progress => Fix Committed ** Changed in: canonical-devices-system-image Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1623853 Title: Device appears to be off after updating to 15Sept2016's rc-proposed image Status in Canonical System Image: In Progress Status in repowerd package in Ubuntu: Fix Committed Status in ubuntu-touch-session package in Ubuntu: In Progress Bug description: Krillin, rc-proposed/bq-aquaris.en r429 Description: Many people, myself included, are reporting that their devices seemed to have turned off after upgrading to today's rc-proposed In my case it was an updated from r428 to r429. The device rebooted to install the upgrade, then at one point I noticed the display was off and not responding to PwrKey. I had for force shutdown via press-holding PwrKey. A few community members reported the same problem on Arale (MX4) and Freiza (M10), so it seems to be device-independent. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+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 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
** Merge proposal linked: https://code.launchpad.net/~repowerd-team/repowerd/+git/repowerd/+merge/307941 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1623853 Title: Device appears to be off after updating to 15Sept2016's rc-proposed image Status in Canonical System Image: In Progress Status in repowerd package in Ubuntu: In Progress Status in ubuntu-touch-session package in Ubuntu: In Progress Bug description: Krillin, rc-proposed/bq-aquaris.en r429 Description: Many people, myself included, are reporting that their devices seemed to have turned off after upgrading to today's rc-proposed In my case it was an updated from r428 to r429. The device rebooted to install the upgrade, then at one point I noticed the display was off and not responding to PwrKey. I had for force shutdown via press-holding PwrKey. A few community members reported the same problem on Arale (MX4) and Freiza (M10), so it seems to be device-independent. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+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 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
** Changed in: ubuntu-touch-session (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1623853 Title: Device appears to be off after updating to 15Sept2016's rc-proposed image Status in Canonical System Image: In Progress Status in repowerd package in Ubuntu: In Progress Status in ubuntu-touch-session package in Ubuntu: In Progress Bug description: Krillin, rc-proposed/bq-aquaris.en r429 Description: Many people, myself included, are reporting that their devices seemed to have turned off after upgrading to today's rc-proposed In my case it was an updated from r428 to r429. The device rebooted to install the upgrade, then at one point I noticed the display was off and not responding to PwrKey. I had for force shutdown via press-holding PwrKey. A few community members reported the same problem on Arale (MX4) and Freiza (M10), so it seems to be device-independent. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+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 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
** Branch linked: lp:~afrantzis/ubuntu-touch-session/keep-display-on- during-boot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1623853 Title: Device appears to be off after updating to 15Sept2016's rc-proposed image Status in Canonical System Image: Confirmed Status in repowerd package in Ubuntu: Confirmed Status in ubuntu-touch-session package in Ubuntu: New Bug description: Krillin, rc-proposed/bq-aquaris.en r429 Description: Many people, myself included, are reporting that their devices seemed to have turned off after upgrading to today's rc-proposed In my case it was an updated from r428 to r429. The device rebooted to install the upgrade, then at one point I noticed the display was off and not responding to PwrKey. I had for force shutdown via press-holding PwrKey. A few community members reported the same problem on Arale (MX4) and Freiza (M10), so it seems to be device-independent. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+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 1623853] Re: Device appears to be off after updating to 15Sept2016's rc-proposed image
** Also affects: ubuntu-touch-session (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-touch-session (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-touch-session (Ubuntu) Assignee: (unassigned) => Alexandros Frantzis (afrantzis) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1623853 Title: Device appears to be off after updating to 15Sept2016's rc-proposed image Status in Canonical System Image: Confirmed Status in repowerd package in Ubuntu: Confirmed Status in ubuntu-touch-session package in Ubuntu: New Bug description: Krillin, rc-proposed/bq-aquaris.en r429 Description: Many people, myself included, are reporting that their devices seemed to have turned off after upgrading to today's rc-proposed In my case it was an updated from r428 to r429. The device rebooted to install the upgrade, then at one point I noticed the display was off and not responding to PwrKey. I had for force shutdown via press-holding PwrKey. A few community members reported the same problem on Arale (MX4) and Freiza (M10), so it seems to be device-independent. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623853/+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 1502145] Re: Apps can keep screen lit permanently
Bob, could you please attach /var/log/repowerd.log and /var/log/syslog to this bug. It could help us debug this issue. -- 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/1502145 Title: Apps can keep screen lit permanently Status in Canonical System Image: Confirmed Status in Oxide: Fix Released Status in Oxide 1.10 series: Fix Released Status in qtmir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: rc-proposed, r140, krillin There are times when it seems the display blanking policy stops working and the display stays on until I press the power button. Steps to reproduce: * install and start Siete * put it in background Expected outcome: * the display is switched off after a predetermined amount of time Actual outcome: * the display stays on forever == Now that apps can request the screen to stay on, they can do so regardless of whether they're focused/visible or not. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502145/+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 1588526] Re: Alarm doesn't ring when screen locked
@Rasool @Mark Could you please attach the /var/log/syslog file from your device to this bug the next time this (alarm not going off) happens to you? It could help us figure out what is going wrong. @Mark Could you please clarify if "this happened the morning before last" is referring to your alarm not going off at all until you pressed the power button? Unless I am misunderstanding, your comment seems to describe two independent issues seen in two different occasions: 1. alarm not going off at all 2. change in alarm sound not being applied -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1588526 Title: Alarm doesn't ring when screen locked Status in Canonical System Image: Incomplete Status in Ubuntu Clock App: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1627053] [NEW] Need visual indication that video recording isn't capturing sound
Public bug reported: When recording a video and the camera-app doesn't have permission to access the microphone, no audio will be recorded. This is expected of course, but it would be useful to have a visual indication that this is happening, perhaps somewhere on the camera HUD. Without this visual indication the users has no way of knowing that the video won't have any sound, until they try to play back the video, and then it's too late. I have a few important videos without sound for this reason :/. Also, taking a step back, a more fundamental solution would be to follow Matthew's suggestion from bug 1554142: the camera-app shouldn't ask for a special microphone permission, "the ability to record video includes the ability to use the microphone". ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1627053 Title: Need visual indication that video recording isn't capturing sound Status in camera-app package in Ubuntu: New Bug description: When recording a video and the camera-app doesn't have permission to access the microphone, no audio will be recorded. This is expected of course, but it would be useful to have a visual indication that this is happening, perhaps somewhere on the camera HUD. Without this visual indication the users has no way of knowing that the video won't have any sound, until they try to play back the video, and then it's too late. I have a few important videos without sound for this reason :/. Also, taking a step back, a more fundamental solution would be to follow Matthew's suggestion from bug 1554142: the camera-app shouldn't ask for a special microphone permission, "the ability to record video includes the ability to use the microphone". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1627053/+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 1615001] Re: lock display when idle timeout not honoured
** Changed in: repowerd Status: In Progress => Fix Released -- 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/1615001 Title: lock display when idle timeout not honoured Status in Canonical System Image: Fix Released Status in repowerd: Fix Released Status in repowerd package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Opinion Bug description: current build number: 412 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Test Case: 1. Go to system-settings/battery/lock when idle and set it to 5min 2. Reboot the device 3. Wait Expected behaviour Display turns off after 5min Actual Behaviour Display doesn't turn off To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615001/+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 1615001] Re: lock display when idle timeout not honoured
** Changed in: repowerd Status: New => In Progress ** Changed in: repowerd (Ubuntu) Status: New => In Progress ** Changed in: repowerd Importance: Undecided => High ** Changed in: repowerd (Ubuntu) Importance: Undecided => High ** Changed in: repowerd (Ubuntu) Assignee: (unassigned) => Alexandros Frantzis (afrantzis) ** Changed in: repowerd Assignee: (unassigned) => Alexandros Frantzis (afrantzis) -- 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/1615001 Title: lock display when idle timeout not honoured Status in Canonical System Image: New Status in repowerd: In Progress Status in repowerd package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Opinion Bug description: current build number: 412 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Test Case: 1. Go to system-settings/battery/lock when idle and set it to 5min 2. Reboot the device 3. Wait Expected behaviour Display turns off after 5min Actual Behaviour Display doesn't turn off To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615001/+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 1613601] Re: [MIR] unity-system-compositor
A new package 0.7.1+16.10.20160824-0ubuntu1 has been uploaded with the required fixes: > - android-properties should be a Build-Dep in arm64, right? Added. > - Is ubuntu-desktop-mir needed anymore? No, removed. > - This builds its autopilot package with python2... Switched everything to python3. > - Can we subscribe phablet-team, ubuntu-phonedations-bugs, or unity- api-team to LP bugs? Added mir-team, see https://bugs.launchpad.net/ubuntu/+source/unity- system-compositor/+bug/1613601/+subscriptions > - Does anyone know if we can drop the "sleep .1" from the wrapper script? I worry the answer is no, and that we will never drop it. The original authors don't recall the exact reason it was added, so more investigation is needed before we take any action. -- 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/1613601 Title: [MIR] unity-system-compositor Status in unity-system-compositor package in Ubuntu: Incomplete Bug description: Note that a much older version of unity-system-compositor had been previously accepted into main: https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1203588 [Availability] * Available in universe [Rationale] * This package is the system compositor for our convergence effort * Used by default on phablet images and in the Unity8 session on the desktop [Security] * No known security issues at this time * A security review is recommended. The package had been reviewed in the past by the security team for use on the phone, but it has changed significantly since then. [Quality assurance] * This package has unit and integration tests that run with each package build * CI is used during development [Dependencies] * All dependencies are in main * It 'Suggests' repowerd which already has a MIR: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1613585 [Standards compliance] * Follows FHS and Debian Policy. * This package uses cmake. [Maintenance] * This package is maintained by Canonical and actively in use on the phone images * mir-development-team/unity-system-compositor-team are subscribed to project and ubuntu package bugs respectively (The unity-system-compositor developers are the Mir developers) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1613601/+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 1615001] Re: lock display when idle timeout not honoured
** Changed in: repowerd Assignee: Alexandros Frantzis (afrantzis) => (unassigned) ** Changed in: repowerd (Ubuntu) Assignee: Alexandros Frantzis (afrantzis) => (unassigned) -- 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/1615001 Title: lock display when idle timeout not honoured Status in Canonical System Image: New Status in repowerd: New Status in repowerd package in Ubuntu: New Status in unity8 package in Ubuntu: Opinion Bug description: current build number: 412 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en Test Case: 1. Go to system-settings/battery/lock when idle and set it to 5min 2. Reboot the device 3. Wait Expected behaviour Display turns off after 5min Actual Behaviour Display doesn't turn off To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615001/+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 1613601] [NEW] [MIR] unity-system-compositor
Public bug reported: Note that a much older version of unity-system-compositor had been previously accepted into main: https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1203588 [Availability] * Available in universe [Rationale] * This package is the system compositor for our convergence effort * Used by default on phablet images and in the Unity8 session on the desktop [Security] * No known security issues at this time * A security review is recommended. The package had been reviewed in the past by the security team for use on the phone, but it has changed significantly since then. [Quality assurance] * This package has unit and integration tests that run with each package build * CI is used during development [Dependencies] * All dependencies are in main * It 'Suggests' repowerd which already has a MIR: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1613585 [Standards compliance] * Follows FHS and Debian Policy. * This package uses cmake. [Maintenance] * This package is maintained by Canonical and actively in use on the phone images * mir-development-team/unity-system-compositor-team are subscribed to project and ubuntu package bugs respectively (The unity-system-compositor developers are the Mir developers) ** Affects: unity-system-compositor (Ubuntu) Importance: Undecided Status: New -- 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/1613601 Title: [MIR] unity-system-compositor Status in unity-system-compositor package in Ubuntu: New Bug description: Note that a much older version of unity-system-compositor had been previously accepted into main: https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1203588 [Availability] * Available in universe [Rationale] * This package is the system compositor for our convergence effort * Used by default on phablet images and in the Unity8 session on the desktop [Security] * No known security issues at this time * A security review is recommended. The package had been reviewed in the past by the security team for use on the phone, but it has changed significantly since then. [Quality assurance] * This package has unit and integration tests that run with each package build * CI is used during development [Dependencies] * All dependencies are in main * It 'Suggests' repowerd which already has a MIR: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1613585 [Standards compliance] * Follows FHS and Debian Policy. * This package uses cmake. [Maintenance] * This package is maintained by Canonical and actively in use on the phone images * mir-development-team/unity-system-compositor-team are subscribed to project and ubuntu package bugs respectively (The unity-system-compositor developers are the Mir developers) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1613601/+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 1603024] Re: Battery drain on Nexus 4 when no network is available
The top output doesn't implicate repowerd. Note, however, that the top output is incomplete so we don't have the whole picture. For future reference you can take textual snapshots of top with: top -b -n10 -d1 > /tmp/top.txt (Write to file 10 textual snapshots with 1 sec delay between snapshots) If you come across this problem again, please provide the output of the command above. >From the provided top screenshot, it's interesting to note that the total CPU times for unity8 and upowerd are very high relative to the uptime, so the cause of the drain could be in one of these components. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: upower (Ubuntu) Importance: Undecided Status: New ** Changed in: repowerd Status: New => Incomplete -- 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/1603024 Title: Battery drain on Nexus 4 when no network is available Status in repowerd: Incomplete Status in unity8 package in Ubuntu: New Status in upower package in Ubuntu: New Bug description: Nexus 4 connected to wifi but not logged in so no network available. Battery drained from full to empty in 6 hours, with no use. rc_proposed Image Part: 10160714 Build No: R486 Device Image Part: 20160404.1 To manage notifications about this bug go to: https://bugs.launchpad.net/repowerd/+bug/1603024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1570698] Re: CI failure in TestClientInput.receives_one_touch_event_per_frame
And again: https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1474/console
and: https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1475/console
Raising importance to high.
** Changed in: mir
Importance: Medium => 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/1570698
Title:
CI failure in TestClientInput.receives_one_touch_event_per_frame
Status in Mir:
Triaged
Status in mir package in Ubuntu:
Triaged
Bug description:
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/863/consoleFull
02:44:41 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
02:44:41 11: [2016-04-15 02:44:41.425619] mirserver: Starting
02:44:41 11: [2016-04-15 02:44:41.430805] mirserver: Selected driver: dummy
(version 0.22.0)
02:44:41 11: [2016-04-15 02:44:41.499565] mirserver: Using software cursor
02:44:41 11: [2016-04-15 02:44:41.509983] mirserver: Initial display
configuration:
02:44:41 11: [2016-04-15 02:44:41.510510] mirserver: 1.1: VGA 0.0" 0x0mm
02:44:41 11: [2016-04-15 02:44:41.510809] mirserver: Current mode 1000x800
60.00Hz
02:44:41 11: [2016-04-15 02:44:41.511107] mirserver: Preferred mode 1000x800
60.00Hz
02:44:41 11: [2016-04-15 02:44:41.511379] mirserver: Logical position +0+0
02:44:41 11: [2016-04-15 02:44:41.565602] mirserver: Selected input driver:
mir:stub-input (version: 0.22.0)
02:44:41 11: [2016-04-15 02:44:41.568428] mirserver: Mir version 0.22.0
02:44:44 11:
02:44:44 11: GMOCK WARNING:
02:44:44 11: Uninteresting mock function call - returning directly.
02:44:44 11: Function call: handle_input(touch_event(when=2480338825735318
(133.240680ms ago), from=3, touch = {{id=1, action=change, tool=finger,
x=7.68054, y=12.2889, pressure=1, major=5, minor=8, size=8}, modifiers=1))
02:44:44 11: Stack trace:
02:44:44 11:
/��BUILDDIR��/mir-0.22.0+xenial881bzr3443/tests/acceptance-tests/test_client_input.cpp:639:
Failure
02:44:44 11: The difference between 1.0f and client_input_events_per_frame is
0.2400953674316, which exceeds 0.2f, where
02:44:44 11: 1.0f evaluates to 1,
02:44:44 11: client_input_events_per_frame evaluates to 0.7599046325684,
and
02:44:44 11: 0.2f evaluates to 0.2000298023224.
02:44:44 11:
02:44:44 11: GMOCK WARNING:
02:44:44 11: Uninteresting mock function call - returning directly.
02:44:45 11: Function call: handle_input(touch_event(when=2480339119018976
(10.576963ms ago), from=3, touch = {{id=1, action=change, tool=finger,
x=7.80214, y=12.4834, pressure=1, major=5, minor=8, size=8}, modifiers=1))
02:44:45 11: Stack trace:
02:44:45 11:
02:44:45 11: GMOCK WARNING:
02:44:45 11: Uninteresting mock function call - returning directly.
02:44:45 11: Function call: handle_input(touch_event(when=2480339135968128
(14.812916ms ago), from=3, touch = {{id=1, action=change, tool=finger,
x=7.84436, y=12.551, pressure=1, major=5, minor=8, size=8}, modifiers=1))
02:44:45 11: Stack trace:
02:44:45 11: [2016-04-15 02:44:45.407565] mirserver: Stopping
02:44:45 11: [ FAILED ] TestClientInput.receives_one_touch_event_per_frame
(4083 ms)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1570698/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1597364] Re: Option for screen dimming is sometimes not visible
Is this a duplicate of https://bugs.launchpad.net/powerd/+bug/1540804 ? -- 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/1597364 Title: Option for screen dimming is sometimes not visible Status in Canonical System Image: Confirmed Status in powerd package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: In System Settings, the option for automatic screen dimming is sometimes not visible. I observed this behaviour on a Meizu Pro 5. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597364/+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 1493013] Re: CI test failure (segmentation fault) in ServerShutdown.server_can_shut_down_when_clients_are_blocked
** Changed in: mir Status: New => Incomplete ** No longer affects: mir (Ubuntu) -- 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/1493013 Title: CI test failure (segmentation fault) in ServerShutdown.server_can_shut_down_when_clients_are_blocked Status in Mir: Incomplete Bug description: As seen in https://jenkins.qa.ubuntu.com/job/mir-clang-vivid- amd64-build/2749/consoleFull : 7: [ RUN ] ServerShutdown.server_can_shut_down_when_clients_are_blocked 7: [1441614824.310851] mirplatform: Found graphics driver: mesa-kms 7: [1441614824.310869] mirplatform: Found graphics driver: mesa-x11 7: [1441614824.310882] mirplatform: Found graphics driver: android 7: [1441614824.310923] mirplatform: Found graphics driver: dummy 7: [1441614824.314576] mirserver: Initial display configuration: 7: [1441614824.314600] mirserver: 1.1: VGA 0.0" 0x0mm 7: [1441614824.314609] mirserver: Current mode 1600x1600 60.00Hz 7: [1441614824.314614] mirserver: Preferred mode 1600x1600 60.00Hz 7: [1441614824.314618] mirserver: Logical position +0+0 7: [1441614824.314846] mirserver: Mir version 0.16.0 7: [1441614824.336046] MirSurfaceAPI: Caught exception at client library boundary (in mir_surface_release): /mir/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector &, const std::vector &) 7: Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorE 7: std::exception::what: Failed to send message to server: Broken pipe 7: 32, "Broken pipe" 7: [1441614824.336149] MirConnectionAPI: Caught exception at client library boundary (in release): /mir/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector &, const std::vector &) 7: Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorE 7: std::exception::what: Failed to send message to server: Broken pipe 7: 32, "Broken pipe" 7: /mir/tools/detect_fd_leaks.bash: line 84: 503 Segmentation fault (core dumped) $@ 2>&1 7:504 Done| detect_fd_leaks 7/9 Test #7: mir_integration_tests .***Failed2.98 sec To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1493013/+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 1518385] Re: Proximity sensor kept active after call ended
> @alf - should this be covered under ota12 with the repowerd release? Repowerd properly implements "After the call is finished, the proximity sensor must be deactivated.", so yes. However, repowerd does not implement "Leaving the phone for a minute must not dim the screen.", since it contradicts the policy document, as noted in a previous comment. -- 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/1518385 Title: Proximity sensor kept active after call ended Status in Canonical System Image: Confirmed Status in powerd package in Ubuntu: Confirmed Bug description: Test case. - Open the dialer app. - Make a call. - Accept the call in the receiver phone. - Leave the phone for a minute. - Finish the call on the receiver phone. Expected result. - Leaving the phone for a minute must not dim the screen. - After the call is finished, the proximity sensor must be deactivated. Actual result. - After a minute the screen dims. - After the call is finished, the proximity sensor is active. current build number: 27 device name: krillin channel: ubuntu-touch/stable/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518385/+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 1570922] Re: "Placeholder" notification emits powerd notification event
** No longer affects: unity-notifications (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
https://bugs.launchpad.net/bugs/1570922
Title:
"Placeholder" notification emits powerd notification event
Status in unity8 package in Ubuntu:
Triaged
Bug description:
Steps to reproduce:
1. In Notification.qml add:
Component.onDestruction { console.log("Notification onDestruction");
}
and a similar log message in Component.onCompleted.
2. Install dialer-app-autopilot on the phone. This installs a fake phone sim,
that, among other things, creates a fake voice mail every time unity8 starts.
3. Restart unity8.
4. A notification is created for the voice mail, before unity8 is fully
drawn. No bubble can be seen, only the green envelope on top. Note that in
~/.cache/upstart/unity8.log the notification onCompleted log message can be
seen, but not an onDestruction message.
5. stop unity8. Note that ~/.cache/upstart/unity8.log now contains the
onDestruction message.
Effectively the initial notification is somehow "leaked" and not
destroyed until the end of the program. This presents a problem in the
new power architecture model, where unity8 needs to report both when a
notification is shown (it already does so) and when it is destroyed.
Notifications sent after unity8 has completed loading are properly
destroyed when their bubble disappears.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1570922/+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 1585352] Re: Screen comes on beyond the timeout after an incoming text with proximity near
repowerd exhibits the correct behavior -- 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/1585352 Title: Screen comes on beyond the timeout after an incoming text with proximity near Status in Canonical System Image: New Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Receive an SMS with the screen face down or in the pocket Wait longer than the short timeout of 15 secs, say 30-60 Uncover the proximity sensor The screen comes on (immediately on E4.5 but sometimes with a sizeable delay on mx4) Tested on latest proposed on E4.5 and 326 on mx4 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1585352/+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 1570922] Re: Initial notifications never shown and not destroyed until unity8 is stopped
> You can debug this a bit by adding more info into your onCompleted print:
> like "summary", "body", and "type". If type == 0, it's a
> placeholder (and summary and body will be empty). And you can ignore it if so.
Thanks for looking into this.
What I am seeing is indeed caused by this peculiar "placeholder"
notification. This is still a bug, in the sense that unity8 emits a
powerd notification event for a notification that's not real and this
confuses the new power daemon (repowerd). I will need to create a fix
for this issue in unity8.
** Changed in: unity8 (Ubuntu)
Status: Incomplete => Triaged
** Changed in: unity8 (Ubuntu)
Assignee: Michael Terry (mterry) => Alexandros Frantzis (afrantzis)
** Summary changed:
- Initial notifications never shown and not destroyed until unity8 is stopped
+ "Placeholder" notification emits powerd notification event
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-notifications in
Ubuntu.
https://bugs.launchpad.net/bugs/1570922
Title:
"Placeholder" notification emits powerd notification event
Status in unity-notifications package in Ubuntu:
New
Status in unity8 package in Ubuntu:
Triaged
Bug description:
Steps to reproduce:
1. In Notification.qml add:
Component.onDestruction { console.log("Notification onDestruction");
}
and a similar log message in Component.onCompleted.
2. Install dialer-app-autopilot on the phone. This installs a fake phone sim,
that, among other things, creates a fake voice mail every time unity8 starts.
3. Restart unity8.
4. A notification is created for the voice mail, before unity8 is fully
drawn. No bubble can be seen, only the green envelope on top. Note that in
~/.cache/upstart/unity8.log the notification onCompleted log message can be
seen, but not an onDestruction message.
5. stop unity8. Note that ~/.cache/upstart/unity8.log now contains the
onDestruction message.
Effectively the initial notification is somehow "leaked" and not
destroyed until the end of the program. This presents a problem in the
new power architecture model, where unity8 needs to report both when a
notification is shown (it already does so) and when it is destroyed.
Notifications sent after unity8 has completed loading are properly
destroyed when their bubble disappears.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-notifications/+bug/1570922/+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 1566028] Re: low battery notification does not honor proximity sensor
I am not able to reproduce this (tried on krillin) with a fake/mock battery. >From a shell on the phone (e.g. with phablet-shell), to enable the mock battery: $ gdbus call --session --dest "com.canonical.indicator.power" \ --object-path /com/canonical/indicator/power/Testing \ --method org.freedesktop.DBus.Properties.Set \ com.canonical.indicator.power.Testing \ MockBatteryEnabled \ "" Set the mock battery's charge to 10% $ gdbus call --session --dest "com.canonical.indicator.power" \ --object-path /com/canonical/indicator/power/Testing \ --method org.freedesktop.DBus.Properties.Set \ com.canonical.indicator.power.Testing \ MockBatteryLevel \ "" -- 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/1566028 Title: low battery notification does not honor proximity sensor Status in Canonical System Image: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: per our "display blanking spec" we want all notifications to activate the proximity sensor & be obedient to it. This includes any dialogs that are initiated without user input. (from Pat) One example is I experienced the low battery notification which turned on the screen, ignoring proximity, and allowing subsequent touch events that lead to a locked device. I later reproduced this by covering the sensor completely and seeing that in fact the screen is always turned on. it's worth noting that all other notifications appear to obey the proximity sensor. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1566028/+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 1570922] [NEW] Initial notifications never shown and not destroyed until unity8 is stopped
Public bug reported:
Steps to reproduce:
1. In Notification.qml add:
Component.onDestruction { console.log("Notification onDestruction"); }
and a similar log message in Component.onCompleted.
2. Install dialer-app-autopilot on the phone. This installs a fake phone sim,
that, among other things, creates a fake voice mail every time unity8 starts.
3. Restart unity8.
4. A notification is created for the voice mail, before unity8 is fully drawn.
No bubble can be seen, only the green envelope on top. Note that in
~/.cache/upstart/unity8.log the notification onCompleted log message can be
seen, but not an onDestruction message.
5. stop unity8. Note that ~/.cache/upstart/unity8.log now contains the
onDestruction message.
Effectively the initial notification is somehow "leaked" and not
destroyed until the end of the program. This presents a problem in the
new power architecture model, where unity8 needs to report both when a
notification is shown (it already does so) and when it is destroyed.
Notifications sent after unity8 has completed loading are properly
destroyed when their bubble disappears.
** Affects: unity8 (Ubuntu)
Importance: Undecided
Assignee: Michael Terry (mterry)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1570922
Title:
Initial notifications never shown and not destroyed until unity8 is
stopped
Status in unity8 package in Ubuntu:
New
Bug description:
Steps to reproduce:
1. In Notification.qml add:
Component.onDestruction { console.log("Notification onDestruction");
}
and a similar log message in Component.onCompleted.
2. Install dialer-app-autopilot on the phone. This installs a fake phone sim,
that, among other things, creates a fake voice mail every time unity8 starts.
3. Restart unity8.
4. A notification is created for the voice mail, before unity8 is fully
drawn. No bubble can be seen, only the green envelope on top. Note that in
~/.cache/upstart/unity8.log the notification onCompleted log message can be
seen, but not an onDestruction message.
5. stop unity8. Note that ~/.cache/upstart/unity8.log now contains the
onDestruction message.
Effectively the initial notification is somehow "leaked" and not
destroyed until the end of the program. This presents a problem in the
new power architecture model, where unity8 needs to report both when a
notification is shown (it already does so) and when it is destroyed.
Notifications sent after unity8 has completed loading are properly
destroyed when their bubble disappears.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1570922/+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
This seems to be another instance of bug 1550050, which involves the Mir input subsystem sending key repeat events event after an input device disappears. In this case the repeated key is the circular touch key at the bottom of the MX4 (which is sent as left-meta). A fix for this is included in the upcoming Mir 0.20.2 release. I have added steps to reproduce this on MX4 in the description. ** Description changed: 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: + [sudo] password for phablet: System State Requests: - Name: com.canonical.Unity.Screen, Owner: :1.14, State: 1 + 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 ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny) ** Changed in: mir (Ubuntu) Importance: Undecided => High ** Changed in: mir (Ubuntu) Status: New => Confirmed -- 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 package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New 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 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
** Attachment added: "Input devices list" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549701/+attachment/4592385/+files/input-devices.txt -- 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 unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New 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 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
** Attachment added: "Input event log" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1549701/+attachment/4592384/+files/input-events.txt -- 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 unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New 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 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
With the help of Jean-Baptiste I was able to get some more information from a device exhibiting the problem. The logs indicate that the phone is continuously receiving repeat key events (scancode=125=left-meta) from the touchscreen input device. These events are keeping the device awake. -- 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 unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New 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 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 1552371] Re: Unexpected display on
> So you are saying we should have the proximity sensor on all the time ? > I disagree, first that's a power drain. Second, people will complain about > the screen blanking off just interacting with the device. There is a third, ideal way which would be to check the proximity value just before making the transition from off to on. This is currently difficult due to the overall power management architecture and the fact that the proximity API given to us doesn't provide a query function (we get change events, but can't get the current state). In the current system we have worked around this for SMS, calls etc with some funky hacks in USC and powerd which would be difficult to extend to other use cases. In the new architecture I expect that we will be able to manage proximity (and this case in particular) much more elegantly. > The right answer is to get the policy correct in the first place and filter the events properly into those that you want to turn on the display and those you don't. This is correct. Currently USC wakes up the screen when any key other than power and volume (which are handled specially) or a pointer events arrive. Perhaps there is a bug in our input subsystem and we send stray key events, or perhaps the events are valid (some kind of special key event not corresponding to user input?) and we should filter more strictly. In any case, we need to find out more about these unexpected events to make an informed decision. -- 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. 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 1549701] Re: Sometimes devices don't suspend
Is there an app running (perhaps in the background) that's keeping the screen on? -- 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 Status in Canonical System Image: Incomplete Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New 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 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 1543495] Re: boot splash not in native orientation
Packages for unity-system-compositor 0.4.2 that include the orientation improvements are here: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-075/ I don't have the device, so I can't try on it, so please give the new version a try and let me know how it works for you. ** Changed in: unity-system-compositor Importance: Undecided => Critical ** Changed in: unity-system-compositor Milestone: 0.5.0 => 0.4.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/1543495 Title: boot splash not in native orientation Status in The Avila project: Confirmed Status in Canonical System Image: Confirmed Status in Unity System Compositor: Fix Committed Status in unity-system-compositor package in Ubuntu: In Progress 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 1543495] Re: boot splash not in native orientation
** Changed in: unity-system-compositor (Ubuntu) Status: Confirmed => In Progress ** Branch linked: lp:~afrantzis/unity-system-compositor/fix-1543495 -spinner-orientation -- 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: boot splash not in native orientation Status in The Avila project: Confirmed Status in Canonical System Image: Confirmed Status in unity-system-compositor package in Ubuntu: In Progress 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 1532607] Re: Phone not usable while a call comes in - followed by "restart"
*** This bug is a duplicate of bug 1506358 *** https://bugs.launchpad.net/bugs/1506358 The core problem here is that USC crashes with "Compositor thread failed to start" (see unity-system-compositor.log.old), not that libmirclient throws (because the server crashed, in this case). I think this bug should be kept separate from bug #1506358. -- 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 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 1486284] Re: /usr/bin/powerd:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:std::thread::~thread:std::default_delete
** Changed in: powerd (Ubuntu) Status: New => In Progress -- 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/1486284 Title: /usr/bin/powerd:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:std::thread::~thread:std::default_delete Status in Canonical System Image: Confirmed Status in powerd package in Ubuntu: In Progress Bug description: Number 2 on errors.u.c over past week on rc-proposed. Frequency increased significantly with 0.16+15.04.20160111.1-0ubuntu1 The Ubuntu Error Tracker has been receiving reports about a problem regarding powerd. This problem was most recently seen with version 0.16+15.10.20150728-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/bb839865ca4601389dd0bc572bc670f687fd97c8 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1486284/+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 1488413] Re: connected BT mouse should unblank screen (windowed mode)
** Changed in: unity-system-compositor (Ubuntu) Assignee: (unassigned) => Alexandros Frantzis (afrantzis) -- 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/1488413 Title: connected BT mouse should unblank screen (windowed mode) Status in Canonical System Image: In Progress Status in canonical-pocket-desktop: In Progress Status in Unity System Compositor: Fix Committed Status in unity-system-compositor package in Ubuntu: In Progress Bug description: when switching into windowed mode && a BT mouse is connected && screen is blanked (from time out or pwr key press) the BT mouse motion should unblank the screen this may effect multiple projects so sort of shotgunning the effected project list To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488413/+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 1488413] Re: connected BT mouse should unblank screen (windowed mode)
** Changed in: unity-system-compositor Assignee: (unassigned) => Alexandros Frantzis (afrantzis) ** Changed in: unity-system-compositor Status: New => Triaged ** Changed in: unity-system-compositor Importance: Undecided => Critical ** Changed in: unity-system-compositor Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1488413 Title: connected BT mouse should unblank screen (windowed mode) Status in Canonical System Image: Confirmed Status in canonical-pocket-desktop: New Status in Mir: Incomplete Status in Unity System Compositor: In Progress Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: when switching into windowed mode && a BT mouse is connected && screen is blanked (from time out or pwr key press) the BT mouse motion should unblank the screen this may effect multiple projects so sort of shotgunning the effected project list To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488413/+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 1518385] Re: Proximity sensor kept active after call ended
This is different from bug #1531158 and it describes two different behaviors. > Expected - Leaving the phone for a minute must not dim the screen. > Actual - After a minute the screen dims. (I am assuming this is referring to the case when a call is active) USC/Powerd currently implement the behavior as stated in the requirements doc [1]. In particular, the use case: "answer call, let the inactivity timer of 60secs turn off screen [YES] proximity cover/uncover should turn on the screen [YES]". > Expected - After the call is finished, the proximity sensor must be > deactivated. > Actual - After the call is finished, the proximity sensor is active. This is a known issue. There are some technical/architectural issues that have stopped us from providing a better behavior. Currently, ending a call is treated (almost) like a notification arrival, which enables proximity, turns on the screen (if screen is not covered) and enables a short inactivity timeout (15s). [1] https://docs.google.com/document/d/1RBoVknCLZ4GQ8E_iVftd3i_KmdxI5d6JrBt7i5EDZO0/edit ** This bug is no longer a duplicate of bug 1531158 Screen stays black if outgoing call is rejected -- 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/1518385 Title: Proximity sensor kept active after call ended Status in Canonical System Image: Confirmed Status in powerd package in Ubuntu: New Bug description: Test case. - Open the dialer app. - Make a call. - Accept the call in the receiver phone. - Leave the phone for a minute. - Finish the call on the receiver phone. Expected result. - Leaving the phone for a minute must not dim the screen. - After the call is finished, the proximity sensor must be deactivated. Actual result. - After a minute the screen dims. - After the call is finished, the proximity sensor is active. current build number: 27 device name: krillin channel: ubuntu-touch/stable/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518385/+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 1531158] Re: Screen stays black if outgoing call is rejected
You can find packages with the fix at: https://launchpad.net/~ci-train- ppa-service/+archive/ubuntu/landing-025/+packages Note that when a call is rejected the screen is turned on regardless of proximity status. This is a different issue, not related to this bug (or the fix for the bug). -- 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/1531158 Title: Screen stays black if outgoing call is rejected Status in Canonical System Image: Confirmed Status in dialer-app: Opinion Status in powerd package in Ubuntu: In Progress Bug description: current build number: 210 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en Test Case: 1. On DUT1 make a call to DUT2 and cover the proximity sensor 2. On DUT2: - If call forwarding is set to reject the call immediately (ie not redirect to the voicemail), reject the call - Alternatively, you can take the call and immediately hang up. 3. On DUT1, once the call is terminated, uncover the proximity sensor Expected Result Screen is on Actual Result Screen stays black and cannot be switched on even with the power button. After a moment, the screen blinks and works normally again. It works as expected on stable. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531158/+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 1531158] Re: Screen stays black if outgoing call is rejected
** Package changed: unity-system-compositor (Ubuntu) => powerd (Ubuntu) ** Changed in: powerd (Ubuntu) Status: New => In Progress -- 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/1531158 Title: Screen stays black if outgoing call is rejected Status in Canonical System Image: Confirmed Status in dialer-app: Opinion Status in powerd package in Ubuntu: In Progress Bug description: current build number: 210 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en Test Case: 1. On DUT1 make a call to DUT2 and cover the proximity sensor 2. On DUT2: - If call forwarding is set to reject the call immediately (ie not redirect to the voicemail), reject the call - Alternatively, you can take the call and immediately hang up. 3. On DUT1, once the call is terminated, uncover the proximity sensor Expected Result Screen is on Actual Result Screen stays black and cannot be switched on even with the power button. After a moment, the screen blinks and works normally again. It works as expected on stable. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531158/+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 1491881] Re: Intermittent mir-clang-ts-vivid-amd64-build test failures
** Changed in: mir Status: New => Triaged -- 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/1491881 Title: Intermittent mir-clang-ts-vivid-amd64-build test failures Status in Mir: Triaged Status in mir package in Ubuntu: New Bug description: See http://s-jenkins.ubuntu-ci:8080/job/mir-clang-ts-vivid- amd64-build/ for the full job history. A few instances: ~ http://s-jenkins.ubuntu-ci:8080/job/mir-clang-ts-vivid- amd64-build/226/console 8: [ RUN ] BufferQueue/WithTwoOrMoreBuffers.stress/1 8: ==30514==ERROR: ThreadSanitizer failed to allocate 0x12000 (73728) bytes of SignalContext (errno: 12) 8: ERROR: Failed to mmap 8/9 Test #8: mir_unit_tests ***Failed 739.00 sec ~ http://s-jenkins.ubuntu-ci:8080/job/mir-clang-ts-vivid- amd64-build/203/console 8: [ RUN ] BufferQueue/WithAnyNumberOfBuffers.compositor_release_verifies_parameter/1 8: ==23108==ERROR: ThreadSanitizer failed to allocate 0x1 (65536) bytes of stack depot (errno: 12) 8: ERROR: Failed to mmap To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1491881/+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 1512100] Re: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear
The fix for this bug has been committed to our Android code tree. Waiting for this change to be released as part of a device image. -- 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/1512100 Title: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear Status in Canonical System Image: Confirmed Status in powerd package in Ubuntu: In Progress Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: I have a problem with my Meizu MX4 (Arale r6). During a call if you remove the phone from your ear, sometimes (not always) the screen remains turned off. When you try to push the power button to wake up the screen, that starts blinking and it's not possible to hang up. The screen remains in that condition even after the end of the call. When it keeps blinking I try to hold the button down and in few seconds the screen turns black and the phone starts working again. Sometimes, instead, it starts working again by itself. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512100/+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 1516272] Re: Bluetooth keyboard use doesn't prevent screen blanking
** Changed in: unity-system-compositor Status: New => Fix Committed ** Changed in: unity-system-compositor Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny) -- 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/1516272 Title: Bluetooth keyboard use doesn't prevent screen blanking Status in canonical-pocket-desktop: New Status in Unity System Compositor: Fix Committed Status in unity8 package in Ubuntu: Confirmed Bug description: Bluetooth mouse movement clears "idle" flag, but Bluetooth keyboard does not... so if you use a bluetooth keyboard to type for more than a few minutes the screen will blank Tested in r162 14/11/15 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1516272/+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 1520422] Re: Keyboard and mouse events should prevent screen turning off
*** This bug is a duplicate of bug 1516272 *** https://bugs.launchpad.net/bugs/1516272 ** Changed in: unity-system-compositor (Ubuntu) Status: Confirmed => Fix Committed ** This bug has been marked a duplicate of bug 1516272 Bluetooth keyboard use doesn't prevent screen blanking -- 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/1520422 Title: Keyboard and mouse events should prevent screen turning off Status in Canonical System Image: In Progress Status in canonical-pocket-desktop: In Progress Status in unity-system-compositor package in Ubuntu: Fix Committed Bug description: I often use a bluetooth keyboard with the terminal for long periods. When I do so, I have to keep tapping the screen to keep it awake. That in turn enters a tab character so I then have to delete the inserted tab. It's a pretty frustrating way to work. Instead, every bluetooth keypress should count as a screen wake event. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1520422/+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 1384941] Re: Incoming SMS while on a phone call turns screen on
** Changed in: unity-system-compositor Status: In Progress => Fix Released -- 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/1384941 Title: Incoming SMS while on a phone call turns screen on Status in Unity System Compositor: Fix Released Status in powerd package in Ubuntu: Fix Released Bug description: While testing krillin RTM image #120 I noticed that if an incoming SMS is received while on the phone, and the phone is held to your ear, the incoming SMS will cause the screen to come on. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-system-compositor/+bug/1384941/+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 1444857] Re: [enhancement] Allow clients to specify buffering mode for their surfaces
This will be provided by the new buffer semantics. ** Changed in: mir Status: In Progress => New ** Changed in: mir Assignee: Alexandros Frantzis (afrantzis) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1444857 Title: [enhancement] Allow clients to specify buffering mode for their surfaces Status in Mir: New Status in mir package in Ubuntu: New Bug description: Allow clients to specify the buffering mode for their surfaces, so that they can optimize for latency or fluidity, depending on the expected rendering performance (e.g., if it's expected to occasionally miss vsyncs) of the application. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1444857/+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 1518262] Re: Screen does not turn off
Stefan, thanks for the quick feedback. Which was the app that was keeping the screen on? -- 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/1518262 Title: Screen does not turn off Status in Canonical System Image: New Status in unity-system-compositor package in Ubuntu: New Bug description: In the system settings I choose to turn the screen off after 2 minutes. But since OTA-8 it isn't work anymore on my MX4. I tried to change the settings, but it didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518262/+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 1518262] Re: Screen does not turn off
Do you mean that the screen doesn't turn off automatically after two minutes of inactivity? Do you have any apps open (either active or in the background)? If so, please try closing the apps and see if that resolves the problem. -- 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/1518262 Title: Screen does not turn off Status in Canonical System Image: New Status in unity-system-compositor package in Ubuntu: New Bug description: In the system settings I choose to turn the screen off after 2 minutes. But since OTA-8 it isn't work anymore on my MX4. I tried to change the settings, but it didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1518262/+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 1512100] Re: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear
We have tracked down the problem in the Android sensor HAL code and we are currently working on a fix. -- 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/1512100 Title: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear Status in Canonical System Image: Confirmed Status in powerd package in Ubuntu: In Progress Status in unity-system-compositor package in Ubuntu: New Bug description: I have a problem with my Meizu MX4 (Arale r6). During a call if you remove the phone from your ear, sometimes (not always) the screen remains turned off. When you try to push the power button to wake up the screen, that starts blinking and it's not possible to hang up. The screen remains in that condition even after the end of the call. When it keeps blinking I try to hold the button down and in few seconds the screen turns black and the phone starts working again. Sometimes, instead, it starts working again by itself. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512100/+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 1512100] Re: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear
More evidence that this is a problem at a level below either USC or powerd: 0. Build a test program to use and print out events from ubuntu application proximity sensor api (you can use [1] as a starting point, just remove other sensors to reduce irrelevant messages). 1. Use "tail -F /var/log/syslog" to follow powerd messages 2. Start a phone call 3. Start the test program (the one built in step (0)) 4. Cover/uncover the proximity sensor, note the powerd output in syslog and the test program output 5. Continue covering/uncovering, at some point (you need to be patient) powerd will stop reacting to proximity events (the screen won't turn on/off). Note how at this point (a) there is no powerd output as a response to proximity in syslog (b) there *are* kernel message about proximity near/far in syslog (c) the test program has also stopped reacting to proximity events (i.e. the sensor api has stopped calling the event callback) The observed behavior strongly indicates that this is a problem at a layer below powerd. If it was just a powerd issue the test program would continue responding to proximity events. Note, however, that I haven't been able to reproduce this problem with just the test program running. This suggests (but it's just a speculation at this point) that some additional interaction in powerd (screen on/off?, suspending?) triggers the problem at the lower levels, or at least makes the problem more likely to occur. [1] https://bazaar.launchpad.net/~phablet-team/platform- api/trunk/view/head:/examples/test_sensors_api.cpp -- 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/1512100 Title: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear Status in Canonical System Image: Confirmed Status in powerd package in Ubuntu: In Progress Status in unity-system-compositor package in Ubuntu: New Bug description: I have a problem with my Meizu MX4 (Arale r6). During a call if you remove the phone from your ear, sometimes (not always) the screen remains turned off. When you try to push the power button to wake up the screen, that starts blinking and it's not possible to hang up. The screen remains in that condition even after the end of the call. When it keeps blinking I try to hold the button down and in few seconds the screen turns black and the phone starts working again. Sometimes, instead, it starts working again by itself. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512100/+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 1512100] Re: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear
I am able to reproduce the issue by starting a (fake) call and covering/uncovering the proximity sensor for a bit (some times it can take some time but I always eventually get the problem). It seems that powerd stops handling proximity events (although the kernel receives them) at some point. Pressing the power key somehow unblocks whatever is that has been blocked, and all queued events are then processed in quick succession. I don't know yet if it's a problem with powerd or some layer below it. Investigation continues. -- 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/1512100 Title: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear Status in Canonical System Image: Confirmed Status in powerd package in Ubuntu: In Progress Status in unity-system-compositor package in Ubuntu: New Bug description: I have a problem with my Meizu MX4 (Arale r6). During a call if you remove the phone from your ear, sometimes (not always) the screen remains turned off. When you try to push the power button to wake up the screen, that starts blinking and it's not possible to hang up. The screen remains in that condition even after the end of the call. When it keeps blinking I try to hold the button down and in few seconds the screen turns black and the phone starts working again. Sometimes, instead, it starts working again by itself. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512100/+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 1512100] Re: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear
** Changed in: powerd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1512100 Title: Meizu MX4 (Arale r6=OTA7) - Blinking screen during the call if you remove the phone from your ear Status in Canonical System Image: Confirmed Status in powerd package in Ubuntu: In Progress Status in unity-system-compositor package in Ubuntu: New Bug description: I have a problem with my Meizu MX4 (Arale r6). During a call if you remove the phone from your ear, sometimes (not always) the screen remains turned off. When you try to push the power button to wake up the screen, that starts blinking and it's not possible to hang up. The screen remains in that condition even after the end of the call. When it keeps blinking I try to hold the button down and in few seconds the screen turns black and the phone starts working again. Sometimes, instead, it starts working again by itself. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512100/+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 1513792] Re: mircookie requires nettle but libmircookie-dev doesn't depend on it
** 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/1513792 Title: mircookie requires nettle but libmircookie-dev doesn't depend on it Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: I thought that bug #1513225 was fixing this but it wasn't. As long as you have Requires.private: nettle in mircookie's pcfile, libmircookie-dev package needs to Depend on it (since pkg-config will cry otherwise), like: Package 'nettle', required by 'mircookie', not found We're getting this failure in gtk+ now. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1513792/+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 1513792] Re: mircookie requires nettle but libmircookie-dev doesn't depend on it
** Changed in: mir Status: New => In Progress ** Changed in: mir Importance: Undecided => Critical ** Changed in: mir Assignee: (unassigned) => Alexandros Frantzis (afrantzis) -- 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/1513792 Title: mircookie requires nettle but libmircookie-dev doesn't depend on it Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: I thought that bug #1513225 was fixing this but it wasn't. As long as you have Requires.private: nettle in mircookie's pcfile, libmircookie-dev package needs to Depend on it (since pkg-config will cry otherwise), like: Package 'nettle', required by 'mircookie', not found We're getting this failure in gtk+ now. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1513792/+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
Added Mir to affected projects since chances are this is a Mir problem rather than a USC-specific problem. ** Also affects: unity-system-compositor Importance: Undecided Status: New ** Project changed: unity-system-compositor => mir -- 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 1511095] Re: unity-system-compositor crash, no interaction on windowed mode
The stack trace shows a crash in mi::DisplayInputRegion::bounding_rectangle() because we don't have any displays in the region. A fix for the immediate crash is at: https://code.launchpad.net/~afrantzis/mir/maybe-fix-1511095-for-0.17/ >From the supplied info I can't tell if not having any detected active displays is a valid situation or it's indeed a problem and the root cause of what we are seeing. Whatever the case we shouldn't crash like this, so this fix is a definite improvement, even if it turns out not to be a final fix. -- 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 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 1510250] Re: screen comes on without interaction
I'll try to reproduce this locally using the upcoming USC version with more logging ([1]). Hopefully the USC logs along with the powerd logs will give us some more information about what is going on. [1] https://code.launchpad.net/~afrantzis/unity-system- compositor/log/+merge/274550 ** Changed in: unity-system-compositor (Ubuntu) Assignee: (unassigned) => Alexandros Frantzis (afrantzis) -- 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/1510250 Title: screen comes on without interaction Status in Canonical System Image: Confirmed Status in powerd: New Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: Pat and I just discussing. Pat has seen this on MX4, I've seen this very consistently on Nexus7. I would say the Nexus7 screen would turn on by itself every couple of hours or so. MX4 running rc-proposed r145, phone was plugged in and charging To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510250/+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 1510250] Re: screen comes on without interaction
Also, two questions: 1. Do you remember if there are any apps running (perhaps in the background) when you see this? 2. Does the screen stay on forever after it turns on, or do they inactivity timeouts eventually turn the screen off again? -- 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/1510250 Title: screen comes on without interaction Status in Canonical System Image: Confirmed Status in powerd: New Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: Pat and I just discussing. Pat has seen this on MX4, I've seen this very consistently on Nexus7. I would say the Nexus7 screen would turn on by itself every couple of hours or so. MX4 running rc-proposed r145, phone was plugged in and charging To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510250/+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 1509005] Re: [regression] mir-client-platform-mesa-dev pkg-config file dropped
Would it be acceptable to update the xorg and mesa packages to use the new pkgconfig file name instead of changing Mir (which is what we should have done much earlier)? -- 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/1509005 Title: [regression] mir-client-platform-mesa-dev pkg-config file dropped Status in Mir: In Progress Status in mir package in Ubuntu: Triaged Bug description: the mir-client-platform-mesa-dev pkg-config file was dropped in wily, leading to build errors for such optional packages like mesa and xorg- server. Even if you have a feature freeze exception, you shouldn't break existing API's after feature freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1509005/+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 1502145] Re: Apps can keep screen lit permanently
** Changed in: unity-system-compositor (Ubuntu) Status: Confirmed => Invalid -- 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/1502145 Title: Apps can keep screen lit permanently Status in Canonical System Image: Confirmed Status in Oxide: In Progress Status in qtmir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Status in webbrowser-app package in Ubuntu: Invalid Bug description: rc-proposed, r140, krillin There are times when it seems the display blanking policy stops working and the display stays on until I press the power button. Steps to reproduce: * install and start Siete * put it in background Expected outcome: * the display is switched off after a predetermined amount of time Actual outcome: * the display stays on forever == Now that apps can request the screen to stay on, they can do so regardless of whether they're focused/visible or not. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502145/+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 1289072] Re: Nested servers lack cursor support
** 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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1289072 Title: Nested servers lack cursor support Status in Light Display Manager: Fix Released Status in Mir: Fix Released Status in unity-mir: Invalid Status in Unity System Compositor: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in mir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: Fix Released Status in unity8-desktop-session package in Ubuntu: In Progress Bug description: Nested servers lack functional cursor support. The code just returns a null pointer. One of the symptoms of this is that it is not possible to use a mouse or trackpad when running Unity8 as the desktop shell. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1289072/+subscriptions -- Mailing list: https://launchpad.net/~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 1499042] Re: [android] std::exception::what: Failed to monitor fd: Operation not permitted when unplugging external display in a nested configuration
** 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/1499042 Title: [android] std::exception::what: Failed to monitor fd: Operation not permitted when unplugging external display in a nested configuration Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Using the following nested configuration: sudo mir_demo_server --arw-file --display-config=sidebyside --input- report log --legacy-input-report log --scene-report log --debug --window-manager system-compositor --hwc-report log mir_demo_server --host-socket /tmp/mir_socket -f /tmp/nested_mir --display-config sidebyside --input-report log --legacy-input-report log --scene-report log --debug mir_demo_client_fingerpaint -m /tmp/nested_mir The nested server occasionally crashes. Excerpt of the last lines in the log: Input channel destroyed: name='Mir Fingerpaint', fd=34 [1443033760.712569] scene: surface_removed(0xb2601908 ["Mir Fingerpaint"]) - INFO surface count=2 Input channel destroyed: name='decoration', fd=38 [1443033760.712935] scene: surface_removed(0xb2602eb8 ["decoration"]) - INFO surface count=2 [1443033760.713057] scene: surface_deleted(0xb2601908 ["Mir Fingerpaint"]) - INFO surface count=1 [1443033760.721541] scene: surface_deleted(0xb2602eb8 ["decoration"]) - INFO surface count=0 ERROR: /build/mir-GYyRoo/mir-0.15.1+15.04.20150903/src/common/dispatch/multiplexing_dispatchable.cpp(263): Throw in function void mir::dispatch::MultiplexingDispatchable::add_watch(const std::shared_ptr&, mir::dispatch::DispatchReentrancy) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt12system_error std::exception::what: Failed to monitor fd: Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1499042/+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 1501927] Re: [android] various crashes when unplugging external display on a nested configuration
** 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/1501927 Title: [android] various crashes when unplugging external display on a nested configuration Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: With mir 0.16 and lp:mir start a nested server sudo mir_demo_server --arw-file --display-config sidebyside mir_demo_server --host-socket /tmp/mir_socket --display-config sidebyside Hotplug an external monitor and unplug it. You'll get crashes/aborts at various places: 1. pure virtual method call aborts 2. SEGFAULT trying to access display_buffer in mc::DefaultDisplayBufferCompositor::composite 3. SEGFAULT in mrg::RenderingTarget::~RenderingTarget() trying to access buffer 4. other but all points to accessing dead objects. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1501927/+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 1498550] Re: [android] std::exception::what: error during hwc set() when unplugging external monitor
** 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/1498550 Title: [android] std::exception::what: error during hwc set() when unplugging external monitor Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Occasionally when unplugging an external monitor an exception is thrown during hwc set(). " ERROR: Dynamic exception type: St13runtime_error std::exception::what: error during hwc set(). rc = " To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1498550/+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 1498829] Re: tests do not compile without precompiled headers
** 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/1498829 Title: tests do not compile without precompiled headers Status in Mir: Fix Released Status in mir package in Ubuntu: Triaged Bug description: With -DMIR_USE_PRECOMPILED_HEADERS=OFF $ make -j6 -k 2>&1 | grep " \*\*\* " make[2]: *** [tests/unit-tests/CMakeFiles/mir_unit_tests.dir/compositor/test_queueing_schedule.cpp.o] Error 1 make[2]: *** [tests/unit-tests/CMakeFiles/mir_unit_tests.dir/compositor/test_dropping_schedule.cpp.o] Error 1 make[2]: *** [tests/acceptance-tests/CMakeFiles/mir_acceptance_tests.dir/test_surface_specification.cpp.o] Error 1 make[2]: *** [tests/acceptance-tests/CMakeFiles/mir_acceptance_tests.dir/test_client_scaling.cpp.o] Error 1 make[2]: *** [tests/acceptance-tests/CMakeFiles/mir_acceptance_tests.dir/test_surface_morphing.cpp.o] Error 1 make[1]: *** [tests/acceptance-tests/CMakeFiles/mir_acceptance_tests.dir/all] Error 2 make[2]: *** [tests/unit-tests/CMakeFiles/mir_unit_tests.dir/client/test_connection_resource_map.cpp.o] Error 1 make[2]: *** [tests/unit-tests/CMakeFiles/mir_unit_tests.dir/input/test_input_event.cpp.o] Error 1 make[2]: *** [tests/unit-tests/CMakeFiles/mir_unit_tests.dir/input/evdev/test_evdev_device_detection.cpp.o] Error 1 make[2]: *** [tests/unit-tests/CMakeFiles/mir_unit_tests.dir/dispatch/test_readable_fd.cpp.o] Error 1 make[2]: *** [tests/unit-tests/CMakeFiles/mir_unit_tests.dir/graphics/mesa/x11/test_display.cpp.o] Error 1 make[2]: *** [tests/unit-tests/CMakeFiles/mir_unit_tests.dir/input/test_x11_platform.cpp.o] Error 1 make[2]: *** [tests/unit-tests/CMakeFiles/mir_unit_tests.dir/graphics/mesa/x11/test_platform.cpp.o] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1498829/+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 1200114] Re: [enhancement] XMir specific documentation should live in its own subsection
** 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/1200114 Title: [enhancement] XMir specific documentation should live in its own subsection Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Right now, XMir/system-compositor specific build instructions live with the build from source instructions. Mir and XMir are closely but still separate entities and this should be reflected in the documentation. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1200114/+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 1503450] Re: mesa FTBFS due to missing Requires in mirclient
** 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/1503450
Title:
mesa FTBFS due to missing Requires in mirclient
Status in Mir:
Fix Released
Status in mesa package in Ubuntu:
Fix Released
Status in mir package in Ubuntu:
New
Bug description:
mesa currently FTBFS due to a missing mirclient dependency during
build time.
Failed build at
https://launchpad.net/ubuntu/+source/mesa/11.0.2-1ubuntu2/+build/8082519
Build log:
===
/bin/bash ../../libtool --tag=CC --mode=compile gcc
-DPACKAGE_NAME=\"Mesa\" -DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"11.0.2\"
-DPACKAGE_STRING=\"Mesa\ 11.0.2\"
-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\;
-DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"11.0.2\" -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1
-DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1
-DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1
-DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1
-DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1
-DHAVE_FUNC_ATTRIBUTE_CONST=1 -DHAVE_FUNC_ATTRIBUTE_FLATTEN=1
-DHAVE_FUNC_ATTRIBUTE_FORMAT=1 -DHAVE_FUNC_ATTRIBUTE_MALLOC=1
-DHAVE_FUNC_ATTRIBUTE_PACKED=
1 -DHAVE_FUNC_ATTRIBUTE_PURE=1 -DHAVE_FUNC_ATTRIBUTE_UNUSED=1
-DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT=1 -DHAVE_DLADDR=1
-DHAVE_CLOCK_GETTIME=1 -DHAVE_PTHREAD=1 -I. -I../../../../src/egl
-D_FORTIFY_SOURCE=2 -I../../../../include -I../../../../src/egl/main
-I../../../../src/gbm/main -I../../../../src -D__STDC_LIMIT_MACROS
-D_GNU_SOURCE -DUSE_SSE41 -DNDEBUG -DTEXTURE_FLOAT_ENABLED -DUSE_X86_64_ASM
-DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF -DHAVE_MKOSTEMP
-DHAVE_DLOPEN -DHAVE_POSIX_MEMALIGN -DHAVE_LIBDRM -DGLX_USE_DRM -DHAVE_LIBUDEV
-DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DGLX_USE_TLS -DHAVE_ALIAS
-DHAVE_DRI3 -DHAVE_MINCORE -DHAVE_LLVM=0x0306 -DMESA_LLVM_VERSION_PATCH=2
-fvisibility=hidden -I/usr/include/libdrm
-D_EGL_NATIVE_PLATFORM=_EGL_PLATFORM_X11 -DHAVE_X11_PLATFORM
-DHAVE_WAYLAND_PLATFORM -DHAVE_DRM_PLATFORM -DHAVE_MIR_PLATFORM
-I/usr/include/mirplatform -I/usr/include/mircommon -I../../../../src/loader
-I../../../../src/egl/drivers/dri2 -I../../../../sr
c/gbm/backends/dri -I../../../../src/egl/wayland/wayland-egl
-I../../../../src/egl/wayland/wayland-drm -I../../src/egl/wayland/wayland-drm
-DDEFAULT_DRIVER_DIR=\"/usr/lib/x86_64-linux-gnu/dri:\${ORIGIN}/dri:/usr/lib/dri\"
-D_EGL_BUILT_IN_DRIVER_DRI2 -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall -Wall -std=c99
-Werror=implicit-function-declaration -Werror=missing-prototypes
-fno-strict-aliasing -fno-math-errno -fno-trapping-math -fno-builtin-memcmp
-MT main/eglfallbacks.lo -MD -MP -MF $depbase.Tpo -c -o main/eglfallbacks.lo
../../../../src/egl/main/eglfallbacks.c &&\
In file included from ../../../../src/egl/main/egldisplay.c:61:0:
/usr/include/mirplatform/mir_toolkit/mesa/native_display.h:22:38: fatal
error: mir_toolkit/client_types.h: No such file or directory
compilation terminated.
make[3]: *** [main/egldisplay.lo] Error 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1503450/+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 1502200] Re: Cursor becomes visible by itself when an external monitor is connected
** 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/1502200
Title:
Cursor becomes visible by itself when an external monitor is connected
Status in Mir:
Fix Released
Status in mir package in Ubuntu:
New
Bug description:
Steps to reproduce:
--
1 - Build and install the following branches on a laptop:
lp:~dandrader/unity-api/mousePointer
lp:~dandrader/qtmir/multimonitorNext
lp:~dandrader/unity8/externalMonitor
2 - In lightdm greeter, log into a unity8 session
3 - connect an external monitor
Expected outcome:
-
You see only one cursor (the one unity8 draws)
Actual outcome:
-
You see two cursors: the unity8 one and the mir one.
Comments:
--
In qtmir's mir::Server class, this is the snippet it uses to hide the
mir cursor:
"""
add_init_callback([this](){ the_cursor()->hide(); });
"""
The mir cursor remains visible also after you unplug the external
monitor.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1502200/+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 1308133] Re: Mir cursor is missing/invisible until the client sets it multiple times
** Changed in: mir (Ubuntu) Status: Fix Released => Triaged -- 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/1308133 Title: Mir cursor is missing/invisible until the client sets it multiple times Status in Mir: Fix Released Status in mir package in Ubuntu: Triaged Status in unity8-desktop-session package in Ubuntu: Triaged Bug description: Mir cursor is missing/invisible until the client sets it multiple times To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1308133/+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 1308133] Re: Mir cursor is missing/invisible until the client sets it multiple times
** Changed in: mir Status: Fix Committed => Fix Released ** Changed in: mir (Ubuntu) Status: Confirmed => Fix Released ** No longer affects: unity-system-compositor -- 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/1308133 Title: Mir cursor is missing/invisible until the client sets it multiple times Status in Mir: Fix Released Status in mir package in Ubuntu: Triaged Status in unity8-desktop-session package in Ubuntu: Triaged Bug description: Mir cursor is missing/invisible until the client sets it multiple times To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1308133/+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 1498045] Re: [android] input is not dispatched when attaching an external monitor
** 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/1498045 Title: [android] input is not dispatched when attaching an external monitor Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Touch input stops being dispatched when connecting an external monitor on android based devices. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1498045/+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 1498540] Re: [android] input coordinates are scaled incorrectly when an external display is connected
** 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/1498540 Title: [android] input coordinates are scaled incorrectly when an external display is connected Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: When starting a mir server when an external display is already connected, the dispatched touch input coordinates appear to be scaled to different size than the local screen (probably the size of the external display). Input coordinates are scaled correctly if the external display is hotplugged after starting the server. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1498540/+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 1496849] Re: Mouse cursor disappears upon entering the surface area of a nested 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/1496849 Title: Mouse cursor disappears upon entering the surface area of a nested client Status in Mir: Fix Released Status in mir package in Ubuntu: New Bug description: Seen with latest lp:mir (r2940) on an intel desktop (haven't tested on other platforms, phone etc). 1. Start a host server 2. Start a nested server 3. Start a client (e.g., egltriangle) connecting to the nested server 4. Move the cursor inside the nested client surface area 5. ==> Cursor disappears and only become visible again when the nested server shuts down To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1496849/+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 1499134] Re: Mir suddenly no longer builds since Mesa 11.0 was introduced: /usr/include/EGL/eglplatform.h:100:35: fatal error: android/native_window.h: No such file or directory
** Changed in: mir (Ubuntu) Status: Fix Released => Triaged -- 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/1499134 Title: Mir suddenly no longer builds since Mesa 11.0 was introduced: /usr/include/EGL/eglplatform.h:100:35: fatal error: android/native_window.h: No such file or directory Status in Mir: Fix Released Status in Mir 0.15 series: Won't Fix Status in Mir 0.16 series: Fix Released Status in mir package in Ubuntu: Triaged Bug description: Mir suddenly no longer builds on wily desktop: In file included from /usr/include/EGL/egl.h:39:0, from /home/dan/bzr/mir/trunk/include/platform/mir/graphics/platform.h:24, from /home/dan/bzr/mir/trunk/src/platforms/android/server/android_buffer_allocator.cpp:20: /usr/include/EGL/eglplatform.h:100:35: fatal error: android/native_window.h: No such file or directory compilation terminated. src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/build.make:77: recipe for target 'src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/android_buffer_allocator.cpp.o' failed make[2]: *** [src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/android_buffer_allocator.cpp.o] Error 1 CMakeFiles/Makefile2:2322: recipe for target 'src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/all' failed make[1]: *** [src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs Did build-deps change? To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1499134/+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 1496069] Re: [usc] Mir gives up and shuts down due to input with multimonitor qtmir (std::exception::what: Failure sending input event)
** Changed in: mir (Ubuntu) Status: Fix Released => Triaged -- 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/1496069 Title: [usc] Mir gives up and shuts down due to input with multimonitor qtmir (std::exception::what: Failure sending input event) Status in Mir: Fix Released Status in mir package in Ubuntu: Triaged Bug description: I'm implementing proper multimonitor support in QtMir in this branch: lp:~gerboland/qtmir/multimonitor/ Please build & install on device. You don't need to change unity8. The immediate goal is for unity8 to remain on the tablet screen, and have nothing (well a black screen) drawn on the external monitor. This is mostly happening, but I'm experiencing problems related to input. Steps to repro: 1. When you plug in the external monitor, nothing will appear on it (for later), but unity8 should still be interactive on the N7 - unity8 will flicker when the display config changes, due to it tearing down the old gl context and creating a new one. - unity8 is not getting any touch input events. I checked that USC is not sending it any. [1] - however the vol up/down key does cause the volume notification to appear. 2. Now unplug the external monitor. - *sometimes* unity8 works fine, gets input events again just fine and works great. - *sometimes* unity8 crashes as soon as you tap on the screen. It crashes because USC shuts down [2]! Relevant failure message: ERROR: /home/gerry/dev/projects/mir/mir-0.15/src/server/input/android/input_sender.cpp(218): Throw in function void mir::input::android::InputSender::ActiveTransfer::send(mir::input::android::InputSendEntry&&) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error std::exception::what: Failure sending input event : 9, "Bad file descriptor" Something gone screwy with input then. Perhaps QtMir needs to do something special to its input receiver when the multimonitor situation changes and its surface is destroyed & recreated?? Guidance appreciated -G [1] http://pastebin.ubuntu.com/12418660/ - is USC log with input reporting enabled. Started with 1 monitor, then was 2, then 1 again. Observe while in multimonitor case, no input events are "Published" and "Received" [2] http://pastebin.ubuntu.com/12419006/ - USC backtrace when it shuts down To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1496069/+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 1493721] Re: [regression] Fullscreen software surfaces (like Xmir -sw) can crash the Mir 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/1493721 Title: [regression] Fullscreen software surfaces (like Xmir -sw) can crash the Mir server Status in Mir: Fix Released Status in mir package in Ubuntu: Triaged Bug description: Xmir -sw (software) mode crashes the Mir server. If not immediately on startup then soon after running a few X clients... /usr/bin/mir_demo_server_minimal: (gdb) bt #0 0x7f8586f64cc0 in gbm_bo_get_user_data () from /usr/lib/x86_64-linux-gnu/libgbm.so.1 #1 0x7f85858212af in ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.4 #2 0x7f8585822099 in ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.4 #3 0x7f858ac980ac in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.33 #4 0x7f858aca1176 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.33 #5 0x7f858ad23431 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.33 #6 0x7f858a910ed0 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7f858821d6aa in start_thread (arg=0x7f8583bab700) at pthread_create.c:333 #8 0x7f858a37deed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1493721/+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 1496069] Re: [usc] Mir gives up and shuts down due to input with multimonitor qtmir (std::exception::what: Failure sending input event)
** Changed in: mir Status: Fix Committed => Fix Released ** Changed in: mir (Ubuntu) Status: New => 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/1496069 Title: [usc] Mir gives up and shuts down due to input with multimonitor qtmir (std::exception::what: Failure sending input event) Status in Mir: Fix Released Status in mir package in Ubuntu: Triaged Bug description: I'm implementing proper multimonitor support in QtMir in this branch: lp:~gerboland/qtmir/multimonitor/ Please build & install on device. You don't need to change unity8. The immediate goal is for unity8 to remain on the tablet screen, and have nothing (well a black screen) drawn on the external monitor. This is mostly happening, but I'm experiencing problems related to input. Steps to repro: 1. When you plug in the external monitor, nothing will appear on it (for later), but unity8 should still be interactive on the N7 - unity8 will flicker when the display config changes, due to it tearing down the old gl context and creating a new one. - unity8 is not getting any touch input events. I checked that USC is not sending it any. [1] - however the vol up/down key does cause the volume notification to appear. 2. Now unplug the external monitor. - *sometimes* unity8 works fine, gets input events again just fine and works great. - *sometimes* unity8 crashes as soon as you tap on the screen. It crashes because USC shuts down [2]! Relevant failure message: ERROR: /home/gerry/dev/projects/mir/mir-0.15/src/server/input/android/input_sender.cpp(218): Throw in function void mir::input::android::InputSender::ActiveTransfer::send(mir::input::android::InputSendEntry&&) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error std::exception::what: Failure sending input event : 9, "Bad file descriptor" Something gone screwy with input then. Perhaps QtMir needs to do something special to its input receiver when the multimonitor situation changes and its surface is destroyed & recreated?? Guidance appreciated -G [1] http://pastebin.ubuntu.com/12418660/ - is USC log with input reporting enabled. Started with 1 monitor, then was 2, then 1 again. Observe while in multimonitor case, no input events are "Published" and "Received" [2] http://pastebin.ubuntu.com/12419006/ - USC backtrace when it shuts down To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1496069/+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 1499134] Re: Mir suddenly no longer builds since Mesa 11.0 was introduced: /usr/include/EGL/eglplatform.h:100:35: fatal error: android/native_window.h: No such file or directory
** Changed in: mir Status: Fix Committed => Fix Released ** Changed in: mir (Ubuntu) Status: Triaged => 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/1499134 Title: Mir suddenly no longer builds since Mesa 11.0 was introduced: /usr/include/EGL/eglplatform.h:100:35: fatal error: android/native_window.h: No such file or directory Status in Mir: Fix Released Status in Mir 0.15 series: Won't Fix Status in Mir 0.16 series: Fix Released Status in mir package in Ubuntu: Triaged Bug description: Mir suddenly no longer builds on wily desktop: In file included from /usr/include/EGL/egl.h:39:0, from /home/dan/bzr/mir/trunk/include/platform/mir/graphics/platform.h:24, from /home/dan/bzr/mir/trunk/src/platforms/android/server/android_buffer_allocator.cpp:20: /usr/include/EGL/eglplatform.h:100:35: fatal error: android/native_window.h: No such file or directory compilation terminated. src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/build.make:77: recipe for target 'src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/android_buffer_allocator.cpp.o' failed make[2]: *** [src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/android_buffer_allocator.cpp.o] Error 1 CMakeFiles/Makefile2:2322: recipe for target 'src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/all' failed make[1]: *** [src/platforms/android/server/CMakeFiles/mirplatformgraphicsandroidobjects.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs Did build-deps change? To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1499134/+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 1502145] Re: Apps can keep screen lit permanently
I have found a way to deterministically reproduce the issue with webbrowser-app. Perhaps there are other scenarios that are problematic, but hopefully this will at least provide some hints. Below are the steps and between them the USC logs I get for each step, which give some insight into what is going wrong. [TL;DR] The problem seems to be that, for some reason, if after the screen is turned on and logging in the webbrowser is in focus and playing a video (which means that the user previously turned off the screen with the power button while playing a video in the browser) the webbrowser app leaks (doesn't eventually release) two keepDisplayOn requests ids. This causes the screen to stay on even when focusing away from it. [Detailed analysis] 1. Start browser, start watching a youtube video. The browser requests keepDisplayOn twice from two different dbus connections, which is strange, but OK. [1444841076.023016] usc::UnityScreenService: Received request with serial 3 from :1.300 : keepDisplayOn [1444841076.023390] usc::UnityScreenService: Sending reply for serial 3 to :1.300 id: 9 [1444841077.052913] usc::UnityScreenService: Received request with serial 3 from :1.301 : keepDisplayOn [1444841077.053164] usc::UnityScreenService: Sending reply for serial 3 to :1.301 id: 10 2. Turn off screen with power key. Everything is normal the keepDisplayOn requests are released. [1444841087.268477] usc::UnityScreenService: Received request with serial 4 from :1.300 : removeDisplayOnRequest id: 9 [1444841087.274530] usc::UnityScreenService: Received request with serial 4 from :1.301 : removeDisplayOnRequest id: 10 3. Turn on screen with power key, log in, video should resume. Strange things happen here, note the extra keepDisplayOn requests this time (4 vs 2 before, and they are all from webbrowser-app) [1444841106.885474] usc::UnityScreenService: Received request with serial 3 from :1.302 : keepDisplayOn [1444841106.885997] usc::UnityScreenService: Sending reply for serial 3 to :1.302 id: 11 [1444841106.889124] usc::UnityScreenService: Received request with serial 3 from :1.303 : keepDisplayOn [1444841106.889333] usc::UnityScreenService: Sending reply for serial 3 to :1.303 id: 12 [1444841106.895151] usc::UnityScreenService: Received request with serial 3 from :1.304 : keepDisplayOn [1444841106.895258] usc::UnityScreenService: Sending reply for serial 3 to :1.304 id: 13 [1444841106.900406] usc::UnityScreenService: Received request with serial 3 from :1.305 : keepDisplayOn [1444841106.900471] usc::UnityScreenService: Sending reply for serial 3 to :1.305 id: 14 4. Focus away from webbrowser (e.g. go to scopes). webbrowser-app requested 4 keepDisplayOn ids but releases only 2, which causes the screen to stay on. [1444841117.298103] usc::UnityScreenService: Received request with serial 4 from :1.304 : removeDisplayOnRequest id: 13 [1444841117.307436] usc::UnityScreenService: Received request with serial 4 from :1.305 : removeDisplayOnRequest id: 14 -- 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/1502145 Title: Apps can keep screen lit permanently Status in Canonical System Image: Confirmed Status in qtmir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: rc-proposed, r140, krillin There are times when it seems the display blanking policy stops working and the display stays on until I press the power button. Steps to reproduce: * install and start Siete * put it in background Expected outcome: * the display is switched off after a predetermined amount of time Actual outcome: * the display stays on forever == Now that apps can request the screen to stay on, they can do so regardless of whether they're focused/visible or not. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502145/+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 1485737] Re: Screen fades to black while typing a message (after wake-up from notification)
** Changed in: unity-system-compositor Status: Fix Committed => 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/1485737 Title: Screen fades to black while typing a message (after wake-up from notification) Status in Canonical System Image: Fix Committed Status in Unity System Compositor: Fix Released Status in unity-system-compositor package in Ubuntu: Fix Released Bug description: TEST CASE [Phone set to "Lock phone: Never".] [Phone in sleep mode.] 1. SMS message arrives, phone wakes, notification appears. 2. Swipe to unlock phone, enter passcode. 3. Navigate to messaging app, select arrived message, start typing. EXPECTED Continue to type. ACTUAL Screen goes black. This is on arale r89, I'm aware of lp:1433442 , wonder if it could be related? Strangely I'm finding that I'm not able to actuate this at sleep-delay of one minute, e.g. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1485737/+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
