date:20170120

[Expired for Mir because there has been no activity for 60 days.]

** Changed in: mir
   Status: Incomplete => Expired

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

Title:
  Mir is just a black screen and mouse cursor on Nvidia GTX 900 when
  using nouveau

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Expired
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Expired

Bug description:
  Nvidia (using nouveau not binary drivers): Mir servers freeze on
  start-up for 30 seconds, and then you get just a black screen and
  mouse cursor (which at least moves).

  Using lp:mir r3480 ...

  [2016-04-27 15:20:19.369559] mirserver: Selected driver: mir:mesa-kms 
(version 0.22.0)
  nvc0_screen_create:762 - Error allocating PGRAPH context for M2MF: -22
  [2016-04-27 15:20:51.934145] mirserver: Using hardware cursor
  [2016-04-27 15:20:51.937691] mirserver: Initial display configuration:
  [2016-04-27 15:20:51.937703] mirserver:   0.36: unused DVI-I
  [2016-04-27 15:20:51.937713] mirserver:   0.39: DVI-D 24.0" 520x320mm
  [2016-04-27 15:20:51.937722] mirserver: Current mode 1920x1200 59.95Hz
  [2016-04-27 15:20:51.937731] mirserver: Preferred mode 1920x1200 
59.95Hz
  [2016-04-27 15:20:51.937740] mirserver: Logical position +0+0
  [2016-04-27 15:20:51.937781] mirserver:   0.41: unused HDMI-A
  [2016-04-27 15:20:51.937799] mirserver:   0.43: unused DisplayPort
  [2016-04-27 15:20:51.937972] mircommon: Loading modules from: 
bin/../lib/server-modules/
  [2016-04-27 15:20:51.938015] mircommon: Loading module: 
bin/../lib/server-modules/graphics-android.so.9
  [2016-04-27 15:20:51.938107]  mircommon: Failed to load module: 
bin/../lib/server-modules/graphics-android.so.9 (error was:libhardware.so.2: 
cannot open shared object file: No such file or directory)
  [2016-04-27 15:20:51.938119] mircommon: Loading module: 
bin/../lib/server-modules/graphics-mesa-kms.so.9
  [2016-04-27 15:20:51.938142] mircommon: Loading module: 
bin/../lib/server-modules/server-mesa-x11.so.9
  [2016-04-27 15:20:51.938536] mircommon: Loading module: 
bin/../lib/server-modules/input-evdev.so.5
  [2016-04-27 15:20:51.955316] mirserver: Selected input driver: 
mir:evdev-input (version: 0.22.0)
  [2016-04-27 15:20:51.955500] mirserver: Mir version 0.22.0
  [2016-04-27 15:20:51.962627] GLRenderer: EGL vendor: Mesa Project
  [2016-04-27 15:20:51.962645] GLRenderer: EGL version: 1.4 (DRI2)
  [2016-04-27 15:20:51.962651] GLRenderer: EGL client APIs: OpenGL OpenGL_ES 
OpenGL_ES2 OpenGL_ES3
  [2016-04-27 15:20:51.962657] GLRenderer: EGL extensions: EGL_EXT_buffer_age 
EGL_EXT_image_dma_buf_import EGL_KHR_create_context 
EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image 
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image 
EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_surfaceless_context 
EGL_MESA_configless_context EGL_MESA_image_dma_buf_export
  [2016-04-27 15:20:51.962670] GLRenderer: GL vendor: VMware, Inc.
  [2016-04-27 15:20:51.962679] GLRenderer: GL renderer: Gallium 0.4 on llvmpipe 
(LLVM 3.8, 256 bits)
  [2016-04-27 15:20:51.962688] GLRenderer: GL version: OpenGL ES 3.0 Mesa 11.2.0
  [2016-04-27 15:20:51.962697] GLRenderer: GLSL version: OpenGL ES GLSL ES 3.00

  lspci:
  01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] 
(rev a1)

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

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

[Touch-packages] [Bug 1575516] Re: Mir is just a black screen and mouse cursor on Nvidia GTX 900 when using nouveau

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

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

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

Title:
  Mir is just a black screen and mouse cursor on Nvidia GTX 900 when
  using nouveau

Status in Canonical System Image:
  Incomplete
Status in Mir:
  Expired
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Expired

Bug description:
  Nvidia (using nouveau not binary drivers): Mir servers freeze on
  start-up for 30 seconds, and then you get just a black screen and
  mouse cursor (which at least moves).

  Using lp:mir r3480 ...

  [2016-04-27 15:20:19.369559] mirserver: Selected driver: mir:mesa-kms 
(version 0.22.0)
  nvc0_screen_create:762 - Error allocating PGRAPH context for M2MF: -22
  [2016-04-27 15:20:51.934145] mirserver: Using hardware cursor
  [2016-04-27 15:20:51.937691] mirserver: Initial display configuration:
  [2016-04-27 15:20:51.937703] mirserver:   0.36: unused DVI-I
  [2016-04-27 15:20:51.937713] mirserver:   0.39: DVI-D 24.0" 520x320mm
  [2016-04-27 15:20:51.937722] mirserver: Current mode 1920x1200 59.95Hz
  [2016-04-27 15:20:51.937731] mirserver: Preferred mode 1920x1200 
59.95Hz
  [2016-04-27 15:20:51.937740] mirserver: Logical position +0+0
  [2016-04-27 15:20:51.937781] mirserver:   0.41: unused HDMI-A
  [2016-04-27 15:20:51.937799] mirserver:   0.43: unused DisplayPort
  [2016-04-27 15:20:51.937972] mircommon: Loading modules from: 
bin/../lib/server-modules/
  [2016-04-27 15:20:51.938015] mircommon: Loading module: 
bin/../lib/server-modules/graphics-android.so.9
  [2016-04-27 15:20:51.938107]  mircommon: Failed to load module: 
bin/../lib/server-modules/graphics-android.so.9 (error was:libhardware.so.2: 
cannot open shared object file: No such file or directory)
  [2016-04-27 15:20:51.938119] mircommon: Loading module: 
bin/../lib/server-modules/graphics-mesa-kms.so.9
  [2016-04-27 15:20:51.938142] mircommon: Loading module: 
bin/../lib/server-modules/server-mesa-x11.so.9
  [2016-04-27 15:20:51.938536] mircommon: Loading module: 
bin/../lib/server-modules/input-evdev.so.5
  [2016-04-27 15:20:51.955316] mirserver: Selected input driver: 
mir:evdev-input (version: 0.22.0)
  [2016-04-27 15:20:51.955500] mirserver: Mir version 0.22.0
  [2016-04-27 15:20:51.962627] GLRenderer: EGL vendor: Mesa Project
  [2016-04-27 15:20:51.962645] GLRenderer: EGL version: 1.4 (DRI2)
  [2016-04-27 15:20:51.962651] GLRenderer: EGL client APIs: OpenGL OpenGL_ES 
OpenGL_ES2 OpenGL_ES3
  [2016-04-27 15:20:51.962657] GLRenderer: EGL extensions: EGL_EXT_buffer_age 
EGL_EXT_image_dma_buf_import EGL_KHR_create_context 
EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image 
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image 
EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_surfaceless_context 
EGL_MESA_configless_context EGL_MESA_image_dma_buf_export
  [2016-04-27 15:20:51.962670] GLRenderer: GL vendor: VMware, Inc.
  [2016-04-27 15:20:51.962679] GLRenderer: GL renderer: Gallium 0.4 on llvmpipe 
(LLVM 3.8, 256 bits)
  [2016-04-27 15:20:51.962688] GLRenderer: GL version: OpenGL ES 3.0 Mesa 11.2.0
  [2016-04-27 15:20:51.962697] GLRenderer: GLSL version: OpenGL ES GLSL ES 3.00

  lspci:
  01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] 
(rev a1)

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

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

[Touch-packages] [Bug 1658238] Re: apache2 abstraction incomplete

** Branch linked: lp:apparmor/2.10

** Branch linked: lp:apparmor/2.9

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

Title:
  apache2 abstraction incomplete

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

Bug description:
  Apache2 needs updates for proper signal handling, optional saslauth,
  and OCSP stapling...

  
  --- apache2-common  2014-06-24 11:06:06.0 -0700
  +++ /etc/apparmor.d/abstractions/apache2-common 2015-05-21 07:51:49.0 
-0700
  @@ -8,6 +8,8 @@
 signal (receive) peer=unconfined,
 # Allow apache to send us signals by default
 signal (receive) peer=/usr/sbin/apache2,
  +  # Allow other hats to signal by default
  +  signal peer=/usr/sbin/apache2//*,
 # Allow us to signal ourselves
 signal peer=@{profile_name},

  @@ -25,3 +27,12 @@

 /dev/urandomr,

  +  # sasl-auth
  +  /run/saslauthd/mux rw,
  +
  +  # OCSP stapling
  +  /var/log/apache2/stapling-cache rw,

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

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

[Touch-packages] [Bug 1658239] Re: base abstraction missing glibc /proc/$pid/ things

Committed revision 3626.
Committed revision 3382.
Committed revision 3047.

Thanks

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

Title:
  base abstraction missing glibc /proc/$pid/ things

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

