[Touch-packages] [Bug 2051672] Re: Backport iproute2 6.8.0 to noble

[Andrea Righi]

Thanks @dannf for updating the bug! The SRU description looks good to me
and everything seems reasonable, same with the plan.

I'll keep monitoring this tracker and we'll proceed once oracular will
be open.

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

Title:
  Backport iproute2 6.8.0 to noble

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Several networking features introduced in the upstream 6.2->6.8 kernels are 
not accessible to noble users because noble lacks the corresponding iproute2 
update. This includes support for new hardware features such as per-VF offload 
settings (see bug 2060969), but many others that you can see in the attached 
changelogs.

  Normally iproute2 is updated during the devel cycle to align with the
  kernel version, but it was missed this cycle and discovered too late
  for an FFe. We request an exception from the SRU team to do this as an
  SRU. This includes dropping the Ubuntu Fan patches, which adds
  features to iproute2 that no longer work since noble's kernels no
  longer support Ubuntu Fan.

  [Test Case]
  We'll run the 6.8 kernel self tests, which make use of a number of iproute2 
features (see comment #17). NVIDIA's networking organization (Mellanox) has 
offered to put this through their QA process (details TBD). The upstream test 
suite will also run in the autopkgtests, though that suite is fairly stale.

  [What Could Go Wrong]
  Users who may be running noble userspace with a non-noble kernel that 
supports Ubuntu Fan would lose support for configuring it. If the SRU team 
considers this to be a regression we should avoid, then we can add the Ubuntu 
Fan patches back.

  iproute2 6.8 upstream retains backwards compatibility with earlier
  releases (see comment #17). There are no commits with a Fixes:
  annotation since the v6.8.0 tag was applied upstream.

  iproute2 is obviously a key package, and any upstream version bump
  carries risk. This includes the possibility of breaking networking for
  users of an Ubuntu LTS release.

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


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

[Touch-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

[Andrea Righi]

Hello, any progress on this? Now that ubuntu-fan is officially
deprecated in Noble can we simply sync iproute2 with Debian? Is there
any pending activity / requirement that are preventing this? Thanks!

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

Title:
  [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  iproute2 upstream produces releases coinciding with upstream kernel
  releases to support the latest kernel features. Noble's iproute2 is
  still back at v6.1 even though it will use the v6.8 kernel. This means
  we provide no userspace interface for newer features - some of which
  are noted by a networking hardware partner in bug 2060969.

  Ubuntu's iproute2 has diverged from Debian's to add support for Ubuntu
  FAN. Noble has dropped kernel support for Ubuntu FAN, so those are no
  longer needed, and we could now just do a merge. We could also port
  the FAN patches forward if we can identify a need (see the original
  description of this bug to a link to such a port), but I have not done
  any testing with that.

  I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and
  smoke tested it on an amd64 virtual machine:

  ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb
  (Reading database ... 83134 files and directories currently installed.)
  Preparing to unpack iproute2_6.8.0-1~24.04.1_amd64.deb ...
  Unpacking iproute2 (6.8.0-1~24.04.1) over (6.1.0-1ubuntu6) ...
  dpkg: warning: unable to delete old directory '/etc/iproute2/rt_tables.d': 
Directory not empty
  dpkg: warning: unable to delete old directory '/etc/iproute2/rt_protos.d': 
Directory not empty
  dpkg: warning: unable to delete old directory '/etc/iproute2': Directory not 
empty
  Setting up iproute2 (6.8.0-1~24.04.1) ...
  Removing obsolete conffile /etc/iproute2/group ...
  Removing obsolete conffile /etc/iproute2/rt_realms ...
  Removing obsolete conffile /etc/iproute2/rt_scopes ...
  Removing obsolete conffile /etc/iproute2/rt_tables ...
  Removing obsolete conffile /etc/iproute2/rt_tables.d/README ...
  Removing obsolete conffile /etc/iproute2/rt_protos.d/README ...
  Removing obsolete conffile /etc/iproute2/rt_protos ...
  Removing obsolete conffile /etc/iproute2/rt_dsfield ...
  Removing obsolete conffile /etc/iproute2/nl_protos ...
  Removing obsolete conffile /etc/iproute2/ematch_map ...
  Removing obsolete conffile /etc/iproute2/bpf_pinning ...
  Processing triggers for man-db (2.12.0-4build1) ...

  The system rebooted fine. The ip command seems to behave normally.

  Since the upstream test suite only appears to run at autopkgtest time, I 
triggered a run in my PPA, and it passed:

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-test/noble/amd64/i/iproute2/20240412_210819_97417@/log.gz

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


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

[Touch-packages] [Bug 2063298] [NEW] deprecate ubuntu-fan in Noble

[Andrea Righi]

Public bug reported:

[Impact]

In order to provide ubuntu-fan we need to maintain additional kernel
SAUCE patches that are currently conflicting with upstream code,
potentially breaking networking eBPF APIs.

To prevent such incompatibility the whole patch set requires a major
redesign.

However, after investigations and a detailed assessment we have not
found any relevant real-world use-case that still requuires ubuntu-fan,
as most of its features are now available in the upstream kernel and
user-space tools, using alternative solutions.

Moreover, maintaining ubuntu-fan is also slowing down / preventing the
development of other packages (see for example LP: #2051672).

Therefore, we are proposing to deprecate ubuntu-fan starting with noble.

[Test case]

We have ubuntu-fan test cases in our regression testing suite. Such
tests are expected to fail with the noble kernel, so we can hint/disable
them in Noble.

[Fix]

Drop (do not apply) the ubuntu-fan SAUCE patch set from the Ubuntu
kernel.

[Regression potential]

There are still some existing tools/systems that may still rely on
ubuntu-fan, so we may experience regressions when such systems are
moving to noble. However, the potential of breaking eBPF networking has
a much higher impact, so we can probably workaround any potential
ubuntu-fan regression using alternative upstream solutions.

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

** Affects: iproute2 (Ubuntu Noble)
 Importance: Undecided
 Status: New

** Also affects: iproute2 (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

Title:
  deprecate ubuntu-fan in Noble

Status in iproute2 package in Ubuntu:
  New
Status in iproute2 source package in Noble:
  New

Bug description:
  [Impact]

  In order to provide ubuntu-fan we need to maintain additional kernel
  SAUCE patches that are currently conflicting with upstream code,
  potentially breaking networking eBPF APIs.

  To prevent such incompatibility the whole patch set requires a major
  redesign.

  However, after investigations and a detailed assessment we have not
  found any relevant real-world use-case that still requuires ubuntu-
  fan, as most of its features are now available in the upstream kernel
  and user-space tools, using alternative solutions.

  Moreover, maintaining ubuntu-fan is also slowing down / preventing the
  development of other packages (see for example LP: #2051672).

  Therefore, we are proposing to deprecate ubuntu-fan starting with
  noble.

  [Test case]

  We have ubuntu-fan test cases in our regression testing suite. Such
  tests are expected to fail with the noble kernel, so we can
  hint/disable them in Noble.

  [Fix]

  Drop (do not apply) the ubuntu-fan SAUCE patch set from the Ubuntu
  kernel.

  [Regression potential]

  There are still some existing tools/systems that may still rely on
  ubuntu-fan, so we may experience regressions when such systems are
  moving to noble. However, the potential of breaking eBPF networking
  has a much higher impact, so we can probably workaround any potential
  ubuntu-fan regression using alternative upstream solutions.

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


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

[Touch-packages] [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)

[Andrea Righi]

According to the information that I collected (asking around,
investigating, etc.), it seems that there are no critical users of
ubuntu-fan.

Moreover, considering the impact of the ubuntu-fan kernel patches (that
would require a major refactoring to avoid breaking the network eBPF
ABI), we decided to proceed with the plan to deprecate this feature in
all the noble kernels.

Therefore, all the user-space components that rely on such feature can
follow the same plan and drop their corresponding ubuntu-fan support
(iproute2 included).

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

Title:
  [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
  testing/unstable (main)

Status in iproute2 package in Ubuntu:
  Confirmed

Bug description:
  iproute2 upstream produces releases coinciding with upstream kernel
  releases to support the latest kernel features. Noble's iproute2 is
  still back at v6.1 even though it will use the v6.8 kernel. This means
  we provide no userspace interface for newer features - some of which
  are noted by a networking hardware partner in bug 2060969.

  Ubuntu's iproute2 has diverged from Debian's to add support for Ubuntu
  FAN. Noble has dropped kernel support for Ubuntu FAN, so those are no
  longer needed, and we could now just do a merge. We could also port
  the FAN patches forward if we can identify a need (see the original
  description of this bug to a link to such a port), but I have not done
  any testing with that.

  I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and
  smoke tested it on an amd64 virtual machine:

  ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb
  (Reading database ... 83134 files and directories currently installed.)
  Preparing to unpack iproute2_6.8.0-1~24.04.1_amd64.deb ...
  Unpacking iproute2 (6.8.0-1~24.04.1) over (6.1.0-1ubuntu6) ...
  dpkg: warning: unable to delete old directory '/etc/iproute2/rt_tables.d': 
Directory not empty
  dpkg: warning: unable to delete old directory '/etc/iproute2/rt_protos.d': 
Directory not empty
  dpkg: warning: unable to delete old directory '/etc/iproute2': Directory not 
empty
  Setting up iproute2 (6.8.0-1~24.04.1) ...
  Removing obsolete conffile /etc/iproute2/group ...
  Removing obsolete conffile /etc/iproute2/rt_realms ...
  Removing obsolete conffile /etc/iproute2/rt_scopes ...
  Removing obsolete conffile /etc/iproute2/rt_tables ...
  Removing obsolete conffile /etc/iproute2/rt_tables.d/README ...
  Removing obsolete conffile /etc/iproute2/rt_protos.d/README ...
  Removing obsolete conffile /etc/iproute2/rt_protos ...
  Removing obsolete conffile /etc/iproute2/rt_dsfield ...
  Removing obsolete conffile /etc/iproute2/nl_protos ...
  Removing obsolete conffile /etc/iproute2/ematch_map ...
  Removing obsolete conffile /etc/iproute2/bpf_pinning ...
  Processing triggers for man-db (2.12.0-4build1) ...

  The system rebooted fine. The ip command seems to behave normally.

  Since the upstream test suite only appears to run at autopkgtest time, I 
triggered a run in my PPA, and it passed:

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-test/noble/amd64/i/iproute2/20240412_210819_97417@/log.gz

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


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

[Touch-packages] [Bug 2038433] [NEW] systemd autopkgtest regression on arm64 and s390x on mantic

[Andrea Righi]

Public bug reported:

tests-in-lxd seems to fail to download the lxd image used for the test (or 
something similar), looking at the log:
...
Publishing instance: Image pack: 85% (5.51MB/s)

Instance published with fingerprint: 
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
6845s autopkgtest [09:11:14]: version 5.28ubuntu1
6845s autopkgtest [09:11:14]: host autopkgtest; command line: 
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd 
autopkgtest/ubuntu/mantic/arm64
7063s : failure: (down) ['mktemp', '--directory', '--tmpdir', 
'autopkgtest.XX'] failed (exit status 1, stderr '')
7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the 
testbed
7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
7064s autopkgtest [09:14:53]: test tests-in-lxd:  - - - - - - - - - - results - 
- - - - - - - - -
7064s tests-in-lxd FAIL non-zero exit status 1
2:40 PM
...

This introduces a regression that is blocking the promotion of new
kernels in Mantic.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
Uname: Linux 6.5.0-5-lowlatency x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct  4 14:38:15 2023
InstallationDate: Installed on 2023-09-25 (9 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-lowlatency 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.04
dmi.board.asset.tag: Default string
dmi.board.name: G1621-02
dmi.board.vendor: GPD
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 2.3
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.04:bd09/01/2022:br5.19:efr2.3:svnGPD:pnG1621-02:pvrDefaultstring:rvnGPD:rnG1621-02:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: G1621-02
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: GPD

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

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


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

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

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

Title:
  systemd autopkgtest regression on arm64 and s390x on mantic

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Mantic:
  New

Bug description:
  tests-in-lxd seems to fail to download the lxd image used for the test (or 
something similar), looking at the log:
  ...
  Publishing instance: Image pack: 85% (5.51MB/s)

  Instance published with fingerprint: 
83b511be44395f2afc7d4d1ee0708cb18834c8b15cb208c9d218964ed8479114
  6845s autopkgtest [09:11:14]: starting date and time: 2023-10-03 09:11:14+
  6845s autopkgtest [09:11:14]: version 5.28ubuntu1
  6845s autopkgtest [09:11:14]: host autopkgtest; command line: 
/usr/bin/autopkgtest -U -B . --test-name=unit-tests -- lxd 
autopkgtest/ubuntu/mantic/arm64
  7063s : failure: (down) ['mktemp', '--directory', '--tmpdir', 
'autopkgtest.XX'] failed (exit status 1, stderr '')
  7063s autopkgtest [09:14:52]: ERROR: testbed failure: unexpected eof from the 
testbed
  7063s autopkgtest [09:14:52]: test tests-in-lxd: ---]
  7064s autopkgtest [09:14:53]: test tests-in-lxd:  - - - - - - - - - - results 
- - - - - - - - - -
  7064s tests-in-lxd FAIL non-zero exit status 1
  2:40 PM
  ...

  This introduces a regression that is blocking the promotion of new
  kernels in Mantic.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: systemd 253.5-1ubuntu6
  ProcVersionSignature: Ubuntu 6.5.0-5.5.1-lowlatency 6.5.0
  Uname: Linux 6.5.0-5-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:38:15 2023
  InstallationDate: Installed on 2023-09-25 (9 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924)
  MachineType: 

[Touch-packages] [Bug 2017311] Re: gdb wrong dependency to python3.10

[Andrea]

Sorry, my mistake. Can be closed.

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

Title:
  gdb wrong dependency to python3.10

Status in gdb package in Ubuntu:
  New

Bug description:
  Just updated to Ubuntu 13.04 and gdb needs libpython3.10.so.1.0 even
  though it depends on 3.11

  I have removed and installed gdb to make sure I got the latest
  version.

  gdb:
Installed: 13.1-2ubuntu2
Candidate: 13.1-2ubuntu2
Version table:
   *** 13.1-2ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  but when I run it

  > gdb: error while loading shared libraries: libpython3.10.so.1.0:
  cannot open shared object file: No such file or directory

  Which is correct because

  > ldd $(which gdb)
  > libpython3.10.so.1.0 => not found

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


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

[Touch-packages] [Bug 2017311] [NEW] gdb wrong dependency to python3.10

[Andrea]

Public bug reported:

Just updated to Ubuntu 13.04 and gdb needs libpython3.10.so.1.0 even
though it depends on 3.11

I have removed and installed gdb to make sure I got the latest version.

gdb:
  Installed: 13.1-2ubuntu2
  Candidate: 13.1-2ubuntu2
  Version table:
 *** 13.1-2ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
100 /var/lib/dpkg/status

but when I run it

> gdb: error while loading shared libraries: libpython3.10.so.1.0:
cannot open shared object file: No such file or directory

Which is correct because

> ldd $(which gdb)
> libpython3.10.so.1.0 => not found

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

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

Title:
  gdb wrong dependency to python3.10

Status in gdb package in Ubuntu:
  New

Bug description:
  Just updated to Ubuntu 13.04 and gdb needs libpython3.10.so.1.0 even
  though it depends on 3.11

  I have removed and installed gdb to make sure I got the latest
  version.

  gdb:
Installed: 13.1-2ubuntu2
Candidate: 13.1-2ubuntu2
Version table:
   *** 13.1-2ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  but when I run it

  > gdb: error while loading shared libraries: libpython3.10.so.1.0:
  cannot open shared object file: No such file or directory

  Which is correct because

  > ldd $(which gdb)
  > libpython3.10.so.1.0 => not found

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


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

[Touch-packages] [Bug 2009686] [NEW] package rsyslog-mysql 8.2001.0-1ubuntu1.3 failed to install/upgrade: il sottoprocesso installato pacchetto rsyslog-mysql script post-installation ha restituito lo

[Andrea Di Mascio]

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: rsyslog-mysql 8.2001.0-1ubuntu1.3
ProcVersionSignature: Ubuntu 5.14.0-1058.66-oem 5.14.21
Uname: Linux 5.14.0-1058-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Mar  8 10:47:22 2023
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
ErrorMessage: il sottoprocesso installato pacchetto rsyslog-mysql script 
post-installation ha restituito lo stato di errore 1
InstallationDate: Installed on 2023-01-10 (56 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: rsyslog
Title: package rsyslog-mysql 8.2001.0-1ubuntu1.3 failed to install/upgrade: il 
sottoprocesso installato pacchetto rsyslog-mysql script post-installation ha 
restituito lo stato di errore 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package rsyslog-mysql 8.2001.0-1ubuntu1.3 failed to install/upgrade:
  il sottoprocesso installato pacchetto rsyslog-mysql script post-
  installation ha restituito lo stato di errore 1

Status in rsyslog package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: rsyslog-mysql 8.2001.0-1ubuntu1.3
  ProcVersionSignature: Ubuntu 5.14.0-1058.66-oem 5.14.21
  Uname: Linux 5.14.0-1058-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar  8 10:47:22 2023
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  ErrorMessage: il sottoprocesso installato pacchetto rsyslog-mysql script 
post-installation ha restituito lo stato di errore 1
  InstallationDate: Installed on 2023-01-10 (56 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: rsyslog
  Title: package rsyslog-mysql 8.2001.0-1ubuntu1.3 failed to install/upgrade: 
il sottoprocesso installato pacchetto rsyslog-mysql script post-installation ha 
restituito lo stato di errore 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 2000276] Re: FIDO2 user verification impossible when using the ssh agent

[Andrea Ieri]

hi Lena, actually yes, I can reproduce the same issue with a nitrokey 3A
NFC. I also have an older yubikey 5A but I cannot test with it as its
firmware does not support user verification, only user presence.

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

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

Title:
  FIDO2 user verification impossible when using the ssh agent

Status in openssh package in Ubuntu:
  New

Bug description:
  I am having trouble setting up FIDO2 ssh keys with my yubikey 5C NFC
  if I want to enable user verification (user presence works fine).

  
  Steps to reproduce:

  = Prep work =

  Client (kinetic):
  * generate a key that requires user verification:
$ ssh-keygen -t ed25519-sk -f ~/.ssh/id_ed25519_verify_sk -O 
verify-required -C "this key requires UV"
[provide your authenticator PIN, touch it, and add an encryption password]

  Server (jammy):
  * add id_ed25519_verify_sk.pub to authorized_keys

  = Symptoms =

  Shell 1 (w/ssh agent):

  $ eval $(ssh-agent)
  Agent pid 3279738

  $ ssh-add ~/.ssh/id_ed25519_verify_sk
  Enter passphrase for /home/aieri/.ssh/id_ed25519_verify_sk: 
  Identity added: /home/aieri/.ssh/id_ed25519_verify_sk (this key requires UV)

  $ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 fails\!"
  sign_and_send_pubkey: signing failed for ED25519-SK 
"/home/aieri/.ssh/id_ed25519_verify_sk" from agent: agent refused operation
  ubuntu@10.35.202.231: Permission denied (publickey).

  [note that the above is printed immediately, and that the yubikey does
  not light up]

  Shell 2 (no ssh agent):

  $ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 works\!"
  Enter passphrase for key '/home/aieri/.ssh/id_ed25519_verify_sk': 
  Enter PIN for ED25519-SK key /home/aieri/.ssh/id_ed25519_verify_sk: 
  Confirm user presence for key ED25519-SK 
SHA256:nhgS4c2rGtE7XKeez3rAsofrjJvsL6rmBLShZxfTXIY
  User presence confirmed
  FIDO2 works!


  NOTE: 
  * user _presence_ can be validated correctly with or without the ssh-agent: 
keys generated without `-O verify-required` work as expected (aside from bug 
1869897)

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


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

[Touch-packages] [Bug 1680750] Re: pm-hibernate does nothing at all

[Andrea Gelmini]

Do you find something in /var/log/pm-suspend.log ?

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

Title:
  pm-hibernate does nothing at all

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  I have run from a command line:
  # sudo pm-hibernate

  and NOTHING f***ing happens.

  Usually it works (except for lots of issues on resume), but now I have
  tried it twice and it does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: powerman (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  7 10:47:47 2017
  InstallationDate: Installed on 2013-10-11 (1273 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: powerman
  UpgradeStatus: Upgraded to xenial on 2016-12-11 (116 days ago)

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


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

[Touch-packages] [Bug 2000841] [NEW] logrotate does not rotate logs due to/var/log group

[Andrea C G Mennucci]

Public bug reported:

hi Steve

recently  in version 8.2112.0-2ubuntu1, 29 Dec 2021

the postinst would `chgrp syslog /var/log`

but then logrotate will not rotate files any more

unless in the file `/etc/logrotate.d/rsyslog` the option
`su root syslog`
is added

regards

a.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: rsyslog 8.2112.0-2ubuntu2.2
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sun Jan  1 19:02:45 2023
EcryptfsInUse: Yes
SourcePackage: rsyslog
UpgradeStatus: Upgraded to jammy on 2022-12-13 (19 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  logrotate does not rotate logs due to/var/log  group

Status in rsyslog package in Ubuntu:
  New

Bug description:
  hi Steve

  recently  in version 8.2112.0-2ubuntu1, 29 Dec 2021

  the postinst would `chgrp syslog /var/log`

  but then logrotate will not rotate files any more

  unless in the file `/etc/logrotate.d/rsyslog` the option
  `su root syslog`
  is added

  regards

  a.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: rsyslog 8.2112.0-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun Jan  1 19:02:45 2023
  EcryptfsInUse: Yes
  SourcePackage: rsyslog
  UpgradeStatus: Upgraded to jammy on 2022-12-13 (19 days ago)

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


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

[Touch-packages] [Bug 2000276] [NEW] FIDO2 user verification impossible when using the ssh agent

[Andrea Ieri]

Public bug reported:

I am having trouble setting up FIDO2 ssh keys with my yubikey 5C NFC if
I want to enable user verification (user presence works fine).


Steps to reproduce:

= Prep work =

Client (kinetic):
* generate a key that requires user verification:
  $ ssh-keygen -t ed25519-sk -f ~/.ssh/id_ed25519_verify_sk -O verify-required 
-C "this key requires UV"
  [provide your authenticator PIN, touch it, and add an encryption password]

Server (jammy):
* add id_ed25519_verify_sk.pub to authorized_keys

= Symptoms =

Shell 1 (w/ssh agent):

$ eval $(ssh-agent)
Agent pid 3279738

$ ssh-add ~/.ssh/id_ed25519_verify_sk
Enter passphrase for /home/aieri/.ssh/id_ed25519_verify_sk: 
Identity added: /home/aieri/.ssh/id_ed25519_verify_sk (this key requires UV)

$ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 fails\!"
sign_and_send_pubkey: signing failed for ED25519-SK 
"/home/aieri/.ssh/id_ed25519_verify_sk" from agent: agent refused operation
ubuntu@10.35.202.231: Permission denied (publickey).

[note that the above is printed immediately, and that the yubikey does
not light up]

Shell 2 (no ssh agent):

$ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 works\!"
Enter passphrase for key '/home/aieri/.ssh/id_ed25519_verify_sk': 
Enter PIN for ED25519-SK key /home/aieri/.ssh/id_ed25519_verify_sk: 
Confirm user presence for key ED25519-SK 
SHA256:nhgS4c2rGtE7XKeez3rAsofrjJvsL6rmBLShZxfTXIY
User presence confirmed
FIDO2 works!


NOTE: 
* user _presence_ can be validated correctly with or without the ssh-agent: 
keys generated without `-O verify-required` work as expected (aside from bug 
1869897)

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

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

Title:
  FIDO2 user verification impossible when using the ssh agent

Status in openssh package in Ubuntu:
  New

Bug description:
  I am having trouble setting up FIDO2 ssh keys with my yubikey 5C NFC
  if I want to enable user verification (user presence works fine).

  
  Steps to reproduce:

  = Prep work =

  Client (kinetic):
  * generate a key that requires user verification:
$ ssh-keygen -t ed25519-sk -f ~/.ssh/id_ed25519_verify_sk -O 
verify-required -C "this key requires UV"
[provide your authenticator PIN, touch it, and add an encryption password]

  Server (jammy):
  * add id_ed25519_verify_sk.pub to authorized_keys

  = Symptoms =

  Shell 1 (w/ssh agent):

  $ eval $(ssh-agent)
  Agent pid 3279738

  $ ssh-add ~/.ssh/id_ed25519_verify_sk
  Enter passphrase for /home/aieri/.ssh/id_ed25519_verify_sk: 
  Identity added: /home/aieri/.ssh/id_ed25519_verify_sk (this key requires UV)

  $ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 fails\!"
  sign_and_send_pubkey: signing failed for ED25519-SK 
"/home/aieri/.ssh/id_ed25519_verify_sk" from agent: agent refused operation
  ubuntu@10.35.202.231: Permission denied (publickey).

  [note that the above is printed immediately, and that the yubikey does
  not light up]

  Shell 2 (no ssh agent):

  $ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 works\!"
  Enter passphrase for key '/home/aieri/.ssh/id_ed25519_verify_sk': 
  Enter PIN for ED25519-SK key /home/aieri/.ssh/id_ed25519_verify_sk: 
  Confirm user presence for key ED25519-SK 
SHA256:nhgS4c2rGtE7XKeez3rAsofrjJvsL6rmBLShZxfTXIY
  User presence confirmed
  FIDO2 works!


  NOTE: 
  * user _presence_ can be validated correctly with or without the ssh-agent: 
keys generated without `-O verify-required` work as expected (aside from bug 
1869897)

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


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

[Touch-packages] [Bug 1992979] Re: kinetic ppc64le reporting Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected

[Andrea Righi]

It could be related to #1991691 if you're using the kernel currently in
release.

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

Title:
  kinetic ppc64le reporting Failed to send WATCHDOG=1 notification
  message: Transport endpoint is not connected

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgraded from Jammy to Kinetic (14 Oct 2022) on ppc64le in QEMU,
  single CPU, 1GB memory, rebooted, can NO longer login. Stuck in
  systems boot phase.

  Attached is an image of the hang

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


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

[Touch-packages] [Bug 1990824] Re: initramfs-tools: out-of-memory failures during autopkgtest

[Andrea Righi]

All the initramfs-tools autopkgtest tests seem to run fine on a recent
kernel (5.19) with the debdiff in attach applied.

** Patch added: "initramfs-tools-increase-ram-2GB.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1990824/+attachment/5619021/+files/initramfs-tools-increase-ram-2GB.debdiff

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

Title:
  initramfs-tools: out-of-memory failures during autopkgtest

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  [Impact]

  Some autopkgtest tests are failing due to out-of-memory conditions,
  especially amd64-ata-only and net.

  It seems that we are creating a VM with 1GB only to run the amd64-ata-
  only test and even just 512MB for the net test.

  It probably makes sense to create larger VMs (at least 2GB) to run
  these tests with a more recent kernels (that will likely require a
  little more RAM).

  [Test case]

  sudo autopkgtest . -- null

  [Fix]

  Increase memory size of instances used to run the autopkgtests to 2GB.

  [Regression potential]

  We may experience regressions in small cloud instances, or systems
  with less than 2GB or RAM that are using a recent kernel (but this is
  more a generic potential regression, not strictly related to
  initramfs-tools).

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


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

[Touch-packages] [Bug 1990824] [NEW] initramfs-tools: out-of-memory failures during autopkgtest

[Andrea Righi]

Public bug reported:

[Impact]

Some autopkgtest tests are failing due to out-of-memory conditions,
especially amd64-ata-only and net.

It seems that we are creating a VM with 1GB only to run the amd64-ata-
only test and even just 512MB for the net test.

It probably makes sense to create larger VMs (at least 2GB) to run these
tests with a more recent kernels (that will likely require a little more
RAM).

[Test case]

sudo autopkgtest . -- null

[Fix]

Increase memory size of instances used to run the autopkgtests to 2GB.

[Regression potential]

We may experience regressions in small cloud instances, or systems with
less than 2GB or RAM that are using a recent kernel (but this is more a
generic potential regression, not strictly related to initramfs-tools).

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

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

Title:
  initramfs-tools: out-of-memory failures during autopkgtest

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  [Impact]

  Some autopkgtest tests are failing due to out-of-memory conditions,
  especially amd64-ata-only and net.

  It seems that we are creating a VM with 1GB only to run the amd64-ata-
  only test and even just 512MB for the net test.

  It probably makes sense to create larger VMs (at least 2GB) to run
  these tests with a more recent kernels (that will likely require a
  little more RAM).

  [Test case]

  sudo autopkgtest . -- null

  [Fix]

  Increase memory size of instances used to run the autopkgtests to 2GB.

  [Regression potential]

  We may experience regressions in small cloud instances, or systems
  with less than 2GB or RAM that are using a recent kernel (but this is
  more a generic potential regression, not strictly related to
  initramfs-tools).

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


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

[Touch-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported

[Andrea Gadotti]

I have found a (dirty?) workaround for this. The idea is simple: use a
udev rule to suspend the laptop before UPower shuts it down. This can be
done by creating a file /etc/udev/rules.d/99-lowbat.rules with the
following content:

# Suspend the system when battery level drops to 5% or lower
SUBSYSTEM=="power_supply", ATTR{status}=="Discharging", 
ATTR{capacity}=="[0-5]", RUN+="/usr/bin/systemctl suspend"

You can of course tune the threshold.

This method seems to work well for me. If you want to use a threshold
that's lower than the UPower one, *I think* you could set the
PercentageAction parameter to 0% or 1% in /etc/UPower/UPower.conf,
although I'm not 100% sure this is a good idea (the disclaimer at the
beginning of the file seems to discourage users from directly modifying
the file).


Reference: 
https://wiki.archlinux.org/title/laptop#Hibernate_on_low_battery_level


On a side note, I definitely wish this bug could be addressed. It's not normal 
that a computer just shuts down and makes you lose your work when there's still 
battery. Also note that afaik there's currently no way to enable hibernation 
with full disk encryption, so this limitation of UPower will become 
increasingly serious as more and more users will make the (right) choice to use 
FDE.

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in Upower:
  New
Status in upower package in Ubuntu:
  Triaged

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1986619] Re: Fail to install base-passwd

[Andrea Gambacorta]

Hi,
I had the same problem.
First you can check if your file is "immutable" via:
#> lsattr /etc/passwd
i /etc/passwd

If is not immutable you dont have any reason for not edit via sudo, so the 
problem can be, like my case, the antivirus.
I kill all mcafee process multiple time, every 2 seconds, because the process 
try to becoming up, and then I was able to upgrade the library
I hope it will be usefull for you
Ciao

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

Title:
  Fail to install base-passwd

Status in base-passwd package in Ubuntu:
  Confirmed

Bug description:
  /home/frank/Downloads# dpkg -i base-passwd_3.5.52build1_amd64.deb
  (Reading database ... 236425 files and directories currently installed.)
  Preparing to unpack base-passwd_3.5.52build1_amd64.deb ...
  Unpacking base-passwd (3.5.52build1) over (3.5.52build1) ...
  Setting up base-passwd (3.5.52build1) ...
  Changing home-directory of irc from /var/run/ircd to /run/ircd
  1 changes have been made, rewriting files
  Writing passwd-file to /etc/passwd
  Failed to open passwd-file /etc/passwd.upwd-write for writing: Permission 
denied
  dpkg: error processing package base-passwd (--install):
   installed base-passwd package post-installation script subprocess returned 
error exit status 4
  Errors were encountered while processing:
   base-passwd
  root@CNQDSX:/home/frank/Downloads#

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


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

[Touch-packages] [Bug 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29

[Andrea Righi]

** Also affects: network-manager (Ubuntu Kinetic)
   Importance: Undecided
   Status: Invalid

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: Invalid

** Also affects: urfkill (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

Title:
  network-manager/1.36.4-2ubuntu1 ADT test failure with
  linux/5.15.0-28.29

Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid
Status in urfkill package in Ubuntu:
  New
Status in linux source package in Jammy:
  Fix Released
Status in network-manager source package in Jammy:
  Invalid
Status in urfkill source package in Jammy:
  New
Status in linux source package in Kinetic:
  Invalid
Status in network-manager source package in Kinetic:
  Invalid
Status in urfkill source package in Kinetic:
  New

Bug description:
  This is a scripted bug report about ADT failures while running
  network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is
  caused by the dep8 tests of the tested source or the kernel has yet to
  be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz

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


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

[Touch-packages] [Bug 1907878] Re: wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)

[Andrea C G Mennucci]

as ~larsoner mentioned, those scripts contain some `return` but not in
functions, so they may fail in some cases; you should change all
`return` to `exit 0`

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

Title:
  wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]:
  /etc/network/if-up.d/resolved: 12: mystatedir: not found)

Status in ifupdown package in Ubuntu:
  Fix Released

Bug description:
  Syslog error:

 nm-dispatcher[...]: /etc/network/if-up.d/resolved: 12: mystatedir:
  not found

  I think it's because of this line:

if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
mystatedir statedir ifindex interface <- this 
is interpreted as a 'mystatedir' command and fails

interface=$IFACE
if [ ! "$interface" ]; then

  
  Perhaps the intention was to 'export mystatedir statedir ...'

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


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

[Touch-packages] [Bug 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal

[Andrea Righi]

This seems to fix the test failure.

** Patch added: "systemd-test-make-test-execute-pass-on-Linux-5.15.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592621/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.debdiff

** Patch removed: "systemd-test-make-test-execute-pass-on-Linux-5.15.patch"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592620/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.patch

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

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

Title:
  systemd: fix test-execute autotest failure with kernel 5.15 in focal

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

Bug description:
  [Impact]

  test-execute autotest is failing in focal with kernel 5.15. This is
  because the following kernel commit changed the ABI for ioprio:

  e70344c05995 ("block: fix default IO priority handling")

  Previously setting IOPRIO_CLASS_NONE for a process would report
  IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
  IOPRIO_CLASS_BE instead.

  [Test case]

  Run systemd autopkgtest and check for the test-execute result.

  [Fix]

  Change test/test-execute/exec-ioschedulingclass-none.service to
  recognize both "none" and "best-effort" as valid returned strings from
  ionice.

  This change is already available in jammy and above.

  [Regression potential]

  We may see regressions in systemd autopkgtest, we won't introduce any
  potential regressions in systemd itself, because this is only
  affecting the specific unit test.

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


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

[Touch-packages] [Bug 1975587] Re: systemd: fix test-execute autotest failure with kernel 5.15 in focal

[Andrea Righi]

** Patch added: "systemd-test-make-test-execute-pass-on-Linux-5.15.patch"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1975587/+attachment/5592620/+files/systemd-test-make-test-execute-pass-on-Linux-5.15.patch

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

Title:
  systemd: fix test-execute autotest failure with kernel 5.15 in focal

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

Bug description:
  [Impact]

  test-execute autotest is failing in focal with kernel 5.15. This is
  because the following kernel commit changed the ABI for ioprio:

  e70344c05995 ("block: fix default IO priority handling")

  Previously setting IOPRIO_CLASS_NONE for a process would report
  IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
  IOPRIO_CLASS_BE instead.

  [Test case]

  Run systemd autopkgtest and check for the test-execute result.

  [Fix]

  Change test/test-execute/exec-ioschedulingclass-none.service to
  recognize both "none" and "best-effort" as valid returned strings from
  ionice.

  This change is already available in jammy and above.

  [Regression potential]

  We may see regressions in systemd autopkgtest, we won't introduce any
  potential regressions in systemd itself, because this is only
  affecting the specific unit test.

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


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

[Touch-packages] [Bug 1975587] [NEW] systemd: fix test-execute autotest failure with kernel 5.15 in focal

[Andrea Righi]

Public bug reported:

[Impact]

test-execute autotest is failing in focal with kernel 5.15. This is
because the following kernel commit changed the ABI for ioprio:

e70344c05995 ("block: fix default IO priority handling")

Previously setting IOPRIO_CLASS_NONE for a process would report
IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
IOPRIO_CLASS_BE instead.

[Test case]

Run systemd autopkgtest and check for the test-execute result.

[Fix]

Change test/test-execute/exec-ioschedulingclass-none.service to
recognize both "none" and "best-effort" as valid returned strings from
ionice.

This change is already available in jammy and above.

[Regression potential]

We may see regressions in systemd autopkgtest, we won't introduce any
potential regressions in systemd itself, because this is only affecting
the specific unit test.

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

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

Title:
  systemd: fix test-execute autotest failure with kernel 5.15 in focal

Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

  test-execute autotest is failing in focal with kernel 5.15. This is
  because the following kernel commit changed the ABI for ioprio:

  e70344c05995 ("block: fix default IO priority handling")

  Previously setting IOPRIO_CLASS_NONE for a process would report
  IOPRIO_CLASS_NONE back. But starting with 5.15 it reports
  IOPRIO_CLASS_BE instead.

  [Test case]

  Run systemd autopkgtest and check for the test-execute result.

  [Fix]

  Change test/test-execute/exec-ioschedulingclass-none.service to
  recognize both "none" and "best-effort" as valid returned strings from
  ionice.

  This change is already available in jammy and above.

  [Regression potential]

  We may see regressions in systemd autopkgtest, we won't introduce any
  potential regressions in systemd itself, because this is only
  affecting the specific unit test.

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


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

[Touch-packages] [Bug 1971474] Re: SRU: Update gdb to the final 12.1 release in 22.04 LTS

[Andrea]

And it fixes a VSCode integration issue.

https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1971409

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

Title:
  SRU: Update gdb to the final 12.1 release in 22.04 LTS

Status in gdb package in Ubuntu:
  New

Bug description:
  Update gdb to the final 12.1 release in 22.04 LTS. jammy ships with
  the gdb 12.1 release candidate, taken from the gdb-12 branch. Changes
  up to the final release are:

   - updated gnulib library
   - Fix for PR mi/29002 (Windows only)
   - gdb: fix 'remote show FOO-packet' aliases
   - various testsuite fixes
   - fixing compiler warnings
   - Fix bug in Ada number lexing
   - Remove "Ada Settings" node from the manual
   - Handle TLS variable lookups when using separate debug files.
   - PR 28980: gdb: don't copy entirely optimized out values in value_copy
   - gdb/mi: fix use after free of frame_info causing spurious notifications

  Comparing the test results between the two builds doesn't show any
  regression on any architecture.

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


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

[Touch-packages] [Bug 1972059] [NEW] One screen does not come back from lock

[Andrea]

Public bug reported:

I have 2 screen (Dell).
Since having upgraded to 22.04, one of them struggles to come back after a lock.

Sometimes takes a few seconds, sometimes it is ok and sometimes it takes longer.
I have found that if I do Ctrl-Alt-F1... the screen comes back.

I have a DP and HDMI cable and tried to switch them around, it is always
the same screen: a Dell U2415 UltraSharp 24.

Never happened with any other version since about 18.04.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May  7 13:39:19 2022
DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 
seconds (Configuring libpam-systemd (amd64))
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
InstallationDate: Installed on 2020-02-01 (825 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-04-29 (7 days ago)
dmi.bios.date: 11/11/2015
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session

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

Title:
  One screen does not come back from lock

Status in xorg package in Ubuntu:
  New

Bug description:
  I have 2 screen (Dell).
  Since having upgraded to 22.04, one of them struggles to come back after a 
lock.

  Sometimes takes a few seconds, sometimes it is ok and sometimes it takes 
longer.
  I have found that if I do Ctrl-Alt-F1... the screen comes back.

  I have a DP and HDMI cable and tried to switch them around, it is
  always the same screen: a Dell U2415 UltraSharp 24.

  Never happened with any other version since about 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  7 13:39:19 2022
  DistUpgraded: 2022-04-29 21:19:33,557 WARNING no activity on terminal for 300 
seconds (Configuring libpam-systemd (amd64))
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.3.0, 5.15.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-02-01 (825 days ago)
  InstallationMedia: 

[Touch-packages] [Bug 1971409] Re: value_copy: Assertion `arg->contents != nullptr' failed.

[Andrea]

Got the same issue in VSCode using gdb 12.0.90.

I compiled gdb 12.1 and it works.
Can we get it updated to 12.1?

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

Title:
  value_copy: Assertion `arg->contents != nullptr' failed.

Status in gdb package in Ubuntu:
  New

Bug description:
  When debugging RP2040 with vscode this assert makes gdb crash.
  This is a new assert, that wasn't present in gdb 11.
  The fix is easy, replace `if (!value_lazy (val))` to `if (!value_lazy (val) 
&& arg->contents != nullptr) `.

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


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

[Touch-packages] [Bug 1971593] Re: make wireless-tools a dependency for network-manager

[Andrea Righi]

** Description changed:

  The wpa-dhclient autopkgtest is always failing without wireless-tools
- installed. Maybe wireless-tools should be an explicit dependency of
- network-manager.
+ installed. Maybe wireless-tools should be added to the test dependencies
+ (debian/tests/control).

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

Title:
  make wireless-tools a dependency for network-manager

Status in network-manager package in Ubuntu:
  New

Bug description:
  The wpa-dhclient autopkgtest is always failing without wireless-tools
  installed. Maybe wireless-tools should be added to the test
  dependencies (debian/tests/control).

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


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

[Touch-packages] [Bug 1971593] [NEW] make wireless-tools a dependency for network-manager

[Andrea Righi]

Public bug reported:

The wpa-dhclient autopkgtest is always failing without wireless-tools
installed. Maybe wireless-tools should be an explicit dependency of
network-manager.

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

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

Title:
  make wireless-tools a dependency for network-manager

Status in network-manager package in Ubuntu:
  New

Bug description:
  The wpa-dhclient autopkgtest is always failing without wireless-tools
  installed. Maybe wireless-tools should be an explicit dependency of
  network-manager.

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


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

[Touch-packages] [Bug 1964763] [NEW] QtChooser doesn't support qt6

[Andrea Marchesini]

Public bug reported:

qtchooser doesn't run qt6 applications because it doesn't have a
qt6.conf/6.conf file yet.

In order to work, it must have two files `/usr/lib/x86_64-linux-
gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux-
gnu/qtchooser/6.conf` with this content:


```
/usr/lib/qt6/bin
/usr/lib/x86_64-linux-gnu
```

Without it, lupdate, lrelease, and any other qt6 tools show this error:
`could not find a Qt installation of ''`

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

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

Title:
  QtChooser doesn't support qt6

Status in qtchooser package in Ubuntu:
  New

Bug description:
  qtchooser doesn't run qt6 applications because it doesn't have a
  qt6.conf/6.conf file yet.

  In order to work, it must have two files `/usr/lib/x86_64-linux-
  gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux-
  gnu/qtchooser/6.conf` with this content:

  
  ```
  /usr/lib/qt6/bin
  /usr/lib/x86_64-linux-gnu
  ```

  Without it, lupdate, lrelease, and any other qt6 tools show this
  error: `could not find a Qt installation of ''`

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


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

[Touch-packages] [Bug 1461530] Re: Translation make output hard to read

[William Andrea]

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

** This bug has been marked a duplicate of bug 1581433
   free output in german translation line up wrong colums

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

Title:
  Translation make output hard to read

Status in procps package in Ubuntu:
  New

Bug description:
  andreas@asterix:~/projects/uber/uber.data.processor/uber/data/processor$ free 
-m
   Gesamt Belegt Frei Gemeinsam Puffer Cache
  Speicher:  15965  14517   1447   1073204   5516
  -/+ Puffer/Cache:   8796   7168
  Auslagerungsdatei:   7982   3472   4510

  (bad to see with variable width fonts)

  Basically this is an issue with translations destroying the tabular
  output.

  This can be fixed in two ways, either fix all the translation strings,
  or make free truncate the output (even truncated labels should be
  useable for something like free, but then as a long time user I
  probably don't need labels, but without the column alignment the data
  is hard to read).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: procps 1:3.3.9-1ubuntu2.2
  ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9
  Uname: Linux 3.16.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  3 14:37:09 2015
  InstallationDate: Installed on 2015-05-15 (18 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: procps
  UpgradeStatus: No upgrade log present (user-confirmed fresh install)

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


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

[Touch-packages] [Bug 1581433] Re: free output in german translation line up wrong colums

[William Andrea]

Affects the French translation too.

** Attachment added: "free French sample.output"
   
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1581433/+attachment/5566379/+files/free%20French%20sample.output

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

Title:
  free output in german translation line up wrong colums

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Notice how the free column for swap shows 0 in the german translation.

  andreas@asterix:~$ free -m
gesamt   benutzt frei  gemns.  Puffer/Cache 
verfügbar
  Speicher:   159634934714411193884
9779
  Auslagerungsspeicher:7981   07981
  andreas@asterix:~$ LANG=C free -m
totalusedfree  shared  buff/cache   
available
  Mem:  159634935714211193886
9778
  Swap:  7981   07981
  andreas@asterix:~$ free 
gesamt   benutzt frei  gemns.  Puffer/Cache 
verfügbar
  Speicher:16346836 5051476 7317744 1144548 3977616
10017704
  Auslagerungsspeicher: 8173408   0 8173408
  andreas@asterix:~$ LANG=C free 
totalusedfree  shared  buff/cache   
available
  Mem:   16346836 5052300 7316848 1144292 3977688
10017188
  Swap:   8173408   0 8173408

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 13 10:14:05 2016
  InstallationDate: Installed on 2016-04-22 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: procps
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1961196] Re: apparmor autotest failure on jammy with linux 5.15

[Andrea Righi]

updated debdiff in attach FWIW

** Patch added: "apparmor-fix-autotests.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+attachment/5562493/+files/apparmor-fix-autotests.debdiff

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

Title:
  apparmor autotest failure on jammy with linux 5.15

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Jammy:
  New

Bug description:
  [Impact]

  test-aa-notify is also checking if the output of `aa-notify --help`
  matches a specific text. However it looks like this output has changed
  in jammy so the autopkgtest is reporting errors like this:

  05:17:31 ERROR| [stderr] === test-aa-notify.py ===
  05:17:31 ERROR| [stderr] .ssF.
  05:17:31 ERROR| [stderr] 
==
  05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
  05:17:31 ERROR| [stderr] Test output of help text
  05:17:31 ERROR| [stderr] 
--
  05:17:31 ERROR| [stderr] Traceback (most recent call last):
  05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
  05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
  05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n 
 -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
  05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug]
  05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr]   Display AppArmor notifications or messages for 
DENIED entries.
  05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr] - optional arguments:
  05:17:31 ERROR| [stderr] + options:
  05:17:31 ERROR| [stderr] -h, --helpshow this help message and 
exit
  05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and 
display notifications
  05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY 
environment variable (might be needed if
  05:17:31 ERROR| [stderr]   sudo resets $DISPLAY)
  05:17:31 ERROR| [stderr] -f FILE, --file FILE  search FILE for AppArmor 
messages
  05:17:31 ERROR| [stderr] -l, --since-last  display stats since last 
login
  05:17:31 ERROR| [stderr] -s NUM, --since-days NUM
  05:17:31 ERROR| [stderr]   show stats for last NUM 
days (can be used alone or with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] -v, --verbose show messages with stats
  05:17:31 ERROR| [stderr] -u USER, --user USER  user to drop privileges to 
when not using sudo
  05:17:31 ERROR| [stderr] -w NUM, --wait NUMwait NUM seconds before 
displaying notifications (with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] --debug   debug mode
  05:17:31 ERROR| [stderr]  : Got output "usage: aa-notify [-h] [-p] [--display 
DISPLAY] [-f FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr]  [-u USER] [-w NUM] [--debug]

  [Test case]

  Simply run test-aa-notify.py from the autopkgtests.

  [Fix]

  Update the expected output returned by `aa-notify --help` in test-aa-
  notify.py.

  [Regression potential]

  This is just an autopkgtest, we may see regressions if the test is
  used with older version of apparmor-notify. With newer versions
  there's no risk of regressions.

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


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

[Touch-packages] [Bug 1961196] Re: apparmor autotest failure on jammy with linux 5.15

[Andrea Righi]

@alexmurray thanks for the update! BTW I found another issue with test-
network.py: this test is failing because utils/apparmor/rule/network.py
is missing the mctp protocol (in network_domain_keywords[]).

I checked upstream, but I couldn't find any fix for this, do you want me
to open another tracking bug / send a patch?

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

Title:
  apparmor autotest failure on jammy with linux 5.15

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Jammy:
  New

Bug description:
  [Impact]

  test-aa-notify is also checking if the output of `aa-notify --help`
  matches a specific text. However it looks like this output has changed
  in jammy so the autopkgtest is reporting errors like this:

  05:17:31 ERROR| [stderr] === test-aa-notify.py ===
  05:17:31 ERROR| [stderr] .ssF.
  05:17:31 ERROR| [stderr] 
==
  05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
  05:17:31 ERROR| [stderr] Test output of help text
  05:17:31 ERROR| [stderr] 
--
  05:17:31 ERROR| [stderr] Traceback (most recent call last):
  05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
  05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
  05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n 
 -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
  05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug]
  05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr]   Display AppArmor notifications or messages for 
DENIED entries.
  05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr] - optional arguments:
  05:17:31 ERROR| [stderr] + options:
  05:17:31 ERROR| [stderr] -h, --helpshow this help message and 
exit
  05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and 
display notifications
  05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY 
environment variable (might be needed if
  05:17:31 ERROR| [stderr]   sudo resets $DISPLAY)
  05:17:31 ERROR| [stderr] -f FILE, --file FILE  search FILE for AppArmor 
messages
  05:17:31 ERROR| [stderr] -l, --since-last  display stats since last 
login
  05:17:31 ERROR| [stderr] -s NUM, --since-days NUM
  05:17:31 ERROR| [stderr]   show stats for last NUM 
days (can be used alone or with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] -v, --verbose show messages with stats
  05:17:31 ERROR| [stderr] -u USER, --user USER  user to drop privileges to 
when not using sudo
  05:17:31 ERROR| [stderr] -w NUM, --wait NUMwait NUM seconds before 
displaying notifications (with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] --debug   debug mode
  05:17:31 ERROR| [stderr]  : Got output "usage: aa-notify [-h] [-p] [--display 
DISPLAY] [-f FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr]  [-u USER] [-w NUM] [--debug]

  [Test case]

  Simply run test-aa-notify.py from the autopkgtests.

  [Fix]

  Update the expected output returned by `aa-notify --help` in test-aa-
  notify.py.

  [Regression potential]

  This is just an autopkgtest, we may see regressions if the test is
  used with older version of apparmor-notify. With newer versions
  there's no risk of regressions.

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


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

[Touch-packages] [Bug 1961196] Re: apparmor autotest failure on jammy with linux 5.15

[Andrea Righi]

Simple fix in the attached debdiff

** Patch added: "apparmor-fix-test-aa-notify.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+attachment/5561612/+files/apparmor-fix-test-aa-notify.debdiff

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

Title:
  apparmor autotest failure on jammy with linux 5.15

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Jammy:
  New

Bug description:
  [Impact]

  test-aa-notify is also checking if the output of `aa-notify --help`
  matches a specific text. However it looks like this output has changed
  in jammy so the autopkgtest is reporting errors like this:

  05:17:31 ERROR| [stderr] === test-aa-notify.py ===
  05:17:31 ERROR| [stderr] .ssF.
  05:17:31 ERROR| [stderr] 
==
  05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
  05:17:31 ERROR| [stderr] Test output of help text
  05:17:31 ERROR| [stderr] 
--
  05:17:31 ERROR| [stderr] Traceback (most recent call last):
  05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
  05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
  05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n 
 -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
  05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug]
  05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr]   Display AppArmor notifications or messages for 
DENIED entries.
  05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr] - optional arguments:
  05:17:31 ERROR| [stderr] + options:
  05:17:31 ERROR| [stderr] -h, --helpshow this help message and 
exit
  05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and 
display notifications
  05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY 
environment variable (might be needed if
  05:17:31 ERROR| [stderr]   sudo resets $DISPLAY)
  05:17:31 ERROR| [stderr] -f FILE, --file FILE  search FILE for AppArmor 
messages
  05:17:31 ERROR| [stderr] -l, --since-last  display stats since last 
login
  05:17:31 ERROR| [stderr] -s NUM, --since-days NUM
  05:17:31 ERROR| [stderr]   show stats for last NUM 
days (can be used alone or with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] -v, --verbose show messages with stats
  05:17:31 ERROR| [stderr] -u USER, --user USER  user to drop privileges to 
when not using sudo
  05:17:31 ERROR| [stderr] -w NUM, --wait NUMwait NUM seconds before 
displaying notifications (with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] --debug   debug mode
  05:17:31 ERROR| [stderr]  : Got output "usage: aa-notify [-h] [-p] [--display 
DISPLAY] [-f FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr]  [-u USER] [-w NUM] [--debug]

  [Test case]

  Simply run test-aa-notify.py from the autopkgtests.

  [Fix]

  Update the expected output returned by `aa-notify --help` in test-aa-
  notify.py.

  [Regression potential]

  This is just an autopkgtest, we may see regressions if the test is
  used with older version of apparmor-notify. With newer versions
  there's no risk of regressions.

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


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

