date:20220915

** Also affects: ubuntu-settings (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 ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1989807

Title:
  Move raspi cloud-init configuration to ubuntu-settings

Status in Ubuntu Seeds:
  New
Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Jammy:
  New
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to
  disable "real" cloud sources on the raspi images) is hacked into the
  images from livecd-rootfs. It would be preferable to have this in a
  server-specific variant of the ubuntu-raspi-settings package.

  To avoid dpkg conflicts, the file should be differently named
  (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to
  remove the old name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+subscriptions


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

[Touch-packages] [Bug 1989807] Re: Move raspi cloud-init configuration to ubuntu-settings

Apparently rm_conffile is considerably more stubborn than I'd given it
credit for, when it comes to removing files previously unowned by
packages (i.e. /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg). The only
successful method is to rm it in a postinst script unfortunately. The
attached patch remedies this (along with the aforementioned fixes for
LP: #1977764).

** Patch added: "2-1989807.debdiff"
   
https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+attachment/5616205/+files/2-1989807.debdiff

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

Title:
  Move raspi cloud-init configuration to ubuntu-settings

Status in Ubuntu Seeds:
  New
Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to
  disable "real" cloud sources on the raspi images) is hacked into the
  images from livecd-rootfs. It would be preferable to have this in a
  server-specific variant of the ubuntu-raspi-settings package.

  To avoid dpkg conflicts, the file should be differently named
  (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to
  remove the old name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+subscriptions


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

[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say so

** Tags added: foundations-triage-discuss

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

Title:
  When apt keeps back packages due to phased updates, it should say so

Status in apt package in Ubuntu:
  New

Bug description:
  After phased updates have been introduced, it may happen that apt
  upgrade shows packages as upgradable but ends up not upgrading them.
  In this case the packages are indicated as being "kept back".

  Unfortunately, the feedback provided about this to the user is not
  very informative. The user sees the packages being kept back and
  thinks something is going wrong on the system.

  When packages are kept back because of phased updates, apt should say
  so e.g., it should say that the upgrade is delayed.

  Incidentally note that aptitude does not respect phased updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.7
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep  6 10:05:14 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (933 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

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


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

[Touch-packages] [Bug 1989807] Re: Move raspi cloud-init configuration to ubuntu-settings

2022-09-15 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  Move raspi cloud-init configuration to ubuntu-settings

Status in Ubuntu Seeds:
  New
Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to
  disable "real" cloud sources on the raspi images) is hacked into the
  images from livecd-rootfs. It would be preferable to have this in a
  server-specific variant of the ubuntu-raspi-settings package.

  To avoid dpkg conflicts, the file should be differently named
  (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to
  remove the old name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+subscriptions


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

[Touch-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

2022-09-15 Thread Ludovic Rousseau

Seth, pcscd.socket is already enabled. You should not have to run "sudo
systemctl enable pcscd.socket" again.

In your output I see that pcscd is already running.
I would like to get the results of the following commands when you *have* the 
problem and before you try to fix it.

systemctl status pcscd.socket
systemctl status pcscd.service
ls -l /run/pcscd/
journalctl --no-pager --unit=pcscd.socket
journalctl --no-pager --unit=pcscd.service

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

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


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

[Touch-packages] [Bug 1989807] Re: Move raspi cloud-init configuration to ubuntu-settings

Attaching debdiff for ubuntu-settings. This incorporates the diff for
this bug as well as the earlier (and vaguely related) LP: #1977764. In
addition to this, I've extended the merge proposal for the
aforementioned bug to update the necessary seed to include this package
in the Ubuntu Pi server image(s).


** Patch added: "1-1989807.debdiff"
   
https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+attachment/5616189/+files/1-1989807.debdiff

** Tags added: raspi-image

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

Title:
  Move raspi cloud-init configuration to ubuntu-settings

Status in Ubuntu Seeds:
  New
Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to
  disable "real" cloud sources on the raspi images) is hacked into the
  images from livecd-rootfs. It would be preferable to have this in a
  server-specific variant of the ubuntu-raspi-settings package.

  To avoid dpkg conflicts, the file should be differently named
  (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to
  remove the old name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+subscriptions


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

[Touch-packages] [Bug 1989803] Re: Adjust apport for the new Ubuntu debuginfod service

** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/apport/+git/apport/+merge/429986

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

Title:
  Adjust apport for the new Ubuntu debuginfod service

Status in apport package in Ubuntu:
  In Progress

Bug description:
  With the new Ubuntu debuginfod service
  (https://debuginfod.ubuntu.com), and with the prospect of having the
  system automatically fetch debuginfo from the internet without user
  intervention, it is necessary to adjust apport to cope with this
  scenario.

  I had a conversation with bdmurray and he was concerned that having a
  debuginfod-enabled GDB generate the corefiles that are eventually
  submitted to Ubuntu can be a problem.

  My proposed solution is to disable GDB's debuginfod support when
  collecting the corefile.  This should keep things as is and not
  disturb the retrace service.

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


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

[Touch-packages] [Bug 1989807] Re: Move raspi cloud-init configuration to ubuntu-settings

** Also affects: ubuntu-settings (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-seeds
   Importance: Undecided
   Status: New

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

Title:
  Move raspi cloud-init configuration to ubuntu-settings

Status in Ubuntu Seeds:
  New
Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to
  disable "real" cloud sources on the raspi images) is hacked into the
  images from livecd-rootfs. It would be preferable to have this in a
  server-specific variant of the ubuntu-raspi-settings package.

  To avoid dpkg conflicts, the file should be differently named
  (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to
  remove the old name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+subscriptions


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

[Touch-packages] [Bug 1989807] [NEW] Move raspi cloud-init configuration to ubuntu-settings

Public bug reported:

Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to
disable "real" cloud sources on the raspi images) is hacked into the
images from livecd-rootfs. It would be preferable to have this in a
server-specific variant of the ubuntu-raspi-settings package.

To avoid dpkg conflicts, the file should be differently named (99-fake-
cloud.cfg would be sufficient) with a maintscript tweak to remove the
old name.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-settings (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 ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1989807

Title:
  Move raspi cloud-init configuration to ubuntu-settings

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to
  disable "real" cloud sources on the raspi images) is hacked into the
  images from livecd-rootfs. It would be preferable to have this in a
  server-specific variant of the ubuntu-raspi-settings package.

  To avoid dpkg conflicts, the file should be differently named
  (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to
  remove the old name.

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


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

[Touch-packages] [Bug 1989803] [NEW] Adjust apport for the new Ubuntu debuginfod service

2022-09-15 Thread Sergio Durigan Junior

Public bug reported:

With the new Ubuntu debuginfod service (https://debuginfod.ubuntu.com),
and with the prospect of having the system automatically fetch debuginfo
from the internet without user intervention, it is necessary to adjust
apport to cope with this scenario.

I had a conversation with bdmurray and he was concerned that having a
debuginfod-enabled GDB generate the corefiles that are eventually
submitted to Ubuntu can be a problem.

My proposed solution is to disable GDB's debuginfod support when
collecting the corefile.  This should keep things as is and not disturb
the retrace service.

** Affects: apport (Ubuntu)
 Importance: Critical
 Assignee: Sergio Durigan Junior (sergiodj)
 Status: In Progress


** Tags: server-todo

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

Title:
  Adjust apport for the new Ubuntu debuginfod service

Status in apport package in Ubuntu:
  In Progress

Bug description:
  With the new Ubuntu debuginfod service
  (https://debuginfod.ubuntu.com), and with the prospect of having the
  system automatically fetch debuginfo from the internet without user
  intervention, it is necessary to adjust apport to cope with this
  scenario.

  I had a conversation with bdmurray and he was concerned that having a
  debuginfod-enabled GDB generate the corefiles that are eventually
  submitted to Ubuntu can be a problem.

  My proposed solution is to disable GDB's debuginfod support when
  collecting the corefile.  This should keep things as is and not
  disturb the retrace service.

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


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

[Touch-packages] [Bug 1959475] Re: "machinectl shell" connections immediately terminated

** Description changed:

[Impact]

This bug prevents users on Impish and newer from connecting to Focal
systemd containers using `machinectl shell`. This limits users ability
to manage containers spawned with systemd-nspawn.

[Test Plan]

On a Jammy host, do the following:

* Install systemd-container and debootstrap if necessary:

- $ sudo apt install debootstrap systemd-container
+ $ sudo apt install debootstrap systemd-container

* Create a Focal filesystem for the container:

- $ sudo debootstrap --arch= focal /var/lib/containers/lp1959475/
+ $ sudo debootstrap --arch= focal /var/lib/containers/lp1959475/

* Launch the container:

- $ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine
+ $ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine
test-container

* Inside the container, set a password for root and then exit:

- $ passwd # Enter password when prompted
- $ exit
+ $ passwd # Enter password when prompted
+ $ exit

* Re-launch the container with -b option:

- $ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine
+ $ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine
test-container -b

* In a separate terminal window, try to connect to the container:

- $ sudo machinectl shell test-container
+ $ sudo machinectl shell test-container

* Observe the "Connection to machine test-container terminated" error
message.

[Where problems could occur]

- The patch expands the case where the TERM variable is inherited from PID
- 1 when building an execution environment, e.g. for a container. If
- problems were to occur, it would be related to the value of TERM in
- environments forked off of PID 1.
+ The patch changes a path_equal() call to path_equal_ptr() which NULL-
+ checks before calling path_compare(). This avoids an assertion failure
+ in path_compare() and allows the term to be correctly configured in
+ execution environments requiring one. If were regressions were to occur,
+ it would be related to this configuration.

[Other Info]

This bug occurs when trying to connect to a Focal container from e.g. a Jammy
host. For SRU verification, the container
should be Focal, and the host should be Jammy. The -proposed package should
be installed in the Focal container.

[Original Description]

The command "machinectl shell" does not work in systemd 249.9-0ubuntu2:

$ sudo machinectl shell ns-xxx
Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

Connection to machine ns-xxx terminated.

The issue seems to be described here:

https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
https://github.com/systemd/systemd/issues/22234

and solved here:

https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

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

Title:
"machinectl shell" connections immediately terminated

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

Bug description:
[Impact]

This bug prevents users on Impish and newer from connecting to Focal
systemd containers using `machinectl shell`. This limits users ability
to manage containers spawned with systemd-nspawn.

[Test Plan]

On a Jammy host, do the following:

* Install systemd-container and debootstrap if necessary:

$ sudo apt install debootstrap systemd-container

* Create a Focal filesystem for the container:

$ sudo debootstrap --arch= focal
/var/lib/containers/lp1959475/

* Launch the container:

$ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine
test-container

* Inside the container, set a password for root and then exit:

$ passwd # Enter password when prompted
$ exit

* Re-launch the container with -b option:

$ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine
test-container -b

* In a separate terminal window, try to connect to the container:

$ sudo machinectl shell test-container

* Observe the "Connection to machine test-container terminated" error
message.

[Where problems could occur]

The patch changes a path_equal() call to path_equal_ptr() which NULL-
checks before calling path_compare(). This avoids an assertion failure
in path_compare() and allows the term to be correctly configured in
execution environments requiring one. If were regressions were to
occur, it would be related to this configuration.

[Other Info]

[Touch-packages] [Bug 1989733] Re: [FFE] build ubuntu-desktop package for riscv64

This bug was fixed in the package ubuntu-meta - 1.494

---
ubuntu-meta (1.494) kinetic; urgency=medium

  * Provide ubuntu-desktop for riscv64 (LP: #1989733)

 -- Heinrich Schuchardt   Thu, 15 Sep
2022 11:11:32 +0200

** Changed in: ubuntu-meta (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 ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1989733

Title:
  [FFE] build ubuntu-desktop package for riscv64

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Currently the ubuntu-desktop and the ubuntu-desktop-minimal package
  are missing for riscv64. This makes it difficult for users to upgrade
  from a server image to a full desktop.

  Ubuntu-destkop and Ubuntu-desktop-minimal are just meta packages. So
  the only problems that could arise for a user are:

  * the package is not installable if a dependency is missing
  * the numerous dependent packages may exceed the disk space.

  As the riscv64 packages have not existed before and are not included
  in any images there is no regression risk.

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


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

[Touch-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

2022-09-15 Thread Seth Tanner

Ludovic,
Please find the output you requested below.

systemctl status pcscd.socket
● pcscd.socket - PC/SC Smart Card Daemon Activation Socket
 Loaded: loaded (/lib/systemd/system/pcscd.socket; enabled; vendor preset: 
enabled)
 Active: active (running) since Thu 2022-09-15 10:58:12 PDT; 1min 26s ago
   Triggers: ● pcscd.service
 Listen: /run/pcscd/pcscd.comm (Stream)
 CGroup: /system.slice/pcscd.socket

systemctl status pcscd.service
● pcscd.service - PC/SC Smart Card Daemon
 Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor 
preset: enabled)
 Active: active (running) since Thu 2022-09-15 10:58:16 PDT; 1min 31s ago
TriggeredBy: ● pcscd.socket
   Docs: man:pcscd(8)
   Main PID: 2544 (pcscd)
  Tasks: 7 (limit: 38174)
 Memory: 1.5M
CPU: 73ms
 CGroup: /system.slice/pcscd.service
 └─2544 /usr/sbin/pcscd --foreground --auto-exit

Let me provide additional information on the behavior that we are seeing
If we use
sudo systemctl enable pcscd.socket

then we must issue either
sudo systemctl restart pcscd.socket
sudo systemctl stop pcscd.socket; sudo systemctl start pcscd.socket

almost every time we want to use smartcard authentication at gnome login
screen

We have observed this behavior after the following events:
reboot
lock screen (seems to respond better to a stop and start of the socket rather 
than a restart, e.g. we can get multiple locks where we are able to log back 
in, if we stop and start the socket, whereas a restart just lets us get logged 
back in once)
log out

output from /var/log/auth.log
Sep 15 11:29:10 test-jammy gdm-password]: pam_sss(gdm-password:auth): received 
for user test.user: 7 (Authentication failure)
Sep 15 11:29:10 test-jammy gdm-password]: pam_pkcs11(gdm-password:auth): no 
suitable token available
Sep 15 11:29:10 test-jammy gdm-password]: pam_sss(gdm-password:auth): 
authentication failure; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= 
user=test.user
Sep 15 11:29:10 test-jammy gdm-password]: pam_sss(gdm-password:auth): received 
for user test.user: 7 (Authentication failure)
Sep 15 11:29:19 test-jammy gdm-smartcard]: pam_sss(gdm-smartcard:auth): User 
info message: Please insert smart card

Commandline tools on the other hand seem to work as expected once the socket 
has been enabled, no additional socket restarts are needed
opensc-tool --list-readers
pkcs11-tool --list-token-slots
pkcs11_listcerts debug

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

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


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

[Touch-packages] [Bug 1959475] Re: "machinectl shell" connections immediately terminated

Er, I see the problem in my description now. It's been a while since I
looked at this patch. In any case, the patch is still appropriate.

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

Title:
  "machinectl shell" connections immediately terminated

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

Bug description:
  [Impact]

  This bug prevents users on Impish and newer from connecting to Focal
  systemd containers using `machinectl shell`. This limits users ability
  to manage containers spawned with systemd-nspawn.

  [Test Plan]

  On a Jammy host, do the following:

  * Install systemd-container and debootstrap if necessary:

$ sudo apt install debootstrap systemd-container

  * Create a Focal filesystem for the container:

$ sudo debootstrap --arch= focal
  /var/lib/containers/lp1959475/

  * Launch the container:

$ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine
  test-container

  * Inside the container, set a password for root and then exit:

$ passwd # Enter password when prompted
$ exit

  * Re-launch the container with -b option:

$ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine
  test-container -b

  * In a separate terminal window, try to connect to the container:

$ sudo machinectl shell test-container

  * Observe the "Connection to machine test-container terminated" error
  message.

  [Where problems could occur]

  The patch expands the case where the TERM variable is inherited from
  PID 1 when building an execution environment, e.g. for a container. If
  problems were to occur, it would be related to the value of TERM in
  environments forked off of PID 1.

  [Other Info]

  This bug occurs when trying to connect to a Focal container from e.g. a Jammy 
host. For SRU verification, the container
  should be Focal, and the host should be Jammy. The -proposed package should 
be installed in the Focal container.

  [Original Description]

  The command "machinectl shell" does not work in systemd
  249.9-0ubuntu2:

  $ sudo machinectl shell ns-xxx
  Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

  Connection to machine ns-xxx terminated.

  The issue seems to be described here:
  
https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
  https://github.com/systemd/systemd/issues/22234

  and solved here:

  
https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

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


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

[Touch-packages] [Bug 1980494] Re: krb5-multidev is not multi-arch installable due to differences in /usr/bin/krb5-config.mit

2022-09-15 Thread Andreas Hasenack

> @Andreas - you subscribed the Foundations team to his bug report back
in July. What were you looking for from the Foundations team?


I don't know how this should be fixed, and was hoping Foundations could help, 
since it's an issue that is happening because of the introduction of LTO, and 
affects a multiarch package.

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

Title:
  krb5-multidev is not multi-arch installable due to differences in
  /usr/bin/krb5-config.mit

Status in krb5 package in Ubuntu:
  New

Bug description:
  I am trying to build wine in a wow64 configuration and need to install
  the i386 and amd64 version of the krb5-multidev package on Ubuntu
  22.04.  The two version are not co-installable due to differences in
  the /usr/bin/krb5-config.mit file between the two version of the
  package.

  The diff between the two files is:

  --- krb5-config.mit-i386  2022-06-18 21:32:44.034889873 -0400
  +++ krb5-config.mit-amd64 2022-06-18 21:31:37.302149522 -0400
  @@ -40,7 +40,7 @@
   libdir=/usr/lib/${tripple}/mit-krb5
   CC_LINK='$(CC) $(PROG_LIBPATH) $(PROG_RPATH_FLAGS) $(CFLAGS) $(LDFLAGS)'
   KDB5_DB_LIB=
  -LDFLAGS='-Wl,-Bsymbolic-functions -Wl,-z,relro'
  +LDFLAGS='-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto 
-Wl,-z,relro'
   RPATH_FLAG=''
   PROG_RPATH_FLAGS=''
   PTHREAD_CFLAGS='-pthread'

  The krb5-multidev package is co-installable on Debian. It appears that
  Ubuntu uses different default linker flags for the i386 and amd64
  platforms and Debian does not.

  This bug is related to
  https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1970979

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


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

[Touch-packages] [Bug 1959475] Re: "machinectl shell" connections immediately terminated

> Eh? That isn't at all what the patch does...

Before the patch, the `getenv("TERM")` call would not happen; now it
does.

While fixing path_compare() may be a better long-term solution, I think
the existing patch is appropriate for this bug/SRU.

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

Title:
"machinectl shell" connections immediately terminated

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

Bug description:
[Impact]

This bug prevents users on Impish and newer from connecting to Focal
systemd containers using `machinectl shell`. This limits users ability
to manage containers spawned with systemd-nspawn.

[Test Plan]

On a Jammy host, do the following:

* Install systemd-container and debootstrap if necessary:

$ sudo apt install debootstrap systemd-container

* Create a Focal filesystem for the container:

$ sudo debootstrap --arch= focal
/var/lib/containers/lp1959475/

* Launch the container:

$ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine
test-container

* Inside the container, set a password for root and then exit:

$ passwd # Enter password when prompted
$ exit

* Re-launch the container with -b option:

$ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine
test-container -b

* In a separate terminal window, try to connect to the container:

$ sudo machinectl shell test-container

* Observe the "Connection to machine test-container terminated" error
message.

[Where problems could occur]

The patch expands the case where the TERM variable is inherited from
PID 1 when building an execution environment, e.g. for a container. If
problems were to occur, it would be related to the value of TERM in
environments forked off of PID 1.

[Other Info]

[Original Description]

The command "machinectl shell" does not work in systemd
249.9-0ubuntu2:

$ sudo machinectl shell ns-xxx
Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

Connection to machine ns-xxx terminated.

The issue seems to be described here:

https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
https://github.com/systemd/systemd/issues/22234

and solved here:

https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

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

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

[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

** Tags added: foundations-todo

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs
  not found which really annoyed and impact the user experience (system
  not able to boot).

  [Test Plan]

   * detailed instructions how to reproduce the bug:

  1. Any method to grow the initramfs, such as install nvidia-driver.

  2. If developers would like to reproduce, then could dd if=/dev/random
  of=... bs=1M count=500, something like:

  ```
  $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
  #!/bin/sh

  PREREQ=""

  prereqs()
  {
  echo "$PREREQ"
  }

  case $1 in
  # get pre-requisites
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /usr/share/initramfs-tools/hook-functions
  dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
  ```

  And then update-initramfs

   * After applying my patches, the issue is gone.

   * I did also test my test grubx64.efi in:

  1. X86_64 qemu with
  1.1. 60M initramfs + 5.15.0-37-generic kernel
  1.2. 565M initramfs + 5.17.0-1011-oem kernel

  2. Amd64 HP mobile workstation with
  2.1. 65M initramfs + 5.15.0-39-generic kernel
  2.2. 771M initramfs + 5.17.0-1011-oem kernel

  All working well.

  [Where problems could occur]

  * The changes almost in i386/efi, thus the impact will be in the i386 / 
x86_64 EFI system.
  The other change is to modify the “grub-core/kern/efi/mm.c” but I use the 
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
  Thus it should not impact them.

  * There is a “#if defined(__x86_64__)” which intent to limit the >
  32bits code in i386 system and also

  ```
   #if defined (__code_model_large__)
  -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
  +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
   #else
   #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
  +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
   #endif
  ```

  If everything works as expected, then i386 should working good.

  If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
  4GB memory region and never be able to access.

  [Other Info]

   * Upstream grub2 bug #61058
  https://savannah.gnu.org/bugs/index.php?61058

   * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320

   * Test grubx64.efi:
  https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320

   * Test source code: https://github.com/os369510/grub2/tree/lp1842320

   * If you built the package, then test grubx64.efi is under
  “obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
  `/var/cache/pbuilder/build/276481/build/grub2-2.06/obj/monolithic/grub-
  efi-amd64/grubx64.efi`

   * My build

[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)

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

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

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

Title:
  mtd device must be supplied (device name is empty)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  [WORKAROUND]

  This will NOT fix a system that is not booting, because the "mtd
  device must be supplied (device name is empty)" message is not the
  cause of failed boots. This work around is only for those who are
  annoyed by the error message, but are otherwise not experiencing any
  issues.

  If you are not able to boot your system, but you see this error
  message, please open a separate bug with your journalctl and dmesg
  logs.

  # cp /{lib,etc}/systemd/system/systemd-pstore.service
  # sed -i 's/modprobe@mtdpstore.service //' 
/etc/systemd/system/systemd-pstore.service
  # systemctl daemon-reload

  [Impact]

  Due to mtdpstore not being properly configured as a pstore backend,
  when systemd-pstore.service tries to load the module, users get the
  following error in dmesg:

  [   18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
  [   18.462685] mtd device must be supplied (device name is empty)

  This is a distracting error for users trying to diagnose other system
  issues, especially if their system does not boot after a kernel crash
  and this is the only message displayed on the console.

  [Test Plan]

  * Force a kernel crash to populate /sys/fs/pstore, thus causing
  systemd-pstore.service to start on the subsequent boot:

  # echo 1 > /proc/sys/kernel/sysrq
  # echo 1 > /proc/sys/kernel/panic
  # echo c > /proc/sysrq-trigger

  * When the system reboots, observe the error in dmesg:

  # dmesg | grep mtd

  [Where problems could occur]

  If a system was relying on this pstore backend, and mtdpstore is built
  as a module, it is possible for systemd-pstore.service to trigger
  before mtdpstore is loaded, causing systemd-pstore to not copy the
  contents of /sys/fs/pstore. Note however that before the patched
  introduced as a result of bug 1978079, systemd-pstore.service would
  not attempt to load *any* kernel modules.

  [Original Description]

  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

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


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

[Touch-packages] [Bug 1959475] Re: "machinectl shell" connections immediately terminated

2022-09-15 Thread Dan Streetman

> The patch expands the case where the TERM variable is inherited from
PID 1 when building an execution environment, e.g. for a container. If
problems were to occur, it would be related to the value of TERM in
environments forked off of PID 1.

Eh? That isn't at all what the patch does...

Anyway, that patch only incidentally 'fixes' this, by changing the
caller to use path_equals_ptr which null-checks; while a better commit
is 105396778174a39bb04e9a78281ec7601e252d9f which fixes path_compare()
itself (i.e. for all callers).

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

Title:
"machinectl shell" connections immediately terminated

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

Bug description:
[Impact]

This bug prevents users on Impish and newer from connecting to Focal
systemd containers using `machinectl shell`. This limits users ability
to manage containers spawned with systemd-nspawn.

[Test Plan]

On a Jammy host, do the following:

* Install systemd-container and debootstrap if necessary:

$ sudo apt install debootstrap systemd-container

* Create a Focal filesystem for the container:

$ sudo debootstrap --arch= focal
/var/lib/containers/lp1959475/

* Launch the container:

$ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine
test-container

* Inside the container, set a password for root and then exit:

$ passwd # Enter password when prompted
$ exit

* Re-launch the container with -b option:

$ sudo systemd-nspawn -D /var/lib/containers/lp1959475/ --machine
test-container -b

* In a separate terminal window, try to connect to the container:

$ sudo machinectl shell test-container

* Observe the "Connection to machine test-container terminated" error
message.

[Where problems could occur]

[Other Info]

[Original Description]

The command "machinectl shell" does not work in systemd
249.9-0ubuntu2:

$ sudo machinectl shell ns-xxx
Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

Connection to machine ns-xxx terminated.

The issue seems to be described here:

https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
https://github.com/systemd/systemd/issues/22234

and solved here:

https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

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

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

[Touch-packages] [Bug 1989733] Re: [FFE] build ubuntu-desktop package for riscv64

2022-09-15 Thread Jeremy Bicha

I've uploaded and unsubscribed ubuntu-sponsors. Thanks!

** Changed in: ubuntu-meta (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  [FFE] build ubuntu-desktop package for riscv64

Status in ubuntu-meta package in Ubuntu:
  Fix Committed

Bug description:
  Currently the ubuntu-desktop and the ubuntu-desktop-minimal package
  are missing for riscv64. This makes it difficult for users to upgrade
  from a server image to a full desktop.

  Ubuntu-destkop and Ubuntu-desktop-minimal are just meta packages. So
  the only problems that could arise for a user are:

  * the package is not installable if a dependency is missing
  * the numerous dependent packages may exceed the disk space.

  As the riscv64 packages have not existed before and are not included
  in any images there is no regression risk.

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


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

[Touch-packages] [Bug 1701297] Re: NTP reload failure (unable to read library) on overlayfs

2022-09-15 Thread James Falcon

** Changed in: cloud-init (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  NTP reload failure (unable to read library) on overlayfs

Status in cloud-init:
  Won't Fix
Status in apparmor package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  After update [1] of cloud-init in Ubuntu (which landed in xenial-
  updates on 2017-06-27), it is causing NTP reload failures.

  https://launchpad.net/ubuntu/+source/cloud-
  init/0.7.9-153-g16a7302f-0ubuntu1~16.04.1

  In MAAS scenarios, this is causing the machine to fail to deploy.

  Related bugs:
   * bug 1645644: cloud-init ntp not using expected servers

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


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

[Touch-packages] [Bug 1970402] Re: Initrd out of memory error after upgrade to 22.04

2022-09-15 Thread Srinath

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

Workaround: Disable Secure Boot and SGX.

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

Title:
  Initrd out of memory error after upgrade to 22.04

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Jammy:
  Confirmed

Bug description:
  After upgrading to 22.04 system is unbootable because of "out of memory" 
error when loading initial ramdisk. I was able to fix it by editing cat 
/etc/initramfs-tools/initramfs.conf
  and changing configuration to:
  MODULES=dep
  COMPRESS=xz
  RUNSIZE=15%

  Not sure which one helped, but I can test it if needed.

  System information:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  initramfs-tools:
Installed: 0.140ubuntu13
Candidate: 0.140ubuntu13
Version table:
   *** 0.140ubuntu13 500
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  100 /var/lib/dpkg/status

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


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

[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

2022-09-15 Thread vanadium

See the four year old bug mentioned here:
https://github.com/flatpak/xdg-desktop-portal-gtk/issues/137


** Bug watch added: github.com/flatpak/xdg-desktop-portal-gtk/issues #137
   https://github.com/flatpak/xdg-desktop-portal-gtk/issues/137

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

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


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

[Touch-packages] [Bug 1989618] Re: [Feature Request] Include support for LACP bonds in initramfs

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

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

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

Title:
  [Feature Request] Include support for LACP bonds in initramfs

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Feature Request:

  When installing a system over the network using live installer
  (subiquity), you can use the kernel cmdline option ip= [1] to provide
  the network configuration.

  In certain situations, it would be ideal to be able to configure a
  lacp bond during this process. Sometimes the network ports on the
  switch are configured with lacp bond (802.3ad) and the switch won't
  let an interface be brought up unless it sends lacpdus.

  I've discussed this through a subiquity bug [2] and it was mentioned
  that there doesn't seem to be any support in our initramfs for LACP
  bonds [3]. It was requested for a new bug to be filed at the
  initramfs-tools project for such functionality to get included.

  I don't have any use case at the moment, but I've received this
  request in the past when the customer was still using debian
  installer. For debian-installer this was once discussed via a debian
  bug [4] and a patch was proposed [5], but this was never accepted /
  merged.

  Considering that Tte new installer is an _entirely_ different codebase
  than d-i, the lacp support would have to come from the initramfs.

  
  [1] 
ip=:
  [2] https://bugs.launchpad.net/subiquity/+bug/1988480
  [3] https://bugs.launchpad.net/subiquity/+bug/1988480/comments/17
  [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611250
  [5] 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=611250;filename=bonding_v2.patch;msg=39

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


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

[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

2022-09-15 Thread Hannu E K N

Current status:
$ grep hda /etc/modprobe.d/blacklist.conf 
blacklist snd_hda_codec_realtek


Seems to stop the problems.

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 1989365] Re: test_omit_all_processes_except_one is racy and fails sometimes

This bug was fixed in the package apport - 2.23.0-0ubuntu2

---
apport (2.23.0-0ubuntu2) kinetic; urgency=medium

  * tests: Wait for test process to be started (LP: #1989365)
  * tests: Fix psutil.NoSuchProcess in wait_for_gdb_child_process
(LP: #1989371)

 -- Benjamin Drung   Thu, 15 Sep 2022 14:04:42 +0200

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

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

Title:
  test_omit_all_processes_except_one is racy and fails sometimes

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  The test case test_omit_all_processes_except_one is racy and fails
  sometimes:

  ```
  test_omit_all_processes_except_one 
(tests.system.test_unkillable_shutdown.TestUnkillableShutdown)
  unkillable_shutdown will write exactly one report. ... Running as unit: 
run-r0b0d3fe87473410c9eb61a5ae4635938.service
  FAIL
  ==
  FAIL: test_omit_all_processes_except_one 
(tests.system.test_unkillable_shutdown.TestUnkillableShutdown)
  unkillable_shutdown will write exactly one report.
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.JJoBfX/autopkgtest_tmp/tests/system/test_unkillable_shutdown.py",
 line 96, in test_omit_all_processes_except_one
  pid = self._launch_process_with_different_session_id(existing_pids)
File 
"/tmp/autopkgtest.JJoBfX/autopkgtest_tmp/tests/system/test_unkillable_shutdown.py",
 line 90, in _launch_process_with_different_session_id
  self.assertEqual(len(test_executable_pids), 1, test_executable_pids)
  AssertionError: 0 != 1 : set()

  --
  ```

  autopkgtest log: https://autopkgtest.ubuntu.com/results/autopkgtest-
  kinetic/kinetic/amd64/a/apport/20220912_055849_5f03e@/log.gz

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


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

[Touch-packages] [Bug 1989371] Re: test_crash_setuid_unpackaged fails with psutil.NoSuchProcess: process no longer exists

This bug was fixed in the package apport - 2.23.0-0ubuntu2

---
apport (2.23.0-0ubuntu2) kinetic; urgency=medium

  * tests: Wait for test process to be started (LP: #1989365)
  * tests: Fix psutil.NoSuchProcess in wait_for_gdb_child_process
(LP: #1989371)

 -- Benjamin Drung   Thu, 15 Sep 2022 14:04:42 +0200

** Changed in: apport (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  test_crash_setuid_unpackaged fails with psutil.NoSuchProcess: process
  no longer exists

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  test_crash_setuid_unpackaged is racy and rarely fails with:

  ==
  ERROR: test_crash_setuid_unpackaged (tests.integration.test_signal_crashes.T)
  report generation for unpackaged setuid program
  --
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/psutil/_pslinux.py", line 1661, in 
wrapper
  return fun(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/psutil/_pslinux.py", line 1782, in 
cmdline
  data = f.read()
  ProcessLookupError: [Errno 3] No such process

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File 
"/tmp/autopkgtest.ukiC2X/autopkgtest_tmp/tests/integration/test_signal_crashes.py",
 line 746, in test_crash_setuid_unpackaged
  self.do_crash(
File 
"/tmp/autopkgtest.ukiC2X/autopkgtest_tmp/tests/integration/test_signal_crashes.py",
 line 918, in do_crash
  command_process = self.wait_for_gdb_child_process(
File 
"/tmp/autopkgtest.ukiC2X/autopkgtest_tmp/tests/integration/test_signal_crashes.py",
 line 1088, in wait_for_gdb_child_process
  cmdline = process.cmdline()
File "/usr/lib/python3/dist-packages/psutil/__init__.py", line 684, in 
cmdline
  return self._proc.cmdline()
File "/usr/lib/python3/dist-packages/psutil/_pslinux.py", line 1665, in 
wrapper
  raise NoSuchProcess(self.pid, self._name)
  psutil.NoSuchProcess: process no longer exists (pid=3767)

  --

  Failing autopkgtest:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  kinetic/kinetic/arm64/a/apport/20220825_140850_23979@/log.gz

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


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

[Touch-packages] [Bug 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)

2022-09-15 Thread William Wilson

** Tags removed: foundations-triage-discuss

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_settings_get_screen(settings=0x0)

Status in apport package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in apport source package in Focal:
  Triaged
Status in gtk+3.0 source package in Focal:
  Confirmed

Bug description:
  Steps to reproduce
  --

  1. Use GNOME with GNOME shell
  2. killall -11 gnome-shell

  Suspicious Apport log:

  gdbus call error: Error:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  Error tracker
  -
  https://errors.ubuntu.com/problem/815a179408135a894bbb5921adef3757563c75c5
  https://errors.ubuntu.com/problem/276759c7bf0b6628977c63ca70d26b53c9defd22

  Original report
  ---
  Session suddenly stopped and came back to login screen, all opened windows 
lost.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: apport-gtk 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:7292709:2019-09-03 16:20:13.909392833 +0200:2019-09-03 
16:20:14.909392833 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:1000:117:48937942:2019-09-03 16:20:11.681426286 +0200:2019-09-03 
16:20:12.681426286 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:117:32054:2019-08-27 17:39:07.125607490 +0200:2019-08-28 
12:36:17.087672961 +0200:/var/crash/_usr_bin_dbus-daemon.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  3 16:20:13 2019
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-16 (443 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  SegvAnalysis:
   Segfault happened at: 0x7f532548f8c4:mov0x18(%rdi),%rax
   PC (0x7f532548f8c4) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-06-10 (84 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/apport/+bug/1842439/+subscriptions


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

[Touch-packages] [Bug 1980494] Re: krb5-multidev is not multi-arch installable due to differences in /usr/bin/krb5-config.mit

@Andreas - you subscribed the Foundations team to his bug report back in
July. What were you looking for from the Foundations team?

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

Title:
  krb5-multidev is not multi-arch installable due to differences in
  /usr/bin/krb5-config.mit

Status in krb5 package in Ubuntu:
  New

Bug description:
  I am trying to build wine in a wow64 configuration and need to install
  the i386 and amd64 version of the krb5-multidev package on Ubuntu
  22.04.  The two version are not co-installable due to differences in
  the /usr/bin/krb5-config.mit file between the two version of the
  package.

  The diff between the two files is:

  --- krb5-config.mit-i386  2022-06-18 21:32:44.034889873 -0400
  +++ krb5-config.mit-amd64 2022-06-18 21:31:37.302149522 -0400
  @@ -40,7 +40,7 @@
   libdir=/usr/lib/${tripple}/mit-krb5
   CC_LINK='$(CC) $(PROG_LIBPATH) $(PROG_RPATH_FLAGS) $(CFLAGS) $(LDFLAGS)'
   KDB5_DB_LIB=
  -LDFLAGS='-Wl,-Bsymbolic-functions -Wl,-z,relro'
  +LDFLAGS='-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto 
-Wl,-z,relro'
   RPATH_FLAG=''
   PROG_RPATH_FLAGS=''
   PTHREAD_CFLAGS='-pthread'

  The krb5-multidev package is co-installable on Debian. It appears that
  Ubuntu uses different default linker flags for the i386 and amd64
  platforms and Debian does not.

  This bug is related to
  https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1970979

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


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

[Touch-packages] [Bug 1981385] Re: initrd lacks modules to mount boot image from http boot

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

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

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

Title:
  initrd lacks modules to mount boot image from http boot

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Jammy:
  Triaged

Bug description:
  If you use UEFI http boot to boot an image (rather than an EFI
  executable) and get all the way to a normal userspace, you can access
  the boot image as /dev/pmem0. But this is not accessible in the
  initrd; presumably some modules are missing. Dimitri added some
  modules that are clearly going to be necessary (kernel/drivers/nvdimm)
  in 0.140ubuntu14 and I added kernel/drivers/dax too in local
  experiments but this appears not to be enough to get it to appear.

  This is desirable because then you can just feed an installer ISO to a
  machine via http boot and the installer just works as normal (the
  speed and, uh, quality, of the implementation of HTTP in a given
  machine's firmware may mean this isn't always the best option but it
  would be nice if it worked in case someone's machine actually does
  this well).

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


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

[Touch-packages] [Bug 1981385] Re: initrd lacks modules to mount boot image from http boot

2022-09-15 Thread Benjamin Drung

** Also affects: initramfs-tools (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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1981385

Title:
  initrd lacks modules to mount boot image from http boot

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Jammy:
  Triaged

Bug description:
  If you use UEFI http boot to boot an image (rather than an EFI
  executable) and get all the way to a normal userspace, you can access
  the boot image as /dev/pmem0. But this is not accessible in the
  initrd; presumably some modules are missing. Dimitri added some
  modules that are clearly going to be necessary (kernel/drivers/nvdimm)
  in 0.140ubuntu14 and I added kernel/drivers/dax too in local
  experiments but this appears not to be enough to get it to appear.

  This is desirable because then you can just feed an installer ISO to a
  machine via http boot and the installer just works as normal (the
  speed and, uh, quality, of the implementation of HTTP in a given
  machine's firmware may mean this isn't always the best option but it
  would be nice if it worked in case someone's machine actually does
  this well).

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


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

[Touch-packages] [Bug 1981385] Re: initrd lacks modules to mount boot image from http boot

** Tags removed: foundations-triage-discuss
** Tags added: foundations-todo

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

Title:
  initrd lacks modules to mount boot image from http boot

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Jammy:
  Triaged

Bug description:
  If you use UEFI http boot to boot an image (rather than an EFI
  executable) and get all the way to a normal userspace, you can access
  the boot image as /dev/pmem0. But this is not accessible in the
  initrd; presumably some modules are missing. Dimitri added some
  modules that are clearly going to be necessary (kernel/drivers/nvdimm)
  in 0.140ubuntu14 and I added kernel/drivers/dax too in local
  experiments but this appears not to be enough to get it to appear.

  This is desirable because then you can just feed an installer ISO to a
  machine via http boot and the installer just works as normal (the
  speed and, uh, quality, of the implementation of HTTP in a given
  machine's firmware may mean this isn't always the best option but it
  would be nice if it worked in case someone's machine actually does
  this well).

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


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

[Touch-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual

2022-09-15 Thread Ludovic Rousseau

Seth, what is the output of the command: systemctl status pcscd.socket

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

Title:
  pcscd 1.9.5-3 do not start automatically, only manual

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Mate 22.04 with the latest updates.
  Problem is present with internal smart-card reader and also external usb 
smart-card reader.

  eid-viewer sees no card reader,but When i do:

  sudo pcscd -f

  it is working, also following the tips of Ludovic:
  
https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html

  sudo systemctl stop pcscd.socket
  sudo systemctl start pcscd.socket

  It is working until next restart.

  libacsccid1  version: 1.1.8-1
  libccid version: 1.5.0-2
  pcscd version: 1.9.5-3
  eid-archive version: 2022.3
  eid-mw version: 5.0.28v5.0.28-0u2204-1
  eid-viewer version: 5.0.28v5.0.28-0u2204-1

  In Firefox, my eid card is then also recognized, but only in the ESR
  version, but this is a know Mozilla bug.

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


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

[Touch-packages] [Bug 1989733] Re: [FFE] build ubuntu-desktop package for riscv64

2022-09-15 Thread Łukasz Zemczak

Tricky. It's a bit sad that we're doing this now, as this might
potentially spawn some bug reports from RISC-V users that will now try
to install ubuntu-desktop and run into problems. That being said, I
suppose the userbase is still small and I know Heinrich is actively
looking into this right now. In this case, let's proceed! Will still
need a sponsor (not sure if I'll be able to get to it today).

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

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

Title:
  [FFE] build ubuntu-desktop package for riscv64

Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  Currently the ubuntu-desktop and the ubuntu-desktop-minimal package
  are missing for riscv64. This makes it difficult for users to upgrade
  from a server image to a full desktop.

  Ubuntu-destkop and Ubuntu-desktop-minimal are just meta packages. So
  the only problems that could arise for a user are:

  * the package is not installable if a dependency is missing
  * the numerous dependent packages may exceed the disk space.

  As the riscv64 packages have not existed before and are not included
  in any images there is no regression risk.

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


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

[Touch-packages] [Bug 1989733] Re: [FFE] build ubuntu-desktop package for riscv64

2022-09-15 Thread Jeremy Bicha

The Ubuntu Desktop Team is ok with this change.

We'll continue to only produce Ubuntu Desktop ISOs for just amd64 and
arm64 and those are the only architectures we officially support for
desktop use cases. But we don't have a problem with making the
metapackages available on other architectures.

Thank you for proposing this!

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

Title:
  [FFE] build ubuntu-desktop package for riscv64

Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  Currently the ubuntu-desktop and the ubuntu-desktop-minimal package
  are missing for riscv64. This makes it difficult for users to upgrade
  from a server image to a full desktop.

  Ubuntu-destkop and Ubuntu-desktop-minimal are just meta packages. So
  the only problems that could arise for a user are:

  * the package is not installable if a dependency is missing
  * the numerous dependent packages may exceed the disk space.

  As the riscv64 packages have not existed before and are not included
  in any images there is no regression risk.

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


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

[Touch-packages] [Bug 1989733] Re: [FFE] build ubuntu-desktop package for riscv64

2022-09-15 Thread Heinrich Schuchardt

** Patch added: "ubuntu-meta-1.493..1.494.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1989733/+attachment/5616101/+files/ubuntu-meta-1.493..1.494.debdiff

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

Title:
  [FFE] build ubuntu-desktop package for riscv64

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Currently the ubuntu-desktop and the ubuntu-desktop-minimal package
  are missing for riscv64. This makes it difficult for users to upgrade
  from a server image to a full desktop.

  Ubuntu-destkop and Ubuntu-desktop-minimal are just meta packages. So
  the only problems that could arise for a user are:

  * the package is not installable if a dependency is missing
  * the numerous dependent packages may exceed the disk space.

  As the riscv64 packages have not existed before and are not included
  in any images there is no regression risk.

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


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

[Touch-packages] [Bug 1989733] [NEW] [FFE] build ubuntu-desktop package for riscv64

2022-09-15 Thread Heinrich Schuchardt

Public bug reported:

Currently the ubuntu-desktop and the ubuntu-desktop-minimal package are
missing for riscv64. This makes it difficult for users to upgrade from a
server image to a full desktop.

Ubuntu-destkop and Ubuntu-desktop-minimal are just meta packages. So the
only problems that could arise for a user are:

* the package is not installable if a dependency is missing
* the numerous dependent packages may exceed the disk space.

As the riscv64 packages have not existed before and are not included in
any images there is no regression risk.

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [FFE] build ubuntu-desktop package for riscv64

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Currently the ubuntu-desktop and the ubuntu-desktop-minimal package
  are missing for riscv64. This makes it difficult for users to upgrade
  from a server image to a full desktop.

  Ubuntu-destkop and Ubuntu-desktop-minimal are just meta packages. So
  the only problems that could arise for a user are:

  * the package is not installable if a dependency is missing
  * the numerous dependent packages may exceed the disk space.

  As the riscv64 packages have not existed before and are not included
  in any images there is no regression risk.

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


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

[Touch-packages] [Bug 1989731] [NEW] Non-root user unable to change own password if pam_pwhistory is used

2022-09-15 Thread Alejandro Santoyo Gonzalez

Public bug reported:

When pam_pwhistory is in use non-root users are unable to change their
passwords. In fact, they are able to change it but the system spits out
an error even though the password was indeed changed.

Reproducer:
---

1. created an Ubuntu/Focal VM
2. added a user 'test'

sudo adduser test # used passwd '123'
su test

3. changed the password using 'passwd' logged in as the user 'test'

passwd test # used passwd '1qaz2wsx'

4. logged out from 'test' and executed

echo 'password required pam_pwhistory.so remember=5' | sudo tee -a
/etc/pam.d/common-password

5. tried again to follow step 3 as user 'test' but the following
happens:

passwd test # used passwd '3edc4rfv' (1)
Changing password for test.
Current password:
New password:
Retype new password:
Password has been already used. Choose another.
passwd: Have exhausted maximum number of retries for service
passwd: password unchanged

However, I'm now able to log in as 'test' using the password in
(1) (the one that was supposedly not set up due to having been
already used) instead of the old one (the one that should be in
place since the change process returned an error).

6. if I comment out 'password required pam_pwhistory.so remember=5'
then I can log in as 'test' and change the password without issues

This behavior has been verified with the below package versioning:

ii  libpam-cap:amd641:2.32-1  amd64 
   POSIX 1003.1e capabilities (PAM module)
ii  libpam-modules:amd641.3.1-5ubuntu4.3  amd64 
   Pluggable Authentication Modules for PAM
ii  libpam-modules-bin  1.3.1-5ubuntu4.3  amd64 
   Pluggable Authentication Modules for PAM - helper binaries
ii  libpam-runtime  1.3.1-5ubuntu4.3  all   
   Runtime support for the PAM library
ii  libpam-systemd:amd64245.4-4ubuntu3.15 amd64 
   system and service manager - PAM module
ii  libpam0g:amd64  1.3.1-5ubuntu4.3  amd64 
   Pluggable Authentication Modules library

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

** Package changed: ubuntu => pam (Ubuntu)

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

Title:
  Non-root user unable to change own password if pam_pwhistory is used

Status in pam package in Ubuntu:
  New

Bug description:
  When pam_pwhistory is in use non-root users are unable to change their
  passwords. In fact, they are able to change it but the system spits
  out an error even though the password was indeed changed.

  Reproducer:
  ---

  1. created an Ubuntu/Focal VM
  2. added a user 'test'

  sudo adduser test # used passwd '123'
  su test

  3. changed the password using 'passwd' logged in as the user 'test'

  passwd test # used passwd '1qaz2wsx'

  4. logged out from 'test' and executed

  echo 'password required pam_pwhistory.so remember=5' | sudo tee -a
  /etc/pam.d/common-password

  5. tried again to follow step 3 as user 'test' but the following
  happens:

  passwd test # used passwd '3edc4rfv' (1)
  Changing password for test.
  Current password:
  New password:
  Retype new password:
  Password has been already used. Choose another.
  passwd: Have exhausted maximum number of retries for service
  passwd: password unchanged

  However, I'm now able to log in as 'test' using the password in
  (1) (the one that was supposedly not set up due to having been
  already used) instead of the old one (the one that should be in
  place since the change process returned an error).

  6. if I comment out 'password required pam_pwhistory.so remember=5'
  then I can log in as 'test' and change the password without issues

  This behavior has been verified with the below package versioning:

  ii  libpam-cap:amd641:2.32-1  
amd64POSIX 1003.1e capabilities (PAM module)
  ii  libpam-modules:amd641.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules for PAM
  ii  libpam-modules-bin  1.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules for PAM - helper binaries
  ii  libpam-runtime  1.3.1-5ubuntu4.3  all 
 Runtime support for the PAM library
  ii  libpam-systemd:amd64245.4-4ubuntu3.15 
amd64system and service manager - PAM module
  ii  libpam0g:amd64  1.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules library

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


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

[Touch-packages] [Bug 1989731] [NEW] Non-root user unable to change own password if pam_pwhistory is used