[Touch-packages] [Bug 1696301] [NEW] Enabling the EQ causes audio corruption and stutter

[Paul]

Public bug reported:

Enabling pulseaudio-equalizer causes audio corruption and stutter
globally, including with bluetooth streaming, despite using little CPU
time.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: pulseaudio-equalizer 1:10.0-1ubuntu2
Uname: Linux 4.11.0-041100-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  paulh 26275 F pulseaudio
 /dev/snd/controlC0:  paulh 26275 F pulseaudio
CurrentDesktop: KDE
Date: Wed Jun  7 14:58:21 2017
InstallationDate: Installed on 2017-01-05 (153 days ago)
InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to zesty on 2017-04-14 (53 days ago)
dmi.bios.date: 10/29/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.1C
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8133
dmi.board.vendor: HP
dmi.board.version: KBC Version 98.0E
dmi.chassis.asset.tag: 5CG6124XBK
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2017-06-07T14:45:08.795195

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


** Tags: amd64 apport-bug zesty

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

Title:
  Enabling the EQ causes audio corruption and stutter

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Enabling pulseaudio-equalizer causes audio corruption and stutter
  globally, including with bluetooth streaming, despite using little CPU
  time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio-equalizer 1:10.0-1ubuntu2
  Uname: Linux 4.11.0-041100-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  paulh 26275 F pulseaudio
   /dev/snd/controlC0:  paulh 26275 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jun  7 14:58:21 2017
  InstallationDate: Installed on 2017-01-05 (153 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to zesty on 2017-04-14 (53 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1C
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8133
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 98.0E
  dmi.chassis.asset.tag: 5CG6124XBK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1C:bd10/29/2015:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn8133:rvrKBCVersion98.0E:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-06-07T14:45:08.795195

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Nicholas Stommel]

Tim, I have a question for you. When you connect through 
network-manager-openconnect-gnome, and type
systemd-resolve --status, what is your link name called? Something like 'tun0' 
or 'tap1' or the like?

Because I've been looking around at the openconnect wiki at 
http://www.infradead.org/openconnect/building.html, and it seems like 
openconnect requires tun/tap drivers. So theoretically, it should have worked 
with the original patch containing just the conditional expression:
if (link_type == NM_LINK_TYPE_TUN || link_type == NM_LINK_TYPE_TAP)
As in, this should evaluate to true as the link should be of type tun or tap.

It seems like the updated patch containing the conditional expression
if (link_type == NM_LINK_TYPE_TUN || link_type == NM_LINK_TYPE_TAP || link_type 
== NM_LINK_TYPE_GRE || link_type == NM_LINK_TYPE_GRETAP)
might, however, help address users of 
network-manager-vpnc/network-manager-vpnc-gnome. If anyone uses 
network-manager-vpnc/network-manager-vpnc-gnome, let me know if the newer patch 
containing the cases for NM_LINK_TYPE_GRE and NM_LINK_TYPE_GRETAP fixes DNS 
leaks for you on a Cisco PPTP/IPsec VPN. I am unable to test this out as I 
don't have access to any such Cisco VPN services.

Anyway, if the network manager doesn't correctly register the
openconnect interface as being link type TUN or TAP, I don't really know
how to fix it as that could be a problem on network-manager-
openconnect's end or the result of some way it doesn't properly notify
the network manager.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1687601] Re: package udev 229-4ubuntu17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

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

Title:
  package udev 229-4ubuntu17 failed to install/upgrade: подпроцесс
  установлен сценарий post-installation возвратил код ошибки 1

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  An error occurred while updating the program. I do not know anything
  else.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Tue May  2 13:51:44 2017
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2016-12-15 (137 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: Hewlett-Packard HP ProBook 4720s
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic 
root=UUID=a784bf3c-f5a1-4b14-9c07-22b064da1362 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: systemd
  Title: package udev 229-4ubuntu17 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68AZZ Ver. F.08
  dmi.board.name: 1411
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 57.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68AZZVer.F.08:bd06/29/2010:svnHewlett-Packard:pnHPProBook4720s:pvr:rvnHewlett-Packard:rn1411:rvrKBCVersion57.1D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4720s
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[Daniel Axtens]

Hi Mao,

I have successfully verified that with the patched kernel and the Xorg
config, X starts fine.

Do you need assistance getting that patch upstream, or is that something
HiSilicon/the HWE team can do?

Regards,
Daniel

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

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

[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[Daniel Axtens]

Hi Dann,

Ignore that, I didn't realise I needed the -extra package.

Regards,
Daniel

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

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

[Touch-packages] [Bug 1696298] [NEW] leap-seconds.list file expires 28 June 2017

[Ryan Kingsbury]

Public bug reported:

The currently published tzdata package for supported distributions
contains a leap-seconds.list file that expires on 28 June 2017 and that
was based on data available up through IERS Bulletin C52.

IERS Bulletin C53 was published on Jan 9 2017 confirming that a June 30
2017 would not be issued. I'm not sure what serves as the upstream data
source for this package, but both IEFT and the eggertz tz repo have a
leap-seconds.list file that incorporates Bulletin C53.

https://www.ietf.org/timezones/data/leap-seconds.list
https://github.com/eggert/tz/blob/master/leap-seconds.list

Would it be possible to get the package updated to include these more
recent files? Some applications make use of the expiration data in this
file and will raise exceptions to the user if it has gone stale.

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

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

Title:
  leap-seconds.list file expires 28 June 2017

Status in tzdata package in Ubuntu:
  New

Bug description:
  The currently published tzdata package for supported distributions
  contains a leap-seconds.list file that expires on 28 June 2017 and
  that was based on data available up through IERS Bulletin C52.

  IERS Bulletin C53 was published on Jan 9 2017 confirming that a June
  30 2017 would not be issued. I'm not sure what serves as the upstream
  data source for this package, but both IEFT and the eggertz tz repo
  have a leap-seconds.list file that incorporates Bulletin C53.

  https://www.ietf.org/timezones/data/leap-seconds.list
  https://github.com/eggert/tz/blob/master/leap-seconds.list

  Would it be possible to get the package updated to include these more
  recent files? Some applications make use of the expiration data in
  this file and will raise exceptions to the user if it has gone stale.

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

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

[Touch-packages] [Bug 1696297] [NEW] system program report prompt on each reboot

[Anthony Zepeda]

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

Public bug reported:

package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
subprocess installed post-installation script returned error exit status
128

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
Uname: Linux 4.10.17-041017-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
Date: Tue Jun  6 20:13:49 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-07 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  system program report prompt on each reboot

Status in gconf package in Ubuntu:
  New

Bug description:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  Uname: Linux 4.10.17-041017-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Tue Jun  6 20:13:49 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-07 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1696297] Re: system program report prompt on each reboot

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  system program report prompt on each reboot

Status in gconf package in Ubuntu:
  New

Bug description:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  Uname: Linux 4.10.17-041017-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Tue Jun  6 20:13:49 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-07 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1567796] Re: It is sometimes unable to find DELL WWAN module.

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Importance: Undecided => Low

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

Title:
  It is sometimes unable to find DELL WWAN module.

Status in OEM Priority Project:
  Incomplete
Status in modemmanager package in Ubuntu:
  New

Bug description:
  I have a DELL WWAN module (DW5580) on my platform. Normally it could
  be detect and used in Ubuntu 16.04 daily image. However it is
  sometimes unusable and can not be detected.

  After debugging, we found there is an upstream patch that can fix the
  issue:

  
https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=8a386218690aeff7e2c923a14f91da7bbc046ed2

  Please merge the fix to modem manager to fix the issue.

  Ubuntu Xenial (daily image)
  Release: 16.04
  modemmanager:
    Installed: 1.4.12-1ubuntu1
    Candidate: 1.4.12-1ubuntu1
    Version table:
   *** 1.4.12-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1586941] Re: Randomly segfault on BYT with 4.4 kernel

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Importance: High => Medium

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

Title:
  Randomly segfault on BYT with 4.4 kernel

Status in OEM Priority Project:
  Confirmed
Status in upstart :
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  
  We have a randomly crash bug when using 14.04 (trusty) upstart 
(1.12.1-0ubuntu4.2).

  We've tried the workarounds of LP:1447756 but it doesn't work.
  Also the test case doesn't crash. So we think this is a new bug.

  The bug is also happened on very early stages. And inside the
  installer, it crashes more often then the system. We see it core
  dumped in the installer, but not about to get the core file because
  the squashfs only keeps file in the memory.

  Also when run on system, the filesystem seems to be read-only then so
  there's also no logs.

  We are using 4.4 kernel (linux-image-4.4.0-22-generic
  4.4.0-22.40~14.04.1)

  I'll paste some images and logs after.

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: External monitor connecting problem on Intel graphics card

[Kai-Heng Feng]

Most kernel drivers are in extra package, i.e. linux-image-
extra-4.4.0-78-generic.

There are only two commits between -72 to -78:
commit 2fce21649c85703a63e9c70ccc6e3b9caa813041
Author: Mika Kuoppala 
Date:   Wed Feb 15 15:52:59 2017 +0200

drm/i915: Avoid tweaking evaluation thresholds on Baytrail v3

commit 81ac6f8ab65e3bc8311af92cf31326dba3135364
Author: Chris Wilson 
Date:   Mon Mar 13 17:06:17 2017 +

drm/i915: Stop using RP_DOWN_EI on Baytrail

Both commits' change are limited to Baytrail. Yours is Haswell so I
don't think this bug is related to Linux kernel here.

-- 
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 on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

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

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

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

[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[Daniel Axtens]

Hi Dann,

I have tried to boot the HiSilicon board with a zesty kernel (and with a
patched zesty kernel) and it boots, gets to the following, and then
hangs without displaying a prompt:

[9.900239] async_tx: api initialized (async)
[9.991929] Btrfs loaded, crc32c=crc32c-arm64-hw
[   55.474203] hidraw: raw HID events driver (C) Jiri Kosina
[   55.483000] usbcore: registered new interface driver usbhid
[   55.488571] usbhid: USB HID core driver
[ME] Fault detect start!
[ME] Fault detect start!

Is there anything different between the pearl kernels and the zesty
kernel that would make the prompt show up and/or avoid the hang?

Regards,
Daniel

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Nicholas Stommel]

Jordi, Sure thing, glad I could help. :)
I wonder if somebody can figure out how to help Tim with 
network-manager-openconnect. I tried adding two more conditions for cisco vpn 
gre connections but apparently it didn't work or those aren't the kind of links 
used. Not sure how to address that because the innards of network-manager and 
how it interacts with plugins is fairly complex, but maybe someone could modify 
the patch to account for that.
For anyone just using network-manager-openvpn, the first patch and .deb 
uploaded are all that is needed.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Jordi Miralles]

Hi Nicholas,

I upgraded to 17.04, installed your patch and I can now say that dns
leaks when using network-manager-openvpn + network-manager-openvpn-gnome
are gone for good now. Awesome work, thanks.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1211102] Re: Get rid of 0.5s latency when playing audio over Bluetooth with A2DP

[Daniel van Vugt]

mokrates: Could you please log a new bug with your system details and a
full description of the persisting problems? ->
https://bugs.launchpad.net/ubuntu/+source/bluez/+filebug

It's easier if we're dealing with bug reports logged against still-
supported versions of Ubuntu.

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

Title:
  Get rid of 0.5s latency when playing audio over Bluetooth with A2DP

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 13.04
  Release:  13.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  bluez:
Instalados: 4.101- 0ubuntu8b1
Candidato:  4.101-0ubuntu8b1
Tabla de versión:
   *** 4.101-0ubuntu8b1 0
  500 http://es.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  The audio always is sync when i listen music on my bluetooth device 
  If i listen music or have a videoconference with skype.. it receive audio 
perfectly without delay.

  4) What happened instead
   I experience a half a second delay when playing audio over Bluetooth with 
A2DP.
  This makes watching movies not possible as the sound is not synchronised with 
the video.

  + If i listen music, then stop about 5 minutes and then restart to listen 
