[Touch-packages] [Bug 1871154] Re: Error message displayed during boot (mountroot hook, premount)

2020-05-29 Thread Gianfranco Costamagna
Laurent, I uploaded the package in queue for review, and in my ppa
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa

please have a look and report back

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

Title:
  Error message displayed during boot (mountroot hook, premount)

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lvm2 source package in Focal:
  In Progress

Bug description:
  [Impact] 
  * People using lvm2 on ubuntu focal are getting a strange and weird message 
due to a wrong path

  [Test Case]
  * Install lvm2 on Ubuntu 20.04

  [Regression Potential] 
  * Low, the fix is already part of groovy

  [Other info]
  Hi,

  my Ubuntu system uses LVM2 for its root file system.  It boots
  correctly, but an ugly error message is displayed during boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  Uname: Linux 5.6.2-050602-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr  6 17:59:03 2020
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1871154] Re: Error message displayed during boot (mountroot hook, premount)

2020-05-29 Thread Gianfranco Costamagna
** Description changed:

+ [Impact] 
+ * People using lvm2 on ubuntu focal are getting a strange and weird message 
due to a wrong path
+ 
+ [Test Case]
+ * Install lvm2 on Ubuntu 20.04
+ 
+ [Regression Potential] 
+ * Low, the fix is already part of groovy
+ 
+ [Other info]
  Hi,
  
  my Ubuntu system uses LVM2 for its root file system.  It boots
  correctly, but an ugly error message is displayed during boot.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  Uname: Linux 5.6.2-050602-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr  6 17:59:03 2020
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: lvm2 (Ubuntu Focal)
   Status: Confirmed => In Progress

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

Title:
  Error message displayed during boot (mountroot hook, premount)

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lvm2 source package in Focal:
  In Progress

Bug description:
  [Impact] 
  * People using lvm2 on ubuntu focal are getting a strange and weird message 
due to a wrong path

  [Test Case]
  * Install lvm2 on Ubuntu 20.04

  [Regression Potential] 
  * Low, the fix is already part of groovy

  [Other info]
  Hi,

  my Ubuntu system uses LVM2 for its root file system.  It boots
  correctly, but an ugly error message is displayed during boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  Uname: Linux 5.6.2-050602-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr  6 17:59:03 2020
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage

2020-05-29 Thread Gianfranco Costamagna
*** This bug is a duplicate of bug 1871154 ***
https://bugs.launchpad.net/bugs/1871154

** This bug has been marked a duplicate of bug 1871154
   Error message displayed during boot (mountroot hook, premount)

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

Title:
  Definition of add_mountroot_fail_hook doesnt match lvm2's usage

Status in initramfs-tools:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Package lvm2 contains a init-premount script named /usr/share
  /initramfs-tools/scripts/init-premount/lvm2

  In this script there is the function call:
  add_mountroot_fail_hook "20-lvm2"

  Which is defined in /usr/share/initramfs-tools/scripts/functions

  In focal's 0.136ubuntu6 , this is defined as:

  add_mountroot_fail_hook()
  {
  mkdir -p /tmp/mountroot-fail-hooks.d
  ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
  }

  The final line of the function will execute as
  ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"

  And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
  not exist.

  It is clear from lvm2's invocation that it expects the symlink to be
  named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
  the case:

  add_mountroot_fail_hook()
  {
  mkdir -p /tmp/mountroot-fail-hooks.d
  ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
  }

  focal's version needs to be updated to either support the "$1"
  argument or strip the directory from "$0".

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

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


[Touch-packages] [Bug 1871154] Re: Error message displayed during boot (mountroot hook, premount)

2020-05-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Error message displayed during boot (mountroot hook, premount)

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lvm2 source package in Focal:
  In Progress

Bug description:
  [Impact] 
  * People using lvm2 on ubuntu focal are getting a strange and weird message 
due to a wrong path

  [Test Case]
  * Install lvm2 on Ubuntu 20.04

  [Regression Potential] 
  * Low, the fix is already part of groovy

  [Other info]
  Hi,

  my Ubuntu system uses LVM2 for its root file system.  It boots
  correctly, but an ugly error message is displayed during boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  Uname: Linux 5.6.2-050602-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr  6 17:59:03 2020
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1871154] Re: Error message displayed during boot (mountroot hook, premount)

2020-05-29 Thread Gianfranco Costamagna
** Also affects: lvm2 (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  Error message displayed during boot (mountroot hook, premount)

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lvm2 source package in Focal:
  In Progress

Bug description:
  [Impact] 
  * People using lvm2 on ubuntu focal are getting a strange and weird message 
due to a wrong path

  [Test Case]
  * Install lvm2 on Ubuntu 20.04

  [Regression Potential] 
  * Low, the fix is already part of groovy

  [Other info]
  Hi,

  my Ubuntu system uses LVM2 for its root file system.  It boots
  correctly, but an ugly error message is displayed during boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  Uname: Linux 5.6.2-050602-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr  6 17:59:03 2020
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise

2020-05-29 Thread Kai Kasurinen
** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Add trailing dot to make connectivity-check.ubuntu.com. absolute and
  reduce NXDOMAIN warning noise

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

Bug description:
  I normally don't like this, but it's a one-character change so it's
  easier to start with the solution:

  diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf  
  +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  @@ -1,2 +1,2 @@
   [connectivity]
  -uri=http://connectivity-check.ubuntu.com/
  +uri=http://connectivity-check.ubuntu.com./

  Making this name absolute instead of relative avoids spurious
  resolutions of "connectivity-check.ubuntu.com.your_domain." This
  removes a fair amount of NXDOMAIN error noise in journalctl.

  
  Observing the issue and the fix requires 3 terminals:

  1. tcpdump -i any 'port domain'
  2. journalctl --boot -u systemd-resolved -f

  3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe the NXDOMAIN noise over a couple few minutes
   
  Now make the hostname absolute with the trailing dot above and run:
 systemctl reload NetworkManager
  Wait 1 min for things to stabilize. Test again:

  nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1"
   => observe non-zero but significantly reduced NXDOMAIN noise over a couple 
few minutes

  Originally reported at https://askubuntu.com/a/1242611/117217

  Plenty of people annoyed by NXDOMAIN warnings, just Google it.

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

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


[Touch-packages] [Bug 1874953] Re: dpkg: conffile difference visualizer subprocess returned error exit status 127

2020-05-29 Thread Brian Murray
** Tags added: rls-ff-incoming

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

Title:
  dpkg: conffile difference visualizer subprocess returned error exit
  status 127

Status in dpkg package in Ubuntu:
  Triaged
Status in less package in Ubuntu:
  Confirmed
Status in smartmontools package in Ubuntu:
  Invalid
Status in dpkg package in Debian:
  Unknown

Bug description:
  Issue occurred on upgrade from 19.10 to 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: smartmontools 7.1-1build1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 24 21:33:08 2020
  ErrorMessage: conffile difference visualizer subprocess returned error exit 
status 127
  InstallationDate: Installed on 2011-06-18 (3233 days ago)
  InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 
(20110426)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: smartmontools
  Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile 
difference visualizer subprocess returned error exit status 127
  UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago)
  mtime.conffile..etc.default.smartmontools: 2017-12-08T19:12:02.064375
  mtime.conffile..etc.smartd.conf: 2017-12-08T20:27:28.727282

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

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


[Touch-packages] [Bug 1801338] Re: apt fails to properly handle server-side connection closure

2020-05-29 Thread Robert Liu
I met the issue when installing packages from a private PPA of
Launchpad. Hope this would be helpful to reproduce the issue.

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

Title:
  apt fails to properly handle server-side connection closure

Status in apt package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Triaged

Bug description:
  [Impact]
  In some cases, apt does not correctly handle server-side connection closure 
after a pipeline, and aborts the file being downloaded with an "Undetermined 
Error" when the connection has been closed.

  [Test case]
  This could be seen by running apt build-dep evince on cosmic with a recent 
apt with the pipelining fix (such as 1.6.6) against a local mirror running 
apache from trusty. It remains to be seen whether this is easily reproducible 
for anyone.

  [Regression potential]
  N/A yet.

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

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


[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-05-29 Thread Lithi
Yes systemd is now at 245.4-4ubuntu3.1  and the interface does come up
at boot.

Note my config is also now using the macaddress parameter as mentioned
by another commenter above, which may have effected the result.


Thank you very much!

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [test case, pre-focal]

  same netplan as above, but remove ethernets: section.  Reboot, and the
  bridge should have its address and route:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static linkdown 
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4 linkdown 

  
  add and remove carrier, by adding and removing a slave interface:

  ubuntu@test-e:~$ sudo ip l set dev ens3 master br0 up
  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet 192.168.0.4/24 brd 192.168.0.255 scope global br0
 valid_lft forever preferred_lft forever
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever
  ubuntu@test-e:~$ sudo ip l set dev ens3 nomaster

  
  the bridge no longer has its address after losing carrier:

  ubuntu@test-e:~$ ip a show br0
  3: br0:  mtu 1500 qdisc noqueue state DOWN 
group default qlen 1000
  link/ether 56:11:da:23:bb:93 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::5411:daff:fe23:bb93/64 scope link 
 valid_lft forever preferred_lft forever


  [regression potential]

  Any regression would likely involve incorrectly configured network
  after an interface carrier gain/loss.

  [scope]

  This is needed for Focal, Eoan, and Bionic.

  While this only reproduces at boot for Focal, the general loss of
  configuration on carrier loss even when ConfigureWithoutCarrier=true
  is reproducable on all releases except Xenial, which does not have the
  ConfigureWithoutCarrier= parameter.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: 

[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

2020-05-29 Thread Samuel Alves Gonçalves
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547

New Install from netboot method ubuntu 20.04 focal same error, I did
everything, but nothing worked

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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

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


[Touch-packages] [Bug 1881357] [NEW] abstractions/X needs new ICEauthority path

2020-05-29 Thread Daniel Richard G.
Public bug reported:

This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal.

Saw this during a Firefox test run:

May 29 17:25:32 test-ubuntu64 kernel: [  818.399967] audit: type=1400
audit(1590787532.023:69): apparmor="DENIED" operation="open"
profile="firefox" name="/run/user/1000/ICEauthority" pid=1791
comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

This comparison was interesting:

$ ls -l ~/.ICEauthority /run/user/1000/ICEauthority 
-rw--- 1 skunk skunk   0 May 29 17:43 /home/skunk/.ICEauthority
-rw--- 1 skunk skunk 350 May 29 17:43 /run/user/1000/ICEauthority

Is the /run path a new canonical location for the ICEauthority file? The
X abstraction would need to know about it.

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


** Tags: focal

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

Title:
  abstractions/X needs new ICEauthority path

Status in apparmor package in Ubuntu:
  New

Bug description:
  This concerns apparmor 2.13.3-7ubuntu5 in Ubuntu focal.

  Saw this during a Firefox test run:

  May 29 17:25:32 test-ubuntu64 kernel: [  818.399967] audit: type=1400
  audit(1590787532.023:69): apparmor="DENIED" operation="open"
  profile="firefox" name="/run/user/1000/ICEauthority" pid=1791
  comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

  This comparison was interesting:

  $ ls -l ~/.ICEauthority /run/user/1000/ICEauthority 
  -rw--- 1 skunk skunk   0 May 29 17:43 /home/skunk/.ICEauthority
  -rw--- 1 skunk skunk 350 May 29 17:43 /run/user/1000/ICEauthority

  Is the /run path a new canonical location for the ICEauthority file?
  The X abstraction would need to know about it.

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

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


[Touch-packages] [Bug 1881342] Re: Display settings are completely broken in 20.04

2020-05-29 Thread Brian Murray
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Display settings are completely broken in 20.04

Status in xorg package in Ubuntu:
  New

Bug description:
  This is after doing a fresh Ubuntu 20.04 installation, on my machine
  equipped with 3 monitors using an SLI of nvidia GTX 980. My 3 monitors
  are 1 4k monitor in landscape mode, and 2 1080p monitors in portrait
  mode. This used to work properly in Ubuntu 19.10, but is utterly
  broken in 20.04. Portrait mode doesn't work anymore, and scaling
  doesn't work anymore.

  It'd be much easier to show what's going on with a video, so here
  goes: https://youtu.be/OHxKWfSxhsE

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

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


[Touch-packages] [Bug 1881314] Re: libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from ddebs.ubuntu.com for 18.04

2020-05-29 Thread Colin Watson
Looks like ddebs.ubuntu.com's update process got stuck that day due to a
network outage, and never recovered.  I've unstuck it and it should
catch up soon.

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

** Changed in: openssl (Ubuntu)
 Assignee: (unassigned) => Colin Watson (cjwatson)

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

Title:
  libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from
  ddebs.ubuntu.com for 18.04

Status in openssl package in Ubuntu:
  In Progress

Bug description:
  After a recent update:

  $ apt-get install libssl1.1-dbgsym
  The following packages have unmet dependencies:
   libssl1.1-dbgsym : Depends: libssl1.1 (= 1.1.1-1ubuntu2.1~18.04.5) but 
1.1.1-1ubuntu2.1~18.04.6 is to be installed
  E: Unable to correct problems, you have held broken packages.

  The following debug repositories are enabled:

  $ cat /etc/apt/sources.list.d/ddebs.list 
  deb http://ddebs.ubuntu.com bionic main restricted universe multiverse
  deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse

  When manually inspecting the apt repository for `bionic-updates`[1],
  the timestamp is 5/19/2020 (prior to the libssl update on ~5/27), and
  the only libssl1.1-dbgsym entry is:

  Package: libssl1.1-dbgsym
  Package-Type: ddeb
  Architecture: amd64
  Version: 1.1.1-1ubuntu2.1~18.04.5

  Meanwhile, I'm unable to find any policy information online about how
  frequently the ddebs repositories get updated.

  [1] http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-
  amd64/Packages.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libssl1.1 1.1.1-1ubuntu2.1~18.04.6
  Uname: Linux 5.5.17-1rodete4-amd64 x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  Date: Fri May 29 08:47:51 2020
  ProcEnviron:
   LD_LIBRARY_PATH=
   TERM=xterm
   PATH=(custom, user)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1881342] [NEW] Display settings are completely broken in 20.04

2020-05-29 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

This is after doing a fresh Ubuntu 20.04 installation, on my machine
equipped with 3 monitors using an SLI of nvidia GTX 980. My 3 monitors
are 1 4k monitor in landscape mode, and 2 1080p monitors in portrait
mode. This used to work properly in Ubuntu 19.10, but is utterly broken
in 20.04. Portrait mode doesn't work anymore, and scaling doesn't work
anymore.

It'd be much easier to show what's going on with a video, so here goes:
https://youtu.be/OHxKWfSxhsE

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


** Tags: bot-comment
-- 
Display settings are completely broken in 20.04
https://bugs.launchpad.net/bugs/1881342
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1874247] Re: Don't work wired connection regression focal

2020-05-29 Thread Igor Zubarev
Currently works ok. It seems it was Beta bug.

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

Title:
  Don't work wired connection regression focal

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to focal I can't connect to wired network. It was ok in
  19.10 before

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 15:44:52 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.254 dev wlp7s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp7s0 scope link metric 1000 
   192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.67 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1804739] Re: libz.a is not compiled with -fPIC

2020-05-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  libz.a is not compiled with -fPIC

Status in zlib package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: xenial
  Package: zlib1g-dev
  Package version: 1:2.2.8.dfsg-2ubuntu4.1

  libz.a in this package is not compiled with -fPIC.
  So it can't be linked into my shared library.

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

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


[Touch-packages] [Bug 1881199] Re: [SoundCore mini, playback] No sound at all from Rhythmbox

