I've reviewed/merged/uploaded the fix now
** Changed in: gtk+3.0 (Ubuntu Noble)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/207729
** Changed in: librsvg (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to librsvg in Ubuntu.
https://bugs.launchpad.net/bugs/2077918
Title:
librsvg 2.58.93+dfsg-4 causes FTBFS and au
** Also affects: kubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Also affects: lubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubuntu-gnome-meta (Ubuntu)
Importance: Undecided
Status: New
** Merge proposal unlinked:
https://cod
Public bug reported:
When a bug is filed against linux-firmware (or any other firmware
package), kernel logs should be collected and attached to the bug
report.
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a me
** Changed in: kubuntu-meta (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2068612
Title:
Please remove wireless-tools from
Going to close this invalid as there's clearly a broken disk and it's
failing to hash an mmaped file, hence the mmap()ed regions SIGBUSes when
the read fails.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
Starting with the librsvg 2.59 series (2.58.9*), librsvg requires
cargo-c to build. cargo-c comes from the Debian source rust-cargo-c.
The issue is that librsvg needs to be built on i386, but rust-cargo-c is
not currently built for i386. The list of Build-Depends is kinda lon
** Tags removed: need-duplicate-check
--
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/2078057
Title:
package udev 255.4-1ubuntu8 failed to install/upgrade: new udev
packa
Public bug reported:
sudo apt-get install wine
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: udev 255.4-1ubuntu8
ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
Uname: Linux 6.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Arch
Public bug reported:
Description:Ubuntu 22.04.2 LTS
Release:22.04
openssl:
Installed: 3.0.2-0ubuntu1.17
Candidate: 3.0.2-0ubuntu1.17
Version table:
*** 3.0.2-0ubuntu1.17 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
500 http://securi
You have been subscribed to a public bug:
In bug 2003027, Ubuntu's procps regressed the default qdisc from
fq_codel to pfifo_fast. Given that this was considered important enough
to justify changing behaviour in a stable release, we should have an
autopkgtest that verifies our intended delta again
Public bug reported:
In bug 2003027, Ubuntu's procps regressed the default qdisc from
fq_codel to pfifo_fast. Given that this was considered important enough
to justify changing behaviour in a stable release, we should have an
autopkgtest that verifies our intended delta against upstream, but we d
Accepting for 24.04. It is unfortunate to have to change behaviour in
this way, but this seems preferable than to switch to the reported-worse
qdisc just for 24.04, and also preferable to do sooner rather than later
in 24.04's lifetime, given that the .1 release is due this week.
However, if this
Hello Dave, or anyone else affected,
Accepted procps into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/procps/2:4.0.4-4ubuntu3.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
This missed making it into 24.04.1, but it'd be nice to get this
released immediately after the images for 24.04.1 are finalised, so that
users get the new behaviour from day one of using 24.04.1. I asked about
this in #ubuntu-release. It'd be a great help if this could be SRU-
verified *immediatel
** Tags added: regression-release
--
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/2003027
Title:
fq_codel qdisc compiled but not enabled on 22.10
Status in Ubuntu:
Fix Re
** No longer affects: openldap (Ubuntu Focal)
** No longer affects: openldap (Ubuntu Noble)
** Summary changed:
- Backport of openldap for focal, jammy and noble
+ Backport of openldap for noble
** Summary changed:
- Backport of openldap for noble
+ Backport of openldap for Jammy
** Changed i
** Changed in: openldap (Ubuntu)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
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/2073316
Title:
Backport of
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/2078243
Title:
package ca-certificates 20240203 failed to install/upgrade: ins
Public bug reported:
Encountered during Ubuntu Server upgrade from 22.04 to 24.04.
Run with 'sudo do-release-upgrade -d' on 2024-08-28 at ~ 12:00 UTC.
I'm aware that there's upcoming point release scheduled for the next 24-48
hours.
Output from 'lsb_release -rd':
No LSB modules are available.
De
** Also affects: ubuntu-release-upgrader
Importance: Undecided
Status: New
** Also affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
Hi,
Thanks for taking the time to report this issue.
Presumably, your boost.asio was not built against the libssl-dev headers
provided in Ubuntu, since in that version those function names aren't
provided as symbols but rather as preprocessor aliases to the more
modern TLS_* alternatives (see
htt
** Merge proposal linked:
https://code.launchpad.net/~waveform/ubiquity/+git/ubiquity/+merge/472161
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/2075337
Title:
[SRU
Public bug reported:
Merge openldap 2.6.8+dfsg-1~exp4 from Debian experimental, which also
fixes an FTBFS with i386.
** Affects: openldap (Ubuntu)
Importance: High
Assignee: Sergio Durigan Junior (sergiodj)
Status: In Progress
** Tags: ftbfs needs-merge upgrade-software-versi
I am planning an SRU for noble in the next couple weeks.
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2076023
Title:
Failed to apply '
Public bug reported:
In python3-setuptools/73.0.1-1, the usage of setup.py to run tests is
not supported anymore (it has been deprecated for a while).
protobuf/3.21.12-9 still uses setup.py to run tests (snippet from
debian/rules):
set -e; \
export LD_LIBRARY_PATH=$(CURDIR)/src/.l
** Tags removed: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to librsvg in Ubuntu.
https://bugs.launchpad.net/bugs/2077918
Title:
librsvg 2.58.93+dfsg-4 causes FTBFS and autopkgtes fail due to missing
depen
This bug was fixed in the package rsyslog - 8.2406.0-1ubuntu2
---
rsyslog (8.2406.0-1ubuntu2) oracular; urgency=medium
* d/usr.sbin.rsyslog: add apparmor rule to allow reading systemd sessions
(LP: #2056768)
-- Andreas Hasenack Tue, 20 Aug 2024 09:46:06
-0300
** Changed in:
Public bug reported:
Important logs:
19:55:29 gdm-session-wor: gkr-pam: unable to locate daemon control file
19:55:19 systemd: Failed to start fluidsynth.service - FluidSynth Daemon.
19:55:19 (uidsynth): fluidsynth.service: Failed to drop capabilities: Operation
not permitted
19:33:37 systemd: F
apport information
** Tags added: apport-collected
** Description changed:
Important logs:
19:55:29 gdm-session-wor: gkr-pam: unable to locate daemon control file
19:55:19 systemd: Failed to start fluidsynth.service - FluidSynth Daemon.
19:55:19 (uidsynth): fluidsynth.service: Failed
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2078284/+attachment/5810211/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https:/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2078284/+attachment/5810213/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://b
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2078284/+attachment/5810212/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubu
All autopkgtests for the newly accepted procps (2:4.0.4-4ubuntu3.1) for noble
have finished running.
The following regressions have been reported in tests triggered by the package:
c-icap/unknown (armhf)
dbus-test-runner/19.04.0-1build2 (s390x)
patroni/3.2.2-2 (s390x)
pslist/unknown (ppc64el)
rub
You have been subscribed to a public bug:
Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel()
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-142-generic x86_64
A
** 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/2078280
Title:
System Crash on reboot/screen lockout: systemd-logind crashed with
Looks like it's still a common issue:
https://errors.ubuntu.com/?package=systemd&period=week
but we'd need the crash ID or the machine's whoopsie ID to tell which
instance this is.
** Package changed: xorg (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: New => Inco
Also was there an assertion in the journal?
--
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/2078280
Title:
System Crash on reboot/screen lockout: systemd-logind crashed wit
38 matches
Mail list logo
