Here's how to reproduce this in a LXD VM:
Download Ubuntu 24.04 Desktop image into ~/Downloads
Import the ISO
$ lxc storage volume import default ~/Downloads/ubuntu-24.04-desktop-amd64.iso
24.04-desktop --type=iso
Prepare a LXD VM
$ lxc init --empty --vm lxd-noble-fde -c limits.memory=6GiB -c
*** This bug is a duplicate of bug 2060676 ***
https://bugs.launchpad.net/bugs/2060676
** This bug has been marked a duplicate of bug 2060676
login: remove pam_lastlog.so from config
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
The issue was introduced with https://github.com/shadow-
maint/shadow/pull/237
Basically, the previous group validation was done using glibc's getgrid
directly, which was presumably coping well with the RO status of
/etc/group, but that poses consistency problems because you could add a
local
:00
** Also affects: software-properties (Ubuntu Noble)
Importance: Critical
Assignee: Simon Quigley (tsimonq2)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-propert
** Summary changed:
- Software sources not correctly updated after upgrade and/or new installs
+ [SRU] Software Sources is not compatible with deb822
** Summary changed:
- [SRU] Software Sources is not compatible with deb822
+ Software Sources is not compatible with deb822
** Summary changed:
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2063200
Title:
useradd --extrausers --groups tries to lock /etc/group
Status in shadow
Quick repro steps:
❯ lxc launch ubuntu-daily:noble shadow
Creating shadow
Starting shadow
❯ lxc exec shadow bash
root@shadow:~# mv /etc /etc_write
root@shadow:~# mkdir /etc
root@shadow:~# mount -o bind,ro /etc_write /etc
root@shadow:~# useradd --extrausers --groups somegroup somenewuser
useradd:
** Changed in: shadow (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2063200
Title:
useradd --extraus
** Changed in: software-properties (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2061214
Title:
Software
I just tested 5.21/stable and couldn't reproduce as it properly disable
the /proc/sys/kernel/apparmor_restrict_unprivileged_userns and
/proc/sys/kernel/apparmor_restrict_unprivileged_unconfined that would
otherwise have caused those denials.
Marking as incomplete until you can reproduce with
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2061214
Ti
Thanks for the follow-up!
** Changed in: lxc (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/2060965
Title:
liblxc is missing in
** Also affects: apport-symptoms (Ubuntu)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu)
Status: New => Invalid
** Description changed:
Apport version: 2.28.0-0ubuntu1
Ubuntu-Server 24.04 Beta amd64 (20240410.1)
- See attached screenshot for error.
+
What now remains to be done is to heavily patch faketime to, when on
armhf:
1/ use the proper symbols from glibc (e.g. __clock_gettime64 instead of
__clock_gettime)
2/ expose those symbols instead of the legacy 32-bit ones.
--
You received this bug notification because you are a member of
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Tags added: rls-nn-incoming
--
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/1951491
Title:
Can't run
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on armhf,
- and possibly on all archs.
+ click 0.5.2-2 is stuck in -proposed. autopkgtest now fails on ppc64el,
+ s390x.
- armhf
Oh, hang on. The bash build has apparently been uploaded just a day
after the t64 gcc, which means gcc was presumably still building when
the bash build started:
gcc-13 armhf 13.2.0-13ubuntu1 (from the bash build logs)
A bash rebuild should "fix" this somewhat. Well, at least a little bit.
**
** Changed in: glibc (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to liblocale-gettext-perl in
Ubuntu.
https://bugs.launchpad.net/bugs/2052930
Title:
liblocale-gettext-perl
It turns out the fix was already in the upstream repo as a PR for a
while (couple of years?). I've submitted a Salsa MR to proactively
address the issue before it shows up there:
https://salsa.debian.org/perl-team/modules/packages/liblocale-gettext-
perl/-/merge_requests/1
and I've uploaded the
Unless I'm missing something, the issue you're linking is about glib,
not glibc. Reassigning the bug accordingly.
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notification
Public bug reported:
Release of Ubuntu: Noble
Package Version: 5.72-0ubuntu1
My headset changed profile from A2DP to HSP as I received a phone call on my
phone (the headset can connect to multiple BT devices).
I'd expect the system to adapt to the new profile (add a new source, change the
Public bug reported:
As a header to all .conf files in systemd there's a comment saying
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file (or a copy of it placed in
# /etc/ if the original file is shipped in /usr/), or by
We had a mitigation for this in glibc but the latest change from simply
denying the unshare() call to allowing it but then denying anything
requiring capabilities *presumably* broke the glibc test suite again.
I'm only basing this from looking at the test logs, as I'm temporarily
unable to run
@enr0n, yes, I did restart systemd-networkd after creating
/etc/systemd/network/10-netplan-vlan1.network.d/keep_master.conf.
If you want to reproduce, the steps outlined in the bug descriptions
should provide you with a simple reproducer.
--
You received this bug notification because you are a
@enr0n, the proposal to add:
bridges:
br0:
interfaces: [vlan1]
To the network config defeats the purpose. The goal is to not have to do
double configuration. The bridge is define in LXD, the vlan1 only in
netplan.
The other proposed fix of `KeepMaster=true` snippet in
FYI, snapd is a "base-less" snap:
$ lxc launch ubuntu-minimal-daily:22.04 c1
$ lxc shell c1
root@c1:~# snap list
No snaps are installed yet. Try 'snap install hello-world'.
root@c1:~# snap install snapd
2024-02-15T21:17:09Z INFO Waiting for automatic snapd restart...
snapd 2.61.1 from Canonical✓
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2020110
Title:
Migrate netplan settings to this package
Status in network-manager
Per discussions in the appropriate PR for Calamares[1], this should be
done in network-manager itself.
The appeal is more custom approaches. Downstreams and vendors of Ubuntu.
[1] https://github.com/calamares/calamares/pull/2284
** Also affects: network-manager (Ubuntu)
Importance: Undecided
** Tags added: foundations-todo
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: glibc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
Public bug reported:
The autopkgtests for liblocale-gettext-perl fail against glibc 2.39 with
the following errors:
autopkgtest [15:27:03]: test autodep8-perl-build-deps: [---
243s t/bind.t ...
243s 1..1
243s # Running under perl version 5.036000 for linux
243s # Current
After further investigations into the gzip issue in python 3.12, it
turns out there was an undocumented change: it is now a buffered writer.
So the fire pattern used in the snippet above doesn't work
anymore, we now need to use it as a proper IO object instead.
I still think this should be
** Also affects: python3.12 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
-debian/rules override_dh_auto_test
+ [Description]
+
+ Python 3.12 gzip.GZipFile.write() outputs truncated data in some cases
+ (maybe all?)
+
+ [Test Plan]
+
+ Run the following
Hi!
Thank you for taking the time to report this. Could you confirm on which
version of Ubuntu you're seeing this issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libtimezonemap in Ubuntu.
This was verified on Mantic with -proposed (1:5.0.1-0ubuntu8~23.10.1).
Here's how:
$ lxc launch ubuntu-daily:23.10 c2
Creating c2
Starting c2
$ lxc shell c2
root@c2:~# apt-get update
...
root@c2:~# apt-get install -Vy liblxc-dev
Reading package lists... Done
Building dependency tree... Done
This was verified on Jammy with -proposed
(1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1). Here's how:
$ lxc launch ubuntu-daily:22.04 c1
Creating c1
Starting c1
root@c1:~# apt-get update
...
root@c1:~# apt-get install -Vy liblxc-dev
Reading package lists... Done
Building dependency tree... Done
Reading
** Description changed:
In removing the LXD snap from preseeding in the server seed for Ubuntu
- 24.04 as part LP #2051346 [1] we also removed the snaps snap and the
+ 24.04 as part LP #2051346 [1] we also removed the snapd snap and the
core22 snap.
This means that are subsequent snap
** Changed in: glibc (Ubuntu)
Status: Triaged => Fix Released
** Changed in: pango1.0 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pango1.0 in Ubuntu.
So, after some fairly exhausting debugging, I kind of gave up on that
bug, but as a last ditch effort I tried a rebuild against the latest
snapshot (even though the changelog didn't seem particularly relevant),
nd... Now it builds.
I'm so tired.
--
You received this bug
@bdrung, I just noticed this package is now in universe in Noble. Is the
demotion related to this bug?
--
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/2047939
Title:
Let
** Patch added: "delta-delta.patch"
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2049885/+attachment/5741436/+files/delta-delta.patch
** Changed in: console-setup (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of
Using a fast HTTPS server (same LAN as client), the `main.py` tests goes
from ~8s to ~2.5s:
# time python3 /tmp/main.py
Distro: Ubuntu 22.04.3 LTS
Python Version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
OpenSSL Version: OpenSSL 3.0.2 15 Mar 2022
0 1 2 3 ... 99
real0m8.163s
user
In fact, the same but updated note was already on
https://documentation.ubuntu.com/lxd/en/latest/installing/#install-lxd-
from-source where it mentions that it affects 22.04 onward while the one
you dug up says 23.04/23.10 are not affected ;)
--
You received this bug notification because you are
** Changed in: glibc (Ubuntu)
Importance: Undecided => Critical
** Changed in: glibc (Ubuntu)
Status: New => Triaged
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Simon Chopin (schopin)
** Tags added: foundations-todo
--
You received this bug notification be
I'm currently focused on cataloguing failures, but I'll try to
investigate it if nobody has picked it up by then.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2049881
Public bug reported:
Hi,
The package pango1.0 failed to build during the recent full archive test
rebuild against a snapshot of the the development branch for the
upcoming glibc 2.39, expected to land in Noble. This was subsequently
confirmed locally against a more recent snapshot.
Full logs
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu)
Status: New => Triaged
** Changed in: glibc (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Hi! Thanks for raising the issue.
Given the relative complexity of the patch and the low number of
affected people, I don't feel we should be shipping this as a Ubuntu-
specific patch. It might be a better idea for you to raise the issue on
the upstream ML, possibly amending the original patch to
** Changed in: bluez (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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2049352
Title:
Package BlueZ 5.72 for Noble
Status
This was missing a build dependency on python3-pygments (which is in
Main), I added it.
Testing well with my Beats Flex, YouTube Music with the Firefox Nightly
snap. I can adjust the latency offset with no issue, and blueman DTRT
with connecting and disconnecting. Popped open journalctl and
** Changed in: vim (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/2040011
Title:
[SRU] Ensure supported codenames are
** Also affects: iptables (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/2049318
Title:
free(): double free
** Changed in: vim (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 vim in Ubuntu.
https://bugs.launchpad.net/bugs/2047982
Title:
Highlighting of patches offers
sarnold, good point!
Holger: I can't pretend speaking for the SRU team, but I'd be willing to
bet that having "the fix is trivial" as a test plan would result in the
SRU being trivially rejected :-).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
It looks like I was overly strict with the MIR compliance, which sort of
balances out this bug as a whole. :)
After it migrates, Gianfranco or myself will try reverting ubuntu2 to
see if we can push those two packages forward.
--
You received this bug notification because you are a member of
https://github.com/vim/vim/pull/13825
I will test this first in Debian, upload it there, then do a merge.
** Changed in: vim (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
> Please also remember to commit proposed changes to
https://git.launchpad.net/~bluetooth/bluez
Force pushing my local commits over, sorry not sorry. :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
> Simon, ell already has a recent approved MIR LP: #1971738
Er, the binary packages in question don't.
--
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/2047780
Title:
Bl
I'm pretty shocked, I ran a local sbuild with this and yet it still
FTBFS. Doing an ubuntu2 upload as a fixup.
I would think that because we use the published tarball and not the
upstream source like Debian does, that would affect our ability to ship
the -test package.
Something's up with my
At first I was just going to say, ell-dev isn't built on i386 and it's
not arch:all, of course it will need an i386 allowlist entry! However,
this is the output I'm getting:
```
$ check-mir
Checking support status of build dependencies...
* debhelper-compat does not exist (pure virtual?)
*
** Changed in: bluez (Ubuntu)
Status: Fix Released => In Progress
** Summary changed:
- BlueZ release 5.71
+ BlueZ release 5.71 and merge from Debian
** Changed in: bluez (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => Simon Quigley (tsimonq2)
--
You received this bug notifi
Reviewed and uploaded.
For the particular patch series attached to this very bug, I'm seeing
the patchset as two distincts parts. First are a few optimization
patches by being more selective in flushing some caches, whereas the
second part are behaviour changes that belong more in the realm of
Daniel, I don't want you to feel burned over this. That wiki page does
seem quite rational, and I appreciate that you linked it. I'm reading
some mixed feelings, so let me be clear: thank you for the work you
*are* able to put into this.
Both Gianfranco and I are Ubuntu Core Developers but are
Is there any terminal in which the default is actually readable?
** Changed in: vim (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
** Changed in: vim (Ubuntu)
Milestone: None => ubuntu-24.04-feature-freeze
** Changed in: vim (Ubuntu)
Importance: Undecided =&g
> In other words, asking an Archive Admin to build binfmt-support on
i386.
I have stopped short of this so far because I'm entirely unsure if we
still need that build dependency in the first place. Debian doesn't have
it, and I'm not sure I see rationale on our end for it.
There is probably
Following the dependency chain through to the cause for the i386 builds,
binfmt-support should be added to the i386 allowlist. This may be a bug
in evolution-data-server in the case libebook-contacts-1.2-4 can build
without libphonenumber8-protobuf32 - for now, blanket-disabling that
dependency in
This is now blocking a Lubuntu feature goal. I tested this locally with
my bluetooth earbuds, and have been streaming audio with no problems.
Uploaded Gianfranco's packaging with some minor tweaks.
Please, we *need* to merge this from Debian *this* cycle. The Security
Team will NOT be happy when
Rik mentioned a common mistake that I've been trying harder to catch
(but didn't in this case, to my great frustration)...
If we're doing a merge and an orig tarball already exists in Debian,
always always ALWAYS grab that one instead of using uscan or finding the
tarball yourself. It breaks
The reason I essentially blindsponsored this was out of faith and
courtesy for the Desktop Team.
Lubuntu does similar things, but we have a merge party from Debian once
a cycle. If your response would be "we don't follow Debian," *I get it*,
but once or twice a cycle a merge should really be
Hi! Thank you for filing a bug and contributing to Ubuntu.
We're able to partially confirm this bug by simply having cloud-init
installed on our system and running `ubuntu-bug libc6`, which will start
off by printing 'cloud-init run data not found on system. Unable to add
cloud-specific data.' on
Little bit of data here. For some reason glib2.0 is thinking we're in a
GDB context and so is spitting out a SIGTRAP rather than the expected
SIGABRT, see
https://sources.debian.org/src/glib2.0/2.78.3-1/glib/gmessages.c/#L556
Now, why is it aborting I'm not too sure. The stack trace gives us a
Hi again!
Thanks for filing the multiple detailed bugs, this is greatly
appreciated as it makes triaging much easier!
In this instance, I'm closing this as Invalid since this output isn't
directly apport/ubuntu-bug related, it's the output of some tools we're
invoking under the hood, and/or GTK
Hi, thanks for taking the time to report this issue and contributing to
Ubuntu :)
I confirmed this issue (along with the one with firefox snap vs deb).
This is a bit bigger of an issue, as it means some non-privileged users
won't be able to report issues (or at least would give up as soon as the
Hi, thanks for taking the time to report this issue and contributing to
Ubuntu :)
I just confirmed on my system.
Since the number of transitional packages is fairly small, I think we
should just maintain a hardcoded list in Apport and hide the .deb by
default (with maybe a way to override this?)
Daniel, if you'd like to iterate on this (a debdiff for an ubuntu2
upload), it would be appreciated.
If you don't have the time, say the word, this looks like a simple fix.
...on everything but i386. What's up with that?
--
You received this bug notification because you are a member of Ubuntu
** Changed in: openssl (Ubuntu Jammy)
Assignee: Adrien Nader (adrien-n) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/2033422
Ti
> 34174 lines in this case is not plausibly reviewable.
I typically use filterdiff to get the packaging changes, and review
specific source files as necessary (including copyright changes in the
diff, which can be important, even if you're just using a script for
it).
Thanks for your help here.
I very much dislike reviewing packages this way. For a package to be in
the sponsorship queue, it needs to have a debdiff, not a debian.tar.xz.
I understand that it's a new upstream release, but that does not excuse
the need for a debdiff, even if you *also* include these files.
I'm uploading
A bug still exists here. GTK as a standalone package should not set Yaru
as a default, especially if it doesn't declare it as a dependency.
lxqt-session was simply a workaround. The Ubuntu Desktop Team needs to
move this to their default settings package, and adjust GTK to
appropriately read
signed) => Simon Quigley (tsimonq2)
--
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/2047705
Title:
Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Critical
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Confirmed
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in
Uploaded with a changelog tweak. It looks like there is precedent for
this, but it's in the SRU team's hands now.
DEP-3 patch headers next time? ;)
** Also affects: modemmanager (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: modemmanager (Ubuntu)
Status: New =>
** Changed in: lubuntu-update-notifier (Ubuntu)
Importance: Undecided => Medium
** Changed in: lubuntu-update-notifier (Ubuntu)
Status: New => Confirmed
** Changed in: lubuntu-update-notifier (Ubuntu)
Milestone: None => ubuntu-24.04-feature-freeze
** Changed in:
: Undecided => Medium
** Changed in: calamares (Ubuntu)
Status: New => Fix Released
** Changed in: calamares (Ubuntu)
Milestone: None => ubuntu-23.11
** Changed in: calamares (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
--
You received this bug notification
Unsubscribing sponsors, since there are merge conflicts.
** Merge proposal linked:
https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/457541
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: busybox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/2022927
Title:
Busybox mount fails to mount Snaps
Status
Tagging this to discuss this during the Foundations weekly meeting
** Tags added: rls-ff-incoming rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
I have the same problem, this bug has been around for quite some time as
it seems. Is there no fix available?
I have this problem with multiple machines, but I don't even find any
useful information about the copymods package aside from this bugreport
and the related posts.
--
You received this
I have what looks to be a similar issue. I suspect the boot partition
may be the problem:
user@host:~$ df -h /boot
FilesystemSize Used Avail Use% Mounted on
bpool/BOOT/ubuntu_ykzcyk 295M 289M 5,5M 99% /boot
user@host:~$ mount | grep -w /
rpool/ROOT/ubuntu_ykzcyk on / type
How about directly sending a SIGSEGV or a SIGABRT to a working
teamviewer process using kill(1) ? That's what I usually do when I test
apport crash reporting code, this might trigger the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Summary changed:
- liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic
+ liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** Changed in: cron (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 cron in Ubuntu.
https://bugs.launchpad.net/bugs/2044015
Title:
please merge cron 3.0pl1-178 from
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2043713
Title:
armhf autopkgtests fail due to
Public bug reported:
autopkgtests are pretty reliably failing[1] on armhf due to the
following (single) test failure:
638s === FAILURES
===
638s TestApportValgrind.test_valgrind_min_installed
638s
> I don't know why LP expired this bug since you commented after I changed
> the its status...
AFAIK, LP will not switch back the status to anything after a comment has been
left. That makes sense, as it wouldn't know what the new status is
supposed to be.
--
You received this bug notification
A version containing a fix for this has been uploaded to the Jammy queue
to be processed by the SRU team. Thanks, Adrien :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
A version containing a fix for this has been uploaded to the Jammy queue
to be processed by the SRU team. Thanks, Adrien :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
A version containing a fix for this has been uploaded to the Jammy queue
to be processed by the SRU team. Thanks, Adrien :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
In addition, could the test plan maybe be edited to answer the following
question?
"How can one validate that the package in -proposed addresses the
issue?"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
I'm very much against uploading this fix as an SRU. While it is a shame
that we have interop problems with the rest of the world, fixing this in
Jammy right now means we *will* break production for anyone that stores
Blowfish-encrypted data.
Doing `apt upgrade` on a production server is supposed
I am not going to upload this, because I'm widely uncomfortable with bug
1990216 (details there).
In addition, I have a few superficial suggestions for aesthetics:
* Use lpX subdirectories in d/patches rather than add a prefix to the
patchname
* Add a Bug-Ubuntu field with a LP URL to each
1 - 100 of 1674 matches
Mail list logo
