[Touch-packages] [Bug 1575893] Re: Toolbar focus & keyboard navigation

[Christian Dywan]

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

** Description changed:

  Toolbar needs focus for keyboard navigation that works in the same way
  as the Sections.
  
- These two bugs need to be fixed first:
- 
- - https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1611327
- - https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1614541
+ Bug 1611327 and bug 1614541 need to be fixed first.

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

Title:
  Toolbar focus & keyboard navigation

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  Toolbar needs focus for keyboard navigation that works in the same way
  as the Sections.

  Bug 1611327 and bug 1614541 need to be fixed first.

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

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

[Touch-packages] [Bug 1628161] Re: SlotsLayout height is not dynamically updated when main paddings change

[Christian Dywan]

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

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

Title:
  SlotsLayout height is not dynamically updated when main paddings
  change

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

Bug description:
  You can see this in the attached testcase.

  When paddings are changed, the SlotsLayout height is not updated
  dynamically.

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

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

[Touch-packages] [Bug 1625584] Re: Removing libnss-* does not remove corresponding options

[Martin Pitt]

I ran the test case on a xenial-proposed machine successfully.

** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1625584

Title:
  Removing libnss-* does not remove corresponding options

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  libnss-{resolve,mymachines,myhostname} automatically add/remove
  themselves from /etc/nsswitch.conf on installation/removal.

  But when (manually) adding NSS action specifiers, these do not get
  removed along.

  SRU FIX: https://anonscm.debian.org/cgit/pkg-
  systemd/systemd.git/commit/?h=ubuntu-xenial=2d08d7e481

  TEST CASE:
    * Install libnss-mymachines. This will change the "hosts" line in 
/etc/nsswitch.conf from e. g. "files dns" to "files dns mymachines".
    * Edit the file to add an action specifier: "files dns mymachines 
[!UNAVAIL=return]"
    * Remove/purge libnss-mymachines.
    * In current xenial (229-4ubuntu7)/yakkety (231-6) the hosts line ends up 
as "files dns [!UNAVAIL=return]", i. e. the action specifier now applies to 
"dns" but should have been removed.
    * With the fixed version, the action specifier is completely gone.
    * Re-test with installing libnss-resolve (which inserts itself before 
"dns") and modifying to "files resolve [!UNAVAIL=return] dns [foo=bar]", then 
purge libnss-resolve again -- this should again remove the [!UNAVAIL=return] 
but *NOT* "dns [foo=bar]".

  Regression potential: This only affects package removal, so upgrades
  or new installs are not affected. Removals of
  libnss-{mymachines,myhostname,resolvle} must be tested carefully to
  ensure that they don't break nsswitch.conf in any way.

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

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

[Touch-packages] [Bug 1628687] Re: Assertion failure when PID 1 receives a zero-length message over notify socket

[Martin Pitt]

I verified that with the -proposed version you cannot create orphaned
notify FDs any more in pid 1 using the test case I just added.

** Description changed:

  Environment:
  
  Xenial 16.04.1
  Amd64
  
  Description.
  
  Systemd fails an assertion in manager_invoke_notify_message when a zero-
  length message is received over /run/systemd/notify. This allows a local
  user to perform a denial-of-service attack against PID 1.
  
  How to trigger the bug:
  
  $ while true; do NOTIFY_SOCKET=/run/systemd/notify systemd-notify "";
  done
  
  The following entries are written into /var/log/syslog, at this point
  systemd is crashed.
  
  Sep 28 20:57:20 ubuntu systemd[1]: Started User Manager for UID 1000.
  Sep 28 20:57:28 ubuntu systemd[1]: Assertion 'n > 0' failed at 
../src/core/manager.c:1501, function manager_invoke_notify_message(). Aborting.
  Sep 28 20:57:29 ubuntu systemd[1]: Caught , dumped core as pid 1307.
  Sep 28 20:57:29 ubuntu systemd[1]: Freezing execution.
  
+ Public bug: https://github.com/systemd/systemd/issues/4234
  
- Public bug: https://github.com/systemd/systemd/issues/4234
+ The original USN/security fix in
+ https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu10 introduced
+ another local DoS due to fd exhaustion:
+ 
+   NOTIFY_SOCKET=/run/systemd/notify python3 -c 'from systemd import
+ daemon; daemon.notify("", fds=[0]*100)'
+ 
+ Run this a few times and watch "sudo ls -l /proc/1/fd" grow.

** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1628687

Title:
  Assertion failure when PID 1 receives a zero-length message over
  notify socket

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Released

Bug description:
  Environment:

  Xenial 16.04.1
  Amd64

  Description.

  Systemd fails an assertion in manager_invoke_notify_message when a
  zero-length message is received over /run/systemd/notify. This allows
  a local user to perform a denial-of-service attack against PID 1.

  How to trigger the bug:

  $ while true; do NOTIFY_SOCKET=/run/systemd/notify systemd-notify "";
  done

  The following entries are written into /var/log/syslog, at this point
  systemd is crashed.

  Sep 28 20:57:20 ubuntu systemd[1]: Started User Manager for UID 1000.
  Sep 28 20:57:28 ubuntu systemd[1]: Assertion 'n > 0' failed at 
../src/core/manager.c:1501, function manager_invoke_notify_message(). Aborting.
  Sep 28 20:57:29 ubuntu systemd[1]: Caught , dumped core as pid 1307.
  Sep 28 20:57:29 ubuntu systemd[1]: Freezing execution.

  Public bug: https://github.com/systemd/systemd/issues/4234

  The original USN/security fix in
  https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu10 introduced
  another local DoS due to fd exhaustion:

NOTIFY_SOCKET=/run/systemd/notify python3 -c 'from systemd import
  daemon; daemon.notify("", fds=[0]*100)'

  Run this a few times and watch "sudo ls -l /proc/1/fd" grow.

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

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

[Touch-packages] [Bug 1627641] Re: Backport netplan to xenial

[Martin Pitt]

systemd's and netplan's tests now work:
  
http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#systemd
  
http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#nplan

nplan's tests still show a race condition on ppc64el, but this isn't a
regression.

network-manager's tests also all work:
  
http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#network-manager

I ran the above test cases on a 16.04.1 desktop (--print-config is
identical, verifying existing connections still work), and NM still
generally works.

** 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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1627641

Title:
  Backport netplan to xenial

Status in network-manager package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in nplan source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  For snappy (at first at least) we need to provide netplan in xenial,
  as for the first snappy GA release we must not use any PPAs any more.

  netplan's NetworkManager backend depends on two patches to read
  configuration and connections from /run/NetworkManager/. These will
  need to be backported for full netplan support; but they are not
  required for snappy as this will use a snapped NM. However, this will
  need a temporary hack
  (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607)
  until snaps can actually properly support OS components like
  NetworkManager.

  PATCHES:
  
https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial=6dcdb85
  
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=4e9c52b0bb

  REGRESSION POTENTIAL:
  netplan: The risk for existing installations is practically zero as nplan 
does not exist in xenial yet and thus will not be pulled in during upgrades.

  NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/
  and as it's an ephemeral tmpfs there is no risk of existing files
  there. If the patches are broken it could in theory happen that
  NetworkManager also does not properly read files from
  /etc/NetworkManager/ any more, so the -proposed package must verify
  that existing connections still work.

  systemd: This does change behavior of networkd quite a bit: RA is now
  being handled in userpsace instead of the kernel, there are some new
  virtual device types, LLDP support, etc., and there are no (known)
  backwards incompatibilities. The 229 version was known buggy with
  DHCPv6 (we disabled these two test cases), and judging by the feedback
  in Debian 231 is now reasonably stable. networkd is not being used by
  default or advertised in Ubuntu 16.04 (so far), so this will not
  affect the vast majority of installations. But while we have quite
  good test coverage, it cannot be ruled out that we break some custom
  setup that uses networkd.

  TEST PLAN:
  1. Run "NetworkManager --print-config" and save the output.
  2. Install the proposed NetworkManager and confirm that existing connections 
(from /etc/NetworkManager/system-connections) still work.
  3. Run "NetworkManager --print-config" again and verify that the output is 
the same as in step 1.
  4. netplan has a very comprehensive integration test suite run as 
autopkgtest, which covers NetworkManager (including the /run patches) and 
network. Confirm that it succeeds.

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

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

[Touch-packages] [Bug 1628287] Re: systemd-resolved crashed with SIGABRT in log_assert_failed()

[Launchpad Bug Tracker]

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

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

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