[Touch-packages] [Bug 1961196] Re: apparmor autotest failure on jammy with linux 5.15

[Andrea Righi]

** Description changed:

+ [Impact]
+ 
+ test-aa-notify is also checking if the output of `aa-notify --help`
+ matches a specific text. However it looks like this output has changed
+ in jammy so the autopkgtest is reporting errors like this:
+ 
  05:17:31 ERROR| [stderr] === test-aa-notify.py ===
  05:17:31 ERROR| [stderr] .ssF.
  05:17:31 ERROR| [stderr] 
==
  05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
  05:17:31 ERROR| [stderr] Test output of help text
  05:17:31 ERROR| [stderr] 
--
  05:17:31 ERROR| [stderr] Traceback (most recent call last):
  05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
  05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
  05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n 
 -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
  05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug]
- 05:17:31 ERROR| [stderr]   
+ 05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr]   Display AppArmor notifications or messages for 
DENIED entries.
- 05:17:31 ERROR| [stderr]   
+ 05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr] - optional arguments:
  05:17:31 ERROR| [stderr] + options:
  05:17:31 ERROR| [stderr] -h, --helpshow this help message and 
exit
  05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and 
display notifications
  05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY 
environment variable (might be needed if
  05:17:31 ERROR| [stderr]   sudo resets $DISPLAY)
  05:17:31 ERROR| [stderr] -f FILE, --file FILE  search FILE for AppArmor 
messages
  05:17:31 ERROR| [stderr] -l, --since-last  display stats since last 
login
  05:17:31 ERROR| [stderr] -s NUM, --since-days NUM
  05:17:31 ERROR| [stderr]   show stats for last NUM 
days (can be used alone or with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] -v, --verbose show messages with stats
  05:17:31 ERROR| [stderr] -u USER, --user USER  user to drop privileges to 
when not using sudo
  05:17:31 ERROR| [stderr] -w NUM, --wait NUMwait NUM seconds before 
displaying notifications (with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] --debug   debug mode
  05:17:31 ERROR| [stderr]  : Got output "usage: aa-notify [-h] [-p] [--display 
DISPLAY] [-f FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr]  [-u USER] [-w NUM] [--debug]
+ 
+ [Test case]
+ 
+ Simply run test-aa-notify.py from the autopkgtests.
+ 
+ [Fix]
+ 
+ Update the expected output returned by `aa-notify --help` in test-aa-
+ notify.py.
+ 
+ [Regression potential]
+ 
+ This is just an autopkgtest, we may see regressions if the test is used
+ with older version of apparmor-notify. With newer versions there's no
+ risk of regressions.

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

Title:
  apparmor autotest failure on jammy with linux 5.15

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Jammy:
  New

Bug description:
  [Impact]

  test-aa-notify is also checking if the output of `aa-notify --help`
  matches a specific text. However it looks like this output has changed
  in jammy so the autopkgtest is reporting errors like this:

  05:17:31 ERROR| [stderr] === test-aa-notify.py ===
  05:17:31 ERROR| [stderr] .ssF.
  05:17:31 ERROR| [stderr] 
==
  05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
  05:17:31 ERROR| [stderr] Test output of help text
  05:17:31 ERROR| [stderr] 
--
  05:17:31 ERROR| [stderr] Traceback (most recent call last):
  05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
  05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
  05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n 
 -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
  05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
  05:17:31 

[Touch-packages] [Bug 1961196] [NEW] apparmor autotest failure on jammy with linux 5.15

[Andrea Righi]

Public bug reported:

05:17:31 ERROR| [stderr] === test-aa-notify.py ===
05:17:31 ERROR| [stderr] .ssF.
05:17:31 ERROR| [stderr] 
==
05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
05:17:31 ERROR| [stderr] Test output of help text
05:17:31 ERROR| [stderr] 
--
05:17:31 ERROR| [stderr] Traceback (most recent call last):
05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n  
-h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug]
05:17:31 ERROR| [stderr]   
05:17:31 ERROR| [stderr]   Display AppArmor notifications or messages for 
DENIED entries.
05:17:31 ERROR| [stderr]   
05:17:31 ERROR| [stderr] - optional arguments:
05:17:31 ERROR| [stderr] + options:
05:17:31 ERROR| [stderr] -h, --helpshow this help message and 
exit
05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and 
display notifications
05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY environment 
variable (might be needed if
05:17:31 ERROR| [stderr]   sudo resets $DISPLAY)
05:17:31 ERROR| [stderr] -f FILE, --file FILE  search FILE for AppArmor 
messages
05:17:31 ERROR| [stderr] -l, --since-last  display stats since last 
login
05:17:31 ERROR| [stderr] -s NUM, --since-days NUM
05:17:31 ERROR| [stderr]   show stats for last NUM days 
(can be used alone or with
05:17:31 ERROR| [stderr]   -p)
05:17:31 ERROR| [stderr] -v, --verbose show messages with stats
05:17:31 ERROR| [stderr] -u USER, --user USER  user to drop privileges to 
when not using sudo
05:17:31 ERROR| [stderr] -w NUM, --wait NUMwait NUM seconds before 
displaying notifications (with
05:17:31 ERROR| [stderr]   -p)
05:17:31 ERROR| [stderr] --debug   debug mode
05:17:31 ERROR| [stderr]  : Got output "usage: aa-notify [-h] [-p] [--display 
DISPLAY] [-f FILE] [-l] [-s NUM] [-v]
05:17:31 ERROR| [stderr]  [-u USER] [-w NUM] [--debug]

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

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

** Also affects: apparmor (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

Title:
  apparmor autotest failure on jammy with linux 5.15

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Jammy:
  New

Bug description:
  05:17:31 ERROR| [stderr] === test-aa-notify.py ===
  05:17:31 ERROR| [stderr] .ssF.
  05:17:31 ERROR| [stderr] 
==
  05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
  05:17:31 ERROR| [stderr] Test output of help text
  05:17:31 ERROR| [stderr] 
--
  05:17:31 ERROR| [stderr] Traceback (most recent call last):
  05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
  05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
  05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n 
 -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
  05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug]
  05:17:31 ERROR| [stderr]   
  05:17:31 ERROR| [stderr]   Display AppArmor notifications or messages for 
DENIED entries.
  05:17:31 ERROR| [stderr]   
  05:17:31 ERROR| [stderr] - optional arguments:
  05:17:31 ERROR| [stderr] + options:
  05:17:31 ERROR| [stderr] -h, --helpshow this help message and 
exit
  05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and 
display notifications
  05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY 
environment variable (might be needed if
  05:17:31 ERROR| [stderr]   sudo resets $DISPLAY)
  05:17:31 

[Touch-packages] [Bug 1951390] Re: update iproute2

[Andrea Righi]

Adding also focal, because with the new linux-hwe-5.15 we get the same
failure.

** Summary changed:

- update iproute2 in jammy
+ update iproute2

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

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

Title:
  update iproute2

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Focal:
  New
