[Touch-packages] [Bug 1536617] Re: Welcome Wizard Wifi Page doesn't display Continue button

[Michał Sawicz]

** Changed in: canonical-devices-system-image
   Status: Confirmed => Triaged

** Changed in: avila
   Status: Confirmed => In Progress

** Changed in: canonical-devices-system-image
   Status: Triaged => In Progress

** Changed in: avila
 Assignee: (unassigned) => Michał Sawicz (saviq)

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => High

-- 
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/1536617

Title:
  Welcome Wizard Wifi Page doesn't display Continue button

Status in The Avila project:
  In Progress
Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  1. Flash frieza
  2. Select a Language
  3. Select a pin
  4. On Wifi page select your ap
  5. Add password

  EXPECTED:
  I expect the skip button to change to a Continue Button

  ACTUAL:
  The Skip button remain even after password is added sucessfully

  NOTE:
  This maybe related to the test device and not apparent on real devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1536617/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543132] Re: unity::scopes::internal::OnlineAccountClientImpl::flush_pending_session gets stuck and freezes UI

[Albert Astals Cid]

*** This bug is a duplicate of bug 1544063 ***
https://bugs.launchpad.net/bugs/1544063

** This bug has been marked a duplicate of bug 1544063
   UI freezes when trying to log in from youtube scope

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1543132

Title:
  unity::scopes::internal::OnlineAccountClientImpl::flush_pending_session
  gets stuck and freezes UI

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  Today's image

  I have a google account setup in system settings and i have enabled
  youtube in settings

  When i go to the youtube scope i still see the "Log-in to youtube"
  button (which idellay i should not see, but that's not the problem)

  When i click the button the ui freezes forever

  Backtrace is http://paste.ubuntu.com/14993287/

  My totally uninformed guess is that Thread 3 is stuck for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1543132/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543883] Re: screen blanked during systemd-logind upgrade

[Martin Pitt]

*** This bug is a duplicate of bug 1473800 ***
https://bugs.launchpad.net/bugs/1473800

Duplicate of bug 1473800 which was fixed in wily.

** This bug has been marked a duplicate of bug 1473800
   restarting logind during systemd update causes screen to lock

-- 
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/1543883

Title:
  screen blanked during systemd-logind upgrade

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded my trusty system and the X11 / unity7 screen turned
  black for ~200ms twice during the upgrade; it appeared roughly when
  the systemd-logind services were stopped and started in this log.
  Music playing via youtube in firefox kept playing without issue and
  the X11 session otherwise seemed unaffected but it certainly was
  jarring.

  Thanks

  The following packages will be upgraded:
flashplugin-installer gir1.2-gudev-1.0 libgudev-1.0-0 libpam-systemd
libsystemd-daemon0 libsystemd-journal0 libsystemd-login0 libudev1
libudev1:i386 systemd-services udev
  11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,138 kB of archives.
  After this operation, 1,024 B of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Get:1 http://mirrors.kernel.org/ubuntu/ trusty-updates/main udev amd64 
204-5ubuntu20.18 [734 kB]
  Get:2 http://security.ubuntu.com/ubuntu/ trusty-security/multiverse 
flashplugin-installer amd64 11.2.202.569ubuntu0.14.04.1 [6,852 B]
  Get:3 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libudev1 i386 
204-5ubuntu20.18 [34.4 kB]
  Get:4 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libudev1 amd64 
204-5ubuntu20.18 [33.5 kB]
  Get:5 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libpam-systemd 
amd64 204-5ubuntu20.18 [25.5 kB]
  Get:6 http://mirrors.kernel.org/ubuntu/ trusty-updates/main systemd-services 
amd64 204-5ubuntu20.18 [197 kB]
  Get:7 http://mirrors.kernel.org/ubuntu/ trusty-updates/main 
libsystemd-daemon0 amd64 204-5ubuntu20.18 [10.0 kB]
  Get:8 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libsystemd-login0 
amd64 204-5ubuntu20.18 [27.0 kB]
  Get:9 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libgudev-1.0-0 
amd64 1:204-5ubuntu20.18 [14.1 kB]
  Get:10 http://mirrors.kernel.org/ubuntu/ trusty-updates/main 
libsystemd-journal0 amd64 204-5ubuntu20.18 [49.9 kB]
  Get:11 http://mirrors.kernel.org/ubuntu/ trusty-updates/main gir1.2-gudev-1.0 
amd64 1:204-5ubuntu20.18 [5,496 B]
  Fetched 1,138 kB in 0s (1,162 kB/s)   
  Preconfiguring packages ...
  (Reading database ... 307737 files and directories currently installed.)
  Preparing to unpack .../udev_204-5ubuntu20.18_amd64.deb ...
  Adding 'diversion of /bin/udevadm to /bin/udevadm.upgrade by fake-udev'
  Unpacking udev (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../libudev1_204-5ubuntu20.18_i386.deb ...
  De-configuring libudev1:amd64 (204-5ubuntu20.15) ...
  Unpacking libudev1:i386 (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../libudev1_204-5ubuntu20.18_amd64.deb ...
  Unpacking libudev1:amd64 (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../libpam-systemd_204-5ubuntu20.18_amd64.deb ...
  systemd-logind stop/waiting
  Unpacking libpam-systemd:amd64 (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../systemd-services_204-5ubuntu20.18_amd64.deb ...
  Unpacking systemd-services (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../libsystemd-daemon0_204-5ubuntu20.18_amd64.deb ...
  Unpacking libsystemd-daemon0:amd64 (204-5ubuntu20.18) over (204-5ubuntu20.15) 
...
  Preparing to unpack .../libsystemd-login0_204-5ubuntu20.18_amd64.deb ...
  Unpacking libsystemd-login0:amd64 (204-5ubuntu20.18) over (204-5ubuntu20.15) 
...
  Preparing to unpack .../libgudev-1.0-0_1%3a204-5ubuntu20.18_amd64.deb ...
  Unpacking libgudev-1.0-0:amd64 (1:204-5ubuntu20.18) over (1:204-5ubuntu20.15) 
...
  Preparing to unpack .../libsystemd-journal0_204-5ubuntu20.18_amd64.deb ...
  Unpacking libsystemd-journal0:amd64 (204-5ubuntu20.18) over 
(204-5ubuntu20.15) ...
  Preparing to unpack 
.../flashplugin-installer_11.2.202.569ubuntu0.14.04.1_amd64.deb ...
  Unpacking flashplugin-installer (11.2.202.569ubuntu0.14.04.1) over 
(11.2.202.559ubuntu0.14.04.1) ...
  Preparing to unpack .../gir1.2-gudev-1.0_1%3a204-5ubuntu20.18_amd64.deb ...
  Unpacking gir1.2-gudev-1.0 (1:204-5ubuntu20.18) over (1:204-5ubuntu20.15) ...
  Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
  Processing triggers for ureadahead (0.100.0-16) ...
  Processing triggers for update-notifier-common (0.154.1ubuntu1) ...
  flashplugin-installer: downloading 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20160209.1.orig.tar.gz
  Installing from local file /tmp/tmpmN_J4k.gz
  

[Touch-packages] [Bug 1473800] Re: restarting logind during systemd update causes screen to lock

[Martin Pitt]

Adding trusty task, as trusty is apparently also affected (see duplicate
bug 1543883).

** Changed in: systemd (Ubuntu Trusty)
   Status: Confirmed => Triaged

-- 
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/1473800

Title:
  restarting logind during systemd update causes screen to lock

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Triaged

Bug description:
  When systemd is updated (through the update manager), the
  screen/session locks when processing the update.

  I've had this happen twice I think, and the only suspicious packages
  are the systemd ones.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 222-1ubuntu3
  ProcVersionSignature: Ubuntu 4.0.0-4.6-generic 4.0.7
  Uname: Linux 4.0.0-4-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 13 09:49:47 2015
  InstallationDate: Installed on 2015-01-31 (162 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-4-generic 
root=UUID=4c827ac5-3a87-4443-86eb-a55dca9626ad ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.30
  dmi.board.name: FM2A88X Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/31/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88XExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1473800/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1542696] Re: 16.04 LTS Xenial Xerus does not reboot properly

[Martin Pitt]

"please remove installation media and press ENTER" is only shown after
installation. I take it you did install Ubuntu and are now (re)booting
that, not the live system on the installation medium?

Please follow /usr/share/doc/systemd/README.Debian.gz "Debugging
boot/shutdown problems", and check "systemctl list-jobs" which unit is
hanging during shutdown. Please also capture the journal output, with
"journalctl > /root/journal.txt" and attach /root/journal.txt here.

Thanks!

** Changed in: systemd (Ubuntu)
   Status: New => Incomplete

-- 
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/1542696

Title:
  16.04 LTS Xenial Xerus does not reboot properly

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04
  Codename: xenial

  Installed it today and fully updated but it always gets stuck on
  reboot, even after installation finished and I got to the part "please
  remove installation media and press ENTER" it didnt work, I had to
  turn off my laptop, every reboot gets stuck, I get a splash like it is
  rebooting but it just stays like that, when I press a key to see
  console output it says something like "starting reboot", when I switch
  to a virtual console in an attempt to try a manual reboot, I cant even
  login, prompt for login is not responding to typing, nothing shows
  there.

  last -5 reboot shutdown root
  reboot   system boot  4.4.0-2-generic  Sat Feb  6 19:23   still running
  reboot   system boot  4.4.0-2-generic  Sat Feb  6 17:59   still running
  reboot   system boot  4.4.0-2-generic  Sat Feb  6 17:46 - 17:57  (00:11)

  wtmp begins Sat Feb  6 17:46:02 2016

  How can I debug this further? Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 228-5ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb  6 19:37:05 2016
  InstallationDate: Installed on 2016-02-06 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  MachineType: ASUSTeK Computer Inc. N61Da
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=54d21952-4601-4641-b958-9a7ac2b9acb1 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N61Da.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N61Da
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN61Da.208:bd08/23/2010:svnASUSTeKComputerInc.:pnN61Da:pvr1.0:rvnASUSTeKComputerInc.:rnN61Da:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: N61Da
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1542696/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 439527] Re: grep crashed with SIGSEGV in __libc_start_main()

[Matthias Klose]

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/439527

Title:
  grep crashed with SIGSEGV in __libc_start_main()

Status in grep package in Ubuntu:
  New

Bug description:
  Binary package hint: grep

  ubuntu 9.10

  ProblemType: Crash
  Architecture: i386
  Date: Wed Sep 30 20:19:59 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /bin/grep
  Package: grep 2.5.4-4
  ProcCmdline: grep Browsing
  ProcEnviron:
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
  SegvAnalysis:
   Segfault happened at: 0x8054840: add%al,(%eax)
   PC (0x08054840) ok
   source "%al" ok
   destination "(%eax)" (0x0011) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: grep
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
   ?? ()
  Title: grep crashed with SIGSEGV in __libc_start_main()
  Uname: Linux 2.6.31-11-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/439527/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536714] Re: Fix the user login experience on the greeter on a tablet

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 - 8.11+16.04.20160208-0ubuntu1

---
unity8 (8.11+16.04.20160208-0ubuntu1) xenial; urgency=medium

  [ Albert Astals Cid ]
  * LVWPH: Reset to initial values when list is empty (LP: #1540490)
  * Make LazyImage qmltest less flaky on CI

  [ Andrea Cimitan ]
  * Make LazyImage qmltest less flaky on CI

  [ CI Train Bot ]
  * Resync trunk.
  * Update translation template

  [ Michael Terry ]
  * Display the current user's real name on the tablet lockscreen. (LP:
#1536714)

 -- Michał Sawicz   Mon, 08 Feb 2016
09:38:00 +

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1536714

Title:
  Fix the user login experience on the greeter on a tablet

Status in The Avila project:
  Fix Committed
Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu RTM:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  In Progress

Bug description:
  The current UX for tablets or when converged with a mouse attached is
  a bit of a placeholder showing the default phablet user.

  We need to support two modes of the greeter that scales according to
  the available input devices. The first one is one that works across
  mobile and tablet devices in non-mouse connected / touch-centric
  state. Unlocking with no mouse connected would be exactly as it is
  today on the phone, which displays the Infographic until you touch the
  screen, and then you get a message that says "swipe to unlock" If you
  don't have a pin code set, the screen unlocks. if you have a pincode
  set, the touch pincode-entry pad appears.

  If a mouse is connected, however, you get the more "desktop-friendly"
  greeter with the infographic, user-name and password entry field (just
  like what we have today) on tablet.  If the user taps or clicks into
  the password edit box, the OSK is popped up (unless an external
  keyboard is also attached). If no password or pincode has been set,
  then instead of the password entry field, you would instead have a
  "login" button that clears the greeter.

  On a tablet with mouse connected and no pincode set, the user could
  either swipe away the greeter or tap on the login button. If the user
  has a password/pincode set and attempts to swipe away the greeter, we
  should put up a hint message asking the user to enter their
  password/pincode to continue.

  This incremental enhancement to recognize the mouse is more consistent
  with convergence because tablets are mobile devices, and if no mouse
  is attached, we should follow a touch-centric approach. In a mouse-
  connected state, we can assume the user will be favoring that device.

  ===

  Immediate problem: "phablet" name on the greeter login list. A bigger
  refactoring of the greeter for bigger screens will follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1536714/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1541125] Re: Clicking a date in the new calendar doesn't change the indicator's appointment list

[Lukáš Tinkl]

** Changed in: unity8 (Ubuntu)
   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/1541125

Title:
  Clicking a date in the new calendar doesn't change the indicator's
  appointment list

Status in Ubuntu UX:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Now that we've got a calendar in indicator-datetime in Unity 8, there
  are a few features from Unity 7 that we should decide if/how we're
  goint to handle in Unity 8.

  * Show Week Numbers
  * Highlight days of the month that include appointments
  * Unity tells indicator-datetime what calendar day has been clicked so that 
the "upcoming appointments" list can be adjusted accordingly

  These are currently implemented as fields in a GAction state
  dictionary and documented in http://bazaar.launchpad.net/~indicator-
  applet-developers/indicator-datetime/trunk.15.10/view/head:/README ...
  however that was all done for Unity 7, and IMO it would make sense to
  improve the unity<->indicator API here so that Unity8 doesn't have to
  deal with key-variant map GAction states.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1541125/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1540449] Re: add sync option to AdaptivePageLayout

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1540449

Title:
  add sync option to AdaptivePageLayout

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  currently there is no way to load a page syncronously when using
  AdaptivePageLayout. This option should be made available in the api
  for the following reasons:

  1) there is a performance issue with async loading of pages (see bug 
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1510201)
  2) developers might have a preference for whatever reason to do the load 
synchronously

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540449/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543883] Re: screen blanked during systemd-logind upgrade

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

-- 
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/1543883

Title:
  screen blanked during systemd-logind upgrade

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded my trusty system and the X11 / unity7 screen turned
  black for ~200ms twice during the upgrade; it appeared roughly when
  the systemd-logind services were stopped and started in this log.
  Music playing via youtube in firefox kept playing without issue and
  the X11 session otherwise seemed unaffected but it certainly was
  jarring.

  Thanks

  The following packages will be upgraded:
flashplugin-installer gir1.2-gudev-1.0 libgudev-1.0-0 libpam-systemd
libsystemd-daemon0 libsystemd-journal0 libsystemd-login0 libudev1
libudev1:i386 systemd-services udev
  11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,138 kB of archives.
  After this operation, 1,024 B of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Get:1 http://mirrors.kernel.org/ubuntu/ trusty-updates/main udev amd64 
204-5ubuntu20.18 [734 kB]
  Get:2 http://security.ubuntu.com/ubuntu/ trusty-security/multiverse 
flashplugin-installer amd64 11.2.202.569ubuntu0.14.04.1 [6,852 B]
  Get:3 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libudev1 i386 
204-5ubuntu20.18 [34.4 kB]
  Get:4 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libudev1 amd64 
204-5ubuntu20.18 [33.5 kB]
  Get:5 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libpam-systemd 
amd64 204-5ubuntu20.18 [25.5 kB]
  Get:6 http://mirrors.kernel.org/ubuntu/ trusty-updates/main systemd-services 
amd64 204-5ubuntu20.18 [197 kB]
  Get:7 http://mirrors.kernel.org/ubuntu/ trusty-updates/main 
libsystemd-daemon0 amd64 204-5ubuntu20.18 [10.0 kB]
  Get:8 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libsystemd-login0 
amd64 204-5ubuntu20.18 [27.0 kB]
  Get:9 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libgudev-1.0-0 
amd64 1:204-5ubuntu20.18 [14.1 kB]
  Get:10 http://mirrors.kernel.org/ubuntu/ trusty-updates/main 
libsystemd-journal0 amd64 204-5ubuntu20.18 [49.9 kB]
  Get:11 http://mirrors.kernel.org/ubuntu/ trusty-updates/main gir1.2-gudev-1.0 
