Public bug reported:
When shifting virtual desks (Alt-Ctrl-Left/Right arrow) one of the keys
(most notably an arrow-key) are not registered as released when arriving
at the destination desktop. E.e. I move one desktop to the right and
after releasing Alt+Ctrl+Right-arrow the system behaves like I'
Something doesn't feel right in the overall design here.
Bitbake wants to take away the ability to connect to network from its
child processes (which generally makes things more secure), and is not
allowed to do so by the system. Isn't this... backwards?
--
You received this bug notification bec
Ken, please be specific about what version of gnome-activity-journal you
tested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069170
Title:
[SRU] gnome-activity-journal instantly fails
To manage
I successfully completed the test cases on Ubuntu Desktop 24.04.4 LTS
using gnome-activity-journal 1.0.0-3ubuntu0.1.
However, I was unable to reproduce the original crash there with gnome-
activity-journal 1.0.0-3build1. This is similar to what Sudip said in
comment 2. But the fix doesn't make gno
The grub patch linked seems similar in that grub is not clearing the
mode correctly when you enter grub text mode, i.e. the menu is drawn/you
enter the console.
However I don't think you are entering the text mode in grub at all, but
you jump straight to the kernel as part of flicker free boot - o
*** This bug is a duplicate of bug 2056555 ***
https://bugs.launchpad.net/bugs/2056555
Yes, its best to mark this as a duplicate.
** This bug has been marked a duplicate of bug 2056555
Allow bitbake to create user namespace
--
You received this bug notification because you are a member o
Public bug reported:
using software updater, an error has occured while trying to upgrade
from 23.10 to 24.04
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: ubuntu-release-upgrader-core 1:23.10.14
ProcVersionSignature: Ubuntu 6.5.0-42.42.1-lowlatency 6.5.13
Uname: Linux 6.5.0-42-lowlatency
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python3-defaults (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056580
Ti
Hello, and sorry for the slow reply here.
I just tried, and I could reproduce the bug with Firefox 128 deb package
on Ubuntu 20.04 and Firefox 128 snap package on Ubuntu 22.04, but
Firefox 128 snap on Ubuntu 24.04 seems to render it correctly. Would you
be able to verify this?
Since the issue hap
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Milestone: ubuntu-24.04 => ubuntu-24.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874272
Title:
Stage "searching for obsolete softwar
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
No longer occurs with 1:2.43.0-1ubuntu7.1
** Changed in: git (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064598
Title:
Localized messages not availabl
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
I get the same error when building an image even in a Docker container
(crops) when ran on 24.04.
```
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/builds/yocto/shared/sources/core/bitbake/bin/bitbake-worker", line
278, in child
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-riscv/6.5.0-44.44.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-mantic-linux-riscv' to 'verification-done-
mantic-linux-riscv'. If
This bug is awaiting verification that the linux-starfive/6.5.0-1017.18
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-mantic-linux-starfive' to 'verification-done-
mantic-linux-starf
For reference, the specific implementation in bitbake that disables
networking is here:
https://git.openembedded.org/bitbake/tree/lib/bb/utils.py?h=2.8.2#n1673
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
It does seem that way. The problem is the design of unprivileged user
namespaces, it gives unprivileged applications access to a lot of kernel
surface that they usually don't have access to. This has been used to
elevate kernel bugs from root exploitable to being exploitable by
unprivileged users.
Public bug reported:
We have shipped a patch for glibc since groovy that adds a fallback path
for clock_nanosleep_time64 to use CLOCK_MONOTONIC, to work around a bug
in WSL1 (see bug 1871240). This has since been fixed in the WSL1
implementation (WSL2 is out of scope as they use a full-blown Linux
** Changed in: python-wcmatch (Ubuntu Noble)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060649
Title:
python-wcmatch not compatible to python3.12
To manage
@milev-philip:
containers are a difficult case. Unfortunately containers share the same
kernel as the host. An application running in the container (docker
image) can use unprivileged user namespaces to compromise not just the
container but the host as well.
There is the ability to turn the restr
@kanavin:
Thanks, we don't have an issue with bitbake, the issue comes down to
running code out of a user writable location.
1. The location of bitbake will vary by user. Making any profile we
could ship only functional for a subset of bitbak users. For the others
it would require a privileged ac
Fixed in https://salsa.debian.org/systemd-
team/systemd/-/merge_requests/267, so we will get it in Ubuntu soon.
** Changed in: systemd (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Thanks for picking this up.
I redacted the URI because some of the examples contained sensitive data
and the the value depends on the actual request, but it always seems to
be the actual request URI including the query string. Here are a few
examples that do not contain sensitive data:
URI has no
We'll probably have to wrap that code in an exception handler that would
instruct the user to install an apparmor profile as root, yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056555
Title:
A
Public bug reported:
Impact
--
This is a new stable release in the GNOME 46 series
It includes a crash fix
Changes since the current Ubuntu 24.04 LTS release:
https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/46.2...46.3
Test Cases
--
Complete the Basic RDP Test Case and
Public bug reported:
gnome-remote-desktop's build test is failing now in Oracular, but passes
in Noble
It has been failing in Debian since gnome-remote-desktop 46 was first
uploaded to Debian Experimental. This was worked around (badly) in
Debian by simply ignoring the test failure.
https://buil
I have uploaded a test package to the security team PPA here:
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages
If you could give it a spin and see if it fixes the issue, that would be
great. If it does, I'll release it as a regression update.
Thanks!
--
You receiv
This still affects at least vtk9 (Ubuntu 24.04 and 22.04) and vtk7
(Ubuntu 22.04).
Is there any prospect of the VTK patch being applied and these packages
updated?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dune-grid (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058415
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: vtk7 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058415
Title:
Readi
Note also the README.apparmor[1] explanation. Packages can also install
apparmor profile snippets in /etc/apparmor.d/rsyslog.d. If the default
of the freeipa package (or whatever produced /etc/ipa/ca.crt) is to
place certificate and keys in /etc/ipa, maybe it could ship such a
profile snippet.
1.
** Also affects: vtk9 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058415
Title:
Reading binary data in paraview broken by libexpat1 update
To
** Also affects: speech-dispatcher (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071468
Title:
ELF package metadata failure: environment variabl
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064539
Title:
Revert back frame pointers for ppc64el (remove -fno-omit-fram
** Patch added: "Patch for speech-dispatcher 0.12.0~rc2-2"
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/2071468/+attachment/5796206/+files/speechdd.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071334
Title:
intel-ipu6-dkms FTBS with the latest linux 6.8 hwe kernel in jammy
To manage notifications about this bug go to:
https://bugs.launchpad.n
$ dkms status
ivsc-driver/0~git202211241536.70d95269-0ubuntu0.22.04.2, 5.15.0-113-generic,
x86_64: installed
ivsc-driver/0~git202211241536.70d95269-0ubuntu0.22.04.2, 6.8.0-38-generic,
x86_64: installed
GA:
$ lsmod | grep vsc
intel_vsc 16384 2 mei_ace,mei_csi
HWE:
$ lsmod | grep vs
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apache2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072648
Title:
Re
@kanavin:
Bitbake could indeed do that, it will depend on if it is considered
worthwhile to carry said exception code. As I mentioned above both
capabilities and SELinux are working towards limiting of unprivileged
user namespaces, and the solutions needed to handle there restrictions
will be diff
This bug was fixed in the package mesa - 24.0.9-0ubuntu0.1
---
mesa (24.0.9-0ubuntu0.1) noble; urgency=medium
* Backport to noble. (LP: #2068918)
mesa (24.0.9-0ubuntu1) oracular; urgency=medium
* New upstream release. (LP: #2068918)
mesa (24.0.8-1ubuntu1) oracular; urgency=medi
The verification of the Stable Release Update for mesa 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 reg
This bug was fixed in the package mesa - 24.0.9-0ubuntu0.1
---
mesa (24.0.9-0ubuntu0.1) noble; urgency=medium
* Backport to noble. (LP: #2068918)
mesa (24.0.9-0ubuntu1) oracular; urgency=medium
* New upstream release. (LP: #2068918)
mesa (24.0.8-1ubuntu1) oracular; urgency=medi
The verification of the Stable Release Update for mesa 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 reg
Public bug reported:
* Impact
The package is currently built with malcontent disabled because the
package was in universe.
The corresponding MIR is now approved, including for Noble (lp:
#1892456). The package got promoted in Oracular already.
The malcontent library is needed to provide parenta
The option is enabled in Oracular
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-control-center (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Public bug reported:
After entering the password, the lock screen crashes and tries again,
still unable to log in. i am using ubuntu 22.04
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
This bug was fixed in the package xdg-desktop-portal - 1.18.4-1ubuntu2
---
xdg-desktop-portal (1.18.4-1ubuntu2) noble; urgency=medium
* Merge with Debian (LP: #2062394). Remaining change:
- Import https://github.com/flatpak/xdg-desktop-portal/pull/705 as a
distro-patch to
The verification of the Stable Release Update for xdg-desktop-portal 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
Public bug reported:
Even though GNOME Online Accounts now natively supports WebDav, CalDav
and CardDav, it doesn't work with Fastmail. This bug was recognised
upstream, and has been fixed upstream in 3.50.1.
Could Ubuntu release gnome-online-accounts 3.50.1 or newer in the Ubuntu
24.04 "updates"
I can confirm that the package that you provided fixes the issue for me.
Thank you very much for the quick help!
Your intuition seems to better than mine, because I have to admit that
it took me a while how the commit that you linked fixes the issue and
how it was previously introduced by the sec
I was able to resolve this by following the instructions on this page :
https://etbe.coker.com.au/2024/04/24/ubuntu-24-04-bubblewrap/
Basically create the file /etc/apparmor.d/bwrap with the following
contents :
abi ,
include
profile bwrap /usr/bin/bwrap flags=(unconfined) {
userns,
# Site
** Changed in: gnome-remote-desktop (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072768
Title:
gnome-remote-desktop build test failing in oracular
To manage
** Changed in: netcfg (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072671
Title:
Remove libiw-dev (wireless-tools) dependency
To manage notifications about
** Tags added: pe-sponsoring-request
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1982335
Title:
[24.10 FEAT] Valgrind: Support for new IBM Z Hardware (IBM z16)
To manage notifications about this
Public bug reported:
With notify-osd, the snap refreshment is done via a dialogue window
notification, which says
> Update available for firefox.
>
> Close the application to update now. It will update automatically in 13 days.
and has OK and cancel buttons.
Why is either button mapped in this
Awesome, thanks for testing it, I'll prepare updated packages to release
ASAP!
That's an excellent write-up of what is happening here, and is why I
suspected that commit was the cause.
** Also affects: apache2 (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: apache2 (U
This was fixed in
https://launchpad.net/ubuntu/+source/openldap/2.5.18+dfsg-0ubuntu0.22.04.1
which I just released into updates. Marking as "fix released" for jammy.
** Changed in: openldap (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you ar
This bug was fixed in the package openldap -
2.5.18+dfsg-0ubuntu0.22.04.1
---
openldap (2.5.18+dfsg-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream version (LP: #2067745).
- Fixed libldap exit handling with OpenSSL3 again (ITS#9952)
- Fixed libldap OpenSSL channel bin
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 a
** Also affects: apt (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Magali Lemes do Sacramento (magalilemes)
** Changed in: linux (Ubun
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072768
Title:
gnome-remote-desktop build test failing in oracular
To manage notifications about this bug go to:
https://b
Tested build: https://launchpad.net/~ubuntu-
cdimage/+livefs/ubuntu/noble/ubuntu-core/+build/651517
qcow2 image has been generated. Releasing.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received this bug notific
This bug was fixed in the package livecd-rootfs - 24.04.73
---
livecd-rootfs (24.04.73) noble; urgency=medium
* Build qcow2 images for ubuntu-core LXD support (LP: #2072759).
-- Łukasz 'sil2100' Zemczak Thu, 11 Jul
2024 13:15:43 +0200
** Changed in: livecd-rootfs (Ubuntu Noble)
The verification of the Stable Release Update for livecd-rootfs 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 encou
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-linux-
aws-6.8' to 'verification-done-jammy-linux-
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1011.12~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-linux-
aws-6.8' to 'verification-done-jammy-linux-
101 - 200 of 411 matches
Mail list logo
