> Do you still see a problem related to the one that you reported in a
> currently supported version of Ubuntu?
Thanks for following up! I don't use Shotwell any more, if nobody else
corroborates the report, I suggest you just can close it.
-k
--
If I haven't seen further, it is by standing in
Just to chime in: Noticed slow machine and systemd-resolved taking 100%
cpu. Edited /etc/systemd/resolved.conf to DNSSEC=no (not off, as "no"
was commented out in the file). Tried systemctl restart systemd-
resolved, but nothing changed. Tried killall systemd-resolved, nothing.
Tried killall -9
@Arul, I found something similar in my comment above, at
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1173915/comments/5.
But it's been almost 4 years since this issue was reported, and over 2
years since I added my comment, and it's clearly not fixed yet, or even
prioritised.
In fact,
Couldn't the upstream fix be to time out the DNS resolution? If you
don't have an answer in X seconds/milliseconds, never mind and carry on.
It's just ping, after all, and it's a good idea to make low level
diagnosis independent of higher level functionality, as noted in the
Debian bug report.
Cac
I see I've made a typo regarding icmp_seq in the output of the second
run of ping (icmp_seq 1, then 2, and then 1 again, but the last one
should be 3). I typed this manually, so there may be other typos as
well. But I can't see any typos regarding the main point, I got the ping
replies from my own
Public bug reported:
I tried pinging an IP address on an internal network. My IP is
10.0.0.95, and I'm trying to ping 10.0.0.96. Here's what it looked like:
$ ping 10.0.0.96
PING 10.0.0.96 (10.0.0.96) 56(84) bytes of data.
>From 10.0.0.95 icmp_seq=1 Destination Host Unreachable
>From 10.0.0.95 ic
Thanks, I was hoping for some help to find the right place to report
this.
I poked around some more, and I found out what the problem was. First of
all, my wireless router was confused. I rebooted it, and then everything
started working again.
I did some debugging before I rebooted it, though, an
To get Ubuntu to send EDNS0 queries, I can set this in resolv.conf:
options edns0
That might work around this bug in my router in the future. And in case
anyone is interested, the wireless router is a Netgear WNR2000v5.
I think this case can be closed.
--
You received this bug notification be
Public bug reported:
Not sure resolvconf is the correct place to report this bug, but I'm
unable to resolve domains with large EDNS0 replies.
A couple of examples are www.sciencedaily.com and www.ncbi.nlm.nih.gov.
Interestingly, they resolve when I use "dig ", but if I enter a
URL with either of
I just had this on my 1 week old new laptop running Ubuntu 14.04.1. I
ran "strace -s 128 -p " where PID was the pid of initctl, and the
output looked like this (small excerpt only included):
poll([{fd=3, events=POLLIN}], 1, 4198964686) = 1 ([{fd=3, revents=POLLIN}])
poll([{fd=3, events=POLLIN}], 1
Proposed package works for me, and I confirmed again that the version I
had before upgrading had the same issue. From apt-get output:
Unpacking util-linux (2.20.1-5.1ubuntu20.2) over (2.20.1-5.1ubuntu20.1)
...
I don't see where I can change verification-needed to verification-done,
however. Hopef
11 matches
Mail list logo