2020-05-29 Thread Albert Cardona
Thank you very much, your suggestion solved the issue: rhythmbox can now
play via bluetooth.

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

Title:
  [SoundCore mini, playback] No sound at all from Rhythmbox

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After connecting via bluetooth the Soundcore Mini, I can get sound to
  play through it just fine from e.g. the Chromium browser, but not from
  Rhythmbox, which instead always plays from the laptop's internal
  speakrs.

  In the bluetooth settings, Soundcore Mini is connected. In the sound
  settings, Soundcore Mini is selected, and the "Test" button opens an
  UI that lets me play test sounds, and it works. And indeed it works
  for e.g. Google Chrome for a youtube video. But Rhythmbox plays
  through the internal speakers no matter what. I've tried restarting
  Rhythmbox, removing the ~/.pulse_secure/pulse/ folder with settings
  and then running "pulseaudio -k", and then restarting Rhythmbox, to no
  avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert120462 F pulseaudio
   /dev/snd/pcmC0D0c:   albert120462 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 28 22:00:38 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-06-24 (1434 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SoundCore mini
  Symptom_DevicesInUse:
   Cannot stat file /proc/43906/fd/6: Permission denied
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  albert120462 F pulseaudio
   /dev/snd/pcmC0D0c:   albert120462 F...m pulseaudio
  Symptom_Type: No sound at all
  Title: [SoundCore mini, playback] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-05-20 (8 days ago)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET40W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 1st
  dmi.product.name: 20FQCTO1WW
  dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st
  dmi.product.version: ThinkPad X1 Yoga 1st
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

2020-05-29 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  libc6-lse lets update-initramfs fail on AWS m6g instances

Status in cloud-images:
  New
Status in btrfs-progs package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in btrfs-progs source package in Focal:
  Invalid
Status in glibc source package in Focal:
  Invalid
Status in initramfs-tools source package in Focal:
  In Progress

Bug description:
  [Impact]

   * update-initramfs -u fails on arm64 m6g instances in AWS

  [Test Case]

   * launch m6g instance in AWS
   * install libc6-lse (if not installed)
   * run $ update-initramfs -u
   * It should suceed

  [Regression Potential]

   * Adding one more path to libgcc_s1 resolution. This will still fail
  if something compiles libc6 for _two_ optimisations like
  /lib/$arch/foo/bar/libpthread.

  [Other Info]

   * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in
  the initrd libgcc_s1 must be copied in too. However the logic to find
  matching libgcc_s1 is broken for optimizied builds of libc6 without
  optimized build of libgcc_s1. I think libpthread should link against
  libgcc_s1 to prevent these issues.

   * Original bug report

  With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse
  lets update-initramfs always fail with the following error:

  ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1.

  ## Steps to reproduce (on AWS)

  ### With focal 20200423 AMI

  1. Find the following AMI and launch on m6g instance family

     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423

  2. Run: sudo apt update && sudo apt install libc6-lse
  3. Try: sudo update-initramfs -u

  ### With focal 20200522 AMI

  1. Find the following AMI and launch on m6g instance family

     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522

  2. Try: sudo update-initramfs -u

  ## Note

  - The entire log of the above steps performed on 20200423 AMI is attached.
  - Latest cloud-image AMI 
"ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes 
libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse 
manually.
  - This doesn't reproduce on EC2 a1.* instance family.

  ## Expected behavior

  Does not fail.

  ## Background to find this bug

  As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get
  upgrade pulls newer package that triggers update-initramfs, apt-get
  upgrade always fail on 20200522 AMI.

  the following is an apport report on 20200423 AMI:

  

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed May 27 09:52:16 2020
  Dependencies:
   gcc-10-base 10-20200411-0ubuntu1
   libc6 2.31-0ubuntu9
   libcrypt1 1:4.4.10-10ubuntu4
   libgcc-s1 10-20200411-0ubuntu1
   libidn2-0 2.2.0-2
   libunistring2 0.9.10-2
  DistroRelease: Ubuntu 20.04
  Ec2AMI: ami-061102f51d47b1c24
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-northeast-1c
  Ec2InstanceType: m6g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: libc6-lse 2.31-0ubuntu9
  PackageArchitecture: arm64
  ProcCpuinfoMinimal:
   processor  : 0
   BogoMIPS   : 243.75
   Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
   CPU implementer: 0x41
   CPU architecture: 8
   CPU variant: 0x3
   CPU part   : 0xd0c
   CPU revision   : 1
  ProcEnviron:
   LANG=C.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30
  SourcePackage: glibc
  Tags:  focal ec2-images
  Uname: Linux 5.4.0-1009-aws aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1880853/+subscriptions

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


[Touch-packages] [Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

2020-05-29 Thread Dimitri John Ledkov
** Description changed:

+ [Impact]
+ 
+  * update-initramfs -u fails on arm64 m6g instances in AWS
+ 
+ [Test Case]
+ 
+  * launch m6g instance in AWS
+  * install libc6-lse (if not installed)
+  * run $ update-initramfs -u
+  * It should suceed
+ 
+ [Regression Potential]
+ 
+  * Adding one more path to libgcc_s1 resolution. This will still fail if
+ something compiles libc6 for _two_ optimisations like
+ /lib/$arch/foo/bar/libpthread.
+ 
+ [Other Info]
+  
+  * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in the 
initrd libgcc_s1 must be copied in too. However the logic to find matching 
libgcc_s1 is broken for optimizied builds of libc6 without optimized build of 
libgcc_s1. I think libpthread should link against libgcc_s1 to prevent these 
issues.
+ 
+  * Original bug report
+ 
  With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse
  lets update-initramfs always fail with the following error:
  
  ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1.
  
  ## Steps to reproduce (on AWS)
  
  ### With focal 20200423 AMI
  
  1. Find the following AMI and launch on m6g instance family
  
-ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423
+    ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423
  
  2. Run: sudo apt update && sudo apt install libc6-lse
  3. Try: sudo update-initramfs -u
  
  ### With focal 20200522 AMI
  
  1. Find the following AMI and launch on m6g instance family
  
-ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522
+    ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522
  
  2. Try: sudo update-initramfs -u
  
  ## Note
  
  - The entire log of the above steps performed on 20200423 AMI is attached.
  - Latest cloud-image AMI 
"ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes 
libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse 
manually.
  - This doesn't reproduce on EC2 a1.* instance family.
  
  ## Expected behavior
  
  Does not fail.
  
  ## Background to find this bug
  
  As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get upgrade
  pulls newer package that triggers update-initramfs, apt-get upgrade
  always fail on 20200522 AMI.
  
- 
  the following is an apport report on 20200423 AMI:
  
  
  
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed May 27 09:52:16 2020
  Dependencies:
-  gcc-10-base 10-20200411-0ubuntu1
-  libc6 2.31-0ubuntu9
-  libcrypt1 1:4.4.10-10ubuntu4
-  libgcc-s1 10-20200411-0ubuntu1
-  libidn2-0 2.2.0-2
-  libunistring2 0.9.10-2
+  gcc-10-base 10-20200411-0ubuntu1
+  libc6 2.31-0ubuntu9
+  libcrypt1 1:4.4.10-10ubuntu4
+  libgcc-s1 10-20200411-0ubuntu1
+  libidn2-0 2.2.0-2
+  libunistring2 0.9.10-2
  DistroRelease: Ubuntu 20.04
  Ec2AMI: ami-061102f51d47b1c24
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-northeast-1c
  Ec2InstanceType: m6g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: libc6-lse 2.31-0ubuntu9
  PackageArchitecture: arm64
  ProcCpuinfoMinimal:
-  processor  : 0
-  BogoMIPS   : 243.75
-  Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
-  CPU implementer: 0x41
-  CPU architecture: 8
-  CPU variant: 0x3
-  CPU part   : 0xd0c
-  CPU revision   : 1
+  processor  : 0
+  BogoMIPS   : 243.75
+  Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
+  CPU implementer: 0x41
+  CPU architecture: 8
+  CPU variant: 0x3
+  CPU part   : 0xd0c
+  CPU revision   : 1
  ProcEnviron:
-  LANG=C.UTF-8
-  TERM=screen-256color
-  PATH=(custom, no user)
-  SHELL=/bin/bash
+  LANG=C.UTF-8
+  TERM=screen-256color
+  PATH=(custom, no user)
+  SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30
  SourcePackage: glibc
  Tags:  focal ec2-images
  Uname: Linux 5.4.0-1009-aws aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  [Impact]
  
-  * update-initramfs -u fails on arm64 m6g instances in AWS
+  * update-initramfs -u fails on arm64 m6g instances in AWS
  
  [Test Case]
  
-  * launch m6g instance in AWS
-  * install libc6-lse (if not installed)
-  * run $ update-initramfs -u
-  * It should suceed
+  * launch m6g instance in AWS
+  * install libc6-lse (if not installed)
+  * run $ update-initramfs -u
+  * It should suceed
  
  [Regression Potential]
  
-  * Adding one more path to libgcc_s1 resolution. This will still fail if
+  * Adding one more path to libgcc_s1 resolution. This will still fail if
  something compiles libc6 for _two_ optimisations like
  /lib/$arch/foo/bar/

[Touch-packages] [Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

2020-05-29 Thread Dimitri John Ledkov
** Changed in: initramfs-tools (Ubuntu Focal)
   Status: New => In Progress

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

Title:
  libc6-lse lets update-initramfs fail on AWS m6g instances

Status in cloud-images:
  New
Status in btrfs-progs package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in btrfs-progs source package in Focal:
  Invalid
Status in glibc source package in Focal:
  Invalid
Status in initramfs-tools source package in Focal:
  In Progress

Bug description:
  [Impact]

   * update-initramfs -u fails on arm64 m6g instances in AWS

  [Test Case]

   * launch m6g instance in AWS
   * install libc6-lse (if not installed)
   * run $ update-initramfs -u
   * It should suceed

  [Regression Potential]

   * Adding one more path to libgcc_s1 resolution. This will still fail
  if something compiles libc6 for _two_ optimisations like
  /lib/$arch/foo/bar/libpthread.

  [Other Info]

   * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in
  the initrd libgcc_s1 must be copied in too. However the logic to find
  matching libgcc_s1 is broken for optimizied builds of libc6 without
  optimized build of libgcc_s1. I think libpthread should link against
  libgcc_s1 to prevent these issues.

   * Original bug report

  With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse
  lets update-initramfs always fail with the following error:

  ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1.

  ## Steps to reproduce (on AWS)

  ### With focal 20200423 AMI

  1. Find the following AMI and launch on m6g instance family

     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423

  2. Run: sudo apt update && sudo apt install libc6-lse
  3. Try: sudo update-initramfs -u

  ### With focal 20200522 AMI

  1. Find the following AMI and launch on m6g instance family

     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522

  2. Try: sudo update-initramfs -u

  ## Note

  - The entire log of the above steps performed on 20200423 AMI is attached.
  - Latest cloud-image AMI 
"ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes 
libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse 
manually.
  - This doesn't reproduce on EC2 a1.* instance family.

  ## Expected behavior

  Does not fail.

  ## Background to find this bug

  As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get
  upgrade pulls newer package that triggers update-initramfs, apt-get
  upgrade always fail on 20200522 AMI.

  the following is an apport report on 20200423 AMI:

  

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed May 27 09:52:16 2020
  Dependencies:
   gcc-10-base 10-20200411-0ubuntu1
   libc6 2.31-0ubuntu9
   libcrypt1 1:4.4.10-10ubuntu4
   libgcc-s1 10-20200411-0ubuntu1
   libidn2-0 2.2.0-2
   libunistring2 0.9.10-2
  DistroRelease: Ubuntu 20.04
  Ec2AMI: ami-061102f51d47b1c24
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-northeast-1c
  Ec2InstanceType: m6g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: libc6-lse 2.31-0ubuntu9
  PackageArchitecture: arm64
  ProcCpuinfoMinimal:
   processor  : 0
   BogoMIPS   : 243.75
   Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
   CPU implementer: 0x41
   CPU architecture: 8
   CPU variant: 0x3
   CPU part   : 0xd0c
   CPU revision   : 1
  ProcEnviron:
   LANG=C.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30
  SourcePackage: glibc
  Tags:  focal ec2-images
  Uname: Linux 5.4.0-1009-aws aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1880853/+subscriptions

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


[Touch-packages] [Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

2020-05-29 Thread Dimitri John Ledkov
** Changed in: btrfs-progs (Ubuntu)
   Status: Triaged => Invalid

** Changed in: btrfs-progs (Ubuntu Focal)
   Status: New => Invalid

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Critical

** Changed in: initramfs-tools (Ubuntu Focal)
   Importance: Undecided => Critical

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

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

** Patch added: "lp1880853.patch"
   
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1880853/+attachment/5378575/+files/lp1880853.patch

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

Title:
  libc6-lse lets update-initramfs fail on AWS m6g instances

Status in cloud-images:
  New
Status in btrfs-progs package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in btrfs-progs source package in Focal:
  Invalid
Status in glibc source package in Focal:
  Invalid
Status in initramfs-tools source package in Focal:
  In Progress

Bug description:
  With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse
  lets update-initramfs always fail with the following error:

  ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1.

  ## Steps to reproduce (on AWS)

  ### With focal 20200423 AMI

  1. Find the following AMI and launch on m6g instance family

 ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423

  2. Run: sudo apt update && sudo apt install libc6-lse
  3. Try: sudo update-initramfs -u

  ### With focal 20200522 AMI

  1. Find the following AMI and launch on m6g instance family

 ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522

  2. Try: sudo update-initramfs -u

  ## Note

  - The entire log of the above steps performed on 20200423 AMI is attached.
  - Latest cloud-image AMI 
"ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes 
libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse 
manually.
  - This doesn't reproduce on EC2 a1.* instance family.

  ## Expected behavior

  Does not fail.

  ## Background to find this bug

  As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get
  upgrade pulls newer package that triggers update-initramfs, apt-get
  upgrade always fail on 20200522 AMI.

  
  the following is an apport report on 20200423 AMI:

  

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed May 27 09:52:16 2020
  Dependencies:
   gcc-10-base 10-20200411-0ubuntu1
   libc6 2.31-0ubuntu9
   libcrypt1 1:4.4.10-10ubuntu4
   libgcc-s1 10-20200411-0ubuntu1
   libidn2-0 2.2.0-2
   libunistring2 0.9.10-2
  DistroRelease: Ubuntu 20.04
  Ec2AMI: ami-061102f51d47b1c24
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-northeast-1c
  Ec2InstanceType: m6g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: libc6-lse 2.31-0ubuntu9
  PackageArchitecture: arm64
  ProcCpuinfoMinimal:
   processor  : 0
   BogoMIPS   : 243.75
   Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
   CPU implementer: 0x41
   CPU architecture: 8
   CPU variant: 0x3
   CPU part   : 0xd0c
   CPU revision   : 1
  ProcEnviron:
   LANG=C.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30
  SourcePackage: glibc
  Tags:  focal ec2-images
  Uname: Linux 5.4.0-1009-aws aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1880853/+subscriptions

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


[Touch-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic

2020-05-29 Thread Vinícius Borriello
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559

Same problem here. A2DP works fine, but HSP/HFP is marked as
unavailable.

$ uname -r
4.19.66-gentoo

$ pulseaudio --version
pulseaudio 13.0

Device 5C:FB:7C:E2:7A:5B (public)
Name: JBL TUNE500BT
Alias: JBL TUNE500BT
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)

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

Title:
  Bluetooth headset HSP/HFP mode not working in Bionic

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is a previous bug with almost the same title, but for Xenial
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I
  have had this issue in Artful, and when commented on the old bug, I
  was asked to raise a new one instead. I waited to see if Bionic fixed
  it for me, but it does not seem to work still. So!

  Steps to reproduce:
  1. enable bluetooth on computer and switch on the headset.
  2. pair and connect the headset
  3. go to settings to switch headset to HSP/HFP mode to enable mic
  4. save and close window.

  Expected behaviour:
  1. mic should be enabled and headset should be usable to attend calls on 
laptop.

  Behaviour in error:
  1. Headset profile switches back to A2DP and mic is not enabled.

  I am using a generic bluetooth headset on a fresh updated Kubuntu
  18.04 bionic with plasma DE.

  Software versions:
  Kernel: 4.15.0-20-generic
  Bluez version: 5.48-0ubuntu3
  pulseaudio: 1:11.1-1ubuntu7
  pulseaudio-module-bluetooth: 1:11.1-1ubuntu7

  
  Additional information:
  Running "pacmd list-cards" says that HSF/HFP is 'not available' on the 
headset:

  Output from Headset section:
  profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, 
available: no)
  off: Off (priority 0, available: yes)
  active profile: 

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

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


[Touch-packages] [Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

2020-05-29 Thread Dimitri John Ledkov
I managed to reproduce this.

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

Title:
  libc6-lse lets update-initramfs fail on AWS m6g instances

Status in cloud-images:
  New
Status in btrfs-progs package in Ubuntu:
  Triaged
Status in glibc package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in btrfs-progs source package in Focal:
  New
Status in glibc source package in Focal:
  New
Status in initramfs-tools source package in Focal:
  New

Bug description:
  With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse
  lets update-initramfs always fail with the following error:

  ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1.

  ## Steps to reproduce (on AWS)

  ### With focal 20200423 AMI

  1. Find the following AMI and launch on m6g instance family

 ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423

  2. Run: sudo apt update && sudo apt install libc6-lse
  3. Try: sudo update-initramfs -u

  ### With focal 20200522 AMI

  1. Find the following AMI and launch on m6g instance family

 ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522

  2. Try: sudo update-initramfs -u

  ## Note

  - The entire log of the above steps performed on 20200423 AMI is attached.
  - Latest cloud-image AMI 
"ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes 
libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse 
manually.
  - This doesn't reproduce on EC2 a1.* instance family.

  ## Expected behavior

  Does not fail.

  ## Background to find this bug

  As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get
  upgrade pulls newer package that triggers update-initramfs, apt-get
  upgrade always fail on 20200522 AMI.

  
  the following is an apport report on 20200423 AMI:

  

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed May 27 09:52:16 2020
  Dependencies:
   gcc-10-base 10-20200411-0ubuntu1
   libc6 2.31-0ubuntu9
   libcrypt1 1:4.4.10-10ubuntu4
   libgcc-s1 10-20200411-0ubuntu1
   libidn2-0 2.2.0-2
   libunistring2 0.9.10-2
  DistroRelease: Ubuntu 20.04
  Ec2AMI: ami-061102f51d47b1c24
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-northeast-1c
  Ec2InstanceType: m6g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: libc6-lse 2.31-0ubuntu9
  PackageArchitecture: arm64
  ProcCpuinfoMinimal:
   processor  : 0
   BogoMIPS   : 243.75
   Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
   CPU implementer: 0x41
   CPU architecture: 8
   CPU variant: 0x3
   CPU part   : 0xd0c
   CPU revision   : 1
  ProcEnviron:
   LANG=C.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30
  SourcePackage: glibc
  Tags:  focal ec2-images
  Uname: Linux 5.4.0-1009-aws aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1880853/+subscriptions

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


[Touch-packages] [Bug 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again

2020-05-29 Thread FelipeAF
bluetoothctl connect is the same that connecting in ubuntu settings?

I tried to connect via terminal, and I had same problem:

*TURN PHONE ON*
bluetoothctl connect 1C:52:16:B6:64:01
Attempting to connect to 1C:52:16:B6:64:01
Failed to connect: org.bluez.Error.Failed

Trying a lot of times, after more than 10 times, it works:

 bluetoothctl connect 1C:52:16:B6:64:01
Attempting to connect to 1C:52:16:B6:64:01
^[[A
[CHG] Device 7C:A6:B4:62:CF:86 RSSI: -90
[CHG] Device 64:32:A8:7D:D7:45 RSSI: -70
[CHG] Device 09:5D:DC:F8:A8:BE RSSI: -72
[CHG] Device 1C:52:16:B6:64:01 RSSI: -51
[CHG] Device 7C:A6:B4:62:CF:86 RSSI: -90
[CHG] Device 3B:F2:81:DB:FB:25 RSSI: -57
[CHG] Device 1C:52:16:B6:64:01 Connected: yes
[CHG] Device E4:7D:BD:56:A8:FD RSSI: -93
[NEW] Device 29:87:FF:B9:CE:42 29-87-FF-B9-CE-42
[CHG] Device 3B:F2:81:DB:FB:25 RSSI: -68
[CHG] Device 3B:F2:81:DB:FB:25 RSSI: -56
[CHG] Device 09:5D:DC:F8:A8:BE RSSI: -71
[CHG] Device 3B:F2:81:DB:FB:25 RSSI: -64
[CHG] Device 09:5D:DC:F8:A8:BE RSSI: -72
[CHG] Device D0:03:DF:52:8A:44 RSSI: -85
[CHG] Device D0:03:DF:52:8A:44 ManufacturerData Key: 0x0075
[CHG] Device D0:03:DF:52:8A:44 ManufacturerData Value:
  42 04 01 01 7e d0 03 df 52 8a 44 d2 03 df 52 8a  B...~...R.D...R.
  43 01 16 ad 09 00 00 00  C...
[CHG] Device D0:03:DF:52:8A:44 ManufacturerData Key: 0x001d
[CHG] Device D0:03:DF:52:8A:44 ManufacturerData Value:
  00 01 4c ..L

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

Title:
  [Redmi AirDots Bluetooth] I need to remove device in settings every
  time i want to connect again

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I can connect to my bluetooth phone only the first time after pair the 
device. It works until disconnecting, (whether by turning off the phone, or 
putting into the case, or disconnecting in ubuntu settings), and then i turn on 
the phone again (or remove from the case), i cannot connect until I manually 
remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. 
  If the Ubuntu/Gnome Settings is opened, i can see the status "connected" 
blinks, and fastly change to "disconnected".

  My bluetooth phone works fine with another devices.
  Ubuntu 20.04 LTS
  Laptop Acer Aspire Nitro 5 (AN515-52-5771).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  felipe 2149 F pulseaudio
   /dev/snd/controlC0:  felipe 2149 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 19 19:10:35 2020
  InstallationDate: Installed on 2020-04-29 (20 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Redmi AirDots_R
  Symptom_Type: None of the above
  Title: [Redmi AirDots_R, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.28
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Freed_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.28
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28:
  dmi.product.family: Nitro 5
  dmi.product.name: Nitro AN515-52
  dmi.product.sku: 
  dmi.product.version: V1.28
  dmi.sys.vendor: Acer

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

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


[Touch-packages] [Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

2020-05-29 Thread Dimitri John Ledkov
** Changed in: btrfs-progs (Ubuntu)
   Status: New => Triaged

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

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

Title:
  libc6-lse lets update-initramfs fail on AWS m6g instances

Status in cloud-images:
  New
Status in btrfs-progs package in Ubuntu:
  Triaged
Status in glibc package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  Triaged
Status in btrfs-progs source package in Focal:
  New
Status in glibc source package in Focal:
  New
Status in initramfs-tools source package in Focal:
  New

Bug description:
  With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse
  lets update-initramfs always fail with the following error:

  ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1.

  ## Steps to reproduce (on AWS)

  ### With focal 20200423 AMI

  1. Find the following AMI and launch on m6g instance family

 ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423

  2. Run: sudo apt update && sudo apt install libc6-lse
  3. Try: sudo update-initramfs -u

  ### With focal 20200522 AMI

  1. Find the following AMI and launch on m6g instance family

 ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522

  2. Try: sudo update-initramfs -u

  ## Note

  - The entire log of the above steps performed on 20200423 AMI is attached.
  - Latest cloud-image AMI 
"ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes 
libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse 
manually.
  - This doesn't reproduce on EC2 a1.* instance family.

  ## Expected behavior

  Does not fail.

  ## Background to find this bug

  As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get
  upgrade pulls newer package that triggers update-initramfs, apt-get
  upgrade always fail on 20200522 AMI.

  
  the following is an apport report on 20200423 AMI:

  

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed May 27 09:52:16 2020
  Dependencies:
   gcc-10-base 10-20200411-0ubuntu1
   libc6 2.31-0ubuntu9
   libcrypt1 1:4.4.10-10ubuntu4
   libgcc-s1 10-20200411-0ubuntu1
   libidn2-0 2.2.0-2
   libunistring2 0.9.10-2
  DistroRelease: Ubuntu 20.04
  Ec2AMI: ami-061102f51d47b1c24
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-northeast-1c
  Ec2InstanceType: m6g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: libc6-lse 2.31-0ubuntu9
  PackageArchitecture: arm64
  ProcCpuinfoMinimal:
   processor  : 0
   BogoMIPS   : 243.75
   Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
   CPU implementer: 0x41
   CPU architecture: 8
   CPU variant: 0x3
   CPU part   : 0xd0c
   CPU revision   : 1
  ProcEnviron:
   LANG=C.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30
  SourcePackage: glibc
  Tags:  focal ec2-images
  Uname: Linux 5.4.0-1009-aws aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1880853/+subscriptions

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


[Touch-packages] [Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

2020-05-29 Thread Dimitri John Ledkov
I'm failing to find a region with spot capacity for m6g instances. Which
region did you launch your instance in such that I can try to reproduce
and fix the issue?

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

Title:
  libc6-lse lets update-initramfs fail on AWS m6g instances

Status in cloud-images:
  New
Status in btrfs-progs package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in btrfs-progs source package in Focal:
  New
Status in glibc source package in Focal:
  New
Status in initramfs-tools source package in Focal:
  New

Bug description:
  With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse
  lets update-initramfs always fail with the following error:

  ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1.

  ## Steps to reproduce (on AWS)

  ### With focal 20200423 AMI

  1. Find the following AMI and launch on m6g instance family

 ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423

  2. Run: sudo apt update && sudo apt install libc6-lse
  3. Try: sudo update-initramfs -u

  ### With focal 20200522 AMI

  1. Find the following AMI and launch on m6g instance family

 ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522

  2. Try: sudo update-initramfs -u

  ## Note

  - The entire log of the above steps performed on 20200423 AMI is attached.
  - Latest cloud-image AMI 
"ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes 
libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse 
manually.
  - This doesn't reproduce on EC2 a1.* instance family.

  ## Expected behavior

  Does not fail.

  ## Background to find this bug

  As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get
  upgrade pulls newer package that triggers update-initramfs, apt-get
  upgrade always fail on 20200522 AMI.

  
  the following is an apport report on 20200423 AMI:

  

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed May 27 09:52:16 2020
  Dependencies:
   gcc-10-base 10-20200411-0ubuntu1
   libc6 2.31-0ubuntu9
   libcrypt1 1:4.4.10-10ubuntu4
   libgcc-s1 10-20200411-0ubuntu1
   libidn2-0 2.2.0-2
   libunistring2 0.9.10-2
  DistroRelease: Ubuntu 20.04
  Ec2AMI: ami-061102f51d47b1c24
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-northeast-1c
  Ec2InstanceType: m6g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: libc6-lse 2.31-0ubuntu9
  PackageArchitecture: arm64
  ProcCpuinfoMinimal:
   processor  : 0
   BogoMIPS   : 243.75
   Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
   CPU implementer: 0x41
   CPU architecture: 8
   CPU variant: 0x3
   CPU part   : 0xd0c
   CPU revision   : 1
  ProcEnviron:
   LANG=C.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30
  SourcePackage: glibc
  Tags:  focal ec2-images
  Uname: Linux 5.4.0-1009-aws aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1880853/+subscriptions

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


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

2020-05-29 Thread bugproxy
--- Comment From z...@us.ibm.com 2020-05-29 12:54 EDT---
>From the link:
https://launchpad.net/ubuntu/+source/iproute2
For Ubuntu Bionic release, the latest supported version is  
4.18.0-1ubuntu2~ubuntu18.04.1.

The iproute2 5.x versions are supported in other releases (Eoan, Focal).

Genesis OS is based on Bionic kernel (18.04.1).

Question: How can Bionic based kernel get the iproute2 version v4.19.0
or later?

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

Title:
  tc filter show tcp_flags wrong mask value

Status in The Ubuntu-power-systems project:
  Triaged
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

   
  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r
   
  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 22   /* <--- Wrong */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen
   
  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r
   
  After that, using "tc filter show dev p0v2_r root" to verify, we still see 
the same output (tcp_flags 22) as shown in 2) above, which is wrong.
   
  Userspace tool common name: tc 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = "\n";" in 
lib/utils.c to be used by 2nd patch */
   
  patch 2:
  commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc
  Author: Keara Leibovitz 
  Date:   Thu Jul 26 09:45:30 2018 -0400
  tc: fix bugs for tcp_flags and ip_attr hex output
  Fix hex output for both the ip_attr and tcp_flags print functions.
   
  With the above 2 patches pull in, the new "tc" utility will show the correct 
tcp_flags mask:
  # tc filter show dev p0v2 root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 0x2/7   /* <--- Correct */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  
  This bug affects tc in Ubuntu 18.04.1 stock image.

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

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


[Touch-packages] [Bug 1881154] Re: xorg crashes with segmentation fault on login; resolved by uninstalling libnvidia-common-440

2020-05-29 Thread Brian Murray
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  xorg crashes with segmentation fault on login; resolved by
  uninstalling libnvidia-common-440

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg.log.0 output:

  
  [   410.800] (--) Log file renamed from "/var/log/Xorg.pid-3446.log" to 
"/var/log/Xorg.0.log"
  [   410.801] 
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [   410.801] X Protocol Version 11, Revision 0
  [   410.801] Build Operating System: Linux 4.4.0-168-generic x86_64 Ubuntu
  [   410.801] Current Operating System: Linux tarmstrong-Precision-7540 
4.15.0-1081-oem #91-Ubuntu SMP Fri May 1 02:03:58 UTC 2020 x86_64
  [   410.801] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=3a3585a1-8378-42d5-a146-bce23c579d8b ro mem_sleep_default=deep 
amdgpu.runpm=0 quiet splash vt.handoff=1
  [   410.801] Build Date: 14 November 2019  06:20:00PM
  [   410.801] xorg-server 2:1.19.6-1ubuntu4.4 (For technical support please 
see http://www.ubuntu.com/support) 
  [   410.801] Current version of pixman: 0.34.0
  [   410.801]  Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  [   410.801] Markers: (--) probed, (**) from config file, (==) default 
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [   410.801] (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 28 09:12:58 
2020
  [   410.801] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [   410.801] (==) No Layout section.  Using the first Screen section.
  [   410.801] (==) No screen section available. Using defaults.
  [   410.801] (**) |-->Screen "Default Screen Section" (0)
  [   410.801] (**) |   |-->Monitor ""
  [   410.801] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
  [   410.801] (==) Automatically adding devices
  [   410.801] (==) Automatically enabling devices
  [   410.801] (==) Automatically adding GPU devices
  [   410.801] (==) Automatically binding GPU devices
  [   410.801] (==) Max clients allowed: 256, resource mask: 0x1f
  [   410.801] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.
  [   410.801]  Entry deleted from font path.
  [   410.801] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
  [   410.801]  Entry deleted from font path.
  [   410.801] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
  [   410.801]  Entry deleted from font path.
  [   410.801] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
  [   410.801]  Entry deleted from font path.
  [   410.801] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
  [   410.801]  Entry deleted from font path.
  [   410.801] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
  [   410.801] (==) ModulePath set to "/usr/lib/xorg/modules"
  [   410.801] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
  [   410.801] (II) Loader magic: 0x555c85989020
  [   410.801] (II) Module ABI versions:
  [   410.801]  X.Org ANSI C Emulation: 0.4
  [   410.801]  X.Org Video Driver: 23.0
  [   410.801]  X.Org XInput driver : 24.1
  [   410.801]  X.Org Server Extension : 10.0
  [   410.802] (++) using VT number 2

  [   410.803] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_312
  [   410.804] (II) xfree86: Adding drm device (/dev/dri/card0)
  [   410.804] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 
paused 0
  [   410.804] (II) xfree86: Adding drm device (/dev/dri/card1)
  [   410.805] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 13 
paused 0
  [   410.806] (**) OutputClass "nvidia" ModulePath extended to 
"/usr/lib/x86_64-linux-gnu/nvidia-430/xorg,/usr/lib/xorg/modules"
  [   410.806] (**) OutputClass "Nvidia Prime" ModulePath extended to 
"/x86_64-linux-gnu/nvidia/xorg,/usr/lib/x86_64-linux-gnu/nvidia-430/xorg,/usr/lib/xorg/modules"
  [   410.806] (**) OutputClass "Nvidia Prime" setting /dev/dri/card0 as 
PrimaryGPU
  [   410.807] (--) PCI: (0:0:2:0) 8086:3e9b:1028:0926 rev 0, Mem @ 
0xb300/16777216, 0x6000/268435456, I/O @ 0x4000/64, BIOS @ 
0x/131072
  [   410.807] (--) PCI:*(0:1:0:0) 10de:1fb9:1028:0926 rev 161, Mem @ 
0xb400/16777216, 0x7000/268435456, 0x8000/33554432, I/O @ 
0x3000/128, BIOS @ 0x/524288
  [   410.807] (II) LoadModule: "glx"
  [   410.807] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
  [   410.808] (II) Module glx: vendor="X.Org Foundation"
  [   410.808]  compiled 

[Touch-packages] [Bug 1881154] [NEW] xorg crashes with segmentation fault on login; resolved by uninstalling libnvidia-common-440

2020-05-29 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Xorg.log.0 output:


[   410.800] (--) Log file renamed from "/var/log/Xorg.pid-3446.log" to 
"/var/log/Xorg.0.log"
[   410.801] 
X.Org X Server 1.19.6
Release Date: 2017-12-20
[   410.801] X Protocol Version 11, Revision 0
[   410.801] Build Operating System: Linux 4.4.0-168-generic x86_64 Ubuntu
[   410.801] Current Operating System: Linux tarmstrong-Precision-7540 
4.15.0-1081-oem #91-Ubuntu SMP Fri May 1 02:03:58 UTC 2020 x86_64
[   410.801] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1081-oem 
root=UUID=3a3585a1-8378-42d5-a146-bce23c579d8b ro mem_sleep_default=deep 
amdgpu.runpm=0 quiet splash vt.handoff=1
[   410.801] Build Date: 14 November 2019  06:20:00PM
[   410.801] xorg-server 2:1.19.6-1ubuntu4.4 (For technical support please see 
http://www.ubuntu.com/support) 
[   410.801] Current version of pixman: 0.34.0
[   410.801]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   410.801] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   410.801] (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 28 09:12:58 
2020
[   410.801] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   410.801] (==) No Layout section.  Using the first Screen section.
[   410.801] (==) No screen section available. Using defaults.
[   410.801] (**) |-->Screen "Default Screen Section" (0)
[   410.801] (**) |   |-->Monitor ""
[   410.801] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   410.801] (==) Automatically adding devices
[   410.801] (==) Automatically enabling devices
[   410.801] (==) Automatically adding GPU devices
[   410.801] (==) Automatically binding GPU devices
[   410.801] (==) Max clients allowed: 256, resource mask: 0x1f
[   410.801] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   410.801]Entry deleted from font path.
[   410.801] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[   410.801]Entry deleted from font path.
[   410.801] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[   410.801]Entry deleted from font path.
[   410.801] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[   410.801]Entry deleted from font path.
[   410.801] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[   410.801]Entry deleted from font path.
[   410.801] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
[   410.801] (==) ModulePath set to "/usr/lib/xorg/modules"
[   410.801] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[   410.801] (II) Loader magic: 0x555c85989020
[   410.801] (II) Module ABI versions:
[   410.801]X.Org ANSI C Emulation: 0.4
[   410.801]X.Org Video Driver: 23.0
[   410.801]X.Org XInput driver : 24.1
[   410.801]X.Org Server Extension : 10.0
[   410.802] (++) using VT number 2

[   410.803] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_312
[   410.804] (II) xfree86: Adding drm device (/dev/dri/card0)
[   410.804] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0
[   410.804] (II) xfree86: Adding drm device (/dev/dri/card1)
[   410.805] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 13 paused 0
[   410.806] (**) OutputClass "nvidia" ModulePath extended to 
"/usr/lib/x86_64-linux-gnu/nvidia-430/xorg,/usr/lib/xorg/modules"
[   410.806] (**) OutputClass "Nvidia Prime" ModulePath extended to 
"/x86_64-linux-gnu/nvidia/xorg,/usr/lib/x86_64-linux-gnu/nvidia-430/xorg,/usr/lib/xorg/modules"
[   410.806] (**) OutputClass "Nvidia Prime" setting /dev/dri/card0 as 
PrimaryGPU
[   410.807] (--) PCI: (0:0:2:0) 8086:3e9b:1028:0926 rev 0, Mem @ 
0xb300/16777216, 0x6000/268435456, I/O @ 0x4000/64, BIOS @ 
0x/131072
[   410.807] (--) PCI:*(0:1:0:0) 10de:1fb9:1028:0926 rev 161, Mem @ 
0xb400/16777216, 0x7000/268435456, 0x8000/33554432, I/O @ 
0x3000/128, BIOS @ 0x/524288
[   410.807] (II) LoadModule: "glx"
[   410.807] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   410.808] (II) Module glx: vendor="X.Org Foundation"
[   410.808]compiled for 1.19.6, module version = 1.0.0
[   410.808]ABI class: X.Org Server Extension, version 10.0
[   410.808] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[   410.808]loading driver: nvidia
[   410.808] (II) Applying OutputClass "Nvidia Prime" to /dev/dri/card0
[   410.808]loading driver: nvidia
[   410.808] (==) Matched nvidia as autoconfigured driver 0
[   410.808] (==) Matched nvidia as autoconfigured driver 1
[   410.808

[Touch-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value

2020-05-29 Thread Andrew Cloke
** Changed in: ubuntu-power-systems
   Status: New => Triaged

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

Title:
  tc filter show tcp_flags wrong mask value

Status in The Ubuntu-power-systems project:
  Triaged
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

   
  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r
   
  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 22   /* <--- Wrong */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen
   
  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r
   
  After that, using "tc filter show dev p0v2_r root" to verify, we still see 
the same output (tcp_flags 22) as shown in 2) above, which is wrong.
   
  Userspace tool common name: tc 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = "\n";" in 
lib/utils.c to be used by 2nd patch */
   
  patch 2:
  commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc
  Author: Keara Leibovitz 
  Date:   Thu Jul 26 09:45:30 2018 -0400
  tc: fix bugs for tcp_flags and ip_attr hex output
  Fix hex output for both the ip_attr and tcp_flags print functions.
   
  With the above 2 patches pull in, the new "tc" utility will show the correct 
tcp_flags mask:
  # tc filter show dev p0v2 root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 0x2/7   /* <--- Correct */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  
  This bug affects tc in Ubuntu 18.04.1 stock image.

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

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


[Touch-packages] [Bug 1877176] Re: 64-char hostname causes dhcp server to reject lease

2020-05-29 Thread Dan Streetman
** Description changed:

  [impact]
  
  a systemd with a 64-character hostname (the maximum hostname length for
  Linux) will cause a dhcp server to reject its dhcp lease due to passing
  the invalid hostname in the dhcp lease request.
  
  [test case]
  
  $ cat /etc/systemd/network/10-ens3.network
  [Match]
  Name=ens3
  
  [Network]
  DHCP=yes
  
- 
  set hostname to 64-char name, e.g.:
  
  $ sudo hostnamectl set-hostname
  a123456789b123456789c123456789d123456789e123456789f123456789g123
  
  restart networkd:
  
  $ sudo systemctl restart systemd-networkd
  
  check logs:
  
  root@a123456789b123456789c123456789d123456789e123456789f123456789g123:~# 
journalctl -b -u systemd-networkd --no-pager | grep 'DHCP error'
  May 06 19:01:30 
a123456789b123456789c123456789d123456789e123456789f123456789g123 
systemd-networkd[737]: ens3: DHCP error: Client failed: Invalid argument
  
+ [regression potential]
+ 
+ Any regression would likely result in failure configuring/processing
+ dhcpv4 server response, or rejection from the dhcpv4 server.
+ 
  [scope]
  
  this is fixed by commit 9740eae694e93b06658ff3b3045b22b591561e7c which
  is included in Bionic and later.  This is needed only for Xenial.
  
  [other info]
  
  this is a follow on to bug 1862232, which corrected sd-dhcp-client.c to
  continue networkd dhcp even if the hostname is invalid, however the
  older code in Xenial doesn't correctly detect the invalid hostname, so
  this additional patch is needed.

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

Title:
  64-char hostname causes dhcp server to reject lease

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress

Bug description:
  [impact]

  a systemd with a 64-character hostname (the maximum hostname length
  for Linux) will cause a dhcp server to reject its dhcp lease due to
  passing the invalid hostname in the dhcp lease request.

  [test case]

  $ cat /etc/systemd/network/10-ens3.network
  [Match]
  Name=ens3

  [Network]
  DHCP=yes

  set hostname to 64-char name, e.g.:

  $ sudo hostnamectl set-hostname
  a123456789b123456789c123456789d123456789e123456789f123456789g123

  restart networkd:

  $ sudo systemctl restart systemd-networkd

  check logs:

  root@a123456789b123456789c123456789d123456789e123456789f123456789g123:~# 
journalctl -b -u systemd-networkd --no-pager | grep 'DHCP error'
  May 06 19:01:30 
a123456789b123456789c123456789d123456789e123456789f123456789g123 
systemd-networkd[737]: ens3: DHCP error: Client failed: Invalid argument

  [regression potential]

  Any regression would likely result in failure configuring/processing
  dhcpv4 server response, or rejection from the dhcpv4 server.

  [scope]

  this is fixed by commit 9740eae694e93b06658ff3b3045b22b591561e7c which
  is included in Bionic and later.  This is needed only for Xenial.

  [other info]

  this is a follow on to bug 1862232, which corrected sd-dhcp-client.c
  to continue networkd dhcp even if the hostname is invalid, however the
  older code in Xenial doesn't correctly detect the invalid hostname, so
  this additional patch is needed.

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

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


[Touch-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value

2020-05-29 Thread Frank Heimes
The Lauchpad package site for iproute2 is this one:
https://launchpad.net/ubuntu/+source/iproute2

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

Title:
  tc filter show tcp_flags wrong mask value

Status in The Ubuntu-power-systems project:
  New
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

   
  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r
   
  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 22   /* <--- Wrong */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen
   
  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r
   
  After that, using "tc filter show dev p0v2_r root" to verify, we still see 
the same output (tcp_flags 22) as shown in 2) above, which is wrong.
   
  Userspace tool common name: tc 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = "\n";" in 
lib/utils.c to be used by 2nd patch */
   
  patch 2:
  commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc
  Author: Keara Leibovitz 
  Date:   Thu Jul 26 09:45:30 2018 -0400
  tc: fix bugs for tcp_flags and ip_attr hex output
  Fix hex output for both the ip_attr and tcp_flags print functions.
   
  With the above 2 patches pull in, the new "tc" utility will show the correct 
tcp_flags mask:
  # tc filter show dev p0v2 root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 0x2/7   /* <--- Correct */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  
  This bug affects tc in Ubuntu 18.04.1 stock image.

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

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


[Touch-packages] [Bug 1881312] Re: systemd-run does not make the new scope unit part of the slice specified via the --slice arg

2020-05-29 Thread Dan Streetman
** Description changed:

  [impact]
  
  running 'systemd-run --scope --slice=$SLICE $PROGRAM' does not start the
  program under $SLICE, instead it starts it under system.slice
  
  [test case]
  
  root:~# systemd-run --scope --slice=user-1000.slice sleep 1000
  Running scope as unit run-r16d872f1b0894b88a79421a890269e6c.scope.
  ^Z
  [3]+  Stopped systemd-run --scope --slice=user-1000.slice 
sleep 1000
  root:~# bg
  [3]+ systemd-run --scope --slice=user-1000.slice sleep 1000 &
  root:~# systemctl show -p Slice run-r16d872f1b0894b88a79421a890269e6c.scope
  Slice=system.slice
  
  [regression potential]
  
- TBD
+ This defers running the manager unit load queue when setting the slice
+ for a transient unit, as well as actually passing the slice parameter
+ over the bus when using --scope, so any regression would very likely
+ involve incorrectly setting the slice for a scope and/or problems when
+ processing transient units that specify a slice.
  
  [scope]
  
  this is needed only for Xenial.
  
  this is fixed upstream by
  https://github.com/systemd/systemd/pull/3094
  which is included starting in v230, so is included in Bionic and later.

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

Title:
  systemd-run does not make the new scope unit part of the slice
  specified via the --slice arg

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress

Bug description:
  [impact]

  running 'systemd-run --scope --slice=$SLICE $PROGRAM' does not start
  the program under $SLICE, instead it starts it under system.slice

  [test case]

  root:~# systemd-run --scope --slice=user-1000.slice sleep 1000
  Running scope as unit run-r16d872f1b0894b88a79421a890269e6c.scope.
  ^Z
  [3]+  Stopped systemd-run --scope --slice=user-1000.slice 
sleep 1000
  root:~# bg
  [3]+ systemd-run --scope --slice=user-1000.slice sleep 1000 &
  root:~# systemctl show -p Slice run-r16d872f1b0894b88a79421a890269e6c.scope
  Slice=system.slice

  [regression potential]

  This defers running the manager unit load queue when setting the slice
  for a transient unit, as well as actually passing the slice parameter
  over the bus when using --scope, so any regression would very likely
  involve incorrectly setting the slice for a scope and/or problems when
  processing transient units that specify a slice.

  [scope]

  this is needed only for Xenial.

  this is fixed upstream by
  https://github.com/systemd/systemd/pull/3094
  which is included starting in v230, so is included in Bionic and later.

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

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


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

2020-05-29 Thread bugproxy
--- Comment From z...@us.ibm.com 2020-05-29 11:58 EDT---
(In reply to comment #8)
> Both fixes are in v4.19.0 and later

Do you know the link of Ubuntu that we can get iproute2 v4.19.0 or later
version?

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

Title:
  tc filter show tcp_flags wrong mask value

Status in The Ubuntu-power-systems project:
  New
Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Triaged

Bug description:
  ---Problem Description---
  Problem Descriptions
  "tc" utility does not show correct TC rule's tcp_flags mask correctly in 
current "iproute2" package shipped on Genesis.
  # dpkg -l |grep iproute2
  ii  iproute2  4.15.0-2ubuntu1  ppc64el  networking and traffic control 
tools

   
  ---Steps to Reproduce---
   Steps to reproduce the problem:
  1) Add a tc rule to the testing VF (i.e. p0v2_r):
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2  
skip_sw action mirred egress redirect dev p0v0_r
   
  2) Validate the added TC rule:
  # tc filter show dev p0v2_r root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 22   /* <--- Wrong */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen
   
  3) If we add the tcp_flags using explicit mask 0x7:
  # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1  
flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 
 skip_sw action mirred egress redirect dev p0v0_r
   
  After that, using "tc filter show dev p0v2_r root" to verify, we still see 
the same output (tcp_flags 22) as shown in 2) above, which is wrong.
   
  Userspace tool common name: tc 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace package: iproute2

  ==
  Fixes:
  There are 2 patches to fix the issue:
  patch 1:
  commit b85076cd74e77538918d35992b1a9cd17ff86af8
  Author: Stephen Hemminger 
  Date:   Tue Sep 11 08:29:33 2018 -0700
  lib: introduce print_nl
  Common pattern in iproute commands is to print a line seperator
  in non-json mode. Make that a simple function.
  /* This patch declares global variable "const char *_SL_ = "\n";" in 
lib/utils.c to be used by 2nd patch */
   
  patch 2:
  commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc
  Author: Keara Leibovitz 
  Date:   Thu Jul 26 09:45:30 2018 -0400
  tc: fix bugs for tcp_flags and ip_attr hex output
  Fix hex output for both the ip_attr and tcp_flags print functions.
   
  With the above 2 patches pull in, the new "tc" utility will show the correct 
tcp_flags mask:
  # tc filter show dev p0v2 root
  filter protocol ip pref 5 flower chain 1
  filter protocol ip pref 5 flower chain 1 handle 0x1
src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff
eth_type ipv4
ip_proto tcp
tcp_flags 0x2/7   /* <--- Correct */
skip_sw
in_hw
  action order 1: mirred (Egress Redirect to device p0v0_r) stolen

  
  This bug affects tc in Ubuntu 18.04.1 stock image.

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

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


[Touch-packages] [Bug 1881314] [NEW] libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from ddebs.ubuntu.com for 18.04

2020-05-29 Thread Gabriel M. Beddingfield
Public bug reported:

After a recent update:

$ apt-get install libssl1.1-dbgsym
The following packages have unmet dependencies:
 libssl1.1-dbgsym : Depends: libssl1.1 (= 1.1.1-1ubuntu2.1~18.04.5) but 
1.1.1-1ubuntu2.1~18.04.6 is to be installed
E: Unable to correct problems, you have held broken packages.

The following debug repositories are enabled:

$ cat /etc/apt/sources.list.d/ddebs.list 
deb http://ddebs.ubuntu.com bionic main restricted universe multiverse
deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse

When manually inspecting the apt repository for `bionic-updates`[1], the
timestamp is 5/19/2020 (prior to the libssl update on ~5/27), and the
only libssl1.1-dbgsym entry is:

Package: libssl1.1-dbgsym
Package-Type: ddeb
Architecture: amd64
Version: 1.1.1-1ubuntu2.1~18.04.5

Meanwhile, I'm unable to find any policy information online about how
frequently the ddebs repositories get updated.

[1] http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-
amd64/Packages.gz

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libssl1.1 1.1.1-1ubuntu2.1~18.04.6
Uname: Linux 5.5.17-1rodete4-amd64 x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
Date: Fri May 29 08:47:51 2020
ProcEnviron:
 LD_LIBRARY_PATH=
 TERM=xterm
 PATH=(custom, user)
SourcePackage: openssl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  libssl1.1-dbgsym 1.1.1-1ubuntu2.1~18.04.6 missing from
  ddebs.ubuntu.com for 18.04

Status in openssl package in Ubuntu:
  New

Bug description:
  After a recent update:

  $ apt-get install libssl1.1-dbgsym
  The following packages have unmet dependencies:
   libssl1.1-dbgsym : Depends: libssl1.1 (= 1.1.1-1ubuntu2.1~18.04.5) but 
1.1.1-1ubuntu2.1~18.04.6 is to be installed
  E: Unable to correct problems, you have held broken packages.

  The following debug repositories are enabled:

  $ cat /etc/apt/sources.list.d/ddebs.list 
  deb http://ddebs.ubuntu.com bionic main restricted universe multiverse
  deb http://ddebs.ubuntu.com bionic-updates main restricted universe multiverse

  When manually inspecting the apt repository for `bionic-updates`[1],
  the timestamp is 5/19/2020 (prior to the libssl update on ~5/27), and
  the only libssl1.1-dbgsym entry is:

  Package: libssl1.1-dbgsym
  Package-Type: ddeb
  Architecture: amd64
  Version: 1.1.1-1ubuntu2.1~18.04.5

  Meanwhile, I'm unable to find any policy information online about how
  frequently the ddebs repositories get updated.

  [1] http://ddebs.ubuntu.com/dists/bionic-updates/main/binary-
  amd64/Packages.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libssl1.1 1.1.1-1ubuntu2.1~18.04.6
  Uname: Linux 5.5.17-1rodete4-amd64 x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  Date: Fri May 29 08:47:51 2020
  ProcEnviron:
   LD_LIBRARY_PATH=
   TERM=xterm
   PATH=(custom, user)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1881312] [NEW] systemd-run does not make the new scope unit part of the slice specified via the --slice arg

2020-05-29 Thread Dan Streetman
Public bug reported:

[impact]

running 'systemd-run --scope --slice=$SLICE $PROGRAM' does not start the
program under $SLICE, instead it starts it under system.slice

[test case]

root:~# systemd-run --scope --slice=user-1000.slice sleep 1000
Running scope as unit run-r16d872f1b0894b88a79421a890269e6c.scope.
^Z
[3]+  Stopped systemd-run --scope --slice=user-1000.slice sleep 
1000
root:~# bg
[3]+ systemd-run --scope --slice=user-1000.slice sleep 1000 &
root:~# systemctl show -p Slice run-r16d872f1b0894b88a79421a890269e6c.scope
Slice=system.slice

[regression potential]

TBD

[scope]

this is needed only for Xenial.

this is fixed upstream by
https://github.com/systemd/systemd/pull/3094
which is included starting in v230, so is included in Bionic and later.

** Affects: systemd
 Importance: Unknown
 Status: Unknown

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: systemd (Ubuntu Xenial)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

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

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

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

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

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

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

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

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

Title:
  systemd-run does not make the new scope unit part of the slice
  specified via the --slice arg

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress

Bug description:
  [impact]

  running 'systemd-run --scope --slice=$SLICE $PROGRAM' does not start
  the program under $SLICE, instead it starts it under system.slice

  [test case]

  root:~# systemd-run --scope --slice=user-1000.slice sleep 1000
  Running scope as unit run-r16d872f1b0894b88a79421a890269e6c.scope.
  ^Z
  [3]+  Stopped systemd-run --scope --slice=user-1000.slice 
sleep 1000
  root:~# bg
  [3]+ systemd-run --scope --slice=user-1000.slice sleep 1000 &
  root:~# systemctl show -p Slice run-r16d872f1b0894b88a79421a890269e6c.scope
  Slice=system.slice

  [regression potential]

  TBD

  [scope]

  this is needed only for Xenial.

  this is fixed upstream by
  https://github.com/systemd/systemd/pull/3094
  which is included starting in v230, so is included in Bionic and later.

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

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


[Touch-packages] [Bug 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify

2020-05-29 Thread Paride Legovini
Thanks for verifying. The patch will be applied to the OpenSSH version
already in Focal, so OpenSSH will stay at version 8.2 in Focal.

Christian set up the PPA specifically for testing the patched package,
it's not meant for production use. It's unlikely that you'll hit any
surprise by using it, but it's entirely up to you. The patched package
meant for production will eventually land in focal-updates.

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

Title:
  Port parameter sshd_config is 22 AND whatever you specify

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Focal:
  Triaged

Bug description:
  On my Ubuntu Server 20.04 LTS with OpenSSH 1:8.2p1-4, I have TWO sshd
  deamons. One (on port 22) is for internal use, accepts passwords etc.
  The second (on port 7722) does not allow PAM use and no passwords,
  allows only one user(name) and uses an alternative autorized_keys file
  (that only root can edit).

  Any parameter FIRST encountered in sshd_config is the one that is
  accepted; others do not override (like in many other config files).
  There is one exception: 'Port', which is accumulative. To make life
  easier, I set the more restrictive parameters for port 7722 first and
  next include the system-default /etc/ssh/sshd_config.

  The /etc/ssh/sshd_config file(s) in Ubuntu Server 20.04 DO NOT specify
  'Port' anywhere - the default is 22. But: it is obviously still
  accumulative: Setting 'Port' to 7722 makes sshd listen on port 7722
  AND 22. This is unwanted.

  Proposed solution: Remove the accumulative behavior for 'Port' and
  REQUIRE the 'Port' parameter like before (and maybe have second and
  later parameters override the earlier ones, like 'everyone else').

  Regards,

  Adriaan

  PS Searching for solutions, I found that specifying 'ListenAddress
  0.0.0.0:7722' stops sshd from listening to port 22. This, however, is
  not documented in 'man 5 sshd_config' and may be an unreliable side-
  effect.

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

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


[Touch-packages] [Bug 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify

2020-05-29 Thread Adriaan van Nijendaal
I have installed (another) fresh Ubuntu Server, got all the updates (apt
dist-upgrade), added the PPA (add-apt-repository ppa:ci-train-ppa-
service/4080) and updated again: openssh server, client and sftp were
replaced. Juggled config files and lines in config files as described
above, and:

The problem has gone away.

Question: should I use this PPA for a production system? Or should I
(and maybe others) keep using work-arounds and wait for OpenSSH 8.4 to
show up?

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

Title:
  Port parameter sshd_config is 22 AND whatever you specify

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Focal:
  Triaged

Bug description:
  On my Ubuntu Server 20.04 LTS with OpenSSH 1:8.2p1-4, I have TWO sshd
  deamons. One (on port 22) is for internal use, accepts passwords etc.
  The second (on port 7722) does not allow PAM use and no passwords,
  allows only one user(name) and uses an alternative autorized_keys file
  (that only root can edit).

  Any parameter FIRST encountered in sshd_config is the one that is
  accepted; others do not override (like in many other config files).
  There is one exception: 'Port', which is accumulative. To make life
  easier, I set the more restrictive parameters for port 7722 first and
  next include the system-default /etc/ssh/sshd_config.

  The /etc/ssh/sshd_config file(s) in Ubuntu Server 20.04 DO NOT specify
  'Port' anywhere - the default is 22. But: it is obviously still
  accumulative: Setting 'Port' to 7722 makes sshd listen on port 7722
  AND 22. This is unwanted.

  Proposed solution: Remove the accumulative behavior for 'Port' and
  REQUIRE the 'Port' parameter like before (and maybe have second and
  later parameters override the earlier ones, like 'everyone else').

  Regards,

  Adriaan

  PS Searching for solutions, I found that specifying 'ListenAddress
  0.0.0.0:7722' stops sshd from listening to port 22. This, however, is
  not documented in 'man 5 sshd_config' and may be an unreliable side-
  effect.

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

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


[Touch-packages] [Bug 1881207] Re: systemd-networkd brings eno1 up and down repeatedly

2020-05-29 Thread Dan Streetman
I can reproduce this with a VM using the emulated 'e1000e' device, and
unfortunately this is still a bug with upstream systemd code.  I'll look
at fixing this upstream but for now as a workaround, I'd recommend
manually setting the mtu and ignoring the mtu from dhcp, for example by
modifying the netplan yaml as such:

network:
  version: 2
  renderer: networkd
  ethernets:
eno1:
  dhcp4: yes
  dhcp4-overrides:
use-mtu: false
  mtu: 9000


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Tags added: seg

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

Title:
  systemd-networkd brings eno1 up and down repeatedly

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress

Bug description:
  Running on a NUC (BOXNUC8i7BEH3).

  After updating the `systemd` package past `237-3ubuntu10.32`, I see
  the onboard NIC link being taken down / up repeatedly, as shown below
  (dates are from my original notes, but the issue remains the same
  today).

  The NIC fails to remain up, and all networking is out of action.

  Running `systemctl stop systemd-netword` stops this and leaves the NIC in an 
unknown state.
  Subsequently running `ifconfig eno1 up && dhclient eno1` allows networking to 
continue basic operation, albeit without systemd's oversight.

  My original solution was to downgrade both the `libsystemd0` and
  `systemd` packages to `237-3ubuntu10.28`.

  After attempting an `apt update && apt upgrade` again today, exactly
  the same thing is happening with `237-3ubuntu10.41`.

  Good versions:
  - 237-3ubuntu10.28
  - 237-3ubuntu10.32 (currently in use, and held)

  Bad versions:
  - 237-3ubuntu10.33
  - 237-3ubuntu10.38
  - 237-3ubuntu10.41

  dmesg:

  [  360.711367] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  360.714370] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  360.726189] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  361.733073] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  361.744146] e1000e :00:1f.6: Interrupt Throttle Rate on
  [  366.760198] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  366.763375] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  366.776060] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  367.781718] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  367.792796] e1000e :00:1f.6: Interrupt Throttle Rate on
  [  372.808660] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  372.811537] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  372.823648] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  373.830436] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  373.841512] e1000e :00:1f.6: Interrupt Throttle Rate on

  journalctl -u systemd-networkd:

  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: Gained carrier
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: DHCPv4 address 
10.42.0.5/24 via 10.42.0.3
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: Configured
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: Lost carrier
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: DHCP lease lost
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:1