Bug description:
  There are yet more glibc-needed files missing from the base
  abstraction:

  --- base2017-01-20 15:37:50.0 -0800
  +++ /etc/apparmor.d/abstractions/base   2016-12-06 14:13:58.0 -0800
  @@ -92,7 +92,7 @@
 /sys/devices/system/cpu/online r,

 # glibc's *printf protections read the maps file
  -  @{PROC}/@{pid}/mapsr,
  +  @{PROC}/@{pid}/{maps,auxv,status}r,

 # libgcrypt reads some flags from /proc
 @{PROC}/sys/crypto/*   r,

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

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

[Touch-packages] [Bug 1658238] Re: apache2 abstraction incomplete

Committed revision 3625.
Committed revision 3381.
Committed revision 3046.

Thanks

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

Title:
  apache2 abstraction incomplete

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

Bug description:
  Apache2 needs updates for proper signal handling, optional saslauth,
  and OCSP stapling...

  
  --- apache2-common  2014-06-24 11:06:06.0 -0700
  +++ /etc/apparmor.d/abstractions/apache2-common 2015-05-21 07:51:49.0 
-0700
  @@ -8,6 +8,8 @@
 signal (receive) peer=unconfined,
 # Allow apache to send us signals by default
 signal (receive) peer=/usr/sbin/apache2,
  +  # Allow other hats to signal by default
  +  signal peer=/usr/sbin/apache2//*,
 # Allow us to signal ourselves
 signal peer=@{profile_name},

  @@ -25,3 +27,12 @@

 /dev/urandomr,

  +  # sasl-auth
  +  /run/saslauthd/mux rw,
  +
  +  # OCSP stapling
  +  /var/log/apache2/stapling-cache rw,

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

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

[Touch-packages] [Bug 1658239] Re: base abstraction missing glibc /proc/$pid/ things

** Branch linked: lp:apparmor/2.10

** Branch linked: lp:apparmor/2.9

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

Title:
  base abstraction missing glibc /proc/$pid/ things

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

Bug description:
  There are yet more glibc-needed files missing from the base
  abstraction:

  --- base2017-01-20 15:37:50.0 -0800
  +++ /etc/apparmor.d/abstractions/base   2016-12-06 14:13:58.0 -0800
  @@ -92,7 +92,7 @@
 /sys/devices/system/cpu/online r,

 # glibc's *printf protections read the maps file
  -  @{PROC}/@{pid}/mapsr,
  +  @{PROC}/@{pid}/{maps,auxv,status}r,

 # libgcrypt reads some flags from /proc
 @{PROC}/sys/crypto/*   r,

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

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

[Touch-packages] [Bug 1658239] Re: base abstraction missing glibc /proc/$pid/ things

** Branch linked: lp:apparmor

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

Title:
  base abstraction missing glibc /proc/$pid/ things

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

Bug description:
  There are yet more glibc-needed files missing from the base
  abstraction:

  --- base2017-01-20 15:37:50.0 -0800
  +++ /etc/apparmor.d/abstractions/base   2016-12-06 14:13:58.0 -0800
  @@ -92,7 +92,7 @@
 /sys/devices/system/cpu/online r,

 # glibc's *printf protections read the maps file
  -  @{PROC}/@{pid}/mapsr,
  +  @{PROC}/@{pid}/{maps,auxv,status}r,

 # libgcrypt reads some flags from /proc
 @{PROC}/sys/crypto/*   r,

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

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

[Touch-packages] [Bug 1658238] Re: apache2 abstraction incomplete

** Branch linked: lp:apparmor

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

Title:
  apache2 abstraction incomplete

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

Bug description:
  Apache2 needs updates for proper signal handling, optional saslauth,
  and OCSP stapling...

  
  --- apache2-common  2014-06-24 11:06:06.0 -0700
  +++ /etc/apparmor.d/abstractions/apache2-common 2015-05-21 07:51:49.0 
-0700
  @@ -8,6 +8,8 @@
 signal (receive) peer=unconfined,
 # Allow apache to send us signals by default
 signal (receive) peer=/usr/sbin/apache2,
  +  # Allow other hats to signal by default
  +  signal peer=/usr/sbin/apache2//*,
 # Allow us to signal ourselves
 signal peer=@{profile_name},

  @@ -25,3 +27,12 @@

 /dev/urandomr,

  +  # sasl-auth
  +  /run/saslauthd/mux rw,
  +
  +  # OCSP stapling
  +  /var/log/apache2/stapling-cache rw,

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

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

[Touch-packages] [Bug 1658238] Re: apache2 abstraction incomplete

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

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

Title:
  apache2 abstraction incomplete

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

Bug description:
  Apache2 needs updates for proper signal handling, optional saslauth,
  and OCSP stapling...

  
  --- apache2-common  2014-06-24 11:06:06.0 -0700
  +++ /etc/apparmor.d/abstractions/apache2-common 2015-05-21 07:51:49.0 
-0700
  @@ -8,6 +8,8 @@
 signal (receive) peer=unconfined,
 # Allow apache to send us signals by default
 signal (receive) peer=/usr/sbin/apache2,
  +  # Allow other hats to signal by default
  +  signal peer=/usr/sbin/apache2//*,
 # Allow us to signal ourselves
 signal peer=@{profile_name},

  @@ -25,3 +27,12 @@

 /dev/urandomr,

  +  # sasl-auth
  +  /run/saslauthd/mux rw,
  +
  +  # OCSP stapling
  +  /var/log/apache2/stapling-cache rw,

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

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

[Touch-packages] [Bug 1658239] Re: base abstraction missing glibc /proc/$pid/ things

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

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

Title:
  base abstraction missing glibc /proc/$pid/ things

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

Bug description:
  There are yet more glibc-needed files missing from the base
  abstraction:

  --- base2017-01-20 15:37:50.0 -0800
  +++ /etc/apparmor.d/abstractions/base   2016-12-06 14:13:58.0 -0800
  @@ -92,7 +92,7 @@
 /sys/devices/system/cpu/online r,

 # glibc's *printf protections read the maps file
  -  @{PROC}/@{pid}/mapsr,
  +  @{PROC}/@{pid}/{maps,auxv,status}r,

 # libgcrypt reads some flags from /proc
 @{PROC}/sys/crypto/*   r,

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

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

[Touch-packages] [Bug 1658236] Re: php abstraction not updated for php7

That's basically what upstream has, but without the symlink:

$ cat php5
#backwards compatibility include, actual abstraction moved from php5 to php

#include 


The php abstraction in the master branch already includes these changes.

Thanks

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

Title:
  php abstraction not updated for php7

Status in apparmor package in Ubuntu:
  New

Bug description:
  The php abstraction (also wrongly named php5 now) was not updated for
  php7. Attached is a diff I used...

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

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

[Touch-packages] [Bug 1658236] Re: php abstraction not updated for php7

This creates an upgrade burden on anyone already including the php5
abstraction. I think there should be a single abstraction (named php)
but a symlink back to php5 that includes 5 and current...

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

Title:
  php abstraction not updated for php7

Status in apparmor package in Ubuntu:
  New

Bug description:
  The php abstraction (also wrongly named php5 now) was not updated for
  php7. Attached is a diff I used...

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

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

[Touch-packages] [Bug 1658236] Re: php abstraction not updated for php7

2017-01-20 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  php abstraction not updated for php7

Status in apparmor package in Ubuntu:
  New

Bug description:
  The php abstraction (also wrongly named php5 now) was not updated for
  php7. Attached is a diff I used...

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

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

[Touch-packages] [Bug 1658250] [NEW] Window positions change in nonsensical ways when a secondary display is moved above the primary

2017-01-20 Thread Ben A

Public bug reported:

Most commonly, they'll be partway on the upper monitor, but mostly on
the bottom. But sometimes, they'll be halfway off the screen on the
bottom monitor. New windows are sometimes created in slightly odd places
as well; usually, the titlebar will be on the top screen and the rest of
the window on the bottom, meaning the gnome-shell bar is obscuring part
of the window.

Windows that are maximized when the change is made aren't affected.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu2
ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
Uname: Linux 4.9.0-11-generic x86_64
ApportVersion: 2.20.4-0ubuntu1
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Jan 20 18:09:51 2017
DistUpgraded: 2017-01-17 21:44:12,781 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Radeon RX 480 [1682:9480]
InstallationDate: Installed on 2017-01-17 (3 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
MachineType: ASUS All Series
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=638d73c8-aa0e-423b-907c-6bbb2c237275 ro i915.modeset=0 quiet splash 
vt.handoff=7
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to zesty on 2017-01-18 (2 days ago)
dmi.bios.date: 08/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2004
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.74-1
version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Jan 16 20:46:55 2017
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug reproducible single-occurrence third-party-packages 
ubuntu zesty

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

Title:
  Window positions change in nonsensical ways when a secondary display
  is moved above the primary

Status in xorg package in Ubuntu:
  New

Bug description:
  Most commonly, they'll be partway on the upper monitor, but mostly on
  the bottom. But sometimes, they'll be halfway off the screen on the
  bottom monitor. New windows are sometimes created in slightly odd
  places as well; usually, the titlebar will be on the top screen and
  the rest of the window on the bottom, meaning the gnome-shell bar is
  obscuring part of the window.

  Windows that are maximized when the change is made aren't affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Jan 20 18:09:51 2017
  DistUpgraded: 2017-01-17 21:44:12,781 DEBUG Running PostI

[Touch-packages] [Bug 1658236] Re: php abstraction not updated for php7

2017-01-20 Thread Christian Boltz

Note that upstream AppArmor renamed abstractions/php5 to
abstractions/php and added some more paths so that it also works with
PHP 7 on openSUSE. abstractions/php5 is still provided as compability
wrapper.

It would probably make sense to take the upstream files instead of your
patch.

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

Title:
  php abstraction not updated for php7

Status in apparmor package in Ubuntu:
  New

Bug description:
  The php abstraction (also wrongly named php5 now) was not updated for
  php7. Attached is a diff I used...

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

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

[Touch-packages] [Bug 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'

2017-01-20 Thread fhsm

I'm running into hung ssh connection and it is crazy making because I'm
getting inconsistent behavior across 16.10 boxes.

I've got two newly installed 16.10 boxes ($ ssh -V: OpenSSH_7.3p1
Ubuntu-1, OpenSSL 1.0.2g  1 Mar 2016). I'll call them Box1 and Box2.
They are in in adjacent ports on switch that has not had any changes in
years and on which all other systems are functioning.

I've got four clients: one OS X 10.9 (OpenSSH_6.2p1,OSSLShim 0.9.8r 8
Dec 2011), OS X 10.11 (OpenSSH_6.9p1, LibreSSL 2.1.8), Box1, and Box2.

I can connect to Box1 from the other three clients without any problem.
Works as expected.

I can ONLY connect to Box2 from OS X 10.9 and itself (i.e. ssh
me@localhost). I cannot get to it from Box1, I cannot get to it from OS
X 10.11. I have swapped the two OS X boxes around on the network and
also the two 16.10 boxes such that I'm confident that the ability to
connect is a function of the client-server combination not the network
link between them. ssh -vvv into Box2 from all of the failing clients
hangs as above, expecting SSH2_MSG_KEX_ECDH_REPLY.

This behavior / bug is so perplexing I'm unsure of it's relevance. I see two 
factors of interest:
 - Two ubuntu 16.10 sshds are behaving differently despite stock config across 
the two;
 - The ubuntu 16.10 is unable to connect to an sshd that one of two OS X ssh 
clients is able to connect two.

Since the two just got installed they haven't had much time to diverge.
The only differences between box1 and box2 are: (1) box2 is a few
updates behind and (2) although both have LXD installed only box2 has
had a container launched on it. Unfortunately prior to racking only the
10.9 system had ssh-ed into these boxes.

I'm going to sit on this for now in case someone interesting in trying
to get the Ubuntu ssh client to function - or - someone curious about
the divergent behavior of the Ubuntu sshd can give guidance on how to
turn this from a odd +1 report into something more useful. If not I'll
do a little more troubleshooting (install the pending updates
[initramfs-tools initramfs-tools-bin initramfs-tools-core isc-dhcp-
client isc-dhcp-common libglib2.0-0 libglib2.0-data liblxc1 lxc-common],
purge LXD) to see if I stumble onto something useful and failing that
nuke and pave.

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

Title:
  ssh fails to connect to VPN host - hangs at 'expecting
  SSH2_MSG_KEX_ECDH_REPLY'

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  ssh -vvv  is failing for me where  is a VPN system.

  VPN is configured and connected via network-manager. Last messages
  from ssh (hangs forever):

  debug2: kex_parse_kexinit: none,z...@openssh.com
  debug2: kex_parse_kexinit: none,z...@openssh.com
  debug2: kex_parse_kexinit: 
  debug2: kex_parse_kexinit: 
  debug2: kex_parse_kexinit: first_kex_follows 0 
  debug2: kex_parse_kexinit: reserved 0 
  debug2: mac_setup: found hmac-md5
  debug1: kex: server->client aes128-ctr hmac-md5 none
  debug2: mac_setup: found hmac-md5
  debug1: kex: client->server aes128-ctr hmac-md5 none
  debug1: sending SSH2_MSG_KEX_ECDH_INIT
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY

  
  = Workaround =

  $ sudo apt-get install putty
  $ putty 

  This works perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.4p1-1
  ProcVersionSignature: Ubuntu 3.12.0-3.8-generic 3.12.0
  Uname: Linux 3.12.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Nov 22 15:37:18 2013
  InstallationDate: Installed on 2010-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  RelatedPackageVersions:
   ssh-askpass   1:1.2.4.1-9
   libpam-sshN/A
   keychain  2.7.1-1
   ssh-askpass-gnome 1:6.4p1-1
  SSHClientVersion: OpenSSH_6.4p1 Ubuntu-1, OpenSSL 1.0.1e 11 Feb 2013
  SourcePackage: openssh
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (20 days ago)

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

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

[Touch-packages] [Bug 1658238] [NEW] apache2 abstraction incomplete

Public bug reported:

Apache2 needs updates for proper signal handling, optional saslauth, and
OCSP stapling...


--- apache2-common  2014-06-24 11:06:06.0 -0700
+++ /etc/apparmor.d/abstractions/apache2-common 2015-05-21 07:51:49.0 
-0700
@@ -8,6 +8,8 @@
   signal (receive) peer=unconfined,
   # Allow apache to send us signals by default
   signal (receive) peer=/usr/sbin/apache2,
+  # Allow other hats to signal by default
+  signal peer=/usr/sbin/apache2//*,
   # Allow us to signal ourselves
   signal peer=@{profile_name},

@@ -25,3 +27,12 @@

   /dev/urandomr,

+  # sasl-auth
+  /run/saslauthd/mux rw,
+
+  # OCSP stapling
+  /var/log/apache2/stapling-cache rw,

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

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

Title:
  apache2 abstraction incomplete

Status in apparmor package in Ubuntu:
  New

Bug description:
  Apache2 needs updates for proper signal handling, optional saslauth,
  and OCSP stapling...

  
  --- apache2-common  2014-06-24 11:06:06.0 -0700
  +++ /etc/apparmor.d/abstractions/apache2-common 2015-05-21 07:51:49.0 
-0700
  @@ -8,6 +8,8 @@
 signal (receive) peer=unconfined,
 # Allow apache to send us signals by default
 signal (receive) peer=/usr/sbin/apache2,
  +  # Allow other hats to signal by default
  +  signal peer=/usr/sbin/apache2//*,
 # Allow us to signal ourselves
 signal peer=@{profile_name},

  @@ -25,3 +27,12 @@

 /dev/urandomr,

  +  # sasl-auth
  +  /run/saslauthd/mux rw,
  +
  +  # OCSP stapling
  +  /var/log/apache2/stapling-cache rw,

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

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

[Touch-packages] [Bug 1658239] [NEW] base abstraction missing glibc /proc/$pid/ things

Public bug reported:

There are yet more glibc-needed files missing from the base abstraction:

--- base2017-01-20 15:37:50.0 -0800
+++ /etc/apparmor.d/abstractions/base   2016-12-06 14:13:58.0 -0800
@@ -92,7 +92,7 @@
   /sys/devices/system/cpu/online r,

   # glibc's *printf protections read the maps file
-  @{PROC}/@{pid}/mapsr,
+  @{PROC}/@{pid}/{maps,auxv,status}r,

   # libgcrypt reads some flags from /proc
   @{PROC}/sys/crypto/*   r,

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

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

Title:
  base abstraction missing glibc /proc/$pid/ things

Status in apparmor package in Ubuntu:
  New

Bug description:
  There are yet more glibc-needed files missing from the base
  abstraction:

  --- base2017-01-20 15:37:50.0 -0800
  +++ /etc/apparmor.d/abstractions/base   2016-12-06 14:13:58.0 -0800
  @@ -92,7 +92,7 @@
 /sys/devices/system/cpu/online r,

 # glibc's *printf protections read the maps file
  -  @{PROC}/@{pid}/mapsr,
  +  @{PROC}/@{pid}/{maps,auxv,status}r,

 # libgcrypt reads some flags from /proc
 @{PROC}/sys/crypto/*   r,

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

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

[Touch-packages] [Bug 1658236] [NEW] php abstraction not updated for php7

Public bug reported:

The php abstraction (also wrongly named php5 now) was not updated for
php7. Attached is a diff I used...

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

** Patch added: "php.diff"
   https://bugs.launchpad.net/bugs/1658236/+attachment/4806929/+files/php.diff

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

Title:
  php abstraction not updated for php7

Status in apparmor package in Ubuntu:
  New

Bug description:
  The php abstraction (also wrongly named php5 now) was not updated for
  php7. Attached is a diff I used...

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

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

[Touch-packages] [Bug 1656801] Re: ntp: changing the default config from server to pool broke the dhcp hook

2017-01-20 Thread Mathew Hodson

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

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

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

Title:
  ntp: changing the default config from server to pool broke the dhcp
  hook

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Triaged
Status in ntp package in Debian:
  Unknown

Bug description:
  In 1:4.2.8p3+dfsg-1, the default config was changed to
  "Use pool instead of server".  This needs a corresponding
  update to /etc/dhcp/dhclient-exit-hooks.d/ntp, since the
  DHCP specified servers now get added to the default pool
  config instead of replacing them.

  This affects Xenial only as the Yakkety build includes the upstream
  fix (1:4.2.8p7+dfsg-1).

  Original Debian busg https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809344 
  & https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806676

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

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

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

2017-01-20 Thread chrissy mcmanus

Juan's fix worked for me. 
I find that I cannot slow down the mouse speed through both the system menu and 
unity-tweaks, but i can get used to it i guess. It has tho given me back 
middle-mouse-button click emulation by means of using left and right click 
simultaneously, so this is a win win situation

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

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

Status in xorg package in Ubuntu:
  Confirmed

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

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

  Thanks,
  MZ

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

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

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

[Touch-packages] [Bug 1635050] Re: Some panel icons disappear after turning display off/on

2017-01-20 Thread trikrasne

it seems this bug have been solved.

** Changed in: xorg (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Some panel icons disappear after turning display off/on

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  When I boot into Ubuntu all panel icons are ok, but after turning the
  screen off (closing lid) and on again some icons disappear and get
  replaced with some generic "missing" icons.

  This happens with Mega and Bitmask icons but the applications still
  work. And if i quit one of those two apps the icon of another appears
  again.

  before:
  https://drive.google.com/open?id=0B4b2sRiO8XlMUkJDWTR0a0ptcFk

  after:
  https://drive.google.com/open?id=0B4b2sRiO8XlMcHRMQzJmbm90azQ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Oct 19 23:09:11 2016
  DistUpgraded: 2016-10-18 09:22:45,469 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics 
Controller [1043:13ad]
 Subsystem: ASUSTeK Computer Inc. GeForce GT 730M [1043:13ad]
  InstallationDate: Installed on 2015-08-20 (426 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUSTeK COMPUTER INC. UX302LG
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-10-18 (1 days ago)
  dmi.bios.date: 06/16/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX302LG.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX302LG
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX302LG.210:bd06/16/2014:svnASUSTeKCOMPUTERINC.:pnUX302LG:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX302LG:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX302LG
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Wed Oct 19 19:43:23 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6

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

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

[Touch-packages] [Bug 1656801] Re: ntp: changing the default config from server to pool broke the dhcp hook

2017-01-20 Thread Mathew Hodson

** Also affects: ntp (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809344
   Importance: Unknown
   Status: Unknown

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

Title:
  ntp: changing the default config from server to pool broke the dhcp
  hook

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Triaged
Status in ntp package in Debian:
  Unknown

Bug description:
  In 1:4.2.8p3+dfsg-1, the default config was changed to
  "Use pool instead of server".  This needs a corresponding
  update to /etc/dhcp/dhclient-exit-hooks.d/ntp, since the
  DHCP specified servers now get added to the default pool
  config instead of replacing them.

  This affects Xenial only as the Yakkety build includes the upstream
  fix (1:4.2.8p7+dfsg-1).

  Original Debian busg https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809344 
  & https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806676

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

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

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

This bug was fixed in the package systemd - 229-4ubuntu16

---
systemd (229-4ubuntu16) xenial; urgency=medium

  * d/p/0001-libudev-util-change-util_replace_whitespace-to-retur.patch,
d/p/0002-udev-event-add-replace_whitespace-param-to-udev_even.patch,
d/p/0003-udev-rules-perform-whitespace-replacement-for-symlin.patch:
Cherry-pick upstream fixes from Dan Streetman  to
fix by-id symlinks for devices whose IDs contain whitespace.
LP: #1647485.

 -- Steve Langasek   Wed, 18 Jan 2017
13:37:19 -0800

** Changed in: systemd (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/1647485

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

  Related bugs:
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
   * bug 1651602: NVMe driver regression for non-smp/1-cpu systems
   * bug 1649635: export nvme drive model/serial strings via sysfs (trusty)

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

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

[Touch-packages] [Bug 1647485] Update Released

2017-01-20 Thread Steve Langasek

The verification of the Stable Release Update for systemd 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/1647485

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

  Related bugs:
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
   * bug 1651602: NVMe driver regression for non-smp/1-cpu systems
   * bug 1649635: export nvme drive model/serial strings via sysfs (trusty)

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

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

[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters

Where was this fixed upstream? Could you provide a link to the fix being
accepted upstream?

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

Title:
  missing or duplicate lines caused by a wrapped line with wide
  characters

Status in less package in Ubuntu:
  Confirmed

Bug description:
  When you scroll down text with "j" key and encounter a wrapped line
  with wide characters (such as UTF8-encoded Japanese characters),
  "less" seems to show the whole wrapped line at a single "j" key,
  causing the view scroll down by 2 lines at once. Strangely, if you
  type "k" to scroll up, it does that by only 1 line. As a result, there
  is a missing line that should have been shown.

  Even stranger stuff (i.e., duplicate lines) happens when you type "j"
  and "k" alternately when a wrapped line with wide characters is at the
  bottom of the view.

  
  # Steps to reproduce

  1. Open xterm.
  2. Set the geometory of xterm to 71x22.
  3. Open the attached lesstest.long_jap.txt with less (maybe you need
 environment variable LANG=ja_JP.UTF-8)
  4. Type "j", then you will see "003" at the top, and a long wrapped
 line with Japanese characters at the bottom.
  5. Type "k", then you will see "001" and "003" at the top. "002" is
 missing.

  # Expected behavior

  In step 4, only the first part of the wrapped line should be shown.

  In step 5, all "001", "002" and "003" should be shown.

  
  # Test Environment

  - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04)
  - less: 481-2.1
  - xterm: 322-1ubuntu1
  - Japanese environment (LANG=ja_JP.UTF-8)

  
  # Note

  - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1)
  - lv (4.51-2.3build1) doesn't have such problem.
  - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't
exist.

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

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

[Touch-packages] [Bug 1658188] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes

** Branch linked: lp:apport

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

Title:
  /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes

Status in apport package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.3-0ubuntu8.2, the problem page at 
https://errors.ubuntu.com/problem/65cb22d7c29a308dad9368b971e1b8d6384c9089 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1658188] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes

Fixed in upstream r3122.

** Changed in: apport (Ubuntu)
   Status: New => Triaged

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

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes

Status in apport package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.3-0ubuntu8.2, the problem page at 
https://errors.ubuntu.com/problem/65cb22d7c29a308dad9368b971e1b8d6384c9089 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1652348] Re: initrd dhcp fails / ignores valid response

2017-01-20 Thread Ubuntu Foundations Team Bug Bot

The attachment "klibc-fix-1.patch" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

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

** Tags added: patch

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

Title:
  initrd dhcp fails / ignores valid response

Status in klibc package in Ubuntu:
  In Progress
Status in klibc source package in Xenial:
  Triaged

Bug description:
  Between kernel versions 4.4.0-53 and 4.4.0-57 a bug has been
  (re?)introduced that is breaking dhcp booting in the initrd
  environment.  This is stopping instances that use iscsi storage from
  being able to connect.

  Over serial console it outputs:

  IP-Config: no response after 2 secs - giving up
  IP-Config: ens2f0 hardware address 90:e2:ba:d1:36:38 mtu 1500 DHCP RARP
  IP-Config: ens2f1 hardware address 90:e2:ba:d1:36:39 mtu 1500 DHCP RARP
  IP-Config: no response after 3 secs - giving up

  with increasing delays until it fails.  At which point a simple
  ipconfig -t dhcp -d "ens2f0"  works.  The console output is slightly
  garbled but should give you an idea:

  (initramfs) ipconfig -t dhcp -[  728.379793] ixgbe :13:00.0 ens2f0: 
changing MTU from 1500 to 9000
  d "ens2f0"
  IP-Config: ens2f0 hardware address 90:e2:ba:d1:36:38 mtu 1500 DHCP RARP
  IP-Config: ens2f0 guessed broadcast address 10.0.1.255
  IP-Config: ens2f0 complete (dhcp from 169.254.169.254):
   addres[  728.980448] ixgbe :13:00.0 ens2f0: detected SFP+: 3
  s: 10.0.1.56broadcast: 10.0.1.255   netmask: 255.255.255.0
   gateway: 10.0.1.1   [  729.148410] ixgbe :13:00.0 ens2f0: NIC Link is Up 
10 Gbps, Flow Control: RX/TX
    dns0 : 169.254.169.254  dns1   : 0.0.0.0
   rootserver: 169.254.169.254 rootpath:
   filename  : /ipxe.efi

  tcpdumps show that dhcp requests are being received from the host, and
  responses sent, but not accepted by the host.  When the ipconfig
  command is issued manually, an identical dhcp request and response
  happens, only this time it is accepted.  It doesn't appear to be that
  the messages are being sent and received incorrectly, just silently
  ignored by ipconfig.

  I was seeing this behaviour earlier this year, which I was able to fix
  by specifying "ip=dhcp" as a kernel parameter.  About a month ago that
  was identified as causing us other problems (long story) and we
  dropped it, at which point we discovered the original bug was no
  longer an issue.

  Putting "ip=dhcp" back on with this kernel no longer fixes the
  problem.

  I've compared the two initrds and effectively the only thing that has
  changed between the two is the kernel components.

  Ubuntu kernel bisect offending commit:
  # first bad commit: [fd4b5fa6e3487d15ede746f92601af008b2abbc0] mnt: Add a per 
mount namespace limit on the number of mounts

  Ubuntu kernel bisect offending commit submission:
  https://lkml.org/lkml/2016/10/5/308

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

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

[Touch-packages] [Bug 1658190] [NEW] Searching rapidly with the app drawer causes Unity 8 to crash

2017-01-20 Thread Larry Price

Public bug reported:

Latest zesty
unity8 8.15+17.04.20170110.4-0ubuntu1

Searching rapidly for apps in the app drawer is causing a crash for me.
I have quite a few applications (including libertine apps) available. To
reproduce:

1. Open app drawer
2. Enter a few characters to match an app
3. Clear searchbar with backspaces
4. Goto step 2 (switching characters from time to time)

This crashes Unity 8 for me sometimes as quickly as 20 searches, but
other times it takes up to 50 searches.

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

Title:
  Searching rapidly with the app drawer causes Unity 8 to crash

Status in unity8 package in Ubuntu:
  New

Bug description:
  Latest zesty
  unity8 8.15+17.04.20170110.4-0ubuntu1

  Searching rapidly for apps in the app drawer is causing a crash for
  me. I have quite a few applications (including libertine apps)
  available. To reproduce:

  1. Open app drawer
  2. Enter a few characters to match an app
  3. Clear searchbar with backspaces
  4. Goto step 2 (switching characters from time to time)

  This crashes Unity 8 for me sometimes as quickly as 20 searches, but
  other times it takes up to 50 searches.

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

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

[Touch-packages] [Bug 1658188] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes

Here's the Traceback:

Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 597, in 
app.run_argv()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 687, in run_argv
return self.run_crashes()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 238, in run_crashes
logind_session[1] > self.report.get_timestamp():
TypeError: unorderable types: float() > NoneType()

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

Title:
  /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.3-0ubuntu8.2, the problem page at 
https://errors.ubuntu.com/problem/65cb22d7c29a308dad9368b971e1b8d6384c9089 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1658188] [NEW] /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes

2017-01-20 Thread errors.ubuntu.com bug bridge

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.3-0ubuntu8.2, the problem page at 
https://errors.ubuntu.com/problem/65cb22d7c29a308dad9368b971e1b8d6384c9089 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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


** Tags: xenial yakkety

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

Title:
  /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.3-0ubuntu8.2, the problem page at 
https://errors.ubuntu.com/problem/65cb22d7c29a308dad9368b971e1b8d6384c9089 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Touch-packages] [Bug 1652348] Re: initrd dhcp fails / ignores valid response

2017-01-20 Thread Jay Vosburgh

Patch proposal to modify ipconfig to use one packet socket per interface


** Patch added: "klibc-fix-1.patch"
   
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1652348/+attachment/4806861/+files/klibc-fix-1.patch

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

Title:
  initrd dhcp fails / ignores valid response

Status in klibc package in Ubuntu:
  In Progress
Status in klibc source package in Xenial:
  Triaged

Bug description:
  Between kernel versions 4.4.0-53 and 4.4.0-57 a bug has been
  (re?)introduced that is breaking dhcp booting in the initrd
  environment.  This is stopping instances that use iscsi storage from
  being able to connect.

  Over serial console it outputs:

  IP-Config: no response after 2 secs - giving up
  IP-Config: ens2f0 hardware address 90:e2:ba:d1:36:38 mtu 1500 DHCP RARP
  IP-Config: ens2f1 hardware address 90:e2:ba:d1:36:39 mtu 1500 DHCP RARP
  IP-Config: no response after 3 secs - giving up

  with increasing delays until it fails.  At which point a simple
  ipconfig -t dhcp -d "ens2f0"  works.  The console output is slightly
  garbled but should give you an idea:

  (initramfs) ipconfig -t dhcp -[  728.379793] ixgbe :13:00.0 ens2f0: 
changing MTU from 1500 to 9000
  d "ens2f0"
  IP-Config: ens2f0 hardware address 90:e2:ba:d1:36:38 mtu 1500 DHCP RARP
  IP-Config: ens2f0 guessed broadcast address 10.0.1.255
  IP-Config: ens2f0 complete (dhcp from 169.254.169.254):
   addres[  728.980448] ixgbe :13:00.0 ens2f0: detected SFP+: 3
  s: 10.0.1.56broadcast: 10.0.1.255   netmask: 255.255.255.0
   gateway: 10.0.1.1   [  729.148410] ixgbe :13:00.0 ens2f0: NIC Link is Up 
10 Gbps, Flow Control: RX/TX
    dns0 : 169.254.169.254  dns1   : 0.0.0.0
   rootserver: 169.254.169.254 rootpath:
   filename  : /ipxe.efi

  tcpdumps show that dhcp requests are being received from the host, and
  responses sent, but not accepted by the host.  When the ipconfig
  command is issued manually, an identical dhcp request and response
  happens, only this time it is accepted.  It doesn't appear to be that
  the messages are being sent and received incorrectly, just silently
  ignored by ipconfig.

  I was seeing this behaviour earlier this year, which I was able to fix
  by specifying "ip=dhcp" as a kernel parameter.  About a month ago that
  was identified as causing us other problems (long story) and we
  dropped it, at which point we discovered the original bug was no
  longer an issue.

  Putting "ip=dhcp" back on with this kernel no longer fixes the
  problem.

  I've compared the two initrds and effectively the only thing that has
  changed between the two is the kernel components.

  Ubuntu kernel bisect offending commit:
  # first bad commit: [fd4b5fa6e3487d15ede746f92601af008b2abbc0] mnt: Add a per 
mount namespace limit on the number of mounts

  Ubuntu kernel bisect offending commit submission:
  https://lkml.org/lkml/2016/10/5/308

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

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

[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites

2017-01-20 Thread Ma Cha

when going on some websites like posteo.de, i don't get even "continue
anyway", just "certificat of this website is not approuved".

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

Title:
  webbrowser only partially loads some https sites

Status in Canonical System Image:
  In Progress
Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 14) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

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

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

[Touch-packages] [Bug 1658178] [NEW] systemd 232-10ubuntu1 ADT test failure with linux 4.9.0-12.13

2017-01-20 Thread Andy Whitcroft

Public bug reported:

Testing failed on:
amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170120_162258_08201@/log.gz
i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170120_162514_08201@/log.gz
ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170120_163827_08201@/log.gz

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

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

Title:
  systemd 232-10ubuntu1 ADT test failure with linux 4.9.0-12.13

Status in systemd package in Ubuntu:
  New

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170120_162258_08201@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170120_162514_08201@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170120_163827_08201@/log.gz

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

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

[Touch-packages] [Bug 1657882] Re: wine

2017-01-20 Thread Paul White

** Package changed: xorg (Ubuntu) => wine (Ubuntu)

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

Title:
  wine

Status in wine package in Ubuntu:
  New

Bug description:
  cant install wine

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jan 19 21:39:58 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8330] [1025:104b]
  InstallationDate: Installed on 2016-12-01 (49 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Acer Aspire ES1-520
  ProcEnviron:
   LANGUAGE=hr
   PATH=(custom, no user)
   LANG=hr_HR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=073388fc-a929-4eae-81b3-5f775ced2d93 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Bellemere_BE
  dmi.board.vendor: Acer
  dmi.board.version: V1.06
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-520:pvrV1.06:rvnAcer:rnBellemere_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion:
  dmi.product.name: Aspire ES1-520
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jan 19 21:37:31 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 940030] Re: rsyslog stops working after logrotate until restarted

2017-01-20 Thread jon bird

I'm seeing something similar with 14.04 since upgrading from 12.04 only
in this case, I'm still getting kernel messages written to the logs
however nothing else is until I force a restart of rsyslog. File
permissions look ok though (syslog:adm).

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

Title:
  rsyslog stops working after logrotate until restarted

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  This could otherwise be titled, rsyslog reload does not create log
  files; only restart does.

  This is happening on a number of machines I work on.  It's happening
  on 10.04 and 11.04.  It might be similar to:

  https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/407862

  But in my case after the restart there is no /var/log/syslog being
  created, nor auth.log, kern.log, etc.  The files are rotated, rsyslog
  is reloaded, and none of the log files are created and nothing is
  being logged.  This has been plaguing my systems since moving from
  syslog-ng, which I may return to as it seems it was actually
  production ready.

  Without manually restarting those files don't exist so here's what I
  did on an 11.04 system:

  logrotate --force --verbose /etc/logrotate.conf

  gives:

  rotating pattern: /var/log/syslog
   forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log /var/log/syslog does not exist -- skipping
  not running postrotate script, since no logs were rotated

  rotating pattern: /var/log/mail.info
  /var/log/mail.warn
  /var/log/mail.err
  /var/log/mail.log
  /var/log/daemon.log
  /var/log/kern.log
  /var/log/auth.log
  /var/log/user.log
  /var/log/lpr.log
  /var/log/cron.log
  /var/log/debug
  /var/log/messages
   forced from command line (4 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/mail.info
log /var/log/mail.info does not exist -- skipping
  considering log /var/log/mail.warn
log /var/log/mail.warn does not exist -- skipping
  considering log /var/log/mail.err
log does not need rotating
  considering log /var/log/mail.log
log does not need rotating
  considering log /var/log/daemon.log
log /var/log/daemon.log does not exist -- skipping
  considering log /var/log/kern.log
log /var/log/kern.log does not exist -- skipping
  considering log /var/log/auth.log
log /var/log/auth.log does not exist -- skipping
  considering log /var/log/user.log
log /var/log/user.log does not exist -- skipping
  considering log /var/log/lpr.log
log /var/log/lpr.log does not exist -- skipping
  considering log /var/log/cron.log
log /var/log/cron.log does not exist -- skipping
  considering log /var/log/debug
log /var/log/debug does not exist -- skipping
  considering log /var/log/messages
log /var/log/messages does not exist -- skipping
  not running postrotate script, since no logs were rotated

  Then
  /sbin/reload rsyslog
  logger -i testing

  At this point there is no /var/log/syslog

  Then:
  /sbin/restart rsyslog

  And voila there is a /var/log/syslog beginning with:

  Feb 23 19:24:48 somehost kernel: imklog 4.6.4, log source = /proc/kmsg 
started.
  Feb 23 19:24:48 somehost rsyslogd: [origin software="rsyslogd" 
swVersion="4.6.4" x-pid="2299" x-info="http://www.rsyslog.com";] (re)start
  Feb 23 19:24:48 somehost rsyslogd: rsyslogd's groupid changed to 114
  Feb 23 19:24:48 somehost rsyslogd: rsyslogd's userid changed to 108

  Then to recreate:

  logrotate --force --verbose /etc/logrotate.conf

  
  rotating pattern: /var/log/syslog
   forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log needs rotating
  rotating log /var/log/syslog, log->rotateCount is 7
  dateext suffix '-20120223'
  glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
  compressing log with: /bin/gzip
  renaming /var/log/syslog to /var/log/syslog-20120223
  running postrotate script
  removing old log /var/log/syslog-20111219.gz

  rotating pattern: /var/log/mail.info
  /var/log/mail.warn
  /var/log/mail.err
  /var/log/mail.log
  /var/log/daemon.log
  /var/log/kern.log
  /var/log/auth.log
  /var/log/user.log
  /var/log/lpr.log
  /var/log/cron.log
  /var/log/debug
  /var/log/messages
   forced from command line (4 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/mail.info
log /var/log/mail.info does not exist -- skipping
  considering log /var/log/mail.warn
log /var/log/mail.warn does not exist -- skipping
  considering log /var/log/mail.err
log does not need rotating
  considering log /var/log/mail.log
log does not need rotating
  considering log /var/log/daemon.log
log /var/log/daemon.log does not exist -- skipping
  considering log /var/log/ke

[Touch-packages] [Bug 1654479] Re: Disabling 'Report to Canonical: App crashes and errors' sets wrong core_pattern

2017-01-20 Thread Pat McGowan

This is set per the fix for lp:1505302 but that also sets suid_dumpable
to 0. The core pattern seems moot in that case?

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

Title:
  Disabling 'Report to Canonical: App crashes and errors' sets wrong
  core_pattern

Status in Canonical System Image:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  Disabling 'Report to Canonical: App crashes and errors' sets wrong
  core_pattern.

  On a fresh boot with error reporting disabled by default:
  # cat /proc/sys/kernel/core_pattern 
  /bad_core_pattern

  Enable 'Report to Canonical: App crashes and errors':
  # cat /proc/sys/kernel/core_pattern 
  |/usr/share/apport/apport %p %s %c %P

  Disable 'Report to Canonical: App crashes and errors':
  # cat /proc/sys/kernel/core_pattern 
  core

  I think it should be reverting to "/bad_core_pattern" instead of
  "core". Because "core" could fill the filesystem with core files (if
  ulimit allows it).

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

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

[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones

2017-01-20 Thread Jim Hodapp

@Wesley: I would also add, did you know that you can place this
headphone in BT pairing mode by first switching it on and then holding
that same switch as far away from the off position as possible for a
second or two? You don't need the Bose Connect app to put it in pairing
mode then.

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => Jim Hodapp (jhodapp)

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

Title:
  Fails to pair with Bose QC35 headphones

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

Bug description:
  I am unable to pair the Bose QC35 BT headphones with Ubuntu, either
  Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez
  5.41 from installed from yakkety archive), nor using Ubuntu Touch rc-
  proposed build for Turbo #174. I'm trying to pair through the normal
  bluetooth control panel brought up through the bluetooth indicator.

  I've attached some logs that show it failing to pair. If I can provide
  anymore useful information about the headphones, please let me know.

  Syslog with bluetoothd debugging enabled:
  http://pastebin.ubuntu.com/23141394/

  btmon output:
  http://pastebin.ubuntu.com/23141446/

  bluetoothctl output:
  http://pastebin.ubuntu.com/23141510/

  With Linux kernel 4.8.0 and bluez 4.52:
  ---

  bluetoothctl: http://pastebin.ubuntu.com/23256457/
  btmon: http://pastebin.ubuntu.com/23256471/

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

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

[Touch-packages] [Bug 1651623] Re: adt tests fail on zesty for apport

** Tags added: rls-z-incoming

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

Title:
  adt tests fail on zesty for apport

Status in apport package in Ubuntu:
  New
Status in apport source package in Yakkety:
  New

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz

  fails.

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

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

[Touch-packages] [Bug 1576282] Re: Snaps built from deb can't be gettext translated

** Branch linked: lp:~kalikiana/ubuntu-ui-toolkit/language-pack-base

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

Title:
  Snaps built from deb can't be gettext translated

Status in Canonical System Image:
  In Progress
Status in Snapcraft:
  New
Status in Ubuntu App Platform:
  In Progress
Status in snapcraft package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Currently it seems not possible to have working gettext translations
  without included a patch glibc build in your snap

  - the core image doesn't have locales definition

  that can be worked around by including locales definitions in the
  snap, though that's tedious, ideally snapcraft would help there

  
  - traditional desktop applications are built with calls to 'bindtextdomain 
("domain", LOCALEDIR)', where LOCALDIR is defined at buildtime and so pointing 
to /usr 

  there seems to be no way to redirect to another directory at runtime

  
  - desktop applications needs system library translations sometime which means 
langpacks need to be included in snaps

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

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

[Touch-packages] [Bug 1656727] Re: Unity8 crashes and restarts when clicking on a menu [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

2017-01-20 Thread Daniel d'Andrada

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

** Changed in: miral (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: qtmir
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

** Changed in: miral
   Status: Incomplete => Invalid

** Changed in: mir
   Status: Incomplete => Invalid

** Branch linked: lp:~dandrader/unity8/childWindows

** Branch linked: lp:~dandrader/qtmir/miral-surfaceLocalPos

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

Title:
  Unity8 crashes and restarts when clicking on a menu [terminate called
  after throwing an instance of 'std::out_of_range' what():  map::at]

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Invalid
Status in MirAL:
  Invalid
Status in QtMir:
  Confirmed
Status in miral package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Unity8 crashes and restarts when clicking on a menu:

  terminate called after throwing an instance of 'std::out_of_range'
    what():  map::at

  Test case:
    1. Launch AisleRiot
    2. Click on a menu

  Expected: Menu opens
  Observed: Unity8 crashes and restarts every time

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170110.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  Date: Mon Jan 16 10:29:08 2017
  InstallationDate: Installed on 2016-11-03 (74 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1654479] Re: Disabling 'Report to Canonical: App crashes and errors' sets wrong core_pattern

There's noting in apport that writes "bad_core_pattern". I also looked
in ubuntu-system-settings and didn't find anything there either.

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

Title:
  Disabling 'Report to Canonical: App crashes and errors' sets wrong
  core_pattern

Status in Canonical System Image:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  Disabling 'Report to Canonical: App crashes and errors' sets wrong
  core_pattern.

  On a fresh boot with error reporting disabled by default:
  # cat /proc/sys/kernel/core_pattern 
  /bad_core_pattern

  Enable 'Report to Canonical: App crashes and errors':
  # cat /proc/sys/kernel/core_pattern 
  |/usr/share/apport/apport %p %s %c %P

  Disable 'Report to Canonical: App crashes and errors':
  # cat /proc/sys/kernel/core_pattern 
  core

  I think it should be reverting to "/bad_core_pattern" instead of
  "core". Because "core" could fill the filesystem with core files (if
  ulimit allows it).

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

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

[Touch-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

Let's wait for Mathieu's opinion.

This seems like a good candidate for 16.04.2 if we can get it fixed in
time.

** Changed in: network-manager (Ubuntu)
Milestone: None => ubuntu-16.04.2

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  * Steps to reproduce:
  1. Install image
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

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

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

[Touch-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

2017-01-20 Thread Jeremy Soller

Yes, I am. I just need to know what is permissible - we can add
IgnoreOnIsolate in a ubuntu patch but it seems like the source of the
issue is in network manager - it should detect that wpa supplicant is
not running and restart it dynamically.

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  * Steps to reproduce:
  1. Install image
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

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

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

[Touch-packages] [Bug 1572807] Re: /bin/nano:* Error in `nano': double free or corruption (!prev): ADDR *

It's possible the stacktrace in the Error Tracker contains sensitive
information, that's why access to it is restricted and it's not
automatically added to the bug report here.

Here's the Stacktrace though:

#0  0x7f38ce77e428 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:54
resultvar = 0
pid = 6528
selftid = 6528
#1  0x7f38ce78002a in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x2020202020383939, 
sa_sigaction = 0x2020202020383939}, sa_mask = {__val = {2314885530818453536, 
2314885530818453536, 7091318039310988591, 3257288213055174703, 
7955377262162766188, 3420042391722602357, 8029123697353646951, 
7017503717531088228, 4049692876519860323, 3472328519700276835, 
3559641648514610989, 8606977229197436472, 3472328296226648109, 
3475143045726351408, 3703708260188037168, 3472387704235647800}}, sa_flags = 
1714892080, sa_restorer = 0x4f}
sigs = {__val = {32, 0 }}
#2  0x7f38ce7c07ea in __libc_message (do_abort=do_abort@entry=2, 
fmt=fmt@entry=0x7f38ce8d92e0 "*** Error in `%s': %s: 0x%s ***\n") at 
../sysdeps/posix/libc_fatal.c:175
ap = 
fd = 4
on_2 = 
list = 
nlist = 
cp = 
written = 
#3  0x7f38ce7c8e0a in malloc_printerr (ar_ptr=, 
ptr=, str=0x7f38ce8d9410 "double free or corruption (!prev)", 
action=3) at malloc.c:5004
buf = "00692690"
cp = 
ar_ptr = 
str = 0x7f38ce8d9410 "double free or corruption (!prev)"
action = 3
#4  _int_free (av=, p=, have_lock=0) at 
malloc.c:3865
size = 
fb = 
nextchunk = 
nextsize = 
nextinuse = 
prevsize = 
bck = 
fwd = 
errstr = 
locked = 
#5  0x7f38ce7cc98c in __GI___libc_free (mem=mem@entry=0x692690) at 
malloc.c:2966
ar_ptr = 
p = 0x692680
hook = 
#6  0x00408b56 in do_lockfile (filename=filename@entry=0x7ffee0fb074d 
"**removed**/COMMIT_EDITMSG") at ../../src/files.c:374
readtot = 
promptstr = 0x692690 "File **removed**/COMMIT_EDITMSG is being edited 
(by **removed** with nano 2.5.3, PID 12547); continue?"
readamt = 
lockbuf = 
ans = 1
namecopy1 = 
namecopy2 = 
locknamesize = 
lockfilename = 0x6999c0 "**removed**/.COMMIT_EDITMSG.swp"
lockprog = "nano 2.5.3"
lockuser = "khazizovroman\000\000\000"
fileinfo = {st_dev = 2050, st_ino = 3733172, st_nlink = 1, st_mode = 
33204, st_uid = 1000, st_gid = 1000, __pad0 = 0, st_rdev = 0, st_size = 1024, 
st_blksize = 4096, st_blocks = 8, st_atim = {tv_sec = 1472024225, tv_nsec = 
596574479}, st_mtim = {tv_sec = 1468485463, tv_nsec = 186453909}, st_ctim = 
{tv_sec = 1468485463, tv_nsec = 186453909}, __glibc_reserved = {0, 0, 0}}
lockpid = 12547
retval = -1
#7  0x0040ccf1 in open_buffer (filename=0x7ffee0fb074d 
"**removed**/COMMIT_EDITMSG", undoable=undoable@entry=false) at 
../../src/files.c:457
lockstatus = 
quiet = false
new_buffer = true
f = 0x3b
rc = 
#8  0x0040431c in main (argc=2, argv=0x7ffee0fae2f8) at 
../../src/nano.c:2599
optchr = 
startline = 0
startcol = 0
fill_used = 
forced_wrapping = 
old_multibuffer = false
long_options = {{name = 0x428236 "boldtext", has_arg = 0, flag = 0x0, 
val = 68}, {name = 0x42826d "multibuffer", has_arg = 0, flag = 0x0, val = 70}, 
{name = 0x4282c8 "ignorercfiles", has_arg = 0, flag = 0x0, val = 73}, {name = 
0x4282d8 "rebindkeypad", has_arg = 0, flag = 0x0, val = 75}, {name = 0x4282e7 
"nonewlines", has_arg = 0, flag = 0x0, val = 76}, {name = 0x42831e "morespace", 
has_arg = 0, flag = 0x0, val = 79}, {name = 0x42875d "quotestr", has_arg = 1, 
flag = 0x0, val = 81}, {name = 0x428371 "restricted", has_arg = 0, flag = 0x0, 
val = 82}, {name = 0x428766 "tabsize", has_arg = 1, flag = 0x0, val = 84}, 
{name = 0x4283cd "version", has_arg = 0, flag = 0x0, val = 86}, {name = 
0x4298ca "syntax", has_arg = 1, flag = 0x0, val = 89}, {name = 0x4283fc 
"constantshow", has_arg = 0, flag = 0x0, val = 99}, {name = 0x42840e 
"rebinddelete", has_arg = 0, flag = 0x0, val = 100}, {name = 0x42843d "help", 
has_arg = 0, flag = 0x0, val = 104}, {name = 0x428474 "mouse", has_arg = 0, 
flag =
  0x0, val = 109}, {name = 0x428487 "noread", has_arg = 0, flag = 0x0, val = 
110}, {name = 0x42876e "operatingdir", has_arg = 1, flag = 0x0, val = 111}, 
{name = 0x4284c9 "preserve", has_arg = 0, flag = 0x0, val = 112}, {name = 
0x4284d7 "quiet", has_arg = 0, flag = 0x0, val = 113}, {name = 0x42877b "fill", 
has_arg = 1, flag = 0x0, val = 114}, {name = 0x428526 "speller", has_arg = 1, 
flag = 0x0, val = 115}, {name = 0x428530 "tempfile", has_arg = 0, flag = 0x0, 
val = 116}, {name = 0x42855e "view", has_arg = 0, flag = 0x0, val = 118}, {name 
= 0x428583 "nowrap", has_arg

[Touch-packages] [Bug 1595607] Re: /bin/nano:* Error in `nano': free(): invalid next size (normal): ADDR *

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

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

Title:
  /bin/nano:*** Error in `nano': free(): invalid next size (normal):
  ADDR ***

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

Bug description:
  [Test Case]
  Using the provided Error Tracker bucket confirm that there are no instances 
of the crash with the version of the package from -proposed.  Given that we 
don't have a reproducer we should let the package age for longer than 7 days to 
ensure many users are testing it.

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding nano.  This problem was most recently seen with version
  2.5.3-2, the problem page at
  https://errors.ubuntu.com/problem/d609e39daa79867af99f7c1c75f3db7b998971d9
  contains more details.

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

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

[Touch-packages] [Bug 1595607] Re: /bin/nano:* Error in `nano': free(): invalid next size (normal): ADDR *

To get an idea of the number of users of the proposed package I filtered
for crashes from Ubuntu 16.04 and with the proposed version of the
package:

https://errors.ubuntu.com/?release=Ubuntu%2016.04&package=nano&period=month&version=2.5.3-2ubuntu1

Looking at some of the individual buckets we can see quite a few people
using 2.5.3-2ubuntu1 and that version doesn't appear in the bucket for
the crash we are trying to fix, so I'll set it as v-done.

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

Title:
  /bin/nano:*** Error in `nano': free(): invalid next size (normal):
  ADDR ***

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

Bug description:
  [Test Case]
  Using the provided Error Tracker bucket confirm that there are no instances 
of the crash with the version of the package from -proposed.  Given that we 
don't have a reproducer we should let the package age for longer than 7 days to 
ensure many users are testing it.

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding nano.  This problem was most recently seen with version
  2.5.3-2, the problem page at
  https://errors.ubuntu.com/problem/d609e39daa79867af99f7c1c75f3db7b998971d9
  contains more details.

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

-- 
Mailing list: https://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 1643708] Re: Add SPNEGO special case for NTLMSSP+MechListMIC

Hi Sam,

Thank you for weighing in on this. I appreciate your opinion.

On Fri, Jan 20, 2017 at 02:03:11PM -, Sam Hartman wrote:
> So, while I think your concern is reasonable, I'd urge you to consider
> that you're setting a really high bar here for backporting a patch that
> an interoperability-conscious upstream has vetted.

I'm more bothered that we've considered and weighed up the non-Windows
use case. I hadn't yet set a bar - I was just asking for regressions in
all use cases to be considered and that consideration documented, as is
SRU policy. This helps us reach a decision, and should ideally have
happened first, before the SRU was accepted into the proposed pocket.

I'm convinced by your arguments, so I'm happy with the testing already
performed. Thank you to Bruce and Joshua for your work on this.

We don't usually release SRUs on Fridays in case of regression, but I'd
be happy to release this on Monday, subject to the usual checks.

Robie

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

Title:
  Add SPNEGO special case for NTLMSSP+MechListMIC

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Trusty:
  Fix Committed
Status in krb5 source package in Xenial:
  Fix Committed
Status in krb5 source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer
  needs to implement specifically for the NTLMSSP mechanism.  This is
  required for compatibility with Windows services.

  Upstream commit:
  https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9b7

  We've run into this issue with Linux to Windows negotiation with
  encrypted http using GSSAPI.

  [Test Case]

  create a file with some credentials:

  $ echo F23:guest:guest > ~/ntlmcreds.txt
  $ export NTLM_USER_FILE=~/ntlmcreds.txt
  $ python
  import gssapi

  spnego = gssapi.raw.oids.OID.from_int_seq('1.3.6.1.5.5.2')
  c = gssapi.creds.Credentials(mechs=[spnego], usage='initiate')
  tname = gssapi.raw.names.import_name("F23/server", 
name_type=gssapi.raw.types.NameType.hostbased_service)
  ac = gssapi.creds.Credentials(mechs=[spnego], usage='accept')

  seci = gssapi.SecurityContext(creds=c, name=tname, mech=spnego, 
usage='initiate')
  seca = gssapi.SecurityContext(creds=ac, usage='accept')
  it = seci.step(token=None)
  ot = seca.step(token=it)
  it = seci.step(token=ot)
  ot = seca.step(token=it)
  it = seci.step(token=ot)

  e = seci.wrap("Secrets", True)
  o = seca.unwrap(e.message)

  o.message
  'Secrets'

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

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

[Touch-packages] [Bug 1607666] Re: sudo fails with host netgroup returned from freeipa

2017-01-20 Thread Florian Apolloner

Can confirm that it works, just pulled it on our machines.

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

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

Title:
  sudo fails with host netgroup returned from freeipa

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Fix Committed
Status in sudo source package in Yakkety:
  New

Bug description:
  [Impact]
  Sudo currently fails to validate netgroups against host netgroups returned 
from the sss plugin, see https://fedorahosted.org/freeipa/ticket/6139 for the 
glory details.

  This was fixed in sudo 1.8.17
  (https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7 to be exact), which
  I'd very much like to see backported to Ubuntu 16.04. If possible,
  updating sudo completely to 1.8.17 would be nice, since there have
  been quite a few improvements with regards to sss and freeipa and it
  would be a shame if we could not benefit from them given that 16.04 is
  LTS.

  [Test case]
  install the update, test that sudo works on a freeipa installation that uses 
netgroups

  [Regression potential]
   I looked at upstream commits to sssd.c, and there were no commits 
that touch this area, so chance of regressions should be slim

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

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

[Touch-packages] [Bug 1658121] Re: TextArea: QtQuick.TextEdit append is not exposed

** Branch linked: lp:~daker/ubuntu-ui-toolkit/fix.1658121

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

Title:
  TextArea: QtQuick.TextEdit append is not exposed

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

Bug description:
  TextArea doesn't expose "append" as QtQuick.TextEdit does.

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

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

[Touch-packages] [Bug 1632715] Re: Can't receive MMS messages

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

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

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

Title:
  Can't receive MMS messages

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

Bug description:
  Hello!

  I'm using the Meizu MX4 on OTA 13 and my provider is Tele2 in Sweden.
  I have checked with Tele2 that everything works on there part, which they say 
it does.

  The bug is that when someone sends a MMS message to me nothing happenes.
  I can send MMS messages to others without problems.
  But not receive, no notification, nothing.

  Edit: I was able to receive MMS messages before OTA-10, during OTA-10
  and OTA-11 I got SMS messages with a link to a web page and a code.

  Best Regards
  / Rasmus

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

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

[Touch-packages] [Bug 1658121] Re: TextArea: QtQuick.TextEdit append is not exposed

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

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

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

Title:
  TextArea: QtQuick.TextEdit append is not exposed

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

Bug description:
  TextArea doesn't expose "append" as QtQuick.TextEdit does.

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

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

[Touch-packages] [Bug 1607666] Re: sudo fails with host netgroup returned from freeipa

2017-01-20 Thread Łukasz Zemczak

Hello Florian, or anyone else affected,

Accepted sudo into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sudo/1.8.16-0ubuntu1.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: sudo (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed

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

Title:
  sudo fails with host netgroup returned from freeipa

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Xenial:
  Fix Committed
Status in sudo source package in Yakkety:
  New

Bug description:
  [Impact]
  Sudo currently fails to validate netgroups against host netgroups returned 
from the sss plugin, see https://fedorahosted.org/freeipa/ticket/6139 for the 
glory details.

  This was fixed in sudo 1.8.17
  (https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7 to be exact), which
  I'd very much like to see backported to Ubuntu 16.04. If possible,
  updating sudo completely to 1.8.17 would be nice, since there have
  been quite a few improvements with regards to sss and freeipa and it
  would be a shame if we could not benefit from them given that 16.04 is
  LTS.

  [Test case]
  install the update, test that sudo works on a freeipa installation that uses 
netgroups

  [Regression potential]
   I looked at upstream commits to sssd.c, and there were no commits 
that touch this area, so chance of regressions should be slim

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

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

[Touch-packages] [Bug 1657875] Re: Google Chrome flickers badly on web pages

2017-01-20 Thread Brandon MacEachern

I can now officially confirm, that simply doing as you mentioned:

sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf

Section "Device"
   Identifier  "Intel Graphics"
   Driver  "intel"
   Option  "AccelMethod"  "sna"
   Option  "TearFree""true"
   Option  "DRI""3"
EndSection

Has FIXED the issue entirely.  I feel that this change should be made
permanent in 16.04 LTS to fix any Intel issues regarding sandy-bridge
GPU's or higher.

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

Title:
  Google Chrome flickers badly on web pages

Status in xorg package in Ubuntu:
  New

Bug description:
  In reference to: https://bugs.launchpad.net/ubuntu/+source/xserver-
  xorg-video-intel/+bug/1586539

  Was asked by Christopher M. Penalver (penalvch) to make this new bug
  report.

  Google chrome intermittently flickers (sometimes even Firefox I found,
  but very very rarely), and can cause a seizure in some people as it
  can flash between black and white 60 times a second.  This is a major
  issue that needs to be resolved as I'm sure many who are suffering
  this bug, feel as well.

  Please refer to the other bug report which is no "Incomplete" as it
  goes into more detail than I have time to honestly type out over
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 19 14:42:57 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:221e]
   NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K1100M] [17aa:221e]
  InstallationDate: Installed on 2016-10-10 (101 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=df32e7f0-11aa-4e43-98d8-fcd5bbeb2c05 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20EFCTO1WW:pvrThinkPadW541:rvnLENOVO:rn20EFCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20EFCTO1WW
  dmi.product.version: ThinkPad W541
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jan 19 10:52:11 2017
  xserver.configfile: default
  xserver.errors: open /dev/dri/card0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5571 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1658130] [NEW] contact names disappear / not displayed in pre-existing messaging conversations

2017-01-20 Thread Joe Liau

Public bug reported:

Mako
Rc-proposed

See attached screenshot. Contact names disappear from the messaging
conversation; only phone numbers are displayed.

This seems to happen when the app/system crashes. The problem tends to
resolve with a reboot.

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

** Attachment added: "screenshot20170120_071548176.png"
   
https://bugs.launchpad.net/bugs/1658130/+attachment/4806823/+files/screenshot20170120_071548176.png

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

Title:
  contact names disappear / not displayed in pre-existing messaging
  conversations

Status in messaging-app package in Ubuntu:
  New

Bug description:
  Mako
  Rc-proposed

  See attached screenshot. Contact names disappear from the messaging
  conversation; only phone numbers are displayed.

  This seems to happen when the app/system crashes. The problem tends to
  resolve with a reboot.

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

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

[Touch-packages] [Bug 1657082] Re: Menu items don't close when pressing them

2017-01-20 Thread Albert Astals Cid

** Branch linked: lp:~aacid/unity8/closeMenusOnClick

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

Title:
  Menu items don't close when pressing them

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Clicking on a menu popup item (e.g. "Edit" -> "Search" in dolphin)
  doesn't hide the menu while it does in unity7.

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

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

[Touch-packages] [Bug 1636337] Re: merge telegram with the messaging app

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

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

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

Title:
  merge telegram with the messaging app

Status in messaging-app package in Ubuntu:
  Confirmed

Bug description:
  The messaging app is suppose to be the main messaging app for all
  types of messages, so if canonical is making both the telegram and
  default messaging app, there'll be some duplicated efforts.

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

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

[Touch-packages] [Bug 1658121] Re: TextArea: QtQuick.TextEdit append is not exposed

** Branch linked: lp:~daker/ubuntu-ui-toolkit/fix.1658121

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

Title:
  TextArea: QtQuick.TextEdit append is not exposed

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

Bug description:
  TextArea doesn't expose "append" as QtQuick.TextEdit does.

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

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

[Touch-packages] [Bug 1652835] Re: [MUST FIX]package kde-config-telepathy-accounts (not installed) failed to install/upgrade: Package System Critical and Wrecked from previous issues encountered

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

** Information type changed from Public Security to Public

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

Title:
  [MUST FIX]package kde-config-telepathy-accounts (not installed) failed
  to install/upgrade: Package System Critical and Wrecked from previous
  issues encountered

Status in account-plugins package in Ubuntu:
  New
Status in ktp-accounts-kcm package in Ubuntu:
  New
Status in telepathy-accounts-signon package in Ubuntu:
  Incomplete

Bug description:
  Worse Besides this, my entire package system is broken, and I've tried
  every command in terminal to fix this. PLEASE HELP FIX THIS

  NOTE: Tried every resource to help me.
  Please set Importance to critical...Package System/System itself
  HAS BEEN BREACHED!!!

  ProblemType: ENTIRE/WHOLE Package System
  DistroRelease: Ubuntu 16.04 (With or without LTS)
  Package: kde-config-telepathy-accounts (not installed)/ Any kind of package 
avalible for installtion, including anything from the Ubuntu Software Center!
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.2
  AptOrdering:
   kde-config-telepathy-accounts: Install
   kde-config-telepathy-accounts: Configure
   kde-telepathy-minimal: Configure
   kde-telepathy: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Dec 27 12:57:53 2016
  DpkgTerminalLog:
   Preparing to unpack 
.../kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb ...
   Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack)
  DuplicateSignature:
   package:kde-config-telepathy-accounts:(not installed)
   Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack):
  ErrorMessage: E: Sub-process /usr/bin/dpkg returned an error code (1)
  InstallationDate: Installed on 2016-12-08 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: ktp-accounts-kcm
  Title: [MUST FIX]package kde-config-telepathy-accounts (not installed) failed 
