[Touch-packages] [Bug 1890858] Re: AppArmor profile causes QEMU/KVM - Not Connected

2021-06-19 Thread Mathew Hodson
** Tags removed: verification-needed

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

Title:
  AppArmor profile causes QEMU/KVM - Not Connected

Status in apparmor package in Ubuntu:
  Invalid
Status in libvirt package in Ubuntu:
  Invalid
Status in apparmor source package in Focal:
  New
Status in libvirt source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * libvirt in Focal in some cases e.g. with non local users
 needs to resolve those users. When trying to do so it fails
 due to apparmor isolation and breaks badly.

   * In later and former releases this issue isn't triggered,
 but it is unknown which (potentially complex) set of changes
 did that. A simple apparmor rule would help to allow libvirt
 to better function in environments with non known user IDs.

  [Test Plan]

   * Following these steps in an unfixed release triggers the issue

  sudo apt update; sudo apt dist-upgrade -y
  sudo apt install -y sssd sssd-ldap slapd ldap-utils openssl expect 
lsb-release libvirt-clients libvirt-daemon-system ubuntu-dev-tools
  pull-lp-source sssd
  cd sssd-2.4.1
  echo "*;*;*;Al-2400;libvirt" | sudo tee -a /etc/security/group.conf
  head -n -5 debian/tests/ldap-user-group-ldap-auth > 
debian/tests/lp1890858-test
  chmod +x debian/tests/lp1890858-test
  sudo ./debian/tests/lp1890858-test
  sudo systemctl restart libvirtd
  # ensure it works in a normal login
  virsh list
  journalctl -u libvirtd
  # try the sssd login
  sudo login
  # use testuser1 / testuser1secret to log in
  virsh list

  If affected this will not work reporting an error like:
  $ virsh list
  error: failed to connect to the hypervisor
  error: End of file while reading data: Input/output error

  And in dmesg/journal an apparmor denial like:

  Jun 14 11:25:26 ldap.example.com audit[48330]: AVC apparmor="DENIED"
  operation="bind" profile="libvirtd" pid=48330 comm="rpc-worker"
  family="unix" sock_type="dgram" protocol=0 requested_mask="bind"
  denied_mask="bind" addr="@userdb-f283d575d74df972f9e10bd14d0befe3"

  
  [Where problems could occur]

   * Allowing a little bit more to a daemon that already is rather powerful 
 and open in regard to it's profile usually isn't changing behavior.
 If anything it would be considered a potential risk, but this rule 
 should be ok to be added and ubuntu-security confirmed this.

  [Other Info]
   
   * Comment 38 confirms that this should be ok - from the security Teams 
 POV. 
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/comments/38 



  
  ---

  On some focal 20.04 systems, users are seeing "QEMU/KVM - Not
  Connected" when they attempt to use virt-manager to manage virtual
  machines. AppArmor denials like the following are seen in the logs:

  sudo grep libvirt /var/log/syslog | grep -i apparmor | grep -i denied
  Jun 28 14:53:27 koromicha kernel: [  334.660844] audit: type=1400 
audit(1593345207.778:951): apparmor="DENIED" operation="bind" 
profile="libvirtd" pid=12254 comm="libvirtd" family="unix" sock_type="dgram" 
protocol=0 requested_mask="bind" denied_mask="bind" 
addr="@userdb-6228daaaf66b14dfd14d93ef46d962c3"
  Jun 28 14:54:19 koromicha kernel: [  386.034970] audit: type=1400 
audit(1593345259.145:952): apparmor="DENIED" operation="bind" 
profile="libvirtd" pid=14311 comm="libvirtd" family="unix" sock_type="dgram" 
protocol=0 requested_mask="bind" denied_mask="bind" 
addr="@userdb-c861507740da1fa0c3356ad3b78bffe9"
  Jun 28 15:02:30 koromicha kernel: [  877.339057] audit: type=1400 
audit(1593345750.437:968): apparmor="DENIED" operation="bind" 
profile="libvirtd" pid=16175 comm="libvirtd" family="unix" sock_type="dgram" 
protocol=0 requested_mask="bind" denied_mask="bind" 
addr="@userdb-7d70643a9f8da0342f6359907817b664"

  Users have reported that the "solution" is to disable the AppArmor
  profile. More details, screenshots, etc. can be found here:
  https://kifarunix.com/how-to-fix-qemu-kvm-not-connected-error-on-
  ubuntu-20-04/

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

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


[Touch-packages] [Bug 1931874] Re: Failure to download packages with epochs (Regression from 2.1.15)

2021-06-19 Thread Mathew Hodson
** Tags added: regression-release

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

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

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

Title:
  Failure to download packages with epochs (Regression from 2.1.15)

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Hirsute:
  Fix Committed
Status in apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Packages where the epoch is encoded in the filename cannot be retrieved, as 
we overlooked some places when changing the acquire system to always use % 
encoded URLs.

  [Test plan]
  A test is included in the comprehensive test suite.

  [Where problems could occur]
  Regressions could occur in places that download debs with filenames that need 
quoting or are already quoted. You can argue this also changes the API 
slightly, since ArchiveURI() now returns encoded URLs, rather than just 
appending the file path to the host. Although, this could actually improve 
things too.

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

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


[Touch-packages] [Bug 1927078] Re: Don't allow useradd to use fully numeric names

2021-06-18 Thread Mathew Hodson
** Changed in: shadow (Ubuntu Focal)
   Importance: Undecided => Low

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

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

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

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Groovy:
  New
Status in shadow source package in Hirsute:
  New
Status in shadow source package in Impish:
  New

Bug description:
  [Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w  

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  
  2. With that same username, every successful authentication in gdm will loop 
back to gdm again instead of starting gnome, making the user unable to login.

  
  Making useradd fail (unless --badnames is set) when a fully numeric name is 
used will make the default OS behavior consistent.

  
  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

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

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


[Touch-packages] [Bug 1405452] Re: Typo in man page ("introduce a much improvement mechanism")

2021-06-04 Thread Mathew Hodson
Patch sent upstream:

https://patchwork.ozlabs.org/project/hostap/patch/20210525031333.7665-1-mathew.hod...@gmail.com/

** Tags added: patch-forwarded-upstream

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

Title:
  Typo in man page ("introduce a much improvement mechanism")

Status in One Hundred Papercuts:
  Triaged
Status in wpa package in Ubuntu:
  Triaged
Status in wpa package in Debian:
  New

Bug description:
  "introduce a much improvement mechanism" should be "introduce a much
  improved mechanism".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: wpasupplicant 2.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 24 16:19:30 2014
  InstallationDate: Installed on 2014-12-19 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list

2021-05-28 Thread Mathew Hodson
** Tags removed: verification-needed

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

Title:
  interruption of dist-upgrade can leave you next release in
  sources.list

Status in apt package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  New
Status in ubuntu-release-upgrader source package in Bionic:
  New
Status in apt source package in Focal:
  New
Status in ubuntu-release-upgrader source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in ubuntu-release-upgrader source package in Groovy:
  Fix Committed
Status in apt source package in Hirsute:
  Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  Calling update() or installing packages from apt clients resets their SIGINT 
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have 
set for them.

  In case of ubuntu-release-upgrader, this results in the release
  upgrader being unable to handle interrupts after it did the initial
  update - the default libc handler will run and the program exits.

  [Test plan]

  [[apt]]
  As a standalone test for apt, we can test the following script:

  import apt
  import time

  apt.Cache().update()
  print("WAITING")
  try:
  time.sleep(1)
  except BaseException as e:
  print("Seen", repr(e))
  print("END")

  Pressing Ctrl+C while WAITING is printed should print Seen
  KeyboardInterrupt, and importantly, also the END line.

  [[ubuntu-release-upgrader]]
  1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
  2) At the "Do you want to start the upgrade?" question say Y.
  3) When you see the "Lock screen disabled" message you will also see 
"Inhibiting until Ctrl+C is pressed".
  4) Press "Ctrl+C"

  Your /etc/apt/sources.list file will now have focal in it instead of
  bionic although the upgrade has quit. With the version of ubuntu-
  release-upgrader in -proposed you will not see the "Ctrl+C" message.
  For your sources.list file to be restored you'll need the version of
  apt from bionic-proposed installed before starting the upgrade.

  [Where problems could occur]
  apt: This specific change removes the two lines that SIG_DFL the signal 
handlers after running scripts. AFAWCT those lines are unnecessary - the code 
that calls it temporarily sets the handlers to SIG_IGN but restores previous 
handlers at the end; it was wrongly refactored decades ago. A regression could 
occur in that those signals will now continue to be ignored if we missed a spot.

  ubuntu-release-upgrader: The change is wrapping a bunch of code in a
  try: except: block so if the indentation was off the pyflakes /
  pycodestyle tests would fail but autopkgtest will catch that.

  [Original bug report]
  As a long-time-user of ?ubuntu, with apt-get as tool of choice for 
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
  In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu 
version; just all packages including new ones. Version updates had to be 
initiated manually, and I was always asked if I really wanted the new ?ubuntu 
version. Sounds appropriate.

  Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. 
I for one consider this kind of intrusive, though.
  It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a 
