date:20190227

Hi Arnold

The apparmour error message at startup of the ubuntu disk has
disappeared.

The only messages that appear in Eset's event log are these lines below:

28/02/2019 00:57:54 Media control access Unable to unlock removable media 
(org.freedesktop.udisks2.filesystem-mount)
28/02/2019 00:56:39 ESET Daemon Unable to read from socket: Connection 
reestablished by the same protocol level

The permissions appear to be released, as can be seen in the Eset event
log.

2/28/2019 00:52:13 Preload library access control Open directory not found at 
descriper 282
2/28/2019 00:52:13 Preload library access control Open directory not found at 
descriper 299
2/28/2019 00:52:13 Preload library access control Open directory not found at 
descriper 282
2/28/2019 00:52:13 Preload library access control Open directory not found at 
descriper 299
2/28/2019 00:52:13 Preload library access control Open directory not found at 
descriper 282
2/28/2019 00:52:13 Preload library access control Open directory not found at 
descriper 299
2/28/2019 00:52:13 Preload library access control Open directory not found at 
descriper 282


All of these messages already appeared before the last line changes, leaving 
only unix,

Here's the new dmesg log:

edson@edson-p6540br:~$ dmesg | grep DENIED
[   58.334359] audit: type=1400 audit(1551326278.953:59): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1109 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   58.334386] audit: type=1400 audit(1551326278.953:60): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1109 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   63.970789] audit: type=1400 audit(1551326284.595:62): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1446 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   63.971152] audit: type=1400 audit(1551326284.595:63): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1446 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   63.971156] audit: type=1400 audit(1551326284.595:64): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1446 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   64.218981] audit: type=1400 audit(1551326284.843:65): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1486 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   64.219001] audit: type=1400 audit(1551326284.843:66): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1486 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   64.219030] audit: type=1400 audit(1551326284.843:67): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1486 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   64.467981] audit: type=1400 audit(1551326285.096:68): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1526 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   64.467986] audit: type=1400 audit(1551326285.096:69): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1526 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   64.467999] audit: type=1400 audit(1551326285.096:70): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1526 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[   64.719216] audit: type=1400 audit(1551326285.348:71): apparmor="DENIED" 
operation="open" profile="/usr/lib/snapd/snap-confine" 
name="/opt/eset/esets/lib/libesets_pac.so" pid=1565 comm="snap-confine" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
edson@edson-p6540br:~$ 

Thanks

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=

