from:"Barry Warsaw"

[Touch-packages] [Bug 1704805] [NEW] All titlebars are corrupt

2017-07-17 Thread Barry Warsaw

Public bug reported:

After today's artful dist-ugprade, all titlebars are corrupted.  The
fonts show only squares.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon Jul 17 10:49:00 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2016-11-07 (251 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161107)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic 
root=UUID=ec4bce78-74fa-43dc-af9e-b26a9a2d562a ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz 1:0.9.13.1+17.10.20170704-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.81-2
version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Dec 13 11:21:08 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVMware VMware Virtual USB Mouse MOUSE, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputVirtualPS/2 VMware VMMouse MOUSE, id 9
 inputVirtualPS/2 VMware VMMouse MOUSE, id 10
xserver.errors: No surface to present from.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: OutputVirtual2 
   Virtual3Virtual4Virtual5Virtual6Virtual7 
   Virtual8
xserver.version: 2:1.18.4-1ubuntu7
xserver.video_driver: vmware

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


** Tags: amd64 apport-bug artful corruption regression single-occurrence 
third-party-packages ubuntu

** Attachment added: "titlebars.png"
   
https://bugs.launchpad.net/bugs/1704805/+attachment/4916193/+files/titlebars.png

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

Title:
  All titlebars are corrupt

Status in xorg package in Ubuntu:
  New

Bug description:
  After today's artful dist-ugprade, all titlebars are corrupted.  The
  fonts show only squares.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Jul 17 10:49:00 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2016-11-07 (251 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161107)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003

[Touch-packages] [Bug 1695141] Re: Recent update broke multiheaded sleep

2017-06-01 Thread Barry Warsaw

% uname -a
Linux subdivisions 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux


FWIW, booting 4.10.0-20 hangs on boot so that's not a viable option.

Also, setting Brightness>Turn screen off when inactive for: Never
does not prevent Ubuntu from sleeping the displays (after progressive dimming) 
and thus causing the problem.

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

