[Bug 1095043] Re: package samba4 4.0.0~beta2+dfsg1-3 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1
*** This bug is a duplicate of bug 1048353 *** https://bugs.launchpad.net/bugs/1048353 ** This bug is no longer a duplicate of bug 1097765 package samba4 4.0.0~beta2+dfsg1-3 failed to install/upgrade -- "The name '...' is not a valid NetBIOS name" ** This bug has been marked a duplicate of bug 1048353 provision crashed with InvalidNetbiosName in guess_names(): The name ''LOGAN-VIRTUALBOX'' is not a valid NetBIOS name -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1095043 Title: package samba4 4.0.0~beta2+dfsg1-3 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1095043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091614] Re: package samba4 4.0.0~beta2+dfsg1-3 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
*** This bug is a duplicate of bug 1048353 *** https://bugs.launchpad.net/bugs/1048353 ** This bug is no longer a duplicate of bug 1097765 package samba4 4.0.0~beta2+dfsg1-3 failed to install/upgrade -- "The name '...' is not a valid NetBIOS name" ** This bug has been marked a duplicate of bug 1048353 provision crashed with InvalidNetbiosName in guess_names(): The name ''LOGAN-VIRTUALBOX'' is not a valid NetBIOS name -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091614 Title: package samba4 4.0.0~beta2+dfsg1-3 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1091614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1048353] Re: provision crashed with InvalidNetbiosName in guess_names(): The name ''...-...'' is not a valid NetBIOS name
** Summary changed: - provision crashed with InvalidNetbiosName in guess_names(): The name ''LOGAN-VIRTUALBOX'' is not a valid NetBIOS name + provision crashed with InvalidNetbiosName in guess_names(): The name ''...-...'' is not a valid NetBIOS name -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048353 Title: provision crashed with InvalidNetbiosName in guess_names(): The name ''...-...'' is not a valid NetBIOS name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1048353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096101] Re: package samba4 4.0.0+dfsg1-1 failed to install/upgrade: "samba4.postinst: samba-tool: not found"
Note: samba4 Depends on samba4-common-bin (which the submitter has installed) which contains /usr/bin/samba-tool. I notice that samba4.postinst runs samba-tool without a path and doesn't set PATH. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096101 Title: package samba4 4.0.0+dfsg1-1 failed to install/upgrade: "samba4.postinst: samba-tool: not found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1096101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098036] Re: samba_dnsupdate crashed with RuntimeError in get_credentials(): kinit for UBUNTUTEST$@LOCALDOMAIN failed (Cannot contact any KDC for requested realm)
*** This bug is a duplicate of bug 809638 *** https://bugs.launchpad.net/bugs/809638 ** This bug has been marked a duplicate of bug 809638 samba_dnsupdate crashed with RuntimeError in get_credentials(): kinit for INTEL$@REALM failed (Cannot contact any KDC for requested realm) ** Summary changed: - samba_dnsupdate crashed with RuntimeError in get_credentials(): kinit for UBUNTUTEST$@LOCALDOMAIN failed (Cannot contact any KDC for requested realm) + samba_dnsupdate crashed with RuntimeError in get_credentials(): kinit for ...$@LOCALDOMAIN failed (Cannot contact any KDC for requested realm) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1098036 Title: samba_dnsupdate crashed with RuntimeError in get_credentials(): kinit for ...$@LOCALDOMAIN failed (Cannot contact any KDC for requested realm) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1098036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049834] Re: samba_dnsupdate crashed with RuntimeError in get_credentials(): kinit for SHUTTLE$@LOCALDOMAIN failed (Cannot contact any KDC for requested realm)
*** This bug is a duplicate of bug 809638 *** https://bugs.launchpad.net/bugs/809638 ** This bug is no longer a duplicate of bug 1036820 samba_dnsupdate crashed with RuntimeError in get_credentials() ** This bug has been marked a duplicate of bug 809638 samba_dnsupdate crashed with RuntimeError in get_credentials(): kinit for INTEL$@REALM failed (Cannot contact any KDC for requested realm) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049834 Title: samba_dnsupdate crashed with RuntimeError in get_credentials(): kinit for SHUTTLE$@LOCALDOMAIN failed (Cannot contact any KDC for requested realm) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1049834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036820] Re: samba_dnsupdate crashed with RuntimeError in get_credentials()
*** This bug is a duplicate of bug 809638 *** https://bugs.launchpad.net/bugs/809638 ** This bug has been marked a duplicate of bug 809638 samba_dnsupdate crashed with RuntimeError in get_credentials(): kinit for INTEL$@REALM failed (Cannot contact any KDC for requested realm) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036820 Title: samba_dnsupdate crashed with RuntimeError in get_credentials() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1036820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 870299] Re: samba_dnsupdate crashed with IndexError in __init__(): list index out of range
Shall we just say that alpha is obsolete? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870299 Title: samba_dnsupdate crashed with IndexError in __init__(): list index out of range To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/870299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091348] Re: Error loading module '/usr/lib/x86_64-linux-gnu/samba//vfs/acl_xattr.so': /usr/lib/x86_64-linux-gnu/samba//vfs/acl_xattr.so: cannot open shared object file: No such file or directory
Does this still happen with 4.0.0+dfsg1-1? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091348 Title: Error loading module '/usr/lib/x86_64-linux- gnu/samba//vfs/acl_xattr.so': /usr/lib/x86_64-linux- gnu/samba//vfs/acl_xattr.so: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1091348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091348] Re: Error loading module '/usr/lib/x86_64-linux-gnu/samba//vfs/acl_xattr.so': /usr/lib/x86_64-linux-gnu/samba//vfs/acl_xattr.so: cannot open shared object file: No such file or directory
Duh, it was reported against 4.0.0+dfsg1-1! Where is my brain? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091348 Title: Error loading module '/usr/lib/x86_64-linux- gnu/samba//vfs/acl_xattr.so': /usr/lib/x86_64-linux- gnu/samba//vfs/acl_xattr.so: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1091348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098152] Re: DNS resolve failed after upgrade from 12.04 to 12.10
*** This bug is a duplicate of bug 933723 *** https://bugs.launchpad.net/bugs/933723 ** This bug has been marked a duplicate of bug 933723 bind9 registers itself with resolvconf even though it's unable to provide name service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1098152 Title: DNS resolve failed after upgrade from 12.04 to 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1098152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969916] Re: host crashed with SIGSEGV in start_thread() on login
Compare bug #113417. ** Summary changed: - host crashed with SIGSEGV in start_thread() + host crashed with SIGSEGV in start_thread() on login ** Summary changed: - host crashed with SIGSEGV in start_thread() on login + "host -t soa local." SIGSEGV in start_thread() on login -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969916 Title: "host -t soa local." SIGSEGV in start_thread() on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/969916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113417] Re: [apport] "host -t soa local" crashed after resume from suspend
** Summary changed: - [apport] host crashed with SIGSEGV + [apport] "host -t soa local" crashed after resume from suspend ** Summary changed: - [apport] "host -t soa local" crashed after resume from suspend + [apport] "host -t soa local" SIGSEGV after resume from suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/113417 Title: [apport] "host -t soa local" SIGSEGV after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/113417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091348] Re: Error loading module '/usr/lib/x86_64-linux-gnu/samba//vfs/acl_xattr.so': /usr/lib/x86_64-linux-gnu/samba//vfs/acl_xattr.so: cannot open shared object file: No such file or directory
Another log showing these messages: http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=697105 ** Bug watch added: Debian Bug tracker #697105 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697105 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091348 Title: Error loading module '/usr/lib/x86_64-linux- gnu/samba//vfs/acl_xattr.so': /usr/lib/x86_64-linux- gnu/samba//vfs/acl_xattr.so: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1091348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 827165] Re: provision crashed with LdbError in add_ldif(): (1, "../ldb_tdb/ldb_index.c:1189: Failed to re-index dnsRoot in CN=Enterprise Configuration, CN=Partitions, CN=Configuration, DC=BRODOCK
I think we can just say that alpha17 is obsolete. ** Changed in: samba4 (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/827165 Title: provision crashed with LdbError in add_ldif(): (1, "../ldb_tdb/ldb_index.c:1189: Failed to re-index dnsRoot in CN=Enterprise Configuration,CN=Partitions,CN=Configuration,DC=BRODOCK- DESKTOP - Failed to create index key for attribute 'dnsRoot':Unknown error") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/827165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889319] Re: popcon.ubuntu.com not updated in a month
It was last updated in December 2012. Surely it doesn't have to be updated daily? ** Changed in: popularity-contest (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889319 Title: popcon.ubuntu.com not updated in a month To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popularity-contest/+bug/889319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067277] Re: popcon.ubuntu.com: Ubuntu Popularity Contest statistics is out of date
It's now at December 2012. ** Changed in: popularity-contest (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067277 Title: popcon.ubuntu.com: Ubuntu Popularity Contest statistics is out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popularity-contest/+bug/1067277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999337] Re: resolvconf(8): misleading description of dns-* options
@Anthony: A "dns-options" option in /e/n/i is indeed not currently supported. Do you need this? The current practice is to put an "options" line in /etc/resolvconf/resolv.conf.d/base. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/999337 Title: resolvconf(8): misleading description of dns-* options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/999337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000244] Re: Symlink /etc/resolv.conf does not exist after installation or upgrade of resolvconf -- various causes
@a_paddy: Thanks. See comment #82 for the most recent summary of causes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000244 Title: Symlink /etc/resolv.conf does not exist after installation or upgrade of resolvconf -- various causes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
>there's still the unresolved question > of whether re-enabling --strict-order > will suffice as a workaround, since > 12.10 relies on DBus to populate the > nameservers. Is there any extra > information on this? Please try it and report back. :-) (Put "strict-order" in a file in /etc/NetworkManager/dnsmasq.d/; stop network-manager; make sure all dnsmasq processes are dead; start network-manager.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1114948] Re: unable to access server on lan by hostname on wi-fi
@Jeremy: Hi, and thanks for the report. Please provide more information by taking the following steps. * Reboot * Log in and open a terminal * In the terminal, run the following commands with the name of your server replacing 'XYZ'. ping XYZ host XYZ dig XYZ ls -l /etc/resolv.conf cat /etc/resolv.conf ls -l /run/resolvconf/interface for F in /run/resolvconf/interface/* ; do echo === $F === ; cat $F ; done apport-collect 1114948 * Post the resulting output here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1114948 Title: unable to access server on lan by hostname on wi-fi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1114948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
This may also help: http://www.thinkwiki.org/wiki/Installing_Ubuntu_11.04_(Natty_Narwhal)_on_a_ThinkPad_X220#Fix_for_hotkey_shortcomings -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/408903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
Simon in #49: > It doesn't work [...] the order of servers given to the DBus > interface isn't preserved internally Aha, so the answer to my question > Will switching on strict-order have the same effect > now that nameserver addresses are sent over D-Bus? (in comment #42) is "No". So switching strict-order back on is no solution. And solutions depending on strict-order including mine in #28 also won't work. Unless dnsmasq is somehow changed such that it remembers the order in which nameserver addresses come in over D-Bus so that strict-order is useful in the D-Bus case, if we want to avoid breaking name service on machines connected to NNNs then we have to disable dnsmasq by default; or disable it initially and only enable it when we know that we aren't on a NNN. (NNN = nonequivalent-nameserver network. As discussed in comment #5, such networks are not properly configured. But as observed several times, there are many NNNs out there. Which is why *many* people have been commenting out "dns=dnsmasq".) There is another problem with NM-dnsmasq (bug #1072899). Some VPNs have multiple nameservers. NM uses dnsmasq to direct VPN domain name queries to the *first* one. But then, if the first one goes down, the second one is not tried. Once again, for the sake of speed enhancement in the favorable case, users suffer radical name service failure in the unfavorable case. This is not a good deal, IMHO. NM-dnsmasq should be disabled by default until these problems are solved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1114948] Re: unable to access server on lan by hostname on wi-fi
@Jeremy: Is your problem bug #1083565? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1114948 Title: unable to access server on lan by hostname on wi-fi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1114948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1114948] Re: unable to access server on lan by hostname on wi-fi
Is you problem bug #80900. Does editing /etc/nsswitch.conf so that it contains hosts: files dns mdns fix it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1114948 Title: unable to access server on lan by hostname on wi-fi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1114948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1114948] Re: unable to access server on lan by hostname on wi-fi
Is your problem bug #80900? Does editing /etc/nsswitch.conf so that it contains hosts: files dns mdns fix it? ** Changed in: resolvconf (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1114948 Title: unable to access server on lan by hostname on wi-fi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1114948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1115419] Re: package samba4 4.0.0+dfsg1-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
*** This bug is a duplicate of bug 1094303 ***
https://bugs.launchpad.net/bugs/1094303
>From DpkgTerminalLog.txt:
Setting up samba4 (4.0.0+dfsg1-1) ...
ERROR(): Provision failed -
ProvisioningError: guess_names: Workgroup 'ONOS' in smb.conf must match chosen
domain 'WORKGROUP'! Please remove the /etc/samba/smb.conf file and let
provision generate it
File "/usr/lib/python2.7/dist-packages/samba/netcmd/domain.py", line 398, in
run
use_rfc2307=use_rfc2307, skip_sysvolacl=False)
File "/usr/lib/python2.7/dist-packages/samba/provision/__init__.py", line
1892, in provision
sitename=sitename, rootdn=rootdn)
File "/usr/lib/python2.7/dist-packages/samba/provision/__init__.py", line
548, in guess_names
raise ProvisioningError("guess_names: Workgroup '%s' in smb.conf must match
chosen domain '%s'! Please remove the %s file and let provision generate it" %
(lp.get("workgroup").upper(), domain, lp.configfile))
dpkg: error processing samba4 (--configure):
subprocess installed post-installation script returned error exit status 255
** This bug has been marked a duplicate of bug 1094303
package samba4 4.0.0~beta2+dfsg1-3 failed to install/upgrade:
"ProvisioningError: guess_names: Workgroup '...' in smb.conf must match chosen
domain 'WORKGROUP'!"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1115419
Title:
package samba4 4.0.0+dfsg1-1 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 255
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1115419/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096791] Re: failed to install/upgrade: "check_password_restrictions: the password does not meet the complexity criteria!"
** Summary changed: - package samba4 4.0.0+dfsg1-1 failed to install/upgrade: "check_password_restrictions: the password does not meet the complexity criteria!" + failed to install/upgrade: "check_password_restrictions: the password does not meet the complexity criteria!" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096791 Title: failed to install/upgrade: "check_password_restrictions: the password does not meet the complexity criteria!" To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1096791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096101] Re: failed to install/upgrade: "samba4.postinst: samba-tool: not found"
** Summary changed: - package samba4 4.0.0+dfsg1-1 failed to install/upgrade: "samba4.postinst: samba-tool: not found" + failed to install/upgrade: "samba4.postinst: samba-tool: not found" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096101 Title: failed to install/upgrade: "samba4.postinst: samba-tool: not found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1096101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094303] Re: failed to install/upgrade: "ProvisioningError: guess_names: Workgroup '...' in smb.conf must match chosen domain 'WORKGROUP'!"
** Summary changed: - package samba4 4.0.0~beta2+dfsg1-3 failed to install/upgrade: "ProvisioningError: guess_names: Workgroup '...' in smb.conf must match chosen domain 'WORKGROUP'!" + failed to install/upgrade: "ProvisioningError: guess_names: Workgroup '...' in smb.conf must match chosen domain 'WORKGROUP'!" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094303 Title: failed to install/upgrade: "ProvisioningError: guess_names: Workgroup '...' in smb.conf must match chosen domain 'WORKGROUP'!" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1094303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1114570] Re: DNS suddenly stops working despite adding 8.8.8.8 as an additional server
Try this. Edit the connection using the Connection Editor and set IPv4 Settings | Method to "Automatic (DHCP) addresses only" instead of "Automatic (DHCP)". Make sure 8.8.8.8 is still included in the "Additional DNS servers" field. Another thing to try is to disable the local forwarding nameserver. Edit /etc/NetworkManager/NetworkManager.conf, comment out "dns=dnsmasq" by putting a '#' at the beginning of the line, and restart network-manager. You'll need sudo to accomplish this. ** Description changed: I see this problem somewhere between once a week and once a day: DNS lookups suddenly stop working causing the browser to fail to load pages and time out. After the last time it happened, I figured "must be comcast's flaky DNS" so I added Google's DNS server 8.8.8.8 as an additional server via network-manager but it just happened again. Even while it was broken, I could still ping 8.8.8.8 so I'm not really sure what's going on. I had a look in resolv.conf but it seems to be the same whether it's - working or not. Wither way it only has 127.0.1.1 as the nameserver. I - was expecting to see the actual nameserver in there but I guess Ubuntu - is using some sort of local proxy DNS? Since I'm not sure how DNS works - anymore, I'm not sure if this is the right package to report against. - Please advise. + working or not. Either way it only has 127.0.1.1 as the nameserver + address. I was expecting to see the actual nameserver in there but I + guess Ubuntu is using some sort of local proxy DNS? Since I'm not sure + how DNS works anymore, I'm not sure if this is the right package to + report against. Please advise. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sun Feb 3 12:02:14 2013 IfupdownConfig: - auto lo - iface lo inet loopback + auto lo + iface lo inet loopback InstallationDate: Installed on 2012-09-26 (130 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2) IpRoute: - default via 192.168.0.1 dev wlan0 proto static - 169.254.0.0/16 dev wlan0 scope link metric 1000 - 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.102 metric 9 + default via 192.168.0.1 dev wlan0 proto static + 169.254.0.0/16 dev wlan0 scope link metric 1000 + 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.102 metric 9 MarkForUpload: True NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - WimaxEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: - NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH - Wired connection 1db3b0216-bf13-4ec6-a5a8-20ffef4c1b22 802-3-ethernet1359824609 Sat 02 Feb 2013 09:03:29 AM PSTyes no /org/freedesktop/NetworkManager/Settings/1 - PinotGrigio 72706fea-5902-4f1f-ad56-891711e12ae9 802-11-wireless 1359921642 Sun 03 Feb 2013 12:00:42 PM PSTyes no /org/freedesktop/NetworkManager/Settings/0 + NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH + Wired connection 1db3b0216-bf13-4ec6-a5a8-20ffef4c1b22 802-3-ethernet1359824609 Sat 02 Feb 2013 09:03:29 AM PSTyes no /org/freedesktop/NetworkManager/Settings/1 + PinotGrigio 72706fea-5902-4f1f-ad56-891711e12ae9 802-11-wireless 1359921642 Sun 03 Feb 2013 12:00:42 PM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: - DEVICE TYPE STATE DBUS-PATH - wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 - eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 + DEVICE TYPE STATE DBUS-PATH + wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 + eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: - RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN - running 0.9.
[Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon
Comment #50 described how Mac OS X 10.2 did it. Here is how Mac OS X v10.[456] does it. (http://support.apple.com/kb/HT3473). "As long as your network's DNS server is properly configured, you do not have to make any changes on your client Mac. Host names that contain only one label in addition to local, for example "My-Computer.local", are resolved using Multicast DNS (Bonjour) by default. Host names that contain two or more labels in addition to local, for example "server.domain.local", are resolved using a DNS server by default. Additionally, Mac OS X v10.6 automatically detects when the local network operator has set up a name server that will answer name requests for a domain ending in ".local". It does this by checking to see if there is a Start Of Authority (SOA) record for the top level domain "local", which is how a DNS server indicates that it claims to have authority over a part of the DNS namespace. As long as the DNS server is properly configured with the required SOA record, Mac OS X v10.6 will detect this SOA record and automatically use this server to look up all host names in the domain." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/327362 Title: Some ISPs have .local domain which disables avahi-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon
Comment #50 described how Mac OS X 10.2 did it. Here is how Mac OS X v10.6 does it (http://support.apple.com/kb/HT3473). "As long as your network's DNS server is properly configured, you do not have to make any changes on your client Mac. Host names that contain only one label in addition to local, for example "My-Computer.local", are resolved using Multicast DNS (Bonjour) by default. Host names that contain two or more labels in addition to local, for example "server.domain.local", are resolved using a DNS server by default. Additionally, Mac OS X v10.6 automatically detects when the local network operator has set up a name server that will answer name requests for a domain ending in ".local". It does this by checking to see if there is a Start Of Authority (SOA) record for the top level domain "local", which is how a DNS server indicates that it claims to have authority over a part of the DNS namespace. As long as the DNS server is properly configured with the required SOA record, Mac OS X v10.6 will detect this SOA record and automatically use this server to look up all host names in the domain." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/327362 Title: Some ISPs have .local domain which disables avahi-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/327362/+subscriptions -- 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 in environments where .local is used as a TLD
Will wrote: > hosts: files dns mdns4_minimal [NOTFOUND=return] mdns4 I don't see the point of putting "mdns4_minimal" before "mdns4". Just "mdns4" should be equivalent and faster, but maybe I'm missing something. Jeremy wrote: > The nsswitch.conf edit fixed it for me. > Can we please get this as default configuration? 1. Jeremy, does the following also work? hosts: files mdns4_minimal dns mdns4 (I.e., *without* the "[NOTFOUND=return]".) 2. Upstream's documentation http://avahi.org/wiki/AvahiAndUnicastDotLocal says If you come across a network where .local is a unicast DNS domain, please contact the local administrator and ask him to move his DNS zone to a different domain. If this is not possible, we recommend not to use Avahi in such a network at all. So editing nsswitch.conf is not the recommended solution. Removing avahi is the recommended solution. Obviously we shouldn't require the user to do this by hand. Avahi should be disabled automatically on such a network. Now, apparently avahi tries to do this (if AVAHI_DAEMON_DETECT_LOCAL=1 in /etc/default/avahi-daemon) but this doesn't always work properly; see, e.g., bug #327362. Here's what Mac OS X 10.6 does (http://support.apple.com/kb/HT3473). (Bonjour plays the same role as avahi.) «Host names that contain only one label in addition to local, for example "My-Computer.local", are resolved using Multicast DNS (Bonjour) by default. Host names that contain two or more labels in addition to local, for example "server.domain.local", are resolved using a DNS server by default. Additionally, Mac OS X v10.6 automatically detects when the local network operator has set up a name server that will answer name requests for a domain ending in ".local". It does this by checking to see if there is a Start Of Authority (SOA) record for the top level domain "local", which is how a DNS server indicates that it claims to have authority over a part of the DNS namespace. As long as the DNS server is properly configured with the required SOA record, Mac OS X v10.6 will detect this SOA record and automatically use this server to look up all host names in the domain.» -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/80900 Title: problems resolving fully qualified domain names in environments where .local is used as a TLD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/80900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1110331] Re: nscd no longer needs to be restarted by libc's resolvconf update script
** Summary changed: - Eliminate nscd restart from update script? + nscd no longer needs to be restarted by libc's resolvconf update script -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1110331 Title: nscd no longer needs to be restarted by libc's resolvconf update script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1110331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1035098] Re: Please also truncate nameserver list after a loopback address in resolv.conf.d/head
** Summary changed: - Also truncate nameserver list after a loopback address in resolv.conf.d/head + Please also truncate nameserver list after a loopback address in resolv.conf.d/head -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1035098 Title: Please also truncate nameserver list after a loopback address in resolv.conf.d/head To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1035098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1114600] Re: wifi network named as number not found
** Description changed: - After Upgrading from 11.04 to 12.10 the wifi Network named "300" isn't - available anymore in networkmanager. + After upgrading from 11.04 to 12.10 the Wi-Fi network named "300" isn't + available any more in NetworkManager. ** Summary changed: - wifi network named as number not found + Wi-Fi network with numerical name not available -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1114600 Title: Wi-Fi network with numerical name not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1114600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1115061] Re: [quantal] modem-manager doesn't handle usb modem
What is the exact model number of your device? Googling for your USB device IDs I found, e.g., this: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=155. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1115061 Title: [quantal] modem-manager doesn't handle usb modem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1115061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1114107] Re: Please backport ability to customize NM-dnsmasq to 12.04
** Summary changed: - No way to customize built-in dnsmasq configuration in 12.04 + Please backport ability to customize NM-dnsmasq to 12.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1114107 Title: Please backport ability to customize NM-dnsmasq to 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1114107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1113703] Re: Trying to connect using a GSM modem without SIM card is not reported to user
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
** Description changed:
- Trying to connect using a GSM modem that lacks a SIM card does just give
- the user a general connection failure message without any hints about
- the missing SIM card.
-
- This can fool the user into thinking something other is wrong than the
- fact that he forgot to insert the SIM card, or inserted it improperly.
+ When the user tries to connect using a GSM modem that lacks a SIM card,
+ NM just gives the user a general connection failure message; it does not
+ give any hint about the missing SIM card. This can fool the user into
+ thinking something other is wrong than the fact that he forgot to insert
+ the SIM card, or inserted it improperly.
Latest modemmanager master branch gives in log:
Feb 2 20:21:24 marius-T1005 ModemManager[1105]: Modem couldn't
be initialized: Couldn't check unlock status: SIM failure
but there is no indication to the user (nm-applet behaves as if mobile
broadband is unavailable).
Seems I get (from "src/mm-error-helpers.c"):
{ MM_MOBILE_EQUIPMENT_ERROR_SIM_FAILURE,
"simfailure","SIM failure" },
but should have got:
{ MM_MOBILE_EQUIPMENT_ERROR_SIM_NOT_INSERTED,
"simnotinserted","SIM not inserted" }
Anyway (any of them should be enough hint to the user), it seems like
the error state is not propagated (src/mm-broadband-modem.c):
static void
iface_modem_initialize_ready (MMBroadbandModem *self,
GAsyncResult *result,
InitializeContext *ctx)
{
GError *error = NULL;
/* If the modem interface fails to get initialized, we will move the modem
* to a FAILED state. Note that in this case we still export the
interface. */
if (!mm_iface_modem_initialize_finish (MM_IFACE_MODEM (self), result,
&error)) {
/* Report the new FAILED state */
mm_warn ("Modem couldn't be initialized: %s", error->message);
g_error_free (error);
mm_iface_modem_update_state (MM_IFACE_MODEM (self),
MM_MODEM_STATE_FAILED,
MM_MODEM_STATE_CHANGE_REASON_UNKNOWN);
/* Jump to the firmware step. We allow firmware switching even in
failed
* state */
ctx->step = INITIALIZE_STEP_IFACE_FIRMWARE;
initialize_step (ctx);
return;
}
Network Manager logs:
20:21:24 marius-T1005 NetworkManager[1128]: (ttyUSB2): unusable
modem detected
** Changed in: networkmanagement (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/1113703
Title:
Trying to connect using a GSM modem without SIM card is not reported
to user
To manage notifications about this bug go to:
https://bugs.launchpad.net/modemmanager/+bug/1113703/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1102317] Re: Unable to disable networking/wireless through network indicator
Could bug #1102092 be related? ** Package changed: network-manager (Ubuntu) => network-manager-applet (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1102317 Title: Unable to disable networking/wireless through network indicator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1102317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1101534] Re: Cannot connect to WiFi network
>From WifiSyslog.txt (eth1 is the Wi-Fi interface): Jan 31 19:50:37 samsung wpa_supplicant[1307]: eth1: Trying to associate with 2e:c7:9f:d6:30:40 (SSID='[...]' freq=2412 MHz) Jan 31 19:50:37 samsung wpa_supplicant[1307]: eth1: Association request to the driver failed Jan 31 19:50:37 samsung NetworkManager[1159]: (eth1): supplicant interface state: scanning -> associating Jan 31 19:50:42 samsung wpa_supplicant[1307]: eth1: Authentication with 2e:c7:9f:d6:30:40 timed out. Jan 31 19:50:42 samsung NetworkManager[1159]: (eth1): supplicant interface state: associating -> disconnected ** Summary changed: - Cannot connect to WiFi network + Cannot connect to WiFi network -- Broadcom BCM4313 wl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101534 Title: Cannot connect to WiFi network -- Broadcom BCM4313 wl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1101534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1101534] Re: Cannot connect to WiFi network -- Broadcom BCM4313 wl
Possible wl driver problem ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101534 Title: Cannot connect to WiFi network -- Broadcom BCM4313 wl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1101534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099696] Re: Can't reconnect 3G HSPA after disconnect ; log out and in fixes it
What is the exact model name of your dongle. Please reboot, reproduce the failure, connect and then run "apport- collect 1099696" in a terminal to provide more information. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099696 Title: Can't reconnect 3G HSPA after disconnect ; log out and in fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1099696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1093622] Re: NM doesn't react to disconnect and connect commands for WiFi networks for very long time (or ever) -- Ralink rt2800usb
Am I correct in understanding that the Wi-Fi device in question is a Ralink and the driver is rt2800usb? ** Summary changed: - NM doesn't react to disconnect and connect commands for WiFi networks for very long time (or ever) + NM doesn't react to disconnect and connect commands for WiFi networks for very long time (or ever) -- Ralink rt2800usb ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1093622 Title: NM doesn't react to disconnect and connect commands for WiFi networks for very long time (or ever) -- Ralink rt2800usb To manage notifications about this bug go to: https://bugs.launchpad.net/ac100/+bug/1093622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1116310] [NEW] "Trying to overwrite shared changelog.Debian.gz"
Public bug reported: # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: libtasn1-3 libtasn1-3:i386 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/88.2 kB of archives. After this operation, 1,024 B disk space will be freed. Do you want to continue [Y/n]? (Reading database ... 278803 files and directories currently installed.) Preparing to replace libtasn1-3:amd64 2.14-2 (using .../libtasn1-3_2.14-2_amd64.deb) ... Unpacking replacement libtasn1-3:amd64 ... dpkg: error processing /var/cache/apt/archives/libtasn1-3_2.14-2_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libtasn1-3/changelog.Debian.gz', which is different from other instances of package libtasn1-3:amd64 Preparing to replace libtasn1-3:i386 2.14-2 (using .../libtasn1-3_2.14-2_i386.deb) ... Unpacking replacement libtasn1-3:i386 ... dpkg: error processing /var/cache/apt/archives/libtasn1-3_2.14-2_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libtasn1-3/changelog.Debian.gz', which is different from other instances of package libtasn1-3:i386 Errors were encountered while processing: /var/cache/apt/archives/libtasn1-3_2.14-2_amd64.deb /var/cache/apt/archives/libtasn1-3_2.14-2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: libtasn1-3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1116310 Title: "Trying to overwrite shared changelog.Debian.gz" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtasn1-3/+bug/1116310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1116310] Re: "Trying to overwrite shared changelog.Debian.gz"
# apt-cache madison libtasn1-3 libtasn1-3:i386 | grep 2.14 libtasn1-3 | 2.14-2 | http://nl.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages libtasn1-3 | 2.14-2 | http://nl.archive.ubuntu.com/ubuntu/ raring/main Sources libtasn1-3:i386 | 2.14-2 | http://nl.archive.ubuntu.com/ubuntu/ raring/main i386 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1116310 Title: "Trying to overwrite shared changelog.Debian.gz" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtasn1-3/+bug/1116310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990049] Re: no network interfaces
Can you reproduce this bug in the 4.0.0+dfsg1-1 version of the Samba 4 package? ** Changed in: samba4 (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990049 Title: no network interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/990049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990049] Re: no network interfaces
>From DpkgTerminalLog: Looking up IPv4 addresses ERROR: Could not determine network interfaces, you must use a interfaces config line WARNING: no network interfaces found talloc: access after free error - first free may be at °- Bad talloc magic value - access after free Aborted dpkg: error processing samba4 (--configure): subprocess installed post-installation script returned error exit status 134 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990049 Title: no network interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/990049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1114600] Re: Wi-Fi network with numerical name not available
Please reboot and then run "apport-collect 1114600" to provide more information about the affected system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1114600 Title: Wi-Fi network with numerical name not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1114600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1103809] Re: nm-applet stops accepting keyboard input
** Changed in: network-manager-applet (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1103809 Title: nm-applet stops accepting keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1103809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1099633] Re: network manager static ip gui bug
I can reproduce this. ** Changed in: network-manager-applet (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1099633 Title: network manager static ip gui bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1099633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1116363] Re: When joining a client to AD the error message "network path not found" appears
** Description changed: What I did: 01. apt-get install samba4 02. /etc/init.d/samba4 stop 03. rm /etc/samba/smb.conf 04. samba-tool domain provision --realm s4test.* --domain S4 --adminpass * --server-role=dc 05. /etc/bind9 stop 06. apt-get remove bind9 07. /etc/init.d/samba4 start 08. try to join Win7 client to domain After a while the error message "Network path not found" appears. Googling for this specifig error brought me to this posting of Andrew Bartlett: https://lists.samba.org/archive/samba/2012-August/168892.html Her he suggests to add the following lines to the global section of the smb.conf server services = +smb -s3fs dcerpc endpoint servers = +winreg +srvsvc And after adding these lines I can join a client to the domain. - So either add s3fs to the samba4 package or add these lines to the - smb.conf generated by samba-tool. + So please either add s3fs to the samba4 package or add these lines to + the smb.conf generated by samba-tool. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: samba4 4.0.0+dfsg1-1 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Tue Feb 5 16:23:21 2013 InstallationDate: Installed on 2013-02-05 (0 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Alpha amd64 (20130205) MarkForUpload: True ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: samba4 UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - When joining a client to AD the error message "network path not found" appears + "network path not found" on joining a client to AD; +smb -s3fs fixes it; please automate this ** Summary changed: - "network path not found" on joining a client to AD; +smb -s3fs fixes it; please automate this + "network path not found" on joining a client to AD; "+smb -s3fs" fixes it; please automate this -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1116363 Title: "network path not found" on joining a client to AD; "+smb -s3fs" fixes it; please automate this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1116363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000244] Re: Symlink /etc/resolv.conf does not exist after installation or upgrade of resolvconf -- various causes
** Changed in: resolvconf (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/1000244 Title: Symlink /etc/resolv.conf does not exist after installation or upgrade of resolvconf -- various causes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
Hi Simon. Before I forget to ask: can you please update dnsmasq(8) to include under "--strict-order" a description of what happens when nameserver addresses are passed in via D-Bus instead of via a file? You wrote, > you can very easily provide the same behaviour - only pass the first > nameserver to dnsmasq Because NM doesn't use dnsmasq to cache, if NM were to give dnsmasq only one address then I guess the only service that dnsmasq would still provide is that of name-to-server mapping. And it turns out that the way NM currently uses dnsmasq to do this is seriously flawed. So I conclude that it's better for NM not to use dnsmasq at all until these problems are solved. > [That NM only supplies one nameserver address per domain name] > is a different problem, and could be solved. >From the man page it's not completely clear how to solve it. Can you confirm (1) that it's possible to give multiple server options as follows server=/google.com/1.2.3.4 server=/google.com/5.6.7.8 and that the result will be that 1.2.3.4 and 5.6.7.8 will be treated equally for the purpose of resolving names in domain google.com? (2) And likewise via D-Bus? (3) What effect does strict-order have on this? > Ironically, I think the > problem arises because for nameservers associated with particular > domains, the equivalent of --strict-order is always in play. What you say here suggests that my proposition #1 above is false. If #1 is false then it seems that in order to fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
[...cont'd after "in order to fix"...] bug #1072899, dnsmasq will have to be enhanced such that proposition #1 is true. But we can discuss the details of that in bug #1072899. There is a close analogy between the problem here (bug #1003842) and a problem we have with avahi. Avahi resolves names in the domain ".local". Networks should not use this TLD, but many do and at least in the past Microsoft actually recommended doing so. When users connect to such networks with avahi enabled the result is malfunction. Upstream purisitically says[*] "If you come across a network where .local is a unicast DNS domain, please contact the local administrator and ask him to move his DNS zone to a different domain. If this is not possible, we recommend not to use Avahi in such a network at all." In practice avahi attempts to detect "bad" networks and disables itself if it thinks it is on a bad network, subject unfortunately both to false positives (bug #327362) and false negatives (bug #80900). We aren't yet doing even that well. We say that networks ought to have equivalent nameservers and we make no attempt to detect networks that have non-equivalent nameservers, of which there are very many. [*]http://avahi.org/wiki/AvahiAndUnicastDotLocal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1110331] Re: nscd no longer needs to be restarted by libc's resolvconf update script
Actually the change will appear in 1.70. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1110331 Title: nscd no longer needs to be restarted by libc's resolvconf update script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1110331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1116310] Re: "Trying to overwrite shared changelog.Debian.gz"
I was able to work around this by doing dpkg --remove --force-all libtasn1 libtasn1-3:i386 apt-get install libtasn1 libtasn1-3:i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1116310 Title: "Trying to overwrite shared changelog.Debian.gz" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtasn1-3/+bug/1116310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1116310] Re: "Trying to overwrite shared changelog.Debian.gz"
It is possible that I had one of those packages installed from Debian Experimental already. I notice that the Raring packages are not identical to the ones in Experimental, even though they have no Ubuntu version suffix. The difference in size is a surprising. >From http://packages.debian.org/experimental/amd64/libtasn1-3/download : More information on libtasn1-3_2.14-2_amd64.deb: Exact Size 68308 Byte (66.7 kByte) MD5 checksum49532105310e0bf84180de01055ac225 SHA1 checksum 089200efaad605b396159e5943832e6f6a69469a SHA256 checksum 958e16b5c72b29c061368bf0d2227f532e5c37ed9b9cdcac494860030ecf7009 >From http://packages.ubuntu.com/raring/amd64/libtasn1-3/download : More information on libtasn1-3_2.14-2_amd64.deb: Exact Size 43872 Byte (42.8 kByte) MD5 checksum8cbf858f6480230d783553fd245d3b23 SHA1 checksum bf45103f8926b0594da5b53b92c4bab64fad16c7 SHA256 checksum 160d4c913dbd81a9fd0f32460fe165f3541f83056378fa756689428e6ebdebec ** Summary changed: - "Trying to overwrite shared changelog.Debian.gz" + Error "trying to overwrite shared changelog.Debian.gz which is different from other instances of package libtasn1-3:amd64" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1116310 Title: Error "trying to overwrite shared changelog.Debian.gz which is different from other instances of package libtasn1-3:amd64" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtasn1-3/+bug/1116310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
Simon wrote: > Consider [...] > server=/google.com/3.3.3.3 > server=/google.com/4.4.4.4 [...] > Queries sent to *google.com will be sent 3.3.3.3 or 4.4.4.4 in the > same way as if strict order was set, ie, to 3.3.3.3 first, and only to > 4.4.4.4 if 3.3.3.3 returns a SERVFAIL or REFUSED error, or doesn't > reply at all. > > This should be changed, but the code which implements it is knarly > and old, and won't stand more tinkering, it needs rewriting. I've > not found the time, as of yet. That doesn't sound as if it's urgently needed for anything we are talking about here. What we do need is for strict-order to work when addresses are provided over D-Bus. (That this requires work: see #49. That this is needed: see below.) >> We say that networks ought to >> have equivalent nameservers and we make no attempt to detect networks >> that have non-equivalent nameservers, of which there are very many. > > Detect non-equivalent servers is hard. I'm very much in favour of > doing it, if a way can be found. Well, let's look at the ideas that have been put forward so far. Solution #1. Disable NM-dnsmasq by default. This is the only solution we have right now. Other ideas that probably need more thought... Solution #2. Enhance dnsmasq such that it can be given an ordered list of nameservers via D-Bus and can process this list in strict-order fashion. Then do every lookup in strict-order fashion, but detect offline nameservers and omit them temporarily from the list. (This is my interpretation of Stéphane's suggestion in #37.) Solution #3. Enhance dnsmasq such that it can be given an ordered list of nameservers via D-Bus and can process this list in strict-order fashion. Then do a given lookup in strict-order fashion if * the lookup is being routed to a specific nameserver due to a "server" option; * the name is in one of the search domains returned by DHCP (as suggested my M T-L in #34); * the name is not in any of the recognized TLDs; or * we have detected nameserver nonequivalence since the last time the list of nameservers changed. The detection mechanism is as described in #28: on encountering NODATA or NXDOMAIN, dnsmasq returns the negative result immediately but also reiterates the query to all nameservers listed earlier than the one that answered. If one of those nameservers later returns an address then nameserver nonequivalence has been detected. (This combines several earlier suggestions.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
Earlier there was some dispute about what the RFCs say about multiple nameservers. I found the following RFC which does have something to say about these issues. http://www.zoneedit.com/doc/rfc/rfc2182.txt Here are a couple of passages... Request for Comments: 2182 Category: Best Current Practice Selection and Operation of Secondary DNS Servers Abstract The Domain Name System requires that multiple servers exist for every delegated domain (zone). This document discusses the selection of secondary servers for DNS zones. Both the physical and topological location of each server are material considerations when selecting secondary servers. The number of servers appropriate for a zone is also discussed, and some general secondary server maintenance issues considered. [...] With multiple servers, usually one server will be the primary server, and others will be secondary servers. Note that while some unusual configurations use multiple primary servers, that can result in data inconsistencies, and is not advisable. The distinction between primary and secondary servers is relevant only to the servers for the zone concerned, to the rest of the DNS there are simply multiple servers. All are treated equally at first instance, even by the parent server that delegates the zone. Resolvers often measure the performance of the various servers, choose the "best", for some definition of best, and prefer that one for most queries. That is automatic, and not considered here. [...] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
The target milestone should be adjusted, I guess. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1116363] Re: "network path not found" on joining a client to AD; "+smb -s3fs; +winreg +srvsvc" fixes it; please automate this
** Summary changed: - "network path not found" on joining a client to AD; "+smb -s3fs" fixes it; please automate this + "network path not found" on joining a client to AD; "+smb -s3fs; +winreg +srvsvc" fixes it; please automate this -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1116363 Title: "network path not found" on joining a client to AD; "+smb -s3fs; +winreg +srvsvc" fixes it; please automate this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1116363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1120228] Re: DNS can't be resolved anymore
"My system doesn't work today" is not a bug report. ** Changed in: resolvconf (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/1120228 Title: DNS can't be resolved anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1120228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1110331] Re: nscd no longer needs to be restarted by libc's resolvconf update script
Done in recently released Debian resolvconf 1.70. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1110331 Title: nscd no longer needs to be restarted by libc's resolvconf update script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1110331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094345] Re: IPv6 DHCP record too late, and other irregularities, in resolvconf interface-order
Done in recently released Debian resolvconf 1.70. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094345 Title: IPv6 DHCP record too late, and other irregularities, in resolvconf interface-order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1094345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1110331] Re: nscd no longer needs to be restarted by libc's resolvconf update script
I have been testing nscd for a while and have discovered, alas, that although nscd notices when resolv.conf changes — e.g., when it needs to do a DNS query it uses the correct nameserver address — it does *not* invalidate its hosts cache when resolv.conf changes. This causes problems when connecting to VPNs whose nameservers give different results from those given by external nameservers. I filed a bug report against nscd in the Debian BTS: bugs.debian.org/700385. The executive summary is: * Nscd doesn't invalidate its hosts cache on resolv.conf changes; * if nscd is supposed to do so then, then please fix the bug; * otherwise please include a resolvconf update script in nscd which invalidates nscd's hosts cache. I wonder if resolvconf should do the nscd hosts cache invalidation itself, using "nscd --invalidate hosts". But considering * nscd is only in universe; * nscd's hosts cache is disabled by default; and * nscd — either the binary or the package — should be responsible for handling resolv.conf changes, not resolvconf, I am reluctant to do so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1110331 Title: nscd no longer needs to be restarted by libc's resolvconf update script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1110331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085849] Re: Please don't change the answer to linkify-resolvconf
Or: * Create a flag file that records the fact that we have created the symlink; * don't create the symlink again if the flag file exists; * delete the flag file on reconfigure or remove. Any objections? If not then I will implement it this way in Debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085849 Title: Please don't change the answer to linkify-resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1085849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085849] Re: Please don't change the answer to linkify-resolvconf
Something like the following. Then Ubuntu just has to uncomment the indicated line and comment the line before it. diff --git a/debian/postinst b/debian/postinst index 2b4faf7..3822ece 100755 --- a/debian/postinst +++ b/debian/postinst @@ -113,9 +113,13 @@ case "$1" in fi # Linkify /etc/resolv.conf if appropriate + if [ "$DEBCONF_RECONFIGURE" = 1 ] || [ "$1" = reconfigure ] ; then + rm -f /etc/resolvconf/already-linkified-resolvconf + fi db_get resolvconf/linkify-resolvconf if [ "$RET" = "true" ] +#Ubuntu: [ "$RET" = "true" ] && [ ! -e /etc/resolvconf/already-linkified-resolvconf ] then if is_immutable_file /etc/resolv.conf ; then report_err "Cannot replace the current /etc/resolv.conf with a symbolic link because it is immutable; to correct this problem, gain root privileges in a terminal and run 'chattr @@ -148,6 +152,19 @@ case "$1" in fi # Create the link ln -nsf /etc/resolvconf/run/resolv.conf /etc/resolv.conf + # Make a record that we have created it + echo "This is a flag file whose presence indicates that +the resolvconf package has already created a symbolic link +at /etc/resolv.conf and should not do so again. + +If you remove this file then the resolvconf package will +create the symbolic link again the next time the package +is upgraded, provided of course the linkify-resolvconf +debconf question has an affirmative answer. + +If the administrator runs 'dpkg-reconfigure resolvconf' +then this file is deleted so that the package can make +another attempt to create the symbolic link." > /etc/resolvconf/already-linkified-resolvconf fi fi ;; -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085849 Title: Please don't change the answer to linkify-resolvconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1085849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123424] [NEW] nscd: Either fix automatic hosts cache invalidation or add resolvconf update script to invalidate the hosts cache
Public bug reported:
When nscd is running and the hosts cache is enabled and resolv.conf
changes, the hosts cache needs to be invalidated, but this does not
currently happen.
I discovered this while running nscd with the hosts cache enabled. I
connected to a VPN whose internal nameservers resolve certain domain
names differently from external nameservers: for a given name, external
nameservers resolve the name to the IP address of the company's reverse
proxy whereas the internal nameservers resolve the name to an internal
IP address. After I connected to the VPN my resolv.conf file was
correctly updated by resolvconf such that the VPN nameserver was listed
first, but nscd continued to supply the old external IP address out of
its cache. Analogous problem on disconnecting from the VPN. (When
resolvconf is installed it updates the resolver configuration file
resolv.conf. It actually writes to /run/resolvconf/resolv.conf to which
/etc/resolv.conf is a symbolic link.)
I would have expected that nscd would invalidate its hosts cache
automatically when resolv.conf changed. I initially thought that this
was the point of the patch discussed here:
http://www.eglibc.org/archives/patches/msg00977.html
which I believe has since been integrated into Ubuntu nscd. But
experimentation proves that nscd does *not* invalid its hosts cache when
resolv.conf changes... at least, not under the circumstances described
above.
Now I understand that when resolv.conf changes, nscd does re-read the
resolv.conf file and so does use the correct nameservers for new
queries, but does not clear its cache.
If nscd is supposed to invalidate its hosts cache when resolv.conf
changes then please fix the bug which causes this to fail to happen.
If it was not the intent to include that functionality in nscd, then
please add a resolvconf update script that invalidates the hosts cache
when resolv.conf is changed by resolvconf.
This can be implemented in two parts. First, add a new "invalidate-
hosts" method to the initscript which invalidates the hosts cache,
making use of nscd's "--invalidate" option. Then include a file named
/etc/resolvconf/update-libc.d/000nscd in the nscd package with the
following content.
#!/bin/sh
[ -x /etc/init.d/nscd ] && /etc/init.d/nscd invalidate-hosts
The code in the initscript could look something like the following.
--- nscd_ORIG 2012-10-04 04:13:52.0 +0200
+++ nscd2013-02-12 21:00:33.191132785 +0100
@@ -70,6 +70,11 @@
return 0
}
+invalidate_hosts()
+{
+ "$DAEMON" --invalidate hosts
+}
+
case "$1" in
start)
log_daemon_msg "Starting $DESC" "$NAME"
@@ -118,8 +123,16 @@
1) log_success_msg "running." ; exit 0 ;;
esac
;;
+invalidate-hosts)
+ log_daemon_msg "Invalidating hosts cache of $DESC"
+ status || invalidate_hosts
+ case "$?" in
+ 0) log_end_msg 0 ; exit 0 ;;
+ *) log_failure_msg " (failed)" ; exit 1 ;;
+ esac
+ ;;
*)
- echo "Usage: /etc/init.d/$NAME
{start|stop|force-reload|restart|status}" >&2
+ echo "Usage: /etc/init.d/$NAME
{start|stop|force-reload|restart|status|invalidate-hosts}" >&2
exit 1
;;
esac
Should you implement this, please Suggest resolvconf (>= 1.70) and Conflict
with resolvconf (<< 1.70), since those older versions of resolvconf restarted
nscd if resolv.conf changed and nscd had its hosts cache enabled.
--
Thomas Hood
** Affects: eglibc (Ubuntu)
Importance: Undecided
Status: New
** Tags: dns nscd patch resolvconf vpn
** Patch added: "nscd initscript patch to add "invalidate-hosts" method"
https://bugs.launchpad.net/bugs/1123424/+attachment/3525726/+files/nscd_initscript_invalidate_hosts.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1123424
Title:
nscd: Either fix automatic hosts cache invalidation or add resolvconf
update script to invalidate the hosts cache
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1123424/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123425] [NEW] nscd: Either fix automatic hosts cache invalidation or add resolvconf update script to invalidate the hosts cache
Public bug reported:
When nscd is running and the hosts cache is enabled and resolv.conf
changes, the hosts cache needs to be invalidated, but this does not
currently happen.
I discovered this while running nscd with the hosts cache enabled. I
connected to a VPN whose internal nameservers resolve certain domain
names differently from external nameservers: for a given name, external
nameservers resolve the name to the IP address of the company's reverse
proxy whereas the internal nameservers resolve the name to an internal
IP address. After I connected to the VPN my resolv.conf file was
correctly updated by resolvconf such that the VPN nameserver was listed
first, but nscd continued to supply the old external IP address out of
its cache. Analogous problem on disconnecting from the VPN. (When
resolvconf is installed it updates the resolver configuration file
resolv.conf. It actually writes to /run/resolvconf/resolv.conf to which
/etc/resolv.conf is a symbolic link.)
I would have expected that nscd would invalidate its hosts cache
automatically when resolv.conf changed. I initially thought that this
was the point of the patch discussed here:
http://www.eglibc.org/archives/patches/msg00977.html
which I believe has since been integrated into Ubuntu nscd. But
experimentation proves that nscd does *not* invalid its hosts cache when
resolv.conf changes... at least, not under the circumstances described
above.
Now I understand that when resolv.conf changes, nscd does re-read the
resolv.conf file and so does use the correct nameservers for new
queries, but does not clear its cache.
If nscd is supposed to invalidate its hosts cache when resolv.conf
changes then please fix the bug which causes this to fail to happen.
If it was not the intent to include that functionality in nscd, then
please add a resolvconf update script that invalidates the hosts cache
when resolv.conf is changed by resolvconf.
This can be implemented in two parts. First, add a new "invalidate-
hosts" method to the initscript which invalidates the hosts cache,
making use of nscd's "--invalidate" option. Then include a file named
/etc/resolvconf/update-libc.d/000nscd in the nscd package with the
following content.
#!/bin/sh
[ -x /etc/init.d/nscd ] && /etc/init.d/nscd invalidate-hosts
The code in the initscript could look something like the following.
--- nscd_ORIG 2012-10-04 04:13:52.0 +0200
+++ nscd2013-02-12 21:00:33.191132785 +0100
@@ -70,6 +70,11 @@
return 0
}
+invalidate_hosts()
+{
+ "$DAEMON" --invalidate hosts
+}
+
case "$1" in
start)
log_daemon_msg "Starting $DESC" "$NAME"
@@ -118,8 +123,16 @@
1) log_success_msg "running." ; exit 0 ;;
esac
;;
+invalidate-hosts)
+ log_daemon_msg "Invalidating hosts cache of $DESC"
+ status || invalidate_hosts
+ case "$?" in
+ 0) log_end_msg 0 ; exit 0 ;;
+ *) log_failure_msg " (failed)" ; exit 1 ;;
+ esac
+ ;;
*)
- echo "Usage: /etc/init.d/$NAME
{start|stop|force-reload|restart|status}" >&2
+ echo "Usage: /etc/init.d/$NAME
{start|stop|force-reload|restart|status|invalidate-hosts}" >&2
exit 1
;;
esac
Should you implement this, please Suggest resolvconf (>= 1.70) and Conflict
with resolvconf (<< 1.70), since those older versions of resolvconf restarted
nscd if resolv.conf changed and nscd had its hosts cache enabled.
--
Thomas Hood
** Affects: eglibc (Ubuntu)
Importance: Undecided
Status: New
** Affects: eglibc (Debian)
Importance: Unknown
Status: Unknown
** Tags: dns nscd patch resolvconf vpn
** Patch added: "nscd initscript patch to add "invalidate-hosts" method"
https://bugs.launchpad.net/bugs/1123425/+attachment/3525727/+files/nscd_initscript_invalidate_hosts.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1123425
Title:
nscd: Either fix automatic hosts cache invalidation or add resolvconf
update script to invalidate the hosts cache
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1123425/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123425] Re: nscd: Either fix automatic hosts cache invalidation or add resolvconf update script to invalidate the hosts cache
*** This bug is a duplicate of bug 1123424 *** https://bugs.launchpad.net/bugs/1123424 ** Bug watch added: Debian Bug tracker #700385 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700385 ** Also affects: eglibc (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700385 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123425 Title: nscd: Either fix automatic hosts cache invalidation or add resolvconf update script to invalidate the hosts cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1123425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123425] Re: nscd: Either fix automatic hosts cache invalidation or add resolvconf update script to invalidate the hosts cache
*** This bug is a duplicate of bug 1123424 *** https://bugs.launchpad.net/bugs/1123424 ** This bug has been marked a duplicate of bug 1123424 nscd: Either fix automatic hosts cache invalidation or add resolvconf update script to invalidate the hosts cache -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123425 Title: nscd: Either fix automatic hosts cache invalidation or add resolvconf update script to invalidate the hosts cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1123425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123424] Re: nscd: Either fix automatic hosts cache invalidation or add resolvconf update script to invalidate the hosts cache
** Bug watch added: Debian Bug tracker #700385 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700385 ** Also affects: eglibc (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700385 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123424 Title: nscd: Either fix automatic hosts cache invalidation or add resolvconf update script to invalidate the hosts cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1123424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123829] Re: NM fails to recognize already configured Wi-Fi connection
** Summary changed: - problem in wifi network configuration + NM fails to recognize already configured Wi-Fi connection -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123829 Title: NM fails to recognize already configured Wi-Fi connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1123829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1123353] Re: problem in internet connection reliance netconnect
The Huawei EC1260 is not listed upstream as a supported model https://live.gnome.org/NetworkManager/MobileBroadband Nevertheless, I found a bug report in the upstream bugzilla related to this model. https://bugzilla.gnome.org/show_bug.cgi?id=663535 ** Bug watch added: GNOME Bug Tracker #663535 https://bugzilla.gnome.org/show_bug.cgi?id=663535 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1123353 Title: problem in internet connection reliance netconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1123353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1133108] Re: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: "samba4.postinst: /usr/share/samba/setoption.pl: Permission denied"
** Summary changed: - package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 126 + package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: "samba4.postinst: /usr/share/samba/setoption.pl: Permission denied" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133108 Title: package samba4 4.0.0~alpha18.dfsg1-4ubuntu2 failed to install/upgrade: "samba4.postinst: /usr/share/samba/setoption.pl: Permission denied" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1133108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000244] Re: Symlink /etc/resolv.conf does not exist after installation or upgrade of resolvconf -- various causes
@Cerin: Was your comment (#117) intended for this bug report? (This report is about the /etc/resolv.conf symlink sometimes being missing after installation of the resolvconf package, but your comment was about a difficulty switching between Wi-Fi networks.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000244 Title: Symlink /etc/resolv.conf does not exist after installation or upgrade of resolvconf -- various causes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366967] Re: ifupdown-udev integration should be thought-out more thoroghly
I am the author and maintainer of resolvconf in Debian. Unfortunately I don't know enough about upstart to maintain resolvconf for Ubuntu. In its current condition in Ubuntu (universe) the resolvconf package does not work properly. If no one is willing to maintain resolvconf in Ubuntu then it should be removed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/366967 Title: ifupdown-udev integration should be thought-out more thoroghly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/366967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878063] [NEW] Can't set memory maximum
Public bug reported: When I run memtest86+ on a ThinkPad X61 with 4 GiB memory, memtest reports failures at locations starting with "4096M". Makes sense, since there is no memory above 4096 MiB. Printing out all the errors slows down the program a lot. I would like to skip testing the non-existent memory. However (and this is the bug), pressing "c", "2", "2" (i.e., Test Address Range | Set Upper Limit) and attempting to change the memory range reveals bugs. It seems to be impossible to enter 4096 MiB as the maximum. I tried various strings such as "4096m" (can't enter capital letters) and "4294967296" but the program didn't interpret these correctly. memtest86+ v.40 run immediately after upgrade to oneiric ** Affects: memtest86+ (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878063 Title: Can't set memory maximum To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/878063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067043] Re: resolvconf adds an empty "nameserver" record into /etc/resolv.conf
What's in /etc/resolvconf/resolv.conf.d/tail? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067043 Title: resolvconf adds an empty "nameserver" record into /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1067043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067043] Re: resolvconf adds an empty "nameserver" record into /etc/resolv.conf
Hmm, OK we'll have to look deeper. Please post the output of the following commands run in a terminal. ls -l /etc/resolv.conf cat /etc/resolv.conf ls -l /etc/default/resolvconf cat /etc/default/resolvconf ls -l /etc/resolvconf/resolv.conf.d for F in /etc/resolvconf/resolv.conf.d/* ; do echo === $F === ; cat $F ; done ls -l /run/resolvconf ls -l /run/resolvconf/interface for F in /run/resolvconf/interface/* ; do echo === $F === ; cat $F ; done cat /etc/network/interfaces ls -l /run/network cat /run/network/ifstate cat /etc/NetworkManager/NetworkManager.conf dpkg -l resolvconf network-manager dnsmasq ps -elf | grep '\(Net\|dh\|dns\|ppp\|pptp\|vpn\)' ** Changed in: resolvconf (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067043 Title: resolvconf adds an empty "nameserver" record into /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1067043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992424] Re: ext4 filesystem errors on SSD disk
@Charles: Can you please explain why this report has been reclassified as "Fix Released"? Which kernel version contains the fix? How has this fix been tested? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992424 Title: ext4 filesystem errors on SSD disk To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/992424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992424] Re: ext4 filesystem errors on SSD disk
@Charles: I've had the same problem in the past. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992424 Title: ext4 filesystem errors on SSD disk To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/992424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000244] Re: /etc/resolv.conf symlink does not exist after initial installation of resolvconf package
Another data point. I just stumbled across AskUbuntu question #137037 and noticed that seven people have voted up the answer to run "dpkg- reconfigure resolvconf". That suggests that seven people had to run that command, i.e., that seven people were lacking the symlink for some reason. http://askubuntu.com/questions/137037/network-manager-not- populating-resolv-conf/172157#172157 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000244 Title: /etc/resolv.conf symlink does not exist after initial installation of resolvconf package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992424] Re: ext4 filesystem errors on SSD disk
Yep, nasty enough for me to stop using my new 240 GB Intel "520 series" SSD (model number SSDSC2CW240A3) and return to my old Hitachi 320GB HD which works perfectly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992424 Title: ext4 filesystem errors on SSD disk To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/992424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067043] Re: resolvconf adds an empty "nameserver" record into /etc/resolv.conf
The empty "nameserver" line comes from /run/resolvconf/interface/br0.inet which was created by the script /etc/network/if-up.d/000resolvconf from the content of the IF_DNS_NAMESERVERS variable whose contents come from the "dns- nameservers" line in the "iface br0" stanza of /etc/network/interfaces. My next guess is that the "dns-nameservers" line contains one or more non-printing characters between the first and the second listed IPv4 address. Can you please check? If there are such characters, what characters are they? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067043 Title: resolvconf adds an empty "nameserver" record into /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1067043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting
@Svartalf: Can you please describe in more technical detail what fails to work on the machines in question, and share with us what you know about the causes of these malfunctionings? Once we have some idea what you're talking about we can help you further. You wrote: > there's tons of local installations that use internal DNS What do you mean by "internal DNS"? > It doesn't honor lookups against the local, specified by DHCP, DNS servers [...] Ubuntu 12.04 *does* use DNS nameserver addresses provided by DHCP. Can you please explain what you are talking about here? > OpenVPN, PPTP, or something like Sonicwall's solution [is] going to re-direct > DNS on you ANYHOW > If you think you're changing their minds, think again. Ubuntu software works properly in Ubuntu 12.04 (except where it doesn't --- see the BTS). Third party software may fail to work properly, but it's up to the third party to fix that. Third parties who think they can dictate how free host operating systems work can go fly a kite. Just my personal view. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/959037 Title: NM-controlled dnsmasq prevents other DNS servers from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067043] Re: resolvconf adds an empty "nameserver" record into /etc/resolv.conf
Well, you actually have to ifdown and ifup the interface (br0) to test properly. But since there are no non-printing characters on the dns- nameservers line I guess my hypothesis has been disproved. Hmm. ** Changed in: resolvconf (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067043 Title: resolvconf adds an empty "nameserver" record into /etc/resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1067043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058089] Re: dnsmasq works intermittently
** Summary changed: - Intel 5100 AGN (iwlwifi) hangs frequently -- intermittent operation + dnsmasq works intermittently -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058089 Title: dnsmasq works intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1058089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 830333] Re: randomly, update-apt-xapi will take 100% cpu for an extended period of time
I just got this too. The update-apt-xapian-index command slowed down at around 30%, finally reached 70% or so before reporting Rebuilding Xapian index: done. Killed While running, the top command showed: %CPU %MEMTIME+ COMMAND 29.5 75.1 3:01.79 update-apt-xapi 14.4 0.0 1:44.51 btrfs-endio-3 13.8 0.0 0:17.87 btrfs-endio-2 12.8 0.0 0:17.92 btrfs-endio-3 So it possibly failed in this case because btrfs-endio also happened to be running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/830333 Title: randomly, update-apt-xapi will take 100% cpu for an extended period of time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/830333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049186] Re: sssd sometimes forgets all but one group memberships of a user
Not reproducible any more with version 1.9.1. ** Changed in: sssd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049186 Title: sssd sometimes forgets all but one group memberships of a user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1049186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066538] [NEW] Problem with signed vs unsigned treatment of uid
Public bug reported: I've been researching the appearance of an error message in sssd_nss.log. [sssd[nss]] [nss_cmd_getpwuid_search] (0x0040): No matching domain found for [-1], fail! Although I don't know yet where this "-1" is coming from, I have discovered something else which indicates a (possibly unrelated) bug. Cranking up the debug_level we see the following when doing "su -c pwd foo" (Sun Oct 14 17:47:33 2012) [sssd[nss]] [nss_cmd_getpwuid_search] (0x0100): Requesting info for [-1@SAMBA] (Sun Oct 14 17:47:33 2012) [sssd[nss]] [sss_dp_issue_request] (0x0400): Issuing request for [0x42bcd0:1:-1@SAMBA] (Sun Oct 14 17:47:33 2012) [sssd[nss]] [sss_dp_get_account_msg] (0x0400): Creating request for [SAMBA][4097][1][idnumber=4294967295] (Sun Oct 14 17:47:33 2012) [sssd[nss]] [sss_dp_internal_get_send] (0x0400): Entering request [0x42bcd0:1:-1@SAMBA] (Sun Oct 14 17:47:33 2012) [sssd[nss]] [nss_cmd_getpwuid_search] (0x0100): Requesting info for [-1@SAMBA] (Sun Oct 14 17:47:33 2012) [sssd[nss]] [nss_cmd_getpwuid_search] (0x0040): No matching domain found for [-1], fail! (Sun Oct 14 17:47:33 2012) [sssd[nss]] [sss_dp_req_destructor] (0x0400): Deleting request: [0x42bcd0:1:-1@SAMBA] (Sun Oct 14 17:47:33 2012) [sssd[nss]] [sss_parse_name_for_domains] (0x0200): name 'foo' matched without domain, user is foo [...] Adding max_id = 99 to the [domain/SAMBA] section of sssd.conf changes this to: (Sun Oct 14 17:49:32 2012) [sssd[nss]] [nss_cmd_getpwuid_search] (0x0100): Uid [4294967295] does not exist in domain [SAMBA]! (id out of range) (Sun Oct 14 17:49:32 2012) [sssd[nss]] [nss_cmd_getpwuid_search] (0x0040): No matching domain found for [-1], fail! (Sun Oct 14 17:49:32 2012) [sssd[nss]] [sss_parse_name_for_domains] (0x0200): name 'foo' matched without domain, user is foo It seems that although the uid is printed out as a signed integer, it is compared with the max_id value as an unsigned integer. ** Affects: sssd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066538 Title: Problem with signed vs unsigned treatment of uid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1066538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067043] Re: resolvconf adds an empty "nameserver" record into /etc/resolv.conf
FIrst, I'd like to know exactly what /etc/network/if-up.d/000resolvconf
is receiving in the IF_DNS_NAMESERVERS variable. Please apply the
appended patch, down and up the br0 interface, confirm that
/run/resolvconf/interface/br0.inet still contains
nameserver 66.185.16.130
nameserver
nameserver 66.185.16.131
and then post here the lines from /var/log/syslog that look like the
following ones.
Oct 22 22:26:38 myhost /etc/network/if-up.d/000resolvconf: 000 2e31 2e32
2e33 2034 2e35 2e36 2e37 0a38
Oct 22 22:26:38 myhost /etc/network/if-up.d/000resolvconf: 020
Second, what happens if you comment out the bridge_* options in the iface br0
stanza? Does the spurious "nameserver" line go away?
--
Thomas
--- 000resolvconf.orig 2012-10-22 22:27:21.187597692 +0200
+++ 000resolvconf 2012-10-22 22:26:18.867595028 +0200
@@ -25,6 +25,7 @@
R="${R}sortlist $IF_DNS_SORTLIST
"
fi
+echo "$IF_DNS_NAMESERVERS" | od -x | logger -t $0
for NS in $IF_DNS_NAMESERVERS ; do
R="${R}nameserver $NS
"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067043
Title:
resolvconf adds an empty "nameserver" record into /etc/resolv.conf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1067043/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070151] Re: resolvconf cannot recover from dnscache-run installation
This behavior reflects the fact that resolvconf will not attempt to create the symbolic link /etc/resolv.conf -> ../run/resolvconf/resolv.conf on upgrade. See bug #922677 for background. A workaround is to *purge resolvconf, install it, then reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070151 Title: resolvconf cannot recover from dnscache-run installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1070151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000244] Re: /etc/resolv.conf symlink does not exist after initial installation of resolvconf package
@Cerin: You say that disabling and re-enabling wireless connection corrects resolv.conf. Please run the following commands when resolv.conf is correct, so we know what you mean by that. cat /etc/resolv.conf ls -l /run/resolvconf/interface for F in /run/resolvconf/interface/* ; do echo === $F === ; cat $F ; done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000244 Title: /etc/resolv.conf symlink does not exist after initial installation of resolvconf package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000244] Re: /etc/resolv.conf symlink does not exist after initial installation of resolvconf package
Cerin, in your earlier comment (#75) you posted the results of several commands. The content of /etc/resolv.conf was incorrect. It was: # Generated by NetworkManager domain home search home nameserver 127.0.0.1 If this file had been generated by resolvconf, it would have begun with the contents of /etc/resolvconf/resolv.conf.d/head and not with the comment "# Generated by NetworkManager". Furthermore, resolvconf never writes a "domain" line. Comparing with what you describe as the correct contents, the domain and search lines are also incorrect, listing "home" instead of "mynetwork". In the later comment (#77) you say that /etc/resolv.conf contains # Generated by NetworkManager domain mynetwork search mynetwork nameserver 127.0.0.1 Although the domain and search lines are now "correct", the content is still not what resolvconf generates, so there is still something amiss. It appears as if NetworkManager is overwriting /etc/resolv.conf. (I say "appears" because some other program or script could be copying from a resolv.conf that was once generated by NM.) But NetworkManager also calls resolvconf, as evidenced by the fact that /run/resolvconf/interface/NetworkManager exists and has the same creation date and time as /run/resolvconf/resolv.conf. Accordingly, in the log file WifiSyslog.txt you posted originally we see the following. May 16 09:42:03 coronis NetworkManager[22975]: (eth2): writing resolv.conf to /sbin/resolvconf Looking in the network-manager source code I see what is most likely the cause of the problem. The code in src/dns-manager/nm-dns-manager.c is essentially the following. success = dispatch_resolvconf (domain, searches, nameservers, iface, error); if (success == FALSE) success = update_resolv_conf (domain, searches, nameservers, iface, error); With this code, if resolvconf returns nonzero for any reason then NetworkManager writes its output directly to (the target of) /etc/resolv.conf. This is wrong. I already wrote about this issue ten months ago. https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/324233/comments/30 Although the most serious of the several problems I discussed there have been fixed in Quantal, the problem remains that NetworkManager does not correctly handle a nonzero exit status returned by resolvconf. When resolvconf runs if may or may not return an error. For example, if some update.d hook script returns a nonzero status then that status is returned. But as NetworkManager is currently coded, if resolvconf returns an error for any reason then NM writes its nameserver information directly to /etc/resolv.conf. That NM behavior dates from the time that resolvconf was an optional package in universe which returned nonzero status to indicate that /etc/resolv.conf wasn't a symbolic link, and the NetworkManager maintainers wanted to avoid leaving the user without a resolv.conf at all costs. The behavior was inappropriate then (because it failed to distinguish between an absent symlink and runtime errors) and is more inappropriate now. The appropriate behavior for NetworkManager is: IF resolvconf is installed as evidenced by the presence of the file /sbin/resolvconf THEN send nameserver information to /sbin/resolvconf ELSE write the nameserver information directly to (the target of) /etc/resolv.conf. I will file a new bug report requesting that this finally be implemented. In the short term, though, Cerin, you should find out why resolvconf returns a nonzero status (... assuming it does and that this is the cause of your problem) and fix the underlying problem that causes it to do so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000244 Title: /etc/resolv.conf symlink does not exist after initial installation of resolvconf package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000244] Re: /etc/resolv.conf symlink does not exist after initial installation of resolvconf package
@Cerin: The resolvconf package only creates the symbolic link /etc/resolv.conf --> ../run/resolvconf/resolv.conf once, on initial installation. The package can be caused to repeat this action by running "dpkg-reconfigure resolvconf" and agreeing to "linkify" /etc/resolv.conf. However, it is certainly not the intention that this be done every time you connect to a new wireless network. If you have to do this then it is because some other piece of software is futzing with the symbolic link /etc/resolv.conf. The best solution is to figure out what software that is and cause it to stop doing that. > if resolvconf locks up Note that resolvconf doesn't lock up. It's not a daemon. It's just a script that gets run by other software that needs to update nameserver information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000244 Title: /etc/resolv.conf symlink does not exist after initial installation of resolvconf package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000244] Re: /etc/resolv.conf symlink does not exist after initial installation of resolvconf package
@Cerin: We need to find out which program it is that is not interfacing correctly with resolvconf. So far as I know all Ubuntu software interfaces correctly with resolvconf. It is known that some third party software doesn't interface correctly with resolvconf. Are you using a VPN client? Which one? When resolv.conf is incorrect, what is the output of these commands? ls -l /etc/resolv.conf cat /etc/resolv.conf ls -l /run/resolvconf ls -l /run/resolvconf/interface for F in /run/resolvconf/interface/* ; do echo === $F === ; cat $F ; done ls -l /etc/resolvconf/resolv.conf.d for F in /etc/resolvconf/resolv.conf.d/* ; do echo === $F === ; cat $F ; done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000244 Title: /etc/resolv.conf symlink does not exist after initial installation of resolvconf package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1053048] Re: network-manager does not respect comments in /etc/hostname
** Description changed: As found at bug 1052664 $ dpkg-query --show network-manager network-manager 0.9.6.0-0ubuntu7 $ cat /etc/hostname # xxx by cloud-init domU-12-31-39-0C-6C-81 This *should* be ok, as per 'man hostname': --F, --file filename - Read the host name from the specified file. Comments (lines - starting with a `#') are ignored. + -F, --file filename + Read the host name from the specified file. Comments (lines + starting with a `#') are ignored. - However, network-manager does not pay ignore the comments. + However, network-manager does not ignore the comments. ** Summary changed: - network-manager does not respect comments in /etc/hostname + network-manager does not ignore comments in /etc/hostname -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1053048 Title: network-manager does not ignore comments in /etc/hostname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1053048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
