[Touch-packages] [Bug 1317437] Re: wubi kernel option "rw" required

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~noorez-kassam/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/321514

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

Title:
  wubi kernel option "rw" required

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  We have installed ubuntu beta-64amd.iso (trusty tahr) as wubi on a
  windows 8.1.

  Since upgrade
   * busybox-initramfs from "1.20.0-8.1ubuntu1" to "1.21.0-1ubuntu1"
   * busybox-static from "1.20.0-8.1ubuntu1" to "1.21.0-1ubuntu1"
  the wubi installation won't work / start and ends with the massage:
  "Bei der Ueberpruefung des Laufwerkes auf / wurden schwere Fehler gefunden"

  "key: »I« zum Ignorieren, »S« ueberspringt das Einhaengen, »M« fuer
  manuelle Wiederherstellung"

  Changing the sequence of "/boot/grub/grub.cfg" inside the line:
   * linux  /boot/vmlinuz-3.13.0-24-generic root=UUID=B65449E05449A449 
loop=/ubuntu/disks/root.disk ro   quiet splash $vt_handoff
  into
   * linux  /boot/vmlinuz-3.13.0-24-generic root=UUID=B65449E05449A449 
loop=/ubuntu/disks/root.disk rw  quiet splash $vt_handoff
  (kernel option »ro« into »rw«) lets start the wubi installation without any 
restrictions.

  For further system-information see -> annex

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lupin-support 0.55
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Thu May  8 10:53:53 2014
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lupin
  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/1317437/+subscriptions

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

[Touch-packages] [Bug 1644530] Re: keepalived fails to restart cleanly due to the wrong systemd settings

[Launchpad Bug Tracker]

This bug was fixed in the package keepalived - 1:1.2.19-1ubuntu0.2