to install/upgrade: Package System Critical and Wrecked from previous issues 
encountered
  UpgradeStatus: N/A Permanent

  Issue related to this on launchpad.net, click below...(Photo Only)
  
https://launchpadlibrarian.net/300380104/Screenshot%20from%202016-12-27%2016-38-18.png

  Link to Issue on website:
  https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1013856

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1652835/+subscriptions

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

[Touch-packages] [Bug 1656727] Re: Unity8 crashes and restarts when clicking on a menu [terminate called after throwing an instance of 'std::out_of_range' what(): map::at]

2017-01-20 Thread Alan Griffiths

** Changed in: miral
   Status: Confirmed => Incomplete

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

** Changed in: miral (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Unity8 crashes and restarts when clicking on a menu [terminate called
  after throwing an instance of 'std::out_of_range' what():  map::at]

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Incomplete
Status in MirAL:
  Incomplete
Status in QtMir:
  Confirmed
Status in miral package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Unity8 crashes and restarts when clicking on a menu:

  terminate called after throwing an instance of 'std::out_of_range'
    what():  map::at

  Test case:
    1. Launch AisleRiot
    2. Click on a menu

  Expected: Menu opens
  Observed: Unity8 crashes and restarts every time

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170110.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  Date: Mon Jan 16 10:29:08 2017
  InstallationDate: Installed on 2016-11-03 (74 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1658121] [NEW] TextArea: QtQuick.TextEdit append is not exposed

2017-01-20 Thread Adnane Belmadiaf

Public bug reported:

TextArea doesn't expose "append" as QtQuick.TextEdit does.

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

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

Title:
  TextArea: QtQuick.TextEdit append is not exposed

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

Bug description:
  TextArea doesn't expose "append" as QtQuick.TextEdit does.

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

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

[Touch-packages] [Bug 1656621] Re: package libgssapi3-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemp

2017-01-20 Thread 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 heimdal in Ubuntu.
https://bugs.launchpad.net/bugs/1656621

Title:
  package libgssapi3-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in heimdal package in Ubuntu:
  New

Bug description:
  Having problem is installing the debian packeges

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libgssapi3-heimdal:i386 1.6~rc2+dfsg-10ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sun Jan 15 12:25:54 2017
  DuplicateSignature: 
package:libgssapi3-heimdal:i386:1.6~rc2+dfsg-10ubuntu1:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-03-10 (310 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu3
  SourcePackage: heimdal
  Title: package libgssapi3-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1656621] Re: package libgssapi3-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemp

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

** Information type changed from Private Security to Public

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

Title:
  package libgssapi3-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in heimdal package in Ubuntu:
  New

Bug description:
  Having problem is installing the debian packeges

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libgssapi3-heimdal:i386 1.6~rc2+dfsg-10ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sun Jan 15 12:25:54 2017
  DuplicateSignature: 
package:libgssapi3-heimdal:i386:1.6~rc2+dfsg-10ubuntu1:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-03-10 (310 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu3
  SourcePackage: heimdal
  Title: package libgssapi3-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1658117] [NEW] Camera app shows top menu

2017-01-20 Thread Víctor R . Ruiz

Public bug reported:

Test case.
- Open camera in device mode.

Expected result.
- Camera opens full screen and top menu hides.

Actual result.
- Camera opens full screen but top menu is not hidden.

current build number: 127
device name: frieza_arm64
channel: ubuntu-touch/staging/ubuntu

** Affects: canonical-devices-system-image
Importance: Undecided
Status: New

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

** Attachment added: "screenshot20170120_150844333.png"

https://bugs.launchpad.net/bugs/1658117/+attachment/4806821/+files/screenshot20170120_150844333.png

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

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

Title:
Camera app shows top menu

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

Bug description:
Test case.
- Open camera in device mode.

Expected result.
- Camera opens full screen and top menu hides.

Actual result.
- Camera opens full screen but top menu is not hidden.

current build number: 127
device name: frieza_arm64
channel: ubuntu-touch/staging/ubuntu

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

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

[Touch-packages] [Bug 1657495] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 1

2017-01-20 Thread 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 perl in Ubuntu.
https://bugs.launchpad.net/bugs/1657495

Title:
  package libperl5.22 5.22.1-9 failed to install/upgrade: el subproceso
  script pre-installation nuevo devolvió el código de salida de error 1

Status in perl package in Ubuntu:
  New

Bug description:
  i Can't update my dist

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Wed Jan 18 11:03:59 2017
  DuplicateSignature:
   package:libperl5.22:5.22.1-9
   Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ...
   dpkg-maintscript-helper: error: original symlink target is not an absolute 
path
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
el subproceso script pre-installation nuevo devolvió el código de salida de 
error 1
  ErrorMessage: el subproceso script pre-installation nuevo devolvió el código 
de salida de error 1
  InstallationDate: Installed on 2017-01-17 (1 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.0.9.2ubuntu2
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 failed to install/upgrade: el subproceso 
script pre-installation nuevo devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1657495] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 1

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

** Information type changed from Private Security to Public

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

Title:
  package libperl5.22 5.22.1-9 failed to install/upgrade: el subproceso
  script pre-installation nuevo devolvió el código de salida de error 1

Status in perl package in Ubuntu:
  New

Bug description:
  i Can't update my dist

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libperl5.22 5.22.1-9
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Wed Jan 18 11:03:59 2017
  DuplicateSignature:
   package:libperl5.22:5.22.1-9
   Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ...
   dpkg-maintscript-helper: error: original symlink target is not an absolute 
path
   dpkg: error processing archive 
/var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack):
el subproceso script pre-installation nuevo devolvió el código de salida de 
error 1
  ErrorMessage: el subproceso script pre-installation nuevo devolvió el código 
