[Touch-packages] [Bug 1686243] Re: NVIDIA driver

2017-04-25 Thread Timo Aaltonen
you're using an unofficial ppa which could mess things up, besides your
machine is a hybrid machine so you need to use prime-select in order to
switch to nvidia

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

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

Title:
  NVIDIA driver

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Trying for days to install an nvidia driver

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-49.52-lowlatency 4.8.17
  Uname: Linux 4.8.0-49-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Apr 26 01:19:29 2017
  DistUpgraded: 2017-04-26 01:05:13,339 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-49-lowlatency, x86_64: installed
   nvidia-378, 378.13, 4.8.0-49-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2017-04-24 (1 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-lowlatency 
root=UUID=65af2065-0769-48de-9408-1d7d5313f54e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2017-04-25 (0 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.80+git20170420.691a2157-0ubuntu0ricotz~xenial
  version.libgl1-mesa-dri: libgl1-mesa-dri 
17.1.0~git20170425+17.1.2bf79cb2-0ubuntu0ricotz~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
17.1.0~git20170425+17.1.2bf79cb2-0ubuntu0ricotz~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Apr 26 01:05:56 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "vesa" (module does not exist, 0)
   Failed to load module "fbdev" (module does not exist, 0)
   Failed to load module "vesa" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2017-04-25 Thread Sachin Bawoor
** Changed in: dnsmasq (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (cyphermox) => Sachin Bawoor (bawoor)

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

Title:
  dnsmasq sometimes fails to resolve private names in networks with non-
  equivalent nameservers

Status in dnsmasq package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Precise:
  Triaged
Status in network-manager source package in Precise:
  Invalid
Status in dnsmasq package in Debian:
  New

Bug description:
  A number of reports already filed against network-manager seem to
  reflect this problem, but to make things very clear I am opening a new
  report.  Where appropriate I will mark other reports as duplicates of
  this one.

  Consider a pre-Precise system with the following /etc/resolv.conf:

  nameserver 192.168.0.1
  nameserver 8.8.8.8

  The first address is the address of a nameserver on the LAN that can
  resolve both private and public domain names.  The second address is
  the address of a nameserver on the Internet that can resolve only
  public names.

  This setup works fine because the GNU resolver always tries the first-
  listed address first.

  Now the administrator upgrades to Precise and instead of writing the
  above to resolv.conf, NetworkManager writes

  server=192.168.0.1
  server=8.8.8.8

  to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to
  resolv.conf.  Resolution of private domain names is now broken because
  dnsmasq treats the two upstream nameservers as equals and uses the
  faster one, which could be 8.8.8.8.

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

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


[Touch-packages] [Bug 1667284] Re: [unity8] can't drag child window back into main GUI

2017-04-25 Thread Launchpad Bug Tracker
[Expired for unity8 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [unity8] can't drag child window back into main GUI

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

Bug description:
  ubuntu 17.04 unity8. see the screenshot first.

  install tiled (qt app) "apt install tiled"
  launch tiled
  in tiled you can move the gui elements arround, drag one of the tabs out of 
main window "Mini-map" "Objects" "Tilesets"  "Terrains" or whatever. it will 
pop out of main window into a child window. now move the tab at the previous 
position in the main window by drag and droping it. you can't because there is 
no way to move or close the child window.

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

-- 
Mailing list: https://launchpad.net/~touch-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-04-25 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

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

-- 
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:
  Expired

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 1667635] Re: Can't add account that used a .paris domain name (OwnCloud account)

2017-04-25 Thread Launchpad Bug Tracker
[Expired for ubuntu-system-settings-online-accounts (Ubuntu) because
there has been no activity for 60 days.]

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Can't add account that used a .paris domain name (OwnCloud account)

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Expired

Bug description:
  Using stable lastest OTA on pro5 (same issue on e4.5):

   * open system settings
   * accounts
   * new account
   * OwnCloud
   * set for example http://bug.with-domain.paris in the url field
   * red alerting message appear
   * can't submit the form

  I don't know in the code ifnowncloud use a custom url parsing check or
  if it use a system check, but it should include (or not exclude) those
  new domain extension like the .paris

  Librement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1667635/+subscriptions

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


[Touch-packages] [Bug 1686275] [NEW] System message indicated a bug on reboot. Shows on reboot always.

2017-04-25 Thread Justin Ngan
Public bug reported:

System message indicated a bug on reboot. Shows on reboot always.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-49-generic x86_64
NonfreeKernelModules: nvidia_uvm wl 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.39  Tue Jan 31 20:47:00 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Apr 25 22:02:42 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GM206 [GeForce GTX 950] [1043:8581]
InstallationDate: Installed on 2017-03-12 (44 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
MachineType: Hewlett-Packard 550-009
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-49-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2015
dmi.bios.vendor: AMI
dmi.bios.version: 80.06
dmi.board.name: 2B2C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 1.01
dmi.chassis.asset.tag: MXX52512YG
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvr80.06:bd04/01/2015:svnHewlett-Packard:pn550-009:pvr1.00:rvnHewlett-Packard:rn2B2C:rvr1.01:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: 550-009
dmi.product.version: 1.00
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Apr 25 21:58:26 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.18.4-1ubuntu6.1~16.04.1

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


** Tags: amd64 apport-bug ubuntu xenial

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/xorg/+question/628593

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

Title:
  System message indicated a bug on reboot. Shows on reboot always.

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  System message indicated a bug on reboot. Shows on reboot always.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl 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.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Apr 25 22:02:42 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM206 [GeForce GTX 950] [1043:8581]
  InstallationDate: Installed on 2017-03-12 (44 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Hewlett-Packard 550-009
  ProcEnviron:
   

[Touch-packages] [Bug 1524963] Re: Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type'

2017-04-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Could not grab port (tty/ttyS4): 'Cannot add port 'tty/ttyS4',
  unhandled serial type'

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  I see these warnings in the journalctl after every boot, on Ubuntu
  15.10:

  
  ```
  Dec 11 09:18:08 M2 ModemManager[816]:   Could not grab port 
(tty/ttyS4): 'Cannot add port 'tty/ttyS4', unhandled serial type'
  Dec 11 09:18:08 M2 ModemManager[816]:   Couldn't create modem for 
device at '/sys/devices/pci:00/:00:16.3': Failed to find primary AT port
  Dec 11 09:18:08 M2 ModemManager[816]:   Modem couldn't be initialized: 
Couldn't check unlock status: SIM not inserted
  ```

  Any clues what this could be and why modem can't be initialized?
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-05-22 (202 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: modemmanager 1.4.10-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  wily
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: Upgraded to wily on 2015-11-15 (24 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Touch-packages] [Bug 1685272] Re: gnome-shell: no window border

2017-04-25 Thread Daniel van Vugt
Yes, what Amr said...

$ dpkg -s light-themes | grep Source
Source: ubuntu-themes


** Changed in: light-themes (Ubuntu Artful)
   Status: Confirmed => Invalid

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

Title:
  gnome-shell: no window border

Status in light-themes package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in light-themes source package in Artful:
  Invalid
Status in ubuntu-themes source package in Artful:
  Confirmed

Bug description:
  Under gnome-shell, there are no window borders.  See attached
  screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1685272/+subscriptions

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


[Touch-packages] [Bug 1685272] Re: gnome-shell: no window border

2017-04-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  gnome-shell: no window border

Status in light-themes package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Confirmed
Status in light-themes source package in Artful:
  Invalid
Status in ubuntu-themes source package in Artful:
  Confirmed

Bug description:
  Under gnome-shell, there are no window borders.  See attached
  screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1685272/+subscriptions

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


[Touch-packages] [Bug 492290] Re: Apport console frontend (ubuntu-bug, apport-cli) doesn't work with non-English locales

2017-04-25 Thread Andrey Vertexx
I confirm this bug on 14.04.1 for russian.

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

Title:
  Apport console frontend (ubuntu-bug, apport-cli) doesn't work with
  non-English locales

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: apport

  I try to report bug using ubuntu-bug:

  divius@divius-laptop:~/Work/pkibd/cbuild$ ubuntu-bug gnome-system-
  monitor

  *** Сбор информации о проблеме

  Собранная информация может быть направлена разработчикам
  для улучшения приложения. Это может занять несколько минут.
  ..

  *** Отправить отчёт об ошибке разработчикам?

  После того, как отчёт будет отправлен, заполните форму
  в автоматически открывшемся окне обозревателя.

  Что вы хотите сделать? Возможные варианты:
О: Отправить отчёт (5.0 KiB)
П: Просмотреть отчёт
С: Сохранить файл отчёта для последующей отправки или копирования куда-либо
Т: Отменить
  Пожалуйста, выберите (О/П/С/Т):ы
  /usr/bin/apport-cli:84: UnicodeWarning: Unicode equal comparison failed to 
convert both arguments to Unicode - interpreting them as being unequal
return self.keys.index(response[0].upper()) + 1
  Что вы хотите сделать? Возможные варианты:
О: Отправить отчёт (5.0 KiB)
П: Просмотреть отчёт
С: Сохранить файл отчёта для последующей отправки или копирования куда-либо
Т: Отменить
  Пожалуйста, выберите (О/П/С/Т):
  Что вы хотите сделать? Возможные варианты:
О: Отправить отчёт (5.0 KiB)
П: Просмотреть отчёт
С: Сохранить файл отчёта для последующей отправки или копирования куда-либо
Т: Отменить
  Пожалуйста, выберите (О/П/С/Т):s
  Что вы хотите сделать? Возможные варианты:
О: Отправить отчёт (5.0 KiB)
П: Просмотреть отчёт
С: Сохранить файл отчёта для последующей отправки или копирования куда-либо
Т: Отменить
  Пожалуйста, выберите (О/П/С/Т):d
  Что вы хотите сделать? Возможные варианты:
О: Отправить отчёт (5.0 KiB)
П: Просмотреть отчёт
С: Сохранить файл отчёта для последующей отправки или копирования куда-либо
Т: Отменить
  Пожалуйста, выберите (О/П/С/Т):О
  Что вы хотите сделать? Возможные варианты:
О: Отправить отчёт (5.0 KiB)
П: Просмотреть отчёт
С: Сохранить файл отчёта для последующей отправки или копирования куда-либо
Т: Отменить
  Пожалуйста, выберите (О/П/С/Т):

  
  And so on. No matter what letter (Russian or English) I input it simply 
reask. Only Ctrl+C helps.

  apport 1.9.3-0ubuntu4.1

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

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


[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in basefiles for ubuntu

2017-04-25 Thread David Britton
** Changed in: base-files (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Ship ubuntu-advantage in basefiles for ubuntu

Status in base-files package in Ubuntu:
  Incomplete

Bug description:
  [Impact]

   * Allow ubuntu-advantage users to access the extended security
  maintenance script with a simple command line tool.  This script needs
  to hit precise machines and be easy for ubuntu-advantage customers to
  enable, thus basefiles was chosen as a home.

  [Test Case]

   * Run ubuntu-advantage, it should print out help
   * Run sudo ubuntu-advantage enable  (without sudo it will warn you), 
but you need to be an ubuntu-advantage customer to get that token.  In the end, 
the script simply adds and removes an /etc/apt/sources.list.d entry.
   * you can contact me (d...@canonical.com) if you would like a token for test 
purposes.

  [Regression Potential]

   * Low, this is a new script, not included in any automated startup
  paths.

  [Other Info]

   * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1686183/+subscriptions

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


[Touch-packages] [Bug 349469] ☑cool surprise

2017-04-25 Thread Muhammad Najmi Fauzi
Hello!

I've  just read something really surprising, just take a look, you'll be
amazed http://www.musorkalauz.hu/fraction.php?0706

Sincerely yours, najmiii

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Ambasa:
  New
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Triaged
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

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

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


[Touch-packages] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe

2017-04-25 Thread Mathew Hodson
** No longer affects: mesa (Ubuntu Xenial)

** No longer affects: mesa (Ubuntu)

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

Title:
  xenial: invalid opcode when using llvmpipe

Status in OEM Priority Project:
  Fix Released
Status in System76:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in llvm-toolchain-3.8 package in Ubuntu:
  Fix Released
Status in llvm-toolchain-3.8 source package in Xenial:
  Fix Released

Bug description:
  [Description updated to reflect state of 16.04 release ISO]

  == In summary ==

  If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
  possibly other GPUs that likewise require use of the llvmpipe opengl
  software fallback), a work-around is needed to install Ubuntu 16.04
  desktop.

  To work-around this, you'll need to:

  1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try
  Ubuntu without installing")

  2) Check "Download updates while installing Ubuntu"

  ** Note: "Download updates while installing Ubuntu" doesn't currently
  seem to be working. If after installing 16.04 on effected Skylake
  hardware you find that Unity/Compiz is broken, switch to a VT with
  Control+Alt+F1, login, and then run:

  sudo apt-get update
  sudo apt-get dist-upgrade

  You should see the `libllvm3.8` package get updated. After a reboot,
  Unity/Compiz should be working.

  == In detail ==

  The Ubuntu 16.04 desktop ISOs include libllvm3.8 1:3.8-2ubuntu1, which
  has a bug that results in invalid JIT code generation when using the
  mesa llvmpipe opengl software fallback on Skylake CPUs.

  When you encounter this bug, Unity/Compiz will fail to start, and
  you'll see something like this in dmesg:

  [ 2092.557913] traps: compiz[10155] trap invalid opcode
  ip:7efc940030d4 sp:7ffccd914ea0 error:0

  libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make
  it onto the 16.04 release ISOs. It will be included on the 16.04.1
  ISOs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions

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


[Touch-packages] [Bug 1686254] [NEW] OpenVPN auto-connect options greyed out or missing for no reason

2017-04-25 Thread Paul
Public bug reported:

"Automatically connect to this network..." and "Automatically connect to
VPN when..." are greyed out or missing from the GUI, the former is also
"checked" however this is not true as it never attempts to auto connect.

There's no reason for these to be unavailable, especially when personal
encrypted passwords and keys are used.

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

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

** Affects: plasma-nm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: openvpn

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

** Also affects: plasma-nm (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  OpenVPN auto-connect options greyed out or missing for no reason

Status in network-manager package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in plasma-nm package in Ubuntu:
  New

Bug description:
  "Automatically connect to this network..." and "Automatically connect
  to VPN when..." are greyed out or missing from the GUI, the former is
  also "checked" however this is not true as it never attempts to auto
  connect.

  There's no reason for these to be unavailable, especially when
  personal encrypted passwords and keys are used.

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

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


[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-04-25 Thread Eric Desrochers
** Description changed:

  [Impact]
  
  * Context:
  
  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit
  only (Confirmed with AMD representative). Current OpenSSL version in
  Ryzens still calls SHA for SSSE3 routine as result a number of
  extensions were effectively masked on Ryzen and shows no improvement.
  
  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family : 23
  model : 1
  model name : AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni 
pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
  
  [2] - sha_ni: SHA1/SHA256 Instruction Extensions
  
  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...
  
  * Program to performs the CPUID check:
  
  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions
  
  ... Availability of the Intel® SHA Extensions on a particular processor
  can be determined by checking the SHA CPUID bit in CPUID.(EAX=07H,
  ECX=0):EBX.SHA [bit 29]. The following C function, using inline
  assembly, performs the CPUID check:
  
  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;
  
     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;
  
     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );
  
     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --
  
  On CPU with sha_ni the program return "1". Otherwise it return "0".
  
  [Test Case]
  
   * Reproducible with Xenial/Zesty/Artful release.
  
   * Generated a checksum of a big file (e.g. 5GB file) with openssl
   $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
  SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8
  
  real  0m12.835s
  user  0m12.344s
  sys   0m0.484s
  
  * Openssl speed
  $ openssl speed sha1
  Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
  Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
  Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
  Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
  Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
  OpenSSL 1.0.2g 1 Mar 2016
  built on: reproducible build, date unspecified
  options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
  compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT 
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall 
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM 
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
  The 'numbers' are in 1000s of bytes per second processed.
  type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
  sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55
  
  The performance are clearly better when using the patch which take
  benefit of the sha extension. (See Regression Potential section for
  result with patch)
  
  [Regression Potential]
  
   * Note from irc discussion with apw and rbasak :
  
  [10:03:20]  slashd, for me some new functionality like that is ok
  as long as it is very self-contained so easy to review and confirm is
  only used on the new h/w
  
  [10:03:52] one of our main goals is to avoid regressions
  
  [10:12:24]  The SRU policy does explicitly permit hardware
  enablement in an LTS IIRC, though I'd expect ~ubuntu-sru to be involved
  in mitigating risk and making the final risk decision, FWIW.
  
  Full discussion:
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2
  
   * It basically allow openssl to take benefit of sha extension potential
  (mostly performance-wise) now that new AMD cpu starting  to have the
  capability.
  
  * The code check the CPUID bit to determine if the sha instructions are
  available are not.
  
   * Generated a checksum of a big file (e.g. 5GB file) with openssl
   $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
  SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8
  
  

[Touch-packages] [Bug 1686211] Re: package libpython2.7 2.7.11-7ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/libpython2.7.so.1.0' to '/usr/lib/i386-linux

2017-04-25 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that there was an error on your system when
trying to install a particular package.  Please execute the following
command, as it will clear your package cache, in a terminal:

sudo apt-get clean

Then try performing the update again.  This will likely resolve your
issue, but the failure could be caused by filesystem or memory
corruption.  So please also run a fsck on your filesystem(s) and a
memory test.  Thanks in advance!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: corrupted-package

** Changed in: python2.7 (Ubuntu)
   Status: New => Invalid

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

Title:
  package libpython2.7 2.7.11-7ubuntu1 failed to install/upgrade: cannot
  copy extracted data for './usr/lib/i386-linux-gnu/libpython2.7.so.1.0'
  to '/usr/lib/i386-linux-gnu/libpython2.7.so.1.0.dpkg-new': unexpected
  end of file or stream

Status in python2.7 package in Ubuntu:
  Invalid

Bug description:
  i dont know details thinked was automatic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpython2.7 2.7.11-7ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  Date: Tue Apr 25 15:47:34 2017
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libpython2.7.so.1.0' to 
'/usr/lib/i386-linux-gnu/libpython2.7.so.1.0.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2017-04-23 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: python2.7
  Title: package libpython2.7 2.7.11-7ubuntu1 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libpython2.7.so.1.0' to 
'/usr/lib/i386-linux-gnu/libpython2.7.so.1.0.dpkg-new': unexpected end of file 
or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

2017-04-25 Thread Julian Andres Klode
** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: apt (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: apt (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: apt (Ubuntu Yakkety)
   Status: New => In Progress

** Changed in: apt (Ubuntu Zesty)
   Status: New => In Progress

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  In Progress
Status in apt source package in Yakkety:
  In Progress
Status in apt source package in Zesty:
  In Progress

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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


[Touch-packages] [Bug 1672710] Re: apt fails to verify keys when Dir has space, and set via cmdline

2017-04-25 Thread Julian Andres Klode
** Changed in: apt (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Changed in: apt (Ubuntu Yakkety)
   Status: Triaged => Fix Committed

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

Title:
  apt fails to verify keys when Dir has space, and set via cmdline

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

Bug description:
  When Dir has a space, and it is set via APT_CONFIG file, keys are found and 
validated correctly.
  When Dir is set without a space via cmdline, keys are found and validated 
correctly.
  When Dir is set with a space via cmdline, keys are not found and repositories 
are not verified.

  [Test case]
  Please see attached reproducer, which works on xenial system (gpg1) but not 
on zesty system (gpg2)

  $ bash reproducer.sh
  ++ mktemp -d
  + tmpdir=/tmp/tmp.sFipy6h5yL
  + pushd /tmp/tmp.sFipy6h5yL
  /tmp/tmp.sFipy6h5yL ~
  + mkdir 'Sub Dir'
  + pushd 'Sub Dir'
  /tmp/tmp.sFipy6h5yL/Sub Dir /tmp/tmp.sFipy6h5yL ~
  + mkdir -p etc/apt/apt.conf.d
  + mkdir -p etc/apt/trusted.gpg.d
  + mkdir -p etc/apt/preferences.d
  + mkdir -p var/lib/apt/lists/partial
  + mkdir -p var/lib/dpkg
  + touch var/lib/dpkg/status
  + cp /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg 
etc/apt/trusted.gpg.d/
  + echo 'deb http://archive.ubuntu.com/ubuntu/ trusty main'
  + echo 'Dir "/tmp/tmp.sFipy6h5yL/Sub Dir";'
  + export APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf
  + APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf
  + cat /tmp/tmp.sFipy6h5yL/apt.conf
  Dir "/tmp/tmp.sFipy6h5yL/Sub Dir";
  + :
  + : == list available keys ==
  + apt-key list
  /tmp/tmp.sFipy6h5yL/Sub 
Dir/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg
  
-
  pub   rsa4096 2012-05-11 [SC]
    790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2012) 


  + :
  + : == update with environ APT_CONFIG setting the Dir variable ==
  + apt update
  Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease
  Get:2 http://archive.ubuntu.com/ubuntu trusty Release [58.5 kB]
  Get:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg [933 B]
  Get:4 http://archive.ubuntu.com/ubuntu trusty/main amd64 Packages [1,350 kB]
  Fetched 1,410 kB in 0s (1,959 kB/s)
  Reading package lists... Done
  Building dependency tree... Done
  All packages are up to date.
  + unset APT_CONFIG
  + :
  + : == update with cmdline Dir option setting Dir to relative pwd ==
  + apt -o Dir=./ update
  Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu trusty Release
  Reading package lists... Done
  Building dependency tree... Done
  All packages are up to date.
  + :
  + : == update with cmdline Dir option setting Dir to absolute pwd with space 
==
  + apt -o 'Dir=/tmp/tmp.sFipy6h5yL/Sub Dir' update
  Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu trusty Release
  Err:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg
    The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  Reading package lists... Done
  Building dependency tree... Done
  All packages are up to date.
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://archive.ubuntu.com/ubuntu trusty Release: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/Release.gpg  
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  
  [Regression Potential]
  The fix changes the code to generate quotes in the Commmandline:AsString 
option, which dumps the command line for logging purposes. This was not 
parseable before, causing the file to be rejected, so what can happen is that 
something now works that did not before.

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

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


[Touch-packages] [Bug 1554848] Re: Please randomise automatic updates over a longer period

2017-04-25 Thread Haw Loeung
As per LP bug #1615482, the window has been reduced to 1hr (see
https://github.com/julian-
klode/apt/commit/93a513c4953bab9b0569c9e2bc2c74075a50dc00) which is
still better than the original 30min window. We'll see how this goes.

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

Title:
  Please randomise automatic updates over a longer period

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Confirmed
Status in unattended-upgrades source package in Trusty:
  Confirmed
Status in apt source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released

Bug description:
  Load on the main Ubuntu archive servers is rather peakish, and tends
  to create a traffic peak on our Internet links at fairly regular times
  each day, preventing customers from accessing the archive.  This
  impacts the cloud archive mirrors using the ubuntu-repository-cache
  charm also, because they are hitting a squid cache which is backed by
  the main archive.  This effect will be even more pronounced under the
  recently-announced automatic update policy for xenial.

  One solution which would alleviate this to some extent would be to
  spread the load over a longer period by increasing the random sleep
  time in the daily update script from 30 minutes to, say, 1-2 hours.

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

-- 
Mailing list: https://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 1615482] Re: apt-daily timer runs at random hours of the day

2017-04-25 Thread Haw Loeung
On Tue, Apr 25, 2017 at 08:16:37AM -, Julian Andres Klode wrote:
> We can't increase the delay for older distros, as it delays all daily
> cron jobs there. We could increase to 2 hours, but I don't feel like
> doing daily APT releases changing time outs, and 1.4.1 with the 1 hour
> time out is out already.
>

For older distros where apt daily still happens from cron (and not
systemd timers), we could rename /etc/cron.daily/apt to something like
zzapt so it happens at the very end so it doesn't delay all daily cron
jobs.

Then ship out /etc/apt/apt.conf.d/50unattended-upgrades overriding
APT::Periodic::RandomSleep (3600) so it's easier for users to override
if needed.

> I mean, I change it to 2 hours now, and tomorrow someone else turns up
> and either says 2 hours is too much or 2 hours is too low. Or not "5 to
> 7, I'd rather have 6 to 8." I think at some point we have to stay with a
> decision.
>
> If 1 hour turns out to be problematic, then we should revisit this when
> we see an issue IMO.

Okay.


Thanks,

Haw

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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


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

2017-04-25 Thread Brian Murray
I tested installing python3 using the instructions at
https://passingcuriosity.com/2015/installing-python-from-source/ and
sure enough I received the same Traceback.

Setting up python3.5-minimal (3.5.3-1) ...
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 57, in 
import types
  File "/usr/lib/python3.5/types.py", line 166, in 
import functools as _functools
  File "/usr/lib/python3.5/functools.py", line 23, in 
from weakref import WeakKeyDictionary
  File "/usr/lib/python3.5/weakref.py", line 12, in 
from _weakref import (
ImportError: cannot import name '_remove_dead_weakref'
dpkg: error processing package python3.5-minimal (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of python3-minimal:
 python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however:
  Package python3.5-minimal is not configured yet.

dpkg: error processing package python3-minimal (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup 
error from a previous failure.

  Errors were encountered while processing:
 python3.5-minimal
 python3-minimal

Once I removed /usr/local/bin/python3.5 I was then able to fix the
upgrade via 'sudo apt-get -f install'.

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

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

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Got this error while using "Transmageddon Video Transcoder" and again
  while updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

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

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


[Touch-packages] [Bug 1686243] [NEW] NVIDIA driver

2017-04-25 Thread Sebastian Carter
Public bug reported:

Trying for days to install an nvidia driver

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-49.52-lowlatency 4.8.17
Uname: Linux 4.8.0-49-lowlatency x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Wed Apr 26 01:19:29 2017
DistUpgraded: 2017-04-26 01:05:13,339 DEBUG icon theme changed, re-reading
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.8.0-49-lowlatency, x86_64: installed
 nvidia-378, 378.13, 4.8.0-49-lowlatency, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
InstallationDate: Installed on 2017-04-24 (1 days ago)
InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-lowlatency 
root=UUID=65af2065-0769-48de-9408-1d7d5313f54e ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to yakkety on 2017-04-25 (0 days ago)
dmi.bios.date: 11/11/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.80+git20170420.691a2157-0ubuntu0ricotz~xenial
version.libgl1-mesa-dri: libgl1-mesa-dri 
17.1.0~git20170425+17.1.2bf79cb2-0ubuntu0ricotz~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
17.1.0~git20170425+17.1.2bf79cb2-0ubuntu0ricotz~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Apr 26 01:05:56 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "fbdev" (module does not exist, 0)
 Failed to load module "vesa" (module does not exist, 0)
 Failed to load module "fbdev" (module does not exist, 0)
 Failed to load module "vesa" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug third-party-packages ubuntu yakkety

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

Title:
  NVIDIA driver

Status in xorg package in Ubuntu:
  New

Bug description:
  Trying for days to install an nvidia driver

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-49.52-lowlatency 4.8.17
  Uname: Linux 4.8.0-49-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Apr 26 01:19:29 2017
  DistUpgraded: 2017-04-26 01:05:13,339 DEBUG icon theme changed, re-reading
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-49-lowlatency, x86_64: installed
   nvidia-378, 378.13, 4.8.0-49-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2017-04-24 (1 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-lowlatency 

[Touch-packages] [Bug 1686036] Re: strange behavior after restore snapshot

2017-04-25 Thread Christian Brauner
Reproducible. Can you please open this bug on github.

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

Title:
  strange behavior after restore snapshot

Status in lxc package in Ubuntu:
  New

Bug description:
  uname -a
  Linux lxd2-chel1 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  lxd: 2.12-0ubuntu3~ubuntu16.04.1~ppa1
  zfsutils-linux: 0.6.5.6-0ubuntu16

  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  after restore container from shapshot cannot add new snapshot or restore again
  until restart container

  example:

  
  # lxc image list
  
+---+--++--++-+--+
  | ALIAS | FINGERPRINT  | PUBLIC | DESCRIPTION 
 |  ARCH  |  SIZE   | UPLOAD DATE  |
  
+---+--++--++-+--+
  | debian/jessie | ba43812c4cb9 | no | Debian jessie amd64 
(20170423_22:42) | x86_64 | 94.14MB | Apr 24, 2017 at 9:07am (UTC) |
  
+---+--++--++-+--+

  # lxc launch debian/jessie
  Creating popular-kitten

  The container you are starting doesn't have any network attached to it.
To create a new network, use: lxc network create
To attach a network to a container, use: lxc network attach

  Starting popular-kitten

  
  # lxc info popular-kitten
  Name: popular-kitten
  Remote: unix:/var/lib/lxd/unix.socket
  Architecture: x86_64
  Created: 2017/04/25 07:17 UTC
  Status: Running
  Type: persistent
  Profiles: default
  Pid: 6965
  Ips:
lo:   inet127.0.0.1
lo:   inet6   ::1
  Resources:
Processes: 7
Disk usage:
  root: 1.48MB
CPU usage:
  CPU usage (in seconds): 25
Memory usage:
  Memory (current): 16.22MB
  Memory (peak): 23.01MB
Network usage:
  lo:
Bytes received: 0B
Bytes sent: 0B
Packets received: 0
Packets sent: 0

  # lxc profile show default
  config: {}
  description: Default LXD profile
  devices:
root:
  path: /
  pool: main-pool
  type: disk
  name: default
  used_by:
  - /1.0/containers/popular-kitten
  # lxc snapshot popular-kitten

  # zfs get mounted main-pool/containers/popular-kitten 
  NAME PROPERTY  VALUESOURCE
  main-pool/containers/popular-kitten  mounted   yes  -

  # zfs get mounted main-pool/snapshots/popular-kitten 
  NAMEPROPERTY  VALUESOURCE
  main-pool/snapshots/popular-kitten  mounted   yes  -

  # lxc restore popular-kitten snap0

  # zfs get mounted main-pool/snapshots/popular-kitten
  NAMEPROPERTY  VALUESOURCE
  main-pool/snapshots/popular-kitten  mounted   yes  -

  # zfs get mounted main-pool/containers/popular-kitten
  NAME PROPERTY  VALUESOURCE
  main-pool/containers/popular-kitten  mounted   no   -

  # lxc snapshot popular-kitten 
  error: Failed to mount ZFS filesystem: filesystem 
'main-pool/containers/popular-kitten' is already mounted
  cannot mount 'main-pool/containers/popular-kitten': mountpoint or dataset is 
busy

  # lxc restore popular-kitten snap0
  error: Failed to mount ZFS filesystem: filesystem 
'main-pool/containers/popular-kitten' is already mounted
  cannot mount 'main-pool/containers/popular-kitten': mountpoint or dataset is 
busy

  but container still work:

  # lxc info popular-kitten
  Name: popular-kitten
  Remote: unix:/var/lib/lxd/unix.socket
  Architecture: x86_64
  Created: 2017/04/25 07:17 UTC
  Status: Running
  ...

  # lxc exec popular-kitten bash
  root@popular-kitten:~# uptime
   07:34:06 up 8 min,  0 users,  load average: 0.00, 0.02, 0.03

  after restart container:

  # lxc restart popular-kitten

  # zfs get mounted main-pool/containers/popular-kitten
  NAME PROPERTY  VALUESOURCE
  main-pool/containers/popular-kitten  mounted   yes  -

  
  on another server this problem missmatch:

  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.10
  Release:16.10
  Codename:   yakkety

  # lxd --version
  2.4.1

  zfsutils-linux: 0.6.5.8-0ubuntu4.1

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

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

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

2017-04-25 Thread Brian Murray
In Brian Kelley's report we can see the following in main.log:

4 2017-04-14 13:27:43,632 INFO python version: '3.5.2+ (default, Sep 22
2016, 12:18:14)
5 [GCC 6.2.0 20160927]'

This matches the output of sys.version on my yakkety system:

 $ python3
Python 3.5.2+ (default, Sep 22 2016, 12:18:14)
[GCC 6.2.0 20160927] on linux

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

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

Status in python3-defaults package in Ubuntu:
  Confirmed

Bug description:
  Got this error while using "Transmageddon Video Transcoder" and again
  while updating 16.10 to 17.04.

  Seems to have something to do with needing that Python3 version for
  Teletext decoding in media that is in transport stream format (.ts).

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3 3.5.1-4
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Fri Apr 14 19:27:33 2017
  ErrorMessage: pre-dependency problem - not installing python3
  InstallationDate: Installed on 2015-05-01 (714 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency 
problem - not installing python3
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago)

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

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


[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in basefiles for ubuntu

2017-04-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: base-files (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ship ubuntu-advantage in basefiles for ubuntu

Status in base-files package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * Allow ubuntu-advantage users to access the extended security
  maintenance script with a simple command line tool.  This script needs
  to hit precise machines and be easy for ubuntu-advantage customers to
  enable, thus basefiles was chosen as a home.

  [Test Case]

   * Run ubuntu-advantage, it should print out help
   * Run sudo ubuntu-advantage enable  (without sudo it will warn you), 
but you need to be an ubuntu-advantage customer to get that token.  In the end, 
the script simply adds and removes an /etc/apt/sources.list.d entry.
   * you can contact me (d...@canonical.com) if you would like a token for test 
purposes.

  [Regression Potential]

   * Low, this is a new script, not included in any automated startup
  paths.

  [Other Info]

   * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1686183/+subscriptions

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


[Touch-packages] [Bug 1672710] Re: apt fails to verify keys when Dir has space, and set via cmdline

2017-04-25 Thread Julian Andres Klode
** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: apt (Ubuntu Xenial)
   Importance: Undecided => Low

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

Title:
  apt fails to verify keys when Dir has space, and set via cmdline

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged
Status in apt source package in Yakkety:
  Triaged

Bug description:
  When Dir has a space, and it is set via APT_CONFIG file, keys are found and 
validated correctly.
  When Dir is set without a space via cmdline, keys are found and validated 
correctly.
  When Dir is set with a space via cmdline, keys are not found and repositories 
are not verified.

  [Test case]
  Please see attached reproducer, which works on xenial system (gpg1) but not 
on zesty system (gpg2)

  $ bash reproducer.sh
  ++ mktemp -d
  + tmpdir=/tmp/tmp.sFipy6h5yL
  + pushd /tmp/tmp.sFipy6h5yL
  /tmp/tmp.sFipy6h5yL ~
  + mkdir 'Sub Dir'
  + pushd 'Sub Dir'
  /tmp/tmp.sFipy6h5yL/Sub Dir /tmp/tmp.sFipy6h5yL ~
  + mkdir -p etc/apt/apt.conf.d
  + mkdir -p etc/apt/trusted.gpg.d
  + mkdir -p etc/apt/preferences.d
  + mkdir -p var/lib/apt/lists/partial
  + mkdir -p var/lib/dpkg
  + touch var/lib/dpkg/status
  + cp /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg 
etc/apt/trusted.gpg.d/
  + echo 'deb http://archive.ubuntu.com/ubuntu/ trusty main'
  + echo 'Dir "/tmp/tmp.sFipy6h5yL/Sub Dir";'
  + export APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf
  + APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf
  + cat /tmp/tmp.sFipy6h5yL/apt.conf
  Dir "/tmp/tmp.sFipy6h5yL/Sub Dir";
  + :
  + : == list available keys ==
  + apt-key list
  /tmp/tmp.sFipy6h5yL/Sub 
Dir/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg
  
-
  pub   rsa4096 2012-05-11 [SC]
    790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2012) 


  + :
  + : == update with environ APT_CONFIG setting the Dir variable ==
  + apt update
  Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease
  Get:2 http://archive.ubuntu.com/ubuntu trusty Release [58.5 kB]
  Get:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg [933 B]
  Get:4 http://archive.ubuntu.com/ubuntu trusty/main amd64 Packages [1,350 kB]
  Fetched 1,410 kB in 0s (1,959 kB/s)
  Reading package lists... Done
  Building dependency tree... Done
  All packages are up to date.
  + unset APT_CONFIG
  + :
  + : == update with cmdline Dir option setting Dir to relative pwd ==
  + apt -o Dir=./ update
  Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu trusty Release
  Reading package lists... Done
  Building dependency tree... Done
  All packages are up to date.
  + :
  + : == update with cmdline Dir option setting Dir to absolute pwd with space 
==
  + apt -o 'Dir=/tmp/tmp.sFipy6h5yL/Sub Dir' update
  Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu trusty Release
  Err:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg
    The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  Reading package lists... Done
  Building dependency tree... Done
  All packages are up to date.
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://archive.ubuntu.com/ubuntu trusty Release: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/Release.gpg  
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  
  [Regression Potential]
  The fix changes the code to generate quotes in the Commmandline:AsString 
option, which dumps the command line for logging purposes. This was not 
parseable before, causing the file to be rejected, so what can happen is that 
something now works that did not before.

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

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


[Touch-packages] [Bug 1686036] Re: strange behavior after restore snapshot

2017-04-25 Thread Christian Brauner
This is very likely not a LXD bug. I suspect this is
https://github.com/zfsonlinux/zfs/issues/5796 again which I reported to
ZFS upstream. I'll ping them about this again tomorrow and if I don't
hear back will take a look at this myself.

** Bug watch added: Github Issue Tracker for ZFS #5796
   https://github.com/zfsonlinux/zfs/issues/5796

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

Title:
  strange behavior after restore snapshot

Status in lxc package in Ubuntu:
  New

Bug description:
  uname -a
  Linux lxd2-chel1 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  lxd: 2.12-0ubuntu3~ubuntu16.04.1~ppa1
  zfsutils-linux: 0.6.5.6-0ubuntu16

  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  after restore container from shapshot cannot add new snapshot or restore again
  until restart container

  example:

  
  # lxc image list
  
+---+--++--++-+--+
  | ALIAS | FINGERPRINT  | PUBLIC | DESCRIPTION 
 |  ARCH  |  SIZE   | UPLOAD DATE  |
  
+---+--++--++-+--+
  | debian/jessie | ba43812c4cb9 | no | Debian jessie amd64 
(20170423_22:42) | x86_64 | 94.14MB | Apr 24, 2017 at 9:07am (UTC) |
  
+---+--++--++-+--+

  # lxc launch debian/jessie
  Creating popular-kitten

  The container you are starting doesn't have any network attached to it.
To create a new network, use: lxc network create
To attach a network to a container, use: lxc network attach

  Starting popular-kitten

  
  # lxc info popular-kitten
  Name: popular-kitten
  Remote: unix:/var/lib/lxd/unix.socket
  Architecture: x86_64
  Created: 2017/04/25 07:17 UTC
  Status: Running
  Type: persistent
  Profiles: default
  Pid: 6965
  Ips:
lo:   inet127.0.0.1
lo:   inet6   ::1
  Resources:
Processes: 7
Disk usage:
  root: 1.48MB
CPU usage:
  CPU usage (in seconds): 25
Memory usage:
  Memory (current): 16.22MB
  Memory (peak): 23.01MB
Network usage:
  lo:
Bytes received: 0B
Bytes sent: 0B
Packets received: 0
Packets sent: 0

  # lxc profile show default
  config: {}
  description: Default LXD profile
  devices:
root:
  path: /
  pool: main-pool
  type: disk
  name: default
  used_by:
  - /1.0/containers/popular-kitten
  # lxc snapshot popular-kitten

  # zfs get mounted main-pool/containers/popular-kitten 
  NAME PROPERTY  VALUESOURCE
  main-pool/containers/popular-kitten  mounted   yes  -

  # zfs get mounted main-pool/snapshots/popular-kitten 
  NAMEPROPERTY  VALUESOURCE
  main-pool/snapshots/popular-kitten  mounted   yes  -

  # lxc restore popular-kitten snap0

  # zfs get mounted main-pool/snapshots/popular-kitten
  NAMEPROPERTY  VALUESOURCE
  main-pool/snapshots/popular-kitten  mounted   yes  -

  # zfs get mounted main-pool/containers/popular-kitten
  NAME PROPERTY  VALUESOURCE
  main-pool/containers/popular-kitten  mounted   no   -

  # lxc snapshot popular-kitten 
  error: Failed to mount ZFS filesystem: filesystem 
'main-pool/containers/popular-kitten' is already mounted
  cannot mount 'main-pool/containers/popular-kitten': mountpoint or dataset is 
busy

  # lxc restore popular-kitten snap0
  error: Failed to mount ZFS filesystem: filesystem 
'main-pool/containers/popular-kitten' is already mounted
  cannot mount 'main-pool/containers/popular-kitten': mountpoint or dataset is 
busy

  but container still work:

  # lxc info popular-kitten
  Name: popular-kitten
  Remote: unix:/var/lib/lxd/unix.socket
  Architecture: x86_64
  Created: 2017/04/25 07:17 UTC
  Status: Running
  ...

  # lxc exec popular-kitten bash
  root@popular-kitten:~# uptime
   07:34:06 up 8 min,  0 users,  load average: 0.00, 0.02, 0.03

  after restart container:

  # lxc restart popular-kitten

  # zfs get mounted main-pool/containers/popular-kitten
  NAME PROPERTY  VALUESOURCE
  main-pool/containers/popular-kitten  mounted   yes  -

  
  on another server this problem missmatch:

  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.10
  Release:16.10
  Codename:   yakkety

  # lxd --version
  2.4.1

  zfsutils-linux: 0.6.5.8-0ubuntu4.1

To 

[Touch-packages] [Bug 1686057] Re: Sync libdrm 2.4.80-1 (main) from Debian experimental (main)

2017-04-25 Thread Mathew Hodson
** Changed in: libdrm (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync libdrm 2.4.80-1 (main) from Debian experimental (main)

Status in libdrm package in Ubuntu:
  New

Bug description:
  Please sync libdrm 2.4.80-1 (main) from Debian experimental (main)

  Changelog entries since current artful version 2.4.76-1:

  libdrm (2.4.80-1) experimental; urgency=medium

* New upstream release.
* Bump libdrm-amdgpu1's and libdrm-etnaviv1's symbols and shlibs.
* Remove libpthread-stubs0-dev build-dep per configure.ac.

   -- Andreas Boll   Wed, 19 Apr 2017
  15:35:21 +0200

  libdrm (2.4.77-1) experimental; urgency=medium

* Team upload.
* New upstream release.
* Bump libdrm-amdgpu1 symbols.
* Update debian/upstream/signing-key.asc

   -- Jordan Justen   Wed, 05 Apr 2017
  02:30:35 -0700

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

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


[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

2017-04-25 Thread Alroger Filho
Same problem here. Editing resolv.conf or #8 post solves it.

I almost lost a RAID today because postfix was not able to send mdadm 
notifications - 
delivery temporarily suspended: Host or domain name not found. Name service 
error for name=smtp.gmail.com type=MX: Host not found

I use /etc/network/interfaces, nothing in networkmanager.
This is serious. Ubuntu shouldn't just start changing things like this, 
specially if it breaks a server.

Using a clean 17.04 install here.

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

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  systemd-resolved, or more precisely the hook script
  /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
  resolvconf to add 127.0.0.53 to the set of nameservers in
  /etc/resolv.conf alongside the other nameservers.  That makes no sense
  because systemd-resolved sets up 127.0.0.53 as a proxy for those other
  nameservers.  The effect is similar to bug 1624071 but for
  applications doing their own DNS lookups.  It breaks any DNSSEC
  validation that systemd-resolved tries to do; applications will
  failover to the other nameservers, bypassing validation failures.  And
  it makes failing queries take twice as long.

  /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
  active.

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

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


[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-04-25 Thread Tamas Papp
Actually it's happening continuously, it does not even require a wakup,
of wifi reconnection or anything...


It's a complete useless peace of crap.

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

Title:
  systemd-resolved using 100% CPU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  dmi.chassis.asset.tag: CNU51199KV
  dmi.chassis.type: 10
  

[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseded by systemd

2017-04-25 Thread Serge Hallyn
@bryanquigley that's an odd non-sequitur.  I'm avoiding switching to
systemd (in part for power usage), and cgroupfs-mount is not the thing
being removed.

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

Title:
  RM Upstart, obsolete, superseded by systemd

Status in cgmanager package in Ubuntu:
  Triaged
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in ubuntu-touch-meta package in Ubuntu:
  Triaged
Status in ubuntu-touch-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session package in Ubuntu:
  Triaged
Status in upstart package in Ubuntu:
  Triaged
Status in upstart-watchdog package in Ubuntu:
  Triaged

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

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

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


[Touch-packages] [Bug 1686211] [NEW] package libpython2.7 2.7.11-7ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/libpython2.7.so.1.0' to '/usr/lib/i386-lin

2017-04-25 Thread Alfredo Bateman
Public bug reported:

i dont know details thinked was automatic

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpython2.7 2.7.11-7ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic i686
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
Date: Tue Apr 25 15:47:34 2017
ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libpython2.7.so.1.0' to 
'/usr/lib/i386-linux-gnu/libpython2.7.so.1.0.dpkg-new': unexpected end of file 
or stream
InstallationDate: Installed on 2017-04-23 (2 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: python2.7
Title: package libpython2.7 2.7.11-7ubuntu1 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libpython2.7.so.1.0' to 
'/usr/lib/i386-linux-gnu/libpython2.7.so.1.0.dpkg-new': unexpected end of file 
or stream
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package libpython2.7 2.7.11-7ubuntu1 failed to install/upgrade: cannot
  copy extracted data for './usr/lib/i386-linux-gnu/libpython2.7.so.1.0'
  to '/usr/lib/i386-linux-gnu/libpython2.7.so.1.0.dpkg-new': unexpected
  end of file or stream

Status in python2.7 package in Ubuntu:
  New

Bug description:
  i dont know details thinked was automatic

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpython2.7 2.7.11-7ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  Date: Tue Apr 25 15:47:34 2017
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libpython2.7.so.1.0' to 
'/usr/lib/i386-linux-gnu/libpython2.7.so.1.0.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2017-04-23 (2 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: python2.7
  Title: package libpython2.7 2.7.11-7ubuntu1 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libpython2.7.so.1.0' to 
'/usr/lib/i386-linux-gnu/libpython2.7.so.1.0.dpkg-new': unexpected end of file 
or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1644363] Re: [trusty/arm64] binutils segfaults on bash gettext configure test

2017-04-25 Thread Adam Conrad
A note to whoever releases this: it was built in the security-proposed
PPA so it can be released to both updates *and* security, to fix a
regression in the security pocket.

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

Title:
  [trusty/arm64] binutils segfaults on bash gettext configure test

Status in binutils package in Ubuntu:
  Invalid
Status in eglibc package in Ubuntu:
  Invalid
Status in binutils source package in Trusty:
  Fix Committed
Status in eglibc source package in Trusty:
  Invalid

Bug description:
  On arm64, the bash gettext configure test causes binutils to segv:

  configure:8453: gcc -o conftest -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=
  format-security -Wall -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -static conftest.c
  >&5
  conftest.c: In function 'main':
  conftest.c:116:8: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
  ^
  conftest.c:116:29: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
   ^
  collect2: error: ld terminated with signal 11 [Segmentation fault], core 
dumped
  configure:8453: $? = 1
  configure: failed program was:
  | /* confdefs.h */
  | #define PACKAGE_NAME "bash"
  | #define PACKAGE_TARNAME "bash"
  | #define PACKAGE_VERSION "4.3-release"
  | #define PACKAGE_STRING "bash 4.3-release"
  | #define PACKAGE_BUGREPORT "bug-b...@gnu.org"
  | #define PACKAGE_URL ""
  | #define ALIAS 1
  | #define PUSHD_AND_POPD 1
  | #define RESTRICTED_SHELL 1
  | #define PROCESS_SUBSTITUTION 1
  | #define PROMPT_STRING_DECODE 1
  | #define SELECT_COMMAND 1
  | #define HELP_BUILTIN 1
  | #define ARRAY_VARS 1
  | #define DPAREN_ARITHMETIC 1
  | #define BRACE_EXPANSION 1
  | #define COMMAND_TIMING 1
  | #define EXTENDED_GLOB 1
  | #define EXTGLOB_DEFAULT 0
  | #define COND_COMMAND 1
  | #define COND_REGEXP 1
  | #define COPROCESS_SUPPORT 1
  | #define ARITH_FOR_COMMAND 1
  | #define NETWORK_REDIRECTIONS 1
  | #define PROGRAMMABLE_COMPLETION 1
  | #define DEBUGGER 1
  | #define CASEMOD_ATTRS 1
  | #define CASEMOD_EXPANSIONS 1
  | #define GLOBASCII_DEFAULT 0
  | #define MEMSCRAMBLE 1
  | #define STDC_HEADERS 1
  | #define HAVE_SYS_TYPES_H 1
  | #define HAVE_SYS_STAT_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_MEMORY_H 1
  | #define HAVE_STRINGS_H 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_STDINT_H 1
  | #define HAVE_UNISTD_H 1
  | #define __EXTENSIONS__ 1
  | #define _ALL_SOURCE 1
  | #define _GNU_SOURCE 1
  | #define _POSIX_PTHREAD_SEMANTICS 1
  | #define _TANDEM_SOURCE 1
  | #define READLINE 1
  | #define HISTORY 1
  | #define BANG_HISTORY 1
  | #define _GNU_SOURCE 1
  | #define HAVE_STRINGIZE 1
  | #define HAVE_LONG_DOUBLE_WIDER 1
  | #define HAVE_LONG_DOUBLE 1
  | #define PROTOTYPES 1
  | #define __PROTOTYPES 1
  | #define restrict __restrict
  | #define HAVE_ALLOCA_H 1
  | #define HAVE_ALLOCA 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_SYS_PARAM_H 1
  | #define HAVE_SYS_TIME_H 1
  | #define HAVE_GETPAGESIZE 1
  | #define HAVE_MMAP 1
  | #define INTDIV0_RAISES_SIGFPE 0
  | #define HAVE_INTTYPES_H_WITH_UINTMAX 1
  | #define HAVE_STDINT_H_WITH_UINTMAX 1
  | #define HAVE_UNSIGNED_LONG_LONG 1
  | #define HAVE_UINTMAX_T 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_ARGZ_H 1
  | #define HAVE_LIMITS_H 1
  | #define HAVE_LOCALE_H 1
  | #define HAVE_NL_TYPES_H 1
  | #define HAVE_MALLOC_H 1
  | #define HAVE_STDDEF_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_SYS_PARAM_H 1
  | #define HAVE_FEOF_UNLOCKED 1
  | #define HAVE_FGETS_UNLOCKED 1
  | #define HAVE_GETC_UNLOCKED 1
  | #define HAVE_GETCWD 1
  | #define HAVE_GETEGID 1
  | #define HAVE_GETEUID 1
  | #define HAVE_GETGID 1
  | #define HAVE_GETUID 1
  | #define HAVE_MEMPCPY 1
  | #define HAVE_MUNMAP 1
  | #define HAVE_PUTENV 1
  | #define HAVE_SETENV 1
  | #define HAVE_SETLOCALE 1
  | #define HAVE_LOCALECONV 1
  | #define HAVE_STPCPY 1
  | #define HAVE_STRCASECMP 1
  | #define HAVE_STRDUP 1
  | #define HAVE_STRTOUL 1
  | #define HAVE_TSEARCH 1
  | #define HAVE___ARGZ_COUNT 1
  | #define HAVE___ARGZ_STRINGIFY 1
  | #define HAVE___ARGZ_NEXT 1
  | #define HAVE___FSETLOCKING 1
  | #define HAVE_ICONV 1
  | #define ICONV_CONST
  | #define HAVE_LANGINFO_CODESET 1
  | #define HAVE_LC_MESSAGES 1
  | /* end confdefs.h.  */
  | #include 
  | extern int _nl_msg_cat_cntr;
  | extern int *_nl_domain_bindings;
  | int
  | main ()
  | {
  | bindtextdomain ("", "");
  | return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 

[Touch-packages] [Bug 1644363] Re: [trusty/arm64] binutils segfaults on bash gettext configure test

2017-04-25 Thread Adam Conrad
Hello Adam, or anyone else affected,

Accepted binutils into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/binutils/2.24-5ubuntu14.2 in a few
hours, and then in the -proposed repository.

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

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

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

** Tags added: verification-needed

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

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

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

Title:
  [trusty/arm64] binutils segfaults on bash gettext configure test

Status in binutils package in Ubuntu:
  Invalid
Status in eglibc package in Ubuntu:
  Invalid
Status in binutils source package in Trusty:
  Fix Committed
Status in eglibc source package in Trusty:
  Invalid

Bug description:
  On arm64, the bash gettext configure test causes binutils to segv:

  configure:8453: gcc -o conftest -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=
  format-security -Wall -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -static conftest.c
  >&5
  conftest.c: In function 'main':
  conftest.c:116:8: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
  ^
  conftest.c:116:29: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
   ^
  collect2: error: ld terminated with signal 11 [Segmentation fault], core 
dumped
  configure:8453: $? = 1
  configure: failed program was:
  | /* confdefs.h */
  | #define PACKAGE_NAME "bash"
  | #define PACKAGE_TARNAME "bash"
  | #define PACKAGE_VERSION "4.3-release"
  | #define PACKAGE_STRING "bash 4.3-release"
  | #define PACKAGE_BUGREPORT "bug-b...@gnu.org"
  | #define PACKAGE_URL ""
  | #define ALIAS 1
  | #define PUSHD_AND_POPD 1
  | #define RESTRICTED_SHELL 1
  | #define PROCESS_SUBSTITUTION 1
  | #define PROMPT_STRING_DECODE 1
  | #define SELECT_COMMAND 1
  | #define HELP_BUILTIN 1
  | #define ARRAY_VARS 1
  | #define DPAREN_ARITHMETIC 1
  | #define BRACE_EXPANSION 1
  | #define COMMAND_TIMING 1
  | #define EXTENDED_GLOB 1
  | #define EXTGLOB_DEFAULT 0
  | #define COND_COMMAND 1
  | #define COND_REGEXP 1
  | #define COPROCESS_SUPPORT 1
  | #define ARITH_FOR_COMMAND 1
  | #define NETWORK_REDIRECTIONS 1
  | #define PROGRAMMABLE_COMPLETION 1
  | #define DEBUGGER 1
  | #define CASEMOD_ATTRS 1
  | #define CASEMOD_EXPANSIONS 1
  | #define GLOBASCII_DEFAULT 0
  | #define MEMSCRAMBLE 1
  | #define STDC_HEADERS 1
  | #define HAVE_SYS_TYPES_H 1
  | #define HAVE_SYS_STAT_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_MEMORY_H 1
  | #define HAVE_STRINGS_H 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_STDINT_H 1
  | #define HAVE_UNISTD_H 1
  | #define __EXTENSIONS__ 1
  | #define _ALL_SOURCE 1
  | #define _GNU_SOURCE 1
  | #define _POSIX_PTHREAD_SEMANTICS 1
  | #define _TANDEM_SOURCE 1
  | #define READLINE 1
  | #define HISTORY 1
  | #define BANG_HISTORY 1
  | #define _GNU_SOURCE 1
  | #define HAVE_STRINGIZE 1
  | #define HAVE_LONG_DOUBLE_WIDER 1
  | #define HAVE_LONG_DOUBLE 1
  | #define PROTOTYPES 1
  | #define __PROTOTYPES 1
  | #define restrict __restrict
  | #define HAVE_ALLOCA_H 1
  | #define HAVE_ALLOCA 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_SYS_PARAM_H 1
  | #define HAVE_SYS_TIME_H 1
  | #define HAVE_GETPAGESIZE 1
  | #define HAVE_MMAP 1
  | #define INTDIV0_RAISES_SIGFPE 0
  | #define HAVE_INTTYPES_H_WITH_UINTMAX 1
  | #define HAVE_STDINT_H_WITH_UINTMAX 1
  | #define HAVE_UNSIGNED_LONG_LONG 1
  | #define HAVE_UINTMAX_T 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_ARGZ_H 1
  | #define HAVE_LIMITS_H 1
  | #define HAVE_LOCALE_H 1
  | #define HAVE_NL_TYPES_H 1
  | #define HAVE_MALLOC_H 1
  | #define HAVE_STDDEF_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_SYS_PARAM_H 1
  | #define HAVE_FEOF_UNLOCKED 1
  

[Touch-packages] [Bug 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1

2017-04-25 Thread Dimitri John Ledkov
dnsutils with bind9-host should be sufficient on regular systems to have
network up.

** Tags removed: block-proposed

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

Title:
  On artful, no working dns after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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


[Touch-packages] [Bug 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1

2017-04-25 Thread Dimitri John Ledkov
How does that service changed between these versions?

$ git diff v232..v233 src/resolve/ | diffstat
36 files changed, 950 insertions(+), 284 deletions(-)

And that's just resolved specific code, but there are a lot more changes
in shared code.

You have not provided any system logs, error messages from the daemon,
or steps to reproduce the problem.

If you are not going to share systemd-journal logs of the failing
systemd-resolved.service there is nothing I can do to fix the problem
you have encountered.

Are you sure you are using systemd-resolved now? Is the service running
and does resolv.conf point at it?

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

Title:
  On artful, no working dns after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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


[Touch-packages] [Bug 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1

2017-04-25 Thread Harry
OK,

So I got this issue fixed by installing the package bind9.
I tested several times, but dnsutils with bind9-host was not enough.
So I removed those two and installed bind9 instead.
Now I have a working dns.

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

Title:
  On artful, no working dns after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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


[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseded by systemd

2017-04-25 Thread Bryan Quigley
@serge-hallyn
>From what I can tell from https://github.com/tianon/cgroupfs-mount, this isn't 
>needed after you go to systemd.  Am I missing something?


Assuming their isn't a missing use case, I'm +1 on this removal. (and I note 
you already bumped them off the livecd/main)

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

Title:
  RM Upstart, obsolete, superseded by systemd

Status in cgmanager package in Ubuntu:
  Triaged
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in ubuntu-touch-meta package in Ubuntu:
  Triaged
Status in ubuntu-touch-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session package in Ubuntu:
  Triaged
Status in upstart package in Ubuntu:
  Triaged
Status in upstart-watchdog package in Ubuntu:
  Triaged

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

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

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


[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in basefiles for ubuntu

2017-04-25 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  Ship ubuntu-advantage in basefiles for ubuntu

Status in base-files package in Ubuntu:
  New

Bug description:
  [Impact]

   * Allow ubuntu-advantage users to access the extended security
  maintenance script with a simple command line tool.  This script needs
  to hit precise machines and be easy for ubuntu-advantage customers to
  enable, thus basefiles was chosen as a home.

  [Test Case]

   * Run ubuntu-advantage, it should print out help
   * Run sudo ubuntu-advantage enable  (without sudo it will warn you), 
but you need to be an ubuntu-advantage customer to get that token.  In the end, 
the script simply adds and removes an /etc/apt/sources.list.d entry.
   * you can contact me (d...@canonical.com) if you would like a token for test 
purposes.

  [Regression Potential]

   * Low, this is a new script, not included in any automated startup
  paths.

  [Other Info]

   * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1686183/+subscriptions

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


[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in basefiles for ubuntu

2017-04-25 Thread Andreas Hasenack
debdiff for base-files on precise

** Patch added: "lp1686183.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1686183/+attachment/4867936/+files/lp1686183.debdiff

** Description changed:

  [Impact]
  
-  * Allow ubuntu-advantage users to access the extended security
+  * Allow ubuntu-advantage users to access the extended security
  maintenance script with a simple command line tool.  This script needs
  to hit precise machines and be easy for ubuntu-advantage customers to
  enable, thus basefiles was chosen as a home.
  
  [Test Case]
  
-  * Run ubuntu-advantage, it should print out help
-  * Run ubuntu-advantage enable , but you need to be an 
ubuntu-advantage customer to get that token.  In the end, the script simply 
adds and removes an /etc/apt/sources.list.d entry.
-  * you can contact me (d...@canonical.com) if you would like a token for test 
purposes.
+  * Run ubuntu-advantage, it should print out help
+  * Run sudo ubuntu-advantage enable  (without sudo it will warn you), 
but you need to be an ubuntu-advantage customer to get that token.  In the end, 
the script simply adds and removes an /etc/apt/sources.list.d entry.
+  * you can contact me (d...@canonical.com) if you would like a token for test 
purposes.
  
  [Regression Potential]
  
-  * Low, this is a new script, not included in any automated startup
+  * Low, this is a new script, not included in any automated startup
  paths.
  
  [Other Info]
-  
-  * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html
+ 
+  * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

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

Title:
  Ship ubuntu-advantage in basefiles for ubuntu

Status in base-files package in Ubuntu:
  New

Bug description:
  [Impact]

   * Allow ubuntu-advantage users to access the extended security
  maintenance script with a simple command line tool.  This script needs
  to hit precise machines and be easy for ubuntu-advantage customers to
  enable, thus basefiles was chosen as a home.

  [Test Case]

   * Run ubuntu-advantage, it should print out help
   * Run sudo ubuntu-advantage enable  (without sudo it will warn you), 
but you need to be an ubuntu-advantage customer to get that token.  In the end, 
the script simply adds and removes an /etc/apt/sources.list.d entry.
   * you can contact me (d...@canonical.com) if you would like a token for test 
purposes.

  [Regression Potential]

   * Low, this is a new script, not included in any automated startup
  paths.

  [Other Info]

   * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1686183/+subscriptions

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


[Touch-packages] [Bug 1686192] [NEW] DHCP Relay not sending DHCP OFFER packets

2017-04-25 Thread J. Kary
Public bug reported:

In Ubuntu Server 17-04. DNSMASQ version 2.76-5

DHCP Relay option for DNSMASQ appears to be broken.  The syslog states
the file is allocating an IP address but TCPDUMP shows no DHCP OFFER is
ever sent out on the receiving interface.

Configuration is included with the bug report.  This problem seems to
occur in centOS as well.

Looking at an strace it appears to be calling sendmsg however no
outgoing DHCP packet is seen on the wire via TCPDUMP.

jkary@DHCP-UBUNTU-SERVER:~$ sudo su -
[sudo] password for jkary:
root@DHCP-UBUNTU-SERVER:~# tcpdump -i ens160 port 67 or port 68 -n
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ens160, link-type EN10MB (Ethernet), capture size 262144 bytes
08:02:12.056671 IP 10.168.102.1.67 > 10.168.101.20.67: BOOTP/DHCP, Request from 
00:0c:29:b5:9b:0e, length 322
08:02:16.420010 IP 10.168.102.1.67 > 10.168.101.20.67: BOOTP/DHCP, Request from 
00:0c:29:65:e0:ea, length 322
08:02:21.522334 IP 10.168.102.1.67 > 10.168.101.20.67: BOOTP/DHCP, Request from 
00:0c:29:65:e0:ea, length 322
^C
3 packets captured
3 packets received by filter
0 packets dropped by kernel
root@DHCP-UBUNTU-SERVER:~# tail -50 /var/log/syslog
Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size:  4 
option: 28 broadcast  10.168.102.255
Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size:  4 
option:  3 router  10.168.102.1
Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size:  4 
option:  6 dns-server  10.168.101.20
Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 20 
option: 82 agent-id  01:0a:01:08:00:06:00:4c:4f:2a:00:2f:02:06...
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 available 
DHCP range: 10.168.102.100 -- 10.168.102.150
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 
DHCPDISCOVER(ens160) 00:0c:29:65:e0:ea
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 tags: ens160
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 
DHCPOFFER(ens160) 10.168.102.128 00:0c:29:65:e0:ea
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested 
options: 1:netmask, 28:broadcast, 2:time-offset, 121:classless-static-route,
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested 
options: 15:domain-name, 6:dns-server, 12:hostname,
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested 
options: 40:nis-domain, 41:nis-server, 42:ntp-server,
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested 
options: 26:mtu, 119:domain-search, 3:router, 121:classless-static-route,
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested 
options: 249, 33:static-route, 252, 42:ntp-server
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 next server: 
10.168.101.20
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size:  1 
option: 53 message-type  2
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size:  4 
option: 54 server-identifier  10.168.101.20
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size:  4 
option: 51 lease-time  12h
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size:  4 
option: 58 T1  6h
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size:  4 
option: 59 T2  10h30m
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size:  4 
option:  1 netmask  255.255.255.0
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size:  4 
option: 28 broadcast  10.168.102.255
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size:  4 
option:  3 router  10.168.102.1
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size:  4 
option:  6 dns-server  10.168.101.20
Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 20 
option: 82 agent-id  01:0a:01:08:00:06:00:4c:4f:2a:00:2f:02:06...
Apr 25 08:02:29 DHCP-UBUNTU-SERVER kernel: [ 2251.45] device ens160 left 
promiscuous mode
Apr 25 08:02:29 DHCP-UBUNTU-SERVER systemd-timesyncd[647]: Timed out waiting 
for reply from 91.189.91.157:123 (ntp.ubuntu.com).
Apr 25 08:02:35 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 available 
DHCP range: 10.168.102.100 -- 10.168.102.150
Apr 25 08:02:35 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 
DHCPDISCOVER(ens160) 00:0c:29:65:e0:ea
Apr 25 08:02:35 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 tags: ens160
Apr 25 08:02:35 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 
DHCPOFFER(ens160) 10.168.102.128 00:0c:29:65:e0:ea
Apr 25 08:02:35 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested 
options: 1:netmask, 28:broadcast, 2:time-offset, 121:classless-static-route,
Apr 25 08:02:35 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested 
options: 15:domain-name, 6:dns-server, 

[Touch-packages] [Bug 1686183] [NEW] Ship ubuntu-advantage in basefiles for ubuntu

2017-04-25 Thread David Britton
Public bug reported:

[Impact]

 * Allow ubuntu-advantage users to access the extended security
maintenance script with a simple command line tool.  This script needs
to hit precise machines and be easy for ubuntu-advantage customers to
enable, thus basefiles was chosen as a home.

[Test Case]

 * Run ubuntu-advantage, it should print out help
 * Run ubuntu-advantage enable , but you need to be an ubuntu-advantage 
customer to get that token.  In the end, the script simply adds and removes an 
/etc/apt/sources.list.d entry.
 * you can contact me (d...@canonical.com) if you would like a token for test 
purposes.

[Regression Potential]

 * Low, this is a new script, not included in any automated startup
paths.

[Other Info]
 
 * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Ship ubuntu-advantage in basefiles for ubuntu

Status in base-files package in Ubuntu:
  New

Bug description:
  [Impact]

   * Allow ubuntu-advantage users to access the extended security
  maintenance script with a simple command line tool.  This script needs
  to hit precise machines and be easy for ubuntu-advantage customers to
  enable, thus basefiles was chosen as a home.

  [Test Case]

   * Run ubuntu-advantage, it should print out help
   * Run ubuntu-advantage enable , but you need to be an 
ubuntu-advantage customer to get that token.  In the end, the script simply 
adds and removes an /etc/apt/sources.list.d entry.
   * you can contact me (d...@canonical.com) if you would like a token for test 
purposes.

  [Regression Potential]

   * Low, this is a new script, not included in any automated startup
  paths.

  [Other Info]
   
   * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1686183/+subscriptions

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


[Touch-packages] [Bug 821799] Re: The music from an mp3 file still plays if the mouse pointer is moved away

2017-04-25 Thread Sebastian Ramacher
This seems to be a bug in whatever file manager you are using, but not
in mpg123.

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

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

Title:
  The music from an mp3 file still plays if the mouse pointer is moved
  away

Status in mpg123 package in Ubuntu:
  Invalid

Bug description:
  when mouse-over a particular mp3 file the correct mp3 file plays. 
  If the mouse is moved away from the mp3 file using the mouse pointer, then 
the music stops playing (as required). 
  But when the pointer is moved away from the mp3 file by scrolling up/down the 
folder containing the mp3 file using the arrow keys (rather than using the 
mouse itself), the mp3 file still plays eventhough the pointer doesn't point to 
the file anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: mpg123 1.12.1-3ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Sat Aug  6 10:11:09 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   LC_MESSAGES=en_IN.UTF-8
   SHELL=/bin/bash
  SourcePackage: mpg123
  UpgradeStatus: Upgraded to natty on 2011-06-13 (54 days ago)

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

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


[Touch-packages] [Bug 1619407] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

2017-04-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 127

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I don'y know which details?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Aug 29 16:45:32 2016
  DuplicateSignature:
   package:gconf2:3.2.6-3ubuntu6
   Removing python3-apport (2.20.1-0ubuntu2) ...
   dpkg: error processing package python3-problem-report (--remove):
package is in a very bad inconsistent state; you should
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2016-08-23 (9 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: subprocess 
installed post-installation 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/gconf/+bug/1619407/+subscriptions

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


[Touch-packages] [Bug 1686189] [NEW] External monitor connecting problem

2017-04-25 Thread naveenkumarmula
Public bug reported:

I am facing a problem with Intel Graphics driver. I have external
monitor and in display settings the second monitor is detecting but it's
not working, so could you email me a solution.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.4.25-040425-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Apr 25 21:45:16 2017
DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
InstallationDate: Installed on 2017-04-25 (0 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
MachineType: Dell Inc. Inspiron 3537
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
dmi.bios.date: 04/30/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 03JPPR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A08
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
dmi.product.name: Inspiron 3537
dmi.product.version: A08
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Apr 25 21:37:24 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   17900 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 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/1686189

Title:
  External monitor connecting problem

Status in xorg package in Ubuntu:
  New

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  

[Touch-packages] [Bug 539570] Re: i could not find the required plugin MPEG-1 layer 3(MP3) decoder plugin

2017-04-25 Thread Sebastian Ramacher
Not a bug mpg123. If this problem still exists, please report it against
whatever player you are using.

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

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

Title:
  i could not find the required plugin MPEG-1 layer 3(MP3) decoder
  plugin

Status in mpg123 package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: mpg123

  i recently installed Ubuntu OS in my system.I wished to play music
  through my music player.But i found that the required plugin for
  playing it was not installed.On trying to install it ,I did not find
  it.So i require some help on how to do it?

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

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


[Touch-packages] [Bug 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1

2017-04-25 Thread Harry
Dmitri,

"I would like to see package versions of everything that is installed"

I have a fully updated artful setup with proposed enabled.


"... as per your messages it appears that systemd-resolved.service is not 
running at all, when it should be."

Systemd-resolved.service works just fine with systemd 232-21ubuntu3 (see
comment #1), but not with systemd 233-5ubuntu1.

How does that service changed between these versions?


"Note that DNSSEC is re-enabled in artful."

What do you mean by that? Should I have certain packages installed because of 
that?
The new systemd 233-5ubuntu1 did not pull in any new packages.


Note that my setup works just fine with systemd 232-21ubuntu3.

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

Title:
  On artful, no working dns after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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


[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-04-25 Thread Julian Andres Klode
(rewording from IRC:) Apparently this needs to go in via security, as
the upgrade would not automatically enable -updates, and we really need
this picked up. Since I can't do security stuff, it'd be best if someone
who can handles the updates.

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Incomplete
Status in cracklib2 source package in Yakkety:
  Triaged
Status in cracklib2 source package in Zesty:
  Triaged
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  This seems to be the same problem as described in bug #1636262, only
  this time it happened during upgrade from 16.10 to 17.04. The setup
  process (do-release-upgrade -d) aborted and I had to finish it
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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


[Touch-packages] [Bug 1672710] Re: apt fails to verify keys when Dir has space, and set via cmdline

2017-04-25 Thread Julian Andres Klode
xenial has the same problem, but does not actually parse the file to
apt-key. If we SRU there, I suggest:

 apt-config dump  -o foo=" bar " | sed
s#CommandLine::AsString#CommandLineAsString#g | apt-config shell FOO
CommandLineAsString -c /dev/stdin

as the test case.

xenial:
> E: Syntax error /dev/stdin:211: Extra junk after value
current:
> FOO='apt-config dump -o foo='\'' bar '\'''

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

Title:
  apt fails to verify keys when Dir has space, and set via cmdline

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Yakkety:
  Triaged

Bug description:
  When Dir has a space, and it is set via APT_CONFIG file, keys are found and 
validated correctly.
  When Dir is set without a space via cmdline, keys are found and validated 
correctly.
  When Dir is set with a space via cmdline, keys are not found and repositories 
are not verified.

  [Test case]
  Please see attached reproducer, which works on xenial system (gpg1) but not 
on zesty system (gpg2)

  $ bash reproducer.sh
  ++ mktemp -d
  + tmpdir=/tmp/tmp.sFipy6h5yL
  + pushd /tmp/tmp.sFipy6h5yL
  /tmp/tmp.sFipy6h5yL ~
  + mkdir 'Sub Dir'
  + pushd 'Sub Dir'
  /tmp/tmp.sFipy6h5yL/Sub Dir /tmp/tmp.sFipy6h5yL ~
  + mkdir -p etc/apt/apt.conf.d
  + mkdir -p etc/apt/trusted.gpg.d
  + mkdir -p etc/apt/preferences.d
  + mkdir -p var/lib/apt/lists/partial
  + mkdir -p var/lib/dpkg
  + touch var/lib/dpkg/status
  + cp /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg 
etc/apt/trusted.gpg.d/
  + echo 'deb http://archive.ubuntu.com/ubuntu/ trusty main'
  + echo 'Dir "/tmp/tmp.sFipy6h5yL/Sub Dir";'
  + export APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf
  + APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf
  + cat /tmp/tmp.sFipy6h5yL/apt.conf
  Dir "/tmp/tmp.sFipy6h5yL/Sub Dir";
  + :
  + : == list available keys ==
  + apt-key list
  /tmp/tmp.sFipy6h5yL/Sub 
Dir/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg
  
-
  pub   rsa4096 2012-05-11 [SC]
    790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2012) 


  + :
  + : == update with environ APT_CONFIG setting the Dir variable ==
  + apt update
  Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease
  Get:2 http://archive.ubuntu.com/ubuntu trusty Release [58.5 kB]
  Get:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg [933 B]
  Get:4 http://archive.ubuntu.com/ubuntu trusty/main amd64 Packages [1,350 kB]
  Fetched 1,410 kB in 0s (1,959 kB/s)
  Reading package lists... Done
  Building dependency tree... Done
  All packages are up to date.
  + unset APT_CONFIG
  + :
  + : == update with cmdline Dir option setting Dir to relative pwd ==
  + apt -o Dir=./ update
  Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu trusty Release
  Reading package lists... Done
  Building dependency tree... Done
  All packages are up to date.
  + :
  + : == update with cmdline Dir option setting Dir to absolute pwd with space 
==
  + apt -o 'Dir=/tmp/tmp.sFipy6h5yL/Sub Dir' update
  Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu trusty Release
  Err:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg
    The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  Reading package lists... Done
  Building dependency tree... Done
  All packages are up to date.
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://archive.ubuntu.com/ubuntu trusty Release: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/Release.gpg  
The following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  
  [Regression Potential]
  The fix changes the code to generate quotes in the Commmandline:AsString 
option, which dumps the command line for logging purposes. This was not 
parseable before, causing the file to be rejected, so what can happen is that 
something now works that did not before.

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

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

[Touch-packages] [Bug 896688] Re: avahi provides incorrect IP address to pulseaudio

2017-04-25 Thread Mike Wild
I've just encountered this issue with Ubuntu 16.04 / avahi-daemon
0.6.32~rc+dfsg-1ubuntu2. I have an AirPort Time Capsule, however the
problem is the same - pinging Airport-Time-Capsule.local resolves to an
incorrect 169.254.x.x IP address. Now interestingly, none of my other
devices (Apple or Android) have issues resolving this hostname. More
interestingly, I can successfully resolve hostnames of other Apple
devices from Ubuntu, just not the Time Capsule. This suggests there is a
specific compatibility issues between avahi and the Apple AirPort's mDNS
implementations.

I have a pcap of mDNS traffic after the Time Capsule was power-cycled.
Is there anything else I can provide to help?

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

Title:
  avahi provides incorrect IP address to pulseaudio

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 10.04
  Packages avahi-daemon 0.6.25-1ubuntu6.2

  I'm using an airport express with pulse audio and I believe avahi-
  daemon is providing/resolving the wrong IP address to pulse audio.

  Using the following command,  avahi-browse -r _raop._tcp

  I get:

  + eth1 IPv4 00254B09A042@Base Station 09a043  AirTunes Remote 
Audio local
  = eth1 IPv4 00254B09A042@Base Station 09a043  AirTunes Remote 
Audio local
 hostname = [Base-Station-09a043.local]
 address = [169.254.135.173]
 port = [5000]
 txt = ["sf=0x5" "fv=74200.9" "am=AirPort4,107" "vs=101.9" "tp=TCP,UDP" 
"vn=65537" "pw=false" "ss=16" "sr=44100" "da=true" "sv=false" "et=0,1" "ek=1" 
"cn=0,1" "ch=2" "txtvers=1"]

  where the address (169.254.135.173) is incorrect. It should be a
  192.168.1.X address which is already assigned to the APEX from the
  router using DHCP. I've had to specify the correct IP address to
  pulseaudio when I manually load the module_raop_sink module in order
  for it to properly stream music to it.

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

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


[Touch-packages] [Bug 46586] Re: Logitech Media Keyboard Elite not fully supported

2017-04-25 Thread Gunnar Hjalmarsson
It would be great if somebody who is affected by this could file an
upstream bug.

https://bugs.freedesktop.org/enter_bug.cgi?product=xkeyboard-config

This kind of addition wouldn't be reasonable to patch in Ubuntu only.

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

Title:
  Logitech Media Keyboard Elite not fully supported

Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  The media keys on the Logitech Media Keyboard Elite are not supported
  properly - the layout appears to be different than the others already
  included and the kernel does not recognise many of the media/extra
  keys. Currently I have the keyboard hooked up through the USB port.

  I have made the following changes to my system to attempt to support
  this keyboard. Caution: Pressing the key I have mapped as XF86LaunchC
  (F11 with the F-mode light off) will reliably crash and reboot the
  system - I have no idea why.

  At boot time, the following script is run to map the scancodes to the
  console level codes.  I assume that this keyboard really requires
  fixes in the kernel code to recognise this keyboard without the use of
  extra scan codes.

  # Kernel level keycode mappings for the Logitech Media Keyboard Elite USB
  # 6a   190   Zoom In
  # e004 191   Zoom Out
  # 6b   192   Zoom Reset
  # e011 193   Messenger
  # e05a 194   Mode F (switch function keys)
  # e03b 195   (F1 )Help
  # e03c 196   (F2 )Word
  # e03d 197   (F3 )Excel
  # e03e 198   (F4 )Powerpoint
  # e03f 199   (F5 )Undo
  # e040 200   (F6 )Redo
  # e041 201   (F7 )Print
  # e042 202   (F8 )Save
  # e043 203   (F9 )Box A
  # e044 204   (F10)Box B
  # e057 205   (F11)Box C
  # e058 206   (F12)Box D

  setkeycodes \
  6a 190 \
  e004 191   \
  6b 192 \
  e011 193   \
  e05a 194   \
  e03b 195   \
  e03c 196   \
  e03d 197   \
  e03e 198   \
  e03f 199   \
  e040 200   \
  e041 201   \
  e042 202   \
  e043 203   \
  e044 204   \
  e057 205   \
  e058 206
  # ---

  I also made the following alterations to the symbols in
  /etc/X11/xkb/symbols/inet:

  --- inet.20060516   2006-05-16 20:44:30.0 -0400
  +++ inet2006-05-16 20:59:41.0 -0400
  @@ -1244,6 +1244,39 @@
   key   {   [ XF86AudioRaiseVolume  ]   };
   };

  +// Logitech Media Keyboard Elite
  +partial alphanumeric_keys
  +xkb_symbols "logimedelite" {
  +include "inet(logitech_base)"
  +
  +key   {   [ XF86ZoomIn]   };
  +key   {   [ XF86ZoomOut   ]   };
  +key   {   [ XF86Clear ]   };
  +key   {   [ XF86AudioPlay, XF86AudioPause ]   };
  +key   {   [ XF86AudioStop ]   };
  +key   {   [ XF86AudioNext ]   };
  +key   {   [ XF86Messenger ]   };
  +key   {   [ XF86Calculator]   };
  +key   {   [ XF86ModeLock  ]   };
  +
  +key   {   [ XF86Help  ]   };
  +key   {   [ XF86Word  ]   };
  +key   {   [ XF86Excel ]   };
  +key   {   [ XF86Finance   ]   };
  +
  +key   {   [ XF86Back  ]   };
  +key   {   [ XF86Forward   ]   };
  +key   {   [ XF86Book  ]   };
  +key   {   [ XF86Save  ]   };
  +
  +key   {   [ XF86LaunchA   ]   };
  +key   {   [ XF86LaunchB   ]   };
  +key   {   [ XF86LaunchC   ]   };
  +key   {   [ XF86LaunchD   ]   };
  +
  +};
  +
  +
   partial alphanumeric_keys
   xkb_symbols "logiultrax" {
   include "inet(logitech_base)"

  
  Then the three rules files in /etc/X11/xkb/rules were updated as follows:

  toby@nexus:/etc/X11/xkb/rules$ diff -Naur base.20060516 base
  --- base.20060516   2006-05-16 21:00:45.0 -0400
  +++ base2006-05-16 21:01:43.0 -0400
  @@ -38,7 +38,7 @@
 honeywell_euroboard \
 rapidaccess rapidaccess2 rapidaccess2a \
 ltcd logiaccess logicdp logicdpa logicdit logicink logiciink \
  -  logiinkse logiinkseusb logiitc logiik itouch logiultrax \
  +  logiinkse logiinkseusb logiitc logiik itouch logimedelite 
logiultrax \
 mx1998 mx2500 mx2750 \
 microsoftinet microsoftpro microsoftprousb microsoftprooem 
microsoftprose \
 microsoftoffice microsoftmult \

  toby@nexus:/etc/X11/xkb/rules$ diff -Naur base.lst.20060516 base.lst
  --- 

[Touch-packages] [Bug 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1

2017-04-25 Thread Dimitri John Ledkov
I would like to see package versions of everything that is installed;
syslog and journal log; as per your messages it appears that systemd-
resolved.service is not running at all, when it should be.

Note that DNSSEC is re-enabled in artful.

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

Title:
  On artful, no working dns after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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


[Touch-packages] [Bug 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1

2017-04-25 Thread Dimitri John Ledkov
Note i cannot reproduce your issue locally at the moment, and dns
resolution works for me as expected.

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

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

Title:
  On artful, no working dns after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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


[Touch-packages] [Bug 1645815] Re: apt install of local debs does not tab-complete

2017-04-25 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.2.20

---
apt (1.2.20) xenial; urgency=medium

  * Microrelease covering fixes of 1.4~rc2 (LP: #1668285)

  [ David Kalnischkies ]
  * don't install new deps of candidates for kept back pkgs
  * keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
  * reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
  * add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
  * let {dsc,tar,diff}-only implicitly enable download-only
  * don't show update stats if cache generation is disabled
  * don't lock dpkg in 'apt-get clean'
  * don't lock dpkg in update commands
  * avoid validate/delete/load race in cache generation
  * remove 'old' FAILED files in the next acquire call (Closes: 846476)
  * stop rred from leaking debug messages on recovered errors (Closes: #850759)

  [ Paul Wise ]
  * show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

  [ John R. Lenton ]
  * bash-completion: Only complete understood file paths for install
(LP: #1645815)

  [ Lukasz Kawczynski ]
  * Honour Acquire::ForceIPv4/6 in the https transport

  [ Julian Andres Klode ]
  * basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
  * Only merge acquire items with the same meta key (Closes: #838441)
  * Do not package names representing .dsc/.deb/... files (Closes: #854794)
  * Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues

 -- Julian Andres Klode   Mon, 27 Feb 2017 15:29:18
+0100

** Changed in: apt (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  apt install of local debs does not tab-complete

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Previously apt's bash completion was such that, given

  $ mkdir xyzzz
  $ touch xyzzy.deb xyzzx.two.deb

  you'd get

  $ apt install xyzz
  xyzzx.two.deb  xyzzz/
  $ apt install /tmp/foo/xyzz
  xyzzx.two.deb  xyzzz/

  this is inconsistent (xyzzx.two.deb is listed but not xyzzy.deb), but
  worse than that it offered things that apt would not actually
  recognise as candidates for install:

  $ sudo apt install xyzzx.two.deb
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  E: Unable to locate package xyzzx.two.deb
  E: Couldn't find any package by glob 'xyzzx.two.deb'
  E: Couldn't find any package by regex 'xyzzx.two.deb'

  [Test case]
  With this small (trival, really) change, apt's bash completion should
  only offer things apt understands, and won't recquire an aditional
  period in the filename to offer it:

  $ apt install xyzz^C
  $ # (no completions!)
  $ apt install ./xyzz
  xyzzx.two.deb  xyzzy.deb  xyzzz/
  $ apt install /tmp/foo/xyzz
  xyzzx.two.deb  xyzzy.deb  xyzzz/

  
  [Regression potential]
  Only the expansion of filenames in the completion is affected:
  -_filedir "*.deb"
  +if [[ "$cur" == ./* || "$cur" == /* ]]; then
  +_filedir "deb"
  +fi
  so it's unlikely to introduce any regression.

  [Original bug report]

  this fails:

  $ touch xyzzy.deb
  $ apt install xyzzy

  because the completion support for install is using _filedir wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.15
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 29 17:51:57 2016
  InstallationDate: Installed on 2016-07-05 (147 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1657440] Re: apt won't redownload Release.gpg after inconsistent cache updates made while UCA is being updated

2017-04-25 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.2.20

---
apt (1.2.20) xenial; urgency=medium

  * Microrelease covering fixes of 1.4~rc2 (LP: #1668285)

  [ David Kalnischkies ]
  * don't install new deps of candidates for kept back pkgs
  * keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
  * reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
  * add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
  * let {dsc,tar,diff}-only implicitly enable download-only
  * don't show update stats if cache generation is disabled
  * don't lock dpkg in 'apt-get clean'
  * don't lock dpkg in update commands
  * avoid validate/delete/load race in cache generation
  * remove 'old' FAILED files in the next acquire call (Closes: 846476)
  * stop rred from leaking debug messages on recovered errors (Closes: #850759)

  [ Paul Wise ]
  * show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

  [ John R. Lenton ]
  * bash-completion: Only complete understood file paths for install
(LP: #1645815)

  [ Lukasz Kawczynski ]
  * Honour Acquire::ForceIPv4/6 in the https transport

  [ Julian Andres Klode ]
  * basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
  * Only merge acquire items with the same meta key (Closes: #838441)
  * Do not package names representing .dsc/.deb/... files (Closes: #854794)
  * Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues

 -- Julian Andres Klode   Mon, 27 Feb 2017 15:29:18
+0100

** Changed in: apt (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  apt won't redownload Release.gpg after inconsistent cache updates made
  while UCA is being updated

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Yakkety:
  Fix Released

Bug description:
  # apt --version
  apt 1.2.18 (amd64)

  xenial

  I got myself into a situation where a repository has a Release and a
  Release.gpg file, but apt is just ignoring the gpg one and won't
  download it via apt update for some reason:

  The repository in question is http://ubuntu-
  cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/. See
  how locally I have just the Release file:

  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# l *Release*
  -rw-r--r-- 1 root root 100K Jan 15 18:03 
archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease
  -rw-r--r-- 1 root root 242K Apr 21  2016 
archive.ubuntu.com_ubuntu_dists_xenial_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
security.ubuntu.com_ubuntu_dists_xenial-security_InRelease
  -rw-r--r-- 1 root root 7.7K Jan 18 11:45 
ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release

  Now I try an update. See how the Release.gpg file gets a "Hit:" instead of a 
"Get:":
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
  Ign:3 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
InRelease
  Get:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
  Hit:5 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release
  Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release.gpg [543 B]
  Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
  Fetched 205 kB in 0s (395 kB/s)
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  8 packages can be upgraded. Run 'apt list --upgradable' to see them.

  And I can't install packages:
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
    python3-setuptools
  The following packages will be upgraded:
    dh-python dnsmasq-base python-pkg-resources python-setuptools 
python3-cryptography python3-pkg-resources python3-requests python3-urllib3
  8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,193 kB of archives.
  After this operation, 808 kB of additional disk space will be used.
  Do you want to continue? [Y/n]
  WARNING: The following packages cannot be authenticated!
    dh-python dnsmasq-base python-setuptools python-pkg-resources 
python3-pkg-resources python3-setuptools python3-cryptography python3-requests 
python3-urllib3
  Install these packages 

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

2017-04-25 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.2.20

---
apt (1.2.20) xenial; urgency=medium

  * Microrelease covering fixes of 1.4~rc2 (LP: #1668285)

  [ David Kalnischkies ]
  * don't install new deps of candidates for kept back pkgs
  * keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
  * reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
  * add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
  * let {dsc,tar,diff}-only implicitly enable download-only
  * don't show update stats if cache generation is disabled
  * don't lock dpkg in 'apt-get clean'
  * don't lock dpkg in update commands
  * avoid validate/delete/load race in cache generation
  * remove 'old' FAILED files in the next acquire call (Closes: 846476)
  * stop rred from leaking debug messages on recovered errors (Closes: #850759)

  [ Paul Wise ]
  * show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

  [ John R. Lenton ]
  * bash-completion: Only complete understood file paths for install
(LP: #1645815)

  [ Lukasz Kawczynski ]
  * Honour Acquire::ForceIPv4/6 in the https transport

  [ Julian Andres Klode ]
  * basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
  * Only merge acquire items with the same meta key (Closes: #838441)
  * Do not package names representing .dsc/.deb/... files (Closes: #854794)
  * Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues

 -- Julian Andres Klode   Mon, 27 Feb 2017 15:29:18
+0100

** Changed in: apt (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  "Content-Range: */" on non-416 responses considered invalid

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Yakkety:
  Fix Released

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

  [Impact]
  Issue breaks and other services that respond with a Content-Range header in a 
302 redirect, or any non 416 one.

  [Test Case]
  Run

  /usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
  http://www.jak-software.de/lp1657567 ubuntu.iso

  Before:

  E: Failed to fetch http://www.jak-software.de/lp1657567  The HTTP
  server sent an invalid Content-Range header Bad header data

  After:

  Redirect is followed successfully and a zesty live image is being
  downloaded.

  [Regression Potential]
  None

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

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


[Touch-packages] [Bug 1668285] Update Released

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

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

Title:
  [SRU] Update apt/xenial to 1.2.20

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Subset of bug #1668280 basically, to the extend the apply to 1.2. This is a 
far saner amount of changes than in 1.3.5, because we don't have the 
installation ordering changes as the new installation ordering was introduced 
in 1.3.

[ David Kalnischkies ]
* don't install new deps of candidates for kept back pkgs
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
  (LP: #1657440)
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
* let {dsc,tar,diff}-only implicitly enable download-only
* don't show update stats if cache generation is disabled
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands
* avoid validate/delete/load race in cache generation
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: 
#850759)

[ Paul Wise ]
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

[ John R. Lenton ]
* bash-completion: Only complete understood file paths for install
  (LP: #1645815)

[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport

[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
  Thanks to James Clarke for debugging these issues

  [Test case]
  Mentioned launchpad bugs have their own test case sections. The rest is 
checked in the CI, so we should just do some updates upgrades and check that 
everything works.

  [Regression Potential]
  In #1668280, about 80% of the code changes are covered by test cases. This 
leaves out most code changes that are not covered, so code coverage should be 
higher, reducing the regression potential enormously.

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

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


[Touch-packages] [Bug 1668285] Re: [SRU] Update apt/xenial to 1.2.20

2017-04-25 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.2.20

---
apt (1.2.20) xenial; urgency=medium

  * Microrelease covering fixes of 1.4~rc2 (LP: #1668285)

  [ David Kalnischkies ]
  * don't install new deps of candidates for kept back pkgs
  * keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
  * reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
  * add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
  * let {dsc,tar,diff}-only implicitly enable download-only
  * don't show update stats if cache generation is disabled
  * don't lock dpkg in 'apt-get clean'
  * don't lock dpkg in update commands
  * avoid validate/delete/load race in cache generation
  * remove 'old' FAILED files in the next acquire call (Closes: 846476)
  * stop rred from leaking debug messages on recovered errors (Closes: #850759)

  [ Paul Wise ]
  * show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

  [ John R. Lenton ]
  * bash-completion: Only complete understood file paths for install
(LP: #1645815)

  [ Lukasz Kawczynski ]
  * Honour Acquire::ForceIPv4/6 in the https transport

  [ Julian Andres Klode ]
  * basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
  * Only merge acquire items with the same meta key (Closes: #838441)
  * Do not package names representing .dsc/.deb/... files (Closes: #854794)
  * Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues

 -- Julian Andres Klode   Mon, 27 Feb 2017 15:29:18
+0100

** Changed in: apt (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Update apt/xenial to 1.2.20

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Subset of bug #1668280 basically, to the extend the apply to 1.2. This is a 
far saner amount of changes than in 1.3.5, because we don't have the 
installation ordering changes as the new installation ordering was introduced 
in 1.3.

[ David Kalnischkies ]
* don't install new deps of candidates for kept back pkgs
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
  (LP: #1657440)
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
* let {dsc,tar,diff}-only implicitly enable download-only
* don't show update stats if cache generation is disabled
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands
* avoid validate/delete/load race in cache generation
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: 
#850759)

[ Paul Wise ]
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

[ John R. Lenton ]
* bash-completion: Only complete understood file paths for install
  (LP: #1645815)

[ Lukasz Kawczynski ]
* Honour Acquire::ForceIPv4/6 in the https transport

[ Julian Andres Klode ]
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
  Thanks to James Clarke for debugging these issues

  [Test case]
  Mentioned launchpad bugs have their own test case sections. The rest is 
checked in the CI, so we should just do some updates upgrades and check that 
everything works.

  [Regression Potential]
  In #1668280, about 80% of the code changes are covered by test cases. This 
leaves out most code changes that are not covered, so code coverage should be 
higher, reducing the regression potential enormously.

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

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


[Touch-packages] [Bug 1685900] Re: On artful, no network after upgrading to systemd 233-5ubuntu1

2017-04-25 Thread Harry
Dimitri,

in my case, not even several reboots helped.
It is all the same here, though network should be up, there is no working dns.

** Summary changed:

- On artful, no network after upgrading to systemd 233-5ubuntu1
+ On artful, no working dns after upgrading to systemd 233-5ubuntu1

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

Title:
  On artful, no working dns after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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


[Touch-packages] [Bug 1657567] Update Released

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

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

Title:
  "Content-Range: */" on non-416 responses considered invalid

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

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

  [Impact]
  Issue breaks and other services that respond with a Content-Range header in a 
302 redirect, or any non 416 one.

  [Test Case]
  Run

  /usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
  http://www.jak-software.de/lp1657567 ubuntu.iso

  Before:

  E: Failed to fetch http://www.jak-software.de/lp1657567  The HTTP
  server sent an invalid Content-Range header Bad header data

  After:

  Redirect is followed successfully and a zesty live image is being
  downloaded.

  [Regression Potential]
  None

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

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


[Touch-packages] [Bug 1657440] Re: apt won't redownload Release.gpg after inconsistent cache updates made while UCA is being updated

2017-04-25 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.3.5

---
apt (1.3.5) yakkety; urgency=medium

  * Microrelease covering important fixes of 1.4~rc2 (LP: #1668280)

  [ David Kalnischkies ]
  * don't install new deps of candidates for kept back pkgs
  * keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
  * reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
  * add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
  * react to trig-pend only if we have nothing else to do
  * correct cross & disappear progress detection
  * improve arch-unqualified dpkg-progress parsing
  * don't perform implicit crossgrades involving M-A:same
  * do not configure unconfigured to be removed packages
  * skip unconfigure for unconfigured to-be removed pkgs
  * get pdiff files from the same mirror as the index
  * let {dsc,tar,diff}-only implicitly enable download-only
  * ensure generation of valid EDSP error stanzas
  * fix minimum pkgs option for dpkg --recursive usage
  * don't show update stats if cache generation is disabled
  * don't lock dpkg in 'apt-get clean'
  * don't lock dpkg in update commands
  * avoid validate/delete/load race in cache generation
  * fix 'install --no-download' mode
  * remove 'old' FAILED files in the next acquire call (Closes: 846476)
  * stop rred from leaking debug messages on recovered errors (Closes: #850759)

  [ Edgar Fuß ]
  * http: clear content before reporting the failure (Closes: #465572)

  [ Paul Wise ]
  * show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

  [ John R. Lenton ]
  * bash-completion: Only complete understood file paths for install
(LP: #1645815)

  [ Lukasz Kawczynski ]
  * Honour Acquire::ForceIPv4/6 in the https transport

  [ Julian Andres Klode ]
  * basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
  * Only merge acquire items with the same meta key (Closes: #838441)
  * Do not package names representing .dsc/.deb/... files (Closes: #854794)
  * Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues
  * CMake: Install statvfs.h to include/sys, not just include/

 -- Julian Andres Klode   Mon, 27 Feb 2017 15:02:40
+0100

** Changed in: apt (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  apt won't redownload Release.gpg after inconsistent cache updates made
  while UCA is being updated

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Released

Bug description:
  # apt --version
  apt 1.2.18 (amd64)

  xenial

  I got myself into a situation where a repository has a Release and a
  Release.gpg file, but apt is just ignoring the gpg one and won't
  download it via apt update for some reason:

  The repository in question is http://ubuntu-
  cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/. See
  how locally I have just the Release file:

  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# l *Release*
  -rw-r--r-- 1 root root 100K Jan 15 18:03 
archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease
  -rw-r--r-- 1 root root 242K Apr 21  2016 
archive.ubuntu.com_ubuntu_dists_xenial_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
security.ubuntu.com_ubuntu_dists_xenial-security_InRelease
  -rw-r--r-- 1 root root 7.7K Jan 18 11:45 
ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release

  Now I try an update. See how the Release.gpg file gets a "Hit:" instead of a 
"Get:":
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
  Ign:3 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
InRelease
  Get:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
  Hit:5 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release
  Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release.gpg [543 B]
  Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
  Fetched 205 kB in 0s (395 kB/s)
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  8 packages can be upgraded. Run 'apt list --upgradable' to see them.

  And I can't install packages:
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW 

[Touch-packages] [Bug 1645815] Update Released

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

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

Title:
  apt install of local debs does not tab-complete

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

Bug description:
  [Impact]
  Previously apt's bash completion was such that, given

  $ mkdir xyzzz
  $ touch xyzzy.deb xyzzx.two.deb

  you'd get

  $ apt install xyzz
  xyzzx.two.deb  xyzzz/
  $ apt install /tmp/foo/xyzz
  xyzzx.two.deb  xyzzz/

  this is inconsistent (xyzzx.two.deb is listed but not xyzzy.deb), but
  worse than that it offered things that apt would not actually
  recognise as candidates for install:

  $ sudo apt install xyzzx.two.deb
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  E: Unable to locate package xyzzx.two.deb
  E: Couldn't find any package by glob 'xyzzx.two.deb'
  E: Couldn't find any package by regex 'xyzzx.two.deb'

  [Test case]
  With this small (trival, really) change, apt's bash completion should
  only offer things apt understands, and won't recquire an aditional
  period in the filename to offer it:

  $ apt install xyzz^C
  $ # (no completions!)
  $ apt install ./xyzz
  xyzzx.two.deb  xyzzy.deb  xyzzz/
  $ apt install /tmp/foo/xyzz
  xyzzx.two.deb  xyzzy.deb  xyzzz/

  
  [Regression potential]
  Only the expansion of filenames in the completion is affected:
  -_filedir "*.deb"
  +if [[ "$cur" == ./* || "$cur" == /* ]]; then
  +_filedir "deb"
  +fi
  so it's unlikely to introduce any regression.

  [Original bug report]

  this fails:

  $ touch xyzzy.deb
  $ apt install xyzzy

  because the completion support for install is using _filedir wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.15
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 29 17:51:57 2016
  InstallationDate: Installed on 2016-07-05 (147 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1645815] Re: apt install of local debs does not tab-complete

2017-04-25 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.3.5

---
apt (1.3.5) yakkety; urgency=medium

  * Microrelease covering important fixes of 1.4~rc2 (LP: #1668280)

  [ David Kalnischkies ]
  * don't install new deps of candidates for kept back pkgs
  * keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
  * reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
  * add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
  * react to trig-pend only if we have nothing else to do
  * correct cross & disappear progress detection
  * improve arch-unqualified dpkg-progress parsing
  * don't perform implicit crossgrades involving M-A:same
  * do not configure unconfigured to be removed packages
  * skip unconfigure for unconfigured to-be removed pkgs
  * get pdiff files from the same mirror as the index
  * let {dsc,tar,diff}-only implicitly enable download-only
  * ensure generation of valid EDSP error stanzas
  * fix minimum pkgs option for dpkg --recursive usage
  * don't show update stats if cache generation is disabled
  * don't lock dpkg in 'apt-get clean'
  * don't lock dpkg in update commands
  * avoid validate/delete/load race in cache generation
  * fix 'install --no-download' mode
  * remove 'old' FAILED files in the next acquire call (Closes: 846476)
  * stop rred from leaking debug messages on recovered errors (Closes: #850759)

  [ Edgar Fuß ]
  * http: clear content before reporting the failure (Closes: #465572)

  [ Paul Wise ]
  * show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

  [ John R. Lenton ]
  * bash-completion: Only complete understood file paths for install
(LP: #1645815)

  [ Lukasz Kawczynski ]
  * Honour Acquire::ForceIPv4/6 in the https transport

  [ Julian Andres Klode ]
  * basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
  * Only merge acquire items with the same meta key (Closes: #838441)
  * Do not package names representing .dsc/.deb/... files (Closes: #854794)
  * Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues
  * CMake: Install statvfs.h to include/sys, not just include/

 -- Julian Andres Klode   Mon, 27 Feb 2017 15:02:40
+0100

** Changed in: apt (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  apt install of local debs does not tab-complete

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

Bug description:
  [Impact]
  Previously apt's bash completion was such that, given

  $ mkdir xyzzz
  $ touch xyzzy.deb xyzzx.two.deb

  you'd get

  $ apt install xyzz
  xyzzx.two.deb  xyzzz/
  $ apt install /tmp/foo/xyzz
  xyzzx.two.deb  xyzzz/

  this is inconsistent (xyzzx.two.deb is listed but not xyzzy.deb), but
  worse than that it offered things that apt would not actually
  recognise as candidates for install:

  $ sudo apt install xyzzx.two.deb
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  E: Unable to locate package xyzzx.two.deb
  E: Couldn't find any package by glob 'xyzzx.two.deb'
  E: Couldn't find any package by regex 'xyzzx.two.deb'

  [Test case]
  With this small (trival, really) change, apt's bash completion should
  only offer things apt understands, and won't recquire an aditional
  period in the filename to offer it:

  $ apt install xyzz^C
  $ # (no completions!)
  $ apt install ./xyzz
  xyzzx.two.deb  xyzzy.deb  xyzzz/
  $ apt install /tmp/foo/xyzz
  xyzzx.two.deb  xyzzy.deb  xyzzz/

  
  [Regression potential]
  Only the expansion of filenames in the completion is affected:
  -_filedir "*.deb"
  +if [[ "$cur" == ./* || "$cur" == /* ]]; then
  +_filedir "deb"
  +fi
  so it's unlikely to introduce any regression.

  [Original bug report]

  this fails:

  $ touch xyzzy.deb
  $ apt install xyzzy

  because the completion support for install is using _filedir wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.15
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 29 17:51:57 2016
  InstallationDate: Installed on 2016-07-05 (147 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1657440] Update Released

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

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

Title:
  apt won't redownload Release.gpg after inconsistent cache updates made
  while UCA is being updated

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Released

Bug description:
  # apt --version
  apt 1.2.18 (amd64)

  xenial

  I got myself into a situation where a repository has a Release and a
  Release.gpg file, but apt is just ignoring the gpg one and won't
  download it via apt update for some reason:

  The repository in question is http://ubuntu-
  cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/. See
  how locally I have just the Release file:

  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# l *Release*
  -rw-r--r-- 1 root root 100K Jan 15 18:03 
archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease
  -rw-r--r-- 1 root root 242K Apr 21  2016 
archive.ubuntu.com_ubuntu_dists_xenial_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
security.ubuntu.com_ubuntu_dists_xenial-security_InRelease
  -rw-r--r-- 1 root root 7.7K Jan 18 11:45 
ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release

  Now I try an update. See how the Release.gpg file gets a "Hit:" instead of a 
"Get:":
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
  Ign:3 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
InRelease
  Get:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
  Hit:5 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release
  Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release.gpg [543 B]
  Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
  Fetched 205 kB in 0s (395 kB/s)
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  8 packages can be upgraded. Run 'apt list --upgradable' to see them.

  And I can't install packages:
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
    python3-setuptools
  The following packages will be upgraded:
    dh-python dnsmasq-base python-pkg-resources python-setuptools 
python3-cryptography python3-pkg-resources python3-requests python3-urllib3
  8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,193 kB of archives.
  After this operation, 808 kB of additional disk space will be used.
  Do you want to continue? [Y/n]
  WARNING: The following packages cannot be authenticated!
    dh-python dnsmasq-base python-setuptools python-pkg-resources 
python3-pkg-resources python3-setuptools python3-cryptography python3-requests 
python3-urllib3
  Install these packages without verification? [y/N] n
  E: Some packages could not be authenticated
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists#

  Somehow apt is thinking it has the Release.gpg file, but it doesn't?

  This server is behind a squid proxy.


  [Impact]
  An apt update of an apt repository that does not use InRelease during the 
time it is being updated can cause the gpg file to not be downloaded and 
updated. This makes the packages from the repository be unable to be 
authenticated.

  The Ubuntu Cloud Archive is one of the archives that meets this
  criteria.

  The impact to downstream automation deployment code is that if they
  are adding the UCA repo to a system and calling apt update during the
  time the UCA is being updated by Canonical, the repo can get into a
  state where the Release.gpg file is not there and all package installs
  will fail due to "unauthenticated packages" error.

  [Test Case]
  A detailed python script was attached.

  To reproduce this outside that script you would want to:
  1. Add the UCA repo
  2. Do the following in a loop starting at 43 minutes after the hour and run 
it until 55 minutes after the hour:
  2.1 Remove these files to simulate the UCA repo being added the first time.

[Touch-packages] [Bug 1668280] Re: [SRU] Update apt/yakkety to 1.3.5

2017-04-25 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.3.5

---
apt (1.3.5) yakkety; urgency=medium

  * Microrelease covering important fixes of 1.4~rc2 (LP: #1668280)

  [ David Kalnischkies ]
  * don't install new deps of candidates for kept back pkgs
  * keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
  * reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
  * add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
  * react to trig-pend only if we have nothing else to do
  * correct cross & disappear progress detection
  * improve arch-unqualified dpkg-progress parsing
  * don't perform implicit crossgrades involving M-A:same
  * do not configure unconfigured to be removed packages
  * skip unconfigure for unconfigured to-be removed pkgs
  * get pdiff files from the same mirror as the index
  * let {dsc,tar,diff}-only implicitly enable download-only
  * ensure generation of valid EDSP error stanzas
  * fix minimum pkgs option for dpkg --recursive usage
  * don't show update stats if cache generation is disabled
  * don't lock dpkg in 'apt-get clean'
  * don't lock dpkg in update commands
  * avoid validate/delete/load race in cache generation
  * fix 'install --no-download' mode
  * remove 'old' FAILED files in the next acquire call (Closes: 846476)
  * stop rred from leaking debug messages on recovered errors (Closes: #850759)

  [ Edgar Fuß ]
  * http: clear content before reporting the failure (Closes: #465572)

  [ Paul Wise ]
  * show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

  [ John R. Lenton ]
  * bash-completion: Only complete understood file paths for install
(LP: #1645815)

  [ Lukasz Kawczynski ]
  * Honour Acquire::ForceIPv4/6 in the https transport

  [ Julian Andres Klode ]
  * basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
  * Only merge acquire items with the same meta key (Closes: #838441)
  * Do not package names representing .dsc/.deb/... files (Closes: #854794)
  * Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues
  * CMake: Install statvfs.h to include/sys, not just include/

 -- Julian Andres Klode   Mon, 27 Feb 2017 15:02:40
+0100

** Changed in: apt (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Update apt/yakkety to 1.3.5

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  This collects several bug fixes from the 1.4 branch. Most of the stuff has 
been in Debian since 20 days, and in testing since Feb 12.

  Fixes in the acquire system - mostly error cases.
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
-> hit often these days, ask Riddel
* get pdiff files from the same mirror as the index
-> we are not really affected by this, but it does not hurt
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
  (LP: #1657440)
-> breaks the assumption of adding untrusted repo; installing keyring, and 
update
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: 
#850759)
* http: clear content before reporting the failure (Closes: #465572)
  Security improvements - dropping environment variables for workers:
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance

  Installation ordering changes - that changed a lot in 1.3:
* react to trig-pend only if we have nothing else to do
* correct cross & disappear progress detection
* improve arch-unqualified dpkg-progress parsing
* don't perform implicit crossgrades involving M-A:same
* do not configure unconfigured to be removed packages
* skip unconfigure for unconfigured to-be removed pkgs
* fix minimum pkgs option for dpkg --recursive usage

  Locking fixes to reduce chance of breaking running install/upgrade commands:
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands

  Other important fixes:
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* avoid validate/delete/load race in cache generation

  Bugfix to not install garbage because it was a dep of something that was hold 
back:
* don't install new deps of candidates for kept back pkgs

  Minor fixes:
* let {dsc,tar,diff}-only implicitly enable download-only
* ensure generation of valid EDSP error stanzas
* don't show update stats if cache generation is disabled
* fix 'install 

[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid

2017-04-25 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.3.5

---
apt (1.3.5) yakkety; urgency=medium

  * Microrelease covering important fixes of 1.4~rc2 (LP: #1668280)

  [ David Kalnischkies ]
  * don't install new deps of candidates for kept back pkgs
  * keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
(LP: #1657440)
  * reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
  * add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance
  * react to trig-pend only if we have nothing else to do
  * correct cross & disappear progress detection
  * improve arch-unqualified dpkg-progress parsing
  * don't perform implicit crossgrades involving M-A:same
  * do not configure unconfigured to be removed packages
  * skip unconfigure for unconfigured to-be removed pkgs
  * get pdiff files from the same mirror as the index
  * let {dsc,tar,diff}-only implicitly enable download-only
  * ensure generation of valid EDSP error stanzas
  * fix minimum pkgs option for dpkg --recursive usage
  * don't show update stats if cache generation is disabled
  * don't lock dpkg in 'apt-get clean'
  * don't lock dpkg in update commands
  * avoid validate/delete/load race in cache generation
  * fix 'install --no-download' mode
  * remove 'old' FAILED files in the next acquire call (Closes: 846476)
  * stop rred from leaking debug messages on recovered errors (Closes: #850759)

  [ Edgar Fuß ]
  * http: clear content before reporting the failure (Closes: #465572)

  [ Paul Wise ]
  * show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)

  [ John R. Lenton ]
  * bash-completion: Only complete understood file paths for install
(LP: #1645815)

  [ Lukasz Kawczynski ]
  * Honour Acquire::ForceIPv4/6 in the https transport

  [ Julian Andres Klode ]
  * basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
  * Only merge acquire items with the same meta key (Closes: #838441)
  * Do not package names representing .dsc/.deb/... files (Closes: #854794)
  * Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
Thanks to James Clarke for debugging these issues
  * CMake: Install statvfs.h to include/sys, not just include/

 -- Julian Andres Klode   Mon, 27 Feb 2017 15:02:40
+0100

** Changed in: apt (Ubuntu Yakkety)
   Status: Fix Committed => Fix Released

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

Title:
  "Content-Range: */" on non-416 responses considered invalid

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

Bug description:
  APT only allows Content-Range: */ to be specified on a 416
  response. Sourceforge sometimes replies with that in a 302 redirect.

  We should probably just accept and silently ignore that content-range
  field for other values.

  [Impact]
  Issue breaks and other services that respond with a Content-Range header in a 
302 redirect, or any non 416 one.

  [Test Case]
  Run

  /usr/lib/apt/apt-helper download-file -o debug::acquire::http=1
  http://www.jak-software.de/lp1657567 ubuntu.iso

  Before:

  E: Failed to fetch http://www.jak-software.de/lp1657567  The HTTP
  server sent an invalid Content-Range header Bad header data

  After:

  Redirect is followed successfully and a zesty live image is being
  downloaded.

  [Regression Potential]
  None

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

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


[Touch-packages] [Bug 1668280] Update Released

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

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

Title:
  [SRU] Update apt/yakkety to 1.3.5

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  This collects several bug fixes from the 1.4 branch. Most of the stuff has 
been in Debian since 20 days, and in testing since Feb 12.

  Fixes in the acquire system - mostly error cases.
* basehttp: Only read Content-Range on 416 and 206 responses (LP: #1657567)
* Only merge acquire items with the same meta key (Closes: #838441)
-> hit often these days, ask Riddel
* get pdiff files from the same mirror as the index
-> we are not really affected by this, but it does not hurt
* keep Release.gpg on untrusted to trusted IMS-Hit (Closes: 838779)
  (LP: #1657440)
-> breaks the assumption of adding untrusted repo; installing keyring, and 
update
* remove 'old' FAILED files in the next acquire call (Closes: 846476)
* stop rred from leaking debug messages on recovered errors (Closes: 
#850759)
* http: clear content before reporting the failure (Closes: #465572)
  Security improvements - dropping environment variables for workers:
* reset HOME, USER(NAME), TMPDIR & SHELL in DropPrivileges (Closes: 842877)
* add TMP/TEMP/TEMPDIR to the TMPDIR DropPrivileges dance

  Installation ordering changes - that changed a lot in 1.3:
* react to trig-pend only if we have nothing else to do
* correct cross & disappear progress detection
* improve arch-unqualified dpkg-progress parsing
* don't perform implicit crossgrades involving M-A:same
* do not configure unconfigured to be removed packages
* skip unconfigure for unconfigured to-be removed pkgs
* fix minimum pkgs option for dpkg --recursive usage

  Locking fixes to reduce chance of breaking running install/upgrade commands:
* don't lock dpkg in 'apt-get clean'
* don't lock dpkg in update commands

  Other important fixes:
* Do not package names representing .dsc/.deb/... files (Closes: #854794)
* avoid validate/delete/load race in cache generation

  Bugfix to not install garbage because it was a dep of something that was hold 
back:
* don't install new deps of candidates for kept back pkgs

  Minor fixes:
* let {dsc,tar,diff}-only implicitly enable download-only
* ensure generation of valid EDSP error stanzas
* don't show update stats if cache generation is disabled
* fix 'install --no-download' mode
* show output as documented for APT::Periodic::Verbose 2 (Closes: 845599)
* bash-completion: Only complete understood file paths for install
  (LP: #1645815)
* Honour Acquire::ForceIPv4/6 in the https transport
* Don't use -1 fd and AT_SYMLINK_NOFOLLOW for faccessat()
  Thanks to James Clarke for debugging these issues
* CMake: Install statvfs.h to include/sys, not just include/

  [Test case]
  Mentioned launchpad bugs have their own test case sections. The rest is 
checked in the CI, so we should just do some updates upgrades and check that 
everything works.

  [Regression Potential]
  About 80% of the code difference is covered by test cases. So, there is less 
than a 20% chance something is wrong. But I think we would have caught these in 
the three weeks or more these changes spent in Debian unstable and (1 week 
less) testing.

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

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


[Touch-packages] [Bug 1238194] Re: keyboard doesn't work to enter password with encrypted partitions ubuntu 13.10 saucy

2017-04-25 Thread Rafael
I was able to solve the problem by booting with an old kernel, editing 
/etc/initramfs-tools/initramfs.conf and replacing
MODULES=most
with
MODULES=dep
and then running sudo update-initramfs -u.
I think the problem was that initramfs was including a module xhci-plat-hcd 
which is buggy and not really required. I was seeing error messages of the type
... xhci_hcd ... HC died; cleaning up
and then couldn't enter my passphrase.
My computer is a MacBookPro 12,1.

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

Title:
  keyboard doesn't work to enter password with encrypted partitions
  ubuntu 13.10 saucy

Status in initramfs-tools:
  New
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Precise:
  Fix Released
Status in initramfs-tools source package in Saucy:
  Fix Released

Bug description:
  [Justification]
  With the kernel in 13.10, some systems use a different USB host driver than 
previously.  Failing to include this driver in the initramfs causes regressions 
for users who need to interact with the system in early boot using a USB 
keyboard, such as users with an encrypted root filesystem.  Such systems are 
not bootable with this host driver missing.

  [Test case]
  1. On an affected system, reboot to a kernel from 13.04.
  2. Install the initramfs-tools package from -proposed.
  3. Reboot to the kernel from 13.10.
  4. Verify that you are able to type your passphrase at the prompt in the 
initramfs.

  [Regression potential]
  Minimal.  The update-initramfs script will ignore missing modules (such as 
the many other modules in the list which are built-ins), and the only change 
made is to copy the module into the initramfs: it will only be loaded in the 
initramfs if udev determines it's needed, just as it would load it after 
switching to the root filesystem.

  
  Is the same problem as here but in the new ubuntu 13.10 saucy 
https://bugs.launchpad.net/bugs/1066376

  I just can't use (i can install) a encrypted partition because when is
  time to introduce the password to unlock partition keyboard is not
  working.

  I don't know how to edit a bug to report it afects other version of
  ubuntu so i created this new bug...

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

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


[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseded by systemd

2017-04-25 Thread Dimitri John Ledkov
** Changed in: upstart-watchdog (Ubuntu)
 Assignee: Dimitri John Ledkov (xnox) => (unassigned)

** Changed in: cgmanager (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: ubuntu-touch-meta (Ubuntu)
 Assignee: Dimitri John Ledkov (xnox) => (unassigned)

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

Title:
  RM Upstart, obsolete, superseded by systemd

Status in cgmanager package in Ubuntu:
  Triaged
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in ubuntu-touch-meta package in Ubuntu:
  Triaged
Status in ubuntu-touch-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session package in Ubuntu:
  Triaged
Status in upstart package in Ubuntu:
  Triaged
Status in upstart-watchdog package in Ubuntu:
  Triaged

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

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

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


[Touch-packages] [Bug 1668169] Re: package linux-image-4.4.0-64-generic 4.4.0-64.85 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2017-04-25 Thread srijan
Can i fix this bug on my own? I can't use ubuntu after upgrading due to
this.


** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/initramfs-tools/+question/628251

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

Title:
  package linux-image-4.4.0-64-generic 4.4.0-64.85 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  I upgrades from 14.04 lts to 16.04.2 lts and now i am encountering
  this issue.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 3.13.0-38.65somerville1-generic 3.13.11.9
  Uname: Linux 3.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  srijan 2207 F pulseaudio
   /dev/snd/controlC0:  srijan 2207 F pulseaudio
  Date: Mon Feb 27 12:08:30 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=3cae9dc6-49a2-48a9-983c-2071e8c309bd
  InstallationDate: Installed on 2017-02-26 (1 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 3558
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-38-generic.efi.signed 
root=UUID=8b176865-3f85-4a10-9422-420bee75e6a0 ro quiet splash radeon.modeset=0 
nouveau.modeset=0 video.use_native_backlight=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  StagingDrivers: rts5139
  Title: package linux-image-4.4.0-64-generic 4.4.0-64.85 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2017-02-27 (0 days ago)
  dmi.bios.date: 05/31/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0XCR91
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/31/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XCR91:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 3558
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1686163] [NEW] Nu am sonor in difuzoare sau este distorsionat

2017-04-25 Thread iulian
Public bug reported:

Sonorul în difuzoare, este dat la maximum, dar se aude încet și
distorsionat!

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Apr 25 20:24:51 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.18, 4.10.0-19-generic, x86_64: installed
 virtualbox, 5.1.18, 4.10.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1858]
InstallationDate: Installed on 2017-04-13 (12 days ago)
InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Hewlett-Packard HP 650 Notebook PC
ProcEnviron:
 LANGUAGE=ro
 PATH=(custom, no user)
 LANG=ro_RO.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=c8fbd7b6-341a-46dc-8f79-c5b887b27f94 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/19/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.32
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 1858
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 65.33
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd10/19/2012:svnHewlett-Packard:pnHP650NotebookPC:pvr088412005B10002600010:rvnHewlett-Packard:rn1858:rvr65.33:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 650 Notebook PC
dmi.product.version: 088412005B10002600010
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
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.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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: Tue Apr 25 20:20:14 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug ubuntu zesty

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

Title:
  Nu am sonor in difuzoare sau este distorsionat

Status in xorg package in Ubuntu:
  New

Bug description:
  Sonorul în difuzoare, este dat la maximum, dar se aude încet și
  distorsionat!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Apr 25 20:24:51 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.18, 4.10.0-19-generic, x86_64: installed
   virtualbox, 5.1.18, 4.10.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1858]
  InstallationDate: Installed on 2017-04-13 (12 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  MachineType: Hewlett-Packard HP 650 Notebook PC
  ProcEnviron:
   LANGUAGE=ro
   PATH=(custom, no user)
   LANG=ro_RO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=c8fbd7b6-341a-46dc-8f79-c5b887b27f94 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2012
  dmi.bios.vendor: Insyde
  

[Touch-packages] [Bug 1685900] Re: On artful, no network after upgrading to systemd 233-5ubuntu1

2017-04-25 Thread Dimitri John Ledkov
Messages about removing obsolete conffiles are normal, as dbus config
files have moved form /etc to /usr; and upstart jobs are no longer
needed as upstart is not required anymore.

I am suspecting if one reboots after an upgrade eveyrhting is fine.

I believe we also need to potentially reload dbus configuration, after
the dbus files are moved to /usr and I'm not sure if this is done
already or not.

I will investigate further the upgrade issue you are pointing out.

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

Title:
  On artful, no network after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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


[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseded by systemd

2017-04-25 Thread Dimitri John Ledkov
** Changed in: lxc-android-config (Ubuntu)
   Status: New => Triaged

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

** Changed in: ubuntu-touch-meta (Ubuntu)
   Status: In Progress => Triaged

** Changed in: unity8-desktop-session (Ubuntu)
   Status: In Progress => Triaged

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

Title:
  RM Upstart, obsolete, superseded by systemd

Status in cgmanager package in Ubuntu:
  Triaged
Status in lxc-android-config package in Ubuntu:
  Triaged
Status in ubuntu-touch-meta package in Ubuntu:
  Triaged
Status in ubuntu-touch-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session package in Ubuntu:
  Triaged
Status in upstart package in Ubuntu:
  Triaged
Status in upstart-watchdog package in Ubuntu:
  Triaged

Bug description:
  In 18.04 LTS src:upstart should not be part of Ubuntu.
  It has already been removed from Debian.
  And most products have migrated to systemd.
  This is a tracking bug to remove a collection of packages that need to go 
away together with upstart.

  Some of these have been ported to systemd under different names, or no
  longer at all required.

  = Removal order =

  * ubuntu-touch-meta
  * unity8-desktop-session

  * ubuntu-touch-session
  * upstart-watchdog
  * lxc-android-config

  * upstart

  * cgmanager

  = Reverse depends checks =

  $ reverse-depends -b src:upstart
  Reverse-Build-Depends
  =
  * tarantool (for upstart)
    ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart 
(<< 1.13),
  * unity (for libupstart-dev)
    https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
    https://bileto.ubuntu.com/#/ticket/2730

  $ reverse-depends src:upstart
  Reverse-Depends
  ===
  * ubuntu-touch-session  (for upstart)
  * unity8-desktop-session(for upstart)
  * upstart-watchdog  (for upstart)

  $ reverse-depends src:ubuntu-touch-session
  Reverse-Depends
  ===
  * ubuntu-touch  (for ubuntu-touch-session)
  $ reverse-depends -b src:ubuntu-touch-session
  No reverse dependencies found

  $ reverse-depends upstart-watchdog
  Reverse-Depends
  ===
  * ubuntu-touch
  $ reverse-depends -b src:upstart-watchdog
  No reverse dependencies found

  $ reverse-depends src:ubuntu-touch-meta
  No reverse dependencies found
  $ reverse-depends -b src:ubuntu-touch-meta
  No reverse dependencies found

  $ reverse-depends src:unity8-desktop-session
  No reverse dependencies found
  $ reverse-depends -b src:unity8-desktop-session
  No reverse dependencies found

  $ reverse-depends src:cgmanager
  Reverse-Depends
  ===
  * lxc-android-config(for cgmanager)
  * numad (for cgmanager)
    ./debian/control:Depends: systemd-sysv | cgmanager
  * upstart [amd64 arm64 armhf i386 ppc64el]  (for libcgmanager0)

  $ reverse-depends -b src:cgmanager
  Reverse-Build-Depends
  =
  * upstart   (for libcgmanager-dev)

  $ reverse-depends src:lxc-android-config
  Reverse-Depends
  ===
  * ubuntu-touch  (for lxc-android-config)

  $ reverse-depends -b src:lxc-android-config
  No reverse dependencies found

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

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


[Touch-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-04-25 Thread Brian Murray
@bill - you might try 'sudo dpkg --configure -a' and see if that
resolves the situation.

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Fix Released
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Incomplete
Status in cracklib2 source package in Yakkety:
  Triaged
Status in cracklib2 source package in Zesty:
  Triaged
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  This seems to be the same problem as described in bug #1636262, only
  this time it happened during upgrade from 16.10 to 17.04. The setup
  process (do-release-upgrade -d) aborted and I had to finish it
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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


[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-04-25 Thread Eric Desrochers
** Description changed:

  [Impact]
  
  * Context:
  
  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit
  only (Confirmed with AMD representative). Current OpenSSL version in
  Ryzens still calls SHA for SSSE3 routine as result a number of
  extensions were effectively masked on Ryzen and shows no improvement.
  
  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family : 23
  model : 1
  model name : AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni 
pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
  
  [2] - sha_ni: SHA1/SHA256 Instruction Extensions
  
  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...
  
  * Program to performs the CPUID check:
  
  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions
  
  ... Availability of the Intel® SHA Extensions on a particular processor
  can be determined by checking the SHA CPUID bit in CPUID.(EAX=07H,
  ECX=0):EBX.SHA [bit 29]. The following C function, using inline
  assembly, performs the CPUID check:
  
  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;
  
     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;
  
     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );
  
     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --
  
  On CPU with sha_ni the program return "1". Otherwise it return "0".
  
  [Test Case]
  
   * Reproducible with Xenial/Zesty/Artful release.
  
   * Generated a checksum of a big file (e.g. 5GB file) with openssl
   $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
  SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8
  
  real  0m12.835s
  user  0m12.344s
  sys   0m0.484s
  
  * Openssl speed
  $ openssl speed sha1
  Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
  Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
  Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
  Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
  Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
  OpenSSL 1.0.2g 1 Mar 2016
  built on: reproducible build, date unspecified
  options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
  compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT 
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall 
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM 
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
  The 'numbers' are in 1000s of bytes per second processed.
  type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
  sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55
  
  The performance are clearly better when using the patch which take
  benefit of the sha extension. (See Regression Potential section for
  result with patch)
  
  [Regression Potential]
  
   * Note from irc discussion with apw and rbasak :
  
  [10:03:20]  slashd, for me some new functionality like that is ok
  as long as it is very self-contained so easy to review and confirm is
  only used on the new h/w
  
  [10:03:52] one of our main goals is to avoid regressions
  
  [10:12:24]  The SRU policy does explicitly permit hardware
  enablement in an LTS IIRC, though I'd expect ~ubuntu-sru to be involved
  in mitigating risk and making the final risk decision, FWIW.
  
-  * None expected, it basically allow openssl to take benefit of sha
- extension potential (mostly performance-wise) now that new AMD cpu
- starting  have the capability.
+ Full discussion:
+ https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2
+ 
+  * It basically allow openssl to take benefit of sha extension potential
+ (mostly performance-wise) now that new AMD cpu starting  to have the
+ capability.
+ 
+ * The code check the CPUID bit to determine if the sha instructions are
+ available are not.
  
   * Generated a checksum of a big file (e.g. 5GB 

[Touch-packages] [Bug 1677239] Re: mir_demo_standalone_render_overlays fails to link

2017-04-25 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2735

** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736

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

Title:
  mir_demo_standalone_render_overlays fails to link

Status in Mir:
  Fix Committed
Status in Mir 0.26 series:
  Fix Committed
Status in mir package in Ubuntu:
  Triaged

Bug description:
  https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
  mir/arch=amd64,compiler=gcc,platform=mesa,release=zesty/4453/console

  11:41:20 [ 52%] Linking CXX executable 
../../../../bin/mir_demo_standalone_render_overlays.bin
  11:41:20 cd 
/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124/obj-x86_64-linux-gnu/src/platforms/android/utils
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/mir_demo_standalone_render_overlays.dir/link.txt --verbose=1
  11:41:20 /usr/lib/ccache/c++ -g -O2 
-fdebug-prefix-map=/<>/mir-0.26.1+17.04.20170209.1+zesty4503bzr4124=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -g -std=c++14 -Werror -Wall -fno-strict-aliasing 
-pedantic -Wnon-virtual-dtor -Wextra -fPIC -flto -ffat-lto-objects 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined 
CMakeFiles/mir_demo_standalone_render_overlays.dir/render_overlays.cpp.o -o 
../../../../bin/mir_demo_standalone_render_overlays.bin -rdynamic 
../../../../lib/libmirplatform.so.16 ../../../../lib/libmircommon.so.7 
../../../capnproto/libmircapnproto.a -lkj -lcapnp 
../../../../lib/libmircore.so.1 -lboost_date_time -lboost_system 
-lboost_program_options -lboost_filesystem -ldl -lEGL -lGLESv2 -lGLESv2 
-L/lib/x86_64-linux-gnu -ludev -ludev
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirInputDeviceStateEvent::device_pressed_keys_for_index(unsigned long, 
unsigned long) const@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirPointerEvent::set_x(float)@MIR_COMMON_0.25_PRIVATE'
  11:41:21 //usr/lib/x86_64-linux-gnu/libmirclient.so.9: undefined reference to 
`MirTouchEvent::pressure(unsigned long) const@MIR_COMMON_0.25_PRIVATE'

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

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


[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem

2017-04-25 Thread Louis Bouchard
** Description changed:

  [SRU justification]
  This fix is needed to make sure that the system does not hang on shutdown 
when /var is a speparate file system
  
  [Impact]
  System can hang up to 10 minutes if not fixed.
  
  [Fix]
  Change the systemd unit's ExecStart to an ExecStop so the unit is correctly 
sequenced.
+ Change WantedBy to multi-user.target. This requires working around Debian Bug 
#797108 which causes the new unit not to be enabled.
+ Remove the unneeded override_dh_isntallinit
+ Add Default-Start levels to the SysV initscript
+ Improve DEP8 testing
  
  [Test Case]
  In a VM with /var separated from the / file system, shutdown the VM. It will 
hang for 10 minutes
  
  [Regression]
- None to be expected. A ExecStop unit will be sequenced before the Before= 
units which is earlier than previously.
+ Upgrade has been tested on Xenial, Yakkety, Zesty. do-release-upgrade has 
been tested from Trusty to Xenial. All behave as expected.
+ 
+ A change of behavior may occur now that the systemd unit is correctly
+ enabled, which would make functionalities like InstallOnShutdown to work
+ as expected whereas it could have been broken previously. This cannot be
+ considered as a regression as it is expected behavior.
+ 
+ Shutdown may be slowed down as it now correctly depends on /var and
+ /boot to be available so the unit will run earlier than previously.
  
  [Original description of the problem]
  The systemd unit file unattended-upgrades.service is used to stop a running 
unattended-upgrade
  process during shutdown. This unit file is running together with all 
filesystem
  unmount services.
  
  The unattended-upgrades service checks if the lockfile for unattended-upgrade
  (in /var/run) exists, and if it does, there is an unattended-upgrade in 
progress
  and the service will wait until it finishes (and therefore automatically wait 
at
  shutdown).
  
  However, if /var is a separate filesystem, it will get unmounted even though 
/var/run
  is a tmpfs that's still mounted on top of the /var/run directory in the /var 
filesystem.
  The unattended-upgrade script will fail to find lockfile, sleeps for 5 
seconds, and
  tries to check the lockfile again. After 10 minutes (the default timeout), it 
will finally
  exit and the system will continue shutdown.
  
  The problem is the error handling in 
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
  where it tries to lock itself:
  
  while True:
  res = apt_pkg.get_lock(options.lock_file)
  logging.debug("get_lock returned %i" % res)
  # exit here if there is no lock
  if res > 0:
  logging.debug("lock not taken")
  break
  lock_was_taken = True
  
  The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an 
error.
  File descriptors are just C file descriptors, so they are always positive 
integers.
  The code should check the result to be negative, not positive. I have 
attached a patch
  to reverse the logic.
  
  Additional information:
  
  1)
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  
  2)
  unattended-upgrades:
    Installed: 0.90ubuntu0.3
    Candidate: 0.90ubuntu0.3
    Version table:
   *** 0.90ubuntu0.3 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  3)
  Fast reboot
  4)
  Very slow reboot (after a 10 minutes timeout)

** Changed in: unattended-upgrades (Ubuntu Yakkety)
   Status: Triaged => In Progress

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: unattended-upgrades (Ubuntu)
 Assignee: Louis Bouchard (louis) => (unassigned)

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

Title:
  unattended-upgrade-shutdown hangs when /var is a separate filesystem

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in unattended-upgrades source package in Yakkety:
  In Progress
Status in unattended-upgrades source package in Zesty:
  In Progress
Status in unattended-upgrades package in Debian:
  New

Bug description:
  [SRU justification]
  This fix is needed to make sure that the system does not hang on shutdown 
when /var is a speparate file system

  [Impact]
  System can hang up to 10 minutes if not fixed.

  [Fix]
  Change the systemd unit's ExecStart to an ExecStop so the unit is correctly 
sequenced.
  Change WantedBy to multi-user.target. This requires working around Debian Bug 
#797108 which causes 

[Touch-packages] [Bug 1686157] [NEW] External Displays Turn Off After Only A Few Seconds Of Inactivity

2017-04-25 Thread Dane Mutters
Public bug reported:

OS VERSION
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=17.04
DISTRIB_CODENAME=zesty
DISTRIB_DESCRIPTION="Ubuntu 17.04"

UPOWER VERSION
upower:
  Installed: 0.99.4-4
  Candidate: 0.99.4-4
  Version table:
 *** 0.99.4-4 500
500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
100 /var/lib/dpkg/status

EXPECTED BEHAVIOR
Expected displays to stay on while idle, for at least a few minutes (per Power 
Settings).

WHAT HAPPENED INSTEAD (and hardware information)
I just upgraded from a fully-updated Ubuntu 16.10 64-bit Desktop installation 
to 17.04, using the update manager.  In 16.10 and 16.04 LTS, this issue did not 
exist for me.

I'm using a MacBook Pro with Ubuntu installed in a dual-boot
configuration.  I have two attached monitors: one via the mini
DisplayPort and one via HDMI.  I normally keep the laptop lid closed
while working.  Since the upgrade (persisting through several reboots),
whenever I have the notebook lid closed, if I don't touch the keyboard
or mouse for about 5 seconds, both external displays go into power-
saving mode.  When I touch the keyboard/mouse, again, they instantly
come back up (no delay), indicating that the computer had probably not
been suspended.  If I then don't touch the keyboard/mouse for another 5
seconds, they immediately go back into power saving mode.  (Repeat...)

Going into Display Settings and changing "Built-in Display" to on or off
doesn't seem to have any effect.  When I close the lid, it changes
itself back to "OFF"; and when I open the lid, it changes itself back to
"ON".  (This seems like a sensible behavior.)  Notably, the on/off
switch doesn't seem to move unless I exit and re-enter Display Settings.

I found a workaround to this problem on a forum post:
In "/etc/UPower/UPower.conf", change "IgnoreLid=false" to "IgnoreLid=true".

After doing this, the Built-in Display switch stays on whatever I set it
to, regardless of whether the laptop lid is open or closed (which
probably isn't ideal); but more importantly, the external displays no
longer turn off when idle for a few seconds.  They now obey the settings
I explicitly define in Power Settings.

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

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

Title:
  External Displays Turn Off After Only A Few Seconds Of Inactivity

Status in upower package in Ubuntu:
  New

Bug description:
  OS VERSION
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=17.04
  DISTRIB_CODENAME=zesty
  DISTRIB_DESCRIPTION="Ubuntu 17.04"

  UPOWER VERSION
  upower:
Installed: 0.99.4-4
Candidate: 0.99.4-4
Version table:
   *** 0.99.4-4 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  EXPECTED BEHAVIOR
  Expected displays to stay on while idle, for at least a few minutes (per 
Power Settings).

  WHAT HAPPENED INSTEAD (and hardware information)
  I just upgraded from a fully-updated Ubuntu 16.10 64-bit Desktop installation 
to 17.04, using the update manager.  In 16.10 and 16.04 LTS, this issue did not 
exist for me.

  I'm using a MacBook Pro with Ubuntu installed in a dual-boot
  configuration.  I have two attached monitors: one via the mini
  DisplayPort and one via HDMI.  I normally keep the laptop lid closed
  while working.  Since the upgrade (persisting through several
  reboots), whenever I have the notebook lid closed, if I don't touch
  the keyboard or mouse for about 5 seconds, both external displays go
  into power-saving mode.  When I touch the keyboard/mouse, again, they
  instantly come back up (no delay), indicating that the computer had
  probably not been suspended.  If I then don't touch the keyboard/mouse
  for another 5 seconds, they immediately go back into power saving
  mode.  (Repeat...)

  Going into Display Settings and changing "Built-in Display" to on or
  off doesn't seem to have any effect.  When I close the lid, it changes
  itself back to "OFF"; and when I open the lid, it changes itself back
  to "ON".  (This seems like a sensible behavior.)  Notably, the on/off
  switch doesn't seem to move unless I exit and re-enter Display
  Settings.

  I found a workaround to this problem on a forum post:
  In "/etc/UPower/UPower.conf", change "IgnoreLid=false" to "IgnoreLid=true".

  After doing this, the Built-in Display switch stays on whatever I set
  it to, regardless of whether the laptop lid is open or closed (which
  probably isn't ideal); but more importantly, the external displays no
  longer turn off when idle for a few seconds.  They now obey the
  settings I explicitly define in Power Settings.

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

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

[Touch-packages] [Bug 1685900] Re: On artful, no network after upgrading to systemd 233-5ubuntu1

2017-04-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  On artful, no network after upgrading to systemd 233-5ubuntu1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got 
no network.
  This is very likely a DNS issue.
  As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS 
work fine.

  So something odd has happened between these versions.

  My setup is a fully upgraded artful with proposed repo turned on.
  I use only Gnome DE with GDM.
  Everything else works fine, but not systemd 233-5ubuntu1.

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

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


[Touch-packages] [Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

2017-04-25 Thread Olivier Tilloy
Closing now as this report wasn’t investigated timely and is now too old to be 
meaningful.
Please do not hesitate to report crashes occurring with recent releases of 
chromium-browser, they will hopefully be investigated and acted upon in a more 
timely manner.

** Changed in: chromium-browser (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  init (chromium-browser) crashed with SIGSEGV

Status in apport package in Ubuntu:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Won't Fix

Bug description:
  Test Case
  -
  1) Set your default browser to Chromium.
  2) Launch synaptic
  3) Click on the home page url for a package.
  4) Observe chromium-browser not launch
  5) Receive apport crash dialog
  5) Also notice the apport crash dialog refers to upstart / systemd

  none

  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu1
  Uname: Linux 3.14.0-031400rc8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Mon Mar 31 09:53:16 2014
  Disassembly: => 0x7fa2b65e94d7:   Cannot access memory at address 
0x7fa2b65e94d7
  ExecutablePath: /sbin/init
  InstallationDate: Installed on 2014-03-05 (25 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140305)
  ProcCmdline: /sbin/init
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic 
root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7fa2b65e94d7:Cannot access memory at address 
0x7fa2b65e94d7
   PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable 
region)!
   Stack pointer not within stack segment
  SegvReason: executing unknown VMA
  Signal: 11SourcePackage: upstart
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
  Title: init crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.12.1)
  UserGroups:

  modified.conffile..etc.default.cups: [modified]
  mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893

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

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


[Touch-packages] [Bug 1685683] Re: Update evolution to 3.24.1

2017-04-25 Thread Jeremy Bicha
** Description changed:

  We should update the Evolution stack to 3.24 for Ubuntu 17.10. The big
  change here is that it now uses cmake instead of autotools.
  
  The update is staged in this PPA and rebuilds of all rdepends have been done:
  https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions/+packages
  
  I made a few packaging changes we should review with Debian.
  
  1. I dropped https://sources.debian.net/src/evolution-data-
  server/unstable/debian/patches/01-noinst-libedbus-private.patch/ and
  added a libedbus-private0 package and had all the e-d-s libraries depend
  on it.
  
  2. I dropped
  https://sources.debian.net/src/evolution/unstable/debian/patches
  /10_revert_libevolution_avoid-version.patch/ since it does not directly
  apply to cmake and it doesn't seem needed. The soname hasn't been bumped
  in 5 years. I had to have libevolution Breaks/Replaces evolution-dev
  since there are no .so symlinks any more.
  
  3. I disabled
  
https://sources.debian.net/src/evolution/unstable/debian/patches/02_nss_paths.patch/
  since it didn't seem to be needed.
  
  To Do
  =
- 4. https://bugzilla.gnome.org/show_bug.cgi?id=781645
- 
- 5. Hook up the new installed-tests packages to be ran as autopkgtests
+ 4. Hook up the new installed-tests packages to be ran as autopkgtests

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

Title:
  Update evolution to 3.24.1

Status in evolution package in Ubuntu:
  New
Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  We should update the Evolution stack to 3.24 for Ubuntu 17.10. The big
  change here is that it now uses cmake instead of autotools.

  The update is staged in this PPA and rebuilds of all rdepends have been done:
  https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions/+packages

  I made a few packaging changes we should review with Debian.

  1. I dropped https://sources.debian.net/src/evolution-data-
  server/unstable/debian/patches/01-noinst-libedbus-private.patch/ and
  added a libedbus-private0 package and had all the e-d-s libraries
  depend on it.

  2. I dropped
  https://sources.debian.net/src/evolution/unstable/debian/patches
  /10_revert_libevolution_avoid-version.patch/ since it does not
  directly apply to cmake and it doesn't seem needed. The soname hasn't
  been bumped in 5 years. I had to have libevolution Breaks/Replaces
  evolution-dev since there are no .so symlinks any more.

  3. I disabled
  
https://sources.debian.net/src/evolution/unstable/debian/patches/02_nss_paths.patch/
  since it didn't seem to be needed.

  To Do
  =
  4. Hook up the new installed-tests packages to be ran as autopkgtests

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

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


[Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

2017-04-25 Thread Jeremy Bicha
** Description changed:

  I'm splitting this issue off from LP: #1685542 (which made xserver-xorg-
  input-all no longer recommend xserver-xorg-input-synaptics) for tracking
  the remaining issues.
  
  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which haven't
  been ported to libinput yet), synaptics overrides libinput. That makes
  gnome-control-center's Mouse & Touchpad settings panel only show basic
  settings and important configurations don't work.
  
  Questions
  -
  1. Which desktops/apps still need -synaptics?
+ - Unity
+ - Xfce?
+ - LXDE? LXQt?
+ All the other major desktops have already been ported (LP: #1417980)
  
  2. Can these apps be ported or removed before 18.04 LTS is released?
  
  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?
  
  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?
  
  5. Is there any other way we can fix this conflict?

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

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

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


[Touch-packages] [Bug 1686145] [NEW] package libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-04-25 Thread Abdelhak Lemkhenter
Public bug reported:

After Upgrade to 17.04

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
Date: Tue Apr 18 19:12:49 2017
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2016-11-06 (170 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: unity-scopes-api
Title: package libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
UpgradeStatus: Upgraded to zesty on 2017-04-18 (6 days ago)

** Affects: unity-scopes-api (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check zesty

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

Title:
  package libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  After Upgrade to 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Tue Apr 18 19:12:49 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-11-06 (170 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0 1.0.8+17.04.20170116-0ubuntu1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1686145/+subscriptions

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


[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-04-25 Thread Eric Desrochers
Another test "Openssl speed"

[Without patch]
 $ openssl speed sha1
Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
OpenSSL 1.0.2g 1 Mar 2016
built on: reproducible build, date unspecified
options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN 
-DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall -DOPENSSL_IA32_SSE2 
-DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM 
-DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM 
-DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55 

[With patch]
 $ openssl speed sha1
Doing sha1 for 3s on 16 size blocks: 12081890 sha1's in 3.00s
Doing sha1 for 3s on 64 size blocks: 11563950 sha1's in 3.00s
Doing sha1 for 3s on 256 size blocks: 8375101 sha1's in 3.00s
Doing sha1 for 3s on 1024 size blocks: 3987643 sha1's in 3.00s
Doing sha1 for 3s on 8192 size blocks: 678036 sha1's in 3.00s
OpenSSL 1.0.2g 1 Mar 2016
built on: reproducible build, date unspecified
options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) 
blowfish(idx)
compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN 
-DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall -DOPENSSL_IA32_SSE2 
-DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM 
-DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM 
-DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
sha1 64436.75k 246697.60k 714675.29k 1361115.48k 1851490.30k


** Description changed:

  [Impact]
  
  * Context:
  
  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit
  only (Confirmed with AMD representative). Current OpenSSL version in
  Ryzens still calls SHA for SSSE3 routine as result a number of
  extensions were effectively masked on Ryzen and shows no improvement.
  
  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family : 23
  model : 1
  model name : AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni 
pclmulqdq monitor ssse3 fma cx16 sse
  4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
  pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
  
  [2] - sha_ni: SHA1/SHA256 Instruction Extensions
  
  [3] - https://en.wikipedia.org/wiki/Ryzen
  ...
  All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
  ...
  
  * Program to performs the CPUID check:
  
  Reference :
  https://software.intel.com/en-us/articles/intel-sha-extensions
  
  ... Availability of the Intel® SHA Extensions on a particular processor
  can be determined by checking the SHA CPUID bit in CPUID.(EAX=07H,
  ECX=0):EBX.SHA [bit 29]. The following C function, using inline
  assembly, performs the CPUID check:
  
  --
  int CheckForIntelShaExtensions() {
     int a, b, c, d;
  
     // Look for CPUID.7.0.EBX[29]
     // EAX = 7, ECX = 0
     a = 7;
     c = 0;
  
     asm volatile ("cpuid"
  :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
  :"a"(a), "c"(c)
     );
  
     // Intel® SHA Extensions feature bit is EBX[29]
     return ((b >> 29) & 1);
  }
  --
  
  On CPU with sha_ni the program return "1". Otherwise it return "0".
  
  [Test Case]
  
   * Reproducible with Xenial/Zesty/Artful release.
  
   * Generated a checksum of a big file (e.g. 5GB file) with openssl
   $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
  SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8
  
  real  0m12.835s
  user  0m12.344s
  sys   0m0.484s
  
+ * Openssl speed 
+ $ openssl speed sha1
+ Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
+ Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
+ Doing sha1 for 3s on 256 size blocks: 5254219 

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-04-25 Thread Tamas Papp
Recently I can definitely reproduce the issue anytime.

It's extremely annoying.

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

Title:
  systemd-resolved using 100% CPU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  dmi.chassis.asset.tag: CNU51199KV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

[Touch-packages] [Bug 1422795] Re: bash crashes often if inputrc contains revert-all-at-newline

2017-04-25 Thread Julian Andres Klode
I just fixed the binutils bug I think, and it's in the queue for trusty.
Just Googled for "segfault iterative_hash" and that turned up a patch
... So I think this should build on arm64 again soon.

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

Title:
  bash crashes often if inputrc contains revert-all-at-newline

Status in bash package in Ubuntu:
  Fix Released
Status in bash source package in Trusty:
  In Progress
Status in bash package in Debian:
  Fix Released

Bug description:
  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747341
  The Debian bug includes complete reproduction case. Basically:
  with .inputrc containing
  set revert-all-at-newline On

  Go back in the commandline history, edit a command, then submit a different 
command (may be empty)
  Such as:
  $ ls something
  $ 

  Attached diff is confirmed to fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: bash 4.3-7ubuntu1.5 [origin: goobuntu-trusty-testing-desktop]
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue Feb 17 15:49:30 2015
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.bash.bashrc: [modified]
  mtime.conffile..etc.bash.bashrc: 2015-01-27T03:27:18.751405

  
  [Test Case]

  Adapted from the Debian bug report:

  1. echo "set revert-all-at-newline on" > bug.inputrc
  2. INPUTRC=bug.inputrc bash
  3. echo hello
  4. ^P^U^N^M  [Hold down control and type "punm".]

  Bash should die immediately with SIGABRT.

  
  [Regression Potential]

  Relatively low.

  The change has no effect at all unless _rl_revert_all_lines() is called,
  which only happens if revert-all-at-newline is set, and then only when a
  newline is typed.  So, the potential for regression is essentially zero for
  non-interactive shells and for anyone not using revert-all-at-newline (which
  is not the default).

  Further, this change appeared upstream and in both Debian and Ubuntu over
  a year ago, so it's had plenty of public testing.

  lib/readline/misc.c:_rl_revert_all_lines() contains a loop which iterates
  over history entries, reverting changes to each history entry.  This patch
  causes entry->data, which points to the per-entry undo list, to be cleared
  before reverting edits rather than after.  At first glance, this shouldn't
  make any difference.  However, it prevents rl_do_undo() from replacing the
  history entry with one reflecting the change.  Otherwise, the entry gets
  freed, leaving _rl_revert_all_lines() with an invalid pointer.

  _Not_ having an invalid pointer and double-free certainly can't be worse
  than the current situation.  Since we're avoiding is making the pointer
  invalid rather than not doing the free, the chance of a new leak is pretty
  much nonexistent.

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

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


[Touch-packages] [Bug 1680421] Status changed to Confirmed

2017-04-25 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  Computer suspends/sleeps before login

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

Bug description:
  I am not able to login into the system because it sleeps in the boot
  process. To fix this, I need to edit (in recovery mode) the
  /etc/systemd/logind.conf to replace the following options:

  HandleLidSwitch=ignore
  HandleLidSwitchDocked=ignore

  This behaviour started in Ubuntu 14.10.

  Some other users have this issue too:
  
http://askubuntu.com/questions/829998/ubuntu-16-04-usually-suspends-before-login-and-while-logout

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5
  Uname: Linux 4.10.0-15-generic i686
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  6 08:25:20 2017
  InstallationDate: Installed on 2017-04-06 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta i386 (20170405)
  MachineType: Positivo Positivo Mobile
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-15-generic 
root=UUID=f7649356-2952-4c27-9279-c3ab658730ad ro locale=pt_BR quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2006
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 4.06CJ15
  dmi.board.name: M5X0V
  dmi.board.vendor: CLEVO Co.
  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:bvnPhoenix:bvr4.06CJ15:bd06/08/2006:svnPositivo:pnPositivoMobile:pvrVT6198:rvnCLEVOCo.:rnM5X0V:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: Positivo Mobile
  dmi.product.version: VT6198
  dmi.sys.vendor: Positivo
  mtime.conffile..etc.systemd.logind.conf: 2017-04-06T08:15:16.198796

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

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


[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs

2017-04-25 Thread Eric Desrochers
So far my test reveal the following :

# Note that the below test has been made on a Ryzen system #

[Without patch]
 * Generated a checksum of a big file (e.g. 5GB file) with openssl
 $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile 
SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8

real0m12.835s
user0m12.344s
sys 0m0.484s

[With patch]
 * Generated a checksum of a big file (e.g. 5GB file) with openssl
 $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile  
SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8

real0m3.471s
user0m2.956s
sys 0m0.516s


** Description changed:

+ [Impact]
+ 
+ * Context:
+ 
+ AMD added support in their processors for SHA Extensions[1] (CPU flag:
+ sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit
+ only (Confirmed with AMD representative). Current OpenSSL version in
+ Ryzens still calls SHA for SSSE3 routine as result a number of
+ extensions were effectively masked on Ryzen and shows no improvement.
+ 
+ [1] /proc/cpuinfo
+ processor : 0
+ vendor_id : AuthenticAMD
+ cpu family : 23
+ model : 1
+ model name : AMD Ryzen 5 1600 Six-Core Processor
+ flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat 
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni 
pclmulqdq monitor ssse3 fma cx16 sse
+ 4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm 
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce 
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall 
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
+ pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save 
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
+ 
+ [2] - sha_ni: SHA1/SHA256 Instruction Extensions
+ 
+ [3] - https://en.wikipedia.org/wiki/Ryzen
+ ...
+ All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, 
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
+ ...
+ 
+ * Program to performs the CPUID check:
+ 
+ Reference :
+ https://software.intel.com/en-us/articles/intel-sha-extensions
+ 
+ ... Availability of the Intel® SHA Extensions on a particular processor
+ can be determined by checking the SHA CPUID bit in CPUID.(EAX=07H,
+ ECX=0):EBX.SHA [bit 29]. The following C function, using inline
+ assembly, performs the CPUID check:
+ 
+ --
+ int CheckForIntelShaExtensions() {
+int a, b, c, d;
+ 
+// Look for CPUID.7.0.EBX[29]
+// EAX = 7, ECX = 0
+a = 7;
+c = 0;
+ 
+asm volatile ("cpuid"
+ :"=a"(a), "=b"(b), "=c"(c), "=d"(d)
+ :"a"(a), "c"(c)
+);
+ 
+// Intel® SHA Extensions feature bit is EBX[29]
+return ((b >> 29) & 1);
+ }
+ --
+ 
+ On CPU with sha_ni the program return "1". Otherwise it return "0".
+ 
+ [Test Case]
+ 
+  * Reproducible with Xenial/Zesty/Artful release.
+   
+  * Generated a checksum of a big file (e.g. 5GB file) with openssl
+  $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile 
+ SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8
+ 
+ real  0m12.835s
+ user  0m12.344s
+ sys   0m0.484s
+ 
+ 
+ [Regression Potential] 
+ 
+  * None expected, it basically allow openssl to take benefit of sha
+ extension potential (mostly performance-wise) if AMD cpu has the
+ capability.
+ 
+  * Generated a checksum of a big file (e.g. 5GB file) with openssl
+  $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile 
+ SHA256(/var/tmp/5Gfile)= 
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8
+ 
+ real  0m3.471s
+ user  0m2.956s
+ sys   0m0.516s
+ 
+ 
+ [Other Info]
+  
+ * Debian Bug : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861145
+ 
+ * Upstream Repository : https://github.com/openssl/openssl.git
+ 
+ * Upstream Commits :
+ 1aed5e1 crypto/x86*cpuid.pl: move extended feature detection.
+ ## This fix moves extended feature detection past basic feature detection 
where it belongs.
+ 
+ f8418d8 crypto/x86_64cpuid.pl: move extended feature detection upwards.
+ ## This commit for x86_64cpuid.pl addressed the problem, but messed up 
processor vendor detection.
+ 
+ [Original Description]
+ 
  * Context
  
  AMD added support in their processors for SHA Extensions[1] (CPU flag:
  sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit
  only (Confirmed with AMD representative). Current OpenSSL version in
  Ryzens still calls SHA for SSSE3 routine as result a number of
  extensions were effectively masked on Ryzen and shows no improvement.
  
  [1] /proc/cpuinfo
  processor : 0
  vendor_id : AuthenticAMD
  cpu family: 23
  model : 1
  model name: AMD Ryzen 5 1600 Six-Core Processor
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 

[Touch-packages] [Bug 1644363] Re: [trusty/arm64] binutils segfaults on bash gettext configure test

2017-04-25 Thread Julian Andres Klode
** Changed in: binutils (Ubuntu Trusty)
   Status: Confirmed => Fix Committed

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

Title:
  [trusty/arm64] binutils segfaults on bash gettext configure test

Status in binutils package in Ubuntu:
  Invalid
Status in eglibc package in Ubuntu:
  New
Status in binutils source package in Trusty:
  Fix Committed
Status in eglibc source package in Trusty:
  New

Bug description:
  On arm64, the bash gettext configure test causes binutils to segv:

  configure:8453: gcc -o conftest -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=
  format-security -Wall -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -static conftest.c
  >&5
  conftest.c: In function 'main':
  conftest.c:116:8: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
  ^
  conftest.c:116:29: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
   return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
   ^
  collect2: error: ld terminated with signal 11 [Segmentation fault], core 
dumped
  configure:8453: $? = 1
  configure: failed program was:
  | /* confdefs.h */
  | #define PACKAGE_NAME "bash"
  | #define PACKAGE_TARNAME "bash"
  | #define PACKAGE_VERSION "4.3-release"
  | #define PACKAGE_STRING "bash 4.3-release"
  | #define PACKAGE_BUGREPORT "bug-b...@gnu.org"
  | #define PACKAGE_URL ""
  | #define ALIAS 1
  | #define PUSHD_AND_POPD 1
  | #define RESTRICTED_SHELL 1
  | #define PROCESS_SUBSTITUTION 1
  | #define PROMPT_STRING_DECODE 1
  | #define SELECT_COMMAND 1
  | #define HELP_BUILTIN 1
  | #define ARRAY_VARS 1
  | #define DPAREN_ARITHMETIC 1
  | #define BRACE_EXPANSION 1
  | #define COMMAND_TIMING 1
  | #define EXTENDED_GLOB 1
  | #define EXTGLOB_DEFAULT 0
  | #define COND_COMMAND 1
  | #define COND_REGEXP 1
  | #define COPROCESS_SUPPORT 1
  | #define ARITH_FOR_COMMAND 1
  | #define NETWORK_REDIRECTIONS 1
  | #define PROGRAMMABLE_COMPLETION 1
  | #define DEBUGGER 1
  | #define CASEMOD_ATTRS 1
  | #define CASEMOD_EXPANSIONS 1
  | #define GLOBASCII_DEFAULT 0
  | #define MEMSCRAMBLE 1
  | #define STDC_HEADERS 1
  | #define HAVE_SYS_TYPES_H 1
  | #define HAVE_SYS_STAT_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_MEMORY_H 1
  | #define HAVE_STRINGS_H 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_STDINT_H 1
  | #define HAVE_UNISTD_H 1
  | #define __EXTENSIONS__ 1
  | #define _ALL_SOURCE 1
  | #define _GNU_SOURCE 1
  | #define _POSIX_PTHREAD_SEMANTICS 1
  | #define _TANDEM_SOURCE 1
  | #define READLINE 1
  | #define HISTORY 1
  | #define BANG_HISTORY 1
  | #define _GNU_SOURCE 1
  | #define HAVE_STRINGIZE 1
  | #define HAVE_LONG_DOUBLE_WIDER 1
  | #define HAVE_LONG_DOUBLE 1
  | #define PROTOTYPES 1
  | #define __PROTOTYPES 1
  | #define restrict __restrict
  | #define HAVE_ALLOCA_H 1
  | #define HAVE_ALLOCA 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_SYS_PARAM_H 1
  | #define HAVE_SYS_TIME_H 1
  | #define HAVE_GETPAGESIZE 1
  | #define HAVE_MMAP 1
  | #define INTDIV0_RAISES_SIGFPE 0
  | #define HAVE_INTTYPES_H_WITH_UINTMAX 1
  | #define HAVE_STDINT_H_WITH_UINTMAX 1
  | #define HAVE_UNSIGNED_LONG_LONG 1
  | #define HAVE_UINTMAX_T 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_ARGZ_H 1
  | #define HAVE_LIMITS_H 1
  | #define HAVE_LOCALE_H 1
  | #define HAVE_NL_TYPES_H 1
  | #define HAVE_MALLOC_H 1
  | #define HAVE_STDDEF_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_SYS_PARAM_H 1
  | #define HAVE_FEOF_UNLOCKED 1
  | #define HAVE_FGETS_UNLOCKED 1
  | #define HAVE_GETC_UNLOCKED 1
  | #define HAVE_GETCWD 1
  | #define HAVE_GETEGID 1
  | #define HAVE_GETEUID 1
  | #define HAVE_GETGID 1
  | #define HAVE_GETUID 1
  | #define HAVE_MEMPCPY 1
  | #define HAVE_MUNMAP 1
  | #define HAVE_PUTENV 1
  | #define HAVE_SETENV 1
  | #define HAVE_SETLOCALE 1
  | #define HAVE_LOCALECONV 1
  | #define HAVE_STPCPY 1
  | #define HAVE_STRCASECMP 1
  | #define HAVE_STRDUP 1
  | #define HAVE_STRTOUL 1
  | #define HAVE_TSEARCH 1
  | #define HAVE___ARGZ_COUNT 1
  | #define HAVE___ARGZ_STRINGIFY 1
  | #define HAVE___ARGZ_NEXT 1
  | #define HAVE___FSETLOCKING 1
  | #define HAVE_ICONV 1
  | #define ICONV_CONST
  | #define HAVE_LANGINFO_CODESET 1
  | #define HAVE_LC_MESSAGES 1
  | /* end confdefs.h.  */
  | #include 
  | extern int _nl_msg_cat_cntr;
  | extern int *_nl_domain_bindings;
  | int
  | main ()
  | {
  | bindtextdomain ("", "");
  | return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + 
*_nl_domain_bindings
  |   ;
  |   return 0;
  | }
  configure:8461: result: no

  [Test case]
  Build 

[Touch-packages] [Bug 1532855] Re: add-apt-repository exits with 0 even when adding key failed

2017-04-25 Thread Robie Basak
I see dep8 failures in software-properties 0.96.20.6. But a recent test
against 0.96.20.5 succeeded, which suggests to me that it is a
regression caused by 0.96.20.6. I don't see anything obvious in the diff
that could cause this, but I think it warrants further investigation.
Please could you take a look?

See http://autopkgtest.ubuntu.com/packages/s/software-
properties/xenial/i386 and http://autopkgtest.ubuntu.com/packages/s
/software-properties/xenial/amd64

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

Title:
  add-apt-repository exits with 0 even when adding key failed

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  Fix Committed
Status in software-properties source package in Yakkety:
  Fix Released

Bug description:
  add-apt-repository exits happily even if it failed adding the key:

  $ sudo env LANGUAGE=en add-apt-repository ppa:launchpad/buildd-staging -k 
hkp://bad-server/
   Buildd staging packages for Launchpad. New packages are staged here for 
testing on the staging PPA buildds.
   More info: https://launchpad.net/~launchpad/+archive/ubuntu/buildd-staging
  Press [ENTER] to continue or ctrl-c to cancel adding it

  gpg: keyring `/tmp/tmp3246v7n8/secring.gpg' created
  gpg: keyring `/tmp/tmp3246v7n8/pubring.gpg' created
  gpg: requesting key 0A5174AF from hkp server bad-server
  ?: bad-server: Host not found
  gpgkeys: HTTP fetch error 7: couldn't connect: Success
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  gpg: keyserver communications error: keyserver unreachable
  gpg: keyserver communications error: public key not found
  gpg: keyserver receive failed: public key not found

  $ echo $?
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-common 0.96.17
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 11 17:17:56 2016
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to xenial on 2015-10-28 (74 days ago)

  Related bugs:
   * bug 1671566 when gpg key add fails, entry is still added to sources.list

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

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


[Touch-packages] [Bug 1553592] Re: 16.04 casper 15_autologin file contains obsolete lightdm configuration

2017-04-25 Thread Sebastien Bacher
** Tags added: rls-z-incoming

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

Title:
  16.04 casper 15_autologin file contains obsolete lightdm configuration

Status in accountsservice package in Ubuntu:
  Triaged
Status in casper package in Ubuntu:
  Triaged

Bug description:
  /usr/share/initramfs-tools/scripts/casper-bottom/15autologin

  the lightdm section of the file contains a lightdm configuration that
  is incorrect for 15.10 and later

  for example it writes out /root/etc/lightdm/lightdm.conf

  according to the lightdm wiki this should be
  /root/etc/lightdm/lightdm.conf.d/xyz.conf

  Additionally using [SeatDefaults] is wrong.  Again according the wiki
  [SeatDefaults] is obsolete and should be [Seat:*]

  Think this is probably why manual live CD creators and those who use
  Pinguy ISO Builder cannot create a lightdm autologin live CD

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.17.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Mar  5 21:07:13 2016
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1374222] Re: path for policy files changed

2017-04-25 Thread Olivier Tilloy
** Changed in: chromium-browser (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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1374222

Title:
  path for policy files changed

Status in apparmor package in Ubuntu:
  Invalid
Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Between package version: 37.0.2062.94-0ubuntu0.12.04.1~pkg909
  and package version: 37.0.2062.120-0ubuntu0.12.04.1~pkg917

  The path checked by Ubuntu's chromium-browser package for policy files
  has changed.  This results in administrator mandated settings not
  being applied, which should be considered a security vulnerability.

  In previous versions of the package, policy files were read from: 
/etc/chromium-browser/policies
  In the new version of the package, it is reading policy files from: 
/etc/chromium/policies

  The new package version has dropped the following line from its debian/rules 
file:
  sed -i 's,/etc/chromium/policies,/etc/chromium-browser/policies,' \
  $(DEB_TAR_SRCDIR)/chrome/common/chrome_paths.cc

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

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


[Touch-packages] [Bug 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind

2017-04-25 Thread Dan Streetman
*** This bug is a duplicate of bug 1447715 ***
https://bugs.launchpad.net/bugs/1447715

This was fixed via update to isc-dhcp in bug 1633479.  Please see that
bug for the specific isc-dhcp version number needed to fix the bug.

** This bug has been marked a duplicate of bug 1447715
   dhclient -6: Can't bind to dhcp address: Cannot assign requested address

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

Title:
  inet6 dhcp doesn't wait for link-local address to leave tentative -
  dhclient fails to bind

Status in ifupdown package in Ubuntu:
  Triaged

Bug description:
  =
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  ifupdown:
Installed: 0.8.10ubuntu1
Candidate: 0.8.10ubuntu1
  =

  With an /etc/network/interfaces file containing:

  auto eno16780032
  iface eno16780032 inet dhcp
  iface eno16780032 inet6 dhcp

  On boot, ifup starts 'dhclient -6' before the link local address has
  completed Duplicate Address Discovery (the address is marked
  'tentative').  In turn, dhclient reports 'Can't bind to dhcp address:
  Cannot assign requested address', and fails almost immediately.

  It would seem that either wait-for-ll6.sh should wait for the link
  local address to come up AND stop being tentative, or the dhcp method
  for inet6 should call settle-dad.sh after wait-for-ll6?

  This is partly a race condition, so on slower devices the dad may
  complete by the time dhclient has got started, however I can regularly
  reproduce this on a virtual machine.

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

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


[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

2017-04-25 Thread Julian Andres Klode
Dropping the tag. Boot time can change randomly. Desktop start does
*not* depend on apt timer start, and timer now depends on network-online
in order to actually work. So yes, it actually does something now, so it
is of course slower.

** Tags removed: block-proposed

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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


[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

2017-04-25 Thread Harry
OK,
I have now tested this new apt (1.4.1) against the old version (1.4).
My setup is using solely systemd (with no upstart nor cgmanager installed).
I have fast SSD's, so my normal booting time is about 4 seconds.

Now after upgrading to apt 1.4.1 the booting time to GDM increased with about 5 
to 8 seconds.
During boot the computer stops just before GDM is starts.
I think systemd now waits till network is OK.

As a workaround, downgrading back to apt 1.4 solves the issue and
booting time to GDM is 4 seconds.

This should be fixed and till that this update kept in proposed.

** Tags added: block-proposed

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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


[Touch-packages] [Bug 1562002] Re: Nautilus: lag after choosing action in top right menu

2017-04-25 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.18.9-1ubuntu3.3

---
gtk+3.0 (3.18.9-1ubuntu3.3) xenial; urgency=medium

  * Backport upstream patch to fix lagging and visual issues in Nautilus
(toggled-not-clicked.patch, LP: #1562002).

 -- Dmitry Shachnev   Thu, 23 Mar 2017 22:44:18
+0300

** Changed in: gtk+3.0 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Nautilus: lag after choosing action in top right menu

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Xenial:
  Fix Released

Bug description:
  # Impact
  This is known to affect Nautilus, but can potentially affect other 
applications too (the upstream bug has an example test app attached).

  See also the duplicate bug 1644393, which is another appearance of the
  same bug but with other symptoms.

  # Proposed Fix
  The proposed fix is an upstream commit taken from gtk-3-20 branch:
  https://git.gnome.org/browse/gtk+/commit/?id=10c3a2483635d1c1

  # Test Case
  https://bugzilla.gnome.org/show_bug.cgi?id=769287#c0 has a test case.

  # Regression Potential
  The bug is fixed in GTK+ 3.20.9, so the fix was already present in the 
version that shipped with Yakkety. I am not aware of any regressions.

  -
  choosing action like New Tab, New Folder, Select Items Matching, will make 
nautilus lag (unresponsive)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 25 20:52:21 2016
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'890x550+685+36'"
  InstallationDate: Installed on 2016-03-24 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 
(20160323.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

2017-04-25 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 1.4.1

---
apt (1.4.1) unstable; urgency=medium

  [ Julian Andres Klode ]
  * systemd: Rework timing and add After=network-online (LP: #1615482)
  * debian/rules: Actually invoke dh_clean in override_dh_clean

  [ Unit 193 ]
  * apt-ftparchive: Support '.ddeb' dbgsym packages

 -- Julian Andres Klode   Mon, 24 Apr 2017 18:47:55
+0200

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

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


[Touch-packages] [Bug 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service

2017-04-25 Thread Launchpad Bug Tracker
This bug was fixed in the package ido - 13.10.0+14.04.20170403-0ubuntu1

---
ido (13.10.0+14.04.20170403-0ubuntu1) trusty; urgency=medium

  * IdoCalendarMenuItem: disconnect from parent signals on item
destruction (LP: #1506427)

 -- Marco Trevisan (Treviño)   Mon, 03 Apr 2017 16:09:37
+

** Changed in: ido (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  Using calendar with keys might cause Indicator-datetime to crash
  unity-panel-service

Status in ido package in Ubuntu:
  Fix Released
Status in ido source package in Trusty:
  Fix Released
Status in ido source package in Xenial:
  Fix Released
Status in ido source package in Yakkety:
  Fix Released

Bug description:
  [Impact] 
  Unity panel service crashes (removing indicators from panel) when calendar 
menu is opened and there are some key presses.

  [Test Case]
  This is a quite random bug that is not easy to reproduce, it happens 
sometimes that you open the indicator-datetime and after a keypress the panel 
crashes.

  [Regression Potential]
  Nothing expected, but calendar item in datetime might behave differently on 
key-presses.
  Although the fix is quite safe since we're just ensuring that we disconnect 
from parent widget signals on menuitem destruction.

  ===

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity.  This problem was most recently seen with version
  7.3.2+15.10.20151002.2-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435
  contains more details.

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

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


[Touch-packages] [Bug 1454668] Re: Failed to upgrade/reinstall libreoffice-common

2017-04-25 Thread Jean-Francis Roy
I had the same issue with different packages (namely texlive-related
packages) during a distribution update from 16.10 to 17.04, resulting in
an incomplete upgrade. After a couple hours of trying to fix the issues,
I finally suspected Sophos, and disabling/enabling on-access scanning
worked around the problem.

This bug is not only related to libreoffice-commons but to other
packages as well, but unfortunately I didn't note what packages they
were.

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

Title:
  Failed to upgrade/reinstall libreoffice-common

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  A few days ago I noticed a problem during a normal apt-get upgrade -
  the libreoffice-common package failed to install:

  dpkg: error processing archive 
/var/cache/apt/archives/libreoffice-common_1%3a4.2.8-0ubuntu2_all.deb 
(--unpack):
   unable to open 
'/usr/lib/libreoffice/share/xslt/import/spreadsheetml/spreadsheetml2ooo.xsl.dpkg-new':
 Operation not permitted

   Initially I assumed it was a download problem so I cleaned the cache
  and retried. I also checked disc space: 12GB free, inodes 1035169
  free. I removed libreoffice entirely (purge) and reinstalled. Up to
  then, libreoffice was working, after the reinstallation failed with
  the same error it was not there. I noted there were two systems with
  the same problem, both i386, and three systems without the problem,
  two 64bit, and one i386. I haven't tried the purge/reinstall on the
  second system because one system with no office software is already
  one too many.

  I've followed the instructions on:
  https://help.ubuntu.com/community/PackageManagerTroubleshootingProcedure
  and the Terminal output follows:

  allan@finwhale:~$ ubuntu-support-status
  Support status summary of 'finwhale':

  You have 9 packages (0.5%) supported until February 2016 (9m)
  You have 29 packages (1.5%) supported until February 2015 (9m)
  You have 1815 packages (94.3%) supported until May 2019 (5y)
  You have 34 packages (1.8%) supported until May 2017 (3y)

  You have 0 packages (0.0%) that can not/no-longer be downloaded
  You have 37 packages (1.9%) that are unsupported

  Run with --show-unsupported, --show-supported or --show-all to see more 
details
  allan@finwhale:~$ cat /etc/dpkg/dpkg.cfg.d/multiarch
  cat: /etc/dpkg/dpkg.cfg.d/multiarch: No such file or directory
  allan@finwhale:~$ dpkg --print-foreign-architectures
  allan@finwhale:~$ sudo grep -R proxy /etc/apt/*
  [sudo] password for allan: 
  allan@finwhale:~$ grep proxy  /etc/environment
  allan@finwhale:~$ echo $http_proxy

  allan@finwhale:~$ echo $ftp_proxy

  allan@finwhale:~$ grep proxy /etc/bash.bashrc
  allan@finwhale:~$ grep proxy ~/.bashrc
  allan@finwhale:~$ cat /etc/apt/apt.conf
  cat: /etc/apt/apt.conf: No such file or directory
  allan@finwhale:~$ sudo fuser -vvv /var/lib/dpkg/lock
  allan@finwhale:~$ sudo fuser -vvv /var/cache/apt/archives/lock
  allan@finwhale:~$ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"
  allan@finwhale:~$ uname -a
  Linux finwhale 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:23:46 UTC 2014 
i686 i686 i686 GNU/Linux
  allan@finwhale:~$ sudo rm /var/lib/apt/lists/lock 
  allan@finwhale:~$ sudo rm  /var/cache/apt/archives/lock
  allan@finwhale:~$ sudo rm /var/lib/dpkg/lock
  allan@finwhale:~$ sudo cp -arf /var/lib/dpkg /var/lib/dpkg.backup
  allan@finwhale:~$ allan@finwhale:~$ sudo mv /var/lib/dpkg/status 
/var/lib/dpkg/status-bad
  allan@finwhale:~$ sudo cp /var/lib/dpkg/status-old /var/lib/dpkg/status  ||  
sudo cp /var/backups/apt.extended_states.0 /var/lib/dpkg/status
  allan@finwhale:~$ sudo mv /var/lib/dpkg/available /var/lib/dpkg/available-bad
  allan@finwhale:~$ sudo cp /var/lib/dpkg/available-old /var/lib/dpkg/available
  allan@finwhale:~$ sudo rm -rf /var/lib/dpkg/updates/*
  allan@finwhale:~$ sudo rm -rf /var/lib/apt/lists
  allan@finwhale:~$ sudo rm /var/cache/apt/*.bin
  allan@finwhale:~$ sudo mkdir /var/lib/apt/lists
  allan@finwhale:~$ sudo mkdir /var/lib/apt/lists/partial
  allan@finwhale:~$ LANG=C;sudo apt-get clean
  allan@finwhale:~$ LANG=C;sudo apt-get autoclean
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  allan@finwhale:~$ LANG=C;sudo apt-get --purge autoremove
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: The package libreoffice-common needs to be reinstalled, but I can't find 
an archive for it.
  allan@finwhale:~$ allan@finwhale:~$ LANG=C;sudo apt-get --fix-missing update 
-o APT::Cache-Limit=1
  Ign http://archive.ubuntu.com trusty InRelease
  Ign http://archive.ubuntu.com trusty-updates InRelease
  Ign http://archive.ubuntu.com trusty-security InRelease
  Get:1 

[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day

2017-04-25 Thread Harry
Added the tag: block-proposed.

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

Title:
  apt-daily timer runs at random hours of the day

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a
  systemd timer instead of a cron.daily job. This is a good thing,
  decoupling apt daily runs from the rest of cron, and ensuring other
  cron.daily jobs are not blocked by up to half an hour by the default
  settings of unattended-upgrades.

  However the policy chosen is to have the apt daily script run at a
  random hour of the day in a wrong headed attempt to reduce server
  load. This has the side effect of running unattended-upgrades at
  random hours of the day — such as business hours — rather than being
  confined to between 6:25am and 6:55am, using the defaults.

  A better policy would be to have the script activate at 6:00am plus an
  interval of 20 minutes at one second intervals reducing the impact of
  timezone population spikes, while still allowing unattended-upgrades
  to run within a predictable interval, before 7am.

  At the very least, some sort of note in the NEWS file detailing the
  new behaviour would be welcome.

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

-- 
Mailing list: https://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   >