[Touch-packages] [Bug 1556120] Re: Include Breton and Welsh in Ubuntu Touch

[Jean-Baptiste Lallement]

Actually both language packs have been added (Brezhoneg and  Cymraeg)
They use around 1MB of disk space.

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

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

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

Title:
  Include Breton and Welsh in Ubuntu Touch

Status in Canonical System Image:
  Fix Committed
Status in langpack-o-matic:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Confirmed
Status in ubuntu-touch-meta package in Ubuntu RTM:
  New

Bug description:
  In Ubuntu Translators mailing list there has been requests to include
  Breton and Welsh in Ubuntu Touch.

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

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

[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Johan Tol]

In /lib/udev/hwdb.d/60-keyboard.hwdb I see the following related to scan
code 150:

# Dell Latitude microphone mute
evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnLatitude*
# Dell Precision microphone mute
evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*
 KEYBOARD_KEY_150=f20  # Mic mute toggle, should be micmute

Is that related to the error message?

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1597598] Re: a11y-profile-manager-indicator has wrong scale in Ubiquity with HiDPI display.

[Kai-Heng Feng]

When using gtk_icon_theme_load_icon_for_scale() instead of
gtk_icon_info_load_icon(), this issue is gone. But I suspect it's not to
root cause.

There's a commit in newer GTK:
"001598a icon theme: Improve loading of unthemed files"
which takes desired_scale into account, but cherry-pick the commit into 
Xenial's gtk does not solve the issue.

** Patch added: "hidpi.patch"
   
https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1597598/+attachment/4692577/+files/hidpi.patch

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

Title:
  a11y-profile-manager-indicator has wrong scale in Ubiquity with HiDPI
  display.

Status in libindicator package in Ubuntu:
  New

Bug description:
  When using a laptop with HiDPI display, the a11y-profile-manager-
  indicator scaled too large in Ubiquity.

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

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

[Touch-packages] [Bug 1597598] [NEW] a11y-profile-manager-indicator has wrong scale in Ubiquity with HiDPI display.

[Kai-Heng Feng]

Public bug reported:

When using a laptop with HiDPI display, the a11y-profile-manager-
indicator scaled too large in Ubiquity.

** Affects: libindicator (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "a11y.png"
   https://bugs.launchpad.net/bugs/1597598/+attachment/4692575/+files/a11y.png

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

Title:
  a11y-profile-manager-indicator has wrong scale in Ubiquity with HiDPI
  display.

Status in libindicator package in Ubuntu:
  New

Bug description:
  When using a laptop with HiDPI display, the a11y-profile-manager-
  indicator scaled too large in Ubiquity.

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

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

[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Johan Tol]

I have exactly the same message for my Dell Latitude E6540.

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 301508] Re: Wish: add "-u" option to /etc/default/ntpdate

[Launchpad Bug Tracker]

[Expired for ntp (Ubuntu) because there has been no activity for 60
days.]

** Changed in: ntp (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Wish: add "-u" option to /etc/default/ntpdate

Status in ntp package in Ubuntu:
  Expired

Bug description:
  Binary package hint: ntpdate

  The "-u" option is useful with firewall, I think.

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

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

[Touch-packages] [Bug 1576442] Re: Crash while upgrading to Ubuntu 16.04

[Launchpad Bug Tracker]

[Expired for sysvinit (Ubuntu) because there has been no activity for 60
days.]

** Changed in: sysvinit (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Crash while upgrading to Ubuntu 16.04

Status in sysvinit package in Ubuntu:
  Expired

Bug description:
  On package sysv-rc: post-install-script returns with errorcode 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sysv-rc 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Fri Apr 29 00:13:45 2016
  DuplicateSignature: package:sysv-rc:2.88dsf-59.3ubuntu2:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationDate: Installed on 2010-10-08 (2028 days ago)
  InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: sysvinit
  Title: package sysv-rc 2.88dsf-59.3ubuntu2 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (0 days ago)

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

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

[Touch-packages] [Bug 1307037] Re: ntp causes time to accelerate

[Launchpad Bug Tracker]

[Expired for ntp (Ubuntu) because there has been no activity for 60
days.]

** Changed in: ntp (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  ntp causes time to accelerate

Status in ntp package in Ubuntu:
  Expired

Bug description:
  1)
  Description:Ubuntu 14.04 LTS
  Release:14.04

  2)
  ntp:
    Installed: (none)
    Candidate: 1:4.2.6.p5+dfsg-3ubuntu2
    Version table:
   1:4.2.6.p5+dfsg-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  3) normal time evolution
  4) accelerating/decelerating time

  My clock time accelerates and decelerates.  Everything is normal in
  the bios, however in Trusty I get this strange behavior.  I launched a
  remote session and recorded the following from time.is in a chrome
  browser session to show the problem:

  https://www.youtube.com/watch?v=BpQ7kdkA34g

  Note the speedup of the clock (esp at the 20 sec mark) and the major
  drift

  If I uninstall ntp, I don't experience these problems.I was
  changing ntp servers before I purged ntp, but I don't see why this
  would happen with any server.  I also was having problems with my
  computer starting (ram timing issues?) but it works fine now, and I
  wasn't having this problem in the bios, only in ubuntu.  ACPI also was
  disabled in the bios.  And the only kernel option I'm passing is
  "text".   Sorry I can't give any other information, but if you have
  any questions, I can try my best to answer them.

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

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

