I get the exact same error when building a rock on 22.04. The build is
using g++.
:: lto1: fatal error: bytecode stream in file
‘/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libunwind.a’
generated with LTO version 11.2 instead of the expected 11.3
:: compilation terminated.
::
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/2023789
Title:
IPv6 fails with busybox: ip: either "dev"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: isc-dhcp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
What exactly is suspicious about remmina using shared memory?
--
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/2024540
Title:
Vulnerability Can Gain Access even with Time
That's awesome! I figure post-quantum cryptography will feel like
something for years in the future until the week when we all realize we
should have moved years earlier. Capture-and-store has to be going on
right now, on the assumptions that someone will bring a reliable quantum
machine to
Hello Olivier, or anyone else affected,
Accepted apparmor into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apparmor/3.0.8-1ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I have confirmed that the updated evince, without an updated apparmor,
fails in lunar with this error on stderr from evince:
internal error, please report: running "chromium" failed: open
/var/lib/snapd/inhibit/chromium.lock: permission denied
that looks sufficient to me to move forward with
Currently nothing to be sponsored, so unsubscribing the team. Tony, if
you want to provide a matching patch for SRU to the stable series,
please feel free to resubscribe ubuntu-sponsors once it's available.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thank you for the bug report, Thiago! I did a little bit of housekeeping
so that this LP accurately reflects this targeting Ubuntu Pro 18.04.
Could you please fill in the description according to the SRU template?
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
** Changed in:
> > The fix was revered in bug #1929560, but the behavior will not be reverted
> > in newer releases. Therefore, every reload of systemd-networkd will remove
> > the physical network interface from neutrons bridge.
>
> It looks like the patch was backported to stable releases in that bug; not
** Tags added: se-sponsor-halves
--
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/2024864
Title:
systemd-networkd crashes with SIGSEGV on bionic
Status in systemd:
New
Also what release are you running?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
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/2004179
Title:
> Since merging https://github.com/systemd/systemd/pull/17392, systemd-
network will remove the master flag > from the "public" interface, that
neutron-linuxbridge-agent assigned to the bridge for the network, e.g. >
brq88363244-5f, breaking all network on the flat network.
> The fix was revered
** Description changed:
Customer reported that this issue happens randomly during their
automated regression runs. It's not consistent and hard to reproduce.
They have shared a coredump:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x555962aa1c34 in
** Also affects: ubuntu-pro
Importance: Undecided
Status: New
** Also affects: ubuntu-pro/18.04
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
*** This bug is a duplicate of bug 1972159 ***
https://bugs.launchpad.net/bugs/1972159
This was fixed in bug 1972159.
** This bug has been marked a duplicate of bug 1972159
systemd-oomd frequently kills firefox and visual studio code
--
You received this bug notification because you are
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also
Ubuntu 21.10 is no longer supported. Is this still a problem in newer
releases?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
What settings have you actually tried to change in
/etc/systemd/logind.conf? The snippet above looks unchanged (or is at
least all commented out).
Some combination of HandleLidSwitch*=ignore should work.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug
Is this issue still relevant?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
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/1838992
Title:
udev doesn't
According to the upstream bug report, this is fixed by
https://github.com/systemd/systemd/commit/1e187d2dd52cbb4f0bb30e4d96acf7f72a145b91,
which is present in Focal and newer.
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you
** Changed in: systemd (Ubuntu Cosmic)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Bionic)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
** Changed in: systemd (Ubuntu Lunar)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The commits referenced in the upstream bug report are present in Lunar
and newer.
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
Between Bionic and Focal, dhclient was patched to set the valid_lft on
ipv4 addresses, which is a timer in the kernel that tells the kernel
when to reap the IP. dhclient then is supposed to issue repeated `ip
addr add` commands to reset this lft and prevent the kernel from
Public bug reported:
On Ubuntu 22.04.2
Package software-properties-common 0.99.22.7
During the launchpad outage on the 23rd June 2023, add-apt-repository was
crashing with the following:
Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 364, in
sys.exit(0 if
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
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/1953226
Title:
systemd journal uses all space
Status in
This was reported against Impish, which is no longer supported. If you
experience this problem on a supported release please open a new bug
report.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
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/1961055
Title:
Key load error: Failed to open key material
I don't think this is a problem with systemd. It would likely be related
to the installer, I think. If this is still an issue please open a new
bug report against the relevant installer package.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification
There have been several package updates since this report. If you
experience similar issues with newer versions, please open a new bug
report.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
There have been several package updates since this report. If you
experience similar issues with newer versions, please open a new bug
report.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This version of systemd is no longer supported in any Ubuntu releases.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
There have been several package updates since this report. If you
experience similar issues with newer versions, please open a new bug
report.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
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/1995097
Title:
systemd
Status in systemd package in Ubuntu:
There have been several package updates since this report, so this is no
longer relevant. If you experience similar issues with newer versions,
please open a new bug report.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a
There have been several package updates since this report, so this is no
longer relevant. If you experience similar issues with newer versions,
please open a new bug report.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a
If this is still relevant, can you share the output from the failed
service? The systemd-journal-upload.service unit should have
DynamicUser=yes, which should take care of the user at runtime (i.e. I
would not expect to see systemd-journal-upload listed in /etc/passwd).
** Changed in: systemd
There have been several updates to the package in Jammy since this was
reported, so this is no longer relevant.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
There have been several updates since this version of the package, so
this is no longer relevant.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Updates were pushed to fix this issue. Please re-open this bug if this
problem is still occurring.
** Changed in: libx11 (Ubuntu)
Status: New => Invalid
** Changed in: libx11 (Ubuntu Trusty)
Status: New => Fix Released
--
You received this bug notification because you are a
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
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/1981531
Title:
package grub-efi-amd64 2.06-2ubuntu7 failed
*** This bug is a duplicate of bug 1946388 ***
https://bugs.launchpad.net/bugs/1946388
This was fixed in bug 1946388.
** This bug has been marked a duplicate of bug 1946388
Journalctl -f --file some.journal causes coredump
--
You received this bug notification because you are a member
This was reported aginst systemd 248.3-1ubuntu8.2 in Impish, which is no
longer supported. If this is still relevant in a supported release,
please open a new bug report.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member
Is this still relevant?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Is this still an issue? If so, can you please enable debug logs on
systemd-networkd, and then reboot, and attach those recent logs?
$ systemctl edit systemd-networkd.service
# Add the following when the editor opens:
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
$ reboot
[...]
$ journalctl -b -u
Indeed, I do not see this behavior any longer.
```
$ dig -x 127.0.0.1
; <<>> DiG 9.18.12-0ubuntu0.22.04.2-Ubuntu <<>> -x 127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12678
;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 2, AUTHORITY: 0,
Sorry this was not looked at sooner. Is this still an issue for you?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I do see this behavior on Focal still, but I don't think systemd is the
correct package.
** Package changed: systemd (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Impish)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Focal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Sorry this was not looked at sooner, but there have been several updates
to systemd in Focal since this report.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
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/1905179
Title:
SDcard show wrong date (one month ahead)
The attachment "cron-reboot.patch" seems to be a patch. If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated message performed by a Launchpad user owned by
** Changed in: systemd (Ubuntu)
Importance: Undecided => Wishlist
--
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/1912855
Title:
debugfs shouldn't be mounted by default
There have been several updates to systemd in bionic since this version.
This also doesn't look like it was a problem with src:systemd:
Setting up libpam-systemd:i386 (237-3ubuntu10.46) ...
^[[B^[[A
^[[B^[[A
Use of uninitialized value $reply in scalar chomp at
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
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/1932354
Title:
systemd/247.3-3ubuntu3.1 ADT test failure
This appears to be fixed in newer releases.
** Changed in: systemd (Ubuntu)
Status: New => 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/1938810
Sorry this was not looked at sooner. Please re-open if still an issue.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This was also suggested upstream[1], but it seems that this is the
desired behavior from upstream's perspective.
[1] https://github.com/systemd/systemd/issues/12793
** Bug watch added: github.com/systemd/systemd/issues #12793
https://github.com/systemd/systemd/issues/12793
** Changed in:
I am using systemd rather than upstart, but the bug is the same: cron
depends on remote-fs.target, autofs depends on remote-fs.target, so they
start together. The result is that the job is run with the working
directory set to /var/spool/cron.
What cron should be waiting for is home directories
Not sure yet about SRU'ing this, but this should at least be fixed in
devel.
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
** Changed in: systemd (Ubuntu Focal)
Status: New => Triaged
** Changed in: systemd
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
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/1932176
Title:
localed-locale test fails for hirsute
After some more digging, turns out it's not a problem with Netplan.
Although, the problem will manifest depending on how Netplan generates
the configuration for Network Manager.
When selecting the option to store the private key in the KDE wallet
agent, the option "private-key-flags=1" will be
** Changed in: systemd (Ubuntu Impish)
Status: New => Won't Fix
--
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/1938058
Title:
systemd-time-wait-sync.service should
This is from when Jammy was still the devel series. Sorry that this
wasn't looked at then.
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Is this still an issue? I tried running a bionic LXD container from a
Lunar host, and in the container I was able to run the snap without
issues.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch
I cannot reproduce this on Focal:
root@focal:~# nslookup pod51041.outlook.com
;; Truncated, retrying in TCP mode.
Server: 127.0.0.53
Address:127.0.0.53#53
Non-authoritative answer:
Name: pod51041.outlook.com
Address: 52.96.122.34
Name: pod51041.outlook.com
Address:
Yeah, fair enough. This does also result in extra kernel modules being
loaded that are not needed, even when systemd-pstore.service is skipped
since /sys/fs/pstore is empty. I don't think this is a huge deal, but it
would probably be nice to clean it up for an LTS indeed.
** Changed in: systemd
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2024661
Title:
Unable to configure Wireguard
** 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/2024889
Title:
Laptop screen show an one pixel row corruption
Status in xorg
Public bug reported:
Observed behaviour:
When I boot my PC or wake it from suspend, it usually gives a desktop
notification about available updates.
Trying to apply the updates often results in this kind of error:
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process
3522905
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
This might actually be apparmor on the LXD host denying the container?
Look for messages like:
2023-06-23T09:53:56.040427+08:00 grook kernel: [772843.931461] audit:
type=1400 audit(1687485236.036:118): apparmor="DENIED" operation="file_lock"
profile="lxd-pat_" pid=3334600 comm="(.plocate)"
This might be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1635382
--
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/1656024
Title:
Units using
74 matches
Mail list logo
