[Touch-packages] [Bug 1790205] Re: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is.

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

[Touch-packages] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet

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

[Touch-packages] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet

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:

[Touch-packages] [Bug 1790205] Re: systemd journals take up too much space, aren't vacuumed automatically

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

[Touch-packages] [Bug 1796474] [NEW] Traceback should be uncollapsed by default

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

[Touch-packages] [Bug 1790205] [NEW] systemd journals take up too much space, aren't vacuumed automatically

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

[Touch-packages] [Bug 1648806] Re: Arbitrary code execution through crafted CrashDB or Package/Source fields in .crash files

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: