[Bug 1666021] Re: zesty systemd-resolve timeout

2017-04-25 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1666021] Re: zesty systemd-resolve timeout

2017-02-24 Thread Jeremy Bicha
I did a reinstall of Ubuntu 17.04 which preserved my home directory but wiped all modified system configurations (there was also a hiccup which meant that my installed apps weren't automatically reinstalled). After the reinstall, I can no longer reproduce this bug, so I guess we'll probably want

[Bug 1666021] Re: zesty systemd-resolve timeout

2017-02-21 Thread Barry Warsaw
I wonder if this is related to something I've seen since before the recent nm and systemd uploads. I have Chromium, Emacs, and Claws-Mail set up as startup apps. After a reboot, as soon as I login, these apps come up, but most of the tabs in Chromium cannot load. After some short amount of

[Bug 1666021] Re: zesty systemd-resolve timeout

2017-02-21 Thread Barry Warsaw
I haven't seen this problem, but I don't suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666021 Title: zesty systemd-resolve timeout To manage notifications about this bug go to:

[Bug 1666021] Re: zesty systemd-resolve timeout

2017-02-21 Thread Jeremy Bicha
One trigger for the high CPU for systemd-resolve is resuming from suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666021 Title: zesty systemd-resolve timeout To manage notifications about

[Bug 1666021] Re: zesty systemd-resolve timeout

2017-02-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666021 Title:

[Bug 1666021] Re: zesty systemd-resolve timeout

2017-02-21 Thread Jeremy Bicha
Two days later, I still get the high CPU usage from systemd-resolved periodically and I have to restart that service. I also have seen very large numbers of "spam" in my journal like this: systemd-resolved: Processing query... -- You received this bug notification because you are a member of

[Bug 1666021] Re: zesty systemd-resolve timeout

2017-02-19 Thread Jeremy Bicha
I worked around the high CPU usage by running sudo systemctl restart systemd-resolved.service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1666021 Title: zesty systemd-resolve timeout To manage

[Bug 1666021] Re: zesty systemd-resolve timeout

2017-02-19 Thread Jeremy Bicha
Look at the top two items using my CPU in the attached screenshot (systemd-resolve and dnsmasq) ** Attachment added: "systemd-resolve-high-cpu.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1666021/+attachment/4822091/+files/systemd-resolve-high-cpu.png -- You received this bug