** Changed in: oem-priority
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/2025563
Title:
System can not shutdown if system has
A fix has landed in mutter 45.0:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3255
But I've also proposed a fix for Mesa:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25173
You only need one fix.
** Tags added: fixed-in-mutter-45.0 fixed-upstream
** Also affects: mesa
[Expired for initramfs-tools (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: initramfs-tools (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
[Expired for initramfs-tools (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: initramfs-tools (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
[Expired for initramfs-tools (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: initramfs-tools (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
The verification of the Stable Release Update for systemd 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 systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
The verification of the Stable Release Update for systemd 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 systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
The verification of the Stable Release Update for systemd 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 systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
The verification of the Stable Release Update for systemd 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 systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
The verification of the Stable Release Update for systemd 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 systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
The verification of the Stable Release Update for systemd 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 systemd - 252.5-2ubuntu3.1
---
systemd (252.5-2ubuntu3.1) lunar; urgency=medium
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 252.5-2ubuntu3.1
---
systemd (252.5-2ubuntu3.1) lunar; urgency=medium
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
The verification of the Stable Release Update for systemd 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
The verification of the Stable Release Update for systemd 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 systemd - 252.5-2ubuntu3.1
---
systemd (252.5-2ubuntu3.1) lunar; urgency=medium
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
The verification of the Stable Release Update for systemd 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 systemd - 252.5-2ubuntu3.1
---
systemd (252.5-2ubuntu3.1) lunar; urgency=medium
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 252.5-2ubuntu3.1
---
systemd (252.5-2ubuntu3.1) lunar; urgency=medium
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
The verification of the Stable Release Update for systemd 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 systemd - 252.5-2ubuntu3.1
---
systemd (252.5-2ubuntu3.1) lunar; urgency=medium
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
The verification of the Stable Release Update for systemd 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
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libwebp in Ubuntu.
https://bugs.launchpad.net/bugs/2035220
Title:
cve-2023-4863
Status in
(In reply to Christian G. Semke from comment #780)
> Here on my Lenovo Legion 7 Slim the audio never worked and the microphone
> worked until 6.4, now in 6.5 nothing works anymore. Does anyone know how I
> can resolve this? I'm a bit of a beginner
>
> Alsa:
** Summary changed:
- ubuntustudio-installer: error occurred while applying changes
+ ubuntu-desktop: unnecessary hard "Depends: pipewire-audio"
** Description changed:
+ Recommend demoting pipewire-audio from Depends: to Recommends:.
- I have installed successfully the standard Ubuntu 23.04
This bug was fixed in the package cups - 2.4.1op1-1ubuntu4.6
---
cups (2.4.1op1-1ubuntu4.6) jammy-security; urgency=medium
* SECURITY UPDATE: recently printed documents authentication issue
- debian/patches/CVE-2023-32360.patch: require authentication for
This bug was fixed in the package cups - 2.4.2-3ubuntu2.4
---
cups (2.4.2-3ubuntu2.4) lunar-security; urgency=medium
* SECURITY UPDATE: recently printed documents authentication issue
- debian/patches/CVE-2023-32360.patch: require authentication for
CUPS-Get-Document in
** No longer affects: libvirt (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/2033325
Title:
systemd fails to set unit as inactive when using socket activation
Hi Robert, thanks for the update to the description.
I would like to see two things
1. (Like Paride, I don't have a SRU hat to wear) While this updated
description elaborates on what has changed, it doesn't really go into
the "what can go wrong" territory. This is an important field for SRU
Public bug reported:
This is on 22.04.3, using coreutils 8.32-4.1ubuntu1.
We're wanting to populate an existing home directory with some starting
example files. The system will be running on an AWS EC2 instance, so
I'll use their default username "ubuntu" for this example:
# touch sourcefile
#
This bug was fixed in the package glibc - 2.35-0ubuntu3.3
---
glibc (2.35-0ubuntu3.3) jammy; urgency=medium
* Drop SVE patches due to kernal-related performance regression
* Fix the armhf stripping exception for ld.so (LP: #1927192)
glibc (2.35-0ubuntu3.2) jammy; urgency=medium
** Description changed:
[IMPACT]
uptime will provide incorrect data after 52 weeks. This is at least confusing
for users utilizing this tool.
Issue is already fixed in upstream
https://gitlab.com/procps-ng/procps/-/commit/8827c6763f79f77a126968e200b0e402de7cb749.
Latest procps
Thanks Paride for feedback.
1.
Old calculation is a little bit wrong.
It assumes that we have 52 weeks in the year - which is 60*60*24*7*52 ->
31449600 seconds
(31449600 - 1) will result in 51 weeks, 31449600 will result in 0 weeks (it is
assuming year has passed).
However year calculation is
I have tested the lunar-proposed package (2.4.2-3ubuntu2.3), and after
updating the package, and recreating the printer, it now defaults to
printing in colour when using Okular.
** Tags removed: verification-needed verification-needed-lunar
** Tags added: verification-done verification-done-lunar
Changing the printerdriver from driverless to a selected Cups driver for
the printermodell solved the issue on my end. It seems that snaps that
are not using Cups-control are having trouble with connecting to
printers using the driverless approach.
--
You received this bug notification because
No longer occurred due to fix or new version. Marked as Invalid.
** Changed in: wpa (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
Hello, I had a look at the debdiffs and they look good (clean upstream
cherry-picks). I think the packages are ready for sponsoring, but before
doing so I have a couple of questions.
1. The issue only happens *exactly* after 52 weeks, or something like
that, am I right? as I have systems that
This sounds like a consequence of a common problem with Intel graphics
-- the kernel occasionally misdetects the screen resolution.
It's not a big deal if only the startup animations are affected but let
us know if you have similar problems on the desktop (such as when
resuming from sleep).
**
Problem disappeared with recent ISO's. changing status ti Invalid.
** Changed in: ubuntu-meta (Ubuntu)
Status: Triaged => Invalid
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
On startup the left of my two screens (DP1.2 connected) appears fussy,
although not unreadable the font is not distinct. Furthermore, the
computer start up logo - in this case "intel nuc" remains in the middle
of the left screen. It always seems to be one screen that goes
I've created a PPA for Jammy that incorporates the fix mentionned. The
details are available at
https://launchpad.net/~adrien-n/+archive/ubuntu/openssl-jammy-sru .
Could you test it and confirm your issue is solved?
--
You received this bug notification because you are a member of Ubuntu
Touch
I've created a PPA for Jammy that incorporates the fix mentionned. The
details are available at
https://launchpad.net/~adrien-n/+archive/ubuntu/openssl-jammy-sru .
Could you test it and confirm your issue is solved?
--
You received this bug notification because you are a member of Ubuntu
Touch
I've created a PPA for Jammy that incorporates the fix mentionned. The
details are available at
https://launchpad.net/~adrien-n/+archive/ubuntu/openssl-jammy-sru .
Could you test it and confirm your issue is solved?
--
You received this bug notification because you are a member of Ubuntu
Touch
I've created a PPA for Jammy that incorporates the fix mentionned. The
details are available at
https://launchpad.net/~adrien-n/+archive/ubuntu/openssl-jammy-sru .
Could you test it and confirm your issue is solved?
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: wget (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wget in Ubuntu.
https://bugs.launchpad.net/bugs/2029930
Title:
wget crash when printing download rate
Status in
Has this been seen more recently than 18/08?
--
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/2031899
Title:
File system layers missing - unable to boot live cd
56 matches
Mail list logo