Status in iproute2 source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6
  In-situ OAM (IOAM6).

  [Test case]

  This lack of support is triggering the following kernel selftest
  failure:

   # selftests: net: ioam6.sh
   # SKIP: iproute2 too old, missing ioam command
   not ok 1 selftests: net: ioam6.sh # exit=1

  [Fix]

  We're still using iproute2 v5.10 in jammy. It'd be nice to update to
  the latest upstream version (v5.15) to properly support this new
  kernel feature (and more).

  [Regression potential]

  We may introduce networking regressions with this change, because we
  are jumping from iproute2 5.10 to 5.15.

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


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

[Touch-packages] [Bug 1958904] Re: autopkgtest is failing on jammy with "no space left on device"

[Andrea Righi]

debdiff in attach can help to prevent this problem from happening
(bumping up image file to 2GB).

** Patch added: 
"initramfs-tools-prevent-out-of-disk-space-error-during-autotest.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+attachment/5557366/+files/initramfs-tools-prevent-out-of-disk-space-error-during-autotest.debdiff

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

Title:
  autopkgtest is failing on jammy with "no space left on device"

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  In debian/tests/prep-image we create an image file of 1GB, but recent
  jammy cloud images are (barely) bigger than that, for example the
  current one uncompressed is 1001MB...

  Maybe we should consider to create image files of 2GB or even bigger,
  considering that we are only going to allocate the space that is
  actually needed, because we create the file using truncate.

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


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

[Touch-packages] [Bug 1958904] [NEW] autopkgtest is failing on jammy with "no space left on device"

[Andrea Righi]

Public bug reported:

In debian/tests/prep-image we create an image file of 1GB, but recent
jammy cloud images are (barely) bigger than that, for example the
current one uncompressed is 1001MB...

Maybe we should consider to create image files of 2GB or even bigger,
considering that we are only going to allocate the space that is
actually needed, because we create the file using truncate.

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

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

Title:
  autopkgtest is failing on jammy with "no space left on device"

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  In debian/tests/prep-image we create an image file of 1GB, but recent
  jammy cloud images are (barely) bigger than that, for example the
  current one uncompressed is 1001MB...

  Maybe we should consider to create image files of 2GB or even bigger,
  considering that we are only going to allocate the space that is
  actually needed, because we create the file using truncate.

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


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

[Touch-packages] [Bug 1953005] Re: systemd autopkgtest failures on jammy 5.15 due to cgroup v2 ABI change

[Andrea Righi]

This failure isn't happening anymore, we can close this one.

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

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

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

Title:
  systemd autopkgtest failures on jammy 5.15 due to cgroup v2 ABI change

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I'm getting the following errors when running systemd autopkgtest on
  the latest Jammy 5.15 Ubuntu kernel:

  Received SIGCHLD from PID 2674 (sh).
  Child 2674 (sh) died (code=killed, status=13/PIPE)
  exec-ignoresigpipe-no.service: Failed to read oom_kill field of memory.events 
cgroup attribute: No such file or directory
  exec-ignoresigpipe-no.service: Child 2674 belongs to 
exec-ignoresigpipe-no.service.
  exec-ignoresigpipe-no.service: Main process exited, code=killed, 
status=13/PIPE
  exec-ignoresigpipe-no.service: Failed with result 'signal'.
  exec-ignoresigpipe-no.service: Service will not restart (restart setting)
  exec-ignoresigpipe-no.service: Changed start -> failed
  exec-ignoresigpipe-no.service: Unit entered failed state.
  Testing without inaccessible, skipping test_exec_inaccessiblepaths
  exec-ioschedulingclass-none.service: Passing 0 fds to service
  exec-ioschedulingclass-none.service: About to execute /bin/sh -x -c 
'c=$$(LC_ALL=C ionice); test "$${c%:*}" = "none"'
  exec-ioschedulingclass-none.service: Forked /bin/sh as 2675
  exec-ioschedulingclass-none.service: Changed dead -> start
  PR_SET_MM_ARG_START failed: Operation not permitted

  ...

  FAIL: test-execute

  The fact that is failing to read memory.events makes me think that the
  expected cgroup wasn't created correctly. I don't see any potential
  ABI change in the kernel. I need to investigate more.

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


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

[Touch-packages] [Bug 1951390] Re: update iproute2 in jammy

[Andrea Righi]

New iproute has been merged in jammy. We can close this.

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

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

Title:
  update iproute2 in jammy

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6
  In-situ OAM (IOAM6).

  [Test case]

  This lack of support is triggering the following kernel selftest
  failure:

   # selftests: net: ioam6.sh
   # SKIP: iproute2 too old, missing ioam command
   not ok 1 selftests: net: ioam6.sh # exit=1

  [Fix]

  We're still using iproute2 v5.10 in jammy. It'd be nice to update to
  the latest upstream version (v5.15) to properly support this new
  kernel feature (and more).

  [Regression potential]

  We may introduce networking regressions with this change, because we
  are jumping from iproute2 5.10 to 5.15.

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


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

[Touch-packages] [Bug 1951390] Re: update iproute2 in jammy

[Andrea Righi]

New iproute has been merged in jammy. We can close this.

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

Title:
  update iproute2 in jammy

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6
  In-situ OAM (IOAM6).

  [Test case]

  This lack of support is triggering the following kernel selftest
  failure:

   # selftests: net: ioam6.sh
   # SKIP: iproute2 too old, missing ioam command
   not ok 1 selftests: net: ioam6.sh # exit=1

  [Fix]

  We're still using iproute2 v5.10 in jammy. It'd be nice to update to
  the latest upstream version (v5.15) to properly support this new
  kernel feature (and more).

  [Regression potential]

  We may introduce networking regressions with this change, because we
  are jumping from iproute2 5.10 to 5.15.

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


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

[Touch-packages] [Bug 1953005] [NEW] systemd autopkgtest failures on jammy 5.15 due to cgroup v2 ABI change

[Andrea Righi]

Public bug reported:

I'm getting the following errors when running systemd autopkgtest on the
latest Jammy 5.15 Ubuntu kernel:

Received SIGCHLD from PID 2674 (sh).
Child 2674 (sh) died (code=killed, status=13/PIPE)
exec-ignoresigpipe-no.service: Failed to read oom_kill field of memory.events 
cgroup attribute: No such file or directory
exec-ignoresigpipe-no.service: Child 2674 belongs to 
exec-ignoresigpipe-no.service.
exec-ignoresigpipe-no.service: Main process exited, code=killed, status=13/PIPE
exec-ignoresigpipe-no.service: Failed with result 'signal'.
exec-ignoresigpipe-no.service: Service will not restart (restart setting)
exec-ignoresigpipe-no.service: Changed start -> failed
exec-ignoresigpipe-no.service: Unit entered failed state.
Testing without inaccessible, skipping test_exec_inaccessiblepaths
exec-ioschedulingclass-none.service: Passing 0 fds to service
exec-ioschedulingclass-none.service: About to execute /bin/sh -x -c 
'c=$$(LC_ALL=C ionice); test "$${c%:*}" = "none"'
exec-ioschedulingclass-none.service: Forked /bin/sh as 2675
exec-ioschedulingclass-none.service: Changed dead -> start
PR_SET_MM_ARG_START failed: Operation not permitted

...

FAIL: test-execute

The fact that is failing to read memory.events makes me think that the
expected cgroup wasn't created correctly. I don't see any potential ABI
change in the kernel. I need to investigate more.

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

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

Title:
  systemd autopkgtest failures on jammy 5.15 due to cgroup v2 ABI change

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm getting the following errors when running systemd autopkgtest on
  the latest Jammy 5.15 Ubuntu kernel:

  Received SIGCHLD from PID 2674 (sh).
  Child 2674 (sh) died (code=killed, status=13/PIPE)
  exec-ignoresigpipe-no.service: Failed to read oom_kill field of memory.events 
cgroup attribute: No such file or directory
  exec-ignoresigpipe-no.service: Child 2674 belongs to 
exec-ignoresigpipe-no.service.
  exec-ignoresigpipe-no.service: Main process exited, code=killed, 
status=13/PIPE
  exec-ignoresigpipe-no.service: Failed with result 'signal'.
  exec-ignoresigpipe-no.service: Service will not restart (restart setting)
  exec-ignoresigpipe-no.service: Changed start -> failed
  exec-ignoresigpipe-no.service: Unit entered failed state.
  Testing without inaccessible, skipping test_exec_inaccessiblepaths
  exec-ioschedulingclass-none.service: Passing 0 fds to service
  exec-ioschedulingclass-none.service: About to execute /bin/sh -x -c 
'c=$$(LC_ALL=C ionice); test "$${c%:*}" = "none"'
  exec-ioschedulingclass-none.service: Forked /bin/sh as 2675
  exec-ioschedulingclass-none.service: Changed dead -> start
  PR_SET_MM_ARG_START failed: Operation not permitted

  ...

  FAIL: test-execute

  The fact that is failing to read memory.events makes me think that the
  expected cgroup wasn't created correctly. I don't see any potential
  ABI change in the kernel. I need to investigate more.

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


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

[Touch-packages] [Bug 1951390] Re: update iproute2 in jammy

[Andrea Righi]

debdiff against Debian iproute2 5.15.0-1 (re-applied Ubuntu Fan driver).

v2: added this tracking bug to the changelog entry.

** Patch added: "iproute2-update-to-5.15-v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+attachment/5541717/+files/iproute2-update-to-5.15-v2.debdiff

** Description changed:

+ [Impact]
+ 
  Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6
- In-situ OAM (IOAM6). This lack of support is also triggering the
- following kernel selftest failure:
+ In-situ OAM (IOAM6).
  
-  # selftests: net: ioam6.sh
-  # SKIP: iproute2 too old, missing ioam command
-  not ok 1 selftests: net: ioam6.sh # exit=1
+ [Test case]
+ 
+ This lack of support is triggering the following kernel selftest
+ failure:
+ 
+  # selftests: net: ioam6.sh
+  # SKIP: iproute2 too old, missing ioam command
+  not ok 1 selftests: net: ioam6.sh # exit=1
+ 
+ [Fix]
  
  We're still using iproute2 v5.10 in jammy. It'd be nice to update to the
  latest upstream version (v5.15) to properly support this new kernel
  feature (and more).
+ 
+ [Regression potential]
+ 
+ We may introduce networking regressions with this change, because we are
+ jumping from iproute2 5.10 to 5.15.

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

Title:
  update iproute2 in jammy

Status in iproute2 package in Ubuntu:
  New
Status in iproute2 source package in Jammy:
  New

Bug description:
  [Impact]

  Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6
  In-situ OAM (IOAM6).

  [Test case]

  This lack of support is triggering the following kernel selftest
  failure:

   # selftests: net: ioam6.sh
   # SKIP: iproute2 too old, missing ioam command
   not ok 1 selftests: net: ioam6.sh # exit=1

  [Fix]

  We're still using iproute2 v5.10 in jammy. It'd be nice to update to
  the latest upstream version (v5.15) to properly support this new
  kernel feature (and more).

  [Regression potential]

  We may introduce networking regressions with this change, because we
  are jumping from iproute2 5.10 to 5.15.

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


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

[Touch-packages] [Bug 1951390] Re: update iproute2 in jammy

[Andrea Righi]

** Patch added: "iproute2-update-to-5.15.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+attachment/5541716/+files/iproute2-update-to-5.15.debdiff

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

Title:
  update iproute2 in jammy

Status in iproute2 package in Ubuntu:
  New
Status in iproute2 source package in Jammy:
  New

Bug description:
  [Impact]

  Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6
  In-situ OAM (IOAM6).

  [Test case]

  This lack of support is triggering the following kernel selftest
  failure:

   # selftests: net: ioam6.sh
   # SKIP: iproute2 too old, missing ioam command
   not ok 1 selftests: net: ioam6.sh # exit=1

  [Fix]

  We're still using iproute2 v5.10 in jammy. It'd be nice to update to
  the latest upstream version (v5.15) to properly support this new
  kernel feature (and more).

  [Regression potential]

  We may introduce networking regressions with this change, because we
  are jumping from iproute2 5.10 to 5.15.

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


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

[Touch-packages] [Bug 1951390] Re: update iproute2 in jammy

[Andrea Righi]

** Also affects: iproute2 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

Title:
  update iproute2 in jammy

Status in iproute2 package in Ubuntu:
  New
Status in iproute2 source package in Jammy:
  New

Bug description:
  Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6
  In-situ OAM (IOAM6). This lack of support is also triggering the
  following kernel selftest failure:

   # selftests: net: ioam6.sh
   # SKIP: iproute2 too old, missing ioam command
   not ok 1 selftests: net: ioam6.sh # exit=1

  We're still using iproute2 v5.10 in jammy. It'd be nice to update to
  the latest upstream version (v5.15) to properly support this new
  kernel feature (and more).

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


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

[Touch-packages] [Bug 1951390] [NEW] update iproute2 in jammy

[Andrea Righi]

Public bug reported:

Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6
In-situ OAM (IOAM6). This lack of support is also triggering the
following kernel selftest failure:

 # selftests: net: ioam6.sh
 # SKIP: iproute2 too old, missing ioam command
 not ok 1 selftests: net: ioam6.sh # exit=1

We're still using iproute2 v5.10 in jammy. It'd be nice to update to the
latest upstream version (v5.15) to properly support this new kernel
feature (and more).

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

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

Title:
  update iproute2 in jammy

Status in iproute2 package in Ubuntu:
  New

Bug description:
  Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6
  In-situ OAM (IOAM6). This lack of support is also triggering the
  following kernel selftest failure:

   # selftests: net: ioam6.sh
   # SKIP: iproute2 too old, missing ioam command
   not ok 1 selftests: net: ioam6.sh # exit=1

  We're still using iproute2 v5.10 in jammy. It'd be nice to update to
  the latest upstream version (v5.15) to properly support this new
  kernel feature (and more).

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


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

[Touch-packages] [Bug 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft

[Andrea Righi]

New debdiff with the enabled autopkgtest test case. (I'm assuming the
Suggests: packages are installed when we run autopkgtest, so I'm not
doing anything special to install nftables).

** Patch added: "iptables-nft-fix-counters-v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1949603/+attachment/5540968/+files/iptables-nft-fix-counters-v2.debdiff

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

Title:
  iptables-save -c shows incorrect counters with iptables-nft

Status in iptables package in Ubuntu:
  New
Status in iptables source package in Impish:
  New
Status in iptables source package in Jammy:
  New

Bug description:
  [Impact]

  Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
  is always failing. Initially I thought it was a kernel issue, but
  debugging further I found that the reason is that with Impish we're
  using iptables-nft by default instead of iptables-legacy.

  This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
  source directory) is creating a bunch of network namespaces and
  checking the iptables counters for the defined policies, in particular
  this is the interesting part:

  check_ipt_policy_count()
  {
  ns=$1

  ip netns exec $ns iptables-save -c |grep policy | ( read c rest
  ip netns exec $ns iptables -Z
  if [ x"$c" = x'[0:0]' ]; then
  exit 0
  elif [ x"$c" = x ]; then
  echo "ERROR: No counters"
  ret=1
  exit 111
  else
  exit 1
  fi
  )
  }

  If I use iptables-nft the counters are never [0:0] as they should be,
  so the test is failing. With iptables-legacy they are [0:0] and the
  test is passing.

  [Test case]

  tools/testing/selftests/net/xfrm_policy.sh from the Linux kernel
  source code.

  [Fix]

  Apply iptables upstream commit:

  5f1fcace ("iptables-nft: fix -Z option")

  In this way also with iptables-nft the counters are reported
  correctly.

  [Regression potential]

  We may require other upstream commits now that the -Z option is
  working properly with iptables-nft.

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


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

[Touch-packages] [Bug 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft

[Andrea Righi]

Alright I figured out why the tests were failing, simply nftables wasn't
installed in my test environment. I see that nftables is reported in the
Suggests: list.

@xnox IIRC we are installing all the suggests when we run the autotest,
is it correct?

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

Title:
  iptables-save -c shows incorrect counters with iptables-nft

Status in iptables package in Ubuntu:
  New
Status in iptables source package in Impish:
  New
Status in iptables source package in Jammy:
  New

Bug description:
  [Impact]

  Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
  is always failing. Initially I thought it was a kernel issue, but
  debugging further I found that the reason is that with Impish we're
  using iptables-nft by default instead of iptables-legacy.

  This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
  source directory) is creating a bunch of network namespaces and
  checking the iptables counters for the defined policies, in particular
  this is the interesting part:

  check_ipt_policy_count()
  {
  ns=$1

  ip netns exec $ns iptables-save -c |grep policy | ( read c rest
  ip netns exec $ns iptables -Z
  if [ x"$c" = x'[0:0]' ]; then
  exit 0
  elif [ x"$c" = x ]; then
  echo "ERROR: No counters"
  ret=1
  exit 111
  else
  exit 1
  fi
  )
  }

  If I use iptables-nft the counters are never [0:0] as they should be,
  so the test is failing. With iptables-legacy they are [0:0] and the
  test is passing.

  [Test case]

  tools/testing/selftests/net/xfrm_policy.sh from the Linux kernel
  source code.

  [Fix]

  Apply iptables upstream commit:

  5f1fcace ("iptables-nft: fix -Z option")

  In this way also with iptables-nft the counters are reported
  correctly.

  [Regression potential]

  We may require other upstream commits now that the -Z option is
  working properly with iptables-nft.

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


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

[Touch-packages] [Bug 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft

[Andrea Righi]

@xnox interestingly enough 2 tests are failing with nft and 1 test in
legacy running `./run-tests.sh --host`:

W: [FAILED]  ././testcases/ipt-restore/0004-restore-race_0: expected 0 but 
got 1
...
I: legacy results: [OK] 49 [FAILED] 1 [TOTAL] 50

W: [FAILED]  ././testcases/ipt-restore/0004-restore-race_0: expected 0 but 
got 1
W: [FAILED]  ././testcases/nft-only/0009-needless-bitwise_0: expected 0 but 
got 127
...
I: nft results: [OK] 48 [FAILED] 2 [TOTAL] 50

So it's definitely worth running this one, now it'd be nice to
understand the failures. Looking...

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

Title:
  iptables-save -c shows incorrect counters with iptables-nft

Status in iptables package in Ubuntu:
  New
Status in iptables source package in Impish:
  New
Status in iptables source package in Jammy:
  New

Bug description:
  [Impact]

  Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
  is always failing. Initially I thought it was a kernel issue, but
  debugging further I found that the reason is that with Impish we're
  using iptables-nft by default instead of iptables-legacy.

  This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
  source directory) is creating a bunch of network namespaces and
  checking the iptables counters for the defined policies, in particular
  this is the interesting part:

  check_ipt_policy_count()
  {
  ns=$1

  ip netns exec $ns iptables-save -c |grep policy | ( read c rest
  ip netns exec $ns iptables -Z
  if [ x"$c" = x'[0:0]' ]; then
  exit 0
  elif [ x"$c" = x ]; then
  echo "ERROR: No counters"
  ret=1
  exit 111
  else
  exit 1
  fi
  )
  }

  If I use iptables-nft the counters are never [0:0] as they should be,
  so the test is failing. With iptables-legacy they are [0:0] and the
  test is passing.

  [Test case]

  tools/testing/selftests/net/xfrm_policy.sh from the Linux kernel
  source code.

  [Fix]

  Apply iptables upstream commit:

  5f1fcace ("iptables-nft: fix -Z option")

  In this way also with iptables-nft the counters are reported
  correctly.

  [Regression potential]

  We may require other upstream commits now that the -Z option is
  working properly with iptables-nft.

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


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

