date:20200721

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

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  The software properties screen freezes when I update the software
  cache

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  I am currently using Ubuntu 20.04, but I had the same problem in
  19.10. When I make changes to the software resources, when closing the
  program, "Update the software cache?" I come across the question. If I
  say yes, it updates the cache but the window freezes. It cannot be
  closed in any way.

  'lsb_release -rd':
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  
  'apt-cache policy software-properties':
  software-properties:
Installed: (none)
Candidate: (none)
Release schedule:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.9
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 20 16:08:11 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2017-06-10 (1075 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  Python3Details: /usr/local/bin/python3.7, Python 3.7.2, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to focal on 2020-05-11 (8 days ago)

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

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

[Touch-packages] [Bug 1886644] Re: SRU the current 3.36.4 stable update

2020-07-21 Thread Chris Halse Rogers

Additionally: since this includes a security fix, should there be a fix
in focal-security?

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

Title:
  SRU the current 3.36.4 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Committed

Bug description:
  * Impact

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1886644/+subscriptions

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

[Touch-packages] [Bug 1886644] Re: SRU the current 3.36.4 stable update

2020-07-21 Thread Chris Halse Rogers

Hello Sebastien, or anyone else affected,

Accepted evolution-data-server into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/evolution-data-server/3.36.4-0ubuntu1 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Changed in: evolution-data-server (Ubuntu Focal)
   Status: New => Fix Committed

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

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

Title:
  SRU the current 3.36.4 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Committed

Bug description:
  * Impact

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1886644/+subscriptions

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

[Touch-packages] [Bug 1888442] [NEW] upgrade did not go well

2020-07-21 Thread Seth Arnold

Public bug reported:

Hello, I had some problems during my most recent apt upgrade. A
confounding factor to these problems was removing my laptop from its
docking station a few minutes earlier.

$ sudo apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-headers-5.4.0-42 linux-headers-5.4.0-42-generic 
linux-image-5.4.0-42-generic
  linux-modules-5.4.0-42-generic linux-modules-extra-5.4.0-42-generic 
python3-click python3-colorama
The following packages will be upgraded:
  base-files libnss-mymachines libnss-systemd libpam-systemd 
libpulse-mainloop-glib0 libpulse0 libpulsedsp
  libseccomp2 libsystemd0 libudev1 libvirt-clients libvirt-daemon 
libvirt-daemon-driver-qemu
  libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-zfs 
libvirt-daemon-system
  libvirt-daemon-system-systemd libvirt0 linux-firmware linux-generic 
linux-headers-generic linux-image-generic
  pulseaudio pulseaudio-utils python3-distupgrade sudo systemd 
systemd-container systemd-journal-remote
  systemd-sysv systemd-timesyncd ubuntu-drivers-common 
ubuntu-release-upgrader-core udev
34 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
Need to get 110 MB/184 MB of archives.
After this operation, 360 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://wopr.domain/ubuntu focal-proposed/main amd64 base-files amd64 
11ubuntu5.1 [60.1 kB]
Get:2 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-systemd amd64 
245.4-4ubuntu3.2 [95.6 kB]
Get:3 http://wopr.domain/ubuntu focal-proposed/universe amd64 
systemd-journal-remote amd64 245.4-4ubuntu3.2 [61.9 kB]
Get:4 http://wopr.domain/ubuntu focal-proposed/main amd64 udev amd64 
245.4-4ubuntu3.2 [1,363 kB]
Get:5 http://wopr.domain/ubuntu focal-proposed/main amd64 libudev1 amd64 
245.4-4ubuntu3.2 [78.9 kB]
Get:6 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon-system 
amd64 6.0.0-0ubuntu8.2 [67.5 kB]
Get:7 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-clients amd64 
6.0.0-0ubuntu8.2 [343 kB]
Get:8 http://wopr.domain/ubuntu focal-proposed/main amd64 
libvirt-daemon-driver-qemu amd64 6.0.0-0ubuntu8.2 [605 kB]
Get:9 http://wopr.domain/ubuntu focal-proposed/universe amd64 
libvirt-daemon-driver-storage-zfs amd64 6.0.0-0ubuntu8.2 [21.4 kB]
Get:10 http://wopr.domain/ubuntu focal-proposed/main amd64 
libvirt-daemon-driver-storage-rbd amd64 6.0.0-0ubuntu8.2 [28.3 kB]
Get:11 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt0 amd64 
6.0.0-0ubuntu8.2 [1,444 kB]
Get:12 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon amd64 
6.0.0-0ubuntu8.2 [404 kB]
Get:13 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-mymachines 
amd64 245.4-4ubuntu3.2 [131 kB]
Get:14 http://wopr.domain/ubuntu focal-proposed/main amd64 libseccomp2 amd64 
2.4.3-1ubuntu3.20.04.3 [42.4 kB]
Get:15 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-container 
amd64 245.4-4ubuntu3.2 [317 kB]
Get:16 http://wopr.domain/ubuntu focal-proposed/main amd64 
libvirt-daemon-system-systemd amd64 6.0.0-0ubuntu8.2 [12.3 kB]
Get:17 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-sysv amd64 
245.4-4ubuntu3.2 [10.3 kB]
Get:18 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-timesyncd 
amd64 245.4-4ubuntu3.2 [28.0 kB]
Get:19 http://wopr.domain/ubuntu focal-proposed/main amd64 libpam-systemd amd64 
245.4-4ubuntu3.2 [186 kB]
Get:20 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd amd64 
245.4-4ubuntu3.2 [3,796 kB]
Get:21 http://wopr.domain/ubuntu focal-proposed/main amd64 libsystemd0 amd64 
245.4-4ubuntu3.2 [271 kB]
Get:22 http://wopr.domain/ubuntu focal-proposed/main amd64 
libpulse-mainloop-glib0 amd64 1:13.99.1-1ubuntu3.5 [11.7 kB]
Get:23 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulsedsp amd64 
1:13.99.1-1ubuntu3.5 [21.7 kB]
Get:24 http://wopr.domain/ubuntu focal-proposed/main amd64 pulseaudio-utils 
amd64 1:13.99.1-1ubuntu3.5 [55.0 kB]
Get:25 http://wopr.domain/ubuntu focal-proposed/main amd64 pulseaudio amd64 
1:13.99.1-1ubuntu3.5 [815 kB]
Get:26 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulse0 amd64 
1:13.99.1-1ubuntu3.5 [263 kB]
Get:27 http://wopr.domain/ubuntu focal/main amd64 python3-colorama all 
0.4.3-1build1 [23.9 kB]
Get:28 http://wopr.domain/ubuntu focal/main amd64 python3-click all 7.0-3 [64.8 
kB]
Get:29 http://wopr.domain/ubuntu focal-proposed/main amd64 
ubuntu-drivers-common amd64 1:0.8.4~0.20.04.1 [45.2 kB]
Get:30 http://wopr.domain/ubuntu focal-proposed/main amd64 sudo amd64 
1.8.31-1ubuntu1.1 [513 kB]
Get:31 http://wopr.domain/ubuntu focal-proposed/main amd64 
ubuntu-release-upgrader-core all 1:20.04.23 [23.6 kB]
Get:32 http://wopr.domain/ubuntu focal-proposed/main amd64 python3-distupgrade 
all 1:20.04.23 [103 kB]
Get:33 http://wopr.domain/ubuntu focal-proposed/main amd64 linux-firmware all 
1.187.2 [98.8 MB]

[Touch-packages] [Bug 1374825] Re: VDPAU does not work in libav on Utopic

2020-07-21 Thread Sebastian Ramacher

Please provide a log of vlc -vvv.

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

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

Title:
  VDPAU does not work in libav on Utopic

Status in libav package in Ubuntu:
  Invalid
Status in mplayer package in Ubuntu:
  Confirmed
Status in mplayer2 package in Ubuntu:
  Confirmed
Status in mpv package in Ubuntu:
  Invalid
Status in vlc package in Ubuntu:
  Incomplete

Bug description:
  After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU
  support has stopped working in all applications that use libav.  In
  mplayer2, it prints "Cannot find codec 'h264_vdpau' in libavcodec..."
  and in VLC I get "[7f909958] vdpau_avcodec generic error:
  decoder profile not supported: 6".

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

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

[Touch-packages] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path

2020-07-21 Thread Michael Hudson-Doyle

** Description changed:

- ssh can't call a binary from a snap, it will only work using the full
- path.
+ [impact]
+ ssh can't call a binary from a snap, it will only work using the full path.
+ 
+ [test case]
+ Create a container. Install the go snap (and make sure golang-go is not 
installed). Run "ssh  go version" and check the binary is found.
+ 
+ [regression potential]
+ It's a pam change an they are always a bit scary but the code follows the 
existing pattern for updating PATH in /etc/environment and has been tested in 
groovy.
+ 
+ [original description]
  
  Let's say I have the hello snap installed in 192.168.122.24. Then:
  
  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
  elopio@192.168.122.24's password:
  bash: hello: command not found
  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
  elopio@192.168.122.24's password:
  Hello, world!

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

Title:
  ssh can't call a binary from a snap without the full path

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  New
Status in openssh source package in Xenial:
  New
Status in pam source package in Xenial:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in openssh source package in Bionic:
  New
Status in pam source package in Bionic:
  New
Status in livecd-rootfs source package in Focal:
  New
Status in openssh source package in Focal:
  New
Status in pam source package in Focal:
  New
Status in livecd-rootfs source package in Groovy:
  Fix Released
Status in openssh source package in Groovy:
  Confirmed
Status in pam source package in Groovy:
  Fix Released
Status in openssh package in Debian:
  New

Bug description:
  [impact]
  ssh can't call a binary from a snap, it will only work using the full path.

  [test case]
  Create a container. Install the go snap (and make sure golang-go is not 
installed). Run "ssh  go version" and check the binary is found.

  [regression potential]
  It's a pam change an they are always a bit scary but the code follows the 
existing pattern for updating PATH in /etc/environment and has been tested in 
groovy.

  [original description]

  Let's say I have the hello snap installed in 192.168.122.24. Then:

  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
  elopio@192.168.122.24's password:
  bash: hello: command not found
  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
  elopio@192.168.122.24's password:
  Hello, world!

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

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

[Touch-packages] [Bug 1374825] Re: VDPAU does not work in libav on Utopic

2020-07-21 Thread Dale Taylor

Can confirm that this is affecting VLC as well.

** Changed in: vlc (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  VDPAU does not work in libav on Utopic

Status in libav package in Ubuntu:
  Invalid
Status in mplayer package in Ubuntu:
  Confirmed
Status in mplayer2 package in Ubuntu:
  Confirmed
Status in mpv package in Ubuntu:
  Invalid
Status in vlc package in Ubuntu:
  Confirmed

Bug description:
  After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU
  support has stopped working in all applications that use libav.  In
  mplayer2, it prints "Cannot find codec 'h264_vdpau' in libavcodec..."
  and in VLC I get "[7f909958] vdpau_avcodec generic error:
  decoder profile not supported: 6".

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

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

[Touch-packages] [Bug 1886300] Re: rename.ul refuses to rename links that don't resolve (regression)

2020-07-21 Thread Mauricio Faria de Oliveira

Hi Seyeong,

Thanks for the debdiffs! 
They look good in general but need a few fixes:

1) groovy-proposed has util-linux 2.35.2-9ubuntu1 (debdiff used groovy-
updates / 2.35.2-7ubuntu3)

2) the DEP3 headers should be before a triple-dash "---" line per [1].
   I'd suggest moving it to before/after the git format-patch headers.

3) Could you please report a bug to Debian and add the Bug-Debian DEP3 header?
   Debian sid/unstable is still on 2.35.2-8 (fix landed in v2.36-rc2).
   No need to wait on them, but just have the bug reported there too.

Did you build this on Launchpad PPAs? 
Sometimes there are differences to local build environments that lead
to "interesting" issues to debug when it builds on PPAs. :-)

[1] https://dep-team.pages.debian.net/deps/dep3/
"A line containing 3 dashes (---) should stop the parsing: lines after it are 
not relevant part of the meta-information."

Thanks,
Mauricio

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

Title:
  rename.ul refuses to rename links that don't resolve (regression)

Status in util-linux package in Ubuntu:
  Confirmed
Status in util-linux source package in Focal:
  Confirmed
Status in util-linux source package in Groovy:
  Confirmed

Bug description:
  [Impact]

  rename.ul refuses to rename links that don't resolve.

  bionic rename.ul renames links whether or not they resolve (util-linux
  2.31.1-0.4ubuntu3.6).

  focal rename.ul refuses to rename links that don't resolve
  (regression) (util-linux 2.34-0.1ubuntu9).

  Eoan is EOL, so removed.

  
  [Test case]

  Commit has good test case. I paste it here

  Before:

$ touch file-found
$ ln -s file-found symlink-1
$ ./rename sym symbolic- symlink-1  # XPASS.
$ echo $?
0

$ ln -s file-not-found symlink-2
$ ./rename sym symbolic- symlink-2  # FAIL! REGRESSION.
rename: symlink-2: not accessible: No such file or directory
$ echo $?
1

$ ./rename sym symbolic- symlink-3  # XFAIL.
rename: symlink-3: not accessible: No such file or directory
$ echo $?
1

$ touch file-found
$ ./rename found existing file-found# XPASS.
$ echo $?
0

$ ./rename found existing file-not-found # XFAIL.
rename: file-not-found: not accessible: No such file or directory
$ echo $?
1

  After:

$ touch file-found
$ ln -s file-found symlink-1
$ ./rename sym symbolic- symlink-1  # XPASS.
$ echo $?
0

$ ln -s file-not-found symlink-2
$ ./rename sym symbolic- symlink-2  # PASS! REGRESSION FIXED.
$ echo $?
0

$ ./rename sym symbolic- symlink-3  # XFAIL.
rename: symlink-3: not accessible: No such file or directory
$ echo $?
1

$ touch file-found
$ ./rename found existing file-found# XPASS.
$ echo $?
0

$ ./rename found existing file-not-found # XFAIL.
rename: file-not-found: not accessible: No such file or directory
$ echo $?
1

  
  [Regression Potential]
  This commit changes code that checking accessibility to file or sym link. 
  If this fails, rename command will not work properly.it could be crashed or 
causes failure of rename. 

  
  [Original Description]

  rename.ul refuses to rename links that don't resolve.

  bionic rename.ul renames links whether or not they resolve (util-linux
  2.31.1-0.4ubuntu3.6).

  focal rename.ul refuses to rename links that don't resolve
  (regression) (util-linux 2.34-0.1ubuntu9).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: util-linux 2.34-0.1ubuntu9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jul  4 20:38:06 2020
  InstallationDate: Installed on 2020-04-05 (90 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1837734] Re: libnss3 reads fips_enabled flag and automatically switches to FIPS mode

2020-07-21 Thread Brian Murray

I'm setting this to Won't Fix as it seems unnecessary based off a later
comment about Firefox. Additionally, the the version of nss with the fix
for this bug was superseded by a security upload.

** Changed in: nss (Ubuntu Bionic)
   Status: Fix Committed => Won't Fix

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

Title:
  libnss3 reads fips_enabled flag and automatically switches to FIPS
  mode

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Xenial:
  Won't Fix