de salida de error 1
  InstallationDate: Installed on 2017-01-17 (1 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.0.9.2ubuntu2
  SourcePackage: perl
  Title: package libperl5.22 5.22.1-9 failed to install/upgrade: el subproceso 
script pre-installation nuevo devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1657882] Re: wine

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

** Information type changed from Private Security to Public

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

Title:
  wine

Status in xorg package in Ubuntu:
  New

Bug description:
  cant install wine

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jan 19 21:39:58 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8330] [1025:104b]
  InstallationDate: Installed on 2016-12-01 (49 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Acer Aspire ES1-520
  ProcEnviron:
   LANGUAGE=hr
   PATH=(custom, no user)
   LANG=hr_HR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=073388fc-a929-4eae-81b3-5f775ced2d93 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Bellemere_BE
  dmi.board.vendor: Acer
  dmi.board.version: V1.06
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-520:pvrV1.06:rvnAcer:rnBellemere_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion:
  dmi.product.name: Aspire ES1-520
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jan 19 21:37:31 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1658102] [NEW] going full screen locks out all other apps and system

2017-01-20 Thread ssameer ssierra

Public bug reported:

full screen on almost any app(that allows full screen) causes the entire
rest of the system to be locked out, cannot kill or force quit or alt
tab to anything else, must use kill xserver command ctrl alt backspace.