[Touch-packages] [Bug 1881301] [NEW] q

2020-05-29 Thread Matias Rubio
Public bug reported:

q

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
Uname: Linux 4.15.0-88-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_4_15_0_88_88_generic_67 wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri May 29 09:16:10 2020
DistUpgraded: 2019-01-04 17:00:34,973 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-76-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.15.0-88-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977]
InstallationDate: Installed on 2017-02-06 (1207 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 20156
ProcEnviron:
 LANGUAGE=es_PE:es
 PATH=(custom, no user)
 LANG=es_PE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic 
root=UUID=cef7f1ec-6114-4595-a4fc-e46a6813a2ca ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-01-04 (510 days ago)
dmi.bios.date: 08/16/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 62CN89WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo G480
dmi.board.vendor: LENOVO
dmi.board.version: 3194WIN8 STD SGL
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G480
dmi.modalias: 
dmi:bvnLENOVO:bvr62CN89WW:bd08/16/2012:svnLENOVO:pn20156:pvrLenovoG480:rvnLENOVO:rnLenovoG480:rvr3194WIN8STDSGL:cvnLENOVO:ct10:cvrLenovoG480:
dmi.product.family: ChiefRiver System
dmi.product.name: 20156
dmi.product.version: Lenovo G480
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Fri Jan  4 13:11:34 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   17740 
 vendor SEC
xserver.version: 2:1.18.4-0ubuntu0.2

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


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

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

Title:
  q

Status in xorg package in Ubuntu:
  New

Bug description:
  q

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_88_88_generic_67 wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri May 29 09:16:10 2020
  DistUpgraded: 2019-01-04 17:00:34,973 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-76-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-88-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977]
  InstallationDate: Installed on 2017-02-06 (1207 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20156
  ProcEnviron:
   LANGUAGE=es_PE:es
   PATH=(custom, no user)
   LANG=es_PE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic 
root=UUID=cef7f1ec-6114-4595-a4fc-e46a6813a2ca ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-01-04 (510 days ago)
  dmi.bios.date: 08/16/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 62CN89WW
  dmi.board.asset.

[Touch-packages] [Bug 1881295] [NEW] package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: subproces van pakket lvm2 werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug

2020-05-29 Thread Asterix1423
Public bug reported:

I tried to install some USB-tools, in which this package apparantly was
bundled. During the installation (using Synaptic) the error occured.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lvm2 2.03.07-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri May 29 15:57:57 2020
ErrorMessage: subproces van pakket lvm2 werd script post-installation 
geïnstalleerd gaf de foutwaarde 1 terug
InstallationDate: Installed on 2020-05-08 (21 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: lvm2
Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: subproces van 
pakket lvm2 werd script post-installation geïnstalleerd gaf de foutwaarde 1 
terug
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: subproces van
  pakket lvm2 werd script post-installation geïnstalleerd gaf de
  foutwaarde 1 terug

Status in lvm2 package in Ubuntu:
  New

Bug description:
  I tried to install some USB-tools, in which this package apparantly
  was bundled. During the installation (using Synaptic) the error
  occured.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 29 15:57:57 2020
  ErrorMessage: subproces van pakket lvm2 werd script post-installation 
geïnstalleerd gaf de foutwaarde 1 terug
  InstallationDate: Installed on 2020-05-08 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: lvm2
  Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: subproces van 
pakket lvm2 werd script post-installation geïnstalleerd gaf de foutwaarde 1 
terug
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1881292] [NEW] Linux 5.7: autopkgtest failures - lxc-test-cloneconfig && lxc-destroy

2020-05-29 Thread Paolo Pisati
Public bug reported:

...
make[1]: Leaving directory '/tmp/autopkgtest.OzTsXV/build.myP/src'
PASS: lxc-tests: lxc-test-api-reboot (75s)
PASS: lxc-tests: lxc-test-apparmor (1s)
PASS: lxc-tests: lxc-test-apparmor-generated (0s)
PASS: lxc-tests: lxc-test-apparmor-mount (25s)
PASS: lxc-tests: lxc-test-attach (0s)
PASS: lxc-tests: lxc-test-autostart (38s)
PASS: lxc-tests: lxc-test-basic (0s)
PASS: lxc-tests: lxc-test-cgpath (0s)
PASS: lxc-tests: lxc-test-checkpoint-restore (0s)
FAIL: lxc-tests: lxc-test-cloneconfig (1s)
---
lxc-destroy: lxctestb: tools/lxc_destroy.c: main: 242 Container is not defined
Test 1 starting (/tmp/lxctest-2SbLtT/1.conf)
lxc-destroy: lxctestb2: tools/lxc_destroy.c: main: 242 Container is not defined
FAIL
---
...

Groovy 5.7 kernel here: https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/bootstrap - linux-5.7

Full log here:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-groovy-canonical-kernel-team-
bootstrap/groovy/amd64/l/lxc/20200528_142652_ac8b1@/log.gz

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

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

Title:
  Linux 5.7: autopkgtest failures - lxc-test-cloneconfig && lxc-destroy

Status in lxc package in Ubuntu:
  New

Bug description:
  ...
  make[1]: Leaving directory '/tmp/autopkgtest.OzTsXV/build.myP/src'
  PASS: lxc-tests: lxc-test-api-reboot (75s)
  PASS: lxc-tests: lxc-test-apparmor (1s)
  PASS: lxc-tests: lxc-test-apparmor-generated (0s)
  PASS: lxc-tests: lxc-test-apparmor-mount (25s)
  PASS: lxc-tests: lxc-test-attach (0s)
  PASS: lxc-tests: lxc-test-autostart (38s)
  PASS: lxc-tests: lxc-test-basic (0s)
  PASS: lxc-tests: lxc-test-cgpath (0s)
  PASS: lxc-tests: lxc-test-checkpoint-restore (0s)
  FAIL: lxc-tests: lxc-test-cloneconfig (1s)
  ---
  lxc-destroy: lxctestb: tools/lxc_destroy.c: main: 242 Container is not defined
  Test 1 starting (/tmp/lxctest-2SbLtT/1.conf)
  lxc-destroy: lxctestb2: tools/lxc_destroy.c: main: 242 Container is not 
defined
  FAIL
  ---
  ...

  Groovy 5.7 kernel here: https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/bootstrap - linux-5.7

  Full log here:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-groovy-canonical-kernel-team-
  bootstrap/groovy/amd64/l/lxc/20200528_142652_ac8b1@/log.gz

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

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


[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-05-29 Thread Cornelius
When switching from A2DP to HSP/HFP I get this log message 5 times:

Bluetooth: hci0: SCO packet for unknown connection handle 0

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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


[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-05-29 Thread Cornelius
Also in 18.04 after regular update some days ago.

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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


[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-05-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bluez (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/1878194

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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


[Touch-packages] [Bug 1870359] Re: My machine as Wi-Fi Hotspot broken after upgrade to 20.04

2020-05-29 Thread Krister
I installed 1.22.10-1ubuntu2.1 and turned the hotspot on...
   my clients can use the hotspot normally.

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

** Tags removed: verification-done
** Tags added: verification-needed

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 20.04

Status in network-manager package in Ubuntu:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  * Regression potential
  the change is only updating the iptables binary location, there shouldn't be 
any code impact out of having the command working on systems without usrmerge 
when it was not before

  -

  
  I have a machine with a wired network connection and a wifi card. I've been 
using the machine as a wireless router and server in my house. I've attached a 
screenshot of the Wi-Fi network settings. It looks as expected.

  Upon updating to 20.04, none of my machines can use the connection.
  The linux machine will not connect. The windows machine will connect
  but will not have internet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  2 15:47:02 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (1645 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.0.1 dev eth0 proto static metric 100
   169.254.0.0/16 dev eth0 scope link metric 1000
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.100 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-04-02 (0 days ago)
  WifiSyslog:

  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-01-13T14:45:42.987041
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


[Touch-packages] [Bug 1881278] Re: Ship 2018 Archive key in xenial's ubuntu-keyring

2020-05-29 Thread Francis Ginther
** Tags added: id-5ed0fe766b5a0d2127bda2d0

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

Title:
  Ship 2018 Archive key in xenial's ubuntu-keyring

Status in ubuntu-keyring package in Ubuntu:
  Invalid
Status in ubuntu-keyring source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * Xenial systems will not be able to debootstrap Groovy archives when
  it finally switches to be signed by single 2018 key. To have support
  for xenial to operate against Groovy+ archives it needs access to 2018
  archive key. Ship it.

  [Test Case]

   * Start xenial chroot or lxd container.
   * Observe that 4 keys are trusted - the original 2004 archive & cdimage, 
2012 archive & cdimage

  # apt-key list --fingerprint
  /etc/apt/trusted.gpg
  
  pub   1024D/437D05B5 2004-09-12
Key fingerprint = 6302 39CC 130E 1A7F D81A  27B1 4097 6EAF 437D 05B5
  uid  Ubuntu Archive Automatic Signing Key 

  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
Key fingerprint = 790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid  Ubuntu Archive Automatic Signing Key (2012) 


  pub   4096R/EFE21092 2012-05-11
Key fingerprint = 8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
  uid  Ubuntu CD Image Automatic Signing Key (2012) 


  pub   1024D/FBB75451 2004-12-30
Key fingerprint = C598 6B4F 1257 FFA8 6632  CBA7 4618 1433 FBB7 5451
  uid  Ubuntu CD Image Automatic Signing Key 


* Install the new ubuntu-keyring package
* Observe that 5 keys are now trusted, including the 2018 archive key

  # apt-key list --fingerprint
  /etc/apt/trusted.gpg
  
  pub   1024D/437D05B5 2004-09-12
Key fingerprint = 6302 39CC 130E 1A7F D81A  27B1 4097 6EAF 437D 05B5
  uid  Ubuntu Archive Automatic Signing Key 

  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
Key fingerprint = 790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid  Ubuntu Archive Automatic Signing Key (2012) 


  pub   4096R/EFE21092 2012-05-11
Key fingerprint = 8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
  uid  Ubuntu CD Image Automatic Signing Key (2012) 


  pub   1024D/FBB75451 2004-12-30
Key fingerprint = C598 6B4F 1257 FFA8 6632  CBA7 4618 1433 FBB7 5451
  uid  Ubuntu CD Image Automatic Signing Key 


  pub   4096R/991BC93C 2018-09-17
Key fingerprint = F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
  uid  Ubuntu Archive Automatic Signing Key (2018) 


* Dist upgrade to bionic
* Observe that only 3 keys are trusted the 2012 cdimage&archive + 2018 key, 
and that none of them are in /etc/apt/trusted.gpg but are key snippets in 
/etc/apt/trusted.gpg.d/

  # apt-key list
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg
  --
  pub   rsa4096 2012-05-11 [SC]
790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2012) 


  /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg
  --
  pub   rsa4096 2012-05-11 [SC]
8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
  uid   [ unknown] Ubuntu CD Image Automatic Signing Key (2012) 


  /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
  --
  pub   rsa4096 2018-09-17 [SC]
F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2018) 


  
  [Regression Potential] 

   * Adding additional new trust key can trigger support request (aka
  why are you adding this key on xenial). The reason to add this key on
  xenial, is for xenial to allow securely debootstrap and operate on
  Groovy+ repositories which are about to drop 2012 key signatures.

  [Other Info]
   
   * Bionic switched from shipping keys in /etc/apt/trusted.gpg keyring, to 
individual snippets. Thus xenial's upload that adds the future key to 
/etc/apt/trusted.gpg should also remove it, during upgrade to bionic. To ensure 
that the systems upgraded from xenial to bionic, look the same as those that 
are fresh bionic installations.

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

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


[Touch-packages] [Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content

2020-05-29 Thread Francis Ginther
** Tags added: id-5ecfd66ad4bb5f1beb8b576d

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

Title:
  apport-unpack: ValueError: ['UserGroups'] has no binary content

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Groovy:
  Triaged

Bug description:
  When running apport-unpack to get at a core dump

  laney@raleigh> sudo apport-unpack 
_usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz
  [sudo] password for laney: 
  Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 73, in 
  pr.extract_keys(f, bin_keys, dir)
File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in 
extract_keys
  [item for item, element in b64_block.items() if element is False])
  ValueError: ['UserGroups'] has no binary content
  laney@raleigh> apport-cli --version
  2.16.2

  It's not terrible, because most files are unpacked (those which sort
  before UserGroups, I guess).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.16.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportLog:
   
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  3 10:09:26 2015
  InstallationDate: Installed on 2012-10-07 (876 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago)

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

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


[Touch-packages] [Bug 1880541] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation returned error code 1

2020-05-29 Thread Francis Ginther
** Tags added: id-5ecfdadcc5bd3d41d5d19e64

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

Title:
  package udev 245.4-4ubuntu3 failed to install/upgrade: podproces
  zainstalowany pakiet udev skrypt post-installation returned error code
  1

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  New

Bug description:
  During the Dist upgrade from 18.04 LTS to 20.04 LTS udev failed to
  configure interrupting the upgrade.

  dpkg complained that kvm already exist but it is not a system group.

  From what I saw my user was the only member of kvm group
  I don't recall installing kvm manually but I do have Android emulator 
installed so it is possible that it is related.

  Removing kvm group via
  groupdel kvm
  allowed 
  dpkg --configure -a 
  to succeed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 56-hpmud.rules 70-snap.core.rules
  Date: Mon May 25 11:01:36 2020
  ErrorMessage: podproces zainstalowany pakiet udev skrypt post-installation 
zwrócił kod błędu 1
  InstallationDate: Installed on 2017-10-18 (949 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic 
root=UUID=1c3374a5-d07b-4588-8159-7607318eb2c9 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces 
zainstalowany pakiet udev skrypt post-installation zwrócił kod błędu 1
  UpgradeStatus: Upgraded to focal on 2020-05-25 (0 days ago)
  dmi.bios.date: 07/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.80
  dmi.board.name: X370 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.80:bd07/18/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Touch-packages] [Bug 1833174] Re: Shadowing the vim-window results in vim-gtk3 crash

2020-05-29 Thread Francis Ginther
** Tags added: id-5ecfd55ec365863c5d5f6027

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

Title:
   Shadowing the vim-window results in vim-gtk3 crash

Status in vim:
  Unknown
Status in vim package in Ubuntu:
  Triaged
Status in vim source package in Focal:
  Triaged
Status in vim source package in Groovy:
  Triaged

Bug description:
  With XFCE when I try to "shadow" the vim-gtk3 window (just to show only the 
title bar) it results in a vim crash and the window just disappears without any 
core dump neither .swp files on.
  The only message I get on the terminal is

  BadMatch (invalid parameter attributes)
  Vim: Got X error
  Vim: Finished.

  This behaviour started from Xubuntu 18.04.
  The vim-gtk package is not suffering from this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: vim-gtk3 2:8.1.0320-1ubuntu3.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun 18 09:10:38 2019
  InstallationDate: Installed on 2019-04-23 (55 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check

2020-05-29 Thread Francis Ginther
** Tags added: id-5ecfd7fe4951b77bf134feed

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

Title:
  Ctrl-C message displayed without any actual disk check

Status in plymouth package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in plymouth source package in Focal:
  New
Status in systemd source package in Focal:
  New
Status in plymouth source package in Groovy:
  New
Status in systemd source package in Groovy:
  New

Bug description:
  It seems the transition to bgrt lost something with Ubuntu's disk
  check details. The only thing I see on my screen during a long disk
  check is the "press Ctrl-C to stop all in progress disk checks" with
  no progress.

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

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


[Touch-packages] [Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

2020-05-29 Thread Francis Ginther
** Tags added: id-5ecfd9948c28fe2dab5906af

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

Title:
  libc6-lse lets update-initramfs fail on AWS m6g instances

Status in cloud-images:
  New
Status in btrfs-progs package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New
Status in initramfs-tools package in Ubuntu:
  New
Status in btrfs-progs source package in Focal:
  New
Status in glibc source package in Focal:
  New
Status in initramfs-tools source package in Focal:
  New

Bug description:
  With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse
  lets update-initramfs always fail with the following error:

  ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1.

  ## Steps to reproduce (on AWS)

  ### With focal 20200423 AMI

  1. Find the following AMI and launch on m6g instance family

 ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423

  2. Run: sudo apt update && sudo apt install libc6-lse
  3. Try: sudo update-initramfs -u

  ### With focal 20200522 AMI

  1. Find the following AMI and launch on m6g instance family

 ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522

  2. Try: sudo update-initramfs -u

  ## Note

  - The entire log of the above steps performed on 20200423 AMI is attached.
  - Latest cloud-image AMI 
"ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes 
libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse 
manually.
  - This doesn't reproduce on EC2 a1.* instance family.

  ## Expected behavior

  Does not fail.

  ## Background to find this bug

  As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get
  upgrade pulls newer package that triggers update-initramfs, apt-get
  upgrade always fail on 20200522 AMI.

  
  the following is an apport report on 20200423 AMI:

  

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed May 27 09:52:16 2020
  Dependencies:
   gcc-10-base 10-20200411-0ubuntu1
   libc6 2.31-0ubuntu9
   libcrypt1 1:4.4.10-10ubuntu4
   libgcc-s1 10-20200411-0ubuntu1
   libidn2-0 2.2.0-2
   libunistring2 0.9.10-2
  DistroRelease: Ubuntu 20.04
  Ec2AMI: ami-061102f51d47b1c24
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-northeast-1c
  Ec2InstanceType: m6g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: libc6-lse 2.31-0ubuntu9
  PackageArchitecture: arm64
  ProcCpuinfoMinimal:
   processor  : 0
   BogoMIPS   : 243.75
   Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
   CPU implementer: 0x41
   CPU architecture: 8
   CPU variant: 0x3
   CPU part   : 0xd0c
   CPU revision   : 1
  ProcEnviron:
   LANG=C.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30
  SourcePackage: glibc
  Tags:  focal ec2-images
  Uname: Linux 5.4.0-1009-aws aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1880853/+subscriptions

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


[Touch-packages] [Bug 1881278] Re: Ship 2018 Archive key in xenial's ubuntu-keyring

2020-05-29 Thread Dimitri John Ledkov
** Changed in: ubuntu-keyring (Ubuntu Xenial)
   Status: Triaged => In Progress

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

Title:
  Ship 2018 Archive key in xenial's ubuntu-keyring

Status in ubuntu-keyring package in Ubuntu:
  Invalid
Status in ubuntu-keyring source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * Xenial systems will not be able to debootstrap Groovy archives when
  it finally switches to be signed by single 2018 key. To have support
  for xenial to operate against Groovy+ archives it needs access to 2018
  archive key. Ship it.

  [Test Case]

   * Start xenial chroot or lxd container.
   * Observe that 4 keys are trusted - the original 2004 archive & cdimage, 
2012 archive & cdimage

  # apt-key list --fingerprint
  /etc/apt/trusted.gpg
  
  pub   1024D/437D05B5 2004-09-12
Key fingerprint = 6302 39CC 130E 1A7F D81A  27B1 4097 6EAF 437D 05B5
  uid  Ubuntu Archive Automatic Signing Key 

  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
Key fingerprint = 790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid  Ubuntu Archive Automatic Signing Key (2012) 


  pub   4096R/EFE21092 2012-05-11
Key fingerprint = 8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
  uid  Ubuntu CD Image Automatic Signing Key (2012) 


  pub   1024D/FBB75451 2004-12-30
Key fingerprint = C598 6B4F 1257 FFA8 6632  CBA7 4618 1433 FBB7 5451
  uid  Ubuntu CD Image Automatic Signing Key 


* Install the new ubuntu-keyring package
* Observe that 5 keys are now trusted, including the 2018 archive key

  # apt-key list --fingerprint
  /etc/apt/trusted.gpg
  
  pub   1024D/437D05B5 2004-09-12
Key fingerprint = 6302 39CC 130E 1A7F D81A  27B1 4097 6EAF 437D 05B5
  uid  Ubuntu Archive Automatic Signing Key 

  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
Key fingerprint = 790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid  Ubuntu Archive Automatic Signing Key (2012) 


  pub   4096R/EFE21092 2012-05-11
Key fingerprint = 8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
  uid  Ubuntu CD Image Automatic Signing Key (2012) 


  pub   1024D/FBB75451 2004-12-30
Key fingerprint = C598 6B4F 1257 FFA8 6632  CBA7 4618 1433 FBB7 5451
  uid  Ubuntu CD Image Automatic Signing Key 


  pub   4096R/991BC93C 2018-09-17
Key fingerprint = F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
  uid  Ubuntu Archive Automatic Signing Key (2018) 


* Dist upgrade to bionic
* Observe that only 3 keys are trusted the 2012 cdimage&archive + 2018 key, 
and that none of them are in /etc/apt/trusted.gpg but are key snippets in 
/etc/apt/trusted.gpg.d/

  # apt-key list
  /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg
  --
  pub   rsa4096 2012-05-11 [SC]
790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2012) 


  /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg
  --
  pub   rsa4096 2012-05-11 [SC]
8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
  uid   [ unknown] Ubuntu CD Image Automatic Signing Key (2012) 


  /etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
  --
  pub   rsa4096 2018-09-17 [SC]
F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
  uid   [ unknown] Ubuntu Archive Automatic Signing Key (2018) 


  
  [Regression Potential] 

   * Adding additional new trust key can trigger support request (aka
  why are you adding this key on xenial). The reason to add this key on
  xenial, is for xenial to allow securely debootstrap and operate on
  Groovy+ repositories which are about to drop 2012 key signatures.

  [Other Info]
   
   * Bionic switched from shipping keys in /etc/apt/trusted.gpg keyring, to 
individual snippets. Thus xenial's upload that adds the future key to 
/etc/apt/trusted.gpg should also remove it, during upgrade to bionic. To ensure 
that the systems upgraded from xenial to bionic, look the same as those that 
are fresh bionic installations.

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

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


[Touch-packages] [Bug 1881278] [NEW] Ship 2018 Archive key in xenial's ubuntu-keyring

2020-05-29 Thread Dimitri John Ledkov
Public bug reported:

[Impact]

 * Xenial systems will not be able to debootstrap Groovy archives when
it finally switches to be signed by single 2018 key. To have support for
xenial to operate against Groovy+ archives it needs access to 2018
archive key. Ship it.

[Test Case]

 * Start xenial chroot or lxd container.
 * Observe that 4 keys are trusted - the original 2004 archive & cdimage, 2012 
archive & cdimage

# apt-key list --fingerprint
/etc/apt/trusted.gpg

pub   1024D/437D05B5 2004-09-12
  Key fingerprint = 6302 39CC 130E 1A7F D81A  27B1 4097 6EAF 437D 05B5
uid  Ubuntu Archive Automatic Signing Key 
sub   2048g/79164387 2004-09-12

pub   4096R/C0B21F32 2012-05-11
  Key fingerprint = 790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
uid  Ubuntu Archive Automatic Signing Key (2012) 


pub   4096R/EFE21092 2012-05-11
  Key fingerprint = 8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
uid  Ubuntu CD Image Automatic Signing Key (2012) 


pub   1024D/FBB75451 2004-12-30
  Key fingerprint = C598 6B4F 1257 FFA8 6632  CBA7 4618 1433 FBB7 5451
uid  Ubuntu CD Image Automatic Signing Key 

  * Install the new ubuntu-keyring package
  * Observe that 5 keys are now trusted, including the 2018 archive key

# apt-key list --fingerprint
/etc/apt/trusted.gpg

pub   1024D/437D05B5 2004-09-12
  Key fingerprint = 6302 39CC 130E 1A7F D81A  27B1 4097 6EAF 437D 05B5
uid  Ubuntu Archive Automatic Signing Key 
sub   2048g/79164387 2004-09-12

pub   4096R/C0B21F32 2012-05-11
  Key fingerprint = 790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
uid  Ubuntu Archive Automatic Signing Key (2012) 


pub   4096R/EFE21092 2012-05-11
  Key fingerprint = 8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
uid  Ubuntu CD Image Automatic Signing Key (2012) 


pub   1024D/FBB75451 2004-12-30
  Key fingerprint = C598 6B4F 1257 FFA8 6632  CBA7 4618 1433 FBB7 5451
uid  Ubuntu CD Image Automatic Signing Key 

pub   4096R/991BC93C 2018-09-17
  Key fingerprint = F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
uid  Ubuntu Archive Automatic Signing Key (2018) 


  * Dist upgrade to bionic
  * Observe that only 3 keys are trusted the 2012 cdimage&archive + 2018 key, 
and that none of them are in /etc/apt/trusted.gpg but are key snippets in 
/etc/apt/trusted.gpg.d/

# apt-key list
/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg
--
pub   rsa4096 2012-05-11 [SC]
  790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
uid   [ unknown] Ubuntu Archive Automatic Signing Key (2012) 


/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg
--
pub   rsa4096 2012-05-11 [SC]
  8439 38DF 228D 22F7 B374  2BC0 D94A A3F0 EFE2 1092
uid   [ unknown] Ubuntu CD Image Automatic Signing Key (2012) 


/etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
--
pub   rsa4096 2018-09-17 [SC]
  F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C
uid   [ unknown] Ubuntu Archive Automatic Signing Key (2018) 



[Regression Potential] 

 * Adding additional new trust key can trigger support request (aka why
are you adding this key on xenial). The reason to add this key on
xenial, is for xenial to allow securely debootstrap and operate on
Groovy+ repositories which are about to drop 2012 key signatures.

[Other Info]
 
 * Bionic switched from shipping keys in /etc/apt/trusted.gpg keyring, to 
individual snippets. Thus xenial's upload that adds the future key to 
/etc/apt/trusted.gpg should also remove it, during upgrade to bionic. To ensure 
that the systems upgraded from xenial to bionic, look the same as those that 
are fresh bionic installations.

** Affects: ubuntu-keyring (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: ubuntu-keyring (Ubuntu Xenial)
 Importance: Undecided
 Status: Triaged

** Also affects: ubuntu-keyring (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-keyring (Ubuntu)
   Status: New => Invalid

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

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

Title:
  Ship 2018 Archive key in xenial's ubuntu-keyring

Status in ubuntu-keyring package in Ubuntu:
  Invalid
Status in ubuntu-keyring source package in Xenial:
  Triaged

Bug description:
  [Impact]

   * Xenial systems will not be able to debootstrap Groovy archives when
  it finally switches to be signed by single 2018 key. To have support
  for xenial to operate against Groovy+ archives it needs access to 201

[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

2020-05-29 Thread Damiön la Bagh
Can confirm that these steps BEFORE REBOOTING lead to a working 18.04
system after the 16.04 upgrade fails.

Maybe these steps could be added to the upgrade script

In psudocode:

if [ error due to systemd1.service ] then;

sudo mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.bak
sudo apt-get install -f
sudo apt dist-upgrade
sudo apt autoremove

exit
fi

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Released
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget 
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb 
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The following packages will be REMOVED:
systemd-shim
  ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  ...

  
  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]

   * original bug report

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

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


[Touch-packages] [Bug 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport

2020-05-29 Thread You-Sheng Yang
@Brian, can we have this backport to Bionic as well? Bionic is to end
extended desktop/server support on 2023 and extended security support on
2028, so it's still likely to receive bug reports in the future on
Bionic.

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

Title:
  missing hardware/runtime info when reporing linux-firmware bugs via
  apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  Invalid
Status in linux-firmware source package in Eoan:
  Invalid
Status in apport source package in Focal:
  Fix Released
Status in linux-firmware source package in Focal:
  Invalid

Bug description:
  linux-firmware doesn't install any package hooks for apport, so it
  will only carry some default items leaving hardware list, kernel
  messages unattached. Suggest symlink /usr/share/apport/package-hooks
  /source_linux-firmware.py to source_linux.py as other linux image debs
  do in bug 1847967.

  Test Case
  -
  1) On an Ubuntu 20.04 LTS system run 'apport-cli linux-firmware'.
  2) Choose 'View report'
  3) Observe that 'ProcFB' is not collected

  With the version of apport from -proposed 'ProcFB' will be in the
  report.

  
  Regression Potential
  
  None, as we are just adding a symlink from linux-firmware to the linux source 
package hook.

  Original Description
  
  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 10 19:15:15 2020
  Dependencies:

  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  PackageArchitecture: allSourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Dependencies:

  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux-firmware
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic 
root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet 
splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 156.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Touch-packages] [Bug 1881207] Re: systemd-networkd brings eno1 up and down repeatedly

2020-05-29 Thread Attie Grande
To clarify:

- I'm now running version `237-3ubuntu10.41` of both `systemd` and 
`libsystemd0`.
- With the DHCP MTU option removed, the network interface comes up correctly 
and remains stable.

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

Title:
  systemd-networkd brings eno1 up and down repeatedly

Status in systemd package in Ubuntu:
  New

Bug description:
  Running on a NUC (BOXNUC8i7BEH3).

  After updating the `systemd` package past `237-3ubuntu10.32`, I see
  the onboard NIC link being taken down / up repeatedly, as shown below
  (dates are from my original notes, but the issue remains the same
  today).

  The NIC fails to remain up, and all networking is out of action.

  Running `systemctl stop systemd-netword` stops this and leaves the NIC in an 
unknown state.
  Subsequently running `ifconfig eno1 up && dhclient eno1` allows networking to 
continue basic operation, albeit without systemd's oversight.

  My original solution was to downgrade both the `libsystemd0` and
  `systemd` packages to `237-3ubuntu10.28`.

  After attempting an `apt update && apt upgrade` again today, exactly
  the same thing is happening with `237-3ubuntu10.41`.

  Good versions:
  - 237-3ubuntu10.28
  - 237-3ubuntu10.32 (currently in use, and held)

  Bad versions:
  - 237-3ubuntu10.33
  - 237-3ubuntu10.38
  - 237-3ubuntu10.41

  dmesg:

  [  360.711367] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  360.714370] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  360.726189] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  361.733073] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  361.744146] e1000e :00:1f.6: Interrupt Throttle Rate on
  [  366.760198] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  366.763375] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  366.776060] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  367.781718] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  367.792796] e1000e :00:1f.6: Interrupt Throttle Rate on
  [  372.808660] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  372.811537] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  372.823648] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  373.830436] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  373.841512] e1000e :00:1f.6: Interrupt Throttle Rate on

  journalctl -u systemd-networkd:

  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: Gained carrier
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: DHCPv4 address 
10.42.0.5/24 via 10.42.0.3
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: Configured
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: Lost carrier
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: DHCP lease lost
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: Gained carrier
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: DHCPv4 address 
10.42.0.5/24 via 10.42.0.3
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: Configured
  Jan 06 18:04:12 patch systemd-networkd[755]: eno1: Lost carrier
  Jan 06 18:04:12 patch systemd-networkd[755]: eno1: DHCP lease lost
  Jan 06 18:04:12 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: Gained carrier
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: DHCPv4 address 
10.42.0.5/24 via 10.42.0.3
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: Configured
  Jan 06 18:04:18 patch systemd-networkd[755]: eno1: Lost carrier
  Jan 06 18:04:18 patch systemd-networkd[755]: eno1: DHCP lease lost
  Jan 06 18:04:18 patch systemd-networkd[755]: eno1: IPv6 successfully enabled

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.32
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  Date: Thu May 28 23:19:27 2020
  InstallationDate: Installed on 2019-06-20 (343 days ago)
  InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0dc6:3401 Precision Squared Technology Corp.
   Bus 001 Device 002: ID 0403:6014 Future Technology Devices International, 