Status in nss source package in Bionic:
  Won't Fix
Status in nss source package in Disco:
  Won't Fix
Status in nss source package in Eoan:
  Fix Released

Bug description:
  [IMPACT]
  nss is not a FIPS certified library. On a machine running FIPS enabled 
kernel, the library by default goes into FIPS mode if 
/proc/sys/crypto/fips_enabled=1. This is an untested configuration and since 
libnss3 is not a certified library we propose disabling reading the 
'fips_enabled' flag and therefore switching the library automatically into FIPS 
mode. 

  The proposed patch disables reading the /proc/sys/crypto/fips_enabled
  flag. The users of the library however can force nss into FIPS mode
  via an environment variable. We plan to leave it as is so as not to
  regress existing users who may be using it.

  The issue impacts libnss3 versions in eoan, disco, bionic and xenial.

  lsb_release -rd
  Description:  Ubuntu Eoan Ermine (development branch)
  Release: 19.10

  Version: 2:3.45-1ubuntu1

  lsb_release -rd
  Description: Ubuntu Disco Dingo
  Release: 19.04

  Version: 2:3.42-1ubuntu2

  lsb_release -rd
  Description:  Ubuntu Bionic Beaver
  Release:  18.04

  Version: 2:3.35-2ubuntu2.3

  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Version: 2:3.28.4-0ubuntu0.16.04

  [FIX]
  This fix proposes to disable libnss3 reading proc/sys/crypto/fips_enabled. We 
only want fips certified modules reading this file and running in fips mode. 
libnss3 is not one of our fips certified modules, so should not be reading this 
along with our fips certified modules to determine whether to run in fips mode.

  Users who do want to run the library in FIPS mode can do so by using
  the environment variable "NSS_FIPS". We propose to leave it as is so
  as not to regress anyone using this. The user who is using this option
  should be doing so with the awareness.

  [TEST]
  Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in 
FIPS mode. With the patch fix no crashes were observed when launching firefox 
browser.
  Without the patch fix, firefox crashes.

  Tested on a xenial and bionic desktop ISO running non-FIPS generic
  kernel. With the patch fix, firefox worked as expected and no changes
  were observed.

  [REGRESSION POTENTIAL]
  The regression potential for this is small. A FIPS kernel is required to
  create /proc/sys/crypto/fips_enabled and it is not available in standard 
ubuntu archive. For users forcing FIPS through environment variable, nothing 
has changed.

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

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