number of times earlier; just to *check* if the upgrade was on offer; but this 
is only a guess.

  In *any* case, a pop-up asking "Are you sure? Are you connected
  through an adequate pipe? Are you sitting with full batteries; better
  a power supply?" would be convenient; since I am using my PC for
  urgent duties, and didn't want to fiddle with unexpected upgrade bugs.

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Thu Oct  1 11:48:39 2020
  InstallationDate: Installed on 2019-03-14 (566 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
  VarLogDistupgradeAptlog:
   Log time: 2020-09-29 19:44:28.696289
   Log time: 2020-09-29 19:44:33.573481

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

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

[Touch-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged

2021-05-25 Thread Mathew Hodson
** Changed in: alsa-ucm-conf (Ubuntu)
   Importance: Undecided => Low

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

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

** Also affects: alsa-ucm-conf (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

** Also affects: alsa-ucm-conf (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Also affects: alsa-ucm-conf (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: alsa-ucm-conf (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: alsa-ucm-conf (Ubuntu Groovy)
   Importance: Undecided => Low

** Changed in: alsa-ucm-conf (Ubuntu Hirsute)
   Importance: Undecided => Low

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

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

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

** Changed in: alsa-ucm-conf (Ubuntu Hirsute)
   Status: New => Fix Released

** Changed in: alsa-ucm-conf (Ubuntu)
   Status: New => Fix Released

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

Title:
  [SRU] there is always a "Rear Microphone - Built-in Audio" option on
  the input device list even if the microphone is unplugged

Status in OEM Priority Project:
  In Progress
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Incomplete
Status in alsa-ucm-conf source package in Focal:
  New
Status in pulseaudio source package in Focal:
  New
Status in alsa-ucm-conf source package in Groovy:
  New
Status in pulseaudio source package in Groovy:
  New
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released
Status in pulseaudio source package in Hirsute:
  New

Bug description:
  [Impact]

  [Fix]

  [Test]

  [Where problems could occur]

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

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


[Touch-packages] [Bug 1928966] Re: Please merge procps 2:3.3.17-5 (main) from Debian unstable

2021-05-25 Thread Mathew Hodson
** Changed in: procps (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Please merge procps 2:3.3.17-5 (main) from Debian unstable

Status in procps package in Ubuntu:
  New

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

  
  Justification of new diff:
- There is a new diff, which is an autopkgtest for the stack limit issue 
  that was seen in bug 1874824. This test has been submitted to 
  Debian so the patch can be dropped if they accept it.

  Justification of dropped patches
- missing_potfiles_in: Debian has now added this code in POTFILES.in
  so the patch is no longer needed
- pmap_test: This patch disables some tests that are not causing
  any problems. These tests are run in Debian so should be run
  in Ubuntu as well
- top_config_file_bwcompat: Debian has applied this code upstream so
  the patch is no longer needed
- tar-version: Debian has applied this code upstream so the patch is
  no longer needed
- stack_limit: Debian has applied this code upstream so the patch is
  no longer needed

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

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


[Touch-packages] [Bug 1850667] Re: Switch to "unified" cgroup hierarchy (cgroupv2)

2021-05-22 Thread Mathew Hodson
** Changed in: lxc (Ubuntu)
   Importance: Wishlist => Medium

** Changed in: lxc (Ubuntu)
   Importance: Medium => Low

** Changed in: docker.io (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Switch to "unified" cgroup hierarchy (cgroupv2)

Status in lxc:
  Fix Released
Status in lxd:
  Fix Released
Status in snapd:
  Confirmed
Status in docker.io package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed
Status in lxc package in Debian:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  Systemd upstream switched the default cgroup hierarchy to unified with
  v243. This change is reverted by the Ubuntu systemd packages, but as
  unified is the way to go per upstream support should be added to all
  relevant Ubuntu packges (and snaps):

  https://github.com/systemd/systemd/blob/v243/NEWS#L56

  * systemd now defaults to the "unified" cgroup hierarchy setup during
build-time, i.e. -Ddefault-hierarchy=unified is now the build-time
default. Previously, -Ddefault-hierarchy=hybrid was the default. 
This
change reflects the fact that cgroupsv2 support has matured
substantially in both systemd and in the kernel, and is clearly the
way forward. Downstream production distributions might want to
continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for
their builds as unfortunately the popular container managers have 
not
caught up with the kernel API changes.

  
  Systemd is rebuilt using the new default and is available from the following 
PPA for testing:

  https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh

  The autopkgtest results against other packges are available here:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain

  lxc autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz

  snapd autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz

  
  docker.io autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz

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

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


[Touch-packages] [Bug 1929110] Re: Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit

2021-05-22 Thread Mathew Hodson
** Changed in: sudo (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Please merge sudo 1.9.5p2-3 (main) from Debian unstable (main) Edit

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

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

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


[Touch-packages] [Bug 1928973] Re: Please merge lvm2 2.03.11-2.1 from Debian unstable

2021-05-22 Thread Mathew Hodson
** Changed in: lvm2 (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Please merge lvm2 2.03.11-2.1 from Debian unstable

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.11-2.1 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

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

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


[Touch-packages] [Bug 1926437] Re: [SRU] Backport zstd support, fix bug in python-apt

2021-05-01 Thread Mathew Hodson
** Changed in: apt (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  [SRU] Backport zstd support, fix bug in python-apt

Status in apt package in Ubuntu:
  Fix Released
Status in python-apt package in Ubuntu:
  New
Status in apt source package in Xenial:
  Fix Released
Status in python-apt source package in Xenial:
  New
Status in python-apt source package in Bionic:
  New
Status in python-apt source package in Focal:
  New
Status in python-apt source package in Groovy:
  New
Status in python-apt source package in Hirsute:
  New
Status in python-apt source package in Impish:
  New

Bug description:
  [Impact]
  APT in xenial needs to learn about zstd support to enable Launchpad to work 
with zstd packages.

  python-apt in all releases needs to be adjusted to pass the compressor
  names instead of programs to ExtractTar, as otherwise, if
  /usr/bin/zstd does not exist, it will pass "false" as the compressor,
  and then ExtractTar fails (same for other compressors).

  On hirsute, the python-apt upload also includes some new  
annotations for build-dependencies, as it's a straight upload of the 2.2
  stable series.

  [Test plan]
  The apt regression tests cover the compression methods extensively, including 
even stored compressed lists in /var/lib/apt and fetching Packages files 
compressed with such methods, for all compression methods.

  The final test is to make apt_inst.DebFile("glibc-doc-
  reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() from
  1923845 work in python3-apt.

  For hirsute, the build dependency changes will verify themselves
  during the build ;)

  [Where problems could occur]

  APT:

  The changes to APT are adding the zstd compression backend to FileFd
  and then linking it into the configuration. The former is adding new
  code, triggered only on zstd files, and should not be able to cause
  regressions.

  The latter is a bunch of small lines here and there, and it caused
  issues during backporting in the test suite because it expected
  compressors in a specific order. However, chances are that nothing
  else has as stringent requirements as the test suite, so I don't
  believe that is a problem for existing users.

  Bugs can of course be in the code dealing with zstd, and that might
  open you up to security vulnerabilities in the zstd code if you pass
  APT zstd compressed files.

  A regression can be if clients used apt-helper cat-file to cat a zstd-
  compressed file ending in .zst - they'll now get uncompressed content,
  rather than compressed.

  python-apt:

  The change just replaces Binary with Name, aligning the code with APT
  itself, so it's so trivial, we don't expect regressions.

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

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


[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

2021-05-01 Thread Mathew Hodson
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #2859
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

** Changed in: mesa
 Remote watch: gitlab.freedesktop.org/mesa/mesa/-/issues #3468 => 
gitlab.freedesktop.org/mesa/mesa/-/issues #2859

** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/-/issues #3468
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468

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

Title:
  Xorg xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New

Bug description:
  I run checkbox job
  com.canonical.certification::memory/memory_stress_ng on focal, and the
  xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

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

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


[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

2021-05-01 Thread Mathew Hodson
** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/-/issues #4275
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275

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

Title:
  Xorg xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  New

Bug description:
  I run checkbox job
  com.canonical.certification::memory/memory_stress_ng on focal, and the
  xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

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

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


[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping

2021-05-01 Thread Mathew Hodson
** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Add Dell Privacy Mic Mute Key mapping

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
     GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

  [Other Info]

   * The change can only work with kernel commit on some specific hardware, ex. 
Latitude 9520. The commit series is 
"hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree.
     https://patchwork.kernel.org/project/alsa-devel/list/?series=465445
   * This change has been verified on Dell machine.

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

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


[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

2021-04-18 Thread Mathew Hodson
** No longer affects: libxcb (Ubuntu)

** No longer affects: libxcb (Ubuntu Focal)

** No longer affects: libxcb (Ubuntu Groovy)

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Focal)
   Status: Incomplete => Triaged

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Groovy)
   Status: Incomplete => Triaged

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: xserver-xorg-video-amdgpu (Ubuntu Groovy)
   Importance: Undecided => High

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in xf86-video-amd:
  Unknown
Status in xfwm4 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Triaged
Status in xfwm4 source package in Focal:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Focal:
  Triaged
Status in xfwm4 source package in Groovy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Groovy:
  Triaged

Bug description:
  [Impact]

   * This issue affects AMD graphics on Xfwm4 4.14.1.

   * Windows are displayed staggered with a multi-window layout

  [Test Plan]

   * Use AMD graphics drivers

   * Connect a second display at a different resolution

   * Open multiple windows

   * While the issue is present, the windows and desktop will appeared
  staggered

   * Once fixed, they display normally.

  [Where problems could occur]

   * Regression potential should be relatively low, as the release
  between 4.14.1 and 4.14.5 are bug releases.

   * With window managers, some changes could lead to different behavior
  and other broken displays. Non-AMD graphics users should also test for
  regressions.

  [Other Info]
   
   * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: 
https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44

  [Original Report]

  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: 

[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

2021-04-18 Thread Mathew Hodson
xfwm4 (4.14.2-1) unstable; urgency=medium

  * Team upload.

  [ Debian Janitor ]
  * Trim trailing whitespace.
  * Bump debhelper from old 11 to 12.
  * Set upstream metadata fields: Name (from ./configure), Repository.
  * Fix day-of-week for changelog entry 4.0.0.final-1.

  [ Mateusz Łukasik ]
  * d/watch: Update to working version.
  * New upstream version 4.14.1
- Fix raise delay (Closes: #940796)
  * d/control: update standards version to 4.5.0

  [ Unit 193 ]
  * New upstream version 4.14.2.
- Fix window title alignment (Closes: #953112)
  * d/control: R³: no.

 -- Unit 193   Sun, 03 May 2020 08:29:52 -0400

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

** Tags added: regression-release

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

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

** Project changed: linux => xf86-video-amd

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in xf86-video-amd:
  Unknown
Status in libxcb package in Ubuntu:
  Incomplete
Status in xfwm4 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete
Status in libxcb source package in Focal:
  Incomplete
Status in xfwm4 source package in Focal:
  In Progress
Status in xserver-xorg-video-amdgpu source package in Focal:
  Incomplete
Status in libxcb source package in Groovy:
  Incomplete
Status in xfwm4 source package in Groovy:
  Fix Released
Status in xserver-xorg-video-amdgpu source package in Groovy:
  Incomplete

Bug description:
  [Impact]

   * This issue affects AMD graphics on Xfwm4 4.14.1.

   * Windows are displayed staggered with a multi-window layout

  [Test Plan]

   * Use AMD graphics drivers

   * Connect a second display at a different resolution

   * Open multiple windows

   * While the issue is present, the windows and desktop will appeared
  staggered

   * Once fixed, they display normally.

  [Where problems could occur]

   * Regression potential should be relatively low, as the release
  between 4.14.1 and 4.14.5 are bug releases.

   * With window managers, some changes could lead to different behavior
  and other broken displays. Non-AMD graphics users should also test for
  regressions.

  [Other Info]
   
   * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: 
https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44

  [Original Report]

  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: 

[Touch-packages] [Bug 1472288] Re: missing attributes in /etc/os-release

2021-04-18 Thread Mathew Hodson
** Changed in: base-files (Ubuntu)
   Importance: Low => Wishlist

** Summary changed:

- missing attributes in /etc/os-release
+ Add additional attributes in /etc/os-release

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

Title:
  Add additional attributes in /etc/os-release

Status in base-files package in Ubuntu:
  Confirmed

Bug description:
  Please add 'CPE_NAME' and 'BUILD_ID' to /etc/os-release.

  More at http://www.freedesktop.org/software/systemd/man/os-
  release.html.

  I'm not sure BUILD_ID should be something like 'vivid' etc, but it
  would be a nice use. Or introduce a new attribute/value pair like

  NICKNAME_ID="vivid"

  No rush. Thanks for adopting this convention so quickly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: base-files 7.2ubuntu9
  Uname: Linux 4.1.0-rc5carif-7-ga8b253b x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul  7 10:26:02 2015
  Dependencies:
   
  InstallationDate: Installed on 2014-11-04 (245 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (73 days ago)

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

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


[Touch-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi

2021-04-18 Thread Mathew Hodson
** Also affects: bluez (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986836
   Importance: Unknown
   Status: Unknown

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

Title:
  Bluez should notify users when they need to reboot to apply changes on
  Raspberry Pi

Status in bluez package in Ubuntu:
  In Progress
Status in bluez package in Debian:
  Unknown

Bug description:
  In the case of upgrading or installing bluez for the first time on
  certain raspberry pi devices, a reboot may be required to apply the
  changes. We should add a check for this scenario in the postinst
  script.

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

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


[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

2021-03-26 Thread Mathew Hodson
** Changed in: mesa (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Xorg xserver got signal 6 to abort

Status in Mesa:
  Unknown
Status in OEM Priority Project:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  I run checkbox job
  com.canonical.certification::memory/memory_stress_ng on focal, and the
  xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468

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

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


[Touch-packages] [Bug 1890572] Re: USB backend never ends if the printer is not connected

2021-03-26 Thread Mathew Hodson
** No longer affects: cups

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

Title:
  USB backend never ends if the printer is not connected

Status in cups package in Ubuntu:
  New

Bug description:
  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:

  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```

  It's also easy to test by invoking the backend by hand:

  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file

  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...

  ```

  Setting a job timeout policy or manually stopping work are not options
  for us. We may have jobs that take hours to complete.

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

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


[Touch-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device

2021-03-26 Thread Mathew Hodson
** Changed in: alsa-lib (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: alsa-lib (Ubuntu Groovy)
   Importance: Undecided => Low

** Changed in: alsa-lib (Ubuntu Hirsute)
   Importance: Undecided => Low

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

Title:
  [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-
  Audio.pcm.iec958_device

Status in OEM Priority Project:
  In Progress
Status in alsa-lib package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  In Progress
Status in alsa-lib source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio.

  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.

  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.

  [Where problems will occur]
  This fix limits to the Cmedia Audio only, other devices are unaffected.

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

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


[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2021-03-25 Thread Mathew Hodson
** Tags removed: verification-needed

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 

[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error

2021-03-25 Thread Mathew Hodson
Fixed in Ubuntu Hirsute.

---
apt (2.1.16) unstable; urgency=medium

  [ Faidon Liambotis ]
  * Various fixes to http and connect method
- basehttp: also consider Access when a Server's URI
- connect: convert a C-style string to std::string
- connect: use ServiceNameOrPort, not Port, as the cache key

  [ Julian Andres Klode ]
  * patterns: Add dependency patterns ?depends, ?conflicts, etc.
Note that the -broken- variants are not implemented yet.
  * Rewrite of the kernel autoremoval code:
- Determine autoremovable kernels at run-time (LP: #1615381), this fixes the
  issue where apt could consider a running kernel autoremovable
- Automatically remove unused kernels on apt {full,dist}-upgrade.
  This helps ensuring that we don't run out of /boot space.
- Only keep up to 3 (not 4) kernels.
  Ubuntu boot partitions were sized for 3 kernels, not 4.
  * Bump codenames to bullseye/hirsute and adjust -security codename for
bullseye (Closes: #969932)
  * Ignore failures from immediate configuration. This does not change the
actual installation ordering - we never passed the return code to the
caller and installation went underway anyway if it could be ordered at a
later stage, this just removes spurious after-the-fact errors.
(Closes: #973305, #188161, #211075, #649588) (LP: #1871268)
  * Add support for Phased-Update-Percentage, previously used only by
update-manager.
  * Implement update --error-on=any so that scripts can reliably check for
transient failures as well. (Closes: #594813)

  [ Demi M. Obenour ]
  * test/integration/framework: Be compatible with Bash

  [ Vangelis Skarmoutsos ]
  * Greek program translation update

 -- Julian Andres Klode   Fri, 08 Jan 2021 21:49:15
+0100

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

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  There is no way for scripts to run apt update and be sure that it was 
entirely successful.

  We introduce a new flag, --error-on=any that makes apt update also
  error out on transient errors.

  [Test plan]
  We have included a test in the test-suite in 
test-apt-update-failure-propagation that ensures that warnings become errors.

  [Where problems could occur]
  If there's an issue some warnings for transient errors could become errors, 
or worse I suppose it's possible but unlikely for errors to be reported as 
warnings...

  Since the new behavior is behind a flag, regression potential for
  existing scripts is low if there is no bug.

  [Original bug report]

  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
    Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
    Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
    Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

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


[Touch-packages] [Bug 1742695] Re: apt-get update silently fails fetching security updates

2021-03-25 Thread Mathew Hodson
*** This bug is a duplicate of bug 1693900 ***
https://bugs.launchpad.net/bugs/1693900

** Also affects: apt (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776152
   Importance: Unknown
   Status: Unknown

** No longer affects: apt (Debian)

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

Title:
  apt-get update silently fails fetching security updates

Status in apt package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu Xenial, apt-get fails silently when security update server
  cannot be reached. This state could be detected by scanning the apt-
  get output afterwards. But manually adding workarounds to each apt-get
  invocation in production automation is prone to error, thus leaving
  machines without security updates.

  Expected behaviour (e.g.):
  * 0 - all OK
  * 1 - temporary failure (e.g. network)
  * 2 - permanent failure

  
  Test:
  * Change your update server IP in /etc/hosts to something unreachable
  * Run apt-get update (might take a while)
  * Check exit status

  
  $ lsb_release -r -d
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  rfiedler@n3ahit1403:~$ 

  ii  apt 1.2.24
  amd64commandline package manager

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

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


[Touch-packages] [Bug 626144] Re: aptdaemon doesn't respond to network errors correctly

2021-03-25 Thread Mathew Hodson
*** This bug is a duplicate of bug 1693900 ***
https://bugs.launchpad.net/bugs/1693900

** This bug is no longer a duplicate of bug 451366
   404 from the archive is not handled well
** This bug has been marked a duplicate of bug 1693900
   apt-get update should return exit code != 0 on error

** Package changed: debian => apt (Ubuntu)

** Changed in: apt (Ubuntu)
   Importance: Unknown => Undecided

** Changed in: apt (Ubuntu)
 Remote watch: Debian Bug tracker #594813 => None

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

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

Title:
  aptdaemon doesn't respond to network errors correctly

Status in Aptdaemon:
  New
Status in apt package in Ubuntu:
  New

Bug description:
  (A script is attached to demonstrate the behavior)

  1) Go to NetworkManager and disconnect from your network
  2) Run the script attached

  What happens - The update starts, continues for a few seconds and then 
finishes with the state "exit-sucess"
  What should happen - The update starts, fails and raises an error because it 
can't connect to the internet.

  1) Make sure you are connected to the Internet
  2) Run the script attached
  3) After a few seconds, go to NetworkManager and disconnect yourself from the 
internet

  What happens - The update starts and just hangs
  What should happen - The update starts and then fails (raising an error) 
because it can no longer connect to the internet.


  Such behavior is essential for applications like software-updater and
  the way it works at the moment seems counter-intuitive.

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

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


[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error

2021-03-25 Thread Mathew Hodson
** Bug watch removed: github.com/moby/moby/issues #23910
   https://github.com/moby/moby/issues/23910

** Bug watch removed: github.com/moby/libnetwork/issues #1654
   https://github.com/moby/libnetwork/issues/1654

** Changed in: apt (Ubuntu Xenial)
   Importance: Undecided => Wishlist

** Changed in: apt (Ubuntu Bionic)
   Importance: Undecided => Wishlist

** Changed in: apt (Ubuntu Focal)
   Importance: Undecided => Wishlist

** Changed in: apt (Ubuntu Groovy)
   Importance: Undecided => Wishlist

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  There is no way for scripts to run apt update and be sure that it was 
entirely successful.

  We introduce a new flag, --error-on=any that makes apt update also
  error out on transient errors.

  [Test plan]
  We have included a test in the test-suite in 
test-apt-update-failure-propagation that ensures that warnings become errors.

  [Where problems could occur]
  If there's an issue some warnings for transient errors could become errors, 
or worse I suppose it's possible but unlikely for errors to be reported as 
warnings...

  Since the new behavior is behind a flag, regression potential for
  existing scripts is low if there is no bug.

  [Original bug report]

  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
    Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
    Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
    Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

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


[Touch-packages] [Bug 451366] Re: 404 from the archive is not handled well

2021-03-25 Thread Mathew Hodson
*** This bug is a duplicate of bug 1693900 ***
https://bugs.launchpad.net/bugs/1693900

** Package changed: aptdaemon (Debian) => apt (Ubuntu)

** Changed in: apt (Ubuntu)
   Importance: Unknown => Undecided

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

** Changed in: apt (Ubuntu)
 Remote watch: Debian Bug tracker #594813 => None

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

** This bug has been marked a duplicate of bug 1693900
   apt-get update should return exit code != 0 on error

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

Title:
  404 from the archive is not handled well

Status in Aptdaemon:
  In Progress
Status in apt package in Ubuntu:
  New
Status in aptdaemon package in Ubuntu:
  Triaged
Status in software-center package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: software-center

  When trying to install Pingus from the Ubuntu Software Center It
  downloads to 50% and then gives the following error message:

  Failed to download package files
  Check your internet connection.
  Details
  Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/pool/main/b/boost1.38/libboost-signals1.38.0_1.38.0-6ubuntu5_i386.deb
 404  Not Found [IP: 91.189.88.31 80]


  My internet is working and I have downloaded and installed other
  software succesfully from the software center.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Oct 14 08:20:35 2009
  DistroRelease: Ubuntu 9.10
  Package: software-center 0.4.6
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-12.39-generic
  SourcePackage: software-center
  Tags:  ubuntu-unr
  Uname: Linux 2.6.31-12-generic i686

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

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


[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error

2021-03-25 Thread Mathew Hodson
** Bug watch added: Debian Bug tracker #594813
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594813

** Also affects: apt (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594813
   Importance: Unknown
   Status: Unknown

** Description changed:

  [Impact]
  There is no way for scripts to run apt update and be sure that it was 
entirely successful.
  
- We introduce a new flag, --error-mode=any that makes apt update also
- error out on transient errors.
+ We introduce a new flag, --error-on=any that makes apt update also error
+ out on transient errors.
  
  [Test plan]
  We have included a test in the test-suite in 
test-apt-update-failure-propagation that ensures that warnings become errors.
  
  [Where problems could occur]
  If there's an issue some warnings for transient errors could become errors, 
or worse I suppose it's possible but unlikely for errors to be reported as 
warnings...
  
  Since the new behavior is behind a flag, regression potential for
  existing scripts is low if there is no bug.
  
  [Original bug report]
  
  When running 'apt-get update' (e.g. on a container install post-install
  script), apt-get return with exit code 0, even so it wasn't able to
  "update" properly. E.g.:
  
  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
    Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
    Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
    Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.
  
  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  There is no way for scripts to run apt update and be sure that it was 
entirely successful.

  We introduce a new flag, --error-on=any that makes apt update also
  error out on transient errors.

  [Test plan]
  We have included a test in the test-suite in 
test-apt-update-failure-propagation that ensures that warnings become errors.

  [Where problems could occur]
  If there's an issue some warnings for transient errors could become errors, 
or worse I suppose it's possible but unlikely for errors to be reported as 
warnings...

  Since the new behavior is behind a flag, regression potential for
  existing scripts is low if there is no bug.

  [Original bug report]

  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
    Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
    Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
    Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

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

[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit

2021-03-25 Thread Mathew Hodson
** Changed in: procps (Ubuntu Focal)
   Importance: Undecided => Medium

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

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

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

Title:
  pgrep reports error "cannot allocate" when run without stack limit

Status in procps package in Ubuntu:
  Fix Committed
Status in procps source package in Focal:
  In Progress
Status in procps source package in Groovy:
  In Progress
Status in procps source package in Hirsute:
  Fix Committed
Status in procps package in Debian:
  New

Bug description:
  [Impact]

- Users who have ulimit set high would see either slow
  or failed pgrep and pkill commands
- Users who have ulimit set to unlimited would see
  failed pgrep and pkill commands
- This bug occurs because the behavior of sysconf(_SC_ARG_MAX)
  changed with a newer version of the kernel.

  [Test Case]

- set the ulimit to unlimited by running `ulimit -S -s unlimited`
- run `pgrep bash` to see that the "cannot allocate" error is
   printed and the command has failed.

  [Where Problems Could Occur]

- We have set upper and lower limits on the size of the malloc, but
  if further kernel versions break the call to sysconf in
  unexpected ways we could still see problems.

  [Original Description]

  If you have no stack limit (ulimit -S -s unlimited), any pgrep call
  will fail with an error:

  > pgrep vim
  pgrep: cannot allocate 4611686018427387903 bytes

  If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is
  very slow:

  > time pgrep vim
  2196
  real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444

  The relevant upstream bug report could be: 
https://gitlab.com/procps-ng/procps/-/issues/152
  Archlinux bug report: https://bugs.archlinux.org/task/66093

  procps:
    Installed: 2:3.3.16-1ubuntu2
    500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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


[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers

2021-03-19 Thread Mathew Hodson
** No longer affects: glibc (Ubuntu Hirsute)

** No longer affects: glibc (Ubuntu Groovy)

** No longer affects: glibc (Ubuntu Focal)

** No longer affects: glibc (Ubuntu Bionic)

** No longer affects: glibc (Ubuntu Xenial)

** No longer affects: glibc (Ubuntu)

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

Title:
  test -x fails inside shell scripts in containers

Status in docker.io package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  Fix Committed
Status in runc package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  New
Status in libseccomp source package in Xenial:
  New
Status in runc source package in Xenial:
  New
Status in systemd source package in Xenial:
  New
Status in docker.io source package in Bionic:
  New
Status in libseccomp source package in Bionic:
  New
Status in runc source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  New
Status in docker.io source package in Focal:
  New
Status in libseccomp source package in Focal:
  New
Status in runc source package in Focal:
  Fix Committed
Status in systemd source package in Focal:
  New
Status in docker.io source package in Groovy:
  New
Status in libseccomp source package in Groovy:
  New
Status in runc source package in Groovy:
  Fix Committed
Status in systemd source package in Groovy:
  Fix Released
Status in docker.io source package in Hirsute:
  New
Status in libseccomp source package in Hirsute:
  Fix Committed
Status in runc source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released

Bug description:
  (SRU template for systemd)

  [impact]

  bash (and some other shells) builtin test command -x operation fails

  [test case]

  on any affected host system, start nspawn container, e.g.:

  $ sudo apt install systemd-container
  $ wget 
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz
  $ mkdir h
  $ cd h
  $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz
  $ sudo systemd-nspawn

  Then from a bash shell, verify if test -x works:

  root@h:~# ls -l /usr/bin/gpg
  -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg
  root@h:~# test -x /usr/bin/gpg || echo "fail"
  fail

  [regression potential]

  any regression would likely occur during a syscall, most likely
  faccessat2(), or during other syscalls.

  [scope]

  this is needed for b/f

  this is fixed upstream by commit
  bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so
  this is fixed in h

  this was pulled into Debian at version 246.2 in commit
  e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g

  in x, the entire systemd seccomp code is completely different and the
  patch doesn't apply, nor does it appear to be needed, as the problem
  doesn't reproduce in a h container under x.

  [other info]

  this needs fixing in libseccomp as well

  [original description]

  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:

  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#

  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail

  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #

  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--==
  ii  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement

  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.

  The build fails with:

  0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one 

[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

2021-03-18 Thread Mathew Hodson
** Changed in: bluez (Ubuntu Focal)
   Importance: Undecided => Medium

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

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  In Progress
Status in bluez source package in Groovy:
  Fix Released
Status in bluez source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * Enable the -proposed repository for the release (groovy)
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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


[Touch-packages] [Bug 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

2021-03-18 Thread Mathew Hodson
** Changed in: bluez (Ubuntu Groovy)
   Importance: Undecided => Medium

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

Title:
  Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Groovy:
  New
Status in bluez source package in Hirsute:
  New

Bug description:
  Bluetooth stops working after updating to bluez version
  5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization
  timed out". Bluetooth is working again if bluez is reverted to version
  5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt.

  Release:  20.10
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14
  Uname: Linux 5.8.0-1007-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: arm64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 25 16:09:03 2020
  ImageMediaBuild: 20200423.1
  InterestingModules: bnep bluetooth
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  Lsusb:
   Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 
25EE
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 
smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 
vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0 console=tty1 
root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 
elevator=deadline rootwait fixrtc
  SourcePackage: bluez
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago)
  acpidump:
   
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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

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


[Touch-packages] [Bug 1891810] Re: Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn containers

2021-03-15 Thread Mathew Hodson
** Changed in: libseccomp (Ubuntu Xenial)
   Importance: Undecided => Medium

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

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

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

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

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

Title:
  Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn
  containers

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Xenial:
  Confirmed
Status in libseccomp source package in Bionic:
  Confirmed
Status in libseccomp source package in Focal:
  Confirmed
Status in libseccomp source package in Groovy:
  Confirmed
Status in libseccomp source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  The version of libseccomp2 in X/B/F/G does not know about the openat2
  syscall. As such applications that use libseccomp cannot specify a
  system-call filter against this system-call and so it cannot be
  mediated.

  [Test Plan]

  This can be tested by simply running scmp_sys_resolver from the
  seccomp binary package and specifying this system-call:

  Existing behaviour:

  $ scmp_sys_resolver openat2
  -1

  Expected behaviour:

  $ scmp_sys_resolver openat2
  437

  (Note this value will be different on other architectures)

  [Where problems could occur]

  In version 2.5.1 of libseccomp which adds this new system-call,
  changes were also made in the way the socket system-call is handled by
  libseccomp on PPC platforms - this resulted in a change in the
  expected behaviour and so this has already been noticed and a fix is
  required for the systemd unit tests as a result
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696

  There was also a similar change for s390x but so far no regressions
  have been observed as a result as systemd already expected that
  behaviour from libseccomp, it was only PPC that was missing.

  In the event that a regression is observed however, we can easily
  either patch the affected package to cope with the new behaviour of
  this updated libseccomp since in each case the change in behaviour
  only affects a few system calls on particular architectures, or we can
  revert this update.

  [Other Info]

   * As usual thorough testing of this update has been performed both
  manually via the QA Regression Testing scripts, and via the
  autopkgtest infrastructure against packages in the Ubuntu Security
  Proposed PPA https://launchpad.net/~ubuntu-security-
  proposed/+archive/ubuntu/ppa/ with results seen
  https://people.canonical.com/~platform/security-britney/current/

  I have attached debdiffs of the prepared updates which are also
  sitting in the Ubuntu Security Proposed PPA.

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

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


[Touch-packages] [Bug 1915126] Re: autopkgtest times out (or fails before that) in hirsute on test infra, passes locally

2021-03-08 Thread Mathew Hodson
This bug was fixed in the package systemd - 247.3-1ubuntu4

---
systemd (247.3-1ubuntu4) hirsute; urgency=medium

  [ Dimitri John Ledkov ]
  * 
d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch:
Patch updated to reduce log level to debug

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=299002546ec2d62e7f0dd7d614ba958fc9df83c2

  [ Dan Streetman ]
  * d/p/lp1906331-sd-event-ref-event-loop-while-in-sd_event_prepare-ot.patch:
Take event reference while processing (LP: #1906331)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1bc38abcd3b62d317fcb62b72e26d9cb2e35ccf9
  * d/p/lp1917458-udev-rules-add-rule-to-create-dev-ptp_hyperv.patch:
Create symlink for hyperv-provided ptp device (LP: #1917458)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f1ee790ad66395457ca64cb5f8a01fdd8aabe47

  [ Balint Reczey ]
  * Pick proposed patch for not returning early in udevadm (LP: #1914062)
File: debian/patches/lp1914062-udevadm-don-t-return-early.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d8c80751a97b0c6c4df972f6f8325293aa1607c4
  * debian/tests/control: Mark systemd-fsckd flaky again.
As promised in LP: 1915126, until further investigation.
File: debian/tests/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=68fbaab272af81aab29497f7c6a3e4e6e9aa091b

 -- Balint Reczey  Thu, 04 Mar 2021 12:19:05 +0100

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

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

Title:
  autopkgtest times out (or fails before that) in hirsute on test infra,
  passes locally

Status in Auto Package Testing:
  Incomplete
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  Hi,
  I've asked yesterday on IRC but so far got no answer. I think it is right to 
file a bug about the current state of systemd autopkgtest to unite the efforts 
in regard to it.

  I was looking at the systemd tests for a no-change rebuild that really
  had no reason to now make it fail. While checking I found that as of
  this month (first bad test on 1st of February) most of the systemd
  test runs on amd64 will not pass/fail but instead in most cases time
  out.

  I've seen various people retry the case as it shows the typical
  symptoms of a "not the fault of the package, let us retry this" case.
  But it seems that won't help as the test history is rather clear.

  
  * Watch this in monospace to make more sense of it *

  $ check-autopkgtest-stats.sh -c 50 -p systemd -r "hirsute" -a "amd64"
  Check last 50 test results for src:systemd on releases 'hirsute' on 
architectures 'amd64'
  Of the 50 last tests, we had these subtest failing per release/arch:

  hirsute
amd64
  tests-in-lxd   (F  2% f  0% S  0% B 12% => P 52%/) 
.BTTTBTT.BTBTTTBBTTT..F..
  hostnamed  (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  build-login(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  unit-config(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  networkd-testpy(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  localed-locale (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  boot-and-services  (F  4% f  0% S  0% B 12% => P 50%/) 
.BTTTBTT.BTBTTTBBTTT...F.F...
  timedated  (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  boot-smoke (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  logind (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  storage(F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  upstream   (F 12% f  0% S  0% B 12% => P 42%/) 
.BTTTBTT.BTBTTTBBTTTF.F.F..FF..F.
  udev   (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  systemd-fsckd  (F  8% f  0% S  0% B 12% => P 46%/) 
FBTTTBTTFBTBTTTBBTTT.F..F
  root-unittests (F  0% f  0% S  0% B 12% => P 54%/) 
.BTTTBTT.BTBTTTBBTTT.
  localed-x11-keymap (F  0% f  0% S  0% B 12% => P 54%/) 

[Touch-packages] [Bug 1685754] Re: 'systemd --user' unduly forces umask=0022

2021-03-08 Thread Mathew Hodson
** No longer affects: dbus (Ubuntu)

** No longer affects: dbus (Ubuntu Bionic)

** No longer affects: gnome-terminal (Ubuntu)

** No longer affects: gnome-terminal (Ubuntu Bionic)

** Project changed: nautilus => ubuntu-translations

** No longer affects: ubuntu-translations

** Project changed: gedit => ubuntu-translations

** No longer affects: ubuntu-translations

** Project changed: gnome-session => ubuntu-translations

** No longer affects: ubuntu-translations

** Bug watch removed: freedesktop.org Bugzilla #18446
   https://bugs.freedesktop.org/show_bug.cgi?id=18446

** Bug watch removed: bugzilla.gnome.org/ #784113
   https://bugzilla.gnome.org/show_bug.cgi?id=784113

** Bug watch removed: GNOME Bug Tracker #780622
   https://gitlab.gnome.org/780622

** Project changed: gnome-terminal => ubuntu-translations

** No longer affects: ubuntu-translations

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

Title:
  'systemd --user' unduly forces umask=0022

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [impact]

  pam_umask, from /etc/passwd, is not honored in systemd --user
  instances

  [test case]

  on a desktop system, edit /etc/passwd to change the test user entry
  (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field
  (5th field). For example change:

  ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash

  to:

  ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash

  You may need to reboot for your X session to pick up the change.

  Then, from the graphical desktop, open a terminal and run:

  $ gnome-terminal -e sh

  in the opened terminal, run:

  $ umask

  the number shown should be 0007, as set in the passwd file

  [regression potential]

  any regression would likely result in an incorrect umask for the user
  whose passwd entry is modified.

  [scope]

  this is needed only for b

  this is fixed in systemd upstream by commit
  5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in
  v246, so this is fixed in g and later. This commit was also picked up
  by Debian and included in the v245 release for focal, so this is fixed
  in focal already.

  [original description]

  In order to set the default umask of my users to 027 or 007, I
  followed the instructions provided in 'man pam_umask' :

  In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
  'umask=007' (for myself).

  Then, MOST graphical applications systematically run with the correct
  umask.

  In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
  it systematically displays 0007.

  But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
  it systematically displays 0022.

  That is BAD, and is a security issue.

  Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
  UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
  if  [ "$UMASK" ];  then
    umask  "${UMASK#$USER:*,umask=}"
  fi

  In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask
  unchanged.

  Thank you in advance for a quick correction.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 24 08:36:58 2017
  InstallationDate: Installed on 2017-03-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1913763] Re: hyperv: unable to distinguish PTP devices

2021-03-08 Thread Mathew Hodson
This bug was fixed in the package systemd - 247.3-1ubuntu4

---
systemd (247.3-1ubuntu4) hirsute; urgency=medium

  [ Dimitri John Ledkov ]
  * 
d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch:
Patch updated to reduce log level to debug

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=299002546ec2d62e7f0dd7d614ba958fc9df83c2

  [ Dan Streetman ]
  * d/p/lp1906331-sd-event-ref-event-loop-while-in-sd_event_prepare-ot.patch:
Take event reference while processing (LP: #1906331)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=1bc38abcd3b62d317fcb62b72e26d9cb2e35ccf9
  * d/p/lp1917458-udev-rules-add-rule-to-create-dev-ptp_hyperv.patch:
Create symlink for hyperv-provided ptp device (LP: #1917458)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8f1ee790ad66395457ca64cb5f8a01fdd8aabe47

  [ Balint Reczey ]
  * Pick proposed patch for not returning early in udevadm (LP: #1914062)
File: debian/patches/lp1914062-udevadm-don-t-return-early.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d8c80751a97b0c6c4df972f6f8325293aa1607c4
  * debian/tests/control: Mark systemd-fsckd flaky again.
As promised in LP: 1915126, until further investigation.
File: debian/tests/control

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=68fbaab272af81aab29497f7c6a3e4e6e9aa091b

 -- Balint Reczey  Thu, 04 Mar 2021 12:19:05 +0100

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

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

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

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

** Changed in: systemd (Ubuntu Groovy)
   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/1913763

Title:
  hyperv: unable to distinguish PTP devices

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

Bug description:
  [impact]

  the /dev/ptp0 device for a hyperv instance may not be the correct,
  hyperv-provided, ptp device.

  [test case]

  on some hyperv instance types, particularly those that might contain
  passthrough network card(s) that also provide ptp, the first ptp
  device may not be the correct one to use for ptp, e.g. there may be
  multiple ones:

  $ ls /dev/ptp*
  /dev/ptp0 /dev/ptp1
  $ cat /sys/class/ptp/ptp0/clock_name
  hyperv
  $ cat /sys/class/ptp/ptp1/clock_name
  mlx5_p2p

  the order can change across boots, so a consistent way of addressing
  the hyperv-provided one is needed

  [regression potential]

  any regression would involve failure to properly create the ptp
  symlink, or other failure while udev is processing newly detected ptp
  device(s)

  [scope]

  this is needed in all releases

  this was fixed upstream with the commit
  32e868f058da8b90add00b2958c516241c532b70 which is not yet included in
  any release

  [original description]

  Hyperv provides a PTP device. On system with multiple PTP devices,
  services like Chrony don't have a way to know which one is which.

  We would like to have a udev rule to create a symlink to the hyperv
  clock. This way, services could be configured to always use this clock
  no matter if it is ptp0, ptp1, etc..

  For example:

  ```
  SUBSYSTEM=="ptp", ATTR{clock_name}=="hyperv", SYMLINK += "ptp_hyperv"
  ```

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

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


[Touch-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC

2021-03-08 Thread Mathew Hodson
** No longer affects: lxd (Ubuntu)

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

Title:
  NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start
  in LXC

Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  This regresses systemd's autopkgtest because it expects the system in
  the container to reach running state, but the system ends up in
  degraded state due to the service failing.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz
  ...

  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", 
line 68, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 
chars]ine'] != []

  First list contains 1 additional elements.
  First extra element 0:
  '● NetworkManager-wait-online.service loaded failed failed Network Manager 
Wait Online'

  + []
  - ['● NetworkManager-wait-online.service loaded failed failed Network Manager 
'
  -  'Wait Online']

  --
  Ran 23 tests in 4.435s
  ...

  Reproducible locally by installing n-m from -proposed, then restarting
  the system in the LXC container.

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

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


[Touch-packages] [Bug 1687791] Re: Install of kdump-tools fails

2021-03-07 Thread Mathew Hodson
*** This bug is a duplicate of bug 1661629 ***
https://bugs.launchpad.net/bugs/1661629

** Also affects: initramfs-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** This bug has been marked a duplicate of bug 1661629
   upgrade of kernel fails with mkinitramfs: failed to determine device for /

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

Title:
  Install of kdump-tools fails

Status in initramfs-tools package in Ubuntu:
  New
Status in makedumpfile package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New

Bug description:
  When installing Ubuntu xenial via netimage, installation fails because
  of an error, when configuring the kdump-tools. /var/log/syslog says:

  ...

  May  2 22:15:17 in-target: Setting up grub2 (2.02~beta2-36ubuntu3.9) ...^M
  May  2 22:15:17 in-target: Setting up lxc-common (2.0.7-0ubuntu1~16.04.2) 
...^M
  May  2 22:15:17 in-target: Running in chroot, ignoring request.^M
  May  2 22:15:17 in-target: invoke-rc.d: policy-rc.d denied execution of 
reload.^M
  May  2 22:15:17 in-target: Setting up grub-gfxpayload-lists (0.7) ...^M
  May  2 22:15:17 in-target: Processing triggers for libc-bin (2.23-0ubuntu7) 
...^M
  May  2 22:15:17 in-target: Processing triggers for systemd (229-4ubuntu17) 
...^M
  May  2 22:15:17 in-target: Processing triggers for ureadahead (0.100.0-19) 
...^M
  May  2 22:15:17 in-target: Processing triggers for dbus (1.10.6-1ubuntu3.3) 
...^M
  May  2 22:15:17 in-target: Errors were encountered while processing:^M
  May  2 22:15:17 in-target:  kdump-tools^M
  May  2 22:15:17 in-target:  linux-crashdump^M
  May  2 22:15:18 in-target: E: Sub-process /usr/bin/dpkg returned an error 
code (1)
  May  2 22:15:18 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ...
  May  2 22:15:18 in-target: dpkg: error processing package kdump-tools 
(--configure):
  May  2 22:15:18 in-target:  subprocess installed post-installation script 
returned error exit status 1
  May  2 22:15:18 in-target: dpkg: dependency problems prevent configuration of 
linux-crashdump:
  May  2 22:15:18 in-target:  linux-crashdump depends on kdump-tools; however:
  May  2 22:15:18 in-target:   Package kdump-tools is not configured yet.
  May  2 22:15:18 in-target: 
  May  2 22:15:18 in-target: dpkg: error processing package linux-crashdump 
(--configure):
  May  2 22:15:18 in-target:  dependency problems - leaving unconfigured
  May  2 22:15:18 in-target: Errors were encountered while processing:
  May  2 22:15:18 in-target:  kdump-tools
  May  2 22:15:18 in-target:  linux-crashdump
  May  2 22:15:18 main-menu[616]: WARNING **: Configuring 'pkgsel' failed with 
error code 100
  May  2 22:15:18 main-menu[616]: WARNING **: Menu item 'pkgsel' failed.

  
  After this the 'Select and install software' dialog pops up and says, that 
'Installation step failed'. If one presses '', one gets bombed back 
into the 'Ubuntu installer main menu'.
  Now you get into a loop, when choosing the 'Select and install software' item 
from the menu.

  Installer image is 'Linux foo 4.4.0-62-generic #83-Ubuntu SMP Wed Jan
  18 14:10:15 UTC 2017 x86_64 GNU/Linux'.

  The only workaround found so far is:
  cp -p /target/var/lib/dpkg/info/kdump-tools.postinst \
  /target/var/lib/dpkg/info/kdump-tools.postinst.suck
  printf '#!/bin/sh\nexit 0\n' \
  >/target/var/lib/dpkg/info/kdump-tools.postinst

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

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


[Touch-packages] [Bug 1905790] Re: Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for p11_child

2021-03-01 Thread Mathew Hodson
** No longer affects: ca-certificates (Ubuntu Focal)

** No longer affects: ca-certificates (Ubuntu)

** Bug watch removed: github.com/SSSD/sssd/issues #1041
   https://github.com/SSSD/sssd/issues/1041

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

Title:
  Make SSSD in 20.04 using OpenSSL and p11-kit (instead of NSS) for
  p11_child

Status in sssd package in Ubuntu:
  Fix Released
Status in sssd source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  SSSD supports in 20.04 two security backends: NSS and OpenSSL
  (speaking in past tense as upstream dropped NSS support completely).

  Those two backends are used for various generic crypto features (so
  they are interchangeable), but also for the management of the PKCS#11
  modules for smart cards.

  In this case, the main problem is that by using NSS it also relies on
  the presence of a "system NSS" database [1] that is something present
  in Fedora and RHEL, but not in ubuntu or generic Linux distributions.

  In order to make SSSD to find a smart card module, we would then need to 
create a such database that mentions a p11kit proxy that will eventually load 
the p11-kit module and then add the card CA certificate to the same DB (see 
more details in [2]).
  And even in such case... It will not work at login phase.

  This is making support for Smart-card based authentication in 20.04
  quite complicated, and hard to implement in professional environments
  (see bug #1865226).

  As per this, recompiling SSSD's p11_child to use OpenSSL (as it
  already happens starting from 20.10) would be enough to make the this
  tool (the one in charge for smartcard authentications and certificate
  matching) to be able to get the smartcard devices from p11-kit allowed
  modules and to check their certificate using CA certificates in the
  ubuntu system ca certificate files (or other configured file).

  One more mayor reason to do this, is also that if we fix 20.04 now to
  use the "proper" method, people who will configure smartcard access
  there via SSSD (not easily possible right now) won't be affected by
  future migrations.

  
  [ Proposed Implementations ]

  1) Use p11-kit and openssl for p11_child, by changing the build/test system 
(preferred)
     https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child

  2) Build both versions and package things accordingly (hackish)
     https://salsa.debian.org/3v1n0-guest/sssd/-/commits/p11-kit-p11_child-v1

  3) Recompile SSSD completely to use libcrypto as backend

  The option 3) has been finally choosen, but we also require migration
  scripts on upgrade.

  
  [ Test case ]

  With a smartcard reader available (and with a card in its slot) as reported 
by:
   $ p11-kit list-modules

  launch:
   $ sudo /usr/libexec/sssd/p11_child --pre -d 10 --debug-fd=2 \
     --nssdb=/etc/ssl/certs/ca-certificates.crt

  The tool should find your card:

  (2020-11-26 21:34:22:020395): [p11_child[100729]] [do_card] (0x4000): Module 
List:
  (2020-11-26 21:34:22:020481): [p11_child[100729]] [do_card] (0x4000): common 
name: [p11-kit-trust].
  (2020-11-26 21:34:22:020497): [p11_child[100729]] [do_card] (0x4000): dll 
name: [/usr/lib/x86_64-linux-gnu/pkcs11/p11-kit-trust.so].
  (2020-11-26 21:34:22:020569): [p11_child[100729]] [do_card] (0x4000): 
Description [/etc/ssl/certs/ca-certificates.crt  
PKCS#11 Kit ] Manufacturer [PKCS#11 Kit 
] flags [1] removable [false] token present [true].
  (2020-11-26 21:34:22:020611): [p11_child[100729]] [do_card] (0x4000): common 
name: [opensc-pkcs11].
  (2020-11-26 21:34:22:020646): [p11_child[100729]] [do_card] (0x4000): dll 
name: [/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so].
  (2020-11-26 21:34:22:025443): [p11_child[100729]] [do_card] (0x4000): 
Description [VMware Virtual USB CCID 00 00   
VMware  ] Manufacturer [VMware  
] flags [7] removable [true] token present [true].
  (2020-11-26 21:34:22:025725): [p11_child[100729]] [do_card] (0x4000): Found 
[MARCO TREVISAN (PIN CNS0)] in slot [VMware Virtual USB CCID 00 00][0] of 
module [1][/usr/lib/x86_64-linux-gnu/pkcs11/opensc-pkcs11.so].

  Then:
   1) If you previously configured SSSD match rules and/or CA certificates:
  - You should still get your certificate public key printed as output
  - Configured login with smartcard should continue working

   2) If SSSD was not configured to do smartcard authentication:
  - p11_child may fail if the card certificate was not previously added to
    the trusted DB, but this is outside of this test case.
  - What it matters is that the card is found.

  [ Regression potential ]

  While the change may involve quite different code paths when it comes
  to 

[Touch-packages] [Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement

2021-03-01 Thread Mathew Hodson
** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- cgroup v2 is not fully supported yet, proceeding with partial confinement
+ Switch to "unified" cgroup hierarchy (cgroupv2)

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

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

Title:
  Switch to "unified" cgroup hierarchy (cgroupv2)

Status in lxc:
  Fix Released
Status in lxd:
  Fix Released
Status in snapd:
  Confirmed
Status in docker.io package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New
Status in lxc package in Debian:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  Systemd upstream switched the default cgroup hierarchy to unified with
  v243. This change is reverted by the Ubuntu systemd packages, but as
  unified is the way to go per upstream support should be added to all
  relevant Ubuntu packges (and snaps):

  https://github.com/systemd/systemd/blob/v243/NEWS#L56

  * systemd now defaults to the "unified" cgroup hierarchy setup during
build-time, i.e. -Ddefault-hierarchy=unified is now the build-time
default. Previously, -Ddefault-hierarchy=hybrid was the default. 
This
change reflects the fact that cgroupsv2 support has matured
substantially in both systemd and in the kernel, and is clearly the
way forward. Downstream production distributions might want to
continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for
their builds as unfortunately the popular container managers have 
not
caught up with the kernel API changes.

  
  Systemd is rebuilt using the new default and is available from the following 
PPA for testing:

  https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh

  The autopkgtest results against other packges are available here:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain

  lxc autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz

  snapd autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz

  
  docker.io autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz

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

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


[Touch-packages] [Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement

2021-03-01 Thread Mathew Hodson
lxc (1:4.0.4-0ubuntu1) groovy; urgency=medium

  * New upstream bugfix release (4.0.4):
- Support for new Linux clone flags (clone into cgroup)
- Support for new Linux VFS system calls
- Internal symbols are now properly hidden from external consumers
  * New upstream bugfix release (4.0.3):
- Improvement to cgroupv1/cgroupv2 handling
- Various improvements and tests for lxc-usernsexec

 -- Stéphane Graber   Thu, 20 Aug 2020 18:07:53
-0400

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

** Changed in: lxc (Ubuntu)
   Importance: Undecided => Wishlist

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

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

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

Title:
  cgroup v2 is not fully supported yet, proceeding with partial
  confinement

Status in lxc:
  Fix Released
Status in lxd:
  Fix Released
Status in snapd:
  Confirmed
Status in docker.io package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New
Status in lxc package in Debian:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  Systemd upstream switched the default cgroup hierarchy to unified with
  v243. This change is reverted by the Ubuntu systemd packages, but as
  unified is the way to go per upstream support should be added to all
  relevant Ubuntu packges (and snaps):

  https://github.com/systemd/systemd/blob/v243/NEWS#L56

  * systemd now defaults to the "unified" cgroup hierarchy setup during
build-time, i.e. -Ddefault-hierarchy=unified is now the build-time
default. Previously, -Ddefault-hierarchy=hybrid was the default. 
This
change reflects the fact that cgroupsv2 support has matured
substantially in both systemd and in the kernel, and is clearly the
way forward. Downstream production distributions might want to
continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for
their builds as unfortunately the popular container managers have 
not
caught up with the kernel API changes.

  
  Systemd is rebuilt using the new default and is available from the following 
PPA for testing:

  https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh

  The autopkgtest results against other packges are available here:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain

  lxc autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz

  snapd autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz

  
  docker.io autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz

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

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


[Touch-packages] [Bug 1893563] Re: netplan: can't login to ap mode with psk

2021-02-28 Thread Mathew Hodson
network-manager (1.30.0-1ubuntu1) hirsute; urgency=medium

  * Resynchronize on Debian, remaining changes:
- Use systemd-resolved instead of dnsmasq
- debian/control:
  + Depend on isc-dhcp-client instead of recommends
  + Recommend network-manager-pptp
  + Suggest avahi-autoipd for IPv4LL support
- debian/rules, debian/network-manager.postinst:
  + Don't restart NetworkManager on upgrade but recommend restarting
the computer
- debian/rules, debian/network-manager.postinst:
  + Don't install sysvinit scripts or migrate from sysvinit
- debian/network-manager.postinst:
  + Don't add the netdev group.
  + drop in an empty override file for NetworkManager to manage all
devices for upgrade from any version, as long as there is no
netplan configuration yet.
- debian/default-wifi-powersave-on.conf, debian/rules:
  + Install a config file to enable WiFi powersave
- Enable build tests
- Add autopkgtests
- debian/source_network-manager.py, debian/network-manager.install,
  debian/network-manager.links: Add apport hook
- Add network-manager-config-connectivity-ubuntu package
- NetworkManager.conf: disable MAC randomization feature. There is no
  easy way for desktop users to disable this feature yet. And there are
  reports that it doesn't work well with some systems.
- Update Vcs links to point to Ubuntu branch
- Add patches. See patch descriptions for more details:
  + Provide-access-to-some-of-NM-s-interfaces-to-whoopsie.patch
  + Update-dnsmasq-parameters.patch
  + Disable-general-with-expect.patch
  + libnm-Check-self-still-NMManager-or-not.patch
  + dns-manager-don-t-merge-split-DNS-search-domains.patch (but disabled)
  + Read-system-connections-from-run.patch
- debian/tests/urfkill-integration - don't stop/start network manager
- debian/patches/ubuntu_revert_systemd.patch:
  + temporarly revert an upstream commit that made udev enabled under lxc,
the new systemd doesn't work there (lp: #1914062)

 -- Sebastien Bacher   Thu, 25 Feb 2021 15:30:59
+0100

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  netplan: can't login to ap mode with psk

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Fix Released
Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  I've setup my wifi cards as ap over a bridge using netplan.
  If I add:

  auth:
key-management: psk
password: "testinglang"

  then my clients are unable to connect.
  If I remove those lines above in netplan then the clients are able to connect 
but without a password.

  If I run wpa_cli -i wlp3s0 status, I get:

  bssid=4c:1d:96:71:a3:90
  freq=2412
  ssid=walad2
  id=0
  mode=AP
  pairwise_cipher=CCMP+TKIP
  group_cipher=TKIP
  key_mgmt=UNKNOWN
  wpa_state=COMPLETED
  p2p_device_address=4c:1d:96:71:a3:91
  address=4c:1d:96:71:a3:90
  uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a

  I notice that key_mgmt=UNKNOWN. Perhaps that's the problem?

  Any pointers on how to debug and fix this?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: netplan.io 0.99-0ubuntu3~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Aug 30 23:11:48 2020
  InstallationDate: Installed on 2020-08-16 (14 days ago)
  InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netplan.io
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement

2021-02-27 Thread Mathew Hodson
** Package changed: lxc (Ubuntu) => lxc

** Changed in: lxc
   Importance: Unknown => Undecided

** Also affects: systemd (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943981
   Importance: Unknown
   Status: Unknown

** Bug watch removed: LXC bug tracker #3198
   https://github.com/lxc/lxc/issues/3198

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

** Also affects: lxc (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944389
   Importance: Unknown
   Status: Unknown

** Bug watch removed: LXC bug tracker #3221
   https://github.com/lxc/lxc/issues/3221

** Bug watch removed: LXC bug tracker #3240
   https://github.com/lxc/lxc/issues/3240

** Bug watch removed: github.com/ubports/ubports-installer/issues #1448
   https://github.com/ubports/ubports-installer/issues/1448

** Also affects: lxd via
   https://github.com/lxc/lxd/issues/6587
   Importance: Unknown
   Status: Unknown

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

Title:
  cgroup v2 is not fully supported yet, proceeding with partial
  confinement

Status in lxc:
  Fix Released
Status in lxd:
  Unknown
Status in snapd:
  Confirmed
Status in docker.io package in Ubuntu:
  Confirmed
Status in lxcfs package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  In Progress
Status in lxc package in Debian:
  Unknown
Status in systemd package in Debian:
  Unknown

Bug description:
  Systemd upstream switched the default cgroup hierarchy to unified with
  v243. This change is reverted by the Ubuntu systemd packages, but as
  unified is the way to go per upstream support should be added to all
  relevant Ubuntu packges (and snaps):

  https://github.com/systemd/systemd/blob/v243/NEWS#L56

  * systemd now defaults to the "unified" cgroup hierarchy setup during
build-time, i.e. -Ddefault-hierarchy=unified is now the build-time
default. Previously, -Ddefault-hierarchy=hybrid was the default. 
This
change reflects the fact that cgroupsv2 support has matured
substantially in both systemd and in the kernel, and is clearly the
way forward. Downstream production distributions might want to
continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for
their builds as unfortunately the popular container managers have 
not
caught up with the kernel API changes.

  
  Systemd is rebuilt using the new default and is available from the following 
PPA for testing:

  https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh

  The autopkgtest results against other packges are available here:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain

  lxc autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz

  snapd autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz

  
  docker.io autopkgtest failing:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan-rbalint-systemd-unified-
  cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz

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

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


[Touch-packages] [Bug 1916570] Re: BlueZ 5.56 release

2021-02-23 Thread Mathew Hodson
** Tags added: upgrade-software-version

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

Title:
  BlueZ 5.56 release

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  BlueZ 5.56 is now available:

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/

  ver 5.56:
  Fix issue with setting AVDTP disconnect timer.
  Fix issue with AVDTP not sending GetCapabilities.
  Fix issue with AVDTP connecting using streaming mode.
  Fix issue with handling A2DP and remote SEP disappearing.
  Fix issue with handling session of A2DP channels.
  Fix issue with GATT and handling device removal.
  Fix issue with GATT not accepting multiple requests.
  Fix issue with HID report value callback registration.
  Add support for new advertising management command.
  Add support for battery D-Bus interface.

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

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


[Touch-packages] [Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2021-02-22 Thread Mathew Hodson
** No longer affects: pam (Ubuntu)

** No longer affects: pam (Ubuntu Bionic)

** No longer affects: pam (Ubuntu Focal)

** No longer affects: pam (Ubuntu Groovy)

** Also affects: gdm3 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953557
   Importance: Unknown
   Status: Unknown

** Project changed: gdm => ubuntu-translations

** Changed in: ubuntu-translations
   Importance: Unknown => Undecided

** Changed in: ubuntu-translations
 Remote watch: Debian Bug tracker #953557 => None

** No longer affects: ubuntu-translations

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

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

Status in GNOME Settings Daemon:
  Unknown
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  In Progress
Status in gdm3 source package in Bionic:
  Won't Fix
Status in gdm3 source package in Focal:
  Confirmed
Status in gnome-settings-daemon source package in Focal:
  New
Status in gdm3 source package in Groovy:
  Confirmed
Status in gnome-settings-daemon source package in Groovy:
  New
Status in gdm3 package in Debian:
  Unknown

Bug description:
  the pam profile for gdm-smartcard is missing. gdm refuses to login
  with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are
  pregenerated into debian/ and installed from there; gdm-smartcard is
  left out.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.4
  ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 14:30:30 2020
  InstallationDate: Installed on 2016-05-23 (1376 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+subscriptions

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


[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute)

2021-02-22 Thread Mathew Hodson
** Changed in: libsignon-glib (Ubuntu)
   Importance: Undecided => Low

** Tags added: package-conflict

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

Title:
  gir1.2-signon-2.0 needs to declare replace on older releases
  (Groovy2Hirsute)

Status in libsignon-glib package in Ubuntu:
  New

Bug description:
  gir1.2-signon-1.0 from groovy
  gir1.2-signon-2.0 from hirsute

  above two packages ship the same file /usr/lib/python3/dist-
  packages/gi/overrides/Signon.py without specifying how to resolve the
  conflict.

  Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', 
which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5
  Errors were encountered while processing:
   /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Probably needs a conflicts/replaces dependency added to the newer
  hirsute package.

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

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


[Touch-packages] [Bug 1915250] Re: buildd file owner/group for shared libraries

2021-02-18 Thread Mathew Hodson
** No longer affects: binutils (Ubuntu)

** No longer affects: glibc (Ubuntu)

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

Title:
  buildd file owner/group for shared libraries

Status in debhelper package in Ubuntu:
  Fix Committed
Status in fakeroot package in Ubuntu:
  Fix Committed
Status in debhelper package in Debian:
  Unknown

Bug description:
  fakeroot with glibc broke dpkg-deb for packages that do not use
  "Rules-Requires-Root: no" was broken.

  binutils stopped preserving permissions from objcopy & strip, leading
  to incorrect permissions of files after stripping.

  fakeroot is now patched with better glibc 2.33 support. TODO upstream
  changes.

  binutils is not fixed, as upstream changes are still being discussed.
  Instead we have worked around objcopy/strip in debhelper to call those
  tools from dh_strip in a safe manner.

  We also rebuilt binutils against glibc 2.32, to avoid this new
  behaviour. However, we need to resolve bintuils in a better way, one
  way or another.

  
  --

  the current state of -proposed creates deb packages with buildd file
  owner/group for shared libraries.

  reported at least for kwayland-integration.

  $ dpkg -c kwayland-integration_5.20.90-0ubuntu1_amd64.deb|grep \.so
  -rw-r--r-- doko/doko 18984 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kguiaddons/kmodifierkey/kmodifierkey_wayland.so
  -rw-r--r-- doko/doko 85392 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kwindowsystem/KF5WindowSystemKWaylandPlugin.so
  -rw-r--r-- doko/doko 35536 2021-01-21 23:44 
./usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeKWaylandPlugin.so

   - in a release pocket, rebuild binutils from proposed. correctly
     restores the file ownership

   - in a release pocket, update glibc from proposed. then rebuild
     binutils from proposed. shows the wrong ownership

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

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


[Touch-packages] [Bug 1915966] Re: Please merge initramfs-tools 0.139 from Debian unstable

2021-02-18 Thread Mathew Hodson
** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Please merge initramfs-tools 0.139 from Debian unstable

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Please merge initramfs-tools 0.139 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  shortly.

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

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


[Touch-packages] [Bug 1908502] Re: [MIR] libdeflate

2021-02-15 Thread Mathew Hodson
** No longer affects: tiff (Ubuntu)

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

Title:
  [MIR] libdeflate

Status in libdeflate package in Ubuntu:
  New
Status in libdeflate source package in Hirsute:
  New

Bug description:
  * Availability

  In sync with Debian, built on all architectures
  https://launchpad.net/ubuntu/+source/libdeflate/1.7-1

  * Rationale

  It's a new depends of libtiff

  * Security

  There is no known security issues

  https://security-tracker.debian.org/tracker/source-package/libdeflate
  https://people.canonical.com/~ubuntu-security/cve/pkg/libdeflate.html
  https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libdeflate

  * Quality assurance

  The desktop team is going to subscribe to the package

  https://launchpad.net/ubuntu/+source/libdeflate/+bugs
  https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libdeflate

  No open reports

  The package enables upstream tests during the build and ships basic
  autopkgtests

  * Dependencies

  No universe binary dependencies

  * Standards compliance

  current 4.5.1 standards-version, debhelper compat 13, dh style simple
  rules

  * Maintenance

  Upstream is active, the package is maintained in Debian and in sync
  for Ubuntu

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

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


[Touch-packages] [Bug 1914481] Re: use the size of the data when determining the server response

2021-02-14 Thread Mathew Hodson
** Changed in: whoopsie (Ubuntu Focal)
   Importance: Undecided => Medium

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

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

Title:
  use the size of the data when determining the server response

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Focal:
  Fix Committed
Status in whoopsie source package in Groovy:
  Fix Committed
Status in whoopsie source package in Hirsute:
  Fix Released

Bug description:
  [Note]
  This SRU has been built in a security-only PPA and should be released to both 
-updates and -security.

  [Impact]
  whoopsie's server_response code is using "g_string_append" instead of 
"g_string_append_len" which has the knock on effect of sending too much data to 
its "handle_response". This ends up being a problem if the daisy servers are 
running on Ubuntu 18.04 instead of Ubuntu 16.04.

  Here's an example when using whoopsie on groovy to send a crash to a
  bionic daisy server:

  [15:35:30] Sent; server replied with: No error
  [15:35:30] Response code: 200
  [15:35:30] Initial response data is: 2bbb776e-64e6-11eb-a8d6-00163eddedf4 
OOPSID
  0

  [15:35:30] Got command: OOPSID

  We can see a fair number of extra characters (\n0\n\n) after the OOSID
  command. This becomes more problematic when daisy requests a core dump
  from the client as the CORE command won't match and the client will
  never send the core dump.

  [Test Case]
  Setup a Bionic version of the Error Tracker:
  0) modify /etc/hosts so daisy.staging.ubuntu.com points to the IP of the 
apache server for daisy
  1) sudo service stop whoopsie
  2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
  3) Run test/submit-crash test-crashes/hirsute/amd64/_bin_cat.2001.crash
  4) check the whoopsie log file for "Got command: OOPSID" and extra data.

  With the version of whoopsie from -proposed this will not happen.
  Additionally, a regression test should be run against the staging
  version of the error tracker by removing the entry from /etc/hosts for
  the daisy.staging server. After confirming that one test crash works
  one should also send a python crash, and an end of life release crash
  as those all generate different response codes from the server.

  [Regression Potential]
  The code being changed is clearly wrong and doesn't confirm to the curl API 
https://curl.se/libcurl/c/CURLOPT_WRITEFUNCTION.html. Additionallly, this is 
similar to the code before r707 of daisy which introduced this change so there 
is little chance of regression. That being said we are running a regression 
test to ensure whoopsie works with servers running Ubuntu 16.04.

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

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


[Touch-packages] [Bug 1915307] Re: Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main)

2021-02-12 Thread Mathew Hodson
** Changed in: sudo (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Please merge sudo 1.9.5p2-2 (main) from Debian unstable (main)

Status in sudo package in Ubuntu:
  In Progress

Bug description:
  This requires a merge because there are changes in the Ubuntu version
  not present in the Debian version.

  -- Justification of patches removed from debian/patches/series --
  * typo-in-classic-insults.diff
* This exact patch is present in upstream version 1.9.5p2-2
  * paths-in-samples.diff
* This exact patch is present in upstream version 1.9.5p2-2
  * Whitelist-DPKG_COLORS-environment-variable.diff
* This exact patch is present in upstream version 1.9.5p2-2
  * CVE-2021-23239.patch
* This exact patch is NOT present in upstream version 1.9.5p2-2
  * The patch is made to address a vulnerability wherein users
were able to gain information about what directories existed
that they should not have had access to.
  * Upstream version 1.9.5p2-2 addresses this vulnerability using
the function sudo_edit_parent_valid in the file src/sudo_edit.c
  * Since the vulnerability is addressed in upstream version
1.9.5p2-2 it can safely be dropped
  * CVE-2021-3156-1.patch
* The code from this patch already exitsts in upstream
  version 1.9.5p2-2
  * CVE-2021-3156-2.patch
* The code from this patch already exitsts in upstream
  version 1.9.5p2-2
  * CVE-2021-3156-3.patch
* The code from this patch already exitsts in upstream
  version 1.9.5p2-2
  * CVE-2021-3156-4.patch
* The code from this patch already exitsts in upstream
  version 1.9.5p2-2
  * CVE-2021-3156-5.patch
* The code from this patch already exitsts in upstream
  version 1.9.5p2-2
  * ineffective_no_root_mailer.patch
* This exact patch is present in upstream version 1.9.5p2-2
  under the name fix-no-root-mailer.diff

  Changes:
* Merge from Debian unstable. (LP: #1915307)
  Remaining changes:
  - debian/rules:
+ use dh-autoreconf
  - debian/rules: stop shipping init scripts, as they are no longer
necessary.
  - debian/rules:
+ compile with --without-lecture --with-tty-tickets --enable-admin-flag
+ install man/man8/sudo_root.8 in both flavours
+ install apport hooks
  - debian/sudo-ldap.dirs, debian/sudo.dirs:
+ add usr/share/apport/package-hooks
  - debian/sudo.pam:
+ Use pam_env to read /etc/environment and /etc/default/locale
  environment files. Reading ~/.pam_environment is not permitted due
  to security reasons.
  - debian/sudoers:
+ also grant admin group sudo access
+ include /snap/bin in the secure_path

  sudo (1.9.5p2-2) unstable; urgency=medium

* patch from upstream repo to fix NO_ROOT_MAILER

  sudo (1.9.5p2-1) unstable; urgency=high

* new upstream version, addresses CVE-2021-3156

  sudo (1.9.5p1-1.1) unstable; urgency=high

* Non-maintainer upload.
* Heap-based buffer overflow (CVE-2021-3156)
  - Reset valid_flags to MODE_NONINTERACTIVE for sudoedit
  - Add sudoedit flag checks in plugin that are consistent with front-end
  - Fix potential buffer overflow when unescaping backslashes in user_args
  - Fix the memset offset when converting a v1 timestamp to TS_LOCKEXCL
  - Don't assume that argv is allocated as a single flat buffer

  sudo (1.9.5p1-1) unstable; urgency=medium

* new upstream version, closes: #980028

  sudo (1.9.5-1) unstable; urgency=medium

* new upstream version

  sudo (1.9.4p2-2ubuntu3) hirsute; urgency=medium

* SECURITY UPDATE: ineffective NO_ROOT_MAILER hardening option
  - debian/patches/ineffective_no_root_mailer.patch: fix NO_ROOT_MAILER
in plugins/sudoers/logging.c, plugins/sudoers/policy.c.
  - No CVE number

  sudo (1.9.4p2-2ubuntu2) hirsute; urgency=medium

* SECURITY UPDATE: dir existence issue via sudoedit race
  - debian/patches/CVE-2021-23239.patch: fix potential directory existing
info leak in sudoedit in src/sudo_edit.c.
  - CVE-2021-23239
* SECURITY UPDATE: heap-based buffer overflow
  - debian/patches/CVE-2021-3156-1.patch: reset valid_flags to
MODE_NONINTERACTIVE for sudoedit in src/parse_args.c.
  - debian/patches/CVE-2021-3156-2.patch: add sudoedit flag checks in
plugin in plugins/sudoers/policy.c.
  - debian/patches/CVE-2021-3156-3.patch: fix potential buffer overflow
when unescaping backslashes in plugins/sudoers/sudoers.c.
  - debian/patches/CVE-2021-3156-4.patch: fix the memset offset when
converting a v1 timestamp to TS_LOCKEXCL in
plugins/sudoers/timestamp.c.
  - debian/patches/CVE-2021-3156-5.patch: don't assume that argv is

[Touch-packages] [Bug 1915347] Re: Sync pyxdg 0.27-2 (main) from Debian unstable (main)

2021-02-12 Thread Mathew Hodson
** Changed in: pyxdg (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync pyxdg 0.27-2 (main) from Debian unstable (main)

Status in pyxdg package in Ubuntu:
  In Progress

Bug description:
  Please sync pyxdg 0.27-2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Fix compatibility issue with python 3.8.4 (Closes: #964609, #968399)

  pyxdg delta was meant to fix an incompatibility with Python 3.8.4
  This was causing a FTBFS at the time. The initial solution was cherry picked
  from an upstream github PR and has since been released.
  Debian BTS bug is referenced in both ubuntu and debian ChangeLog

  Changelog entries since current hirsute version 0.26-3ubuntu1:

  pyxdg (0.27-2) unstable; urgency=medium

* Add the missing build dependency on setuptools.

   -- Andrej Shadura   Wed, 13 Jan 2021 12:13:36
  +0100

  pyxdg (0.27-1) unstable; urgency=medium

[ Andrej Shadura ]
* New upstream release (Closes: #949738, #964609).
* Refresh patches and drop a patch applied upstream.
* Provide the actual module name.
* Add a compatibility layer for the alternative
  xdg package.

[ Debian Janitor ]
* Use secure URI in Homepage field.

[ Håvard Flaget Aasen ]
* Set upstream metadata fields: Bug-Database, Bug-Submit,
  Repository, Repository-Browse.

[ Ondřej Nový ]
* d/control: Update Maintainer field with new Debian Python Team
  contact address.
* d/control: Update Vcs-* fields with new Debian Python Team Salsa
  layout.

   -- Andrej Shadura   Tue, 12 Jan 2021 15:17:29
  +0100

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

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


[Touch-packages] [Bug 1915211] Re: Please merge logrotate 3.18.0-1 (main) from Debian unstable (main) Edit

2021-02-09 Thread Mathew Hodson
** Changed in: logrotate (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Please merge logrotate 3.18.0-1 (main) from Debian unstable (main)
  Edit

Status in logrotate package in Ubuntu:
  Confirmed

Bug description:
  Please merge logrotate 3.18.0-1 (main) from Debian unstable (main)

  At the time of filling this bug, the target debian unstable version is
  3.18.0-1

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

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


[Touch-packages] [Bug 1164016] Re: restore type-ahead find

2021-02-08 Thread Mathew Hodson
** Bug watch removed: gitlab.gnome.org/GNOME/nautilus/-/issues #1154
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/1154

** Bug watch removed: gitlab.gnome.org/GNOME/nautilus/-/issues #1157
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/1157

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

Title:
  restore type-ahead find

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

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

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


[Touch-packages] [Bug 1164016] Re: restore type-ahead find

2021-02-08 Thread Mathew Hodson
** Changed in: nautilus
   Importance: Wishlist => Unknown

** Changed in: nautilus
   Status: Expired => Unknown

** Changed in: nautilus
 Remote watch: GNOME Bug Tracker #681871 => bugzilla.gnome.org/ #681871

** Bug watch removed: GNOME Bug Tracker #681871
   https://gitlab.gnome.org/681871

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

Title:
  restore type-ahead find

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

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

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


[Touch-packages] [Bug 1915005] Re: Please merge findutils 4.8.0 from Debian unstable

2021-02-08 Thread Mathew Hodson
** Changed in: findutils (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Please merge findutils 4.8.0 from Debian unstable

Status in findutils package in Ubuntu:
  New

Bug description:
  Please merge findutils 4.8.0-1 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  shortly.

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

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


[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support

2021-02-07 Thread Mathew Hodson
** Changed in: software-properties (Ubuntu)
   Status: Triaged => Fix Committed

** Tags removed: verification-needed

** Changed in: software-properties (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: software-properties (Ubuntu Groovy)
   Importance: Medium => High

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

Title:
  gi.repository.GLib.GError: pk-client-error-quark: could not do
  untrusted question as no klass support

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Eoan:
  Won't Fix
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Groovy:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
software-properties.  This problem was most recently seen with package version 
0.98.2, the problem page at 
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

  [Back trace]
  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 86, in on_pktask_finish
  results = self._pktask.generic_finish(result)
  gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted 
question as no klass support (8)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 89, in on_pktask_finish
  Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
    File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
    File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in 
__init__
  self._init(*args, **new_kwargs)
    File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
    File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in 
__init__
  _window_init(self, *args, **kwargs)
    File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
  TypeError: could not convert value for property `transient_for' from 
DialogCacheOutdated to GtkWindow

  
  [Impact] 

   * If selected mirrors are not reachable or have
 expired GPG keys, software-properties-gtk
 would crash

  [Test Case]

   * Edit the file /usr/share/python-apt/templates/Ubuntu.mirrors

   * Find your locale in this file and add a non-existent URL
 to the list

   * Run software-properties-gtk and choose your newly added
 URL from the "Download From" dropdown menu

   * Press "Close" in the bottom right, and when
 prompted press "Reload"

   * You should be presented with an error window rather than
 the program crashing

  [Where problems could occur]

   * The new error window binds to the parent window. If the
 parent window has gotten into a bad state this could
 cause problems

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

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


[Touch-packages] [Bug 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression

2021-02-06 Thread Mathew Hodson
** Tags added: regression-update

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

Title:
  GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active
  Directory, causing recent adcli regression

Status in adcli package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in adcli source package in Bionic:
  Fix Released
Status in cyrus-sasl2 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  A recent release of adcli 0.8.2-1ubuntu1 to bionic-updates caused a
  regression for some users when attempting to join a Active Directory
  realm. adcli introduced a default behaviour change, moving from GSS-
  API to GSS-SPNEGO as the default channel encryption algorithm.

  adcli uses the GSS-SPNEGO implementation from libsasl2-modules-gssapi-
  mit, a part of cyrus-sasl2. The implementation seems to have some
  compatibility issues with particular configurations of Active
  Directory on recent Windows Server systems.

  Particularly, adcli sends a ldap query to the domain controller, which
  responds with a tcp ack, but never returns a ldap response. The
  connection just hangs at this point and no more traffic is sent.

  You can see it on the packet trace below:

  https://paste.ubuntu.com/p/WRnnRMGBPm/

  On Focal, where the implementation of GSS-SPNEGO is working, we see a
  full exchange, and adcli works as expected:

  https://paste.ubuntu.com/p/8668pJrr2m/

  The fix is to not assume use of confidentiality and integrity modes,
  and instead use the flags negotiated by GSS-API during the initial
  handshake, as required by Microsoft's implementation.

  [Testcase]

  You will need to set up a Windows Server 2019 system, install and
  configure Active Directory and enable LDAP extensions and configure
  LDAPS and import the AD SSL certificate to the Ubuntu client. Create
  some users in Active Directory.

  On the Ubuntu client, set up /etc/hosts with the hostname of the
  Windows Server machine, if your system isn't configured for AD DNS.

  From there, install adcli 0.8.2-1 from -release.

  $ sudo apt install adcli

  Set up a packet trace with tcpdump:

  $ sudo tcpdump -i any port '(389 or 3268 or 636 or 3269)'

  Next, join the AD realm using the normal GSS-API:

  # adcli join --verbose -U Administrator --domain WIN-
  SB6JAS7PH22.testing.local --domain-controller WIN-
  SB6JAS7PH22.testing.local --domain-realm TESTING.LOCAL

  You will be prompted for Administrator's passowrd.

  The output should look like the below:

  https://paste.ubuntu.com/p/NWHGQn746D/

  Next, enable -proposed, and install adcli 0.8.2-1ubuntu1 which caused the 
regression.
  Repeat the above steps. Now you should see the connection hang.

  https://paste.ubuntu.com/p/WRnnRMGBPm/

  Finally, install the fixed cyrus-sasl2 package from -proposed

  https://launchpad.net/~mruffell/+archive/ubuntu/lp1906627-test

  $ sudo apt-get update
  $ sudo apt install libsasl2-2 libsasl2-modules libsasl2-modules-db 
libsasl2-modules-gssapi-mit

  Repeat the steps. GSS-SPNEGO should be working as intended, and you
  should get output like below:

  https://paste.ubuntu.com/p/W5cJNGvCsx/

  [Where problems could occur]

  Since we are changing the implementation of GSS-SPNEGO, and cyrus-
  sasl2 is the library which provides it, we can potentially break any
  package which depends on libsasl2-modules-gssapi-mit for GSS-SPNEGO.

  $ apt rdepends libsasl2-modules-gssapi-mit
  libsasl2-modules-gssapi-mit
  Reverse Depends:
   |Suggests: ldap-utils
    Depends: adcli
    Conflicts: libsasl2-modules-gssapi-heimdal
   |Suggests: libsasl2-modules
    Conflicts: libsasl2-modules-gssapi-heimdal
   |Recommends: sssd-krb5-common
   |Suggests: slapd
   |Suggests: libsasl2-modules
   |Suggests: ldap-utils
   |Depends: msktutil
    Conflicts: libsasl2-modules-gssapi-heimdal
   |Depends: libapache2-mod-webauthldap
    Depends: freeipa-server
    Depends: freeipa-client
    Depends: adcli
    Depends: 389-ds-base
   |Recommends: sssd-krb5-common
   |Suggests: slapd
   |Suggests: libsasl2-modules

  While this SRU makes cyrus-sasl2 work with Microsoft implementations
  of GSS-SPNEGO, which will be the more common usecase, it may change
  the behaviour  when connecting to a MIT krb5 server with the GSS-
  SPNEGO protocol, as krb5 assumes use of confidentiality and integrity
  modes. This shouldn't be a problem as the krb5 implementation signals
  its intentions by setting the correct flags during handshake, which
  these patches to cyrus-sasl2 should now parse correctly.

  [Other Info]

  The below two commits are needed. The first fixes the problem, the second 
fixes
  some unused parameter warnings.

  commit 816e529043de08f3f9dcc4097380de39478b0b16
  Author: Simo Sorce 
  Date:   Thu Feb 16 15:25:56 2017 -0500
  Subject: Fix GSS-SPNEGO mechanism's 

[Touch-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.

2021-02-01 Thread Mathew Hodson
** No longer affects: coreutils (Ubuntu Groovy)

** No longer affects: coreutils (Ubuntu Focal)

** No longer affects: coreutils (Ubuntu)

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

Title:
  ZFS revert from grub menu not working.

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Focal:
  Fix Released
Status in zfs-linux source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * Users can’t revert to previous snapshots when enabling the hw enablement 
stack kernel on focal or using any more recent version.
   * The option is available on grub and will let you with a broken system, 
partially cloned.

  [Test Case]

   * Boot on a system, using ZFS and ZSys.
   * In grub, select "History" entry
   * Select one of the "Revert" option: the system should boot after being 
reverted with an older version.

  
  [Where problems could occur]
   * The code is in the initramfs, where the generated id suffix for all our 
ZFS datasets was empty due to new coreutils/kernels.
   * We replace dd with another way (more robust and simple) for generating 
this ID.

  
  -

  @coreutils maintainers, any idea why dd is being flagged as having an
  executable stack?

  

  When I try to revert to a previous state from the grub menu, the boot
  fails. The system drops me to a repair modus.

  zfs-mount-generator fails with the message:
  couldn't ensure boot: Mounted clone bootFS dataset created by initramfs 
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".

  After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed 
without a suffix.
  After a little investigation I found the problem in 
/usr/share/initramfs-tools/scripts/zfs at the end in function
  uid()
  {
     dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 
'a-z0-9' | cut -c-6
  }, the dd command fails during boot with the message "process 'dd' started 
with executable stack.
  After this an empty uid is returned which explains the dataset without a 
proper suffix.
  Replacing the function  with:
  uid()
  {
     grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
  }

  fixes the problem.

  Ubuntu version is:
  Description:Ubuntu Groovy Gorilla (development branch)
  Release:20.10

  zfs-initramfs version is:
  0.8.4-1ubuntu11

  With regards,

  Usarin Heininga

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: zfs-initramfs 0.8.4-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Sep  4 20:23:44 2020
  InstallationDate: Installed on 2020-09-02 (2 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1908065] Re: Invalid SYSLOG_PID for (systemd) journal messages

2021-01-23 Thread Mathew Hodson
** No longer affects: systemd (Ubuntu)

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

** Changed in: sssd (Ubuntu)
   Status: Triaged => Fix Released

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

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

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

Title:
  Invalid SYSLOG_PID for (systemd) journal messages

Status in sssd package in Ubuntu:
  Fix Released
Status in sssd source package in Focal:
  New

Bug description:
  [Impact]

   * On Ubuntu (Focal) 20.04, SSSD 2.2.3-3, logs in Journald have
  invalid (non-numeric) SYSLOG_PID. Any tooling collecting SYSLOG_PID
  further, or attempting to work with syslog directly, fail to parse the
  PID as number.

   * Systemd does not validate, and simply expects SYSLOG_PID as numeric 
integers formatted as decimal strings:
     
https://www.freedesktop.org/software/systemd/man/systemd.journal-fields.html#SYSLOG_FACILITY=

  [Test Case]

   * Deploy fresh 20.04 image, and update:
     apt update && apt dist-upgrade

   * apt -qqy install sssd

   * cat << EOF > /etc/sssd/sssd.conf
  [sssd]
    config_file_version = 2
    domains = EXAMPLE.COM
    services =

  [nss]

  [pam]

  [sudo]

  [domain/EXAMPLE.COM]
    id_provider = files
    access_provider = permit
  EOF

   * chmod 600 /etc/sssd/sssd.conf

   * systemctl restart sssd.service

   * journalctl -o verbose -u sssd-sudo.service | grep SYSLOG_PID=
     SYSLOG_PID=sudo

   * journalctl -u sssd.service # Produces malformed example lines:
     Dec 07 14:10:00 servername sssd[be[1234]: Starting up

   * grep sssd /var/log/syslog # Displays non-numeric PIDs:
     Dec  7 08:00:00 servername sssd[be[EXAMPLE.COM]]: Starting up
     Dec  7 08:00:00 servername sssd[nss]: Starting up
     Dec  7 08:00:00 servername sssd[sudo]: Starting up
     Dec  7 08:00:00 servername sssd[pam]: Starting up

  [Where problems could occur]

   * Someone might depend on the malformed output already, and have
  tooling in place to transform it manually.

  [Other Info]

   * Is not reproducible on Ubuntu (Groovy) 20.10 containing SSSD
  2.3.1-3. Considering Debian testing is currently at SSSD 2.4.0-1, it
  does not appear applicable to fix in upstream.

   * The package itself does not appear to provide any SYSLOG_PID. The
  SYSLOG_IDENTIFIER appears to instead 'leak' over into PID, hinting at
  trouble on systemd side. SSSD source at:
  https://github.com/SSSD/sssd/blob/sssd-2_2_3/src/util/sss_log.c#L110

   * Applying a change to SYSLOG_IDENTIFIER (prefixing with "sssd[" and 
suffixing with "]") results in "SYSLOG_IDENTIFIER=sssd_be" being logged, and no 
SYSLOG_PID being reported.
 Cherry-picked upstream commit for testing: 
https://github.com/SSSD/sssd/commit/18233532b72e62452eac6886652fa633ba055d8c

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

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

2021-01-22 Thread Mathew Hodson
libx11 (2:1.7.0-1) unstable; urgency=medium

  * New upstream release.
  * patches: Refreshed.
  * signing-key: Added key from Keith Packard.
  * symbols: Updated.

 -- Timo Aaltonen   Wed, 06 Jan 2021 20:47:58 +0200

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

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

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

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

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

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

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

-- 
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:
  Fix Released
Status in libx11 source package in Bionic:
  New
Status in libx11 source package in Focal:
  New
Status in libx11 source package in Groovy:
  New

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 1813581] Re: gpgme1.0 ftbfs in 18.04 LTS

2021-01-21 Thread Mathew Hodson
** Changed in: gpgme1.0 (Ubuntu)
   Status: Won't Fix => Fix Released

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

Title:
  gpgme1.0 ftbfs in 18.04 LTS

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  gpgme1.0 ftbfs.

  * Start testing of TofuInfoTest *
  Config: Using QtTest library 5.9.5, Qt 5.9.5 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 7.3.0)
  PASS   : TofuInfoTest::initTestCase()
  PASS   : TofuInfoTest::testTofuNull()
  PASS   : TofuInfoTest::testTofuInfo()
  PASS   : TofuInfoTest::testTofuSignCount()
  PASS   : TofuInfoTest::testTofuKeyList()
  PASS   : TofuInfoTest::testTofuPolicy()
  FAIL!  : TofuInfoTest::testTofuConflict() 'sig.validity() == 
Signature::Marginal' returned FALSE. ()
     Loc: [t-tofuinfo.cpp(458)]
  PASS   : TofuInfoTest::cleanupTestCase()
  Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted, 2386ms
  * Finished testing of TofuInfoTest *
  FAIL: t-tofuinfo

  [Test case]
  build it

  [Regression potential]
  This only changes the test suite run during build, and that one currently 
fails, so it can't cause any regression.

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

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


[Touch-packages] [Bug 1901528] Re: [Ubuntu 20.10] - When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB (gzip)

2021-01-21 Thread Mathew Hodson
** No longer affects: zlib (Ubuntu)

** No longer affects: zlib (Ubuntu Groovy)

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

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

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

Title:
  [Ubuntu 20.10] - When zlib acceleration is enabled, gzip fails when
  given multiple files larger than 5KB (gzip)

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in gzip package in Ubuntu:
  Fix Released
Status in gzip source package in Groovy:
  Fix Committed

Bug description:
  When zlib acceleration is enabled, gzip fails when given multiple
  files larger than 5KB.

  This problem does not happen when running gzip against a single file
  at a time. It only happens when you provide multiple files as gzip
  arguments.

  So this works whether zlib acceleration is enabled or not:

  for file in file1 file2; do gzip $file ; done

  But this fails (when zlib acceleration is enabled):

  gzip file1 file2

  The patch to fix this has been accepted upstream:
  
https://git.savannah.gnu.org/cgit/gzip.git/commit/?id=be0a534ba2b6e77da289de8da79e70843b1028cc

  [Impact]

   * With zlib acceleration enabled, attempting to compress multiple files
 over 5MB would cause a segmentation fault.

   * The files could still be compressed in separate commands

  [Test Case]

   * Create two files that are larger than 5MB

   * Enable zlib acceleration (z15 hardware required)

   * Run the command gzip  

   * NOTE: we do not have access to z15 hardware and therefore are relying
 on IBM to verify this fix

  [Where problems could occur]

   * Due to lack of testing resources, it's possible the bug has not been
 fully fixed, and the segmentation fault could still occur.

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

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


[Touch-packages] [Bug 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)

2021-01-21 Thread Mathew Hodson
** Changed in: binutils (Ubuntu)
   Importance: Undecided => Medium

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

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

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

Title:
  [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)

Status in Ubuntu on IBM z Systems:
  In Progress
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Focal:
  New
Status in binutils source package in Groovy:
  Fix Released

Bug description:
  == Comment: #0 - Heinz-Werner Seeck  - 
2020-07-31 03:28:30 ==
  On z13 we have that vector alignment hints are already accepted. This 
backport enables GAS to accept such hints not only for target z14 but also for 
z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly 
benefit from such alignment hints. (note a separate bugzilla entry for GCC 
allowing to emit alignment hints for z13 will be opened shortly)

  This is a backport of upstreams commit 26b6ab7a0e.
   
  Userspace tool common name: as 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: binutils

  
  Already included within 20.10 via LP:
  https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654

  This should also be SRUed for 20.04

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

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


[Touch-packages] [Bug 1912091] Re: Memory Leak GNU Tar 1.33

2021-01-21 Thread Mathew Hodson
** Changed in: tar (Ubuntu)
   Importance: Undecided => Low

** Tags removed: security tar
** Tags added: focal

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

Title:
  Memory Leak GNU Tar 1.33

Status in tar package in Ubuntu:
  New

Bug description:
  
  An issue was discovered in GNU Tar 1.33 and earlier. There is a memory leak 
in read_header() in list.c in the tar application. Occastionally, ASAN detects 
an out of bounds memory read. Valgrind confirms the memory leak in the standard 
tar tool installed by default. This degrades the availability of the tar tool, 
and could potentially result in other memory-related issues.

  Common Weakness Enumeration IDs for reference:
  CWE-401: Missing Release of Memory after Effective Lifetime
  CWE-125: Out-of-bounds Read

  Attached to this report is a PoC malcrafted file "1311745-out-
  bounds.tar"

  VALGRIND OUTPUT:
  valgrind tar -xf 1311745-out-bounds.tar 
  ==3776== Memcheck, a memory error detector
  ==3776== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
  ==3776== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info
  ==3776== Command: tar -xf output/1311745-out-bounds.tar
  ==3776== 
  tar: Unexpected EOF in archive
  tar: Exiting with failure status due to previous errors
  ==3776== 
  ==3776== HEAP SUMMARY:
  ==3776== in use at exit: 1,311,761 bytes in 2 blocks
  ==3776==   total heap usage: 52 allocs, 50 frees, 1,349,212 bytes allocated
  ==3776== 
  ==3776== LEAK SUMMARY:
  ==3776==definitely lost: 1,311,745 bytes in 1 blocks
  ...

  NOTE: Version 1.30, 1.32, 1.33 were tested and confirmed to be
  vulnerable.

  lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  apt-cache policy tar
  tar:
Installed: 1.30+dfsg-7ubuntu0.20.04.1
Candidate: 1.30+dfsg-7ubuntu0.20.04.1

  ---
  Carlos

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

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


[Touch-packages] [Bug 1876495] Re: bash-completion incorrectly shows source package names for APT

2021-01-18 Thread Mathew Hodson
** Changed in: apt (Ubuntu Focal)
   Importance: Undecided => Low

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

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

Title:
  bash-completion incorrectly shows source package names for APT

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Source packages have been included in apt-cache pkgnames, and virtual
  packages have not been included in apt-cache pkgnames --all-names. The
  former leads to completions autocompleting to source package names
  where they only should complete to binaries.

  [Test case]
  An automated test case is included in the test suite

  test-ubuntu-bug-1876495-pkgnames-virtual

  It verifies that pkgnames does not return source package names, and
  that pkgnames --all-names does return source package names and virtual
  package names.

  [Where problems could occur]
  In the pkgnames command only. If there's a bug, it could exclude or include 
packages it should not.

  [Original bug report]
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal, enter one of the commands below

  2a. apt install brisk
  2b. apt source brisk-menu
  2c. apt-get install brisk
  2d. apt-get source brisk-menu
  2e. apt-cache policy brisk

  Expected results:
  * The bash-completion should not lead to package name as there are no binary 
packages named with starting part "brisk" (see 
https://packages.ubuntu.com/search?suite=all=names=brisk )

  Actual results:
  * all commands below get completed to the name of source package - in this 
example named "brisk-menu"
  (see 
https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames).
 This is absolutely unexpected, as user can not really install this package in 
binary form.

  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May  2 20:35:48 2020
  Dependencies:

  InstallationDate: Installed on 2020-04-22 (9 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward

2021-01-18 Thread Mathew Hodson
** Changed in: util-linux (Ubuntu)
   Status: In Progress => Won't Fix

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

Title:
  Enabling DMESG_RESTRICT in Groovy Onward

Status in linux package in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Won't Fix
Status in linux source package in Groovy:
  Fix Released
Status in procps source package in Groovy:
  Fix Released
Status in util-linux source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT
  feature by default for Groovy onward, proposed to ubuntu-devel:

  https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html

  The kernel log buffer contains a wealth of sensitive information, such
  as detailed call traces and kernel addresses found in register dumps
  in kernel oops messages.

  Exploit developers and attackers can leverage these information leaks
  to get past KASLR, and they can use the kernel log buffer to get
  instant feedback on their privilege escalation attacks, as failures
  will be shown as further oops messages, which attackers can use to fix
  and tune their programs until they work.

  Currently, if I create a new, unprivileged user on a Focal system,
  they cannot access /var/log/kern.log, /var/log/syslog or see system
  events in journalctl. But yet, they are given free reign to the kernel
  log buffer.

  $ sudo adduser dave
  $ su dave
  $ groups
  dave
  $ cat /var/log/kern.log
  cat: /var/log/kern.log: Permission denied
  $ cat /var/log/syslog
  cat: /var/log/syslog: Permission denied
  $ journalctl
  Hint: You are currently not seeing messages from other users and the system.
    Users in groups 'adm', 'systemd-journal' can see all messages.
    Pass -q to turn off this notice.
  Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target.
  Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms.
  $ dmesg
  [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014)
  (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 
15:46:55
  UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic
  root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro
  ...

  I propose that we restrict access to dmesg to users in group 'adm'
  like so:

  1) Add kernel.dmesg_restrict = 1 to
 /etc/sysctl.d/10-kernel-hardening.conf
  2) Following changes to /bin/dmesg permissions in package 'util-linux'
  - Ownership changes to root:adm
  - Permissions changed to 0750 (-rwxr-x---)
  - Add cap_syslog capability to binary.

  For most users, they will use the initial admin account, which is in
  the 'adm' group already, and will see no impact to these changes. If a
  log scraper type program needs access to dmesg, the user the daemon
  runs as can simply be added to the 'adm' group.

  [Testcase]

  Currently, all users can run /usr/bin/dmesg to view the kernel log
  buffer:

  $ dmesg
  [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014)
  (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 
15:46:55
  UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic
  root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro
  ...

  When the changes are applied, the default admin user will be able to
  view dmesg (since they are in group 'adm'), while new unprivileged
  users will not.

  Test packages are available in the following ppa:
  https://launchpad.net/~mruffell/+archive/ubuntu/lp1886112-test

  $ whoami
  ubuntu
  $ groups
  ubuntu adm cdrom sudo dip plugdev
  $ dmesg
  [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014)
  (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 
15:46:55
  UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic
  root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro
  ...

  $ sudo adduser dave
  $ su dave
  $ groups
  dave
  $ dmesg
  -bash: /usr/bin/dmesg: Permission denied

  [Regression Potential]

  Some users or log scraper type programs may need to view the kernel
  log buffer, or have access to dmesg. In this case, the underlying
  service user would need to be added to the 'adm' group.

  Users have the ability to disable DMESG_RESTRICT by changing
  kernel.dmesg_restrict sysctl in /etc/sysctl.d/10-kernel-hardening.conf
  from '1' to '0', followed by a reboot.

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2021-01-17 Thread Mathew Hodson
** Bug watch added: Debian Bug tracker #972552
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972552

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  In Progress
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package 

[Touch-packages] [Bug 1876495] Re: bash-completion incorrectly shows source package names for APT

2021-01-17 Thread Mathew Hodson
** No longer affects: bash-completion (Ubuntu Hirsute)

** No longer affects: bash-completion (Ubuntu Groovy)

** No longer affects: bash-completion (Ubuntu Focal)

** No longer affects: bash-completion (Ubuntu)

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

Title:
  bash-completion incorrectly shows source package names for APT

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Fix Committed
Status in apt source package in Groovy:
  Fix Committed
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Source packages have been included in apt-cache pkgnames, and virtual
  packages have not been included in apt-cache pkgnames --all-names. The
  former leads to completions autocompleting to source package names
  where they only should complete to binaries.

  [Test case]
  An automated test case is included in the test suite

  test-ubuntu-bug-1876495-pkgnames-virtual

  It verifies that pkgnames does not return source package names, and
  that pkgnames --all-names does return source package names and virtual
  package names.

  [Where problems could occur]
  In the pkgnames command only. If there's a bug, it could exclude or include 
packages it should not.

  [Original bug report]
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal, enter one of the commands below

  2a. apt install brisk
  2b. apt source brisk-menu
  2c. apt-get install brisk
  2d. apt-get source brisk-menu
  2e. apt-cache policy brisk

  Expected results:
  * The bash-completion should not lead to package name as there are no binary 
packages named with starting part "brisk" (see 
https://packages.ubuntu.com/search?suite=all=names=brisk )

  Actual results:
  * all commands below get completed to the name of source package - in this 
example named "brisk-menu"
  (see 
https://packages.ubuntu.com/search?suite=all=all=any=brisk=sourcenames).
 This is absolutely unexpected, as user can not really install this package in 
binary form.

  ProblemType: Bug
  DistroRelease: Ubuntu Kylin 20.04
  Package: bash-completion 1:2.10-1ubuntu1 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30
  Uname: Linux 5.4.0-28-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Sat May  2 20:35:48 2020
  Dependencies:

  InstallationDate: Installed on 2020-04-22 (9 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200422)
  PackageArchitecture: all
  SourcePackage: bash-completion
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1894329] Re: ZFS revert from grub menu not working.

2021-01-17 Thread Mathew Hodson
** Tags added: verification-done-groovy verification-needed-focal

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

Title:
  ZFS revert from grub menu not working.

Status in coreutils package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in coreutils source package in Focal:
  Incomplete
Status in zfs-linux source package in Focal:
  Fix Committed
Status in coreutils source package in Groovy:
  Incomplete
Status in zfs-linux source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

   * Users can’t revert to previous snapshots when enabling the hw enablement 
stack kernel on focal or using any more recent version.
   * The option is available on grub and will let you with a broken system, 
partially cloned.

  [Test Case]

   * Boot on a system, using ZFS and ZSys.
   * In grub, select "History" entry
   * Select one of the "Revert" option: the system should boot after being 
reverted with an older version.

  
  [Where problems could occur]
   * The code is in the initramfs, where the generated id suffix for all our 
ZFS datasets was empty due to new coreutils/kernels.
   * We replace dd with another way (more robust and simple) for generating 
this ID.

  
  -

  @coreutils maintainers, any idea why dd is being flagged as having an
  executable stack?

  

  When I try to revert to a previous state from the grub menu, the boot
  fails. The system drops me to a repair modus.

  zfs-mount-generator fails with the message:
  couldn't ensure boot: Mounted clone bootFS dataset created by initramfs 
doesn't have a valid _suffix (at least .*_): \"rpool/ROOT/ubuntu_\"".

  After a reboot I have an extra clone called "rpool/ROOT/ubuntu_", indeed 
without a suffix.
  After a little investigation I found the problem in 
/usr/share/initramfs-tools/scripts/zfs at the end in function
  uid()
  {
     dd if=/dev/urandom of=/dev/stdout bs=1 count=100 2>/dev/null | tr -dc 
'a-z0-9' | cut -c-6
  }, the dd command fails during boot with the message "process 'dd' started 
with executable stack.
  After this an empty uid is returned which explains the dataset without a 
proper suffix.
  Replacing the function  with:
  uid()
  {
     grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut -c-6
  }

  fixes the problem.

  Ubuntu version is:
  Description:Ubuntu Groovy Gorilla (development branch)
  Release:20.10

  zfs-initramfs version is:
  0.8.4-1ubuntu11

  With regards,

  Usarin Heininga

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: zfs-initramfs 0.8.4-1ubuntu11
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Sep  4 20:23:44 2020
  InstallationDate: Installed on 2020-09-02 (2 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1891479] Re: pycurl ftbfs in focal (missing python-sphinx)

2021-01-16 Thread Mathew Hodson
The builds in proposed succeeded
https://launchpad.net/ubuntu/+source/pycurl/7.43.0.2-1ubuntu6

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

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

Title:
  pycurl ftbfs in focal (missing python-sphinx)

Status in pycurl package in Ubuntu:
  Fix Released
Status in pycurl source package in Focal:
  Fix Committed

Bug description:
  [SRU Justification]
  This package is unbuildable due to unsatisfiable build-dependencies, as seen 
in a focal test rebuild:
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19799602

  Missing build dependencies: python-sphinx

  This makes the package unsupportable in the event a security update
  needs to be applied.

  [Test case]
  1. let the package attempt to build in focal
  2. check if it succeeds.

  [Regression potential]
  Because the missing build-dependency is python-sphinx, which is only used for 
building the package documentation, the risk of regression is confined to a 
misbuild of the documentation.  Regardless, this package will be held in 
-proposed because the runtime impact of a FTBFS is non-existent.

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

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


[Touch-packages] [Bug 1891479] Re: pycurl ftbfs in focal (wait-deps)

2021-01-16 Thread Mathew Hodson
Already fix in Groovy and later.
---

pycurl (7.43.0.2-3) unstable; urgency=medium

  * Drop python2 support; Closes: #937415
  * debian/control
- annotate flaky as nocheck, patch by Helmut Grohne; Closes: #929194

 -- Sandro Tosi   Wed, 01 Apr 2020 23:22:15 -0400

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

** Summary changed:

- pycurl ftbfs in focal (wait-deps)
+ pycurl ftbfs in focal (missing python-sphinx)

** Tags removed: verification-needed

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

Title:
  pycurl ftbfs in focal (missing python-sphinx)

Status in pycurl package in Ubuntu:
  Fix Released
Status in pycurl source package in Focal:
  Fix Committed

Bug description:
  [SRU Justification]
  This package is unbuildable due to unsatisfiable build-dependencies, as seen 
in a focal test rebuild:
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19799602

  Missing build dependencies: python-sphinx

  This makes the package unsupportable in the event a security update
  needs to be applied.

  [Test case]
  1. let the package attempt to build in focal
  2. check if it succeeds.

  [Regression potential]
  Because the missing build-dependency is python-sphinx, which is only used for 
building the package documentation, the risk of regression is confined to a 
misbuild of the documentation.  Regardless, this package will be held in 
-proposed because the runtime impact of a FTBFS is non-existent.

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

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


[Touch-packages] [Bug 1891479] Re: pycurl ftbfs in focal (wait-deps)

2021-01-16 Thread Mathew Hodson
** Changed in: pycurl (Ubuntu Focal)
   Importance: Undecided => High

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

Title:
  pycurl ftbfs in focal (wait-deps)

Status in pycurl package in Ubuntu:
  Fix Released
Status in pycurl source package in Focal:
  Fix Committed

Bug description:
  [SRU Justification]
  This package is unbuildable due to unsatisfiable build-dependencies, as seen 
in a focal test rebuild:
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19799602

  Missing build dependencies: python-sphinx

  This makes the package unsupportable in the event a security update
  needs to be applied.

  [Test case]
  1. let the package attempt to build in focal
  2. check if it succeeds.

  [Regression potential]
  Because the missing build-dependency is python-sphinx, which is only used for 
building the package documentation, the risk of regression is confined to a 
misbuild of the documentation.  Regardless, this package will be held in 
-proposed because the runtime impact of a FTBFS is non-existent.

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

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


[Touch-packages] [Bug 1840375] Re: groupdel doesn't support extrausers

2021-01-16 Thread Mathew Hodson
** Tags removed: verification-needed verification-needed-disco

** Changed in: shadow (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: shadow (Ubuntu Xenial)
   Importance: Undecided => Wishlist

** Changed in: shadow (Ubuntu Bionic)
   Importance: Undecided => Wishlist

** Changed in: shadow (Ubuntu Disco)
   Importance: Undecided => Wishlist

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

Title:
  groupdel doesn't support extrausers

Status in snapd:
  Triaged
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Fix Committed
Status in shadow source package in Bionic:
  Fix Committed
Status in shadow source package in Disco:
  Won't Fix

Bug description:
  snapd needs the ability to call 'groupdel --extrausers foo' to clean
  up after itself, but --extrausers is currently unsupported.

  [Impact]
  On ubuntu-core systems we want to be able to manage "extrausers" in the same
  way as regular users. This requires updates to the various 
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.

  This is an important feature for Ubuntu Core

  [Test Case]
  0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
  1. install the libnss-extrausers and add "extrauers" to the passwd and shadow 
line (see /usr/share/doc/libnss-extrausers/README for the modifications in 
sswitch.conf)
  2. run "groupadd --extrausers foo" and verify "grep foo 
/var/lib/extrausers/group"
  3  check /var/lib/extrausers/group for the new "foo" group
  4. run "groupdel --extrausers foo"
  5. check /var/lib/extrausers/group and ensure the "foo" group is removed

  [Regression Potential]

   * low: this adds a new (optional) option which is off by default

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

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


[Touch-packages] [Bug 1906701] Re: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main)

2021-01-16 Thread Mathew Hodson
logrotate (3.17.0-1ubuntu1) hirsute; urgency=medium

  * Merge from Debian unstable.  Remaining changes:
- debian/control: Drop mailx to Suggests for Ubuntu; it's only used
  on request, and we don't configure an MTA by default.
- debian/logrotate.conf: use group 'syslog' by default when rotating logs.
  * Dropped changes, included upstream:
- Chery-pick upstream patch to fix FTBFS with GCC 10

logrotate (3.17.0-1) unstable; urgency=medium

  * New upstream version 3.17.0 (Closes: #945097, #966016)

  * debian:
- bump to debhelper compat level 13
- wrap-and-sort
  * d/rules:
- drop custom cleanup
  * d/patches:
- rebase and drop applied ones
- drop patch disabling test 70
- move debian specific patch to subdir
- cherry-pick upstream commits:
  + use getenv() on macOS and BSD
  + logrotate.service: harden with ProtectHostname
  + tests: always run logrotate in verbose mode
  + test-0070: set log modification time to current date
  + make `delaycompress` not to fail with `rotate 0`
  * d/logrotate.preinst: drop ancient maintainer script about old state file
paths
  * d/control: add acl package to build-dependencies to run ACL unit tests
on Linux
  * d/copyright: update years

logrotate (3.16.0-3) unstable; urgency=medium

  * d/patches: cherry-pick upstream switch-user fixes
- When using configuration directive su, accept staying as user root.
  In particular restore mailman's usage of 'su root list'.
- Reset user/group when error returning early in rotateLogSet().

logrotate (3.16.0-2) unstable; urgency=medium

  * d/patches:
- add upstream commit to silence unused parameter warning in
  acl disabled build
  Should fix FTBFS on architectures without acl
- add upstream commit to enable systemd hardening option ProtectClock

logrotate (3.16.0-1) unstable; urgency=medium

  [ Debian Janitor ]
  * Drop no longer supported add-log-mailing-address setting from
debian/changelog.
  * Add missing colon in closes line.
  * Remove obsolete fields Name from debian/upstream/metadata.

  [ Christian Göttsche ]
  * New upstream version 3.16.0 (Closes: #915301)

  * d/patches: rebase and drop upstream applied ones
- add new directive ProtectKernelLogs
- drop NoNewPrivileges, which is actually not implied and
  might be needed for third party rotate scripts
  * d/copyright: add extra sections
- add section for queue.h licensed under BSD-3-Clause
- add section for build-aux/git-version-gen licensed under GPL-3+
  * d/control: bump to std version 4.5.0 (no further changes)
  * d/rules: fail on compiler warnings

logrotate (3.15.1-2) unstable; urgency=medium

  * d/control: drop postgresql-common break
  * d/copyright: update for 2019
  * d/salsa-ci.yml: add standard salsa-ci configuration
  * d/tests: add additional small test script
  * d/patches: add testsuite patches to pass reprotest on salsa-ci
  * d/patches: tighten systemd service hardening
  * d/control: bump to std version 4.4.1 (no further changes)
  * d/source/lintian-overrides: ignore package-does-not-install-examples

logrotate (3.15.1-1) unstable; urgency=medium

  [ Ondřej Nový ]
  * d/changelog: Remove trailing whitespaces

  [ Christian Göttsche ]
  * New upstream version 3.15.1

  * d/patches: rebase and drop upstream applied ones
  * d/patches: add spelling fix
  * d/control: bump to std version 4.4.0 (no further changes)
  * debian: Switch to debhelper compat level 12 (no further changes)

 -- Balint Reczey   Mon, 26 Oct 2020 18:24:33 +0100

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

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

Title:
  Please merge logrotate 3.17.0-1 (main) from Debian unstable (main)

Status in logrotate package in Ubuntu:
  Fix Released

Bug description:
  Please merge logrotate 3.17.0-1 (main) from Debian unstable (main)

  At the time of filling this bug, the target debian unstable version is
  3.17.0-2.

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

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


[Touch-packages] [Bug 1879927] Re: Please merge wpa 2:2.9.0-13 (main) from Debian unstable (main)

2021-01-16 Thread Mathew Hodson
** Summary changed:

- Merge wpa 2:2.9.0-13 (main) from Debian unstable (main)
+ Please merge wpa 2:2.9.0-13 (main) from Debian unstable (main)

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

Title:
  Please merge wpa 2:2.9.0-13 (main) from Debian unstable (main)

Status in wpa package in Ubuntu:
  New

Bug description:
  Please merge wpa 2:2.9.0-13 (main) from Debian unstable (main)

  The Debian package carries some upstream cherry-picks that are nice to
  have in Ubuntu, plus the packaging updates.

  Sorry, I can't work on this merge myself.

  These Ubuntu changes can be dropped because they are already in Debian:
 * debian/patches/git_realtek_macrand.patch:
  - backport an upstream patch to fix issues with some realtek cards
when MAC address randomization is enabled (lp: #1867908)
 * SECURITY UPDATE: Incorrect indication of disconnection in certain
   situations
   - debian/patches/CVE-2019-16275.patch: silently ignore management
 frame from unexpected source address in src/ap/drv_callbacks.c,
 src/ap/ieee882_11.c.
   - CVE-2019-16275

  Remaining changes specific to Ubuntu:
 * debian/patches/wpa_service_ignore-on-isolate.patch: add
   IgnoreOnIsolate=yes so that when switching "runlevels" in oem-config
   will not kill off wpa and cause wireless to be unavailable on first
   boot.
 * debian/patches/session-ticket.patch: disable the TLS Session Ticket
   extension to fix auth with 802.1x PEAP on some hardware.

  Changelog entries since current groovy version 2:2.9-1ubuntu7:

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

* Apply upstream patches:
  - Avoid sending invalid mgmt frames at startup
  - Increase introspection buffer size for D-Bus

   -- Andrej Shadura   Tue, 19 May 2020 14:29:29
  +0200

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

* Add an upstream patch to fix the MAC randomisation issue with some cards
  (LP: #1867908).

   -- Andrej Shadura   Tue, 24 Mar 2020 11:13:16
  +0100

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

* Actually add autopkgtest for libwpa-client-dev and libwpa_test.c.

   -- Andrej Shadura   Sat, 07 Mar 2020 13:18:19
  +0100

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

* Rename the package with the client library to libwpa-client-dev.

   -- Andrej Shadura   Tue, 25 Feb 2020 20:19:52
  +0100

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

[ Terry Burton ]
* Build and install eapol_test in eapoltest package (Closes: #700870)

[ Didier Raboud ]
* Backport upstream patch to fix build with Debian's VERSION_STR.

[ Andrew Lee (李健秋) ]
* Build libwpa-dev binary package which contains a static
  libwpa_client library and the wpa_ctrl header with an example program.

[ Andrej Shadura ]
* Add a patch to provide the BIT() macro locally in wpa_ctrl.h.
* Patch the example to use stddef.h and wpa_ctrl.h from the global location.
* Add an autopkgtest for libwpa-dev and libwpa_test.c.

   -- Andrej Shadura   Tue, 25 Feb 2020 18:21:35
  +0100

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

* Reupload as 2.9.0 to undo an accidental experimental upload to
  unstable.

   -- Andrej Shadura   Sat, 22 Feb 2020 11:25:29
  +0300

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

* Apply upstream patches:
  - trace: handle binutils bfd.h breakage
  - Check for FT support when selecting FT suites (Closes: #942164)

   -- Andrej Shadura   Sat, 15 Feb 2020 16:42:04
  +0100

  wpa (2:2.9-6) unstable; urgency=medium

[ Debian Janitor ]
* Use secure URI in Homepage field.
* Move source package lintian overrides to debian/source.
* Use canonical URL in Vcs-Browser.
* Rely on pre-initialized dpkg-architecture variables.
* Update standards version to 4.4.1, no changes needed.

[ Andrej Shadura ]
* Disable CONFIG_DRIVER_MACSEC_QCA on kfreebsd.

   -- Andrej Shadura   Mon, 13 Jan 2020 16:28:58
  +0100

  wpa (2:2.9-5) unstable; urgency=medium

* Fix erroneously inverted logic in postinst.

   -- Andrej Shadura   Mon, 13 Jan 2020 10:48:26
  +0100

  wpa (2:2.9-4) unstable; urgency=medium

[ Helmut Grohne ]
* Fix FTCBFS: Don’t export CC=cc (Closes: #921998).

[ Andrej Shadura ]
* Don’t act in hostapd.postinst if we’re running in a chrootless root.
* Apply an upstream patch:
  - wpa_supplicant: Do not try to detect PSK mismatch during PTK rekeying.

   -- Andrej Shadura   Mon, 13 Jan 2020 10:37:10
  +0100

  wpa (2:2.9-3) unstable; urgency=medium

* Add pkg.wpa.nogui and noudeb build profiles.

   -- Andrej Shadura   Fri, 04 Oct 2019 11:47:15
  +0200

  wpa (2:2.9-2) unstable; urgency=medium

* SECURITY UPDATE:
  - AP mode PMF disconnection protection bypass.
More details:
 + https://w1.fi/security/2019-7/
Closes: #940080 

[Touch-packages] [Bug 1907676] Re: segmentation fault when opening fd

2021-01-08 Thread Mathew Hodson
** Bug watch added: Debian Bug tracker #977000
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000

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

Title:
  segmentation fault when opening fd

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Released
Status in python-apt source package in Bionic:
  Fix Released
Status in python-apt source package in Focal:
  Fix Released
Status in python-apt source package in Groovy:
  Fix Released
Status in python-apt package in Debian:
  Unknown

Bug description:
  [Impact]

  USN-4668-1 introduced a regression in python-apt when using certain
  APIs with a file handle.

  [Test case]

  # Landscape scenario:
  1) On the Landscape server, create a package profile that installs a single 
package, 'hello' is enough.
  2) On the Landscape server, apply the package profile to a client
  3) On the Landscape client, verify that there is no segfault message on 
'/var/log/kern.log'
  4) On the Landscape server, verify that the activity to apply the package 
profile ends with success.

  Step 3) would show a segfault and step 4), the activity would stay 'In
  Progress' forever.

  # dak scenario:
  dak crashes with a segmentation fault in python3-apt when processing
  uploads or processing the NEW queue on ftp-master; and also on my
  playground server (used to generate the backtrace).

  [Where problems could occurs]

  [Other info]

  See Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000

  Fix:
  
https://salsa.debian.org/apt-team/python-apt/-/commit/3d9af5f196ad6a6c6973ac699a15888d21a9bb52

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

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


[Touch-packages] [Bug 1906364] Re: [SRU] unattended-upgrade still restarts blacklisted daemons

2020-12-23 Thread Mathew Hodson
** No longer affects: unattended-upgrades (Ubuntu)

** No longer affects: unattended-upgrades (Ubuntu Xenial)

** No longer affects: unattended-upgrades (Ubuntu Bionic)

** No longer affects: unattended-upgrades (Ubuntu Focal)

** No longer affects: unattended-upgrades (Ubuntu Groovy)

** No longer affects: unattended-upgrades (Ubuntu Hirsute)

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

Title:
  [SRU] unattended-upgrade still restarts blacklisted daemons

Status in docker.io package in Ubuntu:
  Fix Released
Status in docker.io source package in Xenial:
  Fix Committed
Status in docker.io source package in Bionic:
  Fix Committed
Status in docker.io source package in Focal:
  Fix Committed
Status in docker.io source package in Groovy:
  Fix Committed
Status in docker.io source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  Docker uses containerd under the hood.  When containerd is upgraded it
  stops and restarts its service; docker stops when containerd stops but
  doesn’t restart.  Particularly when doing unattended upgrades, an SRU
  fix rolled out for containerd can result in unexpected and widespread
  service outages for docker.

  [Test Case]

  $ sudo apt install docker.io
  $ sudo systemctl start docker
  $ systemctl status docker | grep Active
   Active: active (running) since[...]
  $ systemctl status containerd | grep Active
   Active: active (running) since[...]

  $ docker pull ubuntu/redis:latest
  $ docker run -e REDIS_PASSWORD=1234 --network host \
  --name test-redis -d ubuntu/redis:latest
  $ telnet localhost 6379
  $ docker container logs test-redis

  $ sudo apt install --reinstall containerd
  $ systemctl status containerd | grep Active
   Active: active (running) since
  $ systemctl status docker | grep Active
   Active: inactive (dead) since [...]; 8s ago
  $ docker container logs test-redis

  [Where Problems Could Occur]

  The challenge with this issue is addressing all important corner
  cases, and as such the biggest risk is that we miss a corner case and
  fail to keep the two services running when they should.  Areas to
  watch will be failures during start/stop/restart/upgrade type
  operations.  Issues during runtime are unlikely to relate to this
  change.

  [Original Report]

  Hello,

  Today plenty of our systems running ubuntu 20.04 were restarting the
  docker daemon, even if i blacklisted the docker package. Since docker
  has an dependency on containerd thats the reason why it was restarted.
  IMO the blacklist should also check the full tree of dependencies...
  This should NOT happen!

  From the log you find:

  2020-12-01 06:40:13,881 INFO Starting unattended upgrades script
  2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, 
o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, 
o=UbuntuESM,a=focal-infra-security
  2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io
  2020-12-01 06:40:13,882 INFO Initial whitelist (not strict):
  2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd 
qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui 
qemu-system-x86 qemu-utils
  2020-12-01 06:40:19,140 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2020-12-01 06:40:46,996 INFO All upgrades installed
  2020-12-01 06:40:50,732 INFO Starting unattended upgrades script
  2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, 
o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, 
o=UbuntuESM,a=focal-infra-security
  2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io
  2020-12-01 06:40:50,733 INFO Initial whitelist (not strict):

  Also this happened for us on plenty of our servers almost at the same
  (why the unattended updates are not spread over time?), which
  destroyed the second time an production environment.

  This is not how unattended-upgraded should be, sadly this package lost
  our trust and we disable it and schedule the 'unattended updates' now
  on our own.

  PS: Not to say that on some servers the docker daemon did not even
  restart..

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

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


[Touch-packages] [Bug 1896073] Re: SRU the current 2.3.6 stable update

2020-12-23 Thread Mathew Hodson
** Tags added: upgrade-software-version

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

Title:
  SRU the current 2.3.6 stable update

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker 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/tracker/-/blob/tracker-2.3/NEWS

  The update add a 'tracker export' command, that's new and not used
  into any integration so has no real regression potential. It's an
  optional new option that can be used to export the data to migrate
  them to the incoming tracker3.

  * Test case

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

  Check that file search works correctly from the command line, shell
  and nautilus

  * Regression potential

  There is no specific change or feature to test in that update

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

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


[Touch-packages] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2020-12-14 Thread Mathew Hodson
** Bug watch removed: github.com/systemd/systemd/issues #12616
   https://github.com/systemd/systemd/issues/12616

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Won't Fix
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

     On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration, but the keyboard-configuration postinst maintaner 
script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode 
to observe the change:
     $  sudo kbd_mode -s -C /dev/tty1
     $ sudo kbd_mode -C /dev/tty1
     The keyboard is in raw (scancode) mode

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you 

[Touch-packages] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2020-12-14 Thread Mathew Hodson
A patch was applied to console-setup so that --force is only used with
debian-installer, which you can see here:
https://launchpadlibrarian.net/420660116/console-
setup_1.191ubuntu1_1.191ubuntu2.diff.gz

You can see the current code for Groovy at
https://git.launchpad.net/ubuntu/+source/console-setup/tree/debian
/keyboard-
configuration.postinst?h=ubuntu/groovy=4c8bc0d16b2b0dcefe2a38e3060e38863b7bb736#n113

Since this bug was closed when that patch was released, please report a
new bug so it can be determined if another fix is needed.

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Won't Fix
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

     On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration, but the keyboard-configuration postinst maintaner 
script still changes mode on vt1-6, thus at the beginning set 

[Touch-packages] [Bug 730307] Re: ALT-F[1-8] switches to text console

2020-12-14 Thread Mathew Hodson
*** This bug is a duplicate of bug 520546 ***
https://bugs.launchpad.net/bugs/520546

** This bug has been marked a duplicate of bug 520546
   [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT 
switch from Alt+Left/Right

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

Title:
  ALT-F[1-8] switches to text console

Status in console-tools package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: xorg

  Related bug: bug 463762 (probably exactly the same bug)

  not only ALT-CTRL-F[1-8] switches to the text console from X-Server,
  but also ALT-F[1-8] does this switching. I don't know where this comes
  from, but it breaks lots of stuff, i.e. ALT-F4 to close an app, ALT-F2
  to open the quick-start-applet, ... This happens not only on my
  desktop, but also on a GDM login desktop too.

  Strange thing is that if I switch back to the X-Server from the text
  console with ALT-F7, the actual keyboard action is executed in the
  X-Server, i.e. if I press ALT-F4, the text console is shown, when I
  switch back, the current application is closed!

  I saw this a while ago after update from 8.04 to 10.04 LTS on a
  different laptop (Toshiba with Nvidia graphix), and now the same bug
  on a fresh install of 10.10 on Lenovo X200t.

  I am using Russian keyboard layout. Once I delete the Russian keyboard
  layout and log-out, the bug is gone. But even without the Russian
  layout the bug returns after reboot. But then it goes away after I add
  the Russian layout and log out then log in. It seems that changing the
  layout disables the bug until next reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: xorg 1:7.5+6ubuntu3
  ProcVersionSignature: Ubuntu 2.6.35-27.48-generic-pae 2.6.35.11
  Uname: Linux 2.6.35-27-generic-pae i686
  Architecture: i386
  DRM.card0.DP.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.DP.2:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.DP.3:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.HDMI.A.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.HDMI.A.2:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.LVDS.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1280x800
   edid-base64: 
AP///wAwrhFAAC0SAQOAGhB46oXFlFdPiicgUFQBAQEBAQEBAQEBAQEBAQEBwBsAq1AgEDA0QDMABaMQAAAZwBsAq1AgEDA0QDMABaMQAAAZDwCBCjyBCjweAABMo1cx/gBMVE4xMjFBUDAzMDAxAOw=
  DRM.card0.VGA.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  Date: Mon Mar  7 00:52:19 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1)
  MachineType: LENOVO 7448CTO
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-27-generic-pae 
root=UUID=6c8fd8aa-fe87-482a-869a-2254bd16f22c ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: xorg
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WET67WW (3.17 )
  dmi.board.name: 7448CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WET67WW(3.17):bd12/02/2010:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7448CTO
  dmi.product.version: ThinkPad X200 Tablet
  dmi.sys.vendor: LENOVO
  glxinfo: Error: [Errno 2] No such file or directory
  system:
   distro: Ubuntu
   codename:   maverick
   architecture:   i686
   kernel: 2.6.35-27-generic-pae

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

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


[Touch-packages] [Bug 1823327] Re: booting cloud images on a Multipass Windows hosted enviroment is slow in the initramfs stage due to font setup / framebuffer issues

2020-12-14 Thread Mathew Hodson
** Changed in: cloud-images
   Status: New => Fix Released

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

Title:
  booting cloud images on a Multipass Windows hosted enviroment is slow
  in the initramfs stage due to font setup / framebuffer issues

Status in cloud-images:
  Fix Released
Status in console-setup package in Ubuntu:
  Fix Released
Status in console-setup source package in Bionic:
  Won't Fix

Bug description:
  Booting an azure kernel Cosmic cloud image with multipass on Windows
  10 pro takes a long time. Using systemd-analyze 25 seconds in kernel
  boot time is reported. Digging into this, the kernel boot time is
  actually ~5 seconds, the other 20 seconds before systemd init is
  exec'd is actually in the initramfs. I've instrumented the kernel to
  record the exec and exit times of each process in the kernel and the
  top offending processes in initramfs during boot are:

  Duration PID process
  14.86832 262 /scripts/init-top/console_setup
  2.48749 263 /bin/setfont
  2.45357 268 /bin/setfont
  2.44657 291 /bin/setfont
  2.44392 286 /bin/setfont
  2.43545 279 /bin/setfont
  2.43161 274 /bin/setfont
  1.19233 255 /scripts/init-top/framebuffer

  console_setup is calling setfont 7 times and each time setfint is
  taking more than 2.4 seconds to complete. Also the framebuffer program
  is taking over a second to run.

  For Disco with azure kernel:

  Duration PID process
  14.19028 275 console_setup
  2.39020 276 setfont
  2.34020 281 setfont
  2.32915 293 setfont
  2.32389 289 setfont
  2.32319 285 setfont
  2.32178 297 setfont
  1.11417 268 framebuffer

  For Xenial with generic kernel:

  Duration PID process
  15.01832 232 console_setup
  2.52273 233 setfont
  2.50960 238 setfont
  2.48476 250 setfont
  2.46333 256 setfont
  2.46289 262 setfont
  2.44667 268 setfont
  1.07674 225 framebuffer

  For Xenial with azure kernel:
  15.00529 260 console_setup
  2.49699 261 setfont
  2.47591 292 setfont
  2.47443 266 setfont
  2.47131 286 setfont
  2.46812 280 setfont
  2.45780 274 setfont
  1.07095 253 framebuffer

  so it seems to occur across releases with generic and azure kernels.

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

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


[Touch-packages] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2020-12-14 Thread Mathew Hodson
** No longer affects: xorg-server (Ubuntu)

** No longer affects: xorg-server (Ubuntu Lucid)

** No longer affects: xorg-server (Ubuntu Maverick)

** No longer affects: xorg-server (Ubuntu Xenial)

** No longer affects: xorg-server (Ubuntu Bionic)

** No longer affects: xorg-server (Ubuntu Cosmic)

** No longer affects: xorg-server (Ubuntu Disco)

** No longer affects: xorg-server (Ubuntu Eoan)

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Cosmic)

** No longer affects: linux (Ubuntu Disco)

** No longer affects: linux (Ubuntu Eoan)

** No longer affects: kbd (Ubuntu Maverick)

** No longer affects: kbd (Ubuntu Lucid)

** No longer affects: console-setup (Ubuntu Maverick)

** No longer affects: console-setup (Ubuntu Lucid)

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Won't Fix
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

  

[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2020-12-10 Thread Mathew Hodson
** Tags removed: block-proposed-eoan

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but that seems paranoid and
  extreme).

  [original description]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

  # original test case

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

To manage notifications about this bug go 

[Touch-packages] [Bug 1867157] Re: Improve command-not-found package headers

2020-12-10 Thread Mathew Hodson
** No longer affects: python3.8 (Ubuntu Focal)

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

Title:
  Improve command-not-found package headers

Status in python-defaults package in Ubuntu:
  Fix Released
Status in python2.7 package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  Fix Released
Status in python3.8 package in Ubuntu:
  Fix Released

Bug description:
  Improve command-not-found package headers

  
  command-not-found uses package metadata, and to improve the UX of the 
misspelled commands / proposed packages.

  python2.7-minimal should gain XB-Cnf-Visible-Pkgname: python2.7

  python3.8-minimal should gain XB-Cnf-Visible-Pkgname: python3.8

  python2-minimal should gain XB-Cnf-Visible-Pkgname: python2

  python3-minimal should gain XB-Cnf-Visible-Pkgname: python3

  This will then improve these messages from:

  """
command 'python2.7' from deb python2.7-minimal (2.7.17-1)
command 'python3.8' from deb python3.8-minimal (3.8.0-5)
command 'python2' from deb python2-minimal (2.7.17-2)
command 'python3' from deb python3-minimal (3.7.5-1ubuntu1)
  """

  To

  """
command 'python2.7' from deb python2.7 (2.7.17-1)
command 'python3.8' from deb python3.8 (3.8.0-5)
command 'python2' from deb python2 (2.7.17-2)
command 'python3' from deb python3 (3.7.5-1ubuntu1)
  """

  
  python3 should drop
  XB-Cnf-Extra-Commands: python
  XB-Cnf-Priority-Bonus: 5

  Such that it stops suggesting that somehow python is available from
  python3 package, which is a lie.

  There is a special case for "python" command hint in command-not-found
  already, which simply points people to "python3".

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

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


[Touch-packages] [Bug 1893563] Re: netplan: can't login to ap mode with psk

2020-12-10 Thread Mathew Hodson
Needs
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/ae31b4bf4eaa9eab9409c59dd420140f5fe6b697
and
https://w1.fi/cgit/hostap/commit/?id=1c58317f56e312576b6872440f125f794e45f991

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

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

** Package changed: wpasupplicant (Ubuntu) => wpa (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/1893563

Title:
  netplan: can't login to ap mode with psk

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Triaged
Status in wpa package in Ubuntu:
  New

Bug description:
  I've setup my wifi cards as ap over a bridge using netplan.
  If I add:

  auth:
key-management: psk
password: "testinglang"

  then my clients are unable to connect.
  If I remove those lines above in netplan then the clients are able to connect 
but without a password.

  If I run wpa_cli -i wlp3s0 status, I get:

  bssid=4c:1d:96:71:a3:90
  freq=2412
  ssid=walad2
  id=0
  mode=AP
  pairwise_cipher=CCMP+TKIP
  group_cipher=TKIP
  key_mgmt=UNKNOWN
  wpa_state=COMPLETED
  p2p_device_address=4c:1d:96:71:a3:91
  address=4c:1d:96:71:a3:90
  uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a

  I notice that key_mgmt=UNKNOWN. Perhaps that's the problem?

  Any pointers on how to debug and fix this?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: netplan.io 0.99-0ubuntu3~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Aug 30 23:11:48 2020
  InstallationDate: Installed on 2020-08-16 (14 days ago)
  InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netplan.io
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1906701] Re: Please merge logrotate 3.17.0-1 (main) from Debian unstable (main)

2020-12-10 Thread Mathew Hodson
** Changed in: logrotate (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Please merge logrotate 3.17.0-1 (main) from Debian unstable (main)

Status in logrotate package in Ubuntu:
  Confirmed

Bug description:
  Please merge logrotate 3.17.0-1 (main) from Debian unstable (main)

  At the time of filling this bug, the target debian unstable version is
  3.17.0-2.

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

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


[Touch-packages] [Bug 1899041] Re: Gnome-Network-Displays chrashes with Intel Wireless AC due to wpasupplicant - patch available

2020-11-30 Thread Mathew Hodson
** Bug watch added: Debian Bug tracker #976091
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976091

** Also affects: wpa (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976091
   Importance: Unknown
   Status: Unknown

** Tags added: patch-accepted-upstream

** Summary changed:

- Gnome-Network-Displays chrashes with Intel Wireless AC due to wpasupplicant - 
patch available
+ Gnome-Network-Displays crashes with Intel Wireless AC due to wpasupplicant

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

Title:
  Gnome-Network-Displays crashes with Intel Wireless AC due to
  wpasupplicant

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa package in Debian:
  Unknown

Bug description:
  When using Gnome-Network-Displays on a laptop with an Intel Wireless
  AC 9462/9560 card, wpasupplicant crashes. This reproducible bug can be
  fixed with this patch:

  
https://patchwork.ozlabs.org/project/hostap/patch/20200825062902.124600-1-benja...@sipsolutions.net/

  A further description can be found here:

  https://gitlab.gnome.org/GNOME/gnome-network-displays/-/issues/157

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

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


[Touch-packages] [Bug 1833116] Re: [chtmax98090 on Bay Trail Chromebooks] audio not working, shows "Dummy Output"

2020-11-24 Thread Mathew Hodson
*** This bug is a duplicate of bug 1871306 ***
https://bugs.launchpad.net/bugs/1871306

** This bug has been marked a duplicate of bug 1871306
   [SRU]No sound from internal card chtmax98090 - missing UCM2 files in 
alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3

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

Title:
  [chtmax98090 on Bay Trail Chromebooks] audio not working, shows "Dummy
  Output"

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  chtmax98090 intel HD audio device doesn't work out of the box after
  installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on
  audio devices.

  Audio options shows device and it works if I do this:

   git clone https://github.com/plbossart/UCM.git
   cd UCM
   cp -r chtmax98090/ /usr/share/alsa/ucm/
   alsactl store

  It would be great if there were a solution to make it works out of the
  box. The device (Chromebook Acer CB3-111 has it's end of life for
  chromeOS in July-August, so I suppose more people with this device
  will change OS perhaps to Ubuntu).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaime  1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 17 20:32:35 2019
  InstallationDate: Installed on 2019-06-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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


[Touch-packages] [Bug 1894917] Re: [chtmax98090][Dell Chromebook 11 'candy'] Pulseaudio fails to detect card // Bluetooth and USB devices work but internal speakers do not work (gives dummy output)

2020-11-24 Thread Mathew Hodson
*** This bug is a duplicate of bug 1871306 ***
https://bugs.launchpad.net/bugs/1871306

** This bug is no longer a duplicate of bug 1833116
   [chtmax98090 on Bay Trail Chromebooks] audio not working, shows "Dummy 
Output"
** This bug has been marked a duplicate of bug 1871306
   [SRU]No sound from internal card chtmax98090 - missing UCM2 files in 
alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3

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

Title:
  [chtmax98090][Dell Chromebook 11 'candy'] Pulseaudio fails to detect
  card // Bluetooth and USB devices work but internal speakers do not
  work (gives dummy output)

Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  To give some other background information:

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.6
Candidate: 1:13.99.1-1ubuntu3.6
Version table:
   *** 1:13.99.1-1ubuntu3.6 500
  500 http://us.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://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Linux is fairly new for me and any other information I need to provide
  can be given as long as I am told on how to retrieve it.

  This system I am currently using is Dell Chromebook 11 (Candy MODEL) with 4 
GB Ram and 16 GB of Har drive space. I am primarily using a Linux Distro such 
as Ubuntu or other distros in the same family. (This one is Linux Lite)
  Audio will play from USB connected devices or Bluetooth speakers/headphones. 
Internal speakers do not work at this moment and give me Dummy Output. The 
configuration file in puvucontrol gives me HDMI outputs or surround sound but 
no option for the internal speakers.
  I'm pretty sure my kernal driver is snd_hda-intel and tried loading different 
drivers from the file in '/etc/modprobe.d/alsa-base.conf' but to no avail.
  I'm not sure if this certain device cannot produce output from a linux distro 
but I will be trying other resources. I've reinstalled Pulse audio, its base 
and reinstalled Linux on this machine multiple times.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.6
  ProcVersionSignature: Ubuntu 5.4.0-46.50-generic 5.4.60
  Uname: Linux 5.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  areebcancode   1417 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Sep  8 17:24:36 2020
  InstallationDate: Installed on 2020-09-01 (7 days ago)
  InstallationMedia: Linux Lite 5.0 - Release amd64
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Title: [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd01/03/2019:svnGOOGLE:pnCandy:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Candy
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2020-09-03T17:56:09.564820

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

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


[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2020-11-22 Thread Mathew Hodson
** Bug watch added: Debian Bug tracker #972552
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972552

** Changed in: apt (Debian)
   Status: Fix Released => Unknown

** Changed in: apt (Debian)
 Remote watch: Debian Bug tracker #953260 => Debian Bug tracker #972552

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

** Bug watch removed: Sourceware.org Bugzilla #25652
   https://sourceware.org/bugzilla/show_bug.cgi?id=25652

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Triaged
Status in apt source package in Focal:
  Triaged
Status in apt source package in Groovy:
  Fix Committed
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  So what we do is change that to a warning.

  [Test case]
  Not available right now. Issues can flare up and then disappear again.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under 

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

2020-11-22 Thread Mathew Hodson
** No longer affects: glibc (Ubuntu)

** No longer affects: glibc (Ubuntu Bionic)

** No longer affects: glibc (Ubuntu Focal)

** Project changed: glibc => ubuntu-translations

** No longer affects: ubuntu-translations

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

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

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Triaged
Status in apt source package in Focal:
  Triaged
Status in apt source package in Groovy:
  Fix Committed
Status in apt package in Debian:
  Unknown

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  So what we do is change that to a warning.

  [Test case]
  Not available right now. Issues can flare up and then disappear again.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 

[Touch-packages] [Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

2020-11-22 Thread Mathew Hodson
** No longer affects: bluez (Ubuntu)

** No longer affects: bluez (Ubuntu Focal)

** No longer affects: bluez (Ubuntu Hirsute)

** No longer affects: bluez (Ubuntu Groovy)

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

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Groovy:
  Fix Committed
Status in apport source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  apport is not creating crash files for multiple system services that use 
ProtectSystem since Ubuntu 20.04 LTS.

  [Test Case]
  On an Ubuntu desktop system perform the following step
  1) sudo pkill -11 upowerd

  With the current version of apport there will not be a crash file for
  upowerd in /var/crash/. With the version of apport in -proposed there
  will be a crash file for upowerd in /var/crash/.

  [Regression Potential]
  In the event that the changes to /usr/share/apport/apport are bad then apport 
itself would crash thereby preventing us from getting any crash reports. So in 
addition to killing upowerd we should also test a regular application like 
xeyes.

  [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash 
reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04=bluez=year

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

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


[Touch-packages] [Bug 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties

2020-11-22 Thread Mathew Hodson
** Changed in: wpa (Ubuntu Bionic)
   Importance: Undecided => High

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

Title:
  Broken dbus GetAll message to wpa supplicant interface properties

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  One of the distro patch is incorrect and create issues when trying to query 
dbus properties

  * Test Case

  $ sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1
  /fi/w1/wpa_supplicant1/Interfaces/1
  org.freedesktop.DBus.Properties.GetAll
  string:fi.w1.wpa_supplicant1.Interface

  shouldn't error out

  (the /1 reflect the interface number and could be a different value,
  check with d-feet if needed)

  * Regression potential

  The fixes is in the dbus interface, check that communication with
  desktop clients (indicator, applet, settings) still works correctly,
  returning expected informations on the signal, etc

  -

  dbus-send is able to read the properties of interface using GetAll. Those 
information include interface name, status, encryption method, etc.
  The regression was introduced when someone try to have the Station attribute 
supported

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

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


[Touch-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

2020-11-22 Thread Mathew Hodson
** Project changed: pulseaudio => alsa-lib

** Changed in: alsa-lib
   Importance: Unknown => Undecided

** Changed in: alsa-lib
   Status: Unknown => New

** Changed in: alsa-lib
 Remote watch: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1030 => 
None

** Changed in: alsa-lib
   Status: New => Fix Released

** Bug watch removed: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues 
#1030
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1030

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

Title:
  [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in ALSA Libraries:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Committed
Status in alsa-lib source package in Hirsute:
  Fix Released
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  After logging in, only a dummy device is available for audio playback 
(resulting in no audible playback). When running "pactl load-module 
module-detect" the sound card shows up, and playback works as expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  

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

2020-11-21 Thread Mathew Hodson
Fixed in libx11 version 1.7.0 with
https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/dbb55e1a5e82870466b095097d9e46046680ec25

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

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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2020-11-21 Thread Mathew Hodson
** No longer affects: pcmanfm (Ubuntu)

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

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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

2020-11-18 Thread Mathew Hodson
** No longer affects: build-essential (Ubuntu)

** No longer affects: build-essential (Ubuntu Focal)

** No longer affects: glib2.0 (Ubuntu)

** No longer affects: iputils (Ubuntu)

** No longer affects: kbd (Ubuntu)

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

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

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

** No longer affects: ntpsec (Ubuntu)

** No longer affects: qemu (Ubuntu)

** No longer affects: qemu (Ubuntu Focal)

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

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

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

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  autopkgtests are failing/flaky and prevent other packages from
  migrating to -updates

  [test case]

  check autopkgtest history

  [regression potential]

  in regard to the changed test cases, any regression would likely
  result in either an incorrectly passed test, or an incorrectly failed
  test.

  [scope]

  for systemd, this is needed for x, b, and f.

  tests in g appear to be mostly stable, but I've opened MR (linked from
  this bug) to update the tests there as well.

  i don't plan to update x, as it's reaching ESM in ~6 months, and
  backporting the test fixes is more work than just a simple code copy,
  since there are additional differences/changes needed in the older
  version of systemd (and python3). the failing/flaky tests in x have
  been like that forever, and people have just retried them; we can keep
  retrying them until x moves into ESM next year.

  [original description]

  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
    amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
    ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
    s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% B  0% => P 67%/) 
FFF..FF..F.FF..F
  root-unittests (F 10% S  0% B  0% => P 90%/) 
FFF...F.
    arm64
  tests-in-lxd   (F 40% S  0% B  2% => P 57%/) 
F.B...FFF.FF..F..F.FFF.F
  logind (F  2% S  0% B  2% => P 95%/) 
..B...F.
  upstream   (F 22% S  0% B  2% => P 75%/) 

[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2020-11-18 Thread Mathew Hodson
*** This bug is a duplicate of bug 1754671 ***
https://bugs.launchpad.net/bugs/1754671

** This bug is no longer a duplicate of bug 1688018
   DNS server from vpn connection is not being used after network-manager 
upgrade to 1.2.6
** This bug has been marked a duplicate of bug 1754671
   Full-tunnel VPN DNS leakage regression

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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


  1   2   3   4   5   6   7   8   9   10   >