Ltd FT232H Single HS USB-UART/FIFO IC
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Machine

[Touch-packages] [Bug 1881207] Re: systemd-networkd brings eno1 up and down repeatedly

2020-05-29 Thread Attie Grande
Hi Dan,

- `/etc/systemd/network/` is empty.
- `/etc/netplan/01-netcfg.yaml` is attached. (I believe this is default, I 
don't think I've made any changes)
- MTU 9000 was being set by DHCP, I've removed this option and with the default 
(MTU=1500), the system comes up correctly.

Attie

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

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

Title:
  systemd-networkd brings eno1 up and down repeatedly

Status in systemd package in Ubuntu:
  New

Bug description:
  Running on a NUC (BOXNUC8i7BEH3).

  After updating the `systemd` package past `237-3ubuntu10.32`, I see
  the onboard NIC link being taken down / up repeatedly, as shown below
  (dates are from my original notes, but the issue remains the same
  today).

  The NIC fails to remain up, and all networking is out of action.

  Running `systemctl stop systemd-netword` stops this and leaves the NIC in an 
unknown state.
  Subsequently running `ifconfig eno1 up && dhclient eno1` allows networking to 
continue basic operation, albeit without systemd's oversight.

  My original solution was to downgrade both the `libsystemd0` and
  `systemd` packages to `237-3ubuntu10.28`.

  After attempting an `apt update && apt upgrade` again today, exactly
  the same thing is happening with `237-3ubuntu10.41`.

  Good versions:
  - 237-3ubuntu10.28
  - 237-3ubuntu10.32 (currently in use, and held)

  Bad versions:
  - 237-3ubuntu10.33
  - 237-3ubuntu10.38
  - 237-3ubuntu10.41

  dmesg:

  [  360.711367] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  360.714370] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  360.726189] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  361.733073] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  361.744146] e1000e :00:1f.6: Interrupt Throttle Rate on
  [  366.760198] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  366.763375] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  366.776060] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  367.781718] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  367.792796] e1000e :00:1f.6: Interrupt Throttle Rate on
  [  372.808660] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  372.811537] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  372.823648] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  373.830436] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  373.841512] e1000e :00:1f.6: Interrupt Throttle Rate on

  journalctl -u systemd-networkd:

  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: Gained carrier
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: DHCPv4 address 
10.42.0.5/24 via 10.42.0.3
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: Configured
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: Lost carrier
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: DHCP lease lost
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: Gained carrier
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: DHCPv4 address 
10.42.0.5/24 via 10.42.0.3
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: Configured
  Jan 06 18:04:12 patch systemd-networkd[755]: eno1: Lost carrier
  Jan 06 18:04:12 patch systemd-networkd[755]: eno1: DHCP lease lost
  Jan 06 18:04:12 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: Gained carrier
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: DHCPv4 address 
10.42.0.5/24 via 10.42.0.3
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: Configured
  Jan 06 18:04:18 patch systemd-networkd[755]: eno1: Lost carrier
  Jan 06 18:04:18 patch systemd-networkd[755]: eno1: DHCP lease lost
  Jan 06 18:04:18 patch systemd-networkd[755]: eno1: IPv6 successfully enabled

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.32
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  Date: Thu May 28 23:19:27 2020
  InstallationDate: Installed on 2019-06-20 (343 days ago)
  InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0dc6:3401 Precision Squared Technology Corp

