NOT fixed !!!
This message, among several others, repeats rapidly, hard drive continually
seeks, system unusable. Reboot, runs ok for a while (couple hours or so), then
it starts again. Sometimes I have to use the reset button to stop it,
sometimes I can get to restart.
Just a very short set
Can someone explain in a noob friendly way how to install the 4.8.7-1
version from the kinetic testing repo? I am experiencing this bug on
Linux Mint 21 XFCE (Jammy) and PulseEffects 4.8.4-1 and don't know
enough to be able to figure it out on my own... can you post the
terminal commands to
Embarrassingly it seems that this week I'm getting more proper behavior.
I will keep trying to replicate here as time permits, but the system
applied some updates automatically and I also installed a few things
since the first incident (sane, wireshark, etc). Rolling everything
back isn't much of
** Also affects: bluez (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu Jammy)
Status: New => Triaged
** Changed in: bluez (Ubuntu Jammy)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Rafael, I have opened bug 1988364 to track that issue and future
backporting of the fix to jammy.
--
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/1982739
Title:
BlueZ 5.65
The fix is:
https://github.com/bluez/bluez/commit/62e591578e3f948e187aacf44ede4286fad37ad7
** Tags added: rls-jj-incoming
** Changed in: bluez (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
Sony WH-1000XM4 missing the A2DP profile and defaults to low quality
https://github.com/bluez/bluez/issues/313
** Affects: bluez
Importance: Unknown
Status: Unknown
** Affects: bluez (Ubuntu)
Importance: High
Status: Fix Released
** Tags:
We got bite by this but we added a cron to our 18.04 instances:
* * * * * host google.com || dhclient
works-for-us :-)
HTH,
Norberto
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I've retried the mtail test.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe] tzdata 2022c update
Status in tzdata package in Ubuntu:
Fix Released
The failure mode still exists if "udevadm trigger" has been issued
before the package upgrade to systemd 237-3ubuntu10.55.
That is, if unattended-upgrades or the user had installed open-vm-tools,
and has not rebooted yet, they will lose network connection on upgrade
to 237-3ubuntu10.55.
We need
Thanks for taking the time to report a bug and make Ubuntu better.
I tried reproducing the problem here but it seems there's something I'm
missing. I have a Samba AD DC setup (running Focal, but that shouldn't
matter) and I setup a Bionic client. I then obtained a ticket using
"kinit", verified
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Released => Fix Committed
--
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/1988119
Title:
systemd-udevd: Run
I've blindly retried both of these failures.
--
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 new platform name IBM z16
** Changed in: systemd (Ubuntu)
Status: Invalid => 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/1985887
Title:
systemd kills gnome-shell or
*** This bug is a duplicate of bug 1922414 ***
https://bugs.launchpad.net/bugs/1922414
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 1922414 ***
https://bugs.launchpad.net/bugs/1922414
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
There are a few upstream issues that seem to be related to this one, but
https://github.com/WayneD/rsync/issues/86 seems like the most likely
candidate.
Not using "-z" was determined to be a possible workaround here. If any
of you (who can actually reproduce the issue) can check if "-zz" also
All autopkgtests for the newly accepted tzdata (2022c-0ubuntu0.20.04.0) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
mtail/3.0.0~rc24.1-1ubuntu1 (armhf)
Please visit the excuses page listed below and investigate the failures,
Josh - Before applying your workaround, you can see which DNS servers
systemd-resolved is using by running:
$ resolvectl status
What does that show you for DNS servers? Your servers, or something else
entirely?
--
You received this bug notification because you are a member of Ubuntu
Touch
The verification of the Stable Release Update for openldap 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
This bug was fixed in the package openldap -
2.5.13+dfsg-0ubuntu0.22.04.1
---
openldap (2.5.13+dfsg-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream version (LP: #1983618).
- Several fixes, including memory leaks that affected libldap.
- Added slapo-emptyds contrib
I verified the upload on Jammy, Focal and Bionic via fresh LXC
containers, using the attached script.
For the ESM releases, it has been handled by sbeattie from the Security
Team. As I understand, the packages are already available in the ESM
security PPA (I don't have access to it).
**
I just created a new worker nodepool this morning, en redschedulded all
pods to the new workers. Solved it for us.
--
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/1988119
** Changed in: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1988300
Title:
systemd-resolved is not
bash upstream encodes the patchlevel into the version number, while
patches and security fixes in Ubuntu are applied on top of the upstream
version. That's expected behavior.
** Changed in: bash (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a
** Also affects: elfutils (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: elfutils (Ubuntu Jammy)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in
** Changed in: elfutils (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1987356
Title:
[BPO] elfutils/0.187-1 from
** Changed in: cyrus-sasl2 (Ubuntu Jammy)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1912256
Title:
I confirm that Mark Gerrits' approach worked also for my AKS instance.
Tahnk you very much.
--
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/1988119
Title:
systemd-udevd:
https://wiki.ubuntu.com/StableReleaseUpdates#tzdata says "Uploads should
also be made to any releases supported via ESM". I see a bug task but
nothing in the queue. What are your plans on this, please?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hello Jason, or anyone else affected,
Accepted tzdata into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2022c-0ubuntu0.22.04.0 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Jason, or anyone else affected,
Accepted tzdata into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2022c-0ubuntu0.18.04.0 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Jason, or anyone else affected,
Accepted tzdata into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2022c-0ubuntu0.20.04.0 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/429166
--
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/1988300
The bug is in the systemd packaging, and we have cherry-picked a fix [1]
from Debian that will be included in the next kinetic upload.
[1] https://salsa.debian.org/systemd-
team/systemd/-/commit/5d8a69933df0e9ce9e02ff07baed916ddc5af35e
** Changed in: dpkg (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => Fix Released
--
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/1988119
Title:
systemd-udevd: Run
Will this also be released for jammy soon?
I'm running into this issue which should be fixed with 5.65:
https://github.com/bluez/bluez/issues/313
** Bug watch added: github.com/bluez/bluez/issues #313
https://github.com/bluez/bluez/issues/313
--
You received this bug notification because
Can confirm we get rid off this issue on our Azure AKS setup; by updating our
NodePool's OS Image to
AKSUbuntu-1804gen2containerd-2022.08.10 (using k8s version 1.22.11)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Thanks for filing this bug, Peter.
The issue here is not related to /etc/resolv.conf being read-only (it is
actually a RW file) [1]. The issue lies in the fact that it is always
mounted in a running container by docker itself [2].
During a package installation process, dpkg performs backups of
@mruffell, spinning up a clean Azure 18.04 Bionic VM and following your
steps + reproducer, I can confirm DNS and network connectivity work
fine:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.6 LTS
Release:18.04
Codename: bionic
I confirm that Sebastiens approach worked also for my AKS instance.
Thank you and to everyone involved, I owe you a pint :)
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/comments/19
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Bug still exists in Kubuntu 22.04.1 and Pulseaudio 15.99
--
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/1961108
Title:
network options greyed out in paprefs
Status in
Oops, forgot about that. Done.
Also, ABI is not affected. We have symbols to track ABI, and there are
no symbols changes for libqt5network5.
** Description changed:
+ [Impact]
+
+ Qt 5 Network library does not use TLS 1.3 on armhf, and falls back to
+ less secure protocols.
+
+ [Test Plan]
+
Hi Matthew,
on our production Ubuntu VM in Azure we have problem to ping google.com
The version of prod Ubuntu is:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.5 LTS"
NAME="Ubuntu"
VERSION="18.04.5 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
Public bug reported:
[Partial copypaste from the linked upstream bug.]
Setting
NO_PROXY=localhost,127.0.0.1,::1
enables connections to http://localhost and http://127.0.0.1 and does
not work for http://[::1] at all. Apparently the problem is caused by an
assumption [1] that a hostname cannot
Fixed upstream and in >= Focal by:
https://github.com/curl/curl/commit/b7f90470be9b75f57167abbcd63aadb2e3b33958
** Description changed:
+ [Partial copypaste from the linked upstream bug.]
+
Setting
- NO_PROXY=localhost,127.0.0.1,::1
+ NO_PROXY=localhost,127.0.0.1,::1
enables
On 31/08/2022 10:38, mtu wrote:
> Note that with kdesu fixed, the hotfix to kubuntu-settings by Erich
> Eickmeyer can possibly be reverted, removing the ugly xterm workaround
> when launching Driver Manager from Kubuntu Settings.
Yes, if this update gets accepted into the main archive for jammy,
Apologies for the metadata bug traffic, I hadn't realized there were
duplicates, and actually use different bug numbers in the SRU and devel
uploads. Marking this manually as released on Kinetic, as the SRU
uploads use this bug number.
** Changed in: tzdata (Ubuntu Kinetic)
Status: Triaged
*** This bug is a duplicate of bug 1986984 ***
https://bugs.launchpad.net/bugs/1986984
** This bug has been marked a duplicate of bug 2022
iso-codes is not available for breezy
** This bug is no longer a duplicate of bug 2022
iso-codes is not available for breezy
** Description
Hello everyone,
I know there are quite a few people watching this bug, so I will provide
a status update.
The test package has been looking good throughout our internal testing,
and we have proceeded to build the next systemd update, version
237-3ubuntu10.55, and it is currently in the
Note that with kdesu fixed, the hotfix to kubuntu-settings by Erich
Eickmeyer can possibly be reverted, removing the ugly xterm workaround
when launching Driver Manager from Kubuntu Settings.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Sebastien Tardif (sebastientardifverituity) the fix you mentioned works
for me, thanks
--
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/1988119
Title:
systemd-udevd: Run
Shouldn't the bug be assigned to grub(/usr/sbin/grub-probe) instead of
lvm2 as the comment here explains ?
https://unix.stackexchange.com/questions/433313/strange-problem-lvs-
invocation-with-grub-on-debian-stretch#comment1232731_433407
The fact that lvm did extra work towards security and
On Jammy, I have installed the following packages from jammy-proposed:
- libkf5su-data (5.92.0-0ubuntu1.1)
- libkf5su5:amd64 (5.92.0-0ubuntu1.1)
- libkf5su-bin (5.92.0-0ubuntu1.1)
I have performed the following tests, in accordance with the bug description:
- launching KSystemLog from the K Menu
This bug was fixed in the package dbus - 1.14.0-2ubuntu2
---
dbus (1.14.0-2ubuntu2) kinetic; urgency=medium
* d/control: Add M-A: foreign to the new dbus-{session,system}-bus-common
packages to permit the resolver to use them to satisfy i386 dependencies
-- Dave Jones Tue,
The patch looks reasonable (assuming that it doesn't change ABI, which
seems to be the case). Could you be able to update the bug with the
necessary SRU information (the
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template can help
here)?
Particularly, the [Test Plan] and [Where problems
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
@mruffel thank you for the debdiff! With my limited systemd codebase
knowledge, this change feels fine. But I agree with the regression
potential section of the SRU description - we should make sure that the
update is well tested before going out as potentially it can change
behavior.
--
You
@sebastientardifverituity the Microsoft support fix you mentioned worked
for me.
--
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/1988119
Title:
systemd-udevd: Run
Is there an workaround for Azure Container Apps at this point?
--
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/1988119
Title:
systemd-udevd: Run net_setup_link on 'change'
Attached is a debdiff for systemd on Bionic which fixes this bug.
** Description changed:
- Two servers today that updated systemd to "systemd 237-3ubuntu10.54"
- https://ubuntu.com/security/notices/USN-5583-1
+ [Impact]
- could not resolve dns anymore.
- no dns servers, normally set through
61 matches
Mail list logo
