Public bug reported:
error occurred during automatic system update from ubuntu 20.04 LTS to
22.04 LTS
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libgstreamer1.0-dev:amd64 1.20.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195
Uname: Linux 5.4.0-124-generic
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1982841
Title:
[22.10 FEAT] [SEC2210] p11-kit:
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]
** Changed in: cups (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
This bug was fixed in the package p11-kit - 0.24.1-1ubuntu1
---
p11-kit (0.24.1-1ubuntu1) kinetic; urgency=medium
* Add support for IBM specific attributes and mechanis by adding the
following upstream commits as quilt patches (LP: #1982841):
** Patch added: "manpage-is-wrong.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5611101/+files/manpage-is-wrong.debdiff
** Tags added: rls-kk-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "bash-is-wrong.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5611100/+files/bash-is-wrong.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
I'm unsure what the "correct" solution is here; could be that bash's
behaviour is wrong, or it could be that the documentation is wrong.
Rather than decide, I'm taking the cowards way out and attaching patches
for both solutions, leaving it to the maintainer to decide which is
appropriate :)
--
Added 'Where problems could occur' section.
** Description changed:
[Impact]
Running ubuntu-bug as normal user has the correct theme (see screenshots
attached to bug #1881640), but running "sudo ubuntu-bug" has a
different, non-matching theme (see attached screenshot). This applies to
** Description changed:
+ Impact
+ --
+
+ The deprecation warning is just a warning, but it clutters the output
+ and can lead to misattributions in case something does not work as
+ expected.
+
Test Case
-
1. Execute following command:
python3 -Wonce -c "import
** Description changed:
[Impact]
Apport will fail for processes with dump mode 2 inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
#!/bin/sh
sudo rm -rf /var/crash/* /var/log/apport.log
sudo -u mail sh -c "ping 127.0.0.1 >
** Description changed:
[Impact]
Apport will write an empty core dump file inside of containers.
[Test plan]
Run following testcase script inside a LXC container:
```
rm -f /var/lib/apport/coredump/*
ulimit -c 100
sleep 86400 &
killall -3 sleep
```
Apport
** Description changed:
+ Impact
+ --
+
+ The Apport Python hook should be transparent to the user (which is
+ normally the case). Bugs and crashes inside the hook lead to an
+ exception inside the exception which clutters the output and confuse the
+ user. User/Developer need to understand
** Description changed:
+ Impact
+ --
+
+ The Apport Python hook should be transparent to the user (which is
+ normally the case). Bugs and crashes inside the hook lead to an
+ exception inside the exception which clutters the output and confuse the
+ user. User/Developer need to understand
** Description changed:
+ Impact
+ --
+
+ All German users (and all translations that use "%s." in their
+ translation template) will get a broken URL link for bug reports against
+ snaps (e.g. Firefox).
+
Test Case
-
1. Execute following command: LANGUAGE=de ubuntu-bug
** Description changed:
+ Impact
+ --
+
+ As it can be seen in
+ https://errors.ubuntu.com/problem/e714f8181c0785693f3a66969c594a3b19bcab2b
+ there are thousands of crashes of this type (and multiple duplicate bug
+ reports for it). Instead of apport logging a failure in
+
Hmm, on the other hand --norc does indeed suppress both user and system-
wide bashrc files. So, the man-page is correct in that instance, and
apparently the intent of bash is to allow the system-wide bashrc file to
be suppressed in certain circumstances. Which sways me back toward the
notion that
** Description changed:
+ [Impact]
+
+ If the user reports a bug and rejects to enter the root password for
+ collecting information (like the CasperMD5json), the Ubuntu add_info
+ hook will fail with a stack trace. The remaining code for collecting
+ more information is not executed. So the
I'm afraid the removal of colons in LP: entries of the changelog is a
deliberate tactic by maintainers to prevent launchpad from inadvertently
marking things closed when it shouldn't (theoretically, this shouldn't
happen if things are targetted correctly to the relevant releases, but
this isn't
same here, with kodi!!. the problem is fixed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1982108
Title:
SRU: update python3.10 to the 3.10.5 release in 22.04
The test case is already in the "Example output" file.
https://launchpadlibrarian.net/493705832/sudo-broken.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1891798
Title:
This has apparently been an issue for some considerable time. I've just
now run into it while delving into a failure in pexpect's test-suite
(during work on LP: #1987420), which apparently assumes that using
--rcfile will suppress both the user *and* the system's bashrc (as the
man-page
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bash (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
** Summary changed:
- bash does not fulfill --bashrc option properly
+ bash does not fulfill --rcfile option properly
** Description changed:
I am starting a bash shell using
- $ bash --noprofile --bashrc my-custom-bash-rc-file
+ $ bash --noprofile --rcfile my-custom-bash-rc-file
Due
I removed the trailing spaces from the old debian/changelog entries from
Ubuntu and uploaded lvm2 2.03.16-1ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1987340
I will sponsor it. Except for some small formatting (patch attached) for
the debian/changelog the merge proposal looks good. Having the git
repository helped reviewing. Suggestion: Base your branch on
https://salsa.debian.org/lvm-team/lvm2 next time.
** Patch added: "0001-Fix-changelog.patch"
Hi Mike,
Do you have a test case that can demonstrate/reproduce this issue?
** 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.
Next update pointing to nowhere again, with a new path:
update-initramfs: Generating /boot/initrd.img-5.19.0-15-generic
depmod: WARNING: could not open modules.builtin.modinfo at
/var/tmp/mkinitramfs_tWthLe/lib/modules/5.19.0-15-generic: No such file or
directory
** Summary changed:
-
** Package changed: systemd (Ubuntu) => libfido2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1983784
Title:
LUKS-encrypted partition is not automatically
Attaching patch against Debian unstable. For ease of review, relevant commits
and tags have been pushed to the following repository:
https://code.launchpad.net/~waveform/ubuntu/+source/dbus/+git/dbus
Specifically:
* logical/1.12.20-2ubuntu4 represents our split-out delta on top of old/debian
Test builds will be available in ppa:waveform/dbus at the following URL:
https://launchpad.net/~waveform/+archive/ubuntu/dbus
** Tags added: fr-2624
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1982841
Title:
[22.10 FEAT] [SEC2210] p11-kit:
Uploaded, thanks :)
** Changed in: p11-kit (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 p11-kit in Ubuntu.
https://bugs.launchpad.net/bugs/1982841
Title:
[22.10
According to
https://launchpadlibrarian.net/619433186/gtk+3.0_3.24.34-1ubuntu1_3.24.34-3ubuntu1.diff.gz
the patch named `reftest-known-fail.patch` was dropped from
`debian/patches/series`. This causes the known failures to not be
recognised as such and therefore are now fatal again.
--
You
Seems to be fixed since Ubuntu Jammy 22.04.1 has been released, "rw"
kernel parameter as a workaround of the read-only RootFS isn't necessary
anymore.
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
*** This bug is a duplicate of bug 1959211 ***
https://bugs.launchpad.net/bugs/1959211
** Changed in: dbus (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => (unassigned)
** Changed in: dbus (Ubuntu)
Status: Triaged => Invalid
** This bug has been marked a duplicate of bug
** Summary changed:
- Please merge dbus 1.12.20-3 from Debian unstable
+ Please merge dbus 1.14.0-2 from Debian unstable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1974115
Title:
[UBUNTU 22.04] BINUTILS: Adding
** Changed in: gtk+3.0 (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1987304
Title:
gtk3 fails to
** Changed in: ubuntu-power-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1978129
Title:
Incomplete support for
Lukas, could you report your findings to
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues ?
Thanks!
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I'll mark the bug as fix released as I think Ubuntu releases no longer
suffer from this problem. Also, all Ubuntu releases still receiving
normal support have moved away from upstart.
** Changed in: upstart (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification
I can confirm this resolves the issue of embedded interpreters crashing
(tested with Kodi).
Versions used:
ii libpython3-dev:amd64 3.10.6-1~22.04
amd64header files and a static library for Python (default)
ii libpython3-stdlib:amd64
I think this might be a real regression in NM.
Netplan is testing something like this (which worked nicely in the past):
mybond:
parameters:
mode: 802.3ad
ad-select: bandwidth
Therefore, /sys/class/net/mybond/bonding/ad_select should actually
contain "bandwidth 1", not
This bug was fixed in the package sysvinit - 3.04-1ubuntu1
---
sysvinit (3.04-1ubuntu1) kinetic; urgency=low
* Merge from Debian unstable. (LP: #1987257) Remaining changes:
- When building for Ubuntu, skip all binaries except for sysvinit-utils
- Define the DEB_HOST_*
Hello bugproxy, or anyone else affected,
Accepted binutils into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/binutils/2.38-4ubuntu2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Matthias, or anyone else affected,
Accepted binutils into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/binutils/2.38-4ubuntu2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello bugproxy, or anyone else affected,
Accepted binutils into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/binutils/2.38-4ubuntu2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1987340
Title:
Please merge lvm2 2.03.16-1 from Debian unstable.
Test builds are available from ppa:waveform/lvm2 at the following URL:
https://launchpad.net/~waveform/+archive/ubuntu/lvm2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
Hi, @jeremyszu
How can I build grub from your repository
https://github.com/os369510/grub2 with your patches for testing my linux
box?
Thanks in advance!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in
Reassigning to correct package, and confirmed. So while [arch=amd64]
works fine [signed-by=...] does not which is odd. Neither are *properly*
supported in software-properties: sources.list options are not exposed
at all; it's unclear what happens if you modify them.
** Package changed:
You have been subscribed to a public bug:
Since apt-key is now deprecated, I followed various guides and moved all
third-party repository keys to /etc/apt/keyrings/, then added the
"signed-by" tag to the corresponding source lists. After that, those
third-party repositories no longer show up in
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1981622
Title:
mtd device must be supplied (device name is empty)
Status in systemd package in Ubuntu:
Fix Released
*** This bug is a duplicate of bug 1983481 ***
https://bugs.launchpad.net/bugs/1983481
I have to correct my last comment: ui was None. Therefore this bug is a
duplicate of bug #1983481.
** Package changed: sudo (Ubuntu) => apport (Ubuntu)
** This bug has been marked a duplicate of bug
Can you provide a test case do demonstrate this behavior (and for using
in https://wiki.ubuntu.com/StableReleaseUpdates)?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1891798
Thanks for reporting this bug. You tried to remove sudo and sudo gave a
clear warning in the dpkg terminal log:
```
Removing ubuntu-minimal (1.472) ...
Removing sudo (1.9.5p2-3ubuntu2) ...
You have asked that the sudo package be removed,
but no root password has been set.
Without sudo, you may
It's fixed in Debian by version 3.121 and therefore fixed in adduser
3.121ubuntu1 in Ubuntu 22.10 (kinetic).
** Changed in: adduser (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
The attachment "rrm-include-passive-channels-in-active-beacon-report-
scan.patch" seems to be a patch. If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message
It's fixed in 3.119 and therefore fixed in adduser 3.121ubuntu1 in
Ubuntu 22.10 (kinetic).
** Changed in: adduser (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in
Weirdly, two of the syncs prepared (python3.10 and python3-stdlib-
extensions) don't have any Launchpad-Bugs-Fixed in their .changes files
(even though bugs are correctly visible in the changelog. Since those
are binary syncs and time-consuming to rebuild, I accepted those as-is.
But please
Hello Matthias, or anyone else affected,
Accepted python3-stdlib-extensions into jammy-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/python3-stdlib-
extensions/3.10.6-1~22.04 in a few hours, and then in the -proposed
repository.
Please help us by
Hello Matthias, or anyone else affected,
Accepted python3.10 into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/python3.10/3.10.6-1~22.04 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Matthias, or anyone else affected,
Accepted python3-defaults into jammy-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/python3-defaults/3.10.6-1~22.04 in
a few hours, and then in the -proposed repository.
Please help us by testing this new
Thanks, LGTM!
** Changed in: sysvinit (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1987257
Title:
Please merge sysvinit
65 matches
Mail list logo
