This bug was fixed in the package apport - 2.20.11-0ubuntu27.27
---
apport (2.20.11-0ubuntu27.27) focal; urgency=medium
* whoopsie-upload-all: Catch zlib.error when decoding CoreDump from
crash file (LP: #1947800)
* Fix KeyError: 'CasperMD5json' (LP: #1964828)
* apport-kde:
The verification of the Stable Release Update for apport 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 r
This bug was fixed in the package apport - 2.20.11-0ubuntu27.27
---
apport (2.20.11-0ubuntu27.27) focal; urgency=medium
* whoopsie-upload-all: Catch zlib.error when decoding CoreDump from
crash file (LP: #1947800)
* Fix KeyError: 'CasperMD5json' (LP: #1964828)
* apport-kde:
This bug was fixed in the package apport - 2.20.11-0ubuntu27.27
---
apport (2.20.11-0ubuntu27.27) focal; urgency=medium
* whoopsie-upload-all: Catch zlib.error when decoding CoreDump from
crash file (LP: #1947800)
* Fix KeyError: 'CasperMD5json' (LP: #1964828)
* apport-kde:
This bug was fixed in the package apport - 2.20.11-0ubuntu27.27
---
apport (2.20.11-0ubuntu27.27) focal; urgency=medium
* whoopsie-upload-all: Catch zlib.error when decoding CoreDump from
crash file (LP: #1947800)
* Fix KeyError: 'CasperMD5json' (LP: #1964828)
* apport-kde:
This bug was fixed in the package apport - 2.20.11-0ubuntu27.27
---
apport (2.20.11-0ubuntu27.27) focal; urgency=medium
* whoopsie-upload-all: Catch zlib.error when decoding CoreDump from
crash file (LP: #1947800)
* Fix KeyError: 'CasperMD5json' (LP: #1964828)
* apport-kde:
This bug was fixed in the package software-properties - 0.96.24.32.22
---
software-properties (0.96.24.32.22) bionic; urgency=medium
[ Nathan Pratta Teodosio ]
* fix a problem in the fix backported in the previous revision
software-properties (0.96.24.32.21) bionic; urgency=mediu
This bug was fixed in the package software-properties - 0.96.24.32.22
---
software-properties (0.96.24.32.22) bionic; urgency=medium
[ Nathan Pratta Teodosio ]
* fix a problem in the fix backported in the previous revision
software-properties (0.96.24.32.21) bionic; urgency=mediu
This bug was fixed in the package software-properties - 0.96.24.32.22
---
software-properties (0.96.24.32.22) bionic; urgency=medium
[ Nathan Pratta Teodosio ]
* fix a problem in the fix backported in the previous revision
software-properties (0.96.24.32.21) bionic; urgency=mediu
Public bug reported:
As part of my sandboxed APT I noticed that the package failed to install
as it was trying to write to /root.
/root is a user directory, not a system one, which may not even exist
because the administrator changed it to like /home/root, for example,
and we definitely should no
Comparing the files /etc/systemd/system/multi-user.target.wants/auditd.service
between Focal and Jammy,
I can see Jammy has the line "ProtectHome=true", If I remove this line and
reboot the system, then the rule can be loaded along with system bootup
--
You received this bug notification becau
I actually failed to mention that before the update I was experiencing
the crash. Not instead of the crashing UI is freezing.
--
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/2003
Sounds like another fix similar to bug 1983456 will be required.
** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.lau
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2021915
Title:
dock overlays the rename box
Status in xorg package in Ubuntu:
Ne
Public bug reported:
The latest release is 0.28.0 and fixes some bugs I've encountered
https://github.com/Exiv2/exiv2/releases/tag/v0.28.0
** Affects: exiv2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch s
Given that python-tz is just a test update I think we should leave that
in -proposed and tag this bug block-proposed-lunar.
** Tags added: block-proposed-lunar
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
This bug was fixed in the package tzdata - 2023c-0ubuntu0.22.04.2
---
tzdata (2023c-0ubuntu0.22.04.2) jammy; urgency=medium
* Build tzdata with PACKRATLIST=zone.tab. In combination with
PACKRATDATA=backzone (which is used since 2023c-0ubuntu0.22.04.1), time
zones that differ
This bug was fixed in the package tzdata - 2023c-0ubuntu0.20.04.2
---
tzdata (2023c-0ubuntu0.20.04.2) focal; urgency=medium
* Build tzdata with PACKRATLIST=zone.tab. In combination with
PACKRATDATA=backzone (which is used since 2023c-0ubuntu0.20.04.1), time
zones that differ
This bug was fixed in the package tzdata - 2023c-0ubuntu0.22.10.2
---
tzdata (2023c-0ubuntu0.22.10.2) kinetic; urgency=medium
* Build tzdata with PACKRATLIST=zone.tab. In combination with
PACKRATDATA=backzone (which is used since 2023c-0ubuntu0.22.10.1), time
zones that diff
The verification of the Stable Release Update for tzdata 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 r
This bug was fixed in the package tzdata - 2023c-2exp1ubuntu1.1
---
tzdata (2023c-2exp1ubuntu1.1) lunar; urgency=medium
* Build tzdata with PACKRATLIST=zone.tab. In combination with
PACKRATDATA=backzone (which is used since 2022g-3), time zones that differ
pre-1970 and had b
** Tags removed: rls-kk-incoming
** Also affects: initramfs-tools (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu Kinetic)
Status: New => Fix Released
** Description changed:
- The initialization of the entropy buffer of the urandom dev
Public bug reported:
After Software Updater performed updates and reboot sound no longer works.
I don't know what updates were performed because I didn't check.
In sound settings only Dummy Output is available.
When searching the internet for solutions I couldn't find any posts with the
exact sam
This bug was fixed in the package iptables - 1.8.4-3ubuntu2.1
---
iptables (1.8.4-3ubuntu2.1) focal; urgency=medium
[ Louis Bouchard ]
* d/p/0001-libiptc-Fix-for-segfault-when-renaming-a-chain.patch: apply
upstream fix for segfault when renaming a chain. Includes a test
ca
The verification of the Stable Release Update for iptables 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
This bug was fixed in the package iptables - 1.8.4-3ubuntu2.1
---
iptables (1.8.4-3ubuntu2.1) focal; urgency=medium
[ Louis Bouchard ]
* d/p/0001-libiptc-Fix-for-segfault-when-renaming-a-chain.patch: apply
upstream fix for segfault when renaming a chain. Includes a test
ca
The verification of the Stable Release Update for iptables 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
This bug was fixed in the package iptables - 1.6.1-2ubuntu2.1
---
iptables (1.6.1-2ubuntu2.1) bionic; urgency=medium
[ Louis Bouchard ]
* d/patches: 0001-libiptc-Fix-for-segfault-when-renaming-a-chain.patch
Apply upstream fix:
- libiptc: Fix for segfault when renaming a c
The verification of the Stable Release Update for iptables 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
This bug was fixed in the package iptables - 1.6.1-2ubuntu2.1
---
iptables (1.6.1-2ubuntu2.1) bionic; urgency=medium
[ Louis Bouchard ]
* d/patches: 0001-libiptc-Fix-for-segfault-when-renaming-a-chain.patch
Apply upstream fix:
- libiptc: Fix for segfault when renaming a c
Oh, I found out it was another image in CI/CD setup. Sorry, my bad.
** Changed in: openssl (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/b
Yes, I did upgrade of all packages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/2021889
Title:
error OSSL_CMP_MSG_update_recipNonce on base64 decoding
Status in openss
Nope, only distribution packages. I noted it first in my CI/CD setup
where I install fresh docker image ubuntu:22.04 and then apt-get update
&& apt-get upgrade
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
OSSL_CMP_MSG_update_recipNonce was added in OpenSSL 3.0.9...did you
perhaps install from source, or a package that didn't come from Ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launch
Thanks for reporting this issue. Did you also upgrade the libssl3
package too?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/2021889
Title:
error OSSL_CMP_MSG_update_reci
** Tags removed: need-duplicate-check
--
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/2021890
Title:
package linux-image-5.19.0-1025-aws 5.19.0-1025.26~22.04.1 fail
Public bug reported:
I upgraded from Ubuntu 20.04 to 22.04
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-1025-aws 5.19.0-1025.26~22.04.1
ProcVersionSignature: Ubuntu 5.15.0-1036.40~20.04.1-aws 5.15.98
Uname: Linux 5.15.0-1036-aws x86_64
NonfreeKernelModules: aufs
Ap
Public bug reported:
$ echo "$SSH_PRIVATE_KEY" | openssl base64 -A -d
Error relocating /usr/bin/openssl: OSSL_CMP_MSG_update_recipNonce: symbol not
found
Error loading key "(stdin)": error in libcrypto
---
works with openssl Version: 3.0.2-0ubuntu1.9.
version 3.0.2-0ubuntu1.10 i
This bug is not present in Jammy or newer.
** Changed in: util-linux (Ubuntu)
Status: New => Fix Released
** Description changed:
+ [Impact]
+
+ The partition detection logic in libblkid1 can falsely report the
+ presence of an atari partition. One place where this has a practical
+ impa
Hardware info:
CPU: Intel core i7-12800H
00:00.0 Host bridge: Intel Corporation 12th Gen Core Processor Host Bridge/DRAM
Registers (rev 02)
00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x16
Controller #1 (rev 02)
00:02.0 VGA compatible controller: Intel Corporation A
Uploaded for Mantic, thanks!
** Changed in: util-linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2019856
Public bug reported:
kwin and plasmashell randomly freeze usually when there is a
notification window pop up. I have to use kwin_x11 --replace or
plasmashell --replace in order to make screen responsive. Please note I
can still type to the app that currently is open (let's say FeatherPad)
but thin
Yes Gunter you might be correct. For me it is a freeze but seems related
since other people have reported the same issue stating the revert of
the two commits solved the freeze issue. There are no GPU hangs in the
kernel logs (I just wanted to stress that out). I guess I will open a
new bug report.
** Changed in: util-linux (Ubuntu Mantic)
Assignee: Mauricio Faria de Oliveira (mfo) => Dan Bungert (dbungert)
** Changed in: util-linux (Ubuntu Mantic)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
On my machine the crashes also seem to be solved. I was using Intel
driver until the weekend (since I use this laptop) and then switched to
the nVidia binary drivers because I wanted to use CUDA for some
experiments.
kwin seems to run properly with both so far.
@Konstantin Petrov: You write abou
Hi there, I see this with "lunar" Xubuntu 23.04
bernie@prod:~/Desktop$ journalctl -b |grep 'exit code 1'
Mai 30 17:16:45 prod systemd-udevd[246]: sda: Process '/usr/bin/unshare -m
/usr/bin/snap auto-import --mount=/dev/sda' failed with exit code 1.
Mai 30 17:16:45 prod systemd-udevd[234]: sr0: Pr
Perhaps every 2 days. Initially it is working find (let's say 2-3 days)
and once it hangs (note no GPU hang kernel logs) perhaps every day. I
have teams open in chrome browser with notifications on.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
How often does it happen for you?
i'm currently running 4days without the bug.
previously it was consistently happening every 24 hours at least once
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.
Public bug reported:
unable to install default jdk and jre. These errors were encountered
while doing the same.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-firmware 20220329.git681281e4-0ubuntu3.12
ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
Uname: Linux
Unfortunately this is still happening for me - though in much lower
rate. My vga is: VGA compatible controller: Intel Corporation Alder
Lake-P Integrated Graphics Controller (rev 0c)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
** Description changed:
- Tracking bug
+ The upstream version 3.134 should be merged into mantic. The current
+ version is 3.129ubuntu1.
+
+ See the merge conflict report:
+ https://merges.ubuntu.com/u/adduser/REPORT
+
+ Note: this is a tracking bug
** Description changed:
The upstream versi
** Changed in: systemd (Ubuntu Jammy)
Importance: High => 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/bugs/1977630
Title:
machinectl pull-tar/pull-raw Operation not p
All autopkgtests for the newly accepted software-properties (0.96.24.32.22) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
crash/7.2.8-1ubuntu0.18.04.2 (i386)
Please visit the excuses page listed below and investigate the failur
All autopkgtests for the newly accepted software-properties (0.96.24.32.22) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
crash/7.2.8-1ubuntu0.18.04.2 (i386)
Please visit the excuses page listed below and investigate the failur
All autopkgtests for the newly accepted software-properties (0.96.24.32.22) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
crash/7.2.8-1ubuntu0.18.04.2 (i386)
Please visit the excuses page listed below and investigate the failur
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/2021505
Title:
Flaky DEP8 test: saslauthd
Status in c
All autopkgtests for the newly accepted lxc (3.0.3-0ubuntu1~18.04.3) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
lxd/3.0.3-0ubuntu1~18.04.2 (i386)
Please visit the excuses page listed below and investigate the failures,
proc
All autopkgtests for the newly accepted lxc (3.0.3-0ubuntu1~18.04.3) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
lxd/3.0.3-0ubuntu1~18.04.2 (i386)
Please visit the excuses page listed below and investigate the failures,
proc
All autopkgtests for the newly accepted lxc (3.0.3-0ubuntu1~18.04.3) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
lxd/3.0.3-0ubuntu1~18.04.2 (i386)
Please visit the excuses page listed below and investigate the failures,
proc
Testing 0.96.24.32.22 on a bionic system while beeing offline the
warning is correctly display and no error prompt is triggered
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because
Testing 0.96.24.32.22 on a bionic system while beeing offline the
warning is correctly display and no error prompt is triggered
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because
Testing 0.96.24.32.22 on bionic, the 'Unable to connect to Ubuntu Pro
servers. Check your internet connection.' warning is correctly displayed
when disconnected and goes away after reconnecting. The error which
existed in .22 about the non existing API is also resolved
** Tags removed: verificatio
** Description changed:
+ [ Impact ]
+
+ * Test suite fails due to inexistent device (/dev/network_latency).
+
+ [ Test Plan ]
+
+ * Run the test suite.
+ * The test should pass.
+
+ [ Where problems could occur ]
+
+ * The regression risk is very low, and the changes only affect the
+ te
** Description changed:
+ [ Impact ]
+
+ * The device_add_remove_test test fails on the affected series (e.g. Bionic).
+ * Having the test fixed for the affected series (for example, Bionic) will
allow us to run the LXC test suite without maintaining local changes for this
test.
+
+ [ Test P
** Description changed:
[ Impact ]
- * The following tests fail as they try to use inexistent LXC images:
-* lxc-test-apparmor-mount
- * lxc-test-autostart
- * lxc-test-unpriv
- * lxc-test-usernic
+ * The following tests fail as they try to use inexistent LXC images:
+ * lxc
Hello errors.ubuntu.com, or anyone else affected,
Accepted software-properties into bionic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/software-properties/0.96.24.32.22
in a few hours, and then in the -proposed repository.
Please help us by testin
Hello Sebastien, or anyone else affected,
Accepted software-properties into bionic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/software-properties/0.96.24.32.22
in a few hours, and then in the -proposed repository.
Please help us by testing this n
Hello errors.ubuntu.com, or anyone else affected,
Accepted software-properties into bionic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/software-properties/0.96.24.32.22
in a few hours, and then in the -proposed repository.
Please help us by testin
** Description changed:
+ [ Impact ]
+
+ * The following tests fail as they try to use inexistent LXC images:
+* lxc-test-apparmor-mount
+ * lxc-test-autostart
+ * lxc-test-unpriv
+ * lxc-test-usernic
+
+ * Having them fixed for the affected series (for example Bionic) will allow
I saw nothing specific to tzdata in 180_ecpg.t. I tried 180_ecpg.t from
postgresql-12 locally and it succeeded. Then I retried the autopkgtest
and it succeeded as well. So all autopkgtest issues are resolved now.
--
You received this bug notification because you are a member of Ubuntu
Touch seede
Looking at the autopkgtest, several of the failing ones got resolved
(e.g. all for python-tz on lunar). Remaining failing ones:
* tzdata on lunar:
- chrony/4.3-1ubuntu4 on armhf: Flaky test case (see bug #2002910)
* tzdata on focal:
- postgresql-12/12.14-0ubuntu0.20.04.1 on amd64: test 8 of 18
Hello Kleber, or anyone else affected,
Accepted lxc into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/3.0.3-0ubuntu1~18.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
Hello Seth, or anyone else affected,
Accepted lxc into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/3.0.3-0ubuntu1~18.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
Hello Po-Hsu, or anyone else affected,
Accepted lxc into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/3.0.3-0ubuntu1~18.04.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
Hi Seth,
Thank you for the advice of "-i". It works if I append "-i" into the
problematic line.
It's strange that:
1) I can not see any difference between /home/ubuntu/test.sh, /
opt/test.sh, /etc/test.sh and /usr/bin/test.sh, as there is no
separated partition
lsblk
vda 252:0020G
75 matches
Mail list logo