music, it gets work bad.
  + If i get a skype videoconference, it gets too much delay.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: bluez 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Mon Aug 12 01:24:24 2013
  InstallationDate: Installed on 2013-07-13 (29 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK Computer Inc. UX31E
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=89d221ec-829a-456e-963d-ec7ac2c7d47d ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash rootfstype=ext4 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31E.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31E.210:bd12/26/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UX31E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 74:2F:68:CE:17:57  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:407502 acl:14820 sco:0 events:8796 errors:0
TX bytes:7391611 acl:8717 sco:0 commands:45 errors:0

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

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

[Touch-packages] [Bug 1692136] Re: Backport "core/timer: downgrade message about random time addition (#5229)".

[Dimitri John Ledkov]

** Description changed:

+ [Impact]
+ 
+  * Systemd spams logs too much with pointless messages
+ 
+ [Test Case]
+ 
+  * Boot system and observe no pointless messages of scheduling random
+ timers for things at a given offset
+ 
+ [Regression Potential]
+ 
+  * Low, this patch simply changes the priority of the message from info
+ to debug.
+ 
+ [Original bug report]
+ 
  Please backport upstream systemd v233 commit
  382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade message
  about random time addition (#5229)".
  
https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1
  
  This removes "random time" messages flooding dmesg.
  
  The spew was introduced with v229 commit "core: add new RandomSec=
  setting for time units".
  
https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07
  
  trusty based off v204 is not affected.
  
  xenial based off v229, yakkety based off v231, and zesty based off v232
  need this fix.
  
  artful based off v233 has the fix.

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

Title:
  Backport "core/timer: downgrade message about random time addition
  (#5229)".

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

Bug description:
  [Impact]

   * Systemd spams logs too much with pointless messages

  [Test Case]

   * Boot system and observe no pointless messages of scheduling random
  timers for things at a given offset

  [Regression Potential]

   * Low, this patch simply changes the priority of the message from
  info to debug.

  [Original bug report]

  Please backport upstream systemd v233 commit
  382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade
  message about random time addition (#5229)".
  
https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1

  This removes "random time" messages flooding dmesg.

  The spew was introduced with v229 commit "core: add new RandomSec=
  setting for time units".
  
https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07

  trusty based off v204 is not affected.

  xenial based off v229, yakkety based off v231, and zesty based off
  v232 need this fix.

  artful based off v233 has the fix.

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

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

[Touch-packages] [Bug 1695876] Re: German Documentation file displays incorrect CUPS version

[Bug Watch Updater]

** Changed in: cups
   Status: New => Fix Released

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

Title:
  German Documentation file displays incorrect CUPS version

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  New

Bug description:
  The /doc/de/index.html.in file in the package source has an incorrect
  version number written into a header instead of using '@CUPS_VERSION@'
  to populate this file as in the other languages' version of the same
  file, seemingly resulting in /usr/share/cups/doc-root/de/index.html
  having the wrong version once CUPS is installed:

  ...
  

  CUPS 2.0.2
  ...

  instead of:

  ...
  

  CUPS @CUPS_VERSION@
  ...

  resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown.

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Nicholas Stommel]

Sorry to here that, I'm frankly not sure what to do about that then :/ 
At the very least the original patch fixes stuff for openvpn, which is good. 
Perhaps someone else could figure out the cisco openconnect thing.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1696269] [NEW] package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package ke

[Rajesh Kanna]

Public bug reported:

when i try to upgrade the package i got this issue

ProblemType: Package
DistroRelease: Debian 9
Package: console-setup-linux 1.108ubuntu15.2
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Wed Jun  7 04:22:32 2017
ErrorMessage: trying to overwrite '/lib/systemd/system/console-setup.service', 
which is also in package keyboard-configuration 1.108ubuntu15.2
InstallationDate: Installed on 2016-10-20 (229 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.24
 apt  1.2.12~ubuntu16.04.1
SourcePackage: console-setup
Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15.2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 third-party-packages xenial

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

Title:
  package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade:
  trying to overwrite '/lib/systemd/system/console-setup.service', which
  is also in package keyboard-configuration 1.108ubuntu15.2

Status in console-setup package in Ubuntu:
  New

Bug description:
  when i try to upgrade the package i got this issue

  ProblemType: Package
  DistroRelease: Debian 9
  Package: console-setup-linux 1.108ubuntu15.2
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Wed Jun  7 04:22:32 2017
  ErrorMessage: trying to overwrite 
'/lib/systemd/system/console-setup.service', which is also in package 
keyboard-configuration 1.108ubuntu15.2
  InstallationDate: Installed on 2016-10-20 (229 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.24
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: console-setup
  Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: 
trying to overwrite '/lib/systemd/system/console-setup.service', which is also 
in package keyboard-configuration 1.108ubuntu15.2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1696269/+subscriptions

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

[Touch-packages] [Bug 1696206] Re: systemd drops lists concatenated with EOF

[Dimitri John Ledkov]

Is a unit with \ continuation lines present in Ubuntu packages?

** Changed in: systemd (Ubuntu)
   Status: New => 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/1696206

Title:
  systemd drops lists concatenated with EOF

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Disclaimer: I originally posted this on Gallium OS's bug tracker but was told 
that Gallium pulls directly from upstream Ubuntu. The original bug report can 
be found here:
  https://github.com/GalliumOS/galliumos-distro/issues/369

  Release: Gallium OS
  Package: systemd

  When a systemd target file contains a "Conflicts" list at the end of
  the file and does not provide a blank line between the end of the list
  and the end of the file the list is silently dropped.

  This is easier to demonstrate than it is to explain.

  Take the following files:

  `ServiceA.service`, `ServiceB.service`, and `ServiceC.service` are identical:
  ```
  [Unit]
  Description=This service just remains on

  [Service]
  Restart=always
  ExecStart=/home/keeton/Permanent/Scripts/StayRunning.sh
  ```

  `StayRunning.sh` is:
  ```
  #!/bin/sh

  while true
do
sleep 3
  done
  ```
  The three services launch a script that keeps on running indefinitely.

  This target, `WillTurnOff.target`, will stop all three services as we would 
expect:
  ```
  [Unit]
  Description=This target will turn off Service's A, B, and C
  Conflicts= \
  ServiceA.service \
  ServiceB.service \
  ServiceC.service \

  ```

  This target, `WillNotTurnOff.target`, will **not** stop the stop the services:
  ```
  [Unit]
  Description=This target will *not* turn off Service's A, B, and C
  Conflicts= \
  ServiceA.service \
  ServiceB.service \
  ServiceC.service \
  ```

  Notice the difference. `WillTurnOff.target` contains a blank line
  between the last item on the list and the end of the file.

  Several things to note:
  * I'm pretty sure that this is a bug in systemd, but Gallium's on systemd 
version 229, which is more than two versions behind the latest version.
  * I'm guessing that systemd is concatenating the EOF onto the list since the 
list ends with a backslash.
  * Shouldn't systemd at least spit out a warning that something is wrong?

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

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

[Touch-packages] [Bug 1696206] Re: systemd drops lists concatenated with EOF

[Dimitri John Ledkov]

I have no idea what Gallium OS is. And indeed launchpad, Ubuntu project
only tracks Ubuntu bugs and Official Flavours.

Gallium OS is not an official Ubuntu flavour.

You may want to report this upstream.

I do not think this is a bug at all, as new lines are not a valid syntax
of systemd units, which is strict, and does not allow multi-line stanzas
like that.

Valid syntax is:
Conflicts=ServiceA.service ServiceB.service
Conflicts=ServiceC.service

As in, space-separated single line value, and the Conflicts= can be
repeated multiple times and the values will be concantenated.

If you have further questions please see errors in the journal, from
systemd about processing/loading that unit, or seek support from systemd
community mailing list.

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

Title:
  systemd drops lists concatenated with EOF

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Disclaimer: I originally posted this on Gallium OS's bug tracker but was told 
that Gallium pulls directly from upstream Ubuntu. The original bug report can 
be found here:
  https://github.com/GalliumOS/galliumos-distro/issues/369

  Release: Gallium OS
  Package: systemd

  When a systemd target file contains a "Conflicts" list at the end of
  the file and does not provide a blank line between the end of the list
  and the end of the file the list is silently dropped.

  This is easier to demonstrate than it is to explain.

  Take the following files:

  `ServiceA.service`, `ServiceB.service`, and `ServiceC.service` are identical:
  ```
  [Unit]
  Description=This service just remains on

  [Service]
  Restart=always
  ExecStart=/home/keeton/Permanent/Scripts/StayRunning.sh
  ```

  `StayRunning.sh` is:
  ```
  #!/bin/sh

  while true
do
sleep 3
  done
  ```
  The three services launch a script that keeps on running indefinitely.

  This target, `WillTurnOff.target`, will stop all three services as we would 
expect:
  ```
  [Unit]
  Description=This target will turn off Service's A, B, and C
  Conflicts= \
  ServiceA.service \
  ServiceB.service \
  ServiceC.service \

  ```

  This target, `WillNotTurnOff.target`, will **not** stop the stop the services:
  ```
  [Unit]
  Description=This target will *not* turn off Service's A, B, and C
  Conflicts= \
  ServiceA.service \
  ServiceB.service \
  ServiceC.service \
  ```

  Notice the difference. `WillTurnOff.target` contains a blank line
  between the last item on the list and the end of the file.

  Several things to note:
  * I'm pretty sure that this is a bug in systemd, but Gallium's on systemd 
version 229, which is more than two versions behind the latest version.
  * I'm guessing that systemd is concatenating the EOF onto the list since the 
list ends with a backslash.
  * Shouldn't systemd at least spit out a warning that something is wrong?

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

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

[Touch-packages] [Bug 319533] Re: FDF file misrecognised as MATLAB script/function

[MikeB]

Has anyone found a work around for this issue? Its been around for quite
a while and we have several staff members that are affected by it too.

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

Title:
  FDF file misrecognised as MATLAB script/function

Status in shared-mime-info package in Ubuntu:
  Confirmed

Bug description:
  (I don't know which component of Gnome is responsible for this
  problem).  This is in Intrepid

  My bank provides tax information via an FDF file.  Internally it
  points to a PDF with named fields and supplies values for the fields.
  It has a text header identifying it as FDF.  The file command gets
  things right:

  $ file tax.fdf
  tax.fdf: FDF document, version 1.2

  Gnome however claims it is a "MATLAB script/function", as shown in
  Nautilus.  What I would expect is for it to be recognised as an FDF
  just like file does, and hopefully to be associated with something
  useful.

  The file starts like this with the  being bytes of
  those hex values.

   8< 
  %FDF-1.2
  %
  1 0 obj
  << 
  /FDF << /Fields 2 0 R /F 
(https://personal.vanguard.com/taxForms/pdfs/TXFRM_1099DIV_1page.pdf)>> 
  >> 
  endobj
  2 0 obj
  [ 
  << /T (REGISTRATION_ADDR_1)/V (My Name)>> << /T (REGISTRATION_ADDR_2)/V (My 
address)>> 
   8< 

  It then follows with more fields.  If I rename the file to have a .pdf
  extension then Nautilus says the type is "PDF document" and tries to
  open it in "Document Viewer" (is that evince?).  The Document Viewer
  then says "File type MATLAB script/function (text/x-matlab) is not
  supported".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/319533/+subscriptions

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Tim Shannon]

Maybe I'm doing something wrong, but I installed the deb, and even did a
full reboot, and I'm still leaking my personal IP in the DNS leak test,
and am still unable to ping servers on the inside of the VPN network
when connected to the ANY connect VPN.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Kai Holthaus]

I checked my system (16.04.02) which is also exhibiting this issue (my Debian 
systems do as well). On both OS, the open-iscsi service is in "active (exited)" 
state after booting (and not in failed state):
● open-iscsi.service - Login to default iSCSI targets
   Loaded: loaded (/lib/systemd/system/open-iscsi.service; enabled; vendor 
preset: enabled)
   Active: active (exited) since Sat 2017-06-03 06:00:19 PDT; 3 days ago
 Docs: man:iscsiadm(8)
   man:iscsid(8)
  Process: 978 ExecStart=/lib/open-iscsi/activate-storage.sh (code=exited, 
status=0/SUCCESS)
  Process: 918 ExecStart=/sbin/iscsiadm -m node --loginall=automatic 
(code=exited, status=0/SUCCESS)
  Process: 905 ExecStartPre=/bin/systemctl --quiet is-active iscsid.service 
(code=exited, status=0/SUCCESS)
 Main PID: 978 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/open-iscsi.service

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Touch-packages] [Bug 1692869] Re: package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-image-extra-4.4.0-79-generic 4.4.0-79.100 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  PEDIU PARA ATUALIZAR A VERSÃO DO UBUNTU E MEU COMPUTADOR NÃO INICIA.
  QUANDO VOU PARA A VERSÃO DE FÁBRICA, ELE PEDE PARA APAGAR TUDO O QUE
  TENHO SALVO NELE... MUITO CHATO ISSO.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-79-generic 4.4.0-79.100
  ProcVersionSignature: Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moema  2203 F pulseaudio
   /dev/snd/controlC0:  moema  2203 F pulseaudio
  Date: Sun May 21 22:33:00 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=d0bb8c75-db9d-4561-9aa7-47a604ccabc5
  InstallationDate: Installed on 2016-07-27 (299 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic 
root=UUID=d3e14fc3-5335-4916-937a-726db739d94a ro quiet splash radeon.modeset=0 
nouveau.modeset=0
  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-extra-4.4.0-79-generic 4.4.0-79.100 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2017-05-22 (1 days ago)
  dmi.bios.date: 05/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/08/2016:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted wayland into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/wayland/1.12.0-1~ubuntu16.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: wayland (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  Fix Committed
Status in libxfont2 source package in Xenial:
  Fix Committed
Status in llvm-toolchain-4.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in vulkan source package in Xenial:
  New
Status in wayland source package in Xenial:
  Fix Committed
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Nicholas Stommel]

Anyone using Cisco PPTP/IPsec/openconnect VPN, please test the network
manager with the aforementioned patch or with the updated built .deb
provided here. The updated patch should address more types of VPN links.
Thanks!

** Attachment added: "updated patched .deb packaged network-manager for easy 
testing"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/+attachment/4890421/+files/network-manager_1.4.4-1ubuntu3_amd64.deb

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

[Jeremy Bicha]

** Description changed:

  Ubuntu Online Accounts is no longer maintained. There is an alternative,
  GNOME Online Accounts for the GNOME desktop.
  
  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.
  
  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-china-photo-scope
  unity-scope-gdrive
  
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud
  
  ubuntu-system-settings
  address-book-app
  address-book-service
  buteo-sync-plugins-contacts-google
  camera-app
  dialer-app
  indicator-transfer
  indicator-transfer-buteo
  libertine
  messaging-app
  ubuntu-experience-tests
  unity-scopes-shell
  unity8
  
  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802
  
- Kubuntu still uses signon-ui
+ Kubuntu still uses the signon-ui source.
+ The signon-ui binary is now NBS (it was transitional pre-vivid depending on 
signon-ui-x11)
  
  unity still recommends unity-scope-gdrive because it FTBFS
  https://code.launchpad.net/~jbicha/unity/drop-uoa-recommends/+merge/325097
+ 
+ See also https://code.launchpad.net/~xnox/ubuntu-
+ seeds/unity8-removals/+merge/323615

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

Title:
  Please remove obsolete UOA packages

Status in gnome-control-center-signon package in Ubuntu:
  New

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-china-photo-scope
  unity-scope-gdrive

  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud

  ubuntu-system-settings
  address-book-app
  address-book-service
  buteo-sync-plugins-contacts-google
  camera-app
  dialer-app
  indicator-transfer
  indicator-transfer-buteo
  libertine
  messaging-app
  ubuntu-experience-tests
  unity-scopes-shell
  unity8

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses the signon-ui source.
  The signon-ui binary is now NBS (it was transitional pre-vivid depending on 
signon-ui-x11)

  unity still recommends unity-scope-gdrive because it FTBFS
  https://code.launchpad.net/~jbicha/unity/drop-uoa-recommends/+merge/325097

  See also https://code.launchpad.net/~xnox/ubuntu-
  seeds/unity8-removals/+merge/323615

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+subscriptions

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

[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-4.0 into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-4.0/1:4.0-1ubuntu1~16.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

** Changed in: llvm-toolchain-4.0 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Backport packages for 16.04.3 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Invalid
Status in libwacom package in Ubuntu:
  Invalid
Status in libxfont package in Ubuntu:
  Invalid
Status in libxfont2 package in Ubuntu:
  Invalid
Status in llvm-toolchain-4.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  New
Status in vulkan package in Ubuntu:
  Invalid
Status in wayland package in Ubuntu:
  Invalid
Status in x11proto-core package in Ubuntu:
  Invalid
Status in xfonts-utils package in Ubuntu:
  New
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  New
Status in libdrm source package in Xenial:
  New
Status in libinput source package in Xenial:
  New
Status in libwacom source package in Xenial:
  New
Status in libxfont source package in Xenial:
  Fix Committed
Status in libxfont2 source package in Xenial:
  Fix Committed
Status in llvm-toolchain-4.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in vulkan source package in Xenial:
  New
Status in wayland source package in Xenial:
  New
Status in x11proto-core source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.3 ***

  Revert changes to use debhelper10.

  xorg-server-hwe-16.04 needs updates
  - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that)
  - x11proto-core 7.0.31
  - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW)

  x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the 
unity mouse config doesn't work with -libinput.
  x-x-i-libinput needs newer libinput, which in turn needs libwacom update.

  Mesa needs llvm-4.0 and libclc, libdrm, wayland updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  zesty hasn't blown up

  [Other information]

  build order:
  1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, 
vulkan, wayland
  2. libclc, libinput, xorg-server (build-dep libxfont1-dev)
  3. mesa, xorg-server-hwe-16.04
  4. drivers
  5. xorg-hwe-16.04

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: External monitor connecting problem on Intel graphics card

[Giacomo Orlandi]

@kaihengfeng this is my output of that command:
~ $ dpkg -l | grep linux-image
hi  linux-image-4.4.0-72-generic  4.4.0-72.93   
   amd64Linux kernel image for version 4.4.0 on 64 
bit x86 SMP
ii  linux-image-4.4.0-78-generic  4.4.0-78.99   
   amd64Linux kernel image for version 4.4.0 on 64 
bit x86 SMP
hi  linux-image-extra-4.4.0-72-generic4.4.0-72.93   
   amd64Linux kernel extra modules for version 
4.4.0 on 64 bit x86 SMP
ii  linux-image-extra-4.4.0-78-generic4.4.0-78.99   
   amd64Linux kernel extra modules for version 
4.4.0 on 64 bit x86 SMP
ii  linux-image-generic   4.4.0.78.84   
   amd64Generic Linux kernel image

I marked the 4.4.0-72 version to hold.
However maybe you wanted to grep for "intel" rather than linux-image? Isn't the 
graphics driver in the xserver-xorg-video-intel package?

-- 
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 on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

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

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

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

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

[Norbert]

Got in Synaptic:
"W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' 
couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)"

Newbies can be frightened of such behavior of Ubuntu.
Do you plan to fix this bug?
It is not user-friendly. You should fix this bug as soon as possible.

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Triaged
Status in apt package in Debian:
  Fix Released

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Nicholas Stommel]

Tim Shannon, from the comment about network-manager-openconnect-gnome, please 
use this updated patch to build the network manager. I added conditions for the 
cisco GRE and GRETAP link types, see 
https://en.wikipedia.org/wiki/Generic_Routing_Encapsulation and 
http://www.cisco.com/c/en/us/td/docs/security/security_management/cisco_security_manager/security_manager/4-4/user/guide/CSMUserGuide_wrapper/vpgredm.html#69194
so I think this might fix the issue connecting through 
network-manager-openconnect-gnome

Please build the network-manager with the following patch and see if DNS
leaks are fixed over cisco openconnect VPN links. Thanks!

** Patch added: "possible cisco network-manager-openconnect-fix"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/+attachment/4890352/+files/resolved-vpn-dns-leak-fix.patch

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

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

[Paul Graydon]

That would be a different bug, unfortunately.

Mine was specifically down to ipconfig not handling multiple network
interfaces correctly, triaged and successfully fixed by Canonical, and
exhaustively validated in our infrastructure.

Roughly speaking, it would quickly loop through the interfaces sending
out DHCP requests, and then listen on all for the responses, but it was
only able to track the request for one interface, which was whatever the
last interface it sent the request out of.  There's a session id
associated with it, and if that didn't match it would drop the packets.

Booting became dependent on the order of network interfaces returned by
the kernel, something that isn't guaranteed in any way, and explains why
it was working with some kernels and not with others, as it would only
work if the one interface that got DHCP responses was the last one
returned by the kernel.

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

Title:
  initrd dhcp fails / ignores valid response

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

Bug description:
  [SRU justification]
  Changes to ordering of kernel enumeration of network interfaces, which may 
happen in any release, can regress network configuration from an initramfs.  
Support for netbooting should not depend on interface order, it should work 
reliably on all systems.

  [Test case]
  Detailed reproducer described in 
  .

  [Regression potential]
  Moderate regression potential, because of a relatively large patch touching a 
not-widely-used but still critical piece of code.  Regression testing should 
include verifying that MAAS-booted cloud images still work as expected in a 
variety of environments.

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

  Over serial console it outputs:

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Matt Schulte]