[Touch-packages] [Bug 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft

[Andrea Righi]

** Description changed:

+ [Impact]
+ 
  Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
  is always failing. Initially I thought it was a kernel issue, but
  debugging further I found that the reason is that with Impish we're
  using iptables-nft by default instead of iptables-legacy.
  
  This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
  source directory) is creating a bunch of network namespaces and checking
  the iptables counters for the defined policies, in particular this is
  the interesting part:
  
  check_ipt_policy_count()
  {
- ns=$1
+ ns=$1
  
- ip netns exec $ns iptables-save -c |grep policy | ( read c rest
- ip netns exec $ns iptables -Z
- if [ x"$c" = x'[0:0]' ]; then
- exit 0
- elif [ x"$c" = x ]; then
- echo "ERROR: No counters"
- ret=1
- exit 111
- else
- exit 1
- fi
- )
+ ip netns exec $ns iptables-save -c |grep policy | ( read c rest
+ ip netns exec $ns iptables -Z
+ if [ x"$c" = x'[0:0]' ]; then
+ exit 0
+ elif [ x"$c" = x ]; then
+ echo "ERROR: No counters"
+ ret=1
+ exit 111
+ else
+ exit 1
+ fi
+ )
  }
  
  If I use iptables-nft the counters are never [0:0] as they should be, so
  the test is failing. With iptables-legacy they are [0:0] and the test is
  passing.
  
- Any idea why this is happening and how I can debug this in iptables?
+ [Test case]
  
- Thanks in advance.
+ tools/testing/selftests/net/xfrm_policy.sh from the Linux kernel source
+ code.
+ 
+ [Fix]
+ 
+ Apply iptables upstream commit:
+   
+ 5f1fcace ("iptables-nft: fix -Z option")
+ 
+ In this way also with iptables-nft the counters are reported correctly.
+ 
+ [Regression potential]
+ 
+ We may require other upstream commits now that the -Z option is working
+ properly with iptables-nft.

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

Title:
  iptables-save -c shows incorrect counters with iptables-nft

Status in iptables package in Ubuntu:
  New
Status in iptables source package in Impish:
  New
Status in iptables source package in Jammy:
  New

Bug description:
  [Impact]

  Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
  is always failing. Initially I thought it was a kernel issue, but
  debugging further I found that the reason is that with Impish we're
  using iptables-nft by default instead of iptables-legacy.

  This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
  source directory) is creating a bunch of network namespaces and
  checking the iptables counters for the defined policies, in particular
  this is the interesting part:

  check_ipt_policy_count()
  {
  ns=$1

  ip netns exec $ns iptables-save -c |grep policy | ( read c rest
  ip netns exec $ns iptables -Z
  if [ x"$c" = x'[0:0]' ]; then
  exit 0
  elif [ x"$c" = x ]; then
  echo "ERROR: No counters"
  ret=1
  exit 111
  else
  exit 1
  fi
  )
  }

  If I use iptables-nft the counters are never [0:0] as they should be,
  so the test is failing. With iptables-legacy they are [0:0] and the
  test is passing.

  [Test case]

  tools/testing/selftests/net/xfrm_policy.sh from the Linux kernel
  source code.

  [Fix]

  Apply iptables upstream commit:

  5f1fcace ("iptables-nft: fix -Z option")

  In this way also with iptables-nft the counters are reported
  correctly.

  [Regression potential]

  We may require other upstream commits now that the -Z option is
  working properly with iptables-nft.

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


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

[Touch-packages] [Bug 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft

[Andrea Righi]

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

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

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

Title:
  iptables-save -c shows incorrect counters with iptables-nft

Status in iptables package in Ubuntu:
  New
Status in iptables source package in Impish:
  New
Status in iptables source package in Jammy:
  New

Bug description:
  Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
  is always failing. Initially I thought it was a kernel issue, but
  debugging further I found that the reason is that with Impish we're
  using iptables-nft by default instead of iptables-legacy.

  This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
  source directory) is creating a bunch of network namespaces and
  checking the iptables counters for the defined policies, in particular
  this is the interesting part:

  check_ipt_policy_count()
  {
  ns=$1

  ip netns exec $ns iptables-save -c |grep policy | ( read c rest
  ip netns exec $ns iptables -Z
  if [ x"$c" = x'[0:0]' ]; then
  exit 0
  elif [ x"$c" = x ]; then
  echo "ERROR: No counters"
  ret=1
  exit 111
  else
  exit 1
  fi
  )
  }

  If I use iptables-nft the counters are never [0:0] as they should be,
  so the test is failing. With iptables-legacy they are [0:0] and the
  test is passing.

  Any idea why this is happening and how I can debug this in iptables?

  Thanks in advance.

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


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

[Touch-packages] [Bug 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft

[Andrea Righi]

The debdiff in attach seems to solve the problem.

Without this fix applied:

$ sudo ./tools/testing/selftests/net/xfrm_policy.sh 
PASS: policy before exception matches
FAIL: expected ping to .254 to fail (exceptions)
...

With this fix applied:

$ sudo ./tools/testing/selftests/net/xfrm_policy.sh 
PASS: policy before exception matches
PASS: ping to .254 bypassed ipsec tunnel (exceptions)
...


** Patch added: "iptables-nft-fix-counters.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1949603/+attachment/5537896/+files/iptables-nft-fix-counters.debdiff

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

Title:
  iptables-save -c shows incorrect counters with iptables-nft

Status in iptables package in Ubuntu:
  New
Status in iptables source package in Impish:
  New
Status in iptables source package in Jammy:
  New

Bug description:
  Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
  is always failing. Initially I thought it was a kernel issue, but
  debugging further I found that the reason is that with Impish we're
  using iptables-nft by default instead of iptables-legacy.

  This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
  source directory) is creating a bunch of network namespaces and
  checking the iptables counters for the defined policies, in particular
  this is the interesting part:

  check_ipt_policy_count()
  {
  ns=$1

  ip netns exec $ns iptables-save -c |grep policy | ( read c rest
  ip netns exec $ns iptables -Z
  if [ x"$c" = x'[0:0]' ]; then
  exit 0
  elif [ x"$c" = x ]; then
  echo "ERROR: No counters"
  ret=1
  exit 111
  else
  exit 1
  fi
  )
  }

  If I use iptables-nft the counters are never [0:0] as they should be,
  so the test is failing. With iptables-legacy they are [0:0] and the
  test is passing.

  Any idea why this is happening and how I can debug this in iptables?

  Thanks in advance.

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


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

[Touch-packages] [Bug 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft

[Andrea Righi]

FYI, I've tested the latest iptables from
https://git.netfilter.org/iptables/ and the test passes also with
iptables-nft.

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

Title:
  iptables-save -c shows incorrect counters with iptables-nft

Status in iptables package in Ubuntu:
  New
Status in iptables source package in Impish:
  New
Status in iptables source package in Jammy:
  New

Bug description:
  Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
  is always failing. Initially I thought it was a kernel issue, but
  debugging further I found that the reason is that with Impish we're
  using iptables-nft by default instead of iptables-legacy.

  This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
  source directory) is creating a bunch of network namespaces and
  checking the iptables counters for the defined policies, in particular
  this is the interesting part:

  check_ipt_policy_count()
  {
  ns=$1

  ip netns exec $ns iptables-save -c |grep policy | ( read c rest
  ip netns exec $ns iptables -Z
  if [ x"$c" = x'[0:0]' ]; then
  exit 0
  elif [ x"$c" = x ]; then
  echo "ERROR: No counters"
  ret=1
  exit 111
  else
  exit 1
  fi
  )
  }

  If I use iptables-nft the counters are never [0:0] as they should be,
  so the test is failing. With iptables-legacy they are [0:0] and the
  test is passing.

  Any idea why this is happening and how I can debug this in iptables?

  Thanks in advance.

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


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

[Touch-packages] [Bug 1949603] [NEW] iptables-save -c shows incorrect counters with iptables-nft

[Andrea Righi]

Public bug reported:

Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
is always failing. Initially I thought it was a kernel issue, but
debugging further I found that the reason is that with Impish we're
using iptables-nft by default instead of iptables-legacy.

This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
source directory) is creating a bunch of network namespaces and checking
the iptables counters for the defined policies, in particular this is
the interesting part:

check_ipt_policy_count()
{
ns=$1

ip netns exec $ns iptables-save -c |grep policy | ( read c rest
ip netns exec $ns iptables -Z
if [ x"$c" = x'[0:0]' ]; then
exit 0
elif [ x"$c" = x ]; then
echo "ERROR: No counters"
ret=1
exit 111
else
exit 1
fi
)
}

If I use iptables-nft the counters are never [0:0] as they should be, so
the test is failing. With iptables-legacy they are [0:0] and the test is
passing.

Any idea why this is happening and how I can debug this in iptables?

Thanks in advance.

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

** Affects: iptables (Ubuntu Impish)
 Importance: Undecided
 Status: New

