[Bug 327362] Re: avahi-daemon disabled because there is a unicast .local domain
If you run "sudo avahi-daemon" that starts Avahi manually, bypassing the init script which is what does the check before starting it. -- avahi-daemon disabled because there is a unicast .local domain https://bugs.launchpad.net/bugs/327362 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327362] Re: avahi-daemon disabled because there is a unicast .local domain
No .. if you want to start Avahi manually and daemonize it sudo avahi-daemon -D Regards, Trent -- avahi-daemon disabled because there is a unicast .local domain https://bugs.launchpad.net/bugs/327362 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 237589] Re: In Ubuntu, avahi lacks proper documentation
This is not an Avahi bug. It is a complex series of steps/setup involving tools other than Avahi. So if anything its more an ubuntu- docs bug, btu right now the facilities to do this are not installed by defuakt. ** Changed in: avahi (Ubuntu) Status: New => Invalid -- In Ubuntu, avahi lacks proper documentation https://bugs.launchpad.net/bugs/237589 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 257687] Re: avahi daemon uses a lot of CPU when network is not availiable
Hi Denis, Unfortunately this bug report isn't too helpful to us as there are no more details. Is this a common problem you see? Does it happen every time? Once off? Thanks, Trent -- avahi daemon uses a lot of CPU when network is not availiable https://bugs.launchpad.net/bugs/257687 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99489] Re: avahi-autoipd gives me an useless default route
Hi Steve, Anything that is broken by this is inherently broken, not the Avahi setup - and -they- should be fixed. The link local default is installed at the lowest preference, and should not be used if a better one exists. The original bug report was about openswan, what specific problems have you had? Regards, trent -- avahi-autoipd gives me an useless default route https://bugs.launchpad.net/bugs/99489 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 327362] Re: avahi-daemon disabled because there is a unicast .local domain
Hi Thomas, On 19/02/2009, at 2:25 AM, ThomasNovin wrote: > $ host -t SOA local > local has SOA record localhost. backbone.telia.net. 1 3600 900 > 360 3600 > > Hmm. I'd say avahi's way of detecting this is pretty bad. Is it > perhaps > possible to add a local addition of the .local-domain and reject > lookups? I have my own DNS specified on this machine but the DNS > server > is configured with forwarders to my local ISPs name servers. Yes, so the problem here is your ISP has this local. record - that is *really* broken, FYI :) - Most actual uses of .local are local LANs, often MS domains. There isn't really any better way to 'detect' this.. you could disable the functionality on your box .. but if the user was actually using those .local domains and they turn Avahi on then they will break - and we can't really guess whether they are using them or not. Best Regards, Trent [Avahi Developer] -- avahi-daemon disabled because there is a unicast .local domain https://bugs.launchpad.net/bugs/327362 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 332345] [NEW] avahi discover shows that avahi in ubuntu isn't ipv6 enabled.
Hello, On 21/02/2009, at 9:45 AM, db wrote: > Public bug reported: > > avahi discover shows that avahi in ubuntu isn't ipv6 enabled. mdns- > scan > also doesn't show ipv6 resources. Scanning from a debian lenny system > shows that the ubuntu 8.10 box isn't publishing / on ipv6 for avahi. Avahi supports IPv6 but it is usually disabled out of the box (default configuration). Edit /etc/avahi/avahi-daemon.conf set use-ipv6 = yes Regards, Trent -- avahi discover shows that avahi in ubuntu isn't ipv6 enabled. https://bugs.launchpad.net/bugs/332345 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 343738] Re: vsftpd max username length too small
Any chance of an explanation for the denial for hardy (denied by "Thierry Carrez") I am also a hosting company and since 6.06 we've had to patch this ourselves.. we are now building new servers with 8.04 and find ourselves doing it again - I'm sure we're not in that small a minority. -- vsftpd max username length too small https://bugs.launchpad.net/bugs/343738 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54984] Re: Missing group 'avahi' makes avahi-daemon fail to start
I'm not sure how you ended up without an avahi group but it definitely creates one on install (confirmed in practice) and from the postinst script: if ! getent passwd avahi >/dev/null; then adduser --disabled-password --quiet --system \ --home /var/run/avahi-daemon \ --gecos "Avahi mDNS daemon" --group avahi fi The only thing I can figure is that you created an avahi user manually, e.g. to compile from source or some such which prevented this from running and not creating a group. -- Missing group 'avahi' makes avahi-daemon fail to start https://launchpad.net/bugs/54984 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 55836] Re: Dapper->Edgy upgrade disabled avahi-daemon
** Changed in: avahi (Ubuntu) Importance: Untriaged => Medium Status: Unconfirmed => Confirmed -- Dapper->Edgy upgrade disabled avahi-daemon https://launchpad.net/bugs/55836 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50772] on purge, vmware player leaves /etc/vmware/locations which makes official vmware distributions uninstallable
Public bug reported: Binary package hint: vmware-player I had the vmware-player packages install, but I decided I wanted to try out vmware workstation trial. I downloaded it and ran the script, it said vmware software was already installed. I purged the vmware-modules-`uname -r` and vmware-player packages, and there was no vmware-related packages left, but it left a file /etc/vmware/locations (purge said leaving /etc/vmware as not empty) This causes the official installer to still barf sayign some other vmware product is installable. rm -rf /etc/vmware solves the problem. ** Affects: vmware-player (Ubuntu) Importance: Untriaged Status: Unconfirmed -- on purge, vmware player leaves /etc/vmware/locations which makes official vmware distributions uninstallable https://launchpad.net/bugs/50772 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50792] Re: avahi-bookmarks not packaged
** Changed in: avahi (Ubuntu) Status: Unconfirmed => Confirmed -- avahi-bookmarks not packaged https://launchpad.net/bugs/50792 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50772] Re: on purge, vmware player leaves /etc/vmware/locations which makes official vmware distributions uninstallable
** Changed in: vmware-player (Ubuntu) Assignee: (unassigned) => VMware Build Team Status: Unconfirmed => Confirmed -- on purge, vmware player leaves /etc/vmware/locations which makes official vmware distributions uninstallable https://launchpad.net/bugs/50772 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 41813] Re: pop-up dialogs doesn't close.
Yes I beleive this should definitely be a candidate for dapper-updates Once dapper-backports is going the new version would be a good candidate for that. -- pop-up dialogs doesn't close. https://launchpad.net/bugs/41813 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67572] Narrowing down time zone location is horridly slow when under vesa driver
Public bug reported: Binary package hint: ubiquity I have a NVIDIA card which is currently incorrectly detected to go under the vesa driver (separate bug pending on that) But when narrowing down the time zone location the second screen of ubiquity (in my case to Perth, Western Australia) It is extremely slow to zoom in, assumedly because the vesa driver is not that great but it takes a good 10 seconds for it to stop zooming. I'm not really sure on the technical details but I wonder if something can be done to make that experience better under vesa as having it bog down for a good 10 seconds is rather unsightly. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: Unconfirmed -- Narrowing down time zone location is horridly slow when under vesa driver https://launchpad.net/bugs/67572 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 67573] Fails to detect Nvidia 7600GT to use "nv" driver, defaults to vesa which is terribly slow
Public bug reported: Binary package hint: xserver-xorg I have a pair of PCI-E 7600GT cards, the live cd fails to detect them as using the "nv" driver [which works if i put it in manually and start a second X server] and sues "vesa" instead which is terribly slow. lspci output: 01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0391 (rev a1) 02:00.0 VGA compatible controller: nVidia Corporation Unknown device 0391 (rev a1) Heres full output for the first card 01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0391 (rev a1) (prog-if 00 [VGA]) Subsystem: XFX Pine Group Inc. Unknown device 2220 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://launchpad.net/bugs/67573 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53911] Re: avahi not usable for normal users
I beleive this is planned but not yet done, i knwo the kubuntu guys are working on it, not sure if anyoen else is doign it in gnome but I would certainly be interested in looking at it. That said I really don't like the whole /etc/default thing as it stops you from even one-time starting avahi perhaps with the 'upstart' replacement init stuff this situation can be made better -- avahi not usable for normal users https://launchpad.net/bugs/53911 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 53911] Re: avahi not usable for normal users
joe - this has been the topic of long debate between the ubuntu guys DHCP and DNS currently have 'policy exceptions' the responsible people currently do not feel avahi can be granted such an exception at this stage. enabling by default is not an option, we simply need to determine the 'best' way to make it turn onable. -- avahi not usable for normal users https://launchpad.net/bugs/53911 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 26380] Re: evolution-exchange-storage crashes constantly
This appears resolved in debian now -- evolution-exchange-storage crashes constantly https://launchpad.net/bugs/26380 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24828] Re: IPv6 should be disabled by default
Disabling IPv6 increaseing the throughput of your internet connection makes no sense and I think thats just circumstantial, sorry :) The place where it *does* make a difference is the speed of new connections, it seems that in some cases certain dns servers ignore requests for IPv6 records and so everytime you try to resolve an IPv6 address it waits for them to timeout. These broken DNS servers should really be fixed, but the last point could work, not to bother looking up, guess it would fix some of these cases. Could someone who experiences and is willing to let me login to their machine please contact me? I'd love to try this as its never really affected me. -- IPv6 should be disabled by default https://launchpad.net/bugs/24828 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54317] Please sync bcm43xx-fwcutter 20060501-4 from unstable
Public bug reported: Binary package hint: bcm43xx-fwcutter Source: bcm43xx-fwcutter Debian Version: 20060501-4 (unstable) Ubuntu changes were just a fake sync, so OK to override ** Affects: bcm43xx-fwcutter (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Please sync bcm43xx-fwcutter 20060501-4 from unstable https://launchpad.net/bugs/54317 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24828] Re: [Bug 24828] Re: [Bug 24828] Re: IPv6 should be disabled by default
On Fri, Jul 28, 2006 at 04:23:11AM -, Martin Hosken wrote: > Dear Trent, > > Disabling IPv6 increaseing the throughput of your internet connection > > makes no sense and I think thats just circumstantial, sorry :) > > > > The place where it *does* make a difference is the speed of new > > connections, it seems that in some cases certain dns servers ignore > > requests for IPv6 records and so everytime you try to resolve an IPv6 > > address it waits for them to timeout. > > > > It is worse than that. In the time it takes for the IPv6 DNS request to > fail the application times out on making its connection. > > These broken DNS servers should really be fixed, but the last point > > could work, not to bother looking up, guess it would fix some of these > > cases. > > > > It's not a question of the DNS server being dumb it's usually some cheap > ADSL router/modem that is sitting between the computer and a good DNS > server. Often configuring the router to pass a real DNS server address > to the dhcp client is enough to solve the problem. But not all routers > allow you to configure the dhcp server in them sufficiently. > > So perhaps the real fix is to provide a way to turn off IPv6 DNS > requests. But I guess that is impossible without turning off IPv6 in > general. How much IPv6 takes off depends to a large extent on what MS do > with Vista, I would suspect. > > Could someone who experiences and is willing to let me login to their > > machine please contact me? I'd love to try this as its never really > > affected me. > > > I'll send you directly, offline, a couple of tcpdump traces to compare. > One is dns request to the D-Link 504T ADSL modem/router and the other is > directly to a DNS server with packets merely routed by the modem. > > -- > IPv6 should be disabled by default > https://launchpad.net/bugs/24828 -- Trent Lloyd <[EMAIL PROTECTED]> Bur.st Networking Inc. -- IPv6 should be disabled by default https://launchpad.net/bugs/24828 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60879] Re: lynx gets stuck in infinite loop rendering invalid HTML
** Visibility changed to: Public -- lynx gets stuck in infinite loop rendering invalid HTML https://launchpad.net/bugs/60879 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49691] Re: gaim does not deactivite 'paste' command when no buffer, and executing it causes crash
I'm afraid I can't seem to reproduce this now so I will close. ** Changed in: gaim (Ubuntu) Status: Needs Info => Rejected -- gaim does not deactivite 'paste' command when no buffer, and executing it causes crash https://launchpad.net/bugs/49691 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69962] Re: umnet dependencies libavahi-compat-libdnssd1
You may need to dpkg --purge bonjour (someone else had an issue where it wouldnt uninstall with apt due to tryign to fix the kubuntu-desktop problem at the same time) -- umnet dependencies libavahi-compat-libdnssd1 https://launchpad.net/bugs/69962 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69457] Re: Avahi warning when launching gobby
Is avahi running? ps aux|grep avahi -- Avahi warning when launching gobby https://launchpad.net/bugs/69457 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69457] Re: Avahi warning when launching gobby
Can you try: cat /etc/default/avahi-daemon also note that this error will popup (the 'warning you are using the howl compat layer') whether avahi is running or not, if thats what you are referring too. -- Avahi warning when launching gobby https://launchpad.net/bugs/69457 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65587] Re: "/etc/init.d/avahi-daemon start" doesn't start anything
The purpose this serves is that avahi-daemon will now be installed by default, but we do not want it to start by default, this is an option provided by the network preferences. This is somewhat slightly confusing, but it's been determined the 'best' way to do this ** Changed in: avahi (Ubuntu) Status: Unconfirmed => Rejected -- "/etc/init.d/avahi-daemon start" doesn't start anything https://launchpad.net/bugs/65587 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65308] Re: Automatic Service Discovery-Button in the network-admin can't be set
Is avahi-daemon actually running? If you install 'avahi-discover' and run it, can you see your own services (workstation service, for example) Also, if so, what network interface do you have / what type is it? -- Automatic Service Discovery-Button in the network-admin can't be set https://launchpad.net/bugs/65308 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65603] /etc/init.d/avahi-daemon should print a message if disabled and run interactively
Public bug reported:
With avahi-daemon being disabled by default, many users get confused as
to why avahi is not working when installed
There are 2 main cases
1) They install avahi and it "just doesnt work"
2) They install avahi, it's not working, they try to manually run
"/etc/init.d/avahi-daemon start" and nothing happens
I think we can solve the latter by makign the init script print a
message when run interactively, the pcmciautils script does this and
uses the following function to determine if its run by init or not:
run_by_init()
{
([ "$previous" ] && [ "$runlevel" ]) || [ "$runlevel" = S ]
}
** Affects: avahi (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
/etc/init.d/avahi-daemon should print a message if disabled and run
interactively
https://launchpad.net/bugs/65603
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65603] Re: /etc/init.d/avahi-daemon should print a message if disabled and run interactively
** Changed in: avahi (Ubuntu) Assignee: (unassigned) => Avahi Team -- /etc/init.d/avahi-daemon should print a message if disabled and run interactively https://launchpad.net/bugs/65603 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65587] Re: "/etc/init.d/avahi-daemon start" doesn't start anything
Fergal: you can run the script with /etc/init.d/avahi-daemon (dont forgot to also fix the /etc/default/avahi file) Please note that with the change to upstart in ubuntu I beleive the /etc/rc?.d stuff has changed but I'm not really familiar with the changes there (they are backwards compatible, e.g. you can link stuff into rc?.d, but the default ubuntu stuff is not put there, it is done the native upstart way) Please refer to the upstart docs as again I'm not familiar how that works. -- "/etc/init.d/avahi-daemon start" doesn't start anything https://launchpad.net/bugs/65587 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65676] Re: Package should edit /etc/nsswitch.conf on install
Yes this would violate the no open ports policy if this package is installed by default nss-mdns (much like a standard DNS resolver) opens a port at the time of tryign to resolve in order to receive responses When avahi is installed it uses that, and its open ports, but in standalone mode it opens them itself. -- Package should edit /etc/nsswitch.conf on install https://launchpad.net/bugs/65676 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65587] Re: "/etc/init.d/avahi-daemon start" doesn't start anything
Actually it's not the only package, I know among other things bittorrent and rsync have this option, and it's there so that avahi can be installed by default but not enabled on an ubuntu system. Yes it is a little confusing, that is unfortunate. As for upstart/rc?.d links, thats the price of moving forward into a better init sytsem, it's simply something people will have to learn like the various other changes I guess As for a warning, see https://launchpad.net/distros/ubuntu/+source/avahi/+bug/65603 -- "/etc/init.d/avahi-daemon start" doesn't start anything https://launchpad.net/bugs/65587 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65587] Re: "/etc/init.d/avahi-daemon start" doesn't start anything
*** This bug is a duplicate of bug 56426 *** Ah yes I forgot dbus starts it not rc?.d.. oops.. What would you propose is the best solution? Given dbus starts it.. im thinking perhaps we could move the default start behavior to ONLY affect the dbus script and leave /etc/inti.d /avahi-daemon to work as expected That would then leave 2 places to check if avahi is being started tho but perhaps that is the better solution ** This bug has been marked a duplicate of bug 56426 /etc/init.d/avahi-daemon is useless -- "/etc/init.d/avahi-daemon start" doesn't start anything https://launchpad.net/bugs/65587 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56426] Re: /etc/init.d/avahi-daemon is useless
While it is started by dbus, it links to ../init.d/avahi-daemon so the init script is the one used by dbus See also Bug #65587 ** Bug 65587 has been marked a duplicate of this bug -- /etc/init.d/avahi-daemon is useless https://launchpad.net/bugs/56426 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56426] Re: /etc/init.d/avahi-daemon is useless
See in Bug #65587 --- Ah yes I forgot dbus starts it not rc?.d.. oops.. What would you propose is the best solution? Given dbus starts it.. im thinking perhaps we could move the default start behavior to ONLY affect the dbus script and leave /etc/inti.d /avahi-daemon to work as expected That would then leave 2 places to check if avahi is being started tho but perhaps that is the better solution --- -- /etc/init.d/avahi-daemon is useless https://launchpad.net/bugs/56426 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65603] Re: /etc/init.d/avahi-daemon should print a message if disabled and run interactively
See https://lists.ubuntu.com/archives/ubuntu- devel/2006-October/021733.html for a revised proposal -- /etc/init.d/avahi-daemon should print a message if disabled and run interactively https://launchpad.net/bugs/65603 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 28712] Re: gdm loses focus when mouse pointer is outside window (when initially started)
Just to confirm, this works fine for me in edgy -- gdm loses focus when mouse pointer is outside window (when initially started) https://launchpad.net/bugs/28712 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
This is actually due to nss-mdns not avahi directly ** Changed in: nss-mdns (Ubuntu) Sourcepackagename: avahi => nss-mdns -- mdns listed in nsswitch.conf causes excessive time for dns lookups https://bugs.launchpad.net/bugs/94940 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
The binary package is called libnss-mdns -- mdns listed in nsswitch.conf causes excessive time for dns lookups https://bugs.launchpad.net/bugs/94940 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192581] Re: [gutsy] avahi goes berserk
This is not a bug in Avahi. Avahi addresses are assigned if and when DHCP gives up trying to assign an address. The root of your problem will be DHCP timing out for some reason - I can't speculate to this but you should check I think /var/log/daemon.log to see what happened around the time it gave up trying to get an address. ** Changed in: avahi (Ubuntu) Status: New => Invalid -- [gutsy] avahi goes berserk https://bugs.launchpad.net/bugs/192581 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80900] Re: problems resolving fully qualified domain names on Kubuntu feisty
Marking as confirmed. This is a known issue. Unfortunately the .local detection script does not work if no root "local." domain exists. A possible fix may be to have libnss-mdns not lookup .local hosts with more than 2 labels i.e. lookup test.local but not machine.test.local Seems all MS networks always will use host-names in the form of host.DOMAIN.local correct? Is there any host.local case? ** Changed in: avahi (Ubuntu) Importance: Undecided => Medium Status: Invalid => Confirmed -- problems resolving fully qualified domain names on Kubuntu feisty https://bugs.launchpad.net/bugs/80900 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 28953] Re: mdns service discovery in cups
Hi Bruce, Your comment doesn't indicate whether this has actually been pushed into Ubuntu and if it can be installed with the Avahi compat layer? Can you let me know? Thanks, Trent -- mdns service discovery in cups https://bugs.launchpad.net/bugs/28953 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99150] Re: Feisty beta can't install avahi-daemon on partial upgrade
Uh... how on earth did this happen? The package is installed and runs setup yet /etc/init.d/avahi-daemon doesn't exist? -- Feisty beta can't install avahi-daemon on partial upgrade https://bugs.launchpad.net/bugs/99150 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99150] Re: Feisty beta can't install avahi-daemon on partial upgrade
OK, I have clarified... This has resulted because the packaged has been REMOVED but not PURGED (which removes conf files, which /etc/init.d/avahi-daemon is one) and then /etc/init.d/avahi-daemon is manually removed. The best thing we can do here is just put || true on the /etc/init.d /avahi-daemon or an if [ -x or something, which we will do but not until feisty is released. ** Changed in: avahi (Ubuntu) Importance: Undecided => Low Assignee: (unassigned) => Trent Lloyd Status: Unconfirmed => Confirmed Target: None => later -- Feisty beta can't install avahi-daemon on partial upgrade https://bugs.launchpad.net/bugs/99150 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99150] Re: Feisty beta can't install avahi-daemon on partial upgrade
Apparently we violate policy by not using invoke-rc.d also. -- Feisty beta can't install avahi-daemon on partial upgrade https://bugs.launchpad.net/bugs/99150 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 162084] Re: MDNS not working properly
Yeh, the other server actually never recieves the query. It works when you first do the restart because the names are announced the first time - but once they fall out of the cache it can't resolve them again as the queries are never received. Unfortunately it is a common problem with dodgy wifi drivers. -- MDNS not working properly https://bugs.launchpad.net/bugs/162084 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195140] Re: SetHostName can be called by users
I'd like to repoint out that mDNS is an *untrusted*, *ad-hoc* source. if you have something relying on mDNS for any secure operation then THAT IS BROKEN, not Avahi. SetHostname in avahi has nothing to do with the 'sethostname' from LSB.. All sethostname in Avahi does is change the hostname avahi reports over mDNS. Nothing more. This can easily be done by firing up another mDNS daemon, or even someone on another host could spoof your hostname as that. Or using the Avahi API you can even publish a second hostname the same as if you had changed the primary one. Again, mDNS is an UNTRUSTED domain. So your report is completely bogus because you should never be trusting it in the first place. Avahi is not a 'mess', you seem to think it is something it is not. -- SetHostName can be called by users https://bugs.launchpad.net/bugs/195140 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195140] Re: SetHostName can be called by users
That is completely bogus... using SetHostName certainly does not change your IP, in fact because Avahi drops its privileges, it couldn't do this even if it wanted to. The only thing here is that it simply says "From foobar.local" - which is just a result of using libnss-mdns to lookup the reverse DNS of the host (which you now changed to foobar.local). This shows up because that host is not reachable so it shows the unreachable messages which come from the local host.. which now has that mDNS reverse-dns. Note that nsswitch.conf refers to DNS first (before mdns) so if you have a local authorative DNS with reverse dns it would be preferred over mDNS. -- SetHostName can be called by users https://bugs.launchpad.net/bugs/195140 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195140] Re: SetHostName can be called by users
Loye, With all due respect.. this is completely and utterly irrelevant. You could have this kind of interaction with any piece of software, they could download and install MSN and chat to each other.. or use windows file sharing.. or one of a million ways to interact with each other over a network. Hell, they could call each other on the phone or shout out the window. At the end of the day if you really think this is a problem for you then just disable it (in /etc/default) but I think you are just being over the top, and if not then theres a LOT more than Avahi you need to worry about so removing Avahi for all users (esp those at homes, etc) in preference of some weird company who thinks this rule is the be all and end all is ludicrous. It would also not be hard to disable Avahi on the long list of things you should be disabling.. nevermind to prevent this kind of information being problematic you should really be using a firewall.. but then what if they both login to a web-based chat site? Your broken again. Perhaps you should turn their network off. Avahi is not "inherrently insecure", it is "inherrently untrustable". It makes the things its designed to do very convenient but you should not rely on it for any trusted activity. It is great for things like, finding multiplayer games, finding people to chat to on a local network, etc. Where trusting what is at the other end is not a problem. Note that even DNS itself is not much more secure at the end of the day it's not hard for me to spoof a local DNS server on a LAN or even the gateway with some arp spoofing. Any network protocol, generally speaking, is not quite as secure as most people wish it was. Please stop this pointless thread, the only bug here is whether SetHostName should or should not be allowed to be changed by any user.. which is at worst a nuisance and I will open a bug upstream about this but I don't really see it as being a "big issue" and I'm not even sure that behavior should be changed. Regards, Trent -- SetHostName can be called by users https://bugs.launchpad.net/bugs/195140 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195140] Re: SetHostName can be called by users
Please note that this SetHostname command does not in any way change the hostname of the computer.. only that which Avahi represents itself on the local un-trusted mDNS domain. Thus this is not much of a security risk and at worst a nuisance. I am not quite sure what you mean about the Destination host unreachable thing.. can you clarify a little further? Thanks, Trent -- SetHostName can be called by users https://bugs.launchpad.net/bugs/195140 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 108826] Re: Ugrade aborts from 6.10 to 7.04
** Attachment added: "apt.log (from submitter)" http://librarian.launchpad.net/7392203/apt.log -- Ugrade aborts from 6.10 to 7.04 https://bugs.launchpad.net/bugs/108826 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 108826] Re: Ugrade aborts from 6.10 to 7.04
** Attachment added: "main.log (from submitter)" http://librarian.launchpad.net/7392198/main.log -- Ugrade aborts from 6.10 to 7.04 https://bugs.launchpad.net/bugs/108826 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82287] Re: [feisty] avahi daemon interacts badly with network-manager
This is odd... there is no reason avahi-daemon should affect Network managers access in any way. I will attempt to find out how you can find some debug info out. -- [feisty] avahi daemon interacts badly with network-manager https://bugs.launchpad.net/bugs/82287 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109750] Re: avah port setup to Eth0 which isn't a valid interface
eth0:avahi is bought up on any interface that does NOT have a real IP, it is a link local IP only needed when a normal IP is not available. According to RFC3927 "When an operable routable address is available on an interface, the host SHOULD NOT also assign an IPv4 Link-Local address on that interface." Hence there is no problem here. -- avah port setup to Eth0 which isn't a valid interface https://bugs.launchpad.net/bugs/109750 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 109750] Re: avah port setup to Eth0 which isn't a valid interface
I will close this bug now, let me know if you have any further queries. ** Changed in: avahi (Ubuntu) Status: Unconfirmed => Rejected -- avah port setup to Eth0 which isn't a valid interface https://bugs.launchpad.net/bugs/109750 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 82287] Re: [feisty] avahi daemon interacts badly with network-manager
** Changed in: avahi (Ubuntu) Assignee: (unassigned) => Trent Lloyd -- [feisty] avahi daemon interacts badly with network-manager https://bugs.launchpad.net/bugs/82287 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94940] Re: mdns listed in nsswitch.conf causes excessive time for dns lookups
Apparently the usual cause for this is having no reverse DNS setup -- mdns listed in nsswitch.conf causes excessive time for dns lookups https://bugs.launchpad.net/bugs/94940 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66845] Re: gnome-nettool window does not repaint correctly when avahi hostname is used.
Closing at submitters request. Thanks for your report. ** Changed in: nss-mdns (Ubuntu) Status: Needs Info => Fix Released -- gnome-nettool window does not repaint correctly when avahi hostname is used. https://bugs.launchpad.net/bugs/66845 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78680] Re: avahi's "enable_avahi" script does not turn on MDNS resolution
Any updates on this bug Jens? -- avahi's "enable_avahi" script does not turn on MDNS resolution https://bugs.launchpad.net/bugs/78680 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112584] Mounting UDF should be preferred over ISO9660
Public bug reported: Binary package hint: gnome-volume-manager Currently, if a CD is inserted with both UDF and ISO9660 file systems, the ISO9660 is mounted instead. This is contrary to /etc/fstab /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 even typing "mount /media/cdrom0", I end up with iso9660 mounted, as I do with the automount. This seems to have been handled in Bug #7682 but that fix doesn't seem to actually work properly. ** Affects: gnome-volume-manager (Ubuntu) Importance: Undecided Status: Unconfirmed -- Mounting UDF should be preferred over ISO9660 https://bugs.launchpad.net/bugs/112584 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112584] Re: Mounting UDF should be preferred over ISO9660
this might be a bug in 'mount' rather than gnome-volume-manager, or maybe both? not sure how it works If i run mount -t udf /dev/scd0 /media/cdrom0 it happily mounts UDF -- Mounting UDF should be preferred over ISO9660 https://bugs.launchpad.net/bugs/112584 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104038] Upgrade to feisty causes loss of TTYs due to incorrect file mangling
Public bug reported: Binary package hint: upstart I upgraded my machine to feisty and caused loss of TTYs, it mangled the tty1-tty6 files The last line now reads "/sbin/getty 38400 tty2exec /sbin/getty 38400 tty2" (same for each different tty) Which obviously is wrong, I suspect one of the upgrade scripts may have caused this Now as a point I cannot remember if this machine was upgraded from dapper, or from edgy, I suspect it may have been dapper which could be the root of the problem, I realise that generally upgrading between releases is not supported but since 6.06 is LTS this may cause a bug when the next LTS comes out so could probably be fixed. This is also really bad because you lose the TTY in recovery mode as well. ** Affects: upstart (Ubuntu) Importance: Critical Status: Unconfirmed ** Changed in: upstart (Ubuntu) Importance: Undecided => Critical -- Upgrade to feisty causes loss of TTYs due to incorrect file mangling https://bugs.launchpad.net/bugs/104038 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68503] Re: libavahi-compat-libdnssd1_0.6.13-2ubuntu2_i386.deb will not install
Hi There, If we look at the line "overwrite `/usr/lib/libdns_sd.so.1', which is also in package bonjour" As far as I am aware 'bonjour' is not an official package, hence the conflict You would need ot remove the bonjour package first and then installation should suceed. -- libavahi-compat-libdnssd1_0.6.13-2ubuntu2_i386.deb will not install https://launchpad.net/bugs/68503 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68503] Re: libavahi-compat-libdnssd1_0.6.13-2ubuntu2_i386.deb will not install
Can you please run dpkg -L bonjour and paste the output? ** Changed in: avahi (Ubuntu) Status: Unconfirmed => Rejected -- libavahi-compat-libdnssd1_0.6.13-2ubuntu2_i386.deb will not install https://launchpad.net/bugs/68503 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65308] Re: Automatic Service Discovery-Button in the network-admin can't be set
** Changed in: avahi (Ubuntu) Status: Unconfirmed => Fix Released -- Automatic Service Discovery-Button in the network-admin can't be set https://launchpad.net/bugs/65308 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50792] Re: avahi-bookmarks not packaged
** Changed in: avahi (Ubuntu) Importance: Undecided => Wishlist -- avahi-bookmarks not packaged https://launchpad.net/bugs/50792 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68503] Re: libavahi-compat-libdnssd1_0.6.13-2ubuntu2_i386.deb will not install
No you need to *remove* the package This is a package of bonjour - apples implementation, obviously the Avahi compatability layer for Bonjour (DNSSD) would conflict with this, hence the failed install And because bonjour is not an official ubuntu package (e.g. not in the ubuntu archives) we haven't told the avahi package to Conflict with it (which would have made the packaging system remove it for you if you tried to install it manually) -- libavahi-compat-libdnssd1_0.6.13-2ubuntu2_i386.deb will not install https://launchpad.net/bugs/68503 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65601] Re: .service file not installed
** Bug watch added: Avahi #67 http://www.avahi.org/ticket/67 ** Also affects: avahi (upstream) via http://www.avahi.org/ticket/67 Importance: Unknown Status: Unknown ** Changed in: avahi (Ubuntu) Importance: Undecided => Low Assignee: (unassigned) => Trent Lloyd Status: Rejected => Confirmed ** Changed in: avahi (Ubuntu) Assignee: Trent Lloyd => Avahi Team ** Changed in: avahi (upstream) Bugwatch: Avahi #67 => Avahi bug tracker #67 -- .service file not installed https://launchpad.net/bugs/65601 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87003] Re: NVIDIA 7600GT detected as vesa not nv
Attaching! ** Attachment added: "lspci -vvn output" http://librarian.launchpad.net/6793430/lspci-nvidia.txt -- NVIDIA 7600GT detected as vesa not nv https://launchpad.net/bugs/87003 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87003] Re: NVIDIA 7600GT detected as vesa not nv
Here's the same thing but run as root so the capabilities etc are shown ** Attachment added: "sudo lspci -vvn output" http://librarian.launchpad.net/6793448/lspci-nvidia.txt -- NVIDIA 7600GT detected as vesa not nv https://launchpad.net/bugs/87003 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86103] Re: azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
Confirmed here with azureus & some in browser applets. -- azureus-> java: xcb_xlib.c:50: xcb_xlib_unlock: Assertion `c->xlib.lock' failed. https://launchpad.net/bugs/86103 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86636] Re: [apport] service-discovery-applet crashed with DBusException in __new__()
Hrm... looks like dbus is not running? -- [apport] service-discovery-applet crashed with DBusException in __new__() https://launchpad.net/bugs/86636 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88745] Re: removing libnss-mdnss leaves system unusable
AIUI, nss-mdns does actually attempt to do this. Can you attach the nsswitch.conf you had at the time? -- removing libnss-mdnss leaves system unusable https://launchpad.net/bugs/88745 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88745] Re: removing libnss-mdnss leaves system unusable
Hrm it's a shame you don't remember as we can't see if it was off standard and why it wasn't automatically edited the default is files mdns_minimal [NOTFOUND=return] dns mdns4 -- removing libnss-mdnss leaves system unusable https://launchpad.net/bugs/88745 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90089] Re: [apport] service-discovery-applet crashed with AttributeError in gc_services_cb()
*** This bug is a duplicate of bug 89940 *** ** This bug has been marked a duplicate of bug 89940 Sync request: service-discovery-applet 0.4.4 from Debian/experimental (main) -- [apport] service-discovery-applet crashed with AttributeError in gc_services_cb() https://launchpad.net/bugs/90089 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24828] Re: IPv6 should be disabled by default
Please remember this has *nothing* to do with whether your modem/router *supports* IPv6, but whether its inherrently broken and doesn't handle DNS queries properly. I'm not saying this makes it any less of a problem but you must understand its a bug in the devices, they should just pass the DNS requests on properly, I highly expect you'll have exactly the same problem with Vista. -- IPv6 should be disabled by default https://launchpad.net/bugs/24828 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99489] Re: avahi-autoipd gives me an useless default route
It is not 'useless' it is installed as a last resort thus should not cause any problems It what way does it confuse openswan? -- avahi-autoipd gives me an useless default route https://launchpad.net/bugs/99489 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99489] Re: avahi-autoipd gives me an useless default route
That route tells it to just send packets for any IP directly out the interface, this is usefull because in a LAN using zeroconf LL IPs (as avahi-autoipd), only hosts without another non-LL ip should have an LL ip. So without a default (last resort) route out the interface, if you only had an LL ip you would not be able to communicate with other hosts that didn't have an LL ip. -- avahi-autoipd gives me an useless default route https://launchpad.net/bugs/99489 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 24828] Re: IPv6 should be disabled by default
Howdy, >>> breaking ip6tables completely, since IPv6 autoloading got disabled, >>> and any sane person will do firewall configuration before >>> configuration the network interfaces. > On my system, the upgrade also had the very unkind effect ofI usually > load a firewall on given protocol once lo is up on that protocol for 2 > reasons > I don't. Is it a reason to break my working system? > > Besides, it does not work either, since there were no need to set inet6 > explicitly on lo so far. > I have to say I am somewhat in agreeance that this should potentially be made to apply "only to new installs", because it can break existing machines that are only available via IPv6, etc. >> 2) it is always executed before any real interface is up. >> > > That's a side effect. In practice, lo is created by the kernel, and the > lo interface in /etc/network/interfaces is really a cosmetic entry. > That is not correct, the kernel creates 'lo' just like it creates eth0, eth1, etc, but it does not configure an IP. This is what that stanza does. > >> Another way to hook up a firewall script to a specific protocol is to >> use the /etc/modprobe.d/ to run a script as soon as a certain module >> is loaded. >> > > If ipv6 gets loaded after some real interface is brought up, we get an > unfirewalled time window, which was the precise reason for not doing it > that way. > Put lo before any other interfaces in 'auto' and that should not happen AFAIK. >> It appears somebody is using it this way and it was brought up as use >> case. I will check this up again. >> > > It appears many more people are using IPv6 and expect it to work out of > the box on their Ubuntu Feisty, as it did in Dapper and Edgy. From > reading the bug thread and the rants on freenode/#ipv6, I have a > feeling I am not the only one. > > 18:44 [EMAIL PROTECTED] ~% host basile.link > basile.link has IPv6 address fe80::211:11ff:fe25:e6b4 > 18:44 [EMAIL PROTECTED] ~% ssh basile.link > ssh: connect to host basile.link port 22: Invalid argument > 18:44 [EMAIL PROTECTED] ~% ssh basile.link%eth0 > ssh: basile.link%eth0: Name or service not known > 18:44 [EMAIL PROTECTED] ~% ping6 basile.link > connect: Invalid argument > 18:44 [EMAIL PROTECTED] ~% ping6 basile.link -I eth0 -c 1 > PING basile.link(basile.link) from fe80::20d:60ff:fe38:6d16 eth0: 56 > data bytes > 64 bytes from basile.link: icmp_seq=1 ttl=64 time=0.167 ms > > --- basile.link ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 0.167/0.167/0.167/0.000 ms > > ping6 is the only application that can handle this, which is of pretty > limited use. Also, when you're down to doing link diagnostics, you > probably cannot reach the DNS server, so you'd better use numerical > addresses anyway. > Link local addresses aren't limited to just "link diagnostics", also when using avahi/zeroconf, you may well have dns for just the local link. It is true, and somewhat annoying, that using link local IPs require interfaces to be specifically set, some applications will do this, some won't, this is an ongoing issue in relation to Avahi right now. Cheers, Trent -- IPv6 should be disabled by default https://bugs.launchpad.net/bugs/24828 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24828] Re: IPv6 should be disabled by default
Has anyone affected by this tried this in feisty? Apparently there may be some changes in glibc 2.5 which affect this? Trent -- IPv6 should be disabled by default https://bugs.launchpad.net/bugs/24828 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 24828] Re: IPv6 should be disabled by default
Thomas Butter wrote: >> Link local addresses aren't limited to just "link diagnostics", also >> when using avahi/zeroconf, you may well have dns for just the local link. >> > > I am no avahi expert so I could be wrong. I think avahi/zeroconf only > uses the dns protocol, but won't use the glibc name resolution functions > with link local addresses. So this use case won't affect the Vista/OS X > like name resolution. > Well, I am ;) I was talking about situations where you could be using a link local IP, that is in DNS, where you may not have a default route. Case in point was Avahi which can make use of link local IPs which you can then get at with DNS using the libnss-mdns, having said that given the interface specification stuff, they are relatively useless unless your using the Avahi API directly which allows you to get the interface along with the name. Cheers, Trent -- IPv6 should be disabled by default https://bugs.launchpad.net/bugs/24828 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97685] Re: Dlink WNA-2230 will not work (listed as "works out of the box")
I fail to see how avahi-daemon could be breaking your network Also it is not insecure it is simply "a security risk" like any other network service running on your machine, there are no known remote bugs but that doesn't mean none exist -- Dlink WNA-2230 will not work (listed as "works out of the box") https://launchpad.net/bugs/97685 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98763] Re: avahi did not warn .local SOA in use
What version of Ubuntu are you running? -- avahi did not warn .local SOA in use https://launchpad.net/bugs/98763 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98763] Re: avahi did not warn .local SOA in use
Hrm, 7.04 beta according to the forum post... there is code to detect this I wonder why it didn't work If you run host -t soa local. What happens? Trent -- avahi did not warn .local SOA in use https://launchpad.net/bugs/98763 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24828] Re: IPv6 should be disabled by default
It is worth noting while the ifupdown changes will cause any static setups to continue working, it will break setups relying on autoconfiguration, which are quite common for those using IPv6. -- IPv6 should be disabled by default https://launchpad.net/bugs/24828 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24828] Re: IPv6 should be disabled by default
As I understand it, a patch has now been applied to glibc "A fixed glibc with the following patch has been uploaded today: 14:30 < Mithrandir> Uploading to ubuntu (via ftp to upload.ubuntu.com): glibc_2.5-0ubuntu13.dsc: done. glibc_2.5-0ubuntu13.diff.gz: done. glibc_2.5-0ubuntu13_source.changes: done. This glibc has the following patch in it: http://err.no/patches/glibc-only-lookup-ipv6-if-it-makes-sense.diff Mithrandir is Tollef Fog Heen, Ubuntu Release Manager. " Which should fix this issue in a much better way - will this hack now be reverted? -- IPv6 should be disabled by default https://bugs.launchpad.net/bugs/24828 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 24828] Re: IPv6 should be disabled by default
Rock, I really do feel this is the right solution I guess at the end of the day your blacklisting kicked enough upraw to fix the problem, so I guess it was the right move :) Cheers! Trent -- IPv6 should be disabled by default https://bugs.launchpad.net/bugs/24828 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102865] Re: avahi-autoipd in roaming mode set ip address to 0.0.0.0
I am a little confused your bug report isn't quite clear enough to indicate the problem. Can you show me the exact tcpdump lines? -- avahi-autoipd in roaming mode set ip address to 0.0.0.0 https://bugs.launchpad.net/bugs/102865 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95743] Re: Local user can crash avahi-daemon with ServiceBrowserNew() call
Well it's a 2 line fix, probably worth doing I guess.. it is a local DoS I guess its not *that* important, i.e. its not remote etc -- Local user can crash avahi-daemon with ServiceBrowserNew() call https://launchpad.net/bugs/95743 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83468] Re: Avahi behaves badly where there is a unicast .local-domain.
This is *not* caused by DHCP releases simply being renewed I have tested this just now (with both NetworkManager and a standard ifup) I can think only possibly it might happen if you got a new IP every lease every few seconds but this seems silly as everything else would drop out also In short: not 100% sure what is causing this issue ATM. Marten -- Are you in a position to reproduce this? Can you tell me if your IP changes each time this happens? ** Changed in: avahi (Ubuntu) Importance: Undecided => High -- Avahi behaves badly where there is a unicast .local-domain. https://launchpad.net/bugs/83468 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83468] Re: Avahi behaves badly where there is a unicast .local-domain.
Possibly makes sense to apply this patch also to disable this function if Avahi is already disabled. Although perhaps we should still check if Avahi is stopped in this case (in case it was started manually) but not send an alert, or perhaps it makes sense not to do a popup notify at all also perhaps makes sense instead to check if avahi is started at all (this can be done with 'avahi-daemon -c' and not notify if its not (i.e. its already disabled) opinions? ** Attachment added: "patch to disable .local checking if /etc/default/avahi-daemon says its not to be started" http://librarian.launchpad.net/6480728/disable-if-default-disabled.diff -- Avahi behaves badly where there is a unicast .local-domain. https://launchpad.net/bugs/83468 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 83468] Re: Avahi behaves badly where there is a unicast .local-domain.
I've just realised I'm totally wrong the message that is actually appearing is from update-notifier, not /etc/network/if-up.d/avahi-daemon unfortunately its midnight I must goto bed I will continue to investigate this issue tomorrow -- Avahi behaves badly where there is a unicast .local-domain. https://launchpad.net/bugs/83468 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87003] NVIDIA 7600GT detected as vesa not nv
Public bug reported: Binary package hint: discover-data My NVIDIA 7600GTs are not detected as using the nv driver (which works fine) and uses vesa instead. FTR, I have 2 of these cards but it should still detect the primary :) ** Affects: discover-data (Ubuntu) Importance: Undecided Status: Unconfirmed -- NVIDIA 7600GT detected as vesa not nv https://launchpad.net/bugs/87003 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87003] Re: NVIDIA 7600GT detected as vesa not nv
** Attachment added: "lspci -vv output for video cards" http://librarian.launchpad.net/6496986/lspci-vv.txt -- NVIDIA 7600GT detected as vesa not nv https://launchpad.net/bugs/87003 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87207] libnss-mdns libraries should be /lib
Public bug reported: Binary package hint: libnss-mdns Quote from debian report #411978 "Hi, When /usr is not mounted and libnss-mdns is installed hostname lookups will fail because lib_mdns* is in /usr/lib instead of /lib. Apart from the more obvious things like nfs-mounting /usr, something like postfix can also fail as it just copies the nss modules from /lib into it's chroot.. Causing a broken setup for resolving, which in turn can cause mail bounces.. Sjoerd" We should either sync up or apply a similar patch ** Affects: nss-mdns (Ubuntu) Importance: High Status: Unconfirmed ** Affects: nss-mdns (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #411978 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411978 ** Also affects: nss-mdns (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411978 Importance: Unknown Status: Unknown ** Changed in: nss-mdns (Ubuntu) Importance: Undecided => High -- libnss-mdns libraries should be /lib https://launchpad.net/bugs/87207 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56426] Re: /etc/init.d/avahi-daemon is useless
It's actually nothing to do with being started by D-BUS It was simply decided by the developers to do it this way, because editing the RC symlinks was considered "wrong" I guess. I admit this was a bad way to do it, I was going to implement a patch to check how it was being started but I wasn't able to get it in time for edgy unfortunately. -- /etc/init.d/avahi-daemon is useless https://launchpad.net/bugs/56426 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72728] Re: Avahi possible regression in 0.6.10-0ubuntu3.2
** Bug watch added: Avahi #72 http://www.avahi.org/ticket/72 ** Also affects: avahi (upstream) via http://www.avahi.org/ticket/72 Importance: Unknown Status: Unknown -- Avahi possible regression in 0.6.10-0ubuntu3.2 https://launchpad.net/bugs/72728 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72728] Re: Avahi possible regression in 0.6.10-0ubuntu3.2
This is known upstream, see Avahi bug #72 (linked) I hope this will be fixed shortly. -- Avahi possible regression in 0.6.10-0ubuntu3.2 https://launchpad.net/bugs/72728 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
