[Touch-packages] [Bug 1562344] Re: Not working hotkeys for brightness in HP ProBook 640 G2
Verified. It works on HP ProBook. With 3.19 kernel at least. 3.13 kernel doesn't support the backlight of this machine. Thanks. -- 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/1562344 Title: Not working hotkeys for brightness in HP ProBook 640 G2 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: Fix Released Bug description: Description = It seems like a new HP laptops are using new vendor string which brokes hotkeys. Workaround == Just to put following lines to fix hotkeys for brithness. evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr* KEYBOARD_KEY_92=brightnessdown KEYBOARD_KEY_97=brightnessup Proposed solution === The issue was already solved by upstream systemd[1] developers 25 days ago, so resync of hwdb/60-keyboard.hwdb should be enough. [1]: commit 325de0ac23596209c252ebcc934dd5f5926fe2b6 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9.1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 26 17:20:25 2016 InstallationDate: Installed on 2016-02-25 (30 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:7053 Lite-On Technology Corp. Bus 001 Device 002: ID 0a5c:640b Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 640 G2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-34-generic root=UUID=4bccba3c-0c3c-430f-bfef-b033d9fcd45c ro cryptopts=target=root,source=/dev/disk/by-uuid/9108c404-6977-4914-afd8-40b3e8824d30 quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: HP dmi.bios.version: N76 Ver. 01.00 dmi.board.name: 80FD dmi.board.vendor: HP dmi.board.version: KBC Version 22.36 dmi.chassis.asset.tag: 5CG605253R dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN76Ver.01.00:bd12/07/2015:svnHP:pnHPProBook640G2:pvr:rvnHP:rn80FD:rvrKBCVersion22.36:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 640 G2 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1562344/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562344] Re: Not working hotkeys for brightness in HP ProBook 640 G2
Hi all. To verify this bug. Please. 1. Install Trusty (14.04). 2. Enable trusty-proposed. https://wiki.ubuntu.com/Testing/EnableProposed 3. apt-get update; apt-get upgrade. 4. apt-cache policy systemd. Make sure the version installed is 204-5ubuntu20.21 5. Reboot. 6. See if hotkey works. Thanks a lot. -- 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/1562344 Title: Not working hotkeys for brightness in HP ProBook 640 G2 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: Fix Committed Bug description: Description = It seems like a new HP laptops are using new vendor string which brokes hotkeys. Workaround == Just to put following lines to fix hotkeys for brithness. evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr* KEYBOARD_KEY_92=brightnessdown KEYBOARD_KEY_97=brightnessup Proposed solution === The issue was already solved by upstream systemd[1] developers 25 days ago, so resync of hwdb/60-keyboard.hwdb should be enough. [1]: commit 325de0ac23596209c252ebcc934dd5f5926fe2b6 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9.1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 26 17:20:25 2016 InstallationDate: Installed on 2016-02-25 (30 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:7053 Lite-On Technology Corp. Bus 001 Device 002: ID 0a5c:640b Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 640 G2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-34-generic root=UUID=4bccba3c-0c3c-430f-bfef-b033d9fcd45c ro cryptopts=target=root,source=/dev/disk/by-uuid/9108c404-6977-4914-afd8-40b3e8824d30 quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: HP dmi.bios.version: N76 Ver. 01.00 dmi.board.name: 80FD dmi.board.vendor: HP dmi.board.version: KBC Version 22.36 dmi.chassis.asset.tag: 5CG605253R dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN76Ver.01.00:bd12/07/2015:svnHP:pnHPProBook640G2:pvr:rvnHP:rn80FD:rvrKBCVersion22.36:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 640 G2 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1562344/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647283] [NEW] WiFi being detected as ethernet when race condition on renaming for persistent name
Public bug reported: Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613 Version: NetworkManager 1.4.2 This bug happens after power-on with probability about 1/50. That means we need to reboot about 50 times to get into the buggy situation. "nmcli d" shows the device type is ethernet: DEVICE TYPE STATECONNECTION wlp1s0 ethernet unavailable -- lo loopback unmanaged-- The bug starts from a race condition. But it is not the root cause. I've also attach 2 logs. One is in good situation. Another is in bad situation. This log is generated by applying a "log patch" to network-manager 1.4.2 so we can see more stuff. In the bad situation. The bug starts with race condition. But the race condition is not the root cause. The race condition is: * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared. * Inside the NM, it is still using "wlan0" in "_linktype_get_type()". * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching failed in _linktype_get_type(). * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 disappeared. * And finally, devtype and kind are both NULL, so it returns NM_LINK_TYPE_ETHERNET for wlan0. Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit the type so it is still type ethernet. But from the log, I saw _linktype_get_type() is called several times later and return the correct type (wifi). But just, "nmcli d" still shows type ethernet. I'm wondering if we are missing to update the type in the Object created after renaming and re-detecting the type. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: originate-from-1639117 somerville ** Attachment added: "Screenshot from 2016-11-30 02-08-01.png" https://bugs.launchpad.net/bugs/1647283/+attachment/4787502/+files/Screenshot%20from%202016-11-30%2002-08-01.png ** Tags added: originate-from-1639117 somerville -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1647283 Title: WiFi being detected as ethernet when race condition on renaming for persistent name Status in HWE Next: New Status in network-manager package in Ubuntu: New Bug description: Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613 Version: NetworkManager 1.4.2 This bug happens after power-on with probability about 1/50. That means we need to reboot about 50 times to get into the buggy situation. "nmcli d" shows the device type is ethernet: DEVICE TYPE STATECONNECTION wlp1s0 ethernet unavailable -- lo loopback unmanaged-- The bug starts from a race condition. But it is not the root cause. I've also attach 2 logs. One is in good situation. Another is in bad situation. This log is generated by applying a "log patch" to network-manager 1.4.2 so we can see more stuff. In the bad situation. The bug starts with race condition. But the race condition is not the root cause. The race condition is: * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared. * Inside the NM, it is still using "wlan0" in "_linktype_get_type()". * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching failed in _linktype_get_type(). * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 disappeared. * And finally, devtype and kind are both NULL, so it returns NM_LINK_TYPE_ETHERNET for wlan0. Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit the type so it is still type ethernet. But from the log, I saw _linktype_get_type() is called several times later and return the correct type (wifi). But just, "nmcli d" still shows type ethernet. I'm wondering if we are missing to update the type in the Object created after renaming and re-detecting the type. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1647283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562344] Re: Not working hotkeys for brightness in HP ProBook 640 G2
Hi Martin, This also affects 14.04 (Trusty). Can you also SRU it in Trusty? Thanks. -- 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/1562344 Title: Not working hotkeys for brightness in HP ProBook 640 G2 Status in systemd package in Ubuntu: Fix Released Bug description: Description = It seems like a new HP laptops are using new vendor string which brokes hotkeys. Workaround == Just to put following lines to fix hotkeys for brithness. evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr* KEYBOARD_KEY_92=brightnessdown KEYBOARD_KEY_97=brightnessup Proposed solution === The issue was already solved by upstream systemd[1] developers 25 days ago, so resync of hwdb/60-keyboard.hwdb should be enough. [1]: commit 325de0ac23596209c252ebcc934dd5f5926fe2b6 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9.1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 26 17:20:25 2016 InstallationDate: Installed on 2016-02-25 (30 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04ca:7053 Lite-On Technology Corp. Bus 001 Device 002: ID 0a5c:640b Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 640 G2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-34-generic root=UUID=4bccba3c-0c3c-430f-bfef-b033d9fcd45c ro cryptopts=target=root,source=/dev/disk/by-uuid/9108c404-6977-4914-afd8-40b3e8824d30 quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: HP dmi.bios.version: N76 Ver. 01.00 dmi.board.name: 80FD dmi.board.vendor: HP dmi.board.version: KBC Version 22.36 dmi.chassis.asset.tag: 5CG605253R dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN76Ver.01.00:bd12/07/2015:svnHP:pnHPProBook640G2:pvr:rvnHP:rn80FD:rvrKBCVersion22.36:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 640 G2 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1562344/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586941] Re: Randomly segfault on BYT with 4.4 kernel
We've tried upstart 1.13.2 from xenial. I download 1.13.2-0ubuntu16 from Xenial. And re-built it in Trusty chroot (also build all of the reverse dependencies). However the package doesn't provide /sbin/init. Thus we cannot use it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1586941 Title: Randomly segfault on BYT with 4.4 kernel Status in OEM Priority Project: Incomplete Status in upstart : New Status in upstart package in Ubuntu: New Bug description: We have a randomly crash bug when using 14.04 (trusty) upstart (1.12.1-0ubuntu4.2). We've tried the workarounds of LP:1447756 but it doesn't work. Also the test case doesn't crash. So we think this is a new bug. The bug is also happened on very early stages. And inside the installer, it crashes more often then the system. We see it core dumped in the installer, but not about to get the core file because the squashfs only keeps file in the memory. Also when run on system, the filesystem seems to be read-only then so there's also no logs. We are using 4.4 kernel (linux-image-4.4.0-22-generic 4.4.0-22.40~14.04.1) I'll paste some images and logs after. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1586941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378469] Re: [design] messaging-menu should be closed after sending last message
** Branch linked: lp:~paulliu/unity8/lp1378469_MessageMenu -- 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/1378469 Title: [design] messaging-menu should be closed after sending last message Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: New Bug description: if you open the messaging-menu and reply to items in there, it should be closed automatically after replying to the last item. To reproduce: - send an sms to the phone - open the messaging-menu - reply to the message Expected results: - the menu should close Actual results: - a blank messaging-menu stays open, forcing user to close it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1378469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365673] Re: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:6:qt_message_fatal:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlu
If using trunk version it doesn't crash at all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1365673 Title: /usr/lib/arm-linux- gnueabihf/qt5/bin/qmlscene:6:qt_message_fatal:QMessageLogger::fatal:UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadIntegration Status in Qt integration with the Mir display server: Confirmed Status in QT Ubuntu: Confirmed Status in “qtubuntu” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding qtdeclarative-opensource-src. This problem was most recently seen with version 5.3.0-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/4618cad07e610ca3c59a3e07c582e963d4780359 contains more details. steps to reproduce: run the lrt switch test 1. open a bunch of apps 2. swipe the screen to show the app selector 3. pick an app at random 4. swipe the screen again to show the app selector 5. pick an app at random 6. repeat steps 2-5 until crash shows in /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1365673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350891] Re: [Dash] [design] Suru Background should scroll
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Jouni Helminen (jounihelminen) -- 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/1350891 Title: [Dash] [design] Suru Background should scroll Status in Clock application for Ubuntu devices: Triaged Status in Ubuntu UX bugs: Triaged Status in “unity8” package in Ubuntu: Incomplete Status in “unity8” package in Ubuntu RTM: Incomplete Bug description: On the dash, the Suru paper folds stays fixed at the bottom, while it should rather scroll away. We should also 'tile' the background, so the paper fold is displayed again after scrolling a certain amount of vertical space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1350891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350891] Re: [Dash] [design] Suru Background should scroll
** Branch linked: lp:~paulliu/unity8/lp1350891_ScrollBackground -- 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/1350891 Title: [Dash] [design] Suru Background should scroll Status in Clock application for Ubuntu devices: Triaged Status in Ubuntu UX bugs: Triaged Status in “unity8” package in Ubuntu: Triaged Bug description: On the dash, the Suru paper folds stays fixed at the bottom, while it should rather scroll away. We should also 'tile' the background, so the paper fold is displayed again after scrolling a certain amount of vertical space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1350891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383693] Re: Demo edges is hard to drag up after bringing the indicators down
This bug seems to be only happened on RTM images right now. By running $ phablet-config edges-intro --enable we can get the bug. -- 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/1383693 Title: Demo edges is hard to drag up after bringing the indicators down Status in “unity8” package in Ubuntu: Triaged Bug description: When you are in the edges demo stage, dragging up after you have dragged down the indicators only seems to work from the right hand side of the screen, not from the left hand side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383693] Re: Demo edges is hard to drag up after bringing the indicators down
--- /tmp/EdgeDemo.qml 2014-10-24 23:19:34.249803667 +0800
+++ EdgeDemo.qml2014-08-11 20:37:50.248255000 +0800
@@ -169,7 +169,7 @@
edge: bottom,
title: i18n.tr(Close),
text: i18n.tr(Swipe up again to close the settings screen),
-anchors.fill: demo.indicators,
+anchors.fill: demo.indicators.content,
});
}
if (d.bottomEdgeDemo) {
Seems this fixes.
--
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/1383693
Title:
Demo edges is hard to drag up after bringing the indicators down
Status in “unity8” package in Ubuntu:
Triaged
Bug description:
When you are in the edges demo stage, dragging up after you have
dragged down the indicators only seems to work from the right hand
side of the screen, not from the left hand side.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383693/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383693] Re: Demo edges is hard to drag up after bringing the indicators down
** Branch linked: lp:~paulliu/unity8/lp1383693 -- 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/1383693 Title: Demo edges is hard to drag up after bringing the indicators down Status in “unity8” package in Ubuntu: In Progress Bug description: When you are in the edges demo stage, dragging up after you have dragged down the indicators only seems to work from the right hand side of the screen, not from the left hand side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383693] Re: Demo edges is hard to drag up after bringing the indicators down
** Changed in: unity8 (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383693 Title: Demo edges is hard to drag up after bringing the indicators down Status in “unity8” package in Ubuntu: In Progress Bug description: When you are in the edges demo stage, dragging up after you have dragged down the indicators only seems to work from the right hand side of the screen, not from the left hand side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379384] Re: Notifications anchored to the left instead of right on manta
** Branch linked: lp:~paulliu/unity8/lp1379384 -- 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/1379384 Title: Notifications anchored to the left instead of right on manta Status in “unity8” package in Ubuntu: Triaged Bug description: See the attached image. They should also be pushed further down to get separated from the indicators at the top. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20141008-0ubuntu1 Uname: Linux 3.4.0-6-manta armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 9 14:45:16 2014 InstallationDate: Installed on 2014-10-09 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141009-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1379384/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379384] Re: Notifications anchored to the left instead of right on manta
** Changed in: unity8 (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1379384 Title: Notifications anchored to the left instead of right on manta Status in “unity8” package in Ubuntu: In Progress Bug description: See the attached image. They should also be pushed further down to get separated from the indicators at the top. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20141008-0ubuntu1 Uname: Linux 3.4.0-6-manta armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Thu Oct 9 14:45:16 2014 InstallationDate: Installed on 2014-10-09 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141009-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1379384/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1282460] Re: Missing rating info in app preview header
** Changed in: unity8 (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1282460 Title: Missing rating info in app preview header Status in “unity-scope-click” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: In Progress Bug description: As per https://docs.google.com/a/canonical.com/file/d/0B- a_7E3tDxOgSnFXSVMzVGd6NXc/edit The app preview header should include the review metadata. Attributes still need implementing in unity8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1282460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1282460] Re: Missing rating info in app preview header
** Branch linked: lp:~paulliu/unity8/previewattribute20140918 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1282460 Title: Missing rating info in app preview header Status in “unity-scope-click” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: Triaged Bug description: As per https://docs.google.com/a/canonical.com/file/d/0B- a_7E3tDxOgSnFXSVMzVGd6NXc/edit The app preview header should include the review metadata. Attributes still need implementing in unity8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1282460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1356881] Re: Scopes previews don't support attributes
** Branch linked: lp:~paulliu/unity8/previewattribute20140918 -- 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/1356881 Title: Scopes previews don't support attributes Status in “unity8” package in Ubuntu: Triaged Bug description: Scopes previews headers widgets should have attributes support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1356881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1328513] Re: Preview header title truncated
** Changed in: unity8 (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1328513 Title: Preview header title truncated Status in The Savilerow project: New Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: In Progress Bug description: When developing a news scope. The title in the grid card fits the news headline, but in the preview (the same text) the title gets truncated. This looks very strange and makes reading news hard tbh. Shouldnt we have a common behaviour (see attached files) To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1328513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1328513] Re: Preview header title truncated
Hi. Where's the link of the spec? Currently I just remove the maxLineCount:2 in PreviewHeader. I'd like to read the spec to see what it really is. ** Branch linked: lp:~paulliu/unity8/preview_title_20140916 -- 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/1328513 Title: Preview header title truncated Status in The Savilerow project: New Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Triaged Bug description: When developing a news scope. The title in the grid card fits the news headline, but in the preview (the same text) the title gets truncated. This looks very strange and makes reading news hard tbh. Shouldnt we have a common behaviour (see attached files) To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1328513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1328513] Re: Preview header title truncated
I tried to chat with Jmulholland yesterday. Trying to figure out what Mike means. I got this link https://drive.google.com/a/canonical.com/folderview?id=0B8T-xKCA6bikX3M1NllLdjhZYkUusp=drive_web But also didn't find anything useful there. -- 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/1328513 Title: Preview header title truncated Status in The Savilerow project: New Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Triaged Bug description: When developing a news scope. The title in the grid card fits the news headline, but in the preview (the same text) the title gets truncated. This looks very strange and makes reading news hard tbh. Shouldnt we have a common behaviour (see attached files) To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1328513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358197] Re: Power off dialog box no longer shows restart
** Branch linked: lp:~paulliu/unity8/readd_restart_20140915 -- 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/1358197 Title: Power off dialog box no longer shows restart Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Triaged Bug description: In the last promoted image, r179, the power off dialog displays three options: * Power off * Restart * Cancel In r197, the power off dialog no longer allows the user to restart the phone. Restart should be added back to the power off dialog box. Note: Not sure why this change was made, it was not a design request --- Desired resolution: - revert this change to add the restart option back to the power off dialogue - Note that when the phone is more stable we will eventually want to remove this option, however for now it should stay. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1358197/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