My test configuration has long since been re-tasked.  I will eventually
be able to come back and test as you ask, but it may take a few weeks.
If anyone else on the bug has their systems up and available, please
test and reply.

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    NOTE: the actual values of the *'s differ for each line above.

  This seems like a bug somewhere but I am unaware of any additional
  logging that I could turn on to pinpoint the problem.

  Note I also have similar setups that are not doing iscsi and they
  don't have this problem.

  Here is a screenshot of what I see on the shell when I try to reboot:

  (https://launchpadlibrarian.net/291303059/Screenshot.jpg)

  This is being tracked in NetApp bug tracker CQ number 860251.

  If I log out of all iscsi sessions before rebooting then I do not
  experience the hang:

  iscsiadm -m node -U all

  We are wondering if this could be some kind of shutdown ordering
  problem.  Like the network devices have already disappeared and then
  iscsi tries to perform some operation (hence the ping timeouts).

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

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

[Touch-packages] [Kernel-packages] [Bug 1652348] [NEW] initrd dhcp fails / ignores valid response

[Michael F Winthrop]

Paul,


  [Kernel-packages] [Bug 1652348] [NEW] initrd dhcp fails / ignores
  valid response
  


https://www.mail-archive.com/kernel-
packa...@lists.launchpad.net/msg211650.html

I also have this bug

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

and tracked it to:

c

I set the countdown to "2 3 4 6 9" and saw the count of failures match 
appropriately.

I note that there are no problems if I attach an Ethernet cable from my 
router to the PC. A probable solution is to use wlan (to get a 
connectible device) or to test and see if the eth actually has a 
connected cable. Perhaps both.

Text requiring attention from /usr/share/initramfs-
tools/scripts/functions

 # support ip options see linux sources
 # Documentation/filesystems/nfs/nfsroot.txt
 # Documentation/frv/booting.txt

 #for ROUNDTTT in 2 3 4 6 9 16 25 36 64 100; do
  for ROUNDTTT in 2 3 4 6 9; do

 # The NIC is to be configured if this file does not exist.
 # Ip-Config tries to create this file and when it succeds
 # creating the file, ipconfig is not run again.
 for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
 if [ -e "$x" ]; then
 IP=done
 break
 fi
 done

 for x in /run/net6-"${DEVICE}".conf /run/net6-*.conf ; do
 if [ -e "$x" ]; then
 IP6=done
 break
 fi

 done

 # if we've reached a point where both IP and IP6 are 
"done",
 # then we're finished with network configuration.
 if [ "$IP" = done ] && [ "$IP6" = done ]; then
 break
 fi

 case ${IP} in
 none|done|off)
 # Do nothing
 IP=done
 ;;
 ""|on|any)
 # Bring up device
 ipconfig -t ${ROUNDTTT} "${DEVICE}"
 ;;
 dhcp|bootp|rarp|both)
 ipconfig -t ${ROUNDTTT} -c ${IP} -d "${DEVICE}"
 ;;
 *)
 ipconfig -t ${ROUNDTTT} -d $IP

 # grab device entry from ip option
 NEW_DEVICE=${IP#*:*:*:*:*:*}
 if [ "${NEW_DEVICE}" != "${IP}" ]; then
 NEW_DEVICE=${NEW_DEVICE%%:*}
 else
 # wrong parse, possibly only a partial 
string
 NEW_DEVICE=
 fi
 if [ -n "${NEW_DEVICE}" ]; then
 DEVICE="${NEW_DEVICE}"
 fi
 ;;
 esac

 case ${IP6} in
 ""|none|done|off)
 # Do nothing
 IP6=done
 ;;
 *)
 # if this is not the first loop, sleep to 
provide the backoff.
 [ "$(($ROUNDTTT-2))" = "0" ] || sleep $ROUNDTTT

 # check the content of IP6, if we have 
something other
 # than a device name there and BOOTIF isn't 
set, clear
 # DEVICE6 and we'll try all available devices.
 if echo "${IP6}" | grep -qv 
'^\(on\|dhcp\|any\)$'; then
 DEVICE6="$IP6"
 fi

 # if we don't have a device specified, try to 
bring up

 # any eligible device.
 if [ -z "${DEVICE6}" ]; then
 DEVICE6=$(all_netbootable_devices)
 fi

 # Bring up device
 for dev in ${DEVICE6} ; do
 dhclient -6 -1 -v "${dev}"
 done
 ;;
 esac
 done

-- 
Cordially Yours,
/*Michael F Winthrop*/
Member: Sterling Lions Club, VA
Member: EAA Chapter 186, Manassas Apt. KHEF

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

Title:
  initrd dhcp fails / ignores valid response

Status in 

[Touch-packages] [Bug 1696237] Re: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Just rebooted this evening and seen this error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.6
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun  6 20:17:09 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2015-10-09 (606 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to xenial on 2017-01-25 (131 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "1";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-04-24T10:11:39.287010

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1696237/+subscriptions

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[bedfojo]

I should add that I'm using network-manager-openvpn and network-manager-
openvpn-gnome.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1696237] [NEW] package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Adriano G. V. Esposito]

Public bug reported:

Just rebooted this evening and seen this error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90ubuntu0.6
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Tue Jun  6 20:17:09 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2015-10-09 (606 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: Upgraded to xenial on 2017-01-25 (131 days ago)
modified.conffile..etc.apt.apt.conf.d.10periodic:
 APT::Periodic::Update-Package-Lists "1";
 APT::Periodic::Download-Upgradeable-Packages "1";
 APT::Periodic::AutocleanInterval "0";
 APT::Periodic::Unattended-Upgrade "1";
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-04-24T10:11:39.287010

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Just rebooted this evening and seen this error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.6
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun  6 20:17:09 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2015-10-09 (606 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: unattended-upgrades
  Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: Upgraded to xenial on 2017-01-25 (131 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic:
   APT::Periodic::Update-Package-Lists "1";
   APT::Periodic::Download-Upgradeable-Packages "1";
   APT::Periodic::AutocleanInterval "0";
   APT::Periodic::Unattended-Upgrade "1";
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-04-24T10:11:39.287010

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1696237/+subscriptions

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[bedfojo]

Nicholas, thank you very much for your work on this patch.

It works correctly for me: no DNS leak detected by either
https://ipleak.net or https://dnsleaktest.com for me, when both detected
leaks in the unpatched version.

Running Ubuntu-MATE 17.04.

Could we perhaps get this upstreamed into NM?

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Nicholas Stommel]

Yeah, apologies as I'm not sure what link type that openconnect uses /
how to identify an openconnect link. It would be a simple matter to add
a conditional for that in the file I patched, please try that. For now
my patch only addresses openvpn tap or tun links, but I'm sure it could
be expanded if possible. Anyone using network-manager-openvpn please
test.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1696075] Re: Please sponsor bluez 5.45 in artful

[Hans Joachim Desserud]

** Tags added: upgrade-software-version

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

Title:
  Please sponsor bluez 5.45 in artful

Status in bluez package in Ubuntu:
  New

Bug description:
  Please sponsor bluez 5.45 in artful

  Debdiff attached.

  Source code for the debdiff: 
https://git.launchpad.net/~bluetooth/bluez/log/?h=artful
  Upstream releases information: http://www.bluez.org/

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

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

[Touch-packages] [Bug 1696206] [NEW] systemd drops lists concatenated with EOF

[Frederick Doe]

Public bug reported:

Disclaimer: I originally posted this on Gallium OS's bug tracker but was told 
that Gallium pulls directly from upstream Ubuntu. The original bug report can 
be found here:
https://github.com/GalliumOS/galliumos-distro/issues/369

Release: Gallium OS
Package: systemd

When a systemd target file contains a "Conflicts" list at the end of the
file and does not provide a blank line between the end of the list and
the end of the file the list is silently dropped.

This is easier to demonstrate than it is to explain.

Take the following files:

`ServiceA.service`, `ServiceB.service`, and `ServiceC.service` are identical:
```
[Unit]
Description=This service just remains on

[Service]
Restart=always
ExecStart=/home/keeton/Permanent/Scripts/StayRunning.sh
```

`StayRunning.sh` is:
```
#!/bin/sh

while true
do
sleep 3
done
```
The three services launch a script that keeps on running indefinitely.

This target, `WillTurnOff.target`, will stop all three services as we would 
expect:
```
[Unit]
Description=This target will turn off Service's A, B, and C
Conflicts= \
ServiceA.service \
ServiceB.service \
ServiceC.service \

```

This target, `WillNotTurnOff.target`, will **not** stop the stop the services:
```
[Unit]
Description=This target will *not* turn off Service's A, B, and C
Conflicts= \
ServiceA.service \
ServiceB.service \
ServiceC.service \
```

Notice the difference. `WillTurnOff.target` contains a blank line
between the last item on the list and the end of the file.

Several things to note:
* I'm pretty sure that this is a bug in systemd, but Gallium's on systemd 
version 229, which is more than two versions behind the latest version.
* I'm guessing that systemd is concatenating the EOF onto the list since the 
list ends with a backslash.
* Shouldn't systemd at least spit out a warning that something is wrong?

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

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

Title:
  systemd drops lists concatenated with EOF

Status in systemd package in Ubuntu:
  New

Bug description:
  Disclaimer: I originally posted this on Gallium OS's bug tracker but was told 
that Gallium pulls directly from upstream Ubuntu. The original bug report can 
be found here:
  https://github.com/GalliumOS/galliumos-distro/issues/369

  Release: Gallium OS
  Package: systemd

  When a systemd target file contains a "Conflicts" list at the end of
  the file and does not provide a blank line between the end of the list
  and the end of the file the list is silently dropped.

  This is easier to demonstrate than it is to explain.

  Take the following files:

  `ServiceA.service`, `ServiceB.service`, and `ServiceC.service` are identical:
  ```
  [Unit]
  Description=This service just remains on

  [Service]
  Restart=always
  ExecStart=/home/keeton/Permanent/Scripts/StayRunning.sh
  ```

  `StayRunning.sh` is:
  ```
  #!/bin/sh

  while true
do
sleep 3
  done
  ```
  The three services launch a script that keeps on running indefinitely.

  This target, `WillTurnOff.target`, will stop all three services as we would 
expect:
  ```
  [Unit]
  Description=This target will turn off Service's A, B, and C
  Conflicts= \
  ServiceA.service \
  ServiceB.service \
  ServiceC.service \

  ```

  This target, `WillNotTurnOff.target`, will **not** stop the stop the services:
  ```
  [Unit]
  Description=This target will *not* turn off Service's A, B, and C
  Conflicts= \
  ServiceA.service \
  ServiceB.service \
  ServiceC.service \
  ```

  Notice the difference. `WillTurnOff.target` contains a blank line
  between the last item on the list and the end of the file.

  Several things to note:
  * I'm pretty sure that this is a bug in systemd, but Gallium's on systemd 
version 229, which is more than two versions behind the latest version.
  * I'm guessing that systemd is concatenating the EOF onto the list since the 
list ends with a backslash.
  * Shouldn't systemd at least spit out a warning that something is wrong?

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

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

[Touch-packages] [Bug 1696196] Re: package python3-problem-report 2.20.4-0ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c

[ludo33200]

Asked synaptic to reinstall package "python3-problem-report"
Done with no error
Awaiting new updates to see if this corrected the error

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

Title:
  package python3-problem-report 2.20.4-0ubuntu4.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Each time the system (and any application) updates, apport crashes.
  No report can be uploaded to launchpad

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-problem-report 2.20.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CrashReports:
   600:0:122:107528:2017-06-06 20:01:17.834536075 +0200:2017-06-06 
20:01:18.834536075 +0200:/var/crash/python3-problem-report.0.crash
   640:0:122:361121:2017-06-05 20:53:44.750577005 +0200:2017-06-05 
20:53:44.758577053 +0200:/var/crash/_usr_lib_xorg_Xorg.0.crash
  Date: Tue Jun  6 20:01:18 2017
  Dependencies:
   
  DuplicateSignature:
   package:python3-problem-report:2.20.4-0ubuntu4.1
   Examining /etc/kernel/header_postinst.d.
   run-parts: executing /etc/kernel/header_postinst.d/dkms 4.10.0-22-generic 
/boot/vmlinuz-4.10.0-22-generic
   dpkg: error processing package python3-problem-report (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-10-25 (223 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package python3-problem-report 2.20.4-0ubuntu4.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (52 days ago)

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

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

[Touch-packages] [Bug 819995] Re: "Print to file" PDF metadata broken

[Yusuf Bolu]

After 5 years from my first comment above, the annoying bug is still here. 
Creator: cairo 1.14.6
Created: Thu 01 Jan 1970 01:59:59 EET

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

Title:
  "Print to file" PDF metadata broken

Status in cairo package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 11.04 Natty Narwhal 64bit

  libgnomeprint2.2-0 - 2.18.8-0ubuntu1

  It seems libgnomeprint sends wrong date, Jan 1st 1970 to PDF metadata when 
printing to file (PDF)
  This behaviour is reproducible for me on both 64bit and 32bit versions of 
11.04
   
  Using dialog "print to file" choosing PDF as output format "Creation Date" 
and "Last edited" is always set to  "Thu 01 Jän 1970 00:59:59 CET" which is 
afaik Date 0 for Unices.
  I am using german localization but in case of needed screenshots I can of 
course change to english.
  This behaviour happens on my main machine (64bit) and my old notebook (32bit) 
looking to my self produced PDFs from 10.10 definitely show the same behaviour, 
I could also look on old backups for even older version.

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

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

[Touch-packages] [Bug 1696196] [NEW] package python3-problem-report 2.20.4-0ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[ludo33200]

Public bug reported:

Each time the system (and any application) updates, apport crashes.
No report can be uploaded to launchpad

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: python3-problem-report 2.20.4-0ubuntu4.1
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportLog:
 
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CrashReports:
 600:0:122:107528:2017-06-06 20:01:17.834536075 +0200:2017-06-06 
20:01:18.834536075 +0200:/var/crash/python3-problem-report.0.crash
 640:0:122:361121:2017-06-05 20:53:44.750577005 +0200:2017-06-05 
20:53:44.758577053 +0200:/var/crash/_usr_lib_xorg_Xorg.0.crash
Date: Tue Jun  6 20:01:18 2017
Dependencies:
 
DuplicateSignature:
 package:python3-problem-report:2.20.4-0ubuntu4.1
 Examining /etc/kernel/header_postinst.d.
 run-parts: executing /etc/kernel/header_postinst.d/dkms 4.10.0-22-generic 
/boot/vmlinuz-4.10.0-22-generic
 dpkg: error processing package python3-problem-report (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-10-25 (223 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: apport
Title: package python3-problem-report 2.20.4-0ubuntu4.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: Upgraded to zesty on 2017-04-15 (52 days ago)

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


** Tags: amd64 apport-package zesty

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

Title:
  package python3-problem-report 2.20.4-0ubuntu4.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Each time the system (and any application) updates, apport crashes.
  No report can be uploaded to launchpad

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-problem-report 2.20.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CrashReports:
   600:0:122:107528:2017-06-06 20:01:17.834536075 +0200:2017-06-06 
20:01:18.834536075 +0200:/var/crash/python3-problem-report.0.crash
   640:0:122:361121:2017-06-05 20:53:44.750577005 +0200:2017-06-05 
20:53:44.758577053 +0200:/var/crash/_usr_lib_xorg_Xorg.0.crash
  Date: Tue Jun  6 20:01:18 2017
  Dependencies:
   
  DuplicateSignature:
   package:python3-problem-report:2.20.4-0ubuntu4.1
   Examining /etc/kernel/header_postinst.d.
   run-parts: executing /etc/kernel/header_postinst.d/dkms 4.10.0-22-generic 
/boot/vmlinuz-4.10.0-22-generic
   dpkg: error processing package python3-problem-report (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-10-25 (223 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package python3-problem-report 2.20.4-0ubuntu4.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (52 days ago)

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

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

[Touch-packages] [Bug 1696196] Re: package python3-problem-report 2.20.4-0ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package python3-problem-report 2.20.4-0ubuntu4.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  Each time the system (and any application) updates, apport crashes.
  No report can be uploaded to launchpad

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-problem-report 2.20.4-0ubuntu4.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CrashReports:
   600:0:122:107528:2017-06-06 20:01:17.834536075 +0200:2017-06-06 
20:01:18.834536075 +0200:/var/crash/python3-problem-report.0.crash
   640:0:122:361121:2017-06-05 20:53:44.750577005 +0200:2017-06-05 
20:53:44.758577053 +0200:/var/crash/_usr_lib_xorg_Xorg.0.crash
  Date: Tue Jun  6 20:01:18 2017
  Dependencies:
   
  DuplicateSignature:
   package:python3-problem-report:2.20.4-0ubuntu4.1
   Examining /etc/kernel/header_postinst.d.
   run-parts: executing /etc/kernel/header_postinst.d/dkms 4.10.0-22-generic 
/boot/vmlinuz-4.10.0-22-generic
   dpkg: error processing package python3-problem-report (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-10-25 (223 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package python3-problem-report 2.20.4-0ubuntu4.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (52 days ago)

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

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

[Touch-packages] [Bug 1696147] Re: installer crashes on raspberry pi 3

[Phillip Susi]

** Package changed: ubiquity (Ubuntu) => apport (Ubuntu)

** Summary changed:

- installer crashes on raspberry pi 3
+ apport failing to collect logs on armhf

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

Title:
  apport failing to collect logs on armhf

Status in apport package in Ubuntu:
  New

Bug description:
  I simply created the user and proceeded to install, and on the
  "creating user" portion of setup it crashed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubiquity 2.21.63.3
  Uname: Linux 4.4.38-v7+ armv7l
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: armhf
  Date: Tue Jun  6 11:04:46 2017
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1696147] [NEW] installer crashes on raspberry pi 3

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I simply created the user and proceeded to install, and on the "creating
user" portion of setup it crashed

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.3
Uname: Linux 4.4.38-v7+ armv7l
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: armhf
Date: Tue Jun  6 11:04:46 2017
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf xenial
-- 
installer crashes on raspberry pi 3
https://bugs.launchpad.net/bugs/1696147
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apport in Ubuntu.

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

Re: [Touch-packages] [Bug 1696175] [NEW] Amazon app does not show up as currently running

[Iain Lane]

On Tue, Jun 06, 2017 at 04:50:37PM -, Jeremy Bicha wrote:
> Public bug reported:
> 
> Ubuntu 17.10 daily ISO with GNOME
> 
> Of course, the current implementation isn't a true webapp but more of a
> bookmark but maybe there's some way we could get the blue dot.
> 
> - Have a background service running? The problem is when should the service 
> stop running?

Far too heavyweight and I can't imagine how you would manage the
lifecycle.

> - Would StartupWMClass in the .desktop do anything useful?

What do you pick? Firefox? Then it's wrong if they change the browser.
And furthermore it would probably make all Firefox windows be associated
with this icon.

I think this is exceedingly minor, but if you want to work on it, be my
guest.

 status triaged
 importance low

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]


** Changed in: ubuntu-settings (Ubuntu)
   Importance: Undecided => Low

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Triaged

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

Title:
  Amazon app does not show up as currently running

Status in ubuntu-settings package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 17.10 daily ISO with GNOME

  When I click the new artful Amazon app, Firefox starts but there is no
  blue dot associated with the icon in GNOME's Activities Overview to
  show that Amazon is running.

  Of course, the current implementation isn't a true webapp but more of
  a bookmark but maybe there's some way we could get the blue dot.

  - Have a background service running? The problem is when should the service 
stop running?
  - Would StartupWMClass in the .desktop do anything useful?

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

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

[Touch-packages] [Bug 1696171] Re: amazon-launcher crashed with GLib.GError in on_simple_ready(): g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Ge

[Iain Lane]

06/06 16:45:45  bigon: is it intentional that libgeoclue-2-0 doesn't 
depend on geoclue-2.0?
06/06 16:46:00  It's a generated wrapper around the DBus API, right?
06/06 16:50:24 <@bigon> mmh
06/06 16:50:57 <@bigon> not sure it's intentional
06/06 17:53:18  bigon: ok, I'll file a bug


On Tue, Jun 06, 2017 at 04:44:51PM -, Jeremy Bicha wrote:
> Public bug reported:
> 
> I logged into the GNOME session today's Ubuntu 17.10 daily ISO.
> 
> In GNOME's Activities Overview, I click the side launcher shortcut for
> Amazon.
> 
> Firefox did open to https://www.amazon.com/?tag=u1webapp-20 but I got a
> crash report from the Amazon app which I am reporting here.
> 
> ProblemType: Crash
> DistroRelease: Ubuntu 17.10
> Package: ubuntu-web-launchers 17.10.3
> ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
> Uname: Linux 4.10.0-22-generic x86_64
> ApportVersion: 2.20.5-0ubuntu4
> Architecture: amd64
> CasperVersion: 1.383
> CurrentDesktop: GNOME
> Date: Tue Jun  6 16:41:08 2017
> ExecutablePath: /usr/share/ubuntu-web-launchers/amazon-launcher
> InterpreterPath: /usr/bin/python3.5
> LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170606.1)
> PackageArchitecture: all
> ProcCmdline: /usr/bin/python3 
> /usr/share/username-web-launchers/amazon-launcher
> ProcEnviron:
>  PATH=(custom, no user)
>  XDG_RUNTIME_DIR=
>  LANG=en_US.UTF-8
>  SHELL=/bin/bash
> PythonArgs: ['/usr/share/username-web-launchers/amazon-launcher']
> SourcePackage: ubuntu-settings
> Title: amazon-launcher crashed with GLib.GError in on_simple_ready(): 
> g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: 
> The name org.freedesktop.GeoClue2 was not provided by any .service files (2)
> Traceback:
>  Traceback (most recent call last):
>File "/usr/share/username-web-launchers/amazon-launcher", line 68, in 
> on_simple_ready
>  simple = Geoclue.Simple.new_finish(result)
>  GLib.GError: g-dbus-error-quark: 
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
> org.freedesktop.GeoClue2 was not provided by any .service files (2)
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> 
> ** Affects: ubuntu-settings (Ubuntu)
>  Importance: Medium
>  Status: New
> 
> 
> ** Tags: amd64 apport-crash artful
> 
> -- 
> You received this bug notification because you are subscribed to ubuntu-
> settings in Ubuntu.
> https://bugs.launchpad.net/bugs/1696171
> 
> Title:
>   amazon-launcher crashed with GLib.GError in on_simple_ready(): g-dbus-
>   error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
>   The name org.freedesktop.GeoClue2 was not provided by any .service
>   files (2)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1696171/+subscriptions

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]


** Package changed: ubuntu-settings (Ubuntu) => geoclue-2.0 (Ubuntu)

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

Title:
  amazon-launcher crashed with GLib.GError in on_simple_ready(): g-dbus-
  error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
  The name org.freedesktop.GeoClue2 was not provided by any .service
  files (2)

Status in geoclue-2.0 package in Ubuntu:
  New
Status in geoclue-2.0 package in Debian:
  Unknown

Bug description:
  I logged into the GNOME session today's Ubuntu 17.10 daily ISO.

  In GNOME's Activities Overview, I click the side launcher shortcut for
  Amazon.

  Firefox did open to https://www.amazon.com/?tag=u1webapp-20 but I got
  a crash report from the Amazon app which I am reporting here.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-web-launchers 17.10.3
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.383
  CurrentDesktop: GNOME
  Date: Tue Jun  6 16:41:08 2017
  ExecutablePath: /usr/share/ubuntu-web-launchers/amazon-launcher
  InterpreterPath: /usr/bin/python3.5
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170606.1)
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 
/usr/share/username-web-launchers/amazon-launcher
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/share/username-web-launchers/amazon-launcher']
  SourcePackage: ubuntu-settings
  Title: amazon-launcher crashed with GLib.GError in on_simple_ready(): 
g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The 
name org.freedesktop.GeoClue2 was 

[Touch-packages] [Bug 1204579] Re: ufw doesn't support concurrent updates

[Christopher M Luciano]

Hi all. I posted a question on this last December, but I never received
feedback on it. Here is the bug report
https://bugs.launchpad.net/ufw/+bug/1652163.

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

Title:
  ufw doesn't support concurrent updates

Status in ufw:
  Triaged
Status in ufw package in Ubuntu:
  Triaged
Status in ufw package in Debian:
  New

Bug description:
  On a server under Ubuntu 12.04 I automatically update firewall rules and I 
unfortunately noticed that if 2 rules are processed at the same time it leads 
to an inconsistent result between iptables and ufw status.
  In fact it can be reproduced using the python script in attachment.

  Before executing this script I didn't have any rules matching the ip 
192.168.254.1 on my computer.
  After a launch iptables takes into acount 464 rules.

  sudo iptables -L -n | grep 192.168.254.1 | wc -l
  464

  It should be 500 rules but the script stressed a lot my system and all rules 
can't be processed by iptables
  sudo ./test_ufw_threads.py
  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.
  [...]

  Anyway, ufw stores only the last updates (in /lib/ufw/user.rules):

  sudo ufw status
  État : actif

  Vers Action Depuis
   -- --
  192.168.254.1 1234/tcp ALLOW   192.168.46.9
  192.168.254.1 1234/tcp ALLOW   192.168.22.10
  192.168.254.1 1234/tcp ALLOW   192.168.32.10
  192.168.254.1 1234/tcp ALLOW   192.168.5.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.9
  192.168.254.1 1234/tcp ALLOW   192.168.40.10
  192.168.254.1 1234/tcp ALLOW   192.168.46.10
  192.168.254.1 1234/tcp ALLOW   192.168.48.10
  192.168.254.1 1234/tcp ALLOW   192.168.42.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.10

  So I can't delete other rules using ufw, I had to directly use iptables.
  In this case I can only delete 10 rules using ufw.
  Could you please handle some kind of lock?

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

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

[Touch-packages] [Bug 1696171] Re: amazon-launcher crashed with GLib.GError in on_simple_ready(): g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Ge

[Apport retracing service]

** Tags removed: need-duplicate-check

** Changed in: ubuntu-settings (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  amazon-launcher crashed with GLib.GError in on_simple_ready(): g-dbus-
  error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
  The name org.freedesktop.GeoClue2 was not provided by any .service
  files (2)

Status in geoclue-2.0 package in Ubuntu:
  New

Bug description:
  I logged into the GNOME session today's Ubuntu 17.10 daily ISO.

  In GNOME's Activities Overview, I click the side launcher shortcut for
  Amazon.

  Firefox did open to https://www.amazon.com/?tag=u1webapp-20 but I got
  a crash report from the Amazon app which I am reporting here.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-web-launchers 17.10.3
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.383
  CurrentDesktop: GNOME
  Date: Tue Jun  6 16:41:08 2017
  ExecutablePath: /usr/share/ubuntu-web-launchers/amazon-launcher
  InterpreterPath: /usr/bin/python3.5
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170606.1)
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 
/usr/share/username-web-launchers/amazon-launcher
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/share/username-web-launchers/amazon-launcher']
  SourcePackage: ubuntu-settings
  Title: amazon-launcher crashed with GLib.GError in on_simple_ready(): 
g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The 
name org.freedesktop.GeoClue2 was not provided by any .service files (2)
  Traceback:
   Traceback (most recent call last):
 File "/usr/share/username-web-launchers/amazon-launcher", line 68, in 
on_simple_ready
   simple = Geoclue.Simple.new_finish(result)
   GLib.GError: g-dbus-error-quark: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.GeoClue2 was not provided by any .service files (2)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1696171/+subscriptions

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

[Touch-packages] [Bug 1696175] [NEW] Amazon app does not show up as currently running

[Jeremy Bicha]

Public bug reported:

Ubuntu 17.10 daily ISO with GNOME

When I click the new artful Amazon app, Firefox starts but there is no
blue dot associated with the icon in GNOME's Activities Overview to show
that Amazon is running.

Of course, the current implementation isn't a true webapp but more of a
bookmark but maybe there's some way we could get the blue dot.

- Have a background service running? The problem is when should the service 
stop running?
- Would StartupWMClass in the .desktop do anything useful?

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

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

Title:
  Amazon app does not show up as currently running

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 daily ISO with GNOME

  When I click the new artful Amazon app, Firefox starts but there is no
  blue dot associated with the icon in GNOME's Activities Overview to
  show that Amazon is running.

  Of course, the current implementation isn't a true webapp but more of
  a bookmark but maybe there's some way we could get the blue dot.

  - Have a background service running? The problem is when should the service 
stop running?
  - Would StartupWMClass in the .desktop do anything useful?

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

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

[Touch-packages] [Bug 1696171] [NEW] amazon-launcher crashed with GLib.GError in on_simple_ready(): g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.

[Jeremy Bicha]

Public bug reported:

I logged into the GNOME session today's Ubuntu 17.10 daily ISO.

In GNOME's Activities Overview, I click the side launcher shortcut for
Amazon.

Firefox did open to https://www.amazon.com/?tag=u1webapp-20 but I got a
crash report from the Amazon app which I am reporting here.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: ubuntu-web-launchers 17.10.3
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CasperVersion: 1.383
CurrentDesktop: GNOME
Date: Tue Jun  6 16:41:08 2017
ExecutablePath: /usr/share/ubuntu-web-launchers/amazon-launcher
InterpreterPath: /usr/bin/python3.5
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170606.1)
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/username-web-launchers/amazon-launcher
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/share/username-web-launchers/amazon-launcher']
SourcePackage: ubuntu-settings
Title: amazon-launcher crashed with GLib.GError in on_simple_ready(): 
g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The 
name org.freedesktop.GeoClue2 was not provided by any .service files (2)
Traceback:
 Traceback (most recent call last):
   File "/usr/share/username-web-launchers/amazon-launcher", line 68, in 
on_simple_ready
 simple = Geoclue.Simple.new_finish(result)
 GLib.GError: g-dbus-error-quark: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.GeoClue2 was not provided by any .service files (2)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: ubuntu-settings (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash artful

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

Title:
  amazon-launcher crashed with GLib.GError in on_simple_ready(): g-dbus-
  error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
  The name org.freedesktop.GeoClue2 was not provided by any .service
  files (2)

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  I logged into the GNOME session today's Ubuntu 17.10 daily ISO.

  In GNOME's Activities Overview, I click the side launcher shortcut for
  Amazon.

  Firefox did open to https://www.amazon.com/?tag=u1webapp-20 but I got
  a crash report from the Amazon app which I am reporting here.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-web-launchers 17.10.3
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.383
  CurrentDesktop: GNOME
  Date: Tue Jun  6 16:41:08 2017
  ExecutablePath: /usr/share/ubuntu-web-launchers/amazon-launcher
  InterpreterPath: /usr/bin/python3.5
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170606.1)
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 
/usr/share/username-web-launchers/amazon-launcher
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/share/username-web-launchers/amazon-launcher']
  SourcePackage: ubuntu-settings
  Title: amazon-launcher crashed with GLib.GError in on_simple_ready(): 
g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The 
name org.freedesktop.GeoClue2 was not provided by any .service files (2)
  Traceback:
   Traceback (most recent call last):
 File "/usr/share/username-web-launchers/amazon-launcher", line 68, in 
on_simple_ready
   simple = Geoclue.Simple.new_finish(result)
   GLib.GError: g-dbus-error-quark: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.GeoClue2 was not provided by any .service files (2)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Will Cooke]

Added to Trello: https://trello.com/c/9GI3EFh2/122-bug1686081-if
--synaptics-is-installed-gnome-mouse--touchpad-settings-doesnt-work

-- 
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 1522675] Re: Warning messages about unsandboxed downloads

[Julian Andres Klode]

I'm not sure why you are highlighting "_as root_" - of course as root,
it only happens as root, otherwise there is no way to drop privileges in
the first place (and not a huge problem of not dropping privileges - you
can only screw up your own stuff).

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Triaged
Status in apt package in Debian:
  Fix Released

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1211102] Re: Get rid of 0.5s latency when playing audio over Bluetooth with A2DP