after relogging in, the same action, fullscreen on same app can be
toggled many times and works normally, but will eventually happen again.
even though i've experienced this over several releases and it's
happened many times, i can't see any pattern or cause for what will make
this happen.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Jan 20 08:46:53 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.24, 4.4.0-57-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-59-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:191e] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake Integrated Graphics [17aa:380e]
InstallationDate: Installed on 2016-10-30 (82 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 80QE
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed 
root=UUID=2bcfd691-709a-43ea-888c-049a926760ab ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: DDCN20WW(V1.04)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo YOGA 700-
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 700-11ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrDDCN20WW(V1.04):bd09/21/2015:svnLENOVO:pn80QE:pvrLenovoYOGA700-11ISK:rvnLENOVO:rnLenovoYOGA700-:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA700-11ISK:
dmi.product.name: 80QE
dmi.product.version: Lenovo YOGA 700-11ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.74+git1701191830.9e4c68~gd~x
version.libgl1-mesa-dri: libgl1-mesa-dri 17.1~git1701200730.414888~gd~x
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1~git1701200730.414888~gd~x
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.8.99+git1701071933.ea30d8~gd~x
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1701040733.028c94~gd~x
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.13+git1610280732.1516d3~gd~x
xserver.bootTime: Fri Jan 20 07:40:58 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   20573 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

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

Title:
  going full screen locks out all other apps and system

Status in xorg package in Ubuntu:
  New

Bug description:
  full screen on almost any app(that allows full screen) causes the
  entire rest of the system to be locked out, cannot kill or force quit
  or alt tab to anything else, must use kill xserver command ctrl alt
  backspace.

  after relogging in, the same action, fullscreen on same app can be
  toggled many times and works normally, but will eventually happen
  again. even though i've experienced this over several releases and
  it's happened many times, i can't see any pattern or cause for what
  will make this happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBla

[Touch-packages] [Bug 1637601] xenial_libvirt_uidgid.debdiff

Default Comment by Bridge

** Attachment added: "xenial_libvirt_uidgid.debdiff"
   
https://bugs.launchpad.net/bugs/1637601/+attachment/4806791/+files/xenial_libvirt_uidgid.debdiff

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in base-passwd source package in Xenial:
  Won't Fix
Status in libvirt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users performing live migration of guests with image files
     shared over NFS between the source and target host systems
     may experience I/O errors in the guests if user id of the
     libvirt-qemu user differs between the host systems, due to
     permission errors when accessing the image files.

   * The 16.04 LTS is an important stream for KVM (at least on
     Power), and guest live migration over NFS is an important
     feature on it.

   * The proposed fix (a minimal backport from what is applied
     on Zesty/Debian, so to be very conservative for the LTS)
     simply tries to use the reserved uid for the libvirt-qemu
     user on new installations (when the user is created) if
     the reserved uid is not taken by another user (no failures
     occur if the libvirt-qemu user already exists or the uid
     is taken.)

  [Test Case]

   * Setup 2x systems with Ubuntu 16.04 LTS as KVM hosts (e.g., micro and tiny)
     (check whether the libvirt-qemu uid differs between them;
  e.g. # id libvirt-qemu )

   * Create a guest in the source KVM host system (e.g, microg5)

   * Live migrate the guest to the destination KVM host system (e.g.,
  tiny)

     root@micro:~# virsh migrate --live --domain microg5 qemu+ssh://tiny/system
   --verbose --undefinesource --persistent --timeout 60
     Migration: [100 %]

   * Check whether the guest is now listed in the destination KVM host
  system:

  root@tiny:~# virsh list --all
  Id Name State

  12 microg5 running

   * Check whether I/O errors are seen in that guest:

  root@microg5:~# dmesg
  ...
  [ 60.818955] blk_update_request: I/O error, dev vdc, sector 96749232
  [ 60.819113] Aborting journal on device vdc2-8.
  [ 60.820121] blk_update_request: I/O error, dev vdc, sector 9084320
  [ 60.820643] EXT4-fs warning (device vdc2): ext4_end_bio:329: I/O error
   -5 writing to inode 393279 (offset 0 size 0 ...

  * Simplified test of the wanted effect:
- install libvirt on a system that didn't have it before and check the  
  id of libvirt-qemu
$ id libvirt-qemu

  [Regression Potential]

   * On installations in which the libvirt-qemu user does not exist
     (e.g., first time installation of libvirt-bin) its assigned uid
     might be different from what the user previously expected, since
     now it's assigned a number from the reserved range.

   * Overall, the fix is very conservative (the uid assignment only
     happens in case: 1) the libvirt-qemu user is being created, and
     2) if the desired uid is not taken by another user, e.g. LDAP).

  [Other Info]

   * None at this time.

  <...>

  Please see comment #8 for the problem description, and summary of
  originally bridged comments in the description in later comments.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1637601] sid_base-passwd_libvirt.debdiff