** Affects: iptables (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Also affects: iptables (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: iptables (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

Title:
  iptables-save -c shows incorrect counters with iptables-nft

Status in iptables package in Ubuntu:
  New
Status in iptables source package in Impish:
  New
Status in iptables source package in Jammy:
  New

Bug description:
  Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
  is always failing. Initially I thought it was a kernel issue, but
  debugging further I found that the reason is that with Impish we're
  using iptables-nft by default instead of iptables-legacy.

  This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
  source directory) is creating a bunch of network namespaces and
  checking the iptables counters for the defined policies, in particular
  this is the interesting part:

  check_ipt_policy_count()
  {
  ns=$1

  ip netns exec $ns iptables-save -c |grep policy | ( read c rest
  ip netns exec $ns iptables -Z
  if [ x"$c" = x'[0:0]' ]; then
  exit 0
  elif [ x"$c" = x ]; then
  echo "ERROR: No counters"
  ret=1
  exit 111
  else
  exit 1
  fi
  )
  }

  If I use iptables-nft the counters are never [0:0] as they should be,
  so the test is failing. With iptables-legacy they are [0:0] and the
  test is passing.

  Any idea why this is happening and how I can debug this in iptables?

  Thanks in advance.

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


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

[Touch-packages] [Bug 1916931] Re: omshell returns inconsistent results or segfaults

[Andrea]

I confirm the bug on our environment with Ubuntu 20.04 and isc-dhcp-server 
4.4.1. 
Omshell randomly goes on segfault:
[Tue Sep 28 11:05:22 2021] omshell[4604]: segfault at 0 ip 55623cdd06dc sp 
7ffd5a2c7c78 error 4 in omshell[55623cd97000+45000]

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

Title:
  omshell returns inconsistent results or segfaults

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  I have just built a Ubuntu 20.04 server and installed isc-dhcp-server
  4.4.1 on it and I am seeing inconsistent returns from omshell. 
  Initially omshell returns data as expected, but when I exit and re-enter 
  omshell connections fail.

  Here is the initial, working, session:

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect
  obj: 
  > new failover-state
  obj: failover-state
  > set name = "dhcp-failover"
  obj: failover-state
  name = "dhcp-failover"
  > open
  obj: failover-state
  name = "dhcp-failover"
  partner-address = c0:9d:e9:76:e9:55:00:00
  partner-port = 00:00:02:07
  local-address = 10:9d:e9:76:e9:55:00:00
  local-port = 00:00:02:07
  max-outstanding-updates = 00:00:00:0a
  mclt = 00:00:01:2c
  load-balance-max-secs = 00:00:00:03
  load-balance-hba =
  
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
  partner-state = 00:00:00:02
  local-state = 00:00:00:02
  partner-stos = 60:36:d0:68
  local-stos = 60:36:8b:3b
  hierarchy = 00:00:00:01
  last-packet-sent = 00:00:00:00
  last-timestamp-received = 00:00:00:00
  skew = 00:00:00:00
  max-response-delay = 00:00:00:3c
  cur-unacked-updates = 00:00:00:00

  Here is what I see when the connect fails.  Well, just hangs really.

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect

  And then I hit ctrl-c to break out and tried again:

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect
  Segmentation fault (core dumped)

  Note, the peer to this server is still running Ubuntu 18.04 with
  isc-dhcp-server 4.3.5.  Running the exact same commands on the peer
  works reliably.  (They are using the same python script to drive
  omshell.)  The DHCP server on the new system appears to be working 
  just fine as reported by omshell on the peer and systemctl.

  I was curious if the problem could be with the mis-matched versions
  of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system
  and get the same results.

  I also tried using a python script with the pypureomapi module to
  try and determine if the problem was in omshell or the server.  I 
  got very similar results when I attempted to get information about
  the failover state of the server.  Interestingly interrogating
  the server about host information seems to work just fine.

  This is a critical bug since I don't see how to fail over a DHCP
  that is running the isc-dhcp-server on 20.04 without being able
  to issue omapi commands.

  I am attaching apport output to this bug report.

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


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

[Touch-packages] [Bug 1943441] Re: lxc: lxc-test-parse-config-file failure

[Andrea Righi]

Makes sense, thanks for looking at this Christian!

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

Title:
  lxc: lxc-test-parse-config-file failure

Status in lxc package in Ubuntu:
  In Progress

Bug description:
  I'm getting the following error with the lxc kernel autotest on
  impish:

  08:46:04 DEBUG| parse_config_file.c: 60: set_get_compare_clear_save_load: 
expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for 
config key "lxc.selinux.context" do not match
  08:46:04 DEBUG|
  08:46:04 DEBUG| parse_config_file.c: 382: main: lxc.selinux.context
  08:46:06 INFO | ERRORubuntu_lxc.lxc-test-parse-config-file
ubuntu_lxc.lxc-test-parse-config-filetimestamp=1631090766localtime=Sep 
08 08:46:06Command  failed, rc=1, Command returned non-zero exit status
* Command:
/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file
Exit status: 1
Duration: 0.0550210475922

stderr:
parse_config_file.c: 60: set_get_compare_clear_save_load: expected value 
"system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key 
"lxc.selinux.context" do not match

parse_config_file.c: 382: main: lxc.selinux.context

  I haven't investigated very much, but it looks like a
  (mis)configuration change / issue. Does it ring any bell? Otherwise
  I'll investigate more.

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


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

[Touch-packages] [Bug 1943441] [NEW] lxc: lxc-test-parse-config-file failure

[Andrea Righi]

Public bug reported:

I'm getting the following error with the lxc kernel autotest on impish:

08:46:04 DEBUG| parse_config_file.c: 60: set_get_compare_clear_save_load: 
expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for 
config key "lxc.selinux.context" do not match
08:46:04 DEBUG|
08:46:04 DEBUG| parse_config_file.c: 382: main: lxc.selinux.context
08:46:06 INFO | ERRORubuntu_lxc.lxc-test-parse-config-file
ubuntu_lxc.lxc-test-parse-config-filetimestamp=1631090766localtime=Sep 
08 08:46:06Command  failed, rc=1, Command returned non-zero exit status
  * Command:
  /tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file
  Exit status: 1
  Duration: 0.0550210475922

  stderr:
  parse_config_file.c: 60: set_get_compare_clear_save_load: expected value 
"system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key 
"lxc.selinux.context" do not match

  parse_config_file.c: 382: main: lxc.selinux.context

I haven't investigated very much, but it looks like a (mis)configuration
change / issue. Does it ring any bell? Otherwise I'll investigate more.

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

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

Title:
  lxc: lxc-test-parse-config-file failure

Status in lxc package in Ubuntu:
  New

Bug description:
  I'm getting the following error with the lxc kernel autotest on
  impish:

  08:46:04 DEBUG| parse_config_file.c: 60: set_get_compare_clear_save_load: 
expected value "system_u:system_r:lxc_t:s0:c22" and retrieved value "" for 
config key "lxc.selinux.context" do not match
  08:46:04 DEBUG|
  08:46:04 DEBUG| parse_config_file.c: 382: main: lxc.selinux.context
  08:46:06 INFO | ERRORubuntu_lxc.lxc-test-parse-config-file
ubuntu_lxc.lxc-test-parse-config-filetimestamp=1631090766localtime=Sep 
08 08:46:06Command  failed, rc=1, Command returned non-zero exit status
* Command:
/tmp/lxc-pkg-ubuntu/src/tests/lxc-test-parse-config-file
Exit status: 1
Duration: 0.0550210475922

stderr:
parse_config_file.c: 60: set_get_compare_clear_save_load: expected value 
"system_u:system_r:lxc_t:s0:c22" and retrieved value "" for config key 
"lxc.selinux.context" do not match

parse_config_file.c: 382: main: lxc.selinux.context

  I haven't investigated very much, but it looks like a
  (mis)configuration change / issue. Does it ring any bell? Otherwise
  I'll investigate more.

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


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

[Touch-packages] [Bug 1938771] [NEW] lxc-test-rootfs test regression with 4.0.10-0ubuntu3

[Andrea Righi]

Public bug reported:

It looks like the option "lxc.rootfs.options = ro" is not honored with
lxc 4.0.10-0ubuntu3 and it used to work with lxc 4.0.6-0ubuntu1 (kernel
is the same, I'm testing this with 5.13.0-13.13).

Output of the test:

09:12 ubuntu@impish$ sudo ./src/tests/lxc-test-rootfs
+ PHASE=setup
+ trap cleanup EXIT
+ lxc-destroy -n lxc-test-rootfs -f
lxc-destroy: lxc-test-rootfs: tools/lxc_destroy.c: main: 242 Container is not 
defined
+ true
+ lxc-create -t busybox -n lxc-test-rootfs
+ PHASE=ro_rootfs
+ echo 'Starting phase ro_rootfs'
Starting phase ro_rootfs
+ config=/var/lib/lxc/lxc-test-rootfs/config
+ sed -i /lxc.rootfs.options/d /var/lib/lxc/lxc-test-rootfs/config
+ echo 'lxc.rootfs.options = ro'
+ lxc-start -n lxc-test-rootfs
++ lxc-info -n lxc-test-rootfs -p -H
+ pid=2147
+ ro=0
+ mkdir /proc/2147/root/rotest
+ '[' 0 -ne 0 ']'
+ cleanup
+ set +e
+ lxc-destroy -n lxc-test-rootfs -f
+ '[' ro_rootfs '!=' done ']'
+ echo 'rootfs test failed at ro_rootfs'
rootfs test failed at ro_rootfs
+ exit 1

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

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

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

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

Title:
  lxc-test-rootfs test regression with 4.0.10-0ubuntu3

Status in lxc package in Ubuntu:
  New
Status in lxc source package in Impish:
  New

Bug description:
  It looks like the option "lxc.rootfs.options = ro" is not honored with
  lxc 4.0.10-0ubuntu3 and it used to work with lxc 4.0.6-0ubuntu1
  (kernel is the same, I'm testing this with 5.13.0-13.13).

  Output of the test:

  09:12 ubuntu@impish$ sudo ./src/tests/lxc-test-rootfs
  + PHASE=setup
  + trap cleanup EXIT
  + lxc-destroy -n lxc-test-rootfs -f
  lxc-destroy: lxc-test-rootfs: tools/lxc_destroy.c: main: 242 Container is not 
defined
  + true
  + lxc-create -t busybox -n lxc-test-rootfs
  + PHASE=ro_rootfs
  + echo 'Starting phase ro_rootfs'
  Starting phase ro_rootfs
  + config=/var/lib/lxc/lxc-test-rootfs/config
  + sed -i /lxc.rootfs.options/d /var/lib/lxc/lxc-test-rootfs/config
  + echo 'lxc.rootfs.options = ro'
  + lxc-start -n lxc-test-rootfs
  ++ lxc-info -n lxc-test-rootfs -p -H
  + pid=2147
  + ro=0
  + mkdir /proc/2147/root/rotest
  + '[' 0 -ne 0 ']'
  + cleanup
  + set +e
  + lxc-destroy -n lxc-test-rootfs -f
  + '[' ro_rootfs '!=' done ']'
  + echo 'rootfs test failed at ro_rootfs'
  rootfs test failed at ro_rootfs
  + exit 1

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


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

[Touch-packages] [Bug 1931064] [NEW] lxc autotest failure with kernel >= 5.13

[Andrea Righi]

Public bug reported:

The lxc autotest is failing with the following error(s) on the latest
kernel linux-unstable 5.13:

FAIL: lxc-tests: lxc-test-apparmor (1s)
---
failed - opened /sys/kernel/uevent_helper
---
PASS: lxc-tests: lxc-test-apparmor-generated (0s)
PASS: lxc-tests: lxc-test-apparmor-mount (29s)
FAIL: lxc-tests: lxc-test-attach (1s)
---
attach.c: 410: main: Using "/tmp/attach_x8lgO2" as temporary log file for 
container lxc-attach-test

I was able to bisect the problem and found that the offending commit is:

bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check /proc/$pid/attr/
writes against file opener")

This commit looks like a sane fix, so simply reverting it in the kernel
doesn't seem a viable solution.

I think we should address and understand the issue in the lxc package.

Detailed log of the failure: https://autopkgtest.ubuntu.com/results
/autopkgtest-impish-canonical-kernel-team-
bootstrap/impish/amd64/l/lxc/20210601_082733_a3ae4@/log.gz

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

** Description changed:

  The lxc autotest is failing with the following error(s) on the latest
  kernel linux-unstable 5.13:
  
  FAIL: lxc-tests: lxc-test-apparmor (1s)
  ---
  failed - opened /sys/kernel/uevent_helper
  ---
  PASS: lxc-tests: lxc-test-apparmor-generated (0s)
  PASS: lxc-tests: lxc-test-apparmor-mount (29s)
  FAIL: lxc-tests: lxc-test-attach (1s)
  ---
  attach.c: 410: main: Using "/tmp/attach_x8lgO2" as temporary log file for 
container lxc-attach-test
  
  I was able to bisect the problem and found that the offending commit is:
  
  bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check /proc/$pid/attr/
  writes against file opener")
  
  This commit looks like a sane fix, so simply reverting it in the kernel
  doesn't seem a viable solution.
  
  I think we should address and understand the issue in the lxc package.
+ 
+ Detailed log of the failure: https://autopkgtest.ubuntu.com/results
+ /autopkgtest-impish-canonical-kernel-team-
+ bootstrap/impish/amd64/l/lxc/20210601_082733_a3ae4@/log.gz

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

Title:
  lxc autotest failure with kernel >= 5.13

Status in lxc package in Ubuntu:
  New

Bug description:
  The lxc autotest is failing with the following error(s) on the latest
  kernel linux-unstable 5.13:

  FAIL: lxc-tests: lxc-test-apparmor (1s)
  ---
  failed - opened /sys/kernel/uevent_helper
  ---
  PASS: lxc-tests: lxc-test-apparmor-generated (0s)
  PASS: lxc-tests: lxc-test-apparmor-mount (29s)
  FAIL: lxc-tests: lxc-test-attach (1s)
  ---
  attach.c: 410: main: Using "/tmp/attach_x8lgO2" as temporary log file for 
container lxc-attach-test

  I was able to bisect the problem and found that the offending commit
  is:

  bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check
  /proc/$pid/attr/ writes against file opener")

  This commit looks like a sane fix, so simply reverting it in the
  kernel doesn't seem a viable solution.

  I think we should address and understand the issue in the lxc package.

  Detailed log of the failure: https://autopkgtest.ubuntu.com/results
  /autopkgtest-impish-canonical-kernel-team-
  bootstrap/impish/amd64/l/lxc/20210601_082733_a3ae4@/log.gz

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

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

[Touch-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing

[Andrea]

Firefox screenshot example

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489523/+files/20210418_180038.jpg

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

Title:
  Massive screen flashing artefacts - tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.10 x64 frequently updated.

  I noticed in the last week that after a while there are huge screen
  artefacts, that I would describe as flashing. Squares of screen flash,
  normally linked to widgets on screen.

  E.g.: the app bars on the left can start flashing blue, or parts of editors.
  I noticed it more in firefox, made worse by scrolling.
  VirtualBox is severely affected too.
  VS Code.

  It does not happen immediately and the feeling I get is that it starts
  happening when there is a lot on screen. For example has not happened
  at all in this session, but I have done little or nothing screen-
  heavy.

  The issue gets worse, then might settle down for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 13:53:28 2021
  DistUpgraded: 2020-11-27 20:39:33,916 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-02-01 (441 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing

[Andrea]

Screenshot of the normal application bar.

** Attachment added: "20210418_180315.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489524/+files/20210418_180315.jpg

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

Title:
  Massive screen flashing artefacts - tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.10 x64 frequently updated.

  I noticed in the last week that after a while there are huge screen
  artefacts, that I would describe as flashing. Squares of screen flash,
  normally linked to widgets on screen.

  E.g.: the app bars on the left can start flashing blue, or parts of editors.
  I noticed it more in firefox, made worse by scrolling.
  VirtualBox is severely affected too.
  VS Code.

  It does not happen immediately and the feeling I get is that it starts
  happening when there is a lot on screen. For example has not happened
  at all in this session, but I have done little or nothing screen-
  heavy.

  The issue gets worse, then might settle down for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 13:53:28 2021
  DistUpgraded: 2020-11-27 20:39:33,916 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-02-01 (441 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing

[Andrea]

Screenshot of damaged application bar.
See the blue square below VLC and compare with the other image.

There should be the zoom icon.

** Attachment added: "20210418_180321.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489525/+files/20210418_180321.jpg

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

Title:
  Massive screen flashing artefacts - tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.10 x64 frequently updated.

  I noticed in the last week that after a while there are huge screen
  artefacts, that I would describe as flashing. Squares of screen flash,
  normally linked to widgets on screen.

  E.g.: the app bars on the left can start flashing blue, or parts of editors.
  I noticed it more in firefox, made worse by scrolling.
  VirtualBox is severely affected too.
  VS Code.

  It does not happen immediately and the feeling I get is that it starts
  happening when there is a lot on screen. For example has not happened
  at all in this session, but I have done little or nothing screen-
  heavy.

  The issue gets worse, then might settle down for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 13:53:28 2021
  DistUpgraded: 2020-11-27 20:39:33,916 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-02-01 (441 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing

[Andrea]

Firefox screenshot example

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489522/+files/20210418_180028.jpg

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

Title:
  Massive screen flashing artefacts - tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.10 x64 frequently updated.

  I noticed in the last week that after a while there are huge screen
  artefacts, that I would describe as flashing. Squares of screen flash,
  normally linked to widgets on screen.

  E.g.: the app bars on the left can start flashing blue, or parts of editors.
  I noticed it more in firefox, made worse by scrolling.
  VirtualBox is severely affected too.
  VS Code.

  It does not happen immediately and the feeling I get is that it starts
  happening when there is a lot on screen. For example has not happened
  at all in this session, but I have done little or nothing screen-
  heavy.

  The issue gets worse, then might settle down for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 13:53:28 2021
  DistUpgraded: 2020-11-27 20:39:33,916 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-02-01 (441 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1924910] Re: Massive screen flashing artefacts - tearing

[Andrea]

Firefox screenshot example

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924910/+attachment/5489521/+files/20210418_180021.jpg

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

Title:
  Massive screen flashing artefacts - tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.10 x64 frequently updated.

  I noticed in the last week that after a while there are huge screen
  artefacts, that I would describe as flashing. Squares of screen flash,
  normally linked to widgets on screen.

  E.g.: the app bars on the left can start flashing blue, or parts of editors.
  I noticed it more in firefox, made worse by scrolling.
  VirtualBox is severely affected too.
  VS Code.

  It does not happen immediately and the feeling I get is that it starts
  happening when there is a lot on screen. For example has not happened
  at all in this session, but I have done little or nothing screen-
  heavy.

  The issue gets worse, then might settle down for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 18 13:53:28 2021
  DistUpgraded: 2020-11-27 20:39:33,916 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2020-02-01 (441 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1924910] [NEW] Massive screen flashing artefacts - tearing

[Andrea]

Public bug reported:

On Ubuntu 20.10 x64 frequently updated.

I noticed in the last week that after a while there are huge screen
artefacts, that I would describe as flashing. Squares of screen flash,
normally linked to widgets on screen.

E.g.: the app bars on the left can start flashing blue, or parts of editors.
I noticed it more in firefox, made worse by scrolling.
VirtualBox is severely affected too.
VS Code.

It does not happen immediately and the feeling I get is that it starts
happening when there is a lot on screen. For example has not happened at
all in this session, but I have done little or nothing screen-heavy.

The issue gets worse, then might settle down for a while.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
Uname: Linux 5.8.0-50-generic x86_64
NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 18 13:53:28 2021
DistUpgraded: 2020-11-27 20:39:33,916 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: groovy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.16, 5.8.0-49-generic, x86_64: installed
 virtualbox, 6.1.16, 5.8.0-50-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
InstallationDate: Installed on 2020-02-01 (441 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic 
root=/dev/mapper/fedora_bomba-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to groovy on 2020-11-27 (141 days ago)
dmi.bios.date: 11/11/2015
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption groovy ubuntu

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

Title:
  Massive screen flashing artefacts - tearing

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 20.10 x64 frequently updated.

  I noticed in the last week that after a while there are huge screen
  artefacts, that I would describe as flashing. Squares of screen flash,
  normally linked to widgets on screen.

  E.g.: the app bars on the left can start flashing blue, or parts of editors.
  I noticed it more in firefox, made worse by scrolling.
  VirtualBox is severely affected too.
  VS Code.

  It does not happen immediately and the feeling I get is that it starts
  happening when there is a lot on screen. For example has not happened
  at all in this session, but I have done little or nothing screen-
  heavy.

  The issue gets worse, then might settle down for a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18
  Uname: Linux 5.8.0-50-generic x86_64
  NonfreeKernelModules: socwatch2_11 vtsspp sep5 socperf3 pax
  ApportVersion: 

[Touch-packages] [Bug 1703377] Re: Gnome online account login prevents paste or autotype

[Andrea Ieri]

As well as in 20.10 (gnome-online-accounts 3.37.90-1ubuntu1).

By the way, the upstream bug link is now https://gitlab.gnome.org/GNOME
/gnome-online-accounts/-/issues/17

** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues #17
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/17

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

Title:
  Gnome online account login prevents paste or autotype

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  On entering Login data to an online account such as google.

  Using keepass as password manager I now can not enter my password via
  paste nor via autotype. Trying any of them results in an invalid
  password.

  Ubuntu 16.10 - GNOME Shell 3.20.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1703377/+subscriptions

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

[Touch-packages] [Bug 1923432] Re: apparmor-utils: missing CAP_CHECKPOINT_RESTORE in /etc/apparmor/severity.db

[Andrea Righi]

New debdiff that contains a proper reference to the upstream patch.
Thanks!

** Patch added: "apparmor-utils-support-cap-checkpoint-restore.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1923432/+attachment/5486963/+files/apparmor-utils-support-cap-checkpoint-restore.debdiff

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

Title:
  apparmor-utils: missing CAP_CHECKPOINT_RESTORE in
  /etc/apparmor/severity.db

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

Bug description:
  It looks like /etc/apparmor/severity.db is missing the new capability
  CAP_CHECKPOINT_RESTORE.

  This causes the following regression test failure:

ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1

  This new capability is correctly supported by the parser already (see
  d/p/ubuntu/parser-Add-support-for-cap-checkpoint-restore.patch), so we
  probably need to update severity.db as well.

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

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

[Touch-packages] [Bug 1923432] Re: apparmor-utils: missing CAP_CHECKPOINT_RESTORE in /etc/apparmor/severity.db

[Andrea Righi]

@sbeattie sorry I didn't notice your comment, I can post another debdiff
that includes the proper upstream commit.

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

Title:
  apparmor-utils: missing CAP_CHECKPOINT_RESTORE in
  /etc/apparmor/severity.db

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

Bug description:
  It looks like /etc/apparmor/severity.db is missing the new capability
  CAP_CHECKPOINT_RESTORE.

  This causes the following regression test failure:

ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1

  This new capability is correctly supported by the parser already (see
  d/p/ubuntu/parser-Add-support-for-cap-checkpoint-restore.patch), so we
  probably need to update severity.db as well.

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

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

[Touch-packages] [Bug 1923432] Re: apparmor-utils: missing CAP_CHECKPOINT_RESTORE in /etc/apparmor/severity.db

[Andrea Righi]

** Patch added: "apparmor-utils-support-cap-checkpoint-restore.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1923432/+attachment/5486955/+files/apparmor-utils-support-cap-checkpoint-restore.debdiff

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

Title:
  apparmor-utils: missing CAP_CHECKPOINT_RESTORE in
  /etc/apparmor/severity.db

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

Bug description:
  It looks like /etc/apparmor/severity.db is missing the new capability
  CAP_CHECKPOINT_RESTORE.

  This causes the following regression test failure:

ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1

  This new capability is correctly supported by the parser already (see
  d/p/ubuntu/parser-Add-support-for-cap-checkpoint-restore.patch), so we
  probably need to update severity.db as well.

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

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

[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[andrea]

Nothing to do for me. Ubuntu 20.10 HP spectre x360. 5.11.22 Kernel (no
microphone)

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Touch-packages] [Bug 1923432] [NEW] apparmor-utils: missing CAP_CHECKPOINT_RESTORE in /etc/apparmor/severity.db

[Andrea Righi]

Public bug reported:

It looks like /etc/apparmor/severity.db is missing the new capability
CAP_CHECKPOINT_RESTORE.

This causes the following regression test failure:

  ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
  make: *** [Makefile:81: check_severity_db] Error 1

This new capability is correctly supported by the parser already (see
d/p/ubuntu/parser-Add-support-for-cap-checkpoint-restore.patch), so we
probably need to update severity.db as well.

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

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

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

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

Title:
  apparmor-utils: missing CAP_CHECKPOINT_RESTORE in
  /etc/apparmor/severity.db

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

Bug description:
  It looks like /etc/apparmor/severity.db is missing the new capability
  CAP_CHECKPOINT_RESTORE.

  This causes the following regression test failure:

ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db
make: *** [Makefile:81: check_severity_db] Error 1

  This new capability is correctly supported by the parser already (see
  d/p/ubuntu/parser-Add-support-for-cap-checkpoint-restore.patch), so we
  probably need to update severity.db as well.

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

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

[Touch-packages] [Bug 1922723] [NEW] Weird CTRL+SHIFT+KEY behaviour

[Andrea Agnolin]

Public bug reported:

I run a newly installed Ubuntu Hirsute.
Inside a "Ubuntu on Xorg"(GNOME) session i cannot use CTRL+SHIFT+KEY shortcut 
normally.
If I press first CTRL, then SHIFT, then KEY everything works.
If I press SHIFT, then CTRL then KEY nothing happens.
On the Ubuntu (GNOME Wayland) session things works out normal.

Step to reproduce:
* Log in in a Xorg session
* Open gnome-terminal
* Press CTRL + SHIFT + "N" (in this order), a new terminal window appears
* Press SHIFT + CTRL + "N" (in this order), nothing happens.

The same happens with Firefox, Nautilus and other apps.

Possibly, Related to this, I also found that, only on a Xorg session,
during a Wine-runned gamed I play "CTRL + KEY" behaves just like "KEY".
But this might be a Wine bug.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu61
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  6 14:14:37 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 rtl8821ce, 5.5.2.1, 5.11.0-13-generic, x86_64: installed
 virtualbox, 6.1.18, 5.11.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a7]
   Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:84a7]
InstallationDate: Installed on 2021-03-31 (5 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 
4.2 Adapter
 Bus 001 Device 002: ID 05c8:03c7 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP TrueVision HD Camera
 Bus 001 Device 004: ID 046d:c51b Logitech, Inc. V220 Cordless Optical Mouse 
for Notebooks
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Laptop 15-da0xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic 
root=UUID=81ec23d7-e690-4f52-b570-c2c252d1f0e8 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2018
dmi.bios.release: 15.7
dmi.bios.vendor: Insyde
dmi.bios.version: F.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 84A7
dmi.board.vendor: HP
dmi.board.version: 80.31
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 80.31
dmi.modalias: 
dmi:bvnInsyde:bvrF.07:bd11/21/2018:br15.7:efr80.31:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.31:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15-da0xxx
dmi.product.sku: 4YC20EA#ABZ
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute ubuntu

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

Title:
  Weird CTRL+SHIFT+KEY behaviour

Status in xorg package in Ubuntu:
  New

Bug description:
  I run a newly installed Ubuntu Hirsute.
  Inside a "Ubuntu on Xorg"(GNOME) session i cannot use CTRL+SHIFT+KEY shortcut 
normally.
  If I press first CTRL, then SHIFT, then KEY everything works.
  If I press SHIFT, then CTRL then KEY nothing happens.
  On the Ubuntu (GNOME Wayland) session things works out normal.

  Step to reproduce:
  * Log in in a Xorg session
  * Open gnome-terminal
  * Press CTRL + SHIFT + "N" (in this order), a new terminal window appears
  * Press SHIFT + CTRL + "N" (in this order), nothing happens.

  The same happens with Firefox, Nautilus and other apps.

  Possibly, Related to this, I also found that, only on a Xorg session,
  during a Wine-runned gamed I play "CTRL + KEY" behaves just like
  "KEY". But this might be a Wine bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 

[Touch-packages] [Bug 1921618] [NEW] Black wallpaper instead than set image

[Andrea Bonarini]

Public bug reported:

The image set as wallpaper appears for one second and then is replaced by a 
black screen.
This occurs after a hard reset. After a suspension: nothing worked and I had to 
do a hard reset by switching the machine off. At restart I'm in the mentioned 
situation and the usual methods to reset the wall paper do not fix the problem.
Thank you!

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
Uname: Linux 5.4.0-70-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Mar 28 13:23:15 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 620 [1028:07a7]
InstallationDate: Installed on 2017-06-16 (1381 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
 Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 001 Device 005: ID 0a5c:5832 Broadcom Corp. 5880
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 5480
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic 
root=UUID=0db16900-e9f1-49a7-b5db-508d231aac23 ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/07/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.17.1
dmi.board.name: 0NDFXD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.1:bd01/07/2020:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn0NDFXD:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5480
dmi.product.sku: 07A7
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug compiz-0.9 focal ubuntu

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

Title:
  Black wallpaper instead than set image

Status in xorg package in Ubuntu:
  New

Bug description:
  The image set as wallpaper appears for one second and then is replaced by a 
black screen.
  This occurs after a hard reset. After a suspension: nothing worked and I had 
to do a hard reset by switching the machine off. At restart I'm in the 
mentioned situation and the usual methods to reset the wall paper do not fix 
the problem.
  Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Mar 28 13:23:15 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:07a7]
  InstallationDate: Installed on 2017-06-16 (1381 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 005: ID 

[Touch-packages] [Bug 1915779] [NEW] sudo: bad onwership of /usr/bin/sudo and /usr/lib/sudo/sudoers.so (2001:2501)

[Andrea Righi]

Public bug reported:

After enabling the -proposed ppa in Hirsute (21.04) I'm getting the
following error:

ubuntu@hirsute:~$ sudo su -
sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
ubuntu@hirsute:~$ ls -l /usr/bin/sudo
-rwsr-xr-x 1 2001 2501 190952 Feb 10 11:42 /usr/bin/sudo

I had a root session open so I could fix it by manually setting user and
group ownership back to root.

After that I noticed that also /usr/lib/sudo/sudoers.so had the wrong
ownership:

ubuntu@hirsute:~$ sudo su -
sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy"
sudo: /usr/lib/sudo/sudoers.so must be owned by uid 0
sudo: fatal error, unable to load plugins

I manually fixed also this one and now my system seems to work normally.

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

** Affects: sudo (Ubuntu Hirsute)
 Importance: Undecided
 Status: New

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

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

Title:
  sudo: bad onwership of /usr/bin/sudo and /usr/lib/sudo/sudoers.so
  (2001:2501)

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

Bug description:
  After enabling the -proposed ppa in Hirsute (21.04) I'm getting the
  following error:

  ubuntu@hirsute:~$ sudo su -
  sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
  ubuntu@hirsute:~$ ls -l /usr/bin/sudo
  -rwsr-xr-x 1 2001 2501 190952 Feb 10 11:42 /usr/bin/sudo

  I had a root session open so I could fix it by manually setting user
  and group ownership back to root.

  After that I noticed that also /usr/lib/sudo/sudoers.so had the wrong
  ownership:

  ubuntu@hirsute:~$ sudo su -
  sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy"
  sudo: /usr/lib/sudo/sudoers.so must be owned by uid 0
  sudo: fatal error, unable to load plugins

  I manually fixed also this one and now my system seems to work
  normally.

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

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

[Touch-packages] [Bug 1913979] Re: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink

[Andrea Ieri]

** Description changed:

- As of a couple of days ago, I am unable to get network manager to
- connect to any wifi network.
+ If the /etc/NetworkManager/system-connections directory is a cross-
+ filesystem symlink, activating connections will fail with the unrelated
+ messages:
  
- It looks like the groovy network manager packages have not received any
- updates since release, but since I can successfully use wpasupplicant
- directly I'm ruling out issues with my specific home wifi or wifi card.
+ * "failed to create file ...: Read-only file system" (TRACE level)
  
- Though this might still ultimately be due to my specific setup, the
- error message logged by network manager is really insufficient for
- determining where the failure may lie, even when debug mode is turned
- on[0]. The Gnome UI doesn't display an error at all.
+ * "failure adding connection: settings plugin does not support adding
+ connections" (DEBUG level and above)
+ 
+ * no error message (Gnome UI)
+ 
+ I suspect moving the systems-connections directory onto a separate
+ filesystem is not supported because network manager tries to atomically
+ move a connection temp file into place and fails, but this is really
+ hard to figure out since the error messages are completely unrelated.
+ 
  
  Versions:
  
  Ubuntu 20.10
  network-manager 1.26.2-1ubuntu1
  network-manager-gnome 1.18.0-1ubuntu2
  
+ 
  How to reproduce:
  
+ sudo mv /etc/NetworkManager/system-connections 
/some/other/mountpoint/system-connections
+ sudo ln -s /some/other/mountpoint/system-connections 
/etc/NetworkManager/system-connections
+ 
+ Then:
  * select any wifi network via the Gnome UI, or
  * connect to a wifi network via nmcli, or
  * connect to a wifi network via nmtui
  
+ 
  Symptoms:
  
- * no UI popup is produced when using the Gnome UI
- * the message "failure adding connection: settings plugin does not support 
adding connections" is shown when using nmcli or nmtui
- * debug logs include slightly more information:
+ * "failed to create file ...: Read-only file system" (TRACE level,
+ journalctl)
  
- Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8651] 
active-connection[0x55b6b9a25b50]: set device "wlp61s0" [0x55b6b9b62cb0]
- Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8652] 
device[fd0e531202f8924b] (wlp61s0): add_pending_action (1): 'activation-22'
- Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8653] 
active-connection[0x55b6b9a25b50]: constructed (NMActRequest, version-id 22, 
type managed)
- Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8807] 
active-connection[0x55b6b9a25b50]: Failed to activate '(null)': failure adding 
connection: settings plugin does not support adding connections
- Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8808] 
active-connection[0x55b6b9a25b50]: set state deactivated (was unknown)
- Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8808] 
active-connection[0x55b6b9a25b50]: check-master-ready: not signalling (state 
deactivated, no master)
- Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8808] 
device[fd0e531202f8924b] (wlp61s0): remove_pending_action (0): 'activation-22'
- Jan 31 20:32:57 laptop NetworkManager[3315]:   [1612143177.8811] audit: 
op="connection-add-activate" pid=452187 uid=1000 result="fail" reason="failure 
adding connection: settings plugin does not support adding connections"
- Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8812] 
active-connection[0x55b6b9a25b50]: disposing
+ * "failure adding connection: settings plugin does not support adding
+ connections" (DEBUG level and above, journalctl and nmtui/nmcli output)
  
- Workaround:
- 
- * connect to networks by using wpasupplicant directly[1]
+ * no error message (Gnome UI)
  
  
- [0] https://wiki.gnome.org/Projects/NetworkManager/Debugging
- [1] https://shapeshed.com/linux-wifi/
+ Relevant sample logs:
+ 
+ Feb 01 20:56:04 laptop NetworkManager[1368510]:  [1612230964.4038] 
active-connection[0x56274f6f0a60]: creating
+ Feb 01 20:56:04 laptop NetworkManager[1368510]:  [1612230964.4039] 
active-connection[0x56274f6f0a60]: set device "wlp61s0" [0x56274f883f00]
+ Feb 01 20:56:04 laptop NetworkManager[1368510]:  [1612230964.4039] 
device[d62304f9da70d783] (wlp61s0): add_pending_action (1): 'activation-5'
+ Feb 01 20:56:04 laptop NetworkManager[1368510]:  [1612230964.4040] 
active-connection[0x56274f6f0a60]: constructed (NMActRequest, version-id 5, 
type managed)
+ Feb 01 20:56:04 laptop NetworkManager[1368510]:  [1612230964.4040] 
auth: call[37]: 
CheckAuthorization(org.freedesktop.NetworkManager.network-control), 
subject=unix-process[pid=1369566, uid=0, start=18908113] (succeeding for root)
+ Feb 01 20:56:04 laptop NetworkManager[1368510]:  [1612230964.4041] 
auth: call[37]: completed: authorized=1, challenge=0 (simulated)
+ Feb 01 20:56:04 laptop NetworkManager[1368510]:  [1612230964.4041] 
auth: call[38]: 

[Touch-packages] [Bug 1913979] Re: misleading error messages when /etc/NetworkManager/system-connections is a cross-filesystem symlink

[Andrea Ieri]

** Summary changed:

- settings plugin does not support adding connections
+ misleading error messages when /etc/NetworkManager/system-connections is a 
cross-filesystem symlink

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

Title:
  misleading error messages when /etc/NetworkManager/system-connections
  is a cross-filesystem symlink

Status in network-manager package in Ubuntu:
  New

Bug description:
  As of a couple of days ago, I am unable to get network manager to
  connect to any wifi network.

  It looks like the groovy network manager packages have not received
  any updates since release, but since I can successfully use
  wpasupplicant directly I'm ruling out issues with my specific home
  wifi or wifi card.

  Though this might still ultimately be due to my specific setup, the
  error message logged by network manager is really insufficient for
  determining where the failure may lie, even when debug mode is turned
  on[0]. The Gnome UI doesn't display an error at all.

  Versions:

  Ubuntu 20.10
  network-manager 1.26.2-1ubuntu1
  network-manager-gnome 1.18.0-1ubuntu2

  How to reproduce:

  * select any wifi network via the Gnome UI, or
  * connect to a wifi network via nmcli, or
  * connect to a wifi network via nmtui

  Symptoms:

  * no UI popup is produced when using the Gnome UI
  * the message "failure adding connection: settings plugin does not support 
adding connections" is shown when using nmcli or nmtui
  * debug logs include slightly more information:

  Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8651] 