[mokrates]

Still not working in 17.04.

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

Title:
  Get rid of 0.5s latency when playing audio over Bluetooth with A2DP

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 13.04
  Release:  13.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  bluez:
Instalados: 4.101- 0ubuntu8b1
Candidato:  4.101-0ubuntu8b1
Tabla de versión:
   *** 4.101-0ubuntu8b1 0
  500 http://es.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  The audio always is sync when i listen music on my bluetooth device 
  If i listen music or have a videoconference with skype.. it receive audio 
perfectly without delay.

  4) What happened instead
   I experience a half a second delay when playing audio over Bluetooth with 
A2DP.
  This makes watching movies not possible as the sound is not synchronised with 
the video.

  + If i listen music, then stop about 5 minutes and then restart to listen 
music, it gets work bad.
  + If i get a skype videoconference, it gets too much delay.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: bluez 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Mon Aug 12 01:24:24 2013
  InstallationDate: Installed on 2013-07-13 (29 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK Computer Inc. UX31E
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=89d221ec-829a-456e-963d-ec7ac2c7d47d ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash rootfstype=ext4 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31E.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31E.210:bd12/26/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UX31E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 74:2F:68:CE:17:57  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:407502 acl:14820 sco:0 events:8796 errors:0
TX bytes:7391611 acl:8717 sco:0 commands:45 errors:0

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

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

[Touch-packages] [Bug 1693819] Re: dhclient DHCPv6 does not work with interface alias

[Eric Desrochers]

** Changed in: isc-dhcp (Ubuntu Artful)
   Status: New => In Progress

** Changed in: isc-dhcp (Ubuntu Zesty)
   Status: New => Confirmed

** Changed in: isc-dhcp (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: isc-dhcp (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: isc-dhcp (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  dhclient DHCPv6 does not work with interface alias

Status in isc-dhcp package in Ubuntu:
  In Progress
Status in isc-dhcp source package in Trusty:
  Confirmed
Status in isc-dhcp source package in Xenial:
  Confirmed
Status in isc-dhcp source package in Yakkety:
  Confirmed
Status in isc-dhcp source package in Zesty:
  Confirmed
Status in isc-dhcp source package in Artful:
  In Progress
Status in isc-dhcp package in Debian:
  New

Bug description:
  [Impact]

  The isc-dhcp-client dhclient program does not work with interface
  alias names, e.g. eth0:1.  It fails immediately.

  [Test Case]

  On trusty through artful, find an interface that is connected to a
  network that has a DHCPv6 server on it.  First verify it can get a
  DHCPv6 address, e.g.:

  $ sudo dhclient -6 -v ens7

  that should successfully set up a DHCPv6 address on the interface.
  Then release the interface:

  $ sudo dhclient -6 -v -r ens7

  Now, try again but use the interface alias, e.g.:

  $ sudo dhclient -6 -v ens7:1

  It should succeed, but it will fail with:

  no link-local IPv6 address for ens7:1

  [Regression Potential]

  Changing how isc-dhcp handles (enumerates/lists/compares) interface
  names may lead to isc-dhcp using the wrong interface or failing to
  find the correct interface to use.  However, if the only change is to
  strip the alias part from the interface during comparison, the
  possibility of error should be small, since all interface aliases
  point back to the same physical interface.

  [Other Info]

  This bug exists in the upstream isc-dhcp; the ISC has no public bug
  tracker, and only accepts bug reports via private email, which has
  been sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1693819/+subscriptions

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

[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets

[Nish Aravamudan]

@gimpeystrada: Thank you for providing your journal logs (in the future,
providing the raw journal file is better, as then we can run
`journalctl` on it locally). From the logs:

Apr 26 08:52:13 ICTM1612S02H1 iscsiadm[3234]: iscsiadm: initiator reported 
error (8 - connection timed out)
Apr 26 08:52:13 ICTM1612S02H1 iscsiadm[3234]: iscsiadm: Could not log into all 
portals
Apr 26 08:52:13 ICTM1612S02H1 iscsiadm[3234]: :0113,3260] successful.
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: open-iscsi.service: Child 3234 
belongs to open-iscsi.service
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: open-iscsi.service: Main process 
exited, code=exited, status=8/n/a
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: open-iscsi.service: Changed start -> 
failed
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=936 
reply_cookie=0 error=n/a
Apr 26 08:52:13 ICTM1612S02H1 systemd-logind[2801]: Got message type=signal 
sender=:1.2 destination=n/a object=/org/freedesktop/systemd1 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=936 
reply_cookie=0 error=n/a
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: open-iscsi.service: Job 
open-iscsi.service/start finished, result=failed
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: Failed to start Login to default 
iSCSI targets.
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: Sent message type=signal sender=n/a 
destination=n/a object=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=JobRemoved cookie=937 
reply_cookie=0 error=n/a
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: open-iscsi.service: Unit entered 
failed state.
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: open-iscsi.service: Failed with 
result 'exit-code'.
Apr 26 08:52:13 ICTM1612S02H1 systemd[1]: open-iscsi.service: cgroup is empty

I *think* the issue in this case is that open-iscsi.service is actually
in a failed state before shutdown, which I think means it does not run
the ExecStop commands? Can you verify that is the case (boot your
system, `systemctl is-system-running` should indicate "degraded",
`systemctl status open-iscsi.service` should indicate Failed). The
problem is that the open-iscsi.service has:

ExecStartPre=/bin/systemctl --quiet is-active iscsid.service
ExecStart=/sbin/iscsiadm -m node --loginall=automatic
ExecStart=/lib/open-iscsi/activate-storage.sh
ExecStop=/lib/open-iscsi/umountiscsi.sh
ExecStop=/bin/sync
ExecStop=/lib/open-iscsi/logout-all.sh

This indicates it, on 'start' of the service, it will try to login to
and active all configured iSCSI targets (the two ExecStart lines).
However, if either of those fail (as they did in the journal in this
case), the ExecStop lines *do not* run. From `man systemd.service`:

   Note that if any of the commands specified in ExecStartPre=,
   ExecStart=, or ExecStartPost= fail (and are not prefixed with "-",
   see above) or time out before the service is fully up, execution
   continues with commands specified in ExecStopPost=, the commands in
   ExecStop= are skipped.

So, I think that we should be using ExecStopPost instead.

@gimpeystrada, can you test locally if your system works correctly by
editing /lib/systemd/system/open-iscsi.service to use ExecStopPost
rather than ExecStop? You will need to run `systemctl daemon-reload`
after editing the service file, I believe.

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

Title:
  Shutdown hang on 16.04 with iscsi targets

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have 4 servers running the latest 16.04 updates from the development
  branch (as of right now).

  Each server is connected to NetApp storage using iscsi software
  initiator.  There are a total of 56 volumes spread across two NetApp
  arrays.  Each volume has 4 paths available to it which are being
  managed by device mapper.

  While logged into the iscsi sessions all I have to do is reboot the
  server and I get a hang.

  I see a message that says:

    "Reached target Shutdown"

  followed by

    "systemd-shutdown[1]: Failed to finalize DM devices, ignoring"

  and then I see 8 lines that say:

    "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 
4311815***, last ping 43118164**, now 4311817***"
    "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 

[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

[Jeremy Bicha]

** Description changed:

  Ubuntu Online Accounts is no longer maintained. There is an alternative,
  GNOME Online Accounts for the GNOME desktop.
  
  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.
  
  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
+ unity-china-photo-scope
  unity-scope-gdrive
  
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud
  
  ubuntu-system-settings
  address-book-app
+ address-book-service
+ buteo-sync-plugins-contacts-google
  camera-app
  dialer-app
+ indicator-transfer
+ indicator-transfer-buteo
  libertine
  messaging-app
  ubuntu-experience-tests
  unity-scopes-shell
  unity8
  
  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802
  
  Kubuntu still uses signon-ui
  
  unity still recommends unity-scope-gdrive because it FTBFS
  https://code.launchpad.net/~jbicha/unity/drop-uoa-recommends/+merge/325097

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

Title:
  Please remove obsolete UOA packages

Status in gnome-control-center-signon package in Ubuntu:
  New

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-china-photo-scope
  unity-scope-gdrive

  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud

  ubuntu-system-settings
  address-book-app
  address-book-service
  buteo-sync-plugins-contacts-google
  camera-app
  dialer-app
  indicator-transfer
  indicator-transfer-buteo
  libertine
  messaging-app
  ubuntu-experience-tests
  unity-scopes-shell
  unity8

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui

  unity still recommends unity-scope-gdrive because it FTBFS
  https://code.launchpad.net/~jbicha/unity/drop-uoa-recommends/+merge/325097

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+subscriptions

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

[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

[Jeremy Bicha]

** Description changed:

  Ubuntu Online Accounts is no longer maintained. There is an alternative,
  GNOME Online Accounts for the GNOME desktop.
  
  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.
  
  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-scope-gdrive
  
- 
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud
- Note: ubuntu-system-settings recommends u-s-s-online-accounts. My 
understanding is that we'll be dropping unity8 from Ubuntu 17.10 so I'm not 
sure it's worthwhile to drop that recommends.
+ 
+ ubuntu-system-settings
+ address-book-app
+ camera-app
+ dialer-app
+ libertine
+ messaging-app
+ ubuntu-experience-tests
+ unity-scopes-shell
+ unity8
  
  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802
  
  Kubuntu still uses signon-ui
+ 
+ unity still recommends unity-scope-gdrive because it FTBFS
+ https://code.launchpad.net/~jbicha/unity/drop-uoa-recommends/+merge/325097

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

Title:
  Please remove obsolete UOA packages

Status in gnome-control-center-signon package in Ubuntu:
  New

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  -
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit
  account-polld
  pay-service
  qt-purchasing-opensource-src
  storage-provider-webdav
  sync-monitor
  ubuntuone-credentials
  ubuntu-push
  unity-scope-gdrive

  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper
  mcloud

  ubuntu-system-settings
  address-book-app
  camera-app
  dialer-app
  libertine
  messaging-app
  ubuntu-experience-tests
  unity-scopes-shell
  unity8

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui

  unity still recommends unity-scope-gdrive because it FTBFS
  https://code.launchpad.net/~jbicha/unity/drop-uoa-recommends/+merge/325097

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+subscriptions

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

[Touch-packages] [Bug 1695884] Re: usb probing malforms Epson TM-T70 label printer output

[Dariusz Gadomski]

Till,
The printer in question is was used completely *outside* CUPS - via the 
/dev/usb/lp* nodes only. Although there was also an attempt with using it with 
a raw queue - with the same result: whenever CUPS was enabled or the printer 
was not blacklisted the output from the printer was malformed.

My understanding is that something that CUPS libusb backend was doing in
the 'probing' phase (backends/usb-libusb.c find_device()) is influencing
the printer configuration and changing it's settings set by control
characters.

Attaching the lsusb portion related to the printer in question.


** Attachment added: "lsusb-out.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1695884/+attachment/4889973/+files/lsusb-out.txt

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

Title:
  usb probing malforms Epson TM-T70 label printer output

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  CUPS USB probing malforms Epson TM-T70 (vendorid: 0x04b8 productid:
  0x0202) which is used outside CUPS (via usblp driver).

  No matter whether the printer is set up as a CUPS raw printer or it's
  not used via CUPS (but rather via a device node under usblp control)
  the formatting is broken on the printed out labels: the orientation is
  different from what had been set, the fonts differ.

  After blacklisting the printer in the quirks file all the problems
  were gone.

  My assumption is that this printer should be blacklisted by default.

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

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

[Touch-packages] [Bug 1695876] Re: German Documentation file displays incorrect CUPS version

[Eric Desrochers]

* Upstream project :

commit 88d45155d6deb71e0ed2203d9bb1eb63a17d3abf
Author: jschwender 
Date:   Sat Apr 23 11:29:15 2016 +0200

version was hardcoded

diff --git a/doc/de/index.html.in b/doc/de/index.html.in
index c37edd8..307bb69 100644a
--- a/doc/de/index.html.in
+++ b/doc/de/index.html.in
@@ -23,7 +23,7 @@
 
 
   
-   CUPS 2.0.2
+   CUPS @CUPS_VERSION@
CUPS basiert auf Standards, Open Source Drucksystem entwickelt durch 
http://www.apple.com/;>Apple Inc. für OS X und 
andere UNIX-artige Betriebssysteme.
   
   

* Correction has also landed in Debian "sid" (unstable)

* Ubuntu

It seems like Xenial is the only one affected :

t/cups-1.7.2/doc/de/index.html.in:32:   CUPS @CUPS_VERSION@
x/cups-2.1.3/doc/de/index.html.in:26:   CUPS 2.0.2
y/cups-2.2.0/doc/de/index.html.in:26:   CUPS @CUPS_VERSION@
z/cups-2.2.2/doc/de/index.html.in:26:   CUPS @CUPS_VERSION@

- Eric

** Changed in: cups (Ubuntu)
 Assignee: (unassigned) => Ivy Alexander (ivyalexander)

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

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

Title:
  German Documentation file displays incorrect CUPS version

Status in CUPS:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  The /doc/de/index.html.in file in the package source has an incorrect
  version number written into a header instead of using '@CUPS_VERSION@'
  to populate this file as in the other languages' version of the same
  file, seemingly resulting in /usr/share/cups/doc-root/de/index.html
  having the wrong version once CUPS is installed:

  ...
  

  CUPS 2.0.2
  ...

  instead of:

  ...
  

  CUPS @CUPS_VERSION@
  ...

  resulting in 'CUPS 2.0.2' instead of 2.1.3 being shown.

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

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

[Touch-packages] [Bug 1204579] Re: ufw doesn't support concurrent updates

[Jamie Strandboge]

@Luke, you could modify backend_iptables.py as mentioned in comment #5
or you could perhaps use 'man 1 flock' or implement a lock wrapper
around your invocation of ufw.

That said, since didn't hear back from Christopher, I'll take a look at
implementing this for 0.36.

** Changed in: ufw
Milestone: None => 0.36

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

Title:
  ufw doesn't support concurrent updates

Status in ufw:
  Triaged
Status in ufw package in Ubuntu:
  Triaged
Status in ufw package in Debian:
  New

Bug description:
  On a server under Ubuntu 12.04 I automatically update firewall rules and I 
unfortunately noticed that if 2 rules are processed at the same time it leads 
to an inconsistent result between iptables and ufw status.
  In fact it can be reproduced using the python script in attachment.

  Before executing this script I didn't have any rules matching the ip 
192.168.254.1 on my computer.
  After a launch iptables takes into acount 464 rules.

  sudo iptables -L -n | grep 192.168.254.1 | wc -l
  464

  It should be 500 rules but the script stressed a lot my system and all rules 
can't be processed by iptables
  sudo ./test_ufw_threads.py
  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.

  iptables: Resource temporarily unavailable.
  [...]

  Anyway, ufw stores only the last updates (in /lib/ufw/user.rules):

  sudo ufw status
  État : actif

  Vers Action Depuis
   -- --
  192.168.254.1 1234/tcp ALLOW   192.168.46.9
  192.168.254.1 1234/tcp ALLOW   192.168.22.10
  192.168.254.1 1234/tcp ALLOW   192.168.32.10
  192.168.254.1 1234/tcp ALLOW   192.168.5.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.9
  192.168.254.1 1234/tcp ALLOW   192.168.40.10
  192.168.254.1 1234/tcp ALLOW   192.168.46.10
  192.168.254.1 1234/tcp ALLOW   192.168.48.10
  192.168.254.1 1234/tcp ALLOW   192.168.42.10
  192.168.254.1 1234/tcp ALLOW   192.168.43.10

  So I can't delete other rules using ufw, I had to directly use iptables.
  In this case I can only delete 10 rules using ufw.
  Could you please handle some kind of lock?

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

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

[Touch-packages] [Bug 1633698] Re: ufw before6.rules adds echo-request and echo-response rules to wrong chain

[Jamie Strandboge]

** Changed in: ufw
Milestone: None => 0.36

** Changed in: ufw
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  ufw before6.rules adds echo-request and echo-response rules to wrong
  chain

Status in ufw:
  Fix Committed
Status in ufw package in Ubuntu:
  Fix Released

Bug description:
  The default before6.rules file that is installed with the ufw package
  contains a copy/paste error. It is apparent that the intention is to
  add rules for echo-request and echo-response to the following chains:

  ufw6-before-input
  ufw6-before-output
  ufw6-before-forward

  However there is a copy/paste error and instead of adding the rules to
  ufw6-before-output, it adds it to ufw6-before-input a second time. The
  result is that the rules are absent from ufw6-before-output.

  The file that needs to be fixed in the package is:
  /usr/share/ufw/iptables/before6.rules

  Here is what diff -u shows if I compare the original file to the
  corrected version:

  --- /usr/share/ufw/iptables/before6.rules 2016-04-15 17:16:29.0 
+1200
  +++ ufw_fixed_before6.rules   2016-10-15 23:00:57.763041239 +1300
  @@ -77,8 +77,8 @@
   -A ufw6-before-output -p icmpv6 --icmpv6-type time-exceeded -j ACCEPT
   # codes 0-2
   -A ufw6-before-output -p icmpv6 --icmpv6-type parameter-problem -j ACCEPT
  --A ufw6-before-input -p icmpv6 --icmpv6-type echo-request -j ACCEPT
  --A ufw6-before-input -p icmpv6 --icmpv6-type echo-reply -j ACCEPT
  +-A ufw6-before-output -p icmpv6 --icmpv6-type echo-request -j ACCEPT
  +-A ufw6-before-output -p icmpv6 --icmpv6-type echo-reply -j ACCEPT
   -A ufw6-before-output -p icmpv6 --icmpv6-type router-solicitation -m hl 
--hl-eq 255 -j ACCEPT
   -A ufw6-before-output -p icmpv6 --icmpv6-type neighbor-advertisement -m hl 
--hl-eq 255 -j ACCEPT
   -A ufw6-before-output -p icmpv6 --icmpv6-type neighbor-solicitation -m hl 
--hl-eq 255 -j ACCEPT

  The impact of this error is minor because the ufw.conf file sets the default 
outbound policy to accept:
  DEFAULT_OUTPUT_POLICY="ACCEPT"

  Of course if anyone changed the default outbound policy then the error
  would mean that pings made from the server to other machines would be
  blocked.

  I will attach the original and my fixed version of before6.rules to
  this bug report.

  Thanks for taking the time to look at this issue.

  Nick.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ufw 0.35-2
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic i686
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  Date: Sat Oct 15 23:09:04 2016
  InstallationDate: Installed on 2016-10-14 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release i386 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1627769] Re: limits.conf not applied

[Christopher Warner]

So i'm just going to add on here instead of opening a new bug report.
The problem is that in most cases when you're setting the limits, you're
doing so for a process/user that isn't going to login. So the default is
to set it in login, cron, sshd, su etc. Unfortunately, for a process
that isn't going to login via normal methods. Such as a server process
or the like this will be ignored because pam_limits.so will never be
activated.

We need to put pam_limits.so in /etc/pam.d/common-session and /etc/pam.d
/common-session-noninteractive as required by default, or, update the
documentation somewhere that notes that limits.conf will not be
activated by pam_limits.so otherwise. Since everything is already
commented out by limits.conf per default it should be a straight-forward
change.

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

Title:
  limits.conf not applied

Status in jackd2 package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Since upgraded to 16.10 Yakkety, modifications in
  /etc/security/limits.conf are not taken into consideration when
  logging in the graphical interface.

  
  /etc/security/limits.conf:
  @audio   -  rtprio 99
  @audio   -  memlockunlimited

  I tried the same settings in /etc/security/limits.d/audio.conf, to the
  same results.

  
  After logging in Unity, opening a console, the limits are not set:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) 64
  real-time priority  (-r) 0

  
  Reloging to my user via bash DOES apply the limits:
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) 64
  real-time priority  (-r) 0
  blablack@ideaon:~$ su blablack
  Password: 
  blablack@ideaon:~$ ulimit -l -r
  max locked memory   (kbytes, -l) unlimited
  real-time priority  (-r) 95

  
  Switching to a console (ctrl+alt+f1) and logging in would apply the limits as 
well.



  The exact same setup used to work fine on Xenial 16.04 before upgrade.

  
  If you need any more information, please let me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: lightdm 1.19.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
  Uname: Linux 4.8.0-16-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Sep 26 17:27:10 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/jackd2/+bug/1627769/+subscriptions

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

[Touch-packages] [Bug 1696126] Re: package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configurac

[Alfonso Puerto]

I'm beeing asked to re-install apport 2.20.1-0ubuntu2. How do I do that?

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

Title:
  package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in apport package in Ubuntu:
  New

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.6
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libtasn1-6: Install
   apport: Configure
   libtasn1-6: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Jun  6 12:49:47 2017
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2016-12-16 (172 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1696126] [NEW] package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configur

[Alfonso Puerto]

Public bug reported:

none

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.6
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
 libtasn1-6: Install
 apport: Configure
 libtasn1-6: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Jun  6 12:49:47 2017
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
InstallationDate: Installed on 2016-12-16 (172 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: apport
Title: package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in apport package in Ubuntu:
  New

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.6
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   libtasn1-6: Install
   apport: Configure
   libtasn1-6: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Jun  6 12:49:47 2017
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2016-12-16 (172 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.6 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Tim Shannon]

Not working for me, but I assume that's because I'm using network-
manager-openconnect-gnome?

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

[Will Cooke]

Added to Trello: https://trello.com/c/TzygcVy7/121-bug1693756-xenial-
dw5816e-to-support-qmi-over-mbim-which-needed-for-fcc-authentication

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in ModemManager:
  New
Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  New

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

  FCC authentication reference:
   * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
   * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704

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

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

[Touch-packages] [Bug 1696119] Re: systemd-journald crashed with SIGABRT in journal_file_find_data_object_with_hash()

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-journald crashed with SIGABRT in
  journal_file_find_data_object_with_hash()

Status in systemd package in Ubuntu:
  New

Bug description:
  All of a sudden, the load started shooting up, and then everything
  hung for a several minutes.  Eventually, things went back to normal.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Tue Jun  6 08:42:39 2017
  ExecutablePath: /lib/systemd/systemd-journald
  MachineType: System76, Inc. Galago UltraPro
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic 
root=UUID=9a35e457-d298-41c4-9274-a5e8eb9f78c5 ro i915.disable_power_well=0 
quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   journal_file_find_data_object_with_hash () from 
/lib/systemd/libsystemd-shared-232.so
   ?? () from /lib/systemd/libsystemd-shared-232.so
   journal_file_append_entry () from /lib/systemd/libsystemd-shared-232.so
   ?? ()
   ?? ()
  Title: systemd-journald crashed with SIGABRT in 
journal_file_find_data_object_with_hash()
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (48 days ago)
  UserGroups:
   
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc,
  dmi.chassis.version: galu1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.

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

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

[Touch-packages] [Bug 1426589] Re: tc class statistics rates are all zero after upgrade to Trusty

[Matti-Oskari Leppänen]

Please check that

cat /sys/module/sch_htb/parameters/htp_rate_est

is set to 1

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

Title:
  tc class statistics rates are all zero after upgrade to Trusty

Status in iproute2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading an Ubuntu server from Lucid -> Precise -> Trusty the command:
  tc -s class show dev eth0
  no longer shows rates for my classification bands. This worked in Lucid, but 
not sure if something changed, or if I need to set some system configuration to 
make it work again. My current non-working version is:

  $ dpkg -s iproute2
  Package: iproute2
  Status: install ok installed
  Priority: important
  Section: net
  Installed-Size: 1147
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Multi-Arch: foreign
  Version: 3.12.0-2
  Replaces: iproute
  Provides: arpd
  Depends: libc6 (>= 2.14), libdb5.3
  Recommends: libatm1 (>= 2.4.1-17~), libxtables10
  Suggests: iproute2-doc
  Conflicts: arpd, iproute (<< 2013-1)
  Conffiles:
   /etc/iproute2/group 3aea2c0e0dd75e13a5f8f48f2936915f
   /etc/iproute2/ematch_map b91e7f9b26918449bade9573f8871d61
   /etc/iproute2/rt_realms 7137bdf40e8d58c87ac7e3bba503767f
   /etc/iproute2/rt_tables a1313318d6778fe6b8c680248ef5a463
   /etc/iproute2/rt_dsfield 4264d5c7c8298300185aa04e1a736934
   /etc/iproute2/rt_protos 95ce0b4b5b79f5a8a45941fb418a904c
   /etc/iproute2/rt_scopes 6298b8df09e9bda23ea7da49021ca457
  Description: networking and traffic control tools
   The iproute2 suite is a collection of utilities for networking and
   traffic control.
   .
   These tools communicate with the Linux kernel via the (rt)netlink
   interface, providing advanced features not available through the
   legacy net-tools commands 'ifconfig' and 'route'.
  Original-Maintainer: Debian iproute2 Maintainers 
  Homepage: http://www.linux-foundation.org/en/Net:Iproute2

  Here is the current output of the command, note that 'rate 0bit 0pps'
  is common to all classes, in Lucid this would produce non-zero values
  for active traffic:

  $ tc -s class show dev eth0
  class htb 2:1 root rate 4000Kbit ceil 1Kbit burst 1600b cburst 1600b
   Sent 140162776 bytes 377793 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 23022 borrowed: 0 giants: 0
   tokens: 46812 ctokens: 18725

  class htb 2:2 parent 2:1 leaf 3: prio 0 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 2021584 bytes 6949 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 6505 borrowed: 189 giants: 0
   tokens: 187250 ctokens: 46812

  class htb 2:3 parent 2:1 leaf 4: prio 1 rate 2000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 16695548 bytes 216855 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 216846 borrowed: 9 giants: 0
   tokens: 94375 ctokens: 47187

  class htb 2:4 parent 2:1 leaf 5: prio 2 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 2963040 bytes 46619 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 46619 borrowed: 0 giants: 0
   tokens: 193250 ctokens: 48312

  class htb 2:5 parent 2:1 leaf 6: prio 3 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 6 bytes 745 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 745 borrowed: 0 giants: 0
   tokens: 183000 ctokens: 45750

  class htb 2:6 parent 2:1 leaf 7: prio 4 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 80608262 bytes 79347 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 50544 borrowed: 13902 giants: 0
   tokens: 190750 ctokens: 47687

  class htb 2:7 parent 2:1 leaf 8: prio 5 rate 1000Kbit ceil 4000Kbit burst 
1600b cburst 1600b
   Sent 37606539 bytes 26129 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 5617 borrowed: 8922 giants: 0
   tokens: -178485 ctokens: 24056

  class htb 2:8 parent 2:1 leaf 9: prio 6 rate 512000bit ceil 1000Kbit burst 
1600b cburst 1600b
   Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 0 borrowed: 0 giants: 0
   tokens: 390625 ctokens: 20

  class htb 2:9 parent 2:1 leaf a: prio 7 rate 1000Kbit ceil 1000Kbit burst 
1600b cburst 1600b
   Sent 167807 bytes 1149 pkt (dropped 0, overlimits 0 requeues 0)
   rate 0bit 0pps backlog 0b 0p requeues 0
   lended: 1149 borrowed: 0 giants: 0
   tokens: 189875 ctokens: 189875

  Did something change upstream to make the rates unavailable? Do I need
  to set some config to enable collection? Running the command as root
  does not make 

[Touch-packages] [Bug 1696112] Re: Visual Studio Code hanged installation at 51% and it got stuck indefenitely. I had to restart to install other software....

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1688721
   Packages that trigger multiple debconf prompts fail to install

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

Title:
  Visual Studio Code hanged installation at 51% and it got stuck
  indefenitely. I had to restart to install other software

Status in gconf package in Ubuntu:
  New

Bug description:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

  
  After restarting, the OS popped-up some crash report window... whatever.

  
  Using Ubuntu 17.04 from Virtual Box machine on Windows 10.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Jun  6 08:53:12 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-06 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1696112] [NEW] Visual Studio Code hanged installation at 51% and it got stuck indefenitely. I had to restart to install other software....

[Rolf Eduardo Evaldt Flores]

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

Public bug reported:

package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
subprocess installed post-installation script returned error exit status
128


After restarting, the OS popped-up some crash report window... whatever.


Using Ubuntu 17.04 from Virtual Box machine on Windows 10.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
AptOrdering:
 gconf2-common:amd64: Install
 libgconf-2-4:amd64: Install
 gconf-service-backend:amd64: Install
 gconf-service:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Jun  6 08:53:12 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-06-06 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  Visual Studio Code hanged installation at 51% and it got stuck
  indefenitely. I had to restart to install other software

Status in gconf package in Ubuntu:
  New

Bug description:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

  
  After restarting, the OS popped-up some crash report window... whatever.

  
  Using Ubuntu 17.04 from Virtual Box machine on Windows 10.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Jun  6 08:53:12 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-06-06 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1583544] Re: an official mirror doesn't show in mirrors list in Update Center, Ubuntu 16.04

[Colin Watson]

Yes, Launchpad can't probe this mirror as it seems to either refuse
connections or time out.  (The mirror admin should have been notified
about this by email.)  I'm afraid that we can only list mirrors that we
can automatically verify as being reasonably up to date, so the mirror
needs to be configured to allow us to do so.

** Changed in: launchpad
   Status: New => Invalid

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

Title:
  an official mirror doesn't show in mirrors list in Update Center,
  Ubuntu 16.04

Status in Launchpad itself:
  Invalid
Status in python-apt package in Ubuntu:
  Incomplete

Bug description:
  There is an official mirror mirrors.cug.edu.cn and I have seen it
  listed in https://launchpad.net/ubuntu/+mirror/mirrors.cug.edu.cn-archive, 
but I can't find it in Update Center in Ubuntu 16.04, Chinese  mirrors list. 

  It seems that the package python-apt ships a template file for the list
  of mirrors, and then it doesnt get updated over time.
  There is a function called get_ubuntu_lp_mirrors but it doesnt seem to
  be used.

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

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

[Touch-packages] [Bug 1610519] Re: apport-gtk crashes with segmentation fault

[LocutusOfBorg]

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

can you please test libepoxy from my ppa?
 https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa

please report back results on bug:
https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1647600

this is a duplicate bug.

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

Title:
  apport-gtk crashes with segmentation fault

Status in apport package in Ubuntu:
  New

Bug description:
  apport-bug calling apport-gtk crashes with a segmentation fault.

  ~ $ lsb_release -rd
  Description: Ubuntu 16.04.1 LTS
  Release: 16.04
  ~ $ dpkg -l apport-gtk
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ NameVersion  Architecture 
Description
  
+++-===---
  ii  apport-gtk  2.20.1-0ubuntu2.1all  
GTK+ frontend for the apport crash report system

  
  This look related to #1610518.

  
  The backtrace from the core:

  ~ $ apport-bug 
  Segmentation fault (core dumped)
  ~ $ gdb64 /usr/bin/python3 core 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /usr/bin/python3...(no debugging symbols found)...done.

  warning: core file may not match specified executable file.
  [New LWP 4932]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

  warning: the debug information found in "/lib64/ld-2.23.so" does not
  match "/lib64/ld-linux-x86-64.so.2" (CRC mismatch).

  Core was generated by `/usr/bin/python3 /usr/share/apport/apport-gtk'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37

  warning: Source file is more recent than executable.
  37movdqu  (%rdi), %xmm0
  (gdb) backtrace full
  #0  rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37
  No locals.
  #1  0x7f89cc55bf22 in _IO_str_init_static_internal 
(sf=sf@entry=0x7ffc1fa72690, ptr=ptr@entry=0x0, size=size@entry=0, 
pstart=pstart@entry=0x0)
  at strops.c:41
  fp = 0x7ffc1fa72690
  end = 
  #2  0x7f89cc54ab67 in __GI___isoc99_vsscanf (string=0x0, 
format=0x7f89c5e972f2 "%d.%d", args=args@entry=0x7ffc1fa727b8) at 
isoc99_vsscanf.c:41
  ret = -863365216
  sf = {_sbf = {_f = {_flags = -72515584, _IO_read_ptr = 0x0, 
_IO_read_end = 0x0, _IO_read_base = 0x0, _IO_write_base = 0x0, 
_IO_write_ptr = 0x0, _IO_write_end = 0x0, _IO_buf_base = 0x0, 
_IO_buf_end = 0x0, _IO_save_base = 0x0, _IO_backup_base = 0x0, 
_IO_save_end = 0x0, _markers = 0x0, _chain = 0x0, _fileno = 0, 
_flags2 = 0, _old_offset = 71776119061217280, _cur_column = 0, 
_vtable_offset = 0 '\000', _shortbuf = "", _lock = 0x0, _offset 
= 0, _codecvt = 0x0, _wide_data = 0x, 
_freeres_list = 0x0, _freeres_buf = 0xff00ff00, __pad5 
= 18446462598732840960, _mode = -1, 
_unused2 = '\000' }, vtable = 0x7f89cc8a17a0 
<_IO_str_jumps>}, _s = {_allocate_buffer = 0x0, _free_buffer = 0x0}}
  #3  0x7f89cc54ab07 in __isoc99_sscanf (s=, 
format=) at isoc99_sscanf.c:31
  arg = 
  done = -863365216
  #4  0x7f89c5e79d22 in epoxy_glx_version () from 
/usr/lib/x86_64-linux-gnu/libepoxy.so.0
  No symbol table info available.
  #5  0x7f89c8b18509 in gdk_x11_screen_init_gl 
(screen=screen@entry=0xdf6160)
  at /build/gtk+3.0-6ZPWga/gtk+3.0-3.18.9/./gdk/x11/gdkglcontext-x11.c:774
  display = 0xdf1020
  display_x11 = 0xdf1020
  dpy = 0xde3800
  error_base = 172
  event_base = 104
  screen_num = 0
  #6  0x7f89c8b1882a in _gdk_x11_screen_update_visuals_for_gl 
(screen=screen@entry=0xdf6160)
  at 

[Touch-packages] [Bug 1696106] [NEW] package isc-dhcp-client 4.3.3-5ubuntu12.7 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

[Murad Magomedov]

Public bug reported:

This error occurs on every load of system

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-client 4.3.3-5ubuntu12.7
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Mon Jun  5 22:07:58 2017
DhclientLeases:
 
ErrorMessage: проблемы зависимостей — оставляем не настроенным
InstallationDate: Installed on 2016-05-04 (397 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=0187d6a6-fa15-4047-a59f-c9dd62d24f68 ro quiet splash
SourcePackage: isc-dhcp
Title: package isc-dhcp-client 4.3.3-5ubuntu12.7 failed to install/upgrade: 
проблемы зависимостей — оставляем не настроенным
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package isc-dhcp-client 4.3.3-5ubuntu12.7 failed to install/upgrade:
  проблемы зависимостей — оставляем не настроенным

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  This error occurs on every load of system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12.7
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Mon Jun  5 22:07:58 2017
  DhclientLeases:
   
  ErrorMessage: проблемы зависимостей — оставляем не настроенным
  InstallationDate: Installed on 2016-05-04 (397 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=0187d6a6-fa15-4047-a59f-c9dd62d24f68 ro quiet splash
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-client 4.3.3-5ubuntu12.7 failed to install/upgrade: 
проблемы зависимостей — оставляем не настроенным
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1696106/+subscriptions

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

[Touch-packages] [Bug 1636395] Re: dnsmasq not working with OpenVPN

[Tim Booth]

Hi,

I'm having exactly the same problem as described by @raffraffraff -
after connection to the VPN the dnsmasq instance handled by
NetworkManager no longer makes DNS queries for addresses outside the VPN
(eg. google.com) but it can resolve ones internal to the VPN (eg. web-
dev.myorg.private).

Using DIG to make a direct DNS query to any remote DNS server works
fine, so it looks like dnsmasq has got in a tizz.

To add a little more info...

I'm able to add a file /etc/NetworkManager/dnsmasq.d/debug containing
the line "log-queries" and I can see lines in syslog like:

... dnsmasq[25056]: forwarded www.google.com to 129.215.205.191

So obviously dnsmasq is trying to process the requests but failing.

I can also see dnsmasq picking up new configurations from DBUS as I
connect/disconnect but there are no errors reported.

I also note that dnsmasq is trying to make queries via the public DNS
servers, but when connected to the VPN all the queries should go to the
trusted DNS server provided on the VPN (this is discussed in bug
1639776) but I think this is a separate issue.

Ubuntu 16.04.2 LTS
dnsmask-base  2.75-1ubuntu0.16.04.2
network-manager  1.2.6-0ubuntu0.16.04.1

Cheers,

TIM

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

Title:
  dnsmasq not working with OpenVPN

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in openvpn-systemd-resolved package in Ubuntu:
  Confirmed

Bug description:
  I'm using OpenVPN configured with Network Manager. My VPN have a DNS
  server configured by OpenVPN and config pushed by it while connecting.
  This server is not registered by dnsmasq so domain names are not
  resolved but pinging by IP address works. When I test name resolving
  by pointing to DNS server (172.16.1.1) from VPN provider it's works.
  For example:

  $ host google.com 172.16.1.1
  Using domain server:
  Name: 172.16.1.1
  Address: 172.16.1.1#53
  Aliases: 

  google.com has address 172.217.0.174
  google.com has IPv6 address 2607:f8b0:400b:807::200e
  google.com mail is handled by 30 alt2.aspmx.l.google.com.
  google.com mail is handled by 20 alt1.aspmx.l.google.com.
  google.com mail is handled by 40 alt3.aspmx.l.google.com.
  google.com mail is handled by 10 aspmx.l.google.com.
  google.com mail is handled by 50 alt4.aspmx.l.google.com.

  But if I test without pointing DNS server is not working:

  $ host google.com
  ;; connection timed out; no servers could be reached

  My /etc/resolv.conf:
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 127.0.1.1

  To repair this bug I have to kill dnsmasq and it's automatically
  reloaded.

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

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

[Touch-packages] [Bug 1696091] [NEW] When the "target" demo recieves mir_event_type_close_window it fails to exit

[Alan Griffiths]

Public bug reported:

Start mir_demo_client_target under mir_proving_server (or miral-shell,
or miral-kiosk)

Ensure it has focus and press Alt+F4

expect: the window disappears and the program exits
actual: the window disappears and the program hangs

It appears that the shutdown_handler() thread is waiting on sigwait()
and the main thread is trying to join. (So, for example, Ctrl-C will
still exit OK)

** Affects: mir (Ubuntu)
 Importance: Low
 Status: New

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

Title:
  When the "target" demo recieves mir_event_type_close_window it fails
  to exit

Status in mir package in Ubuntu:
  New

Bug description:
  Start mir_demo_client_target under mir_proving_server (or miral-shell,
  or miral-kiosk)

  Ensure it has focus and press Alt+F4

  expect: the window disappears and the program exits
  actual: the window disappears and the program hangs

  It appears that the shutdown_handler() thread is waiting on sigwait()
  and the main thread is trying to join. (So, for example, Ctrl-C will
  still exit OK)

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

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

[Touch-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

[Alex Tu]

#item fixed:
* backport needed patches to older version packages on Xenial.

Attached backported private built packages which verified passed with
dw5816.

# libmbim was built from:
 https://github.com/alex-tu-cc/libmbim.git
 branch xenial-libmbim-glib4-1.12.2-2ubuntu2_LP1693756

# libqmi was built from:
 https://github.com/alex-tu-cc/libqmi.git
 branch xenial-libqmi-glib1-1.12.6-1ubuntu1_LP1693756

# modemmanager was built from:
 https://github.com/alex-tu-cc/ubuntu-modemmanager-1.4.x.git
 branch origin/xenial-modemmanager1.4.12-1ubuntu2_LP1693756

# install command:
 $ sudo dpkg -i gir1.2-modemmanager-1.0_1.4.12-1ubuntu2_amd64.deb 
libmbim-glib4_1.12.2-2ubuntu2_amd64.deb 
libmbim-glib-dev_1.12.2-2ubuntu2_amd64.deb 
libmbim-proxy_1.12.2-2ubuntu2_amd64.deb libmbim-utils_1.12.2-2ubuntu2_amd64.deb 
libmm-glib0_1.4.12-1ubuntu2_amd64.deb libmm-glib-dev_1.4.12-1ubuntu2_amd64.deb 
libqmi-glib1_1.12.6-1ubuntu1_amd64.deb 
libqmi-glib-dev_1.12.6-1ubuntu1_amd64.deb 
libqmi-proxy_1.12.6-1ubuntu1_amd64.deb libqmi-utils_1.12.6-1ubuntu1_amd64.deb 
modemmanager_1.4.12-1ubuntu2_amd64.deb 
modemmanager-dev_1.4.12-1ubuntu2_amd64.deb

** Attachment added: "debs.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1693756/+attachment/4889869/+files/debs.tar.gz

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in ModemManager:
  New
Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  New

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

  FCC authentication reference:
   * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
   * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704

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

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

[Touch-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

[Alex Tu]

item fixed:
* find out needed patches on newer version packages.

https://github.com/alex-tu-cc/libmbim.git
branch test-1.12.2
has all needed patches comparing to upstream[1] tag 1.12.2

https://github.com/alex-tu-cc/libqmi.git
branch test-qmi-1-12-6
has all needed patches comparing to upstream[2] tag 1.12.6

https://github.com/alex-tu-cc/ubuntu-modemmanager-1.4.x.git
branch origin/xenial-modemmanager1.4.12-1ubuntu2_LP1693756
has all needed patches comparing to xenial modemmanager 1.4.12-1ubuntu1 [3]

[1] git://anongit.freedesktop.org/libmbim/libmbim
[2] git://anongit.freedesktop.org/libqmi
[3] https://github.com/alex-tu-cc/ubuntu-modemmanager-1.4.x.git ; branch 
xenial-modemmanager1.4.12-1ubuntu1

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in ModemManager:
  New
Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  New

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

  FCC authentication reference:
   * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
   * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Jordi Miralles]

Hi! Thanks for the patch Nicholas. I will upgrade to 17.04, test it and
report back tonight or tomorrow at most.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

[Alex Tu]

item fixed:
 * let the newer version packages could also works well on Xenial.

disabling tlp and Yakkety packages are always works well on Xenial.

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in ModemManager:
  New
Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  New

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

  FCC authentication reference:
   * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
   * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: External monitor connecting problem on Intel graphics card

[Shay Perlstein]

Same thing here, 4.4.0-78 does not solve the problem at all, I barely
can work, is there going to be any attempt to fix this soon?

-- 
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 on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

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

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

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

[Touch-packages] [Bug 1693756] Re: [Xenial][ DW5816e] to support qmi over mbim which needed for FCC authentication.

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  [Xenial][ DW5816e] to support qmi over mbim which needed for FCC
  authentication.

Status in ModemManager:
  New
Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  New

Bug description:
  # issue:
   * wwan card DW5816e[413c:81cc] couldn't be recognized by modemmanager 
1.4.12-1ubuntu1 on xenial.
    - but works well on on Yakkety.

  # investgation:
   * in failed case, mmcli -L shows nothing on Xenial with DW5816. Then tried 
install followed packages from Yakkety ppa on Xenial and wwan card works on 1st 
boot but failed after 2nd boot sometimes.
    - libmbim-glib4_1.14.0-1_amd64.deb
    - libmbim-glib-dev_1.14.0-1_amd64.deb
    - libmbim-proxy_1.14.0-1_amd64.deb
    - libmbim-utils_1.14.0-1_amd64.deb
    - libqmi-glib5_1.16.0-1_amd64.deb
    - libqmi-proxy_1.16.0-1_amd64.deb

   * different from ModemManager --debug
     - In passed case, it received message from /dev/cdc-wdm1 after send "Read 
max control message size from descriptors file: 4096" , but not happens to 
failed case. So, it prints "[mm-port-probe.c:261] 
mm_port_probe_set_result_qcdm(): (tty/ttyS4) port is not QCDM-capable" in 
failed case.
   - passed case: http://paste.ubuntu.com/24664908/
   - failed case: http://paste.ubuntu.com/24664910/

  # Plan:
   * let the newer version packages could also works well on Xenial.
   * find out needed patches on newer version packages.
   * packport needed patches to older version packages on Xenial.

  # environment information:

   * modinfo cdc_mbim for original kernel module: 
http://paste.ubuntu.com/24662359/
    - the code /driver/net/usb/cdc_mbim.c is the same between xenial kernel 
4.4.0 and yakkety kernel 4.8.0.

   * uname -r: 4.4.0-73-generic

   * lsusb -v: http://paste.ubuntu.com/24662332/

  FCC authentication reference:
   * http://lists.infradead.org/pipermail/lede-dev/2016-August/002332.html
   * 
https://lists.freedesktop.org/archives/libmbim-devel/2016-April/thread.html#704

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

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

[Touch-packages] [Bug 1117804] Re: ausearch doesn't show AppArmor denial messages

[Vincas Dargis]

I have asked about it in audit mailing list [0], and Audit developer
said that AppArmor should use assigned event numbers in right way, or
something like that..

[0] https://www.redhat.com/archives/linux-audit/2016-April/msg00129.html

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

Title:
  ausearch doesn't show AppArmor denial messages

Status in AppArmor:
  Confirmed
Status in audit package in Ubuntu:
  Confirmed

Bug description:
  The following command should display all AVC denials:

  ausearch -m avc

  However, it doesn't work with AppArmor denials. Here's a quick test
  case to generate a denial, search for it with ausearch, and see that
  no messages are displayed:

  $ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current
  cat: /proc/self/attr/current: Permission denied
  $ sudo ausearch -m avc -c cat
  

  ausearch claims that there are no matches, but there's a matching
  audit message if you look in audit.log:

  type=AVC msg=audit(1360193426.539:64): apparmor="DENIED"
  operation="open" parent=8253 profile="/usr/sbin/tcpdump"
  name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r"
  denied_mask="r" fsuid=1000 ouid=1000

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

-- 
Mailing list: https://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 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[Zhanglei Mao]

hi Daniel,

I am not knowing it but I will check Huawei and vendor of VGA card for
it.

thanks,
Mao

On Tue, Jun 6, 2017 at 3:14 PM, Daniel Axtens 
wrote:

> Hi Mao,
>
> I have looked at the PCI setup a bit more closely: the VGA card is
> behind a PCI bridge which does not advertise the PCI_BRIDGE_CTL_VGA
> capability, so it is not being picked up by the kernel as the
> default/boot card.
>
> Is there anything special about the bridge or the hardware in this
> regard?
>
> Regards,
> Daniel
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1691991
>
> Title:
>   Xorg Segmentation fault on Hisilicon D05 board (arm64)
>
> Status in xorg package in Ubuntu:
>   New
>
> Bug description:
>   ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg
>   [sudo] password for ubuntu:
>
>   X.Org X Server 1.18.4
>   Release Date: 2016-07-19
>   X Protocol Version 11, Revision 0
>   Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
>   Current Operating System: Linux ubuntu 4.10.0-20.22-generic
> #22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
>   Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic
> root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug
> earlycon=pl011,mmio,0x602B console=tty0
>   Build Date: 02 November 2016  10:05:28PM
>   xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see
> http://www.ubuntu.com/support)
>   Current version of pixman: 0.33.6
> Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
>   Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>   (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>   pci id for fd 10: 19e5:1711, driver (null)
>   EGL_MESA_drm_image required.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
>   (EE)
>   (EE) Segmentation fault at address 0xa0
>   (EE)
>   Fatal server error:
>   (EE) Caught signal 11 (Segmentation fault). Server aborting
>   (EE)
>   (EE)
>   Please consult the The X.Org Foundation support
>  at http://wiki.x.org
>for help.
>   (EE) Please also check the log file at "/var/log/Xorg.0.log" for
> additional information.
>   (EE)
>   (EE) Server terminated with error (1). Closing log file.
>   Aborted (core dumped)
>   ubuntu@ubuntu:~$
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+subscriptions
>


-- 
Zhanglei Mao
Solutions Architect, Sales and Business Development
Canonical Group Ltd.
zhanglei@canonical.com
+86-13625010929 (m)
+852-6700 6026 (m)
www.ubuntu.com
www.canonical.com

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing 

[Touch-packages] [Bug 1696075] [NEW] Please sponsor bluez 5.45 in artful

[Daniel van Vugt]

Public bug reported:

Please sponsor bluez 5.45 in artful

Debdiff attached.

Source code for the debdiff: 
https://git.launchpad.net/~bluetooth/bluez/log/?h=artful
Upstream releases information: http://www.bluez.org/

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

** Attachment added: "bluez_5.45-0ubuntu1.debdiff.gz"
   
https://bugs.launchpad.net/bugs/1696075/+attachment/4889844/+files/bluez_5.45-0ubuntu1.debdiff.gz

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

Title:
  Please sponsor bluez 5.45 in artful

Status in bluez package in Ubuntu:
  New

Bug description:
  Please sponsor bluez 5.45 in artful

  Debdiff attached.

  Source code for the debdiff: 
https://git.launchpad.net/~bluetooth/bluez/log/?h=artful
  Upstream releases information: http://www.bluez.org/

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Nicholas Stommel]

>From the Debian man pages, it seems like this is not in fact a problem
of systemd itself, as it allows for domain routing exclusively for dns
servers on a single interface using the routing-only domain. My patch
effectively just tells the  NetworkManager to make a systemd bus call
for the routing-only domain when the connection is a vpn tun or tap
link. In fact, this feature of systemd, the routing-only domain, is a
marked improvement from the glibc API, which has no equivalent concept
of dns servers limited to a system link. The SetLinkDomains method of
the systemd-resolved API allows for this behavior.

>From SYSTEMD.NETWORK(5):

"The "routing-only" domain "~." (the tilde indicating definition of a routing 
domain, the dot referring to the DNS root domain which is the implied suffix of 
all valid DNS names) has special effect. It causes all DNS traffic which does 
not match another configured domain routing entry to be routed to DNS servers 
specified for this interface. This setting is useful to prefer a certain set of 
DNS servers if a link on which they are connected is available.
 
This setting is read by systemd-resolved.service(8). "Search domains" 
correspond to the domain and search entries in resolv.conf(5). Domain name 
routing has no equivalent in the traditional glibc API, which has no concept of 
domain name servers limited to a specific link."

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

[Fredrik Wendt]

The same (or very similar) privilege issue comes into play when
downloading sources _as root_ under /root, such as with the command
'apt-get source linux-image-extra-4.10.0-19-generic'.

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Triaged
Status in apt package in Debian:
  Fix Released

Bug description:
  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1 root root0 Sep 20 06:36 lock
  drwx-- 2 _apt root16384 Sep 24 15:25 partial
  ..

  oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
  .
  drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: synaptic 0.82+build1
  ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
  Uname: Linux 4.3.0-1-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec  4 05:23:25 2015
  SourcePackage: synaptic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1695971] Re: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to install/upgrade: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot be configured because l

[Timo Aaltonen]

ErrorMessage: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1
cannot be configured because libgl1-mesa-glx:i386 is at a different
version (13.1~git1701031930.c4b87f~gd~x)

you've enabled some ppa which breaks things

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

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

Title:
  package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to
  install/upgrade: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1
  cannot be configured because libgl1-mesa-glx:i386 is at a different
  version (13.1~git1701031930.c4b87f~gd~x)

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I tried to install Qt5 by
  ```
  $ sudo apt-get install qt5-default
  ```
  what gave me a `you have held broken packages' error`-message so I tried
  ```
  $ sudo aptitude install qt5-default
  ```
  what proposed some solutions. I think, the chosen solution downgraded the 
given package in the summary.

  Additional information:
  ```
  $ lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  
  $ apt-cache policy libgl1-mesa-glx:amd64
  libgl1-mesa-glx:
Installed: 12.0.6-0ubuntu0.16.10.1
Candidate: 12.0.6-0ubuntu0.16.10.1
Version table:
   *** 12.0.6-0ubuntu0.16.10.1 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   12.0.3-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages

  
  $ apt-cache policy libgl1-mesa-glx:i386
  libgl1-mesa-glx:i386:
Installed: (none)
Candidate: 12.0.6-0ubuntu0.16.10.1
Version table:
   12.0.6-0ubuntu0.16.10.1 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety-updates/main i386 
Packages
   12.0.3-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu yakkety/main i386 Packages
  ```

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic 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: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun  5 20:33:05 2017
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   vhba, 20161009, 4.8.0-49-generic, x86_64: installed
   vhba, 20161009, 4.8.0-52-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-49-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-52-generic, x86_64: installed
  DuplicateSignature:
   package:libgl1-mesa-glx:amd64:12.0.6-0ubuntu0.16.10.1
   Processing triggers for desktop-file-utils (0.23-1ubuntu1.1) ...
   dpkg: error processing package libglapi-mesa:amd64 (--configure):
package libglapi-mesa:amd64 12.0.6-0ubuntu0.16.10.1 cannot be configured 
because libglapi-mesa:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
  ErrorMessage: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot be 
configured because libgl1-mesa-glx:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:7007]
  InstallationDate: Installed on 2016-06-04 (366 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP EliteBook 2740p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic 
root=UUID=45931ea1-c5bd-4b7e-ae5d-28d50c0d8e97 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: mesa
  Title: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 failed to 
install/upgrade: package libgl1-mesa-glx:amd64 12.0.6-0ubuntu0.16.10.1 cannot 
be configured because libgl1-mesa-glx:i386 is at a different version 
(13.1~git1701031930.c4b87f~gd~x)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68COU Ver. F.04
  dmi.board.name: 7007
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 39.36
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

[Touch-packages] [Bug 1061195] Re: Evolution appears unable to create EWS or Exchange MAPI account

[Giovanni Panozzo]

Confirmed on Ubuntu 17.10, Evolution 3.22.6, using EWS.
The usual workaround (delete cfg, cache and pkill) works fine.
https://askubuntu.com/questions/459504/evolution-appears-unable-to-store-mail-account-details

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

Title:
  Evolution appears unable to create EWS or Exchange MAPI account

Status in evolution-ews:
  Expired
Status in evolution package in Ubuntu:
  Triaged
Status in evolution-data-server package in Ubuntu:
  Triaged
Status in evolution-ews package in Ubuntu:
  Triaged
Status in evolution-mapi package in Ubuntu:
  Won't Fix

Bug description:
  Evolution appears unable to create an EW or MAPI account. All the
  steps proceed normally, including fetching the URL (for EWS) or
  authenticating (for MAPI). However, at the conclusion of account
  creation process, no actual account appears in the list.

  I've tried starting Evolution from the command line using various
  DEBUG_ variables and there are no EWS- or MAPI-specific errors. So I'm
  not exactly sure what to do next.

  I am fairly certain the problem doesn't lie with my corporate Exchange
  server, as web mail works fine and any other EWS-capable client (like
  the mail app in Android).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: evolution 3.6.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  3 12:40:28 2012
  InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Beta amd64 
(20120925)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-ews/+bug/1061195/+subscriptions

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

[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough free handles to register service" at start

[Levi Bard]

Same experience as #40 after installing updates on 16.04 today.
I already have the workaround from #4 applied.
The workaround from #35 appears to still work, thankfully.

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

Title:
  15:10 and 16.04: bluetoothd reports "Not enough free handles to
  register service" at start

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15:10 after the bluetooth service has been stopped and restarted it
  is not possible to scan or connect to devices:

  $ sudo systemctl start bluetooth
  $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print 
$0}'
23:31:53  systemd[1]: Starting Bluetooth service...
23:31:53  bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53  systemd[1]: Started Bluetooth service.
23:31:53  bluetoothd[16647]: Starting SDP server
23:31:53  bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53  bluetoothd[16647]: Failed to obtain handles for "Service Changed" 
characteristic
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Error adding Link Loss service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Current Time Service could not be registered
23:31:53  bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Not enough free handles to register service
23:31:53  bluetoothd[16647]: Sap driver initialization failed.
23:31:53  bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSource
23:31:53  bluetoothd[16647]: Endpoint registered: sender=:1.440 
path=/MediaEndpoint/A2DPSink

  And

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# scan on
  Failed to start discovery: org.bluez.Error.NotReady

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

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

[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Nicholas Stommel]

I can confirm this works for multiple vpn connections and after wakeup from 
system suspend on Ubuntu 17.04. I encourage you to install the patched .deb or 
follow the instructions to build it from source and see for yourself. I'm 
honestly so glad this fixes dns leaks for using openvpn through the network 
manager gui on Ubuntu that I'm switching my primary machine to 17.04. :)
Please let me know if this resolves your problems with DNS leaks using a vpn 
via the network manager.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[Daniel Axtens]

Hi Mao,

I have looked at the PCI setup a bit more closely: the VGA card is
behind a PCI bridge which does not advertise the PCI_BRIDGE_CTL_VGA
capability, so it is not being picked up by the kernel as the
default/boot card.

Is there anything special about the bridge or the hardware in this
regard?

Regards,
Daniel

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

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

[Touch-packages] [Bug 1696053] Re: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  mi si blocca devo forzarlo tenendo premuto il tasto di accensione

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportLog: ERROR: apport (pid 4801) Mon Jun  5 23:01:58 2017: host pid 3093 
crashed in a container without apport support
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CrashReports:
   640:1000:122:4522930:2017-05-31 23:41:50.697556018 +0200:2017-05-31 
23:41:51.697556018 
+0200:/var/crash/_opt_teamviewer_tv_bin_TVGuiDelegate.1000.crash
   600:0:122:82663:2017-06-06 00:06:25.052346229 +0200:2017-06-06 
00:06:26.052346229 +0200:/var/crash/apport.0.crash
  Date: Tue Jun  6 00:06:24 2017
  DuplicateSignature:
   package:apport:2.20.4-0ubuntu4
   Processing triggers for libc-bin (2.24-9ubuntu2) ...
   dpkg: error processing package apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-05 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1696053] [NEW] package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[augusto ingenito]

Public bug reported:

mi si blocca devo forzarlo tenendo premuto il tasto di accensione

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: apport 2.20.4-0ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportLog: ERROR: apport (pid 4801) Mon Jun  5 23:01:58 2017: host pid 3093 
crashed in a container without apport support
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CrashReports:
 640:1000:122:4522930:2017-05-31 23:41:50.697556018 +0200:2017-05-31 
23:41:51.697556018 
+0200:/var/crash/_opt_teamviewer_tv_bin_TVGuiDelegate.1000.crash
 600:0:122:82663:2017-06-06 00:06:25.052346229 +0200:2017-06-06 
00:06:26.052346229 +0200:/var/crash/apport.0.crash
Date: Tue Jun  6 00:06:24 2017
DuplicateSignature:
 package:apport:2.20.4-0ubuntu4
 Processing triggers for libc-bin (2.24-9ubuntu2) ...
 dpkg: error processing package apport (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-05 (31 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: apport
Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  New

Bug description:
  mi si blocca devo forzarlo tenendo premuto il tasto di accensione

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportLog: ERROR: apport (pid 4801) Mon Jun  5 23:01:58 2017: host pid 3093 
crashed in a container without apport support
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CrashReports:
   640:1000:122:4522930:2017-05-31 23:41:50.697556018 +0200:2017-05-31 
23:41:51.697556018 
+0200:/var/crash/_opt_teamviewer_tv_bin_TVGuiDelegate.1000.crash
   600:0:122:82663:2017-06-06 00:06:25.052346229 +0200:2017-06-06 
00:06:26.052346229 +0200:/var/crash/apport.0.crash
  Date: Tue Jun  6 00:06:24 2017
  DuplicateSignature:
   package:apport:2.20.4-0ubuntu4
   Processing triggers for libc-bin (2.24-9ubuntu2) ...
   dpkg: error processing package apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-05 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[Daniel Axtens]

** Changed in: xorg (Ubuntu)
 Assignee: (unassigned) => Daniel Axtens (daxtens)

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: External monitor connecting problem on Intel graphics card

[Kai-Heng Feng]

Maybe graphics driver doesn't exist at all?
Can you attach output of `dpkg -l | grep linux-image`?

-- 
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 on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

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

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

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