Default Comment by Bridge

** Attachment added: "sid_base-passwd_libvirt.debdiff"
   
https://bugs.launchpad.net/bugs/1637601/+attachment/4806792/+files/sid_base-passwd_libvirt.debdiff

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in base-passwd source package in Xenial:
  Won't Fix
Status in libvirt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users performing live migration of guests with image files
     shared over NFS between the source and target host systems
     may experience I/O errors in the guests if user id of the
     libvirt-qemu user differs between the host systems, due to
     permission errors when accessing the image files.

   * The 16.04 LTS is an important stream for KVM (at least on
     Power), and guest live migration over NFS is an important
     feature on it.

   * The proposed fix (a minimal backport from what is applied
     on Zesty/Debian, so to be very conservative for the LTS)
     simply tries to use the reserved uid for the libvirt-qemu
     user on new installations (when the user is created) if
     the reserved uid is not taken by another user (no failures
     occur if the libvirt-qemu user already exists or the uid
     is taken.)

  [Test Case]

   * Setup 2x systems with Ubuntu 16.04 LTS as KVM hosts (e.g., micro and tiny)
     (check whether the libvirt-qemu uid differs between them;
  e.g. # id libvirt-qemu )

   * Create a guest in the source KVM host system (e.g, microg5)

   * Live migrate the guest to the destination KVM host system (e.g.,
  tiny)

     root@micro:~# virsh migrate --live --domain microg5 qemu+ssh://tiny/system
   --verbose --undefinesource --persistent --timeout 60
     Migration: [100 %]

   * Check whether the guest is now listed in the destination KVM host
  system:

  root@tiny:~# virsh list --all
  Id Name State

  12 microg5 running

   * Check whether I/O errors are seen in that guest:

  root@microg5:~# dmesg
  ...
  [ 60.818955] blk_update_request: I/O error, dev vdc, sector 96749232
  [ 60.819113] Aborting journal on device vdc2-8.
  [ 60.820121] blk_update_request: I/O error, dev vdc, sector 9084320
  [ 60.820643] EXT4-fs warning (device vdc2): ext4_end_bio:329: I/O error
   -5 writing to inode 393279 (offset 0 size 0 ...

  * Simplified test of the wanted effect:
- install libvirt on a system that didn't have it before and check the  
  id of libvirt-qemu
$ id libvirt-qemu

  [Regression Potential]

   * On installations in which the libvirt-qemu user does not exist
     (e.g., first time installation of libvirt-bin) its assigned uid
     might be different from what the user previously expected, since
     now it's assigned a number from the reserved range.

   * Overall, the fix is very conservative (the uid assignment only
     happens in case: 1) the libvirt-qemu user is being created, and
     2) if the desired uid is not taken by another user, e.g. LDAP).

  [Other Info]

   * None at this time.

  <...>

  Please see comment #8 for the problem description, and summary of
  originally bridged comments in the description in later comments.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1637601] xenial_libvirt_uidgid_v2.debdiff

Default Comment by Bridge

** Attachment added: "xenial_libvirt_uidgid_v2.debdiff"
   
https://bugs.launchpad.net/bugs/1637601/+attachment/4806794/+files/xenial_libvirt_uidgid_v2.debdiff

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in base-passwd source package in Xenial:
  Won't Fix
Status in libvirt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users performing live migration of guests with image files
     shared over NFS between the source and target host systems
     may experience I/O errors in the guests if user id of the
     libvirt-qemu user differs between the host systems, due to
     permission errors when accessing the image files.

   * The 16.04 LTS is an important stream for KVM (at least on
     Power), and guest live migration over NFS is an important
     feature on it.

   * The proposed fix (a minimal backport from what is applied
     on Zesty/Debian, so to be very conservative for the LTS)
     simply tries to use the reserved uid for the libvirt-qemu
     user on new installations (when the user is created) if
     the reserved uid is not taken by another user (no failures
     occur if the libvirt-qemu user already exists or the uid
     is taken.)

  [Test Case]

   * Setup 2x systems with Ubuntu 16.04 LTS as KVM hosts (e.g., micro and tiny)
     (check whether the libvirt-qemu uid differs between them;
  e.g. # id libvirt-qemu )

   * Create a guest in the source KVM host system (e.g, microg5)

   * Live migrate the guest to the destination KVM host system (e.g.,
  tiny)

     root@micro:~# virsh migrate --live --domain microg5 qemu+ssh://tiny/system
   --verbose --undefinesource --persistent --timeout 60
     Migration: [100 %]

   * Check whether the guest is now listed in the destination KVM host
  system:

  root@tiny:~# virsh list --all
  Id Name State

  12 microg5 running

   * Check whether I/O errors are seen in that guest:

  root@microg5:~# dmesg
  ...
  [ 60.818955] blk_update_request: I/O error, dev vdc, sector 96749232
  [ 60.819113] Aborting journal on device vdc2-8.
  [ 60.820121] blk_update_request: I/O error, dev vdc, sector 9084320
  [ 60.820643] EXT4-fs warning (device vdc2): ext4_end_bio:329: I/O error
   -5 writing to inode 393279 (offset 0 size 0 ...

  * Simplified test of the wanted effect:
- install libvirt on a system that didn't have it before and check the  
  id of libvirt-qemu
$ id libvirt-qemu

  [Regression Potential]

   * On installations in which the libvirt-qemu user does not exist
     (e.g., first time installation of libvirt-bin) its assigned uid
     might be different from what the user previously expected, since
     now it's assigned a number from the reserved range.

   * Overall, the fix is very conservative (the uid assignment only
     happens in case: 1) the libvirt-qemu user is being created, and
     2) if the desired uid is not taken by another user, e.g. LDAP).

  [Other Info]

   * None at this time.

  <...>

  Please see comment #8 for the problem description, and summary of
  originally bridged comments in the description in later comments.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1637601] chig6_migration logs

--- Comment on attachment From lakun...@in.ibm.com 2016-11-14 12:42 
EDT---


Machine Details:
=
Note:- 

System is on a private network.  Access the private network via SSH to 
"banner.isst.aus.stglabs.ibm.com" using your GSA ID and password. 
(Banner itself is behind a BSO, so must authenticate through that first.)

Login details :  
ssh banner.isst.aus.stglabs.ibm.com [debug/don2rry]

Source Host login:-
chikvm.isst.aus.stglabs.ibm.com [10.33.7.207]
[root/don2rry]

Destination Host Login:-
guskvm.isst.aus.stglabs.ibm.com has address 10.33.32.222

start Guest Login :-
virsh console chig6 --force

IPMI Login :- 
-
>From banner machine run the following :
ssh banner.isst.aus.stglabs.ibm.com [debug/don2rry ]

ipmitool -I lanplus -H fsp-chi  -P don2rry sol deactivate
ipmitool -I lanplus -H fsp-chi  -P don2rry sol activate


-
 TESTING INFORMATION
-

SYSTEM INFORMATION
--
  HOST NAME or NETWORK ADDRESS:   chikvm.isst.aus.stglabs.ibm.com
 [10.33.7.207]
guskvm..isst.aus.stglabs.ibm.com 10.33.32.222
   
  Sapphire FIRMWARE LEVEL:  - FW860.00 (SV860_056)

-
DEBUGGING INFORMATION
-
   
DEBUG / LOGIN INFORMATION 
- 
  ERROR LOG: on local machine 
  FSP LOGIN: see name above  [dev/FipSdev]
RECENT SYSTEM CHANGES  : none
-
  none

** Attachment added: "chig6_migration logs"
   
https://bugs.launchpad.net/bugs/1637601/+attachment/4806795/+files/logs_mig.zip

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in base-passwd source package in Xenial:
  Won't Fix
Status in libvirt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users performing live migration of guests with image files
     shared over NFS between the source and target host systems
     may experience I/O errors in the guests if user id of the
     libvirt-qemu user differs between the host systems, due to
     permission errors when accessing the image files.

   * The 16.04 LTS is an important stream for KVM (at least on
     Power), and guest live migration over NFS is an important
     feature on it.

   * The proposed fix (a minimal backport from what is applied
     on Zesty/Debian, so to be very conservative for the LTS)
     simply tries to use the reserved uid for the libvirt-qemu
     user on new installations (when the user is created) if
     the reserved uid is not taken by another user (no failures
     occur if the libvirt-qemu user already exists or the uid
     is taken.)

  [Test Case]

   * Setup 2x systems with Ubuntu 16.04 LTS as KVM hosts (e.g., micro and tiny)
     (check whether the libvirt-qemu uid differs between them;
  e.g. # id libvirt-qemu )

   * Create a guest in the source KVM host system (e.g, microg5)

   * Live migrate the guest to the destination KVM host system (e.g.,
  tiny)

     root@micro:~# virsh migrate --live --domain microg5 qemu+ssh://tiny/system
   --verbose --undefinesource --persistent --timeout 60
     Migration: [100 %]

   * Check whether the guest is now listed in the destination KVM host
  system:

  root@tiny:~# virsh list --all
  Id Name State

  12 microg5 running

   * Check whether I/O errors are seen in that guest:

  root@microg5:~# dmesg
  ...
  [ 60.818955] blk_update_request: I/O error, dev vdc, sector 96749232
  [ 60.819113] Aborting journal on device vdc2-8.
  [ 60.820121] blk_update_request: I/O error, dev vdc, sector 9084320
  [ 60.820643] EXT4-fs warning (device vdc2): ext4_end_bio:329: I/O error
   -5 writing to inode 393279 (offset 0 size 0 ...

  * Simplified test of the wanted effect:
- install libvirt on a system that didn't have it before and check the  
  id of libvirt-qemu
$ id libvirt-qemu

  [Regression Potential]

   * On installations in which the libvirt-qemu user does not exist
     (e.g., first time installation of libvirt-bin) its assigned uid
     might be different from what the user previously expected, since
     now it's assigned a number from the reserved range.

   * Overall, the fix is very conservative (the uid assignment only
     happens in case: 1) the libvirt-qemu user is being created, and
     2) if the desired ui

[Touch-packages] [Bug 1637601] zesty_libvirt_uidgid.debdiff

Default Comment by Bridge

** Attachment added: "zesty_libvirt_uidgid.debdiff"
   
https://bugs.launchpad.net/bugs/1637601/+attachment/4806789/+files/zesty_libvirt_uidgid.debdiff

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in base-passwd source package in Xenial:
  Won't Fix
Status in libvirt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users performing live migration of guests with image files
     shared over NFS between the source and target host systems
     may experience I/O errors in the guests if user id of the
     libvirt-qemu user differs between the host systems, due to
     permission errors when accessing the image files.

   * The 16.04 LTS is an important stream for KVM (at least on
     Power), and guest live migration over NFS is an important
     feature on it.

   * The proposed fix (a minimal backport from what is applied
     on Zesty/Debian, so to be very conservative for the LTS)
     simply tries to use the reserved uid for the libvirt-qemu
     user on new installations (when the user is created) if
     the reserved uid is not taken by another user (no failures
     occur if the libvirt-qemu user already exists or the uid
     is taken.)

  [Test Case]

   * Setup 2x systems with Ubuntu 16.04 LTS as KVM hosts (e.g., micro and tiny)
     (check whether the libvirt-qemu uid differs between them;
  e.g. # id libvirt-qemu )

   * Create a guest in the source KVM host system (e.g, microg5)

   * Live migrate the guest to the destination KVM host system (e.g.,
  tiny)

     root@micro:~# virsh migrate --live --domain microg5 qemu+ssh://tiny/system
   --verbose --undefinesource --persistent --timeout 60
     Migration: [100 %]

   * Check whether the guest is now listed in the destination KVM host
  system:

  root@tiny:~# virsh list --all
  Id Name State

  12 microg5 running

   * Check whether I/O errors are seen in that guest:

  root@microg5:~# dmesg
  ...
  [ 60.818955] blk_update_request: I/O error, dev vdc, sector 96749232
  [ 60.819113] Aborting journal on device vdc2-8.
  [ 60.820121] blk_update_request: I/O error, dev vdc, sector 9084320
  [ 60.820643] EXT4-fs warning (device vdc2): ext4_end_bio:329: I/O error
   -5 writing to inode 393279 (offset 0 size 0 ...

  * Simplified test of the wanted effect:
- install libvirt on a system that didn't have it before and check the  
  id of libvirt-qemu
$ id libvirt-qemu

  [Regression Potential]

   * On installations in which the libvirt-qemu user does not exist
     (e.g., first time installation of libvirt-bin) its assigned uid
     might be different from what the user previously expected, since
     now it's assigned a number from the reserved range.

   * Overall, the fix is very conservative (the uid assignment only
     happens in case: 1) the libvirt-qemu user is being created, and
     2) if the desired uid is not taken by another user, e.g. LDAP).

  [Other Info]

   * None at this time.

  <...>

  Please see comment #8 for the problem description, and summary of
  originally bridged comments in the description in later comments.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1637601] xenial_libvirt_uid_v4.debdiff

