[Touch-packages] [Bug 2026235] Re: Merge a5e6c8498ca, corrupted resolfconf results in inability to talk to link local DNS servers

2023-07-06 Thread gutschke
** Information type changed from Private Security to Public Security

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

Title:
  Merge a5e6c8498ca, corrupted resolfconf results in inability to talk
  to link local DNS servers

Status in systemd package in Ubuntu:
  New

Bug description:
  Package: systemd 249.11-0ubuntu3.9 
https://packages.ubuntu.com/jammy/systemd
  Description: Ubuntu 22.04.2 LTS
  Release: 22.04

  Please merge https://github.com/systemd/systemd/commit/a5e6c8498ca for
  the Ubuntu LTS release. It's a one-line fix that sets an uninitialized
  variable to zero.

  Until this fix is implemented, resolveconf generates incorrect DNS
  configuration for link-local IPv6 addresses discovered from Router
  Advertisements (RA). It retrieves the correct address, but then
  appends a random interface index. So, instead of fe80:::, the
  DNS server reads fe80:::%NNN This results in the client no
  longer being able to reach the locally configured DNS server.

  This bug can be reproduced by installing a DNS server and radvd
  (Router Advertisement demon) in an LXC container that shares a network
  bridge with another container running Ubuntu Jammy. If Jammy is
  configured to accept RDNSS information from RA, it will set the wrong
  server address.

  I believe this only works if radvd advertises a link-local addresses
  as part of the RDNSS information. If instead, it advertises a globally
  routable address (e.g. 2001:::) there is no issue.

  While uninitialized memory is always scary, I don't believe this is
  worse than maybe a denial-of-service attack? So, not quite sure
  whether this is an exploitable security issue. But that probably
  depends on exactly how the network topology looks like and whether an
  attacker can gain (limited) control over manipulating RA packets. It
  is possible that some clusters and/or containers would suffer security
  issues because of this problem.

  Also, this is technically a way to leak memory from within a systemd-
  related process. But I don't see an obvious way how to exploit this
  very limited data leak.

  Out of an abundance of precaution, I am marking this as a security
  issue. Please feel free to unflag, if you think that assessment isn't
  warranted.

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


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


[Touch-packages] [Bug 2026307] Re: ssh-askpass-gnome pops up for every sudo command

2023-07-06 Thread john doe
btw, if i sit there and click "allow" and enter the sudo password for
every sudo command my app envokes, it will eventually process all of
them. So, it's like the preference for the "inhibit shortcuts" dialog is
not being saved, and the sudo auth is not being saved for the 15 min or
whatever it's set for. I find it odd that both of these things would
fail, but maybe one is interfering with the other.

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

Title:
  ssh-askpass-gnome pops up for every sudo command

Status in openssh package in Ubuntu:
  New

Bug description:
  When running multiple commands like this:
   
  SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup 
/usr/local/bin/ 

  from my gtk4 app, the ssh-askpass-gnome dialog and the gnome
  inhibitShortcutsDialog pops up. i click allow on the
  inhibitShortcutsDialog, then enter my password, which is accepted,
  then they both pop up again for each of these sudo commands my app
  calls.

  This happens in ubuntu 22.04-23.04 (completely updated) using gnome.
  If i use xfce in the same ubuntu versions, the gnome dialog doesn't
  pop up, of course, and ssh-askpass-gnome works properly (one entry and
  then all commands executed without further prompting). Fedora 37 works
  properly with gnome x11 or wayland, and xfce. Not sure if this is a
  bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both/something
  else.

  ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome
  1:9.0p1-1ubuntu8.2

  fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6

  thanks

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


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


[Touch-packages] [Bug 2026307] Re: ssh-askpass-gnome pops up for every sudo command

2023-07-06 Thread john doe
** Description changed:

  When running multiple commands like this:
- SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup
- /usr/local/bin/ from my gtk4 app the ssh-askpass-gnome dialog and the
- gnome inhibitShortcutsDialog pops up, i click allow on the
- inhibitShortcutsDialog, then enter my password which is accepted, then
+  
+ SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup 
/usr/local/bin/ 
+ 
+ from my gtk4 app, the ssh-askpass-gnome dialog and the gnome
+ inhibitShortcutsDialog pops up. i click allow on the
+ inhibitShortcutsDialog, then enter my password, which is accepted, then
  they both pop up again for each of these sudo commands my app calls.
  
  This happens in ubuntu 22.04-23.04 (completely updated) using gnome. If
- i use xfce in same ubuntu versions, the gnome dialog doesn't pop up, of
- course, and ssh-askpass-gnome works properly (one entry and then all
- commands executed without further prompting). fedora 37 works properly
+ i use xfce in the same ubuntu versions, the gnome dialog doesn't pop up,
+ of course, and ssh-askpass-gnome works properly (one entry and then all
+ commands executed without further prompting). Fedora 37 works properly
  with gnome x11 or wayland, and xfce. Not sure if this is a bug in
- ubuntu's ssh-askpass-gnome, gnome-shell, or both.
+ ubuntu's ssh-askpass-gnome, gnome-shell, or both/something else.
  
  ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome
  1:9.0p1-1ubuntu8.2
  
  fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6
  
  thanks

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

Title:
  ssh-askpass-gnome pops up for every sudo command

Status in openssh package in Ubuntu:
  New

Bug description:
  When running multiple commands like this:
   
  SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup 
/usr/local/bin/ 

  from my gtk4 app, the ssh-askpass-gnome dialog and the gnome
  inhibitShortcutsDialog pops up. i click allow on the
  inhibitShortcutsDialog, then enter my password, which is accepted,
  then they both pop up again for each of these sudo commands my app
  calls.

  This happens in ubuntu 22.04-23.04 (completely updated) using gnome.
  If i use xfce in the same ubuntu versions, the gnome dialog doesn't
  pop up, of course, and ssh-askpass-gnome works properly (one entry and
  then all commands executed without further prompting). Fedora 37 works
  properly with gnome x11 or wayland, and xfce. Not sure if this is a
  bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both/something
  else.

  ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome
  1:9.0p1-1ubuntu8.2

  fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6

  thanks

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


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


[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2023-07-06 Thread Georgia Garcia
Andreas, Jeremy, you are correct. The worst that could happen is the
same behavior we have currently: when we click a URL the browser does
not open, we get a denied log and evince prints "Permission denied".

My previous statement that profile loading could fail if apparmor did
not find "snap_browsers" was a mistake. Evince installs successfully and
apparmor loads the evince policy correctly. The apparmor service also
does not fail if restarted.

I updated the evince package for jammy removing the "Recommends" in the ppa I 
shared previously if needed:
https://launchpad.net/~georgiag/+archive/ubuntu/lp1794064/+packages

Thank you all and I'm sorry for the confusion.

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Committed
Status in apparmor package in Debian:
  New
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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


[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

2023-07-06 Thread Andreas Hasenack
Hello wieczyk, or anyone else affected,

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

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

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

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

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

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

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

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in dput package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in dput source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in dput source package in Focal:
  Fix Committed
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  Fix Committed
Status in dput source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in dput source package in Kinetic:
  Fix Committed
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New
Status in dput source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    

[Touch-packages] [Bug 1943037] Re: Automounts do not reset properly after TimeoutIdleSec automatic unmounts

2023-07-06 Thread Nick Rosbrook
This wording sounds basically exactly like
https://github.com/systemd/systemd/issues/3332, which is quite older
than Focal. I also cannot reproduce this on Focal.

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

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

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

Title:
  Automounts do not reset properly after TimeoutIdleSec automatic
  unmounts

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Ubuntu version: Ubuntu 20.04.3 LTS
  systemd version: 245.4-4ubuntu3.11

  Expected behavior:

  Automount units whose associated mount units have been auto-unmounted
  with TimeoutIdleSec will trigger the associated mount unit when the
  automount path is accessed again

  Current behavior:

  Automount units whose associated mount units have been auto-unmounted
  with TimeoutIdleSec do not trigger the associated mount unit when the
  automount path is accessed again until the automount unit is
  completely restarted.

  Steps to reproduce the problem

  1. Trigger any automount unit with TimeoutIdleSec= set
  2- Wait for the idle time to occur and systemd to unmount the associated 
mount unit
  3. Then try to access the automount location again.

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


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


[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info

2023-07-06 Thread Chad Smith
SRU validation Focal, Jammy, Kinetic and Lunar successes.

** Attachment added: "sru-1724623.log"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1724623/+attachment/5684389/+files/sru-1724623.log

** Tags removed: block-proposed-focal regression-proposed verification-needed 
verification-needed-focal verification-needed-jammy verification-needed-kinetic
** Tags added: verification-done verification-done-focal 
verification-done-jammy verification-done-kinetic

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

Title:
  Update ubuntu cloud info

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Focal:
  Fix Committed
Status in cloud-init source package in Jammy:
  Fix Committed
Status in cloud-init source package in Kinetic:
  Fix Committed
Status in apport source package in Lunar:
  New
Status in cloud-init source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]
  Apport reported bug add invalid bug tags such as `uec-images` which no longer 
has meaning or `ec2-images` on openstack. Since cloud-init is installed in all 
these images and detects the correct datasource, leverage cloud-init's 
instance-data.json or cloud-id

  [ Test Plan ]

  1. Launch LXD container for each series
  2. upgrade to cloud-init from -proposed.
  3. Execute apport-bug cloud-init and view report to assess that correct tags 
are present for LXD datasource.
  4. replace /run/cloud-init/instance-data.json cloud-id content with examples 
from openstack, ec2, configdrive and assert appropriate tags match the platform 
details.

  verification scriptlet (attached):

  #!/bin/bash
  set -ex

  cat > setup_proposed.sh  openstack.json  ec2.json << EOF
  {
    "ds": {
  "imageId": "ami-123",
  "instanceType": "m1.tiny",
  "region": "us-east-1"
    },
    "v1": {
  "cloud_name": "aws",
  "distro": "ubuntu",
  "distro_release": "jammy",
  "distro_version": "22.04",
  "instance_id": "i-06b5687b4d7b8595d",
  "machine": "x86_64",
  "platform": "ec2",
  "python_version": "3.10.4",
  "region": "us-east-2",
  "variant": "ubuntu"
    }
  }
  EOF

  for release in focal jammy kinetic lunar; do
   VM=sru-$release
   lxc launch ubuntu-daily:$release $VM
   while ! lxc exec $VM -- cloud-init status --wait --long; do
  sleep 5
   done
   echo --- 1. Generate current apport report, selecting Openstack as cloud.
   echo --- step through prompts and select 'K' to keep report
   echo --- VERSION OF APPORT ---
   lxc exec $VM -- apport-bug --version
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.orig
   lxc exec $VM rm /tmp/$APPORT_FILE

   lxc file push setup_proposed.sh $VM/
   lxc exec $VM -- bash /setup_proposed.sh | grep cloud-init

   lxc file push openstack.json $VM/run/cloud-init/instance-data.json
   echo --- 2. Generate -proposed apport report which sources openstack 
instance-data.json, selecting Openstack as cloud.
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.openstack-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   echo --- 3. Generate -proposed apport report which sources ec2 
instance-data, selecting Ec2 as cloud.
   lxc file push ec2.json $VM/run/cloud-init/instance-data.json
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.ec2-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   # redact logs lines for easy diffs
   for file in `ls apport*`; do
   sed -i '1,/logs.tgz/!d' $file
   done
   echo --- 4. Inspect diff tags of orig to openstack-proposed report
   diff -urN apport-$VM.orig apport-$VM.openstack-proposed || true
   echo --- 5. Inspect diff tags of openstack-proposed to ec2-proposed report
   diff -urN apport-$VM.openstack-proposed apport-$VM.ec2-proposed || true

  done

  [ Where problems could occur ]
  apport-bug could traceback on poor logic preventing simple bug filing at 
apport CLI. It could omit tags if unable to process 
cloud-init/instance-data.json. nothing critical to daily performance, uptime or 
security

  [ Other Info ]

  [Original description]

  Issues:
   - Using the presence of cloud-init to flag an image as a cloud image is 
incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images)
   - Using the presence of EC2 metadata source 

[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info

2023-07-06 Thread Chad Smith
SRU validation Focal, Jammy, Kinetic and Lunar successes.

** Attachment added: "sru-1724623.log"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1724623/+attachment/5684388/+files/sru-1724623.log

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

Title:
  Update ubuntu cloud info

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Focal:
  Fix Committed
Status in cloud-init source package in Jammy:
  Fix Committed
Status in cloud-init source package in Kinetic:
  Fix Committed
Status in apport source package in Lunar:
  New
Status in cloud-init source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]
  Apport reported bug add invalid bug tags such as `uec-images` which no longer 
has meaning or `ec2-images` on openstack. Since cloud-init is installed in all 
these images and detects the correct datasource, leverage cloud-init's 
instance-data.json or cloud-id

  [ Test Plan ]

  1. Launch LXD container for each series
  2. upgrade to cloud-init from -proposed.
  3. Execute apport-bug cloud-init and view report to assess that correct tags 
are present for LXD datasource.
  4. replace /run/cloud-init/instance-data.json cloud-id content with examples 
from openstack, ec2, configdrive and assert appropriate tags match the platform 
details.

  verification scriptlet (attached):

  #!/bin/bash
  set -ex

  cat > setup_proposed.sh  openstack.json  ec2.json << EOF
  {
    "ds": {
  "imageId": "ami-123",
  "instanceType": "m1.tiny",
  "region": "us-east-1"
    },
    "v1": {
  "cloud_name": "aws",
  "distro": "ubuntu",
  "distro_release": "jammy",
  "distro_version": "22.04",
  "instance_id": "i-06b5687b4d7b8595d",
  "machine": "x86_64",
  "platform": "ec2",
  "python_version": "3.10.4",
  "region": "us-east-2",
  "variant": "ubuntu"
    }
  }
  EOF

  for release in focal jammy kinetic lunar; do
   VM=sru-$release
   lxc launch ubuntu-daily:$release $VM
   while ! lxc exec $VM -- cloud-init status --wait --long; do
  sleep 5
   done
   echo --- 1. Generate current apport report, selecting Openstack as cloud.
   echo --- step through prompts and select 'K' to keep report
   echo --- VERSION OF APPORT ---
   lxc exec $VM -- apport-bug --version
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.orig
   lxc exec $VM rm /tmp/$APPORT_FILE

   lxc file push setup_proposed.sh $VM/
   lxc exec $VM -- bash /setup_proposed.sh | grep cloud-init

   lxc file push openstack.json $VM/run/cloud-init/instance-data.json
   echo --- 2. Generate -proposed apport report which sources openstack 
instance-data.json, selecting Openstack as cloud.
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.openstack-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   echo --- 3. Generate -proposed apport report which sources ec2 
instance-data, selecting Ec2 as cloud.
   lxc file push ec2.json $VM/run/cloud-init/instance-data.json
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.ec2-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   # redact logs lines for easy diffs
   for file in `ls apport*`; do
   sed -i '1,/logs.tgz/!d' $file
   done
   echo --- 4. Inspect diff tags of orig to openstack-proposed report
   diff -urN apport-$VM.orig apport-$VM.openstack-proposed || true
   echo --- 5. Inspect diff tags of openstack-proposed to ec2-proposed report
   diff -urN apport-$VM.openstack-proposed apport-$VM.ec2-proposed || true

  done

  [ Where problems could occur ]
  apport-bug could traceback on poor logic preventing simple bug filing at 
apport CLI. It could omit tags if unable to process 
cloud-init/instance-data.json. nothing critical to daily performance, uptime or 
security

  [ Other Info ]

  [Original description]

  Issues:
   - Using the presence of cloud-init to flag an image as a cloud image is 
incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images)
   - Using the presence of EC2 metadata source is incorrect as many non-EC2 
clouds provide EC2 metadata.  Thus we have bugs like bug #1722946 that are 
tagged as an 'ec2-images' bug which are clearly on openstack
   - Marking all bugs that have cloud-init but no EC2 metadata source as an 
'uec-images' bug uses a 

[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info

2023-07-06 Thread Chad Smith
SRU validation Focal, Jammy, Kinetic and Lunar successes.

** Attachment added: "sru-1724623.log"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1724623/+attachment/5684387/+files/sru-1724623.log

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

Title:
  Update ubuntu cloud info

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Focal:
  Fix Committed
Status in cloud-init source package in Jammy:
  Fix Committed
Status in cloud-init source package in Kinetic:
  Fix Committed
Status in apport source package in Lunar:
  New
Status in cloud-init source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]
  Apport reported bug add invalid bug tags such as `uec-images` which no longer 
has meaning or `ec2-images` on openstack. Since cloud-init is installed in all 
these images and detects the correct datasource, leverage cloud-init's 
instance-data.json or cloud-id

  [ Test Plan ]

  1. Launch LXD container for each series
  2. upgrade to cloud-init from -proposed.
  3. Execute apport-bug cloud-init and view report to assess that correct tags 
are present for LXD datasource.
  4. replace /run/cloud-init/instance-data.json cloud-id content with examples 
