This bug was fixed in the package openldap - 2.6.4+dfsg-1~exp1ubuntu1
---
openldap (2.6.4+dfsg-1~exp1ubuntu1) mantic; urgency=medium
* Merge with Debian unstable (LP: #2018093). Remaining changes:
- Enable AppArmor support:
+ d/apparmor-profile: add AppArmor profile
** Changed in: software-properties (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/878118
Title:
please merge po files to
Thanks to move it from proposed to update. Confirmed it can be updated
from the end devices.
** Changed in: oem-priority
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanage
** Changed in: bridge-utils (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2018060
Title:
Merge bridge-utils from Debian
** Changed in: libseccomp (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/2018081
Title:
Merge libseccomp from Debian unsta
** Changed in: libmnl (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libmnl in Ubuntu.
https://bugs.launchpad.net/bugs/2018079
Title:
Merge libmnl from Debian unstable for mant
** Patch added: "bionic debdiff with corrected version number"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024637/+attachment/5682930/+files/apparmor_2.12-4ubuntu5.3.debdiff
** Patch removed: "debdiff for bionic"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024637/
It turns out there was already an upload of apparmor 2.12-4ubuntu5.2 to
bionic-proposed that got rejected
(https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1703821/comments/15),
so this update will instead need to skip this version number and use
2.12-4ubuntu5.3 instead.
--
You received th
Sorry, I'm having a hard time understanding how the dput check shows
that distro-info and python-debian are fixed. I'm guessing dput ends up
importing the other two?
Shouldn't python-debian be a block-proposed-kinetic update, since it's
currently unaffected due to its version being still fine rega
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gstreamer1.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu.
https://bugs.l
I triggered a migration-reference/0 run for devscripts. If I understood
it correctly, it will also fail, and that will clear the autopkgtests
for python-debian.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubunt
I bumped into this problem, as described in the issue
https://github.com/CloudI/CloudI/issues/229 . To avoid it, I used clang
for compilation and both linking with '-rtlib=compiler-rt
-unwindlib=libunwind' and '-unwindlib=libgcc' was able to avoid the
segfault. I also didn't see the segfault occu
I've created an upstream issue with some interesting findings so far:
https://github.com/systemd/systemd/issues/28184
** Bug watch added: github.com/systemd/systemd/issues #28184
https://github.com/systemd/systemd/issues/28184
--
You received this bug notification because you are a member of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libunwind (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to google-glog in Ubuntu.
https://bugs.launc
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: google-glog (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to google-glog in Ubuntu.
https://bugs.lau
SUCCESSFUL verification on Jammy, Kinetic and Lunar. No tracebacks, all
expected CloudArchitecture, CloudName, CloudPlatform and CloudRegion are
present when expected for openstack or ec2/aws. No missing apport report
keys from orig to -proposed.
Long logs of test run below Jammy/Kinetic/Lunar:
$
Thank you Lukasz !
Op do 29 jun 2023 om 10:03 schreef Łukasz Zemczak <
1971...@bugs.launchpad.net>:
> Hello Ubucolors, or anyone else affected,
>
> Accepted pcsc-lite into jammy-proposed. The package will build now and
> be available at https://launchpad.net/ubuntu/+source/pcsc-
> lite/1.9.5-3ub
SRU Verification script
** 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
ins
I wasn't able to reproduce this with the test script, so Jammy is likely
unaffected by this. If this changes, please leave a comment so we can
investigate.
** Changed in: systemd (Ubuntu Jammy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a mem
I'm marking Bionic as Won't Fix, as this is no longer under standard
support. The fixes for this bug will be made available under Ubuntu Pro
for 18.04.
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undeci
Thanks for the verification. This looks good to release, except due to a
current breakage in jammy's DEP8 reporting[1], I can't easily verify if
the autopkgtests are green. I can check the test from initramfs-tools[2]
itself pretty easily, but not the DEP8 results of the other tests
triggered by th
Running `sudo dhclient -6 ` appears to work, the problem
seems to be with the systemd-networkd DHCPv6 client.
--
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/2025382
Title:
All failing autopkgtest succeeded after a retry except for
devscripts/2.22.2ubuntu3, which is a unrelated regression (caused by the
release of Debian 12).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
htt
Verified python-debian on focal. To make the test case succeed, dput and
gpgme1.0 have to be fixed as well (see SRU debdiff in previous
comments).
Failing without packages from -proposed:
```
$ schroot-wrapper -c focal -p
dput,python3-pip,python3-debian,python3-distro-info -p
./dput_1.0.3ubuntu
Note: Without the packages from -proposed, dput will complain about the
version from python-debian:
```
$ schroot-wrapper -c jammy -p
dput,python3-pip,python3-debian,python3-distro-info -p
./dput_1.1.0ubuntu2.1_all.deb -p ./python3-gpg_1.16.0-1.2ubuntu4.1_amd64.deb
[...]
(jammy)bdrung@host:~$ pi
** Patch added: "gpgme1.0_1.13.1-7ubuntu2.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dput/+bug/1991606/+attachment/5682869/+files/gpgme1.0_1.13.1-7ubuntu2.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Verified python-debian and distro-info on jammy. To make the test case
succeed, dput and gpgme1.0 have to be fixed as well (see SRU debdiff in
previous comments).
```
$ schroot-wrapper -c jammy -p
dput,python3-pip,python3-debian,python3-distro-info -e -p
./dput_1.1.0ubuntu2.1_all.deb -p ./python
** Patch added: "gpgme1.0_1.16.0-1.2ubuntu4.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dput/+bug/1991606/+attachment/5682868/+files/gpgme1.0_1.16.0-1.2ubuntu4.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
Public bug reported:
Ubuntu 22.04.2 LTS
kernel 5.15.0-1038-oracle
systemd 249.11-0ubuntu3.9
After an update a couple weeks ago, Ubuntu 22.04 can no longer get IPv6
via DHCPv6 systemd-networkd, at least on Oracle OCI, but there are also
other similar reports, e.g.
https://ubuntuforums.org/showthr
For Debian the metadata_csum_seed and orphan_file features were disabled
by default by changing the /etc/mke2fs.conf file.
e2fsprogs (1.47.0-2) unstable; urgency=medium
* Don't enable metadata_csum_seed and orhpan_file by default (Closes:
#1031622, #1030939)
-- Theodore Y. Ts'o Sat, 04
Verified python-debian on kinetic. To make the test case succeed, dput
has to be fixed as well (see SRU debdiff in previous comments).
```
$ schroot-wrapper -c kinetic -p dput,python3-pip,python3-debian -e -p
./dput_1.1.2ubuntu2.1_all.deb
[...]
(kinetic)bdrung@host:~$ pip3 install -U setuptools
D
This bug was fixed in the package accountsservice - 23.13.9-2ubuntu2
---
accountsservice (23.13.9-2ubuntu2) mantic; urgency=medium
* SECURITY UPDATE: use-after-free in user.c (LP: #2024182)
- debian/patches/0010-set-language.patch: updated to properly return
from functions
This bug was fixed in the package pulseaudio - 1:16.1+dfsg1-2ubuntu4
---
pulseaudio (1:16.1+dfsg1-2ubuntu4) mantic; urgency=medium
* debian/rules:
- fix a $LIB escaping issue in the pulsedsp-location option which
is making padsp error out, thanks Márcio (lp: #2025169)
--
** Patch added: "dput_1.0.3ubuntu1.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dput/+bug/1991606/+attachment/5682866/+files/dput_1.0.3ubuntu1.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in U
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bu
Filed a bug tracking focal-proposed regression
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2025376
--
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
Hello, patch build resolved my issue as well
juggler@circus:/tmp$ dpkg -l idn libidn12
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
** Patch added: "dput_1.1.0ubuntu2.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dput/+bug/1991606/+attachment/5682859/+files/dput_1.1.0ubuntu2.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in U
Regression discovered for focal-proposed due to type annotations not
being parsed on python 3.8. this resulted in tracebacks from python when
importing cloud-init's apport/general-hooks module:
..ERROR: hook /usr/share/apport/general-hooks/cloud-init.py crashed:
Traceback (most recent call la
** Patch added: "dput_1.1.2ubuntu2.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/dput/+bug/1991606/+attachment/5682858/+files/dput_1.1.2ubuntu2.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in U
Public bug reported:
Running the qemu-net autopkgtest from initramfs-tools on architectures
like armhf shows that there are sometimes remaining systemd-udevd after
exiting the initramfs. `ps -ww aux` shows:
```
/lib/systemd/systemd-udevd --daemon --resolve-names=never
```
Example run: https://au
Problem seems solved with kernel 5.19.0-45-generic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2012734
Title:
no audio after update
Status in pulseaudio package in
This is a specific case, so the only thing I expect for this upload is
for the autopkgtests to pass (+ the obvious added unit-tests for all the
aforementioned issues listed as fixed).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
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.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
evince and apparmor for lunar should be released together to fix this
bug, but there is still a DEP8 failure that needs clearing under
apparmor: libreoffice/armhf
https://ubuntu-archive-team.ubuntu.com/proposed-
migration/lunar/update_excuses.html#apparmor
It was retried a few times already, but
** Also affects: dput (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1991606
Title:
Invalid PEP440 package versi
Public bug reported:
The Debian package has been upgraded to release 1.222. According to the
changelog this is just a rebuild.
Rebuilding will update the keyboard names.
** Affects: console-setup (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification bec
> Related?
Yes, that is what I suggest above.
I think the real problem is this inhibitor:
xfce4-power-manager 1000 bbogart 1309 xfce4-power-man handle-
power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch
xfce4-power-manager handles these events block
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2024637
Title:
apparmor.service tries to load snapd generated apparmor profiles but
fails
Status in
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
I'm setting the status of this bug to 'Invalid' as it's not seen any activity
for some time and there was no re
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
** Patch added: "xenial debdiff"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024637/+attachment/5682832/+files/apparmor_2.10.95-0ubuntu2.12.debdiff
** Changed in: apparmor (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: apparmor (Ubuntu Bionic)
Importance: Unde
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
Ubuntu 16.04 (xenial) reached end-of-stand
** Patch added: "debdiff for bionic"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2024637/+attachment/5682828/+files/apparmor_2.12-4ubuntu5.2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in U
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
I'm setting the status of this bug to 'In
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
I'm setting the status of this bug to 'In
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1677827
Title:
Missing dep8
I ran into this bug myself a while ago by doing following: I bought a
new NVMe and put it into my laptop. Then I booted a recent Ubuntu live
system, created partitions on the NVMe, copied everything from the old
to the new, updated entries in /etc/fstab etc. When I rebooted the file
system check fa
Newer releases of Ubuntu can always start making use of new file system
feature flags. Looking at all currently supported releases (whether
standard or ESM), we have never SRUed e2fsprogs before, it only ever
received security updates, so I'd be inclined to not do a backport here
either and resolve
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: e2fsprogs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchp
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: e2fsprogs (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.l
Related debian bug: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1031622
** Bug watch added: Debian Bug tracker #1031622
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031622
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
Given new incompatible RO and RW features in ext4 that v5.15 kernels
support, imho we should SRU backport of e2fsprogs on HWE grounds.
--
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
** Description changed:
After installation of the FDE image, the system fails to boot due to
e2fsck failing with:
Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported
feature(s): FEATURE_C12
this means that Jammy fsck fails against mantic created ext4 which
** Also affects: e2fsprogs (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/2025339
Title:
FDE image fails to ru
** Description changed:
After installation of the FDE image, the system fails to boot due to
e2fsck failing with:
- Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported
feature(s): FEATURE_C12
- Jun 21 12:48:19 ubuntu systemd-fsck[268]: e2fsck: Get a newer version of
e2fsck
** Description changed:
After installation of the FDE image, the system fails to boot due to
e2fsck failing with:
- Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported
- feature(s): FEATURE_C12
+ Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported
feature(s)
Public bug reported:
After installation of the FDE image, the system fails to boot due to
e2fsck failing with:
Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported
feature(s): FEATURE_C12
this means that Jammy fsck fails against mantic created ext4 which is
not great
** Aff
Public bug reported:
There is either "dummy" output or it claims the headphones are plugged
in and it is unable to output to the speakers, randomly when rebooting
or walking up from suspend. Usually there is no sound, but maybe once
in several tries it works.
The sound worked fine in the previou
Hello Ubucolors, or anyone else affected,
Accepted pcsc-lite into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/pcsc-
lite/1.9.5-3ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
ht
1 - 100 of 105 matches
Mail list logo
