Upstream Bug:
https://github.com/lxc/lxc/issues/340
Seems patches are floating around, no movement for a bit.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1339781
Title:
*** This bug is a duplicate of bug 1432450 ***
https://bugs.launchpad.net/bugs/1432450
Public bug reported:
This is a duplicate of Bug #1432450 libperl.so.5.20.2 crashed with
SIGSEGV in perl_construct()
Wasn't sure how to upload the crash logs without creating a duplicate
and it wasn't
I am getting this same issue, both on my last install and also on a
brand new install today (15.04). Out of the box.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
Attaching photo showing corruption, does not appear in a screenshot.
** Attachment added: photo showing corruption
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1446521/+attachment/4380420/+files/photo_showing_corruption.jpg
** Description changed:
When my right hand monitor is
Public bug reported:
When my right hand monitor is positioned above the left hand monitor,
the top row of pixels on the left hand monitor appears as garbage. This
does not occur when they are aligned.
May or may not be related to this old bug with the same symptoms:
** Attachment added: network manager connection debug info
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1440607/+attachment/4380455/+files/nm_connection_log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Further investigation:
- Disabling dns=dnsmasq handler means this does not occur
- I am ending up with VPN_IP4_DOMAINS set in the log
- Default route is getting set to the vpn, and is configured as such (the
'disable default route' is not selected)
- Reading
Same connection a couple weeks ago:
Mar 25 08:54:23 localhost NetworkManager[809]: info VPN connection 'Work VPN'
(IP Config Get) reply received.
Mar 25 08:54:23 localhost NetworkManager[809]: info VPN connection 'Work VPN'
(IP4 Config Get) reply received.
Mar 25 08:54:23 localhost
Created a fresh 14.10 installation (utopic) + network-manager-openconnect-gnome
and confirmed the original behaviour.
Upgraded same installation to 15.04 and now experiencing the same behaviour as
reported above.
Additionally, as this VPN specifies that other traffic is firewalled,
the default
** Description changed:
- When connecting to my work VPN (network-manager-openconnect), typically
- the name-servers for the VPN are used entirely for the whole system and
- all domain names.
+ When connecting to a VPN using network manager (openconnect), DNS
+ resolution stops working for me.
Public bug reported:
When connecting to my work VPN (network-manager-openconnect), typically
the name-servers for the VPN are used entirely for the whole system and
all domain names.
After updating vivid today (first time in about a week), suddenly I find
that it is only using it for the VPN
Public bug reported:
I am having issues with my displays blanking out and coming back after 2
seconds, quite often.. sometimes a few times in 10 seconds sometimes
once a minute. I only just started using the Intel graphics today,
instead of previously using a radeon card.
My setup is 1xDVI + 1x
extra dmesg log as more errors occurred.
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1531422/+attachment/4544813/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg
Avahi is not the one actively withdrawing the address, this log message
is a reaction to the address record being removed from the system.. it
withdraws the mDNS "record" for this address.
Most likely theory for this is that DHCP is deciding to drop the address
for some reason (lease expired and
Also uploaded and built the package here, so people can test it out if they
want. Would love feedback from someone with the issue to confirm it fixes it:
https://launchpad.net/~lathiat/+archive/ubuntu/lp1342400-avahi-invalid-response-packet
--
You received this bug notification because you are
Attaching debdiff for sponsorship into trusty. Applies upstream commit
(by myself) to fix this issue.
Not required in xenial, but could be uploaded into wily.
** Patch added: "lp1342400-avahi-invalid-response-packet.debdiff"
** Patch added: "debdiff for precise"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1342400/+attachment/4690004/+files/lp1342400-avahi-invalid-response-packet-precise.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Tested that patch, and it definitely solves the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1534106
Title:
rsyslogd crashed with SIGSEGV with juju-local
Fixed upstream in 8.15:
https://github.com/rsyslog/rsyslog/issues/575
Latest release 8.16 is in Debian, perhaps we could just sync up to it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
I was re-visiting this recently, I'm fairly sure we can get rid of this
requirement to stop avahi with a .local by reconfiguring nsswitch.conf
to remove the [NOTFOUND=RETURN].
Do you know where the initial discussion determining why to do this was
had?
My general understanding is that because
Further debugging, I discovered that the screen blanking issue was being
caused by a faulty power supply on the DisplayPort Expander/Splitter, it
kept resetting. This was causing the errors.
** Changed in: xorg (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification
I have 6 external repos configured, and all 6 fire the warning.
If nothing else, the warning really needs to be re-worded.
"insufficiently signed" and then (weak digest) at the end is not very
straight forward.
W: gpgv:/var/lib/apt/lists/ppa.launchpad.net_js-reynaud_kicad-
Most likely your issue is that the system init scripts are starting the
packaged binary from /usr/sbin/avahi-daemon instead of your compiled
binary from /usr/local/sbin/avahi-daemon
I am going to build and propose an SRU to precise & trusty to fix this
issue.
For Debian Jessie on your rpi,
How did you install avahi?
Can you run this:
sudo which avahi-daemon
sudo dpkg -l avahi-daemon
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1342400
Title:
avahi-daemon
Actually that might happen if you don't have a newer libdaemon (they
made some changes to default log levels), I'll have to check on that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
** Changed in: avahi (Ubuntu)
Assignee: (unassigned) => Trent Lloyd (lathiat)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1441008
Title:
under systemd avahi-dae
** Changed in: avahi (Ubuntu)
Importance: Undecided => Low
** Changed in: avahi (Ubuntu)
Status: New => Confirmed
** Changed in: avahi (Ubuntu)
Assignee: (unassigned) => Trent Lloyd (lathiat)
--
You received this bug notification because you are a member of Ubuntu
Tou
Full patch and explanation here:
https://code.launchpad.net/~lathiat/maas/1.9-lp1521618-dhcp-incorrect-router
With multiple subnets, PXE DHCP clients would receive the router of the first
subnet in the configuration file regardless of which subnet they actually
received a lease from.
This
Thanks for the report.
I was interestingly unable to reproduce this when testing, so I will dig
in further and try to determine why.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
Oh right, I see now.. too early to comment as usual :(
The problem is that you are setting up a "privileged" container for MAAS
which does not use UID mapping, hence the issue shows up in the MAAS
workflow but not with a normal container deployment.
The rlimit-nproc is simply set in
Avahi starts fine in a 16.04 container for me. Can you share what
errors you are actually seeing Dustin?
lxc launch ubuntu:16.04 xenial
ssh ubuntu@
sudo apt install avahi-daemon
sudo systemctl status avahi-daemon
The post you linked is from January 2016 and on 15.10 (wily).. it does in fact
There was previously a patch to skip setting this (because it would
fail), it was removed for a couple of reasons including an upstream
change not to abort of setting RLIMIT_NPROC failed:
I've committed a change upstream to simply remove the default setting of this
option, and will prepare a
** Changed in: avahi (Ubuntu)
Status: New => Confirmed
** Changed in: avahi (Ubuntu)
Importance: Undecided => High
** Changed in: avahi (Ubuntu)
Assignee: (unassigned) => Trent Lloyd (lathiat)
--
You received this bug notification because you are a member of Ubuntu
Tou
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1577596
Title:
ntpd not started when using ntpdate
Status in init-system-helpers package in Ubuntu:
The d-bus activation thing is a quirk of systemd, it actually tells you
when you run stop. You need to use disable (as well as stop) to both
stop it and prevent re-activation.
root@ubuntu:~# systemctl stop avahi-daemon
Warning: Stopping avahi-daemon.service, but it can still be activated by:
Good news for you is that some work is going on upstream in libnss-mdns right
now to fix this problem properly and always handle .local properly even when in
authorative DNS - some commits just went in recently Adam Goode is doing some
great work on this project:
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1392317
Title:
Incorrect order of messages with RepeatedMsgReduction on
Status in rsyslog package in
Paul: Could you file this in the upstream bug tracker here?
https://github.com/lathiat/avahi/issues/new
We should probably just drop reliance on the label and store state
somehow
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
*** This bug is a duplicate of bug 1668559 ***
https://bugs.launchpad.net/bugs/1668559
Commenting here as the duplicate parent is Private at the moment.
Main issue is here, hitting rlimit-data which is set by default in the config
file to 4M
> kernel: mmap: avahi-daemon (992): VmData
I rebuilt both binutils and linux-4.11.0-11 locally to see if anything
changed.
binutils still has the same libbfd-2.28.90-system.20170718.so soname in
the package
however perf in linux-tools is now linked against the new soname. So a
rebuild may solve it however I am not entirely sure if this
New binutils upload today of 2.29, which conflicts with linux-tools as
it turns out it Depends binutils (>= 2.28), binutils (<< 2.29)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
** Changed in: binutils (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1702056
Title:
perf broken on 4.11.0-9-generic (artful):
Likely the reason this doesn't work, is because nss-mdns does not
resolve reverse DNS for IP addresses other than the link local range
(169.254.0.0/16). This is by design and per-spec.
So this will never work, you'll need to look at either:
(1) using the IP address range (according to the
To debug this issue requires more information, the log messages from
avahi itself are simply a "symptom" of the fact the network address was
deleted.
For any affected system we need to know
(1) How your network is setup, e.g. /etc/network/interfaces, Network-Manager,
etc. Plus a copy of the
If you want to block access to the local LAN only, then that is correct.
My best suggestion would be to secure your SSH and thus not worry so
much if it's accessed by some other host on the network. If you
restrict it to one user, have a very secure password and/or SSH key only
then your attack
Doing a quick google, it seems third party binaries can get linked
against this shared library as well possibly. Ran apport-collect for
the extra logs; and both today's binutils and kernel upgrade haven't
fixed it.
Thinking we might need to propose for affecting binutils?
** Also affects:
Same problem with the new 4.11.0-12 upload, i'm assuming since binutils
is still in -proposed it wasn't built against?
linux-tools-4.11.0-12 : Depends: binutils (< 2.29) but 2.29-2ubuntu1 is
to be installed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
[rlimits] is the correct section
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1638345
Title:
avahi-daemon crashes multiple times an hour
Status in avahi package in
Created patch for this problem, am handling the SRU process in the
following bug as effectively the same fix for both issues.
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1661869
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Attached debdiff to remove all rlimits from the default avahi-
daemon.conf. These commits have been made upstream. This also solves
#1638345 because it is effectively the same fix, so I plan to solve it
with the same upload. Will handle the process here.
** Patch added:
https://github.com/lathiat/avahi/issues/41
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1698248
Title:
avahi-daemon constantly registers/withdraws IPv6 address record
This is known upstream but not yet solved, working on it I have a theory
** Changed in: avahi (Ubuntu)
Status: New => Confirmed
** Bug watch added: github.com/lathiat/avahi/issues #41
https://github.com/lathiat/avahi/issues/41
--
You received this bug notification because you are a
Workaround is to edit /etc/avahi/avahi-daemon.conf and comment out the
entire [limits] section or at least the rlimit-data and rlimit-stack
sections
I hope to push out an update for this
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
This is resolved now.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1702056
Title:
perf broken
Thanks for the note ronny, that is a really helpful note. That may well
be the cause for many of these cases.
--
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/1586528
Sponsors: Can we get this debdiff uploaded now? We've had a few more
reports and I'd like to get this workaround in place.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
** Changed in: avahi (Ubuntu)
Status: Confirmed => 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/1586528
Title:
Avahi-daemon withdraws address
Hoping to get attention to this again. Since 18.04.1 is out now, more
and more users are likely to hit this issue as more users will be
upgrading. This issue applies equally to desktop and server scenarios.
I would like to get lp1752411-avahi-host-timeout.diff sponsored for
upload please
--
You
** Description changed:
+ [Impact]
+
+ * Network connections for some users fail (in some cases a direct
+ interface, in others when connecting a VPN) because the 'host' command
+ to check for .local in DNS called by /usr/lib/avahi/avahi-daemon-check-
+ dns.sh never times out like it should -
Request sponsorship of this upload for cosmic and then SRU to bionic
- New debdiff uploaded for both bionic and cosmic
- Fixed the SRU version for bionic
- Added a comment about the workaround to the script
- Updated bug description with SRU template
Tested patch working on bionic with my
** Patch added: "lp1752411-avahi-host-timeout-cosmic.patch"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+attachment/5178710/+files/lp1752411-avahi-host-timeout-cosmic.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I agree with the sentiment that 5 seconds feels too long, however as a
workaround I decided I would just copy the existing timeout. I certainly
would not want to make it longer since this is in the critical boot
path.
I would generally agree that in general a DNS request should fail faster
> When host call fails (even with timeout), it returns "1" claiming
"dns_has_local()=true".
0 = true, 1 = false (you implied the opposite)
What may add confusion here is the grep -vq check is like an extra check
to make sure host didn't return 0 (success = we found .local) but then
say 'not
** Patch added: "lp1752411-avahi-host-timeout-bionic.patch"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+attachment/5178693/+files/lp1752411-avahi-host-timeout-bionic.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Patch added: "lp1752411-avahi-host-timeout-cosmic.patch"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+attachment/5178692/+files/lp1752411-avahi-host-timeout-cosmic.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Attachment added: "log of terminal session during upgrade"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783272/+attachment/5167023/+files/apt-upgrade-console-log.txt
** Description changed:
Upgrading the systemd package, which contains systemd-networkd, appears
to restart
Public bug reported:
Upgrading the systemd package, which contains systemd-networkd, appears
to restart networkd and subsequently reconfigure network interfaces
causing a brief connectivity outage.
This is a bionic system which has a network bridge as it's primary
interface through netplan.
You
** Attachment added: "netplan config"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783272/+attachment/5167024/+files/01-netcfg.yaml
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783272/+attachment/5167022/+files/syslog
--
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:
evolution-source-registry is using 100% CPU after login and never stops,
it continues to do so after kill/respawn or reboot. This started
sometime after upgrade to bionic and has been consistent for the last
couple of weeks.
Looking at the process with perf, it seems that
Public bug reported:
/etc/pam.d/systemd-user does not currently call pam_keyinit.so -- it's
possible this should instead be added to common-session-noninteractive
but I am not entirely sure about that - someone with more understanding
of the PAM modules would probably need to weigh in on that.
Found a Debian bug about the same issue but with AFS instead of fscrypt:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846377
** Bug watch added: Debian Bug tracker #846377
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846377
--
You received this bug notification because you are a
Yeah the exact same change in the 0.7 release (rlimit section removal)
that is shipping in Bionic fixes the issue there, and the issue isn't
present in Bionic.
I also individually tested each of the trusty/xenial/artful packages
built from the supplied debdiffs to ensure the issue goes away after
** Patch added: "lp1661869-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1661869/+attachment/5079951/+files/lp1661869-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
I have updated Bug #1661869 with an SRU template and new updates to fix
this issue, plus the issue in that bug.
The fix is simply to update /etc/avahi/avahi-daemon.conf and comment out
the entire [rlimits] section. You can do this yourself (but the package
update will do it for you).
It'd be
** Patch added: "lp1661869-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1661869/+attachment/5079950/+files/lp1661869-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
Trusty is technically not directly affected by the container proc issue
as there was an Ubuntu patch dropped in xenial to skip setting rlimit-
nproc when /run/container_type=lxc
Could happen if that doesn't exist though, and the memory issue can
still occur, so still recommend upload.
**
** Changed in: avahi (Ubuntu)
Assignee: (unassigned) => Trent Lloyd (lathiat)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1638345
Title:
avahi-daemon cras
** Description changed:
- The bug, and workaround, are clearly described in this mailing list
- thread:
+ [Original Description]
+ The bug, and workaround, are clearly described in this mailing list thread:
https://lists.linuxcontainers.org/pipermail/lxc-
users/2016-January/010791.html
** Patch added: "lp1661869-artful.debdiff"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1661869/+attachment/5079949/+files/lp1661869-artful.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
@jecs Thanks for the feedback; I am curious.. how many service do you
have on your network?
If you run "avahi-browse -a -t|wc -l" -- how many lines do you have?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in
This seems to be some kind of weird interaction with systemd
activation...
root@optane:/lib/systemd# systemctl stop avahi-daemon.socket
Job for avahi-daemon.socket canceled.
I think basically the issue is the service is immediately started again
due to activation.. i'm not sure why
Thanks for the report.
How did this happen, was it during a package upgrade for a normal
installation or is this a new install, etc. If a new install, describe
which install media download and options you used. Or were you
installing avahi-daemon or some other package using apt install, etc.
Looking at your logs, generally it seems like dbus is broken for some
reason.
Would also be great to check it's status:
# systemctl status dbus
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
FYI this will not effect DHCP as the hostname change is only used for
mDNS and is not used as the system hostname and thus would affect DHCP
etc
The cause of this is knwon and hopefully a fix will get done for it
soon.. basically its when IP addresses are added then removed too fast.
Can also
Analysis here appears related:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768620
Seems the interactions here are quite complex
To reproduce the problem, you can do on xenial:
(install old version)
# apt install avahi-daemon=0.6.32~rc+dfsg-1ubuntu2
avahi-dnsconfd=0.6.32~rc+dfsg-1ubuntu2
If you are hit by this issue, it seems sufficient to simply ask dpkg to
finish configuration as it seems the prerm script isn't retried
$ dpkg --configure -a
Or you can just re-run your upgrade command (e.g. "apt upgrade") which
should do the same plus finish any upgrades that didn't finish
I did some testing using strace and looking at backtraces of why "host"
is stuck, and it's not immediately clear to me why it's getting stuck.
Will need to look more in depth into it tracing it's actual execution -
it's multi threaded and using poll so not super straight forward from
the trace for
This bug was fixed in the package avahi for trusty, xenial and artful.
bionic is not affected by this issue.
xenial: 0.6.32~rc+dfsg-1ubuntu2.1
trusty: 0.6.31-4ubuntu1.2
Would be great if the various people affected by this could confirm they
no longer hit the issue.
** Changed in: avahi
** Patch added: "gdb-bionic-gcore-bash.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1762320/+attachment/5107574/+files/gdb-bionic-gcore-bash.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in
No VPN in use.. this is probably a bug equally in bind9-host and avahi-
daemon
The host shouldn't be getting stuck and avahi should probably make the
script timeout somehow
** Also affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bind9 (Ubuntu)
Importance:
Public bug reported:
gcore fails to execute on bionic
$ gcore
/usr/bin/gcore: 28: /usr/bin/gcore: Syntax error: "(" unexpected
Line 28 is:
28 dump_all_cmds=()
This appears to be bash syntax for arrays (as reinforced further
With host -d I simply get
> Trying "local"
When it works normally I get;
Trying "local"
Host local. not found: 3(NXDOMAIN)
Received 98 bytes from 10.48.134.6#53 in 1 ms
Received 98 bytes from 10.48.134.6#53 in 1 ms
The system I am hitting this issue on is an upgraded system (rather than
a
** Patch added: "lp1752411-avahi-host-timeout.diff"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+attachment/5117372/+files/lp1752411-avahi-host-timeout.diff
** Changed in: avahi (Ubuntu)
Assignee: (unassigned) => Trent Lloyd (lathiat)
--
You rece
I'd still like to get the upload debdiff for 'timeout' that I prepared
uploaded. Even if we manage to debug the bind9-host issue, it will
still be useful to have the timeout command there as a backup. Not long
before we run out of time for bionic release.
I am actively looking at the bind9-host
Not sure how this happened,, strange dpkg issue it seems like FS
corruption or shutdown during a package install. Unusual to see that.
To get your system back on track, I suggest you try some combination of
these commands (You might need to run each a couple of times depending)
sudo dpkg
There is a new bind9 upload to bionic-proposed (9.11.3+dfsg-1ubuntu1)
Tested with this version and 'host' is still hanging. So this fix is
still required.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
** Tags removed: verification-needed-artful verification-needed-trusty
verification-needed-xenial
** Tags added: verification-done-artful verification-done-trusty
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Verification completed on trusty, xenial and artful
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1661869
Title:
maas install fails inside of a 16.04 lxd container due to
Sure thing!
I conducted two tests based on the reproduction steps in the SRU
template
* setup lxd (apt install lxd, lxd init, get working networking)
* lxc launch ubuntu:16.04 avahi-test --config security.privileged=true
* lxc exec avahi-test sudo apt install avahi-daemon
For xenial, artful
1 - 100 of 164 matches
Mail list logo
