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 t
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 rel
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 sshd_co
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 s
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: binuti
** 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):
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 s
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 subs
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: "avahi-rlimits-artful.de
[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 Ubuntu
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 subs
This is a bug in CUPS, CUPS needs to remember the address family of the
advertised service (and preferably the interface ID). Avahi does know
this interface and does provide it in the API responses to CUPS, but
it's currently not using it.
For more detailed information please refer to here:
https:
On the previously mentioned HP server today I was able to get closer to
reproducing the situation by testing with bionic (4.15.0-47-generic)
instead of xenial (4.4)
On bionic, unlike xenial, even with the BIOS set to "BIOS controlled
dynamic" mode, the intel_pstate driver is loaded instead of pcc-
Potential upstream fix for backport, may be relevant to MAAS:
https://github.com/lathiat/avahi/pull/206
--
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/1752737
Title:
[2.3.0-
** Changed in: avahi (Ubuntu)
Assignee: (unassigned) => Trent Lloyd (lathiat)
** Changed in: avahi (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
Hi Markos,
After creating this service file, if you check the contents of
/var/log/syslog, you will see that Avahi gave an error parsing the file:
May 10 16:01:30 optane avahi-daemon[1260]: Loading service file
/services/test.service.
May 10 16:01:30 optane avahi-daemon[1260]: /services/test.ser
I'm not sure it makes sense to just universally skip "tun*" interfaces
(at least yet) but we may need to review the scenarios in which
/etc/network/if-up.d/avahi-autoipd is executing.
Helio: Can you provider a reproducer scenario? e.g. is this ubuntu
server, ubuntu desktop, what is the contents of
This is fixed in Ubuntu 20.04 with nss-mdns 0.14 and later which does
proper split horizon handling.
** Changed in: avahi (Ubuntu)
Status: Triaged => Fix Released
** Changed in: nss-mdns (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you a
Public bug reported:
unattended-upgrades attempted to upgrade nova from 2:17.0.9-0ubuntu1 to
2:17.0.10-0ubuntu2.1 (bionic-security), however nova-common contains a
modified conffile (/etc/nova/nova.conf) which prompts during upgrade and
leaves apt/dpkg in a permanent error state requiring manual
i
** Attachment added: "all unattended-upgrades and dpkg logs"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1893889/+attachment/5406806/+files/lp1893889-logs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is sub
** Attachment added: "unattended-upgrades.log.4"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1893889/+attachment/5406807/+files/unattended-upgrades.log.4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Uploaded all historical log files in lp1893889-logs.tar.gz
Uploaded dpkg_-l
For convenient access also uploaded unattended-upgrades.log.4,
unattended-upgrades-dpkg.log.4 and dpkg.log.6 which have the lines from
the first instance of hitting the error
--
You received this bug notification becaus
** Attachment added: "dpkg.log.6"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1893889/+attachment/5406809/+files/dpkg.log.6
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubun
** Attachment added: "unattended-upgrades-dpkg.log.4"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1893889/+attachment/5406808/+files/unattended-upgrades-dpkg.log.4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
** Attachment added: "dpkg_-l"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1893889/+attachment/5406810/+files/dpkg_-l
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
ht
Right, the systems are running 1.1ubuntu1.18.04.11 - in my original
query to you I was trying to figure out if the patches in .12 or .13
were likely to have caused this specific situation and you weren't sure
hence the bug report with more details.
** Changed in: unattended-upgrades (Ubuntu)
For focal we should actually remove this script, since nss-mdns
automatically performs this behaviour and doesn't rely on the "hack" of
stopping avahi-daemon to prevent resolution of .local domains via DNS.
If this error is serious we could consider backport to stable releases.
--
You received t
(for clarity nss-mdns 0.14 does this behavior itself automatically, in
0.10 in bionic does not)
--
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/1870824
Title:
Errors in scrip
For anyone looking at this in 2020, this is fixed in nss-mdns 0.14 which
is in Ubuntu Focal 20.04 - it will now correctly pass through unicast
.local lookups.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
ht
Looking at jctl.txt things look normal, the server starts up, gets
server startup complete and then adds the appropriate IP for wlan0.
Config file looks normal.
Can you please try the following to collect extra debug info
(1) Start a tcpdump and leaving it running - tcpdump --no-promiscuous-mode
OK thanks for the updates. So I can see a lot of mDNS packets in the
lp1874021.pcap capture from various sources. I can see some printers,
google cast, sonoff, etc. Curiously though when you do the avahi cache
dump it isn't seeing any of these.
Wireshark is showing malformed packets for many of th
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 doma
Same connection a couple weeks ago:
Mar 25 08:54:23 localhost NetworkManager[809]: VPN connection 'Work VPN'
(IP Config Get) reply received.
Mar 25 08:54:23 localhost NetworkManager[809]: VPN connection 'Work VPN'
(IP4 Config Get) reply received.
Mar 25 08:54:23 localhost NetworkManager[809]:
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 l
** 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.
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:
ce
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.
https://bugs.launchpad.net/bugs/1
*** 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 showi
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:
https://bugs.launchpad.net/ub
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 po
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 debian/patches/dnsmasq-vpn-dns-fil
** 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
** 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 Ubu
** 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
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:
https://github.com/lathiat/nss-m
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:
av
** 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:
Confir
** 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
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 c
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"
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1342400/+attac
** 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 subscr
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-
4_ubuntu_dists_xenial_
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 c
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.
https://bugs.launchpad
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, you'l
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
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 happens
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.
https://bugs.launchpad.net/
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 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 of
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.
https://bugs.laun
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 c
101 - 164 of 164 matches
Mail list logo