from openstack, ec2, configdrive and assert appropriate tags match the platform 
details.

  verification scriptlet (attached):

  #!/bin/bash
  set -ex

  cat > setup_proposed.sh  openstack.json  ec2.json << EOF
  {
    "ds": {
  "imageId": "ami-123",
  "instanceType": "m1.tiny",
  "region": "us-east-1"
    },
    "v1": {
  "cloud_name": "aws",
  "distro": "ubuntu",
  "distro_release": "jammy",
  "distro_version": "22.04",
  "instance_id": "i-06b5687b4d7b8595d",
  "machine": "x86_64",
  "platform": "ec2",
  "python_version": "3.10.4",
  "region": "us-east-2",
  "variant": "ubuntu"
    }
  }
  EOF

  for release in focal jammy kinetic lunar; do
   VM=sru-$release
   lxc launch ubuntu-daily:$release $VM
   while ! lxc exec $VM -- cloud-init status --wait --long; do
  sleep 5
   done
   echo --- 1. Generate current apport report, selecting Openstack as cloud.
   echo --- step through prompts and select 'K' to keep report
   echo --- VERSION OF APPORT ---
   lxc exec $VM -- apport-bug --version
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.orig
   lxc exec $VM rm /tmp/$APPORT_FILE

   lxc file push setup_proposed.sh $VM/
   lxc exec $VM -- bash /setup_proposed.sh | grep cloud-init

   lxc file push openstack.json $VM/run/cloud-init/instance-data.json
   echo --- 2. Generate -proposed apport report which sources openstack 
instance-data.json, selecting Openstack as cloud.
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.openstack-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   echo --- 3. Generate -proposed apport report which sources ec2 
instance-data, selecting Ec2 as cloud.
   lxc file push ec2.json $VM/run/cloud-init/instance-data.json
   lxc exec $VM -- apport-bug cloud-init
   APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
   lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.ec2-proposed
   lxc exec $VM rm /tmp/$APPORT_FILE

   # redact logs lines for easy diffs
   for file in `ls apport*`; do
   sed -i '1,/logs.tgz/!d' $file
   done
   echo --- 4. Inspect diff tags of orig to openstack-proposed report
   diff -urN apport-$VM.orig apport-$VM.openstack-proposed || true
   echo --- 5. Inspect diff tags of openstack-proposed to ec2-proposed report
   diff -urN apport-$VM.openstack-proposed apport-$VM.ec2-proposed || true

  done

  [ Where problems could occur ]
  apport-bug could traceback on poor logic preventing simple bug filing at 
apport CLI. It could omit tags if unable to process 
cloud-init/instance-data.json. nothing critical to daily performance, uptime or 
security

  [ Other Info ]

  [Original description]

  Issues:
   - Using the presence of cloud-init to flag an image as a cloud image is 
incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images)
   - Using the presence of EC2 metadata source is incorrect as many non-EC2 
clouds provide EC2 metadata.  Thus we have bugs like bug #1722946 that are 
tagged as an 'ec2-images' bug which are clearly on openstack
   - Marking all bugs that have cloud-init but no EC2 metadata source as an 
'uec-images' bug uses a 

[Touch-packages] [Bug 2025650] Re: package linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1-> b

2023-07-06 Thread Stefan
Oh, sorry, I missed that. Thank you!

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