---
keepalived (1:1.2.19-1ubuntu0.2) xenial; urgency=medium

  * Add PIDFile to avoid misdetection of MainPID on restart (LP:
#1644530).

 -- Christian Ehrhardt   Mon, 13 Mar
2017 13:23:47 +0100

** Changed in: keepalived (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1644530

Title:
  keepalived fails to restart cleanly due to the wrong systemd settings

Status in keepalived package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in keepalived source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in keepalived package in Debian:
  New

Bug description:
  [Impact]

   * Restarts of keepalived can leave stale processes with the old
  configuration around.

   * The systemd detection of the MainPID is suboptimal, and combined
  with not waiting on signals being handled it can fail on second
  restart killing the (still) remaining process of the first start.

   * Upstream has a PIDFile statement, this has proven to avoid the
  issue in the MainPID guessing code of systemd.

  [Test Case]

   * Set up keepalived, the more complex the config is the "bigger" is the 
reace window, below in the description is a trivial sample config that works 
well.
   
   * As a test run the loop restarting the service head-to-head while staying 
under the max-restart limit
  $ for j in $(seq 1 20); do sleep 11s; time for i in $(seq 1 5); do sudo 
systemctl restart keepalived; sudo systemctl status keepalived | egrep 
'Main.*exited'; done; done

   Expectation: no output other than timing
   Without fix: sometimes MainPIDs do no more exist, in these cases the child 
processes are the "old" ones from last execution with the old config.

  [Regression Potential]

   * Low because
 * A PIDFile statement is recommended by systemd for type=forking services 
anyway.
 * Upstream keepalived has this statement in their service file
 * By the kind of change, it should have no functional impact to other 
parts of the service other than for the PID detection of the job by Systemd.

   * Yet regression potential is never zero. There might be the unlikely
  case, which were considered working before due to a new config not
  properly being picked up. After the fix they will behave correctly and
  might show up as false-positives then if e.g. config was bad.

  [Other Info]
   
   * Usually a fix has to be in at least the latest Development release before 
SRUing it. But as I outlined below in later Releases than Xenial systemd seems 
to have improved making this change not-required. We haven't identified the 
bits for this (there is a bug task here), and they might as well be very 
complex. I think it is correct to fix Xenial in this regard with the simple 
change to the service file for now.

   * To eventually match I created a Debian bug task to ask them for the
  inclusion of the PIDFile so it can slowly tickle back down to newer
  Ubuntu Releases - also there more often people run backports where the
  issue might occur on older systemd versions (just as it does for us on
  Xenial)

  ---

  Because "PIDFile=" directive is missing in the systemd unit file,
  keepalived sometimes fails to kill all old processes. The old
  processes remain with old settings and cause unexpected behaviors. The
  detail of this bug is described in this ticket in upstream:
  https://github.com/acassen/keepalived/issues/443.

  The official systemd unit file is available since version 1.2.24 by
  this commit:

  
https://github.com/acassen/keepalived/commit/635ab69afb44cd8573663e62f292c6bb84b44f15

  This includes "PIDFile" directive correctly:

  PIDFile=/var/run/keepalived.pid

  We should go the same way.

  I am using Ubuntu 16.04.1, kernel 4.4.0-45-generic.

  Package: keepalived
  Version: 1.2.19-1

  ===

  How to reproduce:

  I used the two instances of Ubuntu 16.04.2 on DigitalOcean:

  Configurations
  --

  MASTER server's /etc/keepalived/keepalived.conf:

    vrrp_script chk_nothing {
   script "/bin/true"
   interval 2
    }

    vrrp_instance G1 {
  interface eth1
  state BACKUP
  priority 100

  virtual_router_id 123
  unicast_src_ip 
  unicast_peer {
    
  }
  track_script {
    chk_nothing
  }
    }

  BACKUP server's /etc/keepalived/keepalived.conf:

    vrrp_script chk_nothing {
   script "/bin/true"
   interval 2
    }

    vrrp_instance G1 {
  interface eth1
  state MASTER
  priority 200

  virtual_router_id 123
  unicast_src_ip 
  unicast_peer {
    
  }
  track_script {
    

[Touch-packages] [Bug 1644530] Update Released

[Steve Langasek]

The verification of the Stable Release Update for keepalived 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1644530

Title:
  keepalived fails to restart cleanly due to the wrong systemd settings

Status in keepalived package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in keepalived source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  New
Status in keepalived package in Debian:
  New

Bug description:
  [Impact]

   * Restarts of keepalived can leave stale processes with the old
  configuration around.

   * The systemd detection of the MainPID is suboptimal, and combined
  with not waiting on signals being handled it can fail on second
  restart killing the (still) remaining process of the first start.

   * Upstream has a PIDFile statement, this has proven to avoid the
  issue in the MainPID guessing code of systemd.

  [Test Case]

   * Set up keepalived, the more complex the config is the "bigger" is the 
reace window, below in the description is a trivial sample config that works 
well.
   
   * As a test run the loop restarting the service head-to-head while staying 
under the max-restart limit
  $ for j in $(seq 1 20); do sleep 11s; time for i in $(seq 1 5); do sudo 
systemctl restart keepalived; sudo systemctl status keepalived | egrep 
'Main.*exited'; done; done

   Expectation: no output other than timing
   Without fix: sometimes MainPIDs do no more exist, in these cases the child 
processes are the "old" ones from last execution with the old config.

  [Regression Potential]

   * Low because
 * A PIDFile statement is recommended by systemd for type=forking services 
anyway.
 * Upstream keepalived has this statement in their service file
 * By the kind of change, it should have no functional impact to other 
parts of the service other than for the PID detection of the job by Systemd.

   * Yet regression potential is never zero. There might be the unlikely
  case, which were considered working before due to a new config not
  properly being picked up. After the fix they will behave correctly and
  might show up as false-positives then if e.g. config was bad.

  [Other Info]
   
   * Usually a fix has to be in at least the latest Development release before 
SRUing it. But as I outlined below in later Releases than Xenial systemd seems 
to have improved making this change not-required. We haven't identified the 
bits for this (there is a bug task here), and they might as well be very 
complex. I think it is correct to fix Xenial in this regard with the simple 
change to the service file for now.

   * To eventually match I created a Debian bug task to ask them for the
  inclusion of the PIDFile so it can slowly tickle back down to newer
  Ubuntu Releases - also there more often people run backports where the
  issue might occur on older systemd versions (just as it does for us on
  Xenial)

  ---

  Because "PIDFile=" directive is missing in the systemd unit file,
  keepalived sometimes fails to kill all old processes. The old
  processes remain with old settings and cause unexpected behaviors. The
  detail of this bug is described in this ticket in upstream:
  https://github.com/acassen/keepalived/issues/443.

  The official systemd unit file is available since version 1.2.24 by
  this commit:

  
https://github.com/acassen/keepalived/commit/635ab69afb44cd8573663e62f292c6bb84b44f15

  This includes "PIDFile" directive correctly:

  PIDFile=/var/run/keepalived.pid

  We should go the same way.

  I am using Ubuntu 16.04.1, kernel 4.4.0-45-generic.

  Package: keepalived
  Version: 1.2.19-1

  ===

  How to reproduce:

  I used the two instances of Ubuntu 16.04.2 on DigitalOcean:

  Configurations
  --

  MASTER server's /etc/keepalived/keepalived.conf:

    vrrp_script chk_nothing {
   script "/bin/true"
   interval 2
    }

    vrrp_instance G1 {
  interface eth1
  state BACKUP
  priority 100

  virtual_router_id 123
  unicast_src_ip 
  unicast_peer {
    
  }
  track_script {
    chk_nothing
  }
    }

  BACKUP server's /etc/keepalived/keepalived.conf:

    vrrp_script chk_nothing {
   script "/bin/true"
   interval 2
    }

    vrrp_instance G1 {
  interface eth1
  state MASTER
  priority 200

  virtual_router_id 123
  unicast_src_ip 
    

[Touch-packages] [Bug 1675163] Re: Don't attempt to create devices in LXC containers

[Stéphane Graber]

** Changed in: makedev (Ubuntu Precise)
 Assignee: rahmadani (rahmadani) => (unassigned)

** Changed in: makedev (Ubuntu Trusty)
 Assignee: rahmadani (rahmadani) => (unassigned)

** Changed in: makedev (Ubuntu Xenial)
 Assignee: rahmadani (rahmadani) => (unassigned)

** Changed in: makedev (Ubuntu Yakkety)
 Assignee: rahmadani (rahmadani) => (unassigned)

** Changed in: makedev (Ubuntu Zesty)
 Assignee: rahmadani (rahmadani) => (unassigned)

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

Title:
  Don't attempt to create devices in LXC containers

Status in makedev package in Ubuntu:
  Fix Released
Status in makedev source package in Precise:
  Fix Released
Status in makedev source package in Trusty:
  Fix Released
Status in makedev source package in Xenial:
  Fix Released
Status in makedev source package in Yakkety:
  Fix Released
Status in makedev source package in Zesty:
  Fix Released

Bug description:
  Right now the "makedev" postinst script will attempt to create a
  number of devices in /dev, failing the package upgrade should any of
  those mknod calls fail.

  LXC containers, especially unprivileged ones do not allow the use of
  mknod, making it impossible to upgrade makedev in those containers and
  preventing Ubuntu release upgrades.

  The fix is quite simple, detect that we are running in an LXC
  container and skip the rest of the postinst script as is done in a
  number of other cases.

  = SRU
  == Rationale
  This issue prevents release to release upgrades in unprivileged LXC 
containers when makedev is part of the upgraded set. This is currently visible 
when upgrading from Ubuntu 12.04 to Ubuntu 14.04.

  == Testcase
  Install the new package in an unprivileged container. With LXD, simply use 
"lxc launch ubuntu: test" to create the container.

  Prior to this fix, the upgrade will fail on some mknod errors, after
  it, it'll go on after printing a message indicating that LXC was
  detected.

  == Regression potential
  The detection logic is based on PID 1's environment containing a 
container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the 
makedev upgrade no longer creating extra devices. This is unlikely to really 
matter though since the system is clearly already functioning properly at that 
point.

  Similarly, some privileged LXC containers can be configured in a way
  where mknod is possible, this update will still disable the postinst
  for those cases as short of attempting every mknod ahead of time,
  there is no reliable way to detect any seccomp or apparmor policy in
  play.

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

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

[Touch-packages] [Bug 1677625] Re: ubuntu-terminal-app if the preferences window is minimized and you click on the cogwheel it doesn't bring up the preferences window and also you can't type in the te

[Daniel van Vugt]

Oh it's a new terminal app "from overlay PPA".

I would hazard a guess the correct title of this bug should be:
"Unity8 allows model dialogs to be minimized, leave the parent window 
unoccluded but unresponsive."

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

** Changed in: ubuntu-terminal-app
   Status: New => Incomplete

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

** Tags added: unity8-desktop

** Summary changed:

- ubuntu-terminal-app if the preferences window is minimized and you click on 
the cogwheel it doesn't bring up the preferences window and also you can't type 
in the terminal anymore
+ Unity8 allows model dialogs to be minimized, leave the parent window 
unoccluded but unresponsive

** Summary changed:

- Unity8 allows model dialogs to be minimized, leave the parent window 
unoccluded but unresponsive
+ Unity8 allows modal dialogs to be minimized, leave the parent window 
unoccluded but unresponsive

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

Title:
  Unity8 allows modal dialogs to be minimized, leave the parent window
  unoccluded but unresponsive

Status in Canonical System Image:
  Incomplete
Status in Ubuntu Terminal App:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 17.04, terminal app from overlay ppa

  ubuntu-terminal-app if the preferences window is minimized and you
  click on the cogwheel it doesn't bring up the preferences window and
  also you can't type in the terminal anymore

  it happens to me a lot, i open the preferences window, minimize it and
  forget about it, then if i click on the cogwheel it doesn't bring up
  the preferences window and the terminal just loses focus and you can't
  type in it anymore

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

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

[Touch-packages] [Bug 1677629] Re: ubuntu-terminal-app doesn't remember the size of the preferences window

[Daniel van Vugt]

** Tags added: unity8-desktop

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

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

Title:
  ubuntu-terminal-app doesn't remember the size of the preferences
  window

Status in Canonical System Image:
  New
Status in Ubuntu Terminal App:
  New
Status in ubuntu-terminal-app package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 ubuntu-terminal-app from overlay ppa

  ubuntu-terminal-app doesn't remember the size of the preferences window
  start the terminal, open the preferences window (by clicking on the 
cogwheel), resize the the preferences window. now close the terminal and 
reopen, now the preferences window is the same size of the terminal window and 
not as the previous size

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

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

[Touch-packages] [Bug 1638167] Re: Thin grey rendering on a white background look inconsistent and provide poor contrast

[Daniel van Vugt]

** Summary changed:

- Thin grey lines on a white background look inconsistent and provide poor 
contrast
+ Thin grey rendering on a white background look inconsistent and provide poor 
contrast

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

Title:
  Thin grey rendering on a white background look inconsistent and
  provide poor contrast

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  The top area of the browser window is really just a series thin grey
  lines on a white background. This is poor design for a few reasons:

    1. Grey and white don't contrast very well, especially thin strips of grey 
on white.
    2. The grey outlines and symbols are inconsistent in thickness and colour:
   2.1. The X icon is thinner than the + icon beside it, which is a 
different consistency again to the < button below it.
   2.2. The rounded grey outline around the address is slighly thicker 
(blurred?) compared to the grey outline delineating the tabs.
    3. Those vision impaired will have a very hard time.
    4. Even those who are not vision impaired will be cognitively slowed by 
having to interpret the fine grey lines rather than areas of greater contrast.
5. It looks unprofessional.

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

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

[Touch-packages] [Bug 1677540] Re: corrupted mouse pointer icon

[Daniel van Vugt]

It looks like a corrupt texture cache/atlas in Unity8 itself...

** Also affects: mir
   Importance: Undecided
   Status: New

** Tags added: cursor unity8-desktop visual-quality

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

Title:
  corrupted mouse pointer icon

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in libsdl2 package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 unity8

  corrupted mouse pointer icon (see attaches screenshot, the mouse pointer is 
hovering places/Home on the file manager app, the orange block/square)
  mostly i see when i run apps with Xmir, maybe stuff that uses SDL, mpv, 
neverball 

  and it's only the arrow pointer, the rest are not affected, resize
  arrows etc

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

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

[Touch-packages] [Bug 1676931] Re: logs are not included in unity-system-compositor bugs automatically reported to Ubuntu using apport

[Daniel van Vugt]

** Changed in: unity-system-compositor (Ubuntu)
   Status: In Progress => Triaged

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

Title:
  logs are not included in unity-system-compositor bugs automatically
  reported to Ubuntu using apport

Status in Canonical System Image:
  In Progress
Status in Unity System Compositor:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  Triaged

Bug description:
  When a crash in unity-system-compositor is automatically reported to
  the Ubuntu bug tracker using the apport tool, additional information
  should be included to make analysis easier.

  At the very least, /var/log/lightdm/unity-system-compositor.log should
  be included.

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

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

[Touch-packages] [Bug 1677430] Re: Titlebar text shifts (changes length) when activating/deactivating a window

[Daniel van Vugt]

No problem. Designs can have bugs too. Let's fix it :)

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

Title:
  Titlebar text shifts (changes length) when activating/deactivating a
  window

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

Bug description:
  Titlebar text shifts (changes length) when activating/deactivating a
  window.

  Seems to be because we're jumping between a bold and regular font.
  Ideally it should be the same font, just a different colour.

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

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

[Touch-packages] [Bug 1672693] Re: GTK theme in apps appears different under Unity8 compared to Unity7

[Daniel van Vugt]

Are you sure ubuntu-app-launch doesn't/shouldn't play a role in
providing some kind of session/settings for GTK apps to get?

I know theoretically this could be fixed in GTK, UAL or Unity8. Just
don't know where is the correct place.

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

** 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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1672693

Title:
  GTK theme in apps appears different under Unity8 compared to Unity7

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.05 Unity8
  some submenus in GTK3 apps look like widgets (see attached screenshots)
  run whatever gtk3 apps native (without Xmir), sol or eog
  open the menu/submenus. the first time you open the menu everything is fine 
but the next times it shows this widget like submenus. just open and close 
submenus (hover the mouse over the main menu left right, right left)

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

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

[Touch-packages] [Bug 1377427] Re: BQ: Thin column of pixels visible on the left (wrapped from the right)

[Daniel van Vugt]

Won't Fix might not be appropriate if this is something like an
uninitialized variable affecting the framebuffer offset... But hopefully
this is a device-specific bug not in the Mir code.

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

Title:
  BQ: Thin column of pixels visible on the left (wrapped from the right)

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Won't Fix
Status in mir package in Ubuntu:
  Won't Fix
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  with image 81 my krillin shows a white 1px line on the left edge of
  the screen, specifically visible when switching apps or sliding the
  launcher in.

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

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

[Touch-packages] [Bug 978604] Re: Banshee/Rhythmbox regularly stop playing audio when left on in the background

[Graham T]

2017 - still happening. LinuxMint 17.3 Cinnamon. Player is Banshee.

syslog snippet when playback stops:
Mar 31 02:39:27 mypc pulseaudio[2108]: [alsa-sink-ALC269VB Analog] ratelimit.c: 
70 events suppressed
Mar 31 02:39:27 mypc pulseaudio[2108]: [alsa-sink-ALC269VB Analog] 
protocol-native.c: Failed to push data into queue

Always happens on transition from one track to another. Always resolved
for me by simply double-clicking on the track that failed to start
playback. No Banshee restart required, just click to play the next track
and off it goes for a seemingly random number of tracks before it
strikes again.

No biggy. Just posting this really to note it's still an unresolved
issue.

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

Title:
  Banshee/Rhythmbox regularly stop playing audio when left on in the
  background

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Precise:
  Confirmed

Bug description:
  If Banshee or Rhythmbox is left playing in the background they will
  randomly stop playing in the latest builds of Ubuntu 12.04. Starting a
  new piece of music usually fixes the problem. If left to its own
  devices, the music will start playing again at some random time, at
  some random position. This problem exists on both my desktop machine
  (custom built Intel machine) and my laptop (Macbook 5,1). It has been
  happening for several months now.

  I became frustrated enough to load up pulseaudio in debugging mode.
  The log shows that when the music player just finishes playing one
  piece, and tries to start the next piece, you see something like this:

  ---
  ( 335.399|  34.388) D: [alsa-sink] sink-input.c: Requesting rewind due to 
corking
  ( 335.400|   0.001) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 
bytes.
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: Limited to 14820 bytes.
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: before: 3705
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: after: 3705
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: Rewound 14820 bytes.
  ( 335.400|   0.000) D: [alsa-sink] sink.c: Processing rewind...
  ( 335.400|   0.000) D: [alsa-sink] sink.c: latency = 1643
  ( 335.400|   0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes 
on render memblockq.
  ( 335.400|   0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes 
on implementor.
  ( 335.400|   0.000) D: [alsa-sink] source.c: Processing rewind...
  ( 335.400|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds.
  ( 335.402|   0.001) D: [alsa-sink] alsa-sink.c: hwbuf_unused=0
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15502
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Requested volume: 0:  34% 1:  
34%
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:in dB: 0: -28.11 
dB 1: -28.11 dB
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Got hardware volume: 0:  34% 
1:  34%
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:   in dB: 0: 
-28.00 dB 1: -28.00 dB
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Calculated software volume: 
0: 100% 1: 100% (accurate-enough=yes)
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:  in dB: 
0: -0.11 dB 1: -0.11 dB
  ( 335.402|   0.000) D: [alsa-sink] sink.c: Volume not changing
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 
bytes.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Limited to 15300 bytes.
  ( 335.402|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: before: 3825
  ( 335.402|   0.000) D: [pulseaudio] core.c: Hmm, no streams around, trying to 
vacuum.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: after: 3825
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Rewound 15300 bytes.
  ( 335.402|   0.000) D: [alsa-sink] sink.c: Processing rewind...
  ( 335.402|   0.000) D: [alsa-sink] sink.c: latency = 1402
  ( 335.402|   0.000) D: [alsa-sink] source.c: Processing rewind...
  ( 335.402|   0.000) I: [pulseaudio] sink-input.c: Freeing input 3 
"'zero-project - 05 - Forest of the unicorns' by 'zero-project'"
  ( 335.402|   0.000) D: [pulseaudio] module-stream-restore.c: Not restoring 
device for stream sink-input-by-media-role:music, because already set to 
'alsa_output.pci-_00_1b.0.analog-stereo'.
  ( 335.403|   0.000) D: [pulseaudio] module-intended-roles.c: Not setting 
device for stream Playback Stream, because already set.
  ( 335.403|   0.000) I: [pulseaudio] module-stream-restore.c: Restoring volume 
for sink input sink-input-by-media-role:music.
  ( 335.403|   0.000) I: [pulseaudio] 

[Touch-packages] [Bug 1603295] Re: Minimise animation goes to/from the middle of the launcher instead of the icon location

[Daniel van Vugt]

** Tags added: visual-quality

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

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

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

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

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

Title:
  Minimise animation goes to/from the middle of the launcher instead of
  the icon location

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

Bug description:
  Minimise animation goes to/from the middle of the launcher instead of
  the icon location

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

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

[Touch-packages] [Bug 1204505] Re: [enhancement] unity-system-compositor needs to have hw pointer functionality enabled back

[Daniel van Vugt]

This may well have been Fix Released in the past, but now the opposite
is true.

See bug 1600220 for the latest status.

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

Title:
  [enhancement] unity-system-compositor needs to have hw pointer
  functionality enabled back

Status in Unity System Compositor:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Fix Released

Bug description:
  Right now, unity-system-compositor disable hw pointer in Mir through:
  unity-compositor-command=unity-system-compositor --enable-input=false

  This was to workaround an issue with some ati cards that we
  encountered: https://bugs.launchpad.net/mir/+bug/1203070

  Prerequisite fix: bug 1206780

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1204505/+subscriptions

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

[Touch-packages] [Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode

[Anastasia]

** Changed in: juju
Milestone: 2.2-beta2 => 2.2-beta3

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

Title:
  MachineSuite.TestMachineWorkers timed out waiting for workers zesty
  because dbus is in interactive mode

Status in juju:
  Triaged
Status in juju 2.1 series:
  Won't Fix
Status in dbus package in Ubuntu:
  New

Bug description:
  As seen at
  http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e

  A unit test is exclusively failing on our new zesty machine. the
  previous issues is not related to the zesty falures

  machine-0: has workers [agent api-address-updater api-caller 
api-config-watcher disk-manager log-forwarder log-sender logging-config-updater 
machine-action-runner machiner migration-fortress migration-inactive-flag 
migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater 
state-config-watcher storage-provisioner termination-signal-handler 
unconverted-api-workers upgrade-check-flag upgrade-check-gate 
upgrade-steps-flag upgrade-steps-gate upgrader]
  machine-0: waiting for [unit-agent-deployer]
  machine-0: unexpected []
  machine-0: report: 
  {}

  
  machine_test.go:1272:
  WaitMatch(c, matcher.Check, coretesting.LongWait, 
s.BackingState.StartSync)
  engine_test.go:234:
  c.Fatalf("timed out waiting for workers")
  ... Error: timed out waiting for workers

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

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

[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

[Mercury]

After two and a half weeks, can we please get a build of resolvconf with
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
applied pushed out?

We don't even need the full new release of resolvconf, we just need the
documented bug (https://bugzilla.redhat.com/show_bug.cgi?id=1373485)
patched.

This was covered in detail in https://bugs.launchpad.net/ubuntu/+source
/network-manager/+bug/1672491 and while it won't fix some of my use
cases, it will at least get a large number of the VPN users working
again.

Regards,
Zephaniah E. Loss-Cutler-Hull.

** Bug watch added: Red Hat Bugzilla #1373485
   https://bugzilla.redhat.com/show_bug.cgi?id=1373485

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1557634] Re: Unity8/Mir server crashes when given an invalid keymap

[Launchpad Bug Tracker]

This bug was fixed in the package qtmir - 0.5.1+17.04.20170328-0ubuntu1

---
qtmir (0.5.1+17.04.20170328-0ubuntu1) zesty; urgency=medium

  [ Alan Griffiths ]
  * MirAL will be correcting another spelling error shortly. Avoid an
FTBFS when that happens.
  * Compatibility with lp:mir and lp:~alan-griffiths/miral/1.3

  [ Albert Astals Cid ]
  * Remove empty property and move invokable
  * Run ApplicationManager::authorizeSession in the calling thread (LP:
#1525285)

  [ Andreas Pokorny ]
  * Report and consume exception that may occur on constructing a keymap
(LP: #1557634)

  [ Daniel d'Andrada ]
  * Ensure the window that got a key down also gets the corresponding
key up (LP: #1671072)

  [ Gerry Boland ]
  * Don't let a child window go offscreen because its parent moved
  * Add env var equivalent to desktop_file_hint

  [ Lukáš Tinkl ]
  * Raise (activate) windows when an app focus is requested (LP:
#1672337)

 -- Michał Sawicz   Tue, 28 Mar 2017
17:14:50 +

** Changed in: qtmir (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 mir in Ubuntu.
https://bugs.launchpad.net/bugs/1557634

Title:
  Unity8/Mir server crashes when given an invalid keymap

Status in Canonical System Image:
  In Progress
Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/4b8d65fc943d9604a00af4439b24bf85ddc6d1a7

  I foolishly tested unity8's keymap switching with the keymap "zh" (I
  should have used "cn").

  But I noticed that libmirclient crashed when I switched to "zh".
  While this isn't a supported use case, we shouldn't crash.

  Here's a non-debugful stack trace:

  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  (gdb) bt
  #0  0xb61379a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
  #1  0xb614562e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
  #2  0xb6146332 in abort () from /lib/arm-linux-gnueabihf/libc.so.6
  #3  0xb6283120 in __gnu_cxx::__verbose_terminate_handler() ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #4  0xb6281950 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #5  0xb62819a6 in std::terminate() ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #6  0xb6281bc6 in __cxa_throw ()
     from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  #7  0xb3d726ec in ?? () from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #8  0xb3d857f2 in 
mir::events::make_event(mir::IntWrapper const&, long long, std::string const&, std::string const&, std::string 
const&, std::string const&) ()
     from /usr/lib/arm-linux-gnueabihf/libmirclient.so.9
  #9  0xb3e3e5e2 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #10 0xb3e24d1e in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #11 0xb3e2aeb0 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #12 0xb3e26870 in ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.38
  #13 0xaa6476ce in qtmir::MirSurface::setKeymap(QString const&, QString const&)

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

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

[Touch-packages] [Bug 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed

[gato171]

Was getting crazy with this.
This worked for me: 
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/comments/14
Thanks Ed!

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

Title:
  cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be
  installed

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This is related to this bug
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790

  After `sudo apt-get -f install`, it removed cups and marked a bunch of
  cups packages as unnecessary

  `sudo apt-get autoremove` removed them.

  Now when I try to re-install cups, I get this error:

  ```
  ☀  sudo apt-get install cups cups-daemon cups-core-drivers
  Mod master
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
  Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed
  Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed
  Recommends: printer-driver-gutenprint but it is not going to be 
installed
   cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to 
be installed
   cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be 
installed
 Depends: libcupsmime1 (>= 1.5.0) but it is not going to be 
installed
 Recommends: cups-browsed but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  ```

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

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

[Touch-packages] [Bug 1671458] Re: Unity8 window restore animation goes to an old location, then jumps to the correct one

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170328.3-0ubuntu1

---
unity8 (8.15+17.04.20170328.3-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * mock: Remove empty property and move invokable
  * Tune quicklist item selection
  * Fix unminimizing going to the wrong position the second time (LP:
#1671458)
  * Remove unclickable gaps on the menubar (LP: #1672722)
  * indicators client is a tool
  * Make sure we destroy the popups when the item goes away (LP:
#1670338)
  * UnityApplicationMocks: Initialize m_state and m_requestedState
  * Don't use appInfo after checking it if is null
  * Initialize m_privateMode
  * Hook up aboutToShow for overflow menus (LP: #1676016)

  [ Daniel d'Andrada ]
  * Give active focus to child surface qml items (LP: #1671072)
  * Satellite child windows (LP: #1673415)
  * Tell qtmir/miral about the available desktop area

  [ Florian Boucault ]
  * WindowStateStorage: use a private QThreadPool to ensure that
WindowStateStorage::saveValue always has a thread available to
execute the query in. (LP: #1675424)

  [ Lukáš Tinkl ]
  * Protect against loading invalid window geometry (LP: #1674262)
  * Remove usage of the deprecated (and non-functional) system-image-
dbus service.
  * Implement Ctrl+Alt+T to launch the terminal app (LP: #1673500)
  * Only take normal and dialog surface types into account for launcher
items (LP: #1669047)
  * Fix the shutdown dialog after recent refactoring in
DBusUnitySessionService (LP: #1676426)

  [ Michael Zanetti ]
  * drop the grey background behind icons in the drawer (LP: #1675688)

  [ Pete Woods ]
  * Fix Unity/Platform::isPC, and add tests (LP: #1670657)

 -- Michał Sawicz   Tue, 28 Mar 2017
21:50:20 +

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

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

Title:
  Unity8 window restore animation goes to an old location, then jumps to
  the correct one

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

Bug description:
  ubuntu 17.04 unity8
  [unity8] minimizing/restoring strange behaviour 

  on restoring the animation is jumpy it goes trough 2 paths, first
  minimized position and then to the actual position.

  open some random app, minimize, click on the icon (launcher) to
  restore. works fine. now move the window a bit, minimize, restore, now
  the animation is broken. first it goes to the first min pos and then
  jumps to the actual pos. repeat

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

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

[Touch-packages] [Bug 1671072] Re: Child windows don't get focused

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170328.3-0ubuntu1

---
unity8 (8.15+17.04.20170328.3-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * mock: Remove empty property and move invokable
  * Tune quicklist item selection
  * Fix unminimizing going to the wrong position the second time (LP:
#1671458)
  * Remove unclickable gaps on the menubar (LP: #1672722)
  * indicators client is a tool
  * Make sure we destroy the popups when the item goes away (LP:
#1670338)
  * UnityApplicationMocks: Initialize m_state and m_requestedState
  * Don't use appInfo after checking it if is null
  * Initialize m_privateMode
  * Hook up aboutToShow for overflow menus (LP: #1676016)

  [ Daniel d'Andrada ]
  * Give active focus to child surface qml items (LP: #1671072)
  * Satellite child windows (LP: #1673415)
  * Tell qtmir/miral about the available desktop area

  [ Florian Boucault ]
  * WindowStateStorage: use a private QThreadPool to ensure that
WindowStateStorage::saveValue always has a thread available to
execute the query in. (LP: #1675424)

  [ Lukáš Tinkl ]
  * Protect against loading invalid window geometry (LP: #1674262)
  * Remove usage of the deprecated (and non-functional) system-image-
dbus service.
  * Implement Ctrl+Alt+T to launch the terminal app (LP: #1673500)
  * Only take normal and dialog surface types into account for launcher
items (LP: #1669047)
  * Fix the shutdown dialog after recent refactoring in
DBusUnitySessionService (LP: #1676426)

  [ Michael Zanetti ]
  * drop the grey background behind icons in the drawer (LP: #1675688)

  [ Pete Woods ]
  * Fix Unity/Platform::isPC, and add tests (LP: #1670657)

 -- Michał Sawicz   Tue, 28 Mar 2017
21:50:20 +

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

** Changed in: qtmir (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 mir in Ubuntu.
https://bugs.launchpad.net/bugs/1671072

Title:
  Child windows don't get focused

Status in Canonical System Image:
  In Progress
Status in Mir:
  Invalid
Status in MirAL:
  Fix Released
Status in mir package in Ubuntu:
  Invalid
Status in miral package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

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

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

[Touch-packages] [Bug 1670338] Re: [unity8] you can break app menus if you open the apps switcher while the menu is open

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170328.3-0ubuntu1

---
unity8 (8.15+17.04.20170328.3-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * mock: Remove empty property and move invokable
  * Tune quicklist item selection
  * Fix unminimizing going to the wrong position the second time (LP:
#1671458)
  * Remove unclickable gaps on the menubar (LP: #1672722)
  * indicators client is a tool
  * Make sure we destroy the popups when the item goes away (LP:
#1670338)
  * UnityApplicationMocks: Initialize m_state and m_requestedState
  * Don't use appInfo after checking it if is null
  * Initialize m_privateMode
  * Hook up aboutToShow for overflow menus (LP: #1676016)

  [ Daniel d'Andrada ]
  * Give active focus to child surface qml items (LP: #1671072)
  * Satellite child windows (LP: #1673415)
  * Tell qtmir/miral about the available desktop area

  [ Florian Boucault ]
  * WindowStateStorage: use a private QThreadPool to ensure that
WindowStateStorage::saveValue always has a thread available to
execute the query in. (LP: #1675424)

  [ Lukáš Tinkl ]
  * Protect against loading invalid window geometry (LP: #1674262)
  * Remove usage of the deprecated (and non-functional) system-image-
dbus service.
  * Implement Ctrl+Alt+T to launch the terminal app (LP: #1673500)
  * Only take normal and dialog surface types into account for launcher
items (LP: #1669047)
  * Fix the shutdown dialog after recent refactoring in
DBusUnitySessionService (LP: #1676426)

  [ Michael Zanetti ]
  * drop the grey background behind icons in the drawer (LP: #1675688)

  [ Pete Woods ]
  * Fix Unity/Platform::isPC, and add tests (LP: #1670657)

 -- Michał Sawicz   Tue, 28 Mar 2017
21:50:20 +

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

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

Title:
  [unity8] you can break app menus if you open the apps switcher while
  the menu is open

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

Bug description:
  ubuntu 17.04 Unity8

  launch Kate and another app, (maximize both apps), click on the main
  menu, open some submenus then with the mouse open the app switcher,
  you'll now see the menu above the app switcher see screenshot1. now
  click on the other app another app (i have qupzilla) and then open the
  menu, now you'll see parts of kate's menu above the other app, see
  sreenshot2

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

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

[Touch-packages] [Bug 1670657] Re: No log out option in session indicator in unity8 in Qemu VM

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170328.3-0ubuntu1

---
unity8 (8.15+17.04.20170328.3-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * mock: Remove empty property and move invokable
  * Tune quicklist item selection
  * Fix unminimizing going to the wrong position the second time (LP:
#1671458)
  * Remove unclickable gaps on the menubar (LP: #1672722)
  * indicators client is a tool
  * Make sure we destroy the popups when the item goes away (LP:
#1670338)
  * UnityApplicationMocks: Initialize m_state and m_requestedState
  * Don't use appInfo after checking it if is null
  * Initialize m_privateMode
  * Hook up aboutToShow for overflow menus (LP: #1676016)

  [ Daniel d'Andrada ]
  * Give active focus to child surface qml items (LP: #1671072)
  * Satellite child windows (LP: #1673415)
  * Tell qtmir/miral about the available desktop area

  [ Florian Boucault ]
  * WindowStateStorage: use a private QThreadPool to ensure that
WindowStateStorage::saveValue always has a thread available to
execute the query in. (LP: #1675424)

  [ Lukáš Tinkl ]
  * Protect against loading invalid window geometry (LP: #1674262)
  * Remove usage of the deprecated (and non-functional) system-image-
dbus service.
  * Implement Ctrl+Alt+T to launch the terminal app (LP: #1673500)
  * Only take normal and dialog surface types into account for launcher
items (LP: #1669047)
  * Fix the shutdown dialog after recent refactoring in
DBusUnitySessionService (LP: #1676426)

  [ Michael Zanetti ]
  * drop the grey background behind icons in the drawer (LP: #1675688)

  [ Pete Woods ]
  * Fix Unity/Platform::isPC, and add tests (LP: #1670657)

 -- Michał Sawicz   Tue, 28 Mar 2017
21:50:20 +

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

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

Title:
  No log out option in session indicator in unity8 in Qemu VM

Status in Canonical System Image:
  In Progress
Status in indicator-session package in Ubuntu:
  In Progress
Status in qmenumodel package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  With a basic VM created with default options in virt-manager on daily
  zesty image.

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

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

[Touch-packages] [Bug 1672722] Re: Unclickable gap between adjacent titlebar menus in Unity8

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170328.3-0ubuntu1

---
unity8 (8.15+17.04.20170328.3-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * mock: Remove empty property and move invokable
  * Tune quicklist item selection
  * Fix unminimizing going to the wrong position the second time (LP:
#1671458)
  * Remove unclickable gaps on the menubar (LP: #1672722)
  * indicators client is a tool
  * Make sure we destroy the popups when the item goes away (LP:
#1670338)
  * UnityApplicationMocks: Initialize m_state and m_requestedState
  * Don't use appInfo after checking it if is null
  * Initialize m_privateMode
  * Hook up aboutToShow for overflow menus (LP: #1676016)

  [ Daniel d'Andrada ]
  * Give active focus to child surface qml items (LP: #1671072)
  * Satellite child windows (LP: #1673415)
  * Tell qtmir/miral about the available desktop area

  [ Florian Boucault ]
  * WindowStateStorage: use a private QThreadPool to ensure that
WindowStateStorage::saveValue always has a thread available to
execute the query in. (LP: #1675424)

  [ Lukáš Tinkl ]
  * Protect against loading invalid window geometry (LP: #1674262)
  * Remove usage of the deprecated (and non-functional) system-image-
dbus service.
  * Implement Ctrl+Alt+T to launch the terminal app (LP: #1673500)
  * Only take normal and dialog surface types into account for launcher
items (LP: #1669047)
  * Fix the shutdown dialog after recent refactoring in
DBusUnitySessionService (LP: #1676426)

  [ Michael Zanetti ]
  * drop the grey background behind icons in the drawer (LP: #1675688)

  [ Pete Woods ]
  * Fix Unity/Platform::isPC, and add tests (LP: #1670657)

 -- Michał Sawicz   Tue, 28 Mar 2017
21:50:20 +

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

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

Title:
  Unclickable gap between adjacent titlebar menus in Unity8

Status in Canonical System Image:
  In Progress
Status in qtubuntu package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 17.04 unity8

  i'm starting to hit more and more the gap in the menu (space between
  the menu strings). clicking there won't open the submenu.

  launch kate native, hover the menu, click on the space between the
  menu strings. should not be such a thing. the space between the
  hitboxes should be 0 so you don't end up in situations like this

  see screenshot

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

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

[Touch-packages] [Bug 1671072] Re: Child windows don't get focused

[Launchpad Bug Tracker]

This bug was fixed in the package qtmir - 0.5.1+17.04.20170328-0ubuntu1

---
qtmir (0.5.1+17.04.20170328-0ubuntu1) zesty; urgency=medium

  [ Alan Griffiths ]
  * MirAL will be correcting another spelling error shortly. Avoid an
FTBFS when that happens.
  * Compatibility with lp:mir and lp:~alan-griffiths/miral/1.3

  [ Albert Astals Cid ]
  * Remove empty property and move invokable
  * Run ApplicationManager::authorizeSession in the calling thread (LP:
#1525285)

  [ Andreas Pokorny ]
  * Report and consume exception that may occur on constructing a keymap
(LP: #1557634)

  [ Daniel d'Andrada ]
  * Ensure the window that got a key down also gets the corresponding
key up (LP: #1671072)

  [ Gerry Boland ]
  * Don't let a child window go offscreen because its parent moved
  * Add env var equivalent to desktop_file_hint

  [ Lukáš Tinkl ]
  * Raise (activate) windows when an app focus is requested (LP:
#1672337)

 -- Michał Sawicz   Tue, 28 Mar 2017
17:14:50 +

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

Title:
  Child windows don't get focused

Status in Canonical System Image:
  In Progress
Status in Mir:
  Invalid
Status in MirAL:
  Fix Released
Status in mir package in Ubuntu:
  Invalid
Status in miral package in Ubuntu:
  Fix Released
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  1. Start Kate
  2. Press Ctrl+O to open the file dialog
  3. Notice the file dialog "appears" to be focused, the cursor in the filename 
text field is blinking but you can't start typing the filename and you can't 
e.g. dismiss the dialog by pressing Esc
  4. Only after you've clicked the filename textfield, you can start typing and 
hit Esc to close
  5. After closing the dialog, you are left with no focused window at all

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

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

[Touch-packages] [Bug 1669047] Re: [Unity8] launcher pips include child windows like menus

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170328.3-0ubuntu1

---
unity8 (8.15+17.04.20170328.3-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * mock: Remove empty property and move invokable
  * Tune quicklist item selection
  * Fix unminimizing going to the wrong position the second time (LP:
#1671458)
  * Remove unclickable gaps on the menubar (LP: #1672722)
  * indicators client is a tool
  * Make sure we destroy the popups when the item goes away (LP:
#1670338)
  * UnityApplicationMocks: Initialize m_state and m_requestedState
  * Don't use appInfo after checking it if is null
  * Initialize m_privateMode
  * Hook up aboutToShow for overflow menus (LP: #1676016)

  [ Daniel d'Andrada ]
  * Give active focus to child surface qml items (LP: #1671072)
  * Satellite child windows (LP: #1673415)
  * Tell qtmir/miral about the available desktop area

  [ Florian Boucault ]
  * WindowStateStorage: use a private QThreadPool to ensure that
WindowStateStorage::saveValue always has a thread available to
execute the query in. (LP: #1675424)

  [ Lukáš Tinkl ]
  * Protect against loading invalid window geometry (LP: #1674262)
  * Remove usage of the deprecated (and non-functional) system-image-
dbus service.
  * Implement Ctrl+Alt+T to launch the terminal app (LP: #1673500)
  * Only take normal and dialog surface types into account for launcher
items (LP: #1669047)
  * Fix the shutdown dialog after recent refactoring in
DBusUnitySessionService (LP: #1676426)

  [ Michael Zanetti ]
  * drop the grey background behind icons in the drawer (LP: #1675688)

  [ Pete Woods ]
  * Fix Unity/Platform::isPC, and add tests (LP: #1670657)

 -- Michał Sawicz   Tue, 28 Mar 2017
21:50:20 +

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

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

Title:
  [Unity8] launcher pips include child windows like menus

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

Bug description:
  ubuntu 17.04 unity8

  the launcher is showing some white dots for every opened
  window/instance of the same app (from what i understand, like unity7),
  but if you open Kate and then right click on document and then open
  then open a submenu now the launcher shows 3 white dots (left side of
  Kate's icon)

  see attached screenshot

  i am not super sure but i think that the launcher is counting menus as
  instances or something

  also not specific to kate, happens with lot of apps (can't tell if bug
  or feature)

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

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

[Touch-packages] [Bug 1672337] Re: [unity8] can't restore an app if you minimize it while a child window, menu or context menu is opened

[Launchpad Bug Tracker]

This bug was fixed in the package qtmir - 0.5.1+17.04.20170328-0ubuntu1

---
qtmir (0.5.1+17.04.20170328-0ubuntu1) zesty; urgency=medium

  [ Alan Griffiths ]
  * MirAL will be correcting another spelling error shortly. Avoid an
FTBFS when that happens.
  * Compatibility with lp:mir and lp:~alan-griffiths/miral/1.3

  [ Albert Astals Cid ]
  * Remove empty property and move invokable
  * Run ApplicationManager::authorizeSession in the calling thread (LP:
#1525285)

  [ Andreas Pokorny ]
  * Report and consume exception that may occur on constructing a keymap
(LP: #1557634)

  [ Daniel d'Andrada ]
  * Ensure the window that got a key down also gets the corresponding
key up (LP: #1671072)

  [ Gerry Boland ]
  * Don't let a child window go offscreen because its parent moved
  * Add env var equivalent to desktop_file_hint

  [ Lukáš Tinkl ]
  * Raise (activate) windows when an app focus is requested (LP:
#1672337)

 -- Michał Sawicz   Tue, 28 Mar 2017
17:14:50 +

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

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

Title:
  [unity8] can't restore an app if you minimize it while a child window,
  menu or context menu is opened

Status in Canonical System Image:
  Triaged
Status in miral package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  ubuntu 17.04 unity8

  [unity8] can't restore an app if you minimize it while a child window,
  menu or context menu is opened

  open whatever app, kate without Xmir, right click to open a context
  menu or just open a child window. minize the app then try to restore
  it by clicking on the icon on the launcher

  doesn't seem to work here

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

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

[Touch-packages] [Bug 1673415] Re: QDockWidgets don't work at all

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170328.3-0ubuntu1

---
unity8 (8.15+17.04.20170328.3-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * mock: Remove empty property and move invokable
  * Tune quicklist item selection
  * Fix unminimizing going to the wrong position the second time (LP:
#1671458)
  * Remove unclickable gaps on the menubar (LP: #1672722)
  * indicators client is a tool
  * Make sure we destroy the popups when the item goes away (LP:
#1670338)
  * UnityApplicationMocks: Initialize m_state and m_requestedState
  * Don't use appInfo after checking it if is null
  * Initialize m_privateMode
  * Hook up aboutToShow for overflow menus (LP: #1676016)

  [ Daniel d'Andrada ]
  * Give active focus to child surface qml items (LP: #1671072)
  * Satellite child windows (LP: #1673415)
  * Tell qtmir/miral about the available desktop area

  [ Florian Boucault ]
  * WindowStateStorage: use a private QThreadPool to ensure that
WindowStateStorage::saveValue always has a thread available to
execute the query in. (LP: #1675424)

  [ Lukáš Tinkl ]
  * Protect against loading invalid window geometry (LP: #1674262)
  * Remove usage of the deprecated (and non-functional) system-image-
dbus service.
  * Implement Ctrl+Alt+T to launch the terminal app (LP: #1673500)
  * Only take normal and dialog surface types into account for launcher
items (LP: #1669047)
  * Fix the shutdown dialog after recent refactoring in
DBusUnitySessionService (LP: #1676426)

  [ Michael Zanetti ]
  * drop the grey background behind icons in the drawer (LP: #1675688)

  [ Pete Woods ]
  * Fix Unity/Platform::isPC, and add tests (LP: #1670657)

 -- Michał Sawicz   Tue, 28 Mar 2017
21:50:20 +

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

Title:
  QDockWidgets don't work at all

Status in qtubuntu package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  How to reproduce:
   * Install tiled
   * Start tiled
   * Press the small square button next to properties
   * That should undock the properties widget, make it a window and you should 
be able to drag it freely around the desktop, that doesn't happen
   * Alternatively, drag the properties widget from the "properties" text, 
you'll be able to drag it, but only inside the window, instead of around the 
desktop, and once you release it, you can't drag it anymore

  To "reset" the docked status, remove
  ~/.config/mapeditor.org/tiled.conf

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

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

[Touch-packages] [Bug 1673500] Re: Ctrl+Alt+T does not bring up a terminal

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170328.3-0ubuntu1

---
unity8 (8.15+17.04.20170328.3-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * mock: Remove empty property and move invokable
  * Tune quicklist item selection
  * Fix unminimizing going to the wrong position the second time (LP:
#1671458)
  * Remove unclickable gaps on the menubar (LP: #1672722)
  * indicators client is a tool
  * Make sure we destroy the popups when the item goes away (LP:
#1670338)
  * UnityApplicationMocks: Initialize m_state and m_requestedState
  * Don't use appInfo after checking it if is null
  * Initialize m_privateMode
  * Hook up aboutToShow for overflow menus (LP: #1676016)

  [ Daniel d'Andrada ]
  * Give active focus to child surface qml items (LP: #1671072)
  * Satellite child windows (LP: #1673415)
  * Tell qtmir/miral about the available desktop area

  [ Florian Boucault ]
  * WindowStateStorage: use a private QThreadPool to ensure that
WindowStateStorage::saveValue always has a thread available to
execute the query in. (LP: #1675424)

  [ Lukáš Tinkl ]
  * Protect against loading invalid window geometry (LP: #1674262)
  * Remove usage of the deprecated (and non-functional) system-image-
dbus service.
  * Implement Ctrl+Alt+T to launch the terminal app (LP: #1673500)
  * Only take normal and dialog surface types into account for launcher
items (LP: #1669047)
  * Fix the shutdown dialog after recent refactoring in
DBusUnitySessionService (LP: #1676426)

  [ Michael Zanetti ]
  * drop the grey background behind icons in the drawer (LP: #1675688)

  [ Pete Woods ]
  * Fix Unity/Platform::isPC, and add tests (LP: #1670657)

 -- Michał Sawicz   Tue, 28 Mar 2017
21:50:20 +

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

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

Title:
  Ctrl+Alt+T does not bring up a terminal

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

Bug description:
  I really miss that keyboard shortcut when using unity8.  In unity7,
  that shortcut would bring up a gnome-terminal window (actual command
  configurable in GNOME gsettings somewhere).

  I guess in unity8, it would bring up a ubuntu-terminal-app window (deb
  or snap).

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

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

[Touch-packages] [Bug 1673415] Re: QDockWidgets don't work at all

[Launchpad Bug Tracker]

This bug was fixed in the package qtubuntu -
0.64+17.04.20170328.1-0ubuntu1

---
qtubuntu (0.64+17.04.20170328.1-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * Remove signal noone uses
  * Honor the menu item visibility (LP: #1675802)

  [ Alberto Aguirre, Arthur Mello ]
  * Remove more uses of deprecated mir apis.

  [ Daniel d'Andrada ]
  * Qt::Tool == mir_window_type_satellite (LP: #1673415)
  * Proper implementation of QPlatformScreen::logicalDpi (LP: #1675572)

  [ Gerry Boland ]
  * BackingStore: is possible for context's QPlatformSurface to be
deleted before backing store is.

 -- Michał Sawicz   Tue, 28 Mar 2017
17:13:20 +

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

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

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

Title:
  QDockWidgets don't work at all

Status in qtubuntu package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  How to reproduce:
   * Install tiled
   * Start tiled
   * Press the small square button next to properties
   * That should undock the properties widget, make it a window and you should 
be able to drag it freely around the desktop, that doesn't happen
   * Alternatively, drag the properties widget from the "properties" text, 
you'll be able to drag it, but only inside the window, instead of around the 
desktop, and once you release it, you can't drag it anymore

  To "reset" the docked status, remove
  ~/.config/mapeditor.org/tiled.conf

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

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

[Touch-packages] [Bug 1675424] Re: Window geometries not saved until unity8 exits when number of CPU cores too low

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170328.3-0ubuntu1

---
unity8 (8.15+17.04.20170328.3-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * mock: Remove empty property and move invokable
  * Tune quicklist item selection
  * Fix unminimizing going to the wrong position the second time (LP:
#1671458)
  * Remove unclickable gaps on the menubar (LP: #1672722)
  * indicators client is a tool
  * Make sure we destroy the popups when the item goes away (LP:
#1670338)
  * UnityApplicationMocks: Initialize m_state and m_requestedState
  * Don't use appInfo after checking it if is null
  * Initialize m_privateMode
  * Hook up aboutToShow for overflow menus (LP: #1676016)

  [ Daniel d'Andrada ]
  * Give active focus to child surface qml items (LP: #1671072)
  * Satellite child windows (LP: #1673415)
  * Tell qtmir/miral about the available desktop area

  [ Florian Boucault ]
  * WindowStateStorage: use a private QThreadPool to ensure that
WindowStateStorage::saveValue always has a thread available to
execute the query in. (LP: #1675424)

  [ Lukáš Tinkl ]
  * Protect against loading invalid window geometry (LP: #1674262)
  * Remove usage of the deprecated (and non-functional) system-image-
dbus service.
  * Implement Ctrl+Alt+T to launch the terminal app (LP: #1673500)
  * Only take normal and dialog surface types into account for launcher
items (LP: #1669047)
  * Fix the shutdown dialog after recent refactoring in
DBusUnitySessionService (LP: #1676426)

  [ Michael Zanetti ]
  * drop the grey background behind icons in the drawer (LP: #1675688)

  [ Pete Woods ]
  * Fix Unity/Platform::isPC, and add tests (LP: #1670657)

 -- Michał Sawicz   Tue, 28 Mar 2017
21:50:20 +

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

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

Title:
  Window geometries not saved until unity8 exits when number of CPU
  cores too low

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

Bug description:
  WindowStateStorage uses QtConcurrent::run with the default QThreadPool
  to write in the SQLite database. But the functions passed are not
  guaranteed to be executed if there is no available thread in the pool.

  Steps to reproduce reliably:
  1. Use a computer (or a VM) with only one CPU core
  2. Start any app
  3. Resize the app window
  4. Close the app
  5. Restart the same app

  Expected result:
  After the app is restarted the window size is back to the size given by the 
user.

  Current result:
  After the app is restarted the window size is the default size.

  However if unity8 is restarted the geometry is then correctly saved to
  DB and correctly restored after the app is launched.

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

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

[Touch-packages] [Bug 1675572] Re: GUI of desktop apps are too big on high-dpi screens

[Launchpad Bug Tracker]

This bug was fixed in the package qtubuntu -
0.64+17.04.20170328.1-0ubuntu1

---
qtubuntu (0.64+17.04.20170328.1-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * Remove signal noone uses
  * Honor the menu item visibility (LP: #1675802)

  [ Alberto Aguirre, Arthur Mello ]
  * Remove more uses of deprecated mir apis.

  [ Daniel d'Andrada ]
  * Qt::Tool == mir_window_type_satellite (LP: #1673415)
  * Proper implementation of QPlatformScreen::logicalDpi (LP: #1675572)

  [ Gerry Boland ]
  * BackingStore: is possible for context's QPlatformSurface to be
deleted before backing store is.

 -- Michał Sawicz   Tue, 28 Mar 2017
17:13:20 +

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

Title:
  GUI of desktop apps are too big on high-dpi screens

Status in Canonical System Image:
  In Progress
Status in qtubuntu package in Ubuntu:
  Fix Released

Bug description:
  On a 13" 1080p display, fonts and UI in general is too big when
  running desktop Qt-based apps like konsole, QtCreator and Kate.

  Strangely, hardcoding logical dpi to 96 in qtubuntu fixes it.

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

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

[Touch-packages] [Bug 1674262] Re: Windows are not sized correctly if an invalid size comes from the state storage.

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170328.3-0ubuntu1

---
unity8 (8.15+17.04.20170328.3-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * mock: Remove empty property and move invokable
  * Tune quicklist item selection
  * Fix unminimizing going to the wrong position the second time (LP:
#1671458)
  * Remove unclickable gaps on the menubar (LP: #1672722)
  * indicators client is a tool
  * Make sure we destroy the popups when the item goes away (LP:
#1670338)
  * UnityApplicationMocks: Initialize m_state and m_requestedState
  * Don't use appInfo after checking it if is null
  * Initialize m_privateMode
  * Hook up aboutToShow for overflow menus (LP: #1676016)

  [ Daniel d'Andrada ]
  * Give active focus to child surface qml items (LP: #1671072)
  * Satellite child windows (LP: #1673415)
  * Tell qtmir/miral about the available desktop area

  [ Florian Boucault ]
  * WindowStateStorage: use a private QThreadPool to ensure that
WindowStateStorage::saveValue always has a thread available to
execute the query in. (LP: #1675424)

  [ Lukáš Tinkl ]
  * Protect against loading invalid window geometry (LP: #1674262)
  * Remove usage of the deprecated (and non-functional) system-image-
dbus service.
  * Implement Ctrl+Alt+T to launch the terminal app (LP: #1673500)
  * Only take normal and dialog surface types into account for launcher
items (LP: #1669047)
  * Fix the shutdown dialog after recent refactoring in
DBusUnitySessionService (LP: #1676426)

  [ Michael Zanetti ]
  * drop the grey background behind icons in the drawer (LP: #1675688)

  [ Pete Woods ]
  * Fix Unity/Platform::isPC, and add tests (LP: #1670657)

 -- Michał Sawicz   Tue, 28 Mar 2017
21:50:20 +

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

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

Title:
  Windows are not sized correctly if an invalid size comes from the
  state storage.

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

Bug description:
  The width/height of a windowed surface can be 0 if the initial size is
  loaded with 0 due to an invalid state storage size.

  http://paste.ubuntu.com/24195871/

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

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

[Touch-packages] [Bug 1675802] Re: Empty spaces in some (titlebar integrated) menus

[Launchpad Bug Tracker]

This bug was fixed in the package qtubuntu -
0.64+17.04.20170328.1-0ubuntu1

---
qtubuntu (0.64+17.04.20170328.1-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * Remove signal noone uses
  * Honor the menu item visibility (LP: #1675802)

  [ Alberto Aguirre, Arthur Mello ]
  * Remove more uses of deprecated mir apis.

  [ Daniel d'Andrada ]
  * Qt::Tool == mir_window_type_satellite (LP: #1673415)
  * Proper implementation of QPlatformScreen::logicalDpi (LP: #1675572)

  [ Gerry Boland ]
  * BackingStore: is possible for context's QPlatformSurface to be
deleted before backing store is.

 -- Michał Sawicz   Tue, 28 Mar 2017
17:13:20 +

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

Title:
  Empty spaces in some (titlebar integrated) menus

Status in Canonical System Image:
  In Progress
Status in qtubuntu package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 17.04 Unity 8

  empty spaces in some menus, see the attached screenshots (unity8/unity7). 
there is tiled a qt5 app running without Xmir but i've seen the same in other 
qt5 apps (to install tiled, apt install tiled)
  affected is File \ Recent Files (menu), you'll see a big empty space

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

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

[Touch-packages] [Bug 1675688] Re: Legacy app icons look poor/broken inside a rounded grey square

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170328.3-0ubuntu1

---
unity8 (8.15+17.04.20170328.3-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * mock: Remove empty property and move invokable
  * Tune quicklist item selection
  * Fix unminimizing going to the wrong position the second time (LP:
#1671458)
  * Remove unclickable gaps on the menubar (LP: #1672722)
  * indicators client is a tool
  * Make sure we destroy the popups when the item goes away (LP:
#1670338)
  * UnityApplicationMocks: Initialize m_state and m_requestedState
  * Don't use appInfo after checking it if is null
  * Initialize m_privateMode
  * Hook up aboutToShow for overflow menus (LP: #1676016)

  [ Daniel d'Andrada ]
  * Give active focus to child surface qml items (LP: #1671072)
  * Satellite child windows (LP: #1673415)
  * Tell qtmir/miral about the available desktop area

  [ Florian Boucault ]
  * WindowStateStorage: use a private QThreadPool to ensure that
WindowStateStorage::saveValue always has a thread available to
execute the query in. (LP: #1675424)

  [ Lukáš Tinkl ]
  * Protect against loading invalid window geometry (LP: #1674262)
  * Remove usage of the deprecated (and non-functional) system-image-
dbus service.
  * Implement Ctrl+Alt+T to launch the terminal app (LP: #1673500)
  * Only take normal and dialog surface types into account for launcher
items (LP: #1669047)
  * Fix the shutdown dialog after recent refactoring in
DBusUnitySessionService (LP: #1676426)

  [ Michael Zanetti ]
  * drop the grey background behind icons in the drawer (LP: #1675688)

  [ Pete Woods ]
  * Fix Unity/Platform::isPC, and add tests (LP: #1670657)

 -- Michał Sawicz   Tue, 28 Mar 2017
21:50:20 +

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

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

Title:
  Legacy app icons look poor/broken inside a rounded grey square

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Legacy app icons look poor/broken inside a rounded grey square (in the
  app drawer).

  We would achieve a much nicer appearance without the rounded grey
  squares at all. Not only that, but we'd then have a visual distinction
  between legacy app icons and "modern" Ubuntu Touch apps.

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

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

[Touch-packages] [Bug 1676016] Re: Overflow menus don't work

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170328.3-0ubuntu1

---
unity8 (8.15+17.04.20170328.3-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * mock: Remove empty property and move invokable
  * Tune quicklist item selection
  * Fix unminimizing going to the wrong position the second time (LP:
#1671458)
  * Remove unclickable gaps on the menubar (LP: #1672722)
  * indicators client is a tool
  * Make sure we destroy the popups when the item goes away (LP:
#1670338)
  * UnityApplicationMocks: Initialize m_state and m_requestedState
  * Don't use appInfo after checking it if is null
  * Initialize m_privateMode
  * Hook up aboutToShow for overflow menus (LP: #1676016)

  [ Daniel d'Andrada ]
  * Give active focus to child surface qml items (LP: #1671072)
  * Satellite child windows (LP: #1673415)
  * Tell qtmir/miral about the available desktop area

  [ Florian Boucault ]
  * WindowStateStorage: use a private QThreadPool to ensure that
WindowStateStorage::saveValue always has a thread available to
execute the query in. (LP: #1675424)

  [ Lukáš Tinkl ]
  * Protect against loading invalid window geometry (LP: #1674262)
  * Remove usage of the deprecated (and non-functional) system-image-
dbus service.
  * Implement Ctrl+Alt+T to launch the terminal app (LP: #1673500)
  * Only take normal and dialog surface types into account for launcher
items (LP: #1669047)
  * Fix the shutdown dialog after recent refactoring in
DBusUnitySessionService (LP: #1676426)

  [ Michael Zanetti ]
  * drop the grey background behind icons in the drawer (LP: #1675688)

  [ Pete Woods ]
  * Fix Unity/Platform::isPC, and add tests (LP: #1670657)

 -- Michał Sawicz   Tue, 28 Mar 2017
21:50:20 +

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

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

Title:
  Overflow menus don't work

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

Bug description:
  Ubuntu 17.04 unity8

  the menu doesn't work if the window is smaller
  launch kate (without Xmir), resize the window until the menu is wider than 
the window (you'll see a down arrow that will expand the menu if pressed) see 
screenshot
  now try to open the expanded menu/submenus see screenshot

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

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

[Touch-packages] [Bug 1676426] Re: "Shut down" option shows the Lock/Log out dialog

[Launchpad Bug Tracker]

This bug was fixed in the package unity8 -
8.15+17.04.20170328.3-0ubuntu1

---
unity8 (8.15+17.04.20170328.3-0ubuntu1) zesty; urgency=medium

  [ Albert Astals Cid ]
  * mock: Remove empty property and move invokable
  * Tune quicklist item selection
  * Fix unminimizing going to the wrong position the second time (LP:
#1671458)
  * Remove unclickable gaps on the menubar (LP: #1672722)
  * indicators client is a tool
  * Make sure we destroy the popups when the item goes away (LP:
#1670338)
  * UnityApplicationMocks: Initialize m_state and m_requestedState
  * Don't use appInfo after checking it if is null
  * Initialize m_privateMode
  * Hook up aboutToShow for overflow menus (LP: #1676016)

  [ Daniel d'Andrada ]
  * Give active focus to child surface qml items (LP: #1671072)
  * Satellite child windows (LP: #1673415)
  * Tell qtmir/miral about the available desktop area

  [ Florian Boucault ]
  * WindowStateStorage: use a private QThreadPool to ensure that
WindowStateStorage::saveValue always has a thread available to
execute the query in. (LP: #1675424)

  [ Lukáš Tinkl ]
  * Protect against loading invalid window geometry (LP: #1674262)
  * Remove usage of the deprecated (and non-functional) system-image-
dbus service.
  * Implement Ctrl+Alt+T to launch the terminal app (LP: #1673500)
  * Only take normal and dialog surface types into account for launcher
items (LP: #1669047)
  * Fix the shutdown dialog after recent refactoring in
DBusUnitySessionService (LP: #1676426)

  [ Michael Zanetti ]
  * drop the grey background behind icons in the drawer (LP: #1675688)

  [ Pete Woods ]
  * Fix Unity/Platform::isPC, and add tests (LP: #1670657)

 -- Michał Sawicz   Tue, 28 Mar 2017
21:50:20 +

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

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

Title:
  "Shut down" option shows the Lock/Log out dialog

Status in Canonical System Image:
  In Progress
Status in indicator-session package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  Session menu → Shut down - shows Log out / Lock dialog instead of Shut
  down / Restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170321-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 27 15:06:43 2017
  InstallationDate: Installed on 2016-05-06 (324 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (124 days ago)

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

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

[Touch-packages] [Bug 1677934] [NEW] package libnss3 2:3.26.2-0ubuntu0.16.04.2 [modified: usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade: tentative de remplacement de « /usr/shar

[Robin]

Public bug reported:

I would install a package and I have this problem.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libnss3 2:3.26.2-0ubuntu0.16.04.2 [modified: 
usr/share/doc/libnss3/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.8.0-45.48~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
 libnss3: Install
 libnss3: Configure
 libnss3: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Mar 31 02:45:46 2017
ErrorMessage: tentative de remplacement de « 
/usr/share/doc/libnss3/changelog.Debian.gz », qui est différent d'autres 
instances du paquet libnss3:i386
InstallationDate: Installed on 2017-03-08 (22 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: nss
Title: package libnss3 2:3.26.2-0ubuntu0.16.04.2 [modified: 
usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade: tentative 
de remplacement de « /usr/share/doc/libnss3/changelog.Debian.gz », qui est 
différent d'autres instances du paquet libnss3:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libnss3 2:3.26.2-0ubuntu0.16.04.2 [modified:
  usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade:
  tentative de remplacement de «
  /usr/share/doc/libnss3/changelog.Debian.gz », qui est différent
  d'autres instances du paquet libnss3:i386

Status in nss package in Ubuntu:
  New

Bug description:
  I would install a package and I have this problem.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libnss3 2:3.26.2-0ubuntu0.16.04.2 [modified: 
usr/share/doc/libnss3/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.8.0-45.48~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   libnss3: Install
   libnss3: Configure
   libnss3: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Mar 31 02:45:46 2017
  ErrorMessage: tentative de remplacement de « 
/usr/share/doc/libnss3/changelog.Debian.gz », qui est différent d'autres 
instances du paquet libnss3:i386
  InstallationDate: Installed on 2017-03-08 (22 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: nss
  Title: package libnss3 2:3.26.2-0ubuntu0.16.04.2 [modified: 
usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade: tentative 
de remplacement de « /usr/share/doc/libnss3/changelog.Debian.gz », qui est 
différent d'autres instances du paquet libnss3:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1675163] Re: Don't attempt to create devices in LXC containers

[rahmadani]

** Changed in: makedev (Ubuntu Precise)
 Assignee: (unassigned) => rahmadani (rahmadani)

** Changed in: makedev (Ubuntu Trusty)
 Assignee: (unassigned) => rahmadani (rahmadani)

** Changed in: makedev (Ubuntu Xenial)
 Assignee: (unassigned) => rahmadani (rahmadani)

** Changed in: makedev (Ubuntu Yakkety)
 Assignee: (unassigned) => rahmadani (rahmadani)

** Changed in: makedev (Ubuntu Zesty)
 Assignee: (unassigned) => rahmadani (rahmadani)

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

Title:
  Don't attempt to create devices in LXC containers

Status in makedev package in Ubuntu:
  Fix Released
Status in makedev source package in Precise:
  Fix Released
Status in makedev source package in Trusty:
  Fix Released
Status in makedev source package in Xenial:
  Fix Released
Status in makedev source package in Yakkety:
  Fix Released
Status in makedev source package in Zesty:
  Fix Released

Bug description:
  Right now the "makedev" postinst script will attempt to create a
  number of devices in /dev, failing the package upgrade should any of
  those mknod calls fail.

  LXC containers, especially unprivileged ones do not allow the use of
  mknod, making it impossible to upgrade makedev in those containers and
  preventing Ubuntu release upgrades.

  The fix is quite simple, detect that we are running in an LXC
  container and skip the rest of the postinst script as is done in a
  number of other cases.

  = SRU
  == Rationale
  This issue prevents release to release upgrades in unprivileged LXC 
containers when makedev is part of the upgraded set. This is currently visible 
when upgrading from Ubuntu 12.04 to Ubuntu 14.04.

  == Testcase
  Install the new package in an unprivileged container. With LXD, simply use 
"lxc launch ubuntu: test" to create the container.

  Prior to this fix, the upgrade will fail on some mknod errors, after
  it, it'll go on after printing a message indicating that LXC was
  detected.

  == Regression potential
  The detection logic is based on PID 1's environment containing a 
container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the 
makedev upgrade no longer creating extra devices. This is unlikely to really 
matter though since the system is clearly already functioning properly at that 
point.

  Similarly, some privileged LXC containers can be configured in a way
  where mknod is possible, this update will still disable the postinst
  for those cases as short of attempting every mknod ahead of time,
  there is no reliable way to detect any seccomp or apparmor policy in
  play.

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

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

[Touch-packages] [Bug 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed

[mike]

Guys, just send a new update so that everyone can fix the dependencies
hell by simply upgrading.

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

Title:
  cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be
  installed

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This is related to this bug
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790

  After `sudo apt-get -f install`, it removed cups and marked a bunch of
  cups packages as unnecessary

  `sudo apt-get autoremove` removed them.

  Now when I try to re-install cups, I get this error:

  ```
  ☀  sudo apt-get install cups cups-daemon cups-core-drivers
  Mod master
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
  Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed
  Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed
  Recommends: printer-driver-gutenprint but it is not going to be 
installed
   cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to 
be installed
   cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be 
installed
 Depends: libcupsmime1 (>= 1.5.0) but it is not going to be 
installed
 Recommends: cups-browsed but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  ```

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

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

[Touch-packages] [Bug 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed

[Till Kamppeter]

Do

sudo dpkg -P --force-depends libcups2 cups-bsd cups-client cups-daemon
libcups2:i386 libcupscgi1 libcupsmime1 libcupsimage2 libcupsppdc1 cups

then

sudo apt-get install -f

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

Title:
  cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be
  installed

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This is related to this bug
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790

  After `sudo apt-get -f install`, it removed cups and marked a bunch of
  cups packages as unnecessary

  `sudo apt-get autoremove` removed them.

  Now when I try to re-install cups, I get this error:

  ```
  ☀  sudo apt-get install cups cups-daemon cups-core-drivers
  Mod master
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
  Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed
  Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed
  Recommends: printer-driver-gutenprint but it is not going to be 
installed
   cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to 
be installed
   cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be 
installed
 Depends: libcupsmime1 (>= 1.5.0) but it is not going to be 
installed
 Recommends: cups-browsed but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  ```

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

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

[Touch-packages] [Bug 1677927] Re: got a systemd bug

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

Title:
  got a systemd bug

Status in systemd package in Ubuntu:
  New

Bug description:
  somehow there was no summary and so I typed in this detail. Hope the
  logs are still attached. I hope this helps.

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar 29 08:43:34 2017
  DuplicateSignature: /lib/systemd/systemd:indicator-session-unknown-user-error
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2017-02-25 (33 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170224)
  ProcCmdline: /lib/systemd/systemd --user
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=bec65355-c6fd-4b16-8f93-406689e8c6fd ro quiet splash 
acpi_backlight=vendor radeon.dpm=1 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/15/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Wasp_BR
  dmi.board.vendor: Acer
  dmi.board.version: V1.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.13:bd11/15/2016:svnAcer:pn:pvrV1.13:rvnAcer:rnWasp_BR:rvrV1.13:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.version: V1.13
  dmi.sys.vendor: Acer
  icon_file: (null)
  is_current_user: true
  is_logged_in: false
  real_name: (null)
  uid: 0
  user_name: (null)

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

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

[Touch-packages] [Bug 1677927] [NEW] got a systemd bug

[aveem ashfaq]

Public bug reported:

somehow there was no summary and so I typed in this detail. Hope the
logs are still attached. I hope this helps.

ProblemType: RecoverableProblem
DistroRelease: Ubuntu 17.04
Package: systemd 232-19
ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
Uname: Linux 4.10.0-13-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Wed Mar 29 08:43:34 2017
DuplicateSignature: /lib/systemd/systemd:indicator-session-unknown-user-error
ExecutablePath: /lib/systemd/systemd
InstallationDate: Installed on 2017-02-25 (33 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170224)
ProcCmdline: /lib/systemd/systemd --user
ProcEnviron:
 LANG=en_IN
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 SHELL=/bin/false
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=bec65355-c6fd-4b16-8f93-406689e8c6fd ro quiet splash 
acpi_backlight=vendor radeon.dpm=1 vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 11/15/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.13
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Wasp_BR
dmi.board.vendor: Acer
dmi.board.version: V1.13
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.13:bd11/15/2016:svnAcer:pn:pvrV1.13:rvnAcer:rnWasp_BR:rvrV1.13:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.version: V1.13
dmi.sys.vendor: Acer
icon_file: (null)
is_current_user: true
is_logged_in: false
real_name: (null)
uid: 0
user_name: (null)

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


** Tags: amd64 apport-recoverableproblem zesty

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

Title:
  got a systemd bug

Status in systemd package in Ubuntu:
  New

Bug description:
  somehow there was no summary and so I typed in this detail. Hope the
  logs are still attached. I hope this helps.

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar 29 08:43:34 2017
  DuplicateSignature: /lib/systemd/systemd:indicator-session-unknown-user-error
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2017-02-25 (33 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170224)
  ProcCmdline: /lib/systemd/systemd --user
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=bec65355-c6fd-4b16-8f93-406689e8c6fd ro quiet splash 
acpi_backlight=vendor radeon.dpm=1 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/15/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Wasp_BR
  dmi.board.vendor: Acer
  dmi.board.version: V1.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.13:bd11/15/2016:svnAcer:pn:pvrV1.13:rvnAcer:rnWasp_BR:rvrV1.13:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.version: V1.13
  dmi.sys.vendor: Acer
  icon_file: (null)
  is_current_user: true
  is_logged_in: false
  real_name: (null)
  uid: 0
  user_name: (null)

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

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

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

[Brian Murray]

Hello Pauli, or anyone else affected,

Accepted dnsmasq into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dnsmasq/2.75-1ubuntu0.16.04.2 in a
few hours, and then in the -proposed repository.

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

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

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

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

Title:
  dnsmasq fails to send queries out after suspend disconnects the
  interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  Fix Committed
Status in dnsmasq source package in Yakkety:
  Fix Committed
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface

[Brian Murray]

Hello Pauli, or anyone else affected,

Accepted dnsmasq into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/dnsmasq/2.76-4ubuntu0.1 in a few
hours, and then in the -proposed repository.

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

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

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

** Changed in: dnsmasq (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

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

Title:
  dnsmasq fails to send queries out after suspend disconnects the
  interface

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Xenial:
  Fix Committed
Status in dnsmasq source package in Yakkety:
  Fix Committed
Status in dnsmasq package in Debian:
  Fix Released

Bug description:
  [Impact]

   * suspend/resume (which involves disconnection of network devices)
  leads to dnsmasq failures.

  [Test Case]

   * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
  failures upon resume.

  [Regression Potential]

   * The fix was NMU'd in Debian in the version immediately after
  16.10's. I believe the regression potential is very low as this is a
  clear bug-fix from upstream.

  ---

  Failure is caused by ENODEV return for all dns queries like:
  sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 
0, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)

  Problem is reported and fixed:
  https://bugzilla.redhat.com/show_bug.cgi?id=1367772

  
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b

  I didn't yet test if applying that patch to ubuntu package works. I
  will try the patch in a few hours.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq-base 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  7 14:11:51 2016
  InstallationDate: Installed on 2037-12-25 (-7718 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)

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

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

[Touch-packages] [Bug 1677904] Re: crash

[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 address-book-app in
Ubuntu.
https://bugs.launchpad.net/bugs/1677904

Title:
  crash

Status in address-book-app package in Ubuntu:
  New

Bug description:

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 17.04
  Package: address-book-app 0.2+17.04.20161219-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  BadURL: tel:(234)%20234-234
  CurrentDesktop: Unity:Unity8
  Date: Fri Mar 31 01:33:40 2017
  DuplicateSignature: /usr/bin/address-book-app:url-dispatcher-bad-url
  ExecutablePath: /usr/bin/address-book-app
  InstallationDate: Installed on 2016-12-12 (108 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  ProcCmdline: address-book-app
  SourcePackage: address-book-app
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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

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

[Brian Murray]

Hello bugproxy, or anyone else affected,

Accepted multipath-tools into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/multipath-
tools/0.5.0+git1.656f8865-5ubuntu2.5 in a few hours, and then in the
-proposed repository.

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

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

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

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in multipath-tools package in Ubuntu:
  Fix Released
Status in hw-detect source package in Xenial:
  In Progress
Status in initramfs-tools source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in multipath-tools source package in Xenial:
  Fix Committed
Status in hw-detect source package in Yakkety:
  In Progress
Status in initramfs-tools source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Committed
Status in multipath-tools source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+subscriptions

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

[Touch-packages] [Bug 1673350] Re: dm-queue-length module is not included in installer/initramfs

[Brian Murray]

Hello bugproxy, or anyone else affected,

Accepted multipath-tools into yakkety-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/multipath-
tools/0.5.0+git1.656f8865-5ubuntu7.3 in a few hours, and then in the
-proposed repository.

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

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

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

** Changed in: multipath-tools (Ubuntu Yakkety)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

** Changed in: multipath-tools (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in multipath-tools package in Ubuntu:
  Fix Released
Status in hw-detect source package in Xenial:
  In Progress
Status in initramfs-tools source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Committed
Status in multipath-tools source package in Xenial:
  Fix Committed
Status in hw-detect source package in Yakkety:
  In Progress
Status in initramfs-tools source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Committed
Status in multipath-tools source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

To manage notifications about this bug go 

[Touch-packages] [Bug 1677904] [NEW] crash

[dinamic]

Public bug reported:


ProblemType: RecoverableProblem
DistroRelease: Ubuntu 17.04
Package: address-book-app 0.2+17.04.20161219-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
Uname: Linux 4.10.0-15-generic x86_64
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
BadURL: tel:(234)%20234-234
CurrentDesktop: Unity:Unity8
Date: Fri Mar 31 01:33:40 2017
DuplicateSignature: /usr/bin/address-book-app:url-dispatcher-bad-url
ExecutablePath: /usr/bin/address-book-app
InstallationDate: Installed on 2016-12-12 (108 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
ProcCmdline: address-book-app
SourcePackage: address-book-app
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

** Affects: address-book-app (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-recoverableproblem third-party-packages zesty

** Description changed:

- synfigstudio crashed with SIGABRT
  
  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 17.04
  Package: address-book-app 0.2+17.04.20161219-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  BadURL: tel:(234)%20234-234
  CurrentDesktop: Unity:Unity8
  Date: Fri Mar 31 01:33:40 2017
  DuplicateSignature: /usr/bin/address-book-app:url-dispatcher-bad-url
  ExecutablePath: /usr/bin/address-book-app
  InstallationDate: Installed on 2016-12-12 (108 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  ProcCmdline: address-book-app
  SourcePackage: address-book-app
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

Title:
  crash

Status in address-book-app package in Ubuntu:
  New

Bug description:

  ProblemType: RecoverableProblem
  DistroRelease: Ubuntu 17.04
  Package: address-book-app 0.2+17.04.20161219-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  BadURL: tel:(234)%20234-234
  CurrentDesktop: Unity:Unity8
  Date: Fri Mar 31 01:33:40 2017
  DuplicateSignature: /usr/bin/address-book-app:url-dispatcher-bad-url
  ExecutablePath: /usr/bin/address-book-app
  InstallationDate: Installed on 2016-12-12 (108 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  ProcCmdline: address-book-app
  SourcePackage: address-book-app
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed

[Nick Stoughton]

Till:

$ sudo dpkg -P --force-depends libcups2
dpkg: libcups2:amd64: dependency problems, but removing anyway as you requested:
 openjdk-8-jre-headless:amd64 depends on libcups2.
 libsane-hpaio:amd64 depends on libcups2 (>= 1.6.0).
 libcupscgi1:amd64 depends on libcups2 (= 2.1.3-4ubuntu0.2).
 printer-driver-ptouch depends on libcups2 (>= 1.4.0).
 cups-client depends on libcups2 (= 2.1.3-4ubuntu0.2).
 libgs9:amd64 depends on libcups2 (>= 1.4.0).
 google-chrome-stable depends on libcups2 (>= 1.4.0).
 printer-driver-c2esp depends on libcups2 (>= 1.4.0).
 cups-filters-core-drivers depends on libcups2 (>= 1.7.0).
 printer-driver-foo2zjs depends on libcups2 (>= 1.4.0).
 cups-pk-helper depends on libcups2 (>= 1.6.0).
 cups-bsd depends on libcups2 (= 2.1.3-4ubuntu0.2).
 libcupsimage2:amd64 depends on libcups2 (= 2.1.3-4ubuntu0.2).
 libcupsfilters1:amd64 depends on libcups2 (>= 1.7.0).
 libcupsppdc1:amd64 depends on libcups2 (= 2.1.3-4ubuntu0.2).
 libfreerdp-plugins-standard:amd64 depends on libcups2 (>= 1.4.0).
 libqt5printsupport5:amd64 depends on libcups2 (>= 1.4.0)
(Reading database ... 592347 files and directories currently installed.)
Removing libcups2:amd64 (2.1.3-4ubuntu0.2) ...
Processing triggers for libc-bin (2.23-0ubuntu7) ...
$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... failed.
The following packages have unmet dependencies:
 chromium-browser : Depends: libcups2 (>= 1.4.0) but it is not installed
 cups-browsed : Depends: libcups2 (>= 1.7.0) but it is not installed
 cups-bsd : Depends: libcups2 (= 2.1.3-4ubuntu0.2) but it is not installed
 cups-client : Depends: libcups2 (= 2.1.3-4ubuntu0.2) but it is not installed
 cups-daemon : Depends: libcups2 (= 2.1.3-4ubuntu0.2) but it is not installed
 cups-filters : Depends: libcups2 (>= 1.7.0) but it is not installed
 cups-filters-core-drivers : Depends: libcups2 (>= 1.7.0) but it is not 
installed
 cups-pk-helper : Depends: libcups2 (>= 1.6.0) but it is not installed
 cups-ppdc : Depends: libcups2 (>= 1.6.2) but it is not installed
 gnome-control-center : Depends: libcups2 (>= 1.6.0) but it is not installed
 gnome-settings-daemon : Depends: libcups2 (>= 1.6.0) but it is not installed
 google-chrome-stable : Depends: libcups2 (>= 1.4.0) but it is not installed
 libcupscgi1 : Depends: libcups2 (= 2.1.3-4ubuntu0.2) but it is not installed
 libcupsfilters1 : Depends: libcups2 (>= 1.7.0) but it is not installed
 libcupsimage2 : Depends: libcups2 (= 2.1.3-4ubuntu0.2) but it is not installed
 libcupsmime1 : Depends: libcups2 (= 2.1.3-4ubuntu0.2) but it is not installed
 libcupsppdc1 : Depends: libcups2 (= 2.1.3-4ubuntu0.2) but it is not installed
 libfreerdp-plugins-standard : Depends: libcups2 (>= 1.4.0) but it is not 
installed
 libgs9 : Depends: libcups2 (>= 1.4.0) but it is not installed
 libgtk-3-0 : Depends: libcups2 (>= 1.6.2) but it is not installed
 libgtk2.0-0 : Depends: libcups2 (>= 1.6.2) but it is not installed
 libqt5printsupport5 : Depends: libcups2 (>= 1.4.0) but it is not installed
 libreoffice-core : Depends: libcups2 (>= 1.4.0) but it is not installed
 libsane-hpaio : Depends: libcups2 (>= 1.6.0) but it is not installed
 Recommends: hplip (= 3.16.3+repack0-1) but it is not installed
 openjdk-8-jre-headless : Depends: libcups2 but it is not installed
 printer-driver-c2esp : Depends: libcups2 (>= 1.4.0) but it is not installed
 printer-driver-foo2zjs : Depends: libcups2 (>= 1.4.0) but it is not installed
  Recommends: cups
 printer-driver-ptouch : Depends: libcups2 (>= 1.4.0) but it is not installed
 python-cups : Depends: libcups2 (>= 1.6.0) but it is not installed
 python3-cups : Depends: libcups2 (>= 1.6.0) but it is not installed
 samba-libs : Depends: libcups2 (>= 1.6.0) but it is not installed
 system-config-printer-udev : Depends: libcups2 (>= 1.6.0) but it is not 
installed
 unity-control-center : Depends: libcups2 (>= 1.6.0) but it is not installed
 unity-settings-daemon : Depends: libcups2 (>= 1.6.0) but it is not installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.
E: Unable to correct dependencies
$ 
$ sudo apt-get install -f libcups2
Reading package lists... Done
Building dependency tree   
Reading state information... Done
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 cups-bsd : Depends: libcups2 (= 2.1.3-4ubuntu0.2) but 2.1.3-4 is to be 
installed
 cups-client : Depends: libcups2 (= 2.1.3-4ubuntu0.2) but 2.1.3-4 is to be 
installed
 cups-daemon : Depends: libcups2 (= 2.1.3-4ubuntu0.2) but 2.1.3-4 is to be 
installed
 libcups2 : Breaks: libcups2:i386 (!= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be 
installed
 libcups2:i386 : Breaks: libcups2 (!= 2.1.3-4ubuntu0.2) but 2.1.3-4 is to be 
installed
 libcupscgi1 : Depends: libcups2 (= 2.1.3-4ubuntu0.2) but 2.1.3-4 is to be 
installed
 

[Touch-packages] [Bug 1677881] [NEW] Missing dep8 tests

[Joshua Powers]

Public bug reported:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As of March 29, 2017, this source package did not contain dep8 tests in
the current development release of Ubuntu, named Zesty. This was
determined by running `pull-lp-source krb5 zesty` and then
checking for the existence of 'debian/tests/' and
'debian/tests/control'.

Test automation is essential to higher levels of quality and confidence
in updates to packages. dep8 tests [1] specify how automatic testing can
be integrated into packages and then run by package maintainers before
new uploads.

This defect is to report the absence of these tests and to report the
opportunity as a potential item for development by both new and
experienced contributors.

[1] http://packaging.ubuntu.com/html/auto-pkg-test.html

 affects ubuntu/krb5
 status new
 importance wishlist
 tag needs-dep8

- ---
Joshua Powers
Ubuntu Server
Canonical Ltd

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJY3YGVAAoJEIP8BxPaZgwlCIEP/36uotG3iLNIh5/fPc2FDzwV
hqK5CLKbCLqlX7RmzkSzO303hJ051Q6uWIb1ZcnvZShO4h2mrQfyXXmWBXO3So/2
imYe6Pg3j9v1aNYCxpvWKL6VIpN5beADCoWlAS9P89qSIdyEYTiaL6HFHzbA5hck
7rtMhHnzw16mkT+ttZ39f4kqZ9jqqV1je0lPyCI3L+UicswkdeymHeZAZSkG13lW
uSi5SVLFDpDeWq/23Ohj0tacLZbpBKG4vScRQ7+Me3ieGnC0gii8C1luXGPWpS9v
CvW1JLPbuo3yHooBzJw6YAYI2TiWyNjtO2/9ESPxcmn+tPn7iXoeTBIstlQC2iY0
fvoUrmxUjSJafgCyZE1NNy8gTlFLObpMP/qZPtw7YLKaD9t64+JZUK4vzSNr1tY5
ltCXFf0mneUrUjTOS1Io+vigiBbMEIFuUjEXT3DxGEybf8rrl6fJdCD++1L0NTXR
ImfhCBgSEYBrluRLHu1tGftin7wKgarl7uWLzZxGeJ/MiXkX0eWIgOVoXaQq6gnR
HR7XF1x9x1VJYi2CGMrDDWSHWDHgXC5UOcBz/KLMSPMcyQakXyRrw1Hqplj3G3PM
OkqR8uLWUYfTZvrVvnSj4jJPNRSiBOz95FFbfMZ43yxoE5F6QBhztwgcJC8/g+bn
zu94s0Hiyv+yxmptMwgX
=ibX0
-END PGP SIGNATURE-

** Affects: krb5 (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: needs-dep8

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

Title:
  Missing dep8 tests

Status in krb5 package in Ubuntu:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source krb5 zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/krb5
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3YGVAAoJEIP8BxPaZgwlCIEP/36uotG3iLNIh5/fPc2FDzwV
  hqK5CLKbCLqlX7RmzkSzO303hJ051Q6uWIb1ZcnvZShO4h2mrQfyXXmWBXO3So/2
  imYe6Pg3j9v1aNYCxpvWKL6VIpN5beADCoWlAS9P89qSIdyEYTiaL6HFHzbA5hck
  7rtMhHnzw16mkT+ttZ39f4kqZ9jqqV1je0lPyCI3L+UicswkdeymHeZAZSkG13lW
  uSi5SVLFDpDeWq/23Ohj0tacLZbpBKG4vScRQ7+Me3ieGnC0gii8C1luXGPWpS9v
  CvW1JLPbuo3yHooBzJw6YAYI2TiWyNjtO2/9ESPxcmn+tPn7iXoeTBIstlQC2iY0
  fvoUrmxUjSJafgCyZE1NNy8gTlFLObpMP/qZPtw7YLKaD9t64+JZUK4vzSNr1tY5
  ltCXFf0mneUrUjTOS1Io+vigiBbMEIFuUjEXT3DxGEybf8rrl6fJdCD++1L0NTXR
  ImfhCBgSEYBrluRLHu1tGftin7wKgarl7uWLzZxGeJ/MiXkX0eWIgOVoXaQq6gnR
  HR7XF1x9x1VJYi2CGMrDDWSHWDHgXC5UOcBz/KLMSPMcyQakXyRrw1Hqplj3G3PM
  OkqR8uLWUYfTZvrVvnSj4jJPNRSiBOz95FFbfMZ43yxoE5F6QBhztwgcJC8/g+bn
  zu94s0Hiyv+yxmptMwgX
  =ibX0
  -END PGP SIGNATURE-

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

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

[Touch-packages] [Bug 1677863] [NEW] Missing dep8 tests

[Joshua Powers]

Public bug reported:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As of March 29, 2017, this source package did not contain dep8 tests in
the current development release of Ubuntu, named Zesty. This was
determined by running `pull-lp-source heimdal zesty` and then
checking for the existence of 'debian/tests/' and
'debian/tests/control'.

Test automation is essential to higher levels of quality and confidence
in updates to packages. dep8 tests [1] specify how automatic testing can
be integrated into packages and then run by package maintainers before
new uploads.

This defect is to report the absence of these tests and to report the
opportunity as a potential item for development by both new and
experienced contributors.

[1] http://packaging.ubuntu.com/html/auto-pkg-test.html

 affects ubuntu/heimdal
 status new
 importance wishlist
 tag needs-dep8

- ---
Joshua Powers
Ubuntu Server
Canonical Ltd

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJY3YANAAoJEIP8BxPaZgwlu24P/iJX01lyOO5vUdzYTOvjqNTF
dGfAICBhOjkiHKMTa56e1VutrufBipgPZVdXAzou9fLb18SMBPH8SP5/iSk3GrCD
3IYIqY/+c+rQg/dVGWEpXOMpop8r+2d1IGarmy3PZuFvVJI34dskSkCBqW2OlHz+
unQ522qfDqfZ/8rq1xKspB/Vi7kbKV0uYenpgOhs5Vlb8nfWrHv1Zm+6lOnI42WJ
r2+Hc1bb6snzKsYPgL6qigouHK4vsZjbWIugTaHalOQpm8R865Q8XSS+Skb2nGDp
Ql2ULalPqERQRDOUtCpPaqZgB1iVlHApCRgH5baSh1a9WMraHoLlZLP/uRL6s4wC
ThzeCGT2qJwSkESc/QE5iPtEx50+Kx8JVJgXxdjEArgVtHZERJ36U2FIzJE94uNG
AiAOcvIjOTwHRqEQngPFtI+XskuKP2WeO5PbwgqgH51fi1LiNIovN1IALYZxsnhz
2qnorVpeJceVDXavgYiaWvPqiGh1EqXDIyqTdjT3r9cE+OjQMJV53SJk16wB6SyH
8E4GsWiazbSTvaAM5mWK7rFZh7vMcIDK8MpqVPxbgQrwV36DFXLyNVr/8eIvpO8G
Gsk2UHxLdm4tPp7/Vkz9eBRhnP6fH6TTOpaKWPsn222m2LsnMS6gjXZMoIS4Pv0j
KJoEHC3RRqOctkLd03Ck
=mrOm
-END PGP SIGNATURE-

** Affects: heimdal (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: needs-dep8

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

Title:
  Missing dep8 tests

Status in heimdal package in Ubuntu:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source heimdal zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/heimdal
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3YANAAoJEIP8BxPaZgwlu24P/iJX01lyOO5vUdzYTOvjqNTF
  dGfAICBhOjkiHKMTa56e1VutrufBipgPZVdXAzou9fLb18SMBPH8SP5/iSk3GrCD
  3IYIqY/+c+rQg/dVGWEpXOMpop8r+2d1IGarmy3PZuFvVJI34dskSkCBqW2OlHz+
  unQ522qfDqfZ/8rq1xKspB/Vi7kbKV0uYenpgOhs5Vlb8nfWrHv1Zm+6lOnI42WJ
  r2+Hc1bb6snzKsYPgL6qigouHK4vsZjbWIugTaHalOQpm8R865Q8XSS+Skb2nGDp
  Ql2ULalPqERQRDOUtCpPaqZgB1iVlHApCRgH5baSh1a9WMraHoLlZLP/uRL6s4wC
  ThzeCGT2qJwSkESc/QE5iPtEx50+Kx8JVJgXxdjEArgVtHZERJ36U2FIzJE94uNG
  AiAOcvIjOTwHRqEQngPFtI+XskuKP2WeO5PbwgqgH51fi1LiNIovN1IALYZxsnhz
  2qnorVpeJceVDXavgYiaWvPqiGh1EqXDIyqTdjT3r9cE+OjQMJV53SJk16wB6SyH
  8E4GsWiazbSTvaAM5mWK7rFZh7vMcIDK8MpqVPxbgQrwV36DFXLyNVr/8eIvpO8G
  Gsk2UHxLdm4tPp7/Vkz9eBRhnP6fH6TTOpaKWPsn222m2LsnMS6gjXZMoIS4Pv0j
  KJoEHC3RRqOctkLd03Ck
  =mrOm
  -END PGP SIGNATURE-

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

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

[Touch-packages] [Bug 1677869] [NEW] Missing dep8 tests

[Joshua Powers]

Public bug reported:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As of March 29, 2017, this source package did not contain dep8 tests in
the current development release of Ubuntu, named Zesty. This was
determined by running `pull-lp-source iproute2 zesty` and then
checking for the existence of 'debian/tests/' and
'debian/tests/control'.

Test automation is essential to higher levels of quality and confidence
in updates to packages. dep8 tests [1] specify how automatic testing can
be integrated into packages and then run by package maintainers before
new uploads.

This defect is to report the absence of these tests and to report the
opportunity as a potential item for development by both new and
experienced contributors.

[1] http://packaging.ubuntu.com/html/auto-pkg-test.html

 affects ubuntu/iproute2
 status new
 importance wishlist
 tag needs-dep8

- ---
Joshua Powers
Ubuntu Server
Canonical Ltd

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJY3YCYAAoJEIP8BxPaZgwl+YMP/itZd9vMISQh89Gz1BvsISKo
u8TSiOxpvECMUls1s530MQQq4qY5fLH3ofyP2RiMkZQpOGZTscHIV1AwntBuYQTY
z039AKp/CRqHdb9z4GCHxDy13B2fIjAEfIcPfD/5XrPHXTTePvvsl2abC1niB+xY
MWyFeHzTVj2vfSnBegiSM4LFvOTqtx4c0JCi7E3njO5AnZQ6Q3NUZ6uY1kzEingO
BaSkM6P7PLRWeX3ScLqk/yFjWbDheQsDTqmqfTjx2gu2aAAPyH10+aZXVotUpklL
+EACK78VRslNPLdq/VAkoCxztcLx7SNSL3oI2Uf27xFY3LYh5MmeZN+J5N2NwLa3
PaCmCt5fYIB6kGTR0eyZyth8S96frOLX8AgifQ7mPlariPosn4bGu/U7vJ3aR+Al
DnD9pr8t9gpToAP2rDOADLzvtX1gaa2/JcULet0ZiYlEAcizW2nJFZjuO7oqOj/G
Y8/MFT6yRXPWRhmhO9f6/O0OE15fTTYwmoYnjkMz2+rtMZkJg7S7OFgfdyfz9LOi
3bcNgw6zNpdoZwpZAhknOst7dZQ0hC9crG4W7r6jBvLTvdEhNwPTkg64HZHWq510
PCCK2MLjxKJdozeyF9yD/gA9H8bgP5cIVy3eEglZr4nlr9W1VDcTl/ZJg65d1HGb
PDmiWw9XnV1jO4QBlD7z
=jCpZ
-END PGP SIGNATURE-

** Affects: iproute2 (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: needs-dep8

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

Title:
  Missing dep8 tests

Status in iproute2 package in Ubuntu:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source iproute2 zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/iproute2
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3YCYAAoJEIP8BxPaZgwl+YMP/itZd9vMISQh89Gz1BvsISKo
  u8TSiOxpvECMUls1s530MQQq4qY5fLH3ofyP2RiMkZQpOGZTscHIV1AwntBuYQTY
  z039AKp/CRqHdb9z4GCHxDy13B2fIjAEfIcPfD/5XrPHXTTePvvsl2abC1niB+xY
  MWyFeHzTVj2vfSnBegiSM4LFvOTqtx4c0JCi7E3njO5AnZQ6Q3NUZ6uY1kzEingO
  BaSkM6P7PLRWeX3ScLqk/yFjWbDheQsDTqmqfTjx2gu2aAAPyH10+aZXVotUpklL
  +EACK78VRslNPLdq/VAkoCxztcLx7SNSL3oI2Uf27xFY3LYh5MmeZN+J5N2NwLa3
  PaCmCt5fYIB6kGTR0eyZyth8S96frOLX8AgifQ7mPlariPosn4bGu/U7vJ3aR+Al
  DnD9pr8t9gpToAP2rDOADLzvtX1gaa2/JcULet0ZiYlEAcizW2nJFZjuO7oqOj/G
  Y8/MFT6yRXPWRhmhO9f6/O0OE15fTTYwmoYnjkMz2+rtMZkJg7S7OFgfdyfz9LOi
  3bcNgw6zNpdoZwpZAhknOst7dZQ0hC9crG4W7r6jBvLTvdEhNwPTkg64HZHWq510
  PCCK2MLjxKJdozeyF9yD/gA9H8bgP5cIVy3eEglZr4nlr9W1VDcTl/ZJg65d1HGb
  PDmiWw9XnV1jO4QBlD7z
  =jCpZ
  -END PGP SIGNATURE-

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

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

[Touch-packages] [Bug 1677827] [NEW] Missing dep8 tests

[Joshua Powers]

Public bug reported:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As of March 29, 2017, this source package did not contain dep8 tests in
the current development release of Ubuntu, named Zesty. This was
determined by running `pull-lp-source dnsmasq zesty` and then
checking for the existence of 'debian/tests/' and
'debian/tests/control'.

Test automation is essential to higher levels of quality and confidence
in updates to packages. dep8 tests [1] specify how automatic testing can
be integrated into packages and then run by package maintainers before
new uploads.

This defect is to report the absence of these tests and to report the
opportunity as a potential item for development by both new and
experienced contributors.

[1] http://packaging.ubuntu.com/html/auto-pkg-test.html

 affects ubuntu/dnsmasq
 status new
 importance wishlist
 tag needs-dep8

- ---
Joshua Powers
Ubuntu Server
Canonical Ltd

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJY3XcdAAoJEIP8BxPaZgwlCPUQAIeBwdnTYjMB0QFt7FZSUOqx
9N4PMHdxodMVmtEW2FytBuuq0S1jTyu06GNsLwKBmzfyuICScCoGPt8KS14omp/R
g0QAA4Fk2T6YMtVdsZIflUpMzlNTiFw2Ndgf7LOs3xX2lkB36xqbWlr+86fCTe+2
O8pzYZoQeveHc7XQxlT0eDFCiZx83ZFwjF8OjgGfWY3iQsvcb2T00hKlkpQ2qCdT
uiBTN6xnw9v50OGGlphObRy4YdE8x4u3/jWFOzwKUk5X1Qi31wK9hQYLSBAgX7Ph
kkL681OBi5RIlUO5QsD3qJPvi3OIGMx2zhMvQfcK8Otn5DMwDoEETOAafMvPmhd/
NUK/OaNcB2TR6Sl5Jt/NUp3E0LRTYgbMuEONkEeBm5YdABb7hUcYRPomnpzCcNBL
iSdcEH2khGbiCK3oYcT5UgtBe4MFlpHHkkQzmew/nLNZ/BrgULFs0HWLXu8gWN8g
Wn0iAF/Ft2kcWgRNXJ3JCd2nc04U0hqiUmMtVXku4r0f3fxfTudtvPACcZC7ctKb
0rqChEm0r/ewtHvLcuOFIIJBaTQxoQmm8zBPv/y/S+YdkwmVYS9LlWKqG54KLlPy
iAt7+/GvQ0fqqzmk88yQ5F4L19Dg+X5fLZVM1wBvvQ4nTsJRfUhf3+I2orcKDy6C
zNZGvitiod7eMrypmXIA
=k1Nj
-END PGP SIGNATURE-

** Affects: dnsmasq (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: needs-dep8

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

Title:
  Missing dep8 tests

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source dnsmasq zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/dnsmasq
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3XcdAAoJEIP8BxPaZgwlCPUQAIeBwdnTYjMB0QFt7FZSUOqx
  9N4PMHdxodMVmtEW2FytBuuq0S1jTyu06GNsLwKBmzfyuICScCoGPt8KS14omp/R
  g0QAA4Fk2T6YMtVdsZIflUpMzlNTiFw2Ndgf7LOs3xX2lkB36xqbWlr+86fCTe+2
  O8pzYZoQeveHc7XQxlT0eDFCiZx83ZFwjF8OjgGfWY3iQsvcb2T00hKlkpQ2qCdT
  uiBTN6xnw9v50OGGlphObRy4YdE8x4u3/jWFOzwKUk5X1Qi31wK9hQYLSBAgX7Ph
  kkL681OBi5RIlUO5QsD3qJPvi3OIGMx2zhMvQfcK8Otn5DMwDoEETOAafMvPmhd/
  NUK/OaNcB2TR6Sl5Jt/NUp3E0LRTYgbMuEONkEeBm5YdABb7hUcYRPomnpzCcNBL
  iSdcEH2khGbiCK3oYcT5UgtBe4MFlpHHkkQzmew/nLNZ/BrgULFs0HWLXu8gWN8g
  Wn0iAF/Ft2kcWgRNXJ3JCd2nc04U0hqiUmMtVXku4r0f3fxfTudtvPACcZC7ctKb
  0rqChEm0r/ewtHvLcuOFIIJBaTQxoQmm8zBPv/y/S+YdkwmVYS9LlWKqG54KLlPy
  iAt7+/GvQ0fqqzmk88yQ5F4L19Dg+X5fLZVM1wBvvQ4nTsJRfUhf3+I2orcKDy6C
  zNZGvitiod7eMrypmXIA
  =k1Nj
  -END PGP SIGNATURE-

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

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

[Touch-packages] [Bug 1677781] [NEW] Missing dep8 tests

[Joshua Powers]

Public bug reported:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As of March 29, 2017, this source package did not contain dep8 tests in
the current development release of Ubuntu, named Zesty. This was
determined by running `pull-lp-source cyrus-sasl2 zesty` and then
checking for the existence of 'debian/tests/' and
'debian/tests/control'.

Test automation is essential to higher levels of quality and confidence
in updates to packages. dep8 tests [1] specify how automatic testing can
be integrated into packages and then run by package maintainers before
new uploads.

This defect is to report the absence of these tests and to report the
opportunity as a potential item for development by both new and
experienced contributors.

[1] http://packaging.ubuntu.com/html/auto-pkg-test.html

 affects ubuntu/cyrus-sasl2
 status new
 importance wishlist
 tag needs-dep8

- ---
Joshua Powers
Ubuntu Server
Canonical Ltd

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJY3XaTAAoJEIP8BxPaZgwlJr8P/j8yn8mXWnAIiXUgHX7jBIGj
JuMQGO5wwcfHRxOwJEOlsO/SIATUN1L1BB84anP7Bp4cfLqXonF8eKFPkEotwaf1
3wADCH98EwLuSyJOaKXsTQHppAKdJ6UEW4jHvfhYizenEWssPfCQdg68LSGZ2enR
wD9ZhZgjwJIpLbqDTp7ygklR0htf4ZAFq/vIcyLykT6qagVE3xC8SAgd+7tb/fYe
4PYfqgGso/qpL0v6JL+YkCKH/aiMYV+HD45o1NcUbGdoiuUa9jpeYSSTP/9OgWpY
nALDXe/dJZT/wz5Zv0cy6sGRh7gtjVqI0608WAM00Jp8CmFX60z4yrq/3t37wKbz
iDQF4HyltqfCNF5oQ6xva9xAq/c2tyP8nBHzQ+ZtH/o1hyS/JdgoR38OojldyUc5
WzcTFL+h612ZVZVNm4lqBpg/0dpEkwXTE9KczyB5kSr5VVz0WXtjU5wFxKMdZpr5
Gq9uM+fHU4YHQqfGGZxmHFOgz7tCAyEsZEzpnPiYvoSksj3tJMkQG7FbIISltort
CBAwLIt1hLR9g4T3p0e4ipCJf6kL/yZR3kMGhsjbDe012bTaC8ZeLG7VYmWkBaxY
ieFMZIxmGgCq7KjDfNPh9JEmCtNgenkEOu6BszZK+gwmhL/AxVuuNRdd5OeBGy3G
WY9JzBOc6MUi46Hh9ZN5
=szTz
-END PGP SIGNATURE-

** Affects: cyrus-sasl2 (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: needs-dep8

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

Title:
  Missing dep8 tests

Status in cyrus-sasl2 package in Ubuntu:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source cyrus-sasl2 zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/cyrus-sasl2
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3XaTAAoJEIP8BxPaZgwlJr8P/j8yn8mXWnAIiXUgHX7jBIGj
  JuMQGO5wwcfHRxOwJEOlsO/SIATUN1L1BB84anP7Bp4cfLqXonF8eKFPkEotwaf1
  3wADCH98EwLuSyJOaKXsTQHppAKdJ6UEW4jHvfhYizenEWssPfCQdg68LSGZ2enR
  wD9ZhZgjwJIpLbqDTp7ygklR0htf4ZAFq/vIcyLykT6qagVE3xC8SAgd+7tb/fYe
  4PYfqgGso/qpL0v6JL+YkCKH/aiMYV+HD45o1NcUbGdoiuUa9jpeYSSTP/9OgWpY
  nALDXe/dJZT/wz5Zv0cy6sGRh7gtjVqI0608WAM00Jp8CmFX60z4yrq/3t37wKbz
  iDQF4HyltqfCNF5oQ6xva9xAq/c2tyP8nBHzQ+ZtH/o1hyS/JdgoR38OojldyUc5
  WzcTFL+h612ZVZVNm4lqBpg/0dpEkwXTE9KczyB5kSr5VVz0WXtjU5wFxKMdZpr5
  Gq9uM+fHU4YHQqfGGZxmHFOgz7tCAyEsZEzpnPiYvoSksj3tJMkQG7FbIISltort
  CBAwLIt1hLR9g4T3p0e4ipCJf6kL/yZR3kMGhsjbDe012bTaC8ZeLG7VYmWkBaxY
  ieFMZIxmGgCq7KjDfNPh9JEmCtNgenkEOu6BszZK+gwmhL/AxVuuNRdd5OeBGy3G
  WY9JzBOc6MUi46Hh9ZN5
  =szTz
  -END PGP SIGNATURE-

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1677781/+subscriptions

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

[Touch-packages] [Bug 1677769] [NEW] Missing dep8 tests

[Joshua Powers]

Public bug reported:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As of March 29, 2017, this source package did not contain dep8 tests in
the current development release of Ubuntu, named Zesty. This was
determined by running `pull-lp-source cgroup-lite zesty` and then
checking for the existence of 'debian/tests/' and
'debian/tests/control'.

Test automation is essential to higher levels of quality and confidence
in updates to packages. dep8 tests [1] specify how automatic testing can
be integrated into packages and then run by package maintainers before
new uploads.

This defect is to report the absence of these tests and to report the
opportunity as a potential item for development by both new and
experienced contributors.

[1] http://packaging.ubuntu.com/html/auto-pkg-test.html

 affects ubuntu/cgroup-lite
 status new
 importance wishlist
 tag needs-dep8

- ---
Joshua Powers
Ubuntu Server
Canonical Ltd

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJY3XV+AAoJEIP8BxPaZgwlA7IP/3CDdW+oOvnshtX+Ec32+cQD
shAMELYx+YZAvAPYIr5aWwspqeeEo5sNr6qIDPkldrvgtPMIbikr7gAeSCsyDFaU
i0KkmA/WCwbFWh8g75FjHdKXpvhG3IJOBt+YhubdAIk8KocxGhsmLCDN8W9g4kLx
iyafNT+h2mtP4WZgIgBxDF0Mk7GJdFJCaxp+ZM8RsaRUM50uUPRaM0QsbSvmy31C
iOHoKzakxFd0dQFHL3fD/akIhoiboo01AnIHtfUN5rI+g86RWO+1Du7+n18aTDKD
fSrHKDKlIhDvi/QDH/fpnGcZJLPHOz3oX/+Jyx50ym1V8HjJNFqi6Mf1aw0JDCuJ
SvQ3FglxbwMkEsOMYt7QM+zpeJxltBBxtbYtR3otG3QsbclD99E+RDXOd+QY/CXH
PIxGXoh8QAJkS2AJ6DkzVL6KLR4U0ku6RgIFctQoznmGyi9Ln8ZtndoqGftspRql
iRp/jeZYXzsBawh50j1BcXys87q1MH62boyZwzhb9Ry4GLlonPc6T6H8/j4qTYpO
pMRJn9u7VzRoGwX9mUku4jPU0ftFKDkvmqDXPhBQcLfoi74yZMijid0VcfFJefnM
siQ9q+sVIPh+XR/iDyx4x93gyUap/0PTHihOhiCxbVOQt/8a8qZqHeBhX+wMZoFX
+2fsSlYb5adTOs1CwZID
=hcjz
-END PGP SIGNATURE-

** Affects: cgroup-lite (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: needs-dep8

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

Title:
  Missing dep8 tests

Status in cgroup-lite package in Ubuntu:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source cgroup-lite zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/cgroup-lite
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3XV+AAoJEIP8BxPaZgwlA7IP/3CDdW+oOvnshtX+Ec32+cQD
  shAMELYx+YZAvAPYIr5aWwspqeeEo5sNr6qIDPkldrvgtPMIbikr7gAeSCsyDFaU
  i0KkmA/WCwbFWh8g75FjHdKXpvhG3IJOBt+YhubdAIk8KocxGhsmLCDN8W9g4kLx
  iyafNT+h2mtP4WZgIgBxDF0Mk7GJdFJCaxp+ZM8RsaRUM50uUPRaM0QsbSvmy31C
  iOHoKzakxFd0dQFHL3fD/akIhoiboo01AnIHtfUN5rI+g86RWO+1Du7+n18aTDKD
  fSrHKDKlIhDvi/QDH/fpnGcZJLPHOz3oX/+Jyx50ym1V8HjJNFqi6Mf1aw0JDCuJ
  SvQ3FglxbwMkEsOMYt7QM+zpeJxltBBxtbYtR3otG3QsbclD99E+RDXOd+QY/CXH
  PIxGXoh8QAJkS2AJ6DkzVL6KLR4U0ku6RgIFctQoznmGyi9Ln8ZtndoqGftspRql
  iRp/jeZYXzsBawh50j1BcXys87q1MH62boyZwzhb9Ry4GLlonPc6T6H8/j4qTYpO
  pMRJn9u7VzRoGwX9mUku4jPU0ftFKDkvmqDXPhBQcLfoi74yZMijid0VcfFJefnM
  siQ9q+sVIPh+XR/iDyx4x93gyUap/0PTHihOhiCxbVOQt/8a8qZqHeBhX+wMZoFX
  +2fsSlYb5adTOs1CwZID
  =hcjz
  -END PGP SIGNATURE-

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1677769/+subscriptions

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

[Touch-packages] [Bug 1677763] [NEW] Missing dep8 tests

[Joshua Powers]

Public bug reported:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As of March 29, 2017, this source package did not contain dep8 tests in
the current development release of Ubuntu, named Zesty. This was
determined by running `pull-lp-source bridge-utils zesty` and then
checking for the existence of 'debian/tests/' and
'debian/tests/control'.

Test automation is essential to higher levels of quality and confidence
in updates to packages. dep8 tests [1] specify how automatic testing can
be integrated into packages and then run by package maintainers before
new uploads.

This defect is to report the absence of these tests and to report the
opportunity as a potential item for development by both new and
experienced contributors.

[1] http://packaging.ubuntu.com/html/auto-pkg-test.html

 affects ubuntu/bridge-utils
 status new
 importance wishlist
 tag needs-dep8

- ---
Joshua Powers
Ubuntu Server
Canonical Ltd

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJY3XT0AAoJEIP8BxPaZgwlnmAP/2eq6+9nUI4biSdor0atJfvp
WghGEsAdDIi7hFAmUAwZ/CzNCihlhjAwuVvO05y/fuVgKbT9bzYYueE8qfv2icVW
0Zf8LDaYWbtEbxbf/WOnHQAUc6uwiPMlzsgi6f2ZExwPBox4rmADyFMzApCZERsN
gTODLjxmxxViEfosGAHSg5C3FaYuP0pcfalq4X5pFcyuph2sUyUsv/snNliKEo1S
xTYgxsZ9Cd1T8oqjaqb2jPZ015HYqMi4ozLAlmFJPC9VynJGOm//kUDU1XzF9qKY
B66P/e1pC9vuK/YwSt3suyrGgjdjMrSjUIhxCcssPeIkZOq0oUsa/pwdVAQcNTGW
siPwVW1jTtRPPuV0nCqoppbu4mtf6wr2tjmN8q7tHBmT6rgsSh0eMaYzWqnrEsiU
dSdhGWH6nojbENE97RVadCQLxASi/e46kbFYxg9OBsuUIJLJlCIHjAWBWaOxt7L5
np1v8kn7XkloUW8sQxnxRTgXW+sXKaSmgZCe5poczBfX7IaZeI4n6YJWfArZNABC
4YGJR/buvfkiiKaAtWZPWGkM88cKOtRJ7DezaGbGvHZOmolJ3CdX3P8RkKTO/ehS
9ma0WzKaYO2Q4KM7b8DcEwGOAHUtVMmR9jcFkrG73GSl4He+CsIHpGFBP1uYtOe3
jVL6n0zG7I5R2NZ+EAx5
=59oi
-END PGP SIGNATURE-

** Affects: bridge-utils (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: needs-dep8

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

Title:
  Missing dep8 tests

Status in bridge-utils package in Ubuntu:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source bridge-utils zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/bridge-utils
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3XT0AAoJEIP8BxPaZgwlnmAP/2eq6+9nUI4biSdor0atJfvp
  WghGEsAdDIi7hFAmUAwZ/CzNCihlhjAwuVvO05y/fuVgKbT9bzYYueE8qfv2icVW
  0Zf8LDaYWbtEbxbf/WOnHQAUc6uwiPMlzsgi6f2ZExwPBox4rmADyFMzApCZERsN
  gTODLjxmxxViEfosGAHSg5C3FaYuP0pcfalq4X5pFcyuph2sUyUsv/snNliKEo1S
  xTYgxsZ9Cd1T8oqjaqb2jPZ015HYqMi4ozLAlmFJPC9VynJGOm//kUDU1XzF9qKY
  B66P/e1pC9vuK/YwSt3suyrGgjdjMrSjUIhxCcssPeIkZOq0oUsa/pwdVAQcNTGW
  siPwVW1jTtRPPuV0nCqoppbu4mtf6wr2tjmN8q7tHBmT6rgsSh0eMaYzWqnrEsiU
  dSdhGWH6nojbENE97RVadCQLxASi/e46kbFYxg9OBsuUIJLJlCIHjAWBWaOxt7L5
  np1v8kn7XkloUW8sQxnxRTgXW+sXKaSmgZCe5poczBfX7IaZeI4n6YJWfArZNABC
  4YGJR/buvfkiiKaAtWZPWGkM88cKOtRJ7DezaGbGvHZOmolJ3CdX3P8RkKTO/ehS
  9ma0WzKaYO2Q4KM7b8DcEwGOAHUtVMmR9jcFkrG73GSl4He+CsIHpGFBP1uYtOe3
  jVL6n0zG7I5R2NZ+EAx5
  =59oi
  -END PGP SIGNATURE-

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1677763/+subscriptions

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

[Touch-packages] [Bug 1671731] Re: [xmir] closing an app while a child window is opened leaves an Xmir process opened eating 100% CPU

[Ted Gould]

** No longer affects: ubuntu-app-launch (Ubuntu)

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

Title:
  [xmir] closing an app while a child window is opened leaves an Xmir
  process opened eating 100% CPU

Status in Canonical System Image:
  Triaged
Status in unity8 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04 Unity 8
  [xmir] closing an app while a child window is opened leaves an Xmir process 
opened eating 100% CPU

  launch solitaire (just click on the sol icon from launcher, it will just run 
on Xmir)
  open the about window from the menu (Help \ About)
  now close the main window 

  now top in a terminal (see attached)

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

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

[Touch-packages] [Bug 1675163] Re: Don't attempt to create devices in LXC containers

[Launchpad Bug Tracker]

This bug was fixed in the package makedev -
2.3.1-93ubuntu2~ubuntu16.04.1

---
makedev (2.3.1-93ubuntu2~ubuntu16.04.1) xenial; urgency=medium

  * Don't attempt to create /dev devices when inside a container.
(LP: #1675163)

 -- Stéphane Graber   Wed, 22 Mar 2017 16:38:22
-0400

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

Title:
  Don't attempt to create devices in LXC containers

Status in makedev package in Ubuntu:
  Fix Released
Status in makedev source package in Precise:
  Fix Released
Status in makedev source package in Trusty:
  Fix Released
Status in makedev source package in Xenial:
  Fix Released
Status in makedev source package in Yakkety:
  Fix Released
Status in makedev source package in Zesty:
  Fix Released

Bug description:
  Right now the "makedev" postinst script will attempt to create a
  number of devices in /dev, failing the package upgrade should any of
  those mknod calls fail.

  LXC containers, especially unprivileged ones do not allow the use of
  mknod, making it impossible to upgrade makedev in those containers and
  preventing Ubuntu release upgrades.

  The fix is quite simple, detect that we are running in an LXC
  container and skip the rest of the postinst script as is done in a
  number of other cases.

  = SRU
  == Rationale
  This issue prevents release to release upgrades in unprivileged LXC 
containers when makedev is part of the upgraded set. This is currently visible 
when upgrading from Ubuntu 12.04 to Ubuntu 14.04.

  == Testcase
  Install the new package in an unprivileged container. With LXD, simply use 
"lxc launch ubuntu: test" to create the container.

  Prior to this fix, the upgrade will fail on some mknod errors, after
  it, it'll go on after printing a message indicating that LXC was
  detected.

  == Regression potential
  The detection logic is based on PID 1's environment containing a 
container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the 
makedev upgrade no longer creating extra devices. This is unlikely to really 
matter though since the system is clearly already functioning properly at that 
point.

  Similarly, some privileged LXC containers can be configured in a way
  where mknod is possible, this update will still disable the postinst
  for those cases as short of attempting every mknod ahead of time,
  there is no reliable way to detect any seccomp or apparmor policy in
  play.

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

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

[Touch-packages] [Bug 1672392] Re: Install an app from Ubuntu Terminal and it doesn't show up in the app drawer

[Ted Gould]

** Branch linked: lp:~ted/ubuntu-app-launch/system-app-watch

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

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

Title:
  Install an app from Ubuntu Terminal and it doesn't show up in the app
  drawer

Status in Canonical System Image:
  Triaged
Status in ubuntu-app-launch package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  On a fresh Zesty Qemu VM, I installed dconf-editor from the archive
  using the terminal.

    sudo apt install dconf-editor

  and it didn't show up in the app drawer, either in the scrollable list
  or searching by name.

  After a reboot (can't logout due to bug #1670657) dconf-editor is
  there.

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

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

[Touch-packages] [Bug 1675163] Re: Don't attempt to create devices in LXC containers

[Launchpad Bug Tracker]

This bug was fixed in the package makedev - 2.3.1-89ubuntu3

---
makedev (2.3.1-89ubuntu3) precise; urgency=medium

  * Don't attempt to create /dev devices when inside a container.
(LP: #1675163)

 -- Stéphane Graber   Fri, 24 Mar 2017 02:12:05
-0400

** Changed in: makedev (Ubuntu Precise)
   Status: Fix Committed => Fix Released

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

Title:
  Don't attempt to create devices in LXC containers

Status in makedev package in Ubuntu:
  Fix Released
Status in makedev source package in Precise:
  Fix Released
Status in makedev source package in Trusty:
  Fix Released
Status in makedev source package in Xenial:
  Fix Released
Status in makedev source package in Yakkety:
  Fix Released
Status in makedev source package in Zesty:
  Fix Released

Bug description:
  Right now the "makedev" postinst script will attempt to create a
  number of devices in /dev, failing the package upgrade should any of
  those mknod calls fail.

  LXC containers, especially unprivileged ones do not allow the use of
  mknod, making it impossible to upgrade makedev in those containers and
  preventing Ubuntu release upgrades.

  The fix is quite simple, detect that we are running in an LXC
  container and skip the rest of the postinst script as is done in a
  number of other cases.

  = SRU
  == Rationale
  This issue prevents release to release upgrades in unprivileged LXC 
containers when makedev is part of the upgraded set. This is currently visible 
when upgrading from Ubuntu 12.04 to Ubuntu 14.04.

  == Testcase
  Install the new package in an unprivileged container. With LXD, simply use 
"lxc launch ubuntu: test" to create the container.

  Prior to this fix, the upgrade will fail on some mknod errors, after
  it, it'll go on after printing a message indicating that LXC was
  detected.

  == Regression potential
  The detection logic is based on PID 1's environment containing a 
container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the 
makedev upgrade no longer creating extra devices. This is unlikely to really 
matter though since the system is clearly already functioning properly at that 
point.

  Similarly, some privileged LXC containers can be configured in a way
  where mknod is possible, this update will still disable the postinst
  for those cases as short of attempting every mknod ahead of time,
  there is no reliable way to detect any seccomp or apparmor policy in
  play.

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

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

[Touch-packages] [Bug 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed

[HaolinLi]

** Changed in: cups (Ubuntu)
 Assignee: (unassigned) => HaolinLi (lihaolin1991)

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

Title:
  cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be
  installed

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This is related to this bug
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790

  After `sudo apt-get -f install`, it removed cups and marked a bunch of
  cups packages as unnecessary

  `sudo apt-get autoremove` removed them.

  Now when I try to re-install cups, I get this error:

  ```
  ☀  sudo apt-get install cups cups-daemon cups-core-drivers
  Mod master
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
  Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed
  Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed
  Recommends: printer-driver-gutenprint but it is not going to be 
installed
   cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to 
be installed
   cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be 
installed
 Depends: libcupsmime1 (>= 1.5.0) but it is not going to be 
installed
 Recommends: cups-browsed but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  ```

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

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

[Touch-packages] [Bug 1675163] Re: Don't attempt to create devices in LXC containers

[Launchpad Bug Tracker]

This bug was fixed in the package makedev -
2.3.1-93ubuntu2~ubuntu14.04.1

---
makedev (2.3.1-93ubuntu2~ubuntu14.04.1) trusty; urgency=medium

  * Don't attempt to create /dev devices when inside a container.
(LP: #1675163)

 -- Stéphane Graber   Wed, 22 Mar 2017 16:38:22
-0400

** Changed in: makedev (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

** Changed in: makedev (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  Don't attempt to create devices in LXC containers

Status in makedev package in Ubuntu:
  Fix Released
Status in makedev source package in Precise:
  Fix Committed
Status in makedev source package in Trusty:
  Fix Released
Status in makedev source package in Xenial:
  Fix Committed
Status in makedev source package in Yakkety:
  Fix Released
Status in makedev source package in Zesty:
  Fix Released

Bug description:
  Right now the "makedev" postinst script will attempt to create a
  number of devices in /dev, failing the package upgrade should any of
  those mknod calls fail.

  LXC containers, especially unprivileged ones do not allow the use of
  mknod, making it impossible to upgrade makedev in those containers and
  preventing Ubuntu release upgrades.

  The fix is quite simple, detect that we are running in an LXC
  container and skip the rest of the postinst script as is done in a
  number of other cases.

  = SRU
  == Rationale
  This issue prevents release to release upgrades in unprivileged LXC 
containers when makedev is part of the upgraded set. This is currently visible 
when upgrading from Ubuntu 12.04 to Ubuntu 14.04.

  == Testcase
  Install the new package in an unprivileged container. With LXD, simply use 
"lxc launch ubuntu: test" to create the container.

  Prior to this fix, the upgrade will fail on some mknod errors, after
  it, it'll go on after printing a message indicating that LXC was
  detected.

  == Regression potential
  The detection logic is based on PID 1's environment containing a 
container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the 
makedev upgrade no longer creating extra devices. This is unlikely to really 
matter though since the system is clearly already functioning properly at that 
point.

  Similarly, some privileged LXC containers can be configured in a way
  where mknod is possible, this update will still disable the postinst
  for those cases as short of attempting every mknod ahead of time,
  there is no reliable way to detect any seccomp or apparmor policy in
  play.

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

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

[Touch-packages] [Bug 1675163] Re: Don't attempt to create devices in LXC containers

[Launchpad Bug Tracker]

This bug was fixed in the package makedev -
2.3.1-93ubuntu2~ubuntu16.10.1

---
makedev (2.3.1-93ubuntu2~ubuntu16.10.1) yakkety; urgency=medium

  * Don't attempt to create /dev devices when inside a container.
(LP: #1675163)

 -- Stéphane Graber   Wed, 22 Mar 2017 16:38:22
-0400

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

Title:
  Don't attempt to create devices in LXC containers

Status in makedev package in Ubuntu:
  Fix Released
Status in makedev source package in Precise:
  Fix Committed
Status in makedev source package in Trusty:
  Fix Released
Status in makedev source package in Xenial:
  Fix Committed
Status in makedev source package in Yakkety:
  Fix Released
Status in makedev source package in Zesty:
  Fix Released

Bug description:
  Right now the "makedev" postinst script will attempt to create a
  number of devices in /dev, failing the package upgrade should any of
  those mknod calls fail.

  LXC containers, especially unprivileged ones do not allow the use of
  mknod, making it impossible to upgrade makedev in those containers and
  preventing Ubuntu release upgrades.

  The fix is quite simple, detect that we are running in an LXC
  container and skip the rest of the postinst script as is done in a
  number of other cases.

  = SRU
  == Rationale
  This issue prevents release to release upgrades in unprivileged LXC 
containers when makedev is part of the upgraded set. This is currently visible 
when upgrading from Ubuntu 12.04 to Ubuntu 14.04.

  == Testcase
  Install the new package in an unprivileged container. With LXD, simply use 
"lxc launch ubuntu: test" to create the container.

  Prior to this fix, the upgrade will fail on some mknod errors, after
  it, it'll go on after printing a message indicating that LXC was
  detected.

  == Regression potential
  The detection logic is based on PID 1's environment containing a 
container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the 
makedev upgrade no longer creating extra devices. This is unlikely to really 
matter though since the system is clearly already functioning properly at that 
point.

  Similarly, some privileged LXC containers can be configured in a way
  where mknod is possible, this update will still disable the postinst
  for those cases as short of attempting every mknod ahead of time,
  there is no reliable way to detect any seccomp or apparmor policy in
  play.

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

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

[Touch-packages] [Bug 1672693] Re: GTK theme in apps appears different under Unity8 compared to Unity7

[Ted Gould]

** No longer affects: ubuntu-app-launch (Ubuntu)

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

Title:
  GTK theme in apps appears different under Unity8 compared to Unity7

Status in Canonical System Image:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.05 Unity8
  some submenus in GTK3 apps look like widgets (see attached screenshots)
  run whatever gtk3 apps native (without Xmir), sol or eog
  open the menu/submenus. the first time you open the menu everything is fine 
but the next times it shows this widget like submenus. just open and close 
submenus (hover the mouse over the main menu left right, right left)

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

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

[Touch-packages] [Bug 1675163] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for makedev 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 makedev in Ubuntu.
https://bugs.launchpad.net/bugs/1675163

Title:
  Don't attempt to create devices in LXC containers

Status in makedev package in Ubuntu:
  Fix Released
Status in makedev source package in Precise:
  Fix Committed
Status in makedev source package in Trusty:
  Fix Released
Status in makedev source package in Xenial:
  Fix Committed
Status in makedev source package in Yakkety:
  Fix Released
Status in makedev source package in Zesty:
  Fix Released

Bug description:
  Right now the "makedev" postinst script will attempt to create a
  number of devices in /dev, failing the package upgrade should any of
  those mknod calls fail.

  LXC containers, especially unprivileged ones do not allow the use of
  mknod, making it impossible to upgrade makedev in those containers and
  preventing Ubuntu release upgrades.

  The fix is quite simple, detect that we are running in an LXC
  container and skip the rest of the postinst script as is done in a
  number of other cases.

  = SRU
  == Rationale
  This issue prevents release to release upgrades in unprivileged LXC 
containers when makedev is part of the upgraded set. This is currently visible 
when upgrading from Ubuntu 12.04 to Ubuntu 14.04.

  == Testcase
  Install the new package in an unprivileged container. With LXD, simply use 
"lxc launch ubuntu: test" to create the container.

  Prior to this fix, the upgrade will fail on some mknod errors, after
  it, it'll go on after printing a message indicating that LXC was
  detected.

  == Regression potential
  The detection logic is based on PID 1's environment containing a 
container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the 
makedev upgrade no longer creating extra devices. This is unlikely to really 
matter though since the system is clearly already functioning properly at that 
point.

  Similarly, some privileged LXC containers can be configured in a way
  where mknod is possible, this update will still disable the postinst
  for those cases as short of attempting every mknod ahead of time,
  there is no reliable way to detect any seccomp or apparmor policy in
  play.

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

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

[Touch-packages] [Bug 1676390] Re: [unity8] launcher menu breaks launch multiple instances

[Ted Gould]

** No longer affects: ubuntu-app-launch (Ubuntu)

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

Title:
  [unity8] launcher menu breaks launch multiple instances

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

Bug description:
  Ubuntu 17.04 Unity 8

  [unity8] launcher menu breaks launch multiple instances
  try with terminix or kate (it doesn't matter), launch terminix (without 
Xmir), right click on the launcher icon to open the menu, click on Terminix 
from the launcher menu (first entry) see screenshot1 then go to and open a New 
Window from the icon/menu (see screenshot2). the window gets unfocuss and it 
doesn't open a new window, but it actually does i think bug hidden somehow, you 
can see the pips/menu in the launcher showing more instances/windows. try the 
same with kate

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

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

[Touch-packages] [Bug 1677305] Re: /dev/sda1 is checked at every boot instead of once every N mounts

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

Title:
  /dev/sda1 is checked at every boot instead of once every N mounts

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Every time I login I get the message:

  *** /dev/sda1 will be checked for errors at next reboot ***

  /dev/sda1 is my root partition. fsck was successfully run, but it
  looks like systemd is not aware of this, so fsck will be run again at
  the next boot.

  root@serverlinux:~# lsb_release -rd
  Description:Ubuntu 16.04.2 LTS
  Release:16.04

  root@serverlinux:~# LANG=en_US apt-cache policy systemd
  systemd:
    Installed: 229-4ubuntu16
    Candidate: 229-4ubuntu16
    Version table:
   *** 229-4ubuntu16 500
  500 http://it.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  root@serverlinux:~# cat /run/initramfs/fsck.log
  Log of fsck -C -a -T -t ext4 /dev/sda1
  Wed Mar 29 00:26:26 2017

  /dev/sda1: clean, 612205/6725632 files, 17326020/2688 blocks
  (check in 2 mounts)

  Wed Mar 29 00:26:26 2017
  

  root@serverlinux:~# LANG=en_US ls -l /run/initramfs/
  total 4
  -rw-r--r-- 1 root root   0 Mar 29 02:26 fsck-root
  -rw-r--r-- 1 root root 194 Mar 29 02:26 fsck.log

  [There's a discrepancy between the time in fsck.log and the time of
  the fsck.log but I suspect this is a UTC/CEST issue:

  root@serverlinux:~# LANG=en_US date
  Wed Mar 29 17:43:17 CEST 2017
  root@serverlinux:~# LANG=en_US date -u
  Wed Mar 29 15:43:21 UTC 2017

  The system was planned for reboot at Mar 29 2:25 CEST (Mar 29 0:25
  UTC)]

  This is the content of /etc/fstab:

  root@serverlinux:~#  cat /etc/fstab
  #
  proc/proc   procnodev,noexec,nosuid 0   0
  # / was on /dev/sda1 during installation
  UUID=c50edc7d-9f0b-4958-8e44-00bb5433ba42 /   ext4
errors=remount-ro,noatime,nodiratime,commit=60 0   1
  # swap was on /dev/sda5 during installation
  UUID=93b413bc-8663-44b4-81de-1a225a2f90da noneswapsw  
0   0
  # /dev/sdb1 in ext4 250GB
  UUID=5f987a15-685a-4d2b-adf9-8bcde0eca04e   /data ext4 
errors=remount-ro,noatime,nodiratime,commit=60   0   1

  The output of dumpe2fs on /dev/sda1 is:
  root@serverlinux:~# LANG=en_US dumpe2fs /dev/sda1
  (...)
  Filesystem created:   Thu Apr 15 15:23:07 2010
  Last mount time:  Wed Mar 29 02:26:26 2017
  Last write time:  Wed Mar 29 02:26:26 2017
  Mount count:  30
  Maximum mount count:  31
  Last checked: Tue Sep  6 02:46:17 2016
  Check interval:   15552000 (6 months)
  Next check after: Sun Mar  5 01:46:17 2017
  (...)

  For some reason, "Last checked:" time is not up to date (see above for
  the content of /run/initramfs/fsck.log), hence the problem (I
  suppose).

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

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

[Touch-packages] [Bug 1613751] Re: journald forwards to syslog with facility=KERN on everything

[Nathan Dorfman]

Ugh, I meant Zesty in my previous comment, not "Zenial."

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

Title:
  journald forwards to syslog with facility=KERN on everything

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Confirmed

Bug description:
  NetworkManager's copious syslog output is for some reason making its
  way into my /var/log/kern.log file. This includes a couple dozen
   lines at startup and a similar amount when connecting to WiFi
  with DHCP.

  The NM man page states that the default facility should be DAEMON, as
  does the NM wiki -- see
  http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html
  and https://wiki.gnome.org/Projects/NetworkManager/Debugging

  Hopefully, it goes without saying that the KERN facility is reserved
  for the kernel and shouldn't be messed with by anything from userland.

  Nothing in the rsyslog configs references kern.log except the one expected 
line:
  /etc/rsyslog.d/50-default.conf:kern.* 
-/var/log/kern.log

  Nothing in NetworkManager.conf references syslog or its facilities.
  Oh, and these messages do also correctly make it to syslog.log. I've
  no idea how or why they also end up in kern.log, though.

  This doesn't happen on Ubuntu 14.04:
  % zgrep -cv kernel: /var/log/kern.log* 
  /var/log/kern.log:0
  /var/log/kern.log.1:0
  /var/log/kern.log.2.gz:0
  /var/log/kern.log.3.gz:0
  /var/log/kern.log.4.gz:0

  On Ubuntu 16.04.1, NM is the major culprit, although there were also a few 
lines from gnome-session:
  % zgrep -cv kernel: /mnt/var/log/kern.log*
  /mnt/var/log/kern.log:402
  /mnt/var/log/kern.log.1:722
  % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager
  17
  % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 
'gnome-session-binary'
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 16 06:53:42 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
86180F  674c9d27-1bb1-4055-a6e4-07de9abbb586  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1677260] Re: bad white flicker when switching tabs

[Bill Filler]

** Tags added: next-candidates

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

Title:
  bad white flicker when switching tabs

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

Bug description:
  when switching tabs from that are shown from a previous session, there
  is a bad white flicker/redraw before the new tab is shown. The
  transition should be smooth without any kind of flicker

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

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

[Touch-packages] [Bug 1677725] [NEW] Error report on bootup is useless to me

[Kevin O'Gorman]

Public bug reported:

On booting my system, I see dialog reporting a "system program error"
with no further information, and is asks me if I want to report this.

I have no basis on which to make the choice, because I have been
completely unable to figure out what problem is being reported.  The few
times I told it to report, I got no feedback at all.

This does nothing to help me do any of the things I want to do about this 
situation:
1. diagnose or even identify the problem
2. determine if the message got you you, or to anybody for that matter
3. determine if there is an official fix
4. supply additional information
5. Fix the problem, whether on my own or based on an official fix

I'm attaching an image of the dialog I see, as it's all I can offer by
way of identifying the source of the message.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu16
ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
Uname: Linux 4.4.0-71-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Thu Mar 30 12:53:28 2017
ExecutablePath: /lib/systemd/systemd
InstallationDate: Installed on 2016-08-08 (233 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: ASUS All Series
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=c7ad145f-f22d-4d18-9aaf-9701e407e243 ro quiet splash vt.handoff=7
SourcePackage: systemd
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
 
 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2702
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-DELUXE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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


** Tags: amd64 apport-bug xenial

** Attachment added: "image of the error dialog (cropped)"
   
https://bugs.launchpad.net/bugs/1677725/+attachment/4850781/+files/BootupError_2017-03-30.png

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

Title:
  Error report on bootup is useless to me

Status in systemd package in Ubuntu:
  New

Bug description:
  On booting my system, I see dialog reporting a "system program error"
  with no further information, and is asks me if I want to report this.

  I have no basis on which to make the choice, because I have been
  completely unable to figure out what problem is being reported.  The
  few times I told it to report, I got no feedback at all.

  This does nothing to help me do any of the things I want to do about this 
situation:
  1. diagnose or even identify the problem
  2. determine if the message got you you, or to anybody for that matter
  3. determine if there is an official fix
  4. supply additional information
  5. Fix the problem, whether on my own or based on an official fix

  I'm attaching an image of the dialog I see, as it's all I can offer by
  way of identifying the source of the message.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu16
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Thu Mar 30 12:53:28 2017
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2016-08-08 (233 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=c7ad145f-f22d-4d18-9aaf-9701e407e243 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  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
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1675448] Re: Unity 8 doesnt allow multiple mir connections from an application instance

[Daniel d'Andrada]

** Changed in: unity8 (Ubuntu)
   Status: In Progress => 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/1675448

Title:
  Unity 8 doesnt allow multiple mir connections from an application
  instance

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

Bug description:
  Some clients like to probe to see if a mir connection is available
  such as SDL2 and SDL1.2.

  This is an issue in U8 as it doesnt seem to allow multiple connections
  in one process.

  Example:
  http://paste.ubuntu.com/24235399/

  Output on U8:
  http://paste.ubuntu.com/24235406/

   Proposed solution 

  Related to bug #1589637

  We need to accept multiple connections from the same application
  instance, relying on ubuntu-app-launch to tell us about instances and
  their lifecycle.

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

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

[Touch-packages] [Bug 1281192] Re: After removing and restarting: low graphics mode and blank screen

[Stephen M. Webb]

The ubuntu-desktop-mir package was discontinued prior to the release of
Ubuntu 16.10 and removed from this project.  This bug is no longer valid
for this project.

** Changed in: unity-system-compositor
   Status: Confirmed => Invalid

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

Title:
  After removing and restarting: low graphics mode and blank screen

Status in One Hundred Papercuts:
  Triaged
Status in Unity System Compositor:
  Invalid
Status in unity-system-compositor package in Ubuntu:
  Triaged

Bug description:
  When I remove u-s-c and ubuntu-desktop-mir with `remove --auto-
  remove`, I get greeted with the "Low graphics" dialog and lightdm
  won't start. I can get back to the desktop if I reinstall both
  packages (and run `sudo restart lightdm`).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-desktop-mir 0.0.2+14.04.20140212.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity
  Date: Mon Feb 17 13:07:13 2014
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:30a2]
     Subsystem: Hewlett-Packard Company Device [103c:30a2]
  InstallationDate: Installed on 2014-01-14 (34 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140113)
  PackageArchitecture: all
  SourcePackage: unity-system-compositor
  UnitySystemCompositorLog:
   ERROR: 
/build/buildd/mir-0.1.5+14.04.20140212/src/platform/graphics/mesa/linux_virtual_terminal.cpp(125):
 Throw in function virtual void 
mir::graphics::mesa::LinuxVirtualTerminal::set_graphics_mode()
   Dynamic exception type: 
boost::exception_detail::clone_impl
   std::exception::what: Failed to set VT to graphics mode
   5, "Input/output error"
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.libdrm: libdrm2 2.4.52-1
  version.lightdm: lightdm 1.9.7-0ubuntu2
  version.mesa: libegl1-mesa-dev N/A

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

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

[Touch-packages] [Bug 1613751] Re: journald forwards to syslog with facility=KERN on everything

[Nathan Dorfman]

Same issue exists in Zenial. However, the fix has just been merged into
upstream master. It's a trivial one-line change.

** Tags added: zesty

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

Title:
  journald forwards to syslog with facility=KERN on everything

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Confirmed

Bug description:
  NetworkManager's copious syslog output is for some reason making its
  way into my /var/log/kern.log file. This includes a couple dozen
   lines at startup and a similar amount when connecting to WiFi
  with DHCP.

  The NM man page states that the default facility should be DAEMON, as
  does the NM wiki -- see
  http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html
  and https://wiki.gnome.org/Projects/NetworkManager/Debugging

  Hopefully, it goes without saying that the KERN facility is reserved
  for the kernel and shouldn't be messed with by anything from userland.

  Nothing in the rsyslog configs references kern.log except the one expected 
line:
  /etc/rsyslog.d/50-default.conf:kern.* 
-/var/log/kern.log

  Nothing in NetworkManager.conf references syslog or its facilities.
  Oh, and these messages do also correctly make it to syslog.log. I've
  no idea how or why they also end up in kern.log, though.

  This doesn't happen on Ubuntu 14.04:
  % zgrep -cv kernel: /var/log/kern.log* 
  /var/log/kern.log:0
  /var/log/kern.log.1:0
  /var/log/kern.log.2.gz:0
  /var/log/kern.log.3.gz:0
  /var/log/kern.log.4.gz:0

  On Ubuntu 16.04.1, NM is the major culprit, although there were also a few 
lines from gnome-session:
  % zgrep -cv kernel: /mnt/var/log/kern.log*
  /mnt/var/log/kern.log:402
  /mnt/var/log/kern.log.1:722
  % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager
  17
  % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 
'gnome-session-binary'
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 16 06:53:42 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
86180F  674c9d27-1bb1-4055-a6e4-07de9abbb586  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1204505] Re: [enhancement] unity-system-compositor needs to have hw pointer functionality enabled back

[Stephen M. Webb]

** Changed in: unity-system-compositor
   Status: Fix Committed => Fix Released

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

Title:
  [enhancement] unity-system-compositor needs to have hw pointer
  functionality enabled back

Status in Unity System Compositor:
  Fix Released
Status in unity-system-compositor package in Ubuntu:
  Fix Released

Bug description:
  Right now, unity-system-compositor disable hw pointer in Mir through:
  unity-compositor-command=unity-system-compositor --enable-input=false

  This was to workaround an issue with some ati cards that we
  encountered: https://bugs.launchpad.net/mir/+bug/1203070

  Prerequisite fix: bug 1206780

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1204505/+subscriptions

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

[Touch-packages] [Bug 1619448] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available()

[Stephen M. Webb]

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

** This bug has been marked a duplicate of bug 1672955
   unity-system-compositor crashed with SIGSEGV in 
libinput_device_config_accel_is_available() from 
libinput_device_config_accel_set_speed() from 
mir::input::evdev::LibInputDevice::apply_settings()

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

Title:
  unity-system-compositor crashed with SIGSEGV in
  libinput_device_config_accel_is_available()

Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in libinput package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: unity-system-compositor 0.7.1+16.10.20160824-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Thu Sep  1 15:49:59 2016
  ExecutablePath: /usr/sbin/unity-system-compositor
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Atom Processor D4xx/D5xx/N4xx/N5xx 
Integrated Graphics Controller [1025:0349]
 Subsystem: Acer Incorporated [ALI] Atom Processor D4xx/D5xx/N4xx/N5xx 
Integrated Graphics Controller [1025:0349]
  InstallationDate: Installed on 2016-08-27 (5 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/sbin/unity-system-compositor 
--disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket 
--from-dm-fd 12 --to-dm-fd 21 --vt 8
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f6efd9035f0 
:mov0x58(%rdi),%rax
   PC (0x7f6efd9035f0) ok
   source "0x58(%rdi)" (0x3289) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   libinput_device_config_accel_is_available () from 
/usr/lib/x86_64-linux-gnu/libinput.so.10
   libinput_device_config_accel_set_speed () from 
/usr/lib/x86_64-linux-gnu/libinput.so.10
   
mir::input::evdev::LibInputDevice::apply_settings(mir::input::PointerSettings 
const&) () from /usr/lib/x86_64-linux-gnu/mir/server-platform/input-evdev.so.5
   mir::dispatch::ActionQueue::dispatch(unsigned int) () from 
/usr/lib/x86_64-linux-gnu/libmircommon.so.6
   mir::dispatch::MultiplexingDispatchable::dispatch(unsigned int) () from 
/usr/lib/x86_64-linux-gnu/libmircommon.so.6
  Title: unity-system-compositor crashed with SIGSEGV in 
libinput_device_config_accel_is_available()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.70-1
  version.lightdm: lightdm 1.19.4-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

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

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

Re: [Touch-packages] [Bug 1672444] Re: Negative number of tabs at left of the browser

[Víctor R . Ruiz]

Oh, cool. Thanks, dinamic!

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

Title:
  Negative number of tabs at left of the browser

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-extras package in Ubuntu:
  Confirmed

Bug description:
  I am not able to reproduce it. I opened the webbrowser-app after
  updating the silo to the new build, and maximized it. After minimizing
  it again, I spotted the negative number of hidden tabs at left. Not
  sure what steps do trigger this.

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

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

[Touch-packages] [Bug 1677625] Re: ubuntu-terminal-app if the preferences window is minimized and you click on the cogwheel it doesn't bring up the preferences window and also you can't type in the te

[Josh Arenson]

Can you elaborate further? It seems to me that the settings dialog opens
as a new page within the terminal window, rather than as separate
windows.

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

Title:
  ubuntu-terminal-app if the preferences window is minimized and you
  click on the cogwheel it doesn't bring up the preferences window and
  also you can't type in the terminal anymore

Status in Canonical System Image:
  New
Status in Ubuntu Terminal App:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  ubuntu 17.04, terminal app from overlay ppa

  ubuntu-terminal-app if the preferences window is minimized and you
  click on the cogwheel it doesn't bring up the preferences window and
  also you can't type in the terminal anymore

  it happens to me a lot, i open the preferences window, minimize it and
  forget about it, then if i click on the cogwheel it doesn't bring up
  the preferences window and the terminal just loses focus and you can't
  type in it anymore

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

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

[Touch-packages] [Bug 1539300] Re: unity-system-compositor crashed on rethrow with no usable stack trace

[Stephen M. Webb]

** Changed in: unity-system-compositor
Milestone: 0.4.2 => None

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

Title:
  unity-system-compositor crashed on rethrow with no usable stack trace

Status in Unity System Compositor:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-system-compositor.  This problem was most recently
  seen with version 0.3.1+16.04.20160121.1-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/43c0c2dadba3b6f445da3ec932dae403bd73f1b2
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-system-compositor/+bug/1539300/+subscriptions

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

[Touch-packages] [Bug 1676931] Re: logs are not included in unity-system-compositor bugs automatically reported to Ubuntu using apport

[Stephen M. Webb]

** Changed in: unity-system-compositor
Milestone: None => 0.9.2

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

Title:
  logs are not included in unity-system-compositor bugs automatically
  reported to Ubuntu using apport

Status in Canonical System Image:
  In Progress
Status in Unity System Compositor:
  In Progress
Status in unity-system-compositor package in Ubuntu:
  In Progress

Bug description:
  When a crash in unity-system-compositor is automatically reported to
  the Ubuntu bug tracker using the apport tool, additional information
  should be included to make analysis easier.

  At the very least, /var/log/lightdm/unity-system-compositor.log should
  be included.

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

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

[Touch-packages] [Bug 1640320] Re: FTBFS in zesty

[Thomas Voß]

** Branch linked: lp:~thomas-voss/location-service/fix-zesty-ftbfs

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

Title:
  FTBFS in zesty

Status in location-service package in Ubuntu:
  In Progress

Bug description:
  FTBFS in zesty during a no change rebuild against new boost

  Please see build logs at: https://launchpad.net/ubuntu/+source
  /location-service/3.0.0+16.10.20160912-0ubuntu2

  Please help fix this

  [ 10%] Building CXX object 
src/location_service/com/ubuntu/location/CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
  cd 
/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service/com/ubuntu/location
 && /usr/bin/g++   -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_NET_CPP=1 
-DCOM_UBUNTU_LOCATION_SERVICE_HAVE_UBUNTU_PLATFORM_HARDWARE_API 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GEOCLUE 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GPS 
-Dubuntu_location_service_connectivity_EXPORTS 
-I/<>/location-service-3.0.0+16.10.20160912/3rd-party 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/json-c 
-I/<>/location-service-3.0.0+16.10.20160912/include/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/src/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service
 -I/usr/include/ubuntu  -g -O2 
-fdebug-prefix-map=/<>/location-service-3.0.0+16.10.20160912=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -Wall -fno-strict-aliasing -pedantic -Wextra 
-fPIC -Wno-error=unused-local-typedefs -fPIC   -o 
CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
 -c 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/connectivity/wireless_network.cpp
  In file included from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.h:21:0,
   from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.cpp:19:
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:57:14:
 error: ‘vector’ in namespace ‘std’ does not name a template type
   std::vector xtra_hosts
^~
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:59:10:
 warning: extra ‘;’ [-Wpedantic]
   };
^
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:66:18:
 error: ‘vector’ in namespace ‘std’ does not name a template type
   virtual std::vector download_xtra_data(const Configuration& 
config) = 0;
^~
  make -f po/CMakeFiles/pofiles_70.dir/build.make 
po/CMakeFiles/pofiles_70.dir/depend

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

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

[Touch-packages] [Bug 1222053] Re: per-session gsettings overrides

[Launchpad Bug Tracker]

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

** Changed in: glib2.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  per-session gsettings overrides

Status in GLib:
  Won't Fix
Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  There have been several occasions now where Ubuntu GNOME has had to
  patch code, that could in theory instead be handled by per-session
  gsettings overrides. A recent example is the background plugin in
  gnome-settings-daemon (LP: #1219148), this should be loaded under
  unity, gnome-flashback sessions but not gnome-shell session. A per-
  session override would make this possible without any patches to the
  codebase.

  As I understand it the overrides are processed by glib-compile-schemas
  so perhaps we would have to recompile schemas on each login to achieve
  this? Any thoughts on how we can achieve this?

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

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

[Touch-packages] [Bug 1669524] Re: GTK window functions `Always on Top, Move and Resize' don't work in Mir/Unity8

[Alan Griffiths]

** Branch linked: lp:~alan-griffiths/mir/server-support-for-client-
initiates-move

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

Title:
  GTK window functions `Always on Top, Move and Resize' don't work in
  Mir/Unity8

Status in Canonical System Image:
  In Progress
Status in Mir:
  In Progress
Status in MirAL:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Triaged
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 17.04 unity8
  [unity8] Always on Top, Move and Resize doesn't work

  open solitaire, right click on the title bar (see attachement) and
  then select Always on Top. the app doesn't stay on top. same with Move
  and Resize, does nothing

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

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

[Touch-packages] [Bug 1188475] Re: ldap group doesn't work

[sles]

Hello!

I created pull request in cyrus sasl repository
https://github.com/cyrusimap/cyrus-sasl/pull/428

If you don't patch debian packages, then why debian should do this,
let cyrus developers fix it ;-)

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

Title:
  ldap group doesn't work

Status in cyrus-sasl2 package in Ubuntu:
  Triaged

Bug description:
  Hello!

  I wrote almost the same mail to sasl mail list, but , I guess, it is
  good to fix in 12.04...

  This bug exists in 2.1.26 , and in 2.1.25 which is in 12.04

  Problem is that after user is authentificated with ldap bind , ldap 
  connection for checking user in group ( lak_group_member function )
  is made with this user's bind, not bind parameters from config file.
  User can not ( and have not in our case- I don't know why , but this is 
  not real problem ) have access to ldap groups.
  And so, authentication is always fail.

  I added unbind and anonymous bind ( enough in our case):

  /var/local/files/sasl/cyrus-sasl-2.1.26/saslauthd# diff -ur lak.c.orig 
  lak.c
  --- lak.c.orig2013-06-07 09:15:20.098788278 +0400
  +++ lak.c2013-06-07 09:22:31.504774185 +0400
  @@ -1342,6 +1342,10 @@
   if (rc != LAK_OK)
   goto done;

  +lak_unbind (lak );
  +rc  = lak_bind(lak, "");
  +
  +
   rc = ldap_search_st(lak->ld, group_search_base, 
  lak->conf->group_scope, group_filter, (char **) group_attrs, 0, 
  &(lak->conf->timeout), );
   switch (rc) {
   case LDAP_SUCCESS:

  
  but, it is obvoius that rebind should be done with credintials from 
  config, but this is over my head :-(

  Could you, please, fix this bug correctly?

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1188475/+subscriptions

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

[Touch-packages] [Bug 1649213] Re: Support rootfs on xhci-plat-hcd attached storage

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.103ubuntu4.7

---
initramfs-tools (0.103ubuntu4.7) trusty; urgency=medium

  * hook-functions: copy xhci-plat-hcd also.
(LP: #1649213)

 -- Ike Panhc   Tue, 10 Jan 2017 12:31:44 +0800

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

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

Title:
  Support rootfs on xhci-plat-hcd attached storage

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Trusty:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Zesty:
  Invalid

Bug description:
  [Impact]
  If you install Ubuntu onto USB storage behind a Platform USB host controller, 
it will not be able to boot because the generated initramfs will not include 
the host controller driver.

  [Test Case]
  Install to a USB stick attached to platform USB controller and reboot. 
Booting will fail because it will be unable to find the root file system.

  [Regression Risk]
  Driver is only loaded when system requires xhci-plat-hcd, minimizing the 
impact to all other systems.

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

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

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

[Dan Streetman]

I created a PPA with fixed vlan packages:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1573272


** Tags removed: bot-comment patch xenial
** Tags added: sts-sponsor

** Tags added: patch

** Also affects: vlan (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859127
   Importance: Unknown
   Status: Unknown

** No longer affects: ifupdown (Ubuntu)

** Changed in: vlan (Ubuntu)
   Importance: High => Medium

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

Title:
  default gateway route not installed for bond interfaces through reboot

Status in vlan package in Ubuntu:
  In Progress
Status in vlan package in Debian:
  Unknown

Bug description:
  [Impact]

  Systems using vlans, especially those using vlans on top of bond
  interfaces, in addition to default or other routes on the vlans, may
  find their vlan routes are not present at boot.

  The attached debdiff patches fix the vlan package's /etc/network/if-
  pre-up.d/vlan script.  Currently, the script will bring up a vlan's
  raw device if needed; but the problem is if the vlan's ifup processing
  happens before the raw device's ifup processing, the raw device may be
  taken down and back up (especially for bonds), and when the raw device
  is taken down, the vlan is as well, and thus loses all its routing
  configuration.  Instead of only bringing the raw device up using ip
  link up, the patch changes the vlan script to do a full ifup on the
  raw device, so it will remain up after the vlan is configured.

  [Test Case]

  Set up a system using two interfaces configured into a bond interface,
  with a vlan on top of that bond.  Add a default route and/or specific
  routes to the vlan interface.  Then edit the system as described in
  comment 8, and reboot.  The vlan's routes will not be present in the
  system.

  [Regression Potential]

  Any modifications to ifupdown or the scripts it uses may cause wider
  problems with network configuration.  Specifically, this could cause
  problems when using vlan interfaces, as it forces every vlan's raw
  device interface to be fully ifup'ed before the vlan interface can
  finish its ifup.

  [Other Info]

  original description below:

  
  Expectation:  After reboot, route for default gateway specified on bonded 
interface is installed according to "gateway x.x.x.x"  (where x.x.x.x is a 
valid IPv4 address) specified in /etc/network/interfaces or files sourced per 
/etc/network/interfaces

  Actual Result: After reboot, route is not installed. Interface does
  work otherwise (I can ping the gateway on that subnet, for instance).
  'ifdown -a' followed by  'ifup -a' (run with proper permission... so
  sudo) brings the gateway back until next reboot.

  Package:  I'm not familiar enough to be certain what is causing this,
  but I was seeing this in beta2 of 16.04 as well.

  *username snipped*@*hostname snipped*:~$ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04
  *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave
  ifenslave:
    Installed: 2.7ubuntu1
    Candidate: 2.7ubuntu1
    Version table:
   *** 2.7ubuntu1 100
  100 /var/lib/dpkg/status

  *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown
  ifupdown:
    Installed: 0.8.10ubuntu1
    Candidate: 0.8.10ubuntu1
    Version table:
   *** 0.8.10ubuntu1 100
  100 /var/lib/dpkg/status

    /etc/network/interfaces

  --
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto enp2s0f1
  iface enp2s0f1 inet manual
  bond-master bond0

  auto enp2s0f0
  iface enp2s0f0 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  address 10.96.96.2
  netmask 255.255.255.0
  network 10.96.96.0
  broadcast 10.96.96.255
  # dns-* options are implemented by the resolvconf package, if 
installed
  dns-search *snip*
  bond-mode balance-alb
  bond-slaves none
  bond-miimon 100
  auto bond0.3000
  iface bond0.3000 inet static
  address 172.21.33.29
  netmask 255.255.255.0
  network 172.21.33.0
  broadcast 172.21.33.255
  gateway 172.21.33.1
  dns-search *snip*
  vlan-raw-device bond0
  dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2

  -
  interfaces.d is empty:

  *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d
  total 8.0K
  10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 .
  10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 ..

To 

[Touch-packages] [Bug 1573307] Update Released

[Brian Murray]

The verification of the Stable Release Update for wget 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 wget in Ubuntu.
https://bugs.launchpad.net/bugs/1573307

Title:
  wget crashed with SIGSEGV in __memset_avx2()

Status in wget package in Ubuntu:
  Fix Released
Status in wget source package in Xenial:
  Fix Released

Bug description:
  [Impact] 
   * wget will crash while displaying progress bar under narrow terminal
   * Upstream already has fixed this issue in commit 7099f489 and 7cb9efa6
  Steps to reproduce:
1. execute "wget 
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-desktop-amd64.manifest;
 under a narrow terminal (such as width less than 40 characters)
  Problems:
1. The wget crash with segmentation fault
  Expected behavior:
1. wget will not crash

  [Test Case]
After upgrading to the new version, the repeating the above steps should 
give expected behavior.

  [Regression Potential]
Potential of causing regression is relatively small for a two line change 
for assertion check

  [Other Info]



  EDIT(other user): The crash actually happens when the terminal window
  is too small.

  When I try to download a big file with wget on Ubuntu 16.04 it crashes
  after a couple seconds.

  To reproduce the bug try the following:

  wget http://releases.ubuntu.com/16.04/ubuntu-16.04-desktop-amd64.iso

  I've asked another guy on IRC on channel #ubuntu-it to try and reproduce this 
bug
  and he said it was crashing also on his machine.

  evan@HPPC:~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  evan@HPPC:~$ apt-cache policy wget
  wget:
    Installato: 1.17.1-1ubuntu1
    Candidato:  1.17.1-1ubuntu1
    Tabella versione:
   *** 1.17.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: wget 1.17.1-1ubuntu1
  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
  CurrentDesktop: Unity
  Date: Fri Apr 22 01:34:10 2016
  ExecutablePath: /usr/bin/wget
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: wget 
http://releases.ubuntu.com/16.04/ubuntu-16.04-desktop-amd64.iso
  SegvAnalysis:
   Segfault happened at: 0x7f4eac3b7328 <__memset_avx2+392>:rep stos 
%al,%es:(%rdi)
   PC (0x7f4eac3b7328) ok
   source "%al" ok
   destination "%es:(%rdi)" (0x562969134000) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: wget
  StacktraceTop:
   __memset_avx2 () at ../sysdeps/x86_64/multiarch/memset-avx2.S:161
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: wget crashed with SIGSEGV in __memset_avx2()
  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/wget/+bug/1573307/+subscriptions

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

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

[Dan Streetman]

** Description changed:

- Expectation:  After reboot, route for default gateway specified on
- bonded interface is installed according to "gateway x.x.x.x"  (where
- x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or
- files sourced per /etc/network/interfaces
+ [Impact]
+ 
+ Systems using vlans, especially those using vlans on top of bond
+ interfaces, in addition to default or other routes on the vlans, may
+ find their vlan routes are not present at boot.
+ 
+ The attached debdiff patches fix the vlan package's /etc/network/if-pre-
+ up.d/vlan script.  Currently, the script will bring up a vlan's raw
+ device if needed; but the problem is if the vlan's ifup processing
+ happens before the raw device's ifup processing, the raw device may be
+ taken down and back up (especially for bonds), and when the raw device
+ is taken down, the vlan is as well, and thus loses all its routing
+ configuration.  Instead of only bringing the raw device up using ip link
+ up, the patch changes the vlan script to do a full ifup on the raw
+ device, so it will remain up after the vlan is configured.
+ 
+ [Test Case]
+ 
+ Set up a system using two interfaces configured into a bond interface,
+ with a vlan on top of that bond.  Add a default route and/or specific
+ routes to the vlan interface.  Then edit the system as described in
+ comment 8, and reboot.  The vlan's routes will not be present in the
+ system.
+ 
+ [Regression Potential]
+ 
+ Any modifications to ifupdown or the scripts it uses may cause wider
+ problems with network configuration.  Specifically, this could cause
+ problems when using vlan interfaces, as it forces every vlan's raw
+ device interface to be fully ifup'ed before the vlan interface can
+ finish its ifup.
+ 
+ [Other Info]
+ 
+ original description below:
+ 
+ 
+ Expectation:  After reboot, route for default gateway specified on bonded 
interface is installed according to "gateway x.x.x.x"  (where x.x.x.x is a 
valid IPv4 address) specified in /etc/network/interfaces or files sourced per 
/etc/network/interfaces
  
  Actual Result: After reboot, route is not installed. Interface does work
  otherwise (I can ping the gateway on that subnet, for instance).
  'ifdown -a' followed by  'ifup -a' (run with proper permission... so
  sudo) brings the gateway back until next reboot.
  
  Package:  I'm not familiar enough to be certain what is causing this,
  but I was seeing this in beta2 of 16.04 as well.
  
  *username snipped*@*hostname snipped*:~$ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04
  *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave
  ifenslave:
-   Installed: 2.7ubuntu1
-   Candidate: 2.7ubuntu1
-   Version table:
-  *** 2.7ubuntu1 100
- 100 /var/lib/dpkg/status
+   Installed: 2.7ubuntu1
+   Candidate: 2.7ubuntu1
+   Version table:
+  *** 2.7ubuntu1 100
+ 100 /var/lib/dpkg/status
  
  *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown
  ifupdown:
-   Installed: 0.8.10ubuntu1
-   Candidate: 0.8.10ubuntu1
-   Version table:
-  *** 0.8.10ubuntu1 100
- 100 /var/lib/dpkg/status
- 
- 
-   
+   Installed: 0.8.10ubuntu1
+   Candidate: 0.8.10ubuntu1
+   Version table:
+  *** 0.8.10ubuntu1 100
+ 100 /var/lib/dpkg/status
  
- 
- 
- 
-   /etc/network/interfaces
+   /etc/network/interfaces
  
  --
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).
  
  source /etc/network/interfaces.d/*
  
  # The loopback network interface
  auto lo
  iface lo inet loopback
  
  # The primary network interface
  auto enp2s0f1
  iface enp2s0f1 inet manual
  bond-master bond0
  
  auto enp2s0f0
  iface enp2s0f0 inet manual
  bond-master bond0
  
  auto bond0
  iface bond0 inet static
- address 10.96.96.2
- netmask 255.255.255.0
- network 10.96.96.0
- broadcast 10.96.96.255
- # dns-* options are implemented by the resolvconf package, if 
installed
- dns-search *snip*
- bond-mode balance-alb
- bond-slaves none
- bond-miimon 100
- auto bond0.3000 
+ address 10.96.96.2
+ netmask 255.255.255.0
+ network 10.96.96.0
+ broadcast 10.96.96.255
+ # dns-* options are implemented by the resolvconf package, if 
installed
+ dns-search *snip*
+ bond-mode balance-alb
+ bond-slaves none
+ bond-miimon 100
+ auto bond0.3000
  iface bond0.3000 inet static
- address 172.21.33.29
- netmask 255.255.255.0
- network 172.21.33.0
- broadcast 172.21.33.255
- gateway 172.21.33.1
- dns-search *snip*
- vlan-raw-device bond0
- dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2
- 
+ address 172.21.33.29
+ netmask 255.255.255.0
+ network 172.21.33.0
+    

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

[Ubuntu Foundations Team Bug Bot]

The attachment "lp1573272-trusty.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

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

Title:
  default gateway route not installed for bond interfaces through reboot

Status in vlan package in Ubuntu:
  In Progress
Status in vlan package in Debian:
  Unknown

Bug description:
  [Impact]

  Systems using vlans, especially those using vlans on top of bond
  interfaces, in addition to default or other routes on the vlans, may
  find their vlan routes are not present at boot.

  The attached debdiff patches fix the vlan package's /etc/network/if-
  pre-up.d/vlan script.  Currently, the script will bring up a vlan's
  raw device if needed; but the problem is if the vlan's ifup processing
  happens before the raw device's ifup processing, the raw device may be
  taken down and back up (especially for bonds), and when the raw device
  is taken down, the vlan is as well, and thus loses all its routing
  configuration.  Instead of only bringing the raw device up using ip
  link up, the patch changes the vlan script to do a full ifup on the
  raw device, so it will remain up after the vlan is configured.

  [Test Case]

  Set up a system using two interfaces configured into a bond interface,
  with a vlan on top of that bond.  Add a default route and/or specific
  routes to the vlan interface.  Then edit the system as described in
  comment 8, and reboot.  The vlan's routes will not be present in the
  system.

  [Regression Potential]

  Any modifications to ifupdown or the scripts it uses may cause wider
  problems with network configuration.  Specifically, this could cause
  problems when using vlan interfaces, as it forces every vlan's raw
  device interface to be fully ifup'ed before the vlan interface can
  finish its ifup.

  [Other Info]

  original description below:

  
  Expectation:  After reboot, route for default gateway specified on bonded 
interface is installed according to "gateway x.x.x.x"  (where x.x.x.x is a 
valid IPv4 address) specified in /etc/network/interfaces or files sourced per 
/etc/network/interfaces

  Actual Result: After reboot, route is not installed. Interface does
  work otherwise (I can ping the gateway on that subnet, for instance).
  'ifdown -a' followed by  'ifup -a' (run with proper permission... so
  sudo) brings the gateway back until next reboot.

  Package:  I'm not familiar enough to be certain what is causing this,
  but I was seeing this in beta2 of 16.04 as well.

  *username snipped*@*hostname snipped*:~$ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04
  *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave
  ifenslave:
    Installed: 2.7ubuntu1
    Candidate: 2.7ubuntu1
    Version table:
   *** 2.7ubuntu1 100
  100 /var/lib/dpkg/status

  *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown
  ifupdown:
    Installed: 0.8.10ubuntu1
    Candidate: 0.8.10ubuntu1
    Version table:
   *** 0.8.10ubuntu1 100
  100 /var/lib/dpkg/status

    /etc/network/interfaces

  --
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto enp2s0f1
  iface enp2s0f1 inet manual
  bond-master bond0

  auto enp2s0f0
  iface enp2s0f0 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  address 10.96.96.2
  netmask 255.255.255.0
  network 10.96.96.0
  broadcast 10.96.96.255
  # dns-* options are implemented by the resolvconf package, if 
installed
  dns-search *snip*
  bond-mode balance-alb
  bond-slaves none
  bond-miimon 100
  auto bond0.3000
  iface bond0.3000 inet static
  address 172.21.33.29
  netmask 255.255.255.0
  network 172.21.33.0
  broadcast 172.21.33.255
  gateway 172.21.33.1
  dns-search *snip*
  vlan-raw-device bond0
  dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2

  -
  interfaces.d is empty:

  *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d
  total 8.0K
  10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 

[Touch-packages] [Bug 1573307] Re: wget crashed with SIGSEGV in __memset_avx2()

[Launchpad Bug Tracker]

This bug was fixed in the package wget - 1.17.1-1ubuntu1.2

---
wget (1.17.1-1ubuntu1.2) xenial-proposed; urgency=medium

  * debian/patches/Sanitize-value-sent-to-memset-to-prevent-SEGFAULT.patch
upstream commited 7099f489 patch to fix segmentation fault (LP: #1573307)

 -- Chen-Han Hsiao (Stanley)   Fri, 24 Feb
2017 12:24:53 -0800

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

Title:
  wget crashed with SIGSEGV in __memset_avx2()

Status in wget package in Ubuntu:
  Fix Released
Status in wget source package in Xenial:
  Fix Released

Bug description:
  [Impact] 
   * wget will crash while displaying progress bar under narrow terminal
   * Upstream already has fixed this issue in commit 7099f489 and 7cb9efa6
  Steps to reproduce:
1. execute "wget 
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-desktop-amd64.manifest;
 under a narrow terminal (such as width less than 40 characters)
  Problems:
1. The wget crash with segmentation fault
  Expected behavior:
1. wget will not crash

  [Test Case]
After upgrading to the new version, the repeating the above steps should 
give expected behavior.

  [Regression Potential]
Potential of causing regression is relatively small for a two line change 
for assertion check

  [Other Info]



  EDIT(other user): The crash actually happens when the terminal window
  is too small.

  When I try to download a big file with wget on Ubuntu 16.04 it crashes
  after a couple seconds.

  To reproduce the bug try the following:

  wget http://releases.ubuntu.com/16.04/ubuntu-16.04-desktop-amd64.iso

  I've asked another guy on IRC on channel #ubuntu-it to try and reproduce this 
bug
  and he said it was crashing also on his machine.

  evan@HPPC:~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  evan@HPPC:~$ apt-cache policy wget
  wget:
    Installato: 1.17.1-1ubuntu1
    Candidato:  1.17.1-1ubuntu1
    Tabella versione:
   *** 1.17.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: wget 1.17.1-1ubuntu1
  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
  CurrentDesktop: Unity
  Date: Fri Apr 22 01:34:10 2016
  ExecutablePath: /usr/bin/wget
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: wget 
http://releases.ubuntu.com/16.04/ubuntu-16.04-desktop-amd64.iso
  SegvAnalysis:
   Segfault happened at: 0x7f4eac3b7328 <__memset_avx2+392>:rep stos 
%al,%es:(%rdi)
   PC (0x7f4eac3b7328) ok
   source "%al" ok
   destination "%es:(%rdi)" (0x562969134000) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: wget
  StacktraceTop:
   __memset_avx2 () at ../sysdeps/x86_64/multiarch/memset-avx2.S:161
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: wget crashed with SIGSEGV in __memset_avx2()
  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/wget/+bug/1573307/+subscriptions

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

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

[Dan Streetman]

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

** Bug watch added: Debian Bug tracker #859127
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859127

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

Title:
  default gateway route not installed for bond interfaces through reboot

Status in ifupdown package in Ubuntu:
  Invalid
Status in vlan package in Ubuntu:
  In Progress

Bug description:
  [Impact]

  Systems using vlans, especially those using vlans on top of bond
  interfaces, in addition to default or other routes on the vlans, may
  find their vlan routes are not present at boot.

  The attached debdiff patches fix the vlan package's /etc/network/if-
  pre-up.d/vlan script.  Currently, the script will bring up a vlan's
  raw device if needed; but the problem is if the vlan's ifup processing
  happens before the raw device's ifup processing, the raw device may be
  taken down and back up (especially for bonds), and when the raw device
  is taken down, the vlan is as well, and thus loses all its routing
  configuration.  Instead of only bringing the raw device up using ip
  link up, the patch changes the vlan script to do a full ifup on the
  raw device, so it will remain up after the vlan is configured.

  [Test Case]

  Set up a system using two interfaces configured into a bond interface,
  with a vlan on top of that bond.  Add a default route and/or specific
  routes to the vlan interface.  Then edit the system as described in
  comment 8, and reboot.  The vlan's routes will not be present in the
  system.

  [Regression Potential]

  Any modifications to ifupdown or the scripts it uses may cause wider
  problems with network configuration.  Specifically, this could cause
  problems when using vlan interfaces, as it forces every vlan's raw
  device interface to be fully ifup'ed before the vlan interface can
  finish its ifup.

  [Other Info]

  original description below:

  
  Expectation:  After reboot, route for default gateway specified on bonded 
interface is installed according to "gateway x.x.x.x"  (where x.x.x.x is a 
valid IPv4 address) specified in /etc/network/interfaces or files sourced per 
/etc/network/interfaces

  Actual Result: After reboot, route is not installed. Interface does
  work otherwise (I can ping the gateway on that subnet, for instance).
  'ifdown -a' followed by  'ifup -a' (run with proper permission... so
  sudo) brings the gateway back until next reboot.

  Package:  I'm not familiar enough to be certain what is causing this,
  but I was seeing this in beta2 of 16.04 as well.

  *username snipped*@*hostname snipped*:~$ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04
  *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave
  ifenslave:
    Installed: 2.7ubuntu1
    Candidate: 2.7ubuntu1
    Version table:
   *** 2.7ubuntu1 100
  100 /var/lib/dpkg/status

  *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown
  ifupdown:
    Installed: 0.8.10ubuntu1
    Candidate: 0.8.10ubuntu1
    Version table:
   *** 0.8.10ubuntu1 100
  100 /var/lib/dpkg/status

    /etc/network/interfaces

  --
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto enp2s0f1
  iface enp2s0f1 inet manual
  bond-master bond0

  auto enp2s0f0
  iface enp2s0f0 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  address 10.96.96.2
  netmask 255.255.255.0
  network 10.96.96.0
  broadcast 10.96.96.255
  # dns-* options are implemented by the resolvconf package, if 
installed
  dns-search *snip*
  bond-mode balance-alb
  bond-slaves none
  bond-miimon 100
  auto bond0.3000
  iface bond0.3000 inet static
  address 172.21.33.29
  netmask 255.255.255.0
  network 172.21.33.0
  broadcast 172.21.33.255
  gateway 172.21.33.1
  dns-search *snip*
  vlan-raw-device bond0
  dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2

  -
  interfaces.d is empty:

  *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d
  total 8.0K
  10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 .
  10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 ..

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

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

[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

[Alberto Salvia Novella]

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

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

[Dan Streetman]

** Patch added: "lp1573272-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850618/+files/lp1573272-xenial.debdiff

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

Title:
  default gateway route not installed for bond interfaces through reboot

Status in ifupdown package in Ubuntu:
  Invalid
Status in vlan package in Ubuntu:
  In Progress

Bug description:
  Expectation:  After reboot, route for default gateway specified on
  bonded interface is installed according to "gateway x.x.x.x"  (where
  x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces
  or files sourced per /etc/network/interfaces

  Actual Result: After reboot, route is not installed. Interface does
  work otherwise (I can ping the gateway on that subnet, for instance).
  'ifdown -a' followed by  'ifup -a' (run with proper permission... so
  sudo) brings the gateway back until next reboot.

  Package:  I'm not familiar enough to be certain what is causing this,
  but I was seeing this in beta2 of 16.04 as well.

  *username snipped*@*hostname snipped*:~$ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04
  *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave
  ifenslave:
Installed: 2.7ubuntu1
Candidate: 2.7ubuntu1
Version table:
   *** 2.7ubuntu1 100
  100 /var/lib/dpkg/status

  *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown
  ifupdown:
Installed: 0.8.10ubuntu1
Candidate: 0.8.10ubuntu1
Version table:
   *** 0.8.10ubuntu1 100
  100 /var/lib/dpkg/status
  
  




  
/etc/network/interfaces

  --
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto enp2s0f1
  iface enp2s0f1 inet manual
  bond-master bond0

  auto enp2s0f0
  iface enp2s0f0 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  address 10.96.96.2
  netmask 255.255.255.0
  network 10.96.96.0
  broadcast 10.96.96.255
  # dns-* options are implemented by the resolvconf package, if 
installed
  dns-search *snip*
  bond-mode balance-alb
  bond-slaves none
  bond-miimon 100
  auto bond0.3000 
  iface bond0.3000 inet static
  address 172.21.33.29
  netmask 255.255.255.0
  network 172.21.33.0
  broadcast 172.21.33.255
  gateway 172.21.33.1
  dns-search *snip*
  vlan-raw-device bond0
  dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2
  
  -
  interfaces.d is empty:

  *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d
  total 8.0K
  10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 .
  10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 ..

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

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

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

[Dan Streetman]

** Patch added: "lp1573272-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850619/+files/lp1573272-yakkety.debdiff

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

Title:
  default gateway route not installed for bond interfaces through reboot

Status in ifupdown package in Ubuntu:
  Invalid
Status in vlan package in Ubuntu:
  In Progress

Bug description:
  Expectation:  After reboot, route for default gateway specified on
  bonded interface is installed according to "gateway x.x.x.x"  (where
  x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces
  or files sourced per /etc/network/interfaces

  Actual Result: After reboot, route is not installed. Interface does
  work otherwise (I can ping the gateway on that subnet, for instance).
  'ifdown -a' followed by  'ifup -a' (run with proper permission... so
  sudo) brings the gateway back until next reboot.

  Package:  I'm not familiar enough to be certain what is causing this,
  but I was seeing this in beta2 of 16.04 as well.

  *username snipped*@*hostname snipped*:~$ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04
  *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave
  ifenslave:
Installed: 2.7ubuntu1
Candidate: 2.7ubuntu1
Version table:
   *** 2.7ubuntu1 100
  100 /var/lib/dpkg/status

  *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown
  ifupdown:
Installed: 0.8.10ubuntu1
Candidate: 0.8.10ubuntu1
Version table:
   *** 0.8.10ubuntu1 100
  100 /var/lib/dpkg/status
  
  




  
/etc/network/interfaces

  --
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto enp2s0f1
  iface enp2s0f1 inet manual
  bond-master bond0

  auto enp2s0f0
  iface enp2s0f0 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  address 10.96.96.2
  netmask 255.255.255.0
  network 10.96.96.0
  broadcast 10.96.96.255
  # dns-* options are implemented by the resolvconf package, if 
installed
  dns-search *snip*
  bond-mode balance-alb
  bond-slaves none
  bond-miimon 100
  auto bond0.3000 
  iface bond0.3000 inet static
  address 172.21.33.29
  netmask 255.255.255.0
  network 172.21.33.0
  broadcast 172.21.33.255
  gateway 172.21.33.1
  dns-search *snip*
  vlan-raw-device bond0
  dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2
  
  -
  interfaces.d is empty:

  *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d
  total 8.0K
  10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 .
  10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 ..

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

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

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

[Dan Streetman]

** Patch added: "lp1573272-zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850620/+files/lp1573272-zesty.debdiff

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

Title:
  default gateway route not installed for bond interfaces through reboot

Status in ifupdown package in Ubuntu:
  Invalid
Status in vlan package in Ubuntu:
  In Progress

Bug description:
  Expectation:  After reboot, route for default gateway specified on
  bonded interface is installed according to "gateway x.x.x.x"  (where
  x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces
  or files sourced per /etc/network/interfaces

  Actual Result: After reboot, route is not installed. Interface does
  work otherwise (I can ping the gateway on that subnet, for instance).
  'ifdown -a' followed by  'ifup -a' (run with proper permission... so
  sudo) brings the gateway back until next reboot.

  Package:  I'm not familiar enough to be certain what is causing this,
  but I was seeing this in beta2 of 16.04 as well.

  *username snipped*@*hostname snipped*:~$ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04
  *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave
  ifenslave:
Installed: 2.7ubuntu1
Candidate: 2.7ubuntu1
Version table:
   *** 2.7ubuntu1 100
  100 /var/lib/dpkg/status

  *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown
  ifupdown:
Installed: 0.8.10ubuntu1
Candidate: 0.8.10ubuntu1
Version table:
   *** 0.8.10ubuntu1 100
  100 /var/lib/dpkg/status
  
  




  
/etc/network/interfaces

  --
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto enp2s0f1
  iface enp2s0f1 inet manual
  bond-master bond0

  auto enp2s0f0
  iface enp2s0f0 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  address 10.96.96.2
  netmask 255.255.255.0
  network 10.96.96.0
  broadcast 10.96.96.255
  # dns-* options are implemented by the resolvconf package, if 
installed
  dns-search *snip*
  bond-mode balance-alb
  bond-slaves none
  bond-miimon 100
  auto bond0.3000 
  iface bond0.3000 inet static
  address 172.21.33.29
  netmask 255.255.255.0
  network 172.21.33.0
  broadcast 172.21.33.255
  gateway 172.21.33.1
  dns-search *snip*
  vlan-raw-device bond0
  dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2
  
  -
  interfaces.d is empty:

  *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d
  total 8.0K
  10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 .
  10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 ..

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

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

[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot

[Dan Streetman]

** Patch added: "lp1573272-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+attachment/4850617/+files/lp1573272-trusty.debdiff

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

Title:
  default gateway route not installed for bond interfaces through reboot

Status in ifupdown package in Ubuntu:
  Invalid
Status in vlan package in Ubuntu:
  In Progress

Bug description:
  Expectation:  After reboot, route for default gateway specified on
  bonded interface is installed according to "gateway x.x.x.x"  (where
  x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces
  or files sourced per /etc/network/interfaces

  Actual Result: After reboot, route is not installed. Interface does
  work otherwise (I can ping the gateway on that subnet, for instance).
  'ifdown -a' followed by  'ifup -a' (run with proper permission... so
  sudo) brings the gateway back until next reboot.

  Package:  I'm not familiar enough to be certain what is causing this,
  but I was seeing this in beta2 of 16.04 as well.

  *username snipped*@*hostname snipped*:~$ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04
  *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave
  ifenslave:
Installed: 2.7ubuntu1
Candidate: 2.7ubuntu1
Version table:
   *** 2.7ubuntu1 100
  100 /var/lib/dpkg/status

  *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown
  ifupdown:
Installed: 0.8.10ubuntu1
Candidate: 0.8.10ubuntu1
Version table:
   *** 0.8.10ubuntu1 100
  100 /var/lib/dpkg/status
  
  




  
/etc/network/interfaces

  --
  # This file describes the network interfaces available on your system
  # and how to activate them. For more information, see interfaces(5).

  source /etc/network/interfaces.d/*

  # The loopback network interface
  auto lo
  iface lo inet loopback

  # The primary network interface
  auto enp2s0f1
  iface enp2s0f1 inet manual
  bond-master bond0

  auto enp2s0f0
  iface enp2s0f0 inet manual
  bond-master bond0

  auto bond0
  iface bond0 inet static
  address 10.96.96.2
  netmask 255.255.255.0
  network 10.96.96.0
  broadcast 10.96.96.255
  # dns-* options are implemented by the resolvconf package, if 
installed
  dns-search *snip*
  bond-mode balance-alb
  bond-slaves none
  bond-miimon 100
  auto bond0.3000 
  iface bond0.3000 inet static
  address 172.21.33.29
  netmask 255.255.255.0
  network 172.21.33.0
  broadcast 172.21.33.255
  gateway 172.21.33.1
  dns-search *snip*
  vlan-raw-device bond0
  dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2
  
  -
  interfaces.d is empty:

  *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d
  total 8.0K
  10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 .
  10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 ..

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

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

[Touch-packages] [Bug 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed

[Till Kamppeter]

ophion, try the following:

sudo dpkg -P --force-depends libcups2

This will remove libcups2 without moving anything else, but now many
applications in your system will not work. DO NOT REBOOT.

Now do

sudo apt-get install -f

How does this try to fix your system? Get libcups2 from the repos? Or
remove half the system?

In the former case simply go on so that you get the old libcups2 from
the download miror. In the latter case, do not go on. Try

sudo apt-get install -f libcups2

Please tell whether this helps and how it helped. Please post any
terminal output.

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

Title:
  cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be
  installed

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This is related to this bug
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790

  After `sudo apt-get -f install`, it removed cups and marked a bunch of
  cups packages as unnecessary

  `sudo apt-get autoremove` removed them.

  Now when I try to re-install cups, I get this error:

  ```
  ☀  sudo apt-get install cups cups-daemon cups-core-drivers
  Mod master
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
  Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed
  Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed
  Recommends: printer-driver-gutenprint but it is not going to be 
installed
   cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to 
be installed
   cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be 
installed
 Depends: libcupsmime1 (>= 1.5.0) but it is not going to be 
installed
 Recommends: cups-browsed but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  ```

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

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

[Touch-packages] [Bug 1677667] [NEW] package linux-image-extra-4.4.0-64-generic 4.4.0-64.85 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Alejandro Arcos]

Public bug reported:

the problem appears after reboot system

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-64-generic 4.4.0-64.85
ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
Uname: Linux 4.4.0-71-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
  USERPID ACCESS COMMAND
 /dev/snd/controlC0:  administrador   1594 F pulseaudio
Date: Thu Mar 30 12:41:47 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=f2970602-8d5d-4112-811b-547f53012e43
PccardctlIdent: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload 
cannot be preloaded (cannot open shared object file): ignored.
PccardctlStatus: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload 
cannot be preloaded (cannot open shared object file): ignored.
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=646bc068-284c-4372-9187-99883ca0face ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: ERROR: ld.so: object 
'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open 
shared object file): ignored.
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.8
RfKill: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot 
be preloaded (cannot open shared object file): ignored.
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.4.0-64-generic 4.4.0-64.85 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: DPP3510J.86A.0572.2009.0715.2346
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DP35DP
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD81073-205
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0572.2009.0715.2346:bd07/15/2009:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-205:cvn:ct3:cvr:

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-extra-4.4.0-64-generic 4.4.0-64.85 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  the problem appears after reboot system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  administrador   1594 F pulseaudio
  Date: Thu Mar 30 12:41:47 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=f2970602-8d5d-4112-811b-547f53012e43
  PccardctlIdent: ERROR: ld.so: object 'libesets_pac.so' from 
/etc/ld.so.preload cannot be preloaded (cannot open shared object file): 
ignored.
  PccardctlStatus: ERROR: ld.so: object 'libesets_pac.so' from 
/etc/ld.so.preload cannot be preloaded (cannot open shared object file): 
ignored.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=646bc068-284c-4372-9187-99883ca0face ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: ERROR: ld.so: 
object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot 
open shared object file): ignored.
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.8
  RfKill: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot 
be preloaded (cannot open shared object file): ignored.
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-64-generic 4.4.0-64.85 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0572.2009.0715.2346
  dmi.board.asset.tag: Base Board Asset 

[Touch-packages] [Bug 1626425] Re: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()

[Launchpad Bug Tracker]

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

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

Title:
  systemd-resolved crashed with SIGSEGV in sd_event_dispatch()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  issue at startup

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-6git1
  ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep 22 09:37:36 2016
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2013-06-06 (1203 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Dell Inc. Dell System XPS L322X
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic 
root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /lib/systemd/libsystemd-shared-231.so
   sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so
   sd_event_run () from /lib/systemd/libsystemd-shared-231.so
  Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (18 days ago)
  UserGroups:
   
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1645037] Re: apparmor_parser hangs indefinitely when called by multiple threads

[Steve Beattie]

** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-7184

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

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

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

Title:
  apparmor_parser hangs indefinitely when called by multiple threads

Status in apparmor package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Yakkety:
  Triaged
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This bug surfaced when starting ~50 LXC container with LXD in parallel
  multiple times:

  # Create the containers
  for c in c foo{1..50}; do lxc launch images:ubuntu/xenial $c; done

  # Exectute this loop multiple times until you observe errors.
  for c in c foo{1..50}; do lxc restart $c & done

  After this you can

  ps aux | grep apparmor

  and you should see output similar to:

  root 19774  0.0  0.0  12524  1116 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
  root 19775  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
  root 19776  0.0  0.0  13592  3224 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo30
  root 19778  0.0  0.0  13592  3384 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo26
  root 19780  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
  root 19782  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
  root 19783  0.0  0.0  13592  3388 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo43
  root 19784  0.0  0.0  13592  3252 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo34
  root 19794  0.0  0.0  12524  1208 pts/1S+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo25
  root 19795  0.0  0.0  13592  3256 pts/1D+   20:14   0:00 
apparmor_parser -RWL /var/lib/lxd/security/apparmor/cache 
/var/lib/lxd/security/apparmor/profiles/lxd-foo25

  apparmor_parser remains stuck even after all LXC/LXD commands have
  exited.

  dmesg output yields lines like:

  [41902.815174] audit: type=1400 audit(1480191089.678:43):
  apparmor="STATUS" operation="profile_load" profile="unconfined" name
  ="lxd-foo30_" pid=12545 comm="apparmor_parser"

  and cat /proc/12545/stack shows:

  [] aa_remove_profiles+0x88/0x270
  21:19   brauner  [] profile_remove+0x144/0x2e0
  21:19   brauner  [] __vfs_write+0x18/0x40
  21:19   brauner  [] vfs_write+0xb8/0x1b0
  21:19   brauner  [] SyS_write+0x55/0xc0
  21:19   brauner  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  21:19   brauner  [] 0x

  This looks like a potential kernel bug.

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

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