Given that systemd-v255 has just migrated from noble-proposed to noble
yesterday, this bug is now present in Ubuntu 24.04 as-is, without the
proposed repo enabled. Can this fix be backported before 22.04 releases
so people don't run into network issues with a newly-installed 22.04?
--
You receive
Upstream has fixed this for v256 and has indicated the fix will be
backported to v255.
https://github.com/systemd/systemd/commit/7dc431839eeeffe6ed65acbe9bfe2a6e89422086
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
Public bug reported:
I noticed a bug in systemd version 255 which is currently available in
noble-proposed (255.2-3ubuntu1).
I have already reported to upstream at
https://github.com/systemd/systemd/issues/30891 but there's no fix
available yet as of today.
I'm still reporting the bug here anywa
Same issue on Bionic, installed May 15 (2 months ago):
➜ ~ sudo journalctl --disk-usage
Archived and active journals take up 4.1G in the file system.
My logs are definitely clogged with endless JavaScript errors from
gnome-shell. Something I would not expect to
Adding to my previous message: After=NetworkManager-wait-online.service
will not work, as it doesn't respect for instance setups where networkd
handles connections.
@Robie Basak
> Will this delay boot for laptop users who are offline, for example?
If someone has installed the dnsmasq package wit
The fix by Terrence Houlahan works for me on 18.04. Thanks!
However, I'm wondering if adding this "After" clause is a problem since
the package doesn't currently depend on Network Manager? Does
"NetworkManager-wait-online.service" satisfy a more generic SystemD
target?
>From the dnsmasq package:
A month before the release of 18.04, a change was released to make
systemd journals persistent, but the setting SystemMaxUse was left unset
in /etc/systemd/journald.conf
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188
The bug's regression analysis seems wrong, as it states: "The jo
Public bug reported:
I'm reporting this in the role of a developer getting issue reports for
non-Ubuntu projects. Apport could work great for this purpose, too,
since it detects our system service's crashes.
For us, the most valuable information is typically in the Traceback
field (it's a Python
Public bug reported:
After running Bionic for 3 months, I had 2.6 GB of journals.
I would not expect from a normal desktop user that they should have to
run commands like `sudo journalctl --vacuum-time=10d`.
I would nominate this command as a sane default to have running at each
reboot to ensure
Public bug reported:
package linux-firmware 1.157.15 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-firmware 1.157.15
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Una
Question:
The release notes state: "Use ast.literal_eval() instead of the generic
eval(), to prevent arbitrary code execution from malicious .crash files"
The change should be in ui.py in this revision:
http://bazaar.launchpad.net/~apport-hackers/apport/trunk/revision/3114
Just to be clear: How
11 matches
Mail list logo