active-connection[0x55b6b9a25b50]: set device "wlp61s0" [0x55b6b9b62cb0]
  Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8652] 
device[fd0e531202f8924b] (wlp61s0): add_pending_action (1): 'activation-22'
  Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8653] 
active-connection[0x55b6b9a25b50]: constructed (NMActRequest, version-id 22, 
type managed)
  Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8807] 
active-connection[0x55b6b9a25b50]: Failed to activate '(null)': failure adding 
connection: settings plugin does not support adding connections
  Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8808] 
active-connection[0x55b6b9a25b50]: set state deactivated (was unknown)
  Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8808] 
active-connection[0x55b6b9a25b50]: check-master-ready: not signalling (state 
deactivated, no master)
  Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8808] 
device[fd0e531202f8924b] (wlp61s0): remove_pending_action (0): 'activation-22'
  Jan 31 20:32:57 laptop NetworkManager[3315]:   [1612143177.8811] audit: 
op="connection-add-activate" pid=452187 uid=1000 result="fail" reason="failure 
adding connection: settings plugin does not support adding connections"
  Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8812] 
active-connection[0x55b6b9a25b50]: disposing

  Workaround:

  * connect to networks by using wpasupplicant directly[1]


  [0] https://wiki.gnome.org/Projects/NetworkManager/Debugging
  [1] https://shapeshed.com/linux-wifi/

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

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

[Touch-packages] [Bug 1913979] [NEW] settings plugin does not support adding connections

[Andrea Ieri]

Public bug reported:

As of a couple of days ago, I am unable to get network manager to
connect to any wifi network.

It looks like the groovy network manager packages have not received any
updates since release, but since I can successfully use wpasupplicant
directly I'm ruling out issues with my specific home wifi or wifi card.

Though this might still ultimately be due to my specific setup, the
error message logged by network manager is really insufficient for
determining where the failure may lie, even when debug mode is turned
on[0]. The Gnome UI doesn't display an error at all.

Versions:

Ubuntu 20.10
network-manager 1.26.2-1ubuntu1
network-manager-gnome 1.18.0-1ubuntu2

How to reproduce:

* select any wifi network via the Gnome UI, or
* connect to a wifi network via nmcli, or
* connect to a wifi network via nmtui

Symptoms:

* no UI popup is produced when using the Gnome UI
* the message "failure adding connection: settings plugin does not support 
adding connections" is shown when using nmcli or nmtui
* debug logs include slightly more information:

Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8651] 
active-connection[0x55b6b9a25b50]: set device "wlp61s0" [0x55b6b9b62cb0]
Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8652] 
device[fd0e531202f8924b] (wlp61s0): add_pending_action (1): 'activation-22'
Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8653] 
active-connection[0x55b6b9a25b50]: constructed (NMActRequest, version-id 22, 
type managed)
Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8807] 
active-connection[0x55b6b9a25b50]: Failed to activate '(null)': failure adding 
connection: settings plugin does not support adding connections
Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8808] 
active-connection[0x55b6b9a25b50]: set state deactivated (was unknown)
Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8808] 
active-connection[0x55b6b9a25b50]: check-master-ready: not signalling (state 
deactivated, no master)
Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8808] 
device[fd0e531202f8924b] (wlp61s0): remove_pending_action (0): 'activation-22'
Jan 31 20:32:57 laptop NetworkManager[3315]:   [1612143177.8811] audit: 
op="connection-add-activate" pid=452187 uid=1000 result="fail" reason="failure 
adding connection: settings plugin does not support adding connections"
Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8812] 
active-connection[0x55b6b9a25b50]: disposing

Workaround:

* connect to networks by using wpasupplicant directly[1]


[0] https://wiki.gnome.org/Projects/NetworkManager/Debugging
[1] https://shapeshed.com/linux-wifi/

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

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

Title:
  settings plugin does not support adding connections

Status in network-manager package in Ubuntu:
  New

Bug description:
  As of a couple of days ago, I am unable to get network manager to
  connect to any wifi network.

  It looks like the groovy network manager packages have not received
  any updates since release, but since I can successfully use
  wpasupplicant directly I'm ruling out issues with my specific home
  wifi or wifi card.

  Though this might still ultimately be due to my specific setup, the
  error message logged by network manager is really insufficient for
  determining where the failure may lie, even when debug mode is turned
  on[0]. The Gnome UI doesn't display an error at all.

  Versions:

  Ubuntu 20.10
  network-manager 1.26.2-1ubuntu1
  network-manager-gnome 1.18.0-1ubuntu2

  How to reproduce:

  * select any wifi network via the Gnome UI, or
  * connect to a wifi network via nmcli, or
  * connect to a wifi network via nmtui

  Symptoms:

  * no UI popup is produced when using the Gnome UI
  * the message "failure adding connection: settings plugin does not support 
adding connections" is shown when using nmcli or nmtui
  * debug logs include slightly more information:

  Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8651] 
active-connection[0x55b6b9a25b50]: set device "wlp61s0" [0x55b6b9b62cb0]
  Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8652] 
device[fd0e531202f8924b] (wlp61s0): add_pending_action (1): 'activation-22'
  Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8653] 
active-connection[0x55b6b9a25b50]: constructed (NMActRequest, version-id 22, 
type managed)
  Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8807] 
active-connection[0x55b6b9a25b50]: Failed to activate '(null)': failure adding 
connection: settings plugin does not support adding connections
  Jan 31 20:32:57 laptop NetworkManager[3315]:  [1612143177.8808] 
active-connection[0x55b6b9a25b50]: set state deactivated (was unknown)
  Jan 31 20:32:57 laptop 