Default Comment by Bridge

** Attachment added: "xenial_libvirt_uid_v4.debdiff"
   
https://bugs.launchpad.net/bugs/1637601/+attachment/4806796/+files/xenial_libvirt_uidgid_v4.debdiff

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in base-passwd source package in Xenial:
  Won't Fix
Status in libvirt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users performing live migration of guests with image files
     shared over NFS between the source and target host systems
     may experience I/O errors in the guests if user id of the
     libvirt-qemu user differs between the host systems, due to
     permission errors when accessing the image files.

   * The 16.04 LTS is an important stream for KVM (at least on
     Power), and guest live migration over NFS is an important
     feature on it.

   * The proposed fix (a minimal backport from what is applied
     on Zesty/Debian, so to be very conservative for the LTS)
     simply tries to use the reserved uid for the libvirt-qemu
     user on new installations (when the user is created) if
     the reserved uid is not taken by another user (no failures
     occur if the libvirt-qemu user already exists or the uid
     is taken.)

  [Test Case]

   * Setup 2x systems with Ubuntu 16.04 LTS as KVM hosts (e.g., micro and tiny)
     (check whether the libvirt-qemu uid differs between them;
  e.g. # id libvirt-qemu )

   * Create a guest in the source KVM host system (e.g, microg5)

   * Live migrate the guest to the destination KVM host system (e.g.,
  tiny)

     root@micro:~# virsh migrate --live --domain microg5 qemu+ssh://tiny/system
   --verbose --undefinesource --persistent --timeout 60
     Migration: [100 %]

   * Check whether the guest is now listed in the destination KVM host
  system:

  root@tiny:~# virsh list --all
  Id Name State

  12 microg5 running

   * Check whether I/O errors are seen in that guest:

  root@microg5:~# dmesg
  ...
  [ 60.818955] blk_update_request: I/O error, dev vdc, sector 96749232
  [ 60.819113] Aborting journal on device vdc2-8.
  [ 60.820121] blk_update_request: I/O error, dev vdc, sector 9084320
  [ 60.820643] EXT4-fs warning (device vdc2): ext4_end_bio:329: I/O error
   -5 writing to inode 393279 (offset 0 size 0 ...

  * Simplified test of the wanted effect:
- install libvirt on a system that didn't have it before and check the  
  id of libvirt-qemu
$ id libvirt-qemu

  [Regression Potential]

   * On installations in which the libvirt-qemu user does not exist
     (e.g., first time installation of libvirt-bin) its assigned uid
     might be different from what the user previously expected, since
     now it's assigned a number from the reserved range.

   * Overall, the fix is very conservative (the uid assignment only
     happens in case: 1) the libvirt-qemu user is being created, and
     2) if the desired uid is not taken by another user, e.g. LDAP).

  [Other Info]

   * None at this time.

  <...>

  Please see comment #8 for the problem description, and summary of
  originally bridged comments in the description in later comments.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1637601] sid_libvirt_uidgid.debdiff

Default Comment by Bridge

** Attachment added: "sid_libvirt_uidgid.debdiff"
   
https://bugs.launchpad.net/bugs/1637601/+attachment/4806793/+files/sid_libvirt_uidgid.debdiff

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in base-passwd source package in Xenial:
  Won't Fix
Status in libvirt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users performing live migration of guests with image files
     shared over NFS between the source and target host systems
     may experience I/O errors in the guests if user id of the
     libvirt-qemu user differs between the host systems, due to
     permission errors when accessing the image files.

   * The 16.04 LTS is an important stream for KVM (at least on
     Power), and guest live migration over NFS is an important
     feature on it.

   * The proposed fix (a minimal backport from what is applied
     on Zesty/Debian, so to be very conservative for the LTS)
     simply tries to use the reserved uid for the libvirt-qemu
     user on new installations (when the user is created) if
     the reserved uid is not taken by another user (no failures
     occur if the libvirt-qemu user already exists or the uid
     is taken.)

  [Test Case]

   * Setup 2x systems with Ubuntu 16.04 LTS as KVM hosts (e.g., micro and tiny)
     (check whether the libvirt-qemu uid differs between them;
  e.g. # id libvirt-qemu )

   * Create a guest in the source KVM host system (e.g, microg5)

   * Live migrate the guest to the destination KVM host system (e.g.,
  tiny)

     root@micro:~# virsh migrate --live --domain microg5 qemu+ssh://tiny/system
   --verbose --undefinesource --persistent --timeout 60
     Migration: [100 %]

   * Check whether the guest is now listed in the destination KVM host
  system:

  root@tiny:~# virsh list --all
  Id Name State

  12 microg5 running

   * Check whether I/O errors are seen in that guest:

  root@microg5:~# dmesg
  ...
  [ 60.818955] blk_update_request: I/O error, dev vdc, sector 96749232
  [ 60.819113] Aborting journal on device vdc2-8.
  [ 60.820121] blk_update_request: I/O error, dev vdc, sector 9084320
  [ 60.820643] EXT4-fs warning (device vdc2): ext4_end_bio:329: I/O error
   -5 writing to inode 393279 (offset 0 size 0 ...

  * Simplified test of the wanted effect:
- install libvirt on a system that didn't have it before and check the  
  id of libvirt-qemu
$ id libvirt-qemu

  [Regression Potential]

   * On installations in which the libvirt-qemu user does not exist
     (e.g., first time installation of libvirt-bin) its assigned uid
     might be different from what the user previously expected, since
     now it's assigned a number from the reserved range.

   * Overall, the fix is very conservative (the uid assignment only
     happens in case: 1) the libvirt-qemu user is being created, and
     2) if the desired uid is not taken by another user, e.g. LDAP).

  [Other Info]

   * None at this time.

  <...>

  Please see comment #8 for the problem description, and summary of
  originally bridged comments in the description in later comments.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1637601] xenial_base-passwd_libvirt.debdiff

Default Comment by Bridge

** Attachment added: "xenial_base-passwd_libvirt.debdiff"
   
https://bugs.launchpad.net/bugs/1637601/+attachment/4806790/+files/xenial_base-passwd_libvirt.debdiff

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in base-passwd source package in Xenial:
  Won't Fix
Status in libvirt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users performing live migration of guests with image files
     shared over NFS between the source and target host systems
     may experience I/O errors in the guests if user id of the
     libvirt-qemu user differs between the host systems, due to
     permission errors when accessing the image files.

   * The 16.04 LTS is an important stream for KVM (at least on
     Power), and guest live migration over NFS is an important
     feature on it.

   * The proposed fix (a minimal backport from what is applied
     on Zesty/Debian, so to be very conservative for the LTS)
     simply tries to use the reserved uid for the libvirt-qemu
     user on new installations (when the user is created) if
     the reserved uid is not taken by another user (no failures
     occur if the libvirt-qemu user already exists or the uid
     is taken.)

  [Test Case]

   * Setup 2x systems with Ubuntu 16.04 LTS as KVM hosts (e.g., micro and tiny)
     (check whether the libvirt-qemu uid differs between them;
  e.g. # id libvirt-qemu )

   * Create a guest in the source KVM host system (e.g, microg5)

   * Live migrate the guest to the destination KVM host system (e.g.,
  tiny)

     root@micro:~# virsh migrate --live --domain microg5 qemu+ssh://tiny/system
   --verbose --undefinesource --persistent --timeout 60
     Migration: [100 %]

   * Check whether the guest is now listed in the destination KVM host
  system:

  root@tiny:~# virsh list --all
  Id Name State

  12 microg5 running

   * Check whether I/O errors are seen in that guest:

  root@microg5:~# dmesg
  ...
  [ 60.818955] blk_update_request: I/O error, dev vdc, sector 96749232
  [ 60.819113] Aborting journal on device vdc2-8.
  [ 60.820121] blk_update_request: I/O error, dev vdc, sector 9084320
  [ 60.820643] EXT4-fs warning (device vdc2): ext4_end_bio:329: I/O error
   -5 writing to inode 393279 (offset 0 size 0 ...

  * Simplified test of the wanted effect:
- install libvirt on a system that didn't have it before and check the  
  id of libvirt-qemu
$ id libvirt-qemu

  [Regression Potential]

   * On installations in which the libvirt-qemu user does not exist
     (e.g., first time installation of libvirt-bin) its assigned uid
     might be different from what the user previously expected, since
     now it's assigned a number from the reserved range.

   * Overall, the fix is very conservative (the uid assignment only
     happens in case: 1) the libvirt-qemu user is being created, and
     2) if the desired uid is not taken by another user, e.g. LDAP).

  [Other Info]

   * None at this time.

  <...>

  Please see comment #8 for the problem description, and summary of
  originally bridged comments in the description in later comments.

  Sorry about the inconvenience.

  <...>

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

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

[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190

--- Comment From mauri...@br.ibm.com 2017-01-20 08:47 EDT---
Verification done with Xenial. All good!

# lsb_release -d
Description:Ubuntu 16.04.1 LTS

Previous Package:


0) No existing user/uid:

# id libvirt-qemu
id: ?libvirt-qemu?: no such user

# getent passwd 64055
#

User is created w/ the next available uid

# apt-get install --yes --no-install-recommends
libvirt{0,-bin}=1.3.1-1ubuntu10.6

# id libvirt-qemu
uid=110(libvirt-qemu) gid=117(kvm) groups=117(kvm)

# getent passwd 64055
#

Proposed Package:


1) With existing user (e.g., package update)

# id libvirt-qemu
uid=110(libvirt-qemu) gid=117(kvm) groups=117(kvm)

User uid remains the same:

# apt-get install --yes --no-install-recommends
libvirt{0,-bin}=1.3.1-1ubuntu10.7

# id libvirt-qemu
uid=110(libvirt-qemu) gid=117(kvm) groups=117(kvm)

# getent passwd 64055
#

2) Without existing user (e.g., new install)

# apt-get purge --yes libvirt{0,-bin}
Reading package lists... Done

# userdel libvirt-qemu

# id libvirt-qemu
id: ?libvirt-qemu?: no such user

# getent passwd 64055
#

User uid is set to the reserved uid:

# apt-get install --yes --no-install-recommends
libvirt{0,-bin}=1.3.1-1ubuntu10.7

# id libvirt-qemu
uid=64055(libvirt-qemu) gid=117(kvm) groups=117(kvm)

# getent passwd 64055
libvirt-qemu:x:64055:117:Libvirt Qemu,,,:/var/lib/libvirt:/bin/false

3) Without existing user (e.g., new install) _but_ with uid taken

# apt-get purge --yes libvirt{0,-bin}

# id libvirt-qemu
id: ?libvirt-qemu?: no such user

# getent passwd 64055
uidtaken:x:64055:1001::/home/uidtaken:

# apt-get install --yes --no-install-recommends
libvirt{0,-bin}=1.3.1-1ubuntu10.7

User uid is set to the next available uid:

# id libvirt-qemu
uid=110(libvirt-qemu) gid=117(kvm) groups=117(kvm)

# getent passwd 64055
uidtaken:x:64055:1001::/home/uidtaken:

--- Comment From mauri...@br.ibm.com 2017-01-20 08:49 EDT---
BTW,
*again*, sorry for all the noise/attachments from the bug mirroring.
This problem has already been passed along to its development team.
I have no idea why this happens.

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

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

Title:
  UbuntuKVM: migration using NFS mount fails #190

Status in libvirt:
  Fix Released
Status in base-passwd package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in base-passwd source package in Xenial:
  Won't Fix
