Thank you for your report!
However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.
Thank you for your understanding, and
Public bug reported:
unexpected crashed
ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: network-manager 1.45.90-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
ApportVersion:
@sudipmuk loupe should be fixed in Beta3
--
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/2046844
Title:
AppArmor user namespace creation restrictions cause many
@eeickmeyer geary should be fixed in Beta3
--
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/2046844
Title:
AppArmor user namespace creation restrictions cause many
@guyster, @eldmannen+launchpad, @valeryan-24
Firefox dailies now have a work around, by detecting and disabling the
user namespace. The proper fix that should allow firefox to still use
the user namespace for its sandbox will land in Beta3, landing early
next week.
--
You received this bug
@pitti: yes this intended. At this stage we are essentially enumerating
the known users of unprivileged user namespaces. We can ship the profile
for you or you are welcome to ship it.
In the future this is going to gradually tighten, some of the
"unconfined" profiles will be developed into real
This affects all current releases AFAICT.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug
It solves several problems, but not all.
With regard to unprivileged user namespace mediation it should fix
- mscode
- nautilis
- devhelp
- element-desktop
- piphany
- evolution
- keybase
- opam
the element-desktop is still known to have some issues, which are on the snapd
side. It
** Tags removed: mantic
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to hicolor-icon-theme in
Ubuntu.
https://bugs.launchpad.net/bugs/2033165
Title:
310 empty dirs created by hicolor-icon-theme
Status
Public bug reported:
Resolved (253 on Ubuntu Server 23.10) seems to continue DNS recursion
after responding with an authoritative answer. i.e. DNS blacklist is
configured in /etc/hosts... see
https://github.com/systemd/systemd/issues/31223
Fixed in
FFe granted.
** Changed in: openssl (Ubuntu)
Status: New => Triaged
--
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/2056593
Title:
[FFE] FIPS compatibility
apparmor 4.0.0~beta2-0ubuntu3 installed today from proposed solves problem of
bug https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2047256, does it
solve other problems too?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Great, I'll leave this bug open for now. Please let us know if there is
anything that is enabled that shouldn't be. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
I may have put 2+2 together and made 5 here then. Pulling strings from the
library i could see one of the insults that i thought was only included
inside the elseif statement for PC being set. I'll double check as i may
have been looking at an old git revision, or perhaps there was a config
option
Adding the lines:
listen-on port 53 { localhost; 192.168.122.0/24; };
allow-query { localhost; 192.168.122.0/24; };
to /etc/bind/named.conf.options helped
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in
** Changed in: openssh (Ubuntu Noble)
Importance: Critical => High
** Changed in: openssh (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: openssh (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: openssh (Ubuntu Jammy)
Assignee: (unassigned) => Andreas
I'm not sure I understand this bug, the --with-pc-insults option is
deprecated since 2017-09-18 as it is the default option.
The noble package doesn't use --enable-offensive-insults.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Description changed:
[ Impact ]
- * An explanation of the effects of the bug on users and
+ The gssapi-keyex authentication mechanism has been inadvertently broken
+ in openssh. It comes from a distro patch[1], and while the patch still
+ applied, it was no longer correct.
- *
** Description changed:
- The Authmethod struct now have 4 entries but the initialization of the
- method_gsskeyex in the debian/patches/gssapi.patch only have 3 entries.
+ [ Impact ]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/openssh/+git/openssh/+merge/462514
--
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/2053146
Public bug reported:
Tame as they might be, I'd like to continue using "Defaults insults" without
any risk of upsetting anyone (and without having to maintain our own package
version.)
Would the safe insults version at compile time "--with-pc-insults" be a
sensible default for all?
Current as
Bump this is also affecting us causing quite a lot of downtime just to
add a vlan interface
--
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/2052137
Title:
bonded link goes
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2049995
Title:
System volume doesn't
Erich Eickmeyer, I don't have a Tuxedo Computer to test, so could you
please check if the following profile works for you?
$ echo "# This profile allows everything and only exists to give the
# application a name instead of having the label "unconfined"
abi ,
include
profile
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
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/2057996
Title:
ubuntu-24.04 version:
Somehow this was fixed for me by the following (almost random) sequence
of steps:
1. remove resume/resume_offset kernel parameters from /etc/default/grub
2. update-grub, reboot: hibernate options appear in ubuntu shutdown menu
3. hibernate: works, no more "invalid argument" error.
4. resume(power
** Merge proposal linked:
https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/462501
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
I can confirm that putting aside vscode.list allowed me to do the upgrade
Thanks
Xavier
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/2047447
Title:
No valid
Public bug reported:
Impact
--
The autopkgtest for 0.96.20.12, which introduces Ubuntu Pro in Xenial's
software-properties, failed on Dbus tests[1].
The failure is because, at some point in time, the .keep file were
removed from the otherwise empty tests/aptroot/etc/apt/apt.conf.d/. This
Hello Hui, or anyone else affected,
Accepted pulseaudio into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:15.99.1+dfsg1-1ubuntu2.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Hui, or anyone else affected,
Accepted pulseaudio into mantic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:16.1+dfsg1-2ubuntu4.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Normalerweise landen gelöschte Dateien im Papierkorb. Hast du geprüft,
ob diese Dateien noch im Papierkorb liegen? Erst nach dem Löschen aus
dem Papierkorb wird der Platz auf der Festplatte frei.
** Changed in: tzdata (Ubuntu)
Status: New => Incomplete
--
You received this bug
I just looked at the changes, and I would prefer to have a new SRU bug
for those, yes please.
--
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/2029473
Title:
Queued where? I don't see it in xenial unapproved. If it's just fixing
the autopkgtests, not the software-properties code or anything else in
debian/*, then no need for a new SRU bug. Just make sure to build it
with the appropriate -v parameter to include all changes since
0.96.20.10 (IIRC).
--
Ah, software-properties, sorry, I still had update-manager in my mind.
--
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/2029473
Title:
Backport Ubuntu Pro to
So, I believe the best solution here would be to add options to DNS
addresses, similar to what we do with IP addresses. Something like this
nameservers:
addresses:
- 1.2.3.4:
sni: domain
port: 1234
interface: eth123
- 1.1.1.1
with this we'd fully support both
** Description changed:
We have an open MR with a handful of FIPS compatibilty changes we wore hoping
to get into 24.04. The main purpose of the changes is to detect whether the
kernel is running in FIPS mode and adjust the behavior of the library
accordingly by loading the correct
** Changed in: openssl (Ubuntu)
Milestone: None => ubuntu-24.04
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Adrien Nader (adrien-n)
** Changed in: openssl (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
I did some additional tests too in a noble container.
With/without the env var to set the file location, including with the
file missing, with/without the env var to force FIPS mode, and using
values 0, 1, 42, -42, a.
By the way, note that access to these environment variables uses
** Merge proposal linked:
https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+merge/462486
--
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/2058017
** Summary changed:
- [FFe] openssl is not LTO-safe
+ openssl is not LTO-safe
--
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/2058017
Title:
openssl is not LTO-safe
** Description changed:
tl;dr: since it's too much work to make openssl LTO-safe, upstream
doesn't see it as a goal and doesn't test it, and there are probably no
performance gains to LTO for this package.
Openssl is an old project and the codebase wasn't written with aliasing
rules
** Summary changed:
- openssl is not LTO-safe
+ [FFe] openssl is not LTO-safe
--
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/2058017
Title:
[FFe] openssl is not LTO-safe
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+merge/462482
** Merge proposal unlinked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
You received this bug notification because you are a
** Merge proposal unlinked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Merge proposal unlinked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Merge proposal unlinked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462482
--
You received this bug
I can confirm the problem. Here is a reproducer:
# nmcli con add ifname dummy0 type dummy ipv4.dns 1.1.1.1#lxd
Error: Failed to add 'dummy-dummy0' connection: Message recipient disconnected
from message bus without replying
This is the crash related to this issue:
Mar 15 09:46:40 noble-vm
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462482
--
You received this bug
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/462481
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Description changed:
[ Impact ]
Kernel (and systemd) log messages appear during boot for many machines,
when the user should be seeing only the BIOS logo and/or Plymouth splash
screens.
[ Workaround ]
On most machines you can hide the problem by using these kernel
Seems it's fairly easy to make a working solution in initramfs-tools
alone, but there's a compromise. If I only include tiny/simple
framebuffer drivers in initrd then i915 starts so late that Plymouth
doesn't use it, and bug 2054769 can occur on some machines. If I include
all the current drm
Public bug reported:
tl;dr: since it's too much work to make openssl LTO-safe, upstream
doesn't see it as a goal and doesn't test it, and there are probably no
performance gains to LTO for this package.
Openssl is an old project and the codebase wasn't written with aliasing
rules in mind. There
Hi Calvin,
Thanks for filing the FFe but looking at it closely, this isn't really a
new feature but more of a packaging fix.
Given that status, please go ahead and upload. +1. :)
** Changed in: software-properties (Ubuntu Noble)
Status: New => Triaged
--
You received this bug
With 0b4c5056925e7358374874c8bf4767290157e903 (in autopkgtest 5.33) lxc-
start-ephemeral is not called anymore.
** Changed in: autopkgtest (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
** Changed in: autopkgtest (Ubuntu)
Status: Triaged => Fix Committed
--
You
Plymouth would still need patching in order to optimize the drm modules
in debian/local/plymouth.hook
** Changed in: plymouth (Ubuntu)
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: netplan.io (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
This will get the same initramfs-tools fix as bug 1970069. After that,
the only way to make Plymouth start sooner will be to use kernel
parameter 'plymouth.use-simpledrm', but we probably don't want that by
default so as to avoid regressing on bug 2054769.
** Also affects: initramfs-tools
Hi Andreas, thank you for having a look.
0.96.20.13 was queued to fix autopkgtest failures with 0.96.20.12. Do I
need a new SRU bug for that?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
I think the delay I'm seeing is a feature of Plymouth, not a bug:
"ignoring since we only handle SimpleDRM devices after timeout"
As much as I dislike it perpetuating bug 1869655, this feature does
prevent bug 2054769 from reoccurring.
But this raises the question: is it worth putting i915,
Public bug reported:
Wenn ich eine grosse Datei in Thunar oder Nautilus lösche wird es auf
die Partition nicht um den Anteil gelöscht.
** Affects: tzdata (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch
@valeryan-24 ModuleNotFoundError: No module named 'imp'" says that your
Gpodder issue is not related to this bug. You are missing a dependency
the 'imp' module. If Gpodder is packaged it will need to add that as
part of its install dependencies.
--
You received this bug notification because you
the plasmashell profile is necessary for it to work under unprivileged
user namespace restrictions.
--
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/2056696
Title:
All
66 matches
Mail list logo