[Touch-packages] [Bug 1881207] Re: systemd-networkd brings eno1 up and down repeatedly

2020-05-29 Thread Dan Streetman
Can you attach your network configuration - either netplan config or
networkd config?

Also, can you try removing your MTU config for eno1 and see if that
allows it to stay up?

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

Title:
  systemd-networkd brings eno1 up and down repeatedly

Status in systemd package in Ubuntu:
  New

Bug description:
  Running on a NUC (BOXNUC8i7BEH3).

  After updating the `systemd` package past `237-3ubuntu10.32`, I see
  the onboard NIC link being taken down / up repeatedly, as shown below
  (dates are from my original notes, but the issue remains the same
  today).

  The NIC fails to remain up, and all networking is out of action.

  Running `systemctl stop systemd-netword` stops this and leaves the NIC in an 
unknown state.
  Subsequently running `ifconfig eno1 up && dhclient eno1` allows networking to 
continue basic operation, albeit without systemd's oversight.

  My original solution was to downgrade both the `libsystemd0` and
  `systemd` packages to `237-3ubuntu10.28`.

  After attempting an `apt update && apt upgrade` again today, exactly
  the same thing is happening with `237-3ubuntu10.41`.

  Good versions:
  - 237-3ubuntu10.28
  - 237-3ubuntu10.32 (currently in use, and held)

  Bad versions:
  - 237-3ubuntu10.33
  - 237-3ubuntu10.38
  - 237-3ubuntu10.41

  dmesg:

  [  360.711367] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  360.714370] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  360.726189] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  361.733073] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  361.744146] e1000e :00:1f.6: Interrupt Throttle Rate on
  [  366.760198] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  366.763375] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  366.776060] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  367.781718] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  367.792796] e1000e :00:1f.6: Interrupt Throttle Rate on
  [  372.808660] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: Rx/Tx
  [  372.811537] e1000e :00:1f.6 eno1: changing MTU from 1500 to 9000
  [  372.823648] e1000e :00:1f.6: Interrupt Throttle Rate off
  [  373.830436] e1000e :00:1f.6 eno1: changing MTU from 9000 to 1500
  [  373.841512] e1000e :00:1f.6: Interrupt Throttle Rate on

  journalctl -u systemd-networkd:

  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: Gained carrier
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: DHCPv4 address 
10.42.0.5/24 via 10.42.0.3
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:05 patch systemd-networkd[755]: eno1: Configured
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: Lost carrier
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: DHCP lease lost
  Jan 06 18:04:06 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: Gained carrier
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: DHCPv4 address 
10.42.0.5/24 via 10.42.0.3
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:11 patch systemd-networkd[755]: eno1: Configured
  Jan 06 18:04:12 patch systemd-networkd[755]: eno1: Lost carrier
  Jan 06 18:04:12 patch systemd-networkd[755]: eno1: DHCP lease lost
  Jan 06 18:04:12 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: Gained carrier
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: DHCPv4 address 
10.42.0.5/24 via 10.42.0.3
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: IPv6 successfully enabled
  Jan 06 18:04:17 patch systemd-networkd[755]: eno1: Configured
  Jan 06 18:04:18 patch systemd-networkd[755]: eno1: Lost carrier
  Jan 06 18:04:18 patch systemd-networkd[755]: eno1: DHCP lease lost
  Jan 06 18:04:18 patch systemd-networkd[755]: eno1: IPv6 successfully enabled

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.32
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  Date: Thu May 28 23:19:27 2020
  InstallationDate: Installed on 2019-06-20 (343 days ago)
  InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0dc6:3401 Precision Squared Technology Corp.
   Bus 001 Device 002: ID 0403:6014 Future Technology Devices International, 
