This turned out to be an issue with some infrastructure that command-
not-found uses to map binaries to package names. Nothing to do for
systemd.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: systemd (Ubuntu Kinetic)
Status: Confirmed => Won't Fix
--
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/1992979
Title:
kinetic ppc64le reporting
Public bug reported:
Randomly, my trackpad has a lot of trouble detecting movement, for 10 to
20 seconds, until it comes back. Used to happen every day in previous
versions, now every 3 days or so.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature:
This bug is stale, and it remains unclear if there is a systemd bug, so
marking invalid.
** 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.
Sorry for the delay in response. I have not had sufficient time to
investigate this further. Since it sounds like this can be observed on
recent systemd releases, and there are no Ubuntu specific patches that
stand out to me that might be causing this, please open an upstream bug
report so that
Only marked won't fix for Kinetic. Thanks for confirming it happens on
other releases.
--
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/1992979
Title:
kinetic ppc64le
** 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/1979352
Title:
system frozen after sleep
Status in
According to the reporter, this issue was not observed in Ubuntu 21.04
forward. I do not think there is a strong case for addressing this in
focal or bionic.
** Changed in: systemd (Ubuntu Bionic)
Status: Incomplete => Won't Fix
** Changed in: systemd (Ubuntu Focal)
Status:
Why won't fix? It occurs on other releases too.
--
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/1992979
Title:
kinetic ppc64le reporting Failed to send WATCHDOG=1
This bug was fixed in the package mesa - 23.0.3-0ubuntu2
---
mesa (23.0.3-0ubuntu2) mantic; urgency=medium
* rules: Set VERSION so that it also includes the packaging
revision. (LP: #2020604)
-- Timo Aaltonen Tue, 30 May 2023 09:53:55 +0300
** Changed in: mesa (Ubuntu)
** Description changed:
[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
I'm going to mark this incomplete
I suspect the issue is a consequence of a bad install -
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2023000
Regardless, if it's a real issue, it'll be re-filed...
** Changed in: evolution-data-server (Ubuntu)
Status: New => Incomplete
--
Public bug reported:
package linux-image-5.4.0-150-generic 5.4.0-150.167 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
exited with return code 1
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-150-generic 5.4.0-150.167
** 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/2023361
Title:
package linux-image-5.4.0-150-generic 5.4.0-150.167 failed to
** 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/1908140
Title:
Bond DHCP fails on Ubuntu Server 20.04
Public bug reported:
When I receive an e-mail, a notification appears. I click it in order
for Thunderbird to open on the correct e-mail. But Thunderbird doesn't
open right away, a new notification "'Thunderbird' is ready" appears,
which I have to click in order for Thunderbird to open correctly.
Marking as invalid for systemd since the bug is stale and it remains
unclear if there is a bug in systemd.
** 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
** Changed in: pcsc-lite (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1971984
Title:
pcscd.socket is disabled after
** Changed in: evince (Debian)
Status: New => Confirmed
--
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
Marking invalid for systemd due to age, and it being unclear whether
this is in fact a systemd bug.
** 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
There is no plan to SRU this to Focal. This feature should be available
in the 22.04 LTS, which ships systemd v249.11.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This bug is stale, so marking Won't Fix for systemd. For any similar
issues on newer releases/hardware, new bugs should be opened.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
When I want to shutdown my computer, very often since last Ubuntu
version, the process seems not to go to the end, and the computer never
shuts down. I used not to notice it, physically close my laptop and put
it back in my bag, then hours later find it very hot and with fans
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
This looks good to me, but the process to land this seems a bit
complicated because gdebi seems to be abandoned at its nominated
upstream, and has a slew of NMUs. I'm not sure what the etiquette is
here. Utkarsh said he'd take a look in the next few days.
** Changed in: gdebi (Ubuntu)
** Changed in: dbus (Ubuntu)
Status: In Progress => New
** Changed in: dbus (Ubuntu)
Assignee: Olivier Gayot (ogayot) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~ogayot/ubuntu/+source/dbus/+git/dbus/+merge/92
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/2023301
Title:
This bug was fixed in the package mesa - 23.0.4-0ubuntu1
---
mesa (23.0.4-0ubuntu1) mantic; urgency=medium
* New upstream release. (LP: #2021948)
- add a revert for amdgpu which missed 23.0.x branch
-- Timo Aaltonen Fri, 09 Jun 2023 12:53:37 +0300
** Changed in: mesa
It looks like this is actually new LXD behavior introduced in 5.14:
https://github.com/lxc/lxd/commit/ac09cfaff4. Previously, this would
have been fine to do, but the --reuse flag is needed to allow this.
** Changed in: systemd (Ubuntu Jammy)
Status: Confirmed => Triaged
** Changed in:
** Tags removed: foundations-todo
--
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/1991661
Title:
systemd mounts /run without noexec
Status in initramfs-tools
** Changed in: debconf (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1782577
Title:
docker: impossible to create image with
This looks low risk, but also low impact (how important is it to have
the correct model name output in lscpu?) in a core package installed on
all users' systems. I'm fine with the idea of such a change being
included in an SRU, but I think we wouldn't normally push an SRU *just*
for a change such
What makes you say the sessions are "leaked", exactly? Is there
something odd about the sessions listed? I realize that is a large
number, however.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch
Hello Robert, or anyone else affected,
Accepted cloud-init into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/23.2-0ubuntu0~22.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Robert, or anyone else affected,
Accepted cloud-init into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/23.2-0ubuntu0~20.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Summary changed:
- update-manager should guest an estimative of upgrade size to prevent running
out of free disk
+ update-manager should guess an estimative of upgrade size to prevent running
out of free disk
--
You received this bug notification because you are a member of Ubuntu
Touch
I think the current log levels and messages are appropriate, so marking
this won't fix.
** Changed in: systemd (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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/2016908
Title:
udev fails to make prctl()
This is done in the systemd-resolved package, which exists in Kinetic
and newer (previously systemd-resolved components were shipped in the
main systemd package).
However, I don't think this is something that we will SRU to Jammy or
Focal.
** Changed in: systemd (Ubuntu)
Status: New =>
I've tested /lib/systemd/systemd-ac-power on my laptop (which gives 0/1
for mains/battery) and it now returns 0 (mains) for my NUC10i3FNYHN.
(But the fix isn't in Lunar for on_ac_power.)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
/lib/systemd/systemd-ac-power works (on lunar). on_ac_power still does
not.
Perhaps on_ac_power should just be made a symlink to this - or the
script should exec that systemd executable if it exists?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
The man page should be up-to-date for Lunar and newer.
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I personally have become very accustomed to the current behavior where
/tmp is emptied on reboot -- I have no idea what most users would say
about this, so I wonder if changing that behavior would be unwelcome. I
do think it could be nice to have the 30d behavior back, however.
In other words, if
Stefano, thanks, that does feel much closer to a test case that models a
real-world scenario.
The doubt I still have is, if you're pulling something as fundamental as
setuptools from pip, why are you using virtualenv --system-site-packages
at all? Is this because it's embedded in third-party
I don't think this is relevant anymore.
** Changed in: systemd (Ubuntu)
Status: Triaged => Won't Fix
--
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/915215
Title:
Sorry for the delay, I got side tracked after initially proposing this
change to Debian. I will try and get this done for Mantic.
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
** Tags added:
According to the Debian bug, this is fixed in 251.2-3 by shipped a
separate libsystemd-shared package.
** Changed in: systemd (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** 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
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** 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/2021902
Title:
package linux-image-5.4.0-1108-azure 5.4.0-1108.114 failed to
Hi Steve.
I updated the patches containing the requested changes and uploaded them to
https://launchpad.net/~georgiag/+archive/ubuntu/lp1794064/+packages
Please let me know if you prefer I attached the debdiffs here.
I'm resubscribing ~ubuntu-sponsors. Thanks
** Patch removed:
** Description changed:
- add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul.
+ [ 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
** Changed in: systemd (Ubuntu)
Status: Triaged => 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/1937019
Title:
FIDO2 tokens not supported on this
Marc:
As it turns out, I executed this command and it appears the package
successfully installed:
sudo apt autoremove.
Thanks Marc
On Fri, Jun 9, 2023 at 2:27 PM Marc Deslauriers <2021...@bugs.launchpad.net>
wrote:
> Thanks for taking the time to report this bug and helping to make
Hello Robert, or anyone else affected,
Accepted cloud-init into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/23.2-0ubuntu0~22.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
The upstream consensus was basically "won't fix", and I don't think we
have a kernel/systemd combo in supported releases that would observe
this (focal has 5.4 kernel but systemd 245, and jammy has kernel 5.15).
** Changed in: systemd (Ubuntu)
Status: Triaged => Won't Fix
--
You received
It does not sound like there is anything for us to do on systemd. If
someone is still interested in a related feature request, please open an
RFE with upstream:
https://github.com/systemd/systemd/labels/RFE%20%F0%9F%8E%81.
** Changed in: systemd (Ubuntu)
Status: Triaged => Won't Fix
--
My understanding from a quick read is that there is nothing to do in
systemd. Please re-open if I am mistaken.
** 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
** Changed in: subiquity
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/2008952
Title:
DNS failure while trying to fetch user-data
Status
What release is this exactly? Have you tried any suggestions from
askubuntu? E.g. this one looks related (though I have not tested it)
https://askubuntu.com/questions/1254772/cryptsetup-waiting-for-
encrypted-source-device-swapfile-fstab-empty.
** Changed in: systemd (Ubuntu)
Status: New
This bug is awaiting verification that the linux-
nvidia-6.2/6.2.0-1003.3~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy' to
'verification-done-jammy'. If the problem
The reason it's specifically important to me not to clean at boot is
that schroot bind mounts /tmp by default but does not bind mount
/var/tmp by default, so I am accustomed (since long before the systemd
behavior became the norm) to using this directory for sharing data
between the host system
(setting bug back to New because I don't see any request for
information)
** 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.
I do see the behavior you are describing in those logs:
Apr 27 00:34:53 Y4M1-II systemd-logind[2855]: Power key pressed short.
Apr 27 00:34:53 Y4M1-II systemd-logind[2855]: The system will suspend now!
Apr 27 00:35:10 Y4M1-II systemd-logind[2855]: Operation 'sleep' finished.
Apr 27 00:35:45
Sorry, I realize the relevant snippet was already posted in the
description.
--
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/2023229
Title:
Autopkgtest failure for
I am seeing this in logs for all releases Jammy and newer.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: systemd (Ubuntu Jammy)
Status: New => Confirmed
** Also affects: systemd (Ubuntu Mantic)
Importance: Undecided
Status: Confirmed
**
It looks like this is the problem:
Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64
autopkgtest [16:21:39]: test tests-in-lxd: ---]
I am not sure why that image exists already now. Maybe we need to use a
random string in the image name somewhere to avoid
The referenced commit should be in Lunar and newer. Marking Won't Fix
for Kinetic as we are not planning on another SRU for that release.
** Changed in: systemd (Ubuntu Kinetic)
Status: Triaged => Won't Fix
** Changed in: systemd (Ubuntu)
Status: Fix Committed => Fix Released
--
** Changed in: ganeti (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/2009498
Title:
autopkg test failure
Status in ganeti
69 matches
Mail list logo