Status in libvirt source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * Users performing live migration of guests with image files
     shared over NFS between the source and target host systems
     may experience I/O errors in the guests if user id of the
     libvirt-qemu user differs between the host systems, due to
     permission errors when accessing the image files.

   * The 16.04 LTS is an important stream for KVM (at least on
     Power), and guest live migration over NFS is an important
     feature on it.

   * The proposed fix (a minimal backport from what is applied
     on Zesty/Debian, so to be very conservative for the LTS)
     simply tries to use the reserved uid for the libvirt-qemu
     user on new installations (when the user is created) if
     the reserved uid is not taken by another user (no failures
     occur if the libvirt-qemu user already exists or the uid
     is taken.)

  [Test Case]

   * Setup 2x systems with Ubuntu 16.04 LTS as KVM hosts (e.g., micro and tiny)
     (check whether the libvirt-qemu uid differs between them;
  e.g. # id libvirt-qemu )

   * Create a guest in the source KVM host system (e.g, microg5)

   * Live migrate the guest to the destination KVM host system (e.g.,
  tiny)

     root@micro:~# virsh migrate --live --domain microg5 qemu+ssh://tiny/system
   --verbose --undefinesource --persistent --timeout 60
     Migration: [100 %]

   * Check whether the guest is now listed in the destination KVM host
  system:

  root@tiny:~# virsh list --all
  Id Name State

  12 microg5 running

   * Check whether I/O errors are seen in that guest:

  root@microg5:~# dmesg
  ...
  [ 60.818955] blk_update_request: I/O error, dev vdc, sector 96749232
  [ 60.819113] Aborting journal on device vdc2-8.
  [ 60.820121] blk_update_request: I/O error, dev vdc, sector 9084320
  [ 60.820643] EXT4-fs warning (device vdc2): ext4_end_bio:329: I/O error
   -5 writing to inode 393279 (offset 0 size 0 ...

  * Simplified test of the wanted effect:
- install libvirt on a system that didn't have it before and check the  
  id of libvirt-qemu
$ id libvirt-qemu

  [Regression Potential]

   * On installations in which the libvirt-qemu user does not exist
     (e.g., first time installation of libvirt-bin) i

Re: [Touch-packages] [Bug 1643708] Re: Add SPNEGO special case for NTLMSSP+MechListMIC

2017-01-20 Thread Sam Hartman

> "Robie" == Robie Basak <1643...@bugs.launchpad.net> writes:

Robie> @Bruce Thank you for detailing your testing. In your test
Robie> suite, do you cover any interoperability with SPNEGO but
Robie> not-Windows, whether in integration or code path coverage?
Robie> That's the use case I'm concerned about - that someone will
Robie> come along and tell us that we regressed SPNEGO against
Robie> WebSphere or something because we focused on just testing
Robie> Windows.

Hi.
As I understand it, this is a backport of an upstream change.
It's always possible there is an interop regression.
In this instance though, given where the patch comes from originally,
and that it's been in upstream releases for a while, I think you're
relatively safe.
SPNEGO interop is really hard to test though; it's not something that
you can get good coverage for without a specific interoperability lab
and careful test plans.

I don't know if upstream has done that for this patch, although I do
have high confidence that people do interop tests against the upstream
version.

So, while I think your concern is reasonable, I'd urge you to consider
that you're setting a really high bar here for backporting a patch that
an interoperability-conscious upstream has vetted.
Yes, the MIT folks have messed up interop (just as everyone else), but
they are fairly careful and conservative.

If you do want to do interop testing, the interesting cases to cover
are:

* Initiator prefers Kerberos; other side does not support it

* Acceptor prefers Kerberos, initiator does not support it

* Initiator prefers NTLM and some non-Kerberos third mechanism

* Acceptor prefers NTLM, doesn't have Kerberos, but does have some third
  mechanism

I think setting all that up is a good week's worth of work with someone
who really knows what they are doing.

--Sam

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

Title:
  Add SPNEGO special case for NTLMSSP+MechListMIC

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Trusty:
  Fix Committed
Status in krb5 source package in Xenial:
  Fix Committed
Status in krb5 source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer
  needs to implement specifically for the NTLMSSP mechanism.  This is
  required for compatibility with Windows services.

  Upstream commit:
  https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9b7

  We've run into this issue with Linux to Windows negotiation with
  encrypted http using GSSAPI.

  [Test Case]

  create a file with some credentials:

  $ echo F23:guest:guest > ~/ntlmcreds.txt
  $ export NTLM_USER_FILE=~/ntlmcreds.txt
  $ python
  import gssapi

  spnego = gssapi.raw.oids.OID.from_int_seq('1.3.6.1.5.5.2')
  c = gssapi.creds.Credentials(mechs=[spnego], usage='initiate')
  tname = gssapi.raw.names.import_name("F23/server", 
name_type=gssapi.raw.types.NameType.hostbased_service)
  ac = gssapi.creds.Credentials(mechs=[spnego], usage='accept')

  seci = gssapi.SecurityContext(creds=c, name=tname, mech=spnego, 
usage='initiate')
  seca = gssapi.SecurityContext(creds=ac, usage='accept')
  it = seci.step(token=None)
  ot = seca.step(token=it)
  it = seci.step(token=ot)
  ot = seca.step(token=it)
  it = seci.step(token=ot)

  e = seci.wrap("Secrets", True)
  o = seca.unwrap(e.message)

  o.message
  'Secrets'

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

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

[Touch-packages] [Bug 1646457] Re: No feedback when changing Launcher's icon size

2017-01-20 Thread Michał Sawicz

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

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

Title:
  No feedback when changing Launcher's icon size

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

Bug description:
  bq M10 FHD rc-proposed r243

  Steps to reproduce:
  0. Make sure 'Desktop mode' is switched off
  1. Go to System Setting > Launcher
  2. Move the slider to change 'Icon size'

  Expected result:
  The launcher is revealed so I can see what changes I'm making with the slider

  What happens instead:
  If I move the slider to the left: nothing happens.
  If I move the slider to the right: the launcher 'jumps' a bit like it was 
trying to show up but never really shows up.

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

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

[Touch-packages] [Bug 1657385] Re: libxcomposite-dev is not Multi-Arch compatible

This bug was fixed in the package libxcomposite - 1:0.4.4-2

---
libxcomposite (1:0.4.4-2) unstable; urgency=low

  [ Julien Cristau ]
  * Mark libxcomposite-dev as Multi-Arch: same (closes: #689082).  Hopefully
the docbook-generated manpage won't be too unpredictable. (LP: #1657385)

 -- Timo Aaltonen   Fri, 20 Jan 2017 07:36:39 +0200

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

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

Title:
  libxcomposite-dev is not Multi-Arch compatible

Status in libxcomposite package in Ubuntu:
  Fix Released

Bug description:
  This is an old bug since 2012, upstream bug report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689082

  Tested on Xenial, when trying to install libxcomposite-dev:i386, the
  64bit version will be removed:

  $ sudo apt-get install libxcomposite-dev:i386
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libxcomposite1:i386
  The following packages will be REMOVED:
libxcomposite-dev
  The following NEW packages will be installed:
libxcomposite-dev:i386 libxcomposite1:i386
  0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
  Need to get 17.5 kB of archives.
  After this operation, 46.1 kB of additional disk space will be used.
  Do you want to continue? [Y/n]

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

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

[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings

2017-01-20 Thread Dan Streetman

Verified with udev 229-4ubuntu16, all /dev/disk/by-id/ NVMe symlinks are
present and correct.

** Tags removed: verification-needed

** Tags added: verification-done

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

Title:
  NVMe symlinks broken by devices with spaces in model or serial strings

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Yakkety:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

  After including the patch from bug 1642903, NVMe devices that include spaces 
in their model or serial strings result in incorrect symlinks, e.g. if the 
model string is "XYZ Corp NVMe drive" then instead of creating:
  /dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
  it creates:
  /dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
  /dev/Corp -> nvme0n1
  /dev/NVMe -> nvme0n1
  /dev/drive_SERIAL -> nvme0n1

  This is because of the way udev handles the SYMLINK value strings; by
  default, it does not do any whitespace replacement.  To enable
  whitespace replacement of a symlink value, the rule must also include
  OPTIONS+="string_escape=replace".  This is done for 'md' and 'dm'
  devices in their rules.  However, there are no rules that actually
  want to specify multiple symlinks, and defaulting to not replacing
  whitespace makes no sense; instead, the default should be to replace
  all whitespace in each symlink value, unless the rule explicitly
  specifies OPTIONS+="string_escape=none".

  [Test Case]

  This assumes using udev with the patch from bug 1642903.

  Without this patch, when using a NVMe drive that contains spaces in
  its model and/or serial strings, check the /dev/disk/by-id/ directory.
  It should contain a partially-correct symlink to the NVMe drive, with
  the name up to the first space.  All following space-separated parts
  of the mode/serial string should have symlinks in the /dev/ directory.
  This is the incorrect behavior.

  With this patch, check the /dev/disk/by-id/ directory.  It should
  contain a fully-correct symlink to the NVMe drive, and no part of the
  drive's model/serial number string should be a link in the /dev
  directory.

  An example of the correct/incorrect naming is in the Impact section.

  There should be no other changes to any of the symlinks under /dev
  before and after this patch.  Typical locations for symlinks are
  /dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
  /dev/disk/by-label/

  [Regression Potential]

  Errors in udev rules can lead to an unbootable or otherwise completely
  broken system if they unintentionally break or clobber existing
  /dev/disks/ symlinks.

  [Other Info]

  This is also tracked with upstream systemd (udev) bug 4833:
  https://github.com/systemd/systemd/issues/4833

  Also note, this can be worked around in individual rules ONLY (i.e.
  not fixed for all rules) by appending OPTIONS+="string_escape=replace"
  to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:

  KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
  ENV{ID_SERIAL_SHORT}=="?*",
  ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
  /by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"

  Related bugs:
   * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives
   * bug 1651602: NVMe driver regression for non-smp/1-cpu systems
   * bug 1649635: export nvme drive model/serial strings via sysfs (trusty)

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

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

[Touch-packages] [Bug 1657845] Re: Unity8 snap can't load the testability libraries

2017-01-20 Thread Michał Sawicz

** Also affects: unity8-session-snap
   Importance: Undecided
   Status: New

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

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

Title:
  Unity8 snap can't load the testability libraries

Status in Unity8 Session Snap:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  In order to introspect unity8, the testability libraries should be
  available. Such libraries are provided by autopilot-qt snap through a
  content interface called testability

  unity8 snap should add a plug to such interface so that testability
  libraries get loaded

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

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

[Touch-packages] [Bug 1521403] Re: Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

2017-01-20 Thread Gerry Boland

Ok, rather marginal use-cases then :)

At least Mir allows this kind of request can be filtered by Unity8 in
future, to prevent this kind of thing being abused. Perhaps need a
system so that privileged clients can do this if they need.

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

Title:
  Unity8 crashes on suspend/standby with SIGSEGV in Screen::makeCurrent
  (./src/platforms/mirserver/screen.cpp:406)

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

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

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

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

[Touch-packages] [Bug 1657082] Re: Menu items don't close when pressing them

2017-01-20 Thread Albert Astals Cid

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Albert Astals Cid (aacid)

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

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

Title:
  Menu items don't close when pressing them

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Clicking on a menu popup item (e.g. "Edit" -> "Search" in dolphin)
  doesn't hide the menu while it does in unity7.

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

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

[Touch-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time

2017-01-20 Thread Sebastien Bacher

The call was added by Mathieu in bin/oem-config-firstboot when he added
systemd support, subscribing him to the bug

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

Title:
  Wifi "device not ready" after booting into OS for the 1st time

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  * Steps to reproduce:
  1. Install image
  2. Boot into OS
  3. Check the wifi status in network-manager applet

  * Expected result:
  Available APs listed in network-manager applet, wifi connection can be 
established

  * Actual result:
  AP list replaced by a greyed-out "device not ready" wording
  Reboot system or do "$ sudo service network-manager restart" and wifi will 
then start working correctly.

  * OS: Xenial
  * Network-manager: 1.1.93-0ubuntu4
  * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac 
Wireless [11ab:2b38]

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

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

[Touch-packages] [Bug 1510968] Re: external monitor grid units are not set correctly

2017-01-20 Thread Christian Dywan

On the UI Toolkit side, the introduction of MainWindow (bug 587431)
makes units window-specific - so long as Unity (or QtUbuntu, more
specifically) provides the right value, the resolution will be correct.

** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-toolkit/outTheWindow

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

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Christian Dywan (kalikiana)

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

Title:
  external monitor grid units are not set correctly

Status in Canonical System Image:
  In Progress
Status in Canonical Pocket Desktop:
  In Progress
Status in qtmir package in Ubuntu:
  In Progress
Status in qtubuntu package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  external monitor grid units are not set correctly so the desktop is
  incorectly scaled.

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

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

[Touch-packages] [Bug 1657473] Re: date format incorrect for a number of Timezones

2017-01-20 Thread Paul White

** Package changed: ubuntu => tzdata (Ubuntu)

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

Title:
  date format incorrect for a number of Timezones

Status in tzdata package in Ubuntu:
  New

Bug description:
  Body:

  For a number of locales, for example, TZ=Europe/London, the default
  format of the date command is wrong. At least one other timezone is
  affected: TZ=Africa/Johannesburg has the same bug.

  
   $(TZ=Europe/London;date)
   Wed Jan 18 13:59:33 GMT 2017

  This format is wrong. It should be:

   $(TZ=Europe/London;date)
   Wed 18 Jan 13:59:33 GMT 2017

  In other words, the date format should be:

   date +%a\ %d\ %b\ %H:%M:%S\ %Z\ %Y

  Not, as it currently is:

  date +%a\ %b\ %d\ %H:%M:%S\ %Z\ %Y

affects ubuntu
status new

  -- 
  Peter Brooks

  
  Mobile: +27 82 717 6404
  Direct:  +27 21 447 9752
  Skype:  Fustbariclation
  Twitter: Fustbariclation
  Google+: Fustbariclation
  Author Page: amazon.com/author/peter_brooks

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

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

[Touch-packages] [Bug 1657473] [NEW] date format incorrect for a number of Timezones

You have been subscribed to a public bug:

Body:

For a number of locales, for example, TZ=Europe/London, the default
format of the date command is wrong. At least one other timezone is
affected: TZ=Africa/Johannesburg has the same bug.


 $(TZ=Europe/London;date)
 Wed Jan 18 13:59:33 GMT 2017

This format is wrong. It should be:

 $(TZ=Europe/London;date)
 Wed 18 Jan 13:59:33 GMT 2017

In other words, the date format should be:

 date +%a\ %d\ %b\ %H:%M:%S\ %Z\ %Y

Not, as it currently is:

date +%a\ %b\ %d\ %H:%M:%S\ %Z\ %Y

  affects ubuntu
  status new

-- 
Peter Brooks


Mobile: +27 82 717 6404
Direct:  +27 21 447 9752
Skype:  Fustbariclation
Twitter: Fustbariclation
Google+: Fustbariclation
Author Page: amazon.com/author/peter_brooks

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


** Tags: bot-comment
-- 
date format incorrect for a number of Timezones
https://bugs.launchpad.net/bugs/1657473
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to tzdata in Ubuntu.

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

[Touch-packages] [Bug 1643708] Re: Add SPNEGO special case for NTLMSSP+MechListMIC

@Bruce

Thank you for detailing your testing. In your test suite, do you cover
any interoperability with SPNEGO but not-Windows, whether in integration
or code path coverage? That's the use case I'm concerned about - that
someone will come along and tell us that we regressed SPNEGO against
WebSphere or something because we focused on just testing Windows.

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

Title:
  Add SPNEGO special case for NTLMSSP+MechListMIC

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Trusty:
  Fix Committed
Status in krb5 source package in Xenial:
  Fix Committed
Status in krb5 source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer
  needs to implement specifically for the NTLMSSP mechanism.  This is
  required for compatibility with Windows services.

  Upstream commit:
  https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9b7

  We've run into this issue with Linux to Windows negotiation with
  encrypted http using GSSAPI.

  [Test Case]

  create a file with some credentials:

  $ echo F23:guest:guest > ~/ntlmcreds.txt
  $ export NTLM_USER_FILE=~/ntlmcreds.txt
  $ python
  import gssapi

  spnego = gssapi.raw.oids.OID.from_int_seq('1.3.6.1.5.5.2')
  c = gssapi.creds.Credentials(mechs=[spnego], usage='initiate')
  tname = gssapi.raw.names.import_name("F23/server", 
name_type=gssapi.raw.types.NameType.hostbased_service)
  ac = gssapi.creds.Credentials(mechs=[spnego], usage='accept')

  seci = gssapi.SecurityContext(creds=c, name=tname, mech=spnego, 
usage='initiate')
  seca = gssapi.SecurityContext(creds=ac, usage='accept')
  it = seci.step(token=None)
  ot = seca.step(token=it)
  it = seci.step(token=ot)
  ot = seca.step(token=it)
  it = seci.step(token=ot)

  e = seci.wrap("Secrets", True)
  o = seca.unwrap(e.message)

  o.message
  'Secrets'

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

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

[Touch-packages] [Bug 1657082] Re: Menu items don't close when pressing them

2017-01-20 Thread Albert Astals Cid

** Summary changed:

- Toggable menu items don't close when pressing them
+ Menu items don't close when pressing them

** Description changed:

- Clicking on a toggable menu bar item (e.g. "Show Toolbar" in dolphin)
+ Clicking on a menu popup item (e.g. "Edit" -> "Search" in dolphin)
  doesn't hide the menu while it does in unity7.

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

Title:
  Menu items don't close when pressing them

Status in unity8 package in Ubuntu:
  New

Bug description:
  Clicking on a menu popup item (e.g. "Edit" -> "Search" in dolphin)
  doesn't hide the menu while it does in unity7.

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

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

[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites

2017-01-20 Thread Olivier Tilloy

@bluexxx: the google+ error is a different bug:
https://launchpad.net/bugs/1656310.

The message on the ML might have been misleading: we are working on an
OTA-15, but it won’t contain new features, only a very limited number of
critical bug fixes.

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

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

Title:
  webbrowser only partially loads some https sites

Status in Canonical System Image:
  In Progress
Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 14) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

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

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

[Touch-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time