[Touch-packages] [Bug 1885562] Re: [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode

2020-07-21 Thread Brian Murray

Hello Dariusz, or anyone else affected,

Accepted nss into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nss/2:3.35-2ubuntu2.10
in a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-bionic

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

Title:
  [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Bionic:
  Fix Committed
Status in nss source package in Focal:
  Fix Committed
Status in nss source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * Prevents using some parts of nss in FIPS mode - e.g.
  libfreeblpriv3.so (failed asserts). The library during initialization
  tries to verify it's own binaries against signatures in chk files
  shipped along with it (created at build time). They are installed at
  /usr/lib/$(DEB_HOST_MULTIARCH)/nss while it tries to look for them at
  /usr/lib/$(DEB_HOST_MULTIARCH).

  [Test Case]

   * Setup Ubuntu 18.04 in FIPS mode.
   * sudo apt install chrony
   * sudo chronyd -d
   * chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed.

  [Regression Potential]

   * Fix introduces 2 new artifacts to the filesystem (symlinks to the
  chk files). It may cause alerts in e.g. CI systems.

  [Other Info]
  Original bug description:

  In FIPS mode there are some additional checks performed.

  They lead to verifying binaries signatures. Those signatures are
  shipped in the libnss3 package as *.chk files installed in
  /usr/lib/$(DEB_HOST_MULTIARCH)/nss. Along with those files are the
  libraries themselves (libfreebl3.so  libfreeblpriv3.so  libnssckbi.so
  libnssdbm3.so  libsoftokn3.so).

  Those libraries are symlinked to be present in /usr/lib/$(DEB_HOST_MULTIARCH):
  ls -l /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so
  lrwxrwxrwx 1 root root 21 Jun 10 18:54 
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so

  The client binaries are linked against the symlinks, so when the verification 
happens (lib/freebl/shvfy.c) the mkCheckFileName function takes path to the 
symlink to the shlib and replaces the .so extension with .chk.
  Then it tries to open that file. Obviosly it fails, because the actual file 
is in /usr/lib/$(DEB_HOST_MULTIARCH)/nss.

  [Test case]
  sudo apt install chrony
  sudo chronyd -d
  chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed.

  Potential solutions:
  Solution A:
  Drop the /usr/lib/$(DEB_HOST_MULTIARCH)/nss directory and put all signatures 
and libs in /usr/lib/$(DEB_HOST_MULTIARCH).

  Solution B:
  Create symlinks to *.chk files in /usr/lib/$(DEB_HOST_MULTIARCH) (like it is 
done for *.so).

  Solution C:
  Implement and upstream NSS feature of resolving symlinks and looking for 
*.chk where the symlinks lead to.

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

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

[Touch-packages] [Bug 1885562] Re: [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode

2020-07-21 Thread Brian Murray

Hello Dariusz, or anyone else affected,

Accepted nss into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/nss/2:3.49.1-1ubuntu1.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: nss (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  [fips] freebl_fipsSoftwareIntegrityTest fails in FIPS mode

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Bionic:
  Fix Committed
Status in nss source package in Focal:
  Fix Committed
Status in nss source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * Prevents using some parts of nss in FIPS mode - e.g.
  libfreeblpriv3.so (failed asserts). The library during initialization
  tries to verify it's own binaries against signatures in chk files
  shipped along with it (created at build time). They are installed at
  /usr/lib/$(DEB_HOST_MULTIARCH)/nss while it tries to look for them at
  /usr/lib/$(DEB_HOST_MULTIARCH).

  [Test Case]

   * Setup Ubuntu 18.04 in FIPS mode.
   * sudo apt install chrony
   * sudo chronyd -d
   * chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed.

  [Regression Potential]

   * Fix introduces 2 new artifacts to the filesystem (symlinks to the
  chk files). It may cause alerts in e.g. CI systems.

  [Other Info]
  Original bug description:

  In FIPS mode there are some additional checks performed.

  They lead to verifying binaries signatures. Those signatures are
  shipped in the libnss3 package as *.chk files installed in
  /usr/lib/$(DEB_HOST_MULTIARCH)/nss. Along with those files are the
  libraries themselves (libfreebl3.so  libfreeblpriv3.so  libnssckbi.so
  libnssdbm3.so  libsoftokn3.so).

  Those libraries are symlinked to be present in /usr/lib/$(DEB_HOST_MULTIARCH):
  ls -l /usr/lib/x86_64-linux-gnu/libfreeblpriv3.so
  lrwxrwxrwx 1 root root 21 Jun 10 18:54 
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so

  The client binaries are linked against the symlinks, so when the verification 
happens (lib/freebl/shvfy.c) the mkCheckFileName function takes path to the 
symlink to the shlib and replaces the .so extension with .chk.
  Then it tries to open that file. Obviosly it fails, because the actual file 
is in /usr/lib/$(DEB_HOST_MULTIARCH)/nss.

  [Test case]
  sudo apt install chrony
  sudo chronyd -d
  chronyd: util.c:373 UTI_IPToRefid: Assertion `MD5_hash >= 0' failed.

  Potential solutions:
  Solution A:
  Drop the /usr/lib/$(DEB_HOST_MULTIARCH)/nss directory and put all signatures 
and libs in /usr/lib/$(DEB_HOST_MULTIARCH).

  Solution B:
  Create symlinks to *.chk files in /usr/lib/$(DEB_HOST_MULTIARCH) (like it is 
done for *.so).

  Solution C:
  Implement and upstream NSS feature of resolving symlinks and looking for 
*.chk where the symlinks lead to.

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

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

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

Alright. +1 on you last comment. Thanks for the feedback! I'll work on
that!

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output

This bug was fixed in the package linux-oem - 4.15.0-1093.103

---
linux-oem (4.15.0-1093.103) bionic; urgency=medium

  * bionic/linux-oem: 4.15.0-1093.103 -proposed tracker (LP: #1887026)

  * [SRU] plug headset won't proper reconfig ouput to it on machine with default
output (LP: #1882248)
- SAUCE: ALSA: hda - let hs_mic be picked ahead of hp_mic

  * Freezing on boot since kernel 4.15.0-72-generic release (LP: #1856387)
- x86/timer: Don't skip PIT setup when APIC is disabled or in legacy mode

  [ Ubuntu: 4.15.0-112.113 ]

  * bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * CVE-2020-11935
- SAUCE: aufs: do not call i_readcount_inc()
- SAUCE: aufs: bugfix, IMA i_readcount
  * CVE-2020-10757
- mm: Fix mremap not considering huge pmd devmap
  * Update lockdown patches (LP: #1884159)
- efi/efi_test: Lock down /dev/efi_test and require CAP_SYS_ADMIN
- efi: Restrict efivar_ssdt_load when the kernel is locked down
- powerpc/xmon: add read-only mode
- powerpc/xmon: Restrict when kernel is locked down
- [Config] CONFIG_XMON_DEFAULT_RO_MODE=y
- SAUCE: acpi: disallow loading configfs acpi tables when locked down
  * seccomp_bpf fails on powerpc (LP: #1885757)
- SAUCE: selftests/seccomp: fix ptrace tests on powerpc
  * Introduce the new NVIDIA 418-server and 440-server series, and update the
current NVIDIA drivers (LP: #1881137)
- [packaging] add signed modules for the 418-server and the 440-server
  flavours

  [ Ubuntu: 4.15.0-111.112 ]

  * bionic/linux: 4.15.0-111.112 -proposed tracker (LP: #1886999)
  * Bionic update: upstream stable patchset 2020-05-07 (LP: #1877461)
- SAUCE: mlxsw: Add missmerged ERR_PTR hunk
  * linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimited memory leak of v2 cgroups"

 -- Kelsey Skunberg   Tue, 14 Jul 2020
12:21:34 -0600

** Changed in: linux-oem (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

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

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

Title:
  [SRU] plug headset won't proper reconfig ouput to it on machine with
  default output

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  This is for pulseaudio bionic:

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, the active profile is Off, after users plug a
  headset to it and users select the headset from the pop-up dialogue,
  users expect the profile changes to analog-stereo (headset is on it),
  but the active_profile is still Off.

  [Fix]
  Upstream already has a patch to fix it, cherrypiack that patch to bionic.
  And that patch is already in the eoan, focal, ...

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and select the headset from UI, the profile changes to
  analog-stereo, and play some sound, we could hear it from the headset

  [Regression Risk]
  Low, this patch is already in the upstream for a long time, and it is
  already in the eoan and focal.


  
  For linux kernel (oem-b):

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, and users plug a headset, the sound couldn't
  output from headset.

  [Fix]
  reverse the order of headset mic and headphone mic

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and play sound, we could hear the sound from headset.

  [Regression Risk]
  Low, this patch only affects the machine without internal mic and
  internal spk, and I already tested this patch on the machine without
  internal mic and internal spk, it worked well.

  target machine does not have built-in speaker, and the monitor does
  not have an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions

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

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

2020-07-21 Thread Ryan Harper

@Rafael

It's in both places:

https://github.com/koverstreet/bcache-tools/pull/1

I can update the PR there as well; though I don't think upstream cares
as Kent's working on bcachefs instead of bcache AFAICT.

> I see that you are trying to come up with something nor relying in the
kernel fix (to throw the variables again after pivot root, etc..)

I think after the systemd discussion upstream:
 
https://github.com/systemd/systemd/pull/16317

The kernel uevent for CACHED_UUID isn't the right way to go long term;
all of the information we want is present in the superblock of the
devices as they are probed;   If we have a 69-bcache.rules with a helper
that uses bcache-super-show; we could drop the Ubuntu sauce patch we
have; it's just noise (and now it's somewhat unreliable, this bug shows
that).

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

And now, after reading it all, I do follow your comment:

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941/comments/47

with the proposed changed. As you're probably not fully dedicated to
this, and I can be, I'll give your suggestions a try, possibly among
with other things, and post findings here with how I think we should
move (considering upstream hasn't been very eager to fix this
situation).

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1888422] Re: Notebook suspends during boot when booting with lid closed

2020-07-21 Thread pabouk

It looks like the suspend is initiated during GDM session
initialization. From syslog:

...
ul 21 20:48:46 delfin /usr/lib/gdm3/gdm-x-session[1635]: (II) event2  - Power 
Button: is tagged by udev as: Keyboard
Jul 21 20:48:46 delfin /usr/lib/gdm3/gdm-x-session[1635]: (II) event2  - Power 
Button: device is a keyboard
Jul 21 20:48:46 delfin /usr/lib/gdm3/gdm-x-session[1635]: (II) event2  - Power 
Button: device removed
Jul 21 20:48:46 delfin /usr/lib/gdm3/gdm-x-session[1635]: (**) Option 
"config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
Jul 21 20:48:46 delfin /usr/lib/gdm3/gdm-x-session[1635]: (II) XINPUT: Adding 
extended input device "Power Button" (type: KEYBOARD, id 6)
Jul 21 20:48:46 delfin /usr/lib/gdm3/gdm-x-session[1635]: (**) Option 
"xkb_model" "pc105"
Jul 21 20:48:46 delfin /usr/lib/gdm3/gdm-x-session[1635]: (**) Option 
"xkb_layout" "cz"
Jul 21 20:48:46 delfin /usr/lib/gdm3/gdm-x-session[1635]: (**) Option 
"xkb_variant" "qwerty"
Jul 21 20:48:46 delfin NetworkManager[1343]:   [1595357326.2138] manager: 
sleep: sleep requested (sleeping: no  enabled: yes)
Jul 21 20:48:46 delfin NetworkManager[1343]:   [1595357326.2139] device 
(DC:F7:56:55:02:9B): state change: disconnected -> unmanaged (reason 
'sleeping', sys-iface-state: 'managed')
Jul 21 20:48:46 delfin NetworkManager[1343]:   [1595357326.2144] device 
(p2p-dev-wlp4s0): state change: disconnected -> unmanaged (reason 'sleeping', 
sys-iface-state: 'managed')
Jul 21 20:48:46 delfin NetworkManager[1343]:   [1595357326.2147] manager: 
NetworkManager state is now ASLEEP
Jul 21 20:48:46 delfin systemd[1]: Reached target Sleep.
Jul 21 20:48:46 delfin systemd[1]: Starting Suspend...
Jul 21 20:48:46 delfin systemd-sleep[1804]: Suspending system...
Jul 21 20:48:46 delfin kernel: [  151.307227] PM: suspend entry (deep)
Jul 21 20:48:46 delfin /usr/lib/gdm3/gdm-x-session[1635]: (II) event2  - Power 
Button: is tagged by udev as: Keyboard
Jul 21 20:48:46 delfin /usr/lib/gdm3/gdm-x-session[1635]: (II) event2  - Power 
Button: device is a keyboard
...

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

Title:
  Notebook suspends during boot when booting with lid closed

Status in systemd package in Ubuntu:
  New

Bug description:
  When I am booting notebook with external monitor connected (either
  directly or through a docking station) and the lid closed I enter the
  full disk encryption password and a moment later the notebook goes to
  suspend state (suspend to RAM) before the GDM login screen shows up on
  the monitor. When I wake the notebook using the power button on the
  docking station (the lid is still closed) everything then works
  correctly.

  It does not matter if the power supply is connected or not.

  The problem shows up in over 95% of cases. (At least once the notebook
  booted normally.)

  The Ubuntu was originally installed in version 19.10 then upgraded to
  20.04. The problem was present in the version 19.10 already. No power
  management or booting changes done outside of the standard GUI
  configuration tools. It is installed in UEFI mode on Lenovo ThinkPad
  T540p.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 21 21:02:56 2020
  InstallationDate: Installed on 2020-01-06 (196 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20BFS0JJ04
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: Upgraded to focal on 2020-04-23 (88 days ago)
  dmi.bios.date: 08/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET89WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BFS0JJ04
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMET89WW(2.37):bd08/23/2019:svnLENOVO:pn20BFS0JJ04:pvrThinkPadT540p:rvnLENOVO:rn20BFS0JJ04:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T540p

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

@raharper,

quick question... I see that you are trying to come up with something
nor relying in the kernel fix (to throw the variables again after pivot
root, etc..)

https://github.com/g2p/bcache-tools/pull/29/#issue-169277283

why are you merging in

"github.com/g2p" ? and not in "github.com/koverstreet" ?

which one is the "current official ?"

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied

2020-07-21 Thread Bob Morane

Same problem encountered on Ubuntu 20.04.

Fixed after I ran
`sudo systemctl mask isc-dhcp-server6.service`

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

Title:
  isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid:
  Permission denied

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 14-10 to 15-04, and now see the following in
  syslog:

  Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 
audit(1430045408.725:8): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1  capname="dac_ove
  rride"
  Apr 26 10:50:08 server sh[8619]: Can't create PID file 
/run/dhcp-server/dhcpd.pid: Permission denied.

  Description:Ubuntu 15.04
  Release:15.04

  isc-dhcp-server:
Installed: 4.3.1-5ubuntu2

  --- 8x -

  # cat /etc/default/isc-dhcp-server

  # Defaults for isc-dhcp-server initscript
  # sourced by /etc/init.d/isc-dhcp-server
  # installed at /etc/default/isc-dhcp-server by the maintainer scripts

  #
  # This is a POSIX shell fragment
  #

  # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
  #DHCPD_CONF=/etc/dhcp/dhcpd.conf

  # Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
  #DHCPD_PID=/var/run/dhcpd.pid

  # Additional options to start dhcpd with.
  #   Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
  #OPTIONS=""

  # On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
  #   Separate multiple interfaces with spaces, e.g. "eth0 eth1".
  INTERFACES=""

  --- 8x -

  # ls -la /var/run
  lrwxrwxrwx 1 root root 4 Oct 24  2013 /var/run -> /run

  # ls -la /run/dhcp-server/
  total 0
  drwxr-xr-x  2 dhcpd dhcpd   40 Apr 26 10:59 .
  drwxr-xr-x 34 root  root  1060 Apr 26 11:33 ..

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

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

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

@raharper,

Great to know.. thanks! I'm in the "reading phase".. I think I managed
to read all the history until now.. now I'm reading your analysis for
this bug more carefully, knowing the history...

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

Status from old attempts to solve same nature issues:



Older (2018) merge request from @raharper:

https://github.com/koverstreet/bcache-tools/pull/1

addressing the fact that kernel uevents would not always emit 
CACHED_UUID parameters, making udev to delete (whenever that happens) 
/dev/bcache/{by-uuid,by-label} symlinks.

This last MR pointed to previous related bugs:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890446
https://bugs.launchpad.net/curtin/+bug/1728742

And to an upstream kernel patch:

https://lore.kernel.org/patchwork/patch/921298/

to

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145

that wasn't accepted upstream.

Even not being accepted upstream, the SRU was attempted:

LP: #1729145

https://lists.ubuntu.com/archives/kernel-team/2017-December/088680.html
https://lists.ubuntu.com/archives/kernel-team/2017-December/088679.html

Both were NACKED.

Attempted again:

https://lists.ubuntu.com/archives/kernel-team/2017-December/088682.html
https://lists.ubuntu.com/archives/kernel-team/2017-December/088683.html

NACKED again.

And a v2 was sent:

https://lists.ubuntu.com/archives/kernel-team/2017-December/088751.html
https://lists.ubuntu.com/archives/kernel-team/2017-December/088750.html
https://lists.ubuntu.com/archives/kernel-team/2017-December/088749.html

and acked in January 2018 by Coling:

https://lists.ubuntu.com/archives/kernel-team/2018-January/089492.html

but not upstreamed.

BIONIC contains the fix:

commit ed9333e1b583
Author: Ryan Harper 
Date:   Mon Dec 11 12:12:01 2017

UBUNTU: SAUCE: (no-up) bcache: decouple emitting a cached_dev CHANGE uevent

BugLink: http://bugs.launchpad.net/bugs/1729145

- decouple emitting a cached_dev CHANGE uevent which includes dev.uuid
  and dev.label from bch_cached_dev_run() which only happens when a
  bcacheX device is bound to the actual backing block device (bcache0 -> 
vdb)

- update bch_cached_dev_run() to invoke bch_cached_dev_emit_change() as
  needed; no functional code path changes here

- Modify register_bcache to detect a re-registering of a bcache
  cached_dev, and in that case call bcache_cached_dev_emit_change() to

Signed-off-by: Ryan Harper 
Signed-off-by: Joseph Salisbury 
Acked-by: Colin Ian King 
Acked-by: Stefan Bader 
Signed-off-by: Khalid Elmously 
[ saf: fix incorrect indentation ]
Signed-off-by: Seth Forshee 

FOCAL contains the fix:

commit 67553dcd7905
Author: Ryan Harper 
Date:   Mon Dec 11 12:12:01 2017

UBUNTU: SAUCE: (no-up) bcache: decouple emitting a cached_dev CHANGE
uevent

GROOVY contains the fix:

commit 67553dcd7905
Author: Ryan Harper 
Date:   Mon Dec 11 12:12:01 2017

UBUNTU: SAUCE: (no-up) bcache: decouple emitting a cached_dev CHANGE
uevent



So, the kernel patch wasn't accepted, nor bcache-tools patch by 
@raharper, the bcache-export-cached.



New Upstream summary from @raharper:

https://github.com/systemd/systemd/pull/16317#issuecomment-655647313

in the upstream merge request made by @rbalint.


** Bug watch added: Debian Bug tracker #890446
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890446

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or

[Touch-packages] [Bug 1888422] Re: Notebook suspends during boot when booting with lid closed

2020-07-21 Thread pabouk

I am sorry for the misinformation. Now I see I originally installed
Ubuntu in the version 19.10 then upgraded it to 20.04. The problem was
present in the version 19.10 already.

** Description changed:

  When I am booting notebook with external monitor connected (either
  directly or through a docking station) and the lid closed I enter the
  full disk encryption password and a moment later the notebook goes to
  suspend state (suspend to RAM) before the GDM login screen shows up on
  the monitor. When I wake the notebook using the power button on the
  docking station (the lid is still closed) everything then works
  correctly.
  
  It does not matter if the power supply is connected or not.
  
  The problem shows up in over 95% of cases. (At least once the notebook
  booted normally.)
  
- It is the clean installation of Ubuntu 20.04 no power management or
- booting changes done outside of the standard GUI configuration tools. It
- is installed in UEFI mode on Lenovo ThinkPad T540p.
+ The Ubuntu was originally installed in version 19.10 then upgraded to
+ 20.04. The problem was present in the version 19.10 already. No power
+ management or booting changes done outside of the standard GUI
+ configuration tools. It is installed in UEFI mode on Lenovo ThinkPad
+ T540p.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 21 21:02:56 2020
  InstallationDate: Installed on 2020-01-06 (196 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20BFS0JJ04
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=cs_CZ.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=cs_CZ.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
-  [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
-  [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
-  
-  2 overridden configuration files found.
+  [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
+  [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
+ 
+  2 overridden configuration files found.
  UpgradeStatus: Upgraded to focal on 2020-04-23 (88 days ago)
  dmi.bios.date: 08/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET89WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BFS0JJ04
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMET89WW(2.37):bd08/23/2019:svnLENOVO:pn20BFS0JJ04:pvrThinkPadT540p:rvnLENOVO:rn20BFS0JJ04:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T540p
  dmi.product.name: 20BFS0JJ04
  dmi.product.sku: LENOVO_MT_20BF
  dmi.product.version: ThinkPad T540p
  dmi.sys.vendor: LENOVO

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

Title:
  Notebook suspends during boot when booting with lid closed

Status in systemd package in Ubuntu:
  New

Bug description:
  When I am booting notebook with external monitor connected (either
  directly or through a docking station) and the lid closed I enter the
  full disk encryption password and a moment later the notebook goes to
  suspend state (suspend to RAM) before the GDM login screen shows up on
  the monitor. When I wake the notebook using the power button on the
  docking station (the lid is still closed) everything then works
  correctly.

  It does not matter if the power supply is connected or not.

  The problem shows up in over 95% of cases. (At least once the notebook
  booted normally.)

  The Ubuntu was originally installed in version 19.10 then upgraded to
  20.04. The problem was present in the version 19.10 already. No power
  management or booting changes done outside of the standard GUI
  configuration tools. It is installed in UEFI mode on Lenovo ThinkPad
  T540p.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4

[Touch-packages] [Bug 1888422] [NEW] Notebook suspends during boot when booting with lid closed

2020-07-21 Thread pabouk

Public bug reported:

When I am booting notebook with external monitor connected (either
directly or through a docking station) and the lid closed I enter the
full disk encryption password and a moment later the notebook goes to
suspend state (suspend to RAM) before the GDM login screen shows up on
the monitor. When I wake the notebook using the power button on the
docking station (the lid is still closed) everything then works
correctly.

It does not matter if the power supply is connected or not.

The problem shows up in over 95% of cases. (At least once the notebook
booted normally.)

The Ubuntu was originally installed in version 19.10 then upgraded to
20.04. The problem was present in the version 19.10 already. No power
management or booting changes done outside of the standard GUI
configuration tools. It is installed in UEFI mode on Lenovo ThinkPad
T540p.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 21 21:02:56 2020
InstallationDate: Installed on 2020-01-06 (196 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20BFS0JJ04
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf

 2 overridden configuration files found.
UpgradeStatus: Upgraded to focal on 2020-04-23 (88 days ago)
dmi.bios.date: 08/23/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: GMET89WW (2.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BFS0JJ04
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGMET89WW(2.37):bd08/23/2019:svnLENOVO:pn20BFS0JJ04:pvrThinkPadT540p:rvnLENOVO:rn20BFS0JJ04:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T540p
dmi.product.name: 20BFS0JJ04
dmi.product.sku: LENOVO_MT_20BF
dmi.product.version: ThinkPad T540p
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  Notebook suspends during boot when booting with lid closed

Status in systemd package in Ubuntu:
  New

Bug description:
  When I am booting notebook with external monitor connected (either
  directly or through a docking station) and the lid closed I enter the
  full disk encryption password and a moment later the notebook goes to
  suspend state (suspend to RAM) before the GDM login screen shows up on
  the monitor. When I wake the notebook using the power button on the
  docking station (the lid is still closed) everything then works
  correctly.

  It does not matter if the power supply is connected or not.

  The problem shows up in over 95% of cases. (At least once the notebook
  booted normally.)

  The Ubuntu was originally installed in version 19.10 then upgraded to
  20.04. The problem was present in the version 19.10 already. No power
  management or booting changes done outside of the standard GUI
  configuration tools. It is installed in UEFI mode on Lenovo ThinkPad
  T540p.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 21 21:02:56 2020
  InstallationDate: Installed on 2020-01-06 (196 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20BFS0JJ04
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

2020-07-21 Thread Ryan Harper

@Rafael

For bcache-tools changes, bcache-export-cached-uuid needs the full path
to bcache-super-show, as PATH is not exported when running from udev.

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

--- Comment From z...@us.ibm.com 2020-07-21 14:57 EDT---
It can be any NIC, or even lo device.
The fix2.txt has the example like this:
$ $TC qdisc add dev lo ingress
$ $TC filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32
$ $TC fitler add dev lo parent : prio 5 proto ip flower ip_proto tcp \
tcp_flags 0x909/f00

$ $TC filter show dev lo parent :
filter protocol ip pref 3 flower chain 0
filter protocol ip pref 3 flower chain 0 handle 0x1
eth_type ipv4
ip_tos 0x8/32
not_in_hw
filter protocol ip pref 5 flower chain 0
filter protocol ip pref 5 flower chain 0 handle 0x1
eth_type ipv4
ip_proto tcp
tcp_flags 0x909/f00  /* <--- */

-- 
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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

Alright, summarizing this so far, we have the following fixes landed in
Groovy:

udev (systemd pkg):

- 60-persistent-storage.rules: skip_bcache_fs_type:
  - /dev/disk/by-uuid/_ and /dev/disk/by-label/_ not created for bcache devs

Since it does not make sense to have the caching device symlink like if
it was a regular filesystem disk to be used:

(k)rafaeldtinoco@bcache:~$ ls -lah /dev/disk/by-uuid
total 0
drwxr-xr-x 2 root root 100 Jul 21 18:49 .
drwxr-xr-x 7 root root 140 Jul 21 17:39 ..
lrwxrwxrwx 1 root root  10 Jul 21 17:39 022E-07E1 -> ../../vda1
lrwxrwxrwx 1 root root  13 Jul 21 18:49 50b98f0d-c0e0-49d2-9856-8ac6bc91e232 -> 
../../bcache0
lrwxrwxrwx 1 root root  10 Jul 21 17:39 67993d4f-fa55-49b1-886e-c692f88393ba -> 
../../vda2

- 69-bcache.rules:
  - if any other driver - than bcache - touches /dev/bcache[0-9]*
bcache/by-uuid/_ (BCACHE_CACHED_UUID and LABEL) symlinks are
recreated.

To address the udev event responsible for wiping /dev/bcache/by-uuid,
like:

KERNEL[4175.725930] change   /devices/virtual/block/bcache0 (block)
ACTION=change
DEVPATH=/devices/virtual/block/bcache0
SUBSYSTEM=block
SYNTH_UUID=0
DEVNAME=/dev/bcache0
DEVTYPE=disk
SEQNUM=6746
MAJOR=251
MINOR=0
 
UDEV  [4175.758078] change   /devices/virtual/block/bcache0 (block)
ACTION=change
DEVPATH=/devices/virtual/block/bcache0
SUBSYSTEM=block
SYNTH_UUID=0
DEVNAME=/dev/bcache0
DEVTYPE=disk
SEQNUM=6746
USEC_INITIALIZED=4151438558
ID_FS_UUID=50b98f0d-c0e0-49d2-9856-8ac6bc91e232
ID_FS_UUID_ENC=50b98f0d-c0e0-49d2-9856-8ac6bc91e232
ID_FS_VERSION=1.0
ID_FS_TYPE=ext4
ID_FS_USAGE=filesystem
MAJOR=251
MINOR=0
DEVLINKS=/dev/disk/by-uuid/50b98f0d-c0e0-49d2-9856-8ac6bc91e232
TAGS=:systemd:

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

** No longer affects: util-linux (Ubuntu)

** No longer affects: bcache-tools (Ubuntu Groovy)

** Changed in: bcache-tools (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: bcache-tools (Ubuntu)
   Importance: High => Medium

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

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

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

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

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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-07-21 Thread Stefan Bader

Sorry this seems to have gotten list in translation. I already got the
one patch fixed up. What I need is some generic instructions to check
the result. Can one just use any pair of NICs or do they have to be
special?

-- 
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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

** No longer affects: linux-signed (Ubuntu Bionic)

** No longer affects: linux-signed (Ubuntu Groovy)

** No longer affects: linux-signed (Ubuntu Focal)

** No longer affects: linux (Ubuntu Groovy)

** Changed in: systemd (Ubuntu Groovy)
 Assignee: Balint Reczey (rbalint) => (unassigned)

** No longer affects: linux (Ubuntu Focal)

** No longer affects: linux (Ubuntu Bionic)

** Also affects: util-linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: bcache-tools (Ubuntu Groovy)
   Status: Triaged => Confirmed

** No longer affects: systemd (Ubuntu Groovy)

** Changed in: bcache-tools (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: bcache-tools (Ubuntu Bionic)
   Importance: Undecided => Medium

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

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

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1881972] Re: systemd-networkd crashes with invalid pointer

2020-07-21 Thread John Nielsen

No crashes on my test machine for 12 days. Push it!

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

Title:
  systemd-networkd crashes with invalid pointer

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

Bug description:
  [impact]

  systemd-networkd double-free causes crash under some circumstances,
  such as adding/removing ip rules

  [test case]

  see original description

  [regression potential]

  this strdup's strings during addition of routing policy rules, so any
  regression would likely occur when adding/modifying/removing ip rules,
  possibly including networkd segfault or failure to add/remove/modify
  ip rules.

  [scope]

  this is needed for bionic.

  this is fixed by upstream commit
  eeab051b28ba6e1b4a56d369d4c6bf7cfa71947c which is included starting in
  v240, so this is already included in Focal and later.

  I did not research what original commit introduced the problem, but
  the reporter indicates this did not happen for Xenial so it's unlikely
  this is a problem in Xenial or earlier.

  [original description]

  This is a serious regression with systemd-networkd that I ran in to
  while setting up a NAT router in AWS. The AWS AMI ubuntu/images/hvm-
  ssd/ubuntu-bionic-18.04-amd64-server-20200131 with
  systemd-237-3ubuntu10.33 does NOT have the problem, but the next most
  recent AWS AMI ubuntu/images/hvm-ssd/ubuntu-
  bionic-18.04-amd64-server-20200311 with systemd-including
  237-3ubuntu10.39 does.

  Also, a system booted from the (good) 20200131 AMI starts showing the
  problem after updating only systemd (to 237-3ubuntu10.41) and its
  direct dependencies (e.g. 'apt-get install systemd'). So I'm fairly
  confident that a change to the systemd package between
  237-3ubuntu10.33 and 237-3ubuntu10.39 introduced the problem and it is
  still present.

  On the NAT router I use three interfaces and have separate routing
  tables for admin and forwarded traffic. Things come up fine initially
  but every 30-60 minutes (DHCP lease renewal time?) one or more
  interfaces is reconfigured and most of the time systemd-networkd will
  crash and need to be restarted. Eventually the system becomes
  unreachable when the default crash loop backoff logic prevents the
  network service from being restarted at all. The log excerpt attached
  illustrates the crash loop.

  Also including the netplan and networkd config files below.

  # grep . /etc/netplan/*
  /etc/netplan/50-cloud-init.yaml:# This file is generated from information 
provided by the datasource.  Changes
  /etc/netplan/50-cloud-init.yaml:# to it will not persist across an instance 
reboot.  To disable cloud-init's
  /etc/netplan/50-cloud-init.yaml:# network configuration capabilities, write a 
file
  /etc/netplan/50-cloud-init.yaml:# 
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  /etc/netplan/50-cloud-init.yaml:# network: {config: disabled}
  /etc/netplan/50-cloud-init.yaml:network:
  /etc/netplan/50-cloud-init.yaml:version: 2
  /etc/netplan/50-cloud-init.yaml:ethernets:
  /etc/netplan/50-cloud-init.yaml:ens5:
  /etc/netplan/50-cloud-init.yaml:dhcp4: true
  /etc/netplan/50-cloud-init.yaml:match:
  /etc/netplan/50-cloud-init.yaml:macaddress: xx:xx:xx:xx:xx:xx
  /etc/netplan/50-cloud-init.yaml:set-name: ens5
  /etc/netplan/99_config.yaml:network:
  /etc/netplan/99_config.yaml:  version: 2
  /etc/netplan/99_config.yaml:  renderer: networkd
  /etc/netplan/99_config.yaml:  ethernets:
  /etc/netplan/99_config.yaml:ens6:
  /etc/netplan/99_config.yaml:  match:
  /etc/netplan/99_config.yaml:macaddress: yy:yy:yy:yy:yy:yy
  /etc/netplan/99_config.yaml:  dhcp4: true
  /etc/netplan/99_config.yaml:  dhcp4-overrides:
  /etc/netplan/99_config.yaml:use-routes: false
  /etc/netplan/99_config.yaml:ens7:
  /etc/netplan/99_config.yaml:  match:
  /etc/netplan/99_config.yaml:macaddress: zz:zz:zz:zz:zz:zz
  /etc/netplan/99_config.yaml:  mtu: 1500
  /etc/netplan/99_config.yaml:  dhcp4: true
  /etc/netplan/99_config.yaml:  dhcp4-overrides:
  /etc/netplan/99_config.yaml:use-mtu: false
  /etc/netplan/99_config.yaml:use-routes: false

  # grep . /etc/networkd-dispatcher/*/*
  /etc/networkd-dispatcher/configured.d/nat:#!/bin/bash
  /etc/networkd-dispatcher/configured.d/nat:# Do additional configuration for 
the inside and outside interfaces
  /etc/networkd-dispatcher/configured.d/nat:# route table used for 
forwarded/routed/natted traffic
  /etc/networkd-dispatcher/configured.d/nat:FWD_TABLE=99
  /etc/networkd-dispatcher/configured.d/nat:if [ "${IFACE}" = "ens6" ]; then
  /etc/networkd-dispatcher/configured.d/nat:  # delete link-local route for 
inside in default table

[Touch-packages] [Bug 1887732] Re: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

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

** Changed in: python3.8 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in eric package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  Confirmed
Status in python3.8 package in Ubuntu:
  Confirmed
Status in python3.8 package in Debian:
  New

Bug description:
  I was upgrading from 18.04 LTS to 20.04 LTS and this popped up. Not
  sure what else to say.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jul 15 17:38:05 2020
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2019-06-26 (385 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to focal on 2020-07-16 (0 days ago)

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

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

[Touch-packages] [Bug 1887732] Re: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

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

** Changed in: python3-defaults (Ubuntu)
   Status: New => Confirmed

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

Title:
  package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in eric package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  Confirmed
Status in python3.8 package in Ubuntu:
  Confirmed
Status in python3.8 package in Debian:
  New

Bug description:
  I was upgrading from 18.04 LTS to 20.04 LTS and this popped up. Not
  sure what else to say.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jul 15 17:38:05 2020
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2019-06-26 (385 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to focal on 2020-07-16 (0 days ago)

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

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

[Touch-packages] [Bug 1770961] Re: Add options to set the snappy refresh schedule

the bug here is probably the wrong place for those discussion, best to
move to some user forum instead. It's worth mentioning that snapd has a
configuration nowadays to respect limited connection and not waste data
in such cases (which was something mentioned in earlier comments)

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

Title:
  Add options to set the snappy refresh schedule

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Snappy has a feature where the user can state when in a month to
  refresh (update) their snaps. Please provide options in Software &
  Updates to control this.

  https://docs.snapcraft.io/system-options

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun May 13 15:10:07 2018
  InstallationDate: Installed on 2017-08-03 (282 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (21 days ago)

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

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

[Touch-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's

The warning you are copying are not related to your connectivity issue,
but the problem you describe seems rather one with wpasupplicant or with
the driver, I'm reassigning to the kernel

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

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1888390

Title:
  apparmor error causing deauthentication for certain SSID's

Status in linux package in Ubuntu:
  New

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)

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

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

[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

2020-07-21 Thread Ubuntu Foundations Team Bug Bot

The attachment "apport_42to43.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  New

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

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

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

[Touch-packages] [Bug 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan

2020-07-21 Thread Mirko Ducic

Hi guys,
I manually fixed this issue with bad GUI representation of process execution.
You have to remove some old or not any more synchronized repositories.
In terminal, execute command: sudo apt update

This will tell you witch repos are bad, examples:
E: The repository 'http://ppa.launchpad.net/somerville-dla-team/ppa/ubuntu
focal Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration
details.
-
E: The repository 'http://oem.archive.canonical.com/updates bionic-oem Release'
is not signed.
N: Updating from such a repository can't be done securely, and is therefore
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration
details.
W: GPG error: http://dell.archive.canonical.com/updates
bionic-dell-beaver-osp1-sansa Release: Detached signature file
'/var/lib/apt/lists/partial/dell.archive.canonical.com_updates_dists_bionic-dell-beaver-osp1-sansa_Release.gpg'
is in unsupported binary format
E: The repository 'http://dell.archive.canonical.com/updates
bionic-dell-beaver-osp1-sansa Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration
details.
W: GPG error: http://dell.archive.canonical.com/updates bionic-dell-service
Release: Detached signature file
'/var/lib/apt/lists/partial/dell.archive.canonical.com_updates_dists_bionic-dell-service_Release.gpg'
is in unsupported binary format
E: The repository 'http://dell.archive.canonical.com/updates
bionic-dell-service Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration
details.

Go to Software & Updates, card Other software, find and remove these
repositories (you have option for this, remove all with E (error)).

That's it. Do not expect to stuck at "Refreshing software cache" any
more.

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

Title:
Stuck at "Refreshing software cache" after enabling repository not
updated for Eoan

Status in software-properties package in Ubuntu:
Confirmed

Bug description:
Steps to reproduce:
1. Open Software and Updates
2. Go to "other software" and enable, for example, a repository disabled
during upgrade to Eoan which is not updated for Eoan yet
3. Press close and then reload on the dialog that opens.
4. Refreshing software cache dialog is stuck

After closing the dialogs by right clicking on the windows and the
open apps bar, re opening Software and updates only shows a white
square you can't interact with.

Ubuntu 19.10

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

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

[Touch-packages] [Bug 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic

2020-07-21 Thread Harry van Haaren (Intel)

Hi All,

I have enabled the bionic-proposed repo as described in link. OVS-master
is used for testing, containing the build-time binutils bug check as
described above.

1) Can confirm that old binutils version (2.30-21ubuntu1~18.04.3) had
issue, and OVS was correctly DISabling AVX512.

2) Can confirm that with -proposed binutils (2.30-21ubuntu1~18.04.4),
OVS build system is correctly ENabling AVX512 support, as linker checks
are passing.

After the configure step, I have tested OVS, running traffic and
enabling the AVX512 optimizations. It is working as expected, with
AVX512 instructions running in the datapath.

I believe you have already added the "verification-done" and bionic
versions Christian, so I'll not change the status... please let me know
if I misunderstood the process.

Thanks Robie & Christian for your support on this issue! -Harry

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

Title:
  fix non-8-bit x86 displacements breaking AVX512 builds on Bionic

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  Fix Committed
Status in binutils package in Debian:
  Confirmed

Bug description:
  [Impact]

   * the assembler scales non 8 bit cases which was identified
 to break e.g. some AVX512 code. It is nasty as it isn't a compile/link/ 
 time error. Instead the instructions might silently be corrupted until 
 running. Things might even work on some but fail on other systems if 
 e.g. the AVX code paths only run on newer chips.

* The fix is upstream for a while and not re-changed again. Furthermore 
  it is in several Ubuntu releases without bugs due to that, which should 
  make the backport rather safe.

  [Test Case]

   * Simple example to trigger the bug:

  echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d
  avx.o | grep vmovaps

  The expected output is that the objdump output matches the vmovaps
  instruction input. When using binutils with the bug, the initial 0x40
  will be incorrect.

  Working:
  $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | 
grep vmovaps
 0: 62 f1 7c 48 28 04 05 vmovaps 0x40(,%rax,1),%zmm0
  Failing:
  $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | 
grep vmovaps
 0: 62 f1 7c 48 28 04 05 vmovaps 0x1(,%rax,1),%zmm0

  [Regression Potential]

   * Well, this is a double edged sword. On one hand this is fortunately a 
 small change and only affects something formerly clearly broken. So it 
 should be good and only change cases formerly being bad.
 But OTOH binutils areused in so many cases that I feel unable to say
 "nothing will happen". The change goes to the gnu assembler, so that is 
 the place to look out for regressions.

  [Other Info]
   
   * needs a sponsor experienced with binutils to check potential pitfalls


  
  ---

  
  Hi,
  DPDK has run into some issues in the past
   https://bugs.dpdk.org/show_bug.cgi?id=97
   https://bugs.dpdk.org/show_bug.cgi?id=249

  Eventually the issues got resolved in binutils via
   https://sourceware.org/bugzilla/show_bug.cgi?id=23465

  After binutils is fixed people rebuilding DPDK themselve can use
   http://patches.dpdk.org/patch/71679/
  to gain more performance while on Bionics bintuils level.

  Note: Bionic is on DPDK 17.11.x which will not get further stable release 
afaik. But quite often people build their own DPDK. In fact this came up as a 
request from Openvswitch upstream/Intel to allow such builds on Bionic.
  I'd ping those people about the bug and ask them to participate in the 
verification if this becomes an SRU.

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

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

[Touch-packages] [Bug 1857036] Re: `sudo --login --user USERNAME` throws `setrlimit(RLIMIT_CORE): Operation not permitted` error when run inside a container.

2020-07-21 Thread Simon Déziel

[Test Case]
$ lxc launch ubuntu:20.04/amd64 sudo-sru-lp1857036-test
$ lxc shell sudo-sru-lp1857036-test

Reproduce the problem

root@sudo-sru-lp1857036-test:~# sudo true
sudo: setrlimit(RLIMIT_CORE): Operation not permitted

Enable -proposed and update

root@sudo-sru-lp1857036-test:~# apt install -V sudo
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
   sudo (1.8.31-1ubuntu1 => 1.8.31-1ubuntu1.1)
1 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
Need to get 513 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 sudo amd64 
1.8.31-1ubuntu1.1 [513 kB]
Fetched 513 kB in 1s (576 kB/s)
(Reading database ... 14621 files and directories currently installed.)
Preparing to unpack .../sudo_1.8.31-1ubuntu1.1_amd64.deb ...
Unpacking sudo (1.8.31-1ubuntu1.1) over (1.8.31-1ubuntu1) ...
Setting up sudo (1.8.31-1ubuntu1.1) ...

Check if the fix works

root@sudo-sru-lp1857036-test:~# sudo true
root@sudo-sru-lp1857036-test:~# 

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

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

Title:
  `sudo --login --user USERNAME` throws `setrlimit(RLIMIT_CORE):
  Operation not permitted` error when run inside a container.

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Focal:
  Fix Committed
Status in sudo source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Logging in as a sudo user in a Ubuntu Focal Linux container displays a
  warning:

    sudo: setrlimit(RLIMIT_CORE): Operation not permitted

  The warning is entirely unnecessary - the container is trying to adjust
  RLIMIT_CORE, but this isn't allowed inside a container anyway.

  While this is "just" a warning, logging into a container as sudo is a
  very common practice, so this warning risks creating confusion for LTS
  users.

  [Test Case]
  $ lxc launch ubuntu:20.04/amd64 sudo-sru-lp1857036-test
  $ lxc shell sudo-sru-lp1857036-test

  # sudo --login --user ubuntu
  sudo: setrlimit(RLIMIT_CORE): Operation not permitted
  To run a command as administrator (user "root"), use "sudo ".
  See "man sudo_root" for details.
  $ logout

  Enable -proposed and update
  # apt-get install sudo

  # sudo --login --user ubuntu
  $

  [Regression Potential]
  As this only affects printing of a couple warnings, the only behavioral
  change is in stderr output.

  [Discussion]
  This changes a couple warnings into equivalent debug printfs, which
  brings the sudo behavior in-line with the behavior in groovy, bionic,
  etc. and should cause no troubles.

  This patch originates from upstream, and is already in groovy's sudo
  package (which thus can be seen not to exhibit the issue).

  The upstream patch includes some new debug prints which should be
  harmless but are unnecessary to the fix so they've been removed.

  [Original Report]
  When using `sudo --login --user USERNAME` with Ubuntu Focal currently, it 
will correctly operate but it will also throw the following error before 
continuing with the logon process (which completes successfully except for the 
stated error):

  sudo: setrlimit(RLIMIT_CORE): Operation not permitted

  A full run of this was tested in a Focal LXD container after dropping
  to a root shell to reproduce (arstotzka is the host system, focal-test
  is the test container):

  teward@arstotzka:~$ lxc shell focal-test
  root@focal-test:~# sudo --login --user ubuntu
  sudo: setrlimit(RLIMIT_CORE): Operation not permitted
  To run a command as administrator (user "root"), use "sudo ".
  See "man sudo_root" for details.

  ubuntu@focal-test:~$

  This appears to be similar to this issue identified on RedHat's
  tracker: https://bugzilla.redhat.com/show_bug.cgi?id=1773148

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: sudo 1.8.29-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu14
  Architecture: amd64
  Date: Thu Dec 19 17:16:31 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/90-cloud-init-users: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

[Touch-packages] [Bug 1887655] Re: unattended-upgrades triggers reboot despite configuration

2020-07-21 Thread Philip Couling

sudo apt-config dump | grep -i reboot

Yielded no lines.

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

Title:
  unattended-upgrades triggers reboot despite configuration

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  I've been having problems with my Ubuntu machine suddenly rebooting
  without any warning.  To my knowledge Ubuntu Desktop is not supposed
  to reboot without warning by default.

  I believe this is being triggered by unattended-upgrades

  unattended-upgrades 2.3 (amd64)

  Ubuntu Desktop:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  One pattern that emerges is that the reboot happens right after
  unattended-upgrades completes successfully. There are multiple
  examples in my /var/log/syslog, but all show "unattended-
  upgrades.service: Succeeded." the same second everything begins to
  shut down, with nothing for a minute or two prior. Example:

  Jul 15 11:17:01 pc systemd[2065]: Starting Notification regarding a new 
release of Ubuntu...
  Jul 15 11:17:14 pc charon: 08[IKE] sending keep alive to 10.10.10.10[4500]
  Jul 15 11:17:22 pc check-new-release-gtk[71843]: 
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:30: PyGIWarning: Gtk was 
imported without specifying a version first. Use gi.require_version('Gtk'
  , '3.0') before import to ensure that the right version gets loaded.
  Jul 15 11:17:22 pc check-new-release-gtk[71843]:   from gi.repository import 
Gtk
  Jul 15 11:17:22 pc check-new-release-gtk[71843]: WARNING:root:timeout 
reached, exiting
  Jul 15 11:17:22 pc systemd[2065]: update-notifier-release.service: Succeeded.
  Jul 15 11:17:22 pc systemd[2065]: Finished Notification regarding a new 
release of Ubuntu.
  Jul 15 11:17:48 pc mysql-workbench[33350]: gtk_tree_view_unref_tree_helper: 
assertion 'node != NULL' failed
  Jul 15 11:17:54 pc charon: 09[IKE] sending keep alive to 10.10.10.10[4500]
  Jul 15 11:18:03 pc systemd[1]: unattended-upgrades.service: Succeeded.
  Jul 15 11:18:03 pc systemd[1]: Stopping Session 3 of user philip.
  Jul 15 11:18:03 pc systemd[1]: Removed slice 
system-clean\x2dmount\x2dpoint.slice.
  Jul 15 11:18:03 pc systemd[1]: Removed slice system-getty.slice.
  Jul 15 11:18:03 pc systemd[1]: Removed slice system-modprobe.slice.
  Jul 15 11:18:03 pc systemd[1]: Stopped target Block Device Preparation for 
/dev/mapper/ubuntu.
  Jul 15 11:18:03 pc systemd[2065]: Stopped target GNOME Wayland Session 
(session: gnome).

  From memory I've never edited the contents of /etc/apt/apt.conf.d/ and
  the configuration for unattended upgrades claims to be default (NOT to
  reboot):

  $ grep -irnC4 reboot /etc/apt/apt.conf.d/
  /etc/apt/apt.conf.d/50unattended-upgrades-88-// Do automatic removal of 
unused packages after the upgrade
  /etc/apt/apt.conf.d/50unattended-upgrades-89-// (equivalent to apt-get 
autoremove)
  
/etc/apt/apt.conf.d/50unattended-upgrades-90-//Unattended-Upgrade::Remove-Unused-Dependencies
 "false";
  /etc/apt/apt.conf.d/50unattended-upgrades-91-
  /etc/apt/apt.conf.d/50unattended-upgrades:92:// Automatically reboot *WITHOUT 
CONFIRMATION* if
  /etc/apt/apt.conf.d/50unattended-upgrades:93://  the file 
/var/run/reboot-required is found after the upgrade
  
/etc/apt/apt.conf.d/50unattended-upgrades:94://Unattended-Upgrade::Automatic-Reboot
 "false";
  /etc/apt/apt.conf.d/50unattended-upgrades-95-
  /etc/apt/apt.conf.d/50unattended-upgrades:96:// Automatically reboot even if 
there are users currently logged in
  /etc/apt/apt.conf.d/50unattended-upgrades:97:// when 
Unattended-Upgrade::Automatic-Reboot is set to true
  
/etc/apt/apt.conf.d/50unattended-upgrades:98://Unattended-Upgrade::Automatic-Reboot-WithUsers
 "true";
  /etc/apt/apt.conf.d/50unattended-upgrades-99-
  /etc/apt/apt.conf.d/50unattended-upgrades:100:// If automatic reboot is 
enabled and needed, reboot at the specific
  /etc/apt/apt.conf.d/50unattended-upgrades-101-// time instead of immediately
  /etc/apt/apt.conf.d/50unattended-upgrades-102-//  Default: "now"
  
/etc/apt/apt.conf.d/50unattended-upgrades:103://Unattended-Upgrade::Automatic-Reboot-Time
 "02:00";
  /etc/apt/apt.conf.d/50unattended-upgrades-104-
  /etc/apt/apt.conf.d/50unattended-upgrades-105-// Use apt bandwidth limit 
feature, this example limits the download
  /etc/apt/apt.conf.d/50unattended-upgrades-106-// speed to 70kb/sec
  /etc/apt/apt.conf.d/50unattended-upgrades-107-//Acquire::http::Dl-Limit "70";

  journalctl -u unattended-upgrades

  Jul 10 07:52:31 PC systemd[1]: Started Unattended Upgrades Shutdown.
  Jul 14 10:03:03 PC systemd[1]: unattended-upgrades.service: Succeeded.
  -- Reboot --
  Jul 14 10:04:11 PC systemd[1]: Started Unattended Upgrades Shutdown.
  Jul 15 11:18:03 PC systemd[1]: unattended-upgrades.service: Succeeded.
  -- Reboot --
  Jul 15 11:19:10 PC systemd[1]: Started Unattended

[Touch-packages] [Bug 1872215] Re: There should be a GUI option to install non-security packages too

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

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

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

Title:
  There should be a GUI option to install non-security packages too

Status in unattended-upgrades package in Ubuntu:
  Opinion

Bug description:
  The Software & Updates program lacks the option for the user to allow
  Ubuntu to automatically install non-security packages. It only
  supports security packages.

  I know Unattended-upgrades supports automatic upgrading of other
  packages but it might be too complicated for new users. There should
  be an easier way.

  Consider that Windows also deals with software updates "unattended" by
  default.

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

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

[Touch-packages] [Bug 1887655] Re: unattended-upgrades triggers reboot despite configuration

What is the output of:

apt-config dump | grep Reboot

?

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

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

Title:
  unattended-upgrades triggers reboot despite configuration

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  I've been having problems with my Ubuntu machine suddenly rebooting
  without any warning.  To my knowledge Ubuntu Desktop is not supposed
  to reboot without warning by default.

  I believe this is being triggered by unattended-upgrades

  unattended-upgrades 2.3 (amd64)

  Ubuntu Desktop:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  One pattern that emerges is that the reboot happens right after
  unattended-upgrades completes successfully. There are multiple
  examples in my /var/log/syslog, but all show "unattended-
  upgrades.service: Succeeded." the same second everything begins to
  shut down, with nothing for a minute or two prior. Example:

  Jul 15 11:17:01 pc systemd[2065]: Starting Notification regarding a new 
release of Ubuntu...
  Jul 15 11:17:14 pc charon: 08[IKE] sending keep alive to 10.10.10.10[4500]
  Jul 15 11:17:22 pc check-new-release-gtk[71843]: 
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:30: PyGIWarning: Gtk was 
imported without specifying a version first. Use gi.require_version('Gtk'
  , '3.0') before import to ensure that the right version gets loaded.
  Jul 15 11:17:22 pc check-new-release-gtk[71843]:   from gi.repository import 
Gtk
  Jul 15 11:17:22 pc check-new-release-gtk[71843]: WARNING:root:timeout 
reached, exiting
  Jul 15 11:17:22 pc systemd[2065]: update-notifier-release.service: Succeeded.
  Jul 15 11:17:22 pc systemd[2065]: Finished Notification regarding a new 
release of Ubuntu.
  Jul 15 11:17:48 pc mysql-workbench[33350]: gtk_tree_view_unref_tree_helper: 
assertion 'node != NULL' failed
  Jul 15 11:17:54 pc charon: 09[IKE] sending keep alive to 10.10.10.10[4500]
  Jul 15 11:18:03 pc systemd[1]: unattended-upgrades.service: Succeeded.
  Jul 15 11:18:03 pc systemd[1]: Stopping Session 3 of user philip.
  Jul 15 11:18:03 pc systemd[1]: Removed slice 
system-clean\x2dmount\x2dpoint.slice.
  Jul 15 11:18:03 pc systemd[1]: Removed slice system-getty.slice.
  Jul 15 11:18:03 pc systemd[1]: Removed slice system-modprobe.slice.
  Jul 15 11:18:03 pc systemd[1]: Stopped target Block Device Preparation for 
/dev/mapper/ubuntu.
  Jul 15 11:18:03 pc systemd[2065]: Stopped target GNOME Wayland Session 
(session: gnome).

  From memory I've never edited the contents of /etc/apt/apt.conf.d/ and
  the configuration for unattended upgrades claims to be default (NOT to
  reboot):

  $ grep -irnC4 reboot /etc/apt/apt.conf.d/
  /etc/apt/apt.conf.d/50unattended-upgrades-88-// Do automatic removal of 
unused packages after the upgrade
  /etc/apt/apt.conf.d/50unattended-upgrades-89-// (equivalent to apt-get 
autoremove)
  
/etc/apt/apt.conf.d/50unattended-upgrades-90-//Unattended-Upgrade::Remove-Unused-Dependencies
 "false";
  /etc/apt/apt.conf.d/50unattended-upgrades-91-
  /etc/apt/apt.conf.d/50unattended-upgrades:92:// Automatically reboot *WITHOUT 
CONFIRMATION* if
  /etc/apt/apt.conf.d/50unattended-upgrades:93://  the file 
/var/run/reboot-required is found after the upgrade
  
/etc/apt/apt.conf.d/50unattended-upgrades:94://Unattended-Upgrade::Automatic-Reboot
 "false";
  /etc/apt/apt.conf.d/50unattended-upgrades-95-
  /etc/apt/apt.conf.d/50unattended-upgrades:96:// Automatically reboot even if 
there are users currently logged in
  /etc/apt/apt.conf.d/50unattended-upgrades:97:// when 
Unattended-Upgrade::Automatic-Reboot is set to true
  
/etc/apt/apt.conf.d/50unattended-upgrades:98://Unattended-Upgrade::Automatic-Reboot-WithUsers
 "true";
  /etc/apt/apt.conf.d/50unattended-upgrades-99-
  /etc/apt/apt.conf.d/50unattended-upgrades:100:// If automatic reboot is 
enabled and needed, reboot at the specific
  /etc/apt/apt.conf.d/50unattended-upgrades-101-// time instead of immediately
  /etc/apt/apt.conf.d/50unattended-upgrades-102-//  Default: "now"
  
/etc/apt/apt.conf.d/50unattended-upgrades:103://Unattended-Upgrade::Automatic-Reboot-Time
 "02:00";
  /etc/apt/apt.conf.d/50unattended-upgrades-104-
  /etc/apt/apt.conf.d/50unattended-upgrades-105-// Use apt bandwidth limit 
feature, this example limits the download
  /etc/apt/apt.conf.d/50unattended-upgrades-106-// speed to 70kb/sec
  /etc/apt/apt.conf.d/50unattended-upgrades-107-//Acquire::http::Dl-Limit "70";

  journalctl -u unattended-upgrades

  Jul 10 07:52:31 PC systemd[1]: Started Unattended Upgrades Shutdown.
  Jul 14 10:03:03 PC systemd[1]: unattended-upgrades.service: Succeeded.
  -- Reboot --
  Jul 14 10:04:11 PC systemd[1]: Started Unattended Upgrades Shutdown.
  Jul 15 11:18:03 PC systemd[1]: unattended-upgrades.service:

[Touch-packages] [Bug 1886161] Re: UU should work on roaming laptops

Those options can be overridden to match your preference. I for example
enable u-u on metered connections because the plan I use allows enough
traffic for that.


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

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

Title:
  UU should work on roaming laptops

Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  For many if not most laptop computers, Unattended Upgrades seems all
  but useless by design.

  For upgrades to happen, with default config, 3 conditions must be met:

  - an internet connection must be up and running when the timer or cron or 
anacron tries the unattended upgrade
  - the connection must not be metered, whatever that means 
(Skip-Updates-On-Metered-Connections "true")
  - the computer must be plugged in (OnlyOnACPower "true")

  These are insurmountable problems for many laptops on the go.
  Inevitably, security upgrades will almost never run unattended on such
  computers. I discovered with shock that Unattended Upgrades had almost
  never run on my laptop. I tried all possible config tweaks. Nothing
  worked reliably and in the end I gave up and wrote a upgrade script
  which uses Network Manager's connection-up hook. Unattended Upgrades
  needs to do something like this out of the box. Users should not need
  to write scripts to ensure security upgrades.

  Unattended upgrades is an excellent project for servers. But it really
  needs to work, out of the box, on laptops too.

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

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

[Touch-packages] [Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x

2020-07-21 Thread Frank Heimes

** Changed in: ubuntu-z-systems
   Status: New => Triaged

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

Title:
  posix_spawn usage in gnu make causes failures on s390x

Status in Ubuntu on IBM z Systems:
  Triaged
Status in glibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in make-dfsg package in Ubuntu:
  New

Bug description:
  posix_spawn usage in gnu make causes failures on s390x

  Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it
  started to use posix_spawn, instead of fork()/exec().

  This has caused failure of an unrelated package flatpak-builder
  autopkgtests on s390x only, like so

echo Building
make: echo: Operation not permitted
make: *** [Makefile:2: all] Error 127

  Julian Klaude investigated this in-depth. His earlier research also
  indicated that this is a heisenbug, if one tries to print to stderr
  before printing to stdout, no issue occurs.

  We are configuring GNU make to be build with --disable-posix-spawn on
  s390x only. We passed these details to Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=964541 too.

  But I do wonder, if there is something different or incorrect about
  posix_spawn() implementation in either glibc, or linux kernel, on
  s390x. Or gnu-make's usage of posix_spawn().

  As otherise, using posix_spawn() in gnu-make works on other
  architectures, and flatpak-builder autopkgtests pass too.

  It seems very weird that stdout does not appear to be functional,
  unless stderr was opened/written to, from gnu-make execution compiled
  with posix-spawn feature.

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

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

[Touch-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's

2020-07-21 Thread Edgars Piņķis

audit: type=1107 audit(1595014020.261:196): pid=1051 uid=103 auid=4294967295 
ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal"  bus="system" 
path="/org/freedesktop/NetworkManager/ActiveConnection/4" 
interface="org.freedesktop.NetworkManager.Connection.Active" 
member="PropertiesChanged" name=":1.12" mask="receive" pid=2401 
label="snap.telegram-desktop.telegram-desktop" peer_pid=1057 
peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
[  477.870889] audit: type=1107 audit(1595014065.447:197): pid=1051 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal"  
bus="system" path="/org/freedesktop/NetworkManager" 
interface="org.freedesktop.NetworkManager" member="PropertiesChanged" 
name=":1.12" mask="receive" pid=2401 
label="snap.telegram-desktop.telegram-desktop" peer_pid=1057 
peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
[  477.870985] audit: type=1107 audit(1595014065.447:198): pid=1051 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal"  
bus="system" path="/org/freedesktop/NetworkManager/ActiveConnection/4" 
interface="org.freedesktop.NetworkManager.Connection.Active" 
member="PropertiesChanged" name=":1.12" mask="receive" pid=2401 
label="snap.telegram-desktop.telegram-desktop" peer_pid=1057 
peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
[  477.871464] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)

this was the output from dmesg previously before I, along with family
members who are more versed in tech in general, attempted to fix the
issue, which sadly did not bring results at my home. The behaviour I
expected was that my laptop will connect to the home network (already
known network) as per usual. What I encountered was/is that whenever I
attempt to connect to the network, the ssid is recognized, it briefly
attempts to connect before deauthenticating by local choice
(Reason:3=DEAUTH_LEAVING).

I have done nothing to cause this to occur. I have done almost
everything I can, excluding resetting the settings of the home network

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)

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

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

[Touch-packages] [Bug 1887964] Re: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found

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

Title:
  VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume
  group vg01 Volume group "vg01" not found

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed

Bug description:
  After upgrading a laptop configured with LVM from 18.04 to 20.04 the volume 
group is no longer found.
  During boot the console shows

  Volume group "vg01" not found
  Cannot process volume group vg01
  Gave up waiting for suspend/resume device
  ALERT! /dev/mapper/vg01-root does not exist. Dropping to a shell!

  Attached dist-upgrade logs and console output.

  Tried the "vgck --updatemetadata vg01" recommended on this bug report:
  https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381

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

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

[Touch-packages] [Bug 1887964] Re: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found

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

** Changed in: lvm2 (Ubuntu)
   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/1887964

Title:
  VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume
  group vg01 Volume group "vg01" not found

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Focal:
  Confirmed

Bug description:
  After upgrading a laptop configured with LVM from 18.04 to 20.04 the volume 
group is no longer found.
  During boot the console shows

  Volume group "vg01" not found
  Cannot process volume group vg01
  Gave up waiting for suspend/resume device
  ALERT! /dev/mapper/vg01-root does not exist. Dropping to a shell!

  Attached dist-upgrade logs and console output.

  Tried the "vgck --updatemetadata vg01" recommended on this bug report:
  https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381

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

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

[Touch-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's

the warning you shared indicates that a snap called indicator-sensors
tries to talking to udisks without having the proper permission, that's
not sign of an authentification issue...

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)

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

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

[Touch-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's

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

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

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Thanks!

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

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

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)

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

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

[Touch-packages] [Bug 1887964] Re: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found

2020-07-21 Thread bene

exactly the same happened here. Help would be much appreciated!

thanks

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

Title:
  VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume
  group vg01 Volume group "vg01" not found

Status in lvm2 package in Ubuntu:
  New
Status in lvm2 source package in Focal:
  New

Bug description:
  After upgrading a laptop configured with LVM from 18.04 to 20.04 the volume 
group is no longer found.
  During boot the console shows

  Volume group "vg01" not found
  Cannot process volume group vg01
  Gave up waiting for suspend/resume device
  ALERT! /dev/mapper/vg01-root does not exist. Dropping to a shell!

  Attached dist-upgrade logs and console output.

  Tried the "vgck --updatemetadata vg01" recommended on this bug report:
  https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381

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

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

[Touch-packages] [Bug 1770961] Re: Add options to set the snappy refresh schedule

2020-07-21 Thread Ads20000

To be fair, I think snappy devs also been open on that thread that if
you need software that follows a 'not-Microsoft' and 'always trust the
user' policy then yes you should not be using snap, use Flatpak or
another alternative instead.

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

Title:
  Add options to set the snappy refresh schedule

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Snappy has a feature where the user can state when in a month to
  refresh (update) their snaps. Please provide options in Software &
  Updates to control this.

  https://docs.snapcraft.io/system-options

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun May 13 15:10:07 2018
  InstallationDate: Installed on 2017-08-03 (282 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (21 days ago)

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

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

--- Comment (attachment only) From z...@us.ibm.com 2020-07-21 10:55 
EDT---


** Attachment added: "Fix 1"
   https://bugs.launchpad.net/bugs/1873961/+attachment/5394632/+files/fix1.txt

-- 
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 1873961] Fix 2

--- Comment (attachment only) From z...@us.ibm.com 2020-07-21 10:56 
EDT---


** Attachment added: "Fix 2"
   https://bugs.launchpad.net/bugs/1873961/+attachment/5394633/+files/fix2.txt

-- 
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 1873961] Comment bridged from LTC Bugzilla

--- Comment From z...@us.ibm.com 2020-07-21 10:54 EDT---
I download iproute2-4.18.0.tar.gz from this upstream url:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git

Then pulled in 2 patches documented in comment 1 on top of 
iproute2-4.18.0.tar.gz, build and test the functionality.
It builds successfully, and it does reports correct tcp_flags mask with these 2 
patches.

Attach these 2 patches in the bug for reference.

The first patch declares global variable "const char *_SL_ = "\n";" in
lib/utils.c to be used by 2nd patch to fix the build break issue.

-- 
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 1883082] Re: Crash when using Package-Whitelist-Strict

** Description changed:

+ [Impact]
+ 
+  * Unattended-upgrades crashes when strict whitelist is enabled and
+ there is an update available.
+ 
+ [Test Case]
+ 
+ Set up a system with at least one updated package available:
+ 
+  $ lxc launch ubuntu:focal ff-uu-strict
+  Creating ff-uu-strict
+  Starting ff-uu-strict   
+  $ lxc shell ff-uu-strict 
+  root@ff-uu-strict:~# apt update
+  ...
+  root@ff-uu-strict:~# apt list --upgradable 
+  Listing... Done
+  open-vm-tools/focal-updates 2:11.1.0-2~ubuntu20.04.1 amd64 [upgradable  
from: 2:11.0.5-4]
+  N: There is 1 additional version. Please use the '-a' switch to see it
+ 
+ Set up strict whitelist not covering the package:
+ 
+  root@ff-uu-strict:~# echo 'Unattended-Upgrade::Package-Whitelist-Strict 
"true";' > /etc/apt/apt.conf.d/51unattended-upgrades-whitelist
+  root@ff-uu-strict:~# echo 'Unattended-Upgrade::Package-Whitelist {"foo";}' 
>> /etc/apt/apt.conf.d/51unattended-upgrades-whitelist
+ 
+ Run unattended-upgrades:
+  root@ff-uu-strict:~# unattended-upgrade 
+ 
+ The fixed version does not crash here, the not fixed one does.
+ 
+ 
+ [Regression Potential] 
+ 
+ Minimal. The fix adds only one extra check to not crash dereferencing
+ None.
+ 
+ [Original Bug Text]
+ 
+ 
  Hi,
  
  I'm trying to use unattended-upgrades only with a few packages from a
  list; to do that I tried this simple /etc/apt/apt.conf.d/51local-ua
  file:
  
- root@focal-ua:~# cat /etc/apt/apt.conf.d/51local-ua   

   
- Unattended-Upgrade::Package-Whitelist-Strict "true";  

   
+ root@focal-ua:~# cat /etc/apt/apt.conf.d/51local-ua
+ Unattended-Upgrade::Package-Whitelist-Strict "true";
  Unattended-Upgrade::Package-Whitelist {
  "firefox";
  "bash";
  "openssh-server";
  }
  
  When running unattended-upgrades in dry run mode I get this crash:
  
  root@focal-ua:~# unattended-upgrade --debug --dry-run
  Running on the development release
  Starting unattended upgrades script
  Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, 
o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security, 
o=UbuntuESM,a=focal-security
- Initial blacklist: 
+ Initial blacklist:
  Initial whitelist (strict): firefox bash openssh-server
  Marking not allowed  
with -32768 pin
  Marking not allowed  
with -32768 pin
  Marking not allowed  
with -32768 pin
  Marking not allowed  
with -32768 pin
  Marking not allowed  with -32768 pin
  Marking not allowed  
with -32768 pin
  Marking not allowed  with -32768 pin
  Marking not allowed  
with -32768 pin
  Marking not allowed  with -32768 pin
  Marking not allowed  
with -32768 pin
  An error occurred: '>' not supported between instances of 'apt_pkg.Version' 
and 'int'
  Traceback (most recent call last):
-   File "/usr/bin/unattended-upgrade", line 1983, in main
- res = run(options, rootdir, mem_log, logfile_dpkg,
-   File "/usr/bin/unattended-upgrade", line 2124, in run
- cache = UnattendedUpgradesCache(rootdir=rootdir)
-   File "/usr/bin/unattended-upgrade", line 171, in __init__
- apt.Cache.__init__(self, rootdir=rootdir)
-   File "/usr/lib/python3/dist-packages/apt/cache.py", line 170, in __init__
- self.open(progress)
-   File "/usr/bin/unattended-upgrade", line 330, in open
- self.apply_pinning(self.pinning_from_config())
-   File "/usr/bin/unattended-upgrade", line 302, in pinning_from_config
- and policy.get_candidate_ver(pkg) > -1:  # type: ignore   

   
- TypeError: '>' not supported between instances of 'apt_pkg.Version' and 'int' 

   
- Extracting content from 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2020-06-11 
09:38:25
  
- Traceback (most recent call last):

   
-   File "/usr/bin/unattended-upgrade", line 2512, in   

   
- sys.exit(main(options))   

   
-   File "/usr/bin/unattended-upgrade", line 1983, in main  

   
-

[Touch-packages] [Bug 1857036] Re: `sudo --login --user USERNAME` throws `setrlimit(RLIMIT_CORE): Operation not permitted` error when run inside a container.

2020-07-21 Thread Łukasz Zemczak

Hello Thomas, or anyone else affected,

Accepted sudo into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sudo/1.8.31-1ubuntu1.1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Description changed:

  [Impact]
  Logging in as a sudo user in a Ubuntu Focal Linux container displays a
  warning:
  
    sudo: setrlimit(RLIMIT_CORE): Operation not permitted
  
  The warning is entirely unnecessary - the container is trying to adjust
  RLIMIT_CORE, but this isn't allowed inside a container anyway.
  
  While this is "just" a warning, logging into a container as sudo is a
  very common practice, so this warning risks creating confusion for LTS
  users.
  
  [Test Case]
  $ lxc launch ubuntu:20.04/amd64 sudo-sru-lp1857036-test
  $ lxc shell sudo-sru-lp1857036-test
  
  # sudo --login --user ubuntu
  sudo: setrlimit(RLIMIT_CORE): Operation not permitted
  To run a command as administrator (user "root"), use "sudo ".
  See "man sudo_root" for details.
  $ logout
  
- Install the PPA
- # apt-add-repository -yus ppa:bryce/sudo-sru-lp1857036-setrlimit-in-lxc
+ Enable -proposed and update
  # apt-get install sudo
  
  # sudo --login --user ubuntu
  $
  
  [Regression Potential]
  As this only affects printing of a couple warnings, the only behavioral
  change is in stderr output.
  
  [Discussion]
  This changes a couple warnings into equivalent debug printfs, which
  brings the sudo behavior in-line with the behavior in groovy, bionic,
  etc. and should cause no troubles.
  
  This patch originates from upstream, and is already in groovy's sudo
  package (which thus can be seen not to exhibit the issue).
  
  The upstream patch includes some new debug prints which should be
  harmless but are unnecessary to the fix so they've been removed.
  
  [Original Report]
  When using `sudo --login --user USERNAME` with Ubuntu Focal currently, it 
will correctly operate but it will also throw the following error before 
continuing with the logon process (which completes successfully except for the 
stated error):
  
  sudo: setrlimit(RLIMIT_CORE): Operation not permitted
  
  A full run of this was tested in a Focal LXD container after dropping to
  a root shell to reproduce (arstotzka is the host system, focal-test is
  the test container):
  
  teward@arstotzka:~$ lxc shell focal-test
  root@focal-test:~# sudo --login --user ubuntu
  sudo: setrlimit(RLIMIT_CORE): Operation not permitted
  To run a command as administrator (user "root"), use "sudo ".
  See "man sudo_root" for details.
  
  ubuntu@focal-test:~$
  
  This appears to be similar to this issue identified on RedHat's tracker:
  https://bugzilla.redhat.com/show_bug.cgi?id=1773148
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: sudo 1.8.29-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu14
  Architecture: amd64
  Date: Thu Dec 19 17:16:31 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: sudo
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/90-cloud-init-users: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

Title:
  `sudo --login --user USERNAME` throws `setrlimit(RLIMIT_CORE):
  Operation not permitted` error when run inside a container.

Status in sudo package in Ubuntu:
  Fix Released
Status in sudo source package in Focal:
  Fix Committed
Status in sudo source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  Logging in as a sudo user in a Ubuntu Focal Linux container displays a
  warning:

    sudo:

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

Thanks Marian... I'm now currently working on this issue and will
provide feedback soon here...

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in linux-signed source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in bcache-tools source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in bcache-tools source package in Groovy:
  Triaged
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

2020-07-21 Thread Shengyao Xue

I can reproduce this issue with the original pulseaudio on a ThinkPad
P14s, and after I opened focal-proposed channel and updated the
pulseaudio package, this issue was fixed.

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

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions

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

[Touch-packages] [Bug 1888391] Re: /etc/dhcp/dhclient-enter-hooks.d/resolved should not run in non-root network namespaces

2020-07-21 Thread Dan Streetman

** Tags added: resolved-resolvconf

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

Title:
  /etc/dhcp/dhclient-enter-hooks.d/resolved should not run in non-root
  network namespaces

Status in systemd package in Ubuntu:
  New

Bug description:
  Running dhclient in a (non-root) network namespace on a system with
  systemd enabled fails because the hook installed by the systemd
  package updates the DNS configuration of the core/root namespace,
  instead of simply the /etc/resolv.conf file of that particular network
  namespace.

  ("ip netns add " nicely links /etc/resolv.conf in that namespace
  to /etc/netns//resolv.conf if it exists.)

  The following patch ensures that this script no longer misbehaves for
  this scenario:

  --- /etc/dhcp/dhclient-enter-hooks.d/resolved.bak 2020-07-21 
14:05:23.390989468 +0200
  +++ /etc/dhcp/dhclient-enter-hooks.d/resolved 2020-07-21 14:03:18.566046842 
+0200
  @@ -14,7 +14,7 @@
   #   (D) = master script downs interface
   #   (-) = master script does nothing with this

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && [ -z "$(ip netns identify)" ] ; 
then
   # For safety, first undefine the nasty default make_resolv_conf()
   make_resolv_conf() { : ; }
   case "$reason" in

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

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

[Touch-packages] [Bug 1886854] Re: Race in load-module snap policy check in classic confinement

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

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

Title:
  Race in load-module snap policy check in classic confinement

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  SUMMARY
  =
  When running a snap in classic confinement, that needs access to 
PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed 
and sometimes fail with "Access denied".

  After running "pacmd unload-module module-snap-policy" and unloading
  the snap policy module, these work reliably.

  I have verified this in a fresh install of Ubuntu 20.04 in a VM.

  STEPS TO REPRODUCE
  =
  a) Either build a snap with classic confinement that sends these commands on 
the pulseaudio native protocol socket. (This is how I found the bug)
  b) Or, what I did here to easier reproduce, abuse the sandbox of a random 
classic snap:

  Download the attached bug.tgz with a minimal reproducer. It contains
  the source code for a program that sends load and unload commands to
  pulse. Unfortunately `pacmd` has a pid-file check that fails inside
  the sandbox and doesn't work. The reproducer does essentially the same
  as "pacmd load/unload-module" though.

  (a pre-compiled x64 binary is also included in case you don't have a
  go compiler and dare to run an untrusted binary in a VM)

  Unpack the tgz, build it, if necessary with "go mod download && go
  build"

  Grab a random classic mode snap to use its sandbox as a test bed:

  $ sudo snap install atom --classic
  atom 1.48.0 from Snapcrafters installed

  Open a shell in its sandbox:

  snap run --shell atom
  
  Navigate to the compiled binary and execute it a few times:

  user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 
  2020/07/08 18:46:10 PulseAudio connection created successfully
  2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio 
error: commandLoadModule -> Access denied
  user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 
  2020/07/08 18:46:11 PulseAudio connection created successfully
  Loaded Module sucessfully at index: 40
  user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 
  2020/07/08 18:46:12 PulseAudio connection created successfully
  Loaded Module sucessfully at index: 41
  user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 
  2020/07/08 18:46:12 PulseAudio connection created successfully
  2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio 
error: commandLoadModule -> Access denied
  user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 
  2020/07/08 18:46:14 PulseAudio connection created successfully
  2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio 
error: commandLoadModule -> Access denied
  user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 
  2020/07/08 18:46:14 PulseAudio connection created successfully
  2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio 
error: commandLoadModule -> Access denied
  user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 
  2020/07/08 18:46:15 PulseAudio connection created successfully
  2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio 
error: commandLoadModule -> Access denied

  Succeeds and fails apparently at random.

  Now from a non-sandboxed shell, run

  pacmd unload-module module-snap-policy

  to unload the snap-policy module from pulseaudio, now run ./bug a few
  more times. It now succeeds reliably, every time.

  Side note, with the real program on my actual machine, the race seems
  to behave slightly differently. It seems not to work the first time an
  application is started, but closing it and reopening it seems to make
  it work pretty reliably afterwards. Restarting "snapd", causes the
  following run the snap to fail again.

  EXPECTED BEHAVIOUR
  ==

  The pulseaudio snap policy module should correctly determine and
  enforce it's policy.

  ACTUAL BEHAVIOUR
  

  The pulseaudio snap policy module seemingly at random denies access
  when the snap has the permissions to do an operation.

  ADDITIONAL INFORMATION
  ==

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.3
Candidate: 1:13.99.1-1ubuntu3.3
Version table:
   *** 1:13.99.1-1ubuntu3.3 500
  500 http://ch.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://ch.archive.ubuntu.com/ubuntu focal/main amd64 Packages

To manage notifications about this bug go to:

[Touch-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

** Changed in: pulseaudio (Ubuntu Bionic)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: pulseaudio (Ubuntu Bionic)
   Status: Confirmed => In Progress

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

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions

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

[Touch-packages] [Bug 1877769] Re: [SRU] Rewinding cache triggers obsolete adjustments consuming a lot of CPU

** Also affects: unattended-upgrades (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1877769

Title:
  [SRU] Rewinding cache triggers obsolete adjustments consuming a lot of
  CPU

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Focal:
  New
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Unattended-upgrades consumes excessive amount of CPU when rewinding
  cache trying to mark packages to upgrade or install even when they are
  already marked to be upgraded or installed. This can be triggered by
  packages held back.

  [Test Case]

   * Run test_rewind.py:
 -Fixed output:
  $ python3 test_rewind.py 
  INFO:root:Allowed origins are: o=Ubuntu,a=lucid-security
  INFO:root:Initial blacklist: ant-doc
  INFO:root:Initial whitelist (not strict): 
  DEBUG:root:Marking not allowed  with 
-32768 pin
  DEBUG:root:Applying pinning: PkgFilePin(id=0, priority=-32768)
  DEBUG:root:Applying pin -32768 to package_file: 
  DEBUG:root:Applying pinning: PkgPin(pkg='/^ant-doc/', priority=-32768)
  DEBUG:root:APT::VersionedKernelPackages is not set
  DEBUG:root:adjusting candidate version: test-package=2.0
  DEBUG:root:adjusting candidate version: test2-package=2.0
  DEBUG:root:falling back to adjusting test2-package's dependencies
  DEBUG:root:falling back to adjusting z-package's dependencies
  DEBUG:root:sanity check failed for: set() : no package is selected to be 
upgraded or installed
  .
  --
  Ran 1 test in 0.022s

  OK

- Not fixed output:
   $ python3 test_rewind.py 
  INFO:root:Allowed origins are: o=Ubuntu,a=lucid-security
  INFO:root:Initial blacklist: ant-doc
  INFO:root:Initial whitelist (not strict): 
  DEBUG:root:Marking not allowed  with 
-32768 pin
  DEBUG:root:Applying pinning: PkgFilePin(id=0, priority=-32768)
  DEBUG:root:Applying pin -32768 to package_file: 
  DEBUG:root:Applying pinning: PkgPin(pkg='/^ant-doc/', priority=-32768)
  DEBUG:root:APT::VersionedKernelPackages is not set
  DEBUG:root:adjusting candidate version: test-package=2.0
  DEBUG:root:adjusting candidate version: test2-package=2.0
  DEBUG:root:falling back to adjusting test2-package's dependencies
  DEBUG:root:falling back to adjusting z-package's dependencies
  DEBUG:root:sanity check failed for: set() : no package is selected to be 
upgraded or installed
  DEBUG:root:falling back to adjusting test-package's dependencies
  DEBUG:root:falling back to adjusting test2-package's dependencies
  DEBUG:root:falling back to adjusting test3-package's dependencies
  DEBUG:root:falling back to adjusting test-package's dependencies
  DEBUG:root:falling back to adjusting test2-package's dependencies
  DEBUG:root:falling back to adjusting test3-package's dependencies
  .
  --
  Ran 1 test in 0.024s

  (Note the extra "DEBUG:root:falling back to adjusting" ... lines)

  [Regression Potential]

   * Minimal. The very small change fixes how call_checked() verifies that the 
package to be upgrades/installed is indeed marked to either being installed or 
upgraded.
  In the worst case, if call_checked() erroneously returns success for a 
package as a result of a regression, unattended-upgrades does not fall back to 
adjusting packages to make marking successful. Later unattended-upgrades finds 
out that the package could not be marked and should be treated as kept back.

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

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

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

--- Comment From andreas.kreb...@de.ibm.com 2020-07-21 08:57 EDT---
Stefan Liebler (our Glibc guy) is having a look. He managed to reproduce it on 
his system.

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

Title:
  posix_spawn usage in gnu make causes failures on s390x

Status in Ubuntu on IBM z Systems:
  New
Status in glibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in make-dfsg package in Ubuntu:
  New

Bug description:
  posix_spawn usage in gnu make causes failures on s390x

  Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it
  started to use posix_spawn, instead of fork()/exec().

  This has caused failure of an unrelated package flatpak-builder
  autopkgtests on s390x only, like so

echo Building
make: echo: Operation not permitted
make: *** [Makefile:2: all] Error 127

  Julian Klaude investigated this in-depth. His earlier research also
  indicated that this is a heisenbug, if one tries to print to stderr
  before printing to stdout, no issue occurs.

  We are configuring GNU make to be build with --disable-posix-spawn on
  s390x only. We passed these details to Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=964541 too.

  But I do wonder, if there is something different or incorrect about
  posix_spawn() implementation in either glibc, or linux kernel, on
  s390x. Or gnu-make's usage of posix_spawn().

  As otherise, using posix_spawn() in gnu-make works on other
  architectures, and flatpak-builder autopkgtests pass too.

  It seems very weird that stdout does not appear to be functional,
  unless stderr was opened/written to, from gnu-make execution compiled
  with posix-spawn feature.

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

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

[Touch-packages] [Bug 1888390] Re: apparmor error causing deauthentication for certain SSID's

2020-07-21 Thread Edgars Piņķis

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

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

Title:
  apparmor error causing deauthentication for certain SSID's

Status in network-manager package in Ubuntu:
  New

Bug description:
  dmesg output:
  [   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
  [  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
  [  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
  [  165.568883] wlan0: authenticated
  [  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
  [  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 
status=0 aid=3)
  [  165.579888] wlan0: associated
  [  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
  Release Information:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  Codename:   bionic
  Expected outcome: 
  Connecting to the home network
  Actual outcome:
  deauthentication by local choice (Reason:3=DEAUTH_LEAVING)

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

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

[Touch-packages] [Bug 1879019] Re: bad mime type for bmp

** Changed in: ristretto (Ubuntu)
   Status: Confirmed => Invalid

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

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

Title:
  bad mime type for bmp

Status in Ristretto:
  New
Status in file package in Ubuntu:
  Confirmed
Status in ristretto package in Ubuntu:
  Invalid

Bug description:
  Sample BMP file attached to this related bug:
  https://bugs.launchpad.net/ubuntu/+source/ristretto/+bug/1762242

  Note the attached screenshot here, this is a regression

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libmagic1 1:5.38-4
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri May 15 23:28:26 2020
  InstallationDate: Installed on 2018-04-29 (747 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: file
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils

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

** Tags added: rls-gg-incoming

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

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

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  New

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

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

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

[Touch-packages] [Bug 1888390] [NEW] apparmor error causing deauthentication for certain SSID's

You have been subscribed to a public bug:

dmesg output:
[   83.493815] audit: type=1107 audit(1595332083.919:115): pid=1040 uid=103 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/UDisks2" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name=":1.4" pid=1922 
label="snap.indicator-sensors.indicator-sensors" peer_pid=1044 
peer_label="unconfined"
exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? 
terminal=?'
[  165.565325] wlan0: authenticate with bc:ee:7b:65:f4:80
[  165.566549] wlan0: send auth to bc:ee:7b:65:f4:80 (try 1/3)
[  165.568883] wlan0: authenticated
[  165.570960] wlan0: associate with bc:ee:7b:65:f4:80 (try 1/3)
[  165.573753] wlan0: RX AssocResp from bc:ee:7b:65:f4:80 (capab=0x411 status=0 
aid=3)
[  165.579888] wlan0: associated
[  165.643053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  211.035453] wlan0: deauthenticating from bc:ee:7b:65:f4:80 by local choice 
(Reason: 3=DEAUTH_LEAVING)
Release Information:
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename:   bionic
Expected outcome: 
Connecting to the home network
Actual outcome:
deauthentication by local choice (Reason:3=DEAUTH_LEAVING)

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


** Tags: bot-comment
-- 
apparmor error causing deauthentication for certain SSID's
https://bugs.launchpad.net/bugs/1888390
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager in Ubuntu.

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

Re: [Touch-packages] [Bug 1770961] Re: Add options to set the snappy refresh schedule

2020-07-21 Thread dee bee

On Tue, Jul 21, 2020 at 6:36 AM Ads2 <1770...@bugs.launchpad.net>
wrote:

> dee bee if you want an off switch it's already been extensively
> discussed at https://forum.snapcraft.io/t/disabling-automatic-refresh-
> for-snap-from-store/707/
> 
>
> Please Like all the posts there that you agree with and provide SPECIFIC
> and preferably REAL use cases where an off switch is needed not just the
> ability to schedule updates for once a month and push them back another
> month as well as turn off automatic updates when on a metered
> connection. (Former?) snapd lead niemeyer requested specific use cases
> to demonstrate that an off switch is NEEDED. If you would like to put
> the work in, please read the thread in full and then provide what the
> developers are requesting on use cases and, if that's not possible, just
> Like all the posts you agree with. Thanks! :)
>
> Greetings

As by at very least inference said 'lead' Niemeyer has made it very clear
that
there NEVER EVER WILL BE SUCH A SWITCH. So why would I waste
further time on this issue.

I had followed such thread from its inception and now only very
occasionally
mostly finding enjoyment at the ever more 'out there' reasons that are
proffered to validate the continuation that many have reviled. Many except
reasons were proffered and after about the first 100 such responses said
lead was downright surly if and when he responded to any further.

I can inform you that I had said miasma installed on a server. As I could
not
control the upgrade schedule I stopped using that particular system. After
a
time later when I assayed to restart the system it was not possible to do
that.
The system was locked into a perpetual loop which I could not break. I was
only able to break that loop by completely reinstalling the system. This
microsoft like control of behavior is something that I chose to reject many
many years ago when I was looking for an option that did not include
said companies then, and still today, software that specializes in porous
software.

Again - - - - - why would I waste time trying to convince someone who
hadn't been listening from the beginning of the argument that they were
not 'helping'. But then why would he or the team care - - - - this
procedure
is all about making more money on what is supposedly open source.

But then today's public is so enamoured of glitz and glitter than it just
doesn't understand that the is almost no privacy left and as far as
security - - - - why they think they don't need any - - - - - they trust
the
software companies. Sadly - - - - I do remember one of the slogans
that was bruted about when PCs were a newish thing - - - that is -
"Computing your way" implying and sometimes stating that the
previous rigidity in the corporate IT department had removed use to
the point where the user was never part of the equation. Somehow
it seems like we've come full circle  - - - - we're back to where the IT
department, or software devs, are 'the only ones who know how things
should be done' - - - - except - - - - that was never true and is still
not true.

Regards

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

Title:
  Add options to set the snappy refresh schedule

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Snappy has a feature where the user can state when in a month to
  refresh (update) their snaps. Please provide options in Software &
  Updates to control this.

  https://docs.snapcraft.io/system-options

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun May 13 15:10:07 2018
  InstallationDate: Installed on 2017-08-03 (282 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (21 days ago)

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

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

[Touch-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2020-07-21 Thread Ubuntu Foundations Team Bug Bot

The attachment "This patch is not the fix. WARNING" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Confirmed
Status in pcmanfm package in Ubuntu:
  Triaged

Bug description:
  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further assert this, note that there is a SpaceFM file manager that
  is available in GTK2 and GTK3. The GTK2 version displays the behavior.
  The GTK3 version does not. Same with LibreOffice.

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

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

[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs

2020-07-21 Thread Bug Watch Updater

** Changed in: jackd2 (Debian)
   Status: Confirmed => Fix Released

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

Title:
  libjack-jackd2-0 double close on a failure to connect to jackd which
  causes crashes in multithreaded programs

Status in alsa-plugins package in Ubuntu:
  Invalid
Status in jackd2 package in Ubuntu:
  Fix Released
Status in jackd2 package in Debian:
  Fix Released

Bug description:
  After upgrading to Ubuntu 19.04, I started experiencing sporadic
  crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded
  alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin
  is enabled by default in /etc/alsa/conf.d/50-jack.conf.

  The crashes are caused by a race condition when kodi's audio engine
  thread is enumerating the ALSA sound devices, and the udev thread is
  enumerating the udev devices triggered by the sound device add from
  turning the AVR on.

  When enumerating the ALSA jack plugin device, it tries to connect to
  connect to jackd. Since I don't have jackd installed, it fails to
  connect. libjack closes the socket on error, and then closes it again
  in it's cleanup code. Since it's closing the same file descriptor
  twice, it interacts with other threads that have potentially opened
  file descriptors, and causes the crash.

  This same bug could potentially affect other multi-threaded programs
  that enumerate ALSA devices.

  Fix committed upstream:
  
https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208

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

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

[Touch-packages] [Bug 696618] Re: factor compiled without bignum support

2020-07-21 Thread Bug Watch Updater

** Changed in: coreutils (Debian)
   Status: Confirmed => Fix Released

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

Title:
  factor compiled without bignum support

Status in coreutils package in Ubuntu:
  Triaged
Status in coreutils package in Debian:
  Fix Released

Bug description:
  factor (from GNU coreutils) in Ubuntu Lucid appears to be compiled without 
bignum support. According to the info page:
 If `factor' is built without using GNU MP, only single-precision
  arithmetic is available, and so large numbers (typically 2^64 and
  above) will not be supported.

  Example:
  user@host:/$ factor 123456789098765432123456789
  factor: `123456789098765432123456789' is too large

  In order to limit dependencies of the basic coreutils package, perhaps
  a bignum-supporting version should be packaged separately.

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

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

[Touch-packages] [Bug 1888391] Re: /etc/dhcp/dhclient-enter-hooks.d/resolved should not run in non-root network namespaces

2020-07-21 Thread Steffan Karger

Gah, the -n should of course be a -z.

** Description changed:

  Running dhclient in a (non-root) network namespace on a system with
  systemd enabled fails because the hook installed by the systemd package
  updates the DNS configuration of the core/root namespace, instead of
  simply the /etc/resolv.conf file of that particular network namespace.
  
  ("ip netns add " nicely links /etc/resolv.conf in that namespace
  to /etc/netns//resolv.conf if it exists.)
  
  The following patch ensures that this script no longer misbehaves for
  this scenario:
  
  --- /etc/dhcp/dhclient-enter-hooks.d/resolved.bak 2020-07-21 
14:05:23.390989468 +0200
  +++ /etc/dhcp/dhclient-enter-hooks.d/resolved 2020-07-21 14:03:18.566046842 
+0200
  @@ -14,7 +14,7 @@
-  #   (D) = master script downs interface
-  #   (-) = master script does nothing with this
-  
+  #   (D) = master script downs interface
+  #   (-) = master script does nothing with this
+ 
  -if [ -x /lib/systemd/systemd-resolved ] ; then
- +if [ -x /lib/systemd/systemd-resolved ] && [ -n "$(ip netns identify)" ] ; 
then
-  # For safety, first undefine the nasty default make_resolv_conf()
-  make_resolv_conf() { : ; }
-  case "$reason" in
+ +if [ -x /lib/systemd/systemd-resolved ] && [ -z "$(ip netns identify)" ] ; 
then
+  # For safety, first undefine the nasty default make_resolv_conf()
+  make_resolv_conf() { : ; }
+  case "$reason" in

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

Title:
  /etc/dhcp/dhclient-enter-hooks.d/resolved should not run in non-root
  network namespaces

Status in systemd package in Ubuntu:
  New

Bug description:
  Running dhclient in a (non-root) network namespace on a system with
  systemd enabled fails because the hook installed by the systemd
  package updates the DNS configuration of the core/root namespace,
  instead of simply the /etc/resolv.conf file of that particular network
  namespace.

  ("ip netns add " nicely links /etc/resolv.conf in that namespace
  to /etc/netns//resolv.conf if it exists.)

  The following patch ensures that this script no longer misbehaves for
  this scenario:

  --- /etc/dhcp/dhclient-enter-hooks.d/resolved.bak 2020-07-21 
14:05:23.390989468 +0200
  +++ /etc/dhcp/dhclient-enter-hooks.d/resolved 2020-07-21 14:03:18.566046842 
+0200
  @@ -14,7 +14,7 @@
   #   (D) = master script downs interface
   #   (-) = master script does nothing with this

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && [ -z "$(ip netns identify)" ] ; 
then
   # For safety, first undefine the nasty default make_resolv_conf()
   make_resolv_conf() { : ; }
   case "$reason" in

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

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

[Touch-packages] [Bug 1888391] [NEW] /etc/dhcp/dhclient-enter-hooks.d/resolved should not run in non-root network namespaces

2020-07-21 Thread Steffan Karger

Public bug reported:

Running dhclient in a (non-root) network namespace on a system with
systemd enabled fails because the hook installed by the systemd package
updates the DNS configuration of the core/root namespace, instead of
simply the /etc/resolv.conf file of that particular network namespace.

("ip netns add " nicely links /etc/resolv.conf in that namespace
to /etc/netns//resolv.conf if it exists.)

The following patch ensures that this script no longer misbehaves for
this scenario:

--- /etc/dhcp/dhclient-enter-hooks.d/resolved.bak   2020-07-21 
14:05:23.390989468 +0200
+++ /etc/dhcp/dhclient-enter-hooks.d/resolved   2020-07-21 14:03:18.566046842 
+0200
@@ -14,7 +14,7 @@
 #   (D) = master script downs interface
 #   (-) = master script does nothing with this

-if [ -x /lib/systemd/systemd-resolved ] ; then
+if [ -x /lib/systemd/systemd-resolved ] && [ -z "$(ip netns identify)" ] ; then
 # For safety, first undefine the nasty default make_resolv_conf()
 make_resolv_conf() { : ; }
 case "$reason" in

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


** Tags: dhclient network-namespace systemd

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

Title:
  /etc/dhcp/dhclient-enter-hooks.d/resolved should not run in non-root
  network namespaces

Status in systemd package in Ubuntu:
  New

Bug description:
  Running dhclient in a (non-root) network namespace on a system with
  systemd enabled fails because the hook installed by the systemd
  package updates the DNS configuration of the core/root namespace,
  instead of simply the /etc/resolv.conf file of that particular network
  namespace.

  ("ip netns add " nicely links /etc/resolv.conf in that namespace
  to /etc/netns//resolv.conf if it exists.)

  The following patch ensures that this script no longer misbehaves for
  this scenario:

  --- /etc/dhcp/dhclient-enter-hooks.d/resolved.bak 2020-07-21 
14:05:23.390989468 +0200
  +++ /etc/dhcp/dhclient-enter-hooks.d/resolved 2020-07-21 14:03:18.566046842 
+0200
  @@ -14,7 +14,7 @@
   #   (D) = master script downs interface
   #   (-) = master script does nothing with this

  -if [ -x /lib/systemd/systemd-resolved ] ; then
  +if [ -x /lib/systemd/systemd-resolved ] && [ -z "$(ip netns identify)" ] ; 
then
   # For safety, first undefine the nasty default make_resolv_conf()
   make_resolv_conf() { : ; }
   case "$reason" in

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

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

[Touch-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2020-07-21 Thread alex-mobigo

I applied the patch attached (libX11) but the crash still occurs with less
frequency.
Maybe i missed some additional patch required to fix this.

For the record:

I am running LUbuntu in this PC box (upgraded from 16.04 to 18.04) and i
have another one with Ubuntu 18.04 + LXDE installed from scratch that
doesn't get the error.

Anything else i could try?

** Patch added: "This patch is not the fix. WARNING"

https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984/+attachment/5394608/+files/Fix-poll_for_response-race-condition.diff

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

Title:
Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
applications

Status in libx11 package in Ubuntu:
Confirmed
Status in pcmanfm package in Ubuntu:
Triaged

Bug description:
STEPS TO REPRODUCE
==
The bug seems to occur when clicking on a file or folder. It is random and
difficult to provide clear steps to reproduce. It is, however, a common
situation.

EXPECTED RESULTS

pcmanfm works without problem.

ACTUAL RESULTS
==
All pcmanfm windows become unresponsive, though background processes (e.g.
copying) may continue without problem. with the same error message in
~/.cache/lxsession/LXDE/run.log:

[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not
been called
[xcb] Aborting, sorry about that.
pcmanfm: xcb_io.c:259: poll_for_event: Assertion
`!xcb_xlib_threads_sequence_lost' failed.
** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

(note the timestamp on the message will vary)

AFFECTED VERSIONS
=
1.2.5-3ubuntu1
NOT 1.2.4-1ubuntu0.1

UPSTREAM BUG

https://sourceforge.net/p/pcmanfm/bugs/1089/

ADDITIONAL NOTES

Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad)
seem to have the same problems. This is probably at least rooted in a GTK2 bug:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

To further assert this, note that there is a SpaceFM file manager that
is available in GTK2 and GTK3. The GTK2 version displays the behavior.
The GTK3 version does not. Same with LibreOffice.

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

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

[Touch-packages] [Bug 1770961] Re: Add options to set the snappy refresh schedule

2020-07-21 Thread Ads20000

dee bee if you want an off switch it's already been extensively
discussed at https://forum.snapcraft.io/t/disabling-automatic-refresh-
for-snap-from-store/707/

Please Like all the posts there that you agree with and provide SPECIFIC
and preferably REAL use cases where an off switch is needed not just the
ability to schedule updates for once a month and push them back another
month as well as turn off automatic updates when on a metered
connection. (Former?) snapd lead niemeyer requested specific use cases
to demonstrate that an off switch is NEEDED. If you would like to put
the work in, please read the thread in full and then provide what the
developers are requesting on use cases and, if that's not possible, just
Like all the posts you agree with. Thanks! :)

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

Title:
  Add options to set the snappy refresh schedule

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Snappy has a feature where the user can state when in a month to
  refresh (update) their snaps. Please provide options in Software &
  Updates to control this.

  https://docs.snapcraft.io/system-options

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun May 13 15:10:07 2018
  InstallationDate: Installed on 2017-08-03 (282 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (21 days ago)

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

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

[Touch-packages] [Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x

2020-07-21 Thread Julian Andres Klode

Andreas, I've not gotten it more isolated, the minimum I had was running
debian/tests/gnome-desktop-testing in a flatpak-builder source tree (apt
source/pull-lp-source flatpak-builder).

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

Title:
  posix_spawn usage in gnu make causes failures on s390x

Status in Ubuntu on IBM z Systems:
  New
Status in glibc package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in make-dfsg package in Ubuntu:
  New

Bug description:
  posix_spawn usage in gnu make causes failures on s390x

  Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it
  started to use posix_spawn, instead of fork()/exec().

  This has caused failure of an unrelated package flatpak-builder
  autopkgtests on s390x only, like so

echo Building
make: echo: Operation not permitted
make: *** [Makefile:2: all] Error 127

  Julian Klaude investigated this in-depth. His earlier research also
  indicated that this is a heisenbug, if one tries to print to stderr
  before printing to stdout, no issue occurs.

  We are configuring GNU make to be build with --disable-posix-spawn on
  s390x only. We passed these details to Debian https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=964541 too.

  But I do wonder, if there is something different or incorrect about
  posix_spawn() implementation in either glibc, or linux kernel, on
  s390x. Or gnu-make's usage of posix_spawn().

  As otherise, using posix_spawn() in gnu-make works on other
  architectures, and flatpak-builder autopkgtests pass too.

  It seems very weird that stdout does not appear to be functional,
  unless stderr was opened/written to, from gnu-make execution compiled
  with posix-spawn feature.

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

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

[Touch-packages] [Bug 1888239] Re: cannot change default application to open XML files

** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)

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

Title:
  cannot change default application to open XML files

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  .xml file -> right click -> Properties -> Open With -> Related
  Applications -> GVim -> "Set as default"

  Expected behaviour: GVim shown as the "Default application" (instead
  of Firefox, as is currently the case)

  Observed behaviour: Firefox remains the default application

  
  The problem only seems to affect .xml files and is unrelated to GVim (if I 
select "Text editor" instead, Firefox still remains the default).

  Workaround: open file from bash

  Repeatability: 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 16:53:35 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'218'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1189x576+66+93'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'"
  InstallationDate: Installed on 2018-05-10 (802 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2020-03-04 (138 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1888239/+subscriptions

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

[Touch-packages] [Bug 1888239] [NEW] cannot change default application to open XML files