[Touch-packages] [Bug 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD

[Andrea Paolo]

I'm at the end of a Ubuntu installation on a pre-installed windows laptop. I 
have the same issue Ubuntu 20 hangs at "kvm: exiting hardware virtualization" 
on AMD laptop.
It has been stuck there for half an hour or more.
I didn't set the wi-fi connection during installation

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

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers with DVD

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

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

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

[Touch-packages] [Bug 1878519] Re: Unable to use TLSv1.1 to connect to external servers

[Andrea Giudiceandrea]

See
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/comments/13
for a workaround.

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

Title:
  Unable to use TLSv1.1 to connect to external servers

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  I'm on 20.04 LTS (Focal Fossa). (Kubuntu)

  openssl (I'm on 1.1.1f-1ubuntu2) appears to now be set to use a
  minimum of TLSv1.2

  This is despite the fact that the Changelog 
(https://launchpad.net/ubuntu/+source/openssl/+changelog) says:
Revert "Enable system default config to enforce TLS1.2 as a
minimum" & "Increase default security level from 1 to 2".

  As a result of this I can't get fetchmail to connect to an external
  IMPA server I use, which only uses TLSv1.1

  I *can* get:
openssl s_client -state -cipher "DEFAULT:@SECLEVEL=1" -connect ... 
-starttls imap
  to open a connexion, but I can find no way of getting that option into a 
configuration file such that it is used.

  Consequently I cannot use a secure connexion to retrieve my emails.

  All was fine in 19.10.

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

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

[Touch-packages] [Bug 1887397] Re: perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1

[Andrea Righi]

** Attachment added: "perf object files / build tree"
   
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1887397/+attachment/5392329/+files/perf-build-fail.tar.gz

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

Title:
  perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1

Status in binutils package in Ubuntu:
  New
Status in binutils source package in Groovy:
  New

Bug description:
  After updating to binutils 2.34.90.20200706-1ubuntu1 Linux' perf build
  is failing with the following error:

  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 syntax error in dynamic list
  collect2: error: ld returned 1 exit status

  The file mentioned in the error (libtraceevent-dynamic-list) contains
  some '@' that ld doesn't seem to like:

  $ cat lib/traceevent/plugins/libtraceevent-dynamic-list
  {
  __stack_chk_fail@@GLIBC_2.4;
  free@@GLIBC_2.2.5;
  memset@@GLIBC_2.2.5;
  realloc@@GLIBC_2.2.5;
  sprintf@@GLIBC_2.2.5;
  strcmp@@GLIBC_2.2.5;
  strdup@@GLIBC_2.2.5;
  strncmp@@GLIBC_2.2.5;
  tep_find_any_field;
  tep_find_field;
  tep_find_function;
  tep_find_function_address;
  tep_get_field_raw;
  tep_get_field_val;
  tep_is_file_bigendian;
  tep_is_local_bigendian;
  tep_plugin_add_options;
  tep_plugin_remove_options;
  tep_print_func_field;
  tep_print_num_field;
  tep_read_number_field;
  tep_register_comm;
  tep_register_event_handler;
  tep_register_print_function;
  tep_unregister_event_handler;
  tep_unregister_print_function;
  trace_seq_printf;
  trace_seq_putc;
  trace_seq_puts;
  trace_seq_terminate;
  warning;
  };

  The same file generated in a Focal environment (w/ binutils
  2.34-6ubuntu1) looks as following:

  $ cat lib/traceevent/plugins/libtraceevent-dynamic-list
  {
  __stack_chk_fail;
  free;
  memset;
  realloc;
  sprintf;
  strcmp;
  strdup;
  strncmp;
  tep_find_any_field;
  tep_find_field;
  tep_find_function;
  tep_find_function_address;
  tep_get_field_raw;
  tep_get_field_val;
  tep_is_file_bigendian;
  tep_is_local_bigendian;
  tep_plugin_add_options;
  tep_plugin_remove_options;
  tep_print_func_field;
  tep_print_num_field;
  tep_read_number_field;
  tep_register_comm;
  tep_register_event_handler;
  tep_register_print_function;
  tep_unregister_event_handler;
  tep_unregister_print_function;
  trace_seq_printf;
  trace_seq_putc;
  trace_seq_puts;
  trace_seq_terminate;
  warning;
  };

  And here is the chunk of Makefile that is generating this file:

  define do_generate_dynamic_list_file
  symbol_type=`$(NM) -u -D $1 | awk 'NF>1 {print $$1}' | \
  xargs echo "U w W" | tr 'w ' 'W\n' | sort -u | xargs echo`;\
  if [ "$$symbol_type" = "U W" ];then \
  (echo '{';  \
  $(NM) -u -D $1 | awk 'NF>1 {print "\t"$$2";"}' | sort -u;\
  echo '};';  \
  ) > $2; \
  else\
  (echo Either missing one of [$1] or bad version of $(NM)) 
1>&2;\
  fi

  My guess is that something changed in the output of `nm` to show the @
  charaters that ld does not like.

  This problem is currently breaking all kernel builds in Groovy.

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

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

[Touch-packages] [Bug 1887397] Re: perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1

[Andrea Righi]

Adding the specific command that is reporting error:

gcc  -Wbad-function-cast -Wdeclaration-after-statement -Wformat-security 
-Wformat-y2k -Winit-self -Wmissing-declarations -Wmissing-prototypes 
-Wnested-externs -Wno-system-headers -Wold-style-definition -Wpacked 
-Wredundant-decls -Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef 
-Wwrite-strings -Wformat -Wstrict-aliasing=3 -Wshadow 
-DHAVE_ARCH_X86_64_SUPPORT -Iarch/x86/include/generated 
-DHAVE_SYSCALL_TABLE_SUPPORT -DHAVE_PERF_REGS_SUPPORT 
-DHAVE_ARCH_REGS_QUERY_REGISTER_OFFSET -Werror -O6 -fno-omit-frame-pointer 
-ggdb3 -funwind-tables -Wall -Wextra -std=gnu99 -fstack-protector-all 
-D_FORTIFY_SOURCE=2 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/perf/lib/include 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/perf/util/include 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/perf/arch/x86/include
 -I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/include/ 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/arch/x86/include/uapi
 -I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/include/uapi 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/arch/x86/include/ 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/arch/x86/ 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/perf/util 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/perf 
-I/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/lib/ 
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE 
-DHAVE_SYNC_COMPARE_AND_SWAP_SUPPORT -DHAVE_PTHREAD_ATTR_SETAFFINITY_NP 
-DHAVE_PTHREAD_BARRIER -DHAVE_EVENTFD -DHAVE_GET_CURRENT_DIR_NAME -DHAVE_GETTID 
-DHAVE_DWARF_GETLOCATIONS_SUPPORT -DHAVE_GLIBC_SUPPORT -DHAVE_AIO_SUPPORT 
-DHAVE_SCHED_GETCPU_SUPPORT -DHAVE_SETNS_SUPPORT -DHAVE_LIBELF_SUPPORT 
-DHAVE_LIBELF_MMAP_SUPPORT -DHAVE_ELF_GETPHDRNUM_SUPPORT 
-DHAVE_GELF_GETNOTE_SUPPORT -DHAVE_ELF_GETSHDRSTRNDX_SUPPORT 
-DHAVE_DWARF_SUPPORT  -DHAVE_LIBBPF_SUPPORT -DHAVE_BPF_PROLOGUE -DHAVE_JITDUMP 
-DHAVE_DWARF_UNWIND_SUPPORT -DNO_LIBUNWIND_DEBUG_FRAME -DHAVE_LIBUNWIND_SUPPORT 
-DHAVE_LIBCRYPTO_SUPPORT -DHAVE_SLANG_SUPPORT -DNO_LIBPERL 
-DHAVE_TIMERFD_SUPPORT -DNO_LIBPYTHON -DHAVE_CPLUS_DEMANGLE_SUPPORT 
-DHAVE_ZLIB_SUPPORT -DHAVE_LZMA_SUPPORT -DHAVE_LIBCAP_SUPPORT 
-DHAVE_BACKTRACE_SUPPORT -DHAVE_LIBNUMA_SUPPORT -DHAVE_KVM_STAT_SUPPORT 
-DHAVE_AUXTRACE_SUPPORT -DHAVE_JVMTI_CMLR -Wl,-z,noexecstack  -lunwind-x86_64 
-lunwind -llzma  -Xlinker 
--dynamic-list=/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/lib/traceevent/plugins/libtraceevent-dynamic-list
 \
perf-in.o pmu-events/pmu-events-in.o -Wl,--whole-archive 
/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/lib/api/libapi.a 
/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/lib/traceevent/libtraceevent.a
 
/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/lib/subcmd/libsubcmd.a
 /home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/perf/lib/libperf.a 
/home/arighi/canonical/kernel/ubuntu/unstable/linux/tools/lib/bpf/libbpf.a  
-Wl,--no-whole-archive -Wl,--start-group -lpthread -lrt -lm -ldl -lelf -ldw 
-lunwind-x86_64 -lunwind -llzma -lcrypto -lslang -liberty -lz -llzma -lcap 
-lnuma -Wl,--end-group -o perf

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

Title:
  perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1

Status in binutils package in Ubuntu:
  New
Status in binutils source package in Groovy:
  New

Bug description:
  After updating to binutils 2.34.90.20200706-1ubuntu1 Linux' perf build
  is failing with the following error:

  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 syntax error in dynamic list
  collect2: error: ld returned 1 exit status

  The file mentioned in the error (libtraceevent-dynamic-list) contains
  some '@' that ld doesn't seem to like:

  $ cat lib/traceevent/plugins/libtraceevent-dynamic-list
  {
  __stack_chk_fail@@GLIBC_2.4;
  free@@GLIBC_2.2.5;
  memset@@GLIBC_2.2.5;
  realloc@@GLIBC_2.2.5;
  sprintf@@GLIBC_2.2.5;
  strcmp@@GLIBC_2.2.5;
  strdup@@GLIBC_2.2.5;
  strncmp@@GLIBC_2.2.5;
  tep_find_any_field;
  tep_find_field;
  tep_find_function;
  tep_find_function_address;
  tep_get_field_raw;
  tep_get_field_val;
  tep_is_file_bigendian;
 

[Touch-packages] [Bug 1887397] [NEW] perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1

[Andrea Righi]

Public bug reported:

After updating to binutils 2.34.90.20200706-1ubuntu1 Linux' perf build
is failing with the following error:

/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 syntax error in dynamic list
collect2: error: ld returned 1 exit status

The file mentioned in the error (libtraceevent-dynamic-list) contains
some '@' that ld doesn't seem to like:

$ cat lib/traceevent/plugins/libtraceevent-dynamic-list
{
__stack_chk_fail@@GLIBC_2.4;
free@@GLIBC_2.2.5;
memset@@GLIBC_2.2.5;
realloc@@GLIBC_2.2.5;
sprintf@@GLIBC_2.2.5;
strcmp@@GLIBC_2.2.5;
strdup@@GLIBC_2.2.5;
strncmp@@GLIBC_2.2.5;
tep_find_any_field;
tep_find_field;
tep_find_function;
tep_find_function_address;
tep_get_field_raw;
tep_get_field_val;
tep_is_file_bigendian;
tep_is_local_bigendian;
tep_plugin_add_options;
tep_plugin_remove_options;
tep_print_func_field;
tep_print_num_field;
tep_read_number_field;
tep_register_comm;
tep_register_event_handler;
tep_register_print_function;
tep_unregister_event_handler;
tep_unregister_print_function;
trace_seq_printf;
trace_seq_putc;
trace_seq_puts;
trace_seq_terminate;
warning;
};

The same file generated in a Focal environment (w/ binutils
2.34-6ubuntu1) looks as following:

$ cat lib/traceevent/plugins/libtraceevent-dynamic-list
{
__stack_chk_fail;
free;
memset;
realloc;
sprintf;
strcmp;
strdup;
strncmp;
tep_find_any_field;
tep_find_field;
tep_find_function;
tep_find_function_address;
tep_get_field_raw;
tep_get_field_val;
tep_is_file_bigendian;
tep_is_local_bigendian;
tep_plugin_add_options;
tep_plugin_remove_options;
tep_print_func_field;
tep_print_num_field;
tep_read_number_field;
tep_register_comm;
tep_register_event_handler;
tep_register_print_function;
tep_unregister_event_handler;
tep_unregister_print_function;
trace_seq_printf;
trace_seq_putc;
trace_seq_puts;
trace_seq_terminate;
warning;
};

And here is the chunk of Makefile that is generating this file:

define do_generate_dynamic_list_file
symbol_type=`$(NM) -u -D $1 | awk 'NF>1 {print $$1}' | \
xargs echo "U w W" | tr 'w ' 'W\n' | sort -u | xargs echo`;\
if [ "$$symbol_type" = "U W" ];then \
(echo '{';  \
$(NM) -u -D $1 | awk 'NF>1 {print "\t"$$2";"}' | sort -u;\
echo '};';  \
) > $2; \
else\
(echo Either missing one of [$1] or bad version of $(NM)) 1>&2;\
fi

My guess is that something changed in the output of `nm` to show the @
charaters that ld does not like.

This problem is currently breaking all kernel builds in Groovy.

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

** Affects: binutils (Ubuntu Groovy)
 Importance: Undecided
 Status: New

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

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

Title:
  perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1

Status in binutils package in Ubuntu:
  New
Status in binutils source package in Groovy:
  New

Bug description:
  After updating to binutils 2.34.90.20200706-1ubuntu1 Linux' perf build
  is failing with the following error:

  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 ignoring invalid character `@' in script
  
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
 syntax error in dynamic 

[Touch-packages] [Bug 1877294] [NEW] graphic problem and no internet connection

[Andrea Grande]

Public bug reported:

every time I start my personal computer there is an error on the
graphics module and I have to restart the service network manager in the
terminal.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-45-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu May  7 13:53:42 2020
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated 
Graphics Controller [104d:90ab]
InstallationDate: Installed on 2020-05-01 (5 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1)
MachineType: Sony Corporation SVE1511F1EW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=c4e39bf2-5485-4178-b290-aa431b8a172b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/24/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0180E5
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0180E5:bd04/24/2012:svnSonyCorporation:pnSVE1511F1EW:pvrC107K8GJ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: SVE1511F1EW
dmi.product.version: C107K8GJ
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu May  7 13:44:28 2020
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

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

Title:
  graphic problem and no internet connection

Status in xorg package in Ubuntu:
  New

Bug description:
  every time I start my personal computer there is an error on the
  graphics module and I have to restart the service network manager in
  the terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-45-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu May  7 13:53:42 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [104d:90ab]
  InstallationDate: Installed on 2020-05-01 (5 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 
(20190227.1)
  MachineType: Sony Corporation SVE1511F1EW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=c4e39bf2-5485-4178-b290-aa431b8a172b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0180E5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 

[Touch-packages] [Bug 1855026] [NEW] package initramfs-tools 0.133ubuntu10 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de sal

[Andrea Velazco]

Public bug reported:

error to install package initiframes

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: initramfs-tools 0.133ubuntu10
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
AptOrdering:
 amd64-microcode:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Dec  3 17:21:20 2019
ErrorMessage: el subproceso instalado paquete initramfs-tools script 
post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2019-11-26 (7 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: el 
subproceso instalado paquete initramfs-tools script post-installation devolvió 
el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package eoan

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

Title:
  package initramfs-tools 0.133ubuntu10 failed to install/upgrade: el
  subproceso instalado paquete initramfs-tools script post-installation
  devolvió el código de salida de error 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  error to install package initiframes

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: initramfs-tools 0.133ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  AptOrdering:
   amd64-microcode:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Dec  3 17:21:20 2019
  ErrorMessage: el subproceso instalado paquete initramfs-tools script 
post-installation devolvió el código de salida de error 1
  InstallationDate: Installed on 2019-11-26 (7 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: el 
subproceso instalado paquete initramfs-tools script post-installation devolvió 
el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 740127] Re: ondemand script in initscripts uses arbitrary sleep

[Andrea Ieri]

It also overrides whatever governor the cpufrequtils sets, and with such
delay not even careful ordering of the services can prevent ondemand
from winning.

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

Title:
  ondemand script in initscripts uses arbitrary sleep

Status in sysvinit package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: initscripts

  The ondemand script in the initscripts package is all very well, but
  the 60 second pause before activation is both arbitrary, and in my
  case, wrong.

  The comment next to it suggests that the 60 seconds is to allow the
  desktop to be logged in before the CPU govener is changed.  however my
  laptop gets from grub to desktop in 17 seconds and then I have to wait
  up to one minute from then for my CPUs to be put into ondemand mode.
  Given I can have CPU frequency panel applets which can change the
  frequency govener; why is the ondemand setting not an XDG autostart
  app which uses the same communications channels to set the govener
  after the desktop has started?

  It took me quite some time to track down that this was the issue as I
  was, from a user point of view, simply seeing that my CPU govener
  choice of ondemand was not being preserved across reboots, yet if I
  left my laptop alone for a bit after booting, the CPUs "suddenly" went
  into ondemand mode.

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

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

[Touch-packages] [Bug 1826056] Re: Desktop context: Keep aligned, Organize desktop by name missing in 19.04

[Andrea Azzarone]

** Package changed: tracker (Ubuntu) => gnome-shell-extension-desktop-
icons (Ubuntu)

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

Title:
  Desktop context: Keep aligned, Organize desktop by name missing in
  19.04

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  After upgrading from 18.10 to 19.04 the desktop context menu no longer
  contains the choices:

  Keep aligned
  Organize desktop by name

  These were very useful to me. I would like them to be restored.

  Ubuntu 19.04, 64bit
  Gnome 3.32.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1826056/+subscriptions

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

[Touch-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment

[Andrea Azzarone]

I proposed a fix upstream [1]. A workaround can be added to apport to
workaroud this while polkit is fixed upstream: we could for example
spawn pkttyagent manually (a similar approach is used by systemd).

[1] https://gitlab.freedesktop.org/polkit/polkit/merge_requests/28

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in policykit-1 package in Ubuntu:
  New

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+subscriptions

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

[Touch-packages] [Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Andrea Azzarone]

** Merge proposal linked:
   
https://code.launchpad.net/~azzar1/ubuntu/+source/gtk+3.0/+git/gtk+3.0/+merge/364501

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

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

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

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

[Touch-packages] [Bug 1816415] Re: gjs-console crashed with SIGSEGV in g_socket_receive_message_with_timeout()

[Andrea Azzarone]

Fixed in gobject-introspection (1.60.0-1).

** Changed in: glib2.0 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  gjs-console crashed with SIGSEGV in
  g_socket_receive_message_with_timeout()

Status in glib2.0 package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/434b8b4abd971c7f84ca824ef5878a00d547753a
  https://gitlab.gnome.org/GNOME/gjs/issues/227

  ---

  I have performance problems, after updating.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gjs 1.54.3-1build1
  Uname: Linux 5.0.0-05rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 18 07:39:11 2019
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2018-12-02 (77 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gjs 
/home/username/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/daemon.js
  SegvAnalysis:
   Segfault happened at: 0x7f224b1fafd8:mov(%r15),%edx
   PC (0x7f224b1fafd8) ok
   source "(%r15)" (0xfff98002) not located in a known VMA region 
(needed readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gjs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_socket_receive_message () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
  Title: gjs-console crashed with SIGSEGV in g_socket_receive_message()
  UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1818992] Re: /usr/bin/software-properties-gtk:gi.repository.GLib.GError:/usr/bin/software-properties-gtk@100:__init__:init_livepatch:__init__:__init__

[Andrea Azzarone]

** Changed in: software-properties (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  /usr/bin/software-properties-gtk:gi.repository.GLib.GError:/usr/bin
  /software-properties-gtk@100:__init__:init_livepatch:__init__:__init__

Status in software-properties package in Ubuntu:
  In Progress

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.97.8, the problem page at 
https://errors.ubuntu.com/problem/d8b64b46f7abc79d13d08d935604a5f7a174e166 
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/.

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

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

[Touch-packages] [Bug 1818992] Re: /usr/bin/software-properties-gtk:gi.repository.GLib.GError:/usr/bin/software-properties-gtk@100:__init__:init_livepatch:__init__:__init__

[Andrea Azzarone]

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  /usr/bin/software-properties-gtk:gi.repository.GLib.GError:/usr/bin
  /software-properties-gtk@100:__init__:init_livepatch:__init__:__init__

Status in software-properties package in Ubuntu:
  New

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.97.8, the problem page at 
https://errors.ubuntu.com/problem/d8b64b46f7abc79d13d08d935604a5f7a174e166 
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/.

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

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

[Touch-packages] [Bug 1816415] Re: gjs-console crashed with SIGSEGV in g_socket_receive_message_with_timeout()

[Andrea Azzarone]

We could also wait for glib 2.60.1 to be released (I think we also need
to update gobject-introspection).

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

Title:
  gjs-console crashed with SIGSEGV in
  g_socket_receive_message_with_timeout()

Status in glib2.0 package in Ubuntu:
  In Progress

Bug description:
  https://errors.ubuntu.com/problem/434b8b4abd971c7f84ca824ef5878a00d547753a
  https://gitlab.gnome.org/GNOME/gjs/issues/227

  ---

  I have performance problems, after updating.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gjs 1.54.3-1build1
  Uname: Linux 5.0.0-05rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 18 07:39:11 2019
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2018-12-02 (77 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gjs 
/home/username/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/daemon.js
  SegvAnalysis:
   Segfault happened at: 0x7f224b1fafd8:mov(%r15),%edx
   PC (0x7f224b1fafd8) ok
   source "(%r15)" (0xfff98002) not located in a known VMA region 
(needed readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gjs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_socket_receive_message () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
  Title: gjs-console crashed with SIGSEGV in g_socket_receive_message()
  UpgradeStatus: Upgraded to disco on 2018-12-02 (77 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1817352] Re: Livepatch is not available for this system Ubuntu Disco 19.04

[Andrea Azzarone]

> Edson, apart from the theme and locale, that looks the same as
Andrea’s screenshot of the intended behavior.

All those strings are translatable. Maybe "Livepatch is not available
for this release" is not clear enough?

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

Title:
  Livepatch is not available for this system Ubuntu Disco 19.04

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  Hi guys

  There is an option for livepacth, but there is information that is not
  yet available for Ubuntu Disk 19.04. Will the livepatch be available
  for Ubuntu Disk 19.04?

  "Livepacth is not available for this system"

  See attached

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: software-properties-gtk 0.97.6
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 14:08:04 2019
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-02-11 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16rc1, python-minimal, 2.7.15-4
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1817352] Re: Livepatch is not available for this system Ubuntu Disco 19.04

[Andrea Azzarone]

I'm attaching a screenshot of how it was supposed to be. There is a
small bug in software-properties-gtk that is preventing the error to
appear. I've already proposed a fix for this. Thanks for the report.

** Attachment added: "Screenshot from 2019-02-25 13-01-15.png"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817352/+attachment/5241551/+files/Screenshot%20from%202019-02-25%2013-01-15.png

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

Title:
  Livepatch is not available for this system Ubuntu Disco 19.04

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  Hi guys

  There is an option for livepacth, but there is information that is not
  yet available for Ubuntu Disk 19.04. Will the livepatch be available
  for Ubuntu Disk 19.04?

  "Livepacth is not available for this system"

  See attached

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: software-properties-gtk 0.97.6
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 14:08:04 2019
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-02-11 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16rc1, python-minimal, 2.7.15-4
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1817352] Re: Livepatch is not available for this system Ubuntu Disco 19.04

[Andrea Azzarone]

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

** Changed in: software-properties (Ubuntu)
   Importance: Low => Medium

** Changed in: software-properties (Ubuntu)
   Status: New => In Progress

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

Title:
  Livepatch is not available for this system Ubuntu Disco 19.04

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  Hi guys

  There is an option for livepacth, but there is information that is not
  yet available for Ubuntu Disk 19.04. Will the livepatch be available
  for Ubuntu Disk 19.04?

  "Livepacth is not available for this system"

  See attached

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: software-properties-gtk 0.97.6
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 14:08:04 2019
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-02-11 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16rc1, python-minimal, 2.7.15-4
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1815317] Re: Update gnome-online-accounts to 3.31.90

[Andrea Azzarone]

** Merge proposal linked:
   
https://code.launchpad.net/~azzar1/ubuntu/+source/gnome-online-accounts/+git/gnome-online-accounts/+merge/363144

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

Title:
  Update gnome-online-accounts to 3.31.90

Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  We should update gnome-online-accounts to 3.31.90 (Debian experimental
  has the update).

  GNOME has dropped its .png icons and replaced them with 128px .svg's.
  If we did the same, we could drop our binary patch since an .svg isn't
  a binary file.

  GNOME also includes a 16px symbolic .svg but I don't think those are
  used right now.

  So although getting the 128px .svg from Canonical Design isn't
  technically a blocker, I think it would be nice to get it for
  consistency (and simplifying our patches a bit).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1815317/+subscriptions

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

[Touch-packages] [Bug 1815317] Re: Update gnome-online-accounts to 3.31.90

[Andrea Azzarone]

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => In Progress

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

Title:
  Update gnome-online-accounts to 3.31.90

Status in gnome-online-accounts package in Ubuntu:
  In Progress

Bug description:
  We should update gnome-online-accounts to 3.31.90 (Debian experimental
  has the update).

  GNOME has dropped its .png icons and replaced them with 128px .svg's.
  If we did the same, we could drop our binary patch since an .svg isn't
  a binary file.

  GNOME also includes a 16px symbolic .svg but I don't think those are
  used right now.

  So although getting the 128px .svg from Canonical Design isn't
  technically a blocker, I think it would be nice to get it for
  consistency (and simplifying our patches a bit).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1815317/+subscriptions

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

[Touch-packages] [Bug 1815317] Re: Update gnome-online-accounts to 3.31.90

[Andrea Azzarone]

** Changed in: gnome-online-accounts (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  Update gnome-online-accounts to 3.31.90

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  We should update gnome-online-accounts to 3.31.90 (Debian experimental
  has the update).

  GNOME has dropped its .png icons and replaced them with 128px .svg's.
  If we did the same, we could drop our binary patch since an .svg isn't
  a binary file.

  GNOME also includes a 16px symbolic .svg but I don't think those are
  used right now.

  So although getting the 128px .svg from Canonical Design isn't
  technically a blocker, I think it would be nice to get it for
  consistency (and simplifying our patches a bit).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1815317/+subscriptions

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

[Touch-packages] [Bug 1815227] [NEW] I don't know

[andrea]

Public bug reported:

The computer is very slow

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Feb  8 19:22:14 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Haswell-ULT Integrated Graphics Controller 
[104d:90c3]
InstallationDate: Installed on 2017-11-08 (457 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Sony Corporation SVF14N2J2ES
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=7882e147-2858-4dbd-ad0b-e8eedad25132 ro drm.debug=0xe plymouth:debug
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/22/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R1130DD
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1130DD:bd04/22/2014:svnSonyCorporation:pnSVF14N2J2ES:pvrC10KKKAB:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: SVF14N2
dmi.product.name: SVF14N2J2ES
dmi.product.version: C10KKKAB
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Jan 15 18:04:54 2019
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  I don't know

Status in xorg package in Ubuntu:
  New

Bug description:
  The computer is very slow

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Feb  8 19:22:14 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Haswell-ULT Integrated Graphics Controller 
[104d:90c3]
  InstallationDate: Installed on 2017-11-08 (457 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Sony Corporation SVF14N2J2ES
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=7882e147-2858-4dbd-ad0b-e8eedad25132 ro drm.debug=0xe plymouth:debug
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R1130DD
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1130DD:bd04/22/2014:svnSonyCorporation:pnSVF14N2J2ES:pvrC10KKKAB:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: SVF14N2
  dmi.product.name: SVF14N2J2ES
  

[Touch-packages] [Bug 1812095] Re: console login loop after entering username followed by RETURN

[Andrea]

Ubuntu Mate 18.04.1, same problem with linux-image-4.15.0-44-generic and
linux-image-4.15.0-45-generic


If I switch back to linux-image-4.15.0-43-generic I can succesfully login to 
TTY.

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

Title:
  console login loop after entering username followed by RETURN

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
   login: 
  password:

  Just do nothing. About two seconds later ...

  login:
  password:

  login:
  password:

  login:
  password:

  After this being displayed three times:

  "Too many failure" or so and login is restarting.

  You cant login at all. Only solution: clear the password for the
  account you want to login with.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: login 1:4.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 16 19:34:30 2019
  InstallationDate: Installed on 2011-10-19 (2645 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: shadow
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago)

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

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