[Touch-packages] [Bug 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

Hi Arnold

It looks like this:

 /tmp/esets.sock rw,
 /etc/opt/eset/  r,
 /etc/opt/eset/** r,
 /opt/eset/esets/lib/** mr,
 unix,

Ao tentar salvar apareceu a mensage abaixo:

dson@edson-p6540br:~$ sudo su
[sudo] senha para edson: 
root@edson-p6540br:/home/edson# gedit
malloc_consolidate(): invalid chunk size
Abortado (imagem do núcleo gravada)
root@edson-p6540br:/home/edson# sudo /etc/init.d/apparmor reload
[] Reloading apparmor configuration (via systemctl): 
apparmor.serviceapparmor.service is not active, cannot reload.
 failed!
root@edson-p6540br:/home/edson# /etc/init.d/apparmor reload
[] Reloading apparmor configuration (via systemctl): 
apparmor.serviceapparmor.service is not active, cannot reload.
 failed!
root@edson-p6540br:/home/edson# 

I'll restart to see how it went.

Thanks

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 18 10:56:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1003 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100
  MachineType: LENOVO 4298R86
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4298R86
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules

[Touch-packages] [Bug 1817998] Re: KVM Guest - DHCP lease lost (Ubuntu 18.04)

2019-02-27 Thread GOVINDA TATTI

** Attachment added: "01-netcfg.yaml.bridge"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817998/+attachment/5242201/+files/01-netcfg.yaml.bridge

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

Title:
  KVM Guest - DHCP lease lost (Ubuntu 18.04)

Status in systemd package in Ubuntu:
  New

Bug description:
  On Nvidia DGX2 system, we configured linux bridge (br0) using host
  physical NIC interface and it is using static IP (see below netplan
  file). BTW, we are using 18.04.2 based BaseOS and Guest images.

  - All KVM guests are being launched using virtual network interface based 
on br0. All VMs are getting DHCP based IP address and network interface works 
fine for few hours (may be upto 24hours).  
  - After that we are noticing these VMs are losing IP address and noticed 
the message in VM’s syslog
  "Feb 26 17:16:41 test-1g0 systemd-networkd[3479]: enp6s0: DHCP lease lost".
  - At this point, we tried to create new VMs using br0 and none of them 
are getting any IP address.
  - Then, we checked KVM host, and status of bridge but we didn’t see any 
error. Tried to unconfigure br0 by removing bridge configuration from host 
netplan and did “sudo netplan apply” but br0 is still there. It seems like 
bridge has in weird state and cannot unload this driver. 

  Guest
  lab@dgx-server-vm:~$ ssh nvidia@192.168.123.138
  The authenticity of host '192.168.123.138 (192.168.123.138)' can't be 
established.
  ECDSA key fingerprint is SHA256:k8XpnGH7yle76z46CX16pflYVeYcKoG6kWCymIkv0kk.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added '192.168.123.138' (ECDSA) to the list of known 
hosts.
  nvidia@192.168.123.138's password: 
   _   _   _ _ _ ______  
  | \ | |_   _(_) __| (_) __ _  | |_ ___  ___| |_ / | __ _ / _ \ 
  |  \| \ \ / / |/ _` | |/ _` | | __/ _ \/ __| __|| |/ _` | | | |
  | |\  |\ V /| | (_| | | (_| | | ||  __/\__ \ ||_| | (_| | |_| |
  |_| \_| \_/ |_|\__,_|_|\__,_|  \__\___||___/\__||_|\__, |\___/ 
 |___/   

  Welcome to Ubuntu 18.04.2 LTS (4.15.0-45-generic)

  Welcome to NVIDIA DGX KVM VM Server Version 4.0.5 (GNU/Linux
  4.15.0-45-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage
  System information as of: Wed Feb 27 12:20:21 PST 2019

  System load:  0.00IP Address: 
  Memory usage: 0.0% (59.36G avail) System uptime:  21:04 hours
  Usage on /:   8% (44G free)   Swap usage: 0.0%
  Local Users:  1   Processes:  158

  
System information as of Wed Feb 27 12:20:22 PST 2019

System load:  0.0   Processes:  155
Usage of /:   6.7% of 48.96GB   Users logged in:1
Memory usage: 0%IP address for enp1s0:  192.168.123.138
Swap usage:   0%IP address for docker0: 172.17.0.1

   * Canonical Livepatch is available for installation.
 - Reduce system reboots and improve kernel security. Activate at:
   https://ubuntu.com/livepatch

  15 packages can be updated.
  9 updates are security updates.

  Last login: Wed Feb 27 12:05:09 2019
  nvidia@test-1g0:~$ ifconfig
  docker0: flags=4099  mtu 1500
  inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
  ether 02:42:5c:b9:6f:94  txqueuelen 0  (Ethernet)
  RX packets 0  bytes 0 (0.0 B)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 0  bytes 0 (0.0 B)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enp1s0: flags=4163  mtu 1500
  inet 192.168.123.138  netmask 255.255.255.0  broadcast 192.168.123.255
  inet6 fe80::5054:ff:feb9:b8a1  prefixlen 64  scopeid 0x20
  ether 52:54:00:b9:b8:a1  txqueuelen 1000  (Ethernet)
  RX packets 38879  bytes 2449778 (2.4 MB)
  RX errors 0  dropped 1  overruns 0  frame 0
  TX packets 977  bytes 132770 (132.7 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  enp6s0: flags=4163  mtu 1500
  inet6 fe80::5055:ff:fe78:faa9  prefixlen 64  scopeid 0x20
  ether 52:55:00:78:fa:a9  txqueuelen 1000  (Ethernet)
  RX packets 93842  bytes 7637062 (7.6 MB)
  RX errors 0  dropped 27  overruns 0  frame 0
  TX packets 1874  bytes 442869 (442.8 KB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  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 562  bytes 52271 (52.2 KB)
  RX errors 0  dropped 0  overruns 0  fram

Re: [Touch-packages] [Bug 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

2019-02-27 Thread Seth Arnold

On Thu, Feb 28, 2019 at 03:04:00AM -, Edson José dos Santos wrote:
> Hello Arnold

>   unix, (connect, send, receive) peer =
(addr="@2F746D702F65736574732E736F636B00*"),

Excellent, here's the mistake. Remove everything after the comma:

  unix,

Then try the reboot again.

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 18 10:56:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1003 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100
  MachineType: LENOVO 4298R86
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4298R86
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-03-12T15:11:15.740184

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

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

[Touch-packages] [Bug 1817998] [NEW] KVM Guest - DHCP lease lost (Ubuntu 18.04)

2019-02-27 Thread GOVINDA TATTI

Public bug reported:

On Nvidia DGX2 system, we configured linux bridge (br0) using host
physical NIC interface and it is using static IP (see below netplan
file). BTW, we are using 18.04.2 based BaseOS and Guest images.

-   All KVM guests are being launched using virtual network interface based 
on br0. All VMs are getting DHCP based IP address and network interface works 
fine for few hours (may be upto 24hours).  
-   After that we are noticing these VMs are losing IP address and noticed 
the message in VM’s syslog
"Feb 26 17:16:41 test-1g0 systemd-networkd[3479]: enp6s0: DHCP lease lost".
-   At this point, we tried to create new VMs using br0 and none of them 
are getting any IP address.
-   Then, we checked KVM host, and status of bridge but we didn’t see any 
error. Tried to unconfigure br0 by removing bridge configuration from host 
netplan and did “sudo netplan apply” but br0 is still there. It seems like 
bridge has in weird state and cannot unload this driver. 

Guest
lab@dgx-server-vm:~$ ssh nvidia@192.168.123.138
The authenticity of host '192.168.123.138 (192.168.123.138)' can't be 
established.
ECDSA key fingerprint is SHA256:k8XpnGH7yle76z46CX16pflYVeYcKoG6kWCymIkv0kk.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.123.138' (ECDSA) to the list of known hosts.
nvidia@192.168.123.138's password: 
 _   _   _ _ _ ______  
| \ | |_   _(_) __| (_) __ _  | |_ ___  ___| |_ / | __ _ / _ \ 
|  \| \ \ / / |/ _` | |/ _` | | __/ _ \/ __| __|| |/ _` | | | |
| |\  |\ V /| | (_| | | (_| | | ||  __/\__ \ ||_| | (_| | |_| |
|_| \_| \_/ |_|\__,_|_|\__,_|  \__\___||___/\__||_|\__, |\___/ 
   |___/   

Welcome to Ubuntu 18.04.2 LTS (4.15.0-45-generic)

Welcome to NVIDIA DGX KVM VM Server Version 4.0.5 (GNU/Linux
4.15.0-45-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage
System information as of: Wed Feb 27 12:20:21 PST 2019

System load:0.00IP Address: 
Memory usage:   0.0% (59.36G avail) System uptime:  21:04 hours
Usage on /: 8% (44G free)   Swap usage: 0.0%
Local Users:1   Processes:  158


  System information as of Wed Feb 27 12:20:22 PST 2019

  System load:  0.0   Processes:  155
  Usage of /:   6.7% of 48.96GB   Users logged in:1
  Memory usage: 0%IP address for enp1s0:  192.168.123.138
  Swap usage:   0%IP address for docker0: 172.17.0.1

 * Canonical Livepatch is available for installation.
   - Reduce system reboots and improve kernel security. Activate at:
 https://ubuntu.com/livepatch

15 packages can be updated.
9 updates are security updates.

Last login: Wed Feb 27 12:05:09 2019
nvidia@test-1g0:~$ ifconfig
docker0: flags=4099  mtu 1500
inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
ether 02:42:5c:b9:6f:94  txqueuelen 0  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp1s0: flags=4163  mtu 1500
inet 192.168.123.138  netmask 255.255.255.0  broadcast 192.168.123.255
inet6 fe80::5054:ff:feb9:b8a1  prefixlen 64  scopeid 0x20
ether 52:54:00:b9:b8:a1  txqueuelen 1000  (Ethernet)
RX packets 38879  bytes 2449778 (2.4 MB)
RX errors 0  dropped 1  overruns 0  frame 0
TX packets 977  bytes 132770 (132.7 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp6s0: flags=4163  mtu 1500
inet6 fe80::5055:ff:fe78:faa9  prefixlen 64  scopeid 0x20
ether 52:55:00:78:fa:a9  txqueuelen 1000  (Ethernet)
RX packets 93842  bytes 7637062 (7.6 MB)
RX errors 0  dropped 27  overruns 0  frame 0
TX packets 1874  bytes 442869 (442.8 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

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 562  bytes 52271 (52.2 KB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 562  bytes 52271 (52.2 KB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

nvidia@test-1g0:~$ uptime
 12:20:35 up 21:04,  2 users,  load average: 0.00, 0.00, 0.00
nvidia@test-1g0:~$ date
Wed Feb 27 12:20:44 PST 2019
nvidia@test-1g0:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
172.17.0.0  0.0.0.0 255.255.0.0 U 0  00 docker0
192.168.123.0   0.0.0.0 255.255.255.0   U 0  00 enp1s0
nvidia@test-1g0:~$ d

[Touch-packages] [Bug 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

Hello Arnold

As requested:


  # Workaround https://launchpad.net/bugs/359338 until upstream handles stacked
  # filesystems generally. This does not appreciably decrease security with
  # Ubuntu profiles because the user is expected to have access to files owned
  # by him/her. Exceptions to this are explicit in the profiles. While this rule
  # grants access to those exceptions, the intended privacy is maintained due to
  # the encrypted contents of the files in this directory. Files in this
  # directory will also use filename encryption by default, so the files are
  # further protected. Also, with the use of 'owner', this rule properly
  # prevents access to the files from processes running under a different uid.

  # encrypted ~/.Private and old-style encrypted $HOME
  owner @{HOME}/.Private/** mrixwlk,
  # new-style encrypted $HOME
  owner @{HOMEDIRS}/.ecryptfs/*/.Private/** mrixwlk,
  /tmp/esets.sock rw,
  /etc/opt/eset/  r,
  /etc/opt/eset/** r,
  /opt/eset/esets/lib/** mr,
  unix, (connect, send, receive) peer = 
(addr="@2F746D702F65736574732E736F636B00*"),


Thank You

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 18 10:56:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1003 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100
  MachineType: LENOVO 4298R86
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi

[Touch-packages] [Bug 1765477] Re: 5s delay in AAAA dns resolving; artful and earlier is quick

2019-02-27 Thread Benjamin DeCamp

Any five second delay in name resolution is most likely caused by this
open bug in systemd-resolved:

https://github.com/systemd/systemd/issues/11849

The root cause is a delay when resolved has to downgrade the feature set
of its requests to upstream DNS servers. It correctly discovers a
compatible feature set, but doesn't implement the discovered feature set
until the next new query attempt. The retry logic is supposed to handle
this, but the bug is that it goes crazy and retries with a known not
working feature set until the max retry counter is hit. Then 5 seconds
later, a new attempt is made, and works perfectly, the compatible
feature set is used on the first attempt of the new query.



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

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

Title:
  5s delay in  dns resolving; artful and earlier is quick

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Basic steps:
  lxc launch ubuntu-daily:bionic bionic-daily
  lxc exec bionic-daily bash
  sleep 10s (because of #1765173)
  time host -d bionic-daily.lxd # or whatever domain your containers use by 
default

  In bionic, there is a 5s delay when requesting the  record:

  
  root@wondrous-grackle:~# time host -d wondrous-grackle.lxd
  Trying "wondrous-grackle.lxd"
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50934
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  A

  ;; ANSWER SECTION:
  wondrous-grackle.lxd. 0   IN  A   10.0.100.125

  Received 54 bytes from 127.0.0.53#53 in 0 ms
  Trying "wondrous-grackle.lxd"

  (5s delay here)

  
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17153
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  

  Received 38 bytes from 127.0.0.53#53 in 1 ms
  Trying "wondrous-grackle.lxd"
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12145
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  MX

  Received 38 bytes from 127.0.0.53#53 in 0 ms

  real0m5.023s

  
  In artful and xenial, there is no such delay and the (correct) empty reply is 
almost instantaneous.

  See https://pastebin.ubuntu.com/p/KP5DBcKyJr/

  
  In both cases, /etc/resolv.conf points at 127.0.0.53

  
  systemd version:
   *** 237-3ubuntu8 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

Re: [Touch-packages] [Bug 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

2019-02-27 Thread Seth Arnold

On Wed, Feb 27, 2019 at 12:59:14PM -, Edson José dos Santos wrote:
> Hi, Arnold
> 
> At startup the error message is appearing in apparmor and I would like
> to know how to generate a log to introduce them to you or just the boot
> boot log. In the absence of this I got this other log, where it points
> several flaws.

> Feb 27 09:37:29 edson-p6540br systemd-tmpfiles[482]: 
> [/usr/lib/tmpfiles.d/spice-vdagentd.conf:2] Line references path below legacy 
> directory /var/run/, updating /var/run/spice-vdagentd → /run/spice-vdagentd; 
> please update the tmpfiles.d/ drop-in file accordingly.
> Feb 27 09:37:29 edson-p6540br apparmor[376]: Erro do analisador AppArmor para 
> /etc/apparmor.d/usr.bin.man in /etc/apparmor.d/abstractions/base na linha 
> 168: syntax error, unexpected TOK_OPENPAREN, expecting TOK_ID or TOK_MODE or 
> TOK_SET_VAR
> Feb 27 09:37:29 edson-p6540br apparmor[376]: Erro do analisador AppArmor para 
> /etc/apparmor.d/sbin.dhclient in /etc/apparmor.d/abstractions/base na linha 
> 168: syntax error, unexpected TOK_OPENPAREN, expecting TOK_ID or TOK_MODE or 
> TOK_SET_VAR

Hello Edson, this means there's an error, probably in
/etc/apparmor.d/abstractions/base , and probably it is near the end.

Can you paste the last ten or twenty lines of that file?

Thanks

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 18 10:56:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1003 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100
  MachineType: LENOVO 4298R86
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.v

[Touch-packages] [Bug 1817912] Re: alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily large: 370196 bytes (2098 мс).

2019-02-27 Thread Daniel van Vugt

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

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

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

Title:
  alsa-util.c: Function snd_pcm_avail() returns a value that is
  extraordinarily large: 370196 bytes (2098 мс).

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  An old issue with ALSA is still present in Ubuntu 16.04.6.
  The system became extraordinarily slow and hangs at total in around a minute 
while playing a music (around a few hours in my case).

  [15:38:51]
  [root@ThinkPad/var/log]#grep "alsa-sink-CX20751/2 Analog" syslog
  Feb 27 14:58:50 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily 
large: 370196 bytes (2098 мс).
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver «snd_hda_intel». 
Please report this issue to the ALSA developers.
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: snd_pcm_dump():
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Soft volume PCM
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Control: PCM Playback Volume
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: min_dB: -51
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: max_dB: 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: resolution: 256
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   format   : S16_LE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   subformat: STD
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   channels : 2
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   rate : 44100
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   exact rate   : 44100 (44100/1)
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   msbits   : 16
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   buffer_size  : 16384
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_size  : 8192
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_time  : 185759
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_mode  : ENABLE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_type  : MONOTONIC
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_step  : 1
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   avail_min: 15680
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_event : 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   start_threshold  : -1
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stop_threshold   : 4611686018427387904
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_threshold: 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_size : 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   boundary : 4611686018427387904
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Slave: Hardware PCM card 1 'HDA Intel PCH' device 0 subdevice 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Ana

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

Uploaded for Bionic and Cosmic.

** Description changed:

  [Impact]
  
-  * Kernel keystroke auditing via pam_tty_audit.so not working
-  
-  * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it 
failed in pam_open_session.
-It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.
+  * Kernel keystroke auditing via pam_tty_audit.so not working
+ 
+  * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it 
failed in pam_open_session.
+    It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.
  
  [Test Case]
  
- 1. Install libpam-ldap
- 2. Add the following to the end of /etc/pam.d/common-sessions
- 
- session required pam_tty_audit.so enable=* open_only
- 
- 3. When logging in with ssh etc., pam_tty_audit will fail and login fails
+ 1) Open a shell & escalate to root
+ 2) Update /etc/pam.d/common-session & 
/etc/pam.d/common-session-noninteractive and add the following line directly 
after the line: "session required pam_unix.so":
+ "session required pam_tty_audit.so enable=*"
+ 
+ 3) Start a second new shell session on the box and type a variety of commands
+ 4) Exit the second shell session to flush the buffer?
+ 5) In the root shell run "aureport -tty -i". The output should show the 
commands run in the other shell.
  
  [Regression Potential]
  
-  * Low, we are simply including the missing header files and copy the old 
status as initialization of new.
-It's already part of Debian and Disco.
+  * Low, we are simply including the missing header files and copy the old 
status as initialization of new.
+    It's already part of Debian and Disco.
  
  [Other Info]
  
  # Upstream fix:
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee
  
  # git describe --contains c5f829931a22c65feffee16570efdae036524bee
  Linux-PAM-1_2_0~75
  
  # rmadision pam
  =>  pam | 1.1.8-1ubuntu2.2   | trusty-updates   | source
  =>  pam | 1.1.8-3.2ubuntu2   | xenial   | source
  =>  pam | 1.1.8-3.2ubuntu2.1 | xenial-updates   | source
  =>  pam | 1.1.8-3.6ubuntu2   | bionic   | source
  =>  pam | 1.1.8-3.6ubuntu2   | cosmic   | source
- pam | 1.3.1-5ubuntu1 | disco| source
+ pam | 1.3.1-5ubuntu1 | disco| source
  
  [Original Description]
  
  Dear Maintainer.
  
  I found a bug in pam_tty_audit.
  When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed 
in pam_open_session.
  It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.
  
  * Enviroments
  Ubuntu 14.04.4 LTS
  linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1
  libpam-ldap:amd64184-8.5ubuntu3
  libpam-modules:amd641.1.8-1ubuntu2.2
  
  Ubuntu 16.04.2 TLS
  linux-image-4.4.0-62-generic4.4.0-62.83
  libpam-ldap:amd64184-8.7ubuntu1
  libpam-modules:amd641.1.8-3.2ubuntu2
  
  * Reproduction method
  1. Install libpam-ldap.
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails
  
  * Solution (== 2018/04/16 Link updated ==)
  apply upstream patch
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee
  
  * Logs (on Ubuntu14.04)
  -- auth.log --
  May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 
port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8
  May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for 
user test by (uid=0)
  May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting 
current audit status: Invalid argument
  May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot 
make/remove an entry for the specified session
  May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: 
disconnected by user
  
  -- syslog --
  May 18 14:47:03 vm audispd: node=vm type=USER_ACCT 
msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): 
pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1
  May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE 
msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set 
old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0
  May 18 14:47:03 vm audispd: node=vm type=USER_START 
msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 
ms

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

Don,

I'll take care of patching Bionic and Cosmic, and I will let you handle
Xenial, if you don't mind through the Ubuntu sponsorship.

I have reviewed your Xenial debdiff, and it will need some rework. 
The patch requires to be in quilt (debian/patches-applied), and not file 
manipulate directly like you did.

- Eric

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

Title:
  pam_tty_audit failed in pam_open_session

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Xenial:
  In Progress
Status in pam source package in Bionic:
  In Progress
Status in pam source package in Cosmic:
  In Progress
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Kernel keystroke auditing via pam_tty_audit.so not working
   
   * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it 
failed in pam_open_session.
 It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  [Test Case]

  1. Install libpam-ldap
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails

  [Regression Potential]

   * Low, we are simply including the missing header files and copy the old 
status as initialization of new.
 It's already part of Debian and Disco.

  [Other Info]

  # Upstream fix:
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  # git describe --contains c5f829931a22c65feffee16570efdae036524bee
  Linux-PAM-1_2_0~75

  # rmadision pam
  =>  pam | 1.1.8-1ubuntu2.2   | trusty-updates   | source
  =>  pam | 1.1.8-3.2ubuntu2   | xenial   | source
  =>  pam | 1.1.8-3.2ubuntu2.1 | xenial-updates   | source
  =>  pam | 1.1.8-3.6ubuntu2   | bionic   | source
  =>  pam | 1.1.8-3.6ubuntu2   | cosmic   | source
  pam | 1.3.1-5ubuntu1 | disco| source

  [Original Description]

  Dear Maintainer.

  I found a bug in pam_tty_audit.
  When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed 
in pam_open_session.
  It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  * Enviroments
  Ubuntu 14.04.4 LTS
  linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1
  libpam-ldap:amd64184-8.5ubuntu3
  libpam-modules:amd641.1.8-1ubuntu2.2

  Ubuntu 16.04.2 TLS
  linux-image-4.4.0-62-generic4.4.0-62.83
  libpam-ldap:amd64184-8.7ubuntu1
  libpam-modules:amd641.1.8-3.2ubuntu2

  * Reproduction method
  1. Install libpam-ldap.
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails

  * Solution (== 2018/04/16 Link updated ==)
  apply upstream patch
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  * Logs (on Ubuntu14.04)
  -- auth.log --
  May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 
port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8
  May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for 
user test by (uid=0)
  May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting 
current audit status: Invalid argument
  May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot 
make/remove an entry for the specified session
  May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: 
disconnected by user

  -- syslog --
  May 18 14:47:03 vm audispd: node=vm type=USER_ACCT 
msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): 
pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1
  May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE 
msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set 
old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0
  May 18 14:47:03 vm audispd: node=vm type=USER_START 
msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=failed'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 
msg='op=PA

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

** Changed in: pam (Ubuntu Bionic)
 Assignee: Don van der Haghen (donvdh) => Eric Desrochers (slashd)

** Changed in: pam (Ubuntu Bionic)
   Importance: High => Medium

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

Title:
  pam_tty_audit failed in pam_open_session

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Xenial:
  In Progress
Status in pam source package in Bionic:
  In Progress
Status in pam source package in Cosmic:
  In Progress
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Kernel keystroke auditing via pam_tty_audit.so not working
   
   * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it 
failed in pam_open_session.
 It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  [Test Case]

  1. Install libpam-ldap
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails

  [Regression Potential]

   * Low, we are simply including the missing header files and copy the old 
status as initialization of new.
 It's already part of Debian and Disco.

  [Other Info]

  # Upstream fix:
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  # git describe --contains c5f829931a22c65feffee16570efdae036524bee
  Linux-PAM-1_2_0~75

  # rmadision pam
  =>  pam | 1.1.8-1ubuntu2.2   | trusty-updates   | source
  =>  pam | 1.1.8-3.2ubuntu2   | xenial   | source
  =>  pam | 1.1.8-3.2ubuntu2.1 | xenial-updates   | source
  =>  pam | 1.1.8-3.6ubuntu2   | bionic   | source
  =>  pam | 1.1.8-3.6ubuntu2   | cosmic   | source
  pam | 1.3.1-5ubuntu1 | disco| source

  [Original Description]

  Dear Maintainer.

  I found a bug in pam_tty_audit.
  When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed 
in pam_open_session.
  It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  * Enviroments
  Ubuntu 14.04.4 LTS
  linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1
  libpam-ldap:amd64184-8.5ubuntu3
  libpam-modules:amd641.1.8-1ubuntu2.2

  Ubuntu 16.04.2 TLS
  linux-image-4.4.0-62-generic4.4.0-62.83
  libpam-ldap:amd64184-8.7ubuntu1
  libpam-modules:amd641.1.8-3.2ubuntu2

  * Reproduction method
  1. Install libpam-ldap.
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails

  * Solution (== 2018/04/16 Link updated ==)
  apply upstream patch
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  * Logs (on Ubuntu14.04)
  -- auth.log --
  May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 
port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8
  May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for 
user test by (uid=0)
  May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting 
current audit status: Invalid argument
  May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot 
make/remove an entry for the specified session
  May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: 
disconnected by user

  -- syslog --
  May 18 14:47:03 vm audispd: node=vm type=USER_ACCT 
msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): 
pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1
  May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE 
msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set 
old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0
  May 18 14:47:03 vm audispd: node=vm type=USER_START 
msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=failed'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CR

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

I have provided a test package to an impacted user for Bionic/18.04LTS.

Here's what has been brought to my attention after this user tried the test 
package:
"Test results look good. Keystroke logging audit messages are coming through."

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

Title:
  pam_tty_audit failed in pam_open_session

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Xenial:
  In Progress
Status in pam source package in Bionic:
  In Progress
Status in pam source package in Cosmic:
  In Progress
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Kernel keystroke auditing via pam_tty_audit.so not working
   
   * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it 
failed in pam_open_session.
 It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  [Test Case]

  1. Install libpam-ldap
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails

  [Regression Potential]

   * Low, we are simply including the missing header files and copy the old 
status as initialization of new.
 It's already part of Debian and Disco.

  [Other Info]

  # Upstream fix:
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  # git describe --contains c5f829931a22c65feffee16570efdae036524bee
  Linux-PAM-1_2_0~75

  # rmadision pam
  =>  pam | 1.1.8-1ubuntu2.2   | trusty-updates   | source
  =>  pam | 1.1.8-3.2ubuntu2   | xenial   | source
  =>  pam | 1.1.8-3.2ubuntu2.1 | xenial-updates   | source
  =>  pam | 1.1.8-3.6ubuntu2   | bionic   | source
  =>  pam | 1.1.8-3.6ubuntu2   | cosmic   | source
  pam | 1.3.1-5ubuntu1 | disco| source

  [Original Description]

  Dear Maintainer.

  I found a bug in pam_tty_audit.
  When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed 
in pam_open_session.
  It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  * Enviroments
  Ubuntu 14.04.4 LTS
  linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1
  libpam-ldap:amd64184-8.5ubuntu3
  libpam-modules:amd641.1.8-1ubuntu2.2

  Ubuntu 16.04.2 TLS
  linux-image-4.4.0-62-generic4.4.0-62.83
  libpam-ldap:amd64184-8.7ubuntu1
  libpam-modules:amd641.1.8-3.2ubuntu2

  * Reproduction method
  1. Install libpam-ldap.
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails

  * Solution (== 2018/04/16 Link updated ==)
  apply upstream patch
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  * Logs (on Ubuntu14.04)
  -- auth.log --
  May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 
port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8
  May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for 
user test by (uid=0)
  May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting 
current audit status: Invalid argument
  May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot 
make/remove an entry for the specified session
  May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: 
disconnected by user

  -- syslog --
  May 18 14:47:03 vm audispd: node=vm type=USER_ACCT 
msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): 
pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1
  May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE 
msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set 
old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0
  May 18 14:47:03 vm audispd: node=vm type=USER_START 
msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=failed'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 termi

[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

2019-02-27 Thread Sergio Callegari

Dimitri, if you can have a package for cosmic with the fix built in a
PPA, I would be glad to try it.

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

Title:
  qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  In Progress
Status in qtbase-opensource-src source package in Cosmic:
  Incomplete

Bug description:
  [Impact]
  All kde applications shipped with ubuntu and particularly kubuntu bionic 
print via the qt print dialog, that, unfortunately, does not seem to respect 
the defaults set for the printer.

  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.

  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a
  total of 3 times the paper usage if the print dialog respected the
  default.

  [Test Case]
  1) Install a printer that can duplex and configure it to do duplex with 
long-edge binding from the printer setup dialog.

  2) Open a PDF with okular, and open the print dialog. Select the
  printer above.

  3) Press the "Options" button to enlarge the dialog to also present
  the options. Select the "options" tab, right of "copies". Verify that
  Duplex Printing is preset to "None"

  This is wrong, because the printer was configured to do duplex with
  long-edge binding.

  4) Print and close okular.

  5) Reopen okular (with the same or another PDF file). Open again the
  print dialog and select the same printer.

  6) Redo 3). Again see that Duplex Printing is preset to "None",
  instead of being at the default or at the previously used setup.

  [Regression Potential]
  The proposed patch only changes the default settings. The regression 
potential may be that the values are wrong, although they are already wrong.

  In case there is some bug it may lead to crashes. But this code is in
  the latest stable Qt release and I am not aware of any such crashes
  reported.

  [Other Info]
  The proposed patch is a backport of the following upstream commits:
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e

  [Original Description]
  See also https://bugs.kde.org/show_bug.cgi?id=395150

  As a final comment and in general, I think that Bionic should be
  updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
  possible (at least via a kubuntu ppa). The QT 5 print dialog has
  always been extremely poor, with no possibility to provide information
  about things like print quality and resolution, paper type, stapling
  (for printers supporting it), etc. Now, QT 5.11 has finally a better
  print dialog and it would be great if the bionic users could use it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions

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

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

@xnox adding you to this bug fyi.

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  [impact]

  systems upgraded from pre-Bionic releases to Bionic or later will
  continue to use ifupdown/resolvconf for network conf and management,
  but resolvconf has a new systemd service in Bionic and later that
  pulls systemd-resolved stub-resolv.conf into its local configuration.
  With the recent addition of edns0 option to the stub resolver conf in
  systemd to fix bug 1811471, this means resolvconf now sets up the
  /etc/resolv.conf file to include upstream servers but also use edns.
  For any systems where the upstream resolver(s) don't support edns, dns
  lookups will break.

  [test case]

  create a xenial system with ifupdown/resolvconf, then upgrade to
  bionic (alternately it should be possible to install bionic, then
  remove netplan and install/configure ifupdown and resolvconf).  The
  system ifupdown config should include an upstream name server.

  After upgrade, the /etc/resolv.conf will contain both the upstream
  name server as well as options edns0.

  [regression potential]

  this changes how resolvconf handles system dns on bionic and later:

  1) networking is managed by ifupdown

  resolvconf is currently adding the local stub resolver to
  /etc/resolv.conf, even though in this case it doesn't know about any
  upstream name servers.  This change will remove the local stub
  resolver from /etc/resolv.conf; it should not be there.

  2) networking is managed by systemd-networkd

  resolvconf is currently setting up /etc/resolv.conf to direct all
  local dns queries to the local stub resolver, similar to how systemd-
  resolved itself configures /etc/resolv.conf.  This change will instead
  set up /etc/resolv.conf to bypass the local stub resolver, and send
  all dns queries to the upstream name server(s).

  In case #1, this change has little chance for regression; in case #2
  however, this change will bypass the local stub resolver and thus
  create more network dns traffic (since dns queries will not be cached
  locally).  However, this is how pre-Bionic releases worked, and simply
  removing resolvconf will restore systemd-resolved control of
  /etc/resolv.conf, causing the system to again use the local stub
  resolver.

  Additional regressions due to this change would likely be seen in dns
  query failures with other system configurations.

  [other info]

  This affects only Bionic and later; in Xenial and earlier, resolvconf
  does not include the 'resolvconf-pull-resolved' service to pull in the
  systemd-resolved stub config, which is what causes this problem.

  This also does not affect Debian, as it does not include the
  'resolvconf-pull-resolved' service either.

  original description:

  --

  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
    Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

@brian-murray since you commented in comment 3 and thus are familiar
with this bug, and I don't have disco upload rights, please give my MP a
look and merge into disco if you have a chance.  I'll SRU to B/C once
it's in D.  Thanks.

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  [impact]

  systems upgraded from pre-Bionic releases to Bionic or later will
  continue to use ifupdown/resolvconf for network conf and management,
  but resolvconf has a new systemd service in Bionic and later that
  pulls systemd-resolved stub-resolv.conf into its local configuration.
  With the recent addition of edns0 option to the stub resolver conf in
  systemd to fix bug 1811471, this means resolvconf now sets up the
  /etc/resolv.conf file to include upstream servers but also use edns.
  For any systems where the upstream resolver(s) don't support edns, dns
  lookups will break.

  [test case]

  create a xenial system with ifupdown/resolvconf, then upgrade to
  bionic (alternately it should be possible to install bionic, then
  remove netplan and install/configure ifupdown and resolvconf).  The
  system ifupdown config should include an upstream name server.

  After upgrade, the /etc/resolv.conf will contain both the upstream
  name server as well as options edns0.

  [regression potential]

  this changes how resolvconf handles system dns on bionic and later:

  1) networking is managed by ifupdown

  resolvconf is currently adding the local stub resolver to
  /etc/resolv.conf, even though in this case it doesn't know about any
  upstream name servers.  This change will remove the local stub
  resolver from /etc/resolv.conf; it should not be there.

  2) networking is managed by systemd-networkd

  resolvconf is currently setting up /etc/resolv.conf to direct all
  local dns queries to the local stub resolver, similar to how systemd-
  resolved itself configures /etc/resolv.conf.  This change will instead
  set up /etc/resolv.conf to bypass the local stub resolver, and send
  all dns queries to the upstream name server(s).

  In case #1, this change has little chance for regression; in case #2
  however, this change will bypass the local stub resolver and thus
  create more network dns traffic (since dns queries will not be cached
  locally).  However, this is how pre-Bionic releases worked, and simply
  removing resolvconf will restore systemd-resolved control of
  /etc/resolv.conf, causing the system to again use the local stub
  resolver.

  Additional regressions due to this change would likely be seen in dns
  query failures with other system configurations.

  [other info]

  This affects only Bionic and later; in Xenial and earlier, resolvconf
  does not include the 'resolvconf-pull-resolved' service to pull in the
  systemd-resolved stub config, which is what causes this problem.

  This also does not affect Debian, as it does not include the
  'resolvconf-pull-resolved' service either.

  original description:

  --

  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
    Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

@drgrumpy can you test the resolvconf package from this ppa to see if it
correctly fixes the problem for you (on a system where you haven't
worked around this by disabling the 'resolvconf-pull-resolved'
service/path, of course):

https://launchpad.net/~ddstreet/+archive/ubuntu/lp1817903

** Description changed:

  [impact]
  
  systems upgraded from pre-Bionic releases to Bionic or later will
  continue to use ifupdown/resolvconf for network conf and management, but
  resolvconf has a new systemd service in Bionic and later that pulls
  systemd-resolved stub-resolv.conf into its local configuration.  With
  the recent addition of edns0 option to the stub resolver conf in systemd
  to fix bug 1811471, this means resolvconf now sets up the
  /etc/resolv.conf file to include upstream servers but also use edns.
  For any systems where the upstream resolver(s) don't support edns, dns
  lookups will break.
  
  [test case]
  
  create a xenial system with ifupdown/resolvconf, then upgrade to bionic
  (alternately it should be possible to install bionic, then remove
  netplan and install/configure ifupdown and resolvconf).  The system
  ifupdown config should include an upstream name server.
  
  After upgrade, the /etc/resolv.conf will contain both the upstream name
  server as well as options edns0.
  
  [regression potential]
  
  this changes how resolvconf handles system dns on bionic and later:
  
  1) networking is managed by ifupdown
  
  resolvconf is currently adding the local stub resolver to
  /etc/resolv.conf, even though in this case it doesn't know about any
  upstream name servers.  This change will remove the local stub resolver
  from /etc/resolv.conf; it should not be there.
  
  2) networking is managed by systemd-networkd
  
  resolvconf is currently setting up /etc/resolv.conf to direct all local
  dns queries to the local stub resolver, similar to how systemd-resolved
  itself configures /etc/resolv.conf.  This change will instead set up
  /etc/resolv.conf to bypass the local stub resolver, and send all dns
  queries to the upstream name server(s).
  
  In case #1, this change has little chance for regression; in case #2
  however, this change will bypass the local stub resolver and thus create
  more network dns traffic (since dns queries will not be cached locally).
  However, this is how pre-Bionic releases worked, and simply removing
  resolvconf will restore systemd-resolved control of /etc/resolv.conf,
  causing the system to again use the local stub resolver.
  
  Additional regressions due to this change would likely be seen in dns
  query failures with other system configurations.
  
  [other info]
  
+ This affects only Bionic and later; in Xenial and earlier, resolvconf
+ does not include the 'resolvconf-pull-resolved' service to pull in the
+ systemd-resolved stub config, which is what causes this problem.
+ 
+ This also does not affect Debian, as it does not include the
+ 'resolvconf-pull-resolved' service either.
+ 
  original description:
  
  --
- 
  
  Mint 19 (Ubuntu 18.04)
  
  Following latest mint update done on 24/02/2019, DNS is broken
  
  nslookup and dig of certain domain names work as expected, ping does not
  (ip works but not domain name)
  
  After a day of trial and error, testing I found that the problem lies
  with the presence of
  
  "options edns0"
  
  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)
  
  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager
  
  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)
  
  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?
  
  systemd:
    Installed: 237-3ubuntu10.13

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  [impact]

  systems upgraded from pre-Bionic releases to Bionic or later will
  continue to use ifupdown/resolvconf for network conf and management,
  but resolvconf has a new systemd service in Bionic and later that
  pulls systemd-resolved stub-resolv.conf into its local configuration.
  With the recent addition of edns0 option to the stub resolver conf in
  systemd to fix bug 1811471, this means resolvconf now sets up the
  /etc/resolv.conf fi

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Disco)
   Importance: Critical
 Assignee: Dan Streetman (ddstreet)
   Status: In Progress

** Also affects: systemd (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

** Changed in: systemd (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Cosmic)
   Status: New => In Progress

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

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

** Changed in: systemd (Ubuntu Cosmic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  [impact]

  systems upgraded from pre-Bionic releases to Bionic or later will
  continue to use ifupdown/resolvconf for network conf and management,
  but resolvconf has a new systemd service in Bionic and later that
  pulls systemd-resolved stub-resolv.conf into its local configuration.
  With the recent addition of edns0 option to the stub resolver conf in
  systemd to fix bug 1811471, this means resolvconf now sets up the
  /etc/resolv.conf file to include upstream servers but also use edns.
  For any systems where the upstream resolver(s) don't support edns, dns
  lookups will break.

  [test case]

  create a xenial system with ifupdown/resolvconf, then upgrade to
  bionic (alternately it should be possible to install bionic, then
  remove netplan and install/configure ifupdown and resolvconf).  The
  system ifupdown config should include an upstream name server.

  After upgrade, the /etc/resolv.conf will contain both the upstream
  name server as well as options edns0.

  [regression potential]

  this changes how resolvconf handles system dns on bionic and later:

  1) networking is managed by ifupdown

  resolvconf is currently adding the local stub resolver to
  /etc/resolv.conf, even though in this case it doesn't know about any
  upstream name servers.  This change will remove the local stub
  resolver from /etc/resolv.conf; it should not be there.

  2) networking is managed by systemd-networkd

  resolvconf is currently setting up /etc/resolv.conf to direct all
  local dns queries to the local stub resolver, similar to how systemd-
  resolved itself configures /etc/resolv.conf.  This change will instead
  set up /etc/resolv.conf to bypass the local stub resolver, and send
  all dns queries to the upstream name server(s).

  In case #1, this change has little chance for regression; in case #2
  however, this change will bypass the local stub resolver and thus
  create more network dns traffic (since dns queries will not be cached
  locally).  However, this is how pre-Bionic releases worked, and simply
  removing resolvconf will restore systemd-resolved control of
  /etc/resolv.conf, causing the system to again use the local stub
  resolver.

  Additional regressions due to this change would likely be seen in dns
  query failures with other system configurations.

  [other info]

  This affects only Bionic and later; in Xenial and earlier, resolvconf
  does not include the 'resolvconf-pull-resolved' service to pull in the
  systemd-resolved stub config, which is what causes this problem.

  This also does not affect Debian, as it does not include the
  'resolvconf-pull-resolved' service either.

  original description:

  --

  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

** Description changed:

+ [impact]
+ 
+ systems upgraded from pre-Bionic releases to Bionic or later will
+ continue to use ifupdown/resolvconf for network conf and management, but
+ resolvconf has a new systemd service in Bionic and later that pulls
+ systemd-resolved stub-resolv.conf into its local configuration.  With
+ the recent addition of edns0 option to the stub resolver conf in systemd
+ to fix bug 1811471, this means resolvconf now sets up the
+ /etc/resolv.conf file to include upstream servers but also use edns.
+ For any systems where the upstream resolver(s) don't support edns, dns
+ lookups will break.
+ 
+ [test case]
+ 
+ create a xenial system with ifupdown/resolvconf, then upgrade to bionic
+ (alternately it should be possible to install bionic, then remove
+ netplan and install/configure ifupdown and resolvconf).  The system
+ ifupdown config should include an upstream name server.
+ 
+ After upgrade, the /etc/resolv.conf will contain both the upstream name
+ server as well as options edns0.
+ 
+ [regression potential]
+ 
+ this changes how resolvconf handles system dns on bionic and later:
+ 
+ 1) networking is managed by ifupdown
+ 
+ resolvconf is currently adding the local stub resolver to
+ /etc/resolv.conf, even though in this case it doesn't know about any
+ upstream name servers.  This change will remove the local stub resolver
+ from /etc/resolv.conf; it should not be there.
+ 
+ 2) networking is managed by systemd-networkd
+ 
+ resolvconf is currently setting up /etc/resolv.conf to direct all local
+ dns queries to the local stub resolver, similar to how systemd-resolved
+ itself configures /etc/resolv.conf.  This change will instead set up
+ /etc/resolv.conf to bypass the local stub resolver, and send all dns
+ queries to the upstream name server(s).
+ 
+ In case #1, this change has little chance for regression; in case #2
+ however, this change will bypass the local stub resolver and thus create
+ more network dns traffic (since dns queries will not be cached locally).
+ However, this is how pre-Bionic releases worked, and simply removing
+ resolvconf will restore systemd-resolved control of /etc/resolv.conf,
+ causing the system to again use the local stub resolver.
+ 
+ Additional regressions due to this change would likely be seen in dns
+ query failures with other system configurations.
+ 
+ [other info]
+ 
+ original description:
+ 
+ --
+ 
+ 
  Mint 19 (Ubuntu 18.04)
  
  Following latest mint update done on 24/02/2019, DNS is broken
  
  nslookup and dig of certain domain names work as expected, ping does not
  (ip works but not domain name)
  
  After a day of trial and error, testing I found that the problem lies
  with the presence of
  
  "options edns0"
  
  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)
  
  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager
  
  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)
  
  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?
  
  systemd:
-   Installed: 237-3ubuntu10.13
+   Installed: 237-3ubuntu10.13

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Trusty:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  In Progress

Bug description:
  [impact]

  systems upgraded from pre-Bionic releases to Bionic or later will
  continue to use ifupdown/resolvconf for network conf and management,
  but resolvconf has a new systemd service in Bionic and later that
  pulls systemd-resolved stub-resolv.conf into its local configuration.
  With the recent addition of edns0 option to the stub resolver conf in
  systemd to fix bug 1811471, this means resolvconf now sets up the
  /etc/resolv.conf file to include upstream servers but also use edns.
  For any systems where the upstream resolver(s) don't support edns, dns
  lookups will break.

  [test case]

  create a xenial system with ifupdown/resolvconf, then upgrade to
  bionic (alternately it should be possible to install bionic, then
  remove netplan and install/configure ifupdown and resolvconf).  The
  system ifupdown config should include an upstream name server.

  After upgrade, the /etc/resolv.conf will contain both the upstream
  name server as well as options edns0.

  [regression potential]

  this changes

[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

** Changed in: qtbase-opensource-src (Ubuntu Cosmic)
Status: New => Incomplete

** Changed in: qtbase-opensource-src (Ubuntu Bionic)
Status: New => In Progress

** Changed in: qtbase-opensource-src (Ubuntu Bionic)
Importance: Undecided => Medium

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

Title:
qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
Fix Released
Status in qtbase-opensource-src source package in Bionic:
In Progress
Status in qtbase-opensource-src source package in Cosmic:
Incomplete

Bug description:
[Impact]
All kde applications shipped with ubuntu and particularly kubuntu bionic
print via the qt print dialog, that, unfortunately, does not seem to respect
the defaults set for the printer.

Specifically, every time one starts to print the "duplex" option gets
reset to "none" even for those printers that were configured for "long
edge" duplex by default.

This may lead to a huge *waste of paper*: people print, expecting the
duplex, do not get it, throw away the printout and reprint, for a
total of 3 times the paper usage if the print dialog respected the
default.

[Test Case]
1) Install a printer that can duplex and configure it to do duplex with
long-edge binding from the printer setup dialog.

2) Open a PDF with okular, and open the print dialog. Select the
printer above.

3) Press the "Options" button to enlarge the dialog to also present
the options. Select the "options" tab, right of "copies". Verify that
Duplex Printing is preset to "None"

This is wrong, because the printer was configured to do duplex with
long-edge binding.

4) Print and close okular.

5) Reopen okular (with the same or another PDF file). Open again the
print dialog and select the same printer.

6) Redo 3). Again see that Duplex Printing is preset to "None",
instead of being at the default or at the previously used setup.

[Regression Potential]
The proposed patch only changes the default settings. The regression
potential may be that the values are wrong, although they are already wrong.

In case there is some bug it may lead to crashes. But this code is in
the latest stable Qt release and I am not aware of any such crashes
reported.

[Other Info]
The proposed patch is a backport of the following upstream commits:
- https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3
- https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e

[Original Description]
See also https://bugs.kde.org/show_bug.cgi?id=395150

As a final comment and in general, I think that Bionic should be
updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
possible (at least via a kubuntu ppa). The QT 5 print dialog has
always been extremely poor, with no possibility to provide information
about things like print quality and resolution, paper type, stapling
(for printers supporting it), etc. Now, QT 5.11 has finally a better
print dialog and it would be great if the bionic users could use it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+subscriptions

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

[Touch-packages] [Bug 1790816] Re: Terrible sound after update to 18.04

It's a shot in the dark, but in my case, pulse sound server (atop of
alsa) seems to have gotten into a mess with an upgrade between 16.04 and
18.04. Post login, removing old / session start user config fixed my
dodgy channel mappings (but not quite the same as crackling, etc):

pulseaudio --kill \
&& rm -r ~/.config/pulse/* \
&& pulseaudio --start

However, every new boot, the same missing channel mappings cause my
audio to sound bad (not mapped correctly to 5.1 channels).

Also, try alsa-info which is a script that bundles all the alsa
inspection commands and then maybe try fish for the problem in that.
Also try figure out how to play a sound file directly to alsa vs via the
pulse sound server to rule out pulse causing the problem.

I think the speaker-test command also directly tests the alsa layer
where as the gnome-control-centre (settings) sound page "Test Speakers"
tests the setup via pulse.

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

Title:
Terrible sound after update to 18.04

Status in alsa-driver package in Ubuntu:
New

Bug description:
The sound just is extremely distorted after update to 18.04. Like an
old radio that's not picking up the station right. I saw a webpage
about the same device I am using and tried their solution. That didn't
help at all. Hope I didn't make things worse.

I saw a page that mentioned the lspci command. Based on that, I guess
I am using an Intel 82801 JD/DO audio card. One site said that
requires an snd_hda_intel driver, but all I could find in Synaptic
Package Manager was that an alsa driver and pulse audio were
installed. Could the correct driver have been removed with the new
installation?

This computer has been kind of buggy as of late, but the audio had
been working. I had problems installing this OS. Mostly it seems to be
working otherwise though.

1) Description: Ubuntu 18.04.1 LTS
Release: 18.04

2) N: Unable to locate package pkgname

3) What you expected to happen: sound to work properly

4) What happened instead: sound distorted

Hope my attempt to fix it doesn't screw up the bug report.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: szettner 2030 F pulseaudio
CurrentDesktop: GNOME-Flashback:GNOME
Date: Wed Sep 5 03:07:08 2018
InstallationDate: Installed on 2017-06-28 (433 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: High background noise, or volume is too low
Title: [OptiPlex 760, Analog Devices AD1984A, Green Headphone Out, Front]
Background noise or low volume
UpgradeStatus: Upgraded to bionic on 2018-09-02 (2 days ago)
dmi.bios.date: 12/03/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0D517D
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA01:bd12/03/2008:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0D517D:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 760
dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

> But in the long term I guess I should move to systemd-networkd as the
> preferred way to set static ip?

that is entirely up to your preferences; ifupdown and resolvconf are
still supported, and included, and you can continue to use them.  They
are still the default way to configure the network in Debian, as far as
I know.  However, Ubuntu starting at Bionic has switched to default to
using either systemd-networkd (and system-resolved), or NetworkManager,
or both; with configuration of both/either done by netplan.  However, as
you have seen, anyone who upgrades to Bionic or later from a pre-Bionic
release will continue to use ifupdown/resolvconf.

If you're asking for what the recommended way is, then I would recommend
switching to using systemd for network management, and using netplan for
network configuration (or if you prefer, just creating systemd-networkd
conf files directly).

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1817967] [NEW] 16.04.6 LTS OpenSSH-Server requires 0705 directory privileges for pubkey auth

2019-02-27 Thread Nathan

Public bug reported:

Many servers are set up to simplify and centralize ssh key management
within a single directory.

This is typically done with the line "AuthorizedKeysFile /somedir/%u".
Much online discussion suggests placing the destination in
/etc/ssh/authorized_keys/%u with 0700 on the authorized_keys folder and
0600 or 0644 on the separate public key-files, StrictTypes is enabled
and is supposed to check for the 0700 and 0600 permissions... but
doesn't appear to be working?.

The current supported version for SSH on 16.04.6 LTS appears to be:
OpenSSH_7.2p2 Ubuntu-4ubuntu2.7, OpenSSL 1.0.2g  1 Mar 2016


Under this configuration, standard key-based authentication is unable to 
complete without the key directory having at least 0705 on the directory, 0700 
fails, and 0644 on the files is sufficient regardless.

This was tested on a 16.04.6 LTS release instance created on Linode.

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

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

Title:
  16.04.6 LTS OpenSSH-Server requires 0705 directory privileges for
  pubkey auth

Status in openssh package in Ubuntu:
  New

Bug description:
  Many servers are set up to simplify and centralize ssh key management
  within a single directory.

  This is typically done with the line "AuthorizedKeysFile /somedir/%u".
  Much online discussion suggests placing the destination in
  /etc/ssh/authorized_keys/%u with 0700 on the authorized_keys folder
  and 0600 or 0644 on the separate public key-files, StrictTypes is
  enabled and is supposed to check for the 0700 and 0600 permissions...
  but doesn't appear to be working?.

  The current supported version for SSH on 16.04.6 LTS appears to be:
  OpenSSH_7.2p2 Ubuntu-4ubuntu2.7, OpenSSL 1.0.2g  1 Mar 2016

  
  Under this configuration, standard key-based authentication is unable to 
complete without the key directory having at least 0705 on the directory, 0700 
fails, and 0644 on the files is sufficient regardless.

  This was tested on a 16.04.6 LTS release instance created on Linode.

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

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

[Touch-packages] [Bug 1791417] Re: Sound bug ubuntu 18.04

Wish there was a "needs more info" tag or a way to tag bug reports like
this. There's no context as to exactly what the problem is despite the
alsa-info script output being supplied.

It's unfair to maintainers to expect them to fish out the problem.
"Sound bug ubuntu 18.04" is way too generic.

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

Title:
  Sound bug ubuntu 18.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod
  +x ./alsa-info.sh && ./alsa-info.sh

  --2018-09-07 12:24:00--  http://www.alsa-project.org/alsa-info.sh
  Resolving www.alsa-project.org (www.alsa-project.org)... 77.48.224.243
  Connecting to www.alsa-project.org 
(www.alsa-project.org)|77.48.224.243|:80... connected.
  HTTP request sent, awaiting response... 302 Found
  Location: 
http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh
 [following]
  --2018-09-07 12:24:00--  
http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh
  Resolving git.alsa-project.org (git.alsa-project.org)... 77.48.224.243
  Connecting to git.alsa-project.org 
(git.alsa-project.org)|77.48.224.243|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: unspecified [application/x-sh]
  Saving to: ‘alsa-info.sh’

  alsa-info.sh[ <=>
  ]  28.03K   170KB/sin 0.2s

  2018-09-07 12:24:01 (170 KB/s) - ‘alsa-info.sh’ saved [28707]

  ALSA Information Script v 0.4.64
  

  This script visits the following commands/files to collect diagnostic
  information about your ALSA installation and sound related hardware.

dmesg
lspci
lsmod
aplay
amixer
alsactl
/proc/asound/
/sys/class/sound/
~/.asoundrc (etc.)

  See './alsa-info.sh --help' for command line options.

  Automatically upload ALSA information to www.alsa-project.org? [y/N] : y
  Uploading information to www.alsa-project.org ...  Done!

  Your ALSA information is located at http://www.alsa-
  project.org/db/?f=84ba91e70cc537608d8ffa04c5ec05a08bcf1ed6

  Please inform the person helping you.

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

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

[Touch-packages] [Bug 736349] Re: "Test speakers" is silent

See
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1774904/comments/4.
gnome-control-center should rather add libcanberra-pulse to depends
rather than just recommends.

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

Title:
  "Test speakers" is silent

Status in OEM Priority Project:
  Fix Released
Status in gnome-media package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntu-sounds package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-media

  My speakers are working fine (I can year playback with Banshee and
  VLC), but "Test speakers" is silent. I hear nothing when I press on
  the "Test" button.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-media 2.32.0-0ubuntu5
  Uname: Linux 2.6.38-020638-generic x86_64
  Architecture: amd64
  Date: Wed Mar 16 20:30:19 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100921.1)
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-media
  UpgradeStatus: Upgraded to natty on 2011-03-11 (5 days ago)

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

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

[Touch-packages] [Bug 1774904] Re: No defualt sound. Test speakers not working.

Hi, in my case, I think it was simply a missing package dependency.
Installing the libcanberra-pulse package fixed it for me.

gnome-control should probably add libcanberra-pulse to a proper
dependency rather than just recommends since it's likely common that
people would want to test speakers and the test silently failing (e.g.
control-centre doesn't even warn its missing the libs it needs) makes a
user (me for example) get lost (i.e. inspecting ALSA, etc) when the
silent test failure misleads.

Also noted at the end of: https://bugs.launchpad.net/ubuntu/+source
/gnome-media/+bug/736349

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

Title:
  No defualt sound. Test speakers not working.

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Default sound is silent, choosing another sound (ie. Sonar) plays the
  sound until the control panel is closed. Test speakers does not
  produce any sounds. Sounds and music work in FF and Rhythm Box.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1766 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sun Jun  3 21:10:36 2018
  InstallationDate: Installed on 2018-03-26 (69 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CO96510J.86A.6100.2009.1004.2331
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DQ965GF
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD41676-402
  dmi.chassis.type: 3
  dmi.chassis.vendor: IN WIN
  dmi.chassis.version: IW-Z583
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrCO96510J.86A.6100.2009.1004.2331:bd10/04/2009:svnPrimeSystems:pnCF2007-965:pvr:rvnIntelCorporation:rnDQ965GF:rvrAAD41676-402:cvnINWIN:ct3:cvrIW-Z583:
  dmi.product.name: CF2007-965
  dmi.sys.vendor: Prime Systems

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

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

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/resolvconf/+git/resolvconf/+merge/363748

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1774904] Re: No defualt sound. Test speakers not working.

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

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

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

Title:
  No defualt sound. Test speakers not working.

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Default sound is silent, choosing another sound (ie. Sonar) plays the
  sound until the control panel is closed. Test speakers does not
  produce any sounds. Sounds and music work in FF and Rhythm Box.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1766 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sun Jun  3 21:10:36 2018
  InstallationDate: Installed on 2018-03-26 (69 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CO96510J.86A.6100.2009.1004.2331
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DQ965GF
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD41676-402
  dmi.chassis.type: 3
  dmi.chassis.vendor: IN WIN
  dmi.chassis.version: IW-Z583
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrCO96510J.86A.6100.2009.1004.2331:bd10/04/2009:svnPrimeSystems:pnCF2007-965:pvr:rvnIntelCorporation:rnDQ965GF:rvrAAD41676-402:cvnINWIN:ct3:cvrIW-Z583:
  dmi.product.name: CF2007-965
  dmi.sys.vendor: Prime Systems

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

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

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

2019-02-27 Thread Daniel Mehrmann

Well, if you're a LVM user i recommend to leave ubuntu/debian. I know this 
sounds somewhat hard, but this nasty bug inside the ramdisk mouning script 
exist now more or less since a year! I can't accept a 30 seconds delay on boot 
for nothing and moved on to other distros.
Yes you can fix it inside the script which will be copied, but with a new 
package the file will be overwritten without any warning or save/new file.

Time to untrack this bug now. Good luck!

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in ubiquity source package in Bionic:
  Fix Released

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

[Touch-packages] [Bug 1733870] Comment bridged from LTC Bugzilla

2019-02-27 Thread bugproxy

--- Comment From pedro...@br.ibm.com 2019-02-27 16:10 EDT---
I checked this source package: 
https://launchpad.net/ubuntu/+source/gdb/8.2.50.20190214-0ubuntu1

If that is indeed the one to be used for 19.04, the patches for this
feature are already included there.

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

Title:
  [Ubuntu 19.10] Add GDB support to access/display POWER8 registers

Status in The Ubuntu-power-systems project:
  Incomplete
Status in gdb package in Ubuntu:
  Incomplete

Bug description:
  This feature request is for GDB support for access to Power registers
  that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM
  registers.

  The feature is currently being worked on, so no upstream code is
  available yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733870/+subscriptions

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

[Touch-packages] [Bug 1817955] Re: Getting new "DN is out of the realm subtree" error on adding principal

2019-02-27 Thread Nate Crawford

I do not think so, but I may not fully understand what "subtree"
implies.

The realm was initially created with a command equivalent to:

kdb5_ldap_util -D cn=admin,dc=example,dc=com create -subtrees
dc=example,dc=com -r TEST.EXAMPLE.COM -s -H
ldap://ldapserver.example.com

with user entries like:
dn: uid=testuser,ou=People,dc=example,dc=com

I explicitly added the ou=People,dc=example,dc=com with "kdb5_ldap_util
... modify -subtrees ...", but that did not help. Setting sscope to 2
also did nothing.

I can add a principal without specifying dn, but that leads to an entry like:
dn: 
krbPrincipalName=testu...@test.example.com,cn=TEST.EXAMPLE.COM,cn=krb5,dc=example,dc=com

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

Title:
  Getting new "DN is out of the realm subtree" error on adding principal

Status in krb5 package in Ubuntu:
  New

Bug description:
  Recently applied security update to 14.04.5 LTS kerberos (1.12+dfsg-
  2ubuntu5.4), and started getting errors when adding new principals to
  LDAP.

  Obfuscated example:

  kadmin.local -q "ank -x
  dn=\"uid=testuser,ou=People,dc=example,dc=com\" -pw \"dummypass\"
  testuser"

  now gives:
  Authenticating as principal root/ad...@test.example.com with password.
  NOTICE: no policy specified for testu...@test.example.com; assigning "default"
  add_principal: DN is out of the realm subtree while creating 
"testu...@test.example.com".

  
  This worked up through 1.12+dfsg-2ubuntu5.3, and I think it now fails due to 
changes in src/plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in response to 
CVE-2018-5729 or CVE-2018-5730.

  I'm going to attempt a downgrade to 1.12+dfsg-2ubuntu5.3 to check.

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

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

Re: [Touch-packages] [Bug 1817955] [NEW] Getting new "DN is out of the realm subtree" error on adding principal

2019-02-27 Thread Sam Hartman

Yes, it is because of that change.
is the dn outside of the subtree?

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

Title:
  Getting new "DN is out of the realm subtree" error on adding principal

Status in krb5 package in Ubuntu:
  New

Bug description:
  Recently applied security update to 14.04.5 LTS kerberos (1.12+dfsg-
  2ubuntu5.4), and started getting errors when adding new principals to
  LDAP.

  Obfuscated example:

  kadmin.local -q "ank -x
  dn=\"uid=testuser,ou=People,dc=example,dc=com\" -pw \"dummypass\"
  testuser"

  now gives:
  Authenticating as principal root/ad...@test.example.com with password.
  NOTICE: no policy specified for testu...@test.example.com; assigning "default"
  add_principal: DN is out of the realm subtree while creating 
"testu...@test.example.com".

  
  This worked up through 1.12+dfsg-2ubuntu5.3, and I think it now fails due to 
changes in src/plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in response to 
CVE-2018-5729 or CVE-2018-5730.

  I'm going to attempt a downgrade to 1.12+dfsg-2ubuntu5.3 to check.

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

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

[Touch-packages] [Bug 1815415] Re: please update libseccomp for newer kernel syscalls

Hello Christian, or anyone else affected,

Accepted libseccomp into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libseccomp/2.3.1-2.1ubuntu4.1 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libseccomp (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  please update libseccomp for newer kernel syscalls

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Bionic:
  Fix Committed
Status in libseccomp source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * The libseccomp library provides an easy to use, platform independent,
     interface to the Linux Kernel's syscall filtering mechanism. But it can
     only "control" those syscalls it knows about. Therefore staying up to
     date with newer kernels is a requirement to be fully funcitonal.

   * At the time 18.04 was released with the 4.15 kernel the new definitions
     were not yet released for libseccomp - lets fix this mismatch by
     backporting the new syscall definitions [2][3][4].

  [Test Case]

   * Note: a lot of this is kernel dependent it should work with the
  intended SRU target of Bionic with kernel 4.15 or 4.18, but be careful
  to run it there (e.g. not a LXD container on Xenials 4.4 kernel)

   * we modify the already existing autopkgtest for this SRU
  verification

  # Prep
  $ apt install ubuntu-dev-tools build-essential linux-libc-dev libseccomp-dev 
libseccomp2 seccomp
  $ pull-lp-source libseccomp bionic
  $ cd libseccomp-2.3.1
  $ export ADTTMP=$(mktemp -d); echo $ADTTMP
  # run original tests as-is (should pass/fail as expected)
  $ ./debian/tests/test-filter
  # add new syscalls of this SRU
  $ cp debian/tests/data/safe.filter debian/tests/data/newcodes.filter
  $ printf 
"preadv2\npwritev2\npkey_mprotect\npkey_alloc\npkey_free\nget_tls\ns390_guarded_storage\ns390_sthyi\n"
 >> debian/tests/data/newcodes.filter
  # remove unknown calls (x86 4.18 kernel)
  sed -i -e '/^_exit$/d' -e '/^fstatvfs$/d' -e '/^llseek$/d' -e '/^pread$/d' -e 
'/^pselect$/d' -e '/^pwrite$/d' -e '/^sigtimedwait$/d' -e '/^sigwaitinfo$/d' -e 
'/^statvfs$/d' debian/tests/data/newcodes.filter
  # make unknown call a fail
  $ sed -i -e '111s/continue;/{fprintf(stderr, "failed to find %s\\n",buf);rc = 
-1;goto out;}/' debian/tests/src/test-seccomp.c
  # run this special test and check return value
  ${ADTTMP}/exe ./debian/tests/data/newcodes.filter /bin/date; echo $?

  Without the fix it will fail like:
  DEBUG: seccomp_load_filters ./debian/tests/data/newcodes.filter
  failed to find preadv2
  seccomp_load_filters failed with -1
  1

  But with the fix applied those new calls will work:
  DEBUG: seccomp_load_filters ./debian/tests/data/newcodes.filter
  Tue Feb 12 07:41:05 UTC 2019
  0

  
  [Regression Potential]

   * This isn't adding new active code like functions, but only extending
     the definitions of per-arch syscall numbers to be aware of the newer
     syscalls that were added in the kernel. Therefore no old use-cases
     should regress (they are not touched). The only change in behavior for
     an SRU POV would be that things that got denied so far (e.g. if you
     tried to set such a new syscall through libseccomp) was denied before
     and would now work. I think that is exactly the intention of the SRU
     and not a regression.

  [Other Info]

   * Requested while security reviewing an libseccomp SRU to have one update
     for both [1].
   * we also missed the former update for kernel 4.9 [3] AND 4.10 [4] as the
     official releases of the lib are rather seldom.
   * In general there already are build time tests and autopkgtests in the 
 package already. So coverage of "old calls" f

[Touch-packages] [Bug 1755250] Re: backport statx syscall whitelist fix

Hello xantares, or anyone else affected,

Accepted libseccomp into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libseccomp/2.3.1-2.1ubuntu4.1 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: libseccomp (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  backport statx syscall whitelist fix

Status in docker.io package in Ubuntu:
  Invalid
Status in libseccomp package in Ubuntu:
  Fix Released
Status in docker.io source package in Bionic:
  Invalid
Status in libseccomp source package in Bionic:
  Fix Committed
Status in docker.io source package in Cosmic:
  Invalid
Status in libseccomp source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

   * Some newer workloads fail due to libseccomp as in Bionic lacking
  statx support

   * This backports the syscall definitions for statx to Bionic to allow
  to manage those

  [Test Case]

  # Note: I took a KVM image of Bionic to not spoil my system with Docker 
config for this test too much
  $ sudo apt install docker.io
  $ sudo usermod -a -G docker ubuntu
  $ cat > test-statx/Dockerfile << EOF
  FROM ubuntu:18.04
  RUN apt-get update && apt-get install -y wget gcc
  WORKDIR /tmp
  RUN wget -q 
https://raw.githubusercontent.com/torvalds/linux/master/samples/statx/test-statx.c
  RUN gcc test-statx.c -o test-statx
  RUN touch test-file
  RUN chmod +x ./test-statx
  RUN ./test-statx test-file
  EOF
  $ docker build test-statx

  With the bug and current docker 18.06.1-0ubuntu1~18.04.1 in Bionic
  that yields

  [...]
  Step 8/8 : RUN ./test-statx test-file
   ---> Running in 6e60a82409e6
  test-file: Operation not permitted
  statx(test-file) = -1
  The command '/bin/sh -c ./test-statx test-file' returned a non-zero code: 1

  With the fix applied it would work and look like:
  Step 8/8 : RUN ./test-statx test-file
   ---> Running in a83bc043e7bd
  statx(test-file) = 0
  results=fff
Size: 0   Blocks: 0  IO Block: 4096regular file
  Device: 00:32   Inode: 261994  Links: 1
  Access: (0644/-rw-r--r--)  Uid: 0   Gid: 0
  Access: 2019-02-08 07:57:42.0+
  Modify: 2019-02-08 07:57:42.0+
  Change: 2019-02-08 07:57:43.076507007+
   Birth: 2019-02-08 07:57:43.076507007+
  Attributes:  (     
 -... .---.-..)
  Removing intermediate container a83bc043e7bd
   ---> d428d14cbc57
  Successfully built d428d14cbc57

  
  [Regression Potential] 

   * This "only" defines a new syscall number for all the architectures.
  It does not make any other changes, thereby it should be rather safe.
  If anything software could now manage statx through libseccomp and
  behavior that was formerly failing (like the reported docker case)
  would not succeed and due to that be a change in behavior - but I
  think it is a wanted change.

  [Other Info]
   
   * n/a

  ---

  
  Hello maintainer,

  The docker version 17.03 (bionic) in ubuntu doesn't allow the statx syscall 
which is needed to build qt >=5.10 applications:
  https://github.com/docker/for-linux/issues/208#issuecomment-372400859

  Could this fix be backported in the ubuntu package ?
  https://github.com/moby/moby/pull/36417

  regards,
  xan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250/+subscriptions

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

[Touch-packages] [Bug 1817955] [NEW] Getting new "DN is out of the realm subtree" error on adding principal

2019-02-27 Thread Nate Crawford

Public bug reported:

Recently applied security update to 14.04.5 LTS kerberos (1.12+dfsg-
2ubuntu5.4), and started getting errors when adding new principals to
LDAP.

Obfuscated example:

kadmin.local -q "ank -x dn=\"uid=testuser,ou=People,dc=example,dc=com\"
-pw \"dummypass\" testuser"

now gives:
Authenticating as principal root/ad...@test.example.com with password.
NOTICE: no policy specified for testu...@test.example.com; assigning "default"
add_principal: DN is out of the realm subtree while creating 
"testu...@test.example.com".


This worked up through 1.12+dfsg-2ubuntu5.3, and I think it now fails due to 
changes in src/plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in response to 
CVE-2018-5729 or CVE-2018-5730.

I'm going to attempt a downgrade to 1.12+dfsg-2ubuntu5.3 to check.

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

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

Title:
  Getting new "DN is out of the realm subtree" error on adding principal

Status in krb5 package in Ubuntu:
  New

Bug description:
  Recently applied security update to 14.04.5 LTS kerberos (1.12+dfsg-
  2ubuntu5.4), and started getting errors when adding new principals to
  LDAP.

  Obfuscated example:

  kadmin.local -q "ank -x
  dn=\"uid=testuser,ou=People,dc=example,dc=com\" -pw \"dummypass\"
  testuser"

  now gives:
  Authenticating as principal root/ad...@test.example.com with password.
  NOTICE: no policy specified for testu...@test.example.com; assigning "default"
  add_principal: DN is out of the realm subtree while creating 
"testu...@test.example.com".

  
  This worked up through 1.12+dfsg-2ubuntu5.3, and I think it now fails due to 
changes in src/plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in response to 
CVE-2018-5729 or CVE-2018-5730.

  I'm going to attempt a downgrade to 1.12+dfsg-2ubuntu5.3 to check.

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

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

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

Yes that works, and many thanks for the explanation.

/etc/resolv.conf is now linked to /run/resolvconf/resolv.conf
and contains only the local proxy dns:

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

and all works as expected

But in the long term I guess I should move to systemd-networkd as the
preferred way to set static ip?

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

2019-02-27 Thread Chris Henderson

Hello Steve,

> * still showing WARNING:Failed to connect to lvmetad. Falling back to
device scanning.

> That is NOT the defining symptom of the bug. This message would always
be shown. The question is whether there is an unreasonable and
unnecessary boot delay after the message is displayed.

I have followed the same steps as Marc Pignat (who you quoted) and can
confirm that I am still getting the problem. To clarify, I am getting
the same unreasonable and unnecessary boot delay after the message is
displayed, as I was getting before upgrading the package.

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Committed
Status in ubiquity source package in Bionic:
  Fix Released

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

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

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

[Touch-packages] [Bug 1641417] Re: Ubuntu 16.04 unable to detect/connect to and work properly with iPhone 4.

2019-02-27 Thread Rob Cannell

This is still an issue for me on Ubuntu 18.04. Can mount iPhone 5 via
Nautilus but it doesn't show on Rhythmbox or Banshee.

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

Title:
  Ubuntu 16.04 unable to detect/connect  to and work properly with
  iPhone 4.

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  
  Action 1: Plug an iPhone 4 to a just booted up Ubuntu 16.04 workstation. 
  Result 1: 2 iPhone connections appear in Nautilus. 1st connect is mount via 
gphoto2, where access is limited to viewing and copying photos and videos. The 
2nd connection that is mounted via afc fail to work, hence other folders in 
iPhone are not accessible.

  Action 2: Unplugged and re-plugged iPhone 4 to the workstation.
  Result 2: iPhone 4 does not reappear in Nautilus at all. No iPhone mount 
point appear.

  Checks and Remedy used: 
  1. "ideviceinfo" and lsusb command show iPhone 4 is connected.
  2. "idevicepair validate" command shows "SUCCESS: Validated pairing with 
device [UDID]"
  3. After running "ifuse /media/iPhone" command, iPhone 4 reappears in 
Nautilus as mounted in /media/iPhone. Furthermore, all folders of iPhone 4 
appears and are accessible.

  I believe the 1st mounting of iPhone 4 on Nautilus is due to the
  "gvfs-backends" package. W/o it, auto detection/connection of iPhone 4
  would not occur and appear in Nautilus. However, the afc mount failed
  to work

  The 2nd mounting is caused by ifuse. This works perfectly but requires
  manual mounting and unmounting.

  
  Questions: 
  1. How to overcome issues/failures mentioned in Result 1 & 2? 
  2. Ideally, i would like the automatic detection-connection between Ubuntu 
and iPhone to work. If not, is there a way to automate connection via ifuse? 

  
  System and package info:

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

  $ uname -or
  4.4.0-47-generic GNU/Linux

  $ dpkg -l | grep iPhone
  ii  ifuse1.1.2-0.1build3 amd64  FUSE module for 
iPhone and iPod Touch devices
  ii  libimobiledevice-utils   1.2.0+dfsg-3~ubuntu0.2  amd64  Library for 
communicating with iPhone and iPod Touch devices
  ii  libimobiledevice6:amd64  1.2.0+dfsg-3~ubuntu0.2  amd64  Library for 
communicating with the iPhone and iPod Touch
  ii  libusbmuxd-tools 1.0.10-2ubuntu0.1   amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices - tools
  ii  libusbmuxd4:amd641.0.10-2ubuntu0.1   amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices - library
  ii  usbmuxd  1.1.0-2 amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices

  $ dpkg -l | grep libusb
  ii  libgusb2:amd64   0.2.9-0ubuntu1  amd64   GLib wrapper around 
libusb1
  ii  libusb-0.1-4:amd64   2:0.1.12-28 amd64   userspace USB 
programming library
  ii  libusb-1.0-0:amd64   2:1.0.20-1  amd64   userspace USB 
programming library
  ii  libusb-1.0-0:i3862:1.0.20-1  i386userspace USB 
programming library
  ii  libusbmuxd-tools 1.0.10-2ubuntu0.1   amd64   USB multiplexor 
daemon for iPhone and iPod Touch devices - tools
  ii  libusbmuxd4:amd641.0.10-2ubuntu0.1   amd64   USB multiplexor 
daemon for iPhone and iPod Touch devices - library
  ii  libusbredirhost1:amd64   0.7.1-1 amd64   Implementing the 
usb-host (*) side of a usbredir connection (runtime)
  ii  libusbredirparser1:amd64 0.7.1-1 amd64   Parser for the 
usbredir protocol (runtime)

  $ dpkg -l | grep gvfs
  ii  gvfs:amd64  1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - GIO module
  ii  gvfs-backends   1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - backends
  ii  gvfs-bin1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - binaries
  ii  gvfs-common 1.28.2-1ubuntu1~16.04.1alluserspace virtual 
filesystem - common data files
  ii  gvfs-daemons1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - servers
  ii  gvfs-fuse   1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - fuse server
  ii  gvfs-libs:amd64 1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - private libraries

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

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

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

> I do not use NetworkManager as I use fixed ip, so the ip, etc. and dns is/was
> specified in /etc/network/interfaces

ah, ok, so you are not using systemd-networkd then, ok that makes sense
since you upgraded from pre-bionic where ifupdown/resolvconf are the
default.  In bionic they have been replaced with just systemd-networkd
(and netplan for configuration) but upgrades keep ifupdown/resolvconf.

> So it seems to that the issue is really that systemd-resolve is adding the 
> options
> to resolv.conf when it shouldn't interfere

no - systemd-resolved does not add anything to the /etc/resolv.conf
file, it *only* sets up its privately-managed files, under
/run/systemd/resolve/.  If /etc/resolv.conf is symlinked to either the
stub or normal systemd-resolved file, then it will pick up all systemd-
resolved's config (since it's just a symlink, of course) but systemd
won't edit an existing /etc/resolv.conf.

> systemd-resolve isn't checking /etc/network/interfaces for dns-
nameservers

it never does.  e/n/i is 100% ifupdown, completely separate from
systemd-networkd.


What's happening here is resolvconf has a systemd service that pulls
"original" config from systemd-resolved:

$ cat /lib/systemd/system/resolvconf-pull-resolved.service 
[Unit]
ConditionPathExists=/run/resolvconf/enable-updates
ConditionFileIsExecutable=/sbin/resolvconf

[Service]
Type=oneshot
ExecStart=+-/bin/sh -c 'cat /run/systemd/resolve/stub-resolv.conf | 
/sbin/resolvconf -a systemd-resolved'


This service is triggered whenever the systemd-resolved stub conf file changes:

$ cat /lib/systemd/system/resolvconf-pull-resolved.path 
[Path]
PathChanged=/run/systemd/resolve/stub-resolv.conf
PathExists=/run/systemd/resolve/stub-resolv.conf

[Install]
WantedBy=systemd-resolved.service


This service is just wrong; the stub-resolv.conf file is *strictly* for use as 
a /etc/resolv.conf symlink when systemd-resolved is managing the system's dns.  
There is another file, /run/systemd/resolve/resolv.conf, that is intended for 
use by other local applications that control the system's dns but also want to 
know about any dns info that systemd-resolved might know about; this file 
leaves out the local stub resolver's address (127.0.0.53) and the edns0 option.


As a temporary workaround until resolvconf can be fixed, can you try 
reinstalling resolvconf, and then disable it from pulling in the 
systemd-resolved stub configuration:

$ sudo apt install resolvconf
$ sudo systemctl disable resolvconf-pull-resolved.path
$ sudo systemctl disable resolvconf-pull-resolved.service
$ sudo reboot


After reboot, you should then have a /etc/resolv.conf that does not contain the 
127.0.0.53 local stub resolver nor the edns0 option.

Let me know if that works.  Thanks!


** Tags added: regression-update sts sts-sponsors

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

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1817947] Re: On Cosmic, there is no automatic pop-up if a Wi-Fi network has a Captive Portal

2019-02-27 Thread Till Kamppeter

** Description changed:

  network-manager has a facility to automatically pop up a Captive Portal
  of a Wi-Fi network if required for access to the internet through that
  network. It does test accesses and on failure it triggers the pop-up.
  
  Unfortunately, this does not work in Cosmic due to an upstream bug which
  is fixed in a later upstream version of network-manager (in Disco the
  pop-up works).
+ 
+ [Impact]
+ 
+ Users of Cosmic who use publicly available Wi-Fi networks (in hotels,
+ stores, ...) with a Captive Portal (Access to an arbitrary web site
+ leads to a page of the Wi-Fi owner to log in or accept the terms) do not
+ get this log-in/accept-terms page presented automatically and if they do
+ not do their first internet access via a web browser but by something
+ else (e-mail, IRC, ...) the access simply does not work. This happens to
+ all users.
+ 
+ [Test Case]
+ 
+ With Cosmic, select a publicly available (usually unencrypted) Wi-Fi
+ network via the facilities of the desktop. The log-in/accept-terms page
+ is not automatically popped up. Access an arbitrary web site with a
+ browser and you see the page (instead of the site you have selected).
+ 
+ With the fix applied, the log-in/accept-terms page will pop-up in a
+ window, as expected and so all users get aware of its presence and the
+ requirement to answer it.
+ 
+ [Regression Potential]
+ 
+ Low, as the solution is an upstream-approved fix which makes part of the
+ current version of network-manager.

** Description changed:

  network-manager has a facility to automatically pop up a Captive Portal
  of a Wi-Fi network if required for access to the internet through that
  network. It does test accesses and on failure it triggers the pop-up.
  
  Unfortunately, this does not work in Cosmic due to an upstream bug which
  is fixed in a later upstream version of network-manager (in Disco the
  pop-up works).
  
  [Impact]
  
  Users of Cosmic who use publicly available Wi-Fi networks (in hotels,
  stores, ...) with a Captive Portal (Access to an arbitrary web site
  leads to a page of the Wi-Fi owner to log in or accept the terms) do not
  get this log-in/accept-terms page presented automatically and if they do
  not do their first internet access via a web browser but by something
  else (e-mail, IRC, ...) the access simply does not work. This happens to
  all users.
  
  [Test Case]
  
  With Cosmic, select a publicly available (usually unencrypted) Wi-Fi
  network via the facilities of the desktop. The log-in/accept-terms page
  is not automatically popped up. Access an arbitrary web site with a
  browser and you see the page (instead of the site you have selected).
  
  With the fix applied, the log-in/accept-terms page will pop-up in a
  window, as expected and so all users get aware of its presence and the
  requirement to answer it.
  
+ Note 1: If you have an access point where you can activate a Captive
+ Portal, you can also test at home or in your office.
+ 
+ Note 2: To do more than one test with one and the same client and
+ without methods like changing your MAC address, do not answer the
+ Captive Portal. Then it would simple appear again the next time you
+ select this network.
+ 
  [Regression Potential]
  
  Low, as the solution is an upstream-approved fix which makes part of the
  current version of network-manager.

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

Title:
  On Cosmic, there is no automatic pop-up if a Wi-Fi network has a
  Captive Portal

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  network-manager has a facility to automatically pop up a Captive
  Portal of a Wi-Fi network if required for access to the internet
  through that network. It does test accesses and on failure it triggers
  the pop-up.

  Unfortunately, this does not work in Cosmic due to an upstream bug
  which is fixed in a later upstream version of network-manager (in
  Disco the pop-up works).

  [Impact]

  Users of Cosmic who use publicly available Wi-Fi networks (in hotels,
  stores, ...) with a Captive Portal (Access to an arbitrary web site
  leads to a page of the Wi-Fi owner to log in or accept the terms) do
  not get this log-in/accept-terms page presented automatically and if
  they do not do their first internet access via a web browser but by
  something else (e-mail, IRC, ...) the access simply does not work.
  This happens to all users.

  [Test Case]

  With Cosmic, select a publicly available (usually unencrypted) Wi-Fi
  network via the facilities of the desktop. The log-in/accept-terms
  page is not automatically popped up. Access an arbitrary web site with
  a browser and you see the page (instead of the site you have
  selected).

  With the fix applied, the log-in/accept-terms page will pop-up in a
  window, as expected and so all users get awa

[Touch-packages] [Bug 1817946] Re: package linux-image-4.15.0-45-generic 4.15.0-45.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2019-02-27 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.15.0-45-generic 4.15.0-45.48 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:
  package linus-image-4.15.0-45-generic 4.15.0-45.48 failed to
  install/upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1176 F pulseaudio
namirasalm   1548 F pulseaudio
   /dev/snd/controlC0:  gdm1176 F pulseaudio
namirasalm   1548 F pulseaudio
  Date: Tue Feb 26 00:16:03 2019
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=49e290fc-e6be-4c95-9a10-3f1c79417eab
  InstallationDate: Installed on 2018-10-23 (127 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80XU
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=54d2d971-1eed-45d6-a46f-e5ba244f02ea ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.6
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-45-generic 4.15.0-45.48 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: 10/29/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5PCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55731WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-14AST
  dmi.modalias: 
dmi:bvnLENOVO:bvr5PCN24WW:bd10/29/2018:svnLENOVO:pn80XU:pvrLenovoideapad320-14AST:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55731WIN:cvnLENOVO:ct10:cvrLenovoideapad320-14AST:
  dmi.product.family: ideapad 320-14AST
  dmi.product.name: 80XU
  dmi.product.version: Lenovo ideapad 320-14AST
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1765477] Re: 5s delay in AAAA dns resolving; artful and earlier is quick

2019-02-27 Thread Benjamin DeCamp

I'm having similar problems with DNS resolution in Bionic Ubuntu-Server.

After configuring the netplan file, with the "local" search suffix, name
resolution works, but I see a 5 second delay for any DNS name ending in
.local.

When watching wireshark during the DIG request, the local system makes
about 25 successful DNS queries to the correct dns server, and the
correct response is returned for all 25 queries. This happens in seconds
0 to 1. Then there is a pause of 4 seconds, then an identical query and
response occurs at second 5, then the DIG result is returned, and the
response is cached by systemd-resolvd.

For some reason the DNS resolver is ignoring all 25 of its first
attempts to resolve the name in the first 0-1 seconds. Then it waits for
4 seconds, makes a single query, and this result is accepted and used.

This netplan file is the only configuration change after installation of
Bionic 18.04.2 Server:

$ cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
 ethernets:
  eth0:
   addresses: [192.168.9.2/24]
   gateway4: 192.168.9.254
   nameservers:
search: [local]
addresses: [192.168.9.1]
 version: 2


** Attachment added: "lots of ignored correct query-responses, then at time=5, 
a single accepted query-response is made"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765477/+attachment/5242115/+files/wireshark-ignored-responses.PNG

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

Title:
  5s delay in  dns resolving; artful and earlier is quick

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Basic steps:
  lxc launch ubuntu-daily:bionic bionic-daily
  lxc exec bionic-daily bash
  sleep 10s (because of #1765173)
  time host -d bionic-daily.lxd # or whatever domain your containers use by 
default

  In bionic, there is a 5s delay when requesting the  record:

  
  root@wondrous-grackle:~# time host -d wondrous-grackle.lxd
  Trying "wondrous-grackle.lxd"
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50934
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  A

  ;; ANSWER SECTION:
  wondrous-grackle.lxd. 0   IN  A   10.0.100.125

  Received 54 bytes from 127.0.0.53#53 in 0 ms
  Trying "wondrous-grackle.lxd"

  (5s delay here)

  
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17153
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  

  Received 38 bytes from 127.0.0.53#53 in 1 ms
  Trying "wondrous-grackle.lxd"
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12145
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  MX

  Received 38 bytes from 127.0.0.53#53 in 0 ms

  real0m5.023s

  
  In artful and xenial, there is no such delay and the (correct) empty reply is 
almost instantaneous.

  See https://pastebin.ubuntu.com/p/KP5DBcKyJr/

  
  In both cases, /etc/resolv.conf points at 127.0.0.53

  
  systemd version:
   *** 237-3ubuntu8 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Touch-packages] [Bug 1817947] [NEW] On Cosmic, there is no automatic pop-up if a Wi-Fi network has a Captive Portal

2019-02-27 Thread Till Kamppeter

Public bug reported:

network-manager has a facility to automatically pop up a Captive Portal
of a Wi-Fi network if required for access to the internet through that
network. It does test accesses and on failure it triggers the pop-up.

Unfortunately, this does not work in Cosmic due to an upstream bug which
is fixed in a later upstream version of network-manager (in Disco the
pop-up works).

** Affects: network-manager (Ubuntu)
 Importance: High
 Status: Triaged

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

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

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

Title:
  On Cosmic, there is no automatic pop-up if a Wi-Fi network has a
  Captive Portal

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  network-manager has a facility to automatically pop up a Captive
  Portal of a Wi-Fi network if required for access to the internet
  through that network. It does test accesses and on failure it triggers
  the pop-up.

  Unfortunately, this does not work in Cosmic due to an upstream bug
  which is fixed in a later upstream version of network-manager (in
  Disco the pop-up works).

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

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

[Touch-packages] [Bug 1817946] [NEW] package linux-image-4.15.0-45-generic 4.15.0-45.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2019-02-27 Thread namira salma

Public bug reported:

package linus-image-4.15.0-45-generic 4.15.0-45.48 failed to
install/upgrade

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-45-generic 4.15.0-45.48
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm1176 F pulseaudio
  namirasalm   1548 F pulseaudio
 /dev/snd/controlC0:  gdm1176 F pulseaudio
  namirasalm   1548 F pulseaudio
Date: Tue Feb 26 00:16:03 2019
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=49e290fc-e6be-4c95-9a10-3f1c79417eab
InstallationDate: Installed on 2018-10-23 (127 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 80XU
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=54d2d971-1eed-45d6-a46f-e5ba244f02ea ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.6
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-45-generic 4.15.0-45.48 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: 10/29/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 5PCN24WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q55731WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 320-14AST
dmi.modalias: 
dmi:bvnLENOVO:bvr5PCN24WW:bd10/29/2018:svnLENOVO:pn80XU:pvrLenovoideapad320-14AST:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55731WIN:cvnLENOVO:ct10:cvrLenovoideapad320-14AST:
dmi.product.family: ideapad 320-14AST
dmi.product.name: 80XU
dmi.product.version: Lenovo ideapad 320-14AST
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package bionic third-party-packages

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

Title:
  package linux-image-4.15.0-45-generic 4.15.0-45.48 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:
  package linus-image-4.15.0-45-generic 4.15.0-45.48 failed to
  install/upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1176 F pulseaudio
namirasalm   1548 F pulseaudio
   /dev/snd/controlC0:  gdm1176 F pulseaudio
namirasalm   1548 F pulseaudio
  Date: Tue Feb 26 00:16:03 2019
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=49e290fc-e6be-4c95-9a10-3f1c79417eab
  InstallationDate: Installed on 2018-10-23 (127 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80XU
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=54d2d971-1eed-45d6-a46f-e5ba244f02ea ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.6
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-45-generic 4.15.0-45.48 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: 10/29/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5PCN24WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55731WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.

[Touch-packages] [Bug 1817897] Re: attempting to enable fingerprint with pam-auth-update breaks gdm

As far as I can tell, the BIOS is able to see the fingerprint reader --
I just booted into the BIOS and told it to reset the fingerprint data,
and it said that it had done so successfully -- so this appears to be a
Linux-specific issue.

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

Title:
  attempting to enable fingerprint with pam-auth-update breaks gdm

Status in pam package in Ubuntu:
  New

Bug description:
  I ran sudo pam-auth-update, enabled "Fingerprint authentication",
  selected "OK", and then rebooted.

  GDM wouldn't start after the reboot:

  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=121 pid=1551 
comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: Unable to 
register display with display manager

  I logged in on a VT and ran pam-auth-update again. I observed that
  "Register user sessions in the systemd control group" was not
  selected, even though my recollection was that it had been selected
  before I enabled fingerprint authentication, and I didn't disable it.

  I unselected fingerprint authentication and selected "Register user
  sessions in the systemd control group" and rebooted again. GDM started
  working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libpam-runtime 1.3.1-5ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 06:31:32 2019
  InstallationDate: Installed on 2019-02-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago)

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

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

[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

Hello Agustin, or anyone else affected,

Accepted gnome-control-center into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.28.2-0ubuntu0.18.04.3 in a few hours, and then
in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gnome-control-center (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in upower source package in Bionic:
  Incomplete
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  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:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0

[Touch-packages] [Bug 1765477] Re: 5s delay in AAAA dns resolving; artful and earlier is quick

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

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

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

Title:
  5s delay in  dns resolving; artful and earlier is quick

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Basic steps:
  lxc launch ubuntu-daily:bionic bionic-daily
  lxc exec bionic-daily bash
  sleep 10s (because of #1765173)
  time host -d bionic-daily.lxd # or whatever domain your containers use by 
default

  In bionic, there is a 5s delay when requesting the  record:

  
  root@wondrous-grackle:~# time host -d wondrous-grackle.lxd
  Trying "wondrous-grackle.lxd"
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50934
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  A

  ;; ANSWER SECTION:
  wondrous-grackle.lxd. 0   IN  A   10.0.100.125

  Received 54 bytes from 127.0.0.53#53 in 0 ms
  Trying "wondrous-grackle.lxd"

  (5s delay here)

  
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17153
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  

  Received 38 bytes from 127.0.0.53#53 in 1 ms
  Trying "wondrous-grackle.lxd"
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12145
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;wondrous-grackle.lxd.IN  MX

  Received 38 bytes from 127.0.0.53#53 in 0 ms

  real0m5.023s

  
  In artful and xenial, there is no such delay and the (correct) empty reply is 
almost instantaneous.

  See https://pastebin.ubuntu.com/p/KP5DBcKyJr/

  
  In both cases, /etc/resolv.conf points at 127.0.0.53

  
  systemd version:
   *** 237-3ubuntu8 500
  500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

Thanks again for the help

Removed resolvconf:
sudo apt remove resolvconf

reboot

as expected now /etc/resolv.conf is linked to run/systemd/sub-resolv.conf
and contains only:

nameserver 127.0.0.53
options edns0

BUT now I cannot connect to anything, nslookup, ping fails, etc.
$ ping google.com
ping: google.com: Temporary failure in name resolution

and
$ systemd-resolve --status
does not list any dns

So I made a guess and added DNS=192.168.2.1
to /etc/systemd/resolved.conf

$ sudo systemctl restart systemd-resolved

now
$ systemd-resolve --status
lists dns as 192.168.2.1

and all is good...

Additional info:
I do not use NetworkManager as I use fixed ip, so the ip, etc. and dns is/was 
specified in
/etc/network/interfaces

Seems resolvconf was detecting this and adding the dns to resolv.conf,
but systemd-resolve is not looking or detecting ?

So it seems to that the issue is really that systemd-resolve is adding
the options to resolv.conf when it shouldn't interfere because
resolvconf is in charge of it OR that systemd-resolve isn't checking
/etc/network/interfaces for dns-nameservers

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1775018] Re: Fix for openssl 1.0.2 backport

2019-02-27 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: Confirmed => Fix Released

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

Title:
  Fix for openssl 1.0.2 backport

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl1.0 package in Ubuntu:
  Won't Fix
Status in openssl source package in Xenial:
  Invalid
Status in openssl1.0 source package in Xenial:
  Invalid
Status in openssl source package in Bionic:
  Fix Released
Status in openssl1.0 source package in Bionic:
  Fix Released
Status in openssl source package in Cosmic:
  Fix Released
Status in openssl1.0 source package in Cosmic:
  Fix Released
Status in openssl source package in Disco:
  Fix Released
Status in openssl1.0 source package in Disco:
  Won't Fix

Bug description:
  [Impact]

   * Fix hw accelerated performance impact on s390x with non-default
  openssl1.0.

  [Test Case]

   * Test that performance of hw accelerated crypto is improved / i.e.
  ssl speed test

   * Test that openssh still works, just in case.

  [Regression Potential]

   * This only changes accelerated codepath on s390x, for specific algos when 
CPACF is enabled on the system cpu, which is usually on.
   * Same fix is already in use by 1.1.0 default openssl package, and well 
excercised on bionic and up.

  [Other Info]
   
   * original bug report.

  
  This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and 
upstream code are not affected ).

  Original LP ticket :
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775018/+subscriptions

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

[Touch-packages] [Bug 1817897] Re: attempting to enable fingerprint with pam-auth-update breaks gdm

I have a new Thinkpad X1 Carbon 6th generation. I can see the
fingerprint reader right next to the trackpad, and the specs say that it
has one, but I don't see it showing up in the output of lspci or lsusb.
Maybe I'm missing it? Maybe it's not supported? Or maybe there's a
hardware issue? I'm not sure how to tell.

lsusb output:

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0bda:0328 Realtek Semiconductor Corp. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 06cb:009a Synaptics, Inc. 
Bus 001 Device 005: ID 04f2:b614 Chicony Electronics Co., Ltd 
Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
Bus 001 Device 003: ID 04f2:b615 Chicony Electronics Co., Ltd 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

Title:
  attempting to enable fingerprint with pam-auth-update breaks gdm

Status in pam package in Ubuntu:
  New

Bug description:
  I ran sudo pam-auth-update, enabled "Fingerprint authentication",
  selected "OK", and then rebooted.

  GDM wouldn't start after the reboot:

  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=121 pid=1551 
comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: Unable to 
register display with display manager

  I logged in on a VT and ran pam-auth-update again. I observed that
  "Register user sessions in the systemd control group" was not
  selected, even though my recollection was that it had been selected
  before I enabled fingerprint authentication, and I didn't disable it.

  I unselected fingerprint authentication and selected "Register user
  sessions in the systemd control group" and rebooted again. GDM started
  working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libpam-runtime 1.3.1-5ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 06:31:32 2019
  InstallationDate: Installed on 2019-02-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago)

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

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

[Touch-packages] [Bug 1775018] Re: Fix for openssl 1.0.2 backport

This bug was fixed in the package openssl1.0 - 1.0.2n-1ubuntu6.2

---
openssl1.0 (1.0.2n-1ubuntu6.2) cosmic-security; urgency=medium

  * SECURITY UPDATE: 0-byte record padding oracle
- debian/patches/CVE-2019-1559.patch: go into the error state if a
  fatal alert is sent or received in ssl/d1_pkt.c, ssl/s3_pkt.c.
- CVE-2019-1559
  * debian/patches/s390x-fix-aes-gcm-tls.patch: fix typo in backported
s390x hw acceleration patch. (LP: #1775018)

 -- Marc Deslauriers   Tue, 26 Feb 2019
14:45:07 -0500

** Changed in: openssl1.0 (Ubuntu Cosmic)
   Status: Confirmed => Fix Released

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

** Changed in: openssl1.0 (Ubuntu Bionic)
   Status: Confirmed => Fix Released

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

Title:
  Fix for openssl 1.0.2 backport

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl1.0 package in Ubuntu:
  Won't Fix
Status in openssl source package in Xenial:
  Invalid
Status in openssl1.0 source package in Xenial:
  Invalid
Status in openssl source package in Bionic:
  Fix Released
Status in openssl1.0 source package in Bionic:
  Fix Released
Status in openssl source package in Cosmic:
  Fix Released
Status in openssl1.0 source package in Cosmic:
  Fix Released
Status in openssl source package in Disco:
  Fix Released
Status in openssl1.0 source package in Disco:
  Won't Fix

Bug description:
  [Impact]

   * Fix hw accelerated performance impact on s390x with non-default
  openssl1.0.

  [Test Case]

   * Test that performance of hw accelerated crypto is improved / i.e.
  ssl speed test

   * Test that openssh still works, just in case.

  [Regression Potential]

   * This only changes accelerated codepath on s390x, for specific algos when 
CPACF is enabled on the system cpu, which is usually on.
   * Same fix is already in use by 1.1.0 default openssl package, and well 
excercised on bionic and up.

  [Other Info]
   
   * original bug report.

  
  This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and 
upstream code are not affected ).

  Original LP ticket :
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775018/+subscriptions

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

[Touch-packages] [Bug 1775018] Re: Fix for openssl 1.0.2 backport

This bug was fixed in the package openssl1.0 - 1.0.2n-1ubuntu5.3

---
openssl1.0 (1.0.2n-1ubuntu5.3) bionic-security; urgency=medium

  * SECURITY UPDATE: 0-byte record padding oracle
- debian/patches/CVE-2019-1559.patch: go into the error state if a
  fatal alert is sent or received in ssl/d1_pkt.c, ssl/s3_pkt.c.
- CVE-2019-1559
  * debian/patches/s390x-fix-aes-gcm-tls.patch: fix typo in backported
s390x hw acceleration patch. (LP: #1775018)

 -- Marc Deslauriers   Tue, 26 Feb 2019
14:46:16 -0500

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

Title:
  Fix for openssl 1.0.2 backport

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl1.0 package in Ubuntu:
  Won't Fix
Status in openssl source package in Xenial:
  Invalid
Status in openssl1.0 source package in Xenial:
  Invalid
Status in openssl source package in Bionic:
  Fix Released
Status in openssl1.0 source package in Bionic:
  Fix Released
Status in openssl source package in Cosmic:
  Fix Released
Status in openssl1.0 source package in Cosmic:
  Fix Released
Status in openssl source package in Disco:
  Fix Released
Status in openssl1.0 source package in Disco:
  Won't Fix

Bug description:
  [Impact]

   * Fix hw accelerated performance impact on s390x with non-default
  openssl1.0.

  [Test Case]

   * Test that performance of hw accelerated crypto is improved / i.e.
  ssl speed test

   * Test that openssh still works, just in case.

  [Regression Potential]

   * This only changes accelerated codepath on s390x, for specific algos when 
CPACF is enabled on the system cpu, which is usually on.
   * Same fix is already in use by 1.1.0 default openssl package, and well 
excercised on bionic and up.

  [Other Info]
   
   * original bug report.

  
  This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and 
upstream code are not affected ).

  Original LP ticket :
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775018/+subscriptions

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

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

Thanks for the attention to this:

DNS servers: 208.67.220.220 (opend dns) and 212.159.6.10 (recommended by
isp)

typical sites: planthealth.co.uk, plus random others...
nslookup and dig ok
ping domain_name gives "Name or service not known"
ping ip ok
FF: Hmmm problem etc...

So this is my resolv.conf which is def linked to
/run/resolvconf/resolv.conf rather than the systemd stub-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 192.168.2.1
nameserver 127.0.0.53
options edns0

I do have resolvconf installed (think I upgreded to Mint 19 from 18.3 so that 
explains it...)...
will remove and report back...

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1817897] Re: attempting to enable fingerprint with pam-auth-update breaks gdm

You are right that pam shouldn't lead to gdm not working in any case.
Knowing the context help to define the priority of the issue though.

The initial report/tools indicate that you are on 19.04, fingerprint
authentification should work out of the box there (if you have a
supported reader, which might be the issue, what device do you have?).
That's probably worth another report (unless it's known/the device not
being handled under linux)

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

Title:
  attempting to enable fingerprint with pam-auth-update breaks gdm

Status in pam package in Ubuntu:
  New

Bug description:
  I ran sudo pam-auth-update, enabled "Fingerprint authentication",
  selected "OK", and then rebooted.

  GDM wouldn't start after the reboot:

  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=121 pid=1551 
comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: Unable to 
register display with display manager

  I logged in on a VT and ran pam-auth-update again. I observed that
  "Register user sessions in the systemd control group" was not
  selected, even though my recollection was that it had been selected
  before I enabled fingerprint authentication, and I didn't disable it.

  I unselected fingerprint authentication and selected "Register user
  sessions in the systemd control group" and rebooted again. GDM started
  working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libpam-runtime 1.3.1-5ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 06:31:32 2019
  InstallationDate: Installed on 2019-02-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago)

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

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

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

Ok I have found what the problem is, I think; I suspect that you have
resolvconf installed on your system, which is taking over the
/etc/resolv.conf file, and I think that resolvconf is pulling the edns0
option, but also including external nameserver(s), which is an incorrect
configuration, since the edns0 option should only be used when talking
to the local stub resolver, because we don't know if external dns
server(s) support edns.

The resolvconf package is not installed by default for Bionic (though I
am not sure if Mint installs it by default for some reason).  Is this
system upgraded from a previous release, or did you install resolvconf
manually?  Unless you specifically need it, can you try unistalling
resolvconf and rebooting to see if that fixes the problem for you?

$ sudo apt remove resolvconf
$ sudo reboot

And also please do paste the contents of /etc/resolv.conf here,
especially if removing resolvconf doesn't help.

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

@downgrade, basically

$ dpkg -l | grep 237-3ubuntu10
-> that should give you the list of systemd debs installed

download those from  https://bugs.launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+build/16258134

and use 'sudo dpkg -i *.deb'

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1817034] Re: Text console login does not allow login - it behaves as if "entered" is continuously keyed after "login". N

2019-02-27 Thread Paul White

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

** This bug has been marked a duplicate of bug 1813873
   Userspace break as a result of missing patch backport

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

Title:
  Text console login does not allow login - it behaves as if "entered"
  is continuously keyed after "login". N

Status in shadow package in Ubuntu:
  New

Bug description:
  The following happens with any user, WITHOUT typing any password !! Only one 
"ENTER" keyed.
  Login: myuser
  Password: 

  Login incorrect
  Login: 

  Login incorrect 
  ...

  
  To happens to all Alt+Ctrl+Fx , while no problem appears in graphical 
terminals or Gnome.
  That appeared only after the last updates, with kernel 4.15.0-45 .
  If I boot back to 4.15.0-43  the issue does not appear.

  The /var/log/auth.log shows: 
  login[6180]: pam_unix(login:auth): conversation failed
  login[6180]: pam_unix(login:auth): auth could not identify password for 
[myuser]
  login[6180]: FAILED LOGIN (1) on '/dev/tty3' FOR 'myuser', Authentication 
failure
  login[6180]: pam_securetty(login:auth): cannot determine username
  login[6180]: FAILED LOGIN (2) on '/dev/tty3' FOR 'UNKNOWN', Error in service 
module
  login[6180]: pam_securetty(login:auth): cannot determine username
  login[6180]: FAILED LOGIN (3) on '/dev/tty3' FOR 'UNKNOWN', Error in service 
module
  login[6180]: pam_securetty(login:auth): cannot determine username
  login[6180]: FAILED LOGIN (4) on '/dev/tty3' FOR 'UNKNOWN', Error in service 
module

  The /var/log/audit.log shows: 
  type=USER_LOGIN msg=audit(1550742677.578:221): pid=7230 uid=0 auid=4294967295 
ses=4294967295 msg='op=login acct="UNKNOWN" exe="/bin/login" hostname=P50 
addr=? terminal=/dev/tty3 res=failed'
  type=USER_AUTH msg=audit(1550742680.902:222): pid=7230 uid=0 auid=4294967295 
ses=4294967295 msg='op=PAM:authentication acct="?" exe="/bin/login" 
hostname=P50 addr=? terminal=/dev/tty3 res=failed'
  type=USER_LOGIN msg=audit(1550742680.902:223): pid=7230 uid=0 auid=4294967295 
ses=4294967295 msg='op=login acct="UNKNOWN" exe="/bin/login" hostname=P50 
addr=? terminal=/dev/tty3 res=failed'
  type=SERVICE_STOP msg=audit(1550742730.226:224): pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  type=SERVICE_START msg=audit(1550742730.226:225): pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  type=SERVICE_STOP msg=audit(1550742730.226:226): pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
  type=SERVICE_START msg=audit(1550742730.230:227): pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: login 1:4.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 21 10:17:48 2019
  InstallationDate: Installed on 2018-11-05 (107 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 305901]

2019-02-27 Thread Nsz-j

(In reply to Kees Cook from comment #14)
> So I'd like to bring this back up and reiterate the issue: there is no
> benefit to the early truncation, and it actively breaks lots of existing
> software (which is why Debian and Ubuntu have had this fix for 10 years now).
> 
> What is the _benefit_ of early truncation that justifies breaking so many
> existing cases?

ideally sprintf, snprintf and sprintf_chk would be able to share code
and have identical behaviour (currently there is a lot of duplicated
logic in glibc with a potential for inconsistent behaviour).

that said, i think _FORTIFY_SOURCE should detect undefined behaviour if
possible since it's a bug that breaks portability.

note that it does not matter what guarantees a library documents: there
are plenty of precedents for compiler optimizations to break code based
on ub in library calls, a compiler can remove all code paths leading to
a sprintf(s, "%s", s), trying to make such code work in glibc is just
hiding a ticking time bomb.

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

Title:
  Intrepid gcc -O2 breaks string appending with sprintf(), due to
  fortify source patch

Status in GLibC:
  Confirmed
Status in 4g8 package in Ubuntu:
  Invalid
Status in abiword package in Ubuntu:
  Invalid
Status in asterisk package in Ubuntu:
  Invalid
Status in atomicparsley package in Ubuntu:
  Invalid
Status in audacious-plugins package in Ubuntu:
  Invalid
Status in barnowl package in Ubuntu:
  Invalid
Status in billard-gl package in Ubuntu:
  Invalid
Status in binutils package in Ubuntu:
  Invalid
Status in blender package in Ubuntu:
  Invalid
Status in ctn package in Ubuntu:
  Invalid
Status in gcc-4.3 package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Fix Released
Status in hypermail package in Ubuntu:
  Invalid
Status in mpeg4ip package in Ubuntu:
  Invalid
Status in nagios-plugins package in Ubuntu:
  Invalid
Status in owl package in Ubuntu:
  Invalid
Status in xmcd package in Ubuntu:
  Invalid
Status in 4g8 source package in Intrepid:
  Invalid
Status in abiword source package in Intrepid:
  Invalid
Status in asterisk source package in Intrepid:
  Invalid
Status in atomicparsley source package in Intrepid:
  Invalid
Status in audacious-plugins source package in Intrepid:
  Invalid
Status in barnowl source package in Intrepid:
  Invalid
Status in billard-gl source package in Intrepid:
  Invalid
Status in binutils source package in Intrepid:
  Invalid
Status in blender source package in Intrepid:
  Invalid
Status in ctn source package in Intrepid:
  Invalid
Status in gcc-4.3 source package in Intrepid:
  Invalid
Status in glibc source package in Intrepid:
  Fix Released
Status in hypermail source package in Intrepid:
  Invalid
Status in mpeg4ip source package in Intrepid:
  Invalid
Status in nagios-plugins source package in Intrepid:
  Invalid
Status in owl source package in Intrepid:
  Invalid
Status in xmcd source package in Intrepid:
  Invalid
Status in 4g8 source package in Jaunty:
  Invalid
Status in abiword source package in Jaunty:
  Invalid
Status in asterisk source package in Jaunty:
  Invalid
Status in atomicparsley source package in Jaunty:
  Invalid
Status in audacious-plugins source package in Jaunty:
  Invalid
Status in barnowl source package in Jaunty:
  Invalid
Status in billard-gl source package in Jaunty:
  Invalid
Status in binutils source package in Jaunty:
  Invalid
Status in blender source package in Jaunty:
  Invalid
Status in ctn source package in Jaunty:
  Invalid
Status in gcc-4.3 source package in Jaunty:
  Invalid
Status in glibc source package in Jaunty:
  Fix Released
Status in hypermail source package in Jaunty:
  Invalid
Status in mpeg4ip source package in Jaunty:
  Invalid
Status in nagios-plugins source package in Jaunty:
  Invalid
Status in owl source package in Jaunty:
  Invalid
Status in xmcd source package in Jaunty:
  Invalid

Bug description:
  Binary package hint: gcc-4.3

  In Hardy and previous releases, one could use statements such as
sprintf(buf, "%s %s%d", buf, foo, bar);
  to append formatted text to a buffer buf.  Intrepid’s gcc-4.3, which has 
fortify source turned on by default when compiling with -O2, breaks this 
pattern.  This introduced mysterious bugs into an application I was compiling 
(the BarnOwl IM client).

  Test case: gcc -O2 sprintf-test.c -o sprintf-test
  :
#include 
char buf[80] = "not ";
int main()
{
sprintf(buf, "%sfail", buf);
puts(buf);
return 0;
}
  This outputs "not fail" in Hardy, and "fail" in Intrepid.

  The assembly output shows that the bug has been introduced by
  replacing the sprintf(buf, "%sfail", buf) call with __sprintf_chk(buf,
  1, 80, "%sfail", buf).  A workaround is to disable fortify source (gcc
  -U_FORTIFY_SOURCE).

  One

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

> in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

in Bionic, resolv.conf links (by default) to /run/systemd/resolve/stub-
resolv.conf; is that what you meant?

Can you paste the contents of your /etc/resolv.conf file here?

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1815236]

2019-02-27 Thread Qamonstergl

The patch was merged to master.
I've performed piglit-test and run check totem-app functionality - all looks 
good.
I close the card.

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

Title:
  totem assert failure: totem: src/intel/genxml/gen9_pack.h:72:
  __gen_uint: La declaración `v <= max' no se cumple.

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/totem/issues/297 (Not GNOME)

  ---

  I'm not sure, but this happened after updating to gstreamer 1.15.1, I
  have problems when I maximize totem.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: 
__gen_uint: La declaración `v <= max' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1815236] Re: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.

2019-02-27 Thread Bug Watch Updater

** Changed in: mesa
   Status: Confirmed => Fix Released

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

Title:
  totem assert failure: totem: src/intel/genxml/gen9_pack.h:72:
  __gen_uint: La declaración `v <= max' no se cumple.

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/totem/issues/297 (Not GNOME)

  ---

  I'm not sure, but this happened after updating to gstreamer 1.15.1, I
  have problems when I maximize totem.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: 
__gen_uint: La declaración `v <= max' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1815236]

2019-02-27 Thread Baker-dylan-c

The mentioned patch has landed in master and 19.0 (presumably it is or
will be in 18.3 shortly), is this okay to close?

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

Title:
  totem assert failure: totem: src/intel/genxml/gen9_pack.h:72:
  __gen_uint: La declaración `v <= max' no se cumple.

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/totem/issues/297 (Not GNOME)

  ---

  I'm not sure, but this happened after updating to gstreamer 1.15.1, I
  have problems when I maximize totem.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: totem 3.30.0-4ubuntu1
  Uname: Linux 4.20.7-042007-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La 
declaración `v <= max' no se cumple.
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  7 18:40:29 2019
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2018-12-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   __assert_fail_base (fmt=0x7ff31939be23 , assertion=0x7ff312a5416c "v <= max", 
file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, 
function=) at assert.c:92
   __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c 
"src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") 
at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: 
__gen_uint: La declaración `v <= max' no se cumple.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

Could you give some examples of DNS lookups that fail for you so we can
try and recreate the issue? Additionally, do you know what DNS servers
you are using?

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

** Changed in: pam (Ubuntu Cosmic)
   Status: New => In Progress

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

** Changed in: pam (Ubuntu Cosmic)
 Assignee: (unassigned) => Eric Desrochers (slashd)

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

Title:
  pam_tty_audit failed in pam_open_session

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Xenial:
  In Progress
Status in pam source package in Bionic:
  In Progress
Status in pam source package in Cosmic:
  In Progress
Status in pam package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Kernel keystroke auditing via pam_tty_audit.so not working
   
   * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it 
failed in pam_open_session.
 It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  [Test Case]

  1. Install libpam-ldap
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails

  [Regression Potential]

   * Low, we are simply including the missing header files and copy the old 
status as initialization of new.
 It's already part of Debian and Disco.

  [Other Info]

  # Upstream fix:
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  # git describe --contains c5f829931a22c65feffee16570efdae036524bee
  Linux-PAM-1_2_0~75

  # rmadision pam
  =>  pam | 1.1.8-1ubuntu2.2   | trusty-updates   | source
  =>  pam | 1.1.8-3.2ubuntu2   | xenial   | source
  =>  pam | 1.1.8-3.2ubuntu2.1 | xenial-updates   | source
  =>  pam | 1.1.8-3.6ubuntu2   | bionic   | source
  =>  pam | 1.1.8-3.6ubuntu2   | cosmic   | source
  pam | 1.3.1-5ubuntu1 | disco| source

  [Original Description]

  Dear Maintainer.

  I found a bug in pam_tty_audit.
  When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed 
in pam_open_session.
  It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.

  * Enviroments
  Ubuntu 14.04.4 LTS
  linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1
  libpam-ldap:amd64184-8.5ubuntu3
  libpam-modules:amd641.1.8-1ubuntu2.2

  Ubuntu 16.04.2 TLS
  linux-image-4.4.0-62-generic4.4.0-62.83
  libpam-ldap:amd64184-8.7ubuntu1
  libpam-modules:amd641.1.8-3.2ubuntu2

  * Reproduction method
  1. Install libpam-ldap.
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails

  * Solution (== 2018/04/16 Link updated ==)
  apply upstream patch
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee

  * Logs (on Ubuntu14.04)
  -- auth.log --
  May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 
port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8
  May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for 
user test by (uid=0)
  May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting 
current audit status: Invalid argument
  May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot 
make/remove an entry for the specified session
  May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: 
disconnected by user

  -- syslog --
  May 18 14:47:03 vm audispd: node=vm type=USER_ACCT 
msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): 
pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1
  May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE 
msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set 
old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0
  May 18 14:47:03 vm audispd: node=vm type=USER_START 
msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=failed'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ss

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

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

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in afterburner.fx package in Ubuntu:
  New
Status in annotation-indexer package in Ubuntu:
  New
Status in apache-directory-server package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in bridge-method-injector package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in elki package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in fontawesomefx package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-core package in Ubuntu:
  New
Status in jackson-databind package in Ubuntu:
  New
Status in jackson-dataformat-xml package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javafxsvg package in Ubuntu:
  New
Status in javamail package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-classfilewriter package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jcommander package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libpdfbox2-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libsambox-java package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libsejda-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mavibot package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in openjpa package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in plexus-io package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubu

[Touch-packages] [Bug 1817912] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1817912/+attachment/5242071/+files/ProcCpuinfoMinimal.txt

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

Title:
  alsa-util.c: Function snd_pcm_avail() returns a value that is
  extraordinarily large: 370196 bytes (2098 мс).

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  An old issue with ALSA is still present in Ubuntu 16.04.6.
  The system became extraordinarily slow and hangs at total in around a minute 
while playing a music (around a few hours in my case).

  [15:38:51]
  [root@ThinkPad/var/log]#grep "alsa-sink-CX20751/2 Analog" syslog
  Feb 27 14:58:50 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily 
large: 370196 bytes (2098 мс).
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver «snd_hda_intel». 
Please report this issue to the ALSA developers.
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: snd_pcm_dump():
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Soft volume PCM
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Control: PCM Playback Volume
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: min_dB: -51
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: max_dB: 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: resolution: 256
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   format   : S16_LE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   subformat: STD
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   channels : 2
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   rate : 44100
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   exact rate   : 44100 (44100/1)
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   msbits   : 16
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   buffer_size  : 16384
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_size  : 8192
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_time  : 185759
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_mode  : ENABLE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_type  : MONOTONIC
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_step  : 1
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   avail_min: 15680
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_event : 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   start_threshold  : -1
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stop_threshold   : 4611686018427387904
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_threshold: 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_size : 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   boundary : 4611686018427387904
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Slave: Hardware PCM card 1 'HDA Intel PCH' device 0 subdevice 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   format   : S16_

[Touch-packages] [Bug 1817912] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1817912/+attachment/5242072/+files/ProcEnviron.txt

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

** Changed in: alsa-utils (Ubuntu)
   Status: New => Confirmed

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

** Description changed:

- An old issue with ALSA is still present in Ubuntu 16.04.5.
+ An old issue with ALSA is still present in Ubuntu 16.04.6.
  The system became extraordinarily slow and hangs at total in around a minute 
while playing a music (around a few hours in my case).
  
  [15:38:51]
  [root@ThinkPad/var/log]#grep "alsa-sink-CX20751/2 Analog" syslog
  Feb 27 14:58:50 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily 
large: 370196 bytes (2098 мс).
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver «snd_hda_intel». 
Please report this issue to the ALSA developers.
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: snd_pcm_dump():
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Soft volume PCM
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Control: PCM Playback Volume
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: min_dB: -51
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: max_dB: 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: resolution: 256
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   format   : S16_LE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   subformat: STD
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   channels : 2
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   rate : 44100
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   exact rate   : 44100 (44100/1)
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   msbits   : 16
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   buffer_size  : 16384
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_size  : 8192
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_time  : 185759
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_mode  : ENABLE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_type  : MONOTONIC
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_step  : 1
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   avail_min: 15680
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_event : 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   start_threshold  : -1
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stop_threshold   : 4611686018427387904
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_threshold: 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_size : 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   boundary : 4611686018427387904
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Slave: Hardware PCM card 1 'HDA Intel PCH' device 0 subdevice 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   format   : S16_LE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   subformat: STD
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-ut

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

My update was from 237-3ubuntu10.11, which didn't have the problem (12
was never installed)

It seems I cannot easily downgrade via apt or synaptic, as the previous
versions do not seem to be in the repos, can you advise how to do so?

On a different machine on the same network I still have 237-3ubuntu10.11
and it is working as expected (and I don't want to update!)

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1817912] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1817912/+attachment/5242070/+files/Dependencies.txt

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

Title:
  alsa-util.c: Function snd_pcm_avail() returns a value that is
  extraordinarily large: 370196 bytes (2098 мс).

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  An old issue with ALSA is still present in Ubuntu 16.04.6.
  The system became extraordinarily slow and hangs at total in around a minute 
while playing a music (around a few hours in my case).

  [15:38:51]
  [root@ThinkPad/var/log]#grep "alsa-sink-CX20751/2 Analog" syslog
  Feb 27 14:58:50 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily 
large: 370196 bytes (2098 мс).
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver «snd_hda_intel». 
Please report this issue to the ALSA developers.
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: snd_pcm_dump():
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Soft volume PCM
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Control: PCM Playback Volume
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: min_dB: -51
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: max_dB: 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: resolution: 256
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   format   : S16_LE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   subformat: STD
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   channels : 2
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   rate : 44100
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   exact rate   : 44100 (44100/1)
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   msbits   : 16
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   buffer_size  : 16384
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_size  : 8192
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_time  : 185759
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_mode  : ENABLE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_type  : MONOTONIC
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_step  : 1
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   avail_min: 15680
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_event : 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   start_threshold  : -1
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stop_threshold   : 4611686018427387904
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_threshold: 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_size : 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   boundary : 4611686018427387904
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Slave: Hardware PCM card 1 'HDA Intel PCH' device 0 subdevice 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   format   : S16_LE
  Feb 27

[Touch-packages] [Bug 1817912] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1817912/+attachment/5242069/+files/CurrentDmesg.txt

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

Title:
  alsa-util.c: Function snd_pcm_avail() returns a value that is
  extraordinarily large: 370196 bytes (2098 мс).

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-utils package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  An old issue with ALSA is still present in Ubuntu 16.04.6.
  The system became extraordinarily slow and hangs at total in around a minute 
while playing a music (around a few hours in my case).

  [15:38:51]
  [root@ThinkPad/var/log]#grep "alsa-sink-CX20751/2 Analog" syslog
  Feb 27 14:58:50 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily 
large: 370196 bytes (2098 мс).
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver «snd_hda_intel». 
Please report this issue to the ALSA developers.
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: snd_pcm_dump():
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Soft volume PCM
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Control: PCM Playback Volume
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: min_dB: -51
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: max_dB: 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: resolution: 256
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   format   : S16_LE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   subformat: STD
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   channels : 2
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   rate : 44100
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   exact rate   : 44100 (44100/1)
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   msbits   : 16
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   buffer_size  : 16384
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_size  : 8192
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_time  : 185759
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_mode  : ENABLE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_type  : MONOTONIC
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_step  : 1
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   avail_min: 15680
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_event : 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   start_threshold  : -1
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stop_threshold   : 4611686018427387904
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_threshold: 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_size : 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   boundary : 4611686018427387904
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Slave: Hardware PCM card 1 'HDA Intel PCH' device 0 subdevice 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   format   : S16_LE
  Feb 27

[Touch-packages] [Bug 1817912] Re: alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily large: 370196 bytes (2098 мс).

apport information

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

** Also affects: alsa-utils (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: apport-collected xenial

** Description changed:

  An old issue with ALSA is still present in Ubuntu 16.04.5.
  The system became extraordinarily slow and hangs at total in around a minute 
while playing a music (around a few hours in my case).
  
  [15:38:51]
  [root@ThinkPad/var/log]#grep "alsa-sink-CX20751/2 Analog" syslog
  Feb 27 14:58:50 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily 
large: 370196 bytes (2098 мс).
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver «snd_hda_intel». 
Please report this issue to the ALSA developers.
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: snd_pcm_dump():
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Soft volume PCM
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Control: PCM Playback Volume
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: min_dB: -51
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: max_dB: 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: resolution: 256
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   format   : S16_LE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   subformat: STD
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   channels : 2
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   rate : 44100
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   exact rate   : 44100 (44100/1)
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   msbits   : 16
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   buffer_size  : 16384
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_size  : 8192
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_time  : 185759
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_mode  : ENABLE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_type  : MONOTONIC
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_step  : 1
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   avail_min: 15680
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_event : 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   start_threshold  : -1
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stop_threshold   : 4611686018427387904
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_threshold: 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_size : 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   boundary : 4611686018427387904
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Slave: Hardware PCM card 1 'HDA Intel PCH' device 0 subdevice 0
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   format   : S16_LE
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   subformat: STD
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   channels : 2
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   rate : 44100
  Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sin

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

** Also affects: apache-directory-server (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in afterburner.fx package in Ubuntu:
  New
Status in annotation-indexer package in Ubuntu:
  New
Status in apache-directory-server package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in bridge-method-injector package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in elki package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in fontawesomefx package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-core package in Ubuntu:
  New
Status in jackson-databind package in Ubuntu:
  New
Status in jackson-dataformat-xml package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javafxsvg package in Ubuntu:
  New
Status in javamail package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-classfilewriter package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libpdfbox2-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libsambox-java package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libsejda-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mavibot package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in openjpa package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in plexus-io package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:

[Touch-packages] [Bug 1817897] Re: attempting to enable fingerprint with pam-auth-update breaks gdm

So, whether or not I needed to run pam-auth-update, doing so and
enabling fingerprint authentication there should not cause GDM to break,
nor should the other weird behavior I described above be happening.

Having said that, yes, I was trying to enable login with fingerprint. I
googled how to do that on Ubuntu and found this page,
https://help.ubuntu.com/stable/ubuntu-help/session-fingerprint.html.en.
But when I followed the instructions there and opened the Users panel,
there was nothing there about fingerprint login. So I googled more and
found this page, https://askubuntu.com/questions/1049526/fingerprint-
activation-on-ubuntu-18-04, which mentioned using pam-auth-update to
ensure that fingerprint authentication was enabled. So I ran pam-auth-
update and found that it wasn't enabled and enabled it, which led to the
problems described above.

If I shouldn't have had to do any of that to be able to configure
fingerprint login, then something else is wrong and I don't even know
where to start looking to figure out what, but regardless of that, the
issues that I encountered with pam-auth-update behaving poorly are still
real.

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

Title:
  attempting to enable fingerprint with pam-auth-update breaks gdm

Status in pam package in Ubuntu:
  New

Bug description:
  I ran sudo pam-auth-update, enabled "Fingerprint authentication",
  selected "OK", and then rebooted.

  GDM wouldn't start after the reboot:

  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=121 pid=1551 
comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: Unable to 
register display with display manager

  I logged in on a VT and ran pam-auth-update again. I observed that
  "Register user sessions in the systemd control group" was not
  selected, even though my recollection was that it had been selected
  before I enabled fingerprint authentication, and I didn't disable it.

  I unselected fingerprint authentication and selected "Register user
  sessions in the systemd control group" and rebooted again. GDM started
  working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libpam-runtime 1.3.1-5ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 06:31:32 2019
  InstallationDate: Installed on 2019-02-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago)

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

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

[Touch-packages] [Bug 464442] Re: alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large: -4496252 bytes (-25488 ms).

An issuue still present in Ubuntu 16.04.5.
```
[15:38:51]
[root@ThinkPad/var/log]#grep "alsa-sink-CX20751/2 Analog" syslog 
Feb 27 14:58:50 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Function snd_pcm_avail() returns a value that is extraordinarily 
large: 370196 байтів (2098 мс).
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver «snd_hda_intel». 
Please report this issue to the ALSA developers.
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: snd_pcm_dump():
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Soft volume PCM
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Control: PCM Playback Volume
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: min_dB: -51
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: max_dB: 0
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: resolution: 256
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   format   : S16_LE
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   subformat: STD
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   channels : 2
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   rate : 44100
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   exact rate   : 44100 (44100/1)
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   msbits   : 16
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   buffer_size  : 16384
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_size  : 8192
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_time  : 185759
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_mode  : ENABLE
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   tstamp_type  : MONOTONIC
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_step  : 1
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   avail_min: 15680
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_event : 0
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   start_threshold  : -1
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stop_threshold   : 4611686018427387904
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_threshold: 0
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   silence_size : 0
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   boundary : 4611686018427387904
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Slave: Hardware PCM card 1 'HDA Intel PCH' device 0 subdevice 0
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c: Its setup is:
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   stream   : PLAYBACK
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   access   : MMAP_INTERLEAVED
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   format   : S16_LE
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   subformat: STD
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   channels : 2
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   rate : 44100
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   exact rate   : 44100 (44100/1)
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   msbits   : 16
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   buffer_size  : 16384
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   period_size  : 8192
Feb 27 14:58:51 ThinkPad pulseaudio[9613]: [alsa-sink-CX20751/2 Analog] 
alsa-util.c:   peri

[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session

** Description changed:

+ [Impact]
+ 
+  * Kernel keystroke auditing via pam_tty_audit.so not working
+  
+  * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it 
failed in pam_open_session.
+It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.
+ 
+ [Test Case]
+ 
+ 1. Install libpam-ldap
+ 2. Add the following to the end of /etc/pam.d/common-sessions
+ 
+ session required pam_tty_audit.so enable=* open_only
+ 
+ 3. When logging in with ssh etc., pam_tty_audit will fail and login fails
+ 
+ [Regression Potential]
+ 
+  * Low, we are simply including the missing header files and copy the old 
status as initialization of new.
+It's already part of Debian and Disco.
+ 
+ [Other Info]
+ 
+ # Upstream fix:
+ 
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee
+ 
+ # git describe --contains c5f829931a22c65feffee16570efdae036524bee
+ Linux-PAM-1_2_0~75
+ 
+ # rmadision pam
+ =>  pam | 1.1.8-1ubuntu2.2   | trusty-updates   | source
+ =>  pam | 1.1.8-3.2ubuntu2   | xenial   | source
+ =>  pam | 1.1.8-3.2ubuntu2.1 | xenial-updates   | source
+ =>  pam | 1.1.8-3.6ubuntu2   | bionic   | source
+ =>  pam | 1.1.8-3.6ubuntu2   | cosmic   | source
+ pam | 1.3.1-5ubuntu1 | disco| source
+ 
+ [Original Description]
+ 
  Dear Maintainer.
  
  I found a bug in pam_tty_audit.
  When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed 
in pam_open_session.
  It was triggared by use uninitialized variable in 
pam_tty_audit.c::pam_open_session.
  
  * Enviroments
  Ubuntu 14.04.4 LTS
  linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1
  libpam-ldap:amd64184-8.5ubuntu3
  libpam-modules:amd641.1.8-1ubuntu2.2
  
  Ubuntu 16.04.2 TLS
  linux-image-4.4.0-62-generic4.4.0-62.83
  libpam-ldap:amd64184-8.7ubuntu1
  libpam-modules:amd641.1.8-3.2ubuntu2
  
  * Reproduction method
  1. Install libpam-ldap.
  2. Add the following to the end of /etc/pam.d/common-sessions
  
  session required pam_tty_audit.so enable=* open_only
  
  3. When logging in with ssh etc., pam_tty_audit will fail and login fails
  
  * Solution (== 2018/04/16 Link updated ==)
  apply upstream patch
  
https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee
  
  * Logs (on Ubuntu14.04)
  -- auth.log --
  May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 
port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8
  May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for 
user test by (uid=0)
  May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting 
current audit status: Invalid argument
  May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot 
make/remove an entry for the specified session
  May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: 
disconnected by user
  
  -- syslog --
  May 18 14:47:03 vm audispd: node=vm type=USER_ACCT 
msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): 
pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1
  May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE 
msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set 
old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0
  May 18 14:47:03 vm audispd: node=vm type=USER_START 
msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=failed'
  May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ 
msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  May 18 14:47:03 vm audispd: node=vm type=CRED_DISP 
msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 
msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 
addr=10.99.0.1 terminal=ssh res=success'
  
  Thanks regards.

** Also affects: pam (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

Title:
  pam_tty_audit failed in pam_open_session

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Xenial:
  In Progr

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

** Also affects: jackson-dataformat-xml (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: jackson-databind (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: jackson-core (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in afterburner.fx package in Ubuntu:
  New
Status in annotation-indexer package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in bridge-method-injector package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in elki package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in fontawesomefx package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-core package in Ubuntu:
  New
Status in jackson-databind package in Ubuntu:
  New
Status in jackson-dataformat-xml package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javafxsvg package in Ubuntu:
  New
Status in javamail package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-classfilewriter package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libpdfbox2-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libsambox-java package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libsejda-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in openjpa package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in plexus-io package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Stat

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

** Also affects: afterburner.fx (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: annotation-indexer (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in afterburner.fx package in Ubuntu:
  New
Status in annotation-indexer package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in bridge-method-injector package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in elki package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in fontawesomefx package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javafxsvg package in Ubuntu:
  New
Status in javamail package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-classfilewriter package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libpdfbox2-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libsambox-java package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libsejda-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in openjpa package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in plexus-io package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-r

[Touch-packages] [Bug 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

Thank you for your bug report, did you try to downgrading the system packages 
to see if that resolves the issue?
The previous update has change in dns queries
https://bugs.launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.12

Would be interesting to know if that version already had 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/1817903

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

Hi Arnold

I got the apparmor log showing boot error.

 Wed Feb 27 09:24:41 -03 2019 
[[0;32m  OK  [0m] Started [0;1;39mShow Plymouth Boot Screen[0m.
[[0;32m  OK  [0m] Started [0;1;39mForward Password R…s to Plymouth Directory 
Watch[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mLocal Encrypted Volumes[0m.
[[0;32m  OK  [0m] Started [0;1;39mNetwork Time Synchronization[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mSystem Time Synchronized[0m.
[[0;32m  OK  [0m] Listening on [0;1;39mLoad/Save RF …itch Status /dev/rfkill 
Watch[0m.
[[0;32m  OK  [0m] Started [0;1;39mNetwork Name Resolution[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mHost and Network Name Lookups[0m.
 Starting [0;1;39mTell Plymouth To Write Out Runtime Data[0m...
 Starting [0;1;39mGRUB failed boot detection[0m...
[[0;32m  OK  [0m] Started [0;1;39mTell Plymouth To Write Out Runtime 
Data[0m.
[[0;32m  OK  [0m] Started [0;1;39mGRUB failed boot detection[0m.
[[0;1;31mFAILED[0m] Failed to start [0;1;39mAppArmor initialization[0m.
See 'systemctl status apparmor.service' for details.
[[0;32m  OK  [0m] Reached target [0;1;39mSystem Initialization[0m.
[[0;32m  OK  [0m] Started [0;1;39mTrigger anacron every hour[0m.
[[0;32m  OK  [0m] Listening on [0;1;39mD-Bus System Message Bus Socket[0m.
[[0;32m  OK  [0m] Started [0;1;39mDaily Cleanup of Temporary Directories[0m.
 Starting [0;1;39mSocket activation for snappy daemon[0m.
[[0;32m  OK  [0m] Started [0;1;39mProcess error repo…rting is enabled (file 
watch)[0m.
[[0;32m  OK  [0m] Started [0;1;39mDaily man-db regeneration[0m.
[[0;32m  OK  [0m] Started [0;1;39mDaily rotation of log files[0m.
[[0;32m  OK  [0m] Started [0;1;39mMessage of the Day[0m.
[[0;32m  OK  [0m] Listening on [0;1;39mActivation so… for spice guest agent 
daemon[0m.
[[0;32m  OK  [0m] Listening on [0;1;39mAvahi mDNS/DNS-SD Stack Activation 
Socket[0m.
[[0;32m  OK  [0m] Listening on [0;1;39mCUPS Scheduler[0m.
[[0;32m  OK  [0m] Started [0;1;39mDiscard unused blocks once a week[0m.
[[0;32m  OK  [0m] Started [0;1;39mDaily apt download activities[0m.
[[0;32m  OK  [0m] Started [0;1;39mDaily apt upgrade and clean activities[0m.
[[0;32m  OK  [0m] Listening on [0;1;39mUUID daemon activation socket[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mTimers[0m.
[[0;32m  OK  [0m] Started [0;1;39mCUPS Scheduler[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mPaths[0m.
 Starting [0;1;39mRaise network interfaces[0m...
[[0;32m  OK  [0m] Listening on [0;1;39mSocket activation for snappy 
daemon[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mSockets[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mBasic System[0m.
 Starting [0;1;39mRotate log files[0m...
 Starting [0;1;39mSystem Logging Service[0m...
[[0;32m  OK  [0m] Started [0;1;39mSet the CPU Frequency Scaling governor[0m.
 Starting [0;1;39mDisk Manager[0m...
[[0;32m  OK  [0m] Reached target [0;1;39mLogin Prompts[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mSound Card[0m.
 Starting [0;1;39mLSB: automatic crash report generation[0m...
 Starting [0;1;39mSwitcheroo Control Proxy service[0m...
 Starting [0;1;39mRestore /etc/reso… the ppp link was shut down[0m...
 Starting [0;1;39mDaily man-db regeneration[0m...
 Starting [0;1;39mThermal Daemon Service[0m...
[[0;32m  OK  [0m] Started [0;1;39mD-Bus System Message Bus[0m.
 Starting [0;1;39mNetwork Manager[0m...
 Starting [0;1;39mWPA supplicant[0m...
 Starting [0;1;39mDetect the availa…eal with any system changes[0m...
 Starting [0;1;39mModem Manager[0m...
 Starting [0;1;39mLogin Service[0m...
 Starting [0;1;39mVirtualBox Linux kernel module[0m...
 Starting [0;1;39mSnappy daemon[0m...
[[0;32m  OK  [0m] Started [0;1;39mRun anacron jobs[0m.
[[0;32m  OK  [0m] Started [0;1;39mRegular background program processing 
daemon[0m.
 Starting [0;1;39mAvahi mDNS/DNS-SD Stack[0m...
 Starting [0;1;39mAccounts Service[0m...
[[0;32m  OK  [0m] Started [0;1;39mCUPS Scheduler[0m.
[[0;32m  OK  [0m] Started [0;1;39mirqbalance daemon[0m.
 Starting [0;1;39mDispatcher daemon for systemd-networkd[0m...
 Starting [0;1;39mLSB: Record successful boot for GRUB[0m...
[[0;32m  OK  [0m] Started [0;1;39mRaise network interfaces[0m.
[[0;32m  OK  [0m] Started [0;1;39mSwitcheroo Control Proxy service[0m.
[[0;32m  OK  [0m] Started [0;1;39mRestore /etc/resolv.conf if the system 
crashed before the ppp link was shut down[0m.
[[0;32m  OK  [0m] Started [0;1;39mDetect the available GPUs and deal with 
any system changes[0m.
[[0;32m  OK  [0m] Started [0;1;39mLSB: automatic crash report generation[0m.
[[0;32m  OK  [0m] Started [0;1;39mVirtualBox Linux kernel module[0m.
[[0;32m  OK  [0m] Started

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

** Also affects: plexus-io (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: libpdfbox2-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libsambox-java (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libsejda-java (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in fontawesomefx package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-classfilewriter package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libpdfbox2-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libsambox-java package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libsejda-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in openjpa package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in plexus-io package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in shiro package in Ubuntu:
  New
Status in sitemesh package in Ubuntu:
  New
Status in snakeyaml package in Ubunt

[Touch-packages] [Bug 1811471] Re: local resolver stub fails to handle multiple TCP dns queries

It seems this breaks dns lookups on some system, see #1817903

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

Title:
  local resolver stub fails to handle multiple TCP dns queries

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

  The systemd local 'stub' resolver handles all local DNS queries (by
  default configuration used in Ubuntu), and essentially proxies all
  requests to its configured upstream DNS resolvers.

  Most local DNS resolution by applications uses glibc's getaddrinfo()
  function.  This function is configured in various ways by the
  /etc/resolv.conf file, which tells glibc what nameserver/resolver to
  contact as well as how to talk to the name server.

  By default, glibc performs UDP DNS queries, with a single DNS query
  per UDP packet.  The UDP packet size is limited per DNS spec to 512
  bytes.  For some DNS lookups, a 512 byte UDP packet is not large
  enough to contain the entire response - for example, an A record
  lookup with a large number (e.g. 30) of A record addresses.  This
  number of A record entries is possible in some cases of load
  balancing.  When the DNS UDP response size is larger than 512 bytes,
  the server puts as much response as it can into the DNS UDP response,
  and marks the "trunacted" flag.  This lets glibc know that the DNS UDP
  packet did not contain the entire response for all the A records.

  When glibc sees a UDP response that is "trunacted", by default it
  ignores the contents of that response and issues a new DNS query,
  using TCP instead of UDP.  The TCP packet size has a higher size limit
  (though see bug 1804487 which is a bug in systemd's max-sizing of TCP
  DNS packets), and so *should* allow glibc to receive the entire DNS
  response.

  However, glibc issues DNS queries for both A and  records.  When
  it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet
  with a single A query, and one UDP DNS packet with a single 
  query).  When glibc uses TCP, it puts both DNS queries into a single
  TCP DNS packet - the RFC refers to this as "pipelining"
  (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that
  clients SHOULD do this, and that servers MUST expect to receive
  pipelined queries and SHOULD respond to all of them.  (Technically
  pipelining can be separate DNS queries, one per TCP packet, but both
  using the same TCP connection - but the clear intention of pipelining
  is to improve TCP performance, and putting both DNS queries into a
  single TCP packet is clearly more performant than using separate TCP
  packets).

  Unfortunately, systemd's local stub resolver has only very basic
  support for TCP DNS, and it handles TCP DNS queries almost identically
  to UDP DNS queries - it reads the DNS query 2-byte header (containing
  the length of the query data), reads in the single DNS query data,
  performs lookup and sends a response to that DNS query, and closes the
  TCP connection.  It does not check for "pipelined" queries in the TCP
  connection.

  That would be bad enough, as glibc is (rightly) expecting a response
  to both its A and  queries; however what glibc gets is a TCP
  connection-reset error.  That is because the local systemd stub
  resolver has closed its TCP socket while input data was still pending
  (i.e. it never even read the second pipelined DNS query).  When the
  kernel sees unread input bytes in a TCP connection that is closed, it
  sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the
  RST, it dumps all data in its socket buffer and passes the ECONNRESET
  error up to the application.  So glibc gets nothing besides a
  connection reset error.

  Note also that even if the systemd local stub resolver's socket
  flushes its input buffer before closing the TCP connection (which will
  avoid the TCP RST), glibc still expects responses to both its A and
   queries before systemd closes the TCP connection, and so a simple
  change to systemd to flush the input buffer is not enough to fix the
  bug (and would also not actually fix the bug since glibc would never
  get the  response).

  [Test Case]

  This can be reproduced on any system using a local systemd stub
  resolver, when using an application that uses getaddrinfo() - such as
  ssh, telnet, ping, etc - or with a simple C program that uses
  getaddrinfo().  The dns name looked up must have enough A records to
  overflow the 512 byte maximum for a UDP DNS packet; e.g.:

  $ ping testing.irongiantdesign.com
  ping: testing

[Touch-packages] [Bug 1817903] [NEW] systemd-resolve appends "options edns0" to resolv.conf

Public bug reported:

Mint 19 (Ubuntu 18.04)

Following latest mint update done on 24/02/2019, DNS is broken

nslookup and dig of certain domain names work as expected, ping does not
(ip works but not domain name)

After a day of trial and error, testing I found that the problem lies
with the presence of

"options edns0"

in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

With option present many dns lookups fail with both FF and chrome browswers and 
thunderbird...
This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

Deleting the option on live system results in the issue immediately
disappearing, but on reboot it is added back in (by systemd-resolve ?)

I cannot find any option to prevent this being added, so presumably it
is hard-coded in systemd following the update?

systemd:
  Installed: 237-3ubuntu10.13

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

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

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...
  This is on a home network, with router set as dns proxy for external wan, not 
using NetworkManager

  Deleting the option on live system results in the issue immediately
  disappearing, but on reboot it is added back in (by systemd-resolve ?)

  I cannot find any option to prevent this being added, so presumably it
  is hard-coded in systemd following the update?

  systemd:
Installed: 237-3ubuntu10.13

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

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

[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS

** Also affects: jboss-classfilewriter (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  update to openjdk 11 in 18.04 LTS

Status in activemq package in Ubuntu:
  New
Status in batik package in Ubuntu:
  New
Status in bindex package in Ubuntu:
  New
Status in ca-certificates-java package in Ubuntu:
  New
Status in carrotsearch-hppc package in Ubuntu:
  New
Status in commons-httpclient package in Ubuntu:
  New
Status in eclipselink package in Ubuntu:
  New
Status in figtree package in Ubuntu:
  New
Status in gatk-native-bindings package in Ubuntu:
  New
Status in gettext package in Ubuntu:
  New
Status in gkl package in Ubuntu:
  New
Status in gradle package in Ubuntu:
  New
Status in groovy package in Ubuntu:
  New
Status in hsqldb package in Ubuntu:
  New
Status in hsqldb1.8.0 package in Ubuntu:
  New
Status in htsjdk package in Ubuntu:
  New
Status in insubstantial package in Ubuntu:
  New
Status in jabref package in Ubuntu:
  New
Status in jackson-module-jaxb-annotations package in Ubuntu:
  New
Status in jameica package in Ubuntu:
  New
Status in jameica-datasource package in Ubuntu:
  New
Status in jameica-util package in Ubuntu:
  New
Status in jasperreports package in Ubuntu:
  New
Status in java-common package in Ubuntu:
  New
Status in javatools package in Ubuntu:
  New
Status in jaxws-api package in Ubuntu:
  New
Status in jboss-classfilewriter package in Ubuntu:
  New
Status in jboss-jdeparser2 package in Ubuntu:
  New
Status in jboss-modules package in Ubuntu:
  New
Status in jersey1 package in Ubuntu:
  New
Status in jftp package in Ubuntu:
  New
Status in jmdns package in Ubuntu:
  New
Status in jnr-posix package in Ubuntu:
  New
Status in jruby package in Ubuntu:
  New
Status in jruby-openssl package in Ubuntu:
  New
Status in junit4 package in Ubuntu:
  New
Status in jws-api package in Ubuntu:
  New
Status in jython package in Ubuntu:
  New
Status in libbtm-java package in Ubuntu:
  New
Status in libcommons-collections3-java package in Ubuntu:
  New
Status in libcommons-collections4-java package in Ubuntu:
  New
Status in libgpars-groovy-java package in Ubuntu:
  New
Status in libhibernate-validator-java package in Ubuntu:
  New
Status in libjackson-json-java package in Ubuntu:
  New
Status in libjdo-api-java package in Ubuntu:
  New
Status in libjdom1-java package in Ubuntu:
  New
Status in libnetx-java package in Ubuntu:
  New
Status in libquartz-java package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in libreoffice-l10n package in Ubuntu:
  New
Status in libscram-java package in Ubuntu:
  New
Status in libswingx-java package in Ubuntu:
  New
Status in libxml-security-java package in Ubuntu:
  New
Status in libxstream-java package in Ubuntu:
  New
Status in logback package in Ubuntu:
  New
Status in mariadb-connector-java package in Ubuntu:
  New
Status in maven-bundle-plugin package in Ubuntu:
  New
Status in maven-enforcer package in Ubuntu:
  New
Status in maven-javadoc-plugin package in Ubuntu:
  New
Status in maven-jaxb2-plugin package in Ubuntu:
  New
Status in maven-plugin-tools package in Ubuntu:
  New
Status in mckoisqldb package in Ubuntu:
  New
Status in metro-policy package in Ubuntu:
  New
Status in mockito package in Ubuntu:
  New
Status in msv package in Ubuntu:
  New
Status in obantoo package in Ubuntu:
  New
Status in objenesis package in Ubuntu:
  New
Status in octave package in Ubuntu:
  New
Status in openjdk-11-jre-dcevm package in Ubuntu:
  New
Status in openjdk-lts package in Ubuntu:
  New
Status in openjfx package in Ubuntu:
  New
Status in openjpa package in Ubuntu:
  New
Status in orthanc-imagej package in Ubuntu:
  New
Status in pdfsam package in Ubuntu:
  New
Status in procyon package in Ubuntu:
  New
Status in rdp-alignment package in Ubuntu:
  New
Status in rdp-classifier package in Ubuntu:
  New
Status in rdp-readseq package in Ubuntu:
  New
Status in resteasy3.0 package in Ubuntu:
  New
Status in rsyntaxtextarea package in Ubuntu:
  New
Status in saaj package in Ubuntu:
  New
Status in scala package in Ubuntu:
  New
Status in scilab package in Ubuntu:
  New
Status in shiro package in Ubuntu:
  New
Status in sitemesh package in Ubuntu:
  New
Status in snakeyaml package in Ubuntu:
  New
Status in trove3 package in Ubuntu:
  New
Status in uimaj package in Ubuntu:
  New
Status in unsafe-mock package in Ubuntu:
  New
Status in visualvm package in Ubuntu:
  New
Status in writer2latex package in Ubuntu:
  New
Status in xmlbeans package in Ubuntu:
  New
Status in zeroc-ice package in Ubuntu:
  New
Status in clojure1.8 source package in Bionic:
  Fix Committed
Status in dd-plist source package in Bionic:
  Fix Committed
Status in gettext source package in Bionic:
  Fix Committed
Status in gradle source package in Bionic:
  Fix Committed
Status in gr

[Touch-packages] [Bug 1817897] Re: attempting to enable fingerprint with pam-auth-update breaks gdm

Thanks for your bug report, what do you need pam-auth-update? What are
you trying to configure? Enabling log-in with fingerprint shouldn't
requiring having to fiddle with pam tools on a command line if that's
what you are trying to enable

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

Title:
  attempting to enable fingerprint with pam-auth-update breaks gdm

Status in pam package in Ubuntu:
  New

Bug description:
  I ran sudo pam-auth-update, enabled "Fingerprint authentication",
  selected "OK", and then rebooted.

  GDM wouldn't start after the reboot:

  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=121 pid=1551 
comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: Unable to 
register display with display manager

  I logged in on a VT and ran pam-auth-update again. I observed that
  "Register user sessions in the systemd control group" was not
  selected, even though my recollection was that it had been selected
  before I enabled fingerprint authentication, and I didn't disable it.

  I unselected fingerprint authentication and selected "Register user
  sessions in the systemd control group" and rebooted again. GDM started
  working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libpam-runtime 1.3.1-5ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 06:31:32 2019
  InstallationDate: Installed on 2019-02-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago)

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

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

[Touch-packages] [Bug 1817897] Re: attempting to enable fingerprint with pam-auth-update breaks gdm

Actually, it's even weirder than that.

I went through all this several times while trying to narrow down the
repro steps, and it's all very bizarre. Somehow I managed to get gdm
working again, and then in a logged in gdm session, I enabled
fingerprint, and exited from pam-auth-update, then ran pam-auth-update
again and disabled fingerprint and re-enabled register user sessions
which had once again somehow magically gotten disabled, but then I ran
pam-auth-update a third time and register user sessions was STILL
disabled even though I'd just enabled it, and then when I rebooted GDM
wouldn't work again. So at that point I logged in on a VT and ran pam-
auth-update again and selected register user sessions again, and then
just out of curiosity ran pam-auth-update again and this time register
user sessions was still selected, so I exited and rebooted and GDM
worked again.

There is something very bizarre going on here.

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

Title:
  attempting to enable fingerprint with pam-auth-update breaks gdm

Status in pam package in Ubuntu:
  New

Bug description:
  I ran sudo pam-auth-update, enabled "Fingerprint authentication",
  selected "OK", and then rebooted.

  GDM wouldn't start after the reboot:

  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=121 pid=1551 
comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: Unable to 
register display with display manager

  I logged in on a VT and ran pam-auth-update again. I observed that
  "Register user sessions in the systemd control group" was not
  selected, even though my recollection was that it had been selected
  before I enabled fingerprint authentication, and I didn't disable it.

  I unselected fingerprint authentication and selected "Register user
  sessions in the systemd control group" and rebooted again. GDM started
  working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libpam-runtime 1.3.1-5ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 06:31:32 2019
  InstallationDate: Installed on 2019-02-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago)

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

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

[Touch-packages] [Bug 1817897] [NEW] attempting to enable fingerprint with pam-auth-update breaks gdm

Public bug reported:

I ran sudo pam-auth-update, enabled "Fingerprint authentication",
selected "OK", and then rebooted.

GDM wouldn't start after the reboot:

Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=121 pid=1551 
comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: Unable to 
register display with display manager

I logged in on a VT and ran pam-auth-update again. I observed that
"Register user sessions in the systemd control group" was not selected,
even though my recollection was that it had been selected before I
enabled fingerprint authentication, and I didn't disable it.

I unselected fingerprint authentication and selected "Register user
sessions in the systemd control group" and rebooted again. GDM started
working again.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libpam-runtime 1.3.1-5ubuntu1
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 27 06:31:32 2019
InstallationDate: Installed on 2019-02-26 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitecture: all
SourcePackage: pam
UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago)

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


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

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

Title:
  attempting to enable fingerprint with pam-auth-update breaks gdm

Status in pam package in Ubuntu:
  New

Bug description:
  I ran sudo pam-auth-update, enabled "Fingerprint authentication",
  selected "OK", and then rebooted.

  GDM wouldn't start after the reboot:

  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=121 pid=1551 
comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: Unable to 
register display with display manager

  I logged in on a VT and ran pam-auth-update again. I observed that
  "Register user sessions in the systemd control group" was not
  selected, even though my recollection was that it had been selected
  before I enabled fingerprint authentication, and I didn't disable it.

  I unselected fingerprint authentication and selected "Register user
  sessions in the systemd control group" and rebooted again. GDM started
  working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libpam-runtime 1.3.1-5ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 06:31:32 2019
  InstallationDate: Installed on 2019-02-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago)

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

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

[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

** Changed in: hwe-next
   Status: Fix Released => In Progress

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  In Progress
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions

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

[Touch-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change

linux/Cosmic  should be Fix Released as the fix is already in 4.18 from
upstream.

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

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

Title:
  broken touchpad after i2c-i801 blacklist change

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Xenial:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in kmod source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in kmod source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  SRU:
  

  [Impact]
  ThinkPad 11e 2nd/3rd touchpad not working when load i2c-i801.
  PNP LEN0049 will use smbus by default in kernel, but i2c bus is in
  runtime suspend mode in old touchpad fw.
  Then touchpad will not work.
  LEN2040 on 11e 3rd can reproduce this issue by passing
  psmouse.synaptics_intertouch=1

  These 2 pnp device should be the same one Synaptics s3203_ver5.

  [Fix]
  i2c-i801 should auto suspend when not used, no need runtime pm.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Touchpad works fine.

  [Regression Potential]
  Low, upstream fix cherry-picked.

  4.18 kernel patch, no need for cosmic.

  
  Original bug report:
  =
  After upgrading to kmod (24-1ubuntu3.1) the trackpads stop working on Lenovo 
11e 2nd gen machines.

  We have a fleet of approximetly 1000 of them in production running
  ubuntu 18.04. Prior to this update the trackpads worked out of box in
  18.04.

  We are currently working around the issue by deploying our own
  blacklist files.

  Here is a link to the SRU justification: https://bugs.launchpad.net
  /hwe-next/+bug/1786574

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

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

[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist

@midnightflash
Please provide more details on the issues you see so that we can help you. As 
Aaron said, please upload the dmesg from both your X11e and X250.

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

Title:
  remove i2c-i801 from blacklist

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  New
Status in kmod package in Ubuntu:
  In Progress
Status in kmod source package in Xenial:
  In Progress
Status in kmod source package in Bionic:
  In Progress
Status in kmod source package in Cosmic:
  In Progress

Bug description:
  SRU justification
  

  [Impact]
  Many modern notebooks need i2c-i801 kernel module to function, but it is 
blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user 
experience.

  [Test case]
  1. Install Ubuntu
  2. Check touchpad works or not
  3. Install the fixed kmod package
  4. Confirm touchpad works

  [Regression Potential]
  i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq 
nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a 
way to workaround the suspend issue, the proper fix should be in linux kernel. 
Since nc6000 was a machine sold in 2004, it is too difficult to find someone to 
verify if it will regress due to this SRU. The rationale to blacklist it is: 
https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, 
however it is no longer valid nowadays on modern computers.

  Besides, there look like to be a quirk in linux kernel that fixes it:
  https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434

  [Other Info]
  rationale of i2c_i801 driver blacklist: 
https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329

  
---
  Original bug report:

  We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module
  to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu.
  To use the touchpad, users have to remove the i2c-i801 line manually.

  i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000
  (Bug #16602), this module should be removed from blacklist.

  There is also another bug (Bug #1475945) that needs this module for
  Acer trackpad to work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions

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

[Touch-packages] [Bug 1802135] Re: broken touchpad after i2c-i801 blacklist change