Title:
  Recent update broke multiheaded sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  I just dist-upgraded my Zesty machine and two things broke related to
  sleeping the displays.  I have a 34" wide panel on the left and a 20"
  high resolution Dell on the right.

  Everything works fine until the displays sleep, say after a lockscreen
  has started.  First, the right screen never wakes from sleep; even
  though the lights on the front are green (indicating an active
  display), once the right display has slept, it never wakes back up
  even after a login.

  Second, and probably related: all the windows that were on the right
  display are now shifted over to the left and full-screened.

  This has all worked for a long time, but something in the recent
  stable updates has broken this, so it's a pretty serious regression.
  Nothing short of a reboot returns the dual screens to full
  functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  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:Unity7
  Date: Fri Jun  2 00:17:33 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-20-generic, x86_64: installed
   bbswitch, 0.8, 4.10.0-21-generic, x86_64: installed
   nvidia-375, 375.66, 4.10.0-21-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GK104 [GeForce GTX 760] [1458:360b]
  InstallationDate: Installed on 2016-01-22 (497 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Thu Jun  1 23:54:29

[Touch-packages] [Bug 1695141] [NEW] Recent update broke multiheaded sleep

2017-06-01 Thread Barry Warsaw

Public bug reported:

I just dist-upgraded my Zesty machine and two things broke related to
sleeping the displays.  I have a 34" wide panel on the left and a 20"
high resolution Dell on the right.

Everything works fine until the displays sleep, say after a lockscreen
has started.  First, the right screen never wakes from sleep; even
though the lights on the front are green (indicating an active display),
once the right display has slept, it never wakes back up even after a
login.

Second, and probably related: all the windows that were on the right
display are now shifted over to the left and full-screened.

This has all worked for a long time, but something in the recent stable
updates has broken this, so it's a pretty serious regression.  Nothing
short of a reboot returns the dual screens to full functionality.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
 GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.1
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:Unity7
Date: Fri Jun  2 00:17:33 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.10.0-20-generic, x86_64: installed
 bbswitch, 0.8, 4.10.0-21-generic, x86_64: installed
 nvidia-375, 375.66, 4.10.0-21-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GK104 [GeForce GTX 760] [1458:360b]
InstallationDate: Installed on 2016-01-22 (497 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170X-UD5-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z170X-UD5
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Thu Jun  1 23:54:29 2017
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu1

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu uec-images 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/1695141

Title:
  Recent update broke multiheaded sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  I just dist-upgraded my Zesty machine and two things broke related to
  sleeping the displays.  I have a 34" wide panel on the left and a 20"
  high resolution Dell on the right.

  Everything

[Touch-packages] [Bug 1473178] Re: package python-pkg-resources 3.3-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-04-10 Thread Barry Warsaw

** Changed in: python-setuptools (Ubuntu)
 Assignee: (unassigned) => Barry Warsaw (barry)

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

Title:
  package python-pkg-resources 3.3-1ubuntu1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in python-setuptools package in Ubuntu:
  Confirmed

Bug description:
  crash on login

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-pkg-resources 3.3-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-43.58~14.04.1-generic 3.16.7-ckt13
  Uname: Linux 3.16.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Wed Jul  8 23:04:00 2015
  Dependencies:
   
  DuplicateSignature: package:python-pkg-resources:3.3-1ubuntu1:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-06-06 (32 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: python-setuptools
  Title: package python-pkg-resources 3.3-1ubuntu1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1473178/+subscriptions

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

[Touch-packages] [Bug 1473178] Re: package python-pkg-resources 3.3-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-04-10 Thread Barry Warsaw

This looks like another case where pyclean (not py3clean) might be
getting called by Python 3, which clearly won't work.  Investigating.

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

Title:
  package python-pkg-resources 3.3-1ubuntu1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 1

Status in python-setuptools package in Ubuntu:
  Confirmed

Bug description:
  crash on login

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python-pkg-resources 3.3-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-43.58~14.04.1-generic 3.16.7-ckt13
  Uname: Linux 3.16.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Wed Jul  8 23:04:00 2015
  Dependencies:
   
  DuplicateSignature: package:python-pkg-resources:3.3-1ubuntu1:subprocess new 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-06-06 (32 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: python-setuptools
  Title: package python-pkg-resources 3.3-1ubuntu1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1473178/+subscriptions

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

[Touch-packages] [Bug 1679849] Re: vim FTBFS during a rebuild test for zesty

2017-04-07 Thread Barry Warsaw

This builds for me locally, so I think this may have fixed itself.

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

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

Title:
  vim FTBFS during a rebuild test for zesty

Status in vim package in Ubuntu:
  Invalid

Bug description:
  vim version 2:8.0.0095-1ubuntu3 failed to build from source on amd64
  during an archive rebuild test for zesty.  The build log can be found
  here:

  https://launchpadlibrarian.net/312225140/buildlog_ubuntu-zesty-
  amd64.vim_2%3A8.0.0095-1ubuntu3_BUILDING.txt.gz

  The failure seems to be:

  rm -rf *.out *.failed *.res *.rej *.orig test.log messages test.out X* 
viminfo tiny.vim small.vim mbyte.vim mzscheme.vim lua.vim test.ok benchmark.out 
valgrind.*
  make[3]: Leaving directory '/<>/src/testdir'
  if test -d po; then \
cd po; /usr/bin/make checkclean; \
  fi
  make[3]: Entering directory '/<>/src/po'
  Makefile:4: ../auto/config.mk: No such file or directory
  make[3]: *** No rule to make target '../auto/config.mk'.  Stop.
  make[3]: Leaving directory '/<>/src/po'
  Makefile:2181: recipe for target 'testclean' failed
  make[2]: *** [testclean] Error 2
  make[2]: *** Waiting for unfinished jobs
  cp config.mk.dist auto/config.mk
  make[2]: Leaving directory '/<>/src'
  Makefile:36: recipe for target 'distclean' failed
  make[1]: *** [distclean] Error 2
  make[1]: Leaving directory '/<>'
  debian/rules:251: recipe for target 'autoconf-stamp' failed
  make: *** [autoconf-stamp] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

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

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

[Touch-packages] [Bug 1569719] Re: package python3 3.5.1-3 failed to install/upgrade: pre-dependency problem - not installing python3

2017-04-06 Thread Barry Warsaw

Setting up python3.5-minimal (3.5.1-10) ...
Traceback (most recent call last):
  File "/usr/lib/python3.5/py_compile.py", line 6, in 
import importlib._bootstrap_external
  File "/usr/lib/python3.5/importlib/__init__.py", line 93
raise ValueError('{}.__loader__ is not set'.format(name)) from None
 ^
SyntaxError: invalid syntax

That's super weird.  raise-from (i.e. PEP 3134 chained exceptions) go
waay back in Python 3.

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

Title:
  package python3 3.5.1-3 failed to install/upgrade: pre-dependency
  problem - not installing python3

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Upgraded to Ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3 3.5.1-3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Tue Apr 12 12:33:05 2016
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-01-16 (453 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-3 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to xenial on 2016-04-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1569719/+subscriptions

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

[Touch-packages] [Bug 1679835] Re: pygobject-2 FTBFS on most arches during zesty test rebuild

2017-04-06 Thread Barry Warsaw

% reverse-depends src:pygobject-2
Reverse-Recommends
==
* python-gtk2-doc   (for python-gobject-2)
* winswitch (for python-gobject-2)

Reverse-Depends
===
* coccinelle(for python-gobject-2)
* comitup   (for python-gobject-2)
* hamster-applet(for python-gobject-2)
* mate-tweak(for python-gobject-2)
* python-gconf  (for python-gobject-2)
* python-gnome2 (for python-gobject-2)
* python-gnome2-dev (for python-gobject-2-dev)
* python-gobject(for python-gobject-2)
* python-gobject-dbg(for python-gobject-2-dbg)
* python-gobject-dev(for python-gobject-2-dev)
* python-gtk2   (for python-gobject-2)
* python-gtk2-dbg   (for python-gobject-2-dbg)
* python-gtk2-dev   (for python-gobject-2-dev)
* python-gtksourceview2 (for python-gobject-2)
* python-indicate   (for python-gobject-2)
* python-liblarch   (for python-gobject-2)
* python-zeitgeist  (for python-gobject-2)
* sat-xmpp-core (for python-gobject-2)
* zenmap(for python-gobject-2)


% reverse-depends -b src:pygobject-2
Reverse-Build-Depends
=
* gnome-python  (for python-gobject-2-dev)
* pygtk (for python-gobject-2-dbg)
* pygtk (for python-gobject-2-dev)
* pygtksourceview   (for python-gobject-2-dev)
* winswitch (for python-gobject-2)

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

Title:
  pygobject-2 FTBFS on most arches during zesty test rebuild

Status in pygobject-2 package in Ubuntu:
  New

Bug description:
   pygobject-2 version 2.28.6-12ubuntu1 failed to build from source on
  most (not amd64) arches during a test rebuild of zesty. The build log
  can be found here:

  https://launchpadlibrarian.net/312383008/buildlog_ubuntu-zesty-i386
  .pygobject-2_2.28.6-12ubuntu1_BUILDING.txt.gz

  The failure seems to be due to the following:

   debian/rules build-arch
  make: *** No rule to make target 'build-arch'.  Stop.
  dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject-2/+bug/1679835/+subscriptions

-- 
Mailing list: https://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 1678604] [NEW] package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127

2017-04-02 Thread Barry Warsaw

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

On Apr 02, 2017, at 12:25 PM, virendra singh wrote:

>afer removing python2.7 and installing python3 and making
>/usr/bin/python soft link from /usr/bin/python3 i am receiving this
>error. Please suggest

Changing /usr/bin/python to point to /usr/bin/python3 is not supported,
therefore we do not recommend it and cannot guarantee things will work
properly if you do this.

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

Title:
  package python3 3.5.1-3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 127

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  afer removing python2.7 and installing python3 and making
  /usr/bin/python soft link from /usr/bin/python3 i am receiving this
  error. Please suggest

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3 3.5.1-3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Sun Apr  2 17:25:22 2017
  DuplicateSignature:
   package:python3:3.5.1-3
   Removing python3 (3.5.1-3) ...
   /var/lib/dpkg/info/python3.prerm: 5: /var/lib/dpkg/info/python3.prerm: 
py3clean: not found
   dpkg: error processing package python3 (--remove):
subprocess installed pre-removal script returned error exit status 127
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 127
  InstallationDate: Installed on 2016-06-23 (282 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.20
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-3 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1678604/+subscriptions

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

[Touch-packages] [Bug 1633331] Re: /usr/bin/pyclean fails with python3

2017-03-29 Thread Barry Warsaw

*doesn't really make sense to be running

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

Title:
  /usr/bin/pyclean fails with python3

Status in python-defaults package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Triaged

Bug description:
  samba

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-samba 2:4.3.9+dfsg-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Fri Oct 14 08:31:48 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-08-05 (69 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  NmbdLog:
   
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SambaServerRegression: Yes
  SmbConfIncluded: Yes
  SmbLog:
   
  SourcePackage: samba
  Title: package python-samba 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-06 (68 days ago)
  WindowsFailedConnect: Yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/161/+subscriptions

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

[Touch-packages] [Bug 1633331] Re: /usr/bin/pyclean fails with python3

2017-03-29 Thread Barry Warsaw

Oh I missed this bit:

"I'd assume this only triggers when the system is tweaked to run 
/usr/bin/python as python3?
Does that match your case?"

Yeah, don't do that! :)

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

Title:
  /usr/bin/pyclean fails with python3

Status in python-defaults package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Triaged

Bug description:
  samba

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-samba 2:4.3.9+dfsg-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Fri Oct 14 08:31:48 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-08-05 (69 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  NmbdLog:
   
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SambaServerRegression: Yes
  SmbConfIncluded: Yes
  SmbLog:
   
  SourcePackage: samba
  Title: package python-samba 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-06 (68 days ago)
  WindowsFailedConnect: Yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/161/+subscriptions

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

[Touch-packages] [Bug 1633331] Re: /usr/bin/pyclean fails with python3

2017-03-29 Thread Barry Warsaw

It doesn't really make to be running /usr/bin/pyclean with Python 3.
That's why we have /usr/bin/py3clean which is part of python3-minimal.
samba isn't even ported to Python 3, so why is it trying to run pyclean
as Python 3?

(samba is really the last thing keeping Python 2 on desktop, and it's
not just us that's blocked on that.)

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

Title:
  /usr/bin/pyclean fails with python3

Status in python-defaults package in Ubuntu:
  New
Status in samba package in Ubuntu:
  Triaged

Bug description:
  samba

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-samba 2:4.3.9+dfsg-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Fri Oct 14 08:31:48 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-08-05 (69 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  NmbdLog:
   
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SambaServerRegression: Yes
  SmbConfIncluded: Yes
  SmbLog:
   
  SourcePackage: samba
  Title: package python-samba 2:4.3.9+dfsg-0ubuntu0.16.04.2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-06 (68 days ago)
  WindowsFailedConnect: Yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/161/+subscriptions

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

[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2017-03-15 Thread Barry Warsaw

Here are a few more relevant comments from IRC and email:

 barry: software-properties was already ported from aptdaemon to pk in
 Debian, we didn't push it into zesty since I don't think anyone
 checked if the driver code worked  [16:51]

 
https://anonscm.debian.org/git/collab-maint/software-properties.git/tree/debian/patches/0004-Implement-PackageKit-support.patch

"sessioninstaller is essentially obsolete when you have gnome-software
w/ the PackageKit backend.  session-installer itself appears to be
broken in general."

"So, sessioninstaller is an aptdaemon based implementation of the
PackageKit session interface. The two can be dropped together, since
they are both unmaintained and not needed. PackageKit provides
everything needed as a replacement.

The dependency by gnome-software is illusory, as it depends on
PackageKit D-Bus interfaces (provided by PackageKit). The dependency
wasn't even present in xenial, as far as I recall...

oem-config-gtk is a single script[1] with only a few lines of code
actually using aptdaemon, and that can be ported to use PackageKit
instead.

language-selector-gnome is similar[2], and should be easy to port out
to PackageKit, assuming this is even needed anymore. It doesn't look
like it's maintained either...

[1]: http://bazaar.launchpad.net/~ubuntu-
installer/ubiquity/trunk/view/head:/bin/oem-config-remove-gtk

[2]: 
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/language-selector/vivid/view/head:/LanguageSelector/gtk/GtkLanguageSelector.py
"


% reverse-depends src:aptdaemon
Reverse-Recommends
==
* 0install-core (for python3-aptdaemon.pkcompat)
* dell-recovery (for python-aptdaemon.gtk3widgets)
* update-notifier   (for python3-aptdaemon)
* update-notifier   (for python3-aptdaemon.gtk3widgets)

Reverse-Depends
===
* apturl(for python3-aptdaemon.gtk3widgets)
* apturl(for python3-aptdaemon)
* gnome-software(for aptdaemon)
* language-selector-gnome   (for python3-aptdaemon.gtk3widgets)
* language-selector-gnome   (for aptdaemon)
* lubuntu-software-center   (for python-aptdaemon)
* lubuntu-software-center   (for python-aptdaemon.gtk3widgets)
* mythbuntu-control-centre  (for python-aptdaemon.gtk3widgets)
* oem-config-gtk(for python3-aptdaemon.gtk3widgets)
* oem-config-gtk(for aptdaemon)
* sessioninstaller  (for python3-aptdaemon.gtk3widgets)
* sessioninstaller  (for aptdaemon)
* software-properties-gtk   (for python3-aptdaemon.gtk3widgets)
* ubuntu-mate-core  (for python3-aptdaemon.gtk3widgets)
* ubuntu-mate-desktop   (for python3-aptdaemon.gtk3widgets)
* ubuntu-mate-welcome   (for python3-aptdaemon.gtk3widgets)
* ubuntu-mate-welcome   (for python3-aptdaemon)
* update-manager(for python3-aptdaemon.gtk3widgets)


** Also affects: zeroinstall-injector (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: dell-recovery (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: update-notifier (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: gnome-software (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: language-selector (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: lubuntu-software-center (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mythbuntu-control-centre (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Also affects: software-properties (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-mate-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-mate-welcome (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: update-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  New
Status in mythbuntu-control-centre package in Ubuntu:
  New
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in

[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2017-03-15 Thread Barry Warsaw

Bugtasks added for revdep source packages.  Hopefully I got them all.

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  New
Status in mythbuntu-control-centre package in Ubuntu:
  New
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in aptdaemon source package in aa-series:
  New
Status in apturl source package in aa-series:
  New
Status in dell-recovery source package in aa-series:
  New
Status in gnome-software source package in aa-series:
  New
Status in language-selector source package in aa-series:
  New
Status in lubuntu-software-center source package in aa-series:
  New
Status in mythbuntu-control-centre source package in aa-series:
  New
Status in sessioninstaller source package in aa-series:
  New
Status in software-properties source package in aa-series:
  New
Status in ubiquity source package in aa-series:
  New
Status in ubuntu-mate-meta source package in aa-series:
  New
Status in ubuntu-mate-welcome source package in aa-series:
  New
Status in update-manager source package in aa-series:
  New
Status in update-notifier source package in aa-series:
  New
Status in zeroinstall-injector source package in aa-series:
  New

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

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

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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-02-21 Thread Barry Warsaw

Uploaded.  Now we just have to get the archive admins to let it pass now
that we've entered feature freeze, if that's even a good idea.

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1666021] Re: zesty systemd-resolve timeout

2017-02-21 Thread Barry Warsaw

I wonder if this is related to something I've seen since before the
recent nm and systemd uploads.  I have Chromium, Emacs, and Claws-Mail
set up as startup apps.  After a reboot, as soon as I login, these apps
come up, but most of the tabs in Chromium cannot load.  After some short
amount of time, hitting reload (or visiting the tabs for auto-reload)
start working again.

I know for sure this was happening before the systemd 232-18ubuntu1 and
n-m 1.4.4-1ubuntu2 uploads, so I doubt it's related to the CNAME change.

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

Title:
  zesty systemd-resolve timeout

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I rebooted my zesty install today so it has network-manager
  1.4.4-1ubuntu2 (re-enabled resolved by default for DNS) and systemd
  232-17ubuntu1 (which is supposed to fix the CNAME problems that got
  resolved by default reverted earlier in zesty).

  I had various DNS issues so I rebooted.

  When I rebooted, I opened up Firefox and browsed several sites.
  I opened a terminal and ran sudo apt update. I disabled a PPA and enabled a 
different PPA and ran sudo apt update then sudo apt dist-upgrade (there were 3 
updates).

  When apt was downloading one of those new packages, it paused mid-
  download. I was unable to browse sites in Firefox. I ran this command
  in a different terminal:

  $ systemd-resolve --status
  Failed to get global data: Connection timed out

  I checked journalctl and there was a very large number of these entries:
  systemd-resolved[3260]: Processing query...

  Finally followed by this repeated 3 times:
  dnsmasq[3563]: Maximum number of concurrent DNS queries reached (max: 150)

  Eventually, after I guess a couple minutes, things returned to normal.
  The apt upgrade completed. systemd-resolve --status looked better and
  I'm able to use Firefox again (to report this bug).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-17ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Feb 19 09:54:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (191 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b57e Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80SA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed 
root=UUID=352e459f-ebca-4dc8-86e3-b078a000910b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2016-12-20 (60 days ago)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0VCN22WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad F
  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 ideapad FLEX 4-1470
  dmi.modalias: 
dmi:bvnLENOVO:bvr0VCN22WW(V1.06):bd09/26/2016:svnLENOVO:pn80SA:pvrLenovoideapadFLEX4-1470:rvnLENOVO:rnLenovoideapadF:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1470:
  dmi.product.name: 80SA
  dmi.product.version: Lenovo ideapad FLEX 4-1470
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1666021] Re: zesty systemd-resolve timeout

2017-02-21 Thread Barry Warsaw

I haven't seen this problem, but I don't suspend.

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

Title:
  zesty systemd-resolve timeout

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I rebooted my zesty install today so it has network-manager
  1.4.4-1ubuntu2 (re-enabled resolved by default for DNS) and systemd
  232-17ubuntu1 (which is supposed to fix the CNAME problems that got
  resolved by default reverted earlier in zesty).

  I had various DNS issues so I rebooted.

  When I rebooted, I opened up Firefox and browsed several sites.
  I opened a terminal and ran sudo apt update. I disabled a PPA and enabled a 
different PPA and ran sudo apt update then sudo apt dist-upgrade (there were 3 
updates).

  When apt was downloading one of those new packages, it paused mid-
  download. I was unable to browse sites in Firefox. I ran this command
  in a different terminal:

  $ systemd-resolve --status
  Failed to get global data: Connection timed out

  I checked journalctl and there was a very large number of these entries:
  systemd-resolved[3260]: Processing query...

  Finally followed by this repeated 3 times:
  dnsmasq[3563]: Maximum number of concurrent DNS queries reached (max: 150)

  Eventually, after I guess a couple minutes, things returned to normal.
  The apt upgrade completed. systemd-resolve --status looked better and
  I'm able to use Firefox again (to report this bug).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-17ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Feb 19 09:54:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-11 (191 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 04f2:b57e Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80SA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed 
root=UUID=352e459f-ebca-4dc8-86e3-b078a000910b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2016-12-20 (60 days ago)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0VCN22WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad F
  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 ideapad FLEX 4-1470
  dmi.modalias: 
dmi:bvnLENOVO:bvr0VCN22WW(V1.06):bd09/26/2016:svnLENOVO:pn80SA:pvrLenovoideapadFLEX4-1470:rvnLENOVO:rnLenovoideapadF:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapadFLEX4-1470:
  dmi.product.name: 80SA
  dmi.product.version: Lenovo ideapad FLEX 4-1470
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-02-21 Thread Barry Warsaw

Testing LGTM.  Thanks very much for the patch.  I will sponsor it.

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-02-21 Thread Barry Warsaw

So far so good:
https://launchpad.net/~barry/+archive/ubuntu/experimental/+packages

I'm going to test encryption with claws-mail in a VM.  If that looks
good too, I'll sponsor gpgme1.0 with your patch.

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-02-21 Thread Barry Warsaw

@panfaust: the patch looks pretty reasonable.  I'll give it a try in my
ppa, which builds all arches except powerpc and s390x.

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-02-17 Thread Barry Warsaw

I will say that I've noticed a delay in having the network come up too,
but that predates the new network-manage, and the latest systemd.  It's
been going on for a while now but I haven't managed to report a bug on
it yet.

I have several startup apps configured in my Gnome environment,
including Chromium, Emacs, Claws, and Firefox (yes, two browsers :).
Immediately after a reboot and login, once say Chromium comes up, many
of the pages are reporting errors that they can't get to the domain.
Just visiting the tab is enough to trigger Chromium to do an auto-reload
of the page, and that always works.  Or if I have to manually reload, it
works.  There's just some small bit of time after a reboot+login where
the network is inaccessible.

But I don't think this is at all related to this bug.  I suppose I
should try to figure out which package is at fault and report a bug on
it.

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-02-17 Thread Barry Warsaw

Interesting.  It worked and works for me.  I tested the version in my
PPA, both outside and inside a chroot (it was the inside-chroot that was
previously broken).  I just dist-upgraded my other Zesty machine and
rebooted, and I am having no troubles resolving both IP and domain names
both on my LAN and in the wider internet (www.ubuntu.com,
www.python.org, youtube.com).  The output of `systemd-resolve --status`
LGTM, with my bridge0 link getting the correct DNS server (local to my
LAN) and DNS domain.

chroots also look good (previously they could not get to my apt-cache-ng
proxy on my LAN).

Virtual machines on the same host are also working fine afaict.

Since two of you have reported problems so closely together, there must
be Something Going On, but I cannot reproduce it.

Can you please review your Network Connections from the network manager
settings panel?  Is there anything weird, misconfigured, or unexpected
there?

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-02-16 Thread Barry Warsaw

I'll cherry pick back 98974a88 and 47c16359 now.

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

-- 
Mailing list: https://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 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-30 Thread Barry Warsaw

On Jan 30, 2017, at 04:42 PM, Rik Mills wrote:

>Ummm. If you are Ok with that FTBFS still on arm64 and armhf, then ok.

Dang.  Well, we'll have to deal with that next.

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-30 Thread Barry Warsaw

All looks good, so I'm uploading.  Thanks very much for all the help!

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-30 Thread Barry Warsaw

The PPA build is looking good.  I'll check autopkgtests next and if that
all looks good, I'll sponsor your debdiff.  Thanks!

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

-- 
Mailing list: https://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 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-30 Thread Barry Warsaw

On Jan 30, 2017, at 09:42 AM, Rik Mills wrote:

>** Patch added: "gpgme1.0_1.8.0-3ubuntu1.debdiff"
>   
> https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+attachment/4810708/+files/gpgme1.0_1.8.0-3ubuntu1.debdiff

Thanks for the debdiff.  LGTM; building in my PPA.  If it passes, I'll sponsor
this.  You might consider reporting this bug (and attaching the debdiff) to
Debian since we'll need to resync the package at some point.

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-26 Thread Barry Warsaw

** Patch added: "lp1647204.diff"
   
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+attachment/4809525/+files/lp1647204.diff

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-26 Thread Barry Warsaw

Thanks; I'm testing this in my own PPA now.  If it succeeds, then I'm
happy to upload this to Zesty.  I have my own patch, which I'll attach
here, but I'm also happy to sponsor a fix authored by you if you want to
attach a debdiff to apply to the Zesty package.  Or, if you are an
Ubuntu developer, don't wait for me!

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

2017-01-13 Thread Barry Warsaw

I think we know almost the entire story now.  See LP: #1656391

The one piece still missing is what changed.  Very clearly the armhf
container tests passed for several months, and then stopped working.  My
best guess is that they switched from using privileged containers to
unprivileged containers.  In any event, I'm going to close this bug.
See the above referenced bug for further discussion.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

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

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

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

** Changed in: multipath-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Incomplete
Status in lvm2 package in Ubuntu:
  Incomplete
Status in multipath-tools package in Ubuntu:
  Incomplete

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

Re: [Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-13 Thread Barry Warsaw

On Jan 13, 2017, at 09:26 PM, dkg wrote:

>a hang during key generation is often due to lack of entropy on the
>system.  Can you ensure that the system isn't entropy-starved somehow?

Oh, oh.  I wonder if you're getting bitten by PEP 524

https://www.python.org/dev/peps/pep-0524/

I don't believe this was back ported to Python 3.5 or 2.7 though.

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

2017-01-13 Thread Barry Warsaw

LP: #1656391

And it's reproducible in an amd64 container run locally.  So probably
some change in the images or lxc.  Maybe a new missing dependency?

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://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 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-12 Thread Barry Warsaw

On Jan 12, 2017, at 10:49 PM, Rik Mills wrote:

>ppc64el hung for nearly that whole time, then for some bizarre reason
>decided to complete. Not seen that before.

That sure is weird.

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

-- 
Mailing list: https://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 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-12 Thread Barry Warsaw

On Jan 12, 2017, at 07:30 PM, Rik Mills wrote:

>I will cancel the amd64 build when it hangs to make the buildlog
>available, but will leave the other architectures to time out and
>eventually be killed by the launchpad build system itself.

Any results yet?

Is it possible that the test suite tries to hit the internet?  And if it does
but external hosts are unavailable, what's the failure mode?

That's another difference between local builds and the Launchpad buildds.  The
latter do not allow access to the internet.

This probably isn't it though.  I added a patch to set `offline=True` to the
Context constructor and while it hasn't been killed yet, a PPA build of mine
still appears hung.  Just thought I'd mention it.

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-12 Thread Barry Warsaw

This diff gets past the build failure:

1 file changed, 1 insertion(+), 1 deletion(-)
debian/rules | 2 +-

modified   debian/rules
@@ -1,6 +1,6 @@
 #!/usr/bin/make -f
 
-export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-pie,+pic
 export QT_SELECT := qt5
 export DEBIAN_VERSION = $(shell dpkg-parsechangelog | sed -n -e 
'/^Version:/s/.*: //p')
 

[back]

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2017-01-12 Thread Barry Warsaw

Did the debdiff get deleted?  I've landed here because gpgme1.0 ftbfs is
blocking claws-mail 3.14.1-2 promotion.  I'm stuck (local build) on the
Qt-related build crash.  If I can fix that, I'll investigate the Python
test suite hang.

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

-- 
Mailing list: https://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 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

2017-01-11 Thread Barry Warsaw

If you run `dmsetup ls` as non-root on amd64, you get an error that's
close:

% dmsetup ls
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
Command failed

where as the failure in the log file says:

[K/dev/mapper/control: mknod failed: Operation not permitted
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.

If you run the same command as root on amd64, it works.

So my question is: despite having needs-root, is it somehow possible that
autopkgtest is running the armhf command as non-root, and the slightly
different error message is indicating that, or is it really not available when
run as root on armhf.

If you have an armhf device with an up-to-date Zesty, can you please
check?

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

2017-01-11 Thread Barry Warsaw

Found this older bug:
https://bugs.launchpad.net/ubuntu/+source/devmapper/+bug/105623

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://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 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

2017-01-11 Thread Barry Warsaw

On Jan 11, 2017, at 08:10 PM, Joseph Salisbury wrote:

>Does the error go away if you boot a Xenial test kernel on this machine
>and re-run the test?  That will tell us if it is a kernel regression.

We're a bit hardware starved atm, but trying to test this.

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

2017-01-11 Thread Barry Warsaw

On Jan 11, 2017, at 06:30 PM, Brad Figg wrote:

>If, due to the nature of the issue you have encountered, you are unable
>to run this command, please add a comment stating that fact and change
>the bug status to 'Confirmed'.

This is probably a regression only on armhf, so the logs generated on amd64
won't be helpful.

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

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).

2017-01-11 Thread Barry Warsaw

Removed unhelpful attachments and retagged to armhf.

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

** Also affects: multipath-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver
  (unknown version).

Status in linux package in Ubuntu:
  Incomplete
Status in lvm2 package in Ubuntu:
  New
Status in multipath-tools package in Ubuntu:
  New

Bug description:
  There is a new Zesty regression on armhf, related to the autopkgtest
  for ubuntu-image.  Here's a log of a recent run:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-zesty/zesty/armhf/u/ubuntu-
  image/20170111_171929_431b1@/log.gz

  Scroll to the bottom and you see this:

  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met
  /dev/mapper/control: mknod failed: Operation not permitted
  Failure to communicate with kernel device-mapper driver.
  Check that device-mapper is available in the kernel.
  Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown 
version).
  device mapper prerequisites not met

  Don't be misled by the gadget.yamls which name different
  architectures.  ubuntu-image should be able to build a disk image for
  any architecture on any architecture.

  What this test does is build the image, then run kpartx to map the
  partitions in the image, and then mount the partitions.  It doesn't do
  anything other than ensure that the partitions can be mounted, and
  this is where it's failing.

  This test succeeds on amd64, i386, and ppc64el.  It's never passed on
  s390x so that's not a regression.  It *used* to pass on armhf even on
  Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the
  regression.

  I will bugtask this to libdevmapper and kpartx since it's possibly a
  bug in one of those packages (though I still suspect the kernel).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  barry  5414 F pulseaudio
   /dev/snd/controlC0:  barry  5414 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 11 13:10:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864
  InstallationDate: Installed on 2016-01-22 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-01-09 Thread Barry Warsaw

** Changed in: network-manager (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-01-06 Thread Barry Warsaw

I've tested the PPA package and am satisfied that it restores CNAME
resolution in schroots without any observed regression otherwise.  I
will upload it momentarily.

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-01-05 Thread Barry Warsaw

I've uploaded a version with the reverts to my PPA:

https://launchpad.net/~barry/+archive/ubuntu/experimental

A local build looks promising, but I want to test it more before I
upload it for real.  Please do test the PPA version once it builds.

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-01-05 Thread Barry Warsaw

As per pitti's email in #12, added network-manager bugtask and
subscribed pitti.

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

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

** Changed in: network-manager (Ubuntu)
   Status: New => In Progress

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Barry Warsaw (barry)

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

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-01-05 Thread Barry Warsaw

I will test the revert of this change until upstream fixes their bug.

** Changed in: systemd (Ubuntu)
   Importance: Low => High

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-01-04 Thread Barry Warsaw

I just hit this same problem, as described here:
https://lists.ubuntu.com/archives/ubuntu-devel/2017-January/039623.html

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

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

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

[Touch-packages] [Bug 1613880] Re: package python-six 1.10.0-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-08-19 Thread Barry Warsaw

Hi, in your description you say Python 3.5 is your default Python.  Does
that mean you changed what /usr/bin/python points to?  If so, that is
not a supported configuration on Ubuntu and it's not surprising that the
installation failed.  You should use /usr/bin/python3 for all your
Python 3 needs.

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

Title:
  package python-six 1.10.0-3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in six package in Ubuntu:
  New

Bug description:
  attempting "sudo apt-get install python-matplotlib" with Python 3.5 as
  my default Python version

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-six 1.10.0-3
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Tue Aug 16 15:47:58 2016
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-08 (8 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: six
  Title: package python-six 1.10.0-3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1568889] Re: OTA and u-d-f fail if image is too big for the system partition

2016-06-03 Thread Barry Warsaw

On Jun 03, 2016, at 08:49 AM, Jean-Baptiste Lallement wrote:

>A possibility would be to calculate the size difference server side, during
>the calculation of the delta, and store this information in the json index
>for delta type updates. Then system-image can use this information to decide
>whether or not an upgrade is possible.

I think that's the only viable way to proceed.

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

Title:
  OTA and u-d-f fail if image is too big for the system partition

Status in Canonical System Image:
  Confirmed
Status in android package in Ubuntu:
  New
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  On Meizu MX4 upgrade from OTA-9.1 to OTA-10 fails.
  Upgrade downloads normally, phone restarts and starts system upgrade and 
after a while it freezes with strange icon (small microchip with red sign on it)

  When you turn off the phone and start it again it still presents itself as 
OTA-9.1 and again it founds and offer upgrade.
  Anyway some changes from OTA-10 seems to be applied, because I can see design 
changes, copy function in web browser etc.

  It's reproducible on my phone any time I try to upgrade. If I can help
  with output of some log, or anything else, please let me know.

  Well described here by Lars Kristian Wichmann Hansen:

http://askubuntu.com/questions/754963/upgrade-meizu-mx4-ubuntu-edition-to-ota-10-fails

  * u-d-f case described in bug 1582325

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

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

[Touch-packages] [Bug 1568889] Re: OTA and u-d-f fail if image is too big for the system partition

2016-06-02 Thread Barry Warsaw

Just to reiterate; currently system-image-client can't do any pre-
calculation to decide whether there is enough space to unpack the update
or not, because there is no server information on the unpacked size.

The best we can do with the current design would be for si-client or
system-settings to parse the recovery log file after reboot and somehow
look for the no space left message.

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

Title:
  OTA and u-d-f fail if image is too big for the system partition

Status in Canonical System Image:
  Confirmed
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Invalid

Bug description:
  On Meizu MX4 upgrade from OTA-9.1 to OTA-10 fails.
  Upgrade downloads normally, phone restarts and starts system upgrade and 
after a while it freezes with strange icon (small microchip with red sign on it)

  When you turn off the phone and start it again it still presents itself as 
OTA-9.1 and again it founds and offer upgrade.
  Anyway some changes from OTA-10 seems to be applied, because I can see design 
changes, copy function in web browser etc.

  It's reproducible on my phone any time I try to upgrade. If I can help
  with output of some log, or anything else, please let me know.

  Well described here by Lars Kristian Wichmann Hansen:
  
http://askubuntu.com/questions/754963/upgrade-meizu-mx4-ubuntu-edition-to-ota-10-fails

  * u-d-f case described in bug 1582325

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

-- 
Mailing list: https://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 362570] Re: Python distutils installs into 'site-packages' instead of 'dist-packages' when a prefix is set

2016-05-02 Thread Barry Warsaw

On May 02, 2016, at 08:28 PM, tripzero wrote:

>This also needs to be fixed for python3...

What exactly needs fixing?  `sudo python3 setup.py install` will install into
/usr/local/.../dist-packages which is exactly where it should install, and is
definitely on the system Python's sys.path.

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

Title:
  Python distutils installs into 'site-packages' instead of 'dist-
  packages' when a prefix is set

Status in python2.6 package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  New
Status in python2.6 package in Debian:
  Fix Released

Bug description:
  Binary package hint: python2.6

  When running a setup.py script with distutils in Jaunty like this:

  $ python setup.py install

  modules get installed at '/usr/local/lib/python2.6/dist-packages'.

  In contrast, when running

  $ python setup.py install --prefix=/usr/local

  modules get installed at '/usr/local/lib/python2.6/site-packages'.

  In the same way

  $ python setup.py install --prefix=/usr

  installs modules at '/usr/lib/python2.6/site-packages'.

  The problem is that '/usr/[local/]lib/python2.6/site-packages' is not
  part of the default sys.path .

  Maybe this is intended but I would expect that specifying an install
  prefix like 'usr' or 'usr/local' still installs modules to a place
  which is in Python's default search path - it worked this way in
  Ubuntu <= 8.10 .

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  Package: python2.6 2.6.2~rc1-0ubuntu2
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: python2.6
  Uname: Linux 2.6.28-11-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.6/+bug/362570/+subscriptions

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

[Touch-packages] [Bug 1547196] Re: Removal of revert_scalable_fonts_metric.patch causes ugliness in Claws-Mail

2016-04-22 Thread Barry Warsaw

Yes, it's unfortunate.  I've had to config away from Ubuntu Mono font in
Claws because it was just unreadable.  I've managed to keep it in gnome-
terminal and Emacs though.

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

Title:
  Removal of revert_scalable_fonts_metric.patch causes ugliness in
  Claws-Mail

Status in freetype package in Ubuntu:
  Confirmed
Status in freetype package in Debian:
  New

Bug description:
  This is mostly a tracking bug for this discussion on ubuntu-devel:

  https://lists.ubuntu.com/archives/ubuntu-
  devel/2016-February/039224.html

  The following precise-era patch was recently removed from freetype:

  http://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/wily/freetype/wily/view/head:/debian/patches-
  freetype/revert_scalable_fonts_metric.patch

  which caused a number of visual effects in various applications.  In
  Emacs, the lines get vertically closer so that more lines are visible
  on screen.  This is subtle and doesn't look too bad otherwise.

  However, in Claws-Mail several negative effects were noticed.  The
  lines in the Summary window are more squished together and the
  characters appear squished too.  This is with Sans 10 font.  This is
  less readable.

  In the Message window it's worse.  There I use Ubuntu  Mono 14.  The
  problem isn't the vertical spacing, but the horizontal spacing.  Now
  there is more space between characters and that actually makes the
  window less readable.

  I will contact the upstream Claws mailing list to see if they have any
  thoughts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libfreetype6 2.6.1-0.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 18 14:34:57 2016
  Dependencies:
   gcc-6-base 6-20160217-0ubuntu1
   libc6 2.21-0ubuntu6
   libgcc1 1:6-20160217-0ubuntu1
   libpng12-0 1.2.54-1ubuntu1
   zlib1g 1:1.2.8.dfsg-2ubuntu4
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-22 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: freetype
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1536638] Re: pip >= 8.0.0 fails because of egg-info files in python stdlib

2016-04-18 Thread Barry Warsaw

OTOH, we're hoping pip will learn how to work better with distro
provided packages.

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

Title:
  pip >= 8.0.0 fails because of egg-info files in python stdlib

Status in python2.7 package in Ubuntu:
  Invalid

Bug description:
  Up-to-date pip might fail because ubuntu ships some egg-info files for
  stdlib packages in /usr/lib/python2.7/, but egg-info files are only
  for locally installed packages.

  How to reproduce with argparse:

  $ virtualenv venv
  $ . venv/bin/activate
  $ pip install -U pip
  $ pip install -U argparse
  Collecting argparse
Downloading argparse-1.4.0-py2.py3-none-any.whl
  Installing collected packages: argparse
Found existing installation: argparse 1.2.1
  Detected a distutils installed project ('argparse') which we cannot 
uninstall. The metadata provided by distutils does not contain a list of files 
which have been installed, so pip does not know which files to uninstall.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1536638/+subscriptions

-- 
Mailing list: https://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 1568889] Re: Upgrade to OTA10 fails on Meizu MX4

2016-04-15 Thread Barry Warsaw

On Apr 15, 2016, at 01:51 PM, Jean-Baptiste Lallement wrote:

>@Barry could anything be done to estimate the space required to do an
>upgrade and stop before proceeding instead of leaving the system in a
>broken state.

We could probably do some checks of the various file systems involved, but
it's difficult to know how much additional space will be consumed by an
update.  The images do have a size parameter, but that's the size of the
compressed data files - they don't tell us anything about how much additional
space is required once they're unpacked and installed.

The other question is what to do if there's no space available.  While I agree
that the current situation isn't at all great, if we don't have a way for the
user (or even better, the system) to mitigate space issues, then it doesn't
make the situation that much better.  The device still won't successfully
update, although we would be able to tell them why.  We might be able to solve
that problem more easily though, by having system settings inspect the
recovery log file for errors after a reboot.

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

Title:
  Upgrade to OTA10 fails on Meizu MX4

Status in Canonical System Image:
  Confirmed
Status in system-image package in Ubuntu:
  Invalid
Status in ubuntu-download-manager package in Ubuntu:
  Invalid

Bug description:
  On Meizu MX4 upgrade from OTA-9.1 to OTA-10 fails.
  Upgrade downloads normally, phone restarts and starts system upgrade and 
after a while it freezes with strange icon (small microchip with red sign on it)

  When you turn off the phone and start it again it still presents itself as 
OTA-9.1 and again it founds and offer upgrade.
  Anyway some changes from OTA-10 seems to be applied, because I can see design 
changes, copy function in web browser etc.

  It's reproducible on my phone any time I try to upgrade. If I can help
  with output of some log, or anything else, please let me know.

  Well described here by Lars Kristian Wichmann Hansen:

http://askubuntu.com/questions/754963/upgrade-meizu-mx4-ubuntu-edition-to-ota-10-fails

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

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

[Touch-packages] [Bug 1568889] Re: Upgrade to OTA10 fails on Meizu MX4

2016-04-15 Thread Barry Warsaw

Thanks for the update.  Good luck!

** Changed in: system-image (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Upgrade to OTA10 fails on Meizu MX4

Status in Canonical System Image:
  Confirmed
Status in system-image package in Ubuntu:
  Invalid
Status in ubuntu-download-manager package in Ubuntu:
  Invalid

Bug description:
  On Meizu MX4 upgrade from OTA-9.1 to OTA-10 fails.
  Upgrade downloads normally, phone restarts and starts system upgrade and 
after a while it freezes with strange icon (small microchip with red sign on it)

  When you turn off the phone and start it again it still presents itself as 
OTA-9.1 and again it founds and offer upgrade.
  Anyway some changes from OTA-10 seems to be applied, because I can see design 
changes, copy function in web browser etc.

  It's reproducible on my phone any time I try to upgrade. If I can help
  with output of some log, or anything else, please let me know.

  Well described here by Lars Kristian Wichmann Hansen:
  
http://askubuntu.com/questions/754963/upgrade-meizu-mx4-ubuntu-edition-to-ota-10-fails

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

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

[Touch-packages] [Bug 1570587] Re: [FFe] Please update to bugfix release 20.7

2016-04-14 Thread Barry Warsaw

Yes, we want this in 16.04 so that the environment markers work
correctly.  My understanding is that without this, some packages can't
be properly installed.

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

Title:
  [FFe] Please update to bugfix release 20.7

Status in python-setuptools package in Ubuntu:
  New

Bug description:
  In the upstream version v20.2 setuptools switched implementations of
  parser libraries. This is an internal implementation detail, however
  the new parser library did not correctly handle several edge cases
  which caused regressions preventing certain packages from installing
  or, in some cases, even running. These issues have been fixed upstream
  by versions v20.6.6 and v20.6.8. The changelog delta between what
  Ubuntu currently has an v20.7 looks like:

  v20.7.0
  ---

  * Refactored extra enviroment marker processing
in WorkingSet.
  * Issue #533: Fixed intermittent test failures.
  * Issue #536: In msvc9_support, trap additional exceptions
that might occur when importing
``distutils.msvc9compiler`` in mingw environments.
  * Issue #537: Provide better context when package
metadata fails to decode in UTF-8.

  v20.6.8
  ---

  * Issue #523: Restored support for environment markers,
now honoring 'extra' environment markers.

  v20.6.7
  ---

  * Issue #523: Disabled support for environment markers
introduced in v20.5.

  v20.6.6
  ---

  * Issue #503: Restore support for PEP 345 environment
markers by updating to Packaging 16.6.

  v20.6.0
  ---

  * New release process that relies on
`bumpversion `_
and Travis CI for continuous deployment.
  * Project versioning semantics now follow
`semver `_ precisely.
The 'v' prefix on version numbers now also allows
version numbers to be referenced in the changelog,
e.g. https://pythonhosted.org/setuptools/history.html#v20-6-0.

  20.5
  

  * BB Pull Request #185: Add support for environment markers
in requirements in install_requires, setup_requires,
tests_require as well as adding a test for the existing
extra_requires machinery.

  20.4
  

  * Issue #422: Moved hosting to
`Github `_
from `Bitbucket `_.
Issues have been migrated, though all issues and comments
are attributed to bb-migration. So if you have a particular
issue or issues to which you've been subscribed, you will
want to "watch" the equivalent issue in Github.
The Bitbucket project will be retained for the indefinite
future, but Github now hosts the canonical project repository.

  
  As you can see, v20.4 simply adjusted documentation and some release scripts 
to deal with the migration from Mercurial+Bitbucket to Git+Github and should 
have little bearing on the actual project or have much potential for 
regression. The next version, v20.5 did add a new feature, but was later 
removed in v20.6.7. v20.6.0 is another release which largely just changed 
processed and documentation without any major code changes. v20.6.1-5 are 
nonexistent, v20.6.6 is a change we want, v20.6.8 is a change we want, and 
v20.7 is some minor bugfixes and a tiny bit of refactoring.

  You can see a diff here: https://launchpadlibrarian.net/253841863
  /python-setuptools_20.3.1-1_20.7.0-1.diff.gz though it is deceptively
  larger than it actually is due to the rename of CHANGES.txt ->
  CHANGES.rst and some shuffling around of URLs and such in the
  documentation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1570587/+subscriptions

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

[Touch-packages] [Bug 1568889] Re: Upgrade to OTA10 fails on Meizu MX4

2016-04-14 Thread Barry Warsaw

>From last_log_r:

e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/platform/mtk-msdc.0/by-name/system: 64906/132192 files (0.2% 
non-contiguous), 523388/528128 blocks
Applying update: 
ubuntu-1159f4dbbd369d693a371b78c9df7550531ba346b20ade297214ff4c7c7eb7ad.delta-ubuntu-5f4806a2d26af9d26279d1e66d217281dfa19219a85d2fd64999460f47d6efb9.tar.xz
tar: write error: No space left on device
E:Ubuntu update failed
fw_upgrade_finish
Slowly SD retry failed (/dev/block/mmcblk1p1)
W:failed to mount /dev/block/mmcblk1p1 (No such file or directory); trying 
/dev/block/mmcblk1
E:failed to mount /sdcard (No such file or directory)
E:unknown volume for path [/sdcard2/logs/recovery]
E:unknown volume for path [/sdcard1/logs/recovery]
Ubuntu update complete.
I:Ubuntu update complete.


So it looks like the partition is out of space.  I wonder if that could be the 
cause of the AssertionError in the client, possibly because either udm isn't 
noticing the ENOSPACE and returning a success code anyway? 

Take a look at /android/cache/recovery.  Delete any big .xz files (and
the associated .asc files) you find there and try again.  But maybe
there just isn't enough space available if the updates are big enough.
In that case, delete those files again and try forcing a full update,
e.g. `system-image-cli -b 0 -vv` to see if those are small enough to fit
in the available space.

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

Title:
  Upgrade to OTA10 fails on Meizu MX4

Status in Canonical System Image:
  Confirmed
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Invalid

Bug description:
  On Meizu MX4 upgrade from OTA-9.1 to OTA-10 fails.
  Upgrade downloads normally, phone restarts and starts system upgrade and 
after a while it freezes with strange icon (small microchip with red sign on it)

  When you turn off the phone and start it again it still presents itself as 
OTA-9.1 and again it founds and offer upgrade.
  Anyway some changes from OTA-10 seems to be applied, because I can see design 
changes, copy function in web browser etc.

  It's reproducible on my phone any time I try to upgrade. If I can help
  with output of some log, or anything else, please let me know.

  Well described here by Lars Kristian Wichmann Hansen:
  
http://askubuntu.com/questions/754963/upgrade-meizu-mx4-ubuntu-edition-to-ota-10-fails

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

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

[Touch-packages] [Bug 1568889] Re: Upgrade to OTA10 fails on Meizu MX4

2016-04-13 Thread Barry Warsaw

@ken-vandine: If it's failing in recovery, then it's not a system-image
problem.  Can we mark that bugtask Invalid?

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

Title:
  Upgrade to OTA10 fails on Meizu MX4

Status in Canonical System Image:
  Confirmed
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Invalid

Bug description:
  On Meizu MX4 upgrade from OTA-9.1 to OTA-10 fails.
  Upgrade downloads normally, phone restarts and starts system upgrade and 
after a while it freezes with strange icon (small microchip with red sign on it)

  When you turn off the phone and start it again it still presents itself as 
OTA-9.1 and again it founds and offer upgrade.
  Anyway some changes from OTA-10 seems to be applied, because I can see design 
changes, copy function in web browser etc.

  It's reproducible on my phone any time I try to upgrade. If I can help
  with output of some log, or anything else, please let me know.

  Well described here by Lars Kristian Wichmann Hansen:
  
http://askubuntu.com/questions/754963/upgrade-meizu-mx4-ubuntu-edition-to-ota-10-fails

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

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

[Touch-packages] [Bug 1568889] Re: Upgrade to OTA10 fails on Meizu MX4

2016-04-13 Thread Barry Warsaw

Michael: I do vaguely remember talking with Manuel about that.  I don't
know why it's been marked invalid either.

@Lukyk: /var/log/system-image/client.log please.

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

Title:
  Upgrade to OTA10 fails on Meizu MX4

Status in Canonical System Image:
  Confirmed
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  Invalid

Bug description:
  On Meizu MX4 upgrade from OTA-9.1 to OTA-10 fails.
  Upgrade downloads normally, phone restarts and starts system upgrade and 
after a while it freezes with strange icon (small microchip with red sign on it)

  When you turn off the phone and start it again it still presents itself as 
OTA-9.1 and again it founds and offer upgrade.
  Anyway some changes from OTA-10 seems to be applied, because I can see design 
changes, copy function in web browser etc.

  It's reproducible on my phone any time I try to upgrade. If I can help
  with output of some log, or anything else, please let me know.

  Well described here by Lars Kristian Wichmann Hansen:
  
http://askubuntu.com/questions/754963/upgrade-meizu-mx4-ubuntu-edition-to-ota-10-fails

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

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

[Touch-packages] [Bug 1568889] Re: Upgrade to OTA10 fails on Meizu MX4

2016-04-13 Thread Barry Warsaw

This looks like an old udm bug coming back, although I can't find the
bug number now.

si calls udm telling it both the source (url) and destination (local fs)
of the files it wants to download.  The old udm bug used to occasionally
and unpredictably lead to a situation where udm claims the files have
been successfully downloaded (via D-Bus signal), but then when si goes
to find the files, they don't exist in the requested destination
location.  For that reason, I added the assertion to si so we could at
least catch this problem when it occurs.

I don't remember the resolution in udm; it either just went away or was
fixed at one point.  But it looks like the bug is back, so I've added a
udm bug task.

One way to double check this is to try the following in the shell:

$ SYSTEMIMAGE_PYCURL=1 system-image-cli -vv

This tells si to bypass udm and use the built-in pycurl based
downloader.  You won't get the traceback (since it originates in the
udm.py module and that won't be used), but if you do have any other
problem with downloading then it may indeed been an si bug.  But I
suspect whatever udm problem we had before is back again.

** Changed in: system-image (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Upgrade to OTA10 fails on Meizu MX4

Status in Canonical System Image:
  Confirmed
Status in system-image package in Ubuntu:
  Incomplete
Status in ubuntu-download-manager package in Ubuntu:
  New

Bug description:
  On Meizu MX4 upgrade from OTA-9.1 to OTA-10 fails.
  Upgrade downloads normally, phone restarts and starts system upgrade and 
after a while it freezes with strange icon (small microchip with red sign on it)

  When you turn off the phone and start it again it still presents itself as 
OTA-9.1 and again it founds and offer upgrade.
  Anyway some changes from OTA-10 seems to be applied, because I can see design 
changes, copy function in web browser etc.

  It's reproducible on my phone any time I try to upgrade. If I can help
  with output of some log, or anything else, please let me know.

  Well described here by Lars Kristian Wichmann Hansen:
  
http://askubuntu.com/questions/754963/upgrade-meizu-mx4-ubuntu-edition-to-ota-10-fails

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

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

[Touch-packages] [Bug 1568889] Re: Upgrade to OTA10 fails on Meizu MX4

2016-04-13 Thread Barry Warsaw

** Also affects: ubuntu-download-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Upgrade to OTA10 fails on Meizu MX4

Status in Canonical System Image:
  Confirmed
Status in system-image package in Ubuntu:
  Incomplete
Status in ubuntu-download-manager package in Ubuntu:
  New

Bug description:
  On Meizu MX4 upgrade from OTA-9.1 to OTA-10 fails.
  Upgrade downloads normally, phone restarts and starts system upgrade and 
after a while it freezes with strange icon (small microchip with red sign on it)

  When you turn off the phone and start it again it still presents itself as 
OTA-9.1 and again it founds and offer upgrade.
  Anyway some changes from OTA-10 seems to be applied, because I can see design 
changes, copy function in web browser etc.

  It's reproducible on my phone any time I try to upgrade. If I can help
  with output of some log, or anything else, please let me know.

  Well described here by Lars Kristian Wichmann Hansen:
  
http://askubuntu.com/questions/754963/upgrade-meizu-mx4-ubuntu-edition-to-ota-10-fails

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

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

[Touch-packages] [Bug 1566279] Re: python2.7 crashed with SIGSEGV

2016-04-08 Thread Barry Warsaw

Very likely it's not a bug in Python, but in some extension module, e.g.
from the looks of the stacktrace gtk.

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

Title:
  python2.7 crashed with SIGSEGV

Status in python2.7 package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 AMD64 Desktop

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: python2.7-minimal 2.7.11-7
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Mon Apr  4 19:13:09 2016
  ExecutablePath: /usr/bin/python2.7
  InstallationDate: Installed on 2016-04-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcCmdline: python ubuntu-after-install.py
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   SHELL=/bin/bash
   TERM=unknown
  Signal: 11
  SourcePackage: python2.7
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: python2.7 crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1566279/+subscriptions

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

[Touch-packages] [Bug 1518955] Re: System image client log file grows indefinitely

2016-04-06 Thread Barry Warsaw

** Changed in: system-image (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  System image client log file grows indefinitely

Status in Canonical System Image:
  In Progress
Status in system-image package in Ubuntu:
  In Progress

Bug description:
  From what I can tell the log file for system image at /var/log/system-
  image/client.log is continually appended to and is not rolled or
  truncated.

  My current log has entries from 8 months ago and is over 3MB.

  Another phone shows entries 5 months old and is over 1MB

  I assume those were since the last full data wipes and flash

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

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

[Touch-packages] [Bug 1566878] Re: Alt-backtick regression

2016-04-06 Thread Barry Warsaw

I'll note that Alt-TAB still works.

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

Title:
  Alt-backtick regression

Status in xorg package in Ubuntu:
  New

Bug description:
  dist-upgrading to xorg-server (source package) 2:1.18.3-1ubuntu1
  (binary packages xserver-common, xserver-xorg-core, xvfb) introduces a
  regression for Alt-backtick switching between windows of the same
  application.  Before the upgrade, Alt-backtick works by showing you
  the switcher and letting you cycle between multiple windows of the
  same application.  After the upgrade, Alt-backtick does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160405 (Ubuntu 5.3.1-13ubuntu4)
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  6 09:52:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-16-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-17-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-16-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-17-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GK104 [GeForce GTX 760] [1458:360b]
  InstallationDate: Installed on 2016-01-22 (75 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu1
  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.6.1-1ubuntu2
  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: Wed Apr  6 09:09:25 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu1

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

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

[Touch-packages] [Bug 1566878] Re: Alt-backtick regression

2016-04-06 Thread Barry Warsaw

I narrowed this down by doing a bisect dist-upgrade with disk snapshots.
I.e. take a snapshot, manually upgrade a few packages, reboot, test,
rinse, repeat.  The only packages left are the three binary packages
mentioned in the bug report.  With the snapshot before upgrading those
packages, Alt-backtick works.  I've verified that after upgrading just
these three, the regression occurs.

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

Title:
  Alt-backtick regression

Status in xorg package in Ubuntu:
  New

Bug description:
  dist-upgrading to xorg-server (source package) 2:1.18.3-1ubuntu1
  (binary packages xserver-common, xserver-xorg-core, xvfb) introduces a
  regression for Alt-backtick switching between windows of the same
  application.  Before the upgrade, Alt-backtick works by showing you
  the switcher and letting you cycle between multiple windows of the
  same application.  After the upgrade, Alt-backtick does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160405 (Ubuntu 5.3.1-13ubuntu4)
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  6 09:52:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-16-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-17-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-16-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-17-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GK104 [GeForce GTX 760] [1458:360b]
  InstallationDate: Installed on 2016-01-22 (75 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu1
  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.6.1-1ubuntu2
  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: Wed Apr  6 09:09:25 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu1

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

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

[Touch-packages] [Bug 1566878] [NEW] Alt-backtick regression

2016-04-06 Thread Barry Warsaw

Public bug reported:

dist-upgrading to xorg-server (source package) 2:1.18.3-1ubuntu1 (binary
packages xserver-common, xserver-xorg-core, xvfb) introduces a
regression for Alt-backtick switching between windows of the same
application.  Before the upgrade, Alt-backtick works by showing you the
switcher and letting you cycle between multiple windows of the same
application.  After the upgrade, Alt-backtick does nothing.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
Uname: Linux 4.4.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
 GCC version:  gcc version 5.3.1 20160405 (Ubuntu 5.3.1-13ubuntu4)
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr  6 09:52:54 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-16-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-17-generic, x86_64: installed
 nvidia-361, 361.42, 4.4.0-16-generic, x86_64: installed
 nvidia-361, 361.42, 4.4.0-17-generic, x86_64: installed
EcryptfsInUse: Yes
GraphicsCard:
 NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GK104 [GeForce GTX 760] [1458:360b]
InstallationDate: Installed on 2016-01-22 (75 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic 
root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170X-UD5-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z170X-UD5
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu1
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.6.1-1ubuntu2
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: Wed Apr  6 09:09:25 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu1

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


** Tags: amd64 apport-bug regression-release 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/1566878

Title:
  Alt-backtick regression

Status in xorg package in Ubuntu:
  New

Bug description:
  dist-upgrading to xorg-server (source package) 2:1.18.3-1ubuntu1
  (binary packages xserver-common, xserver-xorg-core, xvfb) introduces a
  regression for Alt-backtick switching between windows of the same
  application.  Before the upgrade, Alt-backtick works by showing you
  the switcher and letting you cycle between multiple windows of the
  same application.  After the upgrade, Alt-backtick does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160405 (Ubuntu 5.3.1-13ubuntu4)
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr  6 09:52:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial

[Touch-packages] [Bug 1518955] Re: System image client log file grows indefinitely

2016-04-05 Thread Barry Warsaw

** Changed in: canonical-devices-system-image
 Assignee: Pat McGowan (pat-mcgowan) => Barry Warsaw (barry)

** No longer affects: ubuntu-system-image

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

Title:
  System image client log file grows indefinitely

Status in Canonical System Image:
  In Progress
Status in system-image package in Ubuntu:
  Confirmed

Bug description:
  From what I can tell the log file for system image at /var/log/system-
  image/client.log is continually appended to and is not rolled or
  truncated.

  My current log has entries from 8 months ago and is over 3MB.

  Another phone shows entries 5 months old and is over 1MB

  I assume those were since the last full data wipes and flash

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

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

[Touch-packages] [Bug 1390627] Re: tabs being replaced by question marks in report values

2016-03-19 Thread Barry Warsaw

** Branch linked: lp:~barry/whoopsie/lp1390627

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

Title:
  tabs being replaced by question marks in report values

Status in Daisy:
  Confirmed
Status in whoopsie package in Ubuntu:
  In Progress

Bug description:
  Kees Cook and I discovered that something, either whoopsie or daisy or
  pycassa I guess, is replacing values that contain tabs with question
  marks. This error report contains ? instead of tabs in the Registers
  field:

  https://errors.ubuntu.com/oops/e97b1abc-66bd-11e4-9406-fa163e525ba7

  Registers:

  rax 0xfdfc?-516
  rbx 0x2782a60?41429600
  rcx 0x?-1
  rdx 0xb51?2897
  rsi 0x3?3

  This is also true in the database.

  In [2]: 
cassandra.get_crash('e97b1abc-66bd-11e4-9406-fa163e525ba7')['Registers']
  Out[2]: u'rax0xfdfc?-516\nrbx
0x2782a60?41429600\nrcx0x?-1\nrdx
0xb51?2897\nrsi0x3?3\nrdi0x2813dc0?42024384\nrbp
0x3?0x3\nrsp0x7fff44d39920?0x7fff44d39920\nr8 
0x3?3\nr9 0x0?0\nr100x0?0\nr11
0x293?659\nr120x2813dc0?42024384\nr130xb51?2897\nr14
0x7f1c37f00310?139759174288144\nr150x3?3\nrip
0x7f1c39fb439d?0x7f1c39fb439d \neflags 0x293?[ CF AF SF IF 
]\ncs 0x33?51\nss 0x2b?43\nds 0x0?0\nes 
0x0?0\nfs 0x0?0\ngs 0x0?0'

  I've noticed this issue both from clients running 14.04 and 15.04.
  Other fields that include tabs are ProcStatus, Disassembly.

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

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

[Touch-packages] [Bug 1390627] Re: tabs being replaced by question marks in report values

2016-03-19 Thread Barry Warsaw

** Changed in: whoopsie (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  tabs being replaced by question marks in report values

Status in Daisy:
  Confirmed
Status in whoopsie package in Ubuntu:
  In Progress

Bug description:
  Kees Cook and I discovered that something, either whoopsie or daisy or
  pycassa I guess, is replacing values that contain tabs with question
  marks. This error report contains ? instead of tabs in the Registers
  field:

  https://errors.ubuntu.com/oops/e97b1abc-66bd-11e4-9406-fa163e525ba7

  Registers:

  rax 0xfdfc?-516
  rbx 0x2782a60?41429600
  rcx 0x?-1
  rdx 0xb51?2897
  rsi 0x3?3

  This is also true in the database.

  In [2]: 
cassandra.get_crash('e97b1abc-66bd-11e4-9406-fa163e525ba7')['Registers']
  Out[2]: u'rax0xfdfc?-516\nrbx
0x2782a60?41429600\nrcx0x?-1\nrdx
0xb51?2897\nrsi0x3?3\nrdi0x2813dc0?42024384\nrbp
0x3?0x3\nrsp0x7fff44d39920?0x7fff44d39920\nr8 
0x3?3\nr9 0x0?0\nr100x0?0\nr11
0x293?659\nr120x2813dc0?42024384\nr130xb51?2897\nr14
0x7f1c37f00310?139759174288144\nr150x3?3\nrip
0x7f1c39fb439d?0x7f1c39fb439d \neflags 0x293?[ CF AF SF IF 
]\ncs 0x33?51\nss 0x2b?43\nds 0x0?0\nes 
0x0?0\nfs 0x0?0\ngs 0x0?0'

  I've noticed this issue both from clients running 14.04 and 15.04.
  Other fields that include tabs are ProcStatus, Disassembly.

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

-- 
Mailing list: https://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 1390627] Re: tabs being replaced by question marks in report values

2016-03-19 Thread Barry Warsaw

On Mar 17, 2016, at 09:42 PM, Brian Murray wrote:

>I think fixing this in xenial is sufficient i.e. this isn't really worth
>SRU'ing by itself.

Agreed!

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

Title:
  tabs being replaced by question marks in report values

Status in Daisy:
  Confirmed
Status in whoopsie package in Ubuntu:
  In Progress

Bug description:
  Kees Cook and I discovered that something, either whoopsie or daisy or
  pycassa I guess, is replacing values that contain tabs with question
  marks. This error report contains ? instead of tabs in the Registers
  field:

  https://errors.ubuntu.com/oops/e97b1abc-66bd-11e4-9406-fa163e525ba7

  Registers:

  rax 0xfdfc?-516
  rbx 0x2782a60?41429600
  rcx 0x?-1
  rdx 0xb51?2897
  rsi 0x3?3

  This is also true in the database.

  In [2]: 
cassandra.get_crash('e97b1abc-66bd-11e4-9406-fa163e525ba7')['Registers']
  Out[2]: u'rax0xfdfc?-516\nrbx
0x2782a60?41429600\nrcx0x?-1\nrdx
0xb51?2897\nrsi0x3?3\nrdi0x2813dc0?42024384\nrbp
0x3?0x3\nrsp0x7fff44d39920?0x7fff44d39920\nr8 
0x3?3\nr9 0x0?0\nr100x0?0\nr11
0x293?659\nr120x2813dc0?42024384\nr130xb51?2897\nr14
0x7f1c37f00310?139759174288144\nr150x3?3\nrip
0x7f1c39fb439d?0x7f1c39fb439d \neflags 0x293?[ CF AF SF IF 
]\ncs 0x33?51\nss 0x2b?43\nds 0x0?0\nes 
0x0?0\nfs 0x0?0\ngs 0x0?0'

  I've noticed this issue both from clients running 14.04 and 15.04.
  Other fields that include tabs are ProcStatus, Disassembly.

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

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

[Touch-packages] [Bug 1390627] Re: tabs being replaced by question marks in report values

2016-03-18 Thread Barry Warsaw

** Changed in: whoopsie (Ubuntu)
 Assignee: (unassigned) => Barry Warsaw (barry)

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

Title:
  tabs being replaced by question marks in report values

Status in Daisy:
  Confirmed
Status in whoopsie package in Ubuntu:
  Confirmed

Bug description:
  Kees Cook and I discovered that something, either whoopsie or daisy or
  pycassa I guess, is replacing values that contain tabs with question
  marks. This error report contains ? instead of tabs in the Registers
  field:

  https://errors.ubuntu.com/oops/e97b1abc-66bd-11e4-9406-fa163e525ba7

  Registers:

  rax 0xfdfc?-516
  rbx 0x2782a60?41429600
  rcx 0x?-1
  rdx 0xb51?2897
  rsi 0x3?3

  This is also true in the database.

  In [2]: 
cassandra.get_crash('e97b1abc-66bd-11e4-9406-fa163e525ba7')['Registers']
  Out[2]: u'rax0xfdfc?-516\nrbx
0x2782a60?41429600\nrcx0x?-1\nrdx
0xb51?2897\nrsi0x3?3\nrdi0x2813dc0?42024384\nrbp
0x3?0x3\nrsp0x7fff44d39920?0x7fff44d39920\nr8 
0x3?3\nr9 0x0?0\nr100x0?0\nr11
0x293?659\nr120x2813dc0?42024384\nr130xb51?2897\nr14
0x7f1c37f00310?139759174288144\nr150x3?3\nrip
0x7f1c39fb439d?0x7f1c39fb439d <poll+45>\neflags 0x293?[ CF AF SF IF 
]\ncs 0x33?51\nss 0x2b?43\nds 0x0?0\nes 
0x0?0\nfs 0x0?0\ngs 0x0?0'

  I've noticed this issue both from clients running 14.04 and 15.04.
  Other fields that include tabs are ProcStatus, Disassembly.

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

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

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

2016-03-14 Thread Barry Warsaw

** Changed in: ubuntu-system-image
   Status: Fix Committed => Fix Released

** Changed in: system-image (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu system image:
  Fix Released
Status in system-image package in Ubuntu:
  Fix Released
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

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

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

[Touch-packages] [Bug 1518955] Re: System image client log file grows indefinitely

2016-03-04 Thread Barry Warsaw

@pat-mcgowan - Sorry I couldn't get this into si 3.1.  I'm not sure what
the right approach is for touch, but I don't think system-image client
itself should be trimming the log files.  logrotate or some other system
facility should be doing it, IMO.  It's not clear to me what that would
be.  I'll try to do some research but if you (or anyone on your team)
has suggestions, please follow up here.  I think once we figure out
*how* to do it, it'll be easy to get a release out fairly quickly.

** Also affects: ubuntu-system-image
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-system-image
 Assignee: (unassigned) => Barry Warsaw (barry)

** Changed in: ubuntu-system-image
Milestone: None => 3.2

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

Title:
  System image client log file grows indefinitely

Status in Canonical System Image:
  Confirmed
Status in Ubuntu system image:
  Triaged
Status in system-image package in Ubuntu:
  Confirmed

Bug description:
  From what I can tell the log file for system image at /var/log/system-
  image/client.log is continually appended to and is not rolled or
  truncated.

  My current log has entries from 8 months ago and is over 3MB.

  Another phone shows entries 5 months old and is over 1MB

  I assume those were since the last full data wipes and flash

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

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

[Touch-packages] [Bug 1547196] Re: Removal of revert_scalable_fonts_metric.patch causes ugliness in Claws-Mail

2016-02-29 Thread Barry Warsaw

FWIW, and unsurprisingly, the claws-mail mailing list doesn't think
there's a bug in that application.  I've had to change fonts to Droid
Sans 11 for folders and message lists, and Ubuntu Mono 13 for the
message window.  It's not what I want, but it's tolerable.

I have noticed other geometry changes with gnome terminal and Emacs, and
have had to adjust some settings, but so far I haven't had to actually
change the font of either of them.  I understand the rationale for
backing this patch out, but it does seem to have some negative side-
effects for me.  My understanding is that the patch caused problems for
other people though.  I suspect we'll have to wait (perhaps in vain) for
a font expert to dig into the issue.

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

Title:
  Removal of revert_scalable_fonts_metric.patch causes ugliness in
  Claws-Mail

Status in freetype package in Ubuntu:
  New
Status in freetype package in Debian:
  New

Bug description:
  This is mostly a tracking bug for this discussion on ubuntu-devel:

  https://lists.ubuntu.com/archives/ubuntu-
  devel/2016-February/039224.html

  The following precise-era patch was recently removed from freetype:

  http://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/wily/freetype/wily/view/head:/debian/patches-
  freetype/revert_scalable_fonts_metric.patch

  which caused a number of visual effects in various applications.  In
  Emacs, the lines get vertically closer so that more lines are visible
  on screen.  This is subtle and doesn't look too bad otherwise.

  However, in Claws-Mail several negative effects were noticed.  The
  lines in the Summary window are more squished together and the
  characters appear squished too.  This is with Sans 10 font.  This is
  less readable.

  In the Message window it's worse.  There I use Ubuntu  Mono 14.  The
  problem isn't the vertical spacing, but the horizontal spacing.  Now
  there is more space between characters and that actually makes the
  window less readable.

  I will contact the upstream Claws mailing list to see if they have any
  thoughts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libfreetype6 2.6.1-0.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 18 14:34:57 2016
  Dependencies:
   gcc-6-base 6-20160217-0ubuntu1
   libc6 2.21-0ubuntu6
   libgcc1 1:6-20160217-0ubuntu1
   libpng12-0 1.2.54-1ubuntu1
   zlib1g 1:1.2.8.dfsg-2ubuntu4
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-22 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: freetype
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

2016-02-26 Thread Barry Warsaw

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

** Changed in: system-image (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  In Progress
Status in Ubuntu system image:
  Fix Committed
Status in system-image package in Ubuntu:
  Fix Committed
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

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

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

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

2016-02-25 Thread Barry Warsaw

I guess I can't link a git branch to an LP bug yet, so:

https://code.launchpad.net/~ubuntu-system-image/ubuntu-system-image/+git
/ubuntu-system-image/+merge/287220

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

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  In Progress
Status in Ubuntu system image:
  In Progress
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

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

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

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

2016-02-24 Thread Barry Warsaw

I think I have the D-Bus side working now.  I want to add the cli switch
and then I'll prep a PPA package for you to test to make sure it's
actually doing what you want.

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

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  In Progress
Status in Ubuntu system image:
  In Progress
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

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

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

[Touch-packages] [Bug 1440607] Re: network-manager suddenly using VPN nameserver for single domain only, not updating resolv.conf

2016-02-23 Thread Barry Warsaw

I think this is the bug I'm seeing too on Xenial now.  Even though I
have "Use this connection only for resources on its network" enabled for
both IPv4 and IPv6, once the VPN is brought up, all DNS for my LAN (i.e.
talking to my internal DNS server) is non-functional and my internal LAN
host names are not resolvable.

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

Title:
  network-manager suddenly using VPN nameserver for single domain only,
  not updating resolv.conf

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When connecting to a VPN using network manager (openconnect), DNS
  resolution stops working for me.

  This is a regression since 14.10 (and vivid in the last few weeks)
  where it worked as before.  Verified working on a fresh install of
  14.10, upgraded and then verified broken on 15.04.

  Under 14.10 (utopic), the VPN name-servers were used for the entire
  system.

  Under 15.04 (vivid), as of this week, it uses the VPN name-servers
  only for the "VPN domain" (in this case, au.wordomain.com) and
  attempts to use the LAN name-server for all other names.

  This breaks for two reasons

   (1) The VPN domain (which is automatically retrieved from the VPN
  server, and is not manually set, and cannot be overridden) is not the
  only domain I required overridden to get internal DNS.

   (2) The local nameserver access is blocked/firewalled by the
  openconnect policy, and thus even global resolution stops workling.


  
  NetworkManager[836]:  VPN connection 'Work VPN' (IP Config Get) reply 
received.
  NetworkManager[836]:  VPN connection 'Work VPN' (IP4 Config Get) reply 
received.
  NetworkManager[836]:  VPN connection 'Work VPN' (IP6 Config Get) reply 
received.
  NetworkManager[836]:  VPN Gateway: 101.10.10.101
  NetworkManager[836]:  Tunnel Device: vpn0
  NetworkManager[836]:  IPv4 configuration:
  NetworkManager[836]:Internal Address: 10.131.11.21
  NetworkManager[836]:Internal Prefix: 21
  NetworkManager[836]:Internal Point-to-Point Address: 10.131.11.21
  NetworkManager[836]:Maximum Segment Size (MSS): 0
  NetworkManager[836]:Forbid Default Route: no
  NetworkManager[836]:Internal DNS: 10.97.11.12
  NetworkManager[836]:Internal DNS: 10.97.12.12
  NetworkManager[836]:DNS Domain: 'au.workdomain.com'
  NetworkManager[836]:  IPv6 configuration:
  NetworkManager[836]:Internal Address: 2406:cdef:abc:dead:beef::13
  NetworkManager[836]:Internal Prefix: 64
  NetworkManager[836]:Internal Point-to-Point Address: 
2406:cdef:abc:dead:beef::13
  NetworkManager[836]:Maximum Segment Size (MSS): 0
  NetworkManager[836]:Forbid Default Route: no
  NetworkManager[836]:DNS Domain: 'au.workdomain.com'
  openconnect[2710]: Connected vpn0 as 10.131.11.21 + 
2406:cdef:abc:dead:beef::13/64, using SSL
  NetworkManager[836]:  (vpn0): link connected
  NetworkManager[836]:  VPN connection 'Work VPN' (IP Config Get) 
complete.
  NetworkManager[836]:  VPN plugin state changed: started (4)
  NetworkManager[836]:  NetworkManager state is now CONNECTED_LOCAL
  NetworkManager[836]:  NetworkManager state is now CONNECTED_GLOBAL
  NetworkManager[836]:  Policy set 'Work VPN' (vpn0) as default for IPv6 
routing and DNS.
  NetworkManager[836]:  Writing DNS information to /sbin/resolvconf
  dnsmasq[1485]: setting upstream servers from DBus
  dnsmasq[1485]: using nameserver 220.233.0.4#53
  dnsmasq[1485]: using nameserver 220.233.0.3#53
  dnsmasq[1485]: using nameserver 10.101.11.12#53 for domain au.workdomain.com
  dnsmasq[1485]: using nameserver 10.101.11.12#53 for domain 10.in-addr.arpa
  dnsmasq[1485]: using nameserver 10.101.12.12#53 for domain au.workdomain.com
  dnsmasq[1485]: using nameserver 10.101.12.12#53 for domain 10.in-addr.arpa

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

-- 
Mailing list: https://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 1508081] Re: Fails to receive OTA updates

2016-02-22 Thread Barry Warsaw

On Feb 22, 2016, at 08:15 AM, Victor gonzalez wrote:

>Please find attached the output of $ SYSTEMIMAGE_PYCURL=1 system-image-
>cli -v done by the user.

Notice that the device is trying to update to daily/krillin and that the log
file indicates it's not a valid channel, which seems to be backed up by
viewing the system-image.u.c channels.json file:

http://system-image.ubuntu.com/channels.json

I guess you have to switch them to a valid channel for their device.

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

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  In Progress
Status in Ubuntu system image:
  In Progress
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

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

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

[Touch-packages] [Bug 1547196] Re: Removal of revert_scalable_fonts_metric.patch causes ugliness in Claws-Mail

2016-02-18 Thread Barry Warsaw

** Bug watch added: Debian Bug tracker #636776
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636776

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

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

Title:
  Removal of revert_scalable_fonts_metric.patch causes ugliness in
  Claws-Mail

Status in freetype package in Ubuntu:
  New
Status in freetype package in Debian:
  Unknown

Bug description:
  This is mostly a tracking bug for this discussion on ubuntu-devel:

  https://lists.ubuntu.com/archives/ubuntu-
  devel/2016-February/039224.html

  The following precise-era patch was recently removed from freetype:

  http://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/wily/freetype/wily/view/head:/debian/patches-
  freetype/revert_scalable_fonts_metric.patch

  which caused a number of visual effects in various applications.  In
  Emacs, the lines get vertically closer so that more lines are visible
  on screen.  This is subtle and doesn't look too bad otherwise.

  However, in Claws-Mail several negative effects were noticed.  The
  lines in the Summary window are more squished together and the
  characters appear squished too.  This is with Sans 10 font.  This is
  less readable.

  In the Message window it's worse.  There I use Ubuntu  Mono 14.  The
  problem isn't the vertical spacing, but the horizontal spacing.  Now
  there is more space between characters and that actually makes the
  window less readable.

  I will contact the upstream Claws mailing list to see if they have any
  thoughts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libfreetype6 2.6.1-0.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 18 14:34:57 2016
  Dependencies:
   gcc-6-base 6-20160217-0ubuntu1
   libc6 2.21-0ubuntu6
   libgcc1 1:6-20160217-0ubuntu1
   libpng12-0 1.2.54-1ubuntu1
   zlib1g 1:1.2.8.dfsg-2ubuntu4
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-22 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: freetype
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

2016-02-18 Thread Barry Warsaw

@victor-gonalez-0:  It's always going to be helpful to include -v when
running system-image-cli since that captures the log output to the
console.  From the method 2.jpg, you can see that UDM is not doing what
it's told to do.  IIRC, there's an open bug (I can't find it right now)
on this issue in UDM.

Sometimes what happens is that the paths system-image tells UDM to
download the files to don't exist after UDM has reported a successful
download.  That's the bug you see here.  I don't know why it happens.

One way around that is to cheat and bypass UDM.  Because of snappy, si
has an alternative built-in downloader based on pyCurl.  It doesn't know
how to do things like GSM but it often works when the UDM downloader
doesn't.  You can invoke it like so:

$ SYSTEMIMAGE_PYCURL=1 system-image-cli -v

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

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  In Progress
Status in Ubuntu system image:
  In Progress
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

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

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

[Touch-packages] [Bug 1547196] [NEW] Removal of revert_scalable_fonts_metric.patch causes ugliness in Claws-Mail

2016-02-18 Thread Barry Warsaw

Public bug reported:

This is mostly a tracking bug for this discussion on ubuntu-devel:

https://lists.ubuntu.com/archives/ubuntu-devel/2016-February/039224.html

The following precise-era patch was recently removed from freetype:

http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/wily/freetype/wily/view/head:/debian/patches-
freetype/revert_scalable_fonts_metric.patch

which caused a number of visual effects in various applications.  In
Emacs, the lines get vertically closer so that more lines are visible on
screen.  This is subtle and doesn't look too bad otherwise.

However, in Claws-Mail several negative effects were noticed.  The lines
in the Summary window are more squished together and the characters
appear squished too.  This is with Sans 10 font.  This is less readable.

In the Message window it's worse.  There I use Ubuntu  Mono 14.  The
problem isn't the vertical spacing, but the horizontal spacing.  Now
there is more space between characters and that actually makes the
window less readable.

I will contact the upstream Claws mailing list to see if they have any
thoughts.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libfreetype6 2.6.1-0.1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Feb 18 14:34:57 2016
Dependencies:
 gcc-6-base 6-20160217-0ubuntu1
 libc6 2.21-0ubuntu6
 libgcc1 1:6-20160217-0ubuntu1
 libpng12-0 1.2.54-1ubuntu1
 zlib1g 1:1.2.8.dfsg-2ubuntu4
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-01-22 (27 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
SourcePackage: freetype
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Removal of revert_scalable_fonts_metric.patch causes ugliness in
  Claws-Mail

Status in freetype package in Ubuntu:
  New

Bug description:
  This is mostly a tracking bug for this discussion on ubuntu-devel:

  https://lists.ubuntu.com/archives/ubuntu-
  devel/2016-February/039224.html

  The following precise-era patch was recently removed from freetype:

  http://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/wily/freetype/wily/view/head:/debian/patches-
  freetype/revert_scalable_fonts_metric.patch

  which caused a number of visual effects in various applications.  In
  Emacs, the lines get vertically closer so that more lines are visible
  on screen.  This is subtle and doesn't look too bad otherwise.

  However, in Claws-Mail several negative effects were noticed.  The
  lines in the Summary window are more squished together and the
  characters appear squished too.  This is with Sans 10 font.  This is
  less readable.

  In the Message window it's worse.  There I use Ubuntu  Mono 14.  The
  problem isn't the vertical spacing, but the horizontal spacing.  Now
  there is more space between characters and that actually makes the
  window less readable.

  I will contact the upstream Claws mailing list to see if they have any
  thoughts.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libfreetype6 2.6.1-0.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 18 14:34:57 2016
  Dependencies:
   gcc-6-base 6-20160217-0ubuntu1
   libc6 2.21-0ubuntu6
   libgcc1 1:6-20160217-0ubuntu1
   libpng12-0 1.2.54-1ubuntu1
   zlib1g 1:1.2.8.dfsg-2ubuntu4
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-22 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: freetype
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

2016-02-15 Thread Barry Warsaw

I'm having a difficult time figuring out a good test for
ForceAllowGSMDownload().  I already have DownloadStarted() working and
tested, but the former is giving me some pause.

Is it possible to set UDM into a mode where it thinks it's only on GSM?
What I think I'd like to do is invoke UDM in this mode, with si-client
on wifi-only.  Then through the si D-Bus API, I'd issue the
allowGSMDownload(True) call to UDM, which would then complete its
download.

For testing purposes, can I get this in UDM?

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

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  In Progress
Status in Ubuntu system image:
  In Progress
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

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

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

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

2016-02-12 Thread Barry Warsaw

One other thing to remember: we probably want a cli switch to also
override allowGSM, though there we won't need to set that on an existing
group download since si-cli blocks while a download is happening.

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

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  In Progress
Status in Ubuntu system image:
  In Progress
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

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

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

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

2016-02-12 Thread Barry Warsaw

I'm going to call the signal DownloadStarted.

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

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  In Progress
Status in Ubuntu system image:
  In Progress
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

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

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

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

2016-02-11 Thread Barry Warsaw

** Changed in: ubuntu-system-image
   Status: New => In Progress

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

** Changed in: ubuntu-system-image
 Assignee: (unassigned) => Barry Warsaw (barry)

** Changed in: ubuntu-system-image
Milestone: None => 3.1

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

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  In Progress
Status in Ubuntu system image:
  In Progress
Status in system-image package in Ubuntu:
  Confirmed
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

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

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

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

2016-02-10 Thread Barry Warsaw

** Tags added: client

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

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  In Progress
Status in Ubuntu system image:
  New
Status in system-image package in Ubuntu:
  New
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

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

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

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

2016-02-10 Thread Barry Warsaw

So, for the si dbus client we'll:

* Add a Started() signal which just proxies through from UDM.

* Add a ForceAllowGSMDownload() method (no argument), which when called
will forward to UDM's current group download's allowGSMDownload(True).
If there is no download in progress, it will no-op.  It will not change
the value of auto_download.  It will return a boolean indicating whether
a download was in progress or not (i.e. whether the force was in effect
or not).

Is that all you need?

I considered adding a flag to DownloadUpdate() but I think that is not
necessary.

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

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  In Progress
Status in Ubuntu system image:
  New
Status in system-image package in Ubuntu:
  New
Status in ubuntu-download-manager package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  See the comment regarding similar issues for large app installs.
  It seems if anything interrupts the transfer or if the connection is somewhat 
slow the download performance degenerates then times out.

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

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

Re: [Touch-packages] [Bug 1538198] Re: python in xenial cloud image

2016-01-26 Thread Barry Warsaw

On Jan 26, 2016, at 05:49 PM, Scott Moser wrote:

>  mdadm Recommends -> postfix Recommends -> python

Can we bump the latter down to a Suggests?

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

Title:
  python in xenial cloud image

Status in postfix package in Ubuntu:
  Confirmed
Status in python-defaults package in Ubuntu:
  New

Bug description:
  I'm not sure why, but python2 still has a presence inthe cloud image.
  Perhaps something Recommends it ?
  python other than 'libpython2.7' can be purged with no dependency pain.  vim 
pulls libpython in (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729924)

  $ cat /etc/cloud/build.info 
  build_name: server
  serial: 20160125-13

  $ dpkg-query --show | grep python[^3]
  dh-python 2.20151103ubuntu1
  libpython-stdlib:amd642.7.11-1
  libpython2.7:amd642.7.11-3
  libpython2.7-minimal:amd642.7.11-3
  libpython2.7-stdlib:amd64 2.7.11-3
  python2.7.11-1
  python-apt-common 1.1.0~beta1build1
  python-minimal2.7.11-1
  python2.7 2.7.11-3
  python2.7-minimal 2.7.11-3

  $ sudo apt-get --purge remove python python-minimal python2.7 
python2.7-minimal libpython-stdlib
  sudo: unable to resolve host xenial-20160126-155625
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED:
libpython-stdlib* python* python-minimal* python2.7* python2.7-minimal*
  0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
  After this operation, 4,791 kB disk space will be freed.
  Do you want to continue? [Y/n] Y

  P

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: python 2.7.11-1
  ProcVersionSignature: User Name 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  Date: Tue Jan 26 16:13:10 2016
  Ec2AMI: ami-078b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: None
  Ec2Ramdisk: None
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: python-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1523806] Re: /usr/sbin/system-image-dbus:UnicodeDecodeError:/usr/sbin/system-image-dbus@5:/usr/lib/python3/dist-packages/pkg_resources/init.py@3143:_call_aside:_initialize_ma

2015-12-11 Thread Barry Warsaw

This is a problem with setuptools 18.7 and should be fixed by 18.7.1,
which Doko is in the process of uploading to unstable.

** No longer affects: system-image (Ubuntu)

** Changed in: python-setuptools (Ubuntu)
 Assignee: (unassigned) => Matthias Klose (doko)

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

Title:
  /usr/sbin/system-image-dbus:UnicodeDecodeError:/usr/sbin/system-image-
  dbus@5:/usr/lib/python3/dist-
  
packages/pkg_resources/__init__.py@3143:_call_aside:_initialize_master_working_set:_build_master:__init__:add_entry:find_on_path:from_location:_version_from_metadata:_version_from_file:decode

Status in python-setuptools package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding system-image.  This problem was most recently seen with
  version 3.0.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/ba64d27fa5c845ce728bf0c6067cda916ac5ffd2
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1523806/+subscriptions

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

[Touch-packages] [Bug 1524857] [NEW] package systemd 228-2ubuntu1 failed to install/upgrade: triggers looping, abandoned

2015-12-10 Thread Barry Warsaw

Public bug reported:

dist-upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 228-2ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.3-0ubuntu1
Architecture: amd64
Date: Thu Dec 10 09:16:45 2015
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2011-07-12 (1611 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
MachineType: Dell Inc. Studio XPS 435MT
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic 
root=UUID=7ffae0c6-66ea-4bbd-ae3d-f98ddd9603a5 ro nomdmonddf nomdmonisw
RelatedPackageVersions:
 dpkg 1.18.3ubuntu1
 apt  1.0.10.2ubuntu1
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 
 3 overridden configuration files found.
Title: package systemd 228-2ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to xenial on 2011-12-23 (1447 days ago)
dmi.bios.date: 05/05/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.1
dmi.board.name: 0R849J
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd05/05/2009:svnDellInc.:pnStudioXPS435MT:pvr:rvnDellInc.:rn0R849J:rvrA03:cvnDellInc.:ct3:cvr:
dmi.product.name: Studio XPS 435MT
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package xenial

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

Title:
  package systemd 228-2ubuntu1 failed to install/upgrade: triggers
  looping, abandoned

Status in systemd package in Ubuntu:
  New

Bug description:
  dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 228-2ubuntu1
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu1
  Architecture: amd64
  Date: Thu Dec 10 09:16:45 2015
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2011-07-12 (1611 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  MachineType: Dell Inc. Studio XPS 435MT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic 
root=UUID=7ffae0c6-66ea-4bbd-ae3d-f98ddd9603a5 ro nomdmonddf nomdmonisw
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   3 overridden configuration files found.
  Title: package systemd 228-2ubuntu1 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2011-12-23 (1447 days ago)
  dmi.bios.date: 05/05/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.1
  dmi.board.name: 0R849J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd05/05/2009:svnDellInc.:pnStudioXPS435MT:pvr:rvnDellInc.:rn0R849J:rvrA03:cvnDellInc.:ct3:cvr:
  dmi.product.name: Studio XPS 435MT
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1524858] [NEW] package dbus 1.10.4-1ubuntu2 failed to install/upgrade: triggers looping, abandoned

2015-12-10 Thread Barry Warsaw

Public bug reported:

dist-upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: dbus 1.10.4-1ubuntu2
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.3-0ubuntu1
Architecture: amd64
Date: Thu Dec 10 09:16:45 2015
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2011-07-12 (1611 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
RelatedPackageVersions:
 dpkg 1.18.3ubuntu1
 apt  1.0.10.2ubuntu1
SourcePackage: dbus
Title: package dbus 1.10.4-1ubuntu2 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to xenial on 2011-12-23 (1447 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package dbus 1.10.4-1ubuntu2 failed to install/upgrade: triggers
  looping, abandoned

Status in dbus package in Ubuntu:
  New

Bug description:
  dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.4-1ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu1
  Architecture: amd64
  Date: Thu Dec 10 09:16:45 2015
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2011-07-12 (1611 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: dbus
  Title: package dbus 1.10.4-1ubuntu2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2011-12-23 (1447 days ago)

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

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

[Touch-packages] [Bug 1523806] Re: /usr/sbin/system-image-dbus:UnicodeDecodeError:/usr/sbin/system-image-dbus@5:/usr/lib/python3/dist-packages/pkg_resources/init.py@3143:_call_aside:_initialize_ma

2015-12-08 Thread Barry Warsaw

This isn't a bug in system-image; I've been seeing this traceback in
other contexts but now that this has been reported here I'll have to dig
into it in more detail.  FTR, I found it while working on dirtbike, the
test suite of which manipulates packages in a chroot.  What I discovered
there is that the chroot had POSIX locale and an .egg-info file was
being parsed that contained non-ascii characters (latin-1 in a person's
name).  I worked around this by ensuring the chroot had en_US.UTF-8
locale.

Something's changed though since this is a new bug affecting multiple
packages.  For now I'm going to retarget it to setuptools
(pkg_resources) and will investigate further.

** Also affects: python-setuptools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  /usr/sbin/system-image-dbus:UnicodeDecodeError:/usr/sbin/system-image-
  dbus@5:/usr/lib/python3/dist-
  
packages/pkg_resources/__init__.py@3143:_call_aside:_initialize_master_working_set:_build_master:__init__:add_entry:find_on_path:from_location:_version_from_metadata:_version_from_file:decode

Status in python-setuptools package in Ubuntu:
  New
Status in system-image package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding system-image.  This problem was most recently seen with
  version 3.0.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/ba64d27fa5c845ce728bf0c6067cda916ac5ffd2
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1523806/+subscriptions

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

[Touch-packages] [Bug 1513565] Re: libpython2.7 uses the 3.x name for ConfigParser

2015-12-02 Thread Barry Warsaw

Why are you using toolchain-r?  Are you sure that's where your getting
your libpython2.7-minimal from for trusty?

https://launchpad.net/~ubuntu-
toolchain-r/+archive/ubuntu/test?field.series_filter=trusty

This problem doesn't happen in a clean trusty chroot.

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

Title:
  libpython2.7 uses the 3.x name for ConfigParser

Status in python-pip package in Ubuntu:
  Confirmed
Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Installing a minimal virtualenv on Trusty Tahr (using libpython-
  minimal 2.7.10-4~14.04), I ran into crashes because:

File "/usr/lib/python2.7/ssl.py", line 491, in inner
  import configparser
  ImportError: No module named configparser

  Looking at the code in ssl.py, it uses "import configparser" even
  though the package is called "ConfigParser" in Python 2.7 (it changed
  in 3.0), this means that a clean virtualenv cannot install any
  packages using easy_install (since they're served over an https
  connection which uses the code in ssl.py).

  As a workaround, you can `pip install configparser` to install the
  package under the 3.0 name or change the code to be `import
  ConfigParser as configparser` to import the correct package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1513565/+subscriptions

-- 
Mailing list: https://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 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

2015-12-01 Thread Barry Warsaw

On Dec 01, 2015, at 01:38 PM, Marc Deslauriers wrote:

>1- I can't reproduce this by installing the daily live cd in a VM
>2- I can reproduce it successfully by installing the daily live cd on real 
>hardware

Confirmed that my working machine is a VM and the busted one is physical
hardware.

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

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed

Bug description:
  Latest libnss3 upgrade have broken all the browser's queries; no
  matter of which is used. For example: url auto-completion fails

  ERR_SSL_PROTOCOL_ERROR
  Unable to make a secure connection to the server. This may be a problem with 
the server or it may be requiring a client authentication certificate that you 
don't have.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libnss3 2:3.21-1ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-0.8-generic 4.3.0
  Uname: Linux 4.3.0-0-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 27 13:50:26 2015
  SourcePackage: nss
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/+subscriptions

-- 
Mailing list: https://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 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

2015-11-30 Thread Barry Warsaw

On Nov 30, 2015, at 08:51 PM, Bryan Quigley wrote:

>@barry..  Maybe do LiveCD tests on both of them to see if it's a
>configuration issue or if it might be hardware related.

I'd be very surprised if it was hardware, but I can try it.  I never had this
problem on this machine until this morning's dist-upgrade.

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

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed

Bug description:
  Latest libnss3 upgrade have broken all the browser's queries; no
  matter of which is used. For example: url auto-completion fails

  ERR_SSL_PROTOCOL_ERROR
  Unable to make a secure connection to the server. This may be a problem with 
the server or it may be requiring a client authentication certificate that you 
don't have.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libnss3 2:3.21-1ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-0.8-generic 4.3.0
  Uname: Linux 4.3.0-0-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 27 13:50:26 2015
  SourcePackage: nss
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/+subscriptions

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

[Touch-packages] [Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

2015-11-30 Thread Barry Warsaw

I just noticed this today.  AFAICT, it only affects https to
www.google.com and other Google subdomains (first noticed on
docs.google.com).  It does not affect Firefox.

Odder still, I have two fully up-to-date (AFAICT) Xenial machines, both
amd64.  One of them connects to https://www.google.com just fine, the
other produces the error shown here.  https to other sites, e.g.
Launchpad, gitlab, github, etc. all work fine.  No proxies involved, no
weird networking setups afaict (I did have bridge networking set up on
the failing machine, but disabled that and still had the problem after a
reboot).  Running chromium in --verbose mode on the console didn't show
up anything obvious.  I even disabled all plugins and it still had the
problem after a browser restart.

But at least I have two systems that are exhibiting different behavior,
so maybe that can help debug the issue.  I'm at a loss as to what to
look at next.

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

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed

Bug description:
  Latest libnss3 upgrade have broken all the browser's queries; no
  matter of which is used. For example: url auto-completion fails

  ERR_SSL_PROTOCOL_ERROR
  Unable to make a secure connection to the server. This may be a problem with 
the server or it may be requiring a client authentication certificate that you 
don't have.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libnss3 2:3.21-1ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-0.8-generic 4.3.0
  Uname: Linux 4.3.0-0-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 27 13:50:26 2015
  SourcePackage: nss
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1520568/+subscriptions

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

[Touch-packages] [Bug 1508081] Re: Fails to receive OTA updates

2015-11-24 Thread Barry Warsaw

If the log file (or system-image-cli -vv) ends with "Running group
download reactor" it basically means that s-i has told udm to download a
bunch of files, and it's waiting for the D-Bus signals indicating
successful completion or failure.  Since we're not seeing either of
those, s-i will just sit and wait, although it will eventually time out.

There could be several reasons why udm is not responding, including
networking problems anywhere along the path, or bugs. I don't know
whether udm is being actively maintained.

As an experiment, you could try `SYSTEMIMAGE_PYCURL=1 system-image-cli
-vv` and see if you get different behavior.  This bypasses udm and uses
s-i's built-in cURL-based downloader.  It's not recommended currently
for production phone environments because it doesn't have the same
networking behavior as udm, but this is essentially what's used in
snappy.  (Assuming of course that you're running s-i 3.0 or newer).

If the cURL approach works, then it points to a problem in udm.  If it
doesn't work, you should at least get more diagnostics to help narrow it
down to a problem in the networking, client, or server.

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

Title:
  Fails to receive OTA updates

Status in Canonical System Image:
  Incomplete
Status in Ubuntu system image:
  New
Status in system-image package in Ubuntu:
  New
Status in ubuntu-download-manager package in Ubuntu:
  New

Bug description:
  Ubuntu Touch 15.04 (r23) [mako]

  Issue: Phone appears to fail to receive OTA updates. Previously, I jumped 
from (r15) to (r23) due to missing OTA updates. Currently, I see (r24) appears 
to be released on 2015 Oct 16.
  Expected behavior: System Settings > System > Updates (or System Settings > 
About this phone > Check for updates) reveals new image that I can release and 
download.
  Actual behavior: Checking for updates... > Software is up to date

  *Apologies for posting bug here, I cannot find correct location to
  file a bug against release/image/OTA/etc.

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

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

[Touch-packages] [Bug 1518955] Re: System image client log file grows indefinitely

2015-11-23 Thread Barry Warsaw

I guess you're asking for a logrotate.d entry for /var/log/system-
image/client.log?

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

Title:
  System image client log file grows indefinitely

Status in Canonical System Image:
  Confirmed
Status in system-image package in Ubuntu:
  New

Bug description:
  From what I can tell the log file for system image at /var/log/system-
  image/client.log is continually appended to and is not rolled or
  truncated.

  My current log has entries from 8 months ago and is over 3MB.

  Another phone shows entries 5 months old and is over 1MB

  I assume those were since the last full data wipes and flash

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

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

[Touch-packages] [Bug 1518955] Re: System image client log file grows indefinitely

2015-11-23 Thread Barry Warsaw

** Tags added: client

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

Title:
  System image client log file grows indefinitely

Status in Canonical System Image:
  Confirmed
Status in system-image package in Ubuntu:
  New

Bug description:
  From what I can tell the log file for system image at /var/log/system-
  image/client.log is continually appended to and is not rolled or
  truncated.

  My current log has entries from 8 months ago and is over 3MB.

  Another phone shows entries 5 months old and is over 1MB

  I assume those were since the last full data wipes and flash

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

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

1 2 3 4 >

1 - 100 of 360 matches

Mail list logo