amd64 1:204-5ubuntu20.18 [5,496 B]
  Fetched 1,138 kB in 0s (1,162 kB/s)   
  Preconfiguring packages ...
  (Reading database ... 307737 files and directories currently installed.)
  Preparing to unpack .../udev_204-5ubuntu20.18_amd64.deb ...
  Adding 'diversion of /bin/udevadm to /bin/udevadm.upgrade by fake-udev'
  Unpacking udev (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../libudev1_204-5ubuntu20.18_i386.deb ...
  De-configuring libudev1:amd64 (204-5ubuntu20.15) ...
  Unpacking libudev1:i386 (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../libudev1_204-5ubuntu20.18_amd64.deb ...
  Unpacking libudev1:amd64 (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../libpam-systemd_204-5ubuntu20.18_amd64.deb ...
  systemd-logind stop/waiting
  Unpacking libpam-systemd:amd64 (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../systemd-services_204-5ubuntu20.18_amd64.deb ...
  Unpacking systemd-services (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../libsystemd-daemon0_204-5ubuntu20.18_amd64.deb ...
  Unpacking libsystemd-daemon0:amd64 (204-5ubuntu20.18) over (204-5ubuntu20.15) 
...
  Preparing to unpack .../libsystemd-login0_204-5ubuntu20.18_amd64.deb ...
  Unpacking libsystemd-login0:amd64 (204-5ubuntu20.18) over (204-5ubuntu20.15) 
...
  Preparing to unpack .../libgudev-1.0-0_1%3a204-5ubuntu20.18_amd64.deb ...
  Unpacking libgudev-1.0-0:amd64 (1:204-5ubuntu20.18) over (1:204-5ubuntu20.15) 
...
  Preparing to unpack .../libsystemd-journal0_204-5ubuntu20.18_amd64.deb ...
  Unpacking libsystemd-journal0:amd64 (204-5ubuntu20.18) over 
(204-5ubuntu20.15) ...
  Preparing to unpack 
.../flashplugin-installer_11.2.202.569ubuntu0.14.04.1_amd64.deb ...
  Unpacking flashplugin-installer (11.2.202.569ubuntu0.14.04.1) over 
(11.2.202.559ubuntu0.14.04.1) ...
  Preparing to unpack .../gir1.2-gudev-1.0_1%3a204-5ubuntu20.18_amd64.deb ...
  Unpacking gir1.2-gudev-1.0 (1:204-5ubuntu20.18) over (1:204-5ubuntu20.15) ...
  Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
  Processing triggers for ureadahead (0.100.0-16) ...
  Processing triggers for update-notifier-common (0.154.1ubuntu1) ...
  flashplugin-installer: downloading 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20160209.1.orig.tar.gz
  Installing from local file /tmp/tmpmN_J4k.gz
  Flash Plugin installed.
  Setting up libudev1:amd64 (204-5ubuntu20.18) ...
  Setting up libudev1:i386 (204-5ubuntu20.18) ...
  

[Touch-packages] [Bug 1542693] Re: Font used in the news scope is hard to read

[Kyle Nitzsche]

Hi Rüdiger.

Currently scopes cannot control the fonts used. So I have added Unity8
and Ubuntu Design tasks to this bug.

Thanks for filing the bug!

** Also affects: unity8 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Changed in: news-scope
   Status: New => 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/1542693

Title:
  Font used in the news scope is hard to read

Status in News Scope:
  Triaged
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  The news scope uses a fixed font. On the MX4, the font appears so small that 
it will be hardly readable by some (especially older) people. The font color is 
locked to medium gray on a light gray background, which looks sleek, but is a 
very bad choice for text. Text, notably in an application meant to convey 
information, should use high contrast. Moreover, the font is sans serif. Larger 
portions of text, notably newspaper articles, should use serif font ("Times" 
being the standard example,its name deriving from the name of the newspaper).
  Please choose a better font (type, size and color) for the news scope. 
Alternatively, make it configurable by the user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/news-scope/+bug/1542693/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1473800] Re: restarting logind during systemd update causes screen to lock

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: systemd (Ubuntu Trusty)
   Status: New => Confirmed

-- 
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/1473800

Title:
  restarting logind during systemd update causes screen to lock

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Triaged

Bug description:
  When systemd is updated (through the update manager), the
  screen/session locks when processing the update.

  I've had this happen twice I think, and the only suspicious packages
  are the systemd ones.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 222-1ubuntu3
  ProcVersionSignature: Ubuntu 4.0.0-4.6-generic 4.0.7
  Uname: Linux 4.0.0-4-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 13 09:49:47 2015
  InstallationDate: Installed on 2015-01-31 (162 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-4-generic 
root=UUID=4c827ac5-3a87-4443-86eb-a55dca9626ad ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.30
  dmi.board.name: FM2A88X Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/31/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88XExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1473800/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1544108] Re: grep's test long-pattern-perf fails on powerpc when built with optimization

[Matthias Klose]

at least -Og, -O[123] triggers the issue

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1544108

Title:
  grep's test long-pattern-perf fails on powerpc when built with
  optimization

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  grep's test long-pattern-perf fails on powerpc when built with
  optimization

  see
  https://launchpad.net/ubuntu/+source/grep/2.22-1/+build/8281007

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1544108/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1446828] Re: gdb pretty printers do not auto-load on Trusty

[Launchpad Bug Tracker]

This bug was fixed in the package gcc-4.8 - 4.8.4-2ubuntu1~14.04.1

---
gcc-4.8 (4.8.4-2ubuntu1~14.04.1) trusty-proposed; urgency=medium

  * SRU:
  * Fix auto-loading of gdb pretty printers. LP: #1446828.
  * Fix PR libstdc++/56158, taken from the trunk.
Addresses: #804521. LP: #1514309.
  * Backport PR target/64579 and PR target/67281 from the trunk (HTM fixes).
LP: #1517093.

 -- Matthias Klose   Wed, 18 Nov 2015 17:48:36 +0100

** Changed in: gcc-4.8 (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1446828

Title:
  gdb pretty printers do not auto-load on Trusty

Status in gcc-4.8 package in Ubuntu:
  Fix Released
Status in gcc-4.8 source package in Trusty:
  Fix Released

Bug description:
  On Ubuntu 14.04.2 (Trusty), the file in libstdc++6-4.8-dbg to auto-
  load the pretty printers doesn't resolve the right path to the
  printers. To reproduce, on a fresh install:

  $ cat test.cpp
  #include 
  int main() {
std::vector v;
v.push_back(1);
return 0;
  }
  $ g++ test.cpp -g
  $ gdb a.out -ex start
  Reading symbols from a.out...done.
  Temporary breakpoint 1 at 0x400956: file test.cpp, line 3.
  Starting program: /home/emaisin/a.out 
  Traceback (most recent call last):
File "/usr/lib/debug/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", 
line 63, in 
  from libstdcxx.v6.printers import register_libstdcxx_printers
  ImportError: No module named 'libstdcxx'

  Temporary breakpoint 1, main () at test.cpp:3
  3   std::vector v;
  (gdb) 

  It seems like the fixup for multiarch actually adds an extra "..":

  if not os.path.basename(os.path.dirname(__file__)).startswith('lib'):
  backdirs += 1 # multiarch subdir

  Removing these two lines almost makes it work:

  $ gdb a.out -ex start
  Reading symbols from a.out...done.
  Temporary breakpoint 1 at 0x400956: file test.cpp, line 3.
  Starting program: /home/emaisin/a.out 
  Traceback (most recent call last):
File "/usr/lib/debug/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", 
line 63, in 
  from libstdcxx.v6.printers import register_libstdcxx_printers
File 
"/usr/lib/x86_64-linux-gnu/../../share/gcc-4.8/python/libstdcxx/v6/printers.py",
 line 54
  raise ValueError, "Cannot find type %s::%s" % (str(orig), name)
  ^
  SyntaxError: invalid syntax

  Temporary breakpoint 1, main () at test.cpp:3
  3   std::vector v;

  
  That last problem is tracked in bug #1256419, which is still a pending issue 
in Trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1446828/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1517093] Re: HTM builtins aren't treated as compiler barriers on powerpc

[Launchpad Bug Tracker]

This bug was fixed in the package gcc-4.8 - 4.8.4-2ubuntu1~14.04.1

---
gcc-4.8 (4.8.4-2ubuntu1~14.04.1) trusty-proposed; urgency=medium

  * SRU:
  * Fix auto-loading of gdb pretty printers. LP: #1446828.
  * Fix PR libstdc++/56158, taken from the trunk.
Addresses: #804521. LP: #1514309.
  * Backport PR target/64579 and PR target/67281 from the trunk (HTM fixes).
LP: #1517093.

 -- Matthias Klose   Wed, 18 Nov 2015 17:48:36 +0100

** Changed in: gcc-4.8 (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1517093

Title:
  HTM builtins aren't treated as compiler barriers on powerpc

Status in gcc-4.8 package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-4.8 source package in Trusty:
  Fix Released

Bug description:
  ---Problem Description---
  HTM builtins aren't treated as compiler barriers on powerpc

  Contact Information = berg...@us.ibm.com

  ---Steps to Reproduce---

   This bug is a mirror of the (fixed) upstream FSF bugzilla 
https://gcc.gnu.org/PR67281
  All relevant information regarding the bug and the fix can be found there.  
This bugzilla is to track backporting of the fix to the GCC 4.8, 4.9 and 5 
based compilers.

  Userspace tool common name: GCC
  Userspace rpm: gcc-4.8, gcc-4.9 and gcc-5

  == Comment: #1
  The fix for the FSF GCC 5 branch was committed with:

  r228846 | bergner | 2015-10-15 11:38:47 -0500 (Thu, 15 Oct 2015) | 16
  lines

  Backport from mainline
  2015-10-14  Peter Bergner  
  Torvald Riegel  

  PR target/67281
  * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
  (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
  *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): New define_expands.
  * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
  __TM_FENCE__ for htm.
  * doc/extend.texi: Update documentation for htm builtins.

  == Comment: #2
  The fix for the FSF GCC 4.9 branch was committed with:

  r228847 | bergner | 2015-10-15 11:40:14 -0500 (Thu, 15 Oct 2015) | 16
  lines

  Backport from mainline
  2015-10-14  Peter Bergner  
  Torvald Riegel  

  PR target/67281
  * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
  (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
  *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): New define_expands.
  * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
  __TM_FENCE__ for htm.
  * doc/extend.texi: Update documentation for htm builtins.

  == Comment: #3
  Since the FSF 4.8 branch is closed, here is a backport of the fix along with 
another
  simple HTM wrong code bug to GCC 4.8.

  Backport from mainline
  2015-10-14  Peter Bergner  
  Torvald Riegel  

  PR target/67281
  * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
  (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
  *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): New define_expands.
  * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
  __TM_FENCE__ for htm.
  * doc/extend.texi: Update documentation for htm builtins.

  Backport from mainline:
  2015-08-03  Peter Bergner  

  * config/rs6000/htm.md (tabort.): Restrict the source operand to
  using a base register.

  Acceptance creterium: No regressions in the testsuite, and the new
  test passes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1517093/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1514309] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gcc-4.8 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1514309

Title:
  Undefined Behavior in GCC 4.8 ios_base.h

Status in gcc:
  Unknown
Status in gcc-4.8 package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-4.8 source package in Trusty:
  Fix Released
Status in gcc-5 package in Debian:
  Fix Released

Bug description:
  On Linux, the distros often use libstdc++ rather than libc++ for
  Clang. Building libcxx is an art that I have never been able to
  untangle, and I think the maintainers have discovered the same.

  Below, I'm catching a UB finding when using Clang and libstdc++. This
  one has been around for some time. I first encountered it on Apple
  platforms. I regularly encounter it on Debian and Ubuntu.

  The fix is fairly easy, and I usually just do it: a couple of casts
  among unsigned and the flags. Also see http://lists.llvm.org/pipermail
  /cfe-dev/2015-January/040753.html.

  **

  $ cat ub.cxx
  #include 

  int main(int argc, char* argv[])
  {
std::cout << std::hex << argc << std::endl;
std::cout << std::dec << argc << std::endl;
return 0;
  }

  $ clang++ -fsanitize=undefined ub.cxx -o ub.exe

  $ ./ub.exe
  
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/bits/ios_base.h:96:24:
 runtime error: load of value 4294967221, which is not a valid value for type 
'std::_Ios_Fmtflags'
  
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/bits/ios_base.h:76:67:
 runtime error: load of value 4294967221, which is not a valid value for type 
'std::_Ios_Fmtflags'
  1
  1

  **

  $ g++ --version
  g++ (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4

  $ uname -a
  Linux ubuntu 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release
  No LSB modules are available.

  **

  $ apt-cache show g++
  Package: g++
  Priority: optional
  Section: devel
  Installed-Size: 34
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian GCC Maintainers 
  Architecture: amd64
  Source: gcc-defaults (1.124ubuntu6)
  Version: 4:4.8.2-1ubuntu6
  Provides: c++-compiler
  Depends: cpp (>= 4:4.8.2-1ubuntu6), gcc (>= 4:4.8.2-1ubuntu6), g++-4.8 (>= 
4.8.2-5~), gcc-4.8 (>= 4.8.2-5~)
  Suggests: g++-multilib
  Filename: pool/main/g/gcc-defaults/g++_4.8.2-1ubuntu6_amd64.deb
  Size: 1490
  MD5sum: 7332a4e9116b821e167a3d0236ca413a
  SHA1: 2c7201808be1029d21b7691c5a855535a4fcbd51
  SHA256: 02c3d204efe6c34bf3de655aaf6a9ce524511977aedf92d7bce7093d0581f977
  Description-en: GNU C++ compiler
   This is the GNU C++ compiler, a fairly portable optimizing compiler for C++.
   .
   This is a dependency package providing the default GNU C++ compiler.
  Description-md5: 4d44b18774ae5123b7c3f70d940cf655
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Build-Essential: yes
  Origin: Ubuntu
  Supported: 5y

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1514309/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1514309] Re: Undefined Behavior in GCC 4.8 ios_base.h

[Launchpad Bug Tracker]

This bug was fixed in the package gcc-4.8 - 4.8.4-2ubuntu1~14.04.1

---
gcc-4.8 (4.8.4-2ubuntu1~14.04.1) trusty-proposed; urgency=medium

  * SRU:
  * Fix auto-loading of gdb pretty printers. LP: #1446828.
  * Fix PR libstdc++/56158, taken from the trunk.
Addresses: #804521. LP: #1514309.
  * Backport PR target/64579 and PR target/67281 from the trunk (HTM fixes).
LP: #1517093.

 -- Matthias Klose   Wed, 18 Nov 2015 17:48:36 +0100

** Changed in: gcc-4.8 (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1514309

Title:
  Undefined Behavior in GCC 4.8 ios_base.h

Status in gcc:
  Unknown
Status in gcc-4.8 package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-4.8 source package in Trusty:
  Fix Released
Status in gcc-5 package in Debian:
  Fix Released

Bug description:
  On Linux, the distros often use libstdc++ rather than libc++ for
  Clang. Building libcxx is an art that I have never been able to
  untangle, and I think the maintainers have discovered the same.

  Below, I'm catching a UB finding when using Clang and libstdc++. This
  one has been around for some time. I first encountered it on Apple
  platforms. I regularly encounter it on Debian and Ubuntu.

  The fix is fairly easy, and I usually just do it: a couple of casts
  among unsigned and the flags. Also see http://lists.llvm.org/pipermail
  /cfe-dev/2015-January/040753.html.

  **

  $ cat ub.cxx
  #include 

  int main(int argc, char* argv[])
  {
std::cout << std::hex << argc << std::endl;
std::cout << std::dec << argc << std::endl;
return 0;
  }

  $ clang++ -fsanitize=undefined ub.cxx -o ub.exe

  $ ./ub.exe
  
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/bits/ios_base.h:96:24:
 runtime error: load of value 4294967221, which is not a valid value for type 
'std::_Ios_Fmtflags'
  
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../include/c++/4.8/bits/ios_base.h:76:67:
 runtime error: load of value 4294967221, which is not a valid value for type 
'std::_Ios_Fmtflags'
  1
  1

  **

  $ g++ --version
  g++ (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4

  $ uname -a
  Linux ubuntu 3.13.0-66-generic #108-Ubuntu SMP Wed Oct 7 15:20:27 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release
  No LSB modules are available.

  **

  $ apt-cache show g++
  Package: g++
  Priority: optional
  Section: devel
  Installed-Size: 34
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian GCC Maintainers 
  Architecture: amd64
  Source: gcc-defaults (1.124ubuntu6)
  Version: 4:4.8.2-1ubuntu6
  Provides: c++-compiler
  Depends: cpp (>= 4:4.8.2-1ubuntu6), gcc (>= 4:4.8.2-1ubuntu6), g++-4.8 (>= 
4.8.2-5~), gcc-4.8 (>= 4.8.2-5~)
  Suggests: g++-multilib
  Filename: pool/main/g/gcc-defaults/g++_4.8.2-1ubuntu6_amd64.deb
  Size: 1490
  MD5sum: 7332a4e9116b821e167a3d0236ca413a
  SHA1: 2c7201808be1029d21b7691c5a855535a4fcbd51
  SHA256: 02c3d204efe6c34bf3de655aaf6a9ce524511977aedf92d7bce7093d0581f977
  Description-en: GNU C++ compiler
   This is the GNU C++ compiler, a fairly portable optimizing compiler for C++.
   .
   This is a dependency package providing the default GNU C++ compiler.
  Description-md5: 4d44b18774ae5123b7c3f70d940cf655
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Build-Essential: yes
  Origin: Ubuntu
  Supported: 5y

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1514309/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1446828] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gcc-4.8 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1446828

Title:
  gdb pretty printers do not auto-load on Trusty

Status in gcc-4.8 package in Ubuntu:
  Fix Released
Status in gcc-4.8 source package in Trusty:
  Fix Released

Bug description:
  On Ubuntu 14.04.2 (Trusty), the file in libstdc++6-4.8-dbg to auto-
  load the pretty printers doesn't resolve the right path to the
  printers. To reproduce, on a fresh install:

  $ cat test.cpp
  #include 
  int main() {
std::vector v;
v.push_back(1);
return 0;
  }
  $ g++ test.cpp -g
  $ gdb a.out -ex start
  Reading symbols from a.out...done.
  Temporary breakpoint 1 at 0x400956: file test.cpp, line 3.
  Starting program: /home/emaisin/a.out 
  Traceback (most recent call last):
File "/usr/lib/debug/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", 
line 63, in 
  from libstdcxx.v6.printers import register_libstdcxx_printers
  ImportError: No module named 'libstdcxx'

  Temporary breakpoint 1, main () at test.cpp:3
  3   std::vector v;
  (gdb) 

  It seems like the fixup for multiarch actually adds an extra "..":

  if not os.path.basename(os.path.dirname(__file__)).startswith('lib'):
  backdirs += 1 # multiarch subdir

  Removing these two lines almost makes it work:

  $ gdb a.out -ex start
  Reading symbols from a.out...done.
  Temporary breakpoint 1 at 0x400956: file test.cpp, line 3.
  Starting program: /home/emaisin/a.out 
  Traceback (most recent call last):
File "/usr/lib/debug/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", 
line 63, in 
  from libstdcxx.v6.printers import register_libstdcxx_printers
File 
"/usr/lib/x86_64-linux-gnu/../../share/gcc-4.8/python/libstdcxx/v6/printers.py",
 line 54
  raise ValueError, "Cannot find type %s::%s" % (str(orig), name)
  ^
  SyntaxError: invalid syntax

  Temporary breakpoint 1, main () at test.cpp:3
  3   std::vector v;

  
  That last problem is tracked in bug #1256419, which is still a pending issue 
in Trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1446828/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1517093] Update Released

[Chris J Arges]

The verification of the Stable Release Update for gcc-4.8 has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1517093

Title:
  HTM builtins aren't treated as compiler barriers on powerpc

Status in gcc-4.8 package in Ubuntu:
  Fix Released
Status in gcc-5 package in Ubuntu:
  Fix Released
Status in gcc-4.8 source package in Trusty:
  Fix Released

Bug description:
  ---Problem Description---
  HTM builtins aren't treated as compiler barriers on powerpc

  Contact Information = berg...@us.ibm.com

  ---Steps to Reproduce---

   This bug is a mirror of the (fixed) upstream FSF bugzilla 
https://gcc.gnu.org/PR67281
  All relevant information regarding the bug and the fix can be found there.  
This bugzilla is to track backporting of the fix to the GCC 4.8, 4.9 and 5 
based compilers.

  Userspace tool common name: GCC
  Userspace rpm: gcc-4.8, gcc-4.9 and gcc-5

  == Comment: #1
  The fix for the FSF GCC 5 branch was committed with:

  r228846 | bergner | 2015-10-15 11:38:47 -0500 (Thu, 15 Oct 2015) | 16
  lines

  Backport from mainline
  2015-10-14  Peter Bergner  
  Torvald Riegel  

  PR target/67281
  * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
  (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
  *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): New define_expands.
  * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
  __TM_FENCE__ for htm.
  * doc/extend.texi: Update documentation for htm builtins.

  == Comment: #2
  The fix for the FSF GCC 4.9 branch was committed with:

  r228847 | bergner | 2015-10-15 11:40:14 -0500 (Thu, 15 Oct 2015) | 16
  lines

  Backport from mainline
  2015-10-14  Peter Bergner  
  Torvald Riegel  

  PR target/67281
  * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
  (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
  *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): New define_expands.
  * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
  __TM_FENCE__ for htm.
  * doc/extend.texi: Update documentation for htm builtins.

  == Comment: #3
  Since the FSF 4.8 branch is closed, here is a backport of the fix along with 
another
  simple HTM wrong code bug to GCC 4.8.

  Backport from mainline
  2015-10-14  Peter Bergner  
  Torvald Riegel  

  PR target/67281
  * config/rs6000/htm.md (UNSPEC_HTM_FENCE): New.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): Rename define_insns from this...
  (*tabort, *tabortc, *tabortci, *tbegin, *tcheck, *tend,
  *trechkpt, *treclaim, *tsr, *ttest): ...to this.  Add memory barrier.
  (tabort, tabortc, tabortci, tbegin, tcheck, tend,
  trechkpt, treclaim, tsr, ttest): New define_expands.
  * config/rs6000/rs6000-c.c (rs6000_target_modify_macros): Define
  __TM_FENCE__ for htm.
  * doc/extend.texi: Update documentation for htm builtins.

  Backport from mainline:
  2015-08-03  Peter Bergner  

  * config/rs6000/htm.md (tabort.): Restrict the source operand to
  using a base register.

  Acceptance creterium: No regressions in the testsuite, and the new
  test passes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1517093/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1523573] Re: Doesn't let you share several images

[Bill Filler]

@artmello, @uriboni
Please remove the restriction for single selection for sharing. But please test 
sharing with messaging-app and make sure it doesn't break if you try to share 
multiple photos. For now expected behavior of messaging-app would be to just 
show first photo until we add support for sending multiple photos in that app.

** Changed in: canonical-devices-system-image
Milestone: backlog => ww08-2016

** Changed in: gallery-app (Ubuntu)
   Importance: Undecided => High

** Changed in: gallery-app (Ubuntu)
 Assignee: (unassigned) => Arthur Mello (artmello)

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => High

** Changed in: camera-app (Ubuntu)
 Assignee: (unassigned) => Ugo Riboni (uriboni)

** Also affects: messaging-app (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: messaging-app (Ubuntu)
   Importance: Undecided => High

** Changed in: messaging-app (Ubuntu)
   Status: New => Confirmed

** Changed in: messaging-app (Ubuntu)
 Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh)

-- 
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/1523573

Title:
  Doesn't let you share several images

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in gallery-app package in Ubuntu:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Using ota8 on bq devices, the share menu is disabled when more than
  one image is selected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523573/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1526548] Re: grep 2.22 infinite loop