[Touch-packages] [Bug 1597581] Re: package qtcore4-l10n 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to install/upgrade: package qtcore4-l10n is not ready for configuration cannot configure (current

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package qtcore4-l10n 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to
  install/upgrade: package qtcore4-l10n is not ready for configuration
  cannot configure (current status `half-installed')

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  on boot after splash screen

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: qtcore4-l10n 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1
  ProcVersionSignature: Ubuntu 3.19.0-64.72-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-64-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  Date: Wed Jun 29 15:53:56 2016
  Dependencies:
   
  DuplicateSignature: 
package:qtcore4-l10n:4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1:package 
qtcore4-l10n is not ready for configuration  cannot configure (current status 
`half-installed')
  ErrorMessage: package qtcore4-l10n is not ready for configuration  cannot 
configure (current status `half-installed')
  InstallationDate: Installed on 2016-06-29 (1 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: qt4-x11
  Title: package qtcore4-l10n 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to 
install/upgrade: package qtcore4-l10n is not ready for configuration  cannot 
configure (current status `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1597581/+subscriptions

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

[Touch-packages] [Bug 1597583] [NEW] error in initramfs-tools on login

[Aman Mishra]

Public bug reported:

error in  initramfs-tools on login

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Jun 29 17:12:46 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-04-22 (68 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  error in  initramfs-tools on login

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  error in  initramfs-tools on login

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 29 17:12:46 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-22 (68 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1597583/+subscriptions

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

[Touch-packages] [Bug 1597583] Re: error in initramfs-tools on login

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  error in  initramfs-tools on login

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  error in  initramfs-tools on login

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 29 17:12:46 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-22 (68 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1597583/+subscriptions

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

[Touch-packages] [Bug 1577734] Re: Backport packages for 14.04.5 lts-xenial stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted libxrandr into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libxrandr/2:1.5.0-1~trusty1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libxrandr (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  Fix Committed
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Committed
Status in x11proto-core source package in Trusty:
  New
Status in x11proto-randr source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

[Touch-packages] [Bug 1597581] [NEW] package qtcore4-l10n 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to install/upgrade: package qtcore4-l10n is not ready for configuration cannot configure (curre

[Richard Lofgren]

Public bug reported:

on boot after splash screen

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: qtcore4-l10n 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1
ProcVersionSignature: Ubuntu 3.19.0-64.72-generic 3.19.8-ckt22
Uname: Linux 3.19.0-64-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.8
Architecture: amd64
Date: Wed Jun 29 15:53:56 2016
Dependencies:
 
DuplicateSignature: 
package:qtcore4-l10n:4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1:package 
qtcore4-l10n is not ready for configuration  cannot configure (current status 
`half-installed')
ErrorMessage: package qtcore4-l10n is not ready for configuration  cannot 
configure (current status `half-installed')
InstallationDate: Installed on 2016-06-29 (1 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1.1
 apt  1.0.9.7ubuntu4.2
SourcePackage: qt4-x11
Title: package qtcore4-l10n 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to 
install/upgrade: package qtcore4-l10n is not ready for configuration  cannot 
configure (current status `half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package vivid

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

Title:
  package qtcore4-l10n 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to
  install/upgrade: package qtcore4-l10n is not ready for configuration
  cannot configure (current status `half-installed')

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  on boot after splash screen

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: qtcore4-l10n 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1
  ProcVersionSignature: Ubuntu 3.19.0-64.72-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-64-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.8
  Architecture: amd64
  Date: Wed Jun 29 15:53:56 2016
  Dependencies:
   
  DuplicateSignature: 
package:qtcore4-l10n:4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1:package 
qtcore4-l10n is not ready for configuration  cannot configure (current status 
`half-installed')
  ErrorMessage: package qtcore4-l10n is not ready for configuration  cannot 
configure (current status `half-installed')
  InstallationDate: Installed on 2016-06-29 (1 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1.1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: qt4-x11
  Title: package qtcore4-l10n 4:4.8.6+git64-g5dc8b2b+dfsg-3~ubuntu6.1 failed to 
install/upgrade: package qtcore4-l10n is not ready for configuration  cannot 
configure (current status `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1597581/+subscriptions

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

[Touch-packages] [Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

[Seth Arnold]

Tarifa on #ubuntu-server reported problems with his ssh service. The
steps he found that he needed to make sshd start reliably:

systemctl disable ssh
update-rc.d ssh disable
systemctl enable ssh

"Then add both Wants=network-online.target & Requires=network-
online.target in an ssh service override."

** Changed in: openssh (Ubuntu)
   Status: Expired => New

** Tags added: systemd-boot

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

Title:
  ssh will not start at boot:  systemctl status ssh -> output is listed
  as failed 255.

Status in openssh package in Ubuntu:
  New

Bug description:
  Using apt I have reinstalled and purged both ssh and openssh-server. 
  apt-get remove --purge ssh openssh-server
  reinstalled
  updated
  and on boot the ctl status is failed 255

  After much forum research and attempts to default solutions, the final word 
was that reinstall usually fixes this issue. 
  With the issue usually stemming from ssh service trying to start before 
network services are available.

  Currently I have no logs available with 
  journalctl -u sshd | tail -100

  I can provide info pertaining to this on request.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ssh 1:6.9p1-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 24 14:27:55 2016
  InstallationDate: Installed on 2016-02-09 (15 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1577734] Please test proposed package

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted x11proto-randr into trusty-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/x11proto-
randr/1.5.0-1~trusty1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  New
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Committed
Status in x11proto-core source package in Trusty:
  New
Status in x11proto-randr source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

[Touch-packages] [Bug 1577734] Re: Backport packages for 14.04.5 lts-xenial stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-3.8 into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-3.8/1:3.8-2ubuntu3~trusty3 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags removed: verification-failed

** Tags added: verification-needed

** Changed in: x11proto-randr (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  Backport packages for 14.04.5 lts-xenial stack

Status in libdrm package in Ubuntu:
  Invalid
Status in libxrandr package in Ubuntu:
  Invalid
Status in llvm-toolchain-3.8 package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in x11proto-randr package in Ubuntu:
  Invalid
Status in libdrm source package in Trusty:
  Fix Committed
Status in libxrandr source package in Trusty:
  New
Status in llvm-toolchain-3.8 source package in Trusty:
  Fix Committed
Status in x11proto-core source package in Trusty:
  New
Status in x11proto-randr source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  xenial lts stack needs newer libdrm and llvm-toolchain-3.8 backported
  from 16.04

  libdrm 2.4.64 -> 2.4.67 major changes:
  - WIP

  [Test case]

  libdrm: run a desktop session, see that things still work

  llvm-3.8: new for trusty, needed by mesa for radeon/amdgpu

  [Regression potential]

  slim to none

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

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

[Touch-packages] [Bug 1591503] Re: missing fcitx-mozc.mo

[Gunnar Hjalmarsson]

I installed fcitx-mozc 2.17.2116.102+gitfd0f5b34+dfsg-1ubuntu1.1 from
xenial-proposed.

$ dpkg -L fcitx-mozc | grep mo$
/usr/share/locale/ja/LC_MESSAGES/fcitx-mozc.mo
/usr/share/locale/zh_TW/LC_MESSAGES/fcitx-mozc.mo
/usr/share/locale/zh_CN/LC_MESSAGES/fcitx-mozc.mo

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-zh-hans-base
in Ubuntu.
https://bugs.launchpad.net/bugs/1591503

Title:
  missing fcitx-mozc.mo

Status in langpack-o-matic:
  Triaged
Status in language-pack-ja-base package in Ubuntu:
  Confirmed
Status in language-pack-zh-hans-base package in Ubuntu:
  Confirmed
Status in language-pack-zh-hant-base package in Ubuntu:
  Confirmed
Status in mozc package in Ubuntu:
  Won't Fix
Status in mozc source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  For some at this point unknown reason, langpack-o-matic refuses to include 
fcitx-mozc.mo in the applicable language-pack-*-base packages. As a workaround 
for now this proposed upload rebuilds mozc with export NO_PKG_MANGLE=1 so the 
translations are not stripped.

  [Test Case]
  After install, check for the existence of e.g.

   /usr/share/locale/ja/LC_MESSAGES/fcitx-mozc.mo
   /usr/share/locale/zh_CN/LC_MESSAGES/fcitx-mozc.mo

  [Regression Potential]
  Low.

  [Original description]
  $ LANG=C dpkg -S fcitx-mozc.mo
  dpkg-query: no path found matching pattern *fcitx-mozc.mo*

  Please include it for upcoming next translation update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/langpack-o-matic/+bug/1591503/+subscriptions

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

[Touch-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

[Hui Wang]

I did not reproduce this problem yet.

But according to the comment #48, when problem happens, neither sound
notification nor vibration work. So it does not look like a pulseaudio
problem since the vibration does not work too.

When problem happens, to check if media-hub-server sends playing request
to pulseaudio or not, we can do test as below:

1) Problem happens

2) Use adb shell to connect the phone with computer

3) set environment variable according to 
/usr/share/upstart/sessions/pulseaudio.conf
e.g.:
$export PULSE_SCRIPT=/etc/pulse/touch.pa
$export PULSE_CLIENTCONFIG=/etc/pulse/touch-client.conf
$export PULSE_PROP='media.role=multimedia'
$export PULSE_PLAYBACK_CORK_STALLED=1 

4) $pulseaudio --kill && pulseaudio --start - --log-
target=file:/tmp/a.txt

5) check /tmp/a.txt, make sure the pulseaudio starts successfully

6) $cp /tmp/a.txt /tmp/before-sms.txt

7) send a text message to your phone, trigger a sms event

8) $cp /tmp/b.txt /tmp/after-sms.txt

9) comparing before-sms.txt and after-sms.txt (or upload them to LP)


If this problem does not happen, the diff should be like the attached file, we 
can see the media-hub-server really sent playing request to pulseaudio when 
receiving text message.


** Attachment added: "diff-of-without-this-problem.txt"
   
https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1544477/+attachment/4692518/+files/diff-of-without-this-problem.txt

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

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

  UPDATE: Screenshots get silent too.

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

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

[Touch-packages] [Bug 1541730] Re: all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot

[Barry Kolts]

Can't seem to edit my own post. Disregard the last paragraph about
reboot-required, I need to look into that a little further,

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

Title:
  all cron.daily scripts are skipped on a day when unattended-upgrades
  triggers a reboot

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  When unattended-upgrades is configured to apply updates and
  Unattended-Upgrade::Automatic-Reboot is set to "true", and there's an
  update that requires a reboot, you'll find that none of the scripts in
  /etc/cron.daily were executed on that day.  (To be more precise, none
  that are alphabetically after the 'apt' script, which is most of
  them.)

  It would be good if unattended-upgrades did the reboot from
  /etc/cron.daily/zzz-unattended-upgrade-reboot, so the other scripts
  get a chance to run first.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2.4
  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
  Date: Thu Feb  4 10:02:38 2016
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to trusty on 2014-09-16 (505 days ago)
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 2014-10-09T09:04:05

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1541730/+subscriptions

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

[Touch-packages] [Bug 1271633] Re: libclick needs API for determining the current supported framework(s)

[hari]

** Changed in: click (Ubuntu)
 Assignee: Colin Watson (cjwatson) => hari (prahmana)

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

Title:
  libclick needs API for determining the current supported framework(s)

Status in click package in Ubuntu:
  Fix Released

Bug description:
  unity-scope-click needs to know the currently supported framework(s)
  to send to the click apps server in app searches.

  from cjwatson's email on Jan 22 2014:

  Please file a bug on the Ubuntu click package about this so that I don't
  forget.  I think it would be best to add an API for this as part of the
  libclick work.  In the meantime the following Python code or equivalent
  should be safe (although please include a reference to any packages
  where you've open-coded this in your bug report on click):

def installed_frameworks():
ext = ".framework"
for name in os.listdir("/usr/share/click/frameworks"):
if name.endswith(ext):
yield name[:-len(ext)]

  The corresponding bug for the scope is here:
  https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1267190

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

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

[Touch-packages] [Bug 1541730] Re: all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot

[Barry Kolts]

I have noticed this too, at least with logrotate not running. I thought this 
was because the reboot happens right after, or during, unattended-upgrades. So 
I set the time to reboot to 7:30 AM in /etc/apt/apt.conf/50unattended-upgrades 
to give the rest of cron.daily time to run. However logrotate still did not 
run. And I assume neither did the rest of cron.daily. I believe 
unattended-upgrades issues 
shutdown -r 07:30
in my case. So I wondered if the impending shutdown was blocking logrotate, and 
the rest of cron.daily. However searching the Internet I could not confirm that 
theory. So I too think cron.daily/apt should be the last thing run in 
cron.daily.
One more issue that may be related. After the reboot /var/run/reboot-required 
and /var/run/reboot-required.pkgs still exist and the "*System restart 
required" message appearers  at logoin.

** Attachment added: "Apport report and 50unatended-upgrades file"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1541730/+attachment/4692505/+files/apport.unattended-upgrades.fttw5049.apport

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

Title:
  all cron.daily scripts are skipped on a day when unattended-upgrades
  triggers a reboot

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  When unattended-upgrades is configured to apply updates and
  Unattended-Upgrade::Automatic-Reboot is set to "true", and there's an
  update that requires a reboot, you'll find that none of the scripts in
  /etc/cron.daily were executed on that day.  (To be more precise, none
  that are alphabetically after the 'apt' script, which is most of
  them.)

  It would be good if unattended-upgrades did the reboot from
  /etc/cron.daily/zzz-unattended-upgrade-reboot, so the other scripts
  get a chance to run first.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2.4
  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
  Date: Thu Feb  4 10:02:38 2016
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to trusty on 2014-09-16 (505 days ago)
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 2014-10-09T09:04:05

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1541730/+subscriptions

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

[Touch-packages] [Bug 1541730] Re: all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot

[Launchpad Bug Tracker]

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  all cron.daily scripts are skipped on a day when unattended-upgrades
  triggers a reboot

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  When unattended-upgrades is configured to apply updates and
  Unattended-Upgrade::Automatic-Reboot is set to "true", and there's an
  update that requires a reboot, you'll find that none of the scripts in
  /etc/cron.daily were executed on that day.  (To be more precise, none
  that are alphabetically after the 'apt' script, which is most of
  them.)

  It would be good if unattended-upgrades did the reboot from
  /etc/cron.daily/zzz-unattended-upgrade-reboot, so the other scripts
  get a chance to run first.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2.4
  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
  Date: Thu Feb  4 10:02:38 2016
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to trusty on 2014-09-16 (505 days ago)
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 2014-10-09T09:04:05

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1541730/+subscriptions

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

[Touch-packages] [Bug 1595348] Re: Web browser dissapears too often

[Launchpad Bug Tracker]

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

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

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

Title:
  Web browser dissapears too often

Status in Canonical System Image:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  M10 tablet.. Ever since upgrading to OTA11 the web browser has become
  very annoying.

  If I have, say, 3 tabs on and close one, the browser often
  dissapears.. I restart it from the apps page and it restarts with all
  the original tabs, including thecone I tried to close.. I can then
  closecit again, usually without furthervincident.

  Or I might open the bookmarks and try to open a new tab, and the
  browser vanishes.

  Or, very occasionally I click on a search engine result and 'poof' she
  is gone!

  Anyone care to nominate a suitable log file?

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

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

[Touch-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic

[Konrad Zapałowicz]

Thanks. The keyboard that yo use is a Bluetooth Classic one and we do
not have much issues with those. Of course, there are high chances that
we have not been performing our tests using the same model that you use
but just for you to know that the issues with BT Classic are something
unusual.

I will check if we are able to link the Intel error to the performance
penalty.

Best

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

Title:
  Bluetooth mouse laggy and erratic

Status in bluez package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios
  A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves
  erratically (laggy, jumpy). The problem happens after a few (sometimes
  one) suspend and resume. I am attaching below some info on my system.
  Thank you.

  cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep 
-i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth
  Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac 
Wireless Network Adapter [14e4:43b1] (rev 03)
   Subsystem: Dell Device [1028:0019]
   Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0c45:670c Microdia
  Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
  Bus 001 Device 002: ID 0a5c:216f Broadcom Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [2.174367] Bluetooth: Core ver 2.20
  [2.174669] Bluetooth: HCI device and connection manager initialized
  [2.174792] Bluetooth: HCI socket layer initialized
  [2.174795] Bluetooth: L2CAP socket layer initialized
  [2.175449] Bluetooth: SCO socket layer initialized
  [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.542421] Bluetooth: BNEP filters: protocol multicast
  [3.542425] Bluetooth: BNEP socket layer initialized
  [3.551641] Bluetooth: RFCOMM TTY layer initialized
  [3.551649] Bluetooth: RFCOMM socket layer initialized
  [3.551654] Bluetooth: RFCOMM ver 1.11
  [   26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   26.569287] Bluetooth: HIDP socket layer initialized
  [   26.576971] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15
  [   26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [   72.448281] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16
  [   72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 2994.842547] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17
  [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 
lmp_ver=06 lmp_subver=220e
  [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [ 3811.777260] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20
  [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option 
usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr 
binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal 
dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel 
hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc 
glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd 
v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms 
intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic 
cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress 
snd_hda_intel 

[Touch-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

[Ren]

Sorry Anupam : I did not want to pollute this complex bug-id
but I wished to point out that the problem may be an 
interaction between several applications that use the system
sound notifications. I believe it...
I decided to create notifications at the same time for
several applications (sms/calendar/and clock alarm)
at 19:30 every day...
Soon, the sound becomes mute after first notification...
or after a while...

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

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

  UPDATE: Screenshots get silent too.

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

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

[Touch-packages] [Bug 1595569] Re: Indicators panel doesn't close when turning screen off

[Michał Sawicz]

** Changed in: canonical-devices-system-image
   Status: Confirmed => 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/1595569

Title:
  Indicators panel doesn't close when turning screen off

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Steps:
  * open indicators
  * press power button to turn the screen off
  * press power button to turn the screen on

  Expected:
  * greeter shown

  Current:
  * indicators panel shown

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160617-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 23 10:17:32 2016
  InstallationDate: Installed on 2016-05-06 (47 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1597535] Re: Lots of errors in console when running Chromium/Firefox with X11 forwarding.

[Seth Arnold]

As far as I can tell, there's only one warning about dbus in there that
would result from X11 forwarding:

(firefox:3257): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-hUoCogngia: Connection refused

I'm not sure what services Firefox requires via dbus but probably it can
cope without it.

Just about everything else looks like the standard garbage from mediocre
plugins and extensions and javascript errors and possible errors served
by websites. Mine has absolute gobs of similar junk, running locally.

I suspect there's nothing terribly wrong here.

Thanks

** Changed in: dbus (Ubuntu)
   Status: New => Invalid

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

Title:
  Lots of errors in console when running Chromium/Firefox with X11
  forwarding.

Status in dbus package in Ubuntu:
  Invalid

Bug description:
  See attached console transcript.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: dbus 1.6.18-0ubuntu4.3
  ProcVersionSignature: Ubuntu 3.19.0-64.72~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-64-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Wed Jun 29 14:26:21 2016
  InstallationDate: Installed on 2016-02-07 (143 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1576726] Re: [SRU] network-manager 1.2.0

[Mathew Hodson]

network-manager-pptp (1.2.0-1) unstable; urgency=medium

  * New upstream release.

 -- Michael Biebl   Sat, 23 Apr 2016 00:44:17 +0200

** Tags added: upgrade-software-version

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

** No longer affects: freeplane (Ubuntu)

** Changed in: network-manager-pptp (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager-pptp (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [SRU] network-manager 1.2.0

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in network-manager-pptp package in Ubuntu:
  Fix Released
Status in network-manager-ssh package in Ubuntu:
  Fix Released
Status in network-manager-vpnc package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released
Status in network-manager-applet source package in Xenial:
  Fix Released
Status in network-manager-openconnect source package in Xenial:
  Fix Released
Status in network-manager-openvpn source package in Xenial:
  Confirmed
Status in network-manager-ssh source package in Xenial:
  Fix Released
Status in network-manager-vpnc source package in Xenial:
  Confirmed
Status in network-manager-openconnect package in Debian:
  Fix Released

Bug description:
  [Impact]
  Xenial was released with upstream beta2 version of network-manager to keep in 
time for the release schedule, and upstream stable release has been made so 
it's time to update to it.

  [Testcase]
  After upgrading the package, user should still be able to connect to networks 
like Ethernet, Wi-Fi and VPNs.

  [Regression Potential]
  Potential of causing regression is relatively small because there is not big 
changes made during beta2 -> stable process.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576726/+subscriptions

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

[Touch-packages] [Bug 1594874] Re: App won't open from click scope if it got updated in meantime

[Michael Terry]

Looking at the MP real quick, you need the .desktop at the end of the
application:/// URL.  url-dispatcher doesn't actually look for a
.desktop file itself, but it does ignore any application: URLs that
don't end in .desktop.  It strips it before passing the appid on.

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

Title:
  App won't open from click scope if it got updated in meantime

Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  0) Have an app installed that has an available update from the store
  1) Open that app's preview in the click scope
  2) Update the app in System Settings
  3) Click "Open" in the click scope's app preview
  4) Note that the app tries to open, but never does

  Presumably, this is because the click scope is providing a full appid
  including a version.  Either the app preview needs to refresh when an
  update is installed or it needs to provide an appid without a version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1594874/+subscriptions

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

[Touch-packages] [Bug 1586232] Re: "aa-genprof /usr/sbin/nginx" crashed upon readling a line from a log

[Launchpad Bug Tracker]

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

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

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

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

Title:
  "aa-genprof /usr/sbin/nginx" crashed upon readling a line from a log

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  So (not knowing much about apparmor), to me it looks like AppArmor
  changed the word "receive" to "reweive" and thought it was a mode.

  The entire automatically generated bug report is attached.

  Here's my terminal's output:

  [root at localhost]:/etc/apparmor.d# aa-genprof /usr/sbin/nginx
  Writing updated profile for /usr/sbin/nginx.
  Setting /usr/sbin/nginx to complain mode.

  Before you begin, you may wish to check if a
  profile already exists for the application you
  wish to confine. See the following wiki page for
  more information:
  http://wiki.apparmor.net/index.php/Profiles

  Please start the application to be profiled in
  another window and exercise its functionality now.

  Once completed, select the "Scan" option below in
  order to scan the system logs for AppArmor events.

  For each AppArmor event, you will be given the
  opportunity to choose whether the access should be
  allowed or denied.

  Profiling: /usr/sbin/nginx

  [(S)can system log for AppArmor events] / (F)inish
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
  self.add_event_to_tree(event)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
  e = self.parse_event_for_tree(e)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
  raise AppArmorException(_('Log contains unknown mode %s') % rmask)
  apparmor.common.AppArmorException: 'Log contains unknown mode reweive'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "/usr/sbin/aa-genprof", line 151, in 
  lp_ret = apparmor.do_logprof_pass(logmark, passno)
    File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
  log = log_reader.read_log(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
  raise AppArmorBug(ex_msg)  # py3-only: from None
  apparmor.common.AppArmorBug: Log contains unknown mode reweive

  This error was caused by the log line:
  May 27 12:51:51 localhost kernel: [1896557.253647] audit: type=1400 
audit(1464317511.752:362): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/sbin/nginx" pid=13215 comm="nginx" laddr=45.32.xxx.xxx lport=443 
faddr=101.174.xxx.xxx fport=62972 family="inet" sock_type="stream" protocol=6 
requested_mask="receive" denied_mask="receive"

  An unexpected error occoured!

  For details, see /tmp/apparmor-bugreport-v3fjxgk8.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

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

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

[Touch-packages] [Bug 1597535] [NEW] Lots of errors in console when running Chromium/Firefox with X11 forwarding.

[Bob Cannataro]

Public bug reported:

See attached console transcript.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: dbus 1.6.18-0ubuntu4.3
ProcVersionSignature: Ubuntu 3.19.0-64.72~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-64-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Wed Jun 29 14:26:21 2016
InstallationDate: Installed on 2016-02-07 (143 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dbus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

** Attachment added: "May be due to a problem with my System Configuration.  
I'm not an expert in this area."
   
https://bugs.launchpad.net/bugs/1597535/+attachment/4692493/+files/MobaXterm_192.168.1.22_20160629_144225.txt

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

Title:
  Lots of errors in console when running Chromium/Firefox with X11
  forwarding.

Status in dbus package in Ubuntu:
  New

Bug description:
  See attached console transcript.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: dbus 1.6.18-0ubuntu4.3
  ProcVersionSignature: Ubuntu 3.19.0-64.72~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-64-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Wed Jun 29 14:26:21 2016
  InstallationDate: Installed on 2016-02-07 (143 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1568094] Re: Many error message such as "Start request repeated too quickly."

[Martin Pitt]

I backported the two patches and put a test package into
https://launchpad.net/~pitti/+archive/ubuntu/sru-test (it's the only
package there, so safe to upgrade). Feedback appreciated!

** Changed in: systemd (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Martin Pitt (pitti)

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

Title:
  Many error message such as "Start request repeated too quickly."

Status in laptop-mode-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in laptop-mode-tools source package in Xenial:
  New
Status in systemd source package in Xenial:
  In Progress

Bug description:
  * Analysis:

  The error messages are caused by a bad interaction between systemd and
  laptop-mode-tools.

  * Fixes:

  There is a fix in systemd:
  https://github.com/systemd/systemd/pull/3148

  The problem can also be fixed by updating laptop-mode-tools.

  * Symptoms:

  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: Starting Show Plymouth Boot Screen...
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: plymouth-start.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 

[Touch-packages] [Bug 1597523] Re: SRU of LXC 2.0.13(upstream bugfix release)

[Stéphane Graber]

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

** Summary changed:

- SRU of LXC 2.0.13(upstream bugfix release)
+ SRU of LXC 2.0.3 (upstream bugfix release)

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

Title:
  SRU of LXC 2.0.3 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released
Status in lxc source package in Xenial:
  New

Bug description:
  LXC upstream released LXC 2.0.2 & 2.0.3 as bugfix releases with following 
changelog:
   - apparmor: Refresh generated file
   - apparmor: add make-rslave to usr.bin.lxc-start
   - apparmor: Allow bind-mounts and {r}shared/{r}private
   - apparmor: allow mount move
   - apparmor: Update mount states handling
   - core: Drop lxc-devsetup as unneeded by current autodev
   - core: Fix redefinition of struct in6_addr
   - core: Include all lxcmntent.h function declarations on Bionic
   - c/r: c/r: use criu's "full" mode for cgroups
   - systemd: start containers in foreground when using the lxc@.service
   - templates: debian: Make sure init is installed
   - templates: oracle: Fix console login
   - templates: plamo: Fix various issues
   - templates: ubuntu: Install apt-transport-https by default
   - travis: ensure 'make install' doesn't fail
   - travis: test VPATH builds
   - upstart: Force lxc-instance to behave like a good Upstart client

  Just like Ubuntu itself, upstream releases long term support releases,
  as is 2.0 and then periodic point releases including all the
  accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This bugfix release has already been uploaded to Yakkety and
  automatically backported in the upstream PPAs for all Ubuntu releases.
  So far without any reported regression.

  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  Once the SRU hits -updates, we will be backporting this to trusty-
  backports as well, making sure we have the same version everywhere.

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

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

[Touch-packages] [Bug 1597278] Re: [Browser] Homepage as new tab page

[Olivier Tilloy]

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Triaged

** Changed in: webbrowser-app (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  [Browser] Homepage as new tab page

Status in Ubuntu UX:
  New
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  It would be great if you could implement an option to open the
  homepage when one opens a new tab. I personally don't really use the
  new tab page and would rather open my homepage in every new tab
  instead.

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

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

[Touch-packages] [Bug 1377115] Re: [browser] New tab - landscape

[Olivier Tilloy]

** No longer affects: webbrowser-app

** Changed in: webbrowser-app (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 webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1377115

Title:
  [browser] New tab - landscape

Status in Ubuntu UX:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  When going to landscape mode, the new tab use the 'Header sections'
  rather than replicating the portrait view

  UX: https://docs.google.com/a/canonical.com/presentation/d
  /1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-
  L7ve8NKLCX324/edit#slide=id.g2b47931b9_086

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

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

[Touch-packages] [Bug 1582887] Re: SRU of LXC 2.0.1 (upstream bugfix release)

[Stéphane Graber]

** Changed in: lxc (Ubuntu Trusty)
   Status: Triaged => Fix Released

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

Title:
  SRU of LXC 2.0.1 (upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  LXC upstream released LXC 2.0.1 as a bugfix release with following changelog:
   - apparmor: Also allow fstype=fuse for fuse filesystems
   - attach: adapt lxc-attach tests & add test for pty logging
   - attach: don't fail attach on failure to setup a SIGWINCH handler.
   - attach: fix a variety of lxc-attach pts handling issues
   - attach: switch console pty to raw mode (fixes ncurses-based programs)
   - attach: use raw settings of ssh for pty
   - bindings: fixed python-lxc reference to var before assignment in create()
   - bindings: set PyErr when Container.__init__ fails
   - cgfsng: defer to cgfs if needed subsystems are not available
   - cgfsng: don't require that systemd subsystem be mounted
   - core: Added missing type to keys in lxc_list_nicconfigs
   - core: Allow configuration file values to be quoted
   - core: log: remove duplicate definitons and bump buffer size
   - core: sync: properly fail on unexpected message sizes
   - core: Unshare netns after setting the userns mappings (fixes ownership of 
/proc/net)
   - core: various fixes as reported by static analysis
   - c/r: add an option to use faster inotify support in CRIU
   - c/r: rearrange things to pass struct migrate_opts all the way down
   - doc: ignore temporary files generated by doxygen
   - doc: tweak manpage generation date to be compatible with reproducible 
builds
   - doc: update MAINTAINERS
   - doc: update to translated manpages
   - init: add missing lsb headers to sysvinit scripts
   - init: don't make sysv init scripts dependant on distribution specifics
   - init: drop obsolete syslog.target from lxc.service.in
   - lxc-attach: add logging option to manpage
   - lxc-checkconfig: better render when stdout isn't a terminal
   - lxc-create: fix -B best option
   - lxc-destroy: avoid double print
   - lxc-ls: use fewer syscalls when doing ipc
   - templates: Add apt-transport-https to minbase variant of Ubuntu template
   - templates: fix a typo in the capabilities name for Gentoo (sys_resource)
   - templates: logic fix in the Centos template for RHEL7+ support
   - templates: tweak Alpine DHCP configuration to send its hostname
   - templates: tweak to network configuration of the Oracle template

  Just like Ubuntu itself, upstream releases long term support releases,
  as is 2.0 and then periodic point releases including all the
  accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  
  This bugfix release has already been uploaded to Yakkety and automatically 
backported in the upstream PPAs for all Ubuntu releases. So far without any 
reported regression.


  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  
  Once the SRU hits -updates, we will be backporting this to trusty-backports 
as well, making sure we have the same version everywhere.

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

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

[Touch-packages] [Bug 1597431] Re: lightdm could run the X server without root privileges

[Robert Ancell]

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

** This bug has been marked a duplicate of bug 1292324
   Support non-root X

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

Title:
  lightdm could run the X server without root privileges

Status in lightdm package in Ubuntu:
  New

Bug description:
  Hi,

  there is this old document:

https://wiki.ubuntu.com/X/Rootless

  that states the goal of the running the X server without root
  privileges.

  With kernel DRM this goal is now attainable.  gdm already implements
  this and it works on Ubuntu.  Here is what I have on another Ubuntu
  system where I use gdm:

  root  2588  0.0  0.0 285652  5256 ?Ssl  Jun25   0:00 
/usr/sbin/gdm3
  root  2593  0.0  0.0 267344  6448 ?Sl   Jun25   0:00 
gdm-session-worker 
  bonnaudl  2609  0.0  0.0  62320  4464 tty7 Ssl+ Jun25   0:00 
/usr/lib/gdm3/gdm-x-session 
  bonnaudl  2611  0.7  1.0 459736 165292 tty7Sl+  Jun25  43:40 
/usr/lib/xorg/Xorg vt7 -displayfd 3 

  So would it be possible to implement a similar thing in lightdm ?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu1
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jun 29 17:58:21 2016
  EcryptfsInUse: Yes
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)

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

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

[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[zanonmark]

Christopher, thanks for your time.

Please disregard comment #8, as I was just making a comparison between
two different machines - but probably that only added confusion.

Now, about the machine I reported the bug on:
* 12.04.0, 12.04.1, 12.04.2, 12.04.4: X does not start after boot, not even by 
'startx' (I attach /var/log/Xorg.0.log);
* 12.04.3 halts right after boot with a kernel panic ("Kernel panic - not 
syncing - Attempted to kill init!").

So the first distribution running X is effectively 12.04.5, with the
kernel reported above.

Thanks,
MZ

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+attachment/4692477/+files/Xorg.0.log

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

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  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 Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1558331] Re: message "The repository is insufficiently signed by key (weak digest)" is poorly worded

[Colin Law]

@angel-granados-j This bug is about the wording of the error message, not the 
fact that the error may appear.
For how to avoid it I suggest you ask elsewhere, the ubuntu-users email list 
for example.

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

Title:
  message "The repository is insufficiently signed by key  (weak
  digest)" is poorly worded

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  The title pretty much says it all.

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

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

[Touch-packages] [Bug 1594874] Re: App won't open from click scope if it got updated in meantime

[Rodney Dawes]

Well, so much for not having the version in the application:/// URL.
Apparently it doesn't work. Not sure if it's unity-scopes-shell that's
failing there, unity8, or ubuntu-app-launch though.

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

Title:
  App won't open from click scope if it got updated in meantime

Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  0) Have an app installed that has an available update from the store
  1) Open that app's preview in the click scope
  2) Update the app in System Settings
  3) Click "Open" in the click scope's app preview
  4) Note that the app tries to open, but never does

  Presumably, this is because the click scope is providing a full appid
  including a version.  Either the app preview needs to refresh when an
  update is installed or it needs to provide an appid without a version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1594874/+subscriptions

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

[Touch-packages] [Bug 1597523] [NEW] SRU of LXC 2.0.13(upstream bugfix release)

[Stéphane Graber]

Public bug reported:

LXC upstream released LXC 2.0.2 & 2.0.3 as bugfix releases with following 
changelog:
 - apparmor: Refresh generated file
 - apparmor: add make-rslave to usr.bin.lxc-start
 - apparmor: Allow bind-mounts and {r}shared/{r}private
 - apparmor: allow mount move
 - apparmor: Update mount states handling
 - core: Drop lxc-devsetup as unneeded by current autodev
 - core: Fix redefinition of struct in6_addr
 - core: Include all lxcmntent.h function declarations on Bionic
 - c/r: c/r: use criu's "full" mode for cgroups
 - systemd: start containers in foreground when using the lxc@.service
 - templates: debian: Make sure init is installed
 - templates: oracle: Fix console login
 - templates: plamo: Fix various issues
 - templates: ubuntu: Install apt-transport-https by default
 - travis: ensure 'make install' doesn't fail
 - travis: test VPATH builds
 - upstart: Force lxc-instance to behave like a good Upstart client

Just like Ubuntu itself, upstream releases long term support releases,
as is 2.0 and then periodic point releases including all the accumulated
bugfixes.

Only the latest upstream release gets full support from the upstream
developers, everyone else is expected to first update to it before
receiving any kind of support.

This bugfix release has already been uploaded to Yakkety and
automatically backported in the upstream PPAs for all Ubuntu releases.
So far without any reported regression.

This should qualify under the minor upstream bugfix release allowance of
the SRU policy, letting us SRU this without paperwork for every single
change included in this upstream release.

Once the SRU hits -updates, we will be backporting this to trusty-
backports as well, making sure we have the same version everywhere.

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: lxc (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: lxc (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Also affects: lxc (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

Title:
  SRU of LXC 2.0.13(upstream bugfix release)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  New
Status in lxc source package in Xenial:
  New

Bug description:
  LXC upstream released LXC 2.0.2 & 2.0.3 as bugfix releases with following 
changelog:
   - apparmor: Refresh generated file
   - apparmor: add make-rslave to usr.bin.lxc-start
   - apparmor: Allow bind-mounts and {r}shared/{r}private
   - apparmor: allow mount move
   - apparmor: Update mount states handling
   - core: Drop lxc-devsetup as unneeded by current autodev
   - core: Fix redefinition of struct in6_addr
   - core: Include all lxcmntent.h function declarations on Bionic
   - c/r: c/r: use criu's "full" mode for cgroups
   - systemd: start containers in foreground when using the lxc@.service
   - templates: debian: Make sure init is installed
   - templates: oracle: Fix console login
   - templates: plamo: Fix various issues
   - templates: ubuntu: Install apt-transport-https by default
   - travis: ensure 'make install' doesn't fail
   - travis: test VPATH builds
   - upstart: Force lxc-instance to behave like a good Upstart client

  Just like Ubuntu itself, upstream releases long term support releases,
  as is 2.0 and then periodic point releases including all the
  accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This bugfix release has already been uploaded to Yakkety and
  automatically backported in the upstream PPAs for all Ubuntu releases.
  So far without any reported regression.

  This should qualify under the minor upstream bugfix release allowance
  of the SRU policy, letting us SRU this without paperwork for every
  single change included in this upstream release.

  Once the SRU hits -updates, we will be backporting this to trusty-
  backports as well, making sure we have the same version everywhere.

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

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

[Touch-packages] [Bug 1558331] Re: message "The repository is insufficiently signed by key (weak digest)" is poorly worded

[Angel Granados Gonzalez]

I have a owncloud 9 with Ubuntu 16.04. Today has started this error when
I try to do apt-get update.

I have my own local repo and am getting this error for it whenever I try
to do apt-get update. I even recently updated the key I use to sign it
to RSA/RSA 2048/2048 and also add the two lines in

I add the two lines in
~/.gnupg/gpg.conf:

cert-digest-algo SHA256
digest-algo SHA256

as recommended at http://askubuntu.com/a/776599/170127.

And I have del the key and later add key again.

However I still keep getting this error. Please advise as to what I have
to do to stop getting this error.


W: 
http://download.owncloud.org/download/repositories/stable/Ubuntu_16.04/Release.gpg:
 Signature by key BCECA90325B072AB1245F739AB7C32C35180350A uses weak digest 
algorithm (SHA1)

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

Title:
  message "The repository is insufficiently signed by key  (weak
  digest)" is poorly worded

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  The title pretty much says it all.

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

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

[Touch-packages] [Bug 1591503] Please test proposed package

[Martin Pitt]

Hello Ikuya, or anyone else affected,

Accepted mozc into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mozc/2.17.2116.102+gitfd0f5b34
+dfsg-1ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-zh-hans-base
in Ubuntu.
https://bugs.launchpad.net/bugs/1591503

Title:
  missing fcitx-mozc.mo

Status in langpack-o-matic:
  Triaged
Status in language-pack-ja-base package in Ubuntu:
  Confirmed
Status in language-pack-zh-hans-base package in Ubuntu:
  Confirmed
Status in language-pack-zh-hant-base package in Ubuntu:
  Confirmed
Status in mozc package in Ubuntu:
  Won't Fix
Status in mozc source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  For some at this point unknown reason, langpack-o-matic refuses to include 
fcitx-mozc.mo in the applicable language-pack-*-base packages. As a workaround 
for now this proposed upload rebuilds mozc with export NO_PKG_MANGLE=1 so the 
translations are not stripped.

  [Test Case]
  After install, check for the existence of e.g.

   /usr/share/locale/ja/LC_MESSAGES/fcitx-mozc.mo
   /usr/share/locale/zh_CN/LC_MESSAGES/fcitx-mozc.mo

  [Regression Potential]
  Low.

  [Original description]
  $ LANG=C dpkg -S fcitx-mozc.mo
  dpkg-query: no path found matching pattern *fcitx-mozc.mo*

  Please include it for upcoming next translation update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/langpack-o-matic/+bug/1591503/+subscriptions

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

[Touch-packages] [Bug 1568094] Re: Many error message such as "Start request repeated too quickly."

[Martin Pitt]

AFAICS this should be
https://github.com/systemd/systemd/pull/3148/commits/8b26cdbd2a9 and
https://github.com/systemd/systemd/pull/3148/commits/7629ec4642, I'll
see how well this backports.

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

Title:
  Many error message such as "Start request repeated too quickly."

Status in laptop-mode-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in laptop-mode-tools source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  * Analysis:

  The error messages are caused by a bad interaction between systemd and
  laptop-mode-tools.

  * Fixes:

  There is a fix in systemd:
  https://github.com/systemd/systemd/pull/3148

  The problem can also be fixed by updating laptop-mode-tools.

  * Symptoms:

  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: Starting Show Plymouth Boot Screen...
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: plymouth-start.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-ask-password-console.path: Start 
request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Dispatch Password 

[Touch-packages] [Bug 1475678] Re: Unity8 not informing clients that they are not visible and thus can stop rendering

[Pat McGowan]

** Changed in: canonical-devices-system-image
Milestone: 12 => 13

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

Title:
  Unity8 not informing clients that they are not visible and thus can
  stop rendering

Status in Canonical System Image:
  In Progress
Status in QtMir:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Currently on the phone, apps stop rendering when shell hides them,
  because shell also lifecycle stops the app. App isn't actually told it
  should stop rendering, we just SIGSTOP its process.

  But some apps are not lifecycle stopped, e.g. music. So we should have
  unity8 tell the app to stop rendering.

  
  This will be a multi-step process:
  1. Qtubuntu
  Mir has a attribute to set on surfaces to tell them they are 
visible/occluded: (see mir/include/common/mir_toolkit/common.h)
  mir_surface_attrib_visibility - part of the MirSurfaceAttrib enum. 

  This indicates these possible values:
  typedef enum MirSurfaceVisibility
  {
  mir_surface_visibility_occluded = 0,
  mir_surface_visibility_exposed
  } MirSurfaceVisibility;

  On the client side (qtubuntu), you need to listen for this attribute change, 
and connect it to QWindowSystemInterface::handleExposeEvent() which tells Qt 
how much of a QWindow is being drawn.
  Note there is also a QWindowSystemInterface::handleWindowStateChanged() 
handler, which use use to explicitly set QWindow show/hide, but Qt tends to 
release its GL context on hide, which we may not desire. It may not hurt, worth 
a look.

  2. QtMir
  There are methods on mir::scene::Surface to set and get the MirSurfaceAttrib 
attributes. I think it would make sense to use the pre-existing 
MirSurfaceItem::visible property, so that if a surface is marked visible=false, 
then that will dispatch the mir_surface_visibility_occluded event to the 
client, so it will stop drawing.

  3. Unity8
  Correctly set visible=false when an application surface is occluded, and true 
when visible. QML has no automatic way of doing that (i.e. occlusion detection)

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

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

[Touch-packages] [Bug 1591503] Re: missing fcitx-mozc.mo

[Martin Pitt]

I don't think we should apply the workaround to yakkety, let's rather
fix it properly there.

** Changed in: mozc (Ubuntu)
   Status: In Progress => Won't Fix

** Changed in: mozc (Ubuntu)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)

** Changed in: mozc (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-zh-hans-base
in Ubuntu.
https://bugs.launchpad.net/bugs/1591503

Title:
  missing fcitx-mozc.mo

Status in langpack-o-matic:
  Triaged
Status in language-pack-ja-base package in Ubuntu:
  Confirmed
Status in language-pack-zh-hans-base package in Ubuntu:
  Confirmed
Status in language-pack-zh-hant-base package in Ubuntu:
  Confirmed
Status in mozc package in Ubuntu:
  Won't Fix
Status in mozc source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  For some at this point unknown reason, langpack-o-matic refuses to include 
fcitx-mozc.mo in the applicable language-pack-*-base packages. As a workaround 
for now this proposed upload rebuilds mozc with export NO_PKG_MANGLE=1 so the 
translations are not stripped.

  [Test Case]
  After install, check for the existence of e.g.

   /usr/share/locale/ja/LC_MESSAGES/fcitx-mozc.mo
   /usr/share/locale/zh_CN/LC_MESSAGES/fcitx-mozc.mo

  [Regression Potential]
  Low.

  [Original description]
  $ LANG=C dpkg -S fcitx-mozc.mo
  dpkg-query: no path found matching pattern *fcitx-mozc.mo*

  Please include it for upcoming next translation update.

To manage notifications about this bug go to:
https://bugs.launchpad.net/langpack-o-matic/+bug/1591503/+subscriptions

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

[Touch-packages] [Bug 1586050] Re: Splashscreen icon rotates several times when app uses desktop flag X-Ubuntu-Rotates-Window-Contents=true

[Pat McGowan]

** Changed in: canonical-devices-system-image
Milestone: 12 => 13

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

Title:
  Splashscreen icon rotates several times when app uses desktop flag X
  -Ubuntu-Rotates-Window-Contents=true

Status in Canonical System Image:
  In Progress
Status in QtMir:
  Invalid
Status in camera-app package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  On the BQ M10 (frieza), launching an app while holding the device in
  landscape orientation makes its splashscreen icon rotate several times
  without any apparent reason if the desktop file contains the flag X
  -Ubuntu-Rotates-Window-Contents=true

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

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

[Touch-packages] [Bug 1565908] Re: Allow calendar policy to read from device time zone

[Pat McGowan]

@sil can you get this to the overlay

** Changed in: canonical-devices-system-image
Milestone: 12 => 13

** Changed in: canonical-devices-system-image
 Assignee: Emily Ratliff (emilyr) => Łukasz Zemczak (sil2100)

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

Title:
  Allow calendar policy to read from device time zone

Status in Canonical System Image:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Fix Released
Status in apparmor-easyprof-ubuntu package in Ubuntu RTM:
  Confirmed

Bug description:
  qtorganizer5-eds needs to detect device current timezone to be able to
  save events in the correct tz. To do that we need read access to
  /etc/writable/timezone.

  Would be nice to have that policy on calendar policy file.

  This is part of the solution for bug #1563742

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

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

[Touch-packages] [Bug 1588252] Re: [File Manager] Display issue: big white gap below header (portrait) & top gets cut off (landscape) after OTA-11

[Pat McGowan]

** Changed in: canonical-devices-system-image
Milestone: 12 => 13

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

Title:
  [File Manager] Display issue: big white gap below header (portrait) &
  top gets cut off (landscape) after OTA-11

Status in Canonical System Image:
  In Progress
Status in Ubuntu File Manager App:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  After the OTA-11 update, File Manager shows a big white space just below the 
header in portrait mode.
  https://launchpadlibrarian.net/262898404/screenshot20160602_150103754.png

  And also as Davide mentioned, top part goes off the display in landscape mode.
  https://launchpadlibrarian.net/262958275/screenshot20160602_184130460.png

  This only happens on E4.5 and E5, not on MX4 or M10
  0.4.525 of file manager

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

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

[Touch-packages] [Bug 1590776] Re: hide selection handle when start typing

[Pat McGowan]

** Changed in: canonical-devices-system-image
Milestone: 12 => 13

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

Title:
  hide selection handle when start typing

Status in Canonical System Image:
  In Progress
Status in Oxide:
  Fix Released
Status in Oxide 1.15 series:
  Fix Committed
Status in Oxide 1.16 series:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  we are showing the selection handle (in addition to the cursor)
  whenever entering a text field that already has text in it. For
  example, if you are replying to a Gmail message, you have an annoying
  blue selection handle blinking where you are trying to type and you
  can't turn it off. Or on a form, focusing on a field to append text
  will also show the selection handle. Or a multi line text area, adding
  a new line and typing at the beginning.

  Tested Chrome on Android and it behaves differently, and think we should do 
similar:
   1. Show the selection handle initially, but have it disappear when you press 
any key (space, character, etc.)
   2. Tapping anywhere in the field will cause handle to be shown again
   3. Also, can we put the selection handle on the bottom of the cursor instead 
of the top? This is the behavior on Chrome for Android and the rest of our 
non-html platform in Ubuntu touch.

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

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

[Touch-packages] [Bug 1592447] Re: camera startup time regression

[Pat McGowan]

** Changed in: canonical-devices-system-image
Milestone: 12 => 13

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

Title:
  camera startup time regression

Status in Canonical System Image:
  In Progress
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  Please see 
  http://reqorts.qa.ubuntu.com/reports/qa/performance/dashboard/index.html

  the camera time recently jumped in startup time, but this did not seem
  to be something caused by a common component when comparing to other
  apps.

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

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

[Touch-packages] [Bug 1392699] Re: Can't change locale settings (e.g. language, 12/24-hour time, date format) independently

[Pat McGowan]

@jibel can you add whatever concerns came during testing?
note we have a separate issue to add the 12/24 toggle

** Changed in: canonical-devices-system-image
Milestone: 12 => 13

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

** Changed in: canonical-devices-system-image
 Assignee: Will Cooke (willcooke) => Jean-Baptiste Lallement (jibel)

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

Title:
  Can't change locale settings (e.g. language, 12/24-hour time, date
  format) independently

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  A. Try to use US English, but with all apps using 24-hour instead of 12-hour 
time. Or:
  B. Try to use UK English, but with all apps using -MM-DD date format.

  What happens: You can't.
  What should happen: You can.

  Since Ubuntu has existed, it has used the GNU locale system. This
  system assumes that every single person using a particular locale
  wants exactly the same settings for time display, date display,
  currency display, alphabetizing, and number formatting.
  

  Windows, Mac OS, and (to a lesser extent) iOS have always been more
  flexible: setting a locale sets appropriate defaults for these
  settings, but you can also change them individually. Ubuntu should do
  the same.

  This might involve changing the locale system itself, or it might
  involve changing all relevant toolkits so that they ignore the locale
  system when appropriate.

  It would also involve adding settings in System Settings to customize
  the individual locale details.

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

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

[Touch-packages] [Bug 1545118] Re: [AdaptivePageLayout] can't easily grab scrollbar if dual column

[Pat McGowan]

** Changed in: canonical-devices-system-image
Milestone: 12 => 13

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

Title:
  [AdaptivePageLayout] can't easily grab scrollbar if dual column

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

Bug description:
  If you have an app that uses AdaptivePageLayout and supports 2
  columns, if there is a scrollbar in the first column, it's very
  difficult to grab it with your mouse because when you get close to it,
  you get the horizontal arrows showing to allow resizing of the panels
  in the multi-column layout.

  You can try this with messaging-app in silo 30 (soon to land)

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

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

[Touch-packages] [Bug 1593805] Re: libsignon-glib fail to authenticate account

[Pat McGowan]

** Changed in: canonical-devices-system-image
Milestone: 12 => 13

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

Title:
  libsignon-glib fail to authenticate account

Status in Canonical System Image:
  In Progress
Status in Ubuntu Calendar App:
  New
Status in webapps-sprint:
  In Progress
Status in libsignon-glib package in Ubuntu:
  In Progress

Bug description:
  While using syncevolution to sync multiple calendars, we noticed that
  some accounts are failing to authenticate.

  The error returned by 'libsignon-glib' shows the dbus process as
  service name, what is different from the app requested.

  Check syslog attached.

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

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

[Touch-packages] [Bug 1568094] Re: Many error message such as "Start request repeated too quickly."

[Martin Pitt]

** Also affects: laptop-mode-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Xenial)
   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/1568094

Title:
  Many error message such as "Start request repeated too quickly."

Status in laptop-mode-tools package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in laptop-mode-tools source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  * Analysis:

  The error messages are caused by a bad interaction between systemd and
  laptop-mode-tools.

  * Fixes:

  There is a fix in systemd:
  https://github.com/systemd/systemd/pull/3148

  The problem can also be fixed by updating laptop-mode-tools.

  * Symptoms:

  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: Starting Show Plymouth Boot Screen...
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: Started Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: friendly-recovery.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Recovery mode menu.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-fsck-root.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start File System Check on Root 
Device.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-hwdb-update.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Rebuild Hardware Database.
  Apr 08 20:23:50 xeelee systemd[1]: sys-kernel-config.mount: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to mount Configuration File System.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-binfmt.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Set Up Additional Binary 
Formats.
  Apr 08 20:23:50 xeelee systemd[1]: plymouth-start.service: Start request 
repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Show Plymouth Boot Screen.
  Apr 08 20:23:50 xeelee systemd[1]: systemd-ask-password-console.path: Start 
request repeated too quickly.
  Apr 08 20:23:50 xeelee systemd[1]: Failed to start Dispatch Password Requests 
to 

[Touch-packages] [Bug 1556120] Re: Include Breton and Welsh in Ubuntu Touch

[Pat McGowan]

probably will depend on dynamic loading of language support

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

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

Title:
  Include Breton and Welsh in Ubuntu Touch

Status in Canonical System Image:
  In Progress
Status in langpack-o-matic:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Confirmed
Status in ubuntu-touch-meta package in Ubuntu RTM:
  New

Bug description:
  In Ubuntu Translators mailing list there has been requests to include
  Breton and Welsh in Ubuntu Touch.

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

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

[Touch-packages] [Bug 1575744] Re: network disk cache does not take into account the HTTP Vary header

[Pat McGowan]

** Summary changed:

- Language in the Store scope doesn't always change when user switches lang of 
the phone
+ network disk cache does not take into account the HTTP Vary header

** Description changed:

  Switching from English to Polish works as expected
  But then going back to English leaves me with store in Polish
  
  This survives reboots.
  
  Steps to reproduce:
  1. Go to Ubuntu Store scope (with your current language).
  2. Go to phone settings, change the language, accept & reboot the phone.
  3. Go to Ubuntu Store scope. Note how scope title and some strings such as 
"installed" changed for the new language (since these are provided locally by 
the scope for current LANG), but strings such as 'Highlight of the week' or 
departments names (hit the search lens icon to reveal departments) which come 
from the store still use the old language.
+ 
+ See upstream bug at https://bugreports.qt.io/browse/QTBUG-14750

** Changed in: canonical-devices-system-image
Milestone: 12 => 13

** Changed in: canonical-devices-system-image
 Assignee: Alejandro J. Cura (alecu) => John McAleely (john.mcaleely)

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

Title:
  network disk cache does not take into account the HTTP Vary header

Status in Canonical System Image:
  In Progress
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in unity-scope-click package in Ubuntu:
  Fix Released

Bug description:
  Switching from English to Polish works as expected
  But then going back to English leaves me with store in Polish

  This survives reboots.

  Steps to reproduce:
  1. Go to Ubuntu Store scope (with your current language).
  2. Go to phone settings, change the language, accept & reboot the phone.
  3. Go to Ubuntu Store scope. Note how scope title and some strings such as 
"installed" changed for the new language (since these are provided locally by 
the scope for current LANG), but strings such as 'Highlight of the week' or 
departments names (hit the search lens icon to reveal departments) which come 
from the store still use the old language.

  See upstream bug at https://bugreports.qt.io/browse/QTBUG-14750

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

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

[Touch-packages] [Bug 1590188] Re: Widgets is are in wrong order after posting one comment in Preview Page

[Pat McGowan]

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

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

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

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

Title:
  Widgets is are in wrong order after posting one comment in Preview
  Page

Status in Canonical System Image:
  Fix Committed
Status in unity-scopes-shell package in Ubuntu:
  Fix Released

Bug description:
  I am testing on some golang scopes such as
  doubanbook(https://code.launchpad.net/~hanloon-team/hanloon/douban)
  flickr(https://code.launchpad.net/~hanloon-team/hanloon/unity-scope-flickr)
  After I post one comment and the Preview page refreshes, the order of Preview 
Widgets is reversed. For example, before I post comment, Art is on the up most 
position, while after I post comment, Art is the last widget in the page.

  I can see from the log, the order of widgets is adjusted(art at first
  is 0, and at last is 15). But i don't know why.

  AS Pawel's suggestion, I used scopes.ColumnLayout as workaround which
  could fix this issue.

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

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

[Touch-packages] [Bug 1597389] Re: Please fix probleam

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Please fix probleam

Status in xorg package in Ubuntu:
  New

Bug description:
  Resolution do not set 1024x900.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Jun 29 20:52:15 2016
  InstallationDate: Installed on 2016-06-10 (19 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1578141] Re: Predictable interface names partially broken with igb driver

[Anthony Carlson]

I recently ran into this while upgrading 76 systems. In my research I
have concluded that this bug is the result of bad information coming
from the BIOS 3.0b, 3.0c, and 3.2. This bug is not present with BIOS
3.00.

If you run biosdevname, you will see that the BIOS Device name is em1
for both of the intel i350 interfaces resulting (as mentioned above by
Dr. Jens Rosenboom (j-rosenboom-j) in dracut successfully naming the
first device to initialize as eno1. If you reboot the system and check
udevadm, you can see that the interfaces can alternate in which port is
initialized first resulting in eno1 moving from port1 to port2. This is
causing problems primarily with bonding our interfaces.

sudo biosdevname -d
BIOS device: em1
Kernel name: eno1
Permanent MAC: 00:00:00:00:00:00
Assigned MAC : 00:00:00:00:00:00
ifIndex: 2
Driver: igb
Driver version: 5.2.15-k
Firmware version: 1.61, 0x890e
Bus Info: :06:00.0
PCI name  : :06:00.0
PCI Slot  : embedded
SMBIOS Device Type: Ethernet
SMBIOS Instance: 1
SMBIOS Label:  Onboard Intel Ethernet 1
sysfs Index: 1
sysfs Label:  Onboard Intel Ethernet 1
Embedded Index: 1

Duplicate: True
BIOS device: em1
Kernel name: eth1
Permanent MAC: 00:00:00:00:00:00
Assigned MAC : 00:00:00:00:00:00
ifIndex: 3
Driver: igb
Driver version: 5.2.15-k
Firmware version: 1.61, 0x890e
Bus Info: :06:00.1
PCI name  : :06:00.1
PCI Slot  : embedded
SMBIOS Device Type: Ethernet
SMBIOS Instance: 1
SMBIOS Label:  Onboard Intel Ethernet 2
sysfs Index: 1
sysfs Label:  Onboard Intel Ethernet 2
Embedded Index: 2

Duplicate: True

I have submitted my findings for all of my nodes to Supermicro seeking a
bug fix and releasing an update BIOS.

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

Title:
  Predictable interface names partially broken with igb driver

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Note: I'm not sure whether this is really a kernel bug or something
  within systemd/udev, please advise how to further debug.

  On a system with two GE ports, instead of getting named eno1 and eno2,
  I am getting eno1 and renameN. Where N starts at 3 and increases by 2
  on every iteration of doing "rmmod igb;modprobe igb". The
  corresponding lines in dmesg look like this:

  [2.748429] igb :07:00.0: added PHC on eth0
  [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection
  [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8e
  [2.748505] igb :07:00.0: eth0: PBA No: 106100-000
  [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.802555] igb :07:00.1: added PHC on eth1
  [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection
  [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 
00:25:90:d7:60:8f
  [2.802631] igb :07:00.1: eth1: PBA No: 106100-000
  [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx 
queue(s)
  [2.803618] igb :07:00.0 eno1: renamed from eth0
  [2.833208] igb :07:00.1 rename3: renamed from eth1

  What is even worse: Sometimes the naming changes and the second
  interface ends up as eno1 while the first interface is named renameN
  with an even N. The bad thing about this version is that when it
  happens while the installer is running, the installer will setup
  "rename2" as the primary network interface, which works fine for the
  installation itself, but after installation is finished and the first
  boot of the installed system happens, that interface will be gone,
  leaving the system without network connectivity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  4 09:48 seq
   crw-rw 1 root audio 116, 33 May  4 09:48 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed May  4 10:00:39 2016
  HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 

[Touch-packages] [Bug 1597505] Re: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Its an old dell laptop and i need it to work xD

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CrashReports:
   640:0:116:304331:2016-06-29 21:55:40.221202611 +0200:2016-06-29 
21:55:41.725209378 +0200:/var/crash/steam.0.crash
   644:0:116:0:2016-06-29 21:55:41.725209378 +0200:2016-06-29 
21:55:41.725209378 +0200:/var/crash/steam.0.upload
   640:1000:116:1218738:2016-06-29 22:06:45.978306055 +0200:2016-06-29 
22:06:46.978306055 
+0200:/var/crash/_usr_lib_i386-linux-gnu_xfce4_panel_wrapper-1.0.1000.crash
   600:109:116:0:2016-06-29 21:55:42.745222940 +0200:2016-06-29 
21:55:42.745222940 +0200:/var/crash/steam.0.uploaded
   600:0:116:299565:2016-06-29 22:00:20.209570646 +0200:2016-06-29 
22:00:21.209570646 +0200:/var/crash/apport.0.crash
  Date: Wed Jun 29 22:00:20 2016
  DuplicateSignature:
   package:apport:2.20.1-0ubuntu2.1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-06-29 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1492783] Re: GPS does not work on my Bq E5

[flohack]

is there any regression with that, GPS worked for me on the BQ 5 for some time 
now, but stopped after the last OTA. I am not good with debugging, I strongly 
suggest to give a possibility to see status of GPS: number of satellites, if it 
cold starts or can look up constellation etc...
BR

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

Title:
  GPS does not work on my Bq E5

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  I have a Bq E5 (not an E4.5) and the GPS does not seem to work. The
  SensorsStatus app shows GPS as returning no results for location
  (every reading ("Latitude", "Longitude", etc) is shown as a dash,
  except "Method" which is "Satellite" and "Speed" which is "nan") . I
  have attached various logfiles in the hope that they will help. I have
  tried turning off location detection and GPS and turning them back on
  again, to no avail. I have also tried turning off wifi, to no avail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1492783/+subscriptions

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

[Touch-packages] [Bug 1597505] [NEW] package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Sven]

Public bug reported:

Its an old dell laptop and i need it to work xD

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CrashReports:
 640:0:116:304331:2016-06-29 21:55:40.221202611 +0200:2016-06-29 
21:55:41.725209378 +0200:/var/crash/steam.0.crash
 644:0:116:0:2016-06-29 21:55:41.725209378 +0200:2016-06-29 21:55:41.725209378 
+0200:/var/crash/steam.0.upload
 640:1000:116:1218738:2016-06-29 22:06:45.978306055 +0200:2016-06-29 
22:06:46.978306055 
+0200:/var/crash/_usr_lib_i386-linux-gnu_xfce4_panel_wrapper-1.0.1000.crash
 600:109:116:0:2016-06-29 21:55:42.745222940 +0200:2016-06-29 
21:55:42.745222940 +0200:/var/crash/steam.0.uploaded
 600:0:116:299565:2016-06-29 22:00:20.209570646 +0200:2016-06-29 
22:00:21.209570646 +0200:/var/crash/apport.0.crash
Date: Wed Jun 29 22:00:20 2016
DuplicateSignature:
 package:apport:2.20.1-0ubuntu2.1
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package apport (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-06-29 (0 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: apport
Title: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Its an old dell laptop and i need it to work xD

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CrashReports:
   640:0:116:304331:2016-06-29 21:55:40.221202611 +0200:2016-06-29 
21:55:41.725209378 +0200:/var/crash/steam.0.crash
   644:0:116:0:2016-06-29 21:55:41.725209378 +0200:2016-06-29 
21:55:41.725209378 +0200:/var/crash/steam.0.upload
   640:1000:116:1218738:2016-06-29 22:06:45.978306055 +0200:2016-06-29 
22:06:46.978306055 
+0200:/var/crash/_usr_lib_i386-linux-gnu_xfce4_panel_wrapper-1.0.1000.crash
   600:109:116:0:2016-06-29 21:55:42.745222940 +0200:2016-06-29 
21:55:42.745222940 +0200:/var/crash/steam.0.uploaded
   600:0:116:299565:2016-06-29 22:00:20.209570646 +0200:2016-06-29 
22:00:21.209570646 +0200:/var/crash/apport.0.crash
  Date: Wed Jun 29 22:00:20 2016
  DuplicateSignature:
   package:apport:2.20.1-0ubuntu2.1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-06-29 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1597217] Re: New color emojies not appearing in notifications

[Pat McGowan]

** 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 => 13

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

** Changed in: canonical-devices-system-image
   Status: Confirmed => 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/1597217

Title:
  New color emojies not appearing in notifications

Status in Canonical System Image:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Now that we have the color emojies, they seem to not appear in the
  notification when you receive a message with one of them.

  The actual notification does contain the emoji, as I do get it
  displayed on the Pebble watch (which sniffs notifications). So it must
  be a rendering issue on the unity8 side.

  Also there seems to be an empty line which doesn't belong there.

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

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

[Touch-packages] [Bug 1500039] Re: Ubuntu Phone is not getting a mobile network cell triangulation position

[flohack]

Plus is there any chance that this bug also affects GPS liason? I am not
able anymore to use any GPS app on my BQ5, this started some time after
the last OTA.

BR

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

Title:
  Ubuntu Phone is not getting a mobile network cell triangulation
  position

Status in Canonical System Image:
  In Progress
Status in location-service package in Ubuntu:
  In Progress

Bug description:
  Hi!

  I think that the mobile network cell triangulation position is not
  working in Ubuntu Phone OS.

  The position should be really fast (~1 - 5") and I'm thinking that
  Ubuntu Phone is waiting for a real GPS position every time.

  A good test could be this:
  - Go to a room, way out of a sky to avoid a real GPS signal.
  - Set WiFi service OFF.
  - Set GPS service ON.
  - Set data connection ON.
  - Go to this website via webbrowser-app: 
http://leafletjs.com/examples/mobile-example.html The website will ask you to 
allow access to the current location.
  - Make sure to not have a GPS position cached.

  In a PC or *any* Android you'll see your position immediately.
  Bug: In Ubuntu Phone an error will appears. This error is because the 
geoposition 
(https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/Using_geolocation)
 is not working with the cell triangulation network data.

  You can try a lot of apps like Google Maps, OSMTouch, HERE map, uNAV... and a 
fast position from data connection is not happening, unless you be with a WIFI 
connection.
  If you try Google Maps in Android, the position will be really fast just with 
data connection.

  Thanks in advance!

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

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

[Touch-packages] [Bug 1461873] Re: [messaging] Ability to forward SMS without copy 'n past approach

[Pat McGowan]

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

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

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

Title:
  [messaging] Ability to forward SMS without copy 'n past approach

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Fix Committed
Status in messaging-app package in Ubuntu:
  In Progress

Bug description:
  It would be nice if the SMS app swipe left context had the ability to forward 
the SMS to other receivers.
  The existing approah where one can swipe left and copy the content and then 
paste into a new SMS seems less intuitive.

  **

  This feature is in the new designs but has yet to be implemented.
  https://docs.google.com/presentation/d/1hkrF2g-
  ad7fhJ0UVLKmu_5ZXSFK1EkcWS129JxmAAI4/edit#slide=id.p97

  **

  This is a certification requirement

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

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

[Touch-packages] [Bug 1595569] Re: Indicators panel doesn't close when turning screen off

[Pat McGowan]

jibel points out its useful when showing the sound indicator controls,
so perhaps a feature

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

Title:
  Indicators panel doesn't close when turning screen off

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Steps:
  * open indicators
  * press power button to turn the screen off
  * press power button to turn the screen on

  Expected:
  * greeter shown

  Current:
  * indicators panel shown

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160617-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 23 10:17:32 2016
  InstallationDate: Installed on 2016-05-06 (47 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

[Jim Hodapp]

@Anupam: no worries, refer to Pat's comment in #53. We're pretty
confident we've tracked down the source of the problem and how to fix
it.

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

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

  UPDATE: Screenshots get silent too.

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

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

[Touch-packages] [Bug 1595569] Re: Indicators panel doesn't close when turning screen off

[Pat McGowan]

If the indicator is opened when the phone is unlocked then it slides
away and shows the greeter. If opened when locked, it doesn't slide
away.

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

Title:
  Indicators panel doesn't close when turning screen off

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Steps:
  * open indicators
  * press power button to turn the screen off
  * press power button to turn the screen on

  Expected:
  * greeter shown

  Current:
  * indicators panel shown

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160617-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 23 10:17:32 2016
  InstallationDate: Installed on 2016-05-06 (47 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1594874] Re: App won't open from click scope if it got updated in meantime

[Launchpad Bug Tracker]

** Branch linked: lp:~dobey/unity-scope-click/short-appid

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

Title:
  App won't open from click scope if it got updated in meantime

Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  0) Have an app installed that has an available update from the store
  1) Open that app's preview in the click scope
  2) Update the app in System Settings
  3) Click "Open" in the click scope's app preview
  4) Note that the app tries to open, but never does

  Presumably, this is because the click scope is providing a full appid
  including a version.  Either the app preview needs to refresh when an
  update is installed or it needs to provide an appid without a version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1594874/+subscriptions

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

[Touch-packages] [Bug 1594874] Re: App won't open from click scope if it got updated in meantime

[Rodney Dawes]

** Changed in: unity-scope-click (Ubuntu)
 Assignee: (unassigned) => Rodney Dawes (dobey)

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

Title:
  App won't open from click scope if it got updated in meantime

Status in unity-scope-click package in Ubuntu:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  New

Bug description:
  0) Have an app installed that has an available update from the store
  1) Open that app's preview in the click scope
  2) Update the app in System Settings
  3) Click "Open" in the click scope's app preview
  4) Note that the app tries to open, but never does

  Presumably, this is because the click scope is providing a full appid
  including a version.  Either the app preview needs to refresh when an
  update is installed or it needs to provide an appid without a version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1594874/+subscriptions

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

[Touch-packages] [Bug 1595569] Re: Indicators panel doesn't close when turning screen off

[Alejandro J. Cura]

Weird thing is that sometimes the indicator stays still:
https://goo.gl/photos/cdsEc4k2fhPfhKUZ9

and sometimes it closes on its own:
http://people.canonical.com/~davmor2/vids/video20160629_201128513.mp4

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

Title:
  Indicators panel doesn't close when turning screen off

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Steps:
  * open indicators
  * press power button to turn the screen off
  * press power button to turn the screen on

  Expected:
  * greeter shown

  Current:
  * indicators panel shown

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160617-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 23 10:17:32 2016
  InstallationDate: Installed on 2016-05-06 (47 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1595569] Re: Indicators panel doesn't close when turning screen off

[Pat McGowan]

** Changed in: unity8 (Ubuntu)
   Importance: Medium => 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/1595569

Title:
  Indicators panel doesn't close when turning screen off

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Steps:
  * open indicators
  * press power button to turn the screen off
  * press power button to turn the screen on

  Expected:
  * greeter shown

  Current:
  * indicators panel shown

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160617-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 23 10:17:32 2016
  InstallationDate: Installed on 2016-05-06 (47 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1595569] Re: Indicators panel doesn't close when turning screen off

[Michael Terry]

** 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/1595569

Title:
  Indicators panel doesn't close when turning screen off

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Steps:
  * open indicators
  * press power button to turn the screen off
  * press power button to turn the screen on

  Expected:
  * greeter shown

  Current:
  * indicators panel shown

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160617-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 23 10:17:32 2016
  InstallationDate: Installed on 2016-05-06 (47 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1595569] Re: Indicators panel doesn't close when turning screen off

[Pat McGowan]

Just noticed this on all devices with latest image.
Its particularly weird when an incoming text notification is shown over the 
indicator content.

** Also affects: canonical-devices-system-image
   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 => 13

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

** Tags added: regression-proposed

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

Title:
  Indicators panel doesn't close when turning screen off

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Steps:
  * open indicators
  * press power button to turn the screen off
  * press power button to turn the screen on

  Expected:
  * greeter shown

  Current:
  * indicators panel shown

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160617-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 23 10:17:32 2016
  InstallationDate: Installed on 2016-05-06 (47 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)

[Anupam]

@Jim I tried that, but didn't seem helpful. It only changed speaker
volume.

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

Title:
  No sound notification for new SMS (Ubuntu Touch)

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I noticed for last 2-3 days there is no sound notification for a new
  SMS, but there's a blinking green LED notification. Also in the
  indicator menu the envelope icon turns green and the new SMS is listed
  as usual. Things are working alright for Telegram, Gmail etc.
  (sound+LED+indicator menu).

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

  UPDATE: Screenshots get silent too.

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

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

[Touch-packages] [Bug 1574693] Re: No shadows under menus on Unity.

[Albert Cutrona]

Thanks for the info!! :)

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

Title:
  No shadows under menus on Unity.

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  After a fresh install of Ubuntu 16.04 in a new SSD, there aren't
  shadows under menus on application decoration borders and Unity panel.

  I've seen the same problem in Askubuntu:
  
http://askubuntu.com/questions/761842/no-shadows-under-menus-on-application-decoration-borders-and-unity-panel/762487#762487

  Thanks!!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  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 Apr 25 16:38:08 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company RS880M [Mobility Radeon HD 4225/4250] 
[103c:143c]
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 
5430/5450/5470] [1002:68e0] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2016-04-25 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP G62 Notebook PC
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=231aae18-0f30-4b65-943c-646a217d0d72 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 143C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 62.3D
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd03/15/2011:svnHewlett-Packard:pnHPG62NotebookPC:pvr059411252710001020100:rvnHewlett-Packard:rn143C:rvr62.3D:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP G62 Notebook PC
  dmi.product.version: 059411252710001020100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 16:23:48 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1574693/+subscriptions

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

[Touch-packages] [Bug 1596698] Re: Strange font issue after awakening from suspend

[Launching Dumplings]

Actually, I remember when the bug occurred going into the gnome-tweak-
tool and changing the theme as well as turning the dark theme off. But
neither change made any difference to the fonts problem.

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

Title:
  Strange font issue after awakening from suspend

Status in GTK+:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  When I awoke my computer from suspend last week on Thursday
  (23/06/2016) I found that all the text from all the title bars was
  missing, so I restarted gnome-shell as this normally fixes such
  problems, doing so seemed to make some text appear, but most not, as
  you can see from these images until I restarted my machine it was
  almost impossible to use:

  System_Monitor_No_Text.png
  Shutter_Main_Window_Font_Issue.png
  File_Chooser_Font_Issue.png
  Title_Bar_Partly_Missing.png
  Settings_Text_Issue.png

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-0 3.20.6-1ubuntu1~ppa1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 27 21:23:02 2016
  InstallationDate: Installed on 2016-05-15 (43 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history

[Launching Dumplings]

** Description changed:

  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which is
  meant to show the login history for that account), it will show you when
  you last logged in as "Session Started", but it will show that you
  "Session Ended" just before you login the next time.
  
  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I logged
  out, and then this morning I logged into my account somewhere around
  11:20, it will show this:
  
  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started
  
  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.
  
  I have attached a screenshot to show my example as I see it in the
  History GUI.
  
- I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, and
- Ubuntu GNOME 15.10 with GNOME 3.18.
+ I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
+ Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
+ 3.20.

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

Title:
  User accounts login history showing incorrect history

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04,
  Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME
  3.20.

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

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

[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history

[Launching Dumplings]

It seems as though the GNOME upstream change if applied to the 'unity-
control-center' will also fix the problem as it is the same file, same
code.

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

Title:
  User accounts login history showing incorrect history

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, and
  Ubuntu GNOME 15.10 with GNOME 3.18.

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

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

[Touch-packages] [Bug 1547647] Re: CRITICAL: please remove libqt5webkit dependancy

[Will Cooke]

** Also affects: signon-ui (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: signon-ui (Ubuntu Yakkety)
   Importance: Medium
   Status: Fix Released

** Changed in: signon-ui (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.1

** Changed in: signon-ui (Ubuntu Yakkety)
Milestone: ubuntu-16.04.1 => None

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

Title:
  CRITICAL: please remove libqt5webkit dependancy

Status in signon-ui package in Ubuntu:
  Fix Released
Status in signon-ui source package in Xenial:
  New
Status in signon-ui source package in Yakkety:
  Fix Released

Bug description:
  signon-ui-x11(http://packages.ubuntu.com/xenial/signon-ui-x11) depends
  on libqt5webkit5

  https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-
  updates/

  
  Can it be resolved so new LTS wont be released with known webkit1 
bugs/security exploits?

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

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

[Touch-packages] [Bug 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts

[Will Cooke]

** Also affects: gnome-control-center-signon (Ubuntu Yakkety)
   Importance: Critical
   Status: Fix Released

** Also affects: account-plugins (Ubuntu Yakkety)
   Importance: Critical
   Status: Fix Released

** Changed in: gnome-control-center-signon (Ubuntu Yakkety)
Milestone: ubuntu-16.04.1 => None

** Changed in: account-plugins (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.1

** Changed in: gnome-control-center-signon (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.1

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

Title:
  [SRU] Allow plugins to decide which username to set on new accounts

Status in Online Accounts: Account plugins:
  Fix Released
Status in Canonical System Image:
  Fix Committed
Status in Online Accounts: GNOME Control Center:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in account-plugins source package in Xenial:
  Confirmed
Status in gnome-control-center-signon source package in Xenial:
  Confirmed
Status in account-plugins source package in Yakkety:
  Fix Released
Status in gnome-control-center-signon source package in Yakkety:
  Fix Released

Bug description:
  This bug is related to bug 1547647, even though it makes sense in any
  case.

  Currently, the ApOAuthPlugin class in libaccount-plugin gets the
  username from the SignonIdentity, which in turn gets it from signon-
  ui, which in the current WebKit1 implementation gets it from the DOM
  of the login webpage. This is a hack, it's fragile, not trivial to
  port to the Oxide web engine, and possibly against some providers'
  guidelines.

  We should retrieve the username using some REST API provided by the
  service, and in order to do so we need to extend libaccounts-plugin
  with some hooks which subclasses can use to get the username.

  Once we fix this we can also get rid of the files /etc/signon-ui
  /webkit-options.d/, which are conflicting with those installed by the
  KDE account plugins packages.


  SRU information
  ===

  [Impact] The same file /etc/signon-ui/webkit-
  options.d/www.facebook.com.conf is installed by the account-plugin-
  facebook package (used by Unity) and by kaccount-providers (used by
  KDE). See this bug's duplicates to see actual bug reports.

  [Test Case] Install both account-plugin-facebook and kaccount-
  providers and you'll get the conflict.

  [Regression Potential] Users running KDE will be completely unaffected
  by this. Users running Unity might see a change when creating accounts
  in System Settings->Online Accounts: with this bugfix, the account's
  display name is obtained by making a REST API call to the remote
  service, rather than by scrapping the DOM of the server webpages
  (which is a hack, and prone to errors if the providers' webpage
  changes). The new way of retrieving the username is the proper one,
  and it's been tested to work reliably. In any case, the worst thing
  that might happen is that accounts get created with an empty display
  name, which is mostly an aesthetic problem (the display name is used
  only for UI purposes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1565772/+subscriptions

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

[Touch-packages] [Bug 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts

[Will Cooke]

** Changed in: gnome-control-center-signon (Ubuntu)
Milestone: None => ubuntu-16.04.1

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

Title:
  [SRU] Allow plugins to decide which username to set on new accounts

Status in Online Accounts: Account plugins:
  Fix Released
Status in Canonical System Image:
  Fix Committed
Status in Online Accounts: GNOME Control Center:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in account-plugins source package in Xenial:
  Confirmed
Status in gnome-control-center-signon source package in Xenial:
  Confirmed

Bug description:
  This bug is related to bug 1547647, even though it makes sense in any
  case.

  Currently, the ApOAuthPlugin class in libaccount-plugin gets the
  username from the SignonIdentity, which in turn gets it from signon-
  ui, which in the current WebKit1 implementation gets it from the DOM
  of the login webpage. This is a hack, it's fragile, not trivial to
  port to the Oxide web engine, and possibly against some providers'
  guidelines.

  We should retrieve the username using some REST API provided by the
  service, and in order to do so we need to extend libaccounts-plugin
  with some hooks which subclasses can use to get the username.

  Once we fix this we can also get rid of the files /etc/signon-ui
  /webkit-options.d/, which are conflicting with those installed by the
  KDE account plugins packages.


  SRU information
  ===

  [Impact] The same file /etc/signon-ui/webkit-
  options.d/www.facebook.com.conf is installed by the account-plugin-
  facebook package (used by Unity) and by kaccount-providers (used by
  KDE). See this bug's duplicates to see actual bug reports.

  [Test Case] Install both account-plugin-facebook and kaccount-
  providers and you'll get the conflict.

  [Regression Potential] Users running KDE will be completely unaffected
  by this. Users running Unity might see a change when creating accounts
  in System Settings->Online Accounts: with this bugfix, the account's
  display name is obtained by making a REST API call to the remote
  service, rather than by scrapping the DOM of the server webpages
  (which is a hack, and prone to errors if the providers' webpage
  changes). The new way of retrieving the username is the proper one,
  and it's been tested to work reliably. In any case, the worst thing
  that might happen is that accounts get created with an empty display
  name, which is mostly an aesthetic problem (the display name is used
  only for UI purposes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1565772/+subscriptions

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

[Touch-packages] [Bug 1547647] Re: CRITICAL: please remove libqt5webkit dependancy

[Will Cooke]

** Changed in: signon-ui (Ubuntu)
Milestone: None => ubuntu-16.04.1

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

Title:
  CRITICAL: please remove libqt5webkit dependancy

Status in signon-ui package in Ubuntu:
  Fix Released
Status in signon-ui source package in Xenial:
  New
Status in signon-ui source package in Yakkety:
  Fix Released

Bug description:
  signon-ui-x11(http://packages.ubuntu.com/xenial/signon-ui-x11) depends
  on libqt5webkit5

  https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-
  updates/

  
  Can it be resolved so new LTS wont be released with known webkit1 
bugs/security exploits?

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

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

[Touch-packages] [Bug 1565772] Re: [SRU] Allow plugins to decide which username to set on new accounts

[Will Cooke]

** Summary changed:

- Allow plugins to decide which username to set on new accounts
+ [SRU] Allow plugins to decide which username to set on new accounts

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

Title:
  [SRU] Allow plugins to decide which username to set on new accounts

Status in Online Accounts: Account plugins:
  Fix Released
Status in Canonical System Image:
  Fix Committed
Status in Online Accounts: GNOME Control Center:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in account-plugins package in Ubuntu:
  Fix Released
Status in gnome-control-center-signon package in Ubuntu:
  Fix Released
Status in account-plugins source package in Xenial:
  Confirmed
Status in gnome-control-center-signon source package in Xenial:
  Confirmed

Bug description:
  This bug is related to bug 1547647, even though it makes sense in any
  case.

  Currently, the ApOAuthPlugin class in libaccount-plugin gets the
  username from the SignonIdentity, which in turn gets it from signon-
  ui, which in the current WebKit1 implementation gets it from the DOM
  of the login webpage. This is a hack, it's fragile, not trivial to
  port to the Oxide web engine, and possibly against some providers'
  guidelines.

  We should retrieve the username using some REST API provided by the
  service, and in order to do so we need to extend libaccounts-plugin
  with some hooks which subclasses can use to get the username.

  Once we fix this we can also get rid of the files /etc/signon-ui
  /webkit-options.d/, which are conflicting with those installed by the
  KDE account plugins packages.


  SRU information
  ===

  [Impact] The same file /etc/signon-ui/webkit-
  options.d/www.facebook.com.conf is installed by the account-plugin-
  facebook package (used by Unity) and by kaccount-providers (used by
  KDE). See this bug's duplicates to see actual bug reports.

  [Test Case] Install both account-plugin-facebook and kaccount-
  providers and you'll get the conflict.

  [Regression Potential] Users running KDE will be completely unaffected
  by this. Users running Unity might see a change when creating accounts
  in System Settings->Online Accounts: with this bugfix, the account's
  display name is obtained by making a REST API call to the remote
  service, rather than by scrapping the DOM of the server webpages
  (which is a hack, and prone to errors if the providers' webpage
  changes). The new way of retrieving the username is the proper one,
  and it's been tested to work reliably. In any case, the worst thing
  that might happen is that accounts get created with an empty display
  name, which is mostly an aesthetic problem (the display name is used
  only for UI purposes).

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1565772/+subscriptions

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

[Touch-packages] [Bug 1597453] Re: [MIR] content-hub

[Sebastien Bacher]

** Description changed:

  [Availability]
-  * Available in universe
-  
+  * Available in universe
+ 
  [Rationale]
-  * This package is required by unity8
-  
+  * This package is required by unity8
+ 
  [Security]
-  * No known security issues at this time.  It has been reviewed by security 
in the past for use on the phone.
-  
+  * No known security issues at this time.  It has been reviewed by security 
in the past for use on the phone.
+ 
  [Quality assurance]
-  * This package has both unit tests and autopkgtests
-  
+  * This package has both unit tests and autopkgtests
+ 
  [Dependencies]
-  Most dependencies are already in main with the exception of the following:
-  * ubuntu-download-manager
-  * qtbase-opensource-src-gles (the non-gles variant is in main)
-  
+  Most dependencies are already in main with the exception of the following:
+  * ubuntu-download-manager (bug #1488425)
+  * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)
+ 
  [Standards compliance]
-  * This package uses cmake and is properly translated. 
-  
+  * This package uses cmake and is properly translated.
+ 
  [Maintenance]
-  * This package is maintained by Canonical and actively in use on the phone 
images
+  * This package is maintained by Canonical and actively in use on the phone 
images

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

Title:
  [MIR] content-hub

Status in content-hub package in Ubuntu:
  New

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time.  It has been reviewed by security 
in the past for use on the phone.

  [Quality assurance]
   * This package has both unit tests and autopkgtests

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * ubuntu-download-manager (bug #1488425)
   * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1597453/+subscriptions

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

[Touch-packages] [Bug 1597453] [NEW] [MIR] content-hub

[Ken VanDine]

Public bug reported:

[Availability]
 * Available in universe

[Rationale]
 * This package is required by unity8

[Security]
 * No known security issues at this time.  It has been reviewed by security in 
the past for use on the phone.

[Quality assurance]
 * This package has both unit tests and autopkgtests

[Dependencies]
 Most dependencies are already in main with the exception of the following:
 * ubuntu-download-manager (bug #1488425)
 * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need a 
MIR?)

[Standards compliance]
 * This package uses cmake and is properly translated.

[Maintenance]
 * This package is maintained by Canonical and actively in use on the phone 
images

** Affects: content-hub (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [MIR] content-hub

Status in content-hub package in Ubuntu:
  New

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by unity8

  [Security]
   * No known security issues at this time.  It has been reviewed by security 
in the past for use on the phone.

  [Quality assurance]
   * This package has both unit tests and autopkgtests

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * ubuntu-download-manager (bug #1488425)
   * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need 
a MIR?)

  [Standards compliance]
   * This package uses cmake and is properly translated.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1597453/+subscriptions

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

[Touch-packages] [Bug 1525147] Re: webapp-container needs some help

[David Barth]

** Changed in: webapps-sprint
Milestone: sprint-20 => backlog

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

Title:
  webapp-container needs some help

Status in webapps-sprint:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  webapp-container doesn't provide much help on the command line:

  $ webapp-container 
  Could not open manifest file:  
"/usr/share/unity-webapps/userscripts/unity-webapps-amazon/manifest.json" 
  Invalid webapps installation found:  
"/usr/share/unity-webapps/userscripts/unity-webapps-amazon" 
  Using Oxide as the web engine backend 
  QQmlComponent: Component destroyed while completion pending

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1525147/+subscriptions

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

[Touch-packages] [Bug 1595673] Re: Cannot access teamweek.com (site reports browser too old)

[Olivier Tilloy]

Awesome, that’s reactivity and customer care indeed!

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Invalid

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

Title:
  Cannot access teamweek.com (site reports browser too old)

Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  When trying to open the site https://app.teamweek.com the screen is
  overlaid with a warning that the browser is too old.

  The warning cannot be confirmed, since the button seems to be off
  screen. Also there is no other way to get rid of the message.

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

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

[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history

[Jeremy Bicha]

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

** Bug watch added: freedesktop.org Bugzilla #94497
   https://bugs.freedesktop.org/show_bug.cgi?id=94497

** Also affects: accountsservice via
   https://bugs.freedesktop.org/show_bug.cgi?id=94497
   Importance: Unknown
   Status: Unknown

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

Title:
  User accounts login history showing incorrect history

Status in accountsservice:
  Unknown
Status in gnome-control-center:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in accountsservice package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I have found that in "System Settings > User Accounts" that if you
  select an account and then select the button called "History" (which
  is meant to show the login history for that account), it will show you
  when you last logged in as "Session Started", but it will show that
  you "Session Ended" just before you login the next time.

  To clarify what I mean, let's say that yesterday I logged into my
  account on this machine at 14:29, and then sometime near 23:00 I
  logged out, and then this morning I logged into my account somewhere
  around 11:20, it will show this:

  Today 11:20 Session Started
  Today 11:19 Session Ended
  Yesterday, 14:29 Session Started

  So it assumes that the last session ended when you log into a new one,
  so the bug seems to be that it does not log when a session ends
  properly, and only logs it when a new session starts.

  I have attached a screenshot to show my example as I see it in the
  History GUI.

  I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, and
  Ubuntu GNOME 15.10 with GNOME 3.18.

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

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

[Touch-packages] [Bug 1597445] [NEW] package linux-image-4.4.0-28-generic 4.4.0-28.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127

[Juan C. Garza!]

Public bug reported:

I was updating the kernal headers using symantic and it crashed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-28-generic 4.4.0-28.47
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vergon 7022 F pulseaudio
Date: Wed Jun 29 12:10:45 2016
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 127
HibernationDevice: RESUME=UUID=c10d442c-ed19-4e49-a6a1-50932e56369d
InstallationDate: Installed on 2016-05-29 (30 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=/dev/mapper/lubuntu--vg-root ro priority=low edd=on nodmraid quiet splash 
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3
SourcePackage: initramfs-tools
Title: package linux-image-4.4.0-28-generic 4.4.0-28.47 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 127
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2008
dmi.bios.vendor: Phoenix
dmi.bios.version: F.2A
dmi.board.name: 30CD
dmi.board.vendor: Wistron
dmi.board.version: 80.52
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenix:bvrF.2A:bd03/25/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2A:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv2700 Notebook PC
dmi.product.version: F.2A
dmi.sys.vendor: Hewlett-Packard

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 third-party-packages xenial

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

Title:
  package linux-image-4.4.0-28-generic 4.4.0-28.47 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 127

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I was updating the kernal headers using symantic and it crashed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vergon 7022 F pulseaudio
  Date: Wed Jun 29 12:10:45 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 127
  HibernationDevice: RESUME=UUID=c10d442c-ed19-4e49-a6a1-50932e56369d
  InstallationDate: Installed on 2016-05-29 (30 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=/dev/mapper/lubuntu--vg-root ro priority=low edd=on nodmraid quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-28-generic 4.4.0-28.47 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2008
  dmi.bios.vendor: Phoenix
  dmi.bios.version: F.2A
  dmi.board.name: 30CD
  dmi.board.vendor: Wistron
  dmi.board.version: 80.52
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrF.2A:bd03/25/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2A:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv2700 Notebook PC
  dmi.product.version: F.2A
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1597445/+subscriptions

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

[Touch-packages] [Bug 1597445] Re: package linux-image-4.4.0-28-generic 4.4.0-28.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.4.0-28-generic 4.4.0-28.47 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 127

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I was updating the kernal headers using symantic and it crashed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vergon 7022 F pulseaudio
  Date: Wed Jun 29 12:10:45 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 127
  HibernationDevice: RESUME=UUID=c10d442c-ed19-4e49-a6a1-50932e56369d
  InstallationDate: Installed on 2016-05-29 (30 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=/dev/mapper/lubuntu--vg-root ro priority=low edd=on nodmraid quiet splash 
vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-28-generic 4.4.0-28.47 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2008
  dmi.bios.vendor: Phoenix
  dmi.bios.version: F.2A
  dmi.board.name: 30CD
  dmi.board.vendor: Wistron
  dmi.board.version: 80.52
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrF.2A:bd03/25/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2A:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv2700 Notebook PC
  dmi.product.version: F.2A
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1597445/+subscriptions

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

[Touch-packages] [Bug 1377096] Re: [OSK] Ubuntu Touch should allow alternative keyboard layouts

[Andrew Gryaznov]

looking at the keyboard source code - it indeed looks impossible not
only to add custom symbols without recompiling - but no modifier keys
are ever possible to be sent as the keyboard acts as text editor (for
autocorrect, etc) and does not directly send keycode events to Mir. So
there does not seem to be any straightforward way to enable modifier or
any special keys.

It may be easier to implement sending direct keyboard events as a
separate service and then crafting a client into ubuntu-keyboard to talk
to it and use the keyboard as an UI only to send real events, like have
a "^C" button, etc.. otherwise it will require a huge rewrite of the
logic

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

Title:
  [OSK] Ubuntu Touch should allow alternative keyboard layouts

Status in Ubuntu UX:
  Triaged
Status in ubuntu-keyboard package in Ubuntu:
  Triaged

Bug description:
  It would be nice if alternative keyboard layouts were available for
  Ubuntu Touch.

  On Android devices I use the Hacker's Keyboard
  https://code.google.com/p/hackerskeyboard/ from F-Droid
  
https://f-droid.org/repository/browse/?fdfilter=org.pocketworkstation.pckeyboard=org.pocketworkstation.pckeyboard
  as this allows customisation and easy access to keys such as Ctrl,
  Esc, !, : and - and these are keys that take a lot of key presses with
  the current Ubuntu touch keyboard (I use vim). In addition key
  combinations such as Ctrl-n and Ctrl-p (next and previous channel in
  IRSSI) are not possible with the current Ubuntu Touch keyboard.

  Having said the above the gestures, double tap for tab, swipe up, down
  , left and right for the arrow keys is great and I now find myself
  trying to use these gestures on Android devices...

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

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

[Touch-packages] [Bug 1595673] Re: Cannot access teamweek.com (site reports browser too old)

[flohack]

They updated their site in one day. Seem to care for their customers ;)
=> Can be closed.

BR

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

Title:
  Cannot access teamweek.com (site reports browser too old)

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When trying to open the site https://app.teamweek.com the screen is
  overlaid with a warning that the browser is too old.

  The warning cannot be confirmed, since the button seems to be off
  screen. Also there is no other way to get rid of the message.

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

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

[Touch-packages] [Bug 1597439] [NEW] [MIR] zeromq3

[Sebastien Bacher]

Public bug reported:

Trying to get unity8 in main this cycle, that's one of the depends of
unity-scopes-api (MIR to come)

* availability
it's available/built on all the ubuntu architectures, 
https://launchpad.net/ubuntu/+source/zeromq3/4.1.4-7

* security
the trusty version has some open CVEs which seem to have been resolved in the 
newer versions/series of Ubuntu
http://people.canonical.com/~ubuntu-security/cve/pkg/zeromq3.html

* quality
- the package is well maintained in Debian
- it works out of the box with no configuration required
- it has a testsuite which is used during build but currently has some errors 
and doesn't stop the build
 
* dependencies
requires libsodium which is universe

* standards compliance
FHS and Debian Policy compliant.

* ubuntu maintainance
the desktop team is going to look after it, desktop-bugs has been subscribed

* background
no specific info

** Affects: zeromq3 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [MIR] zeromq3

Status in zeromq3 package in Ubuntu:
  New

Bug description:
  Trying to get unity8 in main this cycle, that's one of the depends of
  unity-scopes-api (MIR to come)

  * availability
  it's available/built on all the ubuntu architectures, 
https://launchpad.net/ubuntu/+source/zeromq3/4.1.4-7

  * security
  the trusty version has some open CVEs which seem to have been resolved in the 
newer versions/series of Ubuntu
  http://people.canonical.com/~ubuntu-security/cve/pkg/zeromq3.html

  * quality
  - the package is well maintained in Debian
  - it works out of the box with no configuration required
  - it has a testsuite which is used during build but currently has some errors 
and doesn't stop the build
   
  * dependencies
  requires libsodium which is universe

  * standards compliance
  FHS and Debian Policy compliant.

  * ubuntu maintainance
  the desktop team is going to look after it, desktop-bugs has been subscribed

  * background
  no specific info

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

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

[Touch-packages] [Bug 1597436] Re: [MIR] zeromq3

[Sebastien Bacher]

** Changed in: zeromq3 (Ubuntu)
   Status: New => Invalid

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

Title:
  [MIR] zeromq3

Status in zeromq3 package in Ubuntu:
  Invalid

Bug description:
  Trying to get unity8 in main this cycle, that's one of the depends of
  unity-scopes-api (MIR to come)

  * availability

  it's available/built on all the ubuntu architectures,
  https://launchpad.net/ubuntu/+source/zeromq3/4.1.4-7

  * security

  the trusty version has some open CVEs which seem to have been resolved in the 
newer versions/series of Ubuntu
  http://people.canonical.com/~ubuntu-security/cve/pkg/zeromq3.html

  * quality

  - the package is well maintained in Debian
  - it works out of the box with no configuration required
  - it has a testsuite which is used during build but currently has some errors 
and doesn't stop the build
   
  * dependencies

  requires libsodium which is universe

  * ubuntu maintainance

  the desktop team is going to look after it, desktop-bugs has been
  subscribed

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

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

[Touch-packages] [Bug 1597436] [NEW] [MIR] zeromq3

[Sebastien Bacher]

Public bug reported:

Trying to get unity8 in main this cycle, that's one of the depends of
unity-scopes-api (MIR to come)

* availability

it's available/built on all the ubuntu architectures,
https://launchpad.net/ubuntu/+source/zeromq3/4.1.4-7

* security

the trusty version has some open CVEs which seem to have been resolved in the 
newer versions/series of Ubuntu
http://people.canonical.com/~ubuntu-security/cve/pkg/zeromq3.html

* quality

- the package is well maintained in Debian
- it works out of the box with no configuration required
- it has a testsuite which is used during build but currently has some errors 
and doesn't stop the build
 
* dependencies

requires libsodium which is universe

* ubuntu maintainance

the desktop team is going to look after it, desktop-bugs has been
subscribed

** Affects: zeromq3 (Ubuntu)
 Importance: Undecided
 Status: Invalid

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

Title:
  [MIR] zeromq3

Status in zeromq3 package in Ubuntu:
  Invalid

Bug description:
  Trying to get unity8 in main this cycle, that's one of the depends of
  unity-scopes-api (MIR to come)

  * availability

  it's available/built on all the ubuntu architectures,
  https://launchpad.net/ubuntu/+source/zeromq3/4.1.4-7

  * security

  the trusty version has some open CVEs which seem to have been resolved in the 
newer versions/series of Ubuntu
  http://people.canonical.com/~ubuntu-security/cve/pkg/zeromq3.html

  * quality

  - the package is well maintained in Debian
  - it works out of the box with no configuration required
  - it has a testsuite which is used during build but currently has some errors 
and doesn't stop the build
   
  * dependencies

  requires libsodium which is universe

  * ubuntu maintainance

  the desktop team is going to look after it, desktop-bugs has been
  subscribed

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

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

[Touch-packages] [Bug 1597364] Re: Option for screen dimming is sometimes not visible

[Pat McGowan]

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

** This bug has been marked a duplicate of bug 1540804
   race condition between android container and powerd may disable auto 
brightness availability

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

Title:
  Option for screen dimming is sometimes not visible

Status in Canonical System Image:
  Confirmed
Status in powerd package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  In System Settings, the option for automatic screen dimming is
  sometimes not visible. I observed this behaviour on a Meizu Pro 5.

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

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

[Touch-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/unity-settings-daemon/unity-settings-
daemon-ubuntu-xenial-landing-063

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

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Confirmed
Status in upower source package in Xenial:
  Fix Committed

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

  
  To reset the idle-delay, just call
gsettings reset org.gnome.desktop.session idle-delay

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+subscriptions

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

[Touch-packages] [Bug 1506744] Re: Newly installed applications do not show in the dash

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/libunity/libunity-ubuntu-xenial-
landing-063

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

Title:
  Newly installed applications do not show in the dash

Status in GLib:
  Confirmed
Status in gnome-menus package in Ubuntu:
  Fix Released
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid

Bug description:
  I am running 15.10 development version fully up to date, I installed
  it a few days ago and I have an issue with newly installed
  applications not appearing in the dash when I search for them, they
  can be started via console but the icons/launchers of newly installed
  applications will only appear in the dash after session is restarted.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20151002.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 16 08:41:39 2015
  InstallationDate: Installed on 2015-10-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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