apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909545/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702056
Title:
pe
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909540/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702056
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909546/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702056
Ti
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909543/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702056
Titl
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909542/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702056
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1702056/+attachment/4909544/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702056
Title:
pe
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
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 (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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
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 avahi-dnsconfd
I ran into this myself today after upgrading a machine to bionic..
two copies of it running at once.. both stuck on host.
If I execute a new 'host' command it works, but the existing ones are stuck.l
root 14181 0.0 0.0 4628 868 ?Ss 13:05 0:00 /bin/sh -c
cat /run/systemd/
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: U
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 down)
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
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
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 av
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 (whic
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761763
T
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586528
Title:
Avahi-daemon withdraws addr
Public bug reported:
strongswan-starter and openswan both share the file /usr/sbin/ipsec
however there is no Conflicts relationship
openswan was deprecated in utopic, so trusty installations may wish to
migrate to strongswan ahead of a xenial upgrade. In that case, the
package upgrade can fail.
debdiff to fix the issue
** Patch added: "lp1755693.diff"
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1755693/+attachment/5078920/+files/lp1755693.diff
** Tags added: sts
** Description changed:
strongswan-starter and openswan both share the file /usr/sbin/ipsec
however th
** Changed in: avahi (Ubuntu)
Assignee: (unassigned) => Trent Lloyd (lathiat)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638345
Title:
avahi-daemon crashes multiple times an hour
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
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 gre
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.
** Descript
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
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
** 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
Bugs, which is subscribed to Ubunt
Verification completed on trusty, xenial and artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661869
Title:
maas install fails inside of a 16.04 lxd container due to avahi
problems
To manage
It works for me with my workaround applied, however your groups get
messed up on login due to this bug:
https://github.com/google/fscrypt/issues/77
I've mostly gotten away with that being broken but it causes weird
issues, including problems with snaps as well as anything that needs a
group (virt-
Verified on xenial-queens; fresh nova-lxd install from conjure-up was
exhibiting the behavior, restarting the service did not help. Upgraded
package from queens-proposed and the issue no longer occurs.
** Tags removed: verification-queens-needed
** Tags added: verification-queens-done
--
You r
Public bug reported:
Upgrading python3-cinderclient from 1:4.1.0-0ubuntu1 to 2:4.2.1-0ubuntu2
fails on Eoan due to a conflicting file between the two packages.
It seems there is no equivalent 4.2 upgrade for python-cinderclient so
anyone who previously had both versions installed now meet the con
Part of the reason this behavior exists in Avahi is that many
applications do not correctly retrieve the scope ID (interface index)
when doing hostname resolution, and if not supplied then connection to
such a link local address will fail. Applications are likely to receive
such an address at rando
Part of the reason this behavior exists in Avahi is that many
applications do not correctly retrieve the scope ID (interface index)
when doing hostname resolution, and if not supplied then connection to
such a link local address will fail. Applications are likely to receive
such an address at rando
When I say bind, I actually meant to bind the outgoing connection from
Pidgin (not related to Avahi). So when creating the socket, specify the
source IP address.
The problem is that when you connect (without specifying a source) then
at least for IPv6 due to the routing table specification of the
At a super basic level I can't reproduce this. With an eoan container on
an eoan host I don't get a segfault from ceph-bluestore-tool.
I'd suggest we may need to look at getting
(1) a coredump
(2) the somewhat unlikely but not impossible chance that it's CPU-dependent
for some kind of optimiza
I have been running into this (curtin 18.1-17-gae48e86f-
0ubuntu1~16.04.1)
I think this commit basically agrees with my thoughts but I just wanted
to share them explicitly in case they are interesting
(1) If you *unregister* the cache device from the backing device, it
first has to purge all the
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
n for python3.7
** Changed in: python3.7 (Ubuntu)
Assignee: Trent Lloyd (lathiat) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818778
Title:
Python should be compiled wit
This is a bug in CUPS ultimately, it's driving Avahi using the D-BUS API
(as opposed to manual service files in /etc/avahi/services, this is only
really used for a sysadmin to manually add services, most other types of
advertisements such as printers are expected to use the API to advertise
it).
M
The most likely cause for this is that you have packets outbound on port
5353 firewalled either locally or on your network device. When another
host pings the address, the responses are sent via multicast and Avahi
caches that response, and so can then use it without having to transmit
a packet.
U
I stopped systemd-resolved, disabled it, restarted docker, no change.
I then removed /etc/resolv.conf's symlink and placed my own file there,
restarted docker, still no change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
I ran into this on upgrade today.
>From reading above, I think the root of the problem is that I am using a
>system upgraded from Xenial to Bionic, so I am still using ifupdown and
>resolvconf (and not netplan)
ifupdown doesn't update systemd-resoved, resolvconf/ifupdown updated
/etc/resolv.co
*** This bug is a duplicate of bug 1823281 ***
https://bugs.launchpad.net/bugs/1823281
** This bug has been marked a duplicate of bug 1823281
perf-archive is not shipped in the linux-tools package
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: avahi (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/652870
Title:
Avahi update causes internet connetions to fail
To manage notifications about
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896734
Title:
A privsep daemon spawned by neutron-openvswitch-agent hangs when debug
logging is enabled (large number of registere
There is an indication in the below RHBZ this can actually prevent
openvswitch from working properly as it loses too much CPU time to this
processing in large environments (100s or 1000s of ports)
https://bugzilla.redhat.com/show_bug.cgi?id=1737982
Seems to be a rejected upstream patch here, uncl
I hit this problem again today, but now without zfs-dkms. After
upgrading my kernel from initrd.img-5.8.0-29-generic to 5.8.0-36-generic
my Google Chrome Cache directory is broken again, had to rename it and
then reboot to get out of the problem.
** Changed in: zfs-linux (Ubuntu)
Importance: Un
Another user report here:
https://github.com/openzfs/zfs/issues/10971
Curiously I found a 2016(??) report of similar here:
https://bbs.archlinux.org/viewtopic.php?id=217204
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
It's worth noting that, as best I can understand, the patches won't fix
an already broken filesystem. You have to remove all of the affected
files, and it's difficult to know exactly what files are affected. I try
to guess based on which show a ??? mark in "ls -la". But sometimes the
"ls" hangs, et
Looking to get this approved so that we can verify it, as needing this
ideally released by the weekend of March 27th for some maintenance
activity. Is something holding back the approval?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
When using DVR-SNAT, a simple neutron-l3-agent gateway restart triggers
this issue.
Reproduction Note: Nodes with an ACTIVE or BACKUP (in the case of L3HA)
router for the network are not affected by this issue, so a small 1-6
node environment may make this difficult to reproduce or only affect
hal
I have specifically verified that this bug (vlan traffic interruption
during restart when rabbitmq is down) is fixed by the package in bionic-
proposed. Followed my reproduction steps per the Test Case and all
traffic to instances stops on 12.1.1-0ubuntu3 and does not stop on
12.1.1-0ubuntu4
But n
I got another couple of days out of it without issue - so I think it's
likely fixed.
It seems like this issue looks very similar to the following upstream bug, same
behaviour but a different error, and so I wonder if it was ultimately the same
bug. Looks like this patch from 2.0.3 was pulled int
Just to make the current status clear from what I can gather:
- The GPG key was extended by 1 year to 2022-03-21
- On Ubuntu Bionic (18.04) and newer the GPG key is normally installed
by the ubuntu-dbgsym-keyring package (on 18.04 Bionic onwards). This
package is not yet updated. An update to thi
Updated the following wiki pages:
https://wiki.ubuntu.com/Debug%20Symbol%20Packages
https://wiki.ubuntu.com/DebuggingProgramCrash
With the note:
Note: The GPG key expired on 2021-03-21 and may need updating by either
upgrading the ubuntu-dbgsym-keyring package or re-running the apt-key command.
** Changed in: ubuntu-keyring (Ubuntu)
Importance: Undecided => Critical
** Changed in: ubuntu-keyring (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920640
** Tags added: seg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882416
Title:
virtio-balloon change breaks rocky -> stein live migrate
To manage notifications about this bug go to:
https://bugs.l
I think the issue here is that Stein's qemu comes from Disco which was
EOL before Bug #1848497 was fixed and so the change wasn't backported.
While Stein is EOL next month the problem is this makes live migrations
fail which are often wanted during OpenStack upgrades to actually get
through Stein
I hit this too, after restart to fix it I also lose all my stored
metrics from the last few days. So going to triage this as High.
** Changed in: graphite-carbon (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
SRU proposed for Ubuntu Bionic + Cloud Archive (Queens) for the following 3
bugs:
Bug #1869808 reboot neutron-ovs-agent introduces a short interrupt of vlan
traffic
Bug #1887148 Network loop between physical networks with DVR (Fix for fix to
Bug #1869808)
Bug #1871850 [L3] existing router resour
Ubuntu SRU Justification
[Impact]
- When there is a RabbitMQ or neutron-api outage, the neutron-
openvswitch-agent undergoes a "resync" process and temporarily blocks
all VM traffic. This always happens for a short time period (maybe <1
second) but in some high scale environments this lasts for m
Attaching revised SRU patch for Ubuntu Bionic, no code content changes
but fixed the changelog to list all 3 bug numbers correctly.
** Patch added: "neutron SRU patch for Ubuntu Bionic (new version)"
https://bugs.launchpad.net/neutron/+bug/1869808/+attachment/5464699/+files/lp1869808-bionic.de
This issue seems to have appeared somewhere between zfs-linux
0.8.4-1ubuntu11 (last known working version) and 0.8.4-1ubuntu16.
When the issue first hit, I had zfs-dkms installed, which was on
0.8.4-1ubuntu16 where as the kernel build had 0.8.4-1ubuntu11. I removed
zfs-dkms to go back to the kerne
Accidentally posted the above comment in the wrong bug, sorry, was meant
for https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476 -
where I suspect this bug as having caused a regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
This issue seems to have appeared somewhere between zfs-linux
0.8.4-1ubuntu11 (last known working version) and 0.8.4-1ubuntu16.
When the issue first hit, I had zfs-dkms installed, which was on
0.8.4-1ubuntu16 where as the kernel build had 0.8.4-1ubuntu11. I removed
zfs-dkms to go back to the kerne
Using 2.0.1 from hirsute-proposed it seems like I'm still hitting this.
Move and replace .config/google-chrome and seems after using it for a
day, shutdown, boot up, same issue again.
Going to see if I can somehow try to reproduce this on a different disk
or in a VM with xfstests or something.
--
I can confirm 100% this bug is still happening with 2.0.1 from hirsute-
proposed, even with a brand new install, on a different disk (SATA SSD
instead of NVMe Intel Optane 900p SSD), using 2.0.1 inside the installer
and from first boot. I can reproduce it reliably within about 2 hours
just using th
Public bug reported:
The "perf" tool supports python scripting to process events, this
support is currently not enabled.
$ sudo perf script -g python
Python scripting not supported. Install libpython and rebuild perf to enable
it.
For example:
# apt-get install python-dev (ubuntu)
# yum ins
Logs are not required for this issue
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891269
Title:
perf is not built with python
I have verified the package for this specific virtio-balloon issue
discussed in this bug only.
Migrating from 3.1+dfsg-2ubuntu3.2~cloud0
- To the latest released version (3.1+dfsg-2ubuntu3.7~cloud0) fails due to
balloon setup
2020-10-26T07:40:30.157066Z qemu-system-x86_64: get_pci_config_device
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870824
Title:
Errors in script /usr/lib/avahi/avahi-dae
A no-change rebuild seems to correct this
** Patch added: "lp1873670_mapnik_icu66.debdiff"
https://bugs.launchpad.net/ubuntu/+source/python-mapnik/+bug/1873670/+attachment/5356971/+files/lp1873670_mapnik_icu66.debdiff
--
You received this bug notification because you are a member of Ubuntu
B
= Test Case =
Simple test case per upstream docs:
python3 -c "import mapnik;print(mapnik.__file__)" # should return the
path to the python bindings and no errors
Fails with the current package (1:0.0~20180723-588fc9062-3ubuntu2) -
works with a no-change rebuilt package
** Changed in: python-map
This has been fixed in a new Debian Release (2.2.7+dfsg-1). Tested a
package built on Focal and these warnings go away.
Specifically they added two patches:
0006-Fix-warnings-for-ruby-2.7.patch
0007-Fix-more-warnings-under-ruby-2.7.patch
Since this is in universe but a popular too, hoping we can
I was wrong this package requires a merge due to a small delta on the
upstream Debian package. So I will have to prepare a patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871685
Title:
vagrant
Please sponsor this upload of a merge of Vagrant 2.2.7+dfsg-1 from
Debian. It is a minor upstream version bump (2.2.6 -> 2.2.7) plus
contains new patches from Debian to fix multiple Ruby 2.7 deprecation
warnings on every command invocation.
Two debdiffs attached:
partial merge debdiff showing only
** Patch added: "full merge debdiff from old ubuntu version to new ubuntu
version"
https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+attachment/5356998/+files/lp1871685_complete-merge_2.2.6+dfsg-2ubuntu1_2.2.7+dfsg-1ubuntu1.debdiff
--
You received this bug notification because
** Patch added: "partial merge debdiff showing only the delta to current debian
version"
https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1871685/+attachment/5356999/+files/lp1871685_merge-only_2.2.7+dfsg-1_2.2.7+dfsg-1ubuntu1.debdiff
--
You received this bug notification because you a
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
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
Public bug reported:
As of nss-mdns 0.14 (which is now shipping in Focal 20.04) Avahi no
longer requires to be stopped when a unicast .local domain is present,
nss-mdns now has logic to make this work correctly when Avahi is running
for both multicast and unicast.
We dropped the script that perfo
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
Hi Lucas,
Thanks for the patch updates. When I first submitted this we could have
snuck through before release without an SRU but the patch backport now
makes sense.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
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
Rumen,
When you use 'nslookup' it should go directly to using the DNS server
(127.0.0.53 [which is systemd-resolved]) which typically bypasses
libnss-mdns but also typically doesn't have this 5 second delay (which
avahi can have in some configurations). Seems most likely the 5 second
delay is comi
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
Can you please confirm
(1) The timing of "getent hosts indigosky.local", "host indigosky.local",
"nslookup indigosky.local" and "nslookup indigosky.local 192.168.235.1" all
done at the same time (mainly adding the direct lookup through the server,
wondering if nslookup is doing something weird i
ideally using mdns4_minimal specifically (or i guess, both, but
generally not recommended to use mdns4 in most cases)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888047
Title:
libnss-mdns slow re
This output is generally quite confusing.
Can you try remove the "search www.tendawifi.com" and see how it
differs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888047
Title:
libnss-mdns slow res
The following change in gnome-shell 3.32 looks like the cause:
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/350
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/361
Upstream fix in dash-to-dock here:
https://github.com/micheleg/dash-to-dock/pull/881
This issue is affecting a
This issue is affecting a fairly large number of extensions. The cause
is an intentional breaking change in GNOME Shell 3.32 to move from
Lang.class to ES6 classes.
The following change in gnome-shell 3.32 is the cause:
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/361
Upstream fix in
*** This bug is a duplicate of bug 1819086 ***
https://bugs.launchpad.net/bugs/1819086
** This bug has been marked a duplicate of bug 1819086
Ubuntu 19.04: Some gnome-shell extensions no longer work since updating to
gnome-shell 3.31/3.32
--
You received this bug notification because you
Looks like this was fixed for gnome-shell-extension-*ubuntu-dock* in
upload 64ubuntu5 (March 7).
However gnome-shell-extension-*dashtodock* appears unfixed in the Ubuntu
package
This issue is fixed upstream in git master, however, it appears it has not been
released to extensions.gnome.org or a
** Changed in: passenger (Debian)
Importance: Unknown => Undecided
** Changed in: passenger (Debian)
Remote watch: Debian Bug tracker #812103 => None
** Changed in: passenger (Debian)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs
Forgot to comment: This issue was resolved by the Mirror team shortly
after
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814105
Title:
random 404s on security.ubuntu.com for libavahi packages
To
201 - 300 of 501 matches
Mail list logo
