[Touch-packages] [Bug 1745713] Re: package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1745713

Title:
  package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  new installation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Jan 27 15:50:58 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-01-12 (15 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1745428] Re: package linux-firmware 1.157.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 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/1745428

Title:
  package linux-firmware 1.157.15 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  package linux-firmware 1.157.15 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.15
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Jan 25 16:24:40 2018
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-13 (469 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.157.15 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1745713] [NEW] package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[chrbau]

Public bug reported:

new installation

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Sat Jan 27 15:50:58 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2018-01-12 (15 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: initramfs-tools
Title: package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  new installation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Jan 27 15:50:58 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-01-12 (15 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1745709] [NEW] [Aspire E5-471, Realtek ALC283, Mic, Internal] No sound at all

[Albin John]

Public bug reported:

No sound at all

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0c:   albin  3199 F...m pulseaudio
 /dev/snd/controlC1:  albin  3199 F pulseaudio
 /dev/snd/controlC0:  albin  3199 F pulseaudio
CurrentDesktop: Unity
Date: Sat Jan 27 10:07:44 2018
InstallationDate: Installed on 2018-01-26 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0c:   albin  3199 F...m pulseaudio
 /dev/snd/controlC1:  albin  3199 F pulseaudio
 /dev/snd/controlC0:  albin  3199 F pulseaudio
Symptom_Jack: Mic, Internal
Symptom_Type: No sound at all
Title: [Aspire E5-471, Realtek ALC283, Mic, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.15
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA40_HB
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.15:bd08/13/2014:svnAcer:pnAspireE5-471:pvrTBDbyOEM:rvnAcer:rnEA40_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Type1Family
dmi.product.name: Aspire E5-471
dmi.product.version: TBD by OEM
dmi.sys.vendor: Acer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  [Aspire E5-471, Realtek ALC283, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound at all

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   albin  3199 F...m pulseaudio
   /dev/snd/controlC1:  albin  3199 F pulseaudio
   /dev/snd/controlC0:  albin  3199 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jan 27 10:07:44 2018
  InstallationDate: Installed on 2018-01-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   albin  3199 F...m pulseaudio
   /dev/snd/controlC1:  albin  3199 F pulseaudio
   /dev/snd/controlC0:  albin  3199 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [Aspire E5-471, Realtek ALC283, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.15
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA40_HB
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.15:bd08/13/2014:svnAcer:pnAspireE5-471:pvrTBDbyOEM:rvnAcer:rnEA40_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Aspire E5-471
  dmi.product.version: TBD by OEM
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1734069] Re: idk

[Launchpad Bug Tracker]

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

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

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

Title:
  idk

Status in xorg package in Ubuntu:
  Expired

Bug description:
  idk

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic i686
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: i386
  CompositorRunning: None
  Date: Thu Nov 23 01:59:44 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:3a02]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:3a02]
  InstallationDate: Installed on 2017-10-30 (24 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 
(20171017.1)
  MachineType: LENOVO 4186
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=04d3d2bc-6477-407b-bb6a-316c379aa151 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 15CN31WW(V2.04)
  dmi.board.name: KIWB1
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr15CN31WW(V2.04):bd09/21/2009:svnLENOVO:pn4186:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Lenovo
  dmi.product.name: 4186
  dmi.product.version: Lenovo IdeaPad Y550
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Nov 23 01:49:56 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1734533] Re: package libgssapi3-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado

[Launchpad Bug Tracker]

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

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

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

Title:
  package libgssapi3-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1
  failed to install/upgrade: problemas de dependência - deixando
  desconfigurado

Status in heimdal package in Ubuntu:
  Expired

Bug description:
  Deixa ele lento.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgssapi3-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic i686
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: i386
  Date: Wed Nov 22 10:43:21 2017
  ErrorMessage: problemas de dependência - deixando desconfigurado
  InstallationDate: Installed on 2017-03-06 (264 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: heimdal
  Title: package libgssapi3-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 
failed to install/upgrade: problemas de dependência - deixando desconfigurado
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Anders Kaseorg]

On my bionic system, I had to manually remove resolvconf on account of
bug 1713457.  I think it was not being autoremoved because other
packages like isc-dhcp-client, pppconfig, vpnc-scripts have Suggests:
resolvconf.

So I don’t think I’m seeing this particular issue.  However, the lack of
resolvconf cooperation means that openconnect run from the command line
fights with systemd-resolved over /etc/resolv.conf.  I’m sure that all
kinds of nonsense bugs like that are waiting to be rediscovered.

For the record, I’m still really quite angry at systemd-resolved for a
number of issues that upstream seems to have no interest in addressing.
Its own DNSSEC validation is disabled in Ubuntu because it’s broken (bug
1628778), yet it also breaks DNSSEC validation in applications
downstream of it (https://github.com/systemd/systemd/issues/4621).  It
breaks ‘dig +trace’ (https://github.com/systemd/systemd/issues/5897).
It doesn’t work with resolvconf in a sane way.  The many previous issues
I’ve had with it took way too long to be addressed.  And it does nothing
useful that dnsmasq didn’t do!  (I even had NetworkManager’s dnsmasq
configured to to DNSSEC validation and it worked just fine.)  I’m not
one of those anti-systemd people who hates change for the sake of hating
change.  But systemd-resolved is an actual flaming garbage pile that
needs to be vitrified and launched into the sun.

** Bug watch added: github.com/systemd/systemd/issues #5897
   https://github.com/systemd/systemd/issues/5897

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

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

Status in systemd package in Ubuntu:
  Confirmed

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

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

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

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

[Touch-packages] [Bug 474646] Re: sound dos not work crackaling noise only

[William Grant]

** Attachment removed: "25571E0CEFC5FCBCBF83352F71BC5CD4.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/474646/+attachment/4871138/+files/25571E0CEFC5FCBCBF83352F71BC5CD4.jpg

** Attachment removed: "561D600826864A23F13994B90A4360DE.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/474646/+attachment/4883095/+files/561D600826864A23F13994B90A4360DE.jpg

** Attachment removed: "3114E9F6363BC68F0DD62F5318EB5DAB.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/474646/+attachment/4883851/+files/3114E9F6363BC68F0DD62F5318EB5DAB.jpg

** Attachment removed: "68CF28E2B075DDE62A6E9E679818B384.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/474646/+attachment/4909559/+files/68CF28E2B075DDE62A6E9E679818B384.jpg

** Attachment removed: "953D93BB9E5D2E7E67D8E00F8A82CB04.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/474646/+attachment/4914226/+files/953D93BB9E5D2E7E67D8E00F8A82CB04.jpg

** Attachment removed: "86BB03D2A9359D9294F26F87BA7DA7A8.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/474646/+attachment/4917845/+files/86BB03D2A9359D9294F26F87BA7DA7A8.jpg

** Attachment removed: "A6DA8A09C5740DAA.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/474646/+attachment/4923576/+files/A6DA8A09C5740DAA.jpg

** Attachment removed: "933F1343833118FB.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/474646/+attachment/4951447/+files/933F1343833118FB.jpg

** Attachment removed: "8F94E8701900839F.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/474646/+attachment/4962110/+files/8F94E8701900839F.jpg

** Attachment removed: "949300F0988B07F0.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/474646/+attachment/5007331/+files/949300F0988B07F0.jpg

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

Title:
  sound dos not work crackaling noise only

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  This as not worked for some time I have added utills but they don't help.
  New upgrade to the latest version did not help
  If run a game call railroad tycoon the sound dose work. so the card in the 
laptap is ok
  I am running a msi mega book s430x
  AMD Athlon-x2 64

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: ALC883 Analog [ALC883 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shanta 2558 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfebd8000 irq 23'
 Mixer name : 'Realtek ALC883'
 Components : 'HDA:10ec0883,1462373d,0012 
HDA:11c11040,11c10001,00100200'
 Controls  : 23
 Simple ctrls  : 14
  CheckboxCommand: alsa_record_playback
  CheckboxDescription:
   Connect a microphone to your microphone port. Click the Test button, then 
speak into the microphone. After a few seconds, your speech will be played back 
to you.
   
   Did you hear your speech played back?
  CheckboxTest: alsa_record_playback_external
  Date: Wed Nov  4 11:46:10 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: alsa-base 1.0.20+dfsg-1ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_CA.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: alsa-driver
  Tags: checkbox-bug
  Uname: Linux 2.6.31-14-generic x86_64

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

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

[Touch-packages] [Bug 1730399] Re: Add krackattacks mitigation

[Launchpad Bug Tracker]

This bug was fixed in the package wpa - 2:2.6-15ubuntu1

---
wpa (2:2.6-15ubuntu1) bionic; urgency=low

  * Merge from Debian unstable.  Remaining changes:
- debian/patches/wpa_service_ignore-on-isolate.patch: add
  IgnoreOnIsolate=yes so that when switching "runlevels" in oem-config
  will not kill off wpa and cause wireless to be unavailable on first
  boot.
- debian/patches/session-ticket.patch: disable the TLS Session Ticket
  extension to fix auth with 802.1x PEAP on some hardware.
- debian/patches/android_hal_fw_path_change.patch: add a DBus method
  for requesting a firmware change when working with the Android HAL;
  this is used to set a device in P2P or AP mode; conditional to
  CONFIG_ANDROID_HAL being enabled.
- debian/config/wpasupplicant/linux: enable CONFIG_ANDROID_HAL.
- debian/control: Build-Depends on android-headers to get the required
  wifi headers for the HAL support.
- debian/patches/dbus-available-sta.patch: Make the list of connected
  stations available on DBus for hotspot mode; along with some of the
  station properties, such as rx/tx packets, bytes, capabilities, etc.
  * Updated debian/patches/dbus-available-sta.patch for new getter API
and refreshed other patches.

wpa (2:2.6-15) unstable; urgency=medium

  * Update debian/control:
- Update Maintainer field to point to $pack...@packages.debian.org
- Update Vcs-* fields to point to salsa.d.o
- Drop no longer active uploaders.

wpa (2:2.6-14) unstable; urgency=medium

  * Replace the PEM fix patch by Lukasz Siudut with an upstream patch.
Thanks to David Benjamin .
  * Apply patches from Beniamino Galvani:
- Fix race condition in detecting MAC address change
- Update MAC address when driver detects a change
  * Disable WNM to resolve a compatibility issue with wl.
Thanks to YOSHINO Yoshihito .
Hopefully really closes: #833507.

wpa (2:2.6-13) unstable; urgency=medium

  * Fix a typo in functions.sh (Closes: #883659).

wpa (2:2.6-12) unstable; urgency=medium

  * Add wl to the blacklist for MAC randomisation. (Closes: #833507)
  * Blacklist an out-of-tree driver for Realtek RTL8188EU too.

wpa (2:2.6-11) unstable; urgency=medium

  * Unbreak EAP-TLS.
Thanks to Dmitry Borodaenko 

wpa (2:2.6-10) unstable; urgency=medium

  * Mask hostapd every time it has no valid configuration.

wpa (2:2.6-9) unstable; urgency=medium

  * Tell NetworkManager to not touch MAC addresses on unsupported drivers.
Hopefully, this will fix #849077.

wpa (2:2.6-8) unstable; urgency=medium

  * Revert "Build wpa_supplicant with interface matching support."
(Closes: #882716).
  * Drop override_dh_builddeb.
  * Use dh 10.
  * Prevent hostapd from failing on the package install when there
isn't a valid configuration file yet (Closes: #882740):
- Don't enable hostapd.service by default.
- Mask hostapd.service on the first install.

wpa (2:2.6-7) unstable; urgency=medium

  * Upload to unstable.
  * Optional AP side workaround for key reinstallation attacks (LP: #1730399).

wpa (2:2.6-6) experimental; urgency=medium

  [ Reiner Herrmann ]
  * Port wpa_gui to Qt5 (Closes: #875233).

  [ Andrew Shadura ]
  * Add a service file for hostapd.
  * Build wpa_supplicant with interface matching support (Closes: #879208).

  [ Benedikt Wildenhain (BO) ]
  * Install wpa_supplicant-wired@.service (Closes: #871488).

  [ Jan-Benedict Glaw ]
  * Consider all ifupdown configuration, not only /etc/network/interfaces
(Closes: #853293).

wpa (2:2.6-5) experimental; urgency=medium

  [ Yves-Alexis Perez ]
  * Fix multiple issues in WPA protocol (CVE-2017-13077, CVE-2017-13078,
CVE-2017-13079, CVE-2017-13080, CVE-2017-13081, CVE-2017-13082,
CVE-2017-13086, CVE-2017-13087, CVE-2017-13088):
- hostapd: Avoid key reinstallation in FT handshake
- Prevent reinstallation of an already in-use group key
- Extend protection of GTK/IGTK reinstallation of
- Fix TK configuration to the driver in EAPOL-Key 3/4
- Prevent installation of an all-zero TK
- Fix PTK rekeying to generate a new ANonce
- TDLS: Reject TPK-TK reconfiguration
- WNM: Ignore WNM-Sleep Mode Response if WNM-Sleep Mode
- WNM: Ignore WNM-Sleep Mode Response without pending
- FT: Do not allow multiple Reassociation Response frames
- TDLS: Ignore incoming TDLS Setup Response retries

wpa (2:2.6-4) experimental; urgency=medium

  * Upload to experimental.
  * Bump the epoch to 2:, as the upload to unstable had to bump epoch.

 -- Julian Andres Klode   Thu, 18 Jan 2018 19:47:17
+0100

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-13077

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-13078

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-13079

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-13080

** 

[Touch-packages] [Bug 1745700] [NEW] [Lars, Intel Skylake HDMI, Digital Out, HDMI] No sound at all

[Gertjan]

Public bug reported:

acer chromebook cp5-471

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  frnck  1306 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 27 01:24:08 2018
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1014 F pulseaudio
  frnck  1306 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [Lars, Intel Skylake HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2017
dmi.bios.vendor: coreboot
dmi.board.name: Lars
dmi.board.vendor: Acer
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvncoreboot:bvr:bd06/08/2017:svnAcer:pnLars:pvr1.0:rvnAcer:rnLars:rvr1.0:cvnAcer:ct3:cvr:
dmi.product.family: Google_Lars
dmi.product.name: Lars
dmi.product.version: 1.0
dmi.sys.vendor: Acer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  [Lars, Intel Skylake HDMI, Digital Out, HDMI] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  acer chromebook cp5-471

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  frnck  1306 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 27 01:24:08 2018
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1014 F pulseaudio
frnck  1306 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Lars, Intel Skylake HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: coreboot
  dmi.board.name: Lars
  dmi.board.vendor: Acer
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd06/08/2017:svnAcer:pnLars:pvr1.0:rvnAcer:rnLars:rvr1.0:cvnAcer:ct3:cvr:
  dmi.product.family: Google_Lars
  dmi.product.name: Lars
  dmi.product.version: 1.0
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

[Launchpad Bug Tracker]

This bug was fixed in the package update-notifier - 3.189

---
update-notifier (3.189) bionic; urgency=medium

  * Do not notify-reboot-required on linux-image-extra removal (LP:
#1458204)

 -- Julian Andres Klode   Fri, 12 Jan 2018 09:51:27
+0100

** Changed in: update-notifier (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Confirmed
Status in unattended-upgrades source package in Artful:
  Confirmed
Status in update-notifier source package in Artful:
  Confirmed

Bug description:
  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

[Chris Rainey]

@colin-colino Awesome!  Thanks for your work on this.

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  New
Status in deja-dup package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in meld package in Ubuntu:
  New
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in usb-creator package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://"; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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

[Touch-packages] [Bug 1745698] Re: package libglib2.0-0 2.40.2-0ubuntu1 [modified: usr/share/doc/libglib2.0-0/NEWS.gz usr/share/doc/libglib2.0-0/README.gz usr/share/doc/libglib2.0-0/changelog.Debian.g

[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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1745698

Title:
  package libglib2.0-0 2.40.2-0ubuntu1 [modified:
  usr/share/doc/libglib2.0-0/NEWS.gz
  usr/share/doc/libglib2.0-0/README.gz
  usr/share/doc/libglib2.0-0/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libglib2.0-0/NEWS.gz', which is different from other
  instances of package libglib2.0-0:i386

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Unable to install Wine. Had to manually download the individual
  missing packages and install through gdebi package installer

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libglib2.0-0 2.40.2-0ubuntu1 [modified: 
usr/share/doc/libglib2.0-0/NEWS.gz usr/share/doc/libglib2.0-0/README.gz 
usr/share/doc/libglib2.0-0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.4.0-109.132~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  AptOrdering:
   libglib2.0-0: Install
   libglib2.0-0: Configure
   libglib2.0-0: Configure
  Architecture: amd64
  Date: Sat Jan 27 05:16:19 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DpkgTerminalLog:
   Preparing to unpack .../libglib2.0-0_2.40.2-0ubuntu1_i386.deb ...
   Unpacking libglib2.0-0:i386 (2.40.2-0ubuntu1) over (2.40.0-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libglib2.0-0_2.40.2-0ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libglib2.0-0/NEWS.gz', which is 
different from other instances of package libglib2.0-0:i386
  DuplicateSignature: package:libglib2.0-0:2.40.2-0ubuntu1 [modified: 
usr/share/doc/libglib2.0-0/NEWS.gz usr/share/doc/libglib2.0-0/README.gz 
usr/share/doc/libglib2.0-0/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libglib2.0-0/NEWS.gz', which is different from other instances 
of package libglib2.0-0:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libglib2.0-0/NEWS.gz', which is different from other instances 
of package libglib2.0-0:i386
  InstallationDate: Installed on 2018-01-16 (10 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: glib2.0
  Title: package libglib2.0-0 2.40.2-0ubuntu1 [modified: 
usr/share/doc/libglib2.0-0/NEWS.gz usr/share/doc/libglib2.0-0/README.gz 
usr/share/doc/libglib2.0-0/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libglib2.0-0/NEWS.gz', which is 
different from other instances of package libglib2.0-0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1745698] [NEW] package libglib2.0-0 2.40.2-0ubuntu1 [modified: usr/share/doc/libglib2.0-0/NEWS.gz usr/share/doc/libglib2.0-0/README.gz usr/share/doc/libglib2.0-0/changelog.Debian

[Vikash Denzil]

Public bug reported:

Unable to install Wine. Had to manually download the individual missing
packages and install through gdebi package installer

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libglib2.0-0 2.40.2-0ubuntu1 [modified: 
usr/share/doc/libglib2.0-0/NEWS.gz usr/share/doc/libglib2.0-0/README.gz 
usr/share/doc/libglib2.0-0/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.4.0-109.132~14.04.1-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
AptOrdering:
 libglib2.0-0: Install
 libglib2.0-0: Configure
 libglib2.0-0: Configure
Architecture: amd64
Date: Sat Jan 27 05:16:19 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
DpkgTerminalLog:
 Preparing to unpack .../libglib2.0-0_2.40.2-0ubuntu1_i386.deb ...
 Unpacking libglib2.0-0:i386 (2.40.2-0ubuntu1) over (2.40.0-2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libglib2.0-0_2.40.2-0ubuntu1_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libglib2.0-0/NEWS.gz', which is 
different from other instances of package libglib2.0-0:i386
DuplicateSignature: package:libglib2.0-0:2.40.2-0ubuntu1 [modified: 
usr/share/doc/libglib2.0-0/NEWS.gz usr/share/doc/libglib2.0-0/README.gz 
usr/share/doc/libglib2.0-0/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libglib2.0-0/NEWS.gz', which is different from other instances 
of package libglib2.0-0:i386
ErrorMessage: trying to overwrite shared '/usr/share/doc/libglib2.0-0/NEWS.gz', 
which is different from other instances of package libglib2.0-0:i386
InstallationDate: Installed on 2018-01-16 (10 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: glib2.0
Title: package libglib2.0-0 2.40.2-0ubuntu1 [modified: 
usr/share/doc/libglib2.0-0/NEWS.gz usr/share/doc/libglib2.0-0/README.gz 
usr/share/doc/libglib2.0-0/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libglib2.0-0/NEWS.gz', which is 
different from other instances of package libglib2.0-0:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-conflict third-party-packages trusty

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

Title:
  package libglib2.0-0 2.40.2-0ubuntu1 [modified:
  usr/share/doc/libglib2.0-0/NEWS.gz
  usr/share/doc/libglib2.0-0/README.gz
  usr/share/doc/libglib2.0-0/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libglib2.0-0/NEWS.gz', which is different from other
  instances of package libglib2.0-0:i386

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Unable to install Wine. Had to manually download the individual
  missing packages and install through gdebi package installer

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libglib2.0-0 2.40.2-0ubuntu1 [modified: 
usr/share/doc/libglib2.0-0/NEWS.gz usr/share/doc/libglib2.0-0/README.gz 
usr/share/doc/libglib2.0-0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.4.0-109.132~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  AptOrdering:
   libglib2.0-0: Install
   libglib2.0-0: Configure
   libglib2.0-0: Configure
  Architecture: amd64
  Date: Sat Jan 27 05:16:19 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DpkgTerminalLog:
   Preparing to unpack .../libglib2.0-0_2.40.2-0ubuntu1_i386.deb ...
   Unpacking libglib2.0-0:i386 (2.40.2-0ubuntu1) over (2.40.0-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libglib2.0-0_2.40.2-0ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libglib2.0-0/NEWS.gz', which is 
different from other instances of package libglib2.0-0:i386
  DuplicateSignature: package:libglib2.0-0:2.40.2-0ubuntu1 [modified: 
usr/share/doc/libglib2.0-0/NEWS.gz usr/share/doc/libglib2.0-0/README.gz 
usr/share/doc/libglib2.0-0/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libglib2.0-0/NEWS.gz', which is different from other instances 
of package libglib2.0-0:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libglib2.0-0/NEWS.gz', which is different from other instances 
of package libglib2.0-0:i386
  InstallationDate: Installed on 2018-01-16 (10 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:

[Touch-packages] [Bug 1676115] Re: systemd-resolved spams the system log with useless “Processing query...” messages

[Steve Langasek]

> This was fixed upstream in v233 by downgrading this message from
log_info to log_debug:

So this is fixed in Ubuntu 17.10 and later.

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

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

Title:
  systemd-resolved spams the system log with useless “Processing
  query...” messages

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  If you are running ‘journalctl -f’ to try to debug some other problem,
  you are constantly interrupted by zillions of these messages from
  systemd-resolved:

  Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:27 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:30 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...
  Mar 26 00:53:31 change-mode systemd-resolved[1391]: Processing query...

  This was fixed upstream in v233 by downgrading this message from log_info to 
log_debug:
  https://github.com/systemd/systemd/pull/5233

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

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

[Touch-packages] [Bug 1683066] Re: Broken DNS when using Three UK mobile internet (17.04 zesty)

[Steve Langasek]

Thank you for reporting this problem and helping to improve Ubuntu.

When you were connecting to this 4G network, how was that connection
managed?  Were you using NetworkManager, or some other network
management tool?

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

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

Title:
  Broken DNS when using Three UK mobile internet (17.04 zesty)

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When connected via 4G to Three/3 (UK), DNS lookups fail (though the
  internet is otherwise working).

  The connection receives the correct DNS servers, but as far as I can
  work out systemd-resolve is unaware of them.

  Connection info screenshot is attached.

  DNS lookups time out:

  $ nslookup www.bbc.co.uk
  ;; connection timed out; no servers could be reached

  However they work when manually specifying the DNS server:

  $ nslookup www.bbc.co.uk 217.171.132.0
  Server:   217.171.132.0
  Address:  217.171.132.0#53

  Non-authoritative answer:
  www.bbc.co.uk canonical name = www.bbc.net.uk.
  Name: www.bbc.net.uk
  Address: 212.58.246.54
  Name: www.bbc.net.uk
  Address: 212.58.244.26

  Connections to IP addresses work (though redirect to a Three page at
  present):

  $ curl http://212.58.246.54 -v
  * Rebuilt URL to: http://212.58.246.54/
  *   Trying 212.58.246.54...
  * TCP_NODELAY set
  * Connected to 212.58.246.54 (212.58.246.54) port 80 (#0)
  > GET / HTTP/1.1
  > Host: 212.58.246.54
  > User-Agent: curl/7.52.1
  > Accept: */*
  >
  < HTTP/1.1 302 Moved Temporarily
  < Location: http://mbbinfo.three.co.uk/payg_mbb_data_usage2.html
  < Content-Type: text/plain; charset=UTF-8
  < Content-Length: 0
  <
  * Curl_http_done: called premature == 0
  * Connection #0 to host 212.58.246.54 left intact

  Below is the output of systemd-resolve --status:

  $ systemd-resolve --status
  Global
   DNS Servers: 8.8.8.8
    8.8.4.4
    2001:4860:4860::
    2001:4860:4860::8844
    DNSSEC NTA: 10.in-addr.arpa
    16.172.in-addr.arpa
    168.192.in-addr.arpa
    17.172.in-addr.arpa
    18.172.in-addr.arpa
    19.172.in-addr.arpa
    20.172.in-addr.arpa
    21.172.in-addr.arpa
    22.172.in-addr.arpa
    23.172.in-addr.arpa
    24.172.in-addr.arpa
    25.172.in-addr.arpa
    26.172.in-addr.arpa
    27.172.in-addr.arpa
    28.172.in-addr.arpa
    29.172.in-addr.arpa
    30.172.in-addr.arpa
    31.172.in-addr.arpa
    corp
    d.f.ip6.arpa
    home
    internal
    intranet
    lan
    local
    private
    test

  Link 4 (wlp4s0)
    Current Scopes: none
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 3 (wwp0s20f0u6i12)
    Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 2 (enp0s31f6)
    Current Scopes: none
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Note: Everything works fine on Wi-Fi, this problem is only happening
  on 4G.

  Note 2: I removed the automatically added UdevDb.txt and
  CurrentDmesg.txt attachments as they contained serial numbers of
  devices in my computer (such as for my SSD).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 15 20:54:33 2017
  InstallationDate: Installed on 2017-04-08 (7 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407)
  MachineType: LENOVO 20HDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=88cb6912-997a-41b4-a0f8-050239177218 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1QET53W (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dm

[Touch-packages] [Bug 1745692] Re: Removable storage device not detected as block device

[Dylan Bartlett]

I don't know if this need to go to the kernel team instead of systemd.
Apport decided that systemd is the right place.

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

Title:
  Removable storage device not detected as block device

Status in systemd package in Ubuntu:
  New

Bug description:
  Since updating to the 4.13.0 kernel line I have had bad behaviour from USB 
storage devices. After a reboot the first time I plug a flash drive in, Ubuntu 
mounts the drive normally. If I eject the drive and try to insert the drive 
again them Ubuntu does not automatically mount it, and I cannot mount it 
manually from the terminal.
  If I boot onto a kernel from the 4.10.0 line then the system behaves as 
expected.
  I have installed the latest mainline kernel which is 4.14.15 and have 
observed the same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 61_smfpautoconf_samsung.rules 
99-libsane-samsungmfp.rules 70-snap.keepassxc.rules 99-SaleaeLogic.rules 
71-ti-permissions.rules 70-snap.core.rules 60_smfpautoconf_samsung.rules 
70-mm-no-ti-emulators.rules 61-msp430uif.rules
  Date: Fri Jan 26 22:30:05 2018
  EcryptfsInUse: Yes
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HotplugNewDevices: /dev/sdb /dev/sdb1
  HotplugNewMounts:
   
  InstallationDate: Installed on 2017-09-04 (144 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 008: ID 058f:9380 Alcor Micro Corp. Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-32-generic.efi.signed ro 
root=UUID=dee8db21-42fc-46f8-8b7f-b3b1d1984cfe 
initrd=boot\initrd.img-4.13.0-32-generic
  SourcePackage: systemd
  Symptom: storage
  Title: Removable storage device not detected as block device
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   22:30:09.917: The udisks-daemon is running (name-owner :1.99).
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1665099] Re: package libnss-resolve:amd64 231-9ubuntu2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.

[Steve Langasek]

Thank you for reporting this bug and helping to improve Ubuntu.

Unfortunately, this bug report does not include enough information to
tell us what caused this package to originally end up in an inconsistent
state.  This bug report is by now quite old, so it's likely you no
longer have logs that would tell us more; but if you do have the
original package manager logs, please attach them to this bug report and
set its state back to 'new'.

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

Title:
  package libnss-resolve:amd64 231-9ubuntu2 failed to install/upgrade: O
  pacote está num mau estado de inconsistência; deve  reinstala-lo antes
  de tentar configura-lo.

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  please check

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve:amd64 231-9ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-34.36-lowlatency 4.8.11
  Uname: Linux 4.8.0-34-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  AptOrdering:
   libgc1c2:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Feb 15 16:36:17 2017
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: systemd
  Title: package libnss-resolve:amd64 231-9ubuntu2 failed to install/upgrade: O 
pacote está num mau estado de inconsistência; deve  reinstala-lo antes de 
tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1661716] Re: Domain names not resolving on bootup

[Steve Langasek]

There were a number of bugs reported in the 16.10 timeframe about this
issue.  I believe these have all been resolved as of Ubuntu 17.04, so am
closing this bug fix-released.  If you are still seeing issues with
systemd-resolved in a currently supported release of Ubuntu, please
reopen this report.

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

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

Title:
  Domain names not resolving on bootup

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I just installed Ubuntu 16.10 on my System76 Pangolin Performance
  laptop. After bootup, connecting to the internet via a WiFi
  connection, both Chromium and Firefox failed to resolve any domain
  names (cnn.com, google.com, etc.) I entered into the browser. I at
  first thought that my internet connection was not working, so I opened
  up a terminal and entered "ping 8.8.8.8" and was surprised to see that
  the ping attempt was successful. However, when I tried to ping a
  domain name (google.com), I was not successful.

  I then entered "sudo service systemd-resolved restart" and the problem
  was resolved.

  This is a recurring problem. Every time I start up my laptop I have to
  restart systemd-resolved or else both the browser and command line are
  unable to resolve domain names.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  3 14:00:57 2017
  InstallationDate: Installed on 2017-02-02 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: System76, Inc. Pangolin Performance
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic 
root=UUID=ed0fb709-9a93-4ef8-957b-58dcd639c8a6 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Pangolin Performance
  dmi.board.vendor: System76, Inc.
  dmi.board.version: panp8
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: panp8
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/12/2011:svnSystem76,Inc.:pnPangolinPerformance:pvrpanp8:rvnSystem76,Inc.:rnPangolinPerformance:rvrpanp8:cvnSystem76,Inc.:ct9:cvrpanp8:
  dmi.product.name: Pangolin Performance
  dmi.product.version: panp8
  dmi.sys.vendor: System76, Inc.

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

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

[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

[Colin Leroy]

GNOME devs accepted my patch upstream. I made a debdiff to fix the Ubuntu 
package .Now we're just waiting for an Ubuntu dev with some motivation to fix 
this.
Chris is right. This regression *in an LTS release even!* and the time it takes 
to fix it is awfully long.

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  New
Status in deja-dup package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in meld package in Ubuntu:
  New
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in usb-creator package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://"; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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

[Touch-packages] [Bug 1745692] [NEW] Removable storage device not detected as block device

[Dylan Bartlett]

Public bug reported:

Since updating to the 4.13.0 kernel line I have had bad behaviour from USB 
storage devices. After a reboot the first time I plug a flash drive in, Ubuntu 
mounts the drive normally. If I eject the drive and try to insert the drive 
again them Ubuntu does not automatically mount it, and I cannot mount it 
manually from the terminal.
If I boot onto a kernel from the 4.10.0 line then the system behaves as 
expected.
I have installed the latest mainline kernel which is 4.14.15 and have observed 
the same issue.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu21
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
CustomUdevRuleFiles: 61_smfpautoconf_samsung.rules 99-libsane-samsungmfp.rules 
70-snap.keepassxc.rules 99-SaleaeLogic.rules 71-ti-permissions.rules 
70-snap.core.rules 60_smfpautoconf_samsung.rules 70-mm-no-ti-emulators.rules 
61-msp430uif.rules
Date: Fri Jan 26 22:30:05 2018
EcryptfsInUse: Yes
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HotplugNewDevices: /dev/sdb /dev/sdb1
HotplugNewMounts:
 
InstallationDate: Installed on 2017-09-04 (144 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
 Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
 Bus 001 Device 008: ID 058f:9380 Alcor Micro Corp. Flash Drive
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookPro12,1
ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-32-generic.efi.signed ro 
root=UUID=dee8db21-42fc-46f8-8b7f-b3b1d1984cfe 
initrd=boot\initrd.img-4.13.0-32-generic
SourcePackage: systemd
Symptom: storage
Title: Removable storage device not detected as block device
UdisksMonitorLog:
 Monitoring the udisks daemon. Press Ctrl+C to exit.
 22:30:09.917: The udisks-daemon is running (name-owner :1.99).
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2017
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP121.88Z.0171.B00.1708080033
dmi.board.name: Mac-E43C1C25D4880AD6
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro12,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-E43C1C25D4880AD6
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro12,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  Removable storage device not detected as block device

Status in systemd package in Ubuntu:
  New

Bug description:
  Since updating to the 4.13.0 kernel line I have had bad behaviour from USB 
storage devices. After a reboot the first time I plug a flash drive in, Ubuntu 
mounts the drive normally. If I eject the drive and try to insert the drive 
again them Ubuntu does not automatically mount it, and I cannot mount it 
manually from the terminal.
  If I boot onto a kernel from the 4.10.0 line then the system behaves as 
expected.
  I have installed the latest mainline kernel which is 4.14.15 and have 
observed the same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu21
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 61_smfpautoconf_samsung.rules 
99-libsane-samsungmfp.rules 70-snap.keepassxc.rules 99-SaleaeLogic.rules 
71-ti-permissions.rules 70-snap.core.rules 60_smfpautoconf_samsung.rules 
70-mm-no-ti-emulators.rules 61-msp430uif.rules
  Date: Fri Jan 26 22:30:05 2018
  EcryptfsInUse: Yes
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HotplugNewDevices: /dev/sdb /dev/sdb1
  HotplugNewMounts:
   
  InstallationDate: Installed on 2017-09-04 (144 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 008: ID 058f:9380 Alcor Micro Corp. Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-32-generic.efi.signed ro 
root=UUID=dee8db21-42fc-46f8-8b7f-b3b1d1984cfe 
initrd=b

[Touch-packages] [Bug 1654878] Re: segmentation fault in systemd-resolve

[Steve Langasek]

This is impossible to debug based on the amount of information listed in
dmesg.  If this problem is still reproducible, please submit a crash
dump (as saved by apport to /var/crash, and reportable with ubuntu-bug).

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

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

Title:
  segmentation fault in systemd-resolve

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  `dmesg` reveals a lot (> 1000) message in the form of

  [733613.592593] systemd-resolve[23515]: segfault at 1f ip 
5603285ac866 sp 7ffcd8b1fd30 error 4 in 
systemd-resolved[56032858b000+4c000]
  [733919.154889] systemd-resolve[25753]: segfault at 21 ip 
0021 sp 7fffe5e95438 error 14 in 
systemd-resolved[5647fa725000+4c000]
  [734086.092512] systemd-resolve[25895]: segfault at 3b4 ip 
7f4ce2686226 sp 7ffe901696c0 error 4 in 
libsystemd-shared-231.so[7f4ce2635000+178000]
  [734518.092536] systemd-resolve[28340]: segfault at 55c9157806e0 ip 
55c9157806e0 sp 7ffc0e19c968 error 15
  [734605.092536] systemd-resolve[29254]: segfault at 55f2abd3d630 ip 
55f2abd3d630 sp 7ffd8caea4a8 error 15
  [734810.838123] systemd[1]: open-iscsi.service: Cannot add dependency 
job, ignoring: Unit open-iscsi.service is masked.
  [734811.379177] systemd[1]: brltty.service: Cannot add dependency job, 
ignoring: Unit brltty.service is masked.
  [734811.596355] systemd[1]: open-iscsi.service: Cannot add dependency 
job, ignoring: Unit open-iscsi.service is masked.
  [734811.807015] systemd: 74 output lines suppressed due to ratelimiting
  [735409.842514] systemd-resolve[4784]: segfault at ab39b924f2 ip 
7f7812377226 sp 7fff4150ea30 error 4 in 
libsystemd-shared-231.so[7f7812326000+178000]
  [735530.098073] systemd-resolve[5621]: segfault at 7f4e658abd20 ip 
7f4f6556aea9 sp 7ffe1498e320 error 4 in 
libc-2.24.so[7f4f654ea000+1bd000]
  [736167.939132] systemd-resolve[8931]: segfault at fffe ip 
7fe290f19162 sp 7ffebe838e40 error 5 in 
libc-2.24.so[7fe290e93000+1bd000]
  [736345.592608] systemd-resolve[10056]: segfault at 5 ip 7faa2ea3b226 
sp 7ffdb90ae740 error 4 in libsystemd-shared-231.so[7faa2e9ea000+178000]
  [737069.938626] traps: systemd-resolve[12968] general protection 
ip:7f04f9d1d226 sp:7ffd0c0b1950 error:0 in 
libsystemd-shared-231.so[7f04f9ccc000+178000]
  [737202.342511] systemd-resolve[13961]: segfault at 3 ip 7fdfe82a9226 
sp 7ffe146d3d50 error 4 in libsystemd-shared-231.so[7fdfe8258000+178000]
  [737356.092549] systemd-resolve[15062]: segfault at 41 ip 
56539647b726 sp 7ffe25c518e0 error 4 in 
systemd-resolved[565396467000+4c000]
  [737595.092520] systemd-resolve[16487]: segfault at 91 ip 
0091 sp 7ffd146bf198 error 14 in 
systemd-resolved[5644f4849000+4c000]
  [737686.842560] systemd-resolve[17106]: segfault at 164 ip 
7f14323f4226 sp 7fff98316f90 error 4 in 
libsystemd-shared-231.so[7f14323a3000+178000]
  [738397.592539] systemd-resolve[19734]: segfault at 41 ip 
0041 sp 7ffc5d23da58 error 14 in 
systemd-resolved[55ed3fb85000+4c000]
  [738460.842548] systemd-resolve[20193]: segfault at 12 ip 
7f7ae1a56226 sp 7fff7b503ca0 error 4 in 
libsystemd-shared-231.so[7f7ae1a05000+178000]
  [738518.342511] systemd-resolve[20384]: segfault at 3 ip 7fcb83841226 
sp 7ffc1a5d7ee0 error 4 in libsystemd-shared-231.so[7fcb837f+178000]
  [738799.592554] traps: systemd-resolve[21557] general protection 
ip:562279d7133c sp:7fff4c252188 error:0 in systemd-resolved[562279d5f000+4c000]
  [738931.342522] traps: systemd-resolve[22076] general protection 
ip:7f369eba543e sp:7ffe60bc9630 error:0 in 
libsystemd-shared-231.so[7f369eac9000+178000]
  [739038.092523] traps: systemd-resolve[22633] general protection 
ip:7fd8f27e6226 sp:7fffba5b6aa0 error:0 in 
libsystemd-shared-231.so[7fd8f2795000+178000]
  [739136.592518] systemd-resolve[23157]: segfault at 40 ip 
0040 sp 7ffd544b1cc8 error 14 in 
systemd-resolved[555e904e9000+4c000]
  [739582.092490] systemd-resolve[25373]: segfault at 50 ip 
0050 sp 7ffec6ab6c58 error 14 in 
systemd-resolved[557c48108000+4c000]
  [739933.342529] systemd-resolve[26927]: segfault at 131 ip 
55b472eb2866 sp 7ffe388c35c0 error 4 in 
systemd-resolved[55b472e91000+4c000]
  [740028.592553] systemd-resolve[27180]: segfault at 7f5e4bda5b68 ip 
7f5e4bda5b68 sp 7ffc2b198fc8 error 15 in libc-2.24.so[7f5e4bda5000+2000]
  [740553.092527] systemd-resolve[29516]: segfault at 55edabed2824 ip 
7f3bb8495235 sp 7ffcc8a01ed0 error 7 in 
libsystemd-shared-231.so[7f3bb8444000+178000]
  [740617.092527] traps: systemd-resolve[2

[Touch-packages] [Bug 1649370] Re: libnss-{resolve,myhostname} don’t install correctly if previously removed without being purged

[Steve Langasek]

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

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

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

Title:
  libnss-{resolve,myhostname} don’t install correctly if previously
  removed without being purged

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  # grep hosts /etc/nsswitch.conf
  hosts:  files myhostname dns
  # apt install libnss-resolve
  # grep hosts /etc/nsswitch.conf
  hosts:  files myhostname resolve [!UNAVAIL=return] dns
  # apt remove libnss-resolve
  # grep hosts /etc/nsswitch.conf
  hosts:  files myhostname dns
  # apt install libnss-resolve
  # grep hosts /etc/nsswitch.conf
  hosts:  files myhostname dns

  libnss-resolve.postinst and libnss-myhostname.postinst only update
  /etc/nsswitch.conf if [ "$1" = configure ] && [ -z "$2" ].  If the
  package was previously removed but not purged (it is in the Config-
  Files state), dpkg passes the previous version as $2, so this fails.

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

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

[Touch-packages] [Bug 1745690] [NEW] pcscd cannot load a usb device. Error with libccid.so: undefined symbol: libusb_handle_events_completed

[Yavor Nikolov]

Public bug reported:

I have a problem using my Smart Card with the latest ubuntu version
(17.10). (It works fine with Ubuntu 14.04).

$ sudo service pcscd status

● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: 
enabled)
   Active: inactive (dead) since Fri 2018-01-26 23:19:46 EET; 4min 58s ago
  Process: 6503 ExecStart=/usr/sbin/pcscd --foreground --auto-exit 
(code=exited, status=0/SUCCESS)
 Main PID: 6503 (code=exited, status=0/SUCCESS)
  CPU: 15ms

Jan 26 23:11:01 ubuntu systemd[1]: Started PC/SC Smart Card Daemon.
Jan 26 23:11:01 ubuntu pcscd[6503]:  dyn_unix.c:58:DYN_LoadLibrary() 
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so: 
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so: undefined 
symbol: libusb_handle_events_completed
Jan 26 23:11:01 ubuntu pcscd[6503]: 0144 
readerfactory.c:1081:RFInitializeReader() RFLoadReader failed: 0x80100014
Jan 26 23:11:01 ubuntu pcscd[6503]: 0058 readerfactory.c:376:RFAddReader() 
ACS ACR 38U-CCID init failed.
Jan 26 23:11:01 ubuntu pcscd[6503]: 0011 
hotplug_libudev.c:523:HPAddDevice() Failed adding USB device: ACS ACR 38U-CCID
Jan 26 23:14:38 ubuntu pcscd[6503]:  dyn_unix.c:58:DYN_LoadLibrary() 
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so: 
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so: undefined 
symbol: libusb_handle_events_completed
Jan 26 23:14:38 ubuntu pcscd[6503]: 0039 
readerfactory.c:1081:RFInitializeReader() RFLoadReader failed: 0x80100014
Jan 26 23:14:38 ubuntu pcscd[6503]: 0009 readerfactory.c:376:RFAddReader() 
ACS ACR 38U-CCID init failed.
Jan 26 23:14:38 ubuntu pcscd[6503]: 0007 
hotplug_libudev.c:523:HPAddDevice() Failed adding USB device: ACS ACR 38U-CCID


The problem is similar to something which someone else is facing: 
https://superuser.com/questions/1173940/debian-stretch-smartcard-reader-error-scardestablishcontext-service-not-availa

** Affects: pcsc-lite (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  pcscd cannot load a usb device. Error with libccid.so: undefined
  symbol: libusb_handle_events_completed

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I have a problem using my Smart Card with the latest ubuntu version
  (17.10). (It works fine with Ubuntu 14.04).

  $ sudo service pcscd status

  ● pcscd.service - PC/SC Smart Card Daemon
 Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
 Active: inactive (dead) since Fri 2018-01-26 23:19:46 EET; 4min 58s ago
Process: 6503 ExecStart=/usr/sbin/pcscd --foreground --auto-exit 
(code=exited, status=0/SUCCESS)
   Main PID: 6503 (code=exited, status=0/SUCCESS)
CPU: 15ms

  Jan 26 23:11:01 ubuntu systemd[1]: Started PC/SC Smart Card Daemon.
  Jan 26 23:11:01 ubuntu pcscd[6503]:  dyn_unix.c:58:DYN_LoadLibrary() 
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so: 
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so: undefined 
symbol: libusb_handle_events_completed
  Jan 26 23:11:01 ubuntu pcscd[6503]: 0144 
readerfactory.c:1081:RFInitializeReader() RFLoadReader failed: 0x80100014
  Jan 26 23:11:01 ubuntu pcscd[6503]: 0058 
readerfactory.c:376:RFAddReader() ACS ACR 38U-CCID init failed.
  Jan 26 23:11:01 ubuntu pcscd[6503]: 0011 
hotplug_libudev.c:523:HPAddDevice() Failed adding USB device: ACS ACR 38U-CCID
  Jan 26 23:14:38 ubuntu pcscd[6503]:  dyn_unix.c:58:DYN_LoadLibrary() 
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so: 
/usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so: undefined 
symbol: libusb_handle_events_completed
  Jan 26 23:14:38 ubuntu pcscd[6503]: 0039 
readerfactory.c:1081:RFInitializeReader() RFLoadReader failed: 0x80100014
  Jan 26 23:14:38 ubuntu pcscd[6503]: 0009 
readerfactory.c:376:RFAddReader() ACS ACR 38U-CCID init failed.
  Jan 26 23:14:38 ubuntu pcscd[6503]: 0007 
hotplug_libudev.c:523:HPAddDevice() Failed adding USB device: ACS ACR 38U-CCID

  
  The problem is similar to something which someone else is facing: 
https://superuser.com/questions/1173940/debian-stretch-smartcard-reader-error-scardestablishcontext-service-not-availa

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

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

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

[Steve Langasek]

Anders, are you still seeing this issue with currently-supported
versions of Ubuntu?  I have argued elsewhere that the correct thing to
do for 18.04 is to forcibly remove resolvconf on upgrades, switching
/etc/resolv.conf to exclusively point to /run/systemd/resolve/stub-
resolv.conf.  In the common case, however, this should not make a
difference.  What other sources of DNS settings do you have that are
feeding directly to resolvconf instead of resolved in 16.10 and later?

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

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

Status in systemd package in Ubuntu:
  Confirmed

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

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

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

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

[Touch-packages] [Bug 1650877] Re: systemd-resolved: resolve call failed: DNSSEC validation failed: failed-auxiliary

[Steve Langasek]

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

** This bug has been marked a duplicate of bug 1682499
   Disable DNSSEC by default

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

Title:
  systemd-resolved: resolve call failed: DNSSEC validation failed:
  failed-auxiliary

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After I boot Ubuntu 17.04 "Zesty Zapus" (dev)

  $ systemd-resolve www.facebook.com
  www.facebook.com: resolve call failed: DNSSEC validation failed: 
failed-auxiliary

  But after I have started Mozilla Firefox, and I try again it correctly
  resolves.

  $ systemd-resolve www.facebook.com
  www.facebook.com: 31.13.72.36
(star-mini.c10r.facebook.com)

  -- Information acquired via protocol DNS in 3.6ms.
  -- Data is authenticated: no

  This does not only apply to the above mentioned www.facebook.com domain.
  This seems to be related to a GitHub issue:
  https://github.com/systemd/systemd/issues/4003

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

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

[Touch-packages] [Bug 1663031] Re: cannot resolve www.facebook.com

[Steve Langasek]

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

** This bug is no longer a duplicate of bug 1650877
   systemd-resolved: resolve call failed: DNSSEC validation failed: 
failed-auxiliary
** This bug has been marked a duplicate of bug 1682499
   Disable DNSSEC by default

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

Title:
  cannot resolve www.facebook.com

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  $ systemd-resolve www.facebook.com 
  www.facebook.com: resolve call failed: 'star-mini.c10r.facebook.com' does not 
have any RR of the requested type

  But using dig:

  $ dig @8.8.8.8 www.facebook.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @8.8.8.8 www.facebook.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20609
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;www.facebook.com.IN  A

  ;; ANSWER SECTION:
  www.facebook.com. 734 IN  CNAME   star-mini.c10r.facebook.com.
  star-mini.c10r.facebook.com. 46   IN  A   31.13.93.36

  ;; Query time: 33 msec
  ;; SERVER: 8.8.8.8#53(8.8.8.8)
  ;; WHEN: Wed Feb 08 22:17:05 CET 2017
  ;; MSG SIZE  rcvd: 90

  $ systemd-resolve --status
  Global
   DNS Servers: 127.0.0.1
DNS Domain: fritz.box
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

  Link 6 (wwp0s20u7i8)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 4 (wlan0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  Link 2 (eth0)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: allow-downgrade
  DNSSEC supported: yes

  I'm currently connected via wlan0.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-8
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb  8 22:14:17 2017
  InstallationDate: Installed on 2014-02-07 (1097 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. Latitude E7240
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-15-generic.efi.signed 
root=UUID=052bd6e1-db02-4bca-9f9c-d5600c0237e1 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2017-02-08 (0 days ago)
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.asset.tag: humbaba
  dmi.board.name: 0531FD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: humbaba
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE7240:pvr01:rvnDellInc.:rn0531FD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1659520] Re: openvpn network manager plugin dns server settings do not take effect in 16.10

[Steve Langasek]

I believe this was fixed in Ubuntu 17.04 and later.  If you are still
experiencing this problem with a currently supported Ubuntu release,
please reopen this report.

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

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

Title:
  openvpn network manager plugin dns server settings do not take effect
  in 16.10

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  when using the network manager openvpn plugin the DNS servers do not
  always seem to correctly get passed to the system for use.

  Sometimes it works, but at some point resolved seems to choose to use
  the local DNS servers again and not use the ones provided by the
  openvpn server.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Thu Jan 26 10:25:46 2017
  InstallationDate: Installed on 2016-06-25 (214 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-12-26 (30 days ago)

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

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

[Touch-packages] [Bug 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => Fix Released

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

Title:
  systemd-resolved does not listen on TCP port, cannot serve large
  records (Cannot ping pod51041.outlook.com but can dig.)

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Trying to resolve pod51041.outlook.com's domain name seems to fail for
  applications:

  $ ping pod51041.outlook.com
  ping: pod51041.outlook.com: Temporary failure in name resolution

  (Also can't access via thunderbird).

  However, it seems to work directly via systemd-resolve:

  $ systemd-resolve pod51041.outlook.com
  pod51041.outlook.com: 40.97.160.2
    40.97.126.50
    132.245.38.194
    40.97.147.194
    132.245.41.34
    40.97.176.2
    40.97.150.242
    40.97.85.114
    40.97.120.50
    40.97.85.2
    40.97.176.34
    40.97.138.242
    40.97.166.18
    40.97.120.162
    40.97.119.82
    40.97.176.18
    40.97.85.98
    40.97.134.34
    40.97.84.18

  -- Information acquired via protocol DNS in 2.5ms.
  -- Data is authenticated: no

  It also works with dig and nslookup.

  Not quite sure why this is the case, I've spotted this issue upstream
  that looks similar: https://github.com/systemd/systemd/issues/6520.
  However, I'm not familiar enough with DNS to tell if it is the same
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Nov 10 13:10:02 2017
  InstallationDate: Installed on 2017-11-10 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  MachineType: LENOVO 2324BB9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324BB9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2324BB9
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1658592] Re: systemd-resolved causing google.com not reachable

[Steve Langasek]

This is definitely not reproducible for me.  It may have been a
duplicate of bug #1647031, however google.com is currently not a CNAME,
it is an A record instead.

Is this problem still reproducible for you?  If so, with which version
of Ubuntu?  (You originally reported this with Ubuntu 17.04 before
release; 17.04 is now end of life).

If you can reproduce the problem, please show the output of 'dig
google.com'.

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

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

Title:
  systemd-resolved causing google.com not reachable

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  System info:
  lsb_release -rd: Description: Ubuntu Zesty Zapus (development branch)
  Release:  17.04

  uname -a:
  Linux pc 4.9.0-12-generic #13-Ubuntu SMP Mon Jan 9 20:06:25 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

  systemd --version:
  systemd 232
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN

  Static IP address(10.0.0.250/16), DNS(8.8.8.8) and routes(10.0.0.1)
  are set manually in network manager.

  Problem Description:

  1. google.com is not accessible from firefox or chromium, but
  google.co.uk, google.co.jp can be accessble. Firefox would redirect
  google.com to
  "https://www.google.com.sg/?gfe_rd=cr&ei=eaCFWLfUDIe1vASXoY7gBA";
  reports an error "Firefox can’t find the server at www.google.com.sg."
  Chromium redirect to google.com.sg too and reports a DNS error.

  2. ping and host google.com shows no errors and reports correct IP
  addresses.

  3. ping: google.com.sg: Name or service not known

  4. host google.com.sg: google.com.sg has address 74.125.130.94

  5. entering 74.125.130.94 directly in Firefox address bar redirect the
  webpage to
  "https://www.google.com.sg/?gfe_rd=cr&ei=paKFWO2sJ9LFuASvwq2ADA";

  6. other PC running fedora distro in the same lan can reach google.com
  with firefox or chromium.

  7. Looking at /etc/resolve.conf, nameserver is 127.0.0.53. It also
  suggests systemd-resolved.service is in charge of name resolution. If
  I stop this service and change nameserver in /etc/resolv.conf to
  8.8.8.8, `google.com` can be accessed from firefox.

  8. If changing nameserver back to 127.0.0.53 and start systemd-
  resolved.service, google.com is not accessible from browser anymore.

  The above step seems to suggest the problem is with systemd-
  resolved.service.

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

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

[Touch-packages] [Bug 1653495] Re: systemd-resolved breaks Steam

[Steve Langasek]

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

** This bug has been marked a duplicate of bug 1647031
   systemd-resolved’s 127.0.0.53 server does not follow CNAME records

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

Title:
  systemd-resolved breaks Steam

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When systemd-resolved is active and /etc/resolv.conf points to
  127.0.0.53, steam fails to resolve domain names, and refuses to update
  or install games.  Often, it doesn't even start, because it wants to
  update itself, but cannot reach its content servers.

  Manually (dig/host/nslookup/etc), resolving works fine, and also
  Chrome etc do'nt show any problems.  It seems Steam uses some uncommon
  type of DNS records or so?

  If I change the nameserver in /etc/resolv.conf to 8.8.8.8, of to my
  local resolver, everything works fine again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-8
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jan  2 11:04:03 2017
  InstallationDate: Installed on 2016-12-22 (10 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Dell Inc. Latitude E7470
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-11-generic.efi.signed 
root=/dev/mapper/hostname-root ro nosplash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.3
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.resolved.conf: 2016-12-27T13:33:33.754548

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

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

[Touch-packages] [Bug 1742310] Re: No network in recovery mode (systemd-resolved does not start)

[Steve Langasek]

** Package changed: systemd (Ubuntu) => friendly-recovery (Ubuntu)

** Changed in: friendly-recovery (Ubuntu)
   Importance: Undecided => High

** Changed in: friendly-recovery (Ubuntu)
   Status: New => Triaged

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

Title:
  No network in recovery mode (systemd-resolved does not start)

Status in friendly-recovery package in Ubuntu:
  Triaged

Bug description:
  When booting into recovery mode and enabling networking, networking
  does not get enabled. DNS lookup doesn't work because systemd-resolved
  does not start and /etc/resolv.conf is a broken symlink.

  Steps to reproduce:

  1. Reboot.
  2. In the grub menu, select "Advanced options for Ubuntu" and then select 
boot in recovery mode.
  3. When the menu appears, select "networking". In the console you may notice 
a few errors that /etc/resolv.conf file not found.
  4. Select "drop to root" console.
  5. Try pinging some hosts, like "ping ubuntu.com". You will see that name 
resolution doesn't work.
  6. You can check that the network interface is up, "ip addr" displays valid 
info and the interface has an assigned local IP.
  7. You can check that /etc/resolv.conf is in fact a dangling link to 
../run/resolvconf/resolv.conf.
  8. You can see that systemd-resolved is not running: "systemctl status 
systemd-resolved" shows the service is dead.
  9. Invoking "systemctl start systemd-resolved" hangs indefinitely, the 
service not starting.

  The workaround to get DNS working is to replace /etc/resolv.conf with
  a valid link or a file with a DNS server.

  The DNS lookup and networking in general works fine if the system is
  booted normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jan 10 02:18:14 2018
  InstallationDate: Installed on 2015-05-01 (984 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  SourcePackage: systemd
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1668296] Re: not failing back to IPv4 when AAAA returns SERVFAIL

[Steve Langasek]

I cannot reproduce this with the libnss-resolve in Ubuntu 17.04 or
17.10.  The original problem was reported with systemd 231; 17.04
shipped with 232.  It is possible that this has been fixed in systemd
upstream (the linked upstream bug has been closed), or it's possible
that the DNS configuration for www.fidelityrewards.com has changed.  I'm
closing this fix-released, but if you know of another DNS name that is
still broken because of this, please reopen.

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

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

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

Title:
  not failing back to IPv4 when  returns SERVFAIL

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  A reocrd exists,  returns SERVFAIL, in this case resolution fails
  instead of falling back to IPv4 A record

  
  $ host www.fidelityrewards.com
  www.fidelityrewards.com has address 170.135.184.45
  Host www.fidelityrewards.com not found: 2(SERVFAIL)

  $ wget www.fidelityrewards.com
  --2017-02-27 07:41:57--  http://www.fidelityrewards.com/
  Resolving www.fidelityrewards.com (www.fidelityrewards.com)... failed: Name 
or service not known.
  wget: unable to resolve host address ‘www.fidelityrewards.com

  /etc/nsswitch.conf
  hosts:  files myhostname mdns4_minimal [NOTFOUND=return] resolve 
[!UNAVAIL=return] dns wins 

  
  libnss-resolve 231-9ubuntu3

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

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

[Touch-packages] [Bug 1665394] Re: DNS resolution of irc.freenode.net or chat.freenode.net fails

[Steve Langasek]

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

** This bug has been marked a duplicate of bug 1731522
   systemd-resolved does not listen on TCP port, cannot serve large records 
(Cannot ping pod51041.outlook.com but can dig.)

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

Title:
  DNS resolution of irc.freenode.net or chat.freenode.net fails

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.10 (from a base install upgraded several
  times), with proposed-updates enabled. Recently, I started having
  problems where I am unable to resolve irc.freenode.net.

  This is unrelated to the networks. I have been able to confirm that
  systemd-resolved is able to perform the name resolution. Yet,
  getaddrinfo() call returns -EAI_AGAIN error.

  This can be reproduced using getent:
  > $ getent ahosts irc.freenode.net
  > $

  While testing v4 or v6 directly returns something valid:
  > $ getent ahostsv4 irc.freenode.net
  > 38.229.70.22STREAM chat.freenode.net
  > 38.229.70.22DGRAM  
  > 38.229.70.22RAW
  > 130.239.18.119  STREAM 
  > 130.239.18.119  DGRAM  
  > 130.239.18.119  RAW
  [...]
  > $

  > $ getent ahostsv6 irc.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 STREAM chat.freenode.net
  > 2001:5a0:3604:1:64:86:243:181 DGRAM  
  > 2001:5a0:3604:1:64:86:243:181 RAW
  > 2001:6b0:e:2a18::118 STREAM 
  > 2001:6b0:e:2a18::118 DGRAM  
  > 2001:6b0:e:2a18::118 RAW
  [...]
  > $

  dpkg.log shows there has been some upgrade of systemd recently, though
  I cannot tell for sure if that directly relates to the problem, I do
  use suspend-to-ram a lot and reboot not that often.

  > $ lsb_release -a
  > LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  > Distributor ID: Ubuntu
  > Description:Ubuntu 16.10
  > Release:16.10
  > Codename:   yakkety

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

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

[Touch-packages] [Bug 1737250] Re: systemd-resolved returns only short hostname when PTR record of local IP is requested

[Steve Langasek]

Does setting 'LLMNR=no' in /etc/systemd/resolved.conf and restarting
systemd-resolved solve this for you?

(see also bug #1739672)

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

Title:
  systemd-resolved returns only short hostname when PTR record of local
  IP is requested

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10 comes with systemd-resolved as the default local
  resolver.

  When querying the PTR record of any local IP address it returns only
  the hostname (without domain) and does not forward the query to the
  available nameservers.

  This results in unwanted results.

  How do I change that behaviours without disabling and masking systemd-
  resolved and manually putting the nameservers in /etc/resolv.conf?

  Example:

  root@files05:~# host 192.168.48.115
  115.48.168.192.in-addr.arpa domain name pointer files05.
  root@files05:~# host 192.168.48.116
  116.48.168.192.in-addr.arpa domain name pointer files06.example.net.
  root@files05:~# host 192.168.48.120
  120.48.168.192.in-addr.arpa domain name pointer files05.
  root@files05:~# host 192.168.48.120 192.168.48.2
  Using domain server:
  Name: 192.168.48.2
  Address: 192.168.48.2#53
  Aliases: 

  120.48.168.192.in-addr.arpa domain name pointer fileserv.example.net.

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

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

[Touch-packages] [Bug 1745605] Re: package curl 7.35.0-1ubuntu2.13 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 curl in Ubuntu.
https://bugs.launchpad.net/bugs/1745605

Title:
  package curl 7.35.0-1ubuntu2.13 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in curl package in Ubuntu:
  New

Bug description:
  Not too sure

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: curl 7.35.0-1ubuntu2.13
  ProcVersionSignature: Ubuntu 3.13.0-141.190-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-141-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Fri Jan 26 20:23:37 2018
  DuplicateSignature: package:curl:7.35.0-1ubuntu2.13:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-11-09 (808 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: curl
  Title: package curl 7.35.0-1ubuntu2.13 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/curl/+bug/1745605/+subscriptions

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

[Touch-packages] [Bug 1737318] Re: dependency not met

[Steve Langasek]

If you didn't install these packages from artful-proposed, and you don't
have artful-proposed configured in your sources.list, why is apt
reporting to you that it is installing a version of systemd that is only
published in artful-proposed?

What is the output of 'apt policy systemd'?

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

Title:
  dependency not met

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  The following packages have unmet dependencies:
   libnss-resolve : Depends: systemd (= 234-2ubuntu12.1) but 234-2ubuntu12.2 is 
to be installed
  open: 23; closed: 490; defer: 5; conflict: 5  

.The following actions will 
resolve these dependencies:

   Keep the following packages at their current version:
  1) libpam-systemd [234-2ubuntu12.1 (artful-security, artful-updates, now)]
  2) libsystemd0 [234-2ubuntu12.1 (artful-security, artful-updates, now)]   
  3) systemd [234-2ubuntu12.1 (artful-security, artful-updates, now)]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libnss-resolve 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Dec  9 07:40:09 2017
  InstallationDate: Installed on 2016-10-02 (432 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160512)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (46 days ago)

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

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

[Touch-packages] [Bug 1732019] Re: systemd-resolved does not respect dynamic dns updates

[Steve Langasek]

Please show the output of systemd-resolve --status when this problem
occurs.

The list of DNS servers is not an ordered list.  If you need the VPN DNS
server to be used because it returns different records than the public
DNS, then you have a "split DNS" configuration; seeing this output will
help us diagnose whether this is configured correctly in systemd-
resolved.  It's possible that the NM strongswan plugin does not
correctly feed split DNS information to systemd-resolved.  (The network-
manager-openvpn plugin, for comparison, does.)

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

Title:
  systemd-resolved does not respect dynamic dns updates

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I connect to a vpn using strongswan nm. When connected a new dns
  server is added to systemd-resloved and can be observed via systemd-
  resolved --status as beeing the first in the List. But this dns server
  is not beeing queried while resolving.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov 13 21:39:48 2017
  InstallationDate: Installed on 2017-11-06 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook P64_HJ,HK1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=7e37331f-f91c-42cc-8264-25e3d4d6fba4 ro quiet splash acpi_osi=! 
"acpi_osi=Windows 2009" vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-11-06 (7 days ago)
  dmi.bios.date: 02/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd02/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Touch-packages] [Bug 1731211] Re: systemd breaks interface configuration due to late resolv.conf

[Steve Langasek]

What exactly are the contents of /etc/network/interfaces.d/vlan0?  I
would not normally expect dnsmasq to be started as part of the network
interface configuration via ifupdown.  If there is a reason to configure
it this way, then /lib/systemd/system/networking.service would need to
be changed to start after systemd-resolved.  But perhaps there is a
different way that this could be done that would be simpler and more
consistent with the current boot ordering model.

** Package changed: systemd (Ubuntu) => ifupdown (Ubuntu)

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

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

Title:
  systemd breaks interface configuration due to late resolv.conf

Status in ifupdown package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have configured a linux bridge (vlan0) for virtual machines in
  /etc/network/interfaces.d/vlan0. The usual configuration including to
  start dnasmasq as a dhcp and dns server for that network.

  With 17.10 that fails, systemd can't start networking.service

  # systemctl |fgrep networking.service  
  ● networking.service  
  loaded failed failedRaise network interfaces   


  systemctl status networking.service 
  ● networking.service - Raise network interfaces
 Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Thu 2017-11-09 10:16:02 CET; 1h 
35min ago
   Docs: man:interfaces(5)
   Main PID: 1938 (code=exited, status=1/FAILURE)
CPU: 257ms

  Nov 09 10:15:59 pcdanisch systemd[1]: Starting Raise network interfaces...
  Nov 09 10:16:01 pcdanisch ifup[1938]: Waiting for vlan0 to get ready (MAXWAIT 
is 2 seconds).
  Nov 09 10:16:01 pcdanisch ifup[1938]: Set name-type for VLAN subsystem. 
Should be visible in /proc/net/vlan/config
  Nov 09 10:16:01 pcdanisch ifup[1938]: dnsmasq: directory /etc/resolv.conf for 
resolv-file is missing, cannot poll
  Nov 09 10:16:01 pcdanisch ifup[1938]: Failed to bring up vlan0.
  Nov 09 10:16:02 pcdanisch systemd[1]: networking.service: Main process 
exited, code=exited, status=1/FAILURE
  Nov 09 10:16:02 pcdanisch systemd[1]: Failed to start Raise network 
interfaces.
  Nov 09 10:16:02 pcdanisch systemd[1]: networking.service: Unit entered failed 
state.
  Nov 09 10:16:02 pcdanisch systemd[1]: networking.service: Failed with result 
'exit-code'.

  
  # ls -lF /etc/resolv.conf 
  lrwxrwxrwx 1 root root 39 Okt 24 11:58 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf

  
  As far as I can see at that time of booting, the /etc/resolv.conf shows into 
a a directory which is not yet created (/run is a tmpfs, thus empty at boot 
time), and I have seen more trouble caused by this, that there is a certain 
amount of time in the boot process, where /etc/resolv.conf is neither absent 
nor readable, but a dangling symlink, causing lots of trouble. 

  This construction to have a permanent symlink pointing to nowhere
  while booting is broken by design.

  Furthermore, it's really difficult to get rid of that filthy systemd
  dns. That's really odd stuff.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Nov  9 11:53:46 2017
  InstallationDate: Installed on 2017-10-24 (16 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=c100cc19-4ea7-4c2c-a2ee-10d8ed40c2e7 ro rootflags=subvol=@ nomodeset 
quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

-- 
Mailin

[Touch-packages] [Bug 1745605] Re: package curl 7.35.0-1ubuntu2.13 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Leonidas S. Barbosa]

** Information type changed from Private Security to Public

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

Title:
  package curl 7.35.0-1ubuntu2.13 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in curl package in Ubuntu:
  New

Bug description:
  Not too sure

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: curl 7.35.0-1ubuntu2.13
  ProcVersionSignature: Ubuntu 3.13.0-141.190-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-141-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Fri Jan 26 20:23:37 2018
  DuplicateSignature: package:curl:7.35.0-1ubuntu2.13:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-11-09 (808 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: curl
  Title: package curl 7.35.0-1ubuntu2.13 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/curl/+bug/1745605/+subscriptions

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

[Touch-packages] [Bug 1725928] Re: package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files

[Joe Ferrari]

I got it straightened out folks.  Thank you for the replies.  I had to
remove the previous version of Wine in order to install the newer
version.

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages
  with differing files

Status in sane-backends package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  New

Bug description:
  
  From #3 comment below, to get a workaround, try:

  
  sudo apt-get -o Dpkg::Options::="--force-overwrite" install --reinstall 
libsane1:i386 (or your real package name)

  ***

  apport error this morning.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Oct 22 09:37:46 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-edJWJn/5-libsane1_1.0.27-1~experimental2ubuntu1_i386.deb 
(--unpack):
    trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2016-10-08 (378 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)

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

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

[Touch-packages] [Bug 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

[Steve Langasek]

According to https://github.com/systemd/systemd/issues/6520 this can be
worked around by setting DNSStubListener=yes in
/etc/systemd/resolved.conf.  This is disabled by default due to
.

It is not ideal to have systemd-resolved conflict with other nameservers
listening on 0.0.0.0:53, but as a default behavior of systemd-resolved
in Ubuntu, barring any other upstream fix for
, this should be our
fallback position for bionic.

** Bug watch added: github.com/systemd/systemd/issues #6520
   https://github.com/systemd/systemd/issues/6520

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/6520
   Importance: Unknown
   Status: Unknown

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

Title:
  systemd-resolved does not listen on TCP port, cannot serve large
  records (Cannot ping pod51041.outlook.com but can dig.)

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Trying to resolve pod51041.outlook.com's domain name seems to fail for
  applications:

  $ ping pod51041.outlook.com
  ping: pod51041.outlook.com: Temporary failure in name resolution

  (Also can't access via thunderbird).

  However, it seems to work directly via systemd-resolve:

  $ systemd-resolve pod51041.outlook.com
  pod51041.outlook.com: 40.97.160.2
    40.97.126.50
    132.245.38.194
    40.97.147.194
    132.245.41.34
    40.97.176.2
    40.97.150.242
    40.97.85.114
    40.97.120.50
    40.97.85.2
    40.97.176.34
    40.97.138.242
    40.97.166.18
    40.97.120.162
    40.97.119.82
    40.97.176.18
    40.97.85.98
    40.97.134.34
    40.97.84.18

  -- Information acquired via protocol DNS in 2.5ms.
  -- Data is authenticated: no

  It also works with dig and nslookup.

  Not quite sure why this is the case, I've spotted this issue upstream
  that looks similar: https://github.com/systemd/systemd/issues/6520.
  However, I'm not familiar enough with DNS to tell if it is the same
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Nov 10 13:10:02 2017
  InstallationDate: Installed on 2017-11-10 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  MachineType: LENOVO 2324BB9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324BB9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2324BB9
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1725928] Re: package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files

[Launchpad Bug Tracker]

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages
  with differing files

Status in sane-backends package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  New

Bug description:
  
  From #3 comment below, to get a workaround, try:

  
  sudo apt-get -o Dpkg::Options::="--force-overwrite" install --reinstall 
libsane1:i386 (or your real package name)

  ***

  apport error this morning.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Oct 22 09:37:46 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-edJWJn/5-libsane1_1.0.27-1~experimental2ubuntu1_i386.deb 
(--unpack):
    trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2016-10-08 (378 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)

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

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

[Touch-packages] [Bug 1730744] Re: sudo is slow (10 seconds) when hostname is not resolvable

[Steve Langasek]

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

** This bug has been marked a duplicate of bug 1739672
   Regression in getaddrinfo(): calls block for much longer on Bionic (compared 
to Xenial), please disable LLMNR

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

Title:
  sudo is slow (10 seconds) when hostname is not resolvable

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm seeing very slow 'sudo' times in a qemu guest when the host uses 
systemd-resolved.
  If I change /etc/resolv.conf on the host to point directly to a dns server 
(8.8.8.8) then the problem goes away.

  
  To recreate, you can download a cloud image and boot it under qemu with a 
command line like:
cloud-localds seed.img user-data meta-data 
qemu-system-x86_64 -enable-kvm \
   -device virtio-net-pci,netdev=net00 \
   -netdev type=user,id=net00 \
   -drive file=root.img,id=disk00,if=none,index=0 \
   -device virtio-blk,drive=disk00,serial=root.img \
   -drive file=seed.img,id=disk01,if=none,index=1 \
   -device virtio-blk,drive=disk01,serial=seed.img \
   -m 768

  Make sure that your hostname does not resolve (change it to 'bogus-host1').
  Log into the guest and then just try sudo, you'll see something like:
  # time sudo ls
  sudo: unable to resolve host rooturl-trusty

  real0m10.029s
  user0m0.006s
  sys 0m0.011s

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

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

[Touch-packages] [Bug 1728560] Re: Cannot resolve smtp-mail.outlook.com

[Steve Langasek]

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

Looking at the output of a lookup today of smtp-mail.outlook.com, it
appears the DNS configuration of this name has changed (there are now
much fewer CNAMEs chained together than there were when this bug was
reported).  So I believe the symptom that was reported is now resolved,
but that the root cause is the same as bug #1731522 - resolved fails to
implement TCP support.

** This bug has been marked a duplicate of bug 1731522
   systemd-resolved fails to fall back to TCP for large records (Cannot ping 
pod51041.outlook.com but can dig.)

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

Title:
  Cannot resolve smtp-mail.outlook.com

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10, applications can no longer resolve smtp-
  mail.outlook.com, although host can:

  > mjg@payens:~/Projects/GNOME/geary$ telnet smtp-mail.outlook.com 25
  > telnet: could not resolve smtp-mail.outlook.com/25: Temporary failure in 
name resolution
  > mjg@payens:~/Projects/GNOME/geary$ telnet smtp-mail.outlook.com
  > telnet: could not resolve smtp-mail.outlook.com/telnet: Temporary failure 
in name resolution
  > mjg@payens:~/Projects/GNOME/geary$ host smtp-mail.outlook.com
  > smtp-mail.outlook.com is an alias for smtp.live.com.
  > smtp.live.com is an alias for smtp.glbdns2.microsoft.com.
  > smtp.glbdns2.microsoft.com is an alias for smtp.office365.com.
  > smtp.office365.com is an alias for smtp.outlook.office365.com.
  > smtp.outlook.office365.com is an alias for outlook.office365.com.
  > outlook.office365.com is an alias for lb.geo.office365.com.
  > lb.geo.office365.com is an alias for outlook.office365.com.g.office365.com.
  > outlook.office365.com.g.office365.com is an alias for 
outlook-au.office365.com.
  > outlook-au.office365.com has address 40.100.151.226
  > [many more replies snipped]

  Also reported on ask.ubuntu.com:
  https://askubuntu.com/questions/969689/dns-problem-trying-to-ping-or-
  send-email-using-smtp-mail-outlook-com-after-upgra

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 30 21:07:17 2017
  InstallationDate: Installed on 2015-07-22 (831 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor 
i915.fastboot=1 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B18.1610241407
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B18.1610241407:bd10/24/2016:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Touch-packages] [Bug 1731522] Re: systemd-resolved fails to fall back to TCP for large records (Cannot ping pod51041.outlook.com but can dig.)

[Steve Langasek]

I can confirm this problem.  'dig' works because by default it's only
asking for A records; but applications on ipv6-enabled clients will ask
for both A and  records, and if I query  for this name, the
response is too big to fit in a udp packet:

$ nslookup -q= pod51041.outlook.com 192.168.15.1
;; Truncated, retrying in TCP mode.
Server: 192.168.15.1
Address:192.168.15.1#53

Non-authoritative answer:
pod51041.outlook.comhas  address 2603:1036:d02::2
pod51041.outlook.comhas  address 2603:1036:d02:6::2
pod51041.outlook.comhas  address 2603:1036:d02:7::2
pod51041.outlook.comhas  address 2a01:111:f400:5201::2
pod51041.outlook.comhas  address 2a01:111:f400:f370::2
pod51041.outlook.comhas  address 2603:1036:3:cc::2
pod51041.outlook.comhas  address 2603:1036:3:108::2
pod51041.outlook.comhas  address 2603:1036:4:6f::2
pod51041.outlook.comhas  address 2603:1036:4:71::2
pod51041.outlook.comhas  address 2603:1036:101:3a::2
pod51041.outlook.comhas  address 2603:1036:102:53::2
pod51041.outlook.comhas  address 2603:1036:102:cb::2
pod51041.outlook.comhas  address 2603:1036:405:3b::2
pod51041.outlook.comhas  address 2603:1036:804:1::2
pod51041.outlook.comhas  address 2603:1036:804:a::2
pod51041.outlook.comhas  address 2603:1036:902:a3::2
pod51041.outlook.comhas  address 2603:1036:906:4f::2
pod51041.outlook.comhas  address 2603:1036:d01:1::2

Authoritative answers can be found from:
outlook.com nameserver = ns2.msft.net.
outlook.com nameserver = ns3.msft.net.
outlook.com nameserver = ns1.msft.net.
outlook.com nameserver = ns2a.o365filtering.com.
outlook.com nameserver = ns4.msft.net.
outlook.com nameserver = ns1a.o365filtering.com.
outlook.com nameserver = ns4a.o365filtering.com.
ns1.msft.netinternet address = 208.84.0.53
ns1.msft.nethas  address 2620:0:30::53
ns2.msft.netinternet address = 208.84.2.53
ns2.msft.nethas  address 2620:0:32::53
ns3.msft.netinternet address = 193.221.113.53
ns3.msft.nethas  address 2620:0:34::53
ns4.msft.netinternet address = 208.76.45.53
ns4.msft.nethas  address 2620:0:37::53
ns1a.o365filtering.com  internet address = 157.56.110.11
ns2a.o365filtering.com  internet address = 157.56.116.52
ns4a.o365filtering.com  internet address = 157.55.133.11

$

If I try this against systemd-resolved, I see:

$ nslookup -q= pod51041.outlook.com 
;; Warning: Message parser reports malformed message packet.
;; Truncated, retrying in TCP mode.
;; Connection to 127.0.0.53#53(127.0.0.53) for pod51041.outlook.com failed: 
connection refused.

$

So the problem is that systemd-resolved is not handling tcp requests at
all.

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

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

** Summary changed:

- systemd-resolved fails to fall back to TCP for large records (Cannot ping 
pod51041.outlook.com but can dig.)
+ systemd-resolved does not listen on TCP port, cannot serve large records 
(Cannot ping pod51041.outlook.com but can dig.)

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

Title:
  systemd-resolved does not listen on TCP port, cannot serve large
  records (Cannot ping pod51041.outlook.com but can dig.)

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Trying to resolve pod51041.outlook.com's domain name seems to fail for
  applications:

  $ ping pod51041.outlook.com
  ping: pod51041.outlook.com: Temporary failure in name resolution

  (Also can't access via thunderbird).

  However, it seems to work directly via systemd-resolve:

  $ systemd-resolve pod51041.outlook.com
  pod51041.outlook.com: 40.97.160.2
    40.97.126.50
    132.245.38.194
    40.97.147.194
    132.245.41.34
    40.97.176.2
    40.97.150.242
    40.97.85.114
    40.97.120.50
    40.97.85.2
    40.97.176.34
    40.97.138.242
    40.97.166.18
    40.97.120.162
    40.97.119.82
    40.97.176.18
    40.97.85.98
    40.97.134.34
    40.97.84.18

  -- Information acquired via protocol DNS in 2.5ms.
  -- Data is authenticated: no

  It also works with dig and nslookup.

  Not quite sure why this is the case, I've spotted this issue upstream
  that looks similar: https://github.com/systemd/systemd/issues/6520.
  However, I'm not familiar enough with DNS to tell if it is the same
  issue.

  ProblemType: Bug
  DistroRelease: 

[Touch-packages] [Bug 1731522] Re: systemd-resolved fails to fall back to TCP for large records (Cannot ping pod51041.outlook.com but can dig.)

[Steve Langasek]

** Summary changed:

- Cannot ping pod51041.outlook.com but can dig.
+ systemd-resolved fails to fall back to TCP for large records (Cannot ping 
pod51041.outlook.com but can dig.)

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

Title:
  systemd-resolved fails to fall back to TCP for large records (Cannot
  ping pod51041.outlook.com but can dig.)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Trying to resolve pod51041.outlook.com's domain name seems to fail for
  applications:

  $ ping pod51041.outlook.com
  ping: pod51041.outlook.com: Temporary failure in name resolution

  (Also can't access via thunderbird).

  However, it seems to work directly via systemd-resolve:

  $ systemd-resolve pod51041.outlook.com
  pod51041.outlook.com: 40.97.160.2
    40.97.126.50
    132.245.38.194
    40.97.147.194
    132.245.41.34
    40.97.176.2
    40.97.150.242
    40.97.85.114
    40.97.120.50
    40.97.85.2
    40.97.176.34
    40.97.138.242
    40.97.166.18
    40.97.120.162
    40.97.119.82
    40.97.176.18
    40.97.85.98
    40.97.134.34
    40.97.84.18

  -- Information acquired via protocol DNS in 2.5ms.
  -- Data is authenticated: no

  It also works with dig and nslookup.

  Not quite sure why this is the case, I've spotted this issue upstream
  that looks similar: https://github.com/systemd/systemd/issues/6520.
  However, I'm not familiar enough with DNS to tell if it is the same
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Nov 10 13:10:02 2017
  InstallationDate: Installed on 2017-11-10 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  MachineType: LENOVO 2324BB9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=8ab6bf88-72bd-4308-941e-3b36d4d7811b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324BB9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn2324BB9:pvrThinkPadX230:rvnLENOVO:rn2324BB9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2324BB9
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

[Launchpad Bug Tracker]

This bug was fixed in the package ntp - 1:4.2.8p10+dfsg-5ubuntu5

---
ntp (1:4.2.8p10+dfsg-5ubuntu5) bionic; urgency=medium

  * debian/apparmor-profile: avoid denies to to arg checks (LP:
#1741227)

 -- Christian Ehrhardt   Thu, 04 Jan
2018 14:20:53 +0100

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

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released

Bug description:
  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 1727566] Re: extra left-behind domains break domain name rsolution

[Steve Langasek]

Thank you for reporting this bug and helping to improve Ubuntu.

Why do you believe that the problem here is one of 'leftover state'?
The systemd-resolve --status output shows a simple config, with a domain
search list and two DNS servers (one ipv4 address, one ipv6 address).
If some of this state is "leftover", it's not clear what state that is.

Are 10.1.0.1 and fda0:5173:b519::1 the correct DNS servers for your home
wifi?  Do these DNS lookups work correctly when you issue them directly
against the configured nameservers? (nslookup webvpn.purestorage.com
10.1.0.1; nslookup webvpn.purestorage.com fda0:5173:b519::1)  What
happens if you try to do the lookup with 'nslookup
webvpn.purestorage.com' instead of with systemd-resolve? (systemd-
resolve uses a different protocol to talk to systemd-resolved, and may
give different results - which normally indicates a bug.)

Can you provide a network trace of the DNS traffic when these lookups
fail?

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

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

Title:
  extra left-behind domains break domain name rsolution

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  This seems related to LP: #1717995 but that is marked fixed.

  I used my laptop at work, where I have a docking station with USB
  ethernet included (interface enx0050b6cf4d4a).  The dhcp on the wired
  ethernet includes my work domain, purestorage.com.  I undocked,
  suspended, and came home, where I have no USB ethernet (just wifi
  wlp4s0), and dhcp on wifi doesn't mention purestorage.com.  However, I
  still have leftover state that stops purestorage.com names from
  resolving:

  $ systemd-resolve webvpn.purestorage.com
  webvpn.purestorage.com: resolve call failed: No appropriate name servers or 
networks for name found

  $ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  search lan purestorage.com dev.purestorage.com

  $ systemd-resolve --status
  Global
DNS Domain: lan
purestorage.com
dev.purestorage.com
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

  Link 3 (wlp4s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 10.1.0.1
fda0:5173:b519::1
DNS Domain: lan

  Link 2 (enp0s31f6)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no

  It seems there are still issues around network interfaces being
  removed but leaving behind their DNS config.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 25 17:48:47 2017
  InstallationDate: Installed on 2016-09-01 (419 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. 
   Bus 001 Device 003: ID 13d3:5248 IMC Networks 
   Bus 001 Device 005: ID 056a:5087 Wacom Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FRS2FK00
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_U

[Touch-packages] [Bug 1725680] Re: DNS name resolution doesn't work on Artful

[Steve Langasek]

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

** This bug has been marked a duplicate of bug 1727237
   systemd-resolved is not finding a domain

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

Title:
  DNS name resolution doesn't work on Artful

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  If I boot my laptop with a live image or an installation of Ubuntu
  17.10, DNS name resolution doesn't work (which means I can't access
  any website).

  Steps to reproduce:
  - Boot laptop with Ubuntu 17.10 live image
  - Connect to my wireless network
  - Try to ping any website, e.g. ping ubuntu.com. This immediately fails with 
the error message "Name or service not known"
  - Try to ping an IP-adress, e.g. ping 8.8.8.8 : this works.

  As a workaround, I can get a temporarily working DNS resolution by
  manually editing /etc/resolv.conf (symlink to /run/systemd/resolve
  /stub-resolve.conf) and setting the "nameserver" entry to 8.8.8.8 or
  some other known DNS server.

  On Ubuntu 17.04 this bug is not present.

  The original address in /run/systemd/resolve/stub-resolve.conf is
  127.0.0.53 . I get immediate replies if I ping this address, but
  nevertheless DNS resolution doesn't work.

  It seems that the service systemd-networkd isn't active by default:
  $ sudo systemctl status systemd-networkd
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendo
 Active: inactive (dead)
   Docs: man:systemd-networkd.service(8)

  Manually starting it doesn't seem to help for this bug.

  systemd-resolved is active:

  $ sudo systemctl status systemd-resolved
  ● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor
 Active: active (running) since Sat 2017-10-21 12:13:12 UTC; 44min ago
   Docs: man:systemd-resolved.service(8)
 https://www.freedesktop.org/wiki/Software/systemd/resolved
 
https://www.freedesktop.org/wiki/Software/systemd/writing-network-con
 
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cl
   Main PID: 1095 (systemd-resolve)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/systemd-resolved.service
 └─1095 /lib/systemd/systemd-resolved

  Okt 21 12:13:12 ubuntu systemd[1]: Starting Network Name Resolution...
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Positive Trust Anchors:
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 19036 8 2 
49aac11d7b6f644
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 20326 8 2 
e06d44b80b8f1d3
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Negative trust anchors: 
10.in-add
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Using system hostname 'ubuntu'.
  Okt 21 12:13:12 ubuntu systemd[1]: Started Network Name Resolution.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.387
  Date: Sat Oct 21 12:26:00 2017
  ExecutablePath: /lib/systemd/systemd-resolved
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Acer Extensa 5635Z
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V0.3305
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV0.3305:bd08/14/2009:svnAcer:pnExtensa5635Z:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635Z
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1720976] Re: DNS server in NM static ethernet config fails to configure in systemd-resolved

[Steve Langasek]

I have tested on artful here with a NetworkManager wired connection with
static DNS and cannot reproduce the problem.

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

Title:
  DNS server in NM static ethernet  config fails to configure in
  systemd-resolved

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

Bug description:
  1)
  root@dimension:/home/bp1# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Codename: artful
  root@dimension:/home/bp1# 
  2)
  systemd:
Installed: 234-2ubuntu10
Candidate: 234-2ubuntu10
Version table:
   *** 234-2ubuntu10 500
  500 http://gb.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  3) DNS resolution
  4) No DNS resolution from my configured DNS (in my case 192.168.1.1)
  Workarounds: 
  Enable FallbackDNS=8.8.8.8 8.8.4.4 in resolved.conf
  Or running dhclient

  Fresh boot of Artful (static IP via network manager and DNS should be
  at 192.168.1.1):

  bp1@dimension:~$ ifconfig 
  enp8s0: flags=4163  mtu 1500
  inet 192.168.1.5  netmask 255.255.255.0  broadcast 192.168.1.255
  inet6 fe80::99f:fae5:1467:a576  prefixlen 64  scopeid 0x20
  ether 00:1e:4f:e9:f1:c1  txqueuelen 1000  (Ethernet)
  RX packets 141  bytes 14707 (14.7 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 234  bytes 29807 (29.8 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 16  

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1000  (Local Loopback)
  RX packets 556  bytes 33758 (33.7 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 556  bytes 33758 (33.7 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  bp1@dimension:~$ ping www.dn.se
  ping: www.dn.se: Name or service not known
  bp1@dimension:~$ su
  Password: 
  root@dimension:/home/bp1# systemd-resolve --status
  Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

  Link 2 (enp8s0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
  root@dimension:/home/bp1# ping www.dn.se
  ping: www.dn.se: Name or service not known
  root@dimension:/home/bp1# nano /etc/systemd/resolved.conf 
  root@dimension:/home/bp1# cat /etc/systemd/resolved.conf
  #  This file is part of systemd.
  #
  #  systemd is free software; you can redistribute it and/or modify it
  #  under the terms of the GNU Lesser General Public License as published by
  #  the Free Software Foundation; either version 2.1 of the License, or
  #  (at your option) any later version.
  #
  # Entries in this file show the compile time defaults.
  # You can change settings by editing this file.
  # Defaults can be restored by simply deleting this file.
  #
  # See resolved.conf(5) for details

  [Resolve]
  #DNS=
  FallbackDNS=8.8.8.8 8.8.4.4
  #Domains=
  #LLMNR=yes
  #MulticastDNS=yes
  #DNSSEC=no
  #Cache=yes
  #DNSStubListener=udp
  root@dimension:/home/bp1# ps ax | grep systemd
254 ?Ss 0:00 /lib/systemd/systemd-journald
292 ?Ss 0:00 /lib/systemd/systemd-udevd
573 ?Ssl0:00 /lib/systemd/systemd-timesyncd
585 ?Ss 0:00 /lib/systemd/systemd-networkd
701 ?Ss 0:00 /lib/systemd/systemd-logind
735 ?Ss 0:00 /usr/bin/dbus-daemon --system --address=systemd: 
--nofork --nopidfile --systemd-activation
844 ?Ss 0:00 /lib/systemd/systemd-resolved
   1138 ?Ss

[Touch-packages] [Bug 1738085] Re: Bridge gets created while the network interfaces are still being renamed

[Dawid Wróbel]

Can anyone please acknowledge this issue and assign it?

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

Title:
  Bridge gets created while the network interfaces are still being
  renamed

Status in bridge-utils package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I have a problem with bridge configuration for the interfaces on my
  system that I also happen to rename explicitly.

  Specifically, I have following network configuration:

  # WAN interface
  auto wan
  iface wan inet dhcp

  # LAN interfaces
  iface wlan inet manual
  iface lan1 inet manual
  iface lan2 inet manual
  iface lan3 inet manual

  # LAN bridge
  auto lan
  iface lan inet static
  address 10.0.0.1
  netmask 255.255.255.0
  bridge_ports wlan lan1 lan2 lan3

  I use systemd .link files for renaming each of the 5 bridged
  interfaces, e.g.

  cat /etc/systemd/network/10-lan1.link
  [Match]
  MACAddress=90:e2:ba:ae:e8:21

  [Link]
  Name=lan1

  (BTW, I previously used udev rules to handle the renaming, before I
  migrated to systemd .link files hoping for improvement)

  Upon system boot, I see following messages:

  Dec 13 16:03:38 trout kernel: [2.61] r8169 :03:00.0 lan3: renamed 
from eth0
  Dec 13 16:03:38 trout kernel: [2.729493] igb :01:00.0 wlan: renamed 
from eth1
  Dec 13 16:03:38 trout kernel: [2.867121] igb :01:00.2 lan2: renamed 
from eth2
  Dec 13 16:03:38 trout kernel: [2.879221] igb :01:00.1 lan1: renamed 
from eth0
  Dec 13 16:03:38 trout kernel: [2.899203] igb :01:00.3 wan: renamed 
from eth3
  Dec 13 16:03:38 trout kernel: [   20.572747] bridge: automatic filtering via 
arp/ip/ip6tables has been deprecated. Update your scripts t
  o load br_netfilter if you need this.
  Dec 13 16:03:38 trout kernel: [   20.575364] device lan1 entered promiscuous 
mode
  Dec 13 16:03:38 trout kernel: [   20.705483] IPv6: ADDRCONF(NETDEV_UP): lan1: 
link is not ready
  Dec 13 16:03:38 trout kernel: [   21.097073] rename7: renamed from lan
  Dec 13 16:04:29 trout systemd-udevd[466]: seq 2799 '/devices/virtual/net/lan' 
is taking a long time
  Dec 13 16:04:59 trout systemd-udevd[540]: error changing net interface name 
'lan' to 'lan1': File exists
  Dec 13 16:04:59 trout systemd-udevd[540]: could not rename interface '7' from 
'lan' to 'lan1': File exists
  Dec 13 16:04:59 trout systemd[1]: Started ifup for lan.
  Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev 
sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths 
/sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and 
/sys/devices/virtual/net/lan
  Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev 
sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths 
/sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and 
/sys/devices/virtual/net/rename7
  Dec 13 16:04:59 trout systemd-udevd[543]: Could not generate persistent MAC 
address for lan: No such file or directory
  Dec 13 16:04:59 trout systemd[1]: Started ifup for lan.
  Dec 13 16:04:59 trout systemd[1]: Found device /sys/subsystem/net/devices/lan.
  Dec 13 16:04:59 trout kernel: [  111.797526] device wlan entered promiscuous 
mode
  Dec 13 16:04:59 trout ifup[1753]: /sbin/ifup: waiting for lock on 
/run/network/ifstate.lan
  Dec 13 16:04:59 trout kernel: [  111.943158] device lan3 entered promiscuous 
mode
  Dec 13 16:05:00 trout kernel: [  112.240052] r8169 :03:00.0 lan3: link 
down
  Dec 13 16:05:00 trout kernel: [  112.240081] r8169 :03:00.0 lan3: link 
down
  Dec 13 16:05:00 trout kernel: [  112.242397] IPv6: ADDRCONF(NETDEV_UP): lan: 
link is not ready
  Dec 13 16:05:00 trout sh[1689]: Waiting for lan to get ready (MAXWAIT is 32 
seconds).
  Dec 13 16:05:00 trout CRON[1841]: (root) CMD ([ -x /usr/sbin/dma ] && 
/usr/sbin/dma -q1)
  Dec 13 16:05:01 trout kernel: [  113.610184] igb :01:00.2 lan2: igb: lan2 
NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
  Dec 13 16:05:01 trout kernel: [  113.610324] lan: port 2(lan2) entered 
forwarding state
  Dec 13 16:05:01 trout kernel: [  113.610365] lan: port 2(lan2) entered 
forwarding state
  Dec 13 16:05:01 trout kernel: [  113.610486] IPv6: ADDRCONF(NETDEV_CHANGE): 
lan: link becomes ready

  And after the boot process completes, the bridge is not configured as 
requested:
  # brctl show
  bridge name bridge id   STP enabled interfaces
  lan 8000.7085c2026d54   no  lan2
  lan3
  wlan
  rename7 8000.90e2baaee821   no  lan1

  Note that while the "rename7" name of the bridge seems to be constant,
  the interface bridged is not.

  Pro

[Touch-packages] [Bug 1720976] Re: DNS server in NM static ethernet config fails to configure in systemd-resolved

[Steve Langasek]

** Summary changed:

- no DNS resolution via systemd
+ DNS server in NM static ethernet  config fails to configure in 
systemd-resolved

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

Title:
  DNS server in NM static ethernet  config fails to configure in
  systemd-resolved

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

Bug description:
  1)
  root@dimension:/home/bp1# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Codename: artful
  root@dimension:/home/bp1# 
  2)
  systemd:
Installed: 234-2ubuntu10
Candidate: 234-2ubuntu10
Version table:
   *** 234-2ubuntu10 500
  500 http://gb.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  3) DNS resolution
  4) No DNS resolution from my configured DNS (in my case 192.168.1.1)
  Workarounds: 
  Enable FallbackDNS=8.8.8.8 8.8.4.4 in resolved.conf
  Or running dhclient

  Fresh boot of Artful (static IP via network manager and DNS should be
  at 192.168.1.1):

  bp1@dimension:~$ ifconfig 
  enp8s0: flags=4163  mtu 1500
  inet 192.168.1.5  netmask 255.255.255.0  broadcast 192.168.1.255
  inet6 fe80::99f:fae5:1467:a576  prefixlen 64  scopeid 0x20
  ether 00:1e:4f:e9:f1:c1  txqueuelen 1000  (Ethernet)
  RX packets 141  bytes 14707 (14.7 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 234  bytes 29807 (29.8 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
  device interrupt 16  

  lo: flags=73  mtu 65536
  inet 127.0.0.1  netmask 255.0.0.0
  inet6 ::1  prefixlen 128  scopeid 0x10
  loop  txqueuelen 1000  (Local Loopback)
  RX packets 556  bytes 33758 (33.7 KB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 556  bytes 33758 (33.7 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  bp1@dimension:~$ ping www.dn.se
  ping: www.dn.se: Name or service not known
  bp1@dimension:~$ su
  Password: 
  root@dimension:/home/bp1# systemd-resolve --status
  Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

  Link 2 (enp8s0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
  root@dimension:/home/bp1# ping www.dn.se
  ping: www.dn.se: Name or service not known
  root@dimension:/home/bp1# nano /etc/systemd/resolved.conf 
  root@dimension:/home/bp1# cat /etc/systemd/resolved.conf
  #  This file is part of systemd.
  #
  #  systemd is free software; you can redistribute it and/or modify it
  #  under the terms of the GNU Lesser General Public License as published by
  #  the Free Software Foundation; either version 2.1 of the License, or
  #  (at your option) any later version.
  #
  # Entries in this file show the compile time defaults.
  # You can change settings by editing this file.
  # Defaults can be restored by simply deleting this file.
  #
  # See resolved.conf(5) for details

  [Resolve]
  #DNS=
  FallbackDNS=8.8.8.8 8.8.4.4
  #Domains=
  #LLMNR=yes
  #MulticastDNS=yes
  #DNSSEC=no
  #Cache=yes
  #DNSStubListener=udp
  root@dimension:/home/bp1# ps ax | grep systemd
254 ?Ss 0:00 /lib/systemd/systemd-journald
292 ?Ss 0:00 /lib/systemd/systemd-udevd
573 ?Ssl0:00 /lib/systemd/systemd-timesyncd
585 ?Ss 0:00 /lib/systemd/systemd-networkd
701 ?Ss 0:00 /lib/systemd/systemd-logind
735 ?Ss 0:00 /usr/bin/dbus-daemon --system --address=systemd: 
--nofork --nopidfile --systemd-activation
844 ?Ss 0:00 /lib/systemd/systemd-resolved
 

[Touch-packages] [Bug 1729194] Re: Systemd-Resolvd Forgets to Resolv Request

[Steve Langasek]

127.0.1.1 is not the address of systemd-resolved, as you noted; it's the
address used by dnsmasq.  It sounds like your network-manager config is
pointing to dnsmasq, which is no longer the default in 17.10, and should
have been dropped from your config on upgrade from 16.10 to 17.04.  Can
you please attach the /etc/NetworkManager/NetworkManager.conf from the
affected system?

** Package changed: systemd (Ubuntu) => network-manager (Ubuntu)

** Summary changed:

- Systemd-Resolvd Forgets to Resolv Request
+ /etc/resolv.conf pointing to dnsmasq instead of resolved

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

Title:
  /etc/resolv.conf pointing to dnsmasq instead of resolved

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Systemd sometimes just doesn't resolve DNS queries and for the life of
  me I don't know why.

  So often when I'm switching between wifi networks I find that systemd-
  resolved in 17.10 complete fails to do it's job. Here's the example.
  I'm connected to the internet :

  ```
  chalbersma@nebraska [~] {Tue Oct 31 20:58:18}
  > ping 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 
  64 bytes from 8.8.8.8: icmp_seq=1 ttl=53 time=196 ms 
  64 bytes from 8.8.8.8: icmp_seq=2 ttl=53 time=67.5 ms 

  64 bytes from 8.8.8.8: icmp_seq=3 ttl=53 time=78.9 ms 

  ^C
  --- 8.8.8.8 ping statistics ---  
  3 packets transmitted, 3 received, 0% packet loss, time 1999ms

  rtt min/avg/max/mdev = 67.534/114.169/196.025/58.068 ms
  ```

  But I can't seem to resolve domains:

  ```
  chalbersma@nebraska [~] {Tue Oct 31 20:59:17}
  > nslookup google.com
  ;; connection timed out; no servers could be reached

  ```

  So I did a `systemd-resolver --status` to see if it's getting the
  right dns server. It is :

  ```
  Link 3 (wlp2s0)  
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6  
 LLMNR setting: yes
  MulticastDNS setting: no 
DNSSEC setting: no 
  DNSSEC supported: no 
   DNS Servers: 192.168.43.1   
2001:4888:51:ff00:506:d::  
2001:4888:50:ff00:500:d::

  ```

  And it's actually up and working properly :

  ```
  chalbersma@nebraska [~] {Tue Oct 31 21:02:06}
  > nslookup google.com 192.168.43.1
  Server: 192.168.43.1
  Address:192.168.43.1#53

  Non-authoritative answer:
  Name:   google.com
  Address: 172.217.11.78
  chalbersma@nebraska [~] {Tue Oct 31 21:03:16}
  > nslookup google.com 2001:4888:51:ff00:506:d::
  Server: 2001:4888:51:ff00:506:d::
  Address:2001:4888:51:ff00:506:d::#53

  Non-authoritative answer:
  Name:   google.com
  Address: 172.217.11.78
  ```

  Systemd just can't figure out to make the request. I did try the
  common step of flushing the cache (with `--flush-cache`) restarting
  network-manager and systemd-resolverd service but nothing seems to be
  able to make systemd-resolverd function. Even a reboot doesn't always
  fix the issue; sometimes it persists.

  For debugging this is what's in my /etc/resolv.conf :

  ```  
  chalbersma@nebraska [~] {Tue Oct 31 21:09:15} 
  > cat /etc/resolv.conf
  # Generated by NetworkManager 
  nameserver 127.0.1.1  
  ```

  As soon as I manually set the nameserver from my loopback to the
  actual dns server (bypassing systemd-resolvd) things start working
  again. Let me know what kind of tshooting data I'd need to grab to
  help display this issue.

  In order to restore networking I had to manually edit that file and
  change my dns to the external source.

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

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

[Touch-packages] [Bug 1727869] Re: DNS resolution does not work after upgrade from 17.04 to 17.10

[Steve Langasek]

Is this problem still reproducible for you (if you de-configure
unbound)?

If so, please provide all of the following:
- the contents of /etc/resolv.conf
- the output of 'ls -l /etc/resolv.conf'
- the output of 'systemd-resolve --status'

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

Title:
  DNS resolution does not work after upgrade from 17.04 to 17.10

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Once 17.10 is installed,DNS resolution does not work after reboot.
  May be the bug is in systemd-resolved ?
  Work around by using unbound instead

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-release-upgrader-core 1:17.10.7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Thu Oct 26 23:57:46 2017
  InstallationDate: Installed on 2016-07-07 (475 days ago)
  InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to artful on 2017-10-26 (0 days ago)
  VarLogDistupgradeTermlog:

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

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

[Touch-packages] [Bug 1721092] Re: systemd-resolved and dns-masq make CPU 100% when using lxc name resolution

[Steve Langasek]

This may be related to LP: #1694156.

Can you show /etc/resolv.conf and the output of systemd-resolve --status
from the affected (host) system?

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

Title:
  systemd-resolved and dns-masq make CPU 100% when using lxc name
  resolution

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  This bug may be a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364 but I'm
  not sure, hence this new entry.

  It hits while I wanted systemd to resolve the lxc domain to my
  internal lxc hosts.

  Step to (maybe) reproduce:

  - having lxc installed
  - make some user space lxc container
  - uncomment the line LXC_DOMAIN="lxc" in /etc/default/lxc-net
  - restart lxc-net service

  Now the dnsmasq on 10.0.3.1 should be a dns resolving lxc names.

  - add a file /etc/systemd/resolved.conf.d/lxc.conf

[Resolve]
DNS=10.0.3.1
Domains=~.lxc
DNSSEC=false

  - restart systemd-resolved service

  Now systemd knows it should ask .lxc names to dnsmasq

  - start an lxc container, let assume it's called my-container
  - ping it using my-container.lxc it should work

  After some times, systemd-resolved should use 100% CPU.

  Commenting the /etc/systemd/resolved.conf.d/lxc.conf file and
  restarting it makes systemd-resolved never eating resources again.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu5
  Uname: Linux 4.10.16-041016-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct  3 18:18:56 2017
  InstallationDate: Installed on 2015-11-10 (692 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Intel Corporation Skylake Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.16-041016-generic 
root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2017-02-25 (219 days ago)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: WhiteTip Mountain1 Fab2
  dmi.board.vendor: Topstar
  dmi.board.version: RVP7
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 9
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring:
  dmi.product.name: Skylake Platform
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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

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

[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

[Alfonso Sanchez-Beato]

I have tried the packages in xenial-proposed for two modems:

Sierra HL8548
ZTE MF626

I was able to connect and everything seemed to be working as expected.

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Xenial:
  Fix Committed
Status in libqmi source package in Xenial:
  Fix Committed
Status in modemmanager source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

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

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

[Touch-packages] [Bug 1737732] Re: systemd-resolve default nameserver 127.0.0.53 disables resolution in guest systems

[Steve Langasek]

I can't reproduce this issue.  Can you explain what I'm missing?

$ grep nameserver /etc/resolv.conf 
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
$ lxc launch ubuntu-daily:bionic
Creating the container
Container name is: frank-jaguar   
Starting frank-jaguar
$ lxc exec frank-jaguar -- ping -c 1 www.google.com
PING www.google.com (74.125.199.105) 56(84) bytes of data.
64 bytes from ph-in-f105.1e100.net (74.125.199.105): icmp_seq=1 ttl=46 
time=30.3 ms

--- www.google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 30.326/30.326/30.326/0.000 ms
$

So can you elaborate where you're seeing this problem?

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

Title:
  systemd-resolve default nameserver 127.0.0.53 disables resolution in
  guest systems

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When the default nameserver, which is set by systemd-resolve, is
  127.0.0.53, guest systems (libvirtd, lxc, snaps, anbox, etc) won't
  work unless there's a non 127.0.0.x nameserver (eg. 8.8.8.8) in
  /etc/resolv.conf.  Because the dnsmasq in these guest machines try to
  resolve to 127.0.0.53 and can't find the real nameserver.

  The quick fix is of course to:

  sudo rm /etc/resolv.conf
  sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

  But that's not the default.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.2
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 12 20:01:39 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-28 (805 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 34361A0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=da81a856-84d5-4ca7-8c0a-4f20006730bc ro quiet splash nomodset vga=792 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34361A0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA3WW(2.63):bd09/24/2015:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 34361A0
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.systemd.journald.conf: 2017-09-12T19:43:29.248459

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

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

[Touch-packages] [Bug 1741986] Re: Please merge lvm2 from Debian unstable for lvmlockd and sanlock support

[Julian Andres Klode]

** Changed in: lvm2 (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Please merge lvm2 from Debian unstable for lvmlockd and sanlock
  support

Status in lvm2 package in Ubuntu:
  Fix Committed

Bug description:
  I am extremely interesting in utilizing the following stack to host
  disks for KVM virtual machines:

  * lvm2
  * lvmlockd
  * sanlock

  I believe in order to use lvmlockd, the lvm2 sources will need to be
  merged from Debian and the lvm2-lockd binary package will need to be
  built. Please could I request that this merge happen prior to the
  release of Beaver.

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

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

[Touch-packages] [Bug 1745634] [NEW] Demote idle to universe

[Jeremy Bicha]

Public bug reported:

>From what I can tell, idle is the only thing keeping tcl/tk in universe.

I think it's unnecessary as most Ubuntu developers use something other
than idle to work on Python code.

I came across this while working on LP: #1720482 (tk8.6 recommends xterm which 
is one thing that appears to keep xterm in main. I think the fix there is to 
explictly have recommends/depends on gnome-
terminal for everything that recommends/depend on xterm in main.)

idle is explicitly seeded in
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/view/head:/supported-development-desktop#L36

It was added in 2005:
https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/revision/404

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: bionic

** Also affects: python3-defaults (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-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1745634

Title:
  Demote idle to universe

Status in python3-defaults package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  From what I can tell, idle is the only thing keeping tcl/tk in
  universe.

  I think it's unnecessary as most Ubuntu developers use something other
  than idle to work on Python code.

  I came across this while working on LP: #1720482 (tk8.6 recommends xterm 
which is one thing that appears to keep xterm in main. I think the fix there is 
to explictly have recommends/depends on gnome-
  terminal for everything that recommends/depend on xterm in main.)

  idle is explicitly seeded in
  
http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/view/head:/supported-development-desktop#L36

  It was added in 2005:
  
https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/revision/404

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

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

[Touch-packages] [Bug 1740926] Re: Demote gitk to universe

[Jeremy Bicha]

gitk is in bionic universe now. I'm filing a separate bug for idle.

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Released

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

Title:
  Demote gitk to universe

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  tcl/tk is in main because of gitk.

  gitk was added to main with this commit:
  
https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/revision/628

  It is now in platform.bionic's supported-development-desktop seed.
  
https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/platform.bionic/view/head:/supported-development-desktop

  I propose we remote it from there and demote gitk to universe.

  I came across this while working on LP: #1720482 (tk8.6 recommends
  xterm which is one thing that appears to keep xterm in main).

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

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

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

[Pete]

I also have been experiencing this. Connecting to WiFi network that uses
any captive portal fails.

I dual boot with Windows, and everything is fine in Windows.

System: 
Ubuntu 17.10 (Clean install)

Behavior:
After authenticating with the portal and connecting I cannot resolve DNS.

My work around (after a lot of digging) was to edit "/etc/resolv.conf"

And add "nameserver 8.8.8.8" (Google Public DNS)

So my nameserver looked liked:

nameserver 127.0.0.53
nameserver 8.8.8.8

I had to do this after every reboot obviously.

Also very peculiar:
I have been using this work-around every day since installing 17.10 one week 
ago. However, I connected to a regular home WiFi network (non-captive portal) 
fine last night. Then after returning to my work captive-portal WiFi network 
its now connecting and resolving DNS successfully. Without having to update my 
/etc/resolv.cong. I don't understand why...

Wanted to mention while searching forums and bug reports I came across
many reported bugs that are likely duplicates of this issue. Where users
are reporting spotty or intermittent WiFi issues etc. Many think its
kernel and driver issues, while this isn't the case.

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Triaged
Status in systemd source package in Bionic:
  Triaged

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

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

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

[AsciiWolf]

I have updated the Czech translation by hand. Unfortunately, the
translation template itself seems to be outdated so I was not able to
add some translated strings.

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

Title:
  systemd translations are not synced with upstream

Status in Ubuntu Translations:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1707898/+subscriptions

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

[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

[Chris Rainey]

In case any Ubuntu/GNOME Dev's are confused about the urgency of this
and they don't work in a LAN/WAN-based environment:

1. Switching business users from MS Windows to Ubuntu Linux carries an
expectation that they can still access LAN/WAN resources from the 'file
chooser' dialogs(i.e. Chrome browser --> Gmail --> upload attachment
from an SMB/CIFS location, etc.)

2. Having consistent GUI interfaces imparts a sense of confidence to
Admins(like me) that they won't be burned-at-the-stake on a huge bonfire
by those same users _and_ management for trying to move the company onto
GNU/Linux systems !!

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Fix Released
Status in chromium-browser package in Ubuntu:
  New
Status in deja-dup package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in gdebi package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress
Status in meld package in Ubuntu:
  New
Status in remmina package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in transmission package in Ubuntu:
  New
Status in usb-creator package in Ubuntu:
  New
Status in vinagre package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://"; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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

[Touch-packages] [Bug 1731397] Re: Cant find video driver for Acer Aspire One GZ5

[Launchpad Bug Tracker]

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

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

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

Title:
  Cant find video driver for Acer Aspire One GZ5

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  What i exptected to happen:
  Install Lubuntu 17.10 and have no problems with video drivers

  What happened instead:
  Freshly installed Lubuntu 17.10 has problems with video drivers. Especifying 
nomodeset makes it usable but it's not optimal and the max resolution i'm 
getting is 800x600. 

  Whenever I install Lubuntu and try to get to the desktop, there is an
  about 80% of the screen that is black, and the remaining 20% is
  normal. I don't know if it is because of the driver, but

  sudo apt-get install xserver-xorg-video-intel
  [sudo] password for freddy: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  xserver-xorg-video-intel is already the newest version 
(2:2.99.917+git20170309-0ubuntu1).
  xserver-xorg-video-intel set to manually installed.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  This tells me that supposedly the driver is installed.

  This is the output of lscpci -v that shows the part of the video
  chipset:

  freddy@freddy-PC:~$ sudo lspci -v
  00:00.0 Host bridge: Intel Corporation Mobile 945GSE Express Memory 
Controller Hub (rev 03)
Subsystem: Acer Incorporated [ALI] Mobile 945GSE Express Memory 
Controller Hub
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=09 

  00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Mobile 945GSE Express Integrated 
Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at 5848 (32-bit, non-prefetchable) [size=512K]
I/O ports at 60c0 [size=8]
Memory at 4000 (32-bit, prefetchable) [size=256M]
Memory at 5850 (32-bit, non-prefetchable) [size=256K]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Kernel modules: i915, intelfb

  00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller (rev 03)
Subsystem: Acer Incorporated [ALI] Mobile 945GM/GMS/GME, 943/940GML 
Express Integrated Graphics Controller
Flags: bus master, fast devsel, latency 0
Memory at 5840 (32-bit, non-prefetchable) [size=512K]
Capabilities: [d0] Power Management version 2

  I just want my video to work ok. I installed the Intel microcode
  propietary driver and it doesnt seem to work either. I have to hard
  power down the pc because the reboot button that i can see in the 20%
  of the screen that is viewable doesnt work at all. I'm using the
  latest lubuntu, 17.10.

  freddy@freddy-PC:~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  
  freddy@freddy-PC:~$ apt-cache policy xorg
  xorg:
Installed: (none)
Candidate: 1:7.7+19ubuntu3
Version table:
   1:7.7+19ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu artful/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Fri Nov 10 01:16:59 2017
  InstallationDate: Installed on 2017-11-10 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1745596] Re: xorg

[Jean-Baptiste Lallement]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  xorg

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  this package is not updated

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 26 12:19:52 2018
  InstallationDate: Installed on 2017-12-28 (28 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2017-12-31 (25 days ago)

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

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

[Touch-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward

[Launchpad Bug Tracker]

This bug was fixed in the package unattended-upgrades - 0.98ubuntu4

---
unattended-upgrades (0.98ubuntu4) bionic; urgency=medium

  * Cherry pick from git:
- Fix version of test package in test_remove_unused_dependencies (Closes: 
#886803)

 -- Julian Andres Klode   Fri, 12 Jan 2018 10:10:29
+0100

** Changed in: unattended-upgrades (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  Confirmed
Status in unattended-upgrades source package in Artful:
  Confirmed
Status in update-notifier source package in Artful:
  Confirmed

Bug description:
  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:
   
  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

[Joseph Salisbury]

Commit 2a8a98673c13 has been in Xenial since Ubuntu-4.4.0-98.121.  If
you can confirm the bug is now fixed since this kernel version, I'll
mark the bug as Fix Released.

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in procps package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in linux source package in Zesty:
  In Progress
Status in procps source package in Zesty:
  New
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr
  fs.aio-max-nr = 65536

  ubuntu@zm93k8:~$  cat /proc/sys/fs/ai

[Touch-packages] [Bug 1733557] Re: Login screen showing Authentication Failed Switch to greeter...

[Luis Alberto Pabón]

I'm seeing this also upon 17.10 upgrade in unity / lightdm / unity
greeter.

It doesn't happen 100% of the time, typically takes some time time to
manifest (I only ever suspend my laptop from monday to friday), but once
it starts happening, it always happens until I shut down.

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

Title:
  Login screen showing Authentication Failed Switch to greeter...

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When I lock my machine, the login screen shows my current user with
  the message: "Authentication Failed"

  ..and in the position when the password normally exists, the option
  "Switch to greeter..."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Nov 21 10:28:47 2017
  InstallationDate: Installed on 2017-04-17 (217 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-10-23 (29 days ago)

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

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

[Touch-packages] [Bug 1725928] Re: package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files

[dino99]

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

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages
  with differing files

Status in sane-backends package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  New
Status in sane-backends package in Debian:
  New

Bug description:
  
  From #3 comment below, to get a workaround, try:

  
  sudo apt-get -o Dpkg::Options::="--force-overwrite" install --reinstall 
libsane1:i386 (or your real package name)

  ***

  apport error this morning.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Oct 22 09:37:46 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-edJWJn/5-libsane1_1.0.27-1~experimental2ubuntu1_i386.deb 
(--unpack):
    trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2016-10-08 (378 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)

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

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

[Touch-packages] [Bug 1728378] Re: NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' failed

[blueddy]

Changing the default r8169 driver for the oficial r8168 works for me.

https://blog.desdelinux.net/solucionar-problemas-con-realtek-rtl8111
-8168b-en-lmde/

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

Title:
  NetworkManager: ((src/devices/nm-device.c:1452)): assertion
  '' failed

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  This error shows up in boot logs:
  "NetworkManager: ((src/devices/nm-device.c:1452)): assertion '' 
failed".
  Ubuntu 17.10

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

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

[Touch-packages] [Bug 1745601] Re: package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 137

[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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1745601

Title:
  package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 137

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Fri Jan 26 12:39:07 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 137
  InstallationDate: Installed on 2017-12-29 (28 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 137
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1745601] [NEW] package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 137

[martin kraberg]

Public bug reported:

i don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-31-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Fri Jan 26 12:39:07 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 137
InstallationDate: Installed on 2017-12-29 (28 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: initramfs-tools
Title: package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 137
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 need-duplicate-check xenial

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

Title:
  package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 137

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Fri Jan 26 12:39:07 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 137
  InstallationDate: Installed on 2017-12-29 (28 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 137
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1745596] [NEW] xorg

[amelia]

Public bug reported:

this package is not updated

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Jan 26 12:19:52 2018
InstallationDate: Installed on 2017-12-28 (28 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
UpgradeStatus: Upgraded to artful on 2017-12-31 (25 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  this package is not updated

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 26 12:19:52 2018
  InstallationDate: Installed on 2017-12-28 (28 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2017-12-31 (25 days ago)

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

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

[Touch-packages] [Bug 1744806] Re: Bluetooth is turned off at boot with latest update (bluez 5.37-0ubuntu5.2)

[cement_head]

Kernel 4.13.0-32-generic fixes this regression

** Changed in: bluez (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Bluetooth is turned off at boot with latest update (bluez
  5.37-0ubuntu5.2)

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  With latest update, BLUEZ is now off right after boot, as opposed to
  previous behaviour that was on/off depending on last setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 22 16:08:20 2018
  InstallationDate: Installed on 2017-09-29 (115 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 04f2:b59d Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76 Lemur
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=/dev/mapper/ubuntu--vg-swap_1 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Lemur
  dmi.board.vendor: System76
  dmi.board.version: lemu7
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/17/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Lemur
  dmi.product.version: lemu7
  dmi.sys.vendor: System76
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: AC:ED:5C:F6:32:44  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:667 acl:0 sco:0 events:38 errors:0
TX bytes:405 acl:0 sco:0 commands:38 errors:0
  mtime.conffile..etc.bluetooth.input.conf: 2017-12-06T11:16:58.937870
  mtime.conffile..etc.bluetooth.main.conf: 2018-01-18T18:34:20.102879

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

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

[Touch-packages] [Bug 1744806] Re: Bluetooth is turned off at boot with latest update (bluez 5.37-0ubuntu5.2)

[cement_head]

4.13.0-32-generic now boots with Bluetooth "ON"

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

Title:
  Bluetooth is turned off at boot with latest update (bluez
  5.37-0ubuntu5.2)

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  With latest update, BLUEZ is now off right after boot, as opposed to
  previous behaviour that was on/off depending on last setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 22 16:08:20 2018
  InstallationDate: Installed on 2017-09-29 (115 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 04f2:b59d Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76 Lemur
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=/dev/mapper/ubuntu--vg-swap_1 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Lemur
  dmi.board.vendor: System76
  dmi.board.version: lemu7
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/17/2017:svnSystem76:pnLemur:pvrlemu7:rvnSystem76:rnLemur:rvrlemu7:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Lemur
  dmi.product.version: lemu7
  dmi.sys.vendor: System76
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: AC:ED:5C:F6:32:44  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:667 acl:0 sco:0 events:38 errors:0
TX bytes:405 acl:0 sco:0 commands:38 errors:0
  mtime.conffile..etc.bluetooth.input.conf: 2017-12-06T11:16:58.937870
  mtime.conffile..etc.bluetooth.main.conf: 2018-01-18T18:34:20.102879

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

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

[Touch-packages] [Bug 1745475] Re: Broken eventlet 0.20.0 with python2.7 2.7.12-1ubuntu0~16.04.3

[Dr. Jens Harbott]

** Summary changed:

- Broken eventless 0.20.0 with python2.7 2.7.12-1ubuntu0~16.04.3
+ Broken eventlet 0.20.0 with python2.7 2.7.12-1ubuntu0~16.04.3

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

Title:
  Broken eventlet 0.20.0 with python2.7 2.7.12-1ubuntu0~16.04.3

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Recently we found in Neutron bug described in 
https://bugs.launchpad.net/neutron/+bug/1745013
  It looks that there is problem with eventlet.monkey_patch() when using 
eventlet < 0.22.0 and python2.7 2.7.12-1ubuntu0~16.04.3
  Details of issue can be found in Neutron's bug report.
  It looks that breaking change can be related to fix for 
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1512068

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

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

[Touch-packages] [Bug 1745475] Re: Broken eventless 0.20.0 with python2.7 2.7.12-1ubuntu0~16.04.3

[Launchpad Bug Tracker]

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

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

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

Title:
  Broken eventlet 0.20.0 with python2.7 2.7.12-1ubuntu0~16.04.3

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Recently we found in Neutron bug described in 
https://bugs.launchpad.net/neutron/+bug/1745013
  It looks that there is problem with eventlet.monkey_patch() when using 
eventlet < 0.22.0 and python2.7 2.7.12-1ubuntu0~16.04.3
  Details of issue can be found in Neutron's bug report.
  It looks that breaking change can be related to fix for 
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1512068

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

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

[Touch-packages] [Bug 1744883] Re: package linux-image-extra-4.4.0-109-generic 4.4.0-109.132 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/1744883

Title:
  package linux-image-extra-4.4.0-109-generic 4.4.0-109.132 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:
  Always happen when I start my ubuntu kylin 16.04 LTS, 5 times or more.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-109-generic 4.4.0-109.132
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1353 F pulseaudio
frank  1860 F pulseaudio
   /dev/snd/controlC1:  gdm1353 F pulseaudio
frank  1860 F pulseaudio
  Date: Thu Jan 18 13:40:27 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=bea42c5f-f493-4ded-9704-52833b6dc9ef
  InstallationDate: Installed on 2018-01-17 (6 days ago)
  InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP 256 G3 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=fd3e0cde-fd4b-4b8b-8c73-cbef1e126db4 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.15
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-109-generic 4.4.0-109.132 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2212
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP256G3NotebookPC:pvr097810205F0610181:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 256 G3 Notebook PC
  dmi.product.version: 097810205F0610181
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1745580] [NEW] UMTS-Modem GOBI2000 not connecting in 17.04 and above

[Karl Stephan Stille]

Public bug reported:

After Upgrading from xenial to zesty and further on to artful UMTS connection 
through GOBI2000 modem stopped working.
It is an issue of modemmanager and network-manager.

First modemmanager now reports type as "gsm" and no more "wwan" so the
filter in /usr/lib/NetworkManager/conf.d/10-globally-managed-
devices.conf should be updated to

unmanaged-devices=*,except:type:wifi,except:type:wwan,except:type:gsm

Second, the gobi plugin of modemmanager was removed in end of 2015.
Versions below 1.6.12 do not work with GOBI2000 devices.

This bug has been filed here:
https://bugs.freedesktop.org/show_bug.cgi?id=104795

Tried the proposed solution to compile version 1.6.12 from source on
artfuland it works.

Please update modemmanager to version 1.6.12 in Ubuntu.

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

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

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

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

Title:
  UMTS-Modem GOBI2000 not connecting in 17.04 and above

Status in modemmanager package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  After Upgrading from xenial to zesty and further on to artful UMTS connection 
through GOBI2000 modem stopped working.
  It is an issue of modemmanager and network-manager.

  First modemmanager now reports type as "gsm" and no more "wwan" so the
  filter in /usr/lib/NetworkManager/conf.d/10-globally-managed-
  devices.conf should be updated to

  unmanaged-devices=*,except:type:wifi,except:type:wwan,except:type:gsm

  Second, the gobi plugin of modemmanager was removed in end of 2015.
  Versions below 1.6.12 do not work with GOBI2000 devices.

  This bug has been filed here:
  https://bugs.freedesktop.org/show_bug.cgi?id=104795

  Tried the proposed solution to compile version 1.6.12 from source on
  artfuland it works.

  Please update modemmanager to version 1.6.12 in Ubuntu.

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

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

[Touch-packages] [Bug 1577879] Re: File save as dialog doesn't switch to keyed in path anymore when pressing enter

[ADFH]

https://bugzilla.gnome.org/show_bug.cgi?id=766696
... but they basically put it back to Ubuntu saying packages I had from Ubuntu 
at the time weren't their bleeding edge, so it wasn't their issue.

It kiiinda sorta works now in 17.06 (I'm staying with 17.06 until they
have remote desktop sorted out with Wayland for the moment) - but it can
randomly tack on bits of filename, autocomplete style, at times... or
pressing enter sometimes will or won't work.. it may be slightly
confused by the fact in my folder heirarchy (which exists inside of a
bind mount) I have things like:

Parent/
   A/
 apple/
 aardvark/
   B/
 badger -> ../../A/apple

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

Title:
  File save as dialog doesn't switch to keyed in path anymore when
  pressing enter

Status in GTK+:
  Incomplete
Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Not sure if this is in Nautilus or a GTK package or something else..

  I run Unity as my desktop environment at the moment. With a recent
  update, the file save dialog presented to me by Firefox appears to
  have changed. I'm pretty sure it's an OS dialog and not a Firefox
  specific control, but please feel free to bounce this to whichever
  package is responsible for the File Save As dialog generated by
  Firefox 46.0 in Ubuntu now.

  In the past, when the save dialog came up, I was able to enter a path 
(absolute or relative) in the filename field:
  * If it was a directory path that existed, the directory contents would be 
shown inside the window, allowing me to then specify a name
  * If it was a directory path that didn't exist, it'd take me to the deepest 
part of the path that did match
  * If it was a directory that did exist, and a filename that didn't, it'd save 
as that filename in that folder

  The last is still true, but the others aren't anymore.. Say I have
  structure:

  home
  .../folder
  ../sub2
  ../sub3

  ... and I last saved into sub3 and I want to save into sub2, if I
  remove the filename from the name box, and I type ../sub2 and press
  enter, it doesn't navigate to the folder anymore.. The auto-complete
  function seems more reliable now, and it knows the folder exists, but
  the only way to actually show its contents now would be to click
  through the tree..

  This feels like a functionality downgrade. I should be able to type a
  pathname into the filename area of the dialog, press enter, and have
  it take me to that particular folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nautilus 1:3.14.2-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  4 03:29:09 2016
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'group', 'where', 'mime_type', 
'owner', 'permissions', 'date_accessed']"
  InstallationDate: Installed on 2016-01-21 (103 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1735362] Re: Replace ibus-sunpinyin with ibus-libpinyin

[Gunnar Hjalmarsson]

In order to not break ibus-libzhuyin and fcitx-zhuyin, I have built
libpinyin 2.1.0 in the PPA and then excluded the libzhuyin13 and
libzhuyin-dev binaries.

https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin

With a bit luck, an upload of this might also resolve the autopkgtest
issue with the pending libpinyin build.

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

** Changed in: libpinyin (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Replace ibus-sunpinyin with ibus-libpinyin

Status in Ubuntu Seeds:
  New
Status in fcitx-libpinyin package in Ubuntu:
  Fix Released
Status in ibus-libpinyin package in Ubuntu:
  In Progress
Status in ibus-sunpinyin package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New
Status in libpinyin package in Ubuntu:
  In Progress
Status in ibus-libpinyin package in Debian:
  New
Status in ibus-sunpinyin package in Debian:
  New

Bug description:
  ibus-sunpinyin: port to Python3 needed.

  Currently in the live seed, package owned by desktop-packages.
  Considering the lack of upstream maintenance, demotion might be an
  option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1735362/+subscriptions

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

[Touch-packages] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

[ChristianEhrhardt]

Hi Heinz-Werner,
thanks for the ping.

I think we agreed back then that the config itself is a Ubuntu wide
thing - but I haven't seen any discussions on procps or in general to
lift it. But then as I outlined in comment #7 any limit can be too low.
I'll set the KVM task to won't fix to clearly mark it as "not a kvm
task".

The fix that you need thou is the kernel change to account correctly - so that 
part of the question goes to the Kernel Team if the change that was proposed 
back then was actually released.
@Joseph - we clearly passed the number, but was the change released with it?


** Changed in: kvm (Ubuntu)
   Status: Confirmed => Won't Fix

** No longer affects: kvm (Ubuntu Xenial)

** No longer affects: kvm (Ubuntu Zesty)

** No longer affects: kvm (Ubuntu Artful)

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  In Progress
Status in procps package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in linux source package in Zesty:
  In Progress
Status in procps source package in Zesty:
  New
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no vir

[Touch-packages] [Bug 1635812] Re: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

[Vlad Orlov]

** Tags removed: yakkety

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

Title:
  atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: atril 1.12.2-1
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: MATE
  Date: Sat Oct 22 09:43:08 2016
  ExecutablePath: /usr/bin/atril-thumbnailer
  InstallationDate: Installed on 2016-05-14 (160 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: atril-thumbnailer -s 128 
file:///home/username/Documents/jedi_complaint.pdf 
/tmp/.mate_desktop_thumbnail.8JDPPY
  SegvAnalysis:
   Segfault happened at: 0x7fdcb0258990 : mov
0x50(%rdi),%eax
   PC (0x7fdcb0258990) ok
   source "0x50(%rdi)" (0x0050) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: atril
  StacktraceTop:
   cmsGetColorSpace () from /usr/lib/x86_64-linux-gnu/liblcms2.so.2
   GfxICCBasedColorSpace::parse(Array*, OutputDev*, GfxState*, int) () from 
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
   GfxColorSpace::parse(GfxResources*, Object*, OutputDev*, GfxState*, int) () 
from /usr/lib/x86_64-linux-gnu/libpoppler.so.58
   Page::loadThumb(unsigned char**, int*, int*, int*) () from 
/usr/lib/x86_64-linux-gnu/libpoppler.so.58
   poppler_page_get_thumbnail () from 
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
  Title: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark

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

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

[Touch-packages] [Bug 1717224] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2018-01-26 03:21 EDT---
Canonical, any updates available for this LP ?

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in procps package in Ubuntu:
  New
Status in kvm source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in kvm source package in Zesty:
  New
Status in linux source package in Zesty:
  In Progress
Status in procps source package in Zesty:
  New
Status in kvm source package in Artful:
  Confirmed
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$