Ltd FT232H Single HS USB-UART/FIFO IC
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel(R) Cl

[Touch-packages] [Bug 1881266] [NEW] Xorg crash

2020-05-29 Thread amirhosein mohammadi
Public bug reported:

hi 
there is something wrong with my display
when i using laptop for a while display crashed and getting black
my monitor is 4k and i guess it's cause of this problem

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41
Uname: Linux 5.4.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 29 14:24:38 2020
DistUpgraded: 2020-05-11 18:00:30,770 DEBUG refresh of snap core18 succeeded
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.64, 5.4.0-33-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-34-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1d8d]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1d8d]
InstallationDate: Installed on 2020-05-11 (17 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: ASUSTeK COMPUTER INC. N552VW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic 
root=UUID=a76ee8a9-d0e8-4e74-8578-67f8f39c8f00 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to focal on 2020-05-11 (17 days ago)
dmi.bios.date: 08/31/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N552VW.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N552VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN552VW.300:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnN552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N552VW
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug crash focal ubuntu

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  hi 
  there is something wrong with my display
  when i using laptop for a while display crashed and getting black
  my monitor is 4k and i guess it's cause of this problem

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41
  Uname: Linux 5.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 29 14:24:38 2020
  DistUpgraded: 2020-05-11 18:00:30,770 DEBUG refresh of snap core18 succeeded
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-33-generic, x86_64: in

[Touch-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423

2020-05-29 Thread Ludovic Rousseau
The fact that the LED is green then goes to red after a few seconds is 
completely normal.
See https://ludovicrousseau.blogspot.com/2010/10/card-auto-power-on-and-off.html

The fact that you get "PowerUp failed" errors is NOT normal.
It is a hardware issue with the card and/or the reader.

That is why I asked you to try with another smart card.

On my side I tried with current version of pcsc-lite and libccid and I
have no problem with my ActivIdentity Activkey_Sim device.

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

Title:
  pcscd doesn't support ActivKEy SIM B/N: 0945423

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not 
recognized by pcscd. Since it is not recognized, it is also not recognized by 
VMware Workstation VM which runs Windows. Banking software running in windows 
doesn't see the key and can't authenticate me.
  Few years ago, this was working on Ubuntu 18.04, so it must be something in 
version between.
  After restart of the pcscd service, USB key shows green light, but few 
seconds after it goes to red.

  sudo service pcscd status
  ● pcscd.service - PC/SC Smart Card Daemon
   Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago
  TriggeredBy: ● pcscd.socket
 Docs: man:pcscd(8)
 Main PID: 230408 (pcscd)
Tasks: 5 (limit: 57614)
   Memory: 1.9M
   CGroup: /system.slice/pcscd.service
   └─230408 /usr/sbin/pcscd --foreground --auto-exit

  svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon.
  svi 21 15:48:01 rodigerlaptop1 pcscd[230408]:  
ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 
commands.c:249:CmdPowerOn Card absent or mute
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 
ifdhandler.c:1221:IFDHPowerICC() PowerUp failed
  svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 
eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 
0x80100016

  Result of pcsc_scan
  sudo pcsc_scan 
  Using reader plug'n play mechanism
  Scanning present readers...
  Waiting for the first reader...found one
  Scanning present readers...
  0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
   
  Thu May 21 15:44:16 2020
   Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00
Event number: 0
Card state: Card inserted, Unresponsive card, 

  So USB key is visible

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pcscd 1.8.26-3
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 21 15:38:57 2020
  SourcePackage: pcsc-lite
  UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago)

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

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


[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

2020-05-29 Thread vinod
This package update is still braking few instances hosted on AWS. it is
the same issue what we have seen in version "libjson-c2 0.11-4ubuntu2.1"
and impacted a lot of users.

same issue we are facing in the version libjson-c2/now 0.11-4ubuntu2.6
which caused few aws instances to go in kernel panic mode.


do ubuntu have through testing before pushing update and what about revert 
back. can ubuntu revert back to previous package if unattended upgrade sees any 
error?

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

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

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

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


[Touch-packages] [Bug 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify

2020-05-29 Thread Christian Ehrhardt 
I have prepared a PPA with the fix and would appreciate if that could be tried 
and tested:
@Adriaan - would you be so kind to confirm that this fixes your real case?

PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4080

Furthermore as I expect this will work well I also have merge proposals to fix 
this in Groovy and later Focal:
https://code.launchpad.net/~paelzer/ubuntu/+source/openssh/+git/openssh/+merge/384813
https://code.launchpad.net/~paelzer/ubuntu/+source/openssh/+git/openssh/+merge/384814

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

Title:
  Port parameter sshd_config is 22 AND whatever you specify

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Focal:
  Triaged

Bug description:
  On my Ubuntu Server 20.04 LTS with OpenSSH 1:8.2p1-4, I have TWO sshd
  deamons. One (on port 22) is for internal use, accepts passwords etc.
  The second (on port 7722) does not allow PAM use and no passwords,
  allows only one user(name) and uses an alternative autorized_keys file
  (that only root can edit).

  Any parameter FIRST encountered in sshd_config is the one that is
  accepted; others do not override (like in many other config files).
  There is one exception: 'Port', which is accumulative. To make life
  easier, I set the more restrictive parameters for port 7722 first and
  next include the system-default /etc/ssh/sshd_config.

  The /etc/ssh/sshd_config file(s) in Ubuntu Server 20.04 DO NOT specify
  'Port' anywhere - the default is 22. But: it is obviously still
  accumulative: Setting 'Port' to 7722 makes sshd listen on port 7722
  AND 22. This is unwanted.

  Proposed solution: Remove the accumulative behavior for 'Port' and
  REQUIRE the 'Port' parameter like before (and maybe have second and
  later parameters override the earlier ones, like 'everyone else').

  Regards,

  Adriaan

  PS Searching for solutions, I found that specifying 'ListenAddress
  0.0.0.0:7722' stops sshd from listening to port 22. This, however, is
  not documented in 'man 5 sshd_config' and may be an unreliable side-
  effect.

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

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


[Touch-packages] [Bug 1872118] Re: DHCP Cluster crashes after a few hours

2020-05-29 Thread Andrew Welham
Thats not a bad idea, they  It seems to be they are  ignoring the
critical issue. i.e you CAN@T RUN A PRODUCTION CLUSTER

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

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

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

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


[Touch-packages] [Bug 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify

2020-05-29 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/openssh/+git/openssh/+merge/384813

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/openssh/+git/openssh/+merge/384814

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

Title:
  Port parameter sshd_config is 22 AND whatever you specify

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Focal:
  Triaged

Bug description:
  On my Ubuntu Server 20.04 LTS with OpenSSH 1:8.2p1-4, I have TWO sshd
  deamons. One (on port 22) is for internal use, accepts passwords etc.
  The second (on port 7722) does not allow PAM use and no passwords,
  allows only one user(name) and uses an alternative autorized_keys file
  (that only root can edit).

  Any parameter FIRST encountered in sshd_config is the one that is
  accepted; others do not override (like in many other config files).
  There is one exception: 'Port', which is accumulative. To make life
  easier, I set the more restrictive parameters for port 7722 first and
  next include the system-default /etc/ssh/sshd_config.

  The /etc/ssh/sshd_config file(s) in Ubuntu Server 20.04 DO NOT specify
  'Port' anywhere - the default is 22. But: it is obviously still
  accumulative: Setting 'Port' to 7722 makes sshd listen on port 7722
  AND 22. This is unwanted.

  Proposed solution: Remove the accumulative behavior for 'Port' and
  REQUIRE the 'Port' parameter like before (and maybe have second and
  later parameters override the earlier ones, like 'everyone else').

  Regards,

  Adriaan

  PS Searching for solutions, I found that specifying 'ListenAddress
  0.0.0.0:7722' stops sshd from listening to port 22. This, however, is
  not documented in 'man 5 sshd_config' and may be an unreliable side-
  effect.

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

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


[Touch-packages] [Bug 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify

2020-05-29 Thread Christian Ehrhardt 
Final committed fix for this issue:
https://anongit.mindrot.org/openssh.git/commit/?id=0a9a611619b0a1fecd0195ec86a9885f5d681c84

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

Title:
  Port parameter sshd_config is 22 AND whatever you specify

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Focal:
  Triaged

Bug description:
  On my Ubuntu Server 20.04 LTS with OpenSSH 1:8.2p1-4, I have TWO sshd
  deamons. One (on port 22) is for internal use, accepts passwords etc.
  The second (on port 7722) does not allow PAM use and no passwords,
  allows only one user(name) and uses an alternative autorized_keys file
  (that only root can edit).

  Any parameter FIRST encountered in sshd_config is the one that is
  accepted; others do not override (like in many other config files).
  There is one exception: 'Port', which is accumulative. To make life
  easier, I set the more restrictive parameters for port 7722 first and
  next include the system-default /etc/ssh/sshd_config.

  The /etc/ssh/sshd_config file(s) in Ubuntu Server 20.04 DO NOT specify
  'Port' anywhere - the default is 22. But: it is obviously still
  accumulative: Setting 'Port' to 7722 makes sshd listen on port 7722
  AND 22. This is unwanted.

  Proposed solution: Remove the accumulative behavior for 'Port' and
  REQUIRE the 'Port' parameter like before (and maybe have second and
  later parameters override the earlier ones, like 'everyone else').

  Regards,

  Adriaan

  PS Searching for solutions, I found that specifying 'ListenAddress
  0.0.0.0:7722' stops sshd from listening to port 22. This, however, is
  not documented in 'man 5 sshd_config' and may be an unreliable side-
  effect.

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

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


[Touch-packages] [Bug 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify

2020-05-29 Thread Christian Ehrhardt 
FYI: "Include" functionality was added in 8.2 by upstream.
Thereby as already triaged only >=Focal is affected

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

Title:
  Port parameter sshd_config is 22 AND whatever you specify

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Focal:
  Triaged

Bug description:
  On my Ubuntu Server 20.04 LTS with OpenSSH 1:8.2p1-4, I have TWO sshd
  deamons. One (on port 22) is for internal use, accepts passwords etc.
  The second (on port 7722) does not allow PAM use and no passwords,
  allows only one user(name) and uses an alternative autorized_keys file
  (that only root can edit).

  Any parameter FIRST encountered in sshd_config is the one that is
  accepted; others do not override (like in many other config files).
  There is one exception: 'Port', which is accumulative. To make life
  easier, I set the more restrictive parameters for port 7722 first and
  next include the system-default /etc/ssh/sshd_config.

  The /etc/ssh/sshd_config file(s) in Ubuntu Server 20.04 DO NOT specify
  'Port' anywhere - the default is 22. But: it is obviously still
  accumulative: Setting 'Port' to 7722 makes sshd listen on port 7722
  AND 22. This is unwanted.

  Proposed solution: Remove the accumulative behavior for 'Port' and
  REQUIRE the 'Port' parameter like before (and maybe have second and
  later parameters override the earlier ones, like 'everyone else').

  Regards,

  Adriaan

  PS Searching for solutions, I found that specifying 'ListenAddress
  0.0.0.0:7722' stops sshd from listening to port 22. This, however, is
  not documented in 'man 5 sshd_config' and may be an unreliable side-
  effect.

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

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