Title:
  systemd-resolved crashed with SIGABRT in log_assert_failed()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I don't know

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-6git1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 26 17:02:18 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2015-04-29 (517 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: GOOGLE Samus
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   log_assert_failed () from /lib/systemd/libsystemd-shared-231.so
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-resolved crashed with SIGABRT in log_assert_failed()
  UpgradeStatus: Upgraded to yakkety on 2016-09-26 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 02/25/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd02/25/2015:svnGOOGLE:pnSamus:pvrMP.A:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Samus
  dmi.product.version: MP.A
  dmi.sys.vendor: GOOGLE

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

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

[Touch-packages] [Bug 1630860] Re: [HDA-Intel - HDA Intel PCH, playback] Playback problem

[wjl]

** Attachment added: "Screenshot without dock (expected behaviour)"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1630860/+attachment/4755671/+files/Screenshot%20from%202016-10-05%2008%3A19%3A52.png

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Lenovo Thinkpad P50 with docking station

  Issues: Headphone jack on station not detected; no sound (works without 
docking station)
  Issues: Sound via HDMI on station not detected; no sound (works without 
docking station)

  Since all outputs are routed via the Thunderbolt chip, my guess is
  that it's related to the pin setup (lenovo-dock) in Alsa. Without the
  dock, everything works, headphone/mic jack on the P50 itself is
  hotplug (switches from speaker to headphones right away).

  Screenshots (with and without docking station) attached.

  Thanks and LG,
  Wolfgang

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: symap_custom_dkms_x86_64 nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wjl2943 F pulseaudio
   /dev/snd/controlC0:  wjl2943 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Oct  5 14:14:02 2016
  InstallationDate: Installed on 2016-09-10 (24 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: HDA NVidia - HDA NVidia
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET52W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS1EH0B
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET52W(1.26):bd05/10/2016:svnLENOVO:pn20EQS1EH0B:pvrThinkPadP50:rvnLENOVO:rn20EQS1EH0B:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20EQS1EH0B
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-10-04T12:48:36.270399

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

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

[Touch-packages] [Bug 1630860] [NEW] [HDA-Intel - HDA Intel PCH, playback] Playback problem

[wjl]

Public bug reported:

Lenovo Thinkpad P50 with docking station

Issues: Headphone jack on station not detected; no sound (works without docking 
station)
Issues: Sound via HDMI on station not detected; no sound (works without docking 
station)

Since all outputs are routed via the Thunderbolt chip, my guess is that
it's related to the pin setup (lenovo-dock) in Alsa. Without the dock,
everything works, headphone/mic jack on the P50 itself is hotplug
(switches from speaker to headphones right away).

Screenshots (with and without docking station) attached.

Thanks and LG,
Wolfgang

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: symap_custom_dkms_x86_64 nvidia
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  wjl2943 F pulseaudio
 /dev/snd/controlC0:  wjl2943 F pulseaudio
CurrentDesktop: Unity
Date: Wed Oct  5 14:14:02 2016
InstallationDate: Installed on 2016-09-10 (24 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: HDA NVidia - HDA NVidia
Symptom_Type: Only some of outputs are working
Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/10/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET52W (1.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EQS1EH0B
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET52W(1.26):bd05/10/2016:svnLENOVO:pn20EQS1EH0B:pvrThinkPadP50:rvnLENOVO:rn20EQS1EH0B:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20EQS1EH0B
dmi.product.version: ThinkPad P50
dmi.sys.vendor: LENOVO
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-10-04T12:48:36.270399

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

** Attachment added: "Screenshot from 2016-10-05 08:29:36.png"
   
https://bugs.launchpad.net/bugs/1630860/+attachment/4755663/+files/Screenshot%20from%202016-10-05%2008%3A29%3A36.png

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Lenovo Thinkpad P50 with docking station

  Issues: Headphone jack on station not detected; no sound (works without 
docking station)
  Issues: Sound via HDMI on station not detected; no sound (works without 
docking station)

  Since all outputs are routed via the Thunderbolt chip, my guess is
  that it's related to the pin setup (lenovo-dock) in Alsa. Without the
  dock, everything works, headphone/mic jack on the P50 itself is
  hotplug (switches from speaker to headphones right away).

  Screenshots (with and without docking station) attached.

  Thanks and LG,
  Wolfgang

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: symap_custom_dkms_x86_64 nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wjl2943 F pulseaudio
   /dev/snd/controlC0:  wjl2943 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Oct  5 14:14:02 2016
  InstallationDate: Installed on 2016-09-10 (24 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: HDA NVidia - HDA NVidia
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET52W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS1EH0B
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET52W(1.26):bd05/10/2016:svnLENOVO:pn20EQS1EH0B:pvrThinkPadP50:rvnLENOVO:rn20EQS1EH0B:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 

[Touch-packages] [Bug 1502145] Re: Apps can keep screen lit permanently

[Bob Harvey]

M10 tablet, OTA13

I had not seen this problem until I installed OTA13.

Now my screen never blanks.

I pretty much only use the web browser app.

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

Title:
  Apps can keep screen lit permanently

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Fix Released
Status in Oxide 1.10 series:
  Fix Released
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  rc-proposed, r140, krillin

  There are times when it seems the display blanking policy stops
  working and the display stays on until I press the power button.

  Steps to reproduce:
  * install and start Siete
  * put it in background

  Expected outcome:
  * the display is switched off after a predetermined amount of time

  Actual outcome:
  * the display stays on forever

  ==

  Now that apps can request the screen to stay on, they can do so
  regardless of whether they're focused/visible or not.

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[Launchpad Bug Tracker]

This bug was fixed in the package open-iscsi -
2.0.873+git0.3b4b4500-14ubuntu8

---
open-iscsi (2.0.873+git0.3b4b4500-14ubuntu8) yakkety; urgency=medium

  * debian/tests/xkvm: don't --enable-kvm.

 -- Mathieu Trudel-Lapierre   Wed, 05 Oct 2016
12:58:21 -0400

** Changed in: open-iscsi (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Confirmed
Status in open-iscsi source package in Xenial:
  Fix Released
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
* bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

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

[Touch-packages] [Bug 1621507] Update Released

[Steve Langasek]

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

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Confirmed
Status in open-iscsi source package in Xenial:
  Fix Released
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
* bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[Launchpad Bug Tracker]

This bug was fixed in the package open-iscsi -
2.0.873+git0.3b4b4500-14ubuntu3.1

---
open-iscsi (2.0.873+git0.3b4b4500-14ubuntu3.1) xenial; urgency=medium

  * add support for IPV6{DOMAINSEARCH,DNS0,DNS1} to net-interface-handler
(LP: #1621507)

 -- LaMont Jones   Tue, 20 Sep 2016 08:05:41 -0600

** Changed in: open-iscsi (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Confirmed
Status in open-iscsi source package in Xenial:
  Fix Released
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
* bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

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

[Touch-packages] [Bug 1630839] Re: Request for applying a patch to support OpenVSwitch in hostapd

[Ubuntu Foundations Team Bug Bot]

The attachment "Patch I've applied to Ubuntu upstream wpa source
package." seems to be a patch.  If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Request for applying a patch to support OpenVSwitch in  hostapd

Status in wpa package in Ubuntu:
  New

Bug description:
  Hello Devs,

  I'm requesting the patch https://github.com/helmut-
  jacob/hostapd/commit/c89daaeca4ee90c8bc158e37acb1b679c823d7ab to be
  applied in hostapd in Ubuntu. I compiled wpa-2.4 from Ubuntu sources
  with the attached patch and worked well with ath9k_htc + OpenVSwitch
  from Ubuntu 16.04.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hostapd 1:2.4-0ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct  5 23:40:38 2016
  InstallationDate: Installed on 2016-01-14 (266 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to xenial on 2016-05-13 (145 days ago)
  modified.conffile..etc.default.hostapd: [modified]
  mtime.conffile..etc.default.hostapd: 2016-10-05T00:16:08.475114

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.122ubuntu8.3

---
initramfs-tools (0.122ubuntu8.3) xenial; urgency=medium

  * scripts/functions: make sure we can try to start all available and suitable
interfaces if ip= isn't set when setting up the network, and exit as soon
as we get an IP address. This retains the old behavior from ipconfig when
ip= is unset, for really simple remote-root scenarios. (LP: #1628306)
  * scripts/functions: retain bootp/rarp behavior using ipconfig.

 -- Mathieu Trudel-Lapierre   Tue, 27 Sep 2016
16:27:38 -0400

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Confirmed
Status in open-iscsi source package in Xenial:
  Fix Released
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
* bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

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

[Touch-packages] [Bug 1628306] Re: network booting fails for iscsi root if no ip is set

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.122ubuntu8.3

---
initramfs-tools (0.122ubuntu8.3) xenial; urgency=medium

  * scripts/functions: make sure we can try to start all available and suitable
interfaces if ip= isn't set when setting up the network, and exit as soon
as we get an IP address. This retains the old behavior from ipconfig when
ip= is unset, for really simple remote-root scenarios. (LP: #1628306)
  * scripts/functions: retain bootp/rarp behavior using ipconfig.

 -- Mathieu Trudel-Lapierre   Tue, 27 Sep 2016
16:27:38 -0400

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  network booting fails for iscsi root if no ip is set

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Remote-root installs (eg. / over iscsi and similar) where the configuration 
is simple, and no extra parameters are included on the kernel command-line (as 
opposed to MaaS specifying everything).

  [Test case]
  1) do an installation with /boot on a local disk and / and swap over a remote 
LUN (iSCSI is simple to do).
  2) Update to initramfs-tools with isc-dhcp support.

  [Regression potential]
  This is in itself a fix for a regression found in initramfs-tools 
(0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial). Failure to boot on a 
remote root filesystem would constitue a regression.

  --

  I did a new install with /boot on /dev/sda, and everything else (/ and
  swap) on an iSCSI LUN.

  Booting this with initramfs-tools using ipconfig works without issues.

  Booting this with initramfs-tools (0.125ubuntu4 on yakkety, or
  0.122ubuntu8.2 on xenial) fails because no interface is specified.

  This appears to be because ipconfig interprets "" as meaning to try
  every interface until one works (or all fail), whereas calling
  dhclient without an interface name simply returns a failure.

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

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

[Touch-packages] [Bug 1628306] Update Released

[Steve Langasek]

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

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

Title:
  network booting fails for iscsi root if no ip is set

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Remote-root installs (eg. / over iscsi and similar) where the configuration 
is simple, and no extra parameters are included on the kernel command-line (as 
opposed to MaaS specifying everything).

  [Test case]
  1) do an installation with /boot on a local disk and / and swap over a remote 
LUN (iSCSI is simple to do).
  2) Update to initramfs-tools with isc-dhcp support.

  [Regression potential]
  This is in itself a fix for a regression found in initramfs-tools 
(0.125ubuntu4 on yakkety, or 0.122ubuntu8.2 on xenial). Failure to boot on a 
remote root filesystem would constitue a regression.

  --

  I did a new install with /boot on /dev/sda, and everything else (/ and
  swap) on an iSCSI LUN.

  Booting this with initramfs-tools using ipconfig works without issues.

  Booting this with initramfs-tools (0.125ubuntu4 on yakkety, or
  0.122ubuntu8.2 on xenial) fails because no interface is specified.

  This appears to be because ipconfig interprets "" as meaning to try
  every interface until one works (or all fail), whereas calling
  dhclient without an interface name simply returns a failure.

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

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

[Touch-packages] [Bug 1630850] Re: package initramfs-tools 0.125ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[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/1630850

Title:
  package initramfs-tools 0.125ubuntu3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Plugged a Logitech wireless mouse dongle into a USB3 port

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: initramfs-tools 0.125ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Oct  5 19:27:14 2016
  DpkgTerminalLog:
   Setting up initramfs-tools (0.125ubuntu3) ...
   sudoupdate-initramfs: deferring update (trigger activated)
   cp: cannot create regular file '/cdrom/casper/initrd.gz.new': No such file 
or directory
   dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc4ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu3 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/1630850/+subscriptions

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

[Touch-packages] [Bug 1630850] [NEW] package initramfs-tools 0.125ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[me]

Public bug reported:

Plugged a Logitech wireless mouse dongle into a USB3 port

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: initramfs-tools 0.125ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
Uname: Linux 4.8.0-14-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
AptOrdering: NULL: ConfigurePending
Architecture: amd64
Date: Wed Oct  5 19:27:14 2016
DpkgTerminalLog:
 Setting up initramfs-tools (0.125ubuntu3) ...
 sudoupdate-initramfs: deferring update (trigger activated)
 cp: cannot create regular file '/cdrom/casper/initrd.gz.new': No such file or 
directory
 dpkg: error processing package initramfs-tools (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3~rc4ubuntu1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.125ubuntu3 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 yakkety

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

Title:
  package initramfs-tools 0.125ubuntu3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Plugged a Logitech wireless mouse dongle into a USB3 port

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: initramfs-tools 0.125ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7
  Uname: Linux 4.8.0-14-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Oct  5 19:27:14 2016
  DpkgTerminalLog:
   Setting up initramfs-tools (0.125ubuntu3) ...
   sudoupdate-initramfs: deferring update (trigger activated)
   cp: cannot create regular file '/cdrom/casper/initrd.gz.new': No such file 
or directory
   dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc4ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.125ubuntu3 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/1630850/+subscriptions

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

[Touch-packages] [Bug 1630599] Re: unity8 crashed with SIGSEGV in begin()

[Launchpad Bug Tracker]

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

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

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

Title:
  unity8 crashed with SIGSEGV in begin()

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  I got this crash after trying the Unity 8 session and loggin out.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  5 16:02:06 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2015-10-17 (353 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: unity8 --mode=full-shell
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   qtmir::ApplicationManager::findApplicationWithPid(int) const () from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Unity/Application/libunityapplicationplugin.so
   
qtmir::SessionManager::onSessionStarting(std::shared_ptr 
const&) () from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Unity/Application/libunityapplicationplugin.so
   QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QCoreApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QCoreApplication::notifyInternal2(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: unity8 crashed with SIGSEGV in 
qtmir::ApplicationManager::findApplicationWithPid()
  UpgradeStatus: Upgraded to yakkety on 2016-09-01 (34 days ago)
  UserGroups: adm cdrom dip lpadmin mail plugdev sambashare sudo vboxusers

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

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

[Touch-packages] [Bug 1630846] Re: unity8 crashed with SIGSEGV in qtmir::ApplicationManager::findApplicationWithPid()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1630599, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1630846/+attachment/4755611/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1630846/+attachment/4755613/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1630846/+attachment/4755615/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1630846/+attachment/4755616/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1630846/+attachment/4755617/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1630846/+attachment/4755618/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1630846/+attachment/4755619/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1630599
   unity8 crashed with SIGSEGV in begin()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  unity8 crashed with SIGSEGV in
  qtmir::ApplicationManager::findApplicationWithPid()

Status in unity8 package in Ubuntu:
  New

Bug description:
  unity8 crashed with SIGSEGV in
  qtmir::ApplicationManager::findApplicationWithPid()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  5 16:05:02 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2016-10-05 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161005)
  ProcCmdline: unity8 --mode=full-shell
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fde77d90f4c 
<_ZNK5qtmir18ApplicationManager22findApplicationWithPidEi+12>:  movslq 
0x8(%rax),%rdx
   PC (0x7fde77d90f4c) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   qtmir::ApplicationManager::findApplicationWithPid(int) const () from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Unity/Application/libunityapplicationplugin.so
   
qtmir::SessionManager::onSessionStarting(std::shared_ptr 
const&) () from 
/usr/lib/x86_64-linux-gnu/qt5/qml/Unity/Application/libunityapplicationplugin.so
   QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QCoreApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QCoreApplication::notifyInternal2(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: unity8 crashed with SIGSEGV in 
qtmir::ApplicationManager::findApplicationWithPid()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1630839] [NEW] Request for applying a patch to support OpenVSwitch in hostapd

[Leonardo Silva Amaral]

Public bug reported:

Hello Devs,

I'm requesting the patch https://github.com/helmut-
jacob/hostapd/commit/c89daaeca4ee90c8bc158e37acb1b679c823d7ab to be
applied in hostapd in Ubuntu. I compiled wpa-2.4 from Ubuntu sources
with the attached patch and worked well with ath9k_htc + OpenVSwitch
from Ubuntu 16.04.

Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: hostapd 1:2.4-0ubuntu6
Uname: Linux 4.6.3-040603-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Oct  5 23:40:38 2016
InstallationDate: Installed on 2016-01-14 (266 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
SourcePackage: wpa
UpgradeStatus: Upgraded to xenial on 2016-05-13 (145 days ago)
modified.conffile..etc.default.hostapd: [modified]
mtime.conffile..etc.default.hostapd: 2016-10-05T00:16:08.475114

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


** Tags: amd64 apport-bug xenial

** Patch added: "Patch I've applied to Ubuntu upstream wpa source package."
   
https://bugs.launchpad.net/bugs/1630839/+attachment/4755576/+files/hostapd_openvswitch.patch

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

Title:
  Request for applying a patch to support OpenVSwitch in  hostapd

Status in wpa package in Ubuntu:
  New

Bug description:
  Hello Devs,

  I'm requesting the patch https://github.com/helmut-
  jacob/hostapd/commit/c89daaeca4ee90c8bc158e37acb1b679c823d7ab to be
  applied in hostapd in Ubuntu. I compiled wpa-2.4 from Ubuntu sources
  with the attached patch and worked well with ath9k_htc + OpenVSwitch
  from Ubuntu 16.04.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hostapd 1:2.4-0ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct  5 23:40:38 2016
  InstallationDate: Installed on 2016-01-14 (266 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: wpa
  UpgradeStatus: Upgraded to xenial on 2016-05-13 (145 days ago)
  modified.conffile..etc.default.hostapd: [modified]
  mtime.conffile..etc.default.hostapd: 2016-10-05T00:16:08.475114

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

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

[Touch-packages] [Bug 1630087] Re: Can't log onto Unity8 because can't figure out keyboard layout, as there is no textbox to test it in.

[Akiva]

I was thinking that a keyboard selection test area would suffice, or
maybe a an option to type in the user name.

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

Title:
  Can't log onto Unity8 because can't figure out keyboard layout, as
  there is no textbox to test it in.

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

Bug description:
  I use colemak, and a funky character in my password that requires
  altgr shift level 3.

  On 16.10, logging out of Unity7 brings me to the Unity8 login prompt.
  There is a label with my account name, and a text box for my password.

  I have no idea what I am typing, and what regularly works for me on
  lightdm, is not working for me on Unity8's login prompt. I simply can
  not login.

  I need a way to figure out what I am typing. There is no means to
  figure out what is being typed.

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

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

[Touch-packages] [Bug 1630834] Re: tracker-extract crashed with SIGABRT in raise()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1543354, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1630834/+attachment/479/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1630834/+attachment/4755561/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1630834/+attachment/4755563/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1630834/+attachment/4755564/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1630834/+attachment/4755565/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1630834/+attachment/4755566/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1630834/+attachment/4755567/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1543354

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  tracker-extract crashed with SIGABRT in raise()

Status in tracker package in Ubuntu:
  New

Bug description:
  Every time that I sign into Ubuntu 16.10 Gnome I get this Tracker
  crashed error.

  matthew@stacy-desktop:~$ lsb_release -rd
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  matthew@stacy-desktop:~$ uname -r
  4.8.0-19-generic
  matthew@stacy-desktop:~$ uname -a
  Linux stacy-desktop 4.8.0-19-generic #21-Ubuntu SMP Thu Sep 29 19:39:23 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux
  matthew@stacy-desktop:~$ 

  matthew@stacy-desktop:~$ apt-cache policy tracker
  tracker:
Installed: 1.10.0-1ubuntu1
Candidate: 1.10.0-1ubuntu1
Version table:
   *** 1.10.0-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages
  100 /var/lib/dpkg/status
  matthew@stacy-desktop:~$

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: tracker-extract 1.10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: KDE
  Date: Wed Oct  5 14:35:26 2016
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2014-06-01 (857 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: tracker
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0
  Title: tracker-extract crashed with SIGABRT in raise()
  UpgradeStatus: Upgraded to yakkety on 2016-09-30 (5 days ago)
  UserGroups: adm cdrom dip kismet libvirt libvirtd lpadmin mythtv netdev 
plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1302270] Re: [regression] Poor performance with recent update with i965: libGL error: failed to open drm device: Permission denied

[Daniel van Vugt]

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

Danny: This bug (bug 1415104) was marked as fix released on 2015-02-02.
So if you're still having problems please log a new bug.

I can already tell your problem is that the login hasn't set correct
permissions on /dev/dri/*. This is normal (not a bug) for tty logins,
but should be resolved automatically with graphical logins (lightdm).

Please log a new bug here:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+filebug

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

Title:
  [regression] Poor performance with recent update with i965: libGL
  error: failed to open drm device: Permission denied

Status in Compiz:
  Invalid
Status in Unity:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I rebooted into up to date trusty and noticed Unity was incredibly
  slow. I hadn't rebooted in a while, so I'm not sure what package
  caused the issue, though I'm guessing it is mesa (I saw i965 pci ids
  were ifdef'd in the Launchpad diff, but I didn't look super closely).

  ~/.xsession-errors has this to say:
  libGL error: failed to open drm device: Permission denied
  libGL error: failed to load driver: i965

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr  3 20:08:18 2014
  DistUpgraded: 2013-11-04 08:48:34,282 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:215a]
  InstallationDate: Installed on 2011-06-28 (1010 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110425.2)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 5129CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic 
root=UUID=88689ad2-74b5-442c-9290-8ae60b63e16b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2013-11-04 (150 days ago)
  dmi.bios.date: 02/24/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET64WW (1.34 )
  dmi.board.name: 5129CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET64WW(1.34):bd02/24/2011:svnLENOVO:pn5129CTO:pvrThinkPadX201s:rvnLENOVO:rn5129CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 5129CTO
  dmi.product.version: ThinkPad X201s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Apr  3 19:38:17 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16404 
   vendor LEN
  xserver.version: 2:1.15.0-1ubuntu7

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

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

[Touch-packages] [Bug 1629553] Re: unity8 crashed with SIGSEGV in memcpy() from mir::frontend::SessionMediator::request_persistent_surface_id

[Daniel van Vugt]

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

** Changed in: mir
   Status: New => Confirmed

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

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

Title:
  unity8 crashed with SIGSEGV in memcpy() from
  mir::frontend::SessionMediator::request_persistent_surface_id

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  unity8 crashed with SIGSEGV in memcpy()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity8 8.14+16.10.20160922-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-19-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Oct  1 16:15:40 2016
  ExecutablePath: /usr/bin/unity8
  InstallationDate: Installed on 2016-06-05 (117 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: unity8 --mode=full-shell
  SegvAnalysis:
   Segfault happened at: 0x7ff9d530a877 :movups (%rsi),%xmm0
   PC (0x7ff9d530a877) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity8
  StacktraceTop:
   memcpy () at 
../sysdeps/x86_64/multiarch/../multiarch/memmove-vec-unaligned-erms.S:141
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
   ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41
  Title: unity8 crashed with SIGSEGV in memcpy()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1630722] Re: When logging out of unity8 session everything is crashed all the apport bugs are reported if you log into unity7 session

[Daniel van Vugt]

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

I believe the consistent crash on Unity8 logout is bug 1535297.

** This bug has been marked a duplicate of bug 1535297
   Unity8 crashes on logout with "Error in `unity8': double free or corruption" 
called from libprotobuf.so.9, called from libprotobuf-lite.so.9

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

Title:
  When logging out of unity8 session everything is crashed all the
  apport bugs are reported if you log into unity7 session

Status in unity8-desktop-session:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  When logging out of unity8 session everything is crashed all the
  apport bugs are reported if you log into unity7 session

  It seems to me as if everything is instantly killed like a sudo kill-9
  on everything, this means that when you login to a new desktop session
  all the crashes are instantly reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-desktop-session/+bug/1630722/+subscriptions

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

[Touch-packages] [Bug 1630724] Re: Application remains on unity launcher after uninstallation

[Daniel van Vugt]

** Tags added: unity8-desktop

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

Title:
  Application remains on unity launcher after uninstallation

Status in Canonical System Image:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  I'm not sure if this is reproducible but this is what I did:

  1. Enter Ubuntu One account details through system settings -> online 
accounts.
  2. Open the app store from the main app scope.
  3. Install Popey's Youtube app and then "open" it from the app store page.
  4. Play around in Youtube app for a bit.
  5. Go to the main app scope and long press the Youtube icon to open the store 
page.
  6. Uninstall the app.
  7. Search the store for another Youtube app and install it. (This time I 
installed the top rated one.)
  8. Again, open it by pressing "open" on the store page.
  9. Swipe the left edge to open the app switcher.

  At this point I have two Youtube icons on the switcher. One
  corresponds to the first youtube app, now uninstalled. If I press it,
  I see a low resolution screenshot of that app. I can't interact with
  it though, and if I tap the screen it flickers between the screenshot
  and another app.

  Next I plugged in a keyboard and mouse, activating desktop mode. The
  ghost youtube app now brings up a black window with "youtube" in the
  middle in white text. The close button on the window has no effect.

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

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

[Touch-packages] [Bug 1627795] Re: unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from QObjectPrivate::isSignalConnected from QMetaObject::activate from QMetaObject::activate from QAb

[Daniel van Vugt]

** Changed in: unity-scopes-shell (Ubuntu)
   Importance: Undecided => High

** 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 => 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/1627795

Title:
  unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from
  QObjectPrivate::isSignalConnected from QMetaObject::activate from
  QMetaObject::activate from QAbstractItemModel::modelAboutToBeReset

Status in Canonical System Image:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.14+15.04.20160831.3-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/0168de360a9e17b6337e0304609320555b011747
  contains more details.

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

[Mike Pontillo]

I have regression-tested MAAS images (supplied by LaMont) containing the
proposed fixes on a set of amd64 virtual machines in an IPv4
environment, and LaMont has carried out testing in an IPv6 environment.

Everything seems to be working, so I'm setting this to verification-
done.

** 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 isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1621507

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Confirmed
Status in open-iscsi package in Ubuntu:
  Fix Committed
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Released
Status in klibc source package in Xenial:
  Confirmed
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
* bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init

  [Impact]

  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in
  an ipv6-only environment is affected.

  These uploads address this by replacing the one-off klibc dhcp client
  (IPv4-only) with the defacto standard isc-dhcp-client, and thereby
  provide both ipv6 and ipv4 DHCP configuration.

  [Test Case]

  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to,
  and see it fail to configure the network.

  [Regression Potential]

  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.

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

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

[Touch-packages] [Bug 1624171] Re: systemd-logind error at startup if systemd-shim and upstart-sysv

[Martin Wimpress]

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

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

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

Title:
  systemd-logind error at startup if systemd-shim and upstart-sysv

Status in ubuntu-mate:
  New
Status in systemd-shim package in Ubuntu:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  If systemd-shim is installed with upstart-sysv on PPC64 system running
  ubuntu-mate 16.04.1, the system will not boot to desktop and the below
  error message is generated after logging in to TTY:

  [  646.474008] systemd-logind[2208]: Failed to start user service,
  ignoring: Unknown unit: user@1000.service

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

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

[Touch-packages] [Bug 1519120] Re: NetworkManager should provide default name for VLAN

[Nish Aravamudan]

** Tags removed: server-next

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

Title:
  NetworkManager should provide default name for VLAN

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I tried to use the network manager UI to define a VLAN interface, and
  nothing happened. There are a few bugs here:

  (1) When creating a VLAN interface through the UI, the "vlan interface
  name" must be filled in. This should just default to ., rather than being a required field. (I typed in "vlan100"
  to get the "Save" button to activate.)

  (2) After creating my VLAN interface, nothing happened. No new
  interface appeared. I then realized that I had not installed the
  "vlan" package, and assumed that NetworkManager therefore could not
  complete configuration of the interface.

  (3) After installing the 'vlan' package (and then telling
  NetworkManager to disconnect and reconnect my Ethernet interface from
  the UI, just for good measure), still no VLAN interfaces were present
  on my system.

  I also tried editing the VLAN interface in the UI, and specifying
  "enp4s0f1.100", but still no VLAN interface came online.

  # apt-cache policy network-manager
  network-manager:
Installed: 1.0.4-0ubuntu6
Candidate: 1.0.4-0ubuntu6
Version table:
   *** 1.0.4-0ubuntu6 0
  500 http://172.16.42.88/ubuntu/ xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  # apt-cache policy vlan
  vlan:
Installed: 1.9-3.2ubuntu1
Candidate: 1.9-3.2ubuntu1
Version table:
   *** 1.9-3.2ubuntu1 0
  500 http://172.16.42.88/ubuntu/ xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1629983] Re: Temperature in Weather Report applet impossible to read when using Ambiance

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-themes -
16.10+16.10.20161005-0ubuntu1

---
ubuntu-themes (16.10+16.10.20161005-0ubuntu1) yakkety; urgency=medium

  [ Alberts Muktupāvels ]
  * gnome-panel.css: Fix weather applet text color. (LP: #1629983)

 -- Dmitry Shachnev   Wed, 05 Oct 2016 17:59:11
+

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Fix Released

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

Title:
  Temperature in Weather Report applet impossible to read when using
  Ambiance

Status in gnome-applets package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  When using the Ambiance theme, the temperature on the Weather Report
  applet is impossible to read because the font is black, so it blends
  in with the background of the panel.

  
  Ubuntu Yakkety Yak (development branch) 16.10
  light-themes version 16.10+16.10.20160926-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1629983/+subscriptions

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

[Touch-packages] [Bug 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"

[Alberto Donato]

This is fixed for me on Xenial with 1:0.83-0ubuntu2

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

Title:
  "Ubuntu Light" font has heavier weight than "Ubuntu"

Status in One Hundred Papercuts:
  In Progress
Status in Ubuntu Font Family:
  In Progress
Status in ubuntu-font-family-sources package in Ubuntu:
  In Progress
Status in ubuntu-font-family-sources source package in Wily:
  Triaged

Bug description:
  After upgrading from Vivid to Wily, pages using the "Ubuntu light" font 
actually renders with a weight heavier than the regular one in web pages.
  This happens with Chrome/Chromium and also the Ubuntu browser.

  After manually reinstalling the 0.80-0ubuntu6 version from Vivid (in
  place of 0.83-0ubuntu1), the issue is fixed.

  See the attached screenshot showing the result seen browing
  https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ttf-ubuntu-font-family 0.83-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov  1 17:55:19 2015
  Dependencies:

  InstallationDate: Installed on 2014-10-14 (382 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  PackageArchitecture: all
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago)

  IMPACT: Ubuntu Light font renders incorrectly for all 15.10 users
  which impacts the usability and visual design.

  The new version of font package (0.831) corrects the relationship
  between Light and Medium weight to follow the commonly used naming
  standards:

  Ubuntu Light  Light   Light Italic
  UbuntuRegular Italic  BoldBold Italic
  Ubuntu Medium Medium  Medium Italic   
  Ubuntu Condensed  Regular 
  Ubuntu Mono   Regular Italic  BoldBold Italic

  TEST CASE: in 15.10, go to
  https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu

  If the Light weight renders heavier than Normal weight, the bug is in
  place

  REGRESSION POTENTIAL

  0.831 was tested by manually running in 15.10 and no regression was
  noticed, while the bug was fixed. The potential for regression is
  small.

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

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

[Touch-packages] [Bug 1630702] Re: CVE-2016-8332 allows an out-of-bound heap write to occur resulting in heap corruption and arbitrary code execution

[Seth Arnold]

Our openjpeg and openjpeg2 packages have far more than this one flaw
unaccounted for:

http://people.canonical.com/~ubuntu-security/cve/pkg/openjpeg.html
http://people.canonical.com/~ubuntu-security/cve/pkg/openjpeg2.html

(I suspect that most issues that apply to one also apply to the other;
there is probably more overlap between the two packages.)

Fixing just one open issue is probably not worth the time; fixing most
of them would be. Finding fixes for all of them may not be feasible.

Since we rely upon our community users to test updates, we really do
need whoever supplies patches to have built and tested them all first. If
you're in for only one release, that's still useful, and perhaps someone
else would be willing to tackle the others later.

Probably the 2.x.x patch can be made to apply to the 1.5.2 version
we have packaged; the codebases looked very similar to me last time I
reviewed both.

Thanks

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

Title:
  CVE-2016-8332 allows an out-of-bound heap write to occur resulting in
  heap corruption and arbitrary code execution

Status in openjpeg package in Ubuntu:
  New
Status in openjpeg2 package in Ubuntu:
  New

Bug description:
  A security vulnerability was recently disclosed in openjpeg and
  assigned the CVE number of CVE-2016-8332.

  The vulnerability is described here (http://www.zdnet.com/article
  /openjpeg-zero-day-flaw-leads-to-remote-code-execution/):

  "
  Cisco Talos researchers have uncovered a severe zero-day flaw in the OpenJPEG 
JPEG 2000 codec which could lead to remote code execution on compromised 
systems.

  On Friday, researchers from Cisco revealed the existence of the zero-
  day flaw in the JPEG 2000 image file format parser implemented in
  OpenJPEG library. The out-of-bounds vulnerability, assigned as
  CVE-2016-8332, could allow an out-of-bound heap write to occur
  resulting in heap corruption and arbitrary code execution.

  OpenJPEG is an open-source JPEG 2000 codec. Written in C, the software
  was created to promote JPEG 2000, an image compression standard which
  is in popular use and is often used for tasks including embedding
  images within PDF documents through software including Poppler, MuPDF
  and Pdfium.

  The bug, assigned a CVSS score of 7.5, was caused by errors in parsing
  mcc records in the jpeg2000 file, resulting in "an erroneous read and
  write of adjacent heap area memory." If manipulated, these errors can
  lead to heap metadata process memory corruption.

  In a security advisory, the team said the security vulnerability can
  be exploited by attackers if victims open specifically crafted,
  malicious JPEG 2000 images. For example, if this content was within a
  phishing email or hosted on legitimate services such as Google Drive
  or Dropbox, once downloaded to their system, the path is created for
  attackers to execute code remotely.

  The vulnerability was discovered by Aleksander Nikolic from the Cisco
  Talos security team in OpenJpeg openjp2 version 2.1.1.

  Cisco Talos disclosed the vulnerability to affected vendors on 26 July, 
granting them time to prepare patches to fix the problem before public release.
  "

  I am filing this report as a fix for the issue doesn't seem to have
  yet been backported in and given the importance of the issue and the
  ease in exploiting it, it would be good if this is done soon.

  This is the fix on GitHub:
  https://github.com/uclouvain/openjpeg/pull/820/files

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

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

[Touch-packages] [Bug 1580394] Re: Analog Loopback Static in Headphones while on Dell Latitude 3340 Battery Power

[Martin Wimpress]

** No longer affects: ubuntu-mate

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

Title:
  Analog Loopback Static in Headphones while on Dell Latitude 3340
  Battery Power

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have noticed that when I am on battery power on a Dell Latitude 3340
  laptop with headphones plugged in , and there is no audio playing on
  the computer, there is a consistent static sound that comes through
  the headphones at a constant volume that is not affected by changing
  the volume level. I think it may be picking up some kind of analog
  loopback signal because keyboard presses and disk activity seem to
  influence the noise. When I plug the power cable into the laptop , the
  static immediately goes away.

  I reported this earlier to the upstream Linux Kernel bug tracker, but
  it seems to be fixed in any distro running a 4.4 kernel or greater
  that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This
  make me think it is not a kernel level issue and is found somewhere
  either in the audio settings on Ubuntu MATE or a pulseaudio bug. I
  cannot reproduce it on any other 16.04 distro version, but it also
  affects all the 14.04.4 distros as well.

  Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent
  the static.

  The BIOS Firmware version is up to date.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu-mate   1718 F pulseaudio
   /dev/snd/controlC0:  ubuntu-mate   1718 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: MATE
  Date: Wed May 11 00:43:52 2016
  LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 3340
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1444682] Re: Software properties gtk implies my cpu is unknown and not working.

[Brian Murray]

The Unknown strings come from software-properties so this probably
doesn't need fixing in ubuntu-drivers-common.

1359 widget = Gtk.Label.new("{}:
{}".format(self.devices[device].get('vendor', _('Unknown')),
self.devices[device].get('model', _('Unknown'

The devices detected are the following:

ipdb> self.devices
{'cpu-microcode.py': {'drivers': {'intel-microcode': {'from_distro': True, 
'free': False

Having said that I don't know how software-properties would determine
the right vendor and device.  Additionally, I think all the devices here
will have the same problem.

 $ ls /usr/share/ubuntu-drivers-common/detect/   
arm-gles.py  cpu-microcode.py  open-vm-dkms.py  sl-modem.py

So maybe those should return more than just the package to use.

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

Title:
  Software properties gtk implies my cpu is unknown and not working.

Status in software-properties package in Ubuntu:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  To reproduce install lubuntu 415 i386 on a t6500 core 2 duo cpu. I know I am 
installing 32 bit on 64 but it will show like in with both a braodcom 4322 
which I have not yet installed the prorpietary driver and this intel cpu. Open 
additional drivers from the menu in lxde. 
  software-properties-gtk:
Installed: 0.96.4
Candidate: 0.96.4
Version table:
   *** 0.96.4 0
  500 http://us.archive.ubuntu.com/ubuntu/ vivid/main i386 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04
  https://gist.github.com/dabcbbc9bdcb7ed8d87d is the hardware tracker profile 
for this laptop. 

  I expected software-properties-gtk to not say my processor is unkown
  and not working because I have not installed the latest microcode.
  Instead it said this device which can use the proprietary intel
  microcode driver is unknown and not working and the only device this
  makes sense to be is the cpu.

  I have a screenshot attached of the messages that make no sense.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: software-properties-gtk 0.96.4
  ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
  Uname: Linux 3.19.0-14-generic i686
  ApportVersion: 2.17.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Wed Apr 15 13:11:51 2015
  InstallationDate: Installed on 2015-04-15 (0 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Beta i386 (20150415)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1444682/+subscriptions

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

[Touch-packages] [Bug 1630702] Re: CVE-2016-8332 allows an out-of-bound heap write to occur resulting in heap corruption and arbitrary code execution

[Nikita Yerenkov-Scott]

I can create said debdiffs if there is nobody else better to do them.
I'm just not incredibly experienced with this sort of thing (though I
have successfully made debdiffs in the past and had them accepted) and
in the past I was able to provide a debdiff which would then be altered
by the person in the report I was giving it to so that it would be able
to be applied to all currently supported releases rather than just the
one I had made it for. Is there a person like that this time or do I
need to create a separate one for each Ubuntu release?

Also, the patch I found is for the new 2.x.x series, will it be fine if
I apply it to the 1.5.2-3.1 version we currently have here? I haven't
looked far enough into the code yet to see if it would be a problem and
if any other changes are necessary to make it work for the old version,
but maybe I'm not the best person for that job as I am not familiar with
the code for OpenJPEG.

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

Title:
  CVE-2016-8332 allows an out-of-bound heap write to occur resulting in
  heap corruption and arbitrary code execution

Status in openjpeg package in Ubuntu:
  New
Status in openjpeg2 package in Ubuntu:
  New

Bug description:
  A security vulnerability was recently disclosed in openjpeg and
  assigned the CVE number of CVE-2016-8332.

  The vulnerability is described here (http://www.zdnet.com/article
  /openjpeg-zero-day-flaw-leads-to-remote-code-execution/):

  "
  Cisco Talos researchers have uncovered a severe zero-day flaw in the OpenJPEG 
JPEG 2000 codec which could lead to remote code execution on compromised 
systems.

  On Friday, researchers from Cisco revealed the existence of the zero-
  day flaw in the JPEG 2000 image file format parser implemented in
  OpenJPEG library. The out-of-bounds vulnerability, assigned as
  CVE-2016-8332, could allow an out-of-bound heap write to occur
  resulting in heap corruption and arbitrary code execution.

  OpenJPEG is an open-source JPEG 2000 codec. Written in C, the software
  was created to promote JPEG 2000, an image compression standard which
  is in popular use and is often used for tasks including embedding
  images within PDF documents through software including Poppler, MuPDF
  and Pdfium.

  The bug, assigned a CVSS score of 7.5, was caused by errors in parsing
  mcc records in the jpeg2000 file, resulting in "an erroneous read and
  write of adjacent heap area memory." If manipulated, these errors can
  lead to heap metadata process memory corruption.

  In a security advisory, the team said the security vulnerability can
  be exploited by attackers if victims open specifically crafted,
  malicious JPEG 2000 images. For example, if this content was within a
  phishing email or hosted on legitimate services such as Google Drive
  or Dropbox, once downloaded to their system, the path is created for
  attackers to execute code remotely.

  The vulnerability was discovered by Aleksander Nikolic from the Cisco
  Talos security team in OpenJpeg openjp2 version 2.1.1.

  Cisco Talos disclosed the vulnerability to affected vendors on 26 July, 
granting them time to prepare patches to fix the problem before public release.
  "

  I am filing this report as a fix for the issue doesn't seem to have
  yet been backported in and given the importance of the issue and the
  ease in exploiting it, it would be good if this is done soon.

  This is the fix on GitHub:
  https://github.com/uclouvain/openjpeg/pull/820/files

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

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

[Touch-packages] [Bug 1630510] Re: webbrowser-app crashed with SIGSEGV in QNetworkSession::~QNetworkSession()

[Olivier Tilloy]

This might very well be a regression caused by
https://bileto.ubuntu.com/#/ticket/2015.

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

Title:
  webbrowser-app crashed with SIGSEGV in
  QNetworkSession::~QNetworkSession()

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Crash on close

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: webbrowser-app 0.23+16.10.20160928-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  5 20:49:26 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-08-14 (51 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160813)
  ProcCmdline: webbrowser-app
  ProcEnviron:
   PATH=(custom, user)
   LANGUAGE=en_AU:en
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: webbrowser-app
  StacktraceTop:
   QNetworkSession::~QNetworkSession() () from 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
   QNetworkSession::~QNetworkSession() () from 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
   QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QApplicationPrivate::notify_helper(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
   QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  Title: webbrowser-app crashed with SIGSEGV in 
QNetworkSession::~QNetworkSession()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1622378] Re: package libqtcore4 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other instances of packag

[Launchpad Bug Tracker]

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

** Changed in: qt4-x11 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libqtcore4 (not installed) failed to install/upgrade: trying
  to overwrite shared '/etc/xdg/Trolltech.conf', which is different from
  other instances of package libqtcore4:amd64

Status in qt4-x11 package in Ubuntu:
  Confirmed

Bug description:
  THis came up after I tried to install UNetbootin. I don't really know
  what's going on

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Sep 11 13:42:23 2016
  DuplicateSignature:
   package:libqtcore4:(not installed)
   Unpacking libqtcore4:amd64 (4:4.8.7+dfsg-5ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libqtcore4_4%3a4.8.7+dfsg-5ubuntu2_amd64.deb (--unpack):
trying to overwrite shared '/etc/xdg/Trolltech.conf', which is different 
from other instances of package libqtcore4:amd64
  ErrorMessage: trying to overwrite shared '/etc/xdg/Trolltech.conf', which is 
different from other instances of package libqtcore4:amd64
  InstallationDate: Installed on 2014-08-31 (742 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqtcore4 (not installed) failed to install/upgrade: trying 
to overwrite shared '/etc/xdg/Trolltech.conf', which is different from other 
instances of package libqtcore4:amd64
  UpgradeStatus: Upgraded to xenial on 2016-08-06 (36 days ago)

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

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

[Touch-packages] [Bug 1620313] Re: stop using hardening-wrapper, obsoleted by recent dpkg-dev

[Stéphane Graber]

Re-opening LXC task as it wasn't fixed, the fix was reverted as it was
causing an FTBFS.

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

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

Title:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev

Status in firefox package in Ubuntu:
  In Progress
Status in gtk2-engines-murrine package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Triaged
Status in pidgin package in Ubuntu:
  New
Status in proftpd-dfsg package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in ubuntu-push-qml package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in hardening-wrapper package in Debian:
  Fix Released

Bug description:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev.

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

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

[Touch-packages] [Bug 1630702] Re: CVE-2016-8332 allows an out-of-bound heap write to occur resulting in heap corruption and arbitrary code execution

[Nikita Yerenkov-Scott]

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

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

Title:
  CVE-2016-8332 allows an out-of-bound heap write to occur resulting in
  heap corruption and arbitrary code execution

Status in openjpeg package in Ubuntu:
  New
Status in openjpeg2 package in Ubuntu:
  New

Bug description:
  A security vulnerability was recently disclosed in openjpeg and
  assigned the CVE number of CVE-2016-8332.

  The vulnerability is described here (http://www.zdnet.com/article
  /openjpeg-zero-day-flaw-leads-to-remote-code-execution/):

  "
  Cisco Talos researchers have uncovered a severe zero-day flaw in the OpenJPEG 
JPEG 2000 codec which could lead to remote code execution on compromised 
systems.

  On Friday, researchers from Cisco revealed the existence of the zero-
  day flaw in the JPEG 2000 image file format parser implemented in
  OpenJPEG library. The out-of-bounds vulnerability, assigned as
  CVE-2016-8332, could allow an out-of-bound heap write to occur
  resulting in heap corruption and arbitrary code execution.

  OpenJPEG is an open-source JPEG 2000 codec. Written in C, the software
  was created to promote JPEG 2000, an image compression standard which
  is in popular use and is often used for tasks including embedding
  images within PDF documents through software including Poppler, MuPDF
  and Pdfium.

  The bug, assigned a CVSS score of 7.5, was caused by errors in parsing
  mcc records in the jpeg2000 file, resulting in "an erroneous read and
  write of adjacent heap area memory." If manipulated, these errors can
  lead to heap metadata process memory corruption.

  In a security advisory, the team said the security vulnerability can
  be exploited by attackers if victims open specifically crafted,
  malicious JPEG 2000 images. For example, if this content was within a
  phishing email or hosted on legitimate services such as Google Drive
  or Dropbox, once downloaded to their system, the path is created for
  attackers to execute code remotely.

  The vulnerability was discovered by Aleksander Nikolic from the Cisco
  Talos security team in OpenJpeg openjp2 version 2.1.1.

  Cisco Talos disclosed the vulnerability to affected vendors on 26 July, 
granting them time to prepare patches to fix the problem before public release.
  "

  I am filing this report as a fix for the issue doesn't seem to have
  yet been backported in and given the importance of the issue and the
  ease in exploiting it, it would be good if this is done soon.

  This is the fix on GitHub:
  https://github.com/uclouvain/openjpeg/pull/820/files

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

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

[Touch-packages] [Bug 1630751] Re: package systemd 231-9git1 failed to install/upgrade: triggers looping, abandoned

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1630751

Title:
  package systemd 231-9git1 failed to install/upgrade: triggers looping,
  abandoned

Status in systemd package in Ubuntu:
  New

Bug description:
  Was trying to upgrade from 16.04 to 16.10 beta

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  Uname: Linux 4.7.3-040703-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct  5 22:31:26 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-09-13 (22 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.3-040703-generic 
root=UUID=fa0986da-ae48-47e2-9e62-a8ef25ce5b73 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3
  SourcePackage: systemd
  Title: package systemd 231-9git1 failed to install/upgrade: triggers looping, 
abandoned
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (0 days ago)
  dmi.bios.date: 07/20/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81CC
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 60.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd07/20/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CC:rvrKBCVersion60.26:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1620313] Re: stop using hardening-wrapper, obsoleted by recent dpkg-dev

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 2.0.5-0ubuntu1

---
lxc (2.0.5-0ubuntu1) yakkety; urgency=medium

  * New upstream bugfix release (2.0.5):
- Fix .gitignore after /tools/ split
- Add lxc-test-utils to .gitignore
- bdev: use correct overlay module name
- cleanup: tools: remove --name from lxc-top usage message
- cleanup: whitespaces in option alignment for lxc-execute
- Use full GPG fingerprint instead of long IDs.
- tools: move --rcfile to the common options list
- tools: set configfile after load_config
- doc: add --rcfile to common opts
- doc: Update Korean lxc-attach(1)
- doc: Add --rcfile to Korean common opts
- doc: Add --rcfile to Japanese common opts
- tools: use exit(EXIT_*) everywhere
- tools: unify exit() calls outside of main()
- utils: Add mips signalfd syscall numbers
- seccomp: Implement MIPS seccomp handling
- seccomp: Add mips and mips64 entries to lxc_config_parse_arch
- seccomp: fix strerror()
- confile: add more archs to lxc_config_parse_arch()
- seccomp: add support for s390x
- seccomp: remove double include and order includes
- seccomp: non functional changes
- templates: use fd 9 instead of 200
- templates: fedora requires openssl binary
- tools: use boolean for ret in lxc_device.c
- c/r: use /proc/self/tid/children instead of pidfile
- c/r: Fix pid_t on some arches
- templates: Add mips hostarch detection to debian
- cleanup: replace tabs wth spaces in usage strings
- remove extra 'ret'
- c/r: write status only after trying to parse the pid
- set FULL_PATH_NAMES=NO in doc/api/Doxyfile
- templates: rm halt.target -> sigpwr.target symlink
- templates: remove creation of bogus directory
- console: use correct log name
- configure: add --disable-werror
- tests: fix get_item tests
- templates: use correct cron version in alpine template
- c/r: zero a smaller than known migrate_opts struct
- lxczfs: small fixes
- c/r: free valid_opts if necessary
- make rsync deal with sparse files efficiently
- lxc-create -t debian fails on ppc64el arch
- c/r: fix typo in comment
- cgroup: add new functions for interacting with hierachies
- utils: add lxc_deslashify
- c/r: pass --cgroup-roots on checkpoint
- cgroup: get rid of weird hack in cgfsng_escape
- cgroup: drop cgroup_canonical_path
- c/r: check that cgroup_num_hierarchies > 0
- tools: do not add trailing spaces on lxc-ls -1
- conf: retrieve mtu from netdev->link
- conf: try to retrieve mtu from veth
- c/r: detatch from controlling tty on restore
- Fix null derefence if attach is called without access to any tty
- utils: fix lxc_string_split()
- tools: lxc_deslashify() handle special cases
- tests: add unit tests for lxc_deslashify()
- Fix for ALTLinux container creation in all branches
- utils: lxc_deslashify() free memory
- Fix spelling of CentOS in the templates
- Define LXC_DEVEL to detect development releases
- tools: lxc-checkconfig conditionalize devpts check
  * Drop all cherry-pick patches, now upstream.
  * Update to newer standards. Drop un-needed debian/control field.
  * Address all lintian messages.
  * Revert the previous upload as it caused FTBFS.

 -- Stéphane Graber   Wed, 05 Oct 2016 13:56:58
+0200

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

Title:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev

Status in firefox package in Ubuntu:
  In Progress
Status in gtk2-engines-murrine package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in pidgin package in Ubuntu:
  New
Status in proftpd-dfsg package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in ubuntu-push-qml package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in hardening-wrapper package in Debian:
  Fix Released

Bug description:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev.

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

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

[Touch-packages] [Bug 1630750] [NEW] package dbus 1.10.10-1ubuntu1 failed to install/upgrade: triggers looping, abandoned

[Steven H]

Public bug reported:

Was trying to upgrade from 16.04 to 16.10 beta

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: dbus 1.10.10-1ubuntu1
Uname: Linux 4.7.3-040703-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Oct  5 22:31:26 2016
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2016-09-13 (22 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3
SourcePackage: dbus
Title: package dbus 1.10.10-1ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to yakkety on 2016-10-05 (0 days ago)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package dbus 1.10.10-1ubuntu1 failed to install/upgrade: triggers
  looping, abandoned

Status in dbus package in Ubuntu:
  New

Bug description:
  Was trying to upgrade from 16.04 to 16.10 beta

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: dbus 1.10.10-1ubuntu1
  Uname: Linux 4.7.3-040703-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct  5 22:31:26 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-09-13 (22 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3
  SourcePackage: dbus
  Title: package dbus 1.10.10-1ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (0 days ago)

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

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

[Touch-packages] [Bug 1630750] Re: package dbus 1.10.10-1ubuntu1 failed to install/upgrade: triggers looping, abandoned

[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 dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1630750

Title:
  package dbus 1.10.10-1ubuntu1 failed to install/upgrade: triggers
  looping, abandoned

Status in dbus package in Ubuntu:
  New

Bug description:
  Was trying to upgrade from 16.04 to 16.10 beta

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: dbus 1.10.10-1ubuntu1
  Uname: Linux 4.7.3-040703-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct  5 22:31:26 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-09-13 (22 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3
  SourcePackage: dbus
  Title: package dbus 1.10.10-1ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (0 days ago)

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

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

[Touch-packages] [Bug 1630751] [NEW] package systemd 231-9git1 failed to install/upgrade: triggers looping, abandoned

[Steven H]

Public bug reported:

Was trying to upgrade from 16.04 to 16.10 beta

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: systemd 231-9git1
Uname: Linux 4.7.3-040703-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Oct  5 22:31:26 2016
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2016-09-13 (22 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ENVY Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.3-040703-generic 
root=UUID=fa0986da-ae48-47e2-9e62-a8ef25ce5b73 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3
SourcePackage: systemd
Title: package systemd 231-9git1 failed to install/upgrade: triggers looping, 
abandoned
UpgradeStatus: Upgraded to yakkety on 2016-10-05 (0 days ago)
dmi.bios.date: 07/20/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 81CC
dmi.board.vendor: HP
dmi.board.version: KBC Version 60.26
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd07/20/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CC:rvrKBCVersion60.26:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-package yakkety

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

Title:
  package systemd 231-9git1 failed to install/upgrade: triggers looping,
  abandoned

Status in systemd package in Ubuntu:
  New

Bug description:
  Was trying to upgrade from 16.04 to 16.10 beta

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  Uname: Linux 4.7.3-040703-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Oct  5 22:31:26 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-09-13 (22 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 05c8:038e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.3-040703-generic 
root=UUID=fa0986da-ae48-47e2-9e62-a8ef25ce5b73 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3
  SourcePackage: systemd
  Title: package systemd 231-9git1 failed to install/upgrade: triggers looping, 
abandoned
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (0 days ago)
  dmi.bios.date: 07/20/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81CC
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 60.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd07/20/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn81CC:rvrKBCVersion60.26:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1552100] Re: Create .snap packages of core apps

[Olivier Tilloy]

** No longer affects: webbrowser-app

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

Title:
  Create .snap packages of core apps

Status in Canonical System Image:
  Opinion
Status in Ubuntu Music App:
  Triaged
Status in Ubuntu Notes app:
  Triaged
Status in Telegram app:
  Triaged
Status in Ubuntu Calculator App:
  New
Status in Ubuntu Calendar App:
  In Progress
Status in Ubuntu Clock App:
  Triaged
Status in Ubuntu Document Viewer App:
  Triaged
Status in Ubuntu File Manager App:
  Triaged
Status in Ubuntu Shorts App:
  New
Status in Ubuntu Terminal App:
  In Progress
Status in Ubuntu Weather App:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Move all packages and the system to .snap (snappy)

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

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

[Touch-packages] [Bug 1630702] Re: CVE-2016-8332 allows an out-of-bound heap write to occur resulting in heap corruption and arbitrary code execution

[Nikita Yerenkov-Scott]

I assume that I should create a debdiff for this anyway. What do you
think? And do I need to make one for each release or do you think that
someone else can deal with altering my debdiff to be able to be in any
release they want it to be in (if there is somebody to do that that is)?

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

Title:
  CVE-2016-8332 allows an out-of-bound heap write to occur resulting in
  heap corruption and arbitrary code execution

Status in openjpeg package in Ubuntu:
  New

Bug description:
  A security vulnerability was recently disclosed in openjpeg and
  assigned the CVE number of CVE-2016-8332.

  The vulnerability is described here (http://www.zdnet.com/article
  /openjpeg-zero-day-flaw-leads-to-remote-code-execution/):

  "
  Cisco Talos researchers have uncovered a severe zero-day flaw in the OpenJPEG 
JPEG 2000 codec which could lead to remote code execution on compromised 
systems.

  On Friday, researchers from Cisco revealed the existence of the zero-
  day flaw in the JPEG 2000 image file format parser implemented in
  OpenJPEG library. The out-of-bounds vulnerability, assigned as
  CVE-2016-8332, could allow an out-of-bound heap write to occur
  resulting in heap corruption and arbitrary code execution.

  OpenJPEG is an open-source JPEG 2000 codec. Written in C, the software
  was created to promote JPEG 2000, an image compression standard which
  is in popular use and is often used for tasks including embedding
  images within PDF documents through software including Poppler, MuPDF
  and Pdfium.

  The bug, assigned a CVSS score of 7.5, was caused by errors in parsing
  mcc records in the jpeg2000 file, resulting in "an erroneous read and
  write of adjacent heap area memory." If manipulated, these errors can
  lead to heap metadata process memory corruption.

  In a security advisory, the team said the security vulnerability can
  be exploited by attackers if victims open specifically crafted,
  malicious JPEG 2000 images. For example, if this content was within a
  phishing email or hosted on legitimate services such as Google Drive
  or Dropbox, once downloaded to their system, the path is created for
  attackers to execute code remotely.

  The vulnerability was discovered by Aleksander Nikolic from the Cisco
  Talos security team in OpenJpeg openjp2 version 2.1.1.

  Cisco Talos disclosed the vulnerability to affected vendors on 26 July, 
granting them time to prepare patches to fix the problem before public release.
  "

  I am filing this report as a fix for the issue doesn't seem to have
  yet been backported in and given the importance of the issue and the
  ease in exploiting it, it would be good if this is done soon.

  This is the fix on GitHub:
  https://github.com/uclouvain/openjpeg/pull/820/files

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

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

[Touch-packages] [Bug 1630702] Re: CVE-2016-8332 allows an out-of-bound heap write to occur resulting in heap corruption and arbitrary code execution

[Nikita Yerenkov-Scott]

Seth, I will take a look at those soon after I have created a debdiff
for this (that is if nobody else has done so by the time I do it, which
hopefully will be some time tomorrow).

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

Title:
  CVE-2016-8332 allows an out-of-bound heap write to occur resulting in
  heap corruption and arbitrary code execution

Status in openjpeg package in Ubuntu:
  New

Bug description:
  A security vulnerability was recently disclosed in openjpeg and
  assigned the CVE number of CVE-2016-8332.

  The vulnerability is described here (http://www.zdnet.com/article
  /openjpeg-zero-day-flaw-leads-to-remote-code-execution/):

  "
  Cisco Talos researchers have uncovered a severe zero-day flaw in the OpenJPEG 
JPEG 2000 codec which could lead to remote code execution on compromised 
systems.

  On Friday, researchers from Cisco revealed the existence of the zero-
  day flaw in the JPEG 2000 image file format parser implemented in
  OpenJPEG library. The out-of-bounds vulnerability, assigned as
  CVE-2016-8332, could allow an out-of-bound heap write to occur
  resulting in heap corruption and arbitrary code execution.

  OpenJPEG is an open-source JPEG 2000 codec. Written in C, the software
  was created to promote JPEG 2000, an image compression standard which
  is in popular use and is often used for tasks including embedding
  images within PDF documents through software including Poppler, MuPDF
  and Pdfium.

  The bug, assigned a CVSS score of 7.5, was caused by errors in parsing
  mcc records in the jpeg2000 file, resulting in "an erroneous read and
  write of adjacent heap area memory." If manipulated, these errors can
  lead to heap metadata process memory corruption.

  In a security advisory, the team said the security vulnerability can
  be exploited by attackers if victims open specifically crafted,
  malicious JPEG 2000 images. For example, if this content was within a
  phishing email or hosted on legitimate services such as Google Drive
  or Dropbox, once downloaded to their system, the path is created for
  attackers to execute code remotely.

  The vulnerability was discovered by Aleksander Nikolic from the Cisco
  Talos security team in OpenJpeg openjp2 version 2.1.1.

  Cisco Talos disclosed the vulnerability to affected vendors on 26 July, 
granting them time to prepare patches to fix the problem before public release.
  "

  I am filing this report as a fix for the issue doesn't seem to have
  yet been backported in and given the importance of the issue and the
  ease in exploiting it, it would be good if this is done soon.

  This is the fix on GitHub:
  https://github.com/uclouvain/openjpeg/pull/820/files

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

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

[Touch-packages] [Bug 1588526] Re: [mako] Alarm doesn't ring when screen locked

[slash]

Since when the N4 is not anymore supported, last month in OTA 13 the was
a bug specifically solved for Mako.
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1318360

Moreover, there is high likelihood the future fix for this bug
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1516696 would help
to find this bug.

Regards

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

Title:
  [mako] Alarm doesn't ring when screen locked

Status in Canonical System Image:
  Incomplete
Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

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

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

[Touch-packages] [Bug 1630724] Re: Application remains on unity launcher after uninstallation

[kevin gunn]

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

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

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

Title:
  Application remains on unity launcher after uninstallation

Status in Canonical System Image:
  New
Status in qtmir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  I'm not sure if this is reproducible but this is what I did:

  1. Enter Ubuntu One account details through system settings -> online 
accounts.
  2. Open the app store from the main app scope.
  3. Install Popey's Youtube app and then "open" it from the app store page.
  4. Play around in Youtube app for a bit.
  5. Go to the main app scope and long press the Youtube icon to open the store 
page.
  6. Uninstall the app.
  7. Search the store for another Youtube app and install it. (This time I 
installed the top rated one.)
  8. Again, open it by pressing "open" on the store page.
  9. Swipe the left edge to open the app switcher.

  At this point I have two Youtube icons on the switcher. One
  corresponds to the first youtube app, now uninstalled. If I press it,
  I see a low resolution screenshot of that app. I can't interact with
  it though, and if I tap the screen it flickers between the screenshot
  and another app.

  Next I plugged in a keyboard and mouse, activating desktop mode. The
  ghost youtube app now brings up a black window with "youtube" in the
  middle in white text. The close button on the window has no effect.

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

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

[Touch-packages] [Bug 1630702] Re: CVE-2016-8332 allows an out-of-bound heap write to occur resulting in heap corruption and arbitrary code execution

[Seth Arnold]

Nikita, if you have time and care for OpenJPEG, please consider
reviewing the crashing inputs I reported to the OpenJPEG team:

https://bugs.launchpad.net/ubuntu/+source/openjpeg2/+bug/711061/+attachment/4586223/+files/openjpeg-crashers.tar.gz
https://bugs.launchpad.net/ubuntu/+source/openjpeg2/+bug/711061/+attachment/4723094/+files/crashes-openjpeg-2.1.1.tar.gz

There's a few hundred crashing files there that need inspection and
fixing.

Thanks

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

Title:
  CVE-2016-8332 allows an out-of-bound heap write to occur resulting in
  heap corruption and arbitrary code execution

Status in openjpeg package in Ubuntu:
  New

Bug description:
  A security vulnerability was recently disclosed in openjpeg and
  assigned the CVE number of CVE-2016-8332.

  The vulnerability is described here (http://www.zdnet.com/article
  /openjpeg-zero-day-flaw-leads-to-remote-code-execution/):

  "
  Cisco Talos researchers have uncovered a severe zero-day flaw in the OpenJPEG 
JPEG 2000 codec which could lead to remote code execution on compromised 
systems.

  On Friday, researchers from Cisco revealed the existence of the zero-
  day flaw in the JPEG 2000 image file format parser implemented in
  OpenJPEG library. The out-of-bounds vulnerability, assigned as
  CVE-2016-8332, could allow an out-of-bound heap write to occur
  resulting in heap corruption and arbitrary code execution.

  OpenJPEG is an open-source JPEG 2000 codec. Written in C, the software
  was created to promote JPEG 2000, an image compression standard which
  is in popular use and is often used for tasks including embedding
  images within PDF documents through software including Poppler, MuPDF
  and Pdfium.

  The bug, assigned a CVSS score of 7.5, was caused by errors in parsing
  mcc records in the jpeg2000 file, resulting in "an erroneous read and
  write of adjacent heap area memory." If manipulated, these errors can
  lead to heap metadata process memory corruption.

  In a security advisory, the team said the security vulnerability can
  be exploited by attackers if victims open specifically crafted,
  malicious JPEG 2000 images. For example, if this content was within a
  phishing email or hosted on legitimate services such as Google Drive
  or Dropbox, once downloaded to their system, the path is created for
  attackers to execute code remotely.

  The vulnerability was discovered by Aleksander Nikolic from the Cisco
  Talos security team in OpenJpeg openjp2 version 2.1.1.

  Cisco Talos disclosed the vulnerability to affected vendors on 26 July, 
granting them time to prepare patches to fix the problem before public release.
  "

  I am filing this report as a fix for the issue doesn't seem to have
  yet been backported in and given the importance of the issue and the
  ease in exploiting it, it would be good if this is done soon.

  This is the fix on GitHub:
  https://github.com/uclouvain/openjpeg/pull/820/files

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

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

[Touch-packages] [Bug 1630722] Re: When logging out of unity8 session everything is crashed all the apport bugs are reported if you log into unity7 session

[Christopher Townsend]

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

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

Title:
  When logging out of unity8 session everything is crashed all the
  apport bugs are reported if you log into unity7 session

Status in unity8-desktop-session:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  When logging out of unity8 session everything is crashed all the
  apport bugs are reported if you log into unity7 session

  It seems to me as if everything is instantly killed like a sudo kill-9
  on everything, this means that when you login to a new desktop session
  all the crashes are instantly reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity8-desktop-session/+bug/1630722/+subscriptions

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

[Touch-packages] [Bug 1572528] Re: Side stage close/ collapse gesture hard to discover

[Alistair Buxton]

Also the first time I encountered the side stage was after opening the
weather app and then rotating to landscape mode. The weather app
automatically puts itself into the side stage, obscuring the message
about three finger dragging.

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

Title:
  Side stage close/ collapse gesture hard to discover

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

Bug description:
  Once any app has been in the side stage there seems to be no way to close it 
anymore as long as the device is in landscape orientation. Moving all of the 
side staged apps back to the main stage or closing them will leave a black 
screen behind telling how to use 3 fingers to use the side stage.
  This is particularly inconvenient due to bug 1564348 and renders many apps 
difficult or impossible to use in landscape.

  This is on Frieza with OTA 10.1

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

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

[Touch-packages] [Bug 1572528] Re: Side stage close/ collapse gesture hard to discover

[Alistair Buxton]

+1 the area you need to hit is so small that it takes several attempts
even if you know exactly what you are aiming for. If you just guess that
maybe you can swipe away the side stage then your chances of actually
hitting the absolutely tiny region where it works are virtually nil.

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

Title:
  Side stage close/ collapse gesture hard to discover

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

Bug description:
  Once any app has been in the side stage there seems to be no way to close it 
anymore as long as the device is in landscape orientation. Moving all of the 
side staged apps back to the main stage or closing them will leave a black 
screen behind telling how to use 3 fingers to use the side stage.
  This is particularly inconvenient due to bug 1564348 and renders many apps 
difficult or impossible to use in landscape.

  This is on Frieza with OTA 10.1

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

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

[Touch-packages] [Bug 1630702] Re: CVE-2016-8332 allows an out-of-bound heap write to occur resulting in heap corruption and arbitrary code execution

[Nikita Yerenkov-Scott]

** Description changed:

  A security vulnerability was recently disclosed in openjpeg and assigned
  the CVE number of CVE-2016-8332.
  
  The vulnerability is described here (http://www.zdnet.com/article
  /openjpeg-zero-day-flaw-leads-to-remote-code-execution/):
  
  "
  Cisco Talos researchers have uncovered a severe zero-day flaw in the OpenJPEG 
JPEG 2000 codec which could lead to remote code execution on compromised 
systems.
  
  On Friday, researchers from Cisco revealed the existence of the zero-day
  flaw in the JPEG 2000 image file format parser implemented in OpenJPEG
  library. The out-of-bounds vulnerability, assigned as CVE-2016-8332,
  could allow an out-of-bound heap write to occur resulting in heap
  corruption and arbitrary code execution.
  
  OpenJPEG is an open-source JPEG 2000 codec. Written in C, the software
  was created to promote JPEG 2000, an image compression standard which is
  in popular use and is often used for tasks including embedding images
  within PDF documents through software including Poppler, MuPDF and
  Pdfium.
  
  The bug, assigned a CVSS score of 7.5, was caused by errors in parsing
  mcc records in the jpeg2000 file, resulting in "an erroneous read and
  write of adjacent heap area memory." If manipulated, these errors can
  lead to heap metadata process memory corruption.
  
  In a security advisory, the team said the security vulnerability can be
  exploited by attackers if victims open specifically crafted, malicious
  JPEG 2000 images. For example, if this content was within a phishing
  email or hosted on legitimate services such as Google Drive or Dropbox,
  once downloaded to their system, the path is created for attackers to
  execute code remotely.
  
  The vulnerability was discovered by Aleksander Nikolic from the Cisco
  Talos security team in OpenJpeg openjp2 version 2.1.1.
  
  Cisco Talos disclosed the vulnerability to affected vendors on 26 July, 
granting them time to prepare patches to fix the problem before public release.
  "
  
  I am filing this report as a fix for the issue doesn't seem to have yet
  been backported in and given the importance of the issue and the ease in
  exploiting it, it would be good if this is done soon.
+ 
+ This is the fix on GitHub:
+ https://github.com/uclouvain/openjpeg/pull/820/files

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

Title:
  CVE-2016-8332 allows an out-of-bound heap write to occur resulting in
  heap corruption and arbitrary code execution

Status in openjpeg package in Ubuntu:
  New

Bug description:
  A security vulnerability was recently disclosed in openjpeg and
  assigned the CVE number of CVE-2016-8332.

  The vulnerability is described here (http://www.zdnet.com/article
  /openjpeg-zero-day-flaw-leads-to-remote-code-execution/):

  "
  Cisco Talos researchers have uncovered a severe zero-day flaw in the OpenJPEG 
JPEG 2000 codec which could lead to remote code execution on compromised 
systems.

  On Friday, researchers from Cisco revealed the existence of the zero-
  day flaw in the JPEG 2000 image file format parser implemented in
  OpenJPEG library. The out-of-bounds vulnerability, assigned as
  CVE-2016-8332, could allow an out-of-bound heap write to occur
  resulting in heap corruption and arbitrary code execution.

  OpenJPEG is an open-source JPEG 2000 codec. Written in C, the software
  was created to promote JPEG 2000, an image compression standard which
  is in popular use and is often used for tasks including embedding
  images within PDF documents through software including Poppler, MuPDF
  and Pdfium.

  The bug, assigned a CVSS score of 7.5, was caused by errors in parsing
  mcc records in the jpeg2000 file, resulting in "an erroneous read and
  write of adjacent heap area memory." If manipulated, these errors can
  lead to heap metadata process memory corruption.

  In a security advisory, the team said the security vulnerability can
  be exploited by attackers if victims open specifically crafted,
  malicious JPEG 2000 images. For example, if this content was within a
  phishing email or hosted on legitimate services such as Google Drive
  or Dropbox, once downloaded to their system, the path is created for
  attackers to execute code remotely.

  The vulnerability was discovered by Aleksander Nikolic from the Cisco
  Talos security team in OpenJpeg openjp2 version 2.1.1.

  Cisco Talos disclosed the vulnerability to affected vendors on 26 July, 
granting them time to prepare patches to fix the problem before public release.
  "

  I am filing this report as a fix for the issue doesn't seem to have
  yet been backported in and given the importance of the issue and the
  ease in exploiting it, it would be good if this is done soon.

  This is the fix on GitHub:
  https://github.com/uclouvain/openjpeg/pull/820/files

To manage 

[Touch-packages] [Bug 1547844] Re: systemd-fsckd does not allow fsck to finish

[Martin Pitt]

Thanks kex for testing! FTR, the kernel oops is unrelated to this issue.

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

Title:
  systemd-fsckd does not allow fsck to finish

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  
  during normal boots, fsck runs fine with small partitions.  But I have two 
big partitions and systemd seems to abort fsck somewhere between 5 to 10 
minutes from start.  This results in the partition being checked again at every 
boot.  After manual run in recovery mode, everything is OK again. 

  See e.g.

   sudo tune2fs -l /dev/mapper/xpcvg-home 
  tune2fs 1.42.12 (29-Aug-2014)
  Filesystem volume name:   
  Last mounted on:  /home
  Filesystem UUID:  db583624-afb4-41cb-8b2d-640bee2de61b
  Filesystem magic number:  0xEF53
  Filesystem revision #:1 (dynamic)
  Filesystem features:  has_journal ext_attr resize_inode dir_index 
filetype needs_recovery extent sparse_super large_file uninit_bg
  Filesystem flags: signed_directory_hash 
  Default mount options:(none)
  Filesystem state: clean
  Errors behavior:  Continue
  Filesystem OS type:   Linux
  Inode count:  65536000
  Block count:  262144000
  Reserved block count: 13107200
  Free blocks:  183474571
  Free inodes:  65167292
  First block:  0
  Block size:   4096
  Fragment size:4096
  Reserved GDT blocks:  961
  Blocks per group: 32768
  Fragments per group:  32768
  Inodes per group: 8192
  Inode blocks per group:   512
  RAID stride:  128
  RAID stripe width:384
  Filesystem created:   Mon Jul 25 12:23:50 2011
  Last mount time:  Sat Feb 20 09:34:41 2016
  Last write time:  Sat Feb 20 09:34:41 2016
  Mount count:  166
  Maximum mount count:  157
  Last checked: Sun Nov 29 14:02:12 2015
  Check interval:   15552000 (6 months)
  Next check after: Fri May 27 15:02:12 2016
  Lifetime writes:  1113 GB
  Reserved blocks uid:  0 (user root)
  Reserved blocks gid:  0 (group root)
  First inode:  11
  Inode size: 256
  Required extra isize: 28
  Desired extra isize:  28
  Journal inode:8
  First orphan inode:   65143018
  Default directory hash:   half_md4
  Directory Hash Seed:  ea4a0233-d8af-4c51-9302-140a4affacdf
  Journal backup:   inode blocks

  journalctl says:
  helmi 20 09:30:21 xpc systemd-fsck[720]: /dev/mapper/xpcvg-home has been 
mounted 165 times without being checked, check forced.
  helmi 20 09:34:40 xpc systemd-fsck[720]: fsck: Warning... fsck.ext4 for 
device /dev/mapper/xpcvg-home exited with signal 13.
  helmi 20 09:34:40 xpc systemd-fsck[720]: fsck failed with error code 8.
  helmi 20 09:34:40 xpc systemd-fsck[720]: Ignoring error.
  helmi 20 09:34:40 xpc systemd[1]: Started File System Check on 
/dev/mapper/xpcvg-home.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 14:20:24 2016
  InstallationDate: Installed on 2012-12-22 (1154 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic 
root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro nomdmonddf nomdmonisw 
libata.noacpi=1 irqpoll all_generic_ide=1 ide-pci-generic.all-generic-ide=1 
usbcore.autosuspend=-1 usbcore.old_scheme_first=1 libata.force=8:1.5G 
xhci_hcd.quirks=262144
  SourcePackage: systemd
  UpgradeStatus: Upgraded to wily on 2015-10-23 (119 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIEXTREME:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

-- 
Mailing list: https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1218228] Re: Please update to openjpeg-2.0.0

[Nikita Yerenkov-Scott]

I can't find a package under the name of openjpeg2 in the repositories,
all I can find is openjpeg5 which is not at this version. Could someone
please confirm what is happening with this?

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

Title:
  Please update to openjpeg-2.0.0

Status in openjpeg package in Ubuntu:
  Fix Released

Bug description:
  openjpeg-2.0.0 is already released in November 2012 (last year)

  https://code.google.com/p/openjpeg/

  Please update ubuntu package to openjpeg-2.0.0

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

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

[Touch-packages] [Bug 1630731] [NEW] autodownload check in get_update_automation_level doesn't check hard enough

[Brian Murray]

Public bug reported:

The function get_automation_level tries to see if updates will be
installed automatically, however the check is really incomplete.

143   def get_update_automation_level(self):
144 """ Parse the apt cron configuration. Try to fit a predefined use case 
145 and return it. Special case: if the user made a custom 
146 configurtation, that we cannot represent it will return None """
147 if apt_pkg.config.find_i(softwareproperties.CONF_MAP["autoupdate"]) > 0:
148 # Autodownload
149 if apt_pkg.config.find_i(softwareproperties.CONF_MAP["unattended"]) 
== 1\
150and os.path.exists("/usr/bin/unattended-upgrade"):
151 return softwareproperties.UPDATE_INST_SEC
152 elif 
apt_pkg.config.find_i(softwareproperties.CONF_MAP["autodownload"]) == 1 and  \
153  
apt_pkg.config.find_i(softwareproperties.CONF_MAP["unattended"]) == 0:
154 return softwareproperties.UPDATE_DOWNLOAD
155 elif 
apt_pkg.config.find_i(softwareproperties.CONF_MAP["unattended"]) == 0 and \
156  
apt_pkg.config.find_i(softwareproperties.CONF_MAP["autodownload"]) == 0:
157 return softwareproperties.UPDATE_NOTIFY
158 else:
159 return None


unattended maps to "APT::Periodic::Unattended-Upgrade" (see 
softwareproperties/__init__.py.

However, /etc/apt/apt.conf.d/50unattended-upgrades could contain
Unattended-Upgrade and not allow any origins e.g.:

  1 // Automatically upgrade packages from these (origin:archive) pairs
  2 Unattended-Upgrade::Allowed-Origins {
  3 //"${distro_id}:${distro_codename}-security";
  4 //  "${distro_id}:${distro_codename}-updates";
  5 //  "${distro_id}:${distro_codename}-proposed";
  6 //  "${distro_id}:${distro_codename}-backports";
  7 };

The check really should dig deeper in Unattended-Upgrade.

** Affects: software-properties (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: xenial yakkety

** Changed in: software-properties (Ubuntu)
   Status: New => Triaged

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  autodownload check in get_update_automation_level doesn't check hard
  enough

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  The function get_automation_level tries to see if updates will be
  installed automatically, however the check is really incomplete.

  143   def get_update_automation_level(self):
  144 """ Parse the apt cron configuration. Try to fit a predefined use 
case 
  145 and return it. Special case: if the user made a custom 
  146 configurtation, that we cannot represent it will return None """
  147 if apt_pkg.config.find_i(softwareproperties.CONF_MAP["autoupdate"]) > 
0:
  148 # Autodownload
  149 if 
apt_pkg.config.find_i(softwareproperties.CONF_MAP["unattended"]) == 1\
  150and os.path.exists("/usr/bin/unattended-upgrade"):
  151 return softwareproperties.UPDATE_INST_SEC
  152 elif 
apt_pkg.config.find_i(softwareproperties.CONF_MAP["autodownload"]) == 1 and  \
  153  
apt_pkg.config.find_i(softwareproperties.CONF_MAP["unattended"]) == 0:
  154 return softwareproperties.UPDATE_DOWNLOAD
  155 elif 
apt_pkg.config.find_i(softwareproperties.CONF_MAP["unattended"]) == 0 and \
  156  
apt_pkg.config.find_i(softwareproperties.CONF_MAP["autodownload"]) == 0:
  157 return softwareproperties.UPDATE_NOTIFY
  158 else:
  159 return None

  
  unattended maps to "APT::Periodic::Unattended-Upgrade" (see 
softwareproperties/__init__.py.

  However, /etc/apt/apt.conf.d/50unattended-upgrades could contain
  Unattended-Upgrade and not allow any origins e.g.:

1 // Automatically upgrade packages from these (origin:archive) pairs
2 Unattended-Upgrade::Allowed-Origins {
3 //"${distro_id}:${distro_codename}-security";
4 //  "${distro_id}:${distro_codename}-updates";
5 //  "${distro_id}:${distro_codename}-proposed";
6 //  "${distro_id}:${distro_codename}-backports";
7 };

  The check really should dig deeper in Unattended-Upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1630731/+subscriptions

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

[Touch-packages] [Bug 1630702] Re: CVE-2016-8332 allows an out-of-bound heap write to occur resulting in heap corruption and arbitrary code execution

[Nikita Yerenkov-Scott]

** Summary changed:

- Backport in patch to fix CVE-2016-8332
+ CVE-2016-8332 allows an out-of-bound heap write to occur resulting in heap 
corruption and arbitrary code execution

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

Title:
  CVE-2016-8332 allows an out-of-bound heap write to occur resulting in
  heap corruption and arbitrary code execution

Status in openjpeg package in Ubuntu:
  New

Bug description:
  A security vulnerability was recently disclosed in openjpeg and
  assigned the CVE number of CVE-2016-8332.

  The vulnerability is described here (http://www.zdnet.com/article
  /openjpeg-zero-day-flaw-leads-to-remote-code-execution/):

  "
  Cisco Talos researchers have uncovered a severe zero-day flaw in the OpenJPEG 
JPEG 2000 codec which could lead to remote code execution on compromised 
systems.

  On Friday, researchers from Cisco revealed the existence of the zero-
  day flaw in the JPEG 2000 image file format parser implemented in
  OpenJPEG library. The out-of-bounds vulnerability, assigned as
  CVE-2016-8332, could allow an out-of-bound heap write to occur
  resulting in heap corruption and arbitrary code execution.

  OpenJPEG is an open-source JPEG 2000 codec. Written in C, the software
  was created to promote JPEG 2000, an image compression standard which
  is in popular use and is often used for tasks including embedding
  images within PDF documents through software including Poppler, MuPDF
  and Pdfium.

  The bug, assigned a CVSS score of 7.5, was caused by errors in parsing
  mcc records in the jpeg2000 file, resulting in "an erroneous read and
  write of adjacent heap area memory." If manipulated, these errors can
  lead to heap metadata process memory corruption.

  In a security advisory, the team said the security vulnerability can
  be exploited by attackers if victims open specifically crafted,
  malicious JPEG 2000 images. For example, if this content was within a
  phishing email or hosted on legitimate services such as Google Drive
  or Dropbox, once downloaded to their system, the path is created for
  attackers to execute code remotely.

  The vulnerability was discovered by Aleksander Nikolic from the Cisco
  Talos security team in OpenJpeg openjp2 version 2.1.1.

  Cisco Talos disclosed the vulnerability to affected vendors on 26 July, 
granting them time to prepare patches to fix the problem before public release.
  "

  I am filing this report as a fix for the issue doesn't seem to have
  yet been backported in and given the importance of the issue and the
  ease in exploiting it, it would be good if this is done soon.

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

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

[Touch-packages] [Bug 1630724] [NEW] Application remains on unity launcher after uninstallation

[Alistair Buxton]

Public bug reported:

I'm not sure if this is reproducible but this is what I did:

1. Enter Ubuntu One account details through system settings -> online accounts.
2. Open the app store from the main app scope.
3. Install Popey's Youtube app and then "open" it from the app store page.
4. Play around in Youtube app for a bit.
5. Go to the main app scope and long press the Youtube icon to open the store 
page.
6. Uninstall the app.
7. Search the store for another Youtube app and install it. (This time I 
installed the top rated one.)
8. Again, open it by pressing "open" on the store page.
9. Swipe the left edge to open the app switcher.

At this point I have two Youtube icons on the switcher. One corresponds
to the first youtube app, now uninstalled. If I press it, I see a low
resolution screenshot of that app. I can't interact with it though, and
if I tap the screen it flickers between the screenshot and another app.

Next I plugged in a keyboard and mouse, activating desktop mode. The
ghost youtube app now brings up a black window with "youtube" in the
middle in white text. The close button on the window has no effect.

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

** Summary changed:

- Ghost application remains on unity launcher after uninstallation
+ Application remains on unity launcher after uninstallation

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

Title:
  Application remains on unity launcher after uninstallation

Status in unity8 package in Ubuntu:
  New

Bug description:
  I'm not sure if this is reproducible but this is what I did:

  1. Enter Ubuntu One account details through system settings -> online 
accounts.
  2. Open the app store from the main app scope.
  3. Install Popey's Youtube app and then "open" it from the app store page.
  4. Play around in Youtube app for a bit.
  5. Go to the main app scope and long press the Youtube icon to open the store 
page.
  6. Uninstall the app.
  7. Search the store for another Youtube app and install it. (This time I 
installed the top rated one.)
  8. Again, open it by pressing "open" on the store page.
  9. Swipe the left edge to open the app switcher.

  At this point I have two Youtube icons on the switcher. One
  corresponds to the first youtube app, now uninstalled. If I press it,
  I see a low resolution screenshot of that app. I can't interact with
  it though, and if I tap the screen it flickers between the screenshot
  and another app.

  Next I plugged in a keyboard and mouse, activating desktop mode. The
  ghost youtube app now brings up a black window with "youtube" in the
  middle in white text. The close button on the window has no effect.

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

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

[Touch-packages] [Bug 1630725] Re: Bluetooth settings are showed but my pc doesn't have the bluethoot

[Emanuele Antonio Faraone]

** Attachment added: "image.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1630725/+attachment/4755331/+files/image.jpg

** Summary changed:

- Bluetooth settings are showed but my pc doesn't have the bluethoot
+ Bluetooth settings are showed but my pc doesn't have the bluetooth

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

Title:
  Bluetooth settings are showed but my pc doesn't have the bluetooth

Status in unity8 package in Ubuntu:
  New

Bug description:
  In the control panel the Bluetooth settings are showed , but the my PC
  doesn't have the Bluetooth.

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

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

[Touch-packages] [Bug 1630725] [NEW] Bluetooth settings are showed but my pc doesn't have the bluetooth

[Emanuele Antonio Faraone]

Public bug reported:

In the control panel the Bluetooth settings are showed , but the my PC
doesn't have the Bluetooth.

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

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

Title:
  Bluetooth settings are showed but my pc doesn't have the bluetooth

Status in unity8 package in Ubuntu:
  New

Bug description:
  In the control panel the Bluetooth settings are showed , but the my PC
  doesn't have the Bluetooth.

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

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

[Touch-packages] [Bug 1616107] Re: Kernel oops + system freeze on network-bridge shutdown

[jwiegley]

6 weeks later what's the fix for this? I think we can safely assume that
this bug affects everyone using a bridged bnx2x device and 16.04.

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

Title:
  Kernel oops + system freeze on network-bridge shutdown

Status in bridge-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in bridge-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in bridge-utils source package in Yakkety:
  Confirmed

Bug description:
  A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
  brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
  This error does not appear in Ubuntu 14.04 however.

  The error is reproducible whenever issuing the commands "shutdown",
  "service networking stop" or "brctl delbr br0". Manually creating the
  bridge and subsequently bringing it down results in the same error.

  /var/log/kern.log:
  [...]
  Aug 23 15:09:46 base1 kernel: [  617.996677] device ens1f0 left promiscuous 
mode
  Aug 23 15:09:46 base1 kernel: [  617.996699] br0: port 1(ens1f0) entered 
disabled state
  Aug 23 15:09:46 base1 kernel: [  617.996730] BUG: unable to handle kernel 
NULL pointer dereference at 00d2
  Aug 23 15:09:46 base1 kernel: [  618.008306] IP: [] 
__vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.020549] PGD 10374c0067 PUD 1033927067 
PMD 0
  Aug 23 15:09:46 base1 kernel: [  618.032773] Oops: 0002 [#1] SMP
  Aug 23 15:09:46 base1 kernel: [  618.044434] Modules linked in: nls_iso8859_1 
ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich 
ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm 
iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear 
raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci 
i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio 
libcrc32c wmi fjes
  Aug 23 15:09:46 base1 kernel: [  618.058563] CPU: 3 PID: 4049 Comm: brctl Not 
tainted 4.4.0-34-generic #53-Ubuntu
  Aug 23 15:09:46 base1 kernel: [  618.058564] Hardware name: HP ProLiant DL120 
Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016
  Aug 23 15:09:46 base1 kernel: [  618.058574] task: 881030676040 ti: 
8810341e4000 task.ti: 8810341e4000
  Aug 23 15:09:46 base1 kernel: [  618.058576] RIP: 0010:[]  
[] __vlan_flush+0x18/0x60 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058754] RSP: 0018:8810341e7d68  
EFLAGS: 00010206
  Aug 23 15:09:46 base1 kernel: [  618.058769] RAX:  RBX: 
 RCX: 
  Aug 23 15:09:46 base1 kernel: [  618.058774] RDX: 881038470848 RSI: 
 RDI: 
  Aug 23 15:09:46 base1 kernel: [  618.058775] RBP: 8810341e7d78 R08: 
 R09: 8170d949
  Aug 23 15:09:46 base1 kernel: [  618.058776] R10: ead61340 R11: 
8810329d2c00 R12: 00c0
  Aug 23 15:09:46 base1 kernel: [  618.058777] R13: 881030044000 R14: 
881038470840 R15: 
  Aug 23 15:09:46 base1 kernel: [  618.058782] FS:  7f9aebc94700() 
GS:88107fcc() knlGS:
  Aug 23 15:09:46 base1 kernel: [  618.058789] CS:  0010 DS:  ES:  CR0: 
80050033
  Aug 23 15:09:46 base1 kernel: [  618.058790] CR2: 00d2 CR3: 
00102fe83000 CR4: 001406e0
  Aug 23 15:09:46 base1 kernel: [  618.058802] Stack:
  Aug 23 15:09:46 base1 kernel: [  618.058806]   
8810356a4c00 8810341e7d98 c0489258
  Aug 23 15:09:46 base1 kernel: [  618.058822]  8810356a4c00 
881038470840 8810341e7dc0 c0479bd8
  Aug 23 15:09:46 base1 kernel: [  618.058825]  881038470838 
881038470848 88103847 8810341e7df8
  Aug 23 15:09:46 base1 kernel: [  618.058827] Call Trace:
  Aug 23 15:09:46 base1 kernel: [  618.058863]  [] 
nbp_vlan_flush+0x28/0x65 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058870]  [] 
del_nbp+0x98/0x130 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058889]  [] 
br_dev_delete+0x42/0xb0 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058895]  [] 
br_del_bridge+0x4a/0x70 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058911]  [] 
br_ioctl_deviceless_stub+0x153/0x230 [bridge]
  Aug 23 15:09:46 base1 kernel: [  618.058984]  [] ? 
security_file_alloc+0x33/0x50
  Aug 23 15:09:46 base1 kernel: [  618.059095]  [] 
sock_ioctl+0x215/0x290
  Aug 23 15:09:46 base1 kernel: [  

[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

[Brad Figg]

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

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

Title:
  lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)

Status in e2fsprogs package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Invalid
Status in linux source package in Trusty:
  Triaged
Status in e2fsprogs source package in Vivid:
  Invalid
Status in linux source package in Vivid:
  Fix Committed
Status in e2fsprogs source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in e2fsprogs source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  I run an amd64 kernel on trusty.  The e2fsprogs package was still the
  32 bit i386 variety.  This lead to the following situation (for
  essentially all files on a btrfs partition).

  $ lsattr 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko
  lsattr: Inappropriate ioctl for device While reading flags on 
/lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko

  The problem was resolved by installing e2fsprogs:amd64.

  https://patchwork.kernel.org/patch/7517361/ might be related.

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

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

[Touch-packages] [Bug 1626220] Re: please remove openjpeg

[Jeremy Bicha]

** Description changed:

  It looks like openjpeg packages openjpeg 1.5.2, while openjpeg2 packages
  openjpeg 2.1.1. I don't think we want both packaged. It looks like
  Debian has removed openjpeg from testing and unstable.
  
  Thanks
+ 
+ $ reverse-depends -b src:openjpeg
+ Reverse-Build-Depends
+ =
+ * calligra  (for libopenjpeg-dev)
+ * ffmpeg(for libopenjpeg-dev)
+ * kimageformats (for libopenjpeg-dev)
+ 
+ $ reverse-depends src:openjpeg
+ Reverse-Depends
+ ===
+ * krita (for libopenjpeg5)
+ * libavcodec-extra57(for libopenjpeg5)
+ * libavcodec57  (for libopenjpeg5)

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

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

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

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

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

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

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

Title:
  please remove openjpeg

Status in calligra package in Ubuntu:
  New
Status in ffmpeg package in Ubuntu:
  New
Status in kimageformats package in Ubuntu:
  New
Status in openjpeg package in Ubuntu:
  New

Bug description:
  It looks like openjpeg packages openjpeg 1.5.2, while openjpeg2
  packages openjpeg 2.1.1. I don't think we want both packaged. It looks
  like Debian has removed openjpeg from testing and unstable.

  Thanks

  $ reverse-depends -b src:openjpeg
  Reverse-Build-Depends
  =
  * calligra  (for libopenjpeg-dev)
  * ffmpeg(for libopenjpeg-dev)
  * kimageformats (for libopenjpeg-dev)

  $ reverse-depends src:openjpeg
  Reverse-Depends
  ===
  * krita (for libopenjpeg5)
  * libavcodec-extra57(for libopenjpeg5)
  * libavcodec57  (for libopenjpeg5)

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

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

[Touch-packages] [Bug 1630702] Re: Backport in patch to fix CVE-2016-8332

[Nikita Yerenkov-Scott]

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-8332

** Tags added: precise trusty xenial

** Tags added: yakkety

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

Title:
  Backport in patch to fix CVE-2016-8332

Status in openjpeg package in Ubuntu:
  New

Bug description:
  A security vulnerability was recently disclosed in openjpeg and
  assigned the CVE number of CVE-2016-8332.

  The vulnerability is described here (http://www.zdnet.com/article
  /openjpeg-zero-day-flaw-leads-to-remote-code-execution/):

  "
  Cisco Talos researchers have uncovered a severe zero-day flaw in the OpenJPEG 
JPEG 2000 codec which could lead to remote code execution on compromised 
systems.

  On Friday, researchers from Cisco revealed the existence of the zero-
  day flaw in the JPEG 2000 image file format parser implemented in
  OpenJPEG library. The out-of-bounds vulnerability, assigned as
  CVE-2016-8332, could allow an out-of-bound heap write to occur
  resulting in heap corruption and arbitrary code execution.

  OpenJPEG is an open-source JPEG 2000 codec. Written in C, the software
  was created to promote JPEG 2000, an image compression standard which
  is in popular use and is often used for tasks including embedding
  images within PDF documents through software including Poppler, MuPDF
  and Pdfium.

  The bug, assigned a CVSS score of 7.5, was caused by errors in parsing
  mcc records in the jpeg2000 file, resulting in "an erroneous read and
  write of adjacent heap area memory." If manipulated, these errors can
  lead to heap metadata process memory corruption.

  In a security advisory, the team said the security vulnerability can
  be exploited by attackers if victims open specifically crafted,
  malicious JPEG 2000 images. For example, if this content was within a
  phishing email or hosted on legitimate services such as Google Drive
  or Dropbox, once downloaded to their system, the path is created for
  attackers to execute code remotely.

  The vulnerability was discovered by Aleksander Nikolic from the Cisco
  Talos security team in OpenJpeg openjp2 version 2.1.1.

  Cisco Talos disclosed the vulnerability to affected vendors on 26 July, 
granting them time to prepare patches to fix the problem before public release.
  "

  I am filing this report as a fix for the issue doesn't seem to have
  yet been backported in and given the importance of the issue and the
  ease in exploiting it, it would be good if this is done soon.

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

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

[Touch-packages] [Bug 1627795] Re: unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from QObjectPrivate::isSignalConnected from QMetaObject::activate from QMetaObject::activate from QAb

[Marcus Tomlinson]

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

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

Title:
  unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from
  QObjectPrivate::isSignalConnected from QMetaObject::activate from
  QMetaObject::activate from QAbstractItemModel::modelAboutToBeReset

Status in unity-scopes-shell package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.14+15.04.20160831.3-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/0168de360a9e17b6337e0304609320555b011747
  contains more details.

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

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

[Touch-packages] [Bug 1630702] [NEW] Backport in patch to fix CVE-2016-8332

[Nikita Yerenkov-Scott]

*** This bug is a security vulnerability ***

Public security bug reported:

A security vulnerability was recently disclosed in openjpeg and assigned
the CVE number of CVE-2016-8332.

The vulnerability is described here (http://www.zdnet.com/article
/openjpeg-zero-day-flaw-leads-to-remote-code-execution/):

"
Cisco Talos researchers have uncovered a severe zero-day flaw in the OpenJPEG 
JPEG 2000 codec which could lead to remote code execution on compromised 
systems.

On Friday, researchers from Cisco revealed the existence of the zero-day
flaw in the JPEG 2000 image file format parser implemented in OpenJPEG
library. The out-of-bounds vulnerability, assigned as CVE-2016-8332,
could allow an out-of-bound heap write to occur resulting in heap
corruption and arbitrary code execution.

OpenJPEG is an open-source JPEG 2000 codec. Written in C, the software
was created to promote JPEG 2000, an image compression standard which is
in popular use and is often used for tasks including embedding images
within PDF documents through software including Poppler, MuPDF and
Pdfium.

The bug, assigned a CVSS score of 7.5, was caused by errors in parsing
mcc records in the jpeg2000 file, resulting in "an erroneous read and
write of adjacent heap area memory." If manipulated, these errors can
lead to heap metadata process memory corruption.

In a security advisory, the team said the security vulnerability can be
exploited by attackers if victims open specifically crafted, malicious
JPEG 2000 images. For example, if this content was within a phishing
email or hosted on legitimate services such as Google Drive or Dropbox,
once downloaded to their system, the path is created for attackers to
execute code remotely.

The vulnerability was discovered by Aleksander Nikolic from the Cisco
Talos security team in OpenJpeg openjp2 version 2.1.1.

Cisco Talos disclosed the vulnerability to affected vendors on 26 July, 
granting them time to prepare patches to fix the problem before public release.
"

I am filing this report as a fix for the issue doesn't seem to have yet
been backported in and given the importance of the issue and the ease in
exploiting it, it would be good if this is done soon.

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

** Information type changed from Public to Public Security

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

Title:
  Backport in patch to fix CVE-2016-8332

Status in openjpeg package in Ubuntu:
  New

Bug description:
  A security vulnerability was recently disclosed in openjpeg and
  assigned the CVE number of CVE-2016-8332.

  The vulnerability is described here (http://www.zdnet.com/article
  /openjpeg-zero-day-flaw-leads-to-remote-code-execution/):

  "
  Cisco Talos researchers have uncovered a severe zero-day flaw in the OpenJPEG 
JPEG 2000 codec which could lead to remote code execution on compromised 
systems.

  On Friday, researchers from Cisco revealed the existence of the zero-
  day flaw in the JPEG 2000 image file format parser implemented in
  OpenJPEG library. The out-of-bounds vulnerability, assigned as
  CVE-2016-8332, could allow an out-of-bound heap write to occur
  resulting in heap corruption and arbitrary code execution.

  OpenJPEG is an open-source JPEG 2000 codec. Written in C, the software
  was created to promote JPEG 2000, an image compression standard which
  is in popular use and is often used for tasks including embedding
  images within PDF documents through software including Poppler, MuPDF
  and Pdfium.

  The bug, assigned a CVSS score of 7.5, was caused by errors in parsing
  mcc records in the jpeg2000 file, resulting in "an erroneous read and
  write of adjacent heap area memory." If manipulated, these errors can
  lead to heap metadata process memory corruption.

  In a security advisory, the team said the security vulnerability can
  be exploited by attackers if victims open specifically crafted,
  malicious JPEG 2000 images. For example, if this content was within a
  phishing email or hosted on legitimate services such as Google Drive
  or Dropbox, once downloaded to their system, the path is created for
  attackers to execute code remotely.

  The vulnerability was discovered by Aleksander Nikolic from the Cisco
  Talos security team in OpenJpeg openjp2 version 2.1.1.

  Cisco Talos disclosed the vulnerability to affected vendors on 26 July, 
granting them time to prepare patches to fix the problem before public release.
  "

  I am filing this report as a fix for the issue doesn't seem to have
  yet been backported in and given the importance of the issue and the
  ease in exploiting it, it would be good if this is done soon.

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

-- 
Mailing list: 

[Touch-packages] [Bug 1614108] Re: QStandardPaths::RuntimeLocation returns empty string under pbuilder

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-system-settings-online-accounts
- 0.7+16.10.20161004-0ubuntu1

---
ubuntu-system-settings-online-accounts (0.7+16.10.20161004-0ubuntu1) yakkety; 
urgency=medium

  * Tests: create runtime directory, fix execution under pbuilder (LP:
#1614108)
  * Build-Depend on upstart to avoid s390x builds on yakkety.

 -- Alberto Mardegan   Tue, 04 Oct 2016
09:33:35 +

** Changed in: ubuntu-system-settings-online-accounts (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 ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1614108

Title:
  QStandardPaths::RuntimeLocation returns empty string under pbuilder

Status in webapps-sprint:
  In Progress
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  The unit tests for ubuntu-system-settings-online-accounts are failing
  when run under pbuilder:

  ==
  task-0: * Start testing of UiProxyTest *
  task-0: Config: Using QtTest library 5.5.1, Qt 5.5.1 
(x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.3.1 
20160519)
  task-0: PASS : UiProxyTest::initTestCase()
  task-0: PASS : UiProxyTest::testInit()
  task-0: QWARN : UiProxyTest::testRequest(success) QStandardPaths: wrong 
ownership on runtime directory /run/user/1001, -2 instead of 1234
  task-0: QWARN : UiProxyTest::testRequest(success) Couldn't setup IPC socket
  task-0: FAIL! : UiProxyTest::testRequest(success) 
'(!remoteProcesses.isEmpty())' returned FALSE. ()
  task-0: Loc: [tst_ui_proxy.cpp(319)]
  ==

  I've debugged the issue, and I've verified that
  QStandardPaths::writableLocation(QStandardPaths::RuntimeLocation) is
  returning an empty string. Although it's documented that in some
  systems that function can return NULL, it would be better if it didn't
  :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-sprint/+bug/1614108/+subscriptions

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

[Touch-packages] [Bug 1629219] Re: Blockiness in rendering when run under unity8

[Chris Coulson]

** Changed in: oxide
   Importance: Undecided => High

** Changed in: oxide
   Status: New => Triaged

** No longer affects: webbrowser-app (Ubuntu)

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

Title:
  Blockiness in rendering when run under unity8

Status in Oxide:
  Triaged

Bug description:
  Parts of the welcome page render all strange with weird blocks all
  over, see attached screenshot

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

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

[Touch-packages] [Bug 1608814] Re: qdoc moved to qttools5-dev-tools

[Launchpad Bug Tracker]

This bug was fixed in the package online-accounts-api -
0.1+16.10.20161003.1-0ubuntu1

---
online-accounts-api (0.1+16.10.20161003.1-0ubuntu1) yakkety; urgency=medium

  * debian/control:
- Depend on qttools5-dev-tools for qdoc (LP: #1608814)
  * debian/rules:
- No need to invoke dh_python

 -- Alberto Mardegan   Mon, 03 Oct 2016
09:37:16 +

** Changed in: online-accounts-api (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 ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1608814

Title:
  qdoc moved to qttools5-dev-tools

Status in online-accounts-api package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  qdoc was moved from qtbase to qttools in Qt 5.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/online-accounts-api/+bug/1608814/+subscriptions

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

[Touch-packages] [Bug 1630689] Re: online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1608560, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1630689/+attachment/4755272/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1630689/+attachment/4755274/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1630689/+attachment/4755276/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1630689/+attachment/4755277/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1630689/+attachment/4755278/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1630689/+attachment/4755279/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1630689/+attachment/4755280/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1608560

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1630689

Title:
  online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: ubuntu-system-settings-online-accounts 0.7+16.10.20160929-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity8
  Date: Wed Oct  5 17:26:23 2016
  ExecutablePath: /usr/bin/online-accounts-ui
  InstallationDate: Installed on 2016-09-02 (32 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/bin/online-accounts-ui --socket 
/run/user/1000/online-accounts-ui/ui-1-ubuntuone --profile unconfined
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=de_CH:de
   PATH=(custom, user)
   LANG=de_CH.UTF-8
  Signal: 6
  SourcePackage: ubuntu-system-settings-online-accounts
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, 
char const*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   QPlatformIntegrationFactory::create(QString const&, QStringList const&, 
int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: Upgraded to yakkety on 2016-10-01 (3 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1630689/+subscriptions

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

[Touch-packages] [Bug 1629219] Re: Blockiness in rendering when run under unity8

[Chris Coulson]

Can you paste the contents of chrome://gpu/ please?

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

Title:
  Blockiness in rendering when run under unity8

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Parts of the welcome page render all strange with weird blocks all
  over, see attached screenshot

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

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

[Touch-packages] [Bug 1528050] Re: NTP statsdir cleanup cronjob insecure

[Launchpad Bug Tracker]

This bug was fixed in the package ntp - 1:4.2.8p4+dfsg-3ubuntu5.3

---
ntp (1:4.2.8p4+dfsg-3ubuntu5.3) xenial-security; urgency=medium

  * SECURITY UPDATE: Deja Vu replay attack on authenticated broadcast mode
- debian/patches/CVE-2015-7973.patch: improve timestamp verification in
  include/ntp.h, ntpd/ntp_proto.c.
- CVE-2015-7973
  * SECURITY UPDATE: impersonation between authenticated peers
- debian/patches/CVE-2015-7974.patch: check key ID in ntpd/ntp_proto.c.
- CVE-2015-7974
  * SECURITY UPDATE: ntpq buffer overflow
- debian/patches/CVE-2015-7975.patch: add length check to ntpq/ntpq.c.
- CVE-2015-7975
  * SECURITY UPDATE: ntpq saveconfig command allows dangerous characters in
filenames
- debian/patches/CVE-2015-7976.patch: check filename in
  ntpd/ntp_control.c.
- CVE-2015-7976
  * SECURITY UPDATE: restrict list denial of service
- debian/patches/CVE-2015-7977-7978.patch: improve restrict list
  processing in ntpd/ntp_request.c.
- CVE-2015-7977
- CVE-2015-7978
  * SECURITY UPDATE: authenticated broadcast mode off-path denial of
service
- debian/patches/CVE-2015-7979.patch: add more checks to
  ntpd/ntp_proto.c.
- CVE-2015-7979
- CVE-2016-1547
  * SECURITY UPDATE: Zero Origin Timestamp Bypass
- debian/patches/CVE-2015-8138.patch: check p_org in ntpd/ntp_proto.c.
- CVE-2015-8138
  * SECURITY UPDATE: potential infinite loop in ntpq
- debian/patches/CVE-2015-8158.patch: add time checks to ntpdc/ntpdc.c,
  ntpq/ntpq.c.
- CVE-2015-8158
  * SECURITY UPDATE: NTP statsdir cleanup cronjob insecure (LP: #1528050)
- debian/ntp.cron.daily: fix security issues, patch thanks to halfdog!
- CVE-2016-0727
  * SECURITY UPDATE: time spoofing via interleaved symmetric mode
- debian/patches/CVE-2016-1548.patch: check for bogus packets in
  ntpd/ntp_proto.c.
- CVE-2016-1548
  * SECURITY UPDATE: buffer comparison timing attacks
- debian/patches/CVE-2016-1550.patch: use CRYPTO_memcmp in
  libntp/a_md5encrypt.c, sntp/crypto.c.
- CVE-2016-1550
  * SECURITY UPDATE: DoS via duplicate IPs on unconfig directives
- debian/patches/CVE-2016-2516.patch: improve logic in
  ntpd/ntp_request.c.
- CVE-2016-2516
  * SECURITY UPDATE: denial of service via crafted addpeer
- debian/patches/CVE-2016-2518.patch: check mode value in
  ntpd/ntp_request.c.
- CVE-2016-2518
  * SECURITY UPDATE: denial of service via spoofed packets
- debian/patches/CVE-2016-4954.patch: discard packet that fails tests
  in ntpd/ntp_proto.c.
- CVE-2016-4954
  * SECURITY UPDATE: denial of service via spoofed crypto-NAK or incorrect
MAC
- debian/patches/CVE-2016-4955.patch: fix checks in ntpd/ntp_proto.c.
- CVE-2016-4955
  * SECURITY UPDATE: denial of service via spoofed broadcast packet
- debian/patches/CVE-2016-4956.patch: properly handle switch in
  broadcast interleaved mode in ntpd/ntp_proto.c.
- CVE-2016-4956

 -- Marc Deslauriers   Wed, 05 Oct 2016
08:01:29 -0400

** Changed in: ntp (Ubuntu Xenial)
   Status: Triaged => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-4954

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-4955

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-4956

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

Title:
  NTP statsdir cleanup cronjob insecure

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Wily:
  Won't Fix
Status in ntp source package in Xenial:
  Fix Released

Bug description:
  The cronjob script bundled with ntp package on Ubuntu Wily is intended
  to perform cleanup on statistics files produced by NTP daemon running
  with statistics enabled. The script is run as root during the daily
  cronjobs all operations on the ntp-user controlled statistics
  directory without switching to user ntp. Thus all steps are performed
  with root permissions in place.

  Due to multiple bugs in the script, a malicious ntp user can make the
  backup process to overwrite arbitrary files with content controlled by
  the attacker, thus gaining root privileges. The problematic parts in
  /etc/cron.daily/ntp are:

  find "$statsdir" -type f -mtime +7 -exec rm {} \;

  # compress whatever is left to save space
  cd "$statsdir"
  ls *stats. > /dev/null 2>&1
  if [ $? -eq 0 ]; then
    # Note that gzip won't compress the file names that
    # are hard links to the live/current files, so this
    # compresses yesterday and previous, leaving the live
    # log alone.  We supress the warnings gzip issues
    # about not compressing the linked file.
    gzip --best --quiet *stats.

  Relevant targets are:

  find and rm invocation is racy, symlinks on rm
  rm can be 

[Touch-packages] [Bug 1552100] Re: Create .snap packages of core apps

[Bill Filler]

** Changed in: ubuntu-terminal-app
   Status: Triaged => In Progress

** Changed in: ubuntu-terminal-app
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

** Changed in: ubuntu-filemanager-app
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

** Changed in: music-app
 Assignee: (unassigned) => Andrew Hayzen (ahayzen)

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

Title:
  Create .snap packages of core apps

Status in Canonical System Image:
  Opinion
Status in Ubuntu Music App:
  Triaged
Status in Ubuntu Notes app:
  Triaged
Status in Telegram app:
  Triaged
Status in Ubuntu Calculator App:
  New
Status in Ubuntu Calendar App:
  In Progress
Status in Ubuntu Clock App:
  Triaged
Status in Ubuntu Document Viewer App:
  Triaged
Status in Ubuntu File Manager App:
  Triaged
Status in Ubuntu Shorts App:
  New
Status in Ubuntu Terminal App:
  In Progress
Status in Ubuntu Weather App:
  Triaged
Status in webbrowser-app:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Move all packages and the system to .snap (snappy)

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

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

[Touch-packages] [Bug 1627395] Re: Skip zenity guest warning dialog in MATE

[Martin Wimpress]

** Changed in: ubuntu-mate
   Status: New => Fix Released

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

Title:
  Skip zenity guest warning dialog in MATE

Status in ubuntu-mate:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  When you enter a guest session, a zenity warning dialog is started to
  explain the nature of the guest session. In Ubuntu MATE a welcome
  window is shown when a regular user logs in for the first time. When
  you enter a guest session, an adapted version of that welcome window
  is shown, which essentially provides the same information as the
  zenity dialog and makes the latter redundant. Hence the zenity dialog
  should not be shown when you enter a guest session in Ubuntu MATE.

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

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

[Touch-packages] [Bug 1630683] [NEW] ListItem: setting implicitHeight has no effect

[Andrea Bernabei]

Public bug reported:

ubuntu-ui-toolkit/staging, r2133

Description:
Creating a ListItem and setting its implicitHeight has no effect.
This means any component that derives from ListItem has to be implemented 
setting its height, while the best practice (as far as I know) is that 
components are supposed to set their implicit size, and leave the "real" size 
to the user of those components.

Investigation:
I spent some time on investigating this already. The problem is:
- 
http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/staging/view/2133/src/UbuntuToolkit/uclistitem.cpp#L1128
This means every time the width of the parent changes, ListItem will reset its 
implicit height to the default value. As a consequence, specifying a custom 
implicit height value is not allowed, because any parent's width change would 
cause it to be overwritten.
- 
http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/staging/view/2133/src/UbuntuToolkit/uclistitem.cpp#L1130
 At this point the item has the implicitHeight set by the testcase below. 
Calling _q_updateSize overwrites what the user set.


Testcase:
import QtQuick 2.4
import Ubuntu.Components 1.3

Item {
width: units.gu(42)
height: units.gu(75)
ListItem {
id: menu
Component.onCompleted: console.log(height, implicitHeight)

//This is overridden on ListItem init and on every parent's width 
change.
//It is as if it weren't there
implicitHeight: 5000

//Explicitly setting height is the only way to resize the component
height: 5000

Rectangle {
anchors.fill: parent
color: "blue"
}
}
}

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Assignee: Zsombor Egri (zsombi)
 Status: New

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

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

Title:
  ListItem: setting implicitHeight has no effect

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

Bug description:
  ubuntu-ui-toolkit/staging, r2133

  Description:
  Creating a ListItem and setting its implicitHeight has no effect.
  This means any component that derives from ListItem has to be implemented 
setting its height, while the best practice (as far as I know) is that 
components are supposed to set their implicit size, and leave the "real" size 
to the user of those components.

  Investigation:
  I spent some time on investigating this already. The problem is:
  - 
http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/staging/view/2133/src/UbuntuToolkit/uclistitem.cpp#L1128
  This means every time the width of the parent changes, ListItem will reset 
its implicit height to the default value. As a consequence, specifying a custom 
implicit height value is not allowed, because any parent's width change would 
cause it to be overwritten.
  - 
http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/staging/view/2133/src/UbuntuToolkit/uclistitem.cpp#L1130
 At this point the item has the implicitHeight set by the testcase below. 
Calling _q_updateSize overwrites what the user set.

  
  Testcase:
  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Item {
  width: units.gu(42)
  height: units.gu(75)
  ListItem {
  id: menu
  Component.onCompleted: console.log(height, implicitHeight)

  //This is overridden on ListItem init and on every parent's width 
change.
  //It is as if it weren't there
  implicitHeight: 5000

  //Explicitly setting height is the only way to resize the component
  height: 5000

  Rectangle {
  anchors.fill: parent
  color: "blue"
  }
  }
  }

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

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

[Touch-packages] [Bug 1547844] Re: systemd-fsckd does not allow fsck to finish

[kex]

I installed the 229-4ubuntu11 version.  If the system is stable till the
weekend, and does not hang/crash/livelock/deadlock/whatever happened
when I tested the ubuntu9 version, I'll twiddle max mount count to force
fsck during the weekend.

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

Title:
  systemd-fsckd does not allow fsck to finish

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  
  during normal boots, fsck runs fine with small partitions.  But I have two 
big partitions and systemd seems to abort fsck somewhere between 5 to 10 
minutes from start.  This results in the partition being checked again at every 
boot.  After manual run in recovery mode, everything is OK again. 

  See e.g.

   sudo tune2fs -l /dev/mapper/xpcvg-home 
  tune2fs 1.42.12 (29-Aug-2014)
  Filesystem volume name:   
  Last mounted on:  /home
  Filesystem UUID:  db583624-afb4-41cb-8b2d-640bee2de61b
  Filesystem magic number:  0xEF53
  Filesystem revision #:1 (dynamic)
  Filesystem features:  has_journal ext_attr resize_inode dir_index 
filetype needs_recovery extent sparse_super large_file uninit_bg
  Filesystem flags: signed_directory_hash 
  Default mount options:(none)
  Filesystem state: clean
  Errors behavior:  Continue
  Filesystem OS type:   Linux
  Inode count:  65536000
  Block count:  262144000
  Reserved block count: 13107200
  Free blocks:  183474571
  Free inodes:  65167292
  First block:  0
  Block size:   4096
  Fragment size:4096
  Reserved GDT blocks:  961
  Blocks per group: 32768
  Fragments per group:  32768
  Inodes per group: 8192
  Inode blocks per group:   512
  RAID stride:  128
  RAID stripe width:384
  Filesystem created:   Mon Jul 25 12:23:50 2011
  Last mount time:  Sat Feb 20 09:34:41 2016
  Last write time:  Sat Feb 20 09:34:41 2016
  Mount count:  166
  Maximum mount count:  157
  Last checked: Sun Nov 29 14:02:12 2015
  Check interval:   15552000 (6 months)
  Next check after: Fri May 27 15:02:12 2016
  Lifetime writes:  1113 GB
  Reserved blocks uid:  0 (user root)
  Reserved blocks gid:  0 (group root)
  First inode:  11
  Inode size: 256
  Required extra isize: 28
  Desired extra isize:  28
  Journal inode:8
  First orphan inode:   65143018
  Default directory hash:   half_md4
  Directory Hash Seed:  ea4a0233-d8af-4c51-9302-140a4affacdf
  Journal backup:   inode blocks

  journalctl says:
  helmi 20 09:30:21 xpc systemd-fsck[720]: /dev/mapper/xpcvg-home has been 
mounted 165 times without being checked, check forced.
  helmi 20 09:34:40 xpc systemd-fsck[720]: fsck: Warning... fsck.ext4 for 
device /dev/mapper/xpcvg-home exited with signal 13.
  helmi 20 09:34:40 xpc systemd-fsck[720]: fsck failed with error code 8.
  helmi 20 09:34:40 xpc systemd-fsck[720]: Ignoring error.
  helmi 20 09:34:40 xpc systemd[1]: Started File System Check on 
/dev/mapper/xpcvg-home.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 20 14:20:24 2016
  InstallationDate: Installed on 2012-12-22 (1154 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic 
root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro nomdmonddf nomdmonisw 
libata.noacpi=1 irqpoll all_generic_ide=1 ide-pci-generic.all-generic-ide=1 
usbcore.autosuspend=-1 usbcore.old_scheme_first=1 libata.force=8:1.5G 
xhci_hcd.quirks=262144
  SourcePackage: systemd
  UpgradeStatus: Upgraded to wily on 2015-10-23 (119 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI EXTREME
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIEXTREME:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage 

[Touch-packages] [Bug 1302270] Re: [regression] Poor performance with recent update with i965: libGL error: failed to open drm device: Permission denied

[Danny Howard]

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

I found this bug trying to launch firefox Ubuntu 16.04 server:

djh@test0:~$ firefox
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: i965

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

Title:
  [regression] Poor performance with recent update with i965: libGL
  error: failed to open drm device: Permission denied

Status in Compiz:
  Invalid
Status in Unity:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I rebooted into up to date trusty and noticed Unity was incredibly
  slow. I hadn't rebooted in a while, so I'm not sure what package
  caused the issue, though I'm guessing it is mesa (I saw i965 pci ids
  were ifdef'd in the Launchpad diff, but I didn't look super closely).

  ~/.xsession-errors has this to say:
  libGL error: failed to open drm device: Permission denied
  libGL error: failed to load driver: i965

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr  3 20:08:18 2014
  DistUpgraded: 2013-11-04 08:48:34,282 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:215a]
  InstallationDate: Installed on 2011-06-28 (1010 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110425.2)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 5129CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic 
root=UUID=88689ad2-74b5-442c-9290-8ae60b63e16b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2013-11-04 (150 days ago)
  dmi.bios.date: 02/24/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET64WW (1.34 )
  dmi.board.name: 5129CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET64WW(1.34):bd02/24/2011:svnLENOVO:pn5129CTO:pvrThinkPadX201s:rvnLENOVO:rn5129CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 5129CTO
  dmi.product.version: ThinkPad X201s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Apr  3 19:38:17 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16404 
   vendor LEN
  xserver.version: 2:1.15.0-1ubuntu7

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

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

[Touch-packages] [Bug 1630671] Re: sudo crashed with SIGABRT in kill()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1565332, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1630671/+attachment/4755249/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1630671/+attachment/4755251/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1630671/+attachment/4755254/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1630671/+attachment/4755255/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1630671/+attachment/4755256/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1630671/+attachment/4755257/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1630671/+attachment/4755259/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1565332
   sudo crashed with SIGABRT in kill()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  sudo crashed with SIGABRT in kill()

Status in sudo package in Ubuntu:
  New

Bug description:
  Check this out

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: sudo 1.8.16-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct  5 11:51:08 2016
  ExecutablePath: /usr/bin/sudo
  InstallationDate: Installed on 2016-10-05 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161004)
  ProcCmdline: sudo nautilus
  Signal: 6
  SourcePackage: sudo
  StacktraceTop:
   kill () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   __libc_start_main (main=0x55b752d249f0, argc=2, argv=0x7fffe94e60c8, 
init=, fini=, rtld_fini=, 
stack_end=0x7fffe94e60b8) at ../csu/libc-start.c:291
   ?? ()
  Title: sudo crashed with SIGABRT in kill()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  VisudoCheck:
   /etc/sudoers análisis OK
   /etc/sudoers.d/README análisis OK

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

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

[Touch-packages] [Bug 1623763] Re: GTK Inspector Statistics tab non-functional

[Jeremy Bicha]

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  GTK Inspector Statistics tab non-functional

Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Running a GTK+ 3 app with GOBJECT_DEBUG=instance-count enables the
  Statistics tab in GTK Inspector, but after clicking the Record button
  it never starts collecting statistics. This makes it difficult to
  develop and debug memory leaks in GTK programs on Ubuntu.

  To reproduce:

  1. Start an app with the Inspector and GOBJECT_DEBUG=instance-count
  set, e.g.:

  > GOBJECT_DEBUG=instance-count GTK_DEBUG=interactive gnome-calculator

  2. Click the Statistics tab
  3. Click the Record button
  4. Click around the app a bit

  Expected: Object counts go up, pretty graphs showing things
  Actual: Object counts stay at 0, pretty graphs showing flat lines

  This seems like it is Ubuntu-specific, since when running GTK+
  programs installed via Flatpak (and hence using the Flatpak runtime),
  the above works fine on the same system.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-dev 3.20.8-1ubuntu0~ppa1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 15 13:05:19 2016
  InstallationDate: Installed on 2015-07-22 (421 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to xenial on 2016-03-02 (196 days ago)

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

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

[Touch-packages] [Bug 1628161] Re: SlotsLayout height is not dynamically updated when main paddings change

[Andrea Bernabei]

** Also affects: ubuntu-ui-toolkit (Ubuntu RTM)
   Importance: Undecided
   Status: New

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

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

Title:
  SlotsLayout height is not dynamically updated when main paddings
  change

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

Bug description:
  You can see this in the attached testcase.

  When paddings are changed, the SlotsLayout height is not updated
  dynamically.

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

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

[Touch-packages] [Bug 1630662] [NEW] Can't connect to CalDAV server

[Mikael]

Public bug reported:

I'm trying to connect Maya Calendar to caldav.one.com. I've setup
everything up as per the instructions from one.com. Still when I enter
my Username and Password and click OK I get back to the same window
asking for my Username and Password. I get no error message. I'm using
caldav.one.com on my phone and it works. Please let me know what further
details that are needed.

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Can't connect to CalDAV server

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  I'm trying to connect Maya Calendar to caldav.one.com. I've setup
  everything up as per the instructions from one.com. Still when I enter
  my Username and Password and click OK I get back to the same window
  asking for my Username and Password. I get no error message. I'm using
  caldav.one.com on my phone and it works. Please let me know what
  further details that are needed.

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

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

[Touch-packages] [Bug 1435465] Re: Alt+F4 crashes app where WebView embedded in a Window

[Olivier Tilloy]

** Changed in: qtbase-opensource-src (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Alt+F4 crashes app where WebView embedded in a Window

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  was just watching something on Youtube Web App created by unity
  itself. when i pressed alt-f4 Ubuntu said it had an error and if i
  want to submit it.

  that is all folks.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: webapp-container 0.23+15.04.20150320.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 23 19:56:16 2015
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2015-03-22 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
  ProcCmdline: webapp-container --app-id=YouTubeyoutubecom 
--webapp=WW91VHViZQ== --enable-back-forward
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? ()
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
  Title: webapp-container crashed with SIGSEGV in QMetaObject::activate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1435465/+subscriptions

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

[Touch-packages] [Bug 1602628] Re: can't drag/move window if it's semi-maximized by Ctrl+Super+Left/Right

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/unity8/unity8-ubuntu-yakkety-2026

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

Title:
  can't drag/move window if it's semi-maximized by Ctrl+Super+Left/Right

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

Bug description:
  ubuntu 16.10
  can't drag/move window if it's semi-maximized

  open random app, semi-miaximize left or rigt (CTRL SUPER + Left or
  Right), try to move the window by draggin' it from the title bar.

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

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

[Touch-packages] [Bug 1611859] Re: Keyboard layout isn't applied in dash after wizard

[Launchpad Bug Tracker]

** Branch linked: lp:~ci-train-bot/unity8/unity8-ubuntu-yakkety-2026

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

Title:
  Keyboard layout isn't applied in dash after wizard

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

Bug description:
  In https://requests.ci-train.ubuntu.com/#/ticket/1771

  Steps:
  * connect a BT or a physical keyboard
  * wipe or remove ~/.config/ubuntu-system-settings/wizard-has-run* and reboot
  * go through the wizard

  Expected:
  * I can use the selected layout in the dash after completing the wizard

  Current:
  * layout is only applied on first app focus change

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.14+16.04.20160810.2-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-landing-001]
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 10 19:04:24 2016
  InstallationDate: Installed on 2016-05-06 (95 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/1611859/+subscriptions

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

[Touch-packages] [Bug 1552100] Re: Create .snap packages of core apps

[Emanuele Antonio Faraone]

** Also affects: webbrowser-app
   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/1552100

Title:
  Create .snap packages of core apps

Status in Canonical System Image:
  Opinion
Status in Ubuntu Music App:
  Triaged
Status in Ubuntu Notes app:
  Triaged
Status in Telegram app:
  Triaged
Status in Ubuntu Calculator App:
  New
Status in Ubuntu Calendar App:
  In Progress
Status in Ubuntu Clock App:
  Triaged
Status in Ubuntu Document Viewer App:
  Triaged
Status in Ubuntu File Manager App:
  Triaged
Status in Ubuntu Shorts App:
  New
Status in Ubuntu Terminal App:
  Triaged
Status in Ubuntu Weather App:
  Triaged
Status in webbrowser-app:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Move all packages and the system to .snap (snappy)

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

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

[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

[Michael Terry]

** Also affects: unity-scopes-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity-scopes-shell (Ubuntu)
 Assignee: (unassigned) => Michael Terry (mterry)

** Branch linked: lp:~mterry/unity8/snap-root

** Changed in: unity-scopes-api (Ubuntu)
   Status: New => 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/1629009

Title:
  Does not work inside a snap due to hardcoded paths

Status in address-book-app package in Ubuntu:
  Fix Committed
Status in dialer-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-terminal-app package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

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

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

[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths

[Launchpad Bug Tracker]

** Branch linked: lp:~mterry/unity-scopes-api/snap-root

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

Title:
  Does not work inside a snap due to hardcoded paths

Status in address-book-app package in Ubuntu:
  Fix Committed
Status in dialer-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-terminal-app package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  Some apps can't find their main qml file.  Error messages like:

  "file:///build/messaging-app-gcXPE6/messaging-
  app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"

  (in my case, the file was in /snap/unity8-session/x24/usr/share
  /messaging-app/messaging-app.qml)

  Seems due to code like the following in config.h.in.  Probably needs
  to consider the value of $SNAP or just be a little more forgiving.

  inline bool isRunningInstalled() {
  static bool installed = (QCoreApplication::applicationDirPath() ==
   
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
  return installed;
  }

  inline QString messagingAppDirectory() {
  if (isRunningInstalled()) {
  return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
  } else {
  return QString("@CMAKE_SOURCE_DIR@/src/qml/");
  }
  }

  inline QString ubuntuPhonePluginPath() {
  if (isRunningInstalled()) {
  return QString::null;
  } else {
  return QString("@CMAKE_SOURCE_DIR@/");
  }
  }

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

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

[Touch-packages] [Bug 1630640] Re: signon-ui crashed with SIGABRT in QMessageLogger::fatal()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1608562, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1630640/+attachment/4755148/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1630640/+attachment/4755150/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1630640/+attachment/4755153/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1630640/+attachment/4755154/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1630640/+attachment/4755155/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1630640/+attachment/4755156/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1630640/+attachment/4755157/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1608562

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  signon-ui crashed with SIGABRT in QMessageLogger::fatal()

Status in signon-ui package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: signon-ui-x11 0.17+16.04.20160406-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct  5 17:27:31 2016
  ExecutablePath: /usr/bin/signon-ui
  InstallationDate: Installed on 2016-04-05 (183 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/signon-ui
  Signal: 6
  SourcePackage: signon-ui
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, 
char const*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
   QPlatformIntegrationFactory::create(QString const&, QStringList const&, 
int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  Title: signon-ui crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: Upgraded to yakkety on 2016-10-04 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1441901] Re: 3G modem mode switch doesn't work when using systemd

[Anand Kumria]

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

Ahh, in fact, I've found that by modifying
/lib/systemd/system/usb_modeswitch@.service and changing ExecStart to
be:


...
ExecStart=/bin/echo %i
...

Will cause udev to handle the device normally. So it is switched
correctly.

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

Title:
  3G modem mode switch doesn't work when using systemd

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  I'm using Ubuntu 14.10 and I've got USB 3G modem Huawei E173. If I use
  upstart, when I connect this modem, it is automatically switched to
  modem-mode and I can connect to the network. But if I switch to
  systemd, it doesn't, but I'm able to switch it manually using command:

  sudo usb_modeswitch -v 0x12d1 -p 0x1446 -V 0x12d1 -P 0x1436 -M
  55534243123456780011062001

  I'm using kernel 3.19.3 64-bit from Ubuntu Kernel PPA:

  3.19.3-031903-generic #201503261036 SMP Thu Mar 26 14:37:55 UTC 2015
  x86_64 x86_64 x86_64 GNU/Linux

  All system packages are up-to-date.

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

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

[Touch-packages] [Bug 1620635] Re: libapparmor's aa_query_label() always returns allowed = 0 for file rules containing the "owner" conditional

[Bill Filler]

** Tags added: snap-desktop-issue

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

Title:
  libapparmor's aa_query_label() always returns allowed = 0 for file
  rules containing the "owner" conditional

Status in AppArmor:
  Triaged
Status in Snappy:
  Won't Fix
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. Download and compile the following sample C app that calls aa_query_label

  wget https://launchpadlibrarian.net/207629699/query_file.c
  gcc -o query_file query_file.c -l apparmor

  2. Install a snap that uses the home interface, for example demo-wget:

  snap install demo-wget

  3. Create a file in your home:

  touch /home/USERNAME/testfile

  4. Ask apparmor if demo-wget can read that file with query_file:

  ./query_file snap.demo-wget.wget /home/USERNAME/testfile

  
  Expected result:

  output of ./query_file command is 
  read '/home/kaleo/toto' allowed

  
  Current result:

  output of ./query_file command is 
  read '/home/kaleo/toto' denied

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

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

[Touch-packages] [Bug 1441901] Re: 3G modem mode switch doesn't work when using systemd

[Anand Kumria]

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

However, calling, usb_modeswitch_dispatcher with the following:

# /usr/sbin/usb_modeswitch_dispatcher --switch-systemd 1-9:1.0

Seems to work fine.

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

Title:
  3G modem mode switch doesn't work when using systemd

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  I'm using Ubuntu 14.10 and I've got USB 3G modem Huawei E173. If I use
  upstart, when I connect this modem, it is automatically switched to
  modem-mode and I can connect to the network. But if I switch to
  systemd, it doesn't, but I'm able to switch it manually using command:

  sudo usb_modeswitch -v 0x12d1 -p 0x1446 -V 0x12d1 -P 0x1436 -M
  55534243123456780011062001

  I'm using kernel 3.19.3 64-bit from Ubuntu Kernel PPA:

  3.19.3-031903-generic #201503261036 SMP Thu Mar 26 14:37:55 UTC 2015
  x86_64 x86_64 x86_64 GNU/Linux

  All system packages are up-to-date.

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

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

[Touch-packages] [Bug 1441901] Re: 3G modem mode switch doesn't work when using systemd

[Anand Kumria]

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

The same problem occurs with Ubuntu 16.04 LTS.

Cold-boot, particularly, this seems to fail.

Basically the problem is that usb_modeswitch_dispatcher is called with
incorrect arguments.


# systemctl --all | grep usb_modeswitch
● usb_modeswitch@1-9_1-9:1.0.service
loadedfailed   failedUSB_ModeSwitch_1-9_1-9:1.0
  system-usb_modeswitch.slice   
loadedactive   activesystem-usb_modeswitch.slice

# systemctl status -l usb_modeswitch@1-9_1-9:1.0.service
● usb_modeswitch@1-9_1-9:1.0.service - USB_ModeSwitch_1-9_1-9:1.0
   Loaded: loaded (/lib/systemd/system/usb_modeswitch@.service; static; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Wed 2016-10-05 13:33:07 UTC; 1h 
4min ago
  Process: 615 ExecStart=/usr/sbin/usb_modeswitch_dispatcher --switch-systemd 
%i (code=exited, status=1/FAILURE)
 Main PID: 615 (code=exited, status=1/FAILURE)

Oct 05 13:33:04 giskard2 systemd[1]: Starting USB_ModeSwitch_1-9_1-9:1.0...
Oct 05 13:33:07 giskard2 systemd[1]: usb_modeswitch@1-9_1-9:1.0.service: Main 
process exited, code=exited, status=1/FAILURE
Oct 05 13:33:07 giskard2 systemd[1]: Failed to start USB_ModeSwitch_1-9_1-9:1.0.
Oct 05 13:33:07 giskard2 systemd[1]: usb_modeswitch@1-9_1-9:1.0.service: Unit 
entered failed state.
Oct 05 13:33:07 giskard2 systemd[1]: usb_modeswitch@1-9_1-9:1.0.service: Failed 
with result 'exit-code'.

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

Title:
  3G modem mode switch doesn't work when using systemd

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  I'm using Ubuntu 14.10 and I've got USB 3G modem Huawei E173. If I use
  upstart, when I connect this modem, it is automatically switched to
  modem-mode and I can connect to the network. But if I switch to
  systemd, it doesn't, but I'm able to switch it manually using command:

  sudo usb_modeswitch -v 0x12d1 -p 0x1446 -V 0x12d1 -P 0x1436 -M
  55534243123456780011062001

  I'm using kernel 3.19.3 64-bit from Ubuntu Kernel PPA:

  3.19.3-031903-generic #201503261036 SMP Thu Mar 26 14:37:55 UTC 2015
  x86_64 x86_64 x86_64 GNU/Linux

  All system packages are up-to-date.

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

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

[Touch-packages] [Bug 1595963] Re: vt1-6 getting stuck or blank

[Phillip Susi]

And you can't identify any pattern or cause for it going dead?  It just
happens randomly after it had been working fine?  And switching to
another tty and back doesn't help?

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

Title:
  vt1-6 getting stuck or blank

Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  It's happening from time to time that my vt1-6 are getting stuck
  (showing tty1 and no input) or blank (just black) completely.

  Restarting system-getty.slice or console-getty.slice doesn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.1
  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: Fri Jun 24 10:00:54 2016
  InstallationDate: Installed on 2016-05-06 (48 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-05-06 (48 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS 12-9Q33
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: systemd 229-4ubuntu6
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic.efi.signed 
root=ZFS=/root ro root=ZFS=username-laptop/root quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   
   3 overridden configuration files found.
  Tags:  xenial
  Uname: Linux 4.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/15/2014:svnDellInc.:pnXPS12-9Q33:pvrA06:rvnDellInc.:rnXPS12-9Q33:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1630510] Re: webbrowser-app crashed with SIGSEGV in QNetworkSession::~QNetworkSession()

[Olivier Tilloy]

** Information type changed from Private to Public

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

Title:
  webbrowser-app crashed with SIGSEGV in
  QNetworkSession::~QNetworkSession()

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Crash on close

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: webbrowser-app 0.23+16.10.20160928-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Wed Oct  5 20:49:26 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-08-14 (51 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160813)
  ProcCmdline: webbrowser-app
  ProcEnviron:
   PATH=(custom, user)
   LANGUAGE=en_AU:en
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: webbrowser-app
  StacktraceTop:
   QNetworkSession::~QNetworkSession() () from 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
   QNetworkSession::~QNetworkSession() () from 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
   QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QApplicationPrivate::notify_helper(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
   QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  Title: webbrowser-app crashed with SIGSEGV in 
QNetworkSession::~QNetworkSession()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1441901] Re: 3G modem mode switch doesn't work when using systemd

[Launchpad Bug Tracker]

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

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

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

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

Title:
  3G modem mode switch doesn't work when using systemd

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  I'm using Ubuntu 14.10 and I've got USB 3G modem Huawei E173. If I use
  upstart, when I connect this modem, it is automatically switched to
  modem-mode and I can connect to the network. But if I switch to
  systemd, it doesn't, but I'm able to switch it manually using command:

  sudo usb_modeswitch -v 0x12d1 -p 0x1446 -V 0x12d1 -P 0x1436 -M
  55534243123456780011062001

  I'm using kernel 3.19.3 64-bit from Ubuntu Kernel PPA:

  3.19.3-031903-generic #201503261036 SMP Thu Mar 26 14:37:55 UTC 2015
  x86_64 x86_64 x86_64 GNU/Linux

  All system packages are up-to-date.

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

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

[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

[Hansen]

Well for what it's worth the bug seems to be fixed in 16.10

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Touch-packages] [Bug 1623383] Re: Some restarts fail due to missing base devices

[Dimitri John Ledkov]

** Package changed: udev (Ubuntu) => systemd (Ubuntu)

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

Title:
  Some restarts fail due to missing base devices

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Arch: s390x
  Release: Yakkety / 16.10

  This happens on some (but not all) system starts with Yakkety. In
  Xenial (which is using the same 4.4 kernel version the Yakkety systems
  were using when the problem was first observed) this did not happen.
  The system (LPAR) this was seen first was an upgrade from Xenial but
  since then has been freshly installed with Yakkety. The same behaviour
  is seen on a zVM guest running Yakkety.

  The attached syslog shows a failed boot, followed by one that did work. Note 
the "Found device .*(sclp|encc00).*" messages in the good boot. Those are 
missing in the bad attempt and as a result networking and console fail to be 
usable. Also note, those boots were 4.8 kernels but we saw this with 4.4 
kernels, too.
  This might be a systemd problem / race, I just filed it into udev for now as 
that better matches the not finding basic devices symptom.

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

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