Title:
  package linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1-> boot partition full

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  On every boot, multiple times

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Jun 30 14:59:50 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-05-28 (765 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2023-04-06 (87 days ago)

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


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


[Touch-packages] [Bug 1938692] Re: systemd-cryptsetup-generator generated unit for root filesystem fails with keyfile

2023-07-06 Thread Nick Rosbrook
Sorry this was not looked at sooner. Is this still a problem in newer
releases?

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

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

Title:
  systemd-cryptsetup-generator generated unit for root filesystem fails
  with keyfile

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 21.04 on a Raspberry Pi 4b.

  /etc/crypttab:
  # 
  crypt_root UUID=12989868-19fe-4834-90a8-f1bf13977745
/dev/disk/by-label/wopr_keys:/crypt_root_key  
luks,discard,keyscript=/lib/cryptsetup/scripts/passdev,initramfs,x-initrd.attach
  crypt_swap /dev/disk/by-id/scsi-SSamsung_Portable_SSD_T5_4B1C18654321-part2   
 /dev/urandom  swap,discard,cipher=aes-xts-plain64,size=256,plain

  /etc/fstab
  LABEL=system-boot   /boot/firmware  vfatdefaults0   1
  /dev/mapper/crypt_root  /   btrfs   
defaults,ssd,compress=zstd,discard=async,relatime,x-initrd.mount,subvol=@ 0 0
  /dev/mapper/crypt_root  /home   btrfs   
defaults,ssd,compress=zstd,discard=async,relatime,x-initrd.mount,subvol=@home 0 0
  /dev/mapper/crypt_swap  noneswapdefaults0   0

  /boot/firmware/cmdline.txt
  dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 
cryptdevice=LABEL=crypt_root:crypt_root root=/dev/mapper/crypt_root 
rootflags=subvol=@ rootfstype=btrfs rootwait fixrtc zswap.enabled=1

  On the Raspberry Pi, it seems that cryptsetup-initramfs is responsible
  for unlocking devices in the initramfs. Things worked perfectly before
  I started using a keyfile on a USB Drive to unlock my root device.

  The issue is that /lib/cryptsetup/scripts/passdev expects the keyfile
  to be in a particular format, and systemd-cryptsetup-generator expects
  a slightly different format. So cryptsetup-initramfs successfully
  unlocks the root filesystem and mounts it, but systemd's auto-
  generated unit attempts to mount the (in its view) incorrectly
  formatted keyfile device and fails. As a result the entire boot fails.
  In the rescue shell, I can see that all filesystems have mounted
  correctly.

  I can think of a couple of solutions:
  1. I disabled systemd luks unit generation by passing luks=no in the kernel 
command line. This also disables other crypttab entries from unlocking, so my 
swap partition mount fails.
  2. I tried disabling systemd unit generation just for my root device with 
x-initrd.attach,noauto,nofail,initramfs options. This resulted in the exact 
same error. I also tried adding noauto to the fstab entry for my root device 
and this did not work.
  3. Arch Linux has a separate crypttab.initramfs file that is only loaded into 
the initramfs. Could this be implemented somehow?

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


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


[Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

2023-07-06 Thread Till Kamppeter
Dalik, there is an upstream bug report about your observation of missing
*.bin files for CUPS on /var/lib/snapd/seccomp/bpf/:

https://github.com/OpenPrinting/cups-snap/issues/16

It is reported by GitHub user d3al. Is that you?

I am not able to reproduce this problem on Ubuntu 23.04 and 23.10.

** Bug watch added: github.com/OpenPrinting/cups-snap/issues #16
   https://github.com/OpenPrinting/cups-snap/issues/16

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

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


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


[Touch-packages] [Bug 2009743] Re: networkd: classless routes served by DHCP are created incorrectly

2023-07-06 Thread Nick Rosbrook
** Changed in: systemd (Ubuntu)
   Status: New => Triaged

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

Title:
  networkd: classless routes served by DHCP are created incorrectly

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  After upgrading 20.04 systems to 22.04, the classless routes served
  via DHCP are not being registered correctly - they are missing the
  gateway address.

  Expected routes - these are taken from a 20.04 system on the same
  network:

  $ ip route
  default via 10.10.1.1 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.0.0.0/8 dev enp24s0 proto kernel scope link src 10.10.64.12
  10.88.88.0/24 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.96.0.0/11 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100

  Actual routes - these are the routes created in one of the affected
  22.04 systems:

  $ ip route
  default via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  8.8.8.8 via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  10.0.0.0/8 dev bond0 proto kernel scope link src 10.10.48.20 metric 100
  10.10.1.1 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.10.1.2 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.88.88.0/24 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.96.0.0/11 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100

  Note the routes for 10.88.88.0/24 and 10.96.0.0/11 are missing the "via" 
gateway address, and therefore don't work.
  (For some reason there are also static routes created for DNS server 
(8.8.8.8) and known gateways (10.10.1.1 and 10.10.1.2). These are redundant but 
harmless.)

  Both the working and non-working systems are being managed by netplan.
  The non-working system has a bonded interface but I have checked that
  is not the cause of the problem - using a physical interface directly
  has the same result.

  I have attached the files /etc/netplan/00-installer-config.yaml and
  /run/systemd/network/10-netplan-bond0.network of the affected system.

  Affected system:
  Ubuntu version: Ubuntu 22.04.2 LTS
  systemd version: 249.11-0ubuntu3.6

  Older system not affected:
  Ubuntu version: Ubuntu 20.04.5 LTS
  systemd version: 245.4-4ubuntu3.19

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


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


[Touch-packages] [Bug 2026292] Re: conflict on syslog.service when moving between rsyslog and busybox-syslogd

2023-07-06 Thread Nick Rosbrook
** Changed in: systemd (Ubuntu)
   Status: New => Triaged

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

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

Title:
  conflict on syslog.service when moving between rsyslog and busybox-
  syslogd

Status in busybox package in Ubuntu:
  Won't Fix
Status in rsyslog package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Suppose a system with systemd 252 and rsyslog installed.  Install
  busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to
  be removed (but not purged).  The install of busybox-syslogd will fail
  as follows:

  Failed to preset unit, file "/etc/systemd/system/syslog.service"
  already exists and is a symlink to
  "/lib/systemd/system/rsyslog.service".

  The failure can also be seen in the reverse direction - busybox-
  syslogd 1:1.36.1-3ubuntu1 installed, then install rsyslog.

  With systemd 253, we instead see:
  Removed "/etc/systemd/system/syslog.service".

  Workarounds:
  * use systemd 253 when available
  * purge the existing system-log-daemon before installing the new one

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


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


[Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

2023-07-06 Thread Marcus Pope
@Nathan Teodosio:

Just tried running our test harness via runuser and that works with the
edge version of chromium - which  is a valid path forward for me,
especially if running directly from the current/user snap path is not
supported.

But I'm still around if you want me to investigate further.

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

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


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


[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2023-07-06 Thread Bug Watch Updater
** Changed in: apparmor (Debian)
   Status: Unknown => 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/1794064

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Committed
Status in apparmor package in Debian:
  New
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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


[Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

2023-07-06 Thread Marcus Pope
@Nathan Teodosio:

Running either produces the same issue:

```
$ /snap/bin/chromium
cannot open path of the current working directory: Permission denied

$ /snap/bin/chromium --enable-logging=stderr
cannot open path of the current working directory: Permission denied
```

I presume these are issues with shelling into my vm as a vagrant user.

If I run under our service user I get this output:

```
sudo runuser -l  -c 'chromium --headless --disable-gpu'
[0706/142016.391512:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called 
with multiple threads in process gpu-process.
[0706/142016.397591:WARNING:bluez_dbus_manager.cc(247)] Floss manager not 
present, cannot set Floss enable/disable.

sudo runuser -l  -c 'chromium --headless --disable-gpu 
--disable-software-rasterizer --enable-logging=stderr'
[0706/142336.953854:WARNING:bluez_dbus_manager.cc(247)] Floss manager not 
present, cannot set Floss enable/disable.
```

Which is the same output I get when the snap works.

We have had to use the current/user path from the start, however I just
tried replacing the setBinary call for webdriver with the
/snap/bin/chromium path and it did not resolve the issue either.

Running the `snap refresh` command you provided resolves my problem.  So
thank you for that!  But I'm still available for any debugging requests.

And finally, I only have access to headless installs for ubuntu, so I
don't have a way of running it headed.

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

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


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


[Touch-packages] [Bug 1283309] Re: bash built-in read timeout (-t) doesn't work

2023-07-06 Thread Charles Evans
Hwclock -s is run on the system at least weekly as system time drifts.
Adjtime is not installed.

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

Title:
  bash built-in read timeout (-t) doesn't work

Status in bash package in Ubuntu:
  Expired

Bug description:
  This should timeout after 2 seconds (based on bash man page) but it doesn't:
  #read -t 2 test
  (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..)

  bash --version:
  GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu)

  Installed bash package version:
  4.2-2ubuntu2.1

  $ lsb_release -rd
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

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


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


[Touch-packages] [Bug 2009743] Re: networkd: classless routes served by DHCP are created incorrectly

2023-07-06 Thread Bug Watch Updater
** Changed in: systemd
   Status: Unknown => 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/2009743

Title:
  networkd: classless routes served by DHCP are created incorrectly

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading 20.04 systems to 22.04, the classless routes served
  via DHCP are not being registered correctly - they are missing the
  gateway address.

  Expected routes - these are taken from a 20.04 system on the same
  network:

  $ ip route
  default via 10.10.1.1 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.0.0.0/8 dev enp24s0 proto kernel scope link src 10.10.64.12
  10.88.88.0/24 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.96.0.0/11 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100

  Actual routes - these are the routes created in one of the affected
  22.04 systems:

  $ ip route
  default via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  8.8.8.8 via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  10.0.0.0/8 dev bond0 proto kernel scope link src 10.10.48.20 metric 100
  10.10.1.1 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.10.1.2 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.88.88.0/24 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.96.0.0/11 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100

  Note the routes for 10.88.88.0/24 and 10.96.0.0/11 are missing the "via" 
gateway address, and therefore don't work.
  (For some reason there are also static routes created for DNS server 
(8.8.8.8) and known gateways (10.10.1.1 and 10.10.1.2). These are redundant but 
harmless.)

  Both the working and non-working systems are being managed by netplan.
  The non-working system has a bonded interface but I have checked that
  is not the cause of the problem - using a physical interface directly
  has the same result.

  I have attached the files /etc/netplan/00-installer-config.yaml and
  /run/systemd/network/10-netplan-bond0.network of the affected system.

  Affected system:
  Ubuntu version: Ubuntu 22.04.2 LTS
  systemd version: 249.11-0ubuntu3.6

  Older system not affected:
  Ubuntu version: Ubuntu 20.04.5 LTS
  systemd version: 245.4-4ubuntu3.19

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


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


[Touch-packages] [Bug 2026307] [NEW] ssh-askpass-gnome pops up for every sudo command

2023-07-06 Thread john doe
Public bug reported:

When running multiple commands like this:
SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup
/usr/local/bin/ from my gtk4 app the ssh-askpass-gnome dialog and the
gnome inhibitShortcutsDialog pops up, i click allow on the
inhibitShortcutsDialog, then enter my password which is accepted, then
they both pop up again for each of these sudo commands my app calls.

This happens in ubuntu 22.04-23.04 (completely updated) using gnome. If
i use xfce in same ubuntu versions, the gnome dialog doesn't pop up, of
course, and ssh-askpass-gnome works properly (one entry and then all
commands executed without further prompting). fedora 37 works properly
with gnome x11 or wayland, and xfce. Not sure if this is a bug in
ubuntu's ssh-askpass-gnome, gnome-shell, or both.

ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome
1:9.0p1-1ubuntu8.2

fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6

thanks

** 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/2026307

Title:
  ssh-askpass-gnome pops up for every sudo command

Status in openssh package in Ubuntu:
  New

Bug description:
  When running multiple commands like this:
  SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup
  /usr/local/bin/ from my gtk4 app the ssh-askpass-gnome dialog and the
  gnome inhibitShortcutsDialog pops up, i click allow on the
  inhibitShortcutsDialog, then enter my password which is accepted, then
  they both pop up again for each of these sudo commands my app calls.

  This happens in ubuntu 22.04-23.04 (completely updated) using gnome.
  If i use xfce in same ubuntu versions, the gnome dialog doesn't pop
  up, of course, and ssh-askpass-gnome works properly (one entry and
  then all commands executed without further prompting). fedora 37 works
  properly with gnome x11 or wayland, and xfce. Not sure if this is a
  bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both.

  ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome
  1:9.0p1-1ubuntu8.2

  fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6

  thanks

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


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


[Touch-packages] [Bug 1283309] Re: bash built-in read timeout (-t) doesn't work

2023-07-06 Thread Charles Evans
With multiple bash scripts running for over a month,
I now have random read fails at least once an hour PER SCRIPT. 
Restarting the script did not help.
Restarting bash helps for a while.

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

Title:
  bash built-in read timeout (-t) doesn't work

Status in bash package in Ubuntu:
  Expired

Bug description:
  This should timeout after 2 seconds (based on bash man page) but it doesn't:
  #read -t 2 test
  (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..)

  bash --version:
  GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu)

  Installed bash package version:
  4.2-2ubuntu2.1

  $ lsb_release -rd
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

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


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


[Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

2023-07-06 Thread Joel Vandal
If I execute the following command then I no more have issues :

snap refresh --channel stable/core20 chromium

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

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


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


[Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

2023-07-06 Thread Nathan Teodosio
3. Please specify whether the errors are only observed for headless
Chromium or if it is also observed for normal Chromium.

** Tags added: focal printing

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

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


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


[Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

2023-07-06 Thread Nathan Teodosio
Thank you very much for elaborating, that is much clearer. A couple of
questions:

1. When you do not use /snap/chromium/current/usr/lib/chromium-
browser/chrome, but rather chromium or /snap/bin/chromium, do you ever
get those GLIBC errors? If not, what is the exact error you get? You
mention permission denied, can you give me that full error message?
Also, if you think the message is not clear enough, please try --enable-
logging=stderr.

2. I have uploaded the older version to the stable/core20 channel, with
which you can replace the current one:

  snap refresh --channel stable/core20 chromium

Does that fix any of the issues you observed?

As a matter of fact, I can reproduce the error when using the full
unconfined path (/snap/chromium/current/usr/lib/chromium-
browser/chrome), but that is discouraged and not supported.

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => High

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

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


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


[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2023-07-06 Thread Andreas Hasenack
Looks like we get this if evince is update, apparmor is not, and a link
in a pdf is clicked:

Jul 06 18:36:59 j-evince kernel: audit: type=1400
audit(1688668619.304:78): apparmor="DENIED" operation="exec"
info="profile transition not found" error=-13 profile="/usr/bin/evince"
name="/usr/bin/snap" pid=2246 comm="env" requested_mask="x"
denied_mask="x" fsuid=1000 ouid=0


The end result seems the same: permission denied, link isn't opened, the evince 
gui just does nothing, the console (if launched from a terminal) saya "env: 
'/snap/bin/firefox': Permission denied

If Georgia can confirm this is the worst that can happen by not having
the Recommends on the updated apparmor profile, then I think it's ok to
leave it out, but would be good to have confirmation from @vorlon, as he
raised the objection and it's not clear if he saw Georgia's comment.

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Committed
Status in apparmor package in Debian:
  Unknown
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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


[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2023-07-06 Thread Jeremy Bícha
Andreas, Debian Testing right now has the updated evince but not the
updated apparmor. https://bugs.debian.org/1040481

The consequence is that hyperlinks from Evince don't open if the default
browser is a Snap. That's the same consequence as before the Evince
change.

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

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

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Committed
Status in apparmor package in Debian:
  Unknown
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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


[Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

2023-07-06 Thread Joel Vandal
I need to execute :

snap revert chromium

In order to resolve the issue using Ubuntu 20.04 or 20.10.

-

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

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


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


[Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

2023-07-06 Thread Till Kamppeter
Anyone suffering the described problem, could you follow Nathan's
instructions if you have not done so yet, and could you run the
following commands and paste the output here?

lpstat -r
lpstat -v
lpstat -p
cuos.lpstat -r
cups.lpstat -v
cups.lpstat -p

Aleo try to print through the CUPS Snap, for example via

cups.lp -d PRINTER FILE.PDF

Replace PRINTER by the name of a working print queue and FILE.PDF by the
name of a PDF file which you have. Does this work? If not, could you
also try

lp -d PRINTER FILE.PDF

Does this work?

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

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


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


[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2023-07-06 Thread Andreas Hasenack
> Do we need evince to be reuploaded for jammy there since the previous
upload was rejected by Steve?

I'm trying to see what type of error we get if we load a profile with
such a rule and the target profile does not exist:

  /{,snap/core/[0-9]*/,snap/snapd/[0-9]*/}usr/bin/snap mrCx ->
snap_browsers,

Will it be worse than what we have now?
Will evince's postinst fail when it reloads the profile with the above line, 
and snap_browsers is not defined?
Will it crash when a link in a pdf is clicked?

It's taking a bit to setup a jammy desktop vm to try this, and I have
other SRUs to process. Georgia, could you elaborate on what would happen
if the new evince were to be installed with an old apparmor that knows
nothing about the snap_browsers profile?

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Committed
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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


[Touch-packages] [Bug 2009743] Re: networkd: classless routes served by DHCP are created incorrectly

2023-07-06 Thread Nick Rosbrook
** Bug watch added: github.com/systemd/systemd/issues #28280
   https://github.com/systemd/systemd/issues/28280

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

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

Title:
  networkd: classless routes served by DHCP are created incorrectly

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading 20.04 systems to 22.04, the classless routes served
  via DHCP are not being registered correctly - they are missing the
  gateway address.

  Expected routes - these are taken from a 20.04 system on the same
  network:

  $ ip route
  default via 10.10.1.1 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.0.0.0/8 dev enp24s0 proto kernel scope link src 10.10.64.12
  10.88.88.0/24 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.96.0.0/11 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100

  Actual routes - these are the routes created in one of the affected
  22.04 systems:

  $ ip route
  default via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  8.8.8.8 via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  10.0.0.0/8 dev bond0 proto kernel scope link src 10.10.48.20 metric 100
  10.10.1.1 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.10.1.2 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.88.88.0/24 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.96.0.0/11 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100

  Note the routes for 10.88.88.0/24 and 10.96.0.0/11 are missing the "via" 
gateway address, and therefore don't work.
  (For some reason there are also static routes created for DNS server 
(8.8.8.8) and known gateways (10.10.1.1 and 10.10.1.2). These are redundant but 
harmless.)

  Both the working and non-working systems are being managed by netplan.
  The non-working system has a bonded interface but I have checked that
  is not the cause of the problem - using a physical interface directly
  has the same result.

  I have attached the files /etc/netplan/00-installer-config.yaml and
  /run/systemd/network/10-netplan-bond0.network of the affected system.

  Affected system:
  Ubuntu version: Ubuntu 22.04.2 LTS
  systemd version: 249.11-0ubuntu3.6

  Older system not affected:
  Ubuntu version: Ubuntu 20.04.5 LTS
  systemd version: 245.4-4ubuntu3.19

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


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


[Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

2023-07-06 Thread Marcus Pope
Our CI server was manually updated to the edge version of the snap in an
attempt to resolve the issue, but it produces the same error output.

Edit: Our CI server is on Ubuntu 20.04.6 LTS

```
chromium   116.0.5845.4 2527   latest/edge  canonical✓ -
```

Glibc version:

```
~$ ldd --version
ldd (Ubuntu GLIBC 2.31-0ubuntu9.9) 2.31
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.
```

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

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


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


[Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

2023-07-06 Thread Marcus Pope
Sure thing, I can provide any information you need.

1. Happened with the latest update to Chromium, has been working fine
for over a year.  I use it for functional testing in combination with
selenium and facebook webdriver.  Have it installed as a snap, so I
presume it was auto updated, but I do not have a previous install listed
so I cannot revert.

2. Running chromium from the terminal in headless mode produces the same
series of GLIBC errors as posted by @Dalik.

```
/snap/chromium/current/usr/lib/chromium-browser/chrome --headless --disable-gpu 
--disable-software-rasterizer
/snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
/snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
/snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
/snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
/snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
/snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
```

If I run chromium without the qualified path I get a permission denied
issue, regardless of sudo/--no-sandbox.

Dev environment is ubuntu 20.04 running on a macbook pro in a virtualbox
vm.

We also have this exact same issue on our CI server which is an ubuntu
20.04 server on aws. I'm booting that up to see if snap reports any
previous versions, but we get the exact same error on that server too.

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

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


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

[Touch-packages] [Bug 1794064] Update Released

2023-07-06 Thread Andreas Hasenack
The verification of the Stable Release Update for apparmor has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any 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/1794064

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Committed
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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


[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2023-07-06 Thread Launchpad Bug Tracker
This bug was fixed in the package apparmor - 3.0.8-1ubuntu2.1

---
apparmor (3.0.8-1ubuntu2.1) lunar; urgency=medium

  * Update abstractions/snap-browsers to include lock permissions
(LP: #1794064)
- d/p/u/update-snap-browsers-permissions-lp1794064.patch

 -- Georgia Garcia   Tue, 06 Jun 2023
08:49:17 -0300

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

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  Fix Committed
Status in evince source package in Jammy:
  In Progress
Status in apparmor source package in Lunar:
  Fix Released
Status in evince source package in Lunar:
  Fix Committed
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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


[Touch-packages] [Bug 2026292] Re: conflict on syslog.service when moving between rsyslog and busybox-syslogd

2023-07-06 Thread Dan Bungert
** Changed in: busybox (Ubuntu)
   Status: New => Won't Fix

** Changed in: rsyslog (Ubuntu)
   Status: New => Won't Fix

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

Title:
  conflict on syslog.service when moving between rsyslog and busybox-
  syslogd

Status in busybox package in Ubuntu:
  Won't Fix
Status in rsyslog package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  New

Bug description:
  Suppose a system with systemd 252 and rsyslog installed.  Install
  busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to
  be removed (but not purged).  The install of busybox-syslogd will fail
  as follows:

  Failed to preset unit, file "/etc/systemd/system/syslog.service"
  already exists and is a symlink to
  "/lib/systemd/system/rsyslog.service".

  The failure can also be seen in the reverse direction - busybox-
  syslogd 1:1.36.1-3ubuntu1 installed, then install rsyslog.

  With systemd 253, we instead see:
  Removed "/etc/systemd/system/syslog.service".

  Workarounds:
  * use systemd 253 when available
  * purge the existing system-log-daemon before installing the new one

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


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


[Touch-packages] [Bug 1992688] Re: firefox deb not installed

2023-07-06 Thread Robert C Jennings
FYI, if a user has a 22.04 install where they have explicitly removed
snapd/firefox this will add them back.  Not sure if this was a
consideration in the fix/testing.

Also, the apt resolver is pulling in snapd while holding ubuntu-desktop
back during staging which made finding the cause of the snapd/firefox
installation a bit hard to track down since no packages upgraded in the
same unattended-upgrades operation had dependencies on them.

(thread: https://hachyderm.io/@rcj4747/110667685702206834)

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

Title:
  firefox deb not installed

Status in firefox package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in firefox source package in Jammy:
  Invalid
Status in ubuntu-meta source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  Applications which use x-www-browser to launch a browser will not work on a 
freshly installed Ubuntu 22.04 system as the firefox deb (which provides 
x-www-browser) is not installed.

  Test Plan
  -
  1) Install Ubuntu 22.04.2 using an amd64 desktop iso image
  2) Open a terminal
  3) Run x-www-browser www.ubuntu.com
  4) Observe a command not found message which recommends installing firefox

  Installing of a daily build of Ubuntu 22.04 with -proposed enabled and
  ubuntu-desktop version 1.481.1 will not exhibit the above problem.

  Where problems could occur
  --

  Other Info
  --
  I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was 
not removed during the upgrade process so upgrades are a non-issue.

  Original Description
  
  Bug 1964036 leads me to believe that the firefox deb provides some important 
functionality (the firefox favourite icon in the gnome shell dock) but there is 
nothing that would require the deb to be installed (it is not seeded nor has an 
rdep) and the package description indicates that it can be safely removed. Is 
there some important functionality that it provides?

  ProblemType: BugDistroRelease: Ubuntu 22.10
  Package: ubuntu-release-upgrader-core 1:22.10.8
  ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7
  Uname: Linux 5.19.0-19-generic x86_64
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 12 11:30:46 2022
  InstallationDate: Installed on 2022-04-27 (167 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago)
  VarLogDistupgradeTermlog:

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


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


[Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

2023-07-06 Thread Nathan Teodosio
Thanks for the confirmation, but I don't yet know the context of the
issue.

Did you update from Bionic to Focal or did you simply notice the issue
after the last Chromium update?

Is there any problem when running 'chromium' from a terminal or is it a
issue specific to the launcher?

Please try to be as specific as possible, context is also very welcome.

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Two deployed ubuntu images, 20.04 and 22.04. Both images are fully
  updated.

  Issue appears to only impact 20.04.
  chrome snap version 2529

  Launching chrome from menu shortcut that is managed by the snap works
  and it using this location /snap/bin/chromium

  Launching chrome from desktop shortcut that I manage on 20.04 fails - 
/snap/chromium/current/usr/lib/chromium-browser/chrome
  Updating the desktop shortcut with this location on 20.04 works - 
/snap/bin/chromium

  Try and print from the browser, print dialog in chrome does not list any 
system printers, only shows PDF.
  Doing the same on 22.04 image, I get a list of printers.

  CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I 
get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No 
such file or directory"
  I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 
100% failure rate on 20.04.

  I get this error when running chrome from cli from this path on 20.04
  /snap/chromium/current/usr/lib/chromium-browser which points to 2529
  snap image.

  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/current/usr/lib/chromium-browser/chrome)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)
  /snap/chromium/current/usr/lib/chromium-browser/chrome: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by 
/snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so)

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


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


[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info

2023-07-06 Thread Chad Smith
** Changed in: cloud-init (Ubuntu Lunar)
   Status: New => Fix Committed

** Description changed:

  [ Impact ]
  Apport reported bug add invalid bug tags such as `uec-images` which no longer 
has meaning or `ec2-images` on openstack. Since cloud-init is installed in all 
these images and detects the correct datasource, leverage cloud-init's 
instance-data.json or cloud-id
  
  [ Test Plan ]
  
  1. Launch LXD container for each series
  2. upgrade to cloud-init from -proposed.
  3. Execute apport-bug cloud-init and view report to assess that correct tags 
are present for LXD datasource.
  4. replace /run/cloud-init/instance-data.json cloud-id content with examples 
from openstack, ec2, configdrive and assert appropriate tags match the platform 
details.
  
  verification scriptlet (attached):
  
  #!/bin/bash
  set -ex
  
  cat > setup_proposed.sh  openstack.json  ec2.json << EOF
  {
-   "ds": {
- "imageId": "ami-123",
- "instanceType": "m1.tiny",
- "region": "us-east-1"
-   },
-   "v1": {
- "cloud_name": "aws",
- "distro": "ubuntu",
- "distro_release": "jammy",
- "distro_version": "22.04",
- "instance_id": "i-06b5687b4d7b8595d",
- "machine": "x86_64",
- "platform": "ec2",
- "python_version": "3.10.4",
- "region": "us-east-2",
- "variant": "ubuntu"
-   }
+   "ds": {
+ "imageId": "ami-123",
+ "instanceType": "m1.tiny",
+ "region": "us-east-1"
+   },
+   "v1": {
+ "cloud_name": "aws",
+ "distro": "ubuntu",
+ "distro_release": "jammy",
+ "distro_version": "22.04",
+ "instance_id": "i-06b5687b4d7b8595d",
+ "machine": "x86_64",
+ "platform": "ec2",
+ "python_version": "3.10.4",
+ "region": "us-east-2",
+ "variant": "ubuntu"
+   }
  }
  EOF
  
  for release in focal jammy kinetic lunar; do
-  VM=sru-$release
-  lxc launch ubuntu-daily:$release $VM
-  while ! lxc exec $VM -- cloud-init status --wait --long; do
- sleep 5
-  done
-  echo --- 1. Generate current apport report, selecting Openstack as cloud.
-  echo --- step through prompts and select 'K' to keep report
-  lxc exec $VM -- apport-bug cloud-init
-  APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
-  lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.orig
-  lxc exec $VM rm /tmp/$APPORT_FILE
+  VM=sru-$release
+  lxc launch ubuntu-daily:$release $VM
+  while ! lxc exec $VM -- cloud-init status --wait --long; do
+ sleep 5
+  done
+  echo --- 1. Generate current apport report, selecting Openstack as cloud.
+  echo --- step through prompts and select 'K' to keep report
+  echo --- VERSION OF APPORT ---
+  lxc exec $VM -- apport-bug --version
+  lxc exec $VM -- apport-bug cloud-init
+  APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
+  lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.orig
+  lxc exec $VM rm /tmp/$APPORT_FILE
  
-  lxc file push setup_proposed.sh $VM/
-  lxc exec $VM -- bash /setup_proposed.sh | grep cloud-init
+  lxc file push setup_proposed.sh $VM/
+  lxc exec $VM -- bash /setup_proposed.sh | grep cloud-init
  
-  lxc file push openstack.json $VM/run/cloud-init/instance-data.json
-  echo --- 2. Generate -proposed apport report which sources openstack 
instance-data.json, selecting Openstack as cloud.
-  lxc exec $VM -- apport-bug cloud-init
-  APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
-  lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.openstack-proposed
-  lxc exec $VM rm /tmp/$APPORT_FILE
+  lxc file push openstack.json $VM/run/cloud-init/instance-data.json
+  echo --- 2. Generate -proposed apport report which sources openstack 
instance-data.json, selecting Openstack as cloud.
+  lxc exec $VM -- apport-bug cloud-init
+  APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
+  lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.openstack-proposed
+  lxc exec $VM rm /tmp/$APPORT_FILE
  
-  echo --- 3. Generate -proposed apport report which sources ec2 
instance-data, selecting Ec2 as cloud.
-  lxc file push ec2.json $VM/run/cloud-init/instance-data.json
-  lxc exec $VM -- apport-bug cloud-init
-  APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
-  lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.ec2-proposed
-  lxc exec $VM rm /tmp/$APPORT_FILE
+  echo --- 3. Generate -proposed apport report which sources ec2 
instance-data, selecting Ec2 as cloud.
+  lxc file push ec2.json $VM/run/cloud-init/instance-data.json
+  lxc exec $VM -- apport-bug cloud-init
+  APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport)
+  lxc file pull 

[Touch-packages] [Bug 2026292] Re: conflict on syslog.service when moving between rsyslog and busybox-syslogd

2023-07-06 Thread Dan Bungert
** Attachment added: "syslog-service-conflict"
   
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2026292/+attachment/5684334/+files/syslog-service-conflict

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

Title:
  conflict on syslog.service when moving between rsyslog and busybox-
  syslogd

Status in busybox package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Suppose a system with systemd 252 and rsyslog installed.  Install
  busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to
  be removed (but not purged).  The install of busybox-syslogd will fail
  as follows:

  Failed to preset unit, file "/etc/systemd/system/syslog.service"
  already exists and is a symlink to
  "/lib/systemd/system/rsyslog.service".

  The failure can also be seen in the reverse direction - busybox-
  syslogd 1:1.36.1-3ubuntu1 installed, then install rsyslog.

  With systemd 253, we instead see:
  Removed "/etc/systemd/system/syslog.service".

  Workarounds:
  * use systemd 253 when available
  * purge the existing system-log-daemon before installing the new one

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


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


[Touch-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.

2023-07-06 Thread Marcus Pope
Same issue for me on Ubuntu 20.04.1 LTS

Same version of chromium snap with the same error output as @Dalik

Output of `snap connections chromium`

```
Interface PlugSlot  
  Notes
audio-playbackchromium:audio-playback 
:audio-playback -
audio-record  chromium:audio-record   :audio-record 
  -
bluez chromium:bluez  :bluez
  -
browser-support   chromium:browser-sandbox
:browser-support-
camerachromium:camera :camera   
  -
content   chromium:foo-install-cups   - 
  -
content[gnome-42-2204]chromium:gnome-42-2204  
gnome-42-2204:gnome-42-2204 -
content[gtk-3-themes] chromium:gtk-3-themes   
gtk-common-themes:gtk-3-themes  -
content[icon-themes]  chromium:icon-themes
gtk-common-themes:icon-themes   -
content[sound-themes] chromium:sound-themes   
gtk-common-themes:sound-themes  -
cups  chromium:cups   cups:cups 
  -
desktop   chromium:desktop:desktop  
  -
desktop-legacychromium:desktop-legacy 
:desktop-legacy -
gsettings chromium:gsettings  :gsettings
  -
home  chromium:home   :home 
  -
joystick  chromium:joystick   :joystick 
  -
mount-observe chromium:mount-observe  - 
  -
mpris -   
chromium:mpris  -
network   chromium:network:network  
  -
network-bind  chromium:network-bind   :network-bind 
  -
network-manager   chromium:network-manager- 
  -
openglchromium:opengl :opengl   
  -
password-manager-service  chromium:password-manager-service   - 
  -
personal-fileschromium:chromium-config
:personal-files -
raw-usb   chromium:raw-usb- 
  -
removable-media   chromium:removable-media
:removable-media-
screen-inhibit-controlchromium:screen-inhibit-control 
:screen-inhibit-control -
system-files  chromium:etc-chromium-browser-policies  :system-files 
  -
system-packages-doc   chromium:system-packages-doc
:system-packages-doc-
u2f-devices   chromium:u2f-devices:u2f-devices  
  -
unity7chromium:unity7 :unity7   
  -
upower-observechromium:upower-observe 
:upower-observe -
wayland   chromium:wayland:wayland  
  -
x11   chromium:x11:x11  
  -
```

And cups

```
InterfacePlug  Slot 
 Notes
avahi-controlcups:avahi-control:avahi-control   
 -
cups chromium:cups cups:cups
 -
cups-control - cups:cups-control
 -
cups-control cups:cups-host:cups-control
 -
home cups:home :home
 -
network  cups:network  :network 
 -
network-bind cups:network-bind :network-bind
 -
network-manager-observe  cups:network-manager-observe  :network-manager-observe 
 -
raw-usb  cups:raw-usb  :raw-usb 
 -
system-files cups:etc-cups :system-files
 -
```

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

Title:
  Snap update broke launching and printing on 20.04 Ubuntu.

Status in chromium-browser package in Ubuntu:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete

Bug 

[Touch-packages] [Bug 2026292] Re: conflict on syslog.service when moving between rsyslog and busybox-syslogd

2023-07-06 Thread Dan Bungert
This script is a reproducer, assuming it installs the affected busybox-
syslogd.  Debian sid (systemd 253) passes.

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

Title:
  conflict on syslog.service when moving between rsyslog and busybox-
  syslogd

Status in busybox package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Suppose a system with systemd 252 and rsyslog installed.  Install
  busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to
  be removed (but not purged).  The install of busybox-syslogd will fail
  as follows:

  Failed to preset unit, file "/etc/systemd/system/syslog.service"
  already exists and is a symlink to
  "/lib/systemd/system/rsyslog.service".

  The failure can also be seen in the reverse direction - busybox-
  syslogd 1:1.36.1-3ubuntu1 installed, then install rsyslog.

  With systemd 253, we instead see:
  Removed "/etc/systemd/system/syslog.service".

  Workarounds:
  * use systemd 253 when available
  * purge the existing system-log-daemon before installing the new one

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


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


[Touch-packages] [Bug 2026292] [NEW] conflict on syslog.service when moving between rsyslog and busybox-syslogd

2023-07-06 Thread Dan Bungert
Public bug reported:

Suppose a system with systemd 252 and rsyslog installed.  Install
busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to
be removed (but not purged).  The install of busybox-syslogd will fail
as follows:

Failed to preset unit, file "/etc/systemd/system/syslog.service" already
exists and is a symlink to "/lib/systemd/system/rsyslog.service".

The failure can also be seen in the reverse direction - busybox-syslogd
1:1.36.1-3ubuntu1 installed, then install rsyslog.

With systemd 253, we instead see:
Removed "/etc/systemd/system/syslog.service".

Workarounds:
* use systemd 253 when available
* purge the existing system-log-daemon before installing the new one

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

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

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

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

** Also affects: busybox (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/2026292

Title:
  conflict on syslog.service when moving between rsyslog and busybox-
  syslogd

Status in busybox package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Suppose a system with systemd 252 and rsyslog installed.  Install
  busybox-syslogd version 1:1.36.1-3ubuntu1, which will cause rsyslog to
  be removed (but not purged).  The install of busybox-syslogd will fail
  as follows:

  Failed to preset unit, file "/etc/systemd/system/syslog.service"
  already exists and is a symlink to
  "/lib/systemd/system/rsyslog.service".

  The failure can also be seen in the reverse direction - busybox-
  syslogd 1:1.36.1-3ubuntu1 installed, then install rsyslog.

  With systemd 253, we instead see:
  Removed "/etc/systemd/system/syslog.service".

  Workarounds:
  * use systemd 253 when available
  * purge the existing system-log-daemon before installing the new one

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


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


[Touch-packages] [Bug 1839156] Re: TCP/IP connection stuck when called from UDEV rule

2023-07-06 Thread Nick Rosbrook
>From the udev man page:

"Note that running programs that access the network or mount/unmount
filesystems is not allowed inside of udev rules, due to the default
sandbox that is enforced on systemd-udevd.service."

I have not tested or looked into the specifics of the implementation to
be able to answer your second question.

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

Title:
  TCP/IP connection stuck when called from UDEV rule

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  It seems that in Eoan there is a lock/any other issue preventing
  particular system calls to be executed by the triggered action
  handler. I have an action executing wget when USB-serial adapter is
  plugged:

  SUBSYSTEM=="tty", ACTION=="add", ATTRS{idVendor}=="1a86", 
ATTRS{idProduct}=="7523", MODE="0666", RUN+="/usr/bin/wget -v --method=POST 
http://127.0.0.1:4000/udev_trigger/add;
  This action works perfectly in a prior versions - but in Eoan Ermine it hangs 
for ~30s and fails on a timeout. Analysis with strace shows that execution is 
stuck on connect() syscall - until it returns with ETIMEDOUT.

  Same Wget command, being run from a command line, works perfectly.

  The issue doesn't seem to be related to a particular IP
  (localhost/remote) and/or the status of a listener process - execution
  hangs also when listener is not running and port is free.

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


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


[Touch-packages] [Bug 1990740] Re: laptop wouldn't wake from sleep

2023-07-06 Thread Nick Rosbrook
Okay, thanks for following up. If you see a similar issue in the future,
please open a new bug report.

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

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

Title:
  laptop wouldn't wake from sleep

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Shortly after upgrading from Jammy to Kinetic my laptop went to sleep
  after I was idle for 20 minutes, as it is configured to do. The lid
  was closed when the laptop went to sleep. I was unable to wake up the
  laptop. Opening the lid back up should have caused it to wake up but
  did not. Pressing the power button should have caused it to wake up
  but did not.

  Both the LED on the lid and the power button light were cycling on and
  off as they do when the laptop is sleeping.

  I had to hold down the power button for five seconds to power off the
  laptop completely and then power it back on to get it to come back up.

  Never saw this behavior even once with Jammy.

  After rebooting and logging in, I put the laptop to sleep by selecting
  Suspend from the menu, and after _that_ it woke up immediately when I
  pushed the power button.

  I am not sure yet how reproducible this is, but I thought that even a
  single incidence of something like this was worth reporting.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu6
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 17:29:50 2022
  InstallationDate: Installed on 2019-08-16 (1135 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20KHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  dmi.bios.date: 04/20/2019
  dmi.bios.release: 1.38
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET63W (1.38 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:br1.38:efr1.13:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KH_BU_Think_FM_ThinkPadX1Carbon6th:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.systemd.logind.conf: [modified]
  mtime.conffile..etc.systemd.logind.conf: 2022-09-24T15:20:56.088250

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


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


[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2

2023-07-06 Thread Ghadi Rahme
Won't fix Lunar nor Mantic since package is not available for these
releases

** Changed in: python2.7 (Ubuntu Lunar)
   Status: In Progress => Won't Fix

** Also affects: python2.7 (Ubuntu Mantic)
   Importance: Undecided
 Assignee: Ghadi Rahme (ghadi-rahme)
   Status: In Progress

** Changed in: python2.7 (Ubuntu Mantic)
   Status: In Progress => Won't Fix

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  In Progress
Status in python2.7 source package in Bionic:
  In Progress
Status in python2.7 source package in Focal:
  In Progress
Status in python2.7 source package in Jammy:
  In Progress
Status in python2.7 source package in Kinetic:
  In Progress
Status in python2.7 source package in Lunar:
  Won't Fix
Status in python2.7 source package in Mantic:
  Won't Fix

Bug description:
  Compiling a Python extension using Python2 (Python 2.7.18) is making
  use of wrong compiler flags, hence dropping required optimizations
  when required. This is happening only when python2 is installed from
  Ubuntu's repositories. By default, Python's distutils module uses
  compiler and linker flags used to compile Python itself to be used to
  compile extensions.

  Steps to reproduce:
  1) On Ubuntu 20.04, install python2 using apt package manager.
  2) After successful installation, verify the CFLAGS variable from sysconfig 
module. On my machine, the output is 

  Python 2.7.18 (default, Jul  1 2022, 12:27:04)
  [GCC 9.4.0] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sysconfig
  >>> sysconfig.get_config_var('CFLAGS')
  '-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security  '

  3) Build a test extension module using python2 and verify the compilation 
flags. 
  python2 setup.py build_ext --inplace

  Output from below command is not matching with our expected above CFLAGS. 
  aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time 
-D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/usr/include/python2.7 -c testmodule.c -o 
build/temp.linux-aarch64-2.7/testmodule.o

  
  On further investigation, it looks like Ubuntu's specific patch applied on 
libpython2.7-stdlib package is altering the original upstream implementation of 
distutils/sysconfig.py code.

  Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
  Patch - 
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz

  Below is the code block which is causing the issue, where the presence of 
configure_cflags is modifying cflags. This code is result of ubuntu's patch and 
doesn't come directly from upstream python implementation.
  File - /usr/lib/python2.7/distutils/sysconfig.py
  Part of code block:
  elif configure_cflags:
  cflags = ' '.join(str(x) for x in (basecflags, configure_cflags, 
extra_cflags) if x)
  ldshared = ldshared + ' ' + configure_cflags

  
  I don't see problem on Python3 though we have extra code added from patch 
there as well. Patch used on python3, is not modifying the cflags completely 
and instead appending new flags to cflags.
  On python3 (tested on Ubuntu 20.04)
  File - /usr/lib/python3.8/distutils/sysconfig.py
  Part of code block which doesn't alter cflags completely
  elif configure_cflags:
  cflags = cflags + ' ' + configure_cflags
  ldshared = ldshared + ' ' + configure_cflags

  
  Request to update the python2 patch to behave similar to what is been done on 
python3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+subscriptions


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


[Touch-packages] [Bug 1958584] Re: Initramfs fails on boot

2023-07-06 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

Error 24 : Write error : cannot write compressed block

df log says:

Filesystem1K-blocks  Used Available Use% Mounted on
/dev/nvme0n1p2   721392610440 58488  92% /boot

So generating the initramfs fails because your boot partition is full
(only 57 MiB left). Please cleanup your boot partition. Feel free to
continue to report any other bugs you may find.

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Initramfs fails on boot

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Not sure what happened, but when I booted I got an initramfs error
  about linux kernel 5.13.0.27. Nothing seems to be broken, but the
  error comes up every time I reboot. Using Ubuntu 20.04 LTS.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jan 19 14:35:01 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-04-02 (293 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 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/1958584/+subscriptions


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


[Touch-packages] [Bug 1990740] Re: laptop wouldn't wake from sleep

2023-07-06 Thread Jonathan Kamens
I do not see this issue often enough to be able to reproduce it for
troubleshooting purposes. Can't remember the last time I saw it.

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

Title:
  laptop wouldn't wake from sleep

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Shortly after upgrading from Jammy to Kinetic my laptop went to sleep
  after I was idle for 20 minutes, as it is configured to do. The lid
  was closed when the laptop went to sleep. I was unable to wake up the
  laptop. Opening the lid back up should have caused it to wake up but
  did not. Pressing the power button should have caused it to wake up
  but did not.

  Both the LED on the lid and the power button light were cycling on and
  off as they do when the laptop is sleeping.

  I had to hold down the power button for five seconds to power off the
  laptop completely and then power it back on to get it to come back up.

  Never saw this behavior even once with Jammy.

  After rebooting and logging in, I put the laptop to sleep by selecting
  Suspend from the menu, and after _that_ it woke up immediately when I
  pushed the power button.

  I am not sure yet how reproducible this is, but I thought that even a
  single incidence of something like this was worth reporting.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu6
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 17:29:50 2022
  InstallationDate: Installed on 2019-08-16 (1135 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20KHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  dmi.bios.date: 04/20/2019
  dmi.bios.release: 1.38
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET63W (1.38 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:br1.38:efr1.13:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KH_BU_Think_FM_ThinkPadX1Carbon6th:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.systemd.logind.conf: [modified]
  mtime.conffile..etc.systemd.logind.conf: 2022-09-24T15:20:56.088250

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


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


[Touch-packages] [Bug 2025982] Re: Warning 'failed to get driver name for fd 0' fails gtk tests

2023-07-06 Thread Bug Watch Updater
** Changed in: mesa (Debian)
   Status: New => Confirmed

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

Title:
  Warning 'failed to get driver name for fd 0' fails gtk tests

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa package in Debian:
  Confirmed

Bug description:
  The new version displays that warning which makes the gtk autopkgtest
  red

  Upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199

  Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922

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


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


[Touch-packages] [Bug 2009743] Re: networkd: classless routes served by DHCP are created incorrectly

2023-07-06 Thread Nick Rosbrook
** Changed in: systemd (Ubuntu)
   Status: Incomplete => 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/2009743

Title:
  networkd: classless routes served by DHCP are created incorrectly

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading 20.04 systems to 22.04, the classless routes served
  via DHCP are not being registered correctly - they are missing the
  gateway address.

  Expected routes - these are taken from a 20.04 system on the same
  network:

  $ ip route
  default via 10.10.1.1 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.0.0.0/8 dev enp24s0 proto kernel scope link src 10.10.64.12
  10.88.88.0/24 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.96.0.0/11 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100

  Actual routes - these are the routes created in one of the affected
  22.04 systems:

  $ ip route
  default via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  8.8.8.8 via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  10.0.0.0/8 dev bond0 proto kernel scope link src 10.10.48.20 metric 100
  10.10.1.1 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.10.1.2 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.88.88.0/24 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.96.0.0/11 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100

  Note the routes for 10.88.88.0/24 and 10.96.0.0/11 are missing the "via" 
gateway address, and therefore don't work.
  (For some reason there are also static routes created for DNS server 
(8.8.8.8) and known gateways (10.10.1.1 and 10.10.1.2). These are redundant but 
harmless.)

  Both the working and non-working systems are being managed by netplan.
  The non-working system has a bonded interface but I have checked that
  is not the cause of the problem - using a physical interface directly
  has the same result.

  I have attached the files /etc/netplan/00-installer-config.yaml and
  /run/systemd/network/10-netplan-bond0.network of the affected system.

  Affected system:
  Ubuntu version: Ubuntu 22.04.2 LTS
  systemd version: 249.11-0ubuntu3.6

  Older system not affected:
  Ubuntu version: Ubuntu 20.04.5 LTS
  systemd version: 245.4-4ubuntu3.19

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


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


[Touch-packages] [Bug 2026230] Re: error when setting up after upgrading

2023-07-06 Thread Danilo Egea Gondolfo
So,

the problem appears to be the value of "cloned-mac-address". Netplan
only accepts a MAC address, but Network Manager also supports some
special settings ("preserve", "permanent", "random" and "stable").

I prepared a fix for that https://github.com/canonical/netplan/pull/376

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: netplan.io (Ubuntu)
   Status: New => In Progress

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

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => High

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

Title:
  error when setting up after upgrading

Status in netplan.io package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  I received an error from apport about a programme not working. I
  collected the data to submit. Hope this helps.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.42.6-2ubuntu1
  Uname: Linux 6.2.0-24-generic x86_64
  Architecture: amd64
  Date: Wed Jul  5 23:11:14 2023
  ExecutablePath: /usr/sbin/NetworkManager
  ExecutableTimestamp: 1687429583
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: network-manager
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2026230/+subscriptions


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


[Touch-packages] [Bug 2025563] Re: System can not shutdown if system has multiple VROC RAID arrays

2023-07-06 Thread Nick Rosbrook
Yes, there are a couple low priority things pending for SRU on Jammy, so
I would like to bundle those things eventually.

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

Title:
  System can not shutdown if system has multiple VROC RAID arrays

Status in OEM Priority Project:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  New
Status in systemd source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  The system can not shutdown if the system has multiple VROC RAID arrays.
  Intel has fixed it in systemd v251 [1]. 
  Need to cherry-pick the commit to ubuntu-jammy systemd 249.11-0ubuntu3.9.

  [1] The commit fixes the issue:
  commit 3a3b022d2cc112803ea7b9beea98bbcad110368a
  Author: Mariusz Tkaczyk 
  Date:   Tue Mar 29 12:49:54 2022 +0200

  shutdown: get only active md arrays.
  
  Current md_list_get() implementation filters all block devices, started 
from
  "md*". This is ambiguous because list could contain:
  - partitions created upon md device (mdXpY)
  - external metadata container- specific type of md array.
  
  For partitions there is no issue, because they aren't handle STOP_ARRAY
  ioctl sent later. It generates misleading errors only.
  
  Second case is more problematic because containers are not locked in 
kernel.
  They are stopped even if container member array is active. For that reason
  reboot or shutdown flow could be blocked because metadata manager cannot 
be
  restarted after switch root on shutdown.
  
  Add filters to remove partitions and containers from md_list. Partitions
  can be excluded by DEVTYPE. Containers are determined by MD_LEVEL
  property, we are excluding all with "container" value.
  
  Signed-off-by: Mariusz Tkaczyk 

  
  [ Test Plan ]

  1. Build two VROC RAID. One RAID 0 for System volume, another RAID 10 for 
Data volume.
  2. Install system on System volume.
  3. Update systemd.
  4. Reboot the system.
  5. Verify if the system can reboot.

  [ Where problems could occur ]

  Low, upstream fix.

  [ Scope ]

  Jammy

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


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


[Touch-packages] [Bug 1885313] Re: evince crashes when opening rfc8798.pdf

2023-07-06 Thread Bug Watch Updater
** Changed in: poppler (Debian)
   Status: Confirmed => Fix Released

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

Title:
  evince crashes when opening rfc8798.pdf

Status in poppler package in Ubuntu:
  Fix Released
Status in poppler package in Debian:
  Fix Released

Bug description:
  evince reproducabely crashes when opening the file rfc8798.pdf from
  https://www.rfc-editor.org/rfc/rfc8798.pdf:

  $ evince --version
  GNOME Document Viewer 3.28.4
  $ evince rfc8798.pdf
  Segmentation fault (core dumped)
  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"

  Required information:

  1) Ubuntu release info:
  $ lsb_release -rd
  Description:Ubuntu 18.04.4 LTS
  Release:18.04

  2) Package version info:
  $ apt-cache policy evince
  evince:
Installed: 3.28.4-0ubuntu1.2
Candidate: 3.28.4-0ubuntu1.2
Version table:
   *** 3.28.4-0ubuntu1.2 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) Expected outcome:
  I expected evince to successfully open the PDF, allowing me to read the 
document.

  4) Observed behavior:
  The default PDF reader of Ubuntu, evince, crashed (reporting a "segmentation 
fault".

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


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


[Touch-packages] [Bug 1996437] Re: TagLib 1.13 is available

2023-07-06 Thread Hans Joachim Desserud
The Ubuntu delta seems to have been sorted out for this package and 1.13
will be in the upcoming Ubuntu Mantic
https://bugs.launchpad.net/ubuntu/+source/taglib/1.13-2

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

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

Title:
  TagLib 1.13 is available

Status in taglib package in Ubuntu:
  Fix Released

Bug description:
  A new release 1.13 of TagLib is available and a Debian package already
  exists at https://packages.debian.org/source/bookworm/taglib. It would
  be nice to also have a corresponding Ubuntu package.

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


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


[Touch-packages] [Bug 2025458] Re: SRU: rebuild libunwind with GCC 11.4

2023-07-06 Thread Matthias Klose
the package successfully built. All the autopkg tests from the previous
comment have been retried and succeeded.


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

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

Title:
  SRU: rebuild libunwind with GCC 11.4

Status in libunwind package in Ubuntu:
  New
Status in libunwind source package in Jammy:
  Fix Committed

Bug description:
  Reported in LP: #1997161

  after updating GCC 11 in 22.04 LTS to 11.3, and now to 11.4, linking
  with the static libraries provided by libunwind-dev fails with:

  lto1: fatal error: bytecode stream in file '/usr/lib/gcc/x86_64-linux-
  gnu/11/../../../x86_64-linux-gnu/libunwind-x86_64.a' generated with
  LTO version 11.2 instead of the expected 11.3

  This happens, because gcc-11 bumped the LTO version in 11.3
  (11.3.0-1ubuntu1~22.04), plus the static libraries are not stripped in
  the packaging.

  Fixes could be to change the packaging, disable the LTO build for the
  package, or just rebuild with the new compiler.

  For 22.04 LTS, the least invasive action seems to be the no-change
  rebuild.

  To verify the packages: check that the package builds with the correct
  compiler version, and that the tests succeed during the build.

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


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


[Touch-packages] [Bug 2025563] Re: System can not shutdown if system has multiple VROC RAID arrays

2023-07-06 Thread Simon Chopin
Hi,

Thanks for the patch. I took care of the LP metadata for the bug
(targetting the proper series), and unsubscribe ubuntu-sponsors since
it's not ready for upload yet. Please resubscribe ubuntu-sponsors once
you feel it's ready for upload.

@enr0n can you chime in on this, do we have things pending for a Jammy
SRU on systemd?

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

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

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

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

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

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

Title:
  System can not shutdown if system has multiple VROC RAID arrays

Status in OEM Priority Project:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  New
Status in systemd source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  The system can not shutdown if the system has multiple VROC RAID arrays.
  Intel has fixed it in systemd v251 [1]. 
  Need to cherry-pick the commit to ubuntu-jammy systemd 249.11-0ubuntu3.9.

  [1] The commit fixes the issue:
  commit 3a3b022d2cc112803ea7b9beea98bbcad110368a
  Author: Mariusz Tkaczyk 
  Date:   Tue Mar 29 12:49:54 2022 +0200

  shutdown: get only active md arrays.
  
  Current md_list_get() implementation filters all block devices, started 
from
  "md*". This is ambiguous because list could contain:
  - partitions created upon md device (mdXpY)
  - external metadata container- specific type of md array.
  
  For partitions there is no issue, because they aren't handle STOP_ARRAY
  ioctl sent later. It generates misleading errors only.
  
  Second case is more problematic because containers are not locked in 
kernel.
  They are stopped even if container member array is active. For that reason
  reboot or shutdown flow could be blocked because metadata manager cannot 
be
  restarted after switch root on shutdown.
  
  Add filters to remove partitions and containers from md_list. Partitions
  can be excluded by DEVTYPE. Containers are determined by MD_LEVEL
  property, we are excluding all with "container" value.
  
  Signed-off-by: Mariusz Tkaczyk 

  
  [ Test Plan ]

  1. Build two VROC RAID. One RAID 0 for System volume, another RAID 10 for 
Data volume.
  2. Install system on System volume.
  3. Update systemd.
  4. Reboot the system.
  5. Verify if the system can reboot.

  [ Where problems could occur ]

  Low, upstream fix.

  [ Scope ]

  Jammy

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


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


[Touch-packages] [Bug 2018342] Re: Undefined symbol nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation

2023-07-06 Thread Torben Hansing
I've created an issue at nghttp2 for this, as I think, they should have
incremented the version of the shared object library, when they added
this new function to the interface.

https://github.com/nghttp2/nghttp2/issues/1922

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

Title:
  Undefined symbol
  nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  I updated Ubuntu from 22.10 to 23.04 this morning and have this issue
  when NetworkManager starts :

  > NetworkManager: symbol lookup error: /lib/x86_64-linux-gnu/libcurl-
  gnutls.so.4: undefined symbol:
  nghttp2_option_set_no_rfc9113_leading_and_trailing_ws_validation

  I tried to remove/reinstall libcurl and network-manager and all
  dependencies.

  I created this ticket on the Curl repo :
  https://github.com/curl/curl/tree/d8df0d6db7441b6e14920a7e16a10e32bdc9c7ae

  It was close because :

  > This is not a curl bug. This is libcurl having been built with an
  nghttp2 version >= 1.50.0 (which has that function) and then at run-
  time it uses an older nghttp2 library that doesn't have the function.

  Versions :

  libcurl4 : 7.88.1-8ubuntu1
  libcurl3-gnu-tls : 7.88.1-8ubuntu1
  libnghttp2-dev : 1.52.0-1
  libnghttp2-14 : 1.52.0-1
  network-manager : 1.42.4
  operating system : Linux ubuntu 6.2.0-20-generic #20-Ubuntu SMP 
PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

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


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


[Touch-packages] [Bug 1576524] Re: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2023-07-06 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

update-initramfs: Generating /boot/initrd.img-4.4.0-21-generic
cp: cannot stat '/etc/modprobe.d/nvidia-graphics-drivers.conf': No such file or 
directory
E: /usr/share/initramfs-tools/hooks/copy-nvidia-options failed with return 1.

Since this was a transient error, let's close this bug.

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package initramfs-tools 0.122ubuntu8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  It might have to do with installing nvidia-364 from the graphics diver
  PPA.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Thu Apr 28 22:59:47 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-28 (0 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 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/1576524/+subscriptions


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


[Touch-packages] [Bug 1576762] Re: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2023-07-06 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

E: No boot partition found !

The df log shows that no /boot partition is mounted. Can you check if
you have a separate boot partition and mount it?

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package initramfs-tools 0.122ubuntu8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  just updating ubuntu mate, then this erroe occured

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8
  Uname: Linux 3.4.108 armv7l
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: armhf
  Date: Fri Apr 29 17:14:59 2016
  DuplicateSignature: package:initramfs-tools:0.122ubuntu8:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-29 (0 days ago)
  mtime.conffile..etc.initramfs.tools.initramfs.conf: 2016-02-21T22:22:01

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


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


[Touch-packages] [Bug 1560420] Re: package linux-image-extra-4.2.0-33-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-07-06 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. df log says:

Bestandssysteem 1K-blokken   Gebruikt Beschikbaar Geb% Aangekoppeld op
/dev/sda1   240972 240972   0 100% /boot

So generating the initramfs fails because your boot partition is full.
Please cleanup your boot partition. Feel free to continue to report any
other bugs you may find.


** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

** Summary changed:

- package linux-image-extra-4.2.0-33-generic (not installed) failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
+ package linux-image-extra-4.2.0-33-generic (not installed) failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1 -> boot partition full

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

Title:
  package linux-image-extra-4.2.0-33-generic (not installed) failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1 -> boot partition full

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  After update the system by terminal and executing autoremove, I
  rebooted the system and this error appeared

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-image-extra-4.2.0-33-generic (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  AptOrdering:
   libllvm3.6v5: Remove
   linux-image-extra-4.2.0-33-generic: Remove
   linux-image-4.2.0-33-generic: Remove
   initramfs-tools: Configure
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eluxzen3572 F pulseaudio
  Date: Tue Mar 22 11:00:39 2016
  DuplicateSignature: package:linux-image-extra-4.2.0-33-generic:(not 
installed):run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return 
code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=be5ce25d-e97e-4617-bf87-464ff474022a
  InstallationDate: Installed on 2016-03-09 (12 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: TOSHIBA SATELLITE U920T
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-35-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-29ubuntu0.3
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.2.0-33-generic (not installed) failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UdevLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/27/2013
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.50
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE U920T
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.50:bd09/27/2013:svnTOSHIBA:pnSATELLITEU920T:pvrPSUL1E-00U00HDU:rvnTOSHIBA:rnSATELLITEU920T:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: SATELLITE U920T
  dmi.product.version: PSUL1E-00U00HDU
  dmi.sys.vendor: TOSHIBA

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


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


[Touch-packages] [Bug 1557832] Re: package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2023-07-06 Thread Benjamin Drung
*** This bug is a duplicate of bug 1547505 ***
https://bugs.launchpad.net/bugs/1547505

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

sed: can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-
text.plymouth: No such file or directory

This particular bug has already been reported and is a duplicate of bug
#1547505, so it is being marked as such. Please look at the other bug
report to see if there is any missing information that you can provide,
or to see if there is a workaround for the bug. Additionally, any
further discussion regarding the bug should occur in the other report.
Feel free to continue to report any other bugs you may find.

** This bug has been marked a duplicate of bug 1547505
   package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> 
can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

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

Title:
  package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Upgrade failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  manikandan   1720 F pulseaudio
  Date: Wed Mar 16 00:47:29 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=5aabdff4-e27c-492a-8284-6f4c80f62eb1
  InstallationDate: Installed on 2015-06-15 (274 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 4186
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=263a978e-0c3b-4cb9-9309-8fc7696baf7c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-03-16 (0 days ago)
  dmi.bios.date: 03/15/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 15CN35WW(V2.08)
  dmi.board.name: KIWB1
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr15CN35WW(V2.08):bd03/15/2010:svnLENOVO:pn4186:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 4186
  dmi.product.version: Lenovo IdeaPad Y550
  dmi.sys.vendor: LENOVO

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


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


[Touch-packages] [Bug 1557928] Re: package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2023-07-06 Thread Benjamin Drung
*** This bug is a duplicate of bug 1547505 ***
https://bugs.launchpad.net/bugs/1547505

** This bug is no longer a duplicate of bug 1557832
   package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
** This bug has been marked a duplicate of bug 1547505
   package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> 
can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

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

Title:
  package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Mar 16 00:26:05 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=5c77a969-7f91-4248-ba92-bde1e5aa245d
  InstallationDate: Installed on 2016-03-16 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 2516:0009  
   Bus 001 Device 002: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation STK1AW32SC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic.efi.signed 
root=UUID=543df7a3-758c-4ba1-a0a3-f3403c518e51 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-03-16 (0 days ago)
  dmi.bios.date: 11/19/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SCCHTAX5.86A.0014.2015.1119.1410
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H91596-202
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSCCHTAX5.86A.0014.2015.1119.1410:bd11/19/2015:svnIntelCorporation:pnSTK1AW32SC:pvrH93322-102:rvnIntelCorporation:rnCherryTrailCR:rvrH91596-202:cvnIntelCorporation:ct3:cvr1.0:
  dmi.product.name: STK1AW32SC
  dmi.product.version: H93322-102
  dmi.sys.vendor: Intel Corporation

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


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


[Touch-packages] [Bug 1553744] Re: package linux-image-4.4.0-10-generic 4.4.0-10.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2023-07-06 Thread Benjamin Drung
*** This bug is a duplicate of bug 1547505 ***
https://bugs.launchpad.net/bugs/1547505

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

sed: não foi possível ler /usr/share/plymouth/themes/ubuntu-text/ubuntu-
text.plymouth: Arquivo ou diretório não encontrado

This particular bug has already been reported and is a duplicate of bug
#1547505, so it is being marked as such. Please look at the other bug
report to see if there is any missing information that you can provide,
or to see if there is a workaround for the bug. Additionally, any
further discussion regarding the bug should occur in the other report.
Feel free to continue to report any other bugs you may find.

** This bug has been marked a duplicate of bug 1547505
   package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> 
can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

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

Title:
  package linux-image-4.4.0-10-generic 4.4.0-10.25 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I've installed a fresh new Ubuntu 15.10 AMD64, because I couldn’t install 
directly the 16.04.
  after do a: sudo update-manager -d, the system started to upgrade. some 
packages shows up messages of installation errors. It says kernel isn’t 
functional. Ubuntu 15.10 to 16.04 (AMD A10 7850 APU with a R9 290 graphic card).
  the installation sttoped and system just got unusable.
  Looks like ubuntu 16.04 cant be installed as UEFI, as ubuntu 15.10 can.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zhe1403 F pulseaudio
   /dev/snd/controlC0:  zhe1403 F pulseaudio
   /dev/snd/controlC2:  zhe1403 F pulseaudio
  Date: Sun Mar  6 12:36:46 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=614b6ea9-83ad-4c8a-a581-03bcf289e06e
  InstallationDate: Installed on 2016-03-06 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7900
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=d8cd991e-7ac6-4097-b3cc-775150407e05 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-10-generic 4.4.0-10.25 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-03-06 (0 days ago)
  dmi.bios.date: 01/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88X-G45 GAMING (MS-7900)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd01/12/2016:svnMSI:pnMS-7900:pvr1.0:rvnMSI:rnA88X-G45GAMING(MS-7900):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7900
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


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


[Touch-packages] [Bug 1553749] Re: package linux-image-generic 4.4.0.10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2023-07-06 Thread Benjamin Drung
*** This bug is a duplicate of bug 1547505 ***
https://bugs.launchpad.net/bugs/1547505

** This bug is no longer a duplicate of bug 1553744
   package linux-image-4.4.0-10-generic 4.4.0-10.25 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
** This bug has been marked a duplicate of bug 1547505
   package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> 
can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

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

Title:
  package linux-image-generic 4.4.0.10.11 failed to install/upgrade:
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return
  code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  upgrading from 15.10 with latest update software ( after do a apt-get
  update && sudo apt-get upgrade).

  I got 5 or more errors in sequence.

  I'll try to install manually other kernel.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.10.11
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zhe1403 F pulseaudio
   /dev/snd/controlC0:  zhe1403 F pulseaudio
   /dev/snd/controlC2:  zhe1403 F pulseaudio
  Date: Sun Mar  6 12:37:12 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=614b6ea9-83ad-4c8a-a581-03bcf289e06e
  InstallationDate: Installed on 2016-03-06 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7900
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=d8cd991e-7ac6-4097-b3cc-775150407e05 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-generic 4.4.0.10.11 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
  UpgradeStatus: Upgraded to xenial on 2016-03-06 (0 days ago)
  dmi.bios.date: 01/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88X-G45 GAMING (MS-7900)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd01/12/2016:svnMSI:pnMS-7900:pvr1.0:rvnMSI:rnA88X-G45GAMING(MS-7900):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7900
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


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


[Touch-packages] [Bug 1554726] Re: package linux-image-4.4.0-11-generic 4.4.0-11.26 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2023-07-06 Thread Benjamin Drung
*** This bug is a duplicate of bug 1547505 ***
https://bugs.launchpad.net/bugs/1547505

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

sed: kann /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
nicht lesen: Datei oder Verzeichnis nicht gefunden

This particular bug has already been reported and is a duplicate of bug
#1547505, so it is being marked as such. Please look at the other bug
report to see if there is any missing information that you can provide,
or to see if there is a workaround for the bug. Additionally, any
further discussion regarding the bug should occur in the other report.
Feel free to continue to report any other bugs you may find.

** This bug has been marked a duplicate of bug 1547505
   package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> 
can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

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

Title:
  package linux-image-4.4.0-11-generic 4.4.0-11.26 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Error occured during system update from 15.10 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-11-generic 4.4.0-11.26
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  system 1745 F pulseaudio
  Date: Tue Mar  8 21:46:53 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=b7e7a28f-075a-42e3-ad1e-db34d85756e3
  InstallationDate: Installed on 2012-06-22 (1355 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC210/NC110
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=71292b41-3724-460b-a4fc-603f5ef4dc8f ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-11-generic 4.4.0-11.26 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-03-08 (0 days ago)
  dmi.bios.date: 07/04/2011
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 01VG.M013.20110704.RHU
  dmi.board.asset.tag: SAMSUNG
  dmi.board.name: NC210/NC110
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr01VG.M013.20110704.RHU:bd07/04/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC210/NC110:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC210/NC110:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC210/NC110
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


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


[Touch-packages] [Bug 1553746] Re: package linux-image-extra-4.4.0-10-generic 4.4.0-10.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2023-07-06 Thread Benjamin Drung
*** This bug is a duplicate of bug 1547505 ***
https://bugs.launchpad.net/bugs/1547505

** This bug is no longer a duplicate of bug 1553744
   package linux-image-4.4.0-10-generic 4.4.0-10.25 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
** This bug has been marked a duplicate of bug 1547505
   package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> 
can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

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

Title:
  package linux-image-extra-4.4.0-10-generic 4.4.0-10.25 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  system showed some 5 or 6 kernel errors upgrade messages. 
  All of the in sequence.
  I was upgrading from a 15.10 fresh installation to 16.04.
  the message after all upgrade process was: 
  the upgrade was cancelled. Your system can be unsusable. A recuperation 
process will be run now ( dpkg --configure -a)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zhe1403 F pulseaudio
   /dev/snd/controlC0:  zhe1403 F pulseaudio
   /dev/snd/controlC2:  zhe1403 F pulseaudio
  Date: Sun Mar  6 12:37:12 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=614b6ea9-83ad-4c8a-a581-03bcf289e06e
  InstallationDate: Installed on 2016-03-06 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7900
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=d8cd991e-7ac6-4097-b3cc-775150407e05 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-10-generic 4.4.0-10.25 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-03-06 (0 days ago)
  dmi.bios.date: 01/12/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88X-G45 GAMING (MS-7900)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd01/12/2016:svnMSI:pnMS-7900:pvr1.0:rvnMSI:rnA88X-G45GAMING(MS-7900):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7900
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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


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


[Touch-packages] [Bug 1557686] Re: package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2023-07-06 Thread Benjamin Drung
*** This bug is a duplicate of bug 1547505 ***
https://bugs.launchpad.net/bugs/1547505

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

sed: can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-
text.plymouth: No such file or directory

This particular bug has already been reported and is a duplicate of bug
#1547505, so it is being marked as such. Please look at the other bug
report to see if there is any missing information that you can provide,
or to see if there is a workaround for the bug. Additionally, any
further discussion regarding the bug should occur in the other report.
Feel free to continue to report any other bugs you may find.

** This bug has been marked a duplicate of bug 1547505
   package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> 
can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

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

Title:
  package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  During apt-get dist-upgrade, having already been updated to 16.04.

  Current:  4.2.0-19-generic #23-Ubuntu SMP Wed Nov 11 11:39:30 UTC 2015
  x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-13-generic 4.4.0-13.29
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  alvinc 1927 F pulseaudio
   /dev/snd/controlC2:  alvinc 1927 F pulseaudio
   /dev/snd/controlC1:  alvinc 1927 F pulseaudio
   /dev/snd/controlC0:  alvinc 1927 F pulseaudio
  Date: Tue Mar 15 10:51:48 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=04466c16-d992-47bf-a017-5874ba5a849a
  InstallationDate: Installed on 2013-11-16 (850 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=af24dc68-49e1-4fc0-8a01-9f4bfe3421de ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-13-generic 4.4.0-13.29 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2015-11-28 (107 days ago)
  dmi.bios.date: 10/08/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2701
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M3A78-EM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2701:bd10/08/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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


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


[Touch-packages] [Bug 1556524] Re: package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2023-07-06 Thread Benjamin Drung
*** This bug is a duplicate of bug 1547505 ***
https://bugs.launchpad.net/bugs/1547505

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

sed: can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-
text.plymouth: No such file or directory

This particular bug has already been reported and is a duplicate of bug
#1547505, so it is being marked as such. Please look at the other bug
report to see if there is any missing information that you can provide,
or to see if there is a workaround for the bug. Additionally, any
further discussion regarding the bug should occur in the other report.
Feel free to continue to report any other bugs you may find.

** This bug has been marked a duplicate of bug 1547505
   package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> 
can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

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

Title:
  package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Hi guys, this happens when I was trying to upgrade from 15.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-12-generic 4.4.0-12.28
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xyh1581 F pulseaudio
  Date: Sat Mar 12 23:42:24 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=f9051acb-2e83-48a9-baaf-c901618724b4
  InstallationDate: Installed on 2016-03-12 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 4290AG3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-12-generic 
root=UUID=492bb13e-1f78-46f4-bc1c-bec60bf5cd81 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-03-13 (0 days ago)
  dmi.bios.date: 05/31/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET47WW (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4290AG3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET47WW(1.17):bd05/31/2011:svnLENOVO:pn4290AG3:pvrThinkPadX220:rvnLENOVO:rn4290AG3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4290AG3
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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


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


[Touch-packages] [Bug 1556654] Re: package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2023-07-06 Thread Benjamin Drung
*** This bug is a duplicate of bug 1547505 ***
https://bugs.launchpad.net/bugs/1547505

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

sed: can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-
text.plymouth: No such file or directory

This particular bug has already been reported and is a duplicate of bug
#1547505, so it is being marked as such. Please look at the other bug
report to see if there is any missing information that you can provide,
or to see if there is a workaround for the bug. Additionally, any
further discussion regarding the bug should occur in the other report.
Feel free to continue to report any other bugs you may find.

** This bug has been marked a duplicate of bug 1547505
   package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> 
can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

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

Title:
  package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  after upgrade from 15.10 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-12-generic 4.4.0-12.28
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  markmckinnon   2676 F pulseaudio
   /dev/snd/controlC2:  markmckinnon   2676 F pulseaudio
   /dev/snd/controlC0:  markmckinnon   2676 F pulseaudio
  Date: Sun Mar 13 11:25:51 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=fc7478c2-3968-4d60-a931-099d2584b22b
  InstallationDate: Installed on 2016-03-03 (10 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
   
   tun0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-12-generic 4.4.0-12.28 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-03-13 (0 days ago)
  dmi.bios.date: 05/28/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd05/28/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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


[Touch-packages] [Bug 1550472] Re: package linux-image-4.4.0-7-generic 4.4.0-7.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2023-07-06 Thread Benjamin Drung
*** This bug is a duplicate of bug 1547505 ***
https://bugs.launchpad.net/bugs/1547505

** This bug is no longer a duplicate of bug 1550321
   package linux-image-4.4.0-7-generic 4.4.0-7.22 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

** This bug has been marked a duplicate of bug 1547505
   package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> 
can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

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

Title:
  package linux-image-4.4.0-7-generic 4.4.0-7.22 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This happened for me on a do-release-upgrade from Wily to Xenial. The
  Wily install was fresh today.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-7-generic 4.4.0-7.22
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1566 F pulseaudio
  Date: Fri Feb 26 13:38:45 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=27d2ce07-7815-4c49-808a-ee2fd8cef2a4
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=aff9298e-0673-497f-ac95-3c07c8979b29 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-7-generic 4.4.0-7.22 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-02-26 (0 days ago)
  dmi.bios.date: 12/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: M3A-GLAN
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd12/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A-GLAN:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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


[Touch-packages] [Bug 1550321] Re: package linux-image-4.4.0-7-generic 4.4.0-7.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2023-07-06 Thread Benjamin Drung
*** This bug is a duplicate of bug 1547505 ***
https://bugs.launchpad.net/bugs/1547505

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

sed: can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-
text.plymouth: No such file or directory

This is a duplicate of bug #1547505.

** This bug has been marked a duplicate of bug 1547505
   package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> 
can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

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

Title:
  package linux-image-4.4.0-7-generic 4.4.0-7.22 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  This occurred when trying to upgrade from 15.10 to 16.04 beta 2.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-7-generic 4.4.0-7.22
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic i686
  ApportVersion: 2.20-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mike   1844 F pulseaudio
  Date: Fri Feb 26 12:06:52 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=fca52877-4cd9-49c5-bda2-347ce230d633
  InstallationDate: Installed on 2016-02-15 (10 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp2s0no wireless extensions.
  MachineType: Dell Inc. OptiPlex GX520
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic 
root=UUID=df05bac8-06c3-4efa-b757-814324a48b72 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-7-generic 4.4.0-7.22 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-02-26 (0 days ago)
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0XG309
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX520:pvr:rvnDellInc.:rn0XG309:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX520
  dmi.sys.vendor: Dell Inc.

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


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


[Touch-packages] [Bug 1552381] Re: package linux-image-4.4.0-9-generic 4.4.0-9.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2023-07-06 Thread Benjamin Drung
*** This bug is a duplicate of bug 1547505 ***
https://bugs.launchpad.net/bugs/1547505

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

sed: can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-
text.plymouth: No such file or directory

This particular bug has already been reported and is a duplicate of bug
#1547505, so it is being marked as such. Please look at the other bug
report to see if there is any missing information that you can provide,
or to see if there is a workaround for the bug. Additionally, any
further discussion regarding the bug should occur in the other report.
Feel free to continue to report any other bugs you may find.

** This bug has been marked a duplicate of bug 1547505
   package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> 
can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

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

Title:
  package linux-image-4.4.0-9-generic 4.4.0-9.24 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Issue appeared during update from 15.10.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-9-generic 4.4.0-9.24
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kostas 2315 F pulseaudio
  Date: Wed Mar  2 14:44:20 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=ab442bbf-edfd-449d-9458-6cf581dba71c
  InstallationDate: Installed on 2015-09-22 (161 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Sony Corporation VPCEB47GM
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9-generic 
root=UUID=9b4e2dea-1cf8-484d-acce-a942293c8ce3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-9-generic 4.4.0-9.24 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-03-02 (0 days ago)
  dmi.bios.date: 01/28/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1170Y8
  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:bvnAmericanMegatrendsInc.:bvrR1170Y8:bd01/28/2011:svnSonyCorporation:pnVPCEB47GM:pvrC608NENQ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCEB47GM
  dmi.product.version: C608NENQ
  dmi.sys.vendor: Sony Corporation

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


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


[Touch-packages] [Bug 1521432] Re: package linux-image-4.2.0-19-generic 4.2.0-19.23 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-07-06 Thread Benjamin Drung
The df log does not show any mounted /boot partition. Can you check if
you have a separate boot partition and mount that?

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

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

Title:
  package linux-image-4.2.0-19-generic 4.2.0-19.23 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  I was watching youtube videos when I was notified of this problem.
  I cannot provide you any useful information a this time.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   uaran  1825 F...m pulseaudio
   /dev/snd/controlC0:  uaran  1825 F pulseaudio
  Date: Mon Nov 30 17:42:58 2015
  DuplicateSignature: 
package:linux-image-4.2.0-19-generic:4.2.0-19.23:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=3772b7fc-c846-42d8-98d9-02c4e03f3cfd
  InstallationDate: Installed on 2015-10-31 (30 days ago)
  InstallationMedia: JULinux10x86_RC1 14.04 - Release i386
  MachineType: Acer Aspire 5610Z
  PccardctlIdent:
   Socket 0:
 product info: "SCR243 PCMCIA
   ", "Smart Card Reader
   ", "", ""
 manfid: 0x, 0x0001
  PccardctlStatus:
   Socket 0:
 5.0V
16-bit
PC Card
 Subdevice 0 (function 0) [unbound]
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=643b6563-233a-47c9-a14d-deea0f26d879 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-29
  SourcePackage: initramfs-tools
  Title: package linux-image-4.2.0-19-generic 4.2.0-19.23 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to wily on 2015-11-01 (29 days ago)
  dmi.bios.date: 01/09/2007
  dmi.bios.vendor: Acer
  dmi.bios.version: V3.33
  dmi.board.name: Grapevine
  dmi.board.vendor: Acer
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV3.33:bd01/09/2007:svnAcer:pnAspire5610Z:pvrV3.33:rvnAcer:rnGrapevine:rvrN/A:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5610Z
  dmi.product.version: V3.33
  dmi.sys.vendor: Acer

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


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


[Touch-packages] [Bug 1547505] Re: package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2023-07-06 Thread Benjamin Drung
** Description changed:

  error occurred while updating from 15.10 to 16.04
+ 
+ dpkg terminal log:
+ 
+ update-initramfs: Generating /boot/initrd.img-4.4.0-6-generic
+ sed: can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth: 
No such file or directory
+ E: /usr/share/initramfs-tools/hooks/plymouth failed with return 2.
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-6-generic 4.4.0-6.21
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  naveen 1479 F pulseaudio
-  /dev/snd/controlC1:  naveen 1479 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  naveen 1479 F pulseaudio
+  /dev/snd/controlC1:  naveen 1479 F pulseaudio
  CRDA:
-  country IN: DFS-JP
-   (2402 - 2482 @ 40), (N/A, 20), (N/A)
-   (5170 - 5250 @ 80), (N/A, 20), (N/A)
-   (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
-   (5735 - 5835 @ 80), (N/A, 20), (N/A)
+  country IN: DFS-JP
+   (2402 - 2482 @ 40), (N/A, 20), (N/A)
+   (5170 - 5250 @ 80), (N/A, 20), (N/A)
+   (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
+   (5735 - 5835 @ 80), (N/A, 20), (N/A)
  Date: Fri Feb 19 18:20:10 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=d9abc4f7-9e91-4ecd-842c-097a41546ed3
  InstallationDate: Installed on 2015-12-13 (68 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 021: ID 04f3:0447 Elan Microelectronics Corp. 
-  Bus 001 Device 002: ID 0bda:579c Realtek Semiconductor Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 021: ID 04f3:0447 Elan Microelectronics Corp.
+  Bus 001 Device 002: ID 0bda:579c Realtek Semiconductor Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20404
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic.efi.signed 
root=UUID=38b413f2-788a-4715-895f-8dae3d2bb707 ro noprompt persistent quiet 
splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-02-19 (0 days ago)
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A0CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Flex 2-14
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900059 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Flex 2-14
  dmi.modalias: 
dmi:bvnLENOVO:bvrA0CN31WW:bd10/08/2014:svnLENOVO:pn20404:pvrLenovoFlex2-14:rvnLENOVO:rnLenovoFlex2-14:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoFlex2-14:
  dmi.product.name: 20404
  dmi.product.version: Lenovo Flex 2-14
  dmi.sys.vendor: LENOVO

** Summary changed:

- package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
+ package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> 
can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

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

Title:
  package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2 -> can't read
  /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  error occurred while updating from 15.10 to 16.04

  dpkg terminal log:

  update-initramfs: Generating /boot/initrd.img-4.4.0-6-generic
  sed: can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth: 
No such file or directory
  E: /usr/share/initramfs-tools/hooks/plymouth failed with return 2.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-6-generic 4.4.0-6.21
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  

[Touch-packages] [Bug 1549292] Re: package linux-image-4.4.0-7-generic 4.4.0-7.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

2023-07-06 Thread Benjamin Drung
*** This bug is a duplicate of bug 1547505 ***
https://bugs.launchpad.net/bugs/1547505

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

sed: no se puede leer /usr/share/plymouth/themes/ubuntu-text/ubuntu-
text.plymouth: No existe el archivo o el directorio

This is a duplicate of bug #1547505.

** This bug has been marked a duplicate of bug 1547505
   package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> 
can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth

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

Title:
  package linux-image-4.4.0-7-generic 4.4.0-7.22 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  i dont know what is going on

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-7-generic 4.4.0-7.22
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ingjulianparra   1484 F pulseaudio
   /dev/snd/controlC0:  ingjulianparra   1484 F pulseaudio
  Date: Wed Feb 24 09:10:51 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=34e4498e-f910-4a8b-ba96-0a8af0f99a30
  InstallationDate: Installed on 2016-02-07 (16 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Inspiron 3537
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed 
root=UUID=8caa2eae-c7d9-4df9-b152-eb273ab58259 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-7-generic 4.4.0-7.22 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  UpgradeStatus: Upgraded to xenial on 2016-02-24 (0 days ago)
  dmi.bios.date: 11/12/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0MJNYC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A07
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/12/2013:svnDellInc.:pnInspiron3537:pvrA07:rvnDellInc.:rn0MJNYC:rvrA00:cvnDellInc.:ct8:cvrA07:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.

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


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


[Touch-packages] [Bug 1512173] Re: package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-07-06 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

E: No boot partition found !

The df log does not show any mounted /boot partition. Can you check if
you have a separate boot partition and mount that?

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  it happened during upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-17-generic 4.2.0-17.21
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cornel 3577 F pulseaudio
   /dev/snd/controlC1:  cornel 3577 F pulseaudio
  Date: Mon Nov  2 00:26:44 2015
  DuplicateSignature: 
package:linux-image-4.2.0-17-generic:4.2.0-17.21:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=834c5503-899e-49e3-8052-23d4eafa3dbf
  InstallationDate: Installed on 2015-10-31 (0 days ago)
  InstallationMedia: It
  MachineType: Acer Aspire E5-572G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=6171c983-bf53-4ca6-8c95-87e101690592 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-29
  SourcePackage: initramfs-tools
  Title: package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago)
  dmi.bios.date: 08/01/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HWS
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd08/01/2014:svnAcer:pnAspireE5-572G:pvrV1.02:rvnAcer:rnEA50_HWS:rvrV1.02:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-572G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

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


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


[Touch-packages] [Bug 1499173] Re: package initramfs-tools 0.120ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2023-07-06 Thread Benjamin Drung
The JournalErrors.txt show that there were issues with the disk. So
let's assume that this was the cause and close this bug.

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

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

Title:
  package initramfs-tools 0.120ubuntu5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  E: initramfs-tools: subprocess installed post-installation script
  returned error exit status 2

  During regular update via synaptic of 15.10.

  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

Installed: 0.120ubuntu5
Candidate: 0.120ubuntu5
Version table:
   *** 0.120ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: initramfs-tools 0.120ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair spl zavl nvidia
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  Date: Wed Sep 23 23:05:15 2015
  DuplicateSignature: package:initramfs-tools:0.120ubuntu5:subprocess installed 
post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu4
   apt  1.0.9.10ubuntu7
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.120ubuntu5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  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/1499173/+subscriptions


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


[Touch-packages] [Bug 1658519] Re: package linux-image-4.4.0-59-generic 4.4.0-59.80 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-07-06 Thread Benjamin Drung
** Description changed:

-  I don't know
+ dpkg terminal log:
+ 
+ update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
+ cp: impossible d'évaluer 
'/usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif.ttf': Aucun fichier ou 
dossier de ce type
+ E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
+ 
+ translated:
+ 
+ update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
+ cp: unable to evaluate 
'/usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif.ttf': No such file or folder
+ E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  alain  1597 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  alain  1597 F pulseaudio
  Date: Sun Jan 22 21:38:50 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=0f6e45e9-1db8-424f-b077-e221aa9ab057
  InstallationDate: Installed on 2017-01-03 (19 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
-  lono wireless extensions.
-  
-  eth0  no wireless extensions.
+  lono wireless extensions.
+ 
+  eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=c7441fe3-cc4b-485e-9f5a-5934116777fb ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.6
  RfKill:
-  
+ 
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-59-generic 4.4.0-59.80 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2017-01-06 (16 days ago)
  dmi.bios.date: 12/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88X-D3HP
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

Title:
  package linux-image-4.4.0-59-generic 4.4.0-59.80 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  dpkg terminal log:

  update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
  cp: impossible d'évaluer 
'/usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif.ttf': Aucun fichier ou 
dossier de ce type
  E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.

  translated:

  update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
  cp: unable to evaluate 
'/usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif.ttf': No such file or folder
  E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-59-generic 4.4.0-59.80
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alain  1597 F pulseaudio
  Date: Sun Jan 22 21:38:50 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=0f6e45e9-1db8-424f-b077-e221aa9ab057
  InstallationDate: Installed on 2017-01-03 (19 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 

[Touch-packages] [Bug 2021948] Re: New bugfix release 23.0.4

2023-07-06 Thread Timo Aaltonen
Tested on Intel Kaby Lake (gen9) and AMD Radeon W5700 on lunar, no
issues found.


Tested on Intel DG2 (gen12) and AMD Radeon 520 Mobile on jammy, no issues found


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

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

Title:
  New bugfix release 23.0.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed
Status in mesa source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 23.0.x-series, we should put it
  in lunar so latest bugfixes would get there, and in jammy for 22.04.3
  image.

  We'll include an additional bugfix (a revert) to fix GPU hangs on some
  AMD gpu's running certain games.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

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


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


[Touch-packages] [Bug 1647689] Re: package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-07-06 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

cp: error reading '/sbin/e2fsck': Input/output error

dmesg shows:

[39600.144088] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[39600.144097] ata3.00: BMDMA stat 0x24
[39600.144103] ata3.00: failed command: READ DMA
[39600.144114] ata3.00: cmd c8/00:00:80:fe:b1/00:00:00:00:00/e1 tag 0 dma 
131072 in
res 51/40:00:75:ff:b1/00:00:00:00:00/e1 Emask 0x9 
(media error)
[39600.144120] ata3.00: status: { DRDY ERR }
[39600.144124] ata3.00: error: { UNC }
[39600.255501] ata3.00: configured for UDMA/133
[39600.255532] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[39600.255541] sd 2:0:0:0: [sda] tag#0 Sense Key : Medium Error [current] 
[descriptor] 
[39600.255547] sd 2:0:0:0: [sda] tag#0 Add. Sense: Unrecovered read error - 
auto reallocate failed
[39600.24] sd 2:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 01 b1 fe 80 00 01 00 
00
[39600.255560] blk_update_request: I/O error, dev sda, sector 28442485

So generating the initramfs fails because of your device /dev/sda having
(hardware) problems. Feel free to continue to report any other bugs you
may find.

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

** Summary changed:

- package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
+ package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 -> 
I/O error

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

Title:
  package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1 -> I/O error

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Unable to install the package.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-53-generic 4.4.0-53.74
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  smeet  1817 F pulseaudio
  Date: Tue Dec  6 09:46:25 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=e0452b32-85ea-4b59-8c8a-2a31d97b13c8
  InstallationDate: Installed on 2016-02-03 (306 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: System Manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-53-generic 4.4.0-53.74 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (128 days ago)
  dmi.bios.date: 09/13/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080012
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: LG-95C
  dmi.board.vendor: www.abit.com.tw
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: System Enclosure Manufacturer
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080012:bd09/13/2007:svnSystemManufacturer:pnSystemProductName:pvrSystemVersion:rvnwww.abit.com.tw:rnLG-95C:rvr1.0:cvnSystemEnclosureManufacturer:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System Manufacturer

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


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


[Touch-packages] [Bug 1652516] Re: package linux-image-4.4.0-57-generic 4.4.0-57.78 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139

2023-07-06 Thread Benjamin Drung
The dmesg output says:

[ 1206.213807] sed[6426]: segfault at 7ffe2d4d4ef0 ip 7fee694be94e sp 
7ffe2d5d3e70 error 4 in libc-2.23.so[7fee693e2000+1bf000]
[ 1206.426143] apport-checkrep[6466]: segfault at 10 ip 00553c05 sp 
7ffd7402cac0 error 6 in python3.5[40+3a8000]
[ 1206.430509] apport[6467]: segfault at 8 ip 005e9fee sp 
7ffd89e2b5a0 error 4 in python3.5[40+3a8000]
[ 1206.430521] Process 6467(apport) has RLIMIT_CORE set to 1
[ 1206.430522] Aborting core
[ 1206.617857] plymouth[6477]: segfault at 18 ip 558690a8f417 sp 
7fff9af74240 error 4 in dash[558690a74000+24000]
[ 1206.787584] apport-checkrep[6796]: segfault at 18 ip 0050ee20 sp 
7fff8630eaa8 error 4 in python3.5[40+3a8000]

The failing sed program was probably part of the initramfs-tools run. I
am marking this bug as invalid for initramfs-tools. It is either a
hardware problem or a bug in sed.

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package linux-image-4.4.0-57-generic 4.4.0-57.78 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 139

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  I DON'T KNOW

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jayachitra   1514 F pulseaudio
  Date: Sun Dec 25 19:52:55 2016
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 139
  HibernationDevice: RESUME=UUID=73e2f5bd-93f6-4c8f-aec4-6090372de0b4
  InstallationDate: Installed on 2016-07-28 (149 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic 
root=UUID=1aba02be-eab0-416e-8f86-52396085f8a8 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-57-generic 4.4.0-57.78 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH61HO
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG62445-102
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr:

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


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


[Touch-packages] [Bug 1671392] Re: package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-07-06 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

gzip: stdout: No space left on device

df log says:

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda7 464808   450080 0 100% /boot

So generating the initramfs fails because your boot partition is full.
Please cleanup your boot partition. Feel free to continue to report any
other bugs you may find.


** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

** Summary changed:

- package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
+ package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1 -> boot partition full

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

Title:
  package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1 -> boot partition full

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  After login to ubuntu I'm getting the error as Crash Report and the
  above package is unable to install.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-66-generic 4.4.0-66.87
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  revanth1868 F pulseaudio
  Date: Wed Mar  8 21:22:52 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=77c1c942-aeb9-48c9-81e5-f87ec8d0ddfc
  InstallationDate: Installed on 2016-11-04 (124 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20150
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic 
root=UUID=f83b85c5-66c7-418a-bfc9-0b4f1e06478c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-66-generic 4.4.0-66.87 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN41WW(V4.00)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Mainboard version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN41WW(V4.00):bd12/20/2012:svnLENOVO:pn20150:pvrLenovoG580:rvnLENOVO:rnProductName:rvrMainboardversion:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 20150
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO

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


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


[Touch-packages] [Bug 2024972] Re: package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-07-06 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

zstd: error 25 : Write error : No space left on device (cannot write
compressed block)

df log says:

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 498688   423964   132 100% /boot

So generating the initramfs fails because your boot partition is full.
Please cleanup your boot partition. Feel free to continue to report any
other bugs you may find.

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

** Summary changed:

- package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
+ package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 -> 
boot partition full

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

Title:
  package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1 -> boot partition full

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  bluetooth

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-75-generic 5.15.0-75.82
  ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richard2268 F pulseaudio
   /dev/snd/controlC1:  richard2268 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Sat Jun 17 11:50:04 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2023-02-14 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic 
root=UUID=c4093c70-14d4-4d70-a42a-0b8baa53982c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
  SourcePackage: initramfs-tools
  StagingDrivers: atomisp_gmin_platform atomisp_lm3554
  Title: package linux-image-5.15.0-75-generic 5.15.0-75.82 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2023-02-14 (130 days ago)
  dmi.bios.date: 10/31/2014
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: Q1900-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/31/2014:br5.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQ1900-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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


[Touch-packages] [Bug 2025489] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: el subproceso instalado paquete linux-firmware script post-installation devolvió e

2023-07-06 Thread Benjamin Drung
** Summary changed:

- package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to 
install/upgrade: el subproceso instalado paquete linux-firmware script 
post-installation devolvió el código de salida de error 1
+ package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to 
install/upgrade: el subproceso instalado paquete linux-firmware script 
post-installation devolvió el código de salida de error 1 -> boot partition full

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

Title:
  package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to
  install/upgrade: el subproceso instalado paquete linux-firmware script
  post-installation devolvió el código de salida de error 1 -> boot
  partition full

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Ero

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.13
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ruku   2089 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Jun 30 18:21:10 2023
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.1
  ErrorMessage: el subproceso instalado paquete linux-firmware script 
post-installation devolvió el código de salida de error 1
  InstallationDate: Installed on 2023-06-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: Intel(R) Client Systems NUC12WSHi5
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-46-generic 
root=UUID=7578c75a-4115-4777-87ab-8ea180da082b ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
  SourcePackage: initramfs-tools
  Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to 
install/upgrade: el subproceso instalado paquete linux-firmware script 
post-installation devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2023
  dmi.bios.release: 5.26
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WSADL357.0088.2023.0505.1623
  dmi.board.name: NUC12WSBi5
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M46425-303
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrWSADL357.0088.2023.0505.1623:bd05/05/2023:br5.26:svnIntel(R)ClientSystems:pnNUC12WSHi5:pvrM46655-303:rvnIntelCorporation:rnNUC12WSBi5:rvrM46425-303:cvnIntelCorporation:ct35:cvr2.0:skuNUC12WSHi5000:
  dmi.product.family: WS
  dmi.product.name: NUC12WSHi5
  dmi.product.sku: NUC12WSHi5000
  dmi.product.version: M46655-303
  dmi.sys.vendor: Intel(R) Client Systems

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


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


[Touch-packages] [Bug 2025315] Re: package linux-image-5.15.0-76-generic 5.15.0-76.83 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 -> boot par

2023-07-06 Thread Benjamin Drung
** Summary changed:

- package linux-image-5.15.0-76-generic 5.15.0-76.83 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
+ package linux-image-5.15.0-76-generic 5.15.0-76.83 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 -> 
boot partition full

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

Title:
  package linux-image-5.15.0-76-generic 5.15.0-76.83 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1 -> boot partition full

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  what i have done  is not journal boot file

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-76-generic 5.15.0-76.83
  ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richard2167 F pulseaudio
   /dev/snd/controlC2:  richard2167 F pulseaudio
   /dev/snd/controlC1:  richard2167 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Thu Jun 29 13:36:04 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2023-02-14 (134 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic 
root=UUID=c4093c70-14d4-4d70-a42a-0b8baa53982c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
  SourcePackage: initramfs-tools
  StagingDrivers: atomisp_gmin_platform atomisp_lm3554
  Title: package linux-image-5.15.0-76-generic 5.15.0-76.83 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2023-02-14 (134 days ago)
  dmi.bios.date: 10/31/2014
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: Q1900-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/31/2014:br5.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQ1900-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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


[Touch-packages] [Bug 2025650] Re: package linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1-> b

2023-07-06 Thread Benjamin Drung
** Summary changed:

- package linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
+ package linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1-> boot partition full

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

Title:
  package linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1-> boot partition full

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  On every boot, multiple times

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Jun 30 14:59:50 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-05-28 (765 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2023-04-06 (87 days ago)

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


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


[Touch-packages] [Bug 2024969] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro

2023-07-06 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

df log says:

zstd: error 25 : Write error : No space left on device (cannot write
compressed block)

Filesystem 1K-blocks  Used Available Use% Mounted on
/dev/sda10166760146868  6208  96% /boot

So generating the initramfs fails because your boot partition is full.
Please cleanup your boot partition. Feel free to continue to report any
other bugs you may find.


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

** Summary changed:

- package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to 
install/upgrade: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
+ package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to 
install/upgrade: installed linux-firmware package post-installation script 
subprocess returned error exit status 1 -> boot partition full

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

Title:
  package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to
  install/upgrade: installed linux-firmware package post-installation
  script subprocess returned error exit status 1 -> boot partition full

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  /

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.13
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chuyues1133 F pulseaudio
   /dev/snd/controlC1:  chuyues1133 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Sat Jun 24 17:24:56 2023
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.1
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  MachineType: Alienware Alienware Aurora R12
  PackageArchitecture: all
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=UUID=a089e437-b437-482c-a957-d55995aae5a7 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
  SourcePackage: initramfs-tools
  Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to 
install/upgrade: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2021
  dmi.bios.release: 1.1
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.1.4
  dmi.board.name: 0P0JWX
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.1.4:bd07/08/2021:br1.1:svnAlienware:pnAlienwareAuroraR12:pvr1.1.4:rvnAlienware:rn0P0JWX:rvrA00:cvnAlienware:ct3:cvrNotSpecified:sku0A63:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R12
  dmi.product.sku: 0A63
  dmi.product.version: 1.1.4
  dmi.sys.vendor: Alienware

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


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


[Touch-packages] [Bug 2025315] Re: package linux-image-5.15.0-76-generic 5.15.0-76.83 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-07-06 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

zstd: error 25 : Write error : No space left on device (cannot write
compressed block)

df log says:

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda1 498688   424012   116 100% /boot

So generating the initramfs fails because your boot partition is full.
Please cleanup your boot partition. Feel free to continue to report any
other bugs you may find.

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package linux-image-5.15.0-76-generic 5.15.0-76.83 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  what i have done  is not journal boot file

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-76-generic 5.15.0-76.83
  ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richard2167 F pulseaudio
   /dev/snd/controlC2:  richard2167 F pulseaudio
   /dev/snd/controlC1:  richard2167 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Thu Jun 29 13:36:04 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2023-02-14 (134 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic 
root=UUID=c4093c70-14d4-4d70-a42a-0b8baa53982c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
  SourcePackage: initramfs-tools
  StagingDrivers: atomisp_gmin_platform atomisp_lm3554
  Title: package linux-image-5.15.0-76-generic 5.15.0-76.83 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2023-02-14 (134 days ago)
  dmi.bios.date: 10/31/2014
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: Q1900-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/31/2014:br5.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQ1900-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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


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


[Touch-packages] [Bug 2025445] Re: package initramfs-tools 0.142ubuntu2 failed to install/upgrade: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde 2

2023-07-06 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

update-initramfs: Generating /boot/initrd.img-6.2.0-1004-raspi
/usr/sbin/mkinitramfs: 133: .: cannot open 
/usr/share/initramfs-tools/conf-hooks.d/cryptsetup: No such device or address
update-initramfs: failed for /boot/initrd.img-6.2.0-1004-raspi with 2.

Can you read the content of /usr/share/initramfs-tools/conf-
hooks.d/cryptsetup?

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

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

Title:
  package initramfs-tools 0.142ubuntu2 failed to install/upgrade:
  subproces van pakket initramfs-tools werd script post-installation
  geïnstalleerd gaf de foutwaarde 2 terug

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  RaspberryPi4 (Berryboot Image), this Ubuntu image has some issues by
  updating the system. The graphic update shell always crashed, but I
  used the terminal anyway.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: initramfs-tools 0.142ubuntu2
  Uname: Linux 5.10.43v64 aarch64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Fri Jun 30 09:25:07 2023
  ErrorMessage: subproces van pakket initramfs-tools werd script 
post-installation geïnstalleerd gaf de foutwaarde 2 terug
  ImageMediaBuild: 20230417
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.142ubuntu2 failed to install/upgrade: 
subproces van pakket initramfs-tools werd script post-installation 
geïnstalleerd gaf de foutwaarde 2 terug
  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/2025445/+subscriptions


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


[Touch-packages] [Bug 2025489] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to install/upgrade: el subproceso instalado paquete linux-firmware script post-installation devolvió e

2023-07-06 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

cat: error de escritura: No queda espacio en el dispositivo

(translated: cat: write error: No space left on the device)

So generating the initramfs fails because your boot partition is full.
Please cleanup your boot partition. Feel free to continue to report any
other bugs you may find.

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

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

Title:
  package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to
  install/upgrade: el subproceso instalado paquete linux-firmware script
  post-installation devolvió el código de salida de error 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Ero

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.13
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ruku   2089 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Fri Jun 30 18:21:10 2023
  Dependencies: firmware-sof-signed 2.0-1ubuntu4.1
  ErrorMessage: el subproceso instalado paquete linux-firmware script 
post-installation devolvió el código de salida de error 1
  InstallationDate: Installed on 2023-06-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: Intel(R) Client Systems NUC12WSHi5
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-46-generic 
root=UUID=7578c75a-4115-4777-87ab-8ea180da082b ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
  SourcePackage: initramfs-tools
  Title: package linux-firmware 20220329.git681281e4-0ubuntu3.13 failed to 
install/upgrade: el subproceso instalado paquete linux-firmware script 
post-installation devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2023
  dmi.bios.release: 5.26
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WSADL357.0088.2023.0505.1623
  dmi.board.name: NUC12WSBi5
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M46425-303
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrWSADL357.0088.2023.0505.1623:bd05/05/2023:br5.26:svnIntel(R)ClientSystems:pnNUC12WSHi5:pvrM46655-303:rvnIntelCorporation:rnNUC12WSBi5:rvrM46425-303:cvnIntelCorporation:ct35:cvr2.0:skuNUC12WSHi5000:
  dmi.product.family: WS
  dmi.product.name: NUC12WSHi5
  dmi.product.sku: NUC12WSHi5000
  dmi.product.version: M46655-303
  dmi.sys.vendor: Intel(R) Client Systems

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


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


[Touch-packages] [Bug 2025650] Re: package linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-07-06 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

zstd: error 25 : Write error : No space left on device (cannot write
compressed block)

So generating the initramfs fails because your boot partition is full.
Please cleanup your boot partition. Feel free to continue to report any
other bugs you may find.

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

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

Title:
  package linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  On every boot, multiple times

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Jun 30 14:59:50 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-05-28 (765 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2023-04-06 (87 days ago)

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


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


[Touch-packages] [Bug 2025599] Re: BlueZ release 5.68

2023-07-06 Thread Sebastien Bacher
Thanks Daniel, uploaded

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

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

Title:
  BlueZ release 5.68

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  BlueZ release 5.68 is now available:

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

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


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


[Touch-packages] [Bug 1980805] Re: Backport packages for 20.04.5 HWE stack

2023-07-06 Thread Timo Aaltonen
** Changed in: mesa (Ubuntu Focal)
   Status: New => Won't Fix

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

Title:
  Backport packages for 20.04.5 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-13 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in mesa-amber package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-13 source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Won't Fix
Status in mesa-amber source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: pci-id updates, some minor api updates

  mesa: a new major release, but we'll pull the final stable release of
  22.0.x series, so there shouldn't be any regressions left at that
  point

  mesa-amber: forked from mesa 21.3.x, this LTS branch keeps old DRI
  drivers that were removed from main mesa

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


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


[Touch-packages] [Bug 2026273] [NEW] SRU e2fsprogs v1.47.0 for HWE reasons

2023-07-06 Thread Dimitri John Ledkov
Public bug reported:

[ Impact ]

 * orphan_file ext4 feature is available in Jammy v5.15 GA kernel
 * It is to be enabled by default in Mantic
 * fsck utility in jammy doesn't support orphan_file feature
 * as part of forwards-compatibility support it would be useful for Jammy 22.04 
LTS to be able to fsck future releases (i.e. 23.10 / 24.04)
 * as part of HWE support, users may opt-in and choose to use orphan_file in 
Jammy today, when they do so they currently loose support to fsck a given 
filesystem.

[ Test Plan ]

 * Create new ext4 filesystem with GA version of e2fsprogs and with proposed one
 * Ensure that default feature set enabled is the same (i.e. orphan_file & 
metadata_csum features are OFF)
 * Ensure that either fsck can fsck both filesystems
 * Use tune2fs to enable orphan_file feature
 * Ensure that new fsck can check such a filesystem, and that GA (v5.15) kernel 
can mount it

 * do test rebuilds of reverse-build-depends of e2fsprogs to verify to
change of API and ABI, none should FTBFS and none should gain any new
dependencies on the 1.47 symbols

[ Where problems could occur ]

 * library api/abi changes:

struct ext2_super_block size is unchanged, s_orphan_file_inum consumes
one of the s_reserved fields.

orphan_file related public APIs are added.

 * default features:

Ensure that config files are unchanged, to ensure that no new features
are enabled by default, meaning filesystems created with the upgraded
e2fsprogs in a given Ubuntu release will keep the same feature level.

[ Other Info ]
 
 * Anything else you think is useful to include
 * Anticipate questions from users, SRU, +1 maintenance, security teams and the 
Technical Board
 * and address these questions in advance

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

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

** Affects: e2fsprogs (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

** Affects: e2fsprogs (Ubuntu Lunar)
 Importance: Undecided
 Status: New

** Summary changed:

- SRU e2fsprogs for HWE reasons
+ SRU e2fsprogs v1.47.0 for HWE reasons

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

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

** Also affects: e2fsprogs (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

Title:
  SRU e2fsprogs v1.47.0 for HWE reasons

Status in e2fsprogs package in Ubuntu:
  New
Status in e2fsprogs source package in Jammy:
  New
Status in e2fsprogs source package in Kinetic:
  New
Status in e2fsprogs source package in Lunar:
  New

Bug description:
  [ Impact ]

   * orphan_file ext4 feature is available in Jammy v5.15 GA kernel
   * It is to be enabled by default in Mantic
   * fsck utility in jammy doesn't support orphan_file feature
   * as part of forwards-compatibility support it would be useful for Jammy 
22.04 LTS to be able to fsck future releases (i.e. 23.10 / 24.04)
   * as part of HWE support, users may opt-in and choose to use orphan_file in 
Jammy today, when they do so they currently loose support to fsck a given 
filesystem.

  [ Test Plan ]

   * Create new ext4 filesystem with GA version of e2fsprogs and with proposed 
one
   * Ensure that default feature set enabled is the same (i.e. orphan_file & 
metadata_csum features are OFF)
   * Ensure that either fsck can fsck both filesystems
   * Use tune2fs to enable orphan_file feature
   * Ensure that new fsck can check such a filesystem, and that GA (v5.15) 
kernel can mount it

   * do test rebuilds of reverse-build-depends of e2fsprogs to verify to
  change of API and ABI, none should FTBFS and none should gain any new
  dependencies on the 1.47 symbols

  [ Where problems could occur ]

   * library api/abi changes:

  struct ext2_super_block size is unchanged, s_orphan_file_inum consumes
  one of the s_reserved fields.

  orphan_file related public APIs are added.

   * default features:

  Ensure that config files are unchanged, to ensure that no new features
  are enabled by default, meaning filesystems created with the upgraded
  e2fsprogs in a given Ubuntu release will keep the same feature level.

  [ Other Info ]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance

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


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


[Touch-packages] [Bug 2026230] Re: error when setting up after upgrading

2023-07-06 Thread Danilo Egea Gondolfo
Thank for your bug report.

Based on the core dump you provided, the problem seems to be related to
libnetplan.

Can you collect the NetworkManager's systemd journal and attach to the
ticket, please?

journalctl -u NetworkManager > network-manager.log

Thanks!

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

Title:
  error when setting up after upgrading

Status in network-manager package in Ubuntu:
  New

Bug description:
  I received an error from apport about a programme not working. I
  collected the data to submit. Hope this helps.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.42.6-2ubuntu1
  Uname: Linux 6.2.0-24-generic x86_64
  Architecture: amd64
  Date: Wed Jul  5 23:11:14 2023
  ExecutablePath: /usr/sbin/NetworkManager
  ExecutableTimestamp: 1687429583
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: network-manager
  UserGroups: N/A

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


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


[Touch-packages] [Bug 2026258] Re: package libpam-cap:amd64 1:2.66-3ubuntu2.1 failed to install/upgrade: el subproceso instalado paquete libpam-cap:amd64 script post-installation devolvió el código de

2023-07-06 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your log files attached to this bug report it
seems that a package failed to install due to a segmentation fault in
the application being used for the package installation process.
Unfortunately, this bug report isn't very useful in its current state
and a crash report would be much more useful.  Could you try recreating
this issue by enabling apport to catch the crash report 'sudo service
apport start force_start=1' and then trying to install the same package
again?  This process will create a new bug report so I am marking this
one as Invalid.  Thanks again for helping out!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: package-install-segfault

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

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

Title:
  package libpam-cap:amd64 1:2.66-3ubuntu2.1 failed to install/upgrade:
  el subproceso instalado paquete libpam-cap:amd64 script post-
  installation devolvió el código de salida de error 128

Status in libcap2 package in Ubuntu:
  Invalid

Bug description:
  Simplemente encendí mi pc y me salió ese error, no se lo que lo
  ocaciona, solo le di en que sí.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: libpam-cap:amd64 1:2.66-3ubuntu2.1
  ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
  Uname: Linux 6.2.0-24-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Jul  3 07:42:44 2023
  ErrorMessage: el subproceso instalado paquete libpam-cap:amd64 script 
post-installation devolvió el código de salida de error 128
  InstallationDate: Installed on 2023-07-03 (2 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: libcap2
  Title: package libpam-cap:amd64 1:2.66-3ubuntu2.1 failed to install/upgrade: 
el subproceso instalado paquete libpam-cap:amd64 script post-installation 
devolvió el código de salida de error 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 2026258] [NEW] package libpam-cap:amd64 1:2.66-3ubuntu2.1 failed to install/upgrade: el subproceso instalado paquete libpam-cap:amd64 script post-installation devolvió el código

2023-07-06 Thread Dicov Developer
Public bug reported:

Simplemente encendí mi pc y me salió ese error, no se lo que lo
ocaciona, solo le di en que sí.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: libpam-cap:amd64 1:2.66-3ubuntu2.1
ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
Uname: Linux 6.2.0-24-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Jul  3 07:42:44 2023
ErrorMessage: el subproceso instalado paquete libpam-cap:amd64 script 
post-installation devolvió el código de salida de error 128
InstallationDate: Installed on 2023-07-03 (2 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.6.0
SourcePackage: libcap2
Title: package libpam-cap:amd64 1:2.66-3ubuntu2.1 failed to install/upgrade: el 
subproceso instalado paquete libpam-cap:amd64 script post-installation devolvió 
el código de salida de error 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package lunar

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

Title:
  package libpam-cap:amd64 1:2.66-3ubuntu2.1 failed to install/upgrade:
  el subproceso instalado paquete libpam-cap:amd64 script post-
  installation devolvió el código de salida de error 128

Status in libcap2 package in Ubuntu:
  New

Bug description:
  Simplemente encendí mi pc y me salió ese error, no se lo que lo
  ocaciona, solo le di en que sí.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: libpam-cap:amd64 1:2.66-3ubuntu2.1
  ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
  Uname: Linux 6.2.0-24-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Jul  3 07:42:44 2023
  ErrorMessage: el subproceso instalado paquete libpam-cap:amd64 script 
post-installation devolvió el código de salida de error 128
  InstallationDate: Installed on 2023-07-03 (2 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: libcap2
  Title: package libpam-cap:amd64 1:2.66-3ubuntu2.1 failed to install/upgrade: 
el subproceso instalado paquete libpam-cap:amd64 script post-installation 
devolvió el código de salida de error 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 2025599] Re: BlueZ release 5.68

2023-07-06 Thread Daniel van Vugt
** Attachment added: "bluez_5.68.orig.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2025599/+attachment/5684197/+files/bluez_5.68.orig.tar.xz

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

Title:
  BlueZ release 5.68

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  BlueZ release 5.68 is now available:

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

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


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


[Touch-packages] [Bug 2025599] Re: BlueZ release 5.68

2023-07-06 Thread Daniel van Vugt
** Attachment added: "bluez_5.68-0ubuntu1.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2025599/+attachment/5684205/+files/bluez_5.68-0ubuntu1.debian.tar.xz

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

Title:
  BlueZ release 5.68

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  BlueZ release 5.68 is now available:

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

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


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


[Touch-packages] [Bug 2026249] Re: bug

2023-07-06 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

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

** Changed in: ubuntu
   Status: New => Won't Fix

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

Title:
  bug

Status in Ubuntu:
  Won't Fix

Bug description:
  keyboard is not typing correct letter,wrong typing

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-142-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.30
  Architecture: amd64
  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 Jul  6 12:30:47 2023
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 510 [8086:1906] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Device [17aa:39fd]
  InstallationDate: Installed on 2022-08-27 (312 days ago)
  InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 
(20200806)
  MachineType: LENOVO 80SX
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic 
root=UUID=38997579-5da1-40ec-8615-cc5b83fb6d3c ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0ZCN40ARBA X64
  dmi.board.asset.tag: No Asset Tag
  dmi.board.vendor: LENOVO
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvr0ZCN40ARBAX64:bd07/13/2017:svnLENOVO:pn80SX:pvrLenovoV310-14ISK:rvnLENOVO:rn:rvr:cvnLENOVO:ct10:cvr:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80SX
  dmi.product.version: Lenovo V310-14ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  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 2:1.18.4-0ubuntu0.12
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  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 Jul  6 12:22:40 2023
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.12
  xserver.video_driver: modeset

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


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


[Touch-packages] [Bug 2026249] [NEW] bug

2023-07-06 Thread TRIDIP
Public bug reported:

keyboard is not typing correct letter,wrong typing

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-142-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.30
Architecture: amd64
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 Jul  6 12:30:47 2023
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 510 [8086:1906] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo Device [17aa:39fd]
InstallationDate: Installed on 2022-08-27 (312 days ago)
InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806)
MachineType: LENOVO 80SX
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic 
root=UUID=38997579-5da1-40ec-8615-cc5b83fb6d3c ro
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/13/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 0ZCN40ARBA X64
dmi.board.asset.tag: No Asset Tag
dmi.board.vendor: LENOVO
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.modalias: 
dmi:bvnLENOVO:bvr0ZCN40ARBAX64:bd07/13/2017:svnLENOVO:pn80SX:pvrLenovoV310-14ISK:rvnLENOVO:rn:rvr:cvnLENOVO:ct10:cvr:
dmi.product.family: IDEAPAD
dmi.product.name: 80SX
dmi.product.version: Lenovo V310-14ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
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 2:1.18.4-0ubuntu0.12
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
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 Jul  6 12:22:40 2023
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.12
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 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/2026249

Title:
  bug

Status in xorg package in Ubuntu:
  New

Bug description:
  keyboard is not typing correct letter,wrong typing

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-142-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.30
  Architecture: amd64
  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 Jul  6 12:30:47 2023
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 510 [8086:1906] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Device [17aa:39fd]
  InstallationDate: Installed on 2022-08-27 (312 days ago)
  InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 
(20200806)
  MachineType: LENOVO 80SX
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic 
root=UUID=38997579-5da1-40ec-8615-cc5b83fb6d3c ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0ZCN40ARBA X64
  dmi.board.asset.tag: No Asset Tag
  dmi.board.vendor: LENOVO
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvr0ZCN40ARBAX64:bd07/13/2017:svnLENOVO:pn80SX:pvrLenovoV310-14ISK:rvnLENOVO:rn:rvr:cvnLENOVO:ct10:cvr:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80SX
  dmi.product.version: Lenovo V310-14ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  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
  

  1   2   >