[Matthias Klose]

fix included in -1ubuntu1

** Tags removed: block-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1526548

Title:
  grep 2.22 infinite loop

Status in grep package in Ubuntu:
  New

Bug description:
  Christian Boltz discovered that grep 2.22 can be sent into an infinite
  loop. 2.21 does not have this issue. The reproducer we have available
  so far:

  grep -obUa -P '\x04\x08\x00profile\x00\x07' /etc/apparmor.d/cache/*

  Probably one of the files in that directory will report infinite
  output in the style of:

  # grep -obUa -P '\x04\x08\x00profile\x00\x07' cache--usr.sbin.smbldap-useradd 
 
  16profile
  27801profile
  27801profile
  27801profile
  27801profile
  27801profile
  ...

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1526548/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543790] Re: OOBE not designed well for the tablet screen size

[Michał Sawicz]

** Attachment added: "language"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1543790/+attachment/4568490/+files/screenshot20160210_140450309.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1543790

Title:
  OOBE not designed well for the tablet screen size

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  The UI is quite odd on a wide landscape mode tablet

  Language selector should not be the entire width of the tablet in landscape
  Lock security selection shows a check mark on far right hand side of the 
screen and is very hard to detect
  Need to select the box on far right hand side for the Access point

  The Wifi screen never updated to show the AP was connected, and so it
  never changed from Skip to Continue

  After completing the wizard the lock screen is shown but the passcode
  is not required, tapping opens it

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543790/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543790] Re: OOBE not designed well for the tablet screen size

[Michał Sawicz]

** Attachment added: "screenshot20160210_140506202.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1543790/+attachment/4568492/+files/screenshot20160210_140506202.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1543790

Title:
  OOBE not designed well for the tablet screen size

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  The UI is quite odd on a wide landscape mode tablet

  Language selector should not be the entire width of the tablet in landscape
  Lock security selection shows a check mark on far right hand side of the 
screen and is very hard to detect
  Need to select the box on far right hand side for the Access point

  The Wifi screen never updated to show the AP was connected, and so it
  never changed from Skip to Continue

  After completing the wizard the lock screen is shown but the passcode
  is not required, tapping opens it

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543790/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543790] Re: OOBE not designed well for the tablet screen size

[Michał Sawicz]

** Attachment added: "security"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1543790/+attachment/4568491/+files/screenshot20160210_140455811.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1543790

Title:
  OOBE not designed well for the tablet screen size

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  The UI is quite odd on a wide landscape mode tablet

  Language selector should not be the entire width of the tablet in landscape
  Lock security selection shows a check mark on far right hand side of the 
screen and is very hard to detect
  Need to select the box on far right hand side for the Access point

  The Wifi screen never updated to show the AP was connected, and so it
  never changed from Skip to Continue

  After completing the wizard the lock screen is shown but the passcode
  is not required, tapping opens it

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543790/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

[Rafael David Tinoco]

The PPA for tests is:

https://launchpad.net/~inaddy/+archive/ubuntu/lp1529815

$ sudo add-apt-repository ppa:inaddy/lp1529815
$ sudo apt-get update && sudo apt-get dist-upgrade

Using a versioning schema that will be superseded by the final SRU.

PS: I'm also attaching the Trusty debdiff if this PPA proves to work.

Thank you

Rafael

** Patch added: "trusty_isc-dhcp_4.2.4-7ubuntu12.5.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+attachment/4568495/+files/trusty_isc-dhcp_4.2.4-7ubuntu12.5.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1529815

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  
  DHCP client is sending discover with Unicast type request for the offer, in 
this configuration of IB to ETH through a relay we need the type to be 
broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  
  DHCP CLIENT (IPoIB) 
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

[Rafael David Tinoco]

** Changed in: isc-dhcp (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: isc-dhcp (Ubuntu Wily)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1529815

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Wily:
  In Progress
Status in isc-dhcp source package in Xenial:
  In Progress

Bug description:
  
  DHCP client is sending discover with Unicast type request for the offer, in 
this configuration of IB to ETH through a relay we need the type to be 
broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  
  DHCP CLIENT (IPoIB) 
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543859] Re: Autopilot tests cannot launch most apps

[Josh Arenson]

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Josh Arenson (josharenson)

-- 
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/1543859

Title:
  Autopilot tests cannot launch most apps

Status in unity8 package in Ubuntu:
  New

Bug description:
  Only the dialer-app and webbrowser-app can be launched by calling the
  main_window.launch_application(appId) method. Possibly related to the
  fact that the location for .desktop files for most (all) other pre-
  installed apps has changed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1543859/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1535058] Re: applications close instantly when launched from the launcher or dash

[kevin gunn]

@serge a couple of things that could be preventing your login of unity8

1) Upgrade your system. Verify you have Mir 0.19.0 installed and then remove 
some broken packages that _will_ make Unity8 crash:
  $ sudo apt-get remove mir-client-platform-mesa3 mir-client-platform-mesa2 
mir-client-platform-mesa1
you should be on mir-client-platform-mesa4

2) Exercise your arm. We presently block for up to 30 seconds waiting for the 
kernel entropy pool to get populated (which may not happen). After 30 seconds, 
if it hasn't then Mir will give up and crash. Presently this is considered a 
"security feature" but we're improving on it. The workaround is to move your 
mouse around furiously both before and during the login process.
(https://bugs.launchpad.net/mir/+bug/1536662)

3) unity8 is supposed to be on vt8, but double check vt9 and see if
unity8 is there, for some reason, i see it on vt9 not vt8 - i discovered
on accident in frustration flipping between vts

4) this bug may also get you https://bugs.launchpad.net/ubuntu/+source
/clutter-gst-3.0/+bug/1525285 causes a deadlock

lastly, how to find unity8 login (which i've always found hard to explain in 
words) for those that may want to try
http://www.youtube.com/watch?v=W4Ijz8QSMJM

-- 
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/1535058

Title:
  applications close instantly when launched from the launcher or dash

Status in cgmanager package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Invalid

Bug description:
  xenial
  applications close instantly when launched from the launcher or dash
  but... if i launch the apps from a VT (for ex firefox using Xmir or gedit 
native --), the app loads ok.

  what close instantly means.. it opens the window and then it closes
  instantly in ~0.3s

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1535058/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

[Louis Bouchard]

** Also affects: isc-dhcp (Ubuntu Xenial)
   Importance: Undecided
 Assignee: Rafael David Tinoco (inaddy)
   Status: In Progress

** Also affects: isc-dhcp (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1529815

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Wily:
  In Progress
Status in isc-dhcp source package in Xenial:
  In Progress

Bug description:
  
  DHCP client is sending discover with Unicast type request for the offer, in 
this configuration of IB to ETH through a relay we need the type to be 
broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  
  DHCP CLIENT (IPoIB) 
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1544052] Re: Page header: Wrong actions moved to burger menu

[Bill Filler]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Zoltan Balogh (bzoltan)

** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1544052

Title:
  Page header: Wrong actions moved to burger menu

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  If a page is created with actions 'a, b, c' the actions appear as 'c, b, a' 
on the header. 
  But if you add an extra action 'a, b, c, d' the actions appear as 'b, a, [c, 
d]' with actions 'c,d' in the burger menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544052/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1440111] Re: Reminder notifications are not integrated into system notifications

[Merlijn Sebrechts]

Clock alarms overriding silent mode is default behavior in most phones.
That in itself seems like a good idea to keep that behavior.

2016-02-10 14:37 GMT+01:00 Jos van Houtem :

> If we would be able to choose which notifications could override silent
> mode, that would be great.
>
> On Wednesday, 10 February 2016, Daniel Frost  wrote:
> > @charlesk - post from 2016-02-04
> > Uhm, I hope you don't mind the question, but why should clock alarms
> override silent mode?
> > I did actually file this behavior as a bug (
> https://bugs.launchpad.net/ubuntu-clock-app/+bug/1542889).
> > Silent mode should be silent regardless of the action coming up. Or maybe
> you should be able to choose which actions are allowed to override silent
> mode?
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1463936).
> > https://bugs.launchpad.net/bugs/1440111
> >
> > Title:
> >   [calendar] Reminder notifications are not integrated into system
> >   notifications
> >
> > Status in Canonical System Image:
> >   In Progress
> > Status in Ubuntu Calendar App:
> >   Fix Committed
> > Status in Ubuntu UX:
> >   Fix Committed
> > Status in indicator-datetime package in Ubuntu:
> >   In Progress
> >
> > Bug description:
> >   The calendar app does not use the standard notification system. You
> >   can't find it in the "Notifications" area of System Settings, and it
> >   uses its own notification sound regardless of what is set in "Sound".
> >
> >   Also, reminders are not muted when the phone is in silent mode (I
> >   guess it's related).
> >
> >   I'm on bq Aquaris, r20 and with the latest calendar-app.
> >
> >   --- --- --- ---
> >   UX Comment:
> >
> >   Calendar Notifications need to be overhauled:
> >   -- Calendar Notifications are displayed for too brief a period and
> should conform to the same timing as other notifications.
> >
> >   -- Calendar Notifications are not currently appearing in the
> >   notification tray within indicators and should be.
> >
> >   -- Calendar Notification title is misleading ('Alarm') and should make
> >   clear that the notification relates to a calendar event ('Event') and
> >   not a alarm-clock event.
> >
> >   -- Calendar Notification's should NOT override silent mode (unlike
> >   clock-alarms) although the notification should still be displayed,
> >   appear in the notification within indicators and cause the device to
> >   vibrate (if enabled) - This is accepted/common behaviour for
> >   notifications of this type on mobile.
> >
> >   Notifications Spec:
> >
>
> https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit
> >
> > To manage notifications about this bug go to:
> >
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1440111/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1440111
>
> Title:
>   [calendar] Reminder notifications are not integrated into system
>   notifications
>
> Status in Canonical System Image:
>   In Progress
> Status in Ubuntu Calendar App:
>   Fix Committed
> Status in Ubuntu UX:
>   Fix Committed
> Status in indicator-datetime package in Ubuntu:
>   In Progress
>
> Bug description:
>   The calendar app does not use the standard notification system. You
>   can't find it in the "Notifications" area of System Settings, and it
>   uses its own notification sound regardless of what is set in "Sound".
>
>   Also, reminders are not muted when the phone is in silent mode (I
>   guess it's related).
>
>   I'm on bq Aquaris, r20 and with the latest calendar-app.
>
>   --- --- --- ---
>   UX Comment:
>
>   Calendar Notifications need to be overhauled:
>   -- Calendar Notifications are displayed for too brief a period and
> should conform to the same timing as other notifications.
>
>   -- Calendar Notifications are not currently appearing in the
>   notification tray within indicators and should be.
>
>   -- Calendar Notification title is misleading ('Alarm') and should make
>   clear that the notification relates to a calendar event ('Event') and
>   not a alarm-clock event.
>
>   -- Calendar Notification's should NOT override silent mode (unlike
>   clock-alarms) although the notification should still be displayed,
>   appear in the notification within indicators and cause the device to
>   vibrate (if enabled) - This is accepted/common behaviour for
>   notifications of this type on mobile.
>
>   Notifications Spec:
>
> https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1440111/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.

[Touch-packages] [Bug 1536208] Re: Can no longer find dlna server after upgrade from 15.10 to 16.04

[Sebastien Bacher]

** Tags added: rls-x-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1536208

Title:
  Can no longer find dlna server after upgrade from 15.10 to 16.04

Status in dleyna-server package in Ubuntu:
  New
Status in grilo-plugins package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  From irc:
  08:28 < jdstrand> Laney: question for you-- just otoh, can you think of a 
reason why dlna wouldn't work on xenial in rhythmbox any more when it has the 
same upstream version as wily (and the Ubuntu delta didn't have any relevant 
changes), grilo is the same as wily and grilo-plugins only has one irrelevant 
change over wily?
  08:29 < jdstrand> (it the dleyna code in grilo that handles this afaik)
  08:30 < jdstrand> Laney: the dlna server just doesn't show up any more (but 
daap still does)
  08:33 < jdstrand> I have both forked-daapd and minidlna exporting 
  08:33 < jdstrand> and rhythmbox used to see both on wily. on xenial, it only 
sees daap

  This may be a bug in grilo or grilo-plugins since, AIUI, it is the
  dleyna code in grilo-plugins that handles this. It appears that grilo
  relies on dleyna-server and dleyna-server isn't able to find the
  server any more. I tried on a separate wily install and it wasn't able
  to find it.

  Coming up with a reproducer was more difficult than I thought it would
  be.

  1. minidlna server setup
  $ sudo apt-get install minidlna

  Adjust /etc/minidlna.conf to have:
  media_dir=A,/path/to/some/music/files

  I believe everything else can be left as defaults.

  2. rhythmbox setup
  $ sudo apt-get install grilo-plugins-0.2-extra rhythmbox-plugins dleyna-server

  stop and start rhythmbox

  go into Tools/Plugins and check Grilo media browser

  This was all I needed to do initially for it to start working. Now it
  now longer works. Android devices and 'kodi' from Ubuntu can find and
  use it fine. Using d-feet and going to 'com.intel.dleyna-server' and
  into com.intel.dLeynaServer.Manager and looking at 'GetServers'
  returns nothing. Looking at Rescan() triggers traffic (as seen with
  tcpcump) with the server (ie, there are responses). Looking at an
  strace of /usr/lib/dleyna-server/dleyna-server-service shows it got a
  response from the minidlna server. I guess the problem is in dleyna-
  server. There is a new upstream version (0.5), but it is newer than
  what is in Debian.

  Apparently minidlna is installed in Netgear devices and other places
  and is quite popular.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dleyna-server/+bug/1536208/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1539446] Re: Today scope hangs-on after OTA9 update

[Kyle Nitzsche]

HI Danilo,

Thanks for your responses!

Can you please get the following file right after the "freeze" and attach it to 
this bug:
/home/phablet/.cache/upstart/scope-registry.log

Cheers

-- 
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/1539446

Title:
  Today scope hangs-on after OTA9 update

Status in Today Scope:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  really often  from Yesterday night (OTA9 updated at 11 p.m.) the Today
  scope freeze the screen and no other actiion is possibile to achieve.
  the system restart itself after 20-30 seconds .

  it happens especially  recalling the Today scope by sweeping from Rhs to Lhs  
to view the full  open scopes  on the screeen. 
  when you touch the Today scope to acces it (or, as well, if you touch the 
Ubuntu logo icon in the Unity view)  the scope open full screen and the device 
freeze.

  no more possibility to acces vertical "courtains" menu
  (notifications, blutooth, netwoorks a.s.o.)  neither  any of the other
  icons.

  If you send a call to the device SIM number,  you can ear (frpm the
  sender device speaker) the usual network ringigng tone, but nothing
  happens on the Ubuntu phone . After the self reboot, the lost call is
  correctly notified on the notification menu.

  device BQ E5 - Ubuntu 15.04 OTA9 (28/01/2016) -  UA001808

  available for testing and further info supply

  Regards and thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1539446/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1540372] Re: [Intel DP35DP, SigmaTel STAC9271D, Green Speaker, Rear] Underruns, dropouts or crackling sound

[nour]

One more thing here:
tuned@tuned-desktop:~$ cat /proc/asound/devices
  1:: sequencer
  2: [ 0]   : control
  3: [ 0- 0]: digital audio playback
  4: [ 0- 0]: digital audio capture
  5: [ 0- 1]: digital audio playback
  6: [ 0- 2]: digital audio capture
  7: [ 0- 2]: hardware dependent

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1540372

Title:
  [Intel DP35DP, SigmaTel STAC9271D, Green Speaker, Rear] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  I cant record or play on my sound card ubuntu 14.04.1

  Alsa is detecting the sound card
   List of PLAYBACK Hardware Devices 
  card 0: Intel [HDA Intel], device 0: STAC9271D Analog [STAC9271D Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 1: STAC9271D Digital [STAC9271D Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  but PulseAudio is not detecting the card 

  attached the log file

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuned  1851 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 15:09:35 2016
  InstallationDate: Installed on 2015-10-26 (98 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Green Speaker, Rear
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [, SigmaTel STAC9271D, Green Speaker, Rear] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP35DP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81073-207
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-207:cvn:ct2:cvr:
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-01-29T17:09:52.179523

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1540372/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1473225] Re: with encrypted home, /etc/legal is printed twice on every login

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: shadow (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1473225

Title:
  with encrypted home, /etc/legal is printed twice on every login

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  I have an encrypted home directory, and whenever I log in at the
  console, the contents of /etc/legal are printed twice (after the
  system load stats).

  This happens because:

  1) pam_motd.so uses ~/.cache/motd.legal-displayed to record the fact
  that /etc/legal has already been displayed;

  2) the home directory is read-only until ecryptfs is mounted;

  3) the MOTD is printed before ecryptfs is mounted, because in
  /etc/pam.d/login the pam_motd.so rules come before "@include common-
  session" (which includes the pam_ecryptfs.so rule).

  The fix should be simple - just change the order so that the
  pam_motd.so rules come after "@include common-session". (The Apport
  report says my /etc/pam.d/login is modified, because I did just that.)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: login 1:4.1.5.1-1.1ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Fri Jul 10 00:24:19 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-06-22 (1112 days ago)
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
  ProcEnviron:
   TERM=linux
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=ru_RU.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: shadow
  UpgradeStatus: Upgraded to vivid on 2015-06-27 (12 days ago)
  modified.conffile..etc.pam.d.login: [modified]
  mtime.conffile..etc.pam.d.login: 2015-07-10T00:04:57.396555

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1473225/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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"

[Alberto Aguirre]

@Daniel,

The OP also reports a "restart", whose description match what would
happen if USC restarts... so we are going by our suspicion that it's
related to the failure to start the compositor threads. The error logs
in unity8 (USC's client) are irrelevant in that case.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1532607

Title:
  Phone not usable while a call comes in - followed by "restart"

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in Mir 0.19 series:
  New
Status in Mir 0.20 series:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  My system:

  current build number: 225
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-01-09 06:52:53
  version version: 225
  version ubuntu: 20160109
  version device: 20151216-378d4f3
  version custom: 2015--36-46-vivid

  What happened:
  Someone called me and I wanted to take the call on the phone (nothing 
attached to the phone). The screen was locked and I pressed the power button to 
unlock the screen. The phone did not react on any pushed buttons. The phone 
continued ringing but I was not able to do anything with the phone during this 
time.

  During the next minute the phone was blocked. After this period a
  "restart" followed.

  "Restart":
  The restart was not a real reset. The phone screen was black. Then approx. 1 
- 2 minutes after the call was gone, the screen went on again and the ubuntu 
logo with the dots appeared (same screen when you start the phone but without 
the "bq"-screen). 

  I did not need to enter the PIN code of the SIM card. The phone was
  again fully operational.

  This happened on January, 10th at approx. 13:30 h. I have attached the
  sys.log for your review and hopefully for tracing back the issue to
  the root cause.

  Matthias

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

[Rafael David Tinoco]

** Attachment added: "dhclient.conf"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+attachment/4568545/+files/dhclient.conf

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1529815

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Wily:
  In Progress
Status in isc-dhcp source package in Xenial:
  In Progress

Bug description:
  
  DHCP client is sending discover with Unicast type request for the offer, in 
this configuration of IB to ETH through a relay we need the type to be 
broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  
  DHCP CLIENT (IPoIB) 
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

[Rafael David Tinoco]

** Patch removed: "trusty_isc-dhcp_4.2.4-7ubuntu12.5.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+attachment/4568495/+files/trusty_isc-dhcp_4.2.4-7ubuntu12.5.debdiff

** Patch added: "trusty_isc-dhcp_4.2.4-7ubuntu12.5.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+attachment/4568523/+files/trusty_isc-dhcp_4.2.4-7ubuntu12.5.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1529815

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Wily:
  In Progress
Status in isc-dhcp source package in Xenial:
  In Progress

Bug description:
  
  DHCP client is sending discover with Unicast type request for the offer, in 
this configuration of IB to ETH through a relay we need the type to be 
broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  
  DHCP CLIENT (IPoIB) 
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

[Rafael David Tinoco]

** Attachment added: "dhcpd.conf"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+attachment/4568546/+files/dhcpd.conf

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1529815

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Wily:
  In Progress
Status in isc-dhcp source package in Xenial:
  In Progress

Bug description:
  
  DHCP client is sending discover with Unicast type request for the offer, in 
this configuration of IB to ETH through a relay we need the type to be 
broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  
  DHCP CLIENT (IPoIB) 
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543883] Re: screen blanked during systemd-logind upgrade

[Timo Jyrinki]

For me the screen was locked when upgrading 14.04 with the systemd and I
needed to unlock it. This happened when external screen was attached and
laptop lid closed, so possibly laptop lid being closed was read as a new
event or something.

-- 
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/1543883

Title:
  screen blanked during systemd-logind upgrade

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded my trusty system and the X11 / unity7 screen turned
  black for ~200ms twice during the upgrade; it appeared roughly when
  the systemd-logind services were stopped and started in this log.
  Music playing via youtube in firefox kept playing without issue and
  the X11 session otherwise seemed unaffected but it certainly was
  jarring.

  Thanks

  The following packages will be upgraded:
flashplugin-installer gir1.2-gudev-1.0 libgudev-1.0-0 libpam-systemd
libsystemd-daemon0 libsystemd-journal0 libsystemd-login0 libudev1
libudev1:i386 systemd-services udev
  11 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,138 kB of archives.
  After this operation, 1,024 B of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Get:1 http://mirrors.kernel.org/ubuntu/ trusty-updates/main udev amd64 
204-5ubuntu20.18 [734 kB]
  Get:2 http://security.ubuntu.com/ubuntu/ trusty-security/multiverse 
flashplugin-installer amd64 11.2.202.569ubuntu0.14.04.1 [6,852 B]
  Get:3 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libudev1 i386 
204-5ubuntu20.18 [34.4 kB]
  Get:4 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libudev1 amd64 
204-5ubuntu20.18 [33.5 kB]
  Get:5 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libpam-systemd 
amd64 204-5ubuntu20.18 [25.5 kB]
  Get:6 http://mirrors.kernel.org/ubuntu/ trusty-updates/main systemd-services 
amd64 204-5ubuntu20.18 [197 kB]
  Get:7 http://mirrors.kernel.org/ubuntu/ trusty-updates/main 
libsystemd-daemon0 amd64 204-5ubuntu20.18 [10.0 kB]
  Get:8 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libsystemd-login0 
amd64 204-5ubuntu20.18 [27.0 kB]
  Get:9 http://mirrors.kernel.org/ubuntu/ trusty-updates/main libgudev-1.0-0 
amd64 1:204-5ubuntu20.18 [14.1 kB]
  Get:10 http://mirrors.kernel.org/ubuntu/ trusty-updates/main 
libsystemd-journal0 amd64 204-5ubuntu20.18 [49.9 kB]
  Get:11 http://mirrors.kernel.org/ubuntu/ trusty-updates/main gir1.2-gudev-1.0 
amd64 1:204-5ubuntu20.18 [5,496 B]
  Fetched 1,138 kB in 0s (1,162 kB/s)   
  Preconfiguring packages ...
  (Reading database ... 307737 files and directories currently installed.)
  Preparing to unpack .../udev_204-5ubuntu20.18_amd64.deb ...
  Adding 'diversion of /bin/udevadm to /bin/udevadm.upgrade by fake-udev'
  Unpacking udev (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../libudev1_204-5ubuntu20.18_i386.deb ...
  De-configuring libudev1:amd64 (204-5ubuntu20.15) ...
  Unpacking libudev1:i386 (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../libudev1_204-5ubuntu20.18_amd64.deb ...
  Unpacking libudev1:amd64 (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../libpam-systemd_204-5ubuntu20.18_amd64.deb ...
  systemd-logind stop/waiting
  Unpacking libpam-systemd:amd64 (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../systemd-services_204-5ubuntu20.18_amd64.deb ...
  Unpacking systemd-services (204-5ubuntu20.18) over (204-5ubuntu20.15) ...
  Preparing to unpack .../libsystemd-daemon0_204-5ubuntu20.18_amd64.deb ...
  Unpacking libsystemd-daemon0:amd64 (204-5ubuntu20.18) over (204-5ubuntu20.15) 
...
  Preparing to unpack .../libsystemd-login0_204-5ubuntu20.18_amd64.deb ...
  Unpacking libsystemd-login0:amd64 (204-5ubuntu20.18) over (204-5ubuntu20.15) 
...
  Preparing to unpack .../libgudev-1.0-0_1%3a204-5ubuntu20.18_amd64.deb ...
  Unpacking libgudev-1.0-0:amd64 (1:204-5ubuntu20.18) over (1:204-5ubuntu20.15) 
...
  Preparing to unpack .../libsystemd-journal0_204-5ubuntu20.18_amd64.deb ...
  Unpacking libsystemd-journal0:amd64 (204-5ubuntu20.18) over 
(204-5ubuntu20.15) ...
  Preparing to unpack 
.../flashplugin-installer_11.2.202.569ubuntu0.14.04.1_amd64.deb ...
  Unpacking flashplugin-installer (11.2.202.569ubuntu0.14.04.1) over 
(11.2.202.559ubuntu0.14.04.1) ...
  Preparing to unpack .../gir1.2-gudev-1.0_1%3a204-5ubuntu20.18_amd64.deb ...
  Unpacking gir1.2-gudev-1.0 (1:204-5ubuntu20.18) over (1:204-5ubuntu20.15) ...
  Processing triggers for man-db (2.6.7.1-1ubuntu1) ...
  Processing triggers for ureadahead (0.100.0-16) ...
  Processing triggers for update-notifier-common (0.154.1ubuntu1) ...
  flashplugin-installer: downloading 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20160209.1.orig.tar.gz
  Installing from local file /tmp/tmpmN_J4k.gz
  Flash Plugin installed.
  

[Touch-packages] [Bug 1543495] Re: boot splash not in native orientation

[Alexandros Frantzis]

** 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 1541925] Re: Tries to create temp files under ~/.gnupg but doesn't create the dir

[Bug Watch Updater]

** Changed in: gnupg
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1541925

Title:
  Tries to create temp files under ~/.gnupg but doesn't create the dir

Status in GnuPG:
  In Progress
Status in gnupg package in Ubuntu:
  Fix Released

Bug description:
  That's a regression since the 1.4.20 update which impacts the
  software-properties tests [1]

  the error is
  "test_add_gpg_key (tests.test_dbus.TestDBus) ... gpg: failed to create 
temporary file `/home/ubuntu/.gnupg/.#lk0x21044c0.adt.7314': No such file or 
directory"

  the command called is 
  "/usr/bin/gpg --no-options --no-default-keyring --no-auto-check-trustdb 
--trust-model always --keyring 
/build/software-properties-0.96.17/tests/aptroot/etc/apt/trusted.gpg 
--secret-keyring /tmp/tmpohq9ksnp/secring.gpg --quiet --batch --import 
/build/software-properties-0.96.17/tests/data/testkey.gpg"

  which fails if there is no .gnupg directory

  [1]
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-xenial/xenial/amd64/s/software-
  properties/20160203_235320@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnupg/+bug/1541925/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1544052] [NEW] Page header: Wrong actions moved to burger menu

[Renato Araujo Oliveira Filho]

Public bug reported:

If a page is created with actions 'a, b, c' the actions appear as 'c, b, a' on 
the header. 
But if you add an extra action 'a, b, c, d' the actions appear as 'b, a, [c, 
d]' with actions 'c,d' in the burger menu.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1544052

Title:
  Page header: Wrong actions moved to burger menu

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  If a page is created with actions 'a, b, c' the actions appear as 'c, b, a' 
on the header. 
  But if you add an extra action 'a, b, c, d' the actions appear as 'b, a, [c, 
d]' with actions 'c,d' in the burger menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1544052/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1440111] Re: Reminder notifications are not integrated into system notifications

[Jos van Houtem]

If we would be able to choose which notifications could override silent
mode, that would be great.

On Wednesday, 10 February 2016, Daniel Frost  wrote:
> @charlesk - post from 2016-02-04
> Uhm, I hope you don't mind the question, but why should clock alarms
override silent mode?
> I did actually file this behavior as a bug (
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1542889).
> Silent mode should be silent regardless of the action coming up. Or maybe
you should be able to choose which actions are allowed to override silent
mode?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1463936).
> https://bugs.launchpad.net/bugs/1440111
>
> Title:
>   [calendar] Reminder notifications are not integrated into system
>   notifications
>
> Status in Canonical System Image:
>   In Progress
> Status in Ubuntu Calendar App:
>   Fix Committed
> Status in Ubuntu UX:
>   Fix Committed
> Status in indicator-datetime package in Ubuntu:
>   In Progress
>
> Bug description:
>   The calendar app does not use the standard notification system. You
>   can't find it in the "Notifications" area of System Settings, and it
>   uses its own notification sound regardless of what is set in "Sound".
>
>   Also, reminders are not muted when the phone is in silent mode (I
>   guess it's related).
>
>   I'm on bq Aquaris, r20 and with the latest calendar-app.
>
>   --- --- --- ---
>   UX Comment:
>
>   Calendar Notifications need to be overhauled:
>   -- Calendar Notifications are displayed for too brief a period and
should conform to the same timing as other notifications.
>
>   -- Calendar Notifications are not currently appearing in the
>   notification tray within indicators and should be.
>
>   -- Calendar Notification title is misleading ('Alarm') and should make
>   clear that the notification relates to a calendar event ('Event') and
>   not a alarm-clock event.
>
>   -- Calendar Notification's should NOT override silent mode (unlike
>   clock-alarms) although the notification should still be displayed,
>   appear in the notification within indicators and cause the device to
>   vibrate (if enabled) - This is accepted/common behaviour for
>   notifications of this type on mobile.
>
>   Notifications Spec:
>
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit
>
> To manage notifications about this bug go to:
>
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1440111/+subscriptions
>

-- 
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/1440111

Title:
  [calendar] Reminder notifications are not integrated into system
  notifications

Status in Canonical System Image:
  In Progress
Status in Ubuntu Calendar App:
  Fix Committed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  The calendar app does not use the standard notification system. You
  can't find it in the "Notifications" area of System Settings, and it
  uses its own notification sound regardless of what is set in "Sound".

  Also, reminders are not muted when the phone is in silent mode (I
  guess it's related).

  I'm on bq Aquaris, r20 and with the latest calendar-app.

  --- --- --- ---
  UX Comment:

  Calendar Notifications need to be overhauled:
  -- Calendar Notifications are displayed for too brief a period and should 
conform to the same timing as other notifications.

  -- Calendar Notifications are not currently appearing in the
  notification tray within indicators and should be.

  -- Calendar Notification title is misleading ('Alarm') and should make
  clear that the notification relates to a calendar event ('Event') and
  not a alarm-clock event.

  -- Calendar Notification's should NOT override silent mode (unlike
  clock-alarms) although the notification should still be displayed,
  appear in the notification within indicators and cause the device to
  vibrate (if enabled) - This is accepted/common behaviour for
  notifications of this type on mobile.

  Notifications Spec:
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1440111/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1528321] Re: Everything hangs when coming out of fullscreen in chrome

[checoimg]

The HW acceleration is fixed in Version 48.0.2564.103-1 as of today.
Latest stable. I tried on Youtube and Javascript based Fullscreen from
Treehouse.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1528321

Title:
  Everything hangs when coming out of fullscreen in chrome

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  If I have hardware acceleration enabled in my chrome settings (which
  it is automatically), my entire desktop freezes 9 times out of 10 when
  I come out of fullscreen mode. It doesn't matter whether it's with F11
  or a video on a site such as YouTube. Strangely enough, the audio
  keeps on going.

  If I disable hardware acceleration, then I don't experience this
  issue, but I can't use WebGL. My CPU usage also goes through the roof
  , heating my laptop up, and reducing my battery life.

  If I switch to a different tty with CTRL+ALT and login it says
  that it can't connect to the X server or something. I don't
  particularly want to cause a another hang to find out either as a
  forceful shutdown may damage my filesystem(s).

  I'm using Ubuntu Desktop 15.10 wily.

  Here's my uname -a:

  Linux Snowflake 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC
  2015 x86_64 x86_64 x86_64 GNU/Linux

  Here's my chrome version information:

  Google Chrome 48.0.2564.48 (Official Build) beta (64-bit)
  Revision  
ae7f323bae9104a543ae39d46453b712de27d15d-refs/branch-heads/2564@{#362}
  OSLinux 
  Blink 537.36 (@ae7f323bae9104a543ae39d46453b712de27d15d)
  JavaScriptV8 4.8.271.9
  Flash 20.0.0.248
  User AgentMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like 
Gecko) Chrome/48.0.2564.48 Safari/537.36

  Can anyone help me please?

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Dec 21 18:43:27 2015
  DistUpgraded: 2015-10-17 12:39:24,649 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-352, 352.63, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04ca]
   NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2015-09-14 (98 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=dd320194-8d8a-491f-89af-a4997c775049 ro quiet splash nomodest 
init=/sbin/e4rat-preload
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-17 (65 days ago)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0FXK2Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0FXK2Y:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Mon Dec 21 07:14:24 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   13905 
   vendor   

[Touch-packages] [Bug 1389309] Re: /etc/init.d/ondemand assumes cpu0 exists and is online

[Breno Leitão]

** Changed in: sysvinit (Ubuntu)
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1389309

Title:
  /etc/init.d/ondemand assumes cpu0 exists and is online

Status in sysvinit package in Ubuntu:
  New

Bug description:
  I have a ppc64el box with a couple of processors disabled because of
  hardware issues:

  # head /proc/cpuinfo 
  processor : 16

  The ondemand initscript assumes cpu0 is online:

  AVAILABLE="/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors"

  I also opened a bug on Debian and proposed a patch that seems to fix
  this problem. It is bug#767942

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767942

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1389309/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1473800] Re: restarting logind during systemd update causes screen to lock

[Martin Pitt]

** Also affects: systemd (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
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/1473800

Title:
  restarting logind during systemd update causes screen to lock

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Triaged

Bug description:
  When systemd is updated (through the update manager), the
  screen/session locks when processing the update.

  I've had this happen twice I think, and the only suspicious packages
  are the systemd ones.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 222-1ubuntu3
  ProcVersionSignature: Ubuntu 4.0.0-4.6-generic 4.0.7
  Uname: Linux 4.0.0-4-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jul 13 09:49:47 2015
  InstallationDate: Installed on 2015-01-31 (162 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-4-generic 
root=UUID=4c827ac5-3a87-4443-86eb-a55dca9626ad ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.30
  dmi.board.name: FM2A88X Extreme4+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/31/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88XExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1473800/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1416642] Re: No mouse cursor shown when connecting a BT mouse to the phone

[Michael Zanetti]

** Changed in: unity8 (Ubuntu)
   Status: Triaged => 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/1416642

Title:
  No mouse cursor shown when connecting a BT mouse to the phone

Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  No mouse cursor is being displayed when a BT mouse is connected to my
  phone. I noticed that the mouse does actually work but the user isn't
  able to see its current position.

  phablet@ubuntu-phablet:~$ system-image-cli --info
  current build number: 86
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-01-31 10:08:49
  version version: 86
  version ubuntu: 20150131
  version device: 20150129
  version custom: 20150131

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1416642/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1068960] Re: crash when touch grab fails

[Stephen M. Webb]

Ran the attached test program and verified it was grabbing the touches,
but Compiz did not crash on startup or use.  I'm closing this bug on the
assumption that the fix for #1080386 was also the solution for this bug.

** Changed in: geis (Ubuntu)
   Status: Triaged => Invalid

** Changed in: geis (Ubuntu)
 Assignee: Stephen M. Webb (bregma) => (unassigned)

** Changed in: geis
Milestone: 2.2.18 => None

** Changed in: geis
   Status: Triaged => Invalid

** Changed in: geis
Milestone: None => 2.2.18

** Changed in: geis
 Assignee: Stephen M. Webb (bregma) => (unassigned)

** Changed in: geis
Milestone: 2.2.18 => None

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to geis in Ubuntu.
https://bugs.launchpad.net/bugs/1068960

Title:
  crash when touch grab fails

Status in Geis:
  Invalid
Status in geis package in Ubuntu:
  Invalid

Bug description:
  If another client already has a touch grab on the root window, libgeis
  crashes, taking unity down in the process.

  To reproduce, compile the attached program, and then add it to the
  startup applications.  The command should be '/path/to/touchgrab 2 0
  reject'.  Then log out and log back into unity, which results in the
  crash.  Tested on quantal.

  This might be the underlying cause of bug #1038455.

To manage notifications about this bug go to:
https://bugs.launchpad.net/geis/+bug/1068960/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536664] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From roes...@de.ibm.com 2016-02-10 10:13 EDT---
With this fix you can format a DASD that was used for LVM.

I have however found a problem, of which I don't know if this is related
or a new one or is even expected behaviour. If this is separate, please
tell me so that I can open a new bug for this.

Here's what I tried:

- Select DASD (which I used for an installation with LVM before)
- Format the Device -> no
- Finish
- Partitioning method: manual

- Menu "Partition disks":
DASD 0.0.5d32 (ECKD) - 7.4 GB IBM S390 DASD drive
> #1500.0 MB   ext2
> #2  6.9 GBK  lvm
>49.2 kB   FREE SPACE
LVM VG rootVG, LV rootLV - 6.9 GB Linux device-mapper (linear)
> #1  6.9 GB   ext4

- Go Back

- Select "Configure direct access storage devices (DASD)"

- Select previous DASD again; DASD is displayed as 0.0.5d32 (online)

- Format the device -> Yes

- Error:

Installation step failed
An installation step failed. You can try to run the failing item again from the 
menu, or skip it and choose something
else. The failing step is: Configure direct access storage devices (DASD)

/proc/partitions looks like this:

major minor  #blocks  name

10  4 ram0
11  4 ram1
12  4 ram2
13  4 ram3
14  4 ram4
15  4 ram5
16  4 ram6
17  4 ram7
18  4 ram8
19  4 ram9
1   10  4 ram10
1   11  4 ram11
1   12  4 ram12
1   13  4 ram13
1   14  4 ram14
1   15  4 ram15
9407212240 dasda
941 488304 dasda1
9426723792 dasda2
25206721536 dm-0

I have attached the syslog that was created during my test.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1536664

Title:
  Installer cannot use DASD if it was used with LVM before

Status in lvm2 package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Michael Roesch  - 2016-01-21 07:31:16 ==
  A DASD that has been used with and partitioned for LVM, cannot be used for 
installation. The installer cannot format the disk. It throws the error "An 
installation step failed. You can try to run the failing item again from the 
menu, or skip it and choose something else. The failing step is: Configure 
direct access storage devices (DASD)". 
  When you just select the DASD without formatting, the installer accepts the 
DASD, but hangs at "Scanning disks..." at 45 percent. I have attached the 
syslog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1536664/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1523573] Re: Doesn't let you share several images

[Bill Filler]

iirc, if we are initiating the share from the gallery app we purposely
limited to 1 selection (possibly the same in camera?) because messaging-
app could only handle a single attachment at a time (and think this is
still the case). I don't know if content-hub api specifies a way for the
source app to know whether or not the destination app supports multiple
files in this case. I suppose we could allow multi-selection and if the
destination app doesn't support it, it should notify the user.

I believe if another app requests the import from the gallery (i.e.
dekko asks to attach images) then gallery should honor the multi-select
request from content-hub.

-- 
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/1523573

Title:
  Doesn't let you share several images

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in gallery-app package in Ubuntu:
  Confirmed

Bug description:
  Using ota8 on bq devices, the share menu is disabled when more than
  one image is selected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523573/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536664] Syslog lvm format

[bugproxy]

--- Comment (attachment only) From roes...@de.ibm.com 2016-02-10 10:17 
EDT---


** Attachment added: "Syslog lvm format"
   
https://bugs.launchpad.net/bugs/1536664/+attachment/4568556/+files/syslog_lvm_format.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1536664

Title:
  Installer cannot use DASD if it was used with LVM before

Status in lvm2 package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Michael Roesch  - 2016-01-21 07:31:16 ==
  A DASD that has been used with and partitioned for LVM, cannot be used for 
installation. The installer cannot format the disk. It throws the error "An 
installation step failed. You can try to run the failing item again from the 
menu, or skip it and choose something else. The failing step is: Configure 
direct access storage devices (DASD)". 
  When you just select the DASD without formatting, the installer accepts the 
DASD, but hangs at "Scanning disks..." at 45 percent. I have attached the 
syslog.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1536664/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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"

[Alberto Aguirre]

** Branch linked: lp:mir/0.19

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1532607

Title:
  Phone not usable while a call comes in - followed by "restart"

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in Mir 0.19 series:
  New
Status in Mir 0.20 series:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  My system:

  current build number: 225
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-01-09 06:52:53
  version version: 225
  version ubuntu: 20160109
  version device: 20151216-378d4f3
  version custom: 2015--36-46-vivid

  What happened:
  Someone called me and I wanted to take the call on the phone (nothing 
attached to the phone). The screen was locked and I pressed the power button to 
unlock the screen. The phone did not react on any pushed buttons. The phone 
continued ringing but I was not able to do anything with the phone during this 
time.

  During the next minute the phone was blocked. After this period a
  "restart" followed.

  "Restart":
  The restart was not a real reset. The phone screen was black. Then approx. 1 
- 2 minutes after the call was gone, the screen went on again and the ubuntu 
logo with the dots appeared (same screen when you start the phone but without 
the "bq"-screen). 

  I did not need to enter the PIN code of the SIM card. The phone was
  again fully operational.

  This happened on January, 10th at approx. 13:30 h. I have attached the
  sys.log for your review and hopefully for tracing back the issue to
  the root cause.

  Matthias

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532607/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543594] Re: unity-system-compositor locked up in __libc_do_syscall()

[Alberto Aguirre]

** Changed in: mir/0.20
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1543594

Title:
  unity-system-compositor locked up in __libc_do_syscall()

Status in Mir:
  Fix Committed
Status in Mir 0.19 series:
  Fix Committed
Status in Mir 0.20 series:
  Fix Committed
Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  This happened when I got an incoming call, couldn't wake the screen
  up, even though the phone worked fine otherwise.

  powerd-cli list took ~20s to return

  https://paste.ubuntu.com/15001777/ for u-s-c trace
  https://paste.ubuntu.com/15001805/ tamer powerd trace

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity-system-compositor 0.4.1+15.04.20160203-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Tue Feb  9 15:06:13 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1454530118
  GraphicsCard:
   
  InstallationDate: Installed on 2016-02-06 (3 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160206-020305)
  ProcCmdline: unity-system-compositor --disable-overlays=false 
--spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket 
--from-dm-fd 10 --to-dm-fd 13 --vt 1
  ProcCwd: /
  ProcEnviron:
   
  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:46
   __lll_lock_wait (futex=futex@entry=0x6402fc, private=0) at lowlevellock.c:46
   __GI___pthread_mutex_lock (mutex=0x6402fc) at pthread_mutex_lock.c:80
   __gthread_mutex_lock (__mutex=0x6402fc) at 
/usr/include/arm-linux-gnueabihf/c++/4.9/bits/gthr-default.h:748
   lock (this=0x6402fc) at /usr/include/c++/4.9/mutex:135
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.60-2
  version.lightdm: lightdm 1.14.4-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1543594/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 629850] Re: grep crashed with SIGILL in __kernel_vsyscall()

[Matthias Klose]

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/629850

Title:
  grep crashed with SIGILL in __kernel_vsyscall()

Status in grep package in Ubuntu:
  New

Bug description:
  Binary package hint: grep

  I don't know more info about this crash. I just updated my system,
  reboot PC and send this report.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: grep 2.6.3-3
  ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
  Uname: Linux 2.6.35-19-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Sat Sep  4 02:30:39 2010
  ExecutablePath: /bin/grep
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100630.1)
  ProcCmdline: grep 3000
  ProcEnviron:
   LANGUAGE=ru_RU
   LANG=ru_RU.utf8
   SHELL=/bin/bash
  Signal: 4
  SourcePackage: grep
  StacktraceTop:
   __kernel_vsyscall ()
   __write_nocancel () at ../sysdeps/unix/syscall-template.S:82
   _IO_new_file_write (f=0x26a4e0, data=0xb7466000, n=134)
   new_do_write (fp=0x26a4e0, 
   _IO_new_do_write (fp=0x26a4e0,
  Title: grep crashed with SIGILL in __kernel_vsyscall()
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/629850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1389430] Re: egrep dependency on /bin/bash prevents egrep use in .bash_profile

[Matthias Klose]

fixed in wily

** Changed in: grep (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1389430

Title:
  egrep dependency on /bin/bash prevents egrep use in .bash_profile

Status in grep package in Ubuntu:
  Fix Released

Bug description:
  julian@ip-10-0-2-91:~$ head -n 1 /bin/egrep
  #!/bin/bash

  This prevents egrep from being used in .bash_profile, since that
  creates in infinite loop.

  Debian's latest grep package has that fixed:

  grep (2.20-4) unstable; urgency=medium

* d/patches/05-grep-wrapper-sh.patch: egrep and fgrep wrap scripts use sh
  instead of bash. The patch also removes the possible call ./grep (looking
  for it in the working directory) (Closes: #762427, #762917).

  Please update the grep package in Ubuntu, and in Utopic in particular.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1389430/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 530189] Re: grep crashed with SIGSEGV

[Matthias Klose]

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/530189

Title:
  grep crashed with SIGSEGV

Status in grep package in Ubuntu:
  New

Bug description:
  Binary package hint: grep

  Description:  Ubuntu lucid (development branch)
  Release:  10.04

  ProblemType: Crash
  Architecture: i386
  Date: Mon Mar  1 18:45:33 2010
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /bin/grep
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 
(20091020.3)
  Package: grep 2.5.4-4
  ProcAttrCurrent: unconfined (enforce)
  ProcCmdline: grep -v ^wlan0=
  ProcEnviron:
   
  ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
  SegvAnalysis:
   Segfault happened at: 0x80545a7: mov0xc(%ebx),%esi
   PC (0x080545a7) ok
   source "0xc(%ebx)" (0x000b) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: grep
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: grep crashed with SIGSEGV
  Uname: Linux 2.6.32-13-generic i686
  UserGroups: root

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/530189/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

[Rafael David Tinoco]

Last test I did was to see if IB DHCP would get the BROADCAST flag on IB
interfaces. It did. Now, I removed:

ip->client->config->bootp_broadcast_always = 1;

from setup_ib_interface (when preparing for DHCP REQUEST), so I could
check if the option:

bootp-broadcast-always

from the config file (added by this patch also) to check if it makes a
difference.



## without bootp-broadcast-always

tcpdump: listening on ib0, link-type LINUX_SLL (Linux cooked), capture size 
65535 bytes
13:34:47.376362 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP 
(17), length 328)
0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request, length 
300, htype 32, hlen 0, xid 0x5f7f9774, Flags [none] (0x)
  Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
Hostname Option 12, length 5: "dixie"
Parameter-Request Option 55, length 13:
  Subnet-Mask, BR, Time-Zone, Default-Gateway
  Domain-Name, Domain-Name-Server, Option 119, Hostname
  Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route
  NTP
Client-ID Option 61, length 17: hardware-type 56, 
30:3a:30:30:3a:30:30:3a:34:38:3a:46:45:3a:38:30
END Option 255, length 0
PAD Option 0, length 0, occurs 15

## with bootp-broadcast-always

13:51:10.735292 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP 
(17), length 328)
0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request, length 
300, htype 32, hlen 0, xid 0x5bbf492d, Flags [Broadcast] (0x8000)
  Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
Hostname Option 12, length 5: "dixie"
Parameter-Request Option 55, length 13:
  Subnet-Mask, BR, Time-Zone, Default-Gateway
  Domain-Name, Domain-Name-Server, Option 119, Hostname
  Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route
  NTP
Client-ID Option 61, length 17: hardware-type 56, 
30:3a:30:30:3a:30:30:3a:34:38:3a:46:45:3a:38:30
END Option 255, length 0
PAD Option 0, length 0, occurs 15



So the following statement in dhclient.conf

interface "ib0" {
send dhcp-client-identifier = "80:00:00:48:FE:80";
bootp-broadcast-always;
}

Is working good also.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1529815

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  In Progress

Bug description:
  
  DHCP client is sending discover with Unicast type request for the offer, in 
this configuration of IB to ETH through a relay we need the type to be 
broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  
  DHCP CLIENT (IPoIB) 
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1543061] Re: error sis630 smbus SIS630 comp. bus not detected

[Enzo Eduardo Polo Cheva]

This message appears always in the startup

El 02/09/2016 6:25, Timo Aaltonen  escribió:
>
> error where? logs look normal 
>
> ** Changed in: xorg (Ubuntu) 
>    Status: New => Incomplete 
>
> -- 
> You received this bug notification because you are subscribed to the bug 
> report. 
> https://bugs.launchpad.net/bugs/1543061 
>
> Title: 
>    error sis630 smbus SIS630 comp. bus not detected 
>
> Status in xorg package in Ubuntu: 
>   Incomplete 
>
> Bug description: 
>   I can't eliminate this error booting 
>
>   ProblemType: Bug 
>   DistroRelease: Ubuntu 14.04 
>   Package: xorg 1:7.7+1ubuntu8.1 
>   ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 
>   Uname: Linux 3.13.0-77-generic x86_64 
>   ApportVersion: 2.14.1-0ubuntu3.19 
>   Architecture: amd64 
>   CompizPlugins: No value set for 
> `/apps/compiz-1/general/screen0/options/active_plugins' 
>   CompositorRunning: None 
>   Date: Mon Feb  8 05:38:41 2016 
>   DistUpgraded: 2016-02-07 05:44:05,129 DEBUG Running PostInstallScript: 
> './xorg_fix_proprietary.py' 
>   DistroCodename: trusty 
>   DistroVariant: ubuntu 
>   ExtraDebuggingInterest: Yes, including running git bisection searches 
>   GraphicsCard: 
>    Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA 
> Display Adapter [1039:6330] (prog-if 00 [VGA controller]) 
>  Subsystem: Lenovo Device [17aa:100a] 
>   Lsusb: 
>    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 
>    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 
>    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 
>    Bus 002 Device 002: ID 0583:a000 Padix Co., Ltd (Rockfire) MaxFire G-08XU 
> Gamepad 
>    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 
>   MachineType: LENOVO 8818D32 
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic 
> root=UUID=62f4682b-64b2-4bd4-91ba-01835d984df7 ro quiet splash vt.handoff=7 
>   Renderer: Software 
>   SourcePackage: xorg 
>   UpgradeStatus: Upgraded to trusty on 2016-02-07 (0 days ago) 
>   dmi.bios.date: 08/07/2006 
>   dmi.bios.vendor: LENOVO 
>   dmi.bios.version: 40KT24A 
>   dmi.board.name: GA-8S661FXM-775 
>   dmi.board.vendor: LENOVO 
>   dmi.chassis.type: 3 
>   dmi.chassis.vendor: LENOVO 
>   dmi.modalias: 
> dmi:bvnLENOVO:bvr40KT24A:bd08/07/2006:svnLENOVO:pn8818D32:pvr:rvnLENOVO:rnGA-8S661FXM-775:rvr:cvnLENOVO:ct3:cvr:
>  
>   dmi.product.name: 8818D32 
>   dmi.sys.vendor: LENOVO 
>   version.compiz: compiz N/A 
>   version.ia32-libs: ia32-libs N/A 
>   version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 
>   version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A 
>   version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 
>   version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel 
> 2:2.99.910-0ubuntu1.6 
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
> 1:1.0.10-1ubuntu2 
>   xserver.bootTime: Mon Feb  8 05:00:35 2016 
>   xserver.configfile: default 
>   xserver.devices: 
>    input    Power Button KEYBOARD, id 6 
>    input    Power Button KEYBOARD, id 7 
>    input    AT Translated Set 2 keyboard KEYBOARD, id 8 
>    input    ImPS/2 Logitech Wheel Mouse MOUSE, id 9 
>   xserver.errors: 
>    open /dev/dri/card0: No such file or directory 
>    AIGLX: reverting to software rendering 
>   xserver.logfile: /var/log/Xorg.0.log 
>   xserver.version: 2:1.15.1-0ubuntu2.7 
>
> To manage notifications about this bug go to: 
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1543061/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1543061

Title:
   error sis630 smbus SIS630 comp. bus not detected

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I can't eliminate this error booting

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Feb  8 05:38:41 2016
  DistUpgraded: 2016-02-07 05:44:05,129 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA 
Display Adapter [1039:6330] (prog-if 00 

[Touch-packages] [Bug 1542375] Re: Get rid of the formFactor context property

[Launchpad Bug Tracker]

** Branch linked: lp:~osomon/webapps-core/remove-formFactor

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1542375

Title:
  Get rid of the formFactor context property

Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu.Web plugin exposes a 'formFactor' context property, whose
  value is either "mobile" or "desktop".

  It relies on QGuiApplication::platformName() to determine the so-called "form 
factor". With convergence, this approach is flawed, because the same device can 
change from a phone to a desktop and back to phone during the lifetime of the 
application.
  Form factor is not even a concept that should be used for dynamic layout of 
the application.

  This property is not (and has never been) publicly documented, so it
  should be fine to remove it.

  In most cases, where the value of that property was used, we can use one of 
the following:
   - wide VS narrow mode
   - presence of a mouse/touchpad/touchscreen/keyboard
   - can a given QML plugin be dynamically loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1542375/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1540490] Re: app icons getting their top cut off (Ubuntu Touch)

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 - 8.11+16.04.20160208-0ubuntu1

---
unity8 (8.11+16.04.20160208-0ubuntu1) xenial; urgency=medium

  [ Albert Astals Cid ]
  * LVWPH: Reset to initial values when list is empty (LP: #1540490)
  * Make LazyImage qmltest less flaky on CI

  [ Andrea Cimitan ]
  * Make LazyImage qmltest less flaky on CI

  [ CI Train Bot ]
  * Resync trunk.
  * Update translation template

  [ Michael Terry ]
  * Display the current user's real name on the tablet lockscreen. (LP:
#1536714)

 -- Michał Sawicz   Mon, 08 Feb 2016
09:38:00 +

** Changed in: unity8 (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1540490

Title:
  app icons getting their top cut off (Ubuntu Touch)

Status in Canonical System Image:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  I'm having this issue since OTA-9. I can easily reproduce this with 100% 
success rate now. Here's how to reproduce:
  1. go to apps scope
  2. scroll down to bottom (or at least till the first few rows go out of the 
screen)
  3. scroll SLIGHTLY up so that the header with the search option (magnifying 
glass icon) appears
  4. search for something
  5. press the back button to get back to apps scope
  6. scroll down through the app list
  7. pull and release to refresh
  8. scroll down through the app list again
  9. search for something again

  expected to happen:
  nothing weird

  happened instead:
  at step 4. the app icon(s) appearing in the search result have their top cut 
off
  https://launchpadlibrarian.net/235945153/screenshot20160201_195047392.png
  at step 5. now the apps in the top row of apps scope also have their top cut 
off
  https://launchpadlibrarian.net/235945187/screenshot20160201_195056867.png
  at step 6. still top row has top cut off
  at step 7. still top row has top cut off
  at step 8. normality is restored
  at step 9. same tops getting cut off as in step 4.

  Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9)

  NOTE: I was having the opposite kinda issue (one extra blank row
  before actual results and in apps scope, see Bug #1539606) previously
  but it's apparently gone after restarting the device once.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540490/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536714] Re: Fix the user login experience on the greeter on a tablet

[Michał Sawicz]

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => 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/1536714

Title:
  Fix the user login experience on the greeter on a tablet

Status in The Avila project:
  Fix Committed
Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu RTM:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  In Progress

Bug description:
  The current UX for tablets or when converged with a mouse attached is
  a bit of a placeholder showing the default phablet user.

  We need to support two modes of the greeter that scales according to
  the available input devices. The first one is one that works across
  mobile and tablet devices in non-mouse connected / touch-centric
  state. Unlocking with no mouse connected would be exactly as it is
  today on the phone, which displays the Infographic until you touch the
  screen, and then you get a message that says "swipe to unlock" If you
  don't have a pin code set, the screen unlocks. if you have a pincode
  set, the touch pincode-entry pad appears.

  If a mouse is connected, however, you get the more "desktop-friendly"
  greeter with the infographic, user-name and password entry field (just
  like what we have today) on tablet.  If the user taps or clicks into
  the password edit box, the OSK is popped up (unless an external
  keyboard is also attached). If no password or pincode has been set,
  then instead of the password entry field, you would instead have a
  "login" button that clears the greeter.

  On a tablet with mouse connected and no pincode set, the user could
  either swipe away the greeter or tap on the login button. If the user
  has a password/pincode set and attempts to swipe away the greeter, we
  should put up a hint message asking the user to enter their
  password/pincode to continue.

  This incremental enhancement to recognize the mouse is more consistent
  with convergence because tablets are mobile devices, and if no mouse
  is attached, we should follow a touch-centric approach. In a mouse-
  connected state, we can assume the user will be favoring that device.

  ===

  Immediate problem: "phablet" name on the greeter login list. A bigger
  refactoring of the greeter for bigger screens will follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1536714/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1533835] Re: Support direct access to the location panel

[Jonas G. Drange]

** Branch linked: lp:~jonas-drange/ubuntu-system-settings/lp1533835

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-location in
Ubuntu.
https://bugs.launchpad.net/bugs/1533835

Title:
  Support direct access to the location panel

Status in Canonical System Image:
  Confirmed
Status in indicator-location package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  When selection Location settings from the indicator we want to go
  directly to the Location panel per the design at

  
https://docs.google.com/document/edit?hgd=1=1810KDpFl2Mxsn1z3wehPU9pkbS6R6o-j1-pmYpkYb7A#heading=h.jh8j7gb6bo0s

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533835/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1389309] Re: /etc/init.d/ondemand assumes cpu0 exists and is online

[bugproxy]

** Tags removed: targetmilestone-inin1504
** Tags added: targetmilestone-inin1604

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1389309

Title:
  /etc/init.d/ondemand assumes cpu0 exists and is online

Status in sysvinit package in Ubuntu:
  New

Bug description:
  I have a ppc64el box with a couple of processors disabled because of
  hardware issues:

  # head /proc/cpuinfo 
  processor : 16

  The ondemand initscript assumes cpu0 is online:

  AVAILABLE="/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors"

  I also opened a bug on Debian and proposed a patch that seems to fix
  this problem. It is bug#767942

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767942

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1389309/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 350341] Re: egrep crashed with SIGSEGV in free()

[Matthias Klose]

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/350341

Title:
  egrep crashed with SIGSEGV in free()

Status in grep package in Ubuntu:
  New

Bug description:
  Binary package hint: grep

  Only Update Manager was running when I saw this crash report, although
  the updates (to pidgin-libnotify, xserver-common and xserver-xorg-
  core) were applied successfully.

  ProblemType: Crash
  Architecture: i386
  Dependencies:
   libgcc1 1:4.3.3-5ubuntu4andersk1
   gcc-4.3-base 4.3.3-5ubuntu4andersk1
   libpcre3 7.8-2ubuntu1
   findutils 4.4.0-2ubuntu3
   libc6 2.9-4ubuntu4
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /bin/egrep
  NonfreeKernelModules: nvidia
  Package: grep 2.5.3~dfsg-6ubuntu1
  ProcCmdline: egrep --text -v -f /tmp/logcheck.yIRuhi/ignore/openvpn 
/tmp/logcheck.yIRuhi/checked
  ProcEnviron:
   SHELL=/bin/sh
   PATH=(custom, no user)
  Signal: 11
  SourcePackage: grep
  StacktraceTop:
   free () from /lib/tls/i686/cmov/libc.so.6
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: egrep crashed with SIGSEGV in free()
  Uname: Linux 2.6.29-020629-generic i686
  UserGroups: adm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/350341/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 274645] Re: egrep crashed with SIGSEGV in re_compile_pattern()

[Matthias Klose]

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/274645

Title:
  egrep crashed with SIGSEGV in re_compile_pattern()

Status in grep package in Ubuntu:
  New

Bug description:
  Binary package hint: grep

  From apport

  ProblemType: Crash
  Architecture: i386
  Dependencies:
   libgcc1 1:4.3.2-1ubuntu8
   gcc-4.3-base 4.3.2-1ubuntu8
   libpcre3 7.6-2.1ubuntu1
   findutils 4.4.0-2ubuntu3
   libc6 2.8~20080505-0ubuntu6
  DistroRelease: Ubuntu 8.10
  ExecutablePath: /bin/egrep
  Package: grep 2.5.3~dfsg-5ubuntu2
  ProcAttrCurrent: unconfined
  ProcCmdline: egrep ^[^#]*LC_ALL= /etc/default/locale
  ProcEnviron:
   PATH=/sbin:/usr/sbin:/bin:/usr/bin
   LANG=en_CA.UTF-8
  Signal: 11
  SourcePackage: grep
  StacktraceTop:
   ?? () from /lib/tls/i686/cmov/libc.so.6
   re_compile_pattern () from /lib/tls/i686/cmov/libc.so.6
   ?? ()
   ?? ()
   __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
  Title: egrep crashed with SIGSEGV in re_compile_pattern()
  Uname: Linux 2.6.27-4-generic i686
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/274645/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1544108] [NEW] grep's test long-pattern-perf fails on powerpc when built with optimization

[Matthias Klose]

Public bug reported:

grep's test long-pattern-perf fails on powerpc when built with
optimization

see
https://launchpad.net/ubuntu/+source/grep/2.22-1/+build/8281007

** Affects: grep (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: ftbfs

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1544108

Title:
  grep's test long-pattern-perf fails on powerpc when built with
  optimization

Status in grep package in Ubuntu:
  Confirmed

Bug description:
  grep's test long-pattern-perf fails on powerpc when built with
  optimization

  see
  https://launchpad.net/ubuntu/+source/grep/2.22-1/+build/8281007

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1544108/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity-system-compositor (Ubuntu)
   Status: New => Confirmed

** Branch linked: lp:~afrantzis/mir/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 1523573] Re: Doesn't let you share several images

[Bill Filler]

@tiagosh
same is true for videos and contacts, should handle multi-select in both 
directions

-- 
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/1523573

Title:
  Doesn't let you share several images

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in gallery-app package in Ubuntu:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Using ota8 on bq devices, the share menu is disabled when more than
  one image is selected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523573/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1523573] Re: Doesn't let you share several images

[Bill Filler]

@tiagosh
Please add support for handling multiple photos shared from 
gallery/camera->messaging-app

-- 
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/1523573

Title:
  Doesn't let you share several images

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in gallery-app package in Ubuntu:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Using ota8 on bq devices, the share menu is disabled when more than
  one image is selected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523573/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543179] Re: image 242 no audio bt devices connect

[Christopher Townsend]

Any chance this is being looked at?  I can confirm that BT audio is
busted on Mako using rc-proposed.  In my use case, I have my phone
paired with my car and when I either dial a number or accept an incoming
call, the call is not heard over the speaker in the car.  After this
happens, my phone usually reconnects with my car.

Thanks!

-- 
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/1543179

Title:
  image 242 no audio bt devices connect

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. Flash the latest daily rc-proposed image to a phone
  2. Connect a bluetooth headset to the phone
  3. Connect a speaker to the phone.

  EXPECTED:
  I expect the devices to connect and play audio

  ACTUAL:
  Speakers just connect and instantly disconnect

  Headsets don't get trusted and disconnect instantly, Once you trust it
  and then turn the headset off and back on again it connect can accept
  calls but the audio from both the mic and earpiece don't function.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543179/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1523573] Re: Doesn't let you share several images

[Bill Filler]

@tiagosh
And also when pressing the attach button in messaging-app it should set the 
multipleFiles flag to true in the content-hub api such that it works in this 
direction as well

-- 
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/1523573

Title:
  Doesn't let you share several images

Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in gallery-app package in Ubuntu:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  Using ota8 on bq devices, the share menu is disabled when more than
  one image is selected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1523573/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1271973] Re: Results from U1db.Query contain only indexed fields, not the whole document

[Christian Dywan]

** Changed in: u1db-qt
   Importance: Medium => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to u1db-qt in Ubuntu.
https://bugs.launchpad.net/bugs/1271973

Title:
  Results from U1db.Query contain only indexed fields, not the whole
  document

Status in U1DB Qt/ QML:
  Confirmed
Status in u1db-qt package in Ubuntu:
  Confirmed

Bug description:
  Whe using U1db.Index and U1db.Query to query information from a U1db,
  the results returned from a Query should be the entire document, and
  instead they are a subset of the document containing only the indexed
  fields.

  Example code below. Observe that the left-hand ListView is showing
  results, but those results are not the whole content of each document;
  instead, they contain only the fields in the index. Index queries
  should return the whole document. Otherwise queries are almost
  useless; they are designed so that you can get a list of the documents
  which match the query fields, not just the query fields which match
  the query fields. Returning the value of the fields which match the
  query is pointless: you must already know those values in order to
  construct the query in the first place.

  import QtQuick 2.0
  import U1db 1.0 as U1db

  Rectangle {
  width: 600
  height: 300

  U1db.Database { id: db; path: "u1db-broken-query"; }
  U1db.Document {
  database: db; docId: "doc1"; create: true
  defaults: { "topfield": { "subfield": "subvalue1" }, "toplevelfield": 
"topvalue1" }
  }
  U1db.Document {
  database: db; docId: "doc2"; create: true
  defaults: { "topfield": { "subfield": "subvalue2" }, "toplevelfield": 
"topvalue2" }
  }
  U1db.Index {
  database: db
  id: by_topfield_subfield
  expression: ["topfield.subfield"]
  }
  U1db.Index {
  database: db
  id: by_toplevelfield
  expression: ["toplevelfield.subfield"]
  }
  U1db.Query { id: qtopsub; index: by_topfield_subfield; query: [{subfield: 
"*"}] }
  U1db.Query { id: qtoplevel; index: by_toplevelfield; query: 
[{toplevelfield: "*"}] }

  Text {
  id: h1
  width: parent.width / 2
  height: 50
  anchors.left: parent.left
  anchors.top: parent.top
  horizontalAlignment: Text.AlignHCenter
  text: "ListModel on topfield.subfield"
  }

  ListView {
  anchors.top: h1.bottom
  anchors.left: parent.left
  width: h1.width
  anchors.bottom: parent.bottom
  model: qtopsub
  delegate: Text {
  text: JSON.stringify(model.contents)
  }
  }

  Text {
  id: h2
  width: parent.width / 2
  height: 50
  anchors.right: parent.right
  anchors.top: parent.top
  horizontalAlignment: Text.AlignHCenter
  text: "ListModel on toplevelfield"
  }

  ListView {
  anchors.top: h2.bottom
  anchors.right: parent.right
  width: h2.width
  anchors.bottom: parent.bottom
  model: qtoplevel
  delegate: Text {
  text: JSON.stringify(model.contents)
  }
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/u1db-qt/+bug/1271973/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1311148] Re: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostp

[Iulia]

*** This bug is a duplicate of bug 1286836 ***
https://bugs.launchpad.net/bugs/1286836

Also happened the same after upgrading from 14.10 to 15.04 . Unity is
not starting automatically either

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/1311148

Title:
  package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to
  install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch:
  no) is not co-installable with libpostproc52 which has multiple
  installed instances

Status in libav package in Ubuntu:
  Confirmed

Bug description:
  Immediately after 14.04 LTS upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpostproc52 6:0.8.10-0ubuntu0.13.10.1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  AptOrdering:
   libpostproc52: Install
   python-smbc: Install
   libpostproc52: Configure
   python-smbc: Configure
  Architecture: amd64
  Date: Tue Apr 22 07:11:33 2014
  Dependencies:
   gcc-4.9-base 4.9-20140406-0ubuntu1
   libavutil51 6:0.8.10-0ubuntu0.13.10.1 [origin: unknown]
   libc6 2.19-0ubuntu6
   libgcc1 1:4.9-20140406-0ubuntu1
   multiarch-support 2.19-0ubuntu6
  DpkgTerminalLog:
   dpkg: error processing archive 
/var/cache/apt/archives/libpostproc52_6%3a0.git20120821-4_amd64.deb (--unpack):
libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not 
co-installable with libpostproc52 which has multiple installed instances
  DuplicateSignature: 
package:libpostproc52:6:0.8.10-0ubuntu0.13.10.1:libpostproc52:amd64 
6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 
which has multiple installed instances
  ErrorMessage: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not 
co-installable with libpostproc52 which has multiple installed instances
  InstallationDate: Installed on 2012-12-26 (482 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: libav
  Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to 
install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not 
co-installable with libpostproc52 which has multiple installed instances
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1311148/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1544159] [NEW] Remove "phone settings" link from network indicator non-phone devices

[Jean-Baptiste Lallement]

Public bug reported:

On devices without phone capabilities remove the link "Cellular
Settings" from the network indicator

** Affects: canonical-devices-system-image
 Importance: High
 Status: Confirmed

** Affects: indicator-network (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: qa-frieza

** Also affects: indicator-network (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => ww04-2016

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1544159

Title:
  Remove "phone settings" link from network indicator non-phone devices

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  New

Bug description:
  On devices without phone capabilities remove the link "Cellular
  Settings" from the network indicator

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544159/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1544157] Re: lxc exec not working in xenial

[Stéphane Graber]

** Package changed: lxc (Ubuntu) => lxd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1544157

Title:
  lxc exec not working in xenial

Status in lxd package in Ubuntu:
  New

Bug description:
  My host is on the very latest Xenial as of yesterday Feb9,2016

  My work flow has been...
  $ newgrp lxd
  $ lxc images:ubuntu/xenial/amd64 xen
  $ lxc start xen
  $ lxc exec xen -- /bin/bash

  at the moment, the image creation works, i can list my images - and it says 
they are running
  however, upon exec i'm not logged onto the shell - no output, even if i pass 
--verbose=true

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1544157/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1482317] Re: Unify code that turns screen on when a notification happens

[Michael Terry]

** Also affects: powerd (Ubuntu)
   Importance: Undecided
   Status: New

** Branch linked: lp:~mterry/powerd/no-screen-on

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => Fix Released

** Also affects: telephony-service (Ubuntu)
   Importance: Undecided
   Status: New

** Branch linked: lp:~mterry/telephony-service/no-screen-on

** Changed in: telephony-service (Ubuntu)
   Status: New => In Progress

** Changed in: telephony-service (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

** Changed in: powerd (Ubuntu)
   Status: New => In Progress

** Changed in: powerd (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

-- 
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/1482317

Title:
  Unify code that turns screen on when a notification happens

Status in powerd package in Ubuntu:
  In Progress
Status in telephony-service package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Right now, there are several places we ask USC to turn the screen on
  when a notification happens:

  - powerd for SMS, USSD, and incoming calls
  - telephony-service for MMS and telephony messages

  And we don't seem to be turning them on for ubuntu-push notifications,
  but we should, right?  Following the pattern above, we'd have ubuntu-
  push itself turn the screen on, for a third location.

  We don't turn the screen on at all for notifications that don't come
  via those sources.  For example, the following command line doesn't
  turn the screen on, but I think it should:

  gdbus call --session --dest org.freedesktop.Notifications --object-
  path /org/freedesktop/Notifications --method
  org.freedesktop.Notifications.Notify '' 0 '' 'Hello' 'World' '[]' '{}'
  0

  It feels weird to have telephony-service turning the screen on.
  Logically, it is just emitting a notification.  The presentation of
  that notification is up to a higher layer (maybe we're on a raspberry
  pi2 and we present notifications as LED morse code or whatever).  It
  just makes sense that unity8, which is drawing the notification, is
  the one that knows that the screen needs to be on.  It also knows what
  form factor we are in (I assume we only want to turn screen on for
  phones/tablets, not desktops).

  So I'm proposing that we unify all those places into one code path in
  unity8 that can turn the screen on when a notification is received.

  (This is a breakout bug from bug 1426115.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1482317/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

[Barry Warsaw]

** Tags added: client

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system-image in Ubuntu.
https://bugs.launchpad.net/bugs/1508081

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  In Progress
Status in Ubuntu system image:
  New
Status in system-image package in Ubuntu:
  New
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508081/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1542375] Re: Get rid of the formFactor context property

[Bill Filler]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Bill Filler (bfiller)

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1542375

Title:
  Get rid of the formFactor context property

Status in Canonical System Image:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu.Web plugin exposes a 'formFactor' context property, whose
  value is either "mobile" or "desktop".

  It relies on QGuiApplication::platformName() to determine the so-called "form 
factor". With convergence, this approach is flawed, because the same device can 
change from a phone to a desktop and back to phone during the lifetime of the 
application.
  Form factor is not even a concept that should be used for dynamic layout of 
the application.

  This property is not (and has never been) publicly documented, so it
  should be fine to remove it.

  In most cases, where the value of that property was used, we can use one of 
the following:
   - wide VS narrow mode
   - presence of a mouse/touchpad/touchscreen/keyboard
   - can a given QML plugin be dynamically loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1542375/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1544173] [NEW] [tablet] login entry field should default to numeric keyboad if passcode set

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

On tablet, if you select a 4-digit passcode for security type, the
greeter shows a text entry field, tapping in it brings up the regular
keyboard layout. In this case, we should set the input hint for the
entry field to force the numeric keyboard to appear.

** Affects: avila
 Importance: Undecided
 Status: New

** Affects: canonical-devices-system-image
 Importance: High
 Assignee: Michał Sawicz (saviq)
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: High
 Assignee: Michael Terry (mterry)
 Status: Triaged

-- 
[tablet] login entry field should default to numeric keyboad if passcode set
https://bugs.launchpad.net/bugs/1544173
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to unity8 in Ubuntu.

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1540397] Re: Mouse and touchpad settings are not applied

[Michael Terry]

*** This bug is a duplicate of bug 1540398 ***
https://bugs.launchpad.net/bugs/1540398

** Branch linked: lp:~mterry/unity8/new-input-proxies

** Changed in: unity8 (Ubuntu)
   Status: Triaged => In Progress

** This bug has been marked a duplicate of bug 1540398
   Mouse and touchpad settings are not applied

-- 
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/1540397

Title:
  Mouse and touchpad settings are not applied

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  We need to apply the mouse and touchpad settings from gsettings.

  We've now set the mouse speed up, but we need to hook up all the rest.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity8 8.11+15.04.20160122-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.17.2-0ubuntu1.3touch1
  Architecture: armhf
  Date: Mon Feb  1 15:39:00 2016
  InstallationDate: Installed on 2016-01-30 (2 days ago)
  InstallationMedia: Ubuntu 15.04 - armhf (20160130-020304)
  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/1540397/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1536714] Re: Fix the user login experience on the greeter on a tablet

[Michał Sawicz]

Will close this bug and track a bigger redesign elsewhere.

-- 
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/1536714

Title:
  Fix the user login experience on the greeter on a tablet

Status in The Avila project:
  Fix Committed
Status in Canonical System Image:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu RTM:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  In Progress

Bug description:
  The current UX for tablets or when converged with a mouse attached is
  a bit of a placeholder showing the default phablet user.

  We need to support two modes of the greeter that scales according to
  the available input devices. The first one is one that works across
  mobile and tablet devices in non-mouse connected / touch-centric
  state. Unlocking with no mouse connected would be exactly as it is
  today on the phone, which displays the Infographic until you touch the
  screen, and then you get a message that says "swipe to unlock" If you
  don't have a pin code set, the screen unlocks. if you have a pincode
  set, the touch pincode-entry pad appears.

  If a mouse is connected, however, you get the more "desktop-friendly"
  greeter with the infographic, user-name and password entry field (just
  like what we have today) on tablet.  If the user taps or clicks into
  the password edit box, the OSK is popped up (unless an external
  keyboard is also attached). If no password or pincode has been set,
  then instead of the password entry field, you would instead have a
  "login" button that clears the greeter.

  On a tablet with mouse connected and no pincode set, the user could
  either swipe away the greeter or tap on the login button. If the user
  has a password/pincode set and attempts to swipe away the greeter, we
  should put up a hint message asking the user to enter their
  password/pincode to continue.

  This incremental enhancement to recognize the mouse is more consistent
  with convergence because tablets are mobile devices, and if no mouse
  is attached, we should follow a touch-centric approach. In a mouse-
  connected state, we can assume the user will be favoring that device.

  ===

  Immediate problem: "phablet" name on the greeter login list. A bigger
  refactoring of the greeter for bigger screens will follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1536714/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1540522] Re: vfat support broken in initramfs

[Scott Moser]

Hi.
This should be fixed in the latest image maas-images and in the ubuntu archive 
with 0.122ubuntu3
The maas image is numbered 20160210 that has the fix. 
https://gist.github.com/smoser/2cec72d243404a72fdb5 will show you what your 
maas images are:
  maas-dump-image-status my-maas-name | grep xenial
  ubuntu/xenial amd64/hwe-w 20160210 daily True


Deployment of xenial with maas will require a curtin that is >= revision 324.
  http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/revision/324

You can get a trunk version of curtin from the daily ppa at
https://launchpad.net/~curtin-dev/+archive/ubuntu/daily

** Changed in: maas-images
   Status: New => Fix Released

** Changed in: maas-images
   Importance: Undecided => High

** Changed in: maas-images
 Assignee: (unassigned) => Scott Moser (smoser)

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Scott Moser (smoser)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1540522

Title:
  vfat support broken in initramfs

Status in MAAS:
  Invalid
Status in maas-images:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  when it try to mount the fat32 for the efi it failed with the
  following error : [  117.627721] FAT-fs (sda1): IO charset iso8859-1
  not found

  
  which is due to the missing module : nls_iso8859_1

  workaround is : to apt-get install linux-generic
  than the module is properly loaded.

  here's the error that I've seen in the boot.log : 
   can't create directory '/root/lib/modules': Read-only file system

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1540522/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

[Ken VanDine]

Summarizing plan:

system-image-dbus adds a "force" (or some other name) method to the
update which would set allowOverGsm to true

system-image-dbus should proxy the started signal from udm

system-settings will display "Download now" button if the started signal
hasn't been received, which will call the force method on s-i-d to force
the download regardless of network type.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system-image in Ubuntu.
https://bugs.launchpad.net/bugs/1508081

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  In Progress
Status in Ubuntu system image:
  New
Status in system-image package in Ubuntu:
  New
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508081/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1528321] Re: Everything hangs when coming out of fullscreen in chrome

[Starbeamrainbowlabs]

@checoimg I agree it is better in the latest beta (version 49.0.2623.39
(Official Build) beta (64-bit)), but it still isn't fixed. It's
happening one time in three for me still.

Here's my test video (bump the quality before testing):
https://www.youtube.com/watch?v=WG8y1_y-kPw

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1528321

Title:
  Everything hangs when coming out of fullscreen in chrome

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  If I have hardware acceleration enabled in my chrome settings (which
  it is automatically), my entire desktop freezes 9 times out of 10 when
  I come out of fullscreen mode. It doesn't matter whether it's with F11
  or a video on a site such as YouTube. Strangely enough, the audio
  keeps on going.

  If I disable hardware acceleration, then I don't experience this
  issue, but I can't use WebGL. My CPU usage also goes through the roof
  , heating my laptop up, and reducing my battery life.

  If I switch to a different tty with CTRL+ALT and login it says
  that it can't connect to the X server or something. I don't
  particularly want to cause a another hang to find out either as a
  forceful shutdown may damage my filesystem(s).

  I'm using Ubuntu Desktop 15.10 wily.

  Here's my uname -a:

  Linux Snowflake 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC
  2015 x86_64 x86_64 x86_64 GNU/Linux

  Here's my chrome version information:

  Google Chrome 48.0.2564.48 (Official Build) beta (64-bit)
  Revision  
ae7f323bae9104a543ae39d46453b712de27d15d-refs/branch-heads/2564@{#362}
  OSLinux 
  Blink 537.36 (@ae7f323bae9104a543ae39d46453b712de27d15d)
  JavaScriptV8 4.8.271.9
  Flash 20.0.0.248
  User AgentMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like 
Gecko) Chrome/48.0.2564.48 Safari/537.36

  Can anyone help me please?

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Dec 21 18:43:27 2015
  DistUpgraded: 2015-10-17 12:39:24,649 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-352, 352.63, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04ca]
   NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2015-09-14 (98 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=dd320194-8d8a-491f-89af-a4997c775049 ro quiet splash nomodest 
init=/sbin/e4rat-preload
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-17 (65 days ago)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0FXK2Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0FXK2Y:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Mon Dec 21 07:14:24 2015
  xserver.configfile: default
  xserver.errors:
   
  

[Touch-packages] [Bug 1536714] Re: Fix the user login experience on the greeter on a tablet

[Michał Sawicz]

** No longer affects: ubuntu-ux

-- 
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/1536714

Title:
  Fix the user login experience on the greeter on a tablet

Status in The Avila project:
  Fix Committed
Status in Canonical System Image:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu RTM:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  In Progress

Bug description:
  The current UX for tablets or when converged with a mouse attached is
  a bit of a placeholder showing the default phablet user.

  We need to support two modes of the greeter that scales according to
  the available input devices. The first one is one that works across
  mobile and tablet devices in non-mouse connected / touch-centric
  state. Unlocking with no mouse connected would be exactly as it is
  today on the phone, which displays the Infographic until you touch the
  screen, and then you get a message that says "swipe to unlock" If you
  don't have a pin code set, the screen unlocks. if you have a pincode
  set, the touch pincode-entry pad appears.

  If a mouse is connected, however, you get the more "desktop-friendly"
  greeter with the infographic, user-name and password entry field (just
  like what we have today) on tablet.  If the user taps or clicks into
  the password edit box, the OSK is popped up (unless an external
  keyboard is also attached). If no password or pincode has been set,
  then instead of the password entry field, you would instead have a
  "login" button that clears the greeter.

  On a tablet with mouse connected and no pincode set, the user could
  either swipe away the greeter or tap on the login button. If the user
  has a password/pincode set and attempts to swipe away the greeter, we
  should put up a hint message asking the user to enter their
  password/pincode to continue.

  This incremental enhancement to recognize the mouse is more consistent
  with convergence because tablets are mobile devices, and if no mouse
  is attached, we should follow a touch-centric approach. In a mouse-
  connected state, we can assume the user will be favoring that device.

  ===

  Immediate problem: "phablet" name on the greeter login list. A bigger
  refactoring of the greeter for bigger screens will follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1536714/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 711061] Re: [MIR] openjpeg

[Will Cooke]

Just to reiterate, this is vital for us in 16.04.  Please let me know
what we can do to help make sure this happens.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openjpeg in Ubuntu.
https://bugs.launchpad.net/bugs/711061

Title:
  [MIR] openjpeg

Status in openjpeg package in Ubuntu:
  Confirmed

Bug description:
  libopenjpeg should be included in main because compiling poppler with
  --enable-openjpeg in debian/rules gives poppler greater functionality
  (please see bug 710412). Since this change to /debian/rules adds
  libopenjpeg as a build-dep to poppler, which is in main, libopenjpeg
  must also be in main.

  Main inclusion requirements:

  1. It is already in the universe.

  2. The package is a new build-dep, and has a large user base (think
  evince).

  3. Searching http://secunia.com/advisories/search/ for libopenjpeg
  gave zero results.

  4. Libopenjpeg has no current Ubuntu bugs 
(https://bugs.launchpad.net/ubuntu/maverick/+source/openjpeg)
   in the Debian bug tracking system libopenjpeg has 1 open bug 
(http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=libopenjpeg2), this is an 
encoding bug, but the main use for this package will be decoding.
   Libopenjpeg does not require any configuration or debconf questions.

  5. N/A

  6. All build-deps are already included in main.

  7. I am afraid that this is a bit over my head, hopefully someone else
  could ensure that this package meets the requirments here. Based on
  its long inclusion in Debian and Ubuntu I think that it should be
  alright here.

  8.This is a fairly simple program not needed too much maintenance, as
  shown by the bug reports.

  9. The package title and description seem to be in order.

  
  My only final comments are that I am sorry this may not be quite the normal 
MIR, but I am just a member of bug control, not a dev. Also, any help and 
advise along the way would be much appreciated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjpeg/+bug/711061/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1544173] Re: [tablet] login entry field should default to numeric keyboad if passcode set

[Michael Terry]

** Branch linked: lp:~josharenson/unity8/wide-greeter-shows-pin-pad-for-
pins

-- 
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/1544173

Title:
  [tablet] login entry field should default to numeric keyboad if
  passcode set

Status in The Avila project:
  In Progress
Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  On tablet, if you select a 4-digit passcode for security type, the
  greeter shows a text entry field, tapping in it brings up the regular
  keyboard layout. In this case, we should set the input hint for the
  entry field to force the numeric keyboard to appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1544173/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543031] Re: No notification when new OTA is available

[John McAleely]

I believe this is also happening on other devices post OTA 9?

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-download-manager in
Ubuntu.
https://bugs.launchpad.net/bugs/1543031

Title:
  No notification when new OTA is available

Status in The Avila project:
  New
Status in Canonical System Image:
  New
Status in ubuntu-download-manager package in Ubuntu:
  New

Bug description:
  frieza 7

  I flashed build 7, there is build 8 on system-image.u.c but I didn't
  receive a notification. client.log and u-d-m attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1543031/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1543872] Re: Desktop streched across both screens

[sjp333]

In 16.04 the stretching issue is resolved. However, the display manager
is still a bit buggy. It switched to mirrored displays when I tried to
turn on both displays. However after exiting the manager and re-opening
it. I was able to get both displays working correctly. Another issue is
that the other display is a HDTV and I need to adjust the underscan on
it. When I do that it also underscans the laptop's screen.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1543872

Title:
  Desktop streched across both screens

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Intel HD graphics controls the internal display and the nvidia card
  handles the display port out. When trying to utilize a dual monitor
  setup the output of the desktop looks like its been stretched across
  both displays. It appears like the resolution is very low and the
  mouse pointer is incorrectly calibrated with its location on the
  screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  352.79  Wed Jan 13 16:17:53 
PST 2016
   GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:

  CurrentDesktop: Unity
  Date: Tue Feb  9 19:50:31 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.2.0-17-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-25-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-27-generic, x86_64: installed
   nvidia-352, 352.79, 4.2.0-25-generic, x86_64: installed
   nvidia-352, 352.79, 4.2.0-27-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1909]
   NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1909]
  InstallationDate: Installed on 2015-07-29 (195 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150727)
  MachineType: Hewlett-Packard HP ZBook 15
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-27-generic 
root=UUID=d0125fd5-5a86-4280-94b5-e38def1ab992 ro quiet nosplash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L70 Ver. 01.08
  dmi.board.name: 1909
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 94.51
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL70Ver.01.08:bd04/10/2014:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10303:rvnHewlett-Packard:rn1909:rvrKBCVersion94.51:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 15
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.65+git20151026.c745e541-0ubuntu0ricotz~wily
  version.libgl1-mesa-dri: libgl1-mesa-dri 
11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~wily
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~wily
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.99+git20150521.d64a13eb-0ubuntu0ricotz
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151202.da9ad388-0ubuntu0sarvatt
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20150926.1ff13a92-0ubuntu0sarvatt
  xserver.bootTime: Tue Feb  9 19:31:46 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1543872/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1529815] Re: InfiniBand DHCP flow with PRA and DHCP relay not working

[Ubuntu Foundations Team Bug Bot]

The attachment "trusty_isc-dhcp_4.2.4-7ubuntu12.5.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1529815

Title:
  InfiniBand DHCP flow with PRA and DHCP relay not working

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Trusty:
  In Progress
Status in isc-dhcp source package in Wily:
  In Progress
Status in isc-dhcp source package in Xenial:
  In Progress

Bug description:
  
  DHCP client is sending discover with Unicast type request for the offer, in 
this configuration of IB to ETH through a relay we need the type to be 
broadcast.

  The issue is that when using dhclient from the client on Ubuntu (and only on 
Ubuntu) with MOFED or inbox driver, we see that that DHCP server offers in 
unicast instead of broadcast. It seems there is no way to correct this from the 
client side using dhclient configuration file.
  this issue exist even when we use always-broadcast statement in configuration 
file.

  in other vendors we see that discover request type is broadcast.
  attached pcap files from working (other vendor) and not working (Ubuntu) 
clients.

  
  DHCP CLIENT (IPoIB) 
  Ubuntu 14.04  kernel 3.13.0-74
  Mellanox OFED 3.1-1.0.3 or inbox driver
  isc-dhcp-client  4.2.4-7ubuntu12.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1529815/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1544108] Re: grep's test long-pattern-perf fails on powerpc when built with optimization

[Matthias Klose]

http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21826

** Also affects: grep
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1544108

Title:
  grep's test long-pattern-perf fails on powerpc when built with
  optimization

Status in grep:
  New
Status in grep package in Ubuntu:
  Fix Released

Bug description:
  grep's test long-pattern-perf fails on powerpc when built with
  optimization

  see
  https://launchpad.net/ubuntu/+source/grep/2.22-1/+build/8281007

To manage notifications about this bug go to:
https://bugs.launchpad.net/grep/+bug/1544108/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1544108] Re: grep's test long-pattern-perf fails on powerpc when built with optimization

[Matthias Klose]

this is just an unstable test

** Changed in: grep (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1544108

Title:
  grep's test long-pattern-perf fails on powerpc when built with
  optimization

Status in grep:
  New
Status in grep package in Ubuntu:
  Fix Released

Bug description:
  grep's test long-pattern-perf fails on powerpc when built with
  optimization

  see
  https://launchpad.net/ubuntu/+source/grep/2.22-1/+build/8281007

To manage notifications about this bug go to:
https://bugs.launchpad.net/grep/+bug/1544108/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1544157] [NEW] lxc exec not working in xenial

[kevin gunn]

Public bug reported:

My host is on the very latest Xenial as of yesterday Feb9,2016

My work flow has been...
$ newgrp lxd
$ lxc images:ubuntu/xenial/amd64 xen
$ lxc start xen
$ lxc exec xen -- /bin/bash

at the moment, the image creation works, i can list my images - and it says 
they are running
however, upon exec i'm not logged onto the shell - no output, even if i pass 
--verbose=true

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1544157

Title:
  lxc exec not working in xenial

Status in lxc package in Ubuntu:
  New

Bug description:
  My host is on the very latest Xenial as of yesterday Feb9,2016

  My work flow has been...
  $ newgrp lxd
  $ lxc images:ubuntu/xenial/amd64 xen
  $ lxc start xen
  $ lxc exec xen -- /bin/bash

  at the moment, the image creation works, i can list my images - and it says 
they are running
  however, upon exec i'm not logged onto the shell - no output, even if i pass 
--verbose=true

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1544157/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1544173] Re: [tablet] login entry field should default to numeric keyboad if passcode set

[Michał Sawicz]

** Package changed: unity-greeter (Ubuntu) => unity8 (Ubuntu)

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => High

** Changed in: unity8 (Ubuntu)
   Status: New => Triaged

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

-- 
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/1544173

Title:
  [tablet] login entry field should default to numeric keyboad if
  passcode set

Status in The Avila project:
  New
Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  On tablet, if you select a 4-digit passcode for security type, the
  greeter shows a text entry field, tapping in it brings up the regular
  keyboard layout. In this case, we should set the input hint for the
  entry field to force the numeric keyboard to appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1544173/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1544159] Re: Remove "phone settings" link from network indicator on devices without phone capabilities

[Jean-Baptiste Lallement]

** Summary changed:

- Remove "phone settings" link from network indicator non-phone devices
+ Remove "phone settings" link from network indicator on devices without phone 
capabilities

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1544159

Title:
  Remove "phone settings" link from network indicator on devices without
  phone capabilities

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  New

Bug description:
  On devices without phone capabilities remove the link "Cellular
  Settings" from the network indicator

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544159/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1520369] Re: 3G not working when wifi is selected, even if no wifi available

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: indicator-network (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1520369

Title:
  3G not working when wifi is selected, even if no wifi available

Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Hi I am using a Meizu MX4 with the OTA 8 update. If I try to select
  3G "in the open" with no wifi signal (but wifi turned on) the phone
  doesn’t switch to 3G and stays on wifi. I understand that auto
  switching between 3G and wifi is a good thing and wifi should take
  priority,  but if there is no wifi is available in the area then I
  would have thought the phone should switch to 3G when  selected.

  Note, the old MX4 problem with wifi dropping out (from the same router) when 
moving around a building, and not reconnecting is still occurring with the OTA 
8 update. This is not serious but very annoying.  The only way to reconnect is 
to turn wifi off then back on again.  
  If the phone knows it is connected to the internet, then looses connection, 
could you not just treat this in the same way as the first time it connected in 
the building. I guess the same idea could also help for the above 3G problem. 
In this case if wifi on, but no signal then 3G takes priority even if the wifi 
is on. 

  Thanks for your hard work, love Ubuntu Touch and have also flashed a
  Nexus 4 to try some stuff of my own.

  Regards

  Dave H

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1520369/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1526548] Re: grep 2.22 infinite loop

[Launchpad Bug Tracker]

This bug was fixed in the package grep - 2.22-1ubuntu2

---
grep (2.22-1ubuntu2) xenial; urgency=medium

  * Mark tests/long-pattern-perf as expensive, instead of lowering the
build options (patch taken from upstream).

 -- Matthias Klose   Wed, 10 Feb 2016 17:22:07 +0100

** Changed in: grep (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1526548

Title:
  grep 2.22 infinite loop

Status in grep package in Ubuntu:
  Fix Released

Bug description:
  Christian Boltz discovered that grep 2.22 can be sent into an infinite
  loop. 2.21 does not have this issue. The reproducer we have available
  so far:

  grep -obUa -P '\x04\x08\x00profile\x00\x07' /etc/apparmor.d/cache/*

  Probably one of the files in that directory will report infinite
  output in the style of:

  # grep -obUa -P '\x04\x08\x00profile\x00\x07' cache--usr.sbin.smbldap-useradd 
 
  16profile
  27801profile
  27801profile
  27801profile
  27801profile
  27801profile
  ...

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1526548/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1544173] Re: [tablet] login entry field should default to numeric keyboad if passcode set

[Michał Sawicz]

** Changed in: canonical-devices-system-image
   Status: New => Triaged

** Changed in: avila
   Status: New => In Progress

** Changed in: avila
 Assignee: (unassigned) => Michał Sawicz (saviq)

-- 
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/1544173

Title:
  [tablet] login entry field should default to numeric keyboad if
  passcode set

Status in The Avila project:
  In Progress
Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  On tablet, if you select a 4-digit passcode for security type, the
  greeter shows a text entry field, tapping in it brings up the regular
  keyboard layout. In this case, we should set the input hint for the
  entry field to force the numeric keyboard to appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1544173/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1443869] Re: [Edge Education] New wizard in Vivid doesn't excercise indicator gesture

[Michael Terry]

** Branch linked: lp:~mterry/unity8/tutorial-redesign

** 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/1443869

Title:
  [Edge Education] New wizard in Vivid doesn't excercise indicator
  gesture

Status in Ubuntu UX:
  Fix Committed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Test case.
  - Flash the device with a recent Vivid image.
  - Complete the wizard.
  - Go through edges demo.

  Expected result.
  - Edges demo exercises the indicator gesture.

  Actual result.
  - Indicators aren't opened.

  current build number: 184
  device name: krillin
  channel: ubuntu-touch/devel-proposed

  
  --- UX Comment ---

  Expected behaviour as per new OOBE and Edge education specification
  (https://docs.google.com/document/d/1pZ-Ro--
  2eaRzjZKNRoYAeDvQHMkCuyvVuPFWFQfPW4s/edit#heading=h.56fezu5i5j0h)

  Top edge education overlay will be trigger when the following is true:

  - 30 seconds after the Left edge gesture is acted on
  - 3 seconds of user's inactivity on the screen

  If the user discovered by himself the notification bar, the Top Edge
  coachmark will not be displayed at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1443869/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp