@Chow Loong Jin: feel free to submit a bug to upstream bugzilla about
this, link it to this bug and reopen it as Wishlist.
--
net usershare info takes too long (was: Nautilus hangs from time to time)
https://bugs.launchpad.net/bugs/479614
You received this bug notification because you are a membe
I agree nautilus could be more resistant to that... Closing as invalid
nevertheless.
** Changed in: samba (Ubuntu)
Status: Incomplete => Invalid
** Changed in: nautilus-share (Ubuntu)
Status: Incomplete => Invalid
--
net usershare info takes too long (was: Nautilus hangs from time
I found out what was wrong:
I copied the smb.conf from my old setup, where I used KVM and had
several vnet's. This line in smb.conf allowed me to share files only
with my virtual machines:
interfaces = 127.0.0.0/8 vnet0 vnet1 vnet2
I did not setup kvm that way again, therefor I had no vnet0-2
Hi,
I attached nsswitch.conf. The config in question in smb.conf is commented out:
# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
I think I have a copied version of smb.conf from an older instalation,
My trace does not do:
socket(PF_FILE, 0x80801 /* SOCK_??? */, 0) = 3
connect(3, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 110) = -1 ENOENT
(No such file or directory)
...
It jumps directly to:
geteuid() = 1000
Could you attach your /etc/nsswitch.conf, and let
I asked myself why it has two times the same nameserver in this list.
Its because im connected two times to that network, over wireless and
ethernet. When I disable one connection, one nameserver disappears.
Nevertheless the problem persists...
** Attachment added: "resolv.conf"
http://launchpa
** Attachment added: "hosts"
http://launchpadlibrarian.net/35569828/hosts
--
net usershare info takes too long (was: Nautilus hangs from time to time)
https://bugs.launchpad.net/bugs/479614
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Oops, sorry, that was not intended... Again an strace...
$ time strace net usershare info 2> strace-info.txt
real1m24.015s
user0m0.030s
sys 0m0.030s
strace-info.txt is attached. It hangs at the same line as "list" does...
$ hostname -f
alpha
hosts and resolv.conf is attached... I do
Yes, like I said in comment 9, net usershare list is very local, so it
shouldn't really need to resolve names. I suspect some TCP connections
against the local system hostname that would trigger a simple resolution
(that may fail on faulty setups). If that doesn't prove right, next step
is looking
The trace also seems to point to an issue in your name resolution
configuration. Either failing to connect to 192.168.220.1 for name resolution,
or failing to get an answer from it...
What happens if you run "ping $(hostname)" ? Could you attach your
/etc/resolv.conf and /etc/hosts ?
--
net us
Hi,
My setup is a typical home setup, no domain server or something like
that, local user accounts. I have a D-Link DIR-855 Router at
192.168.220.1 which also acts as DHCP and DNS-Server (DNS-forwarding or
something like that). That router has also the ability to share an
attached USB-Harddisk (SM
The timeout seems to point to some name resolution issue, but "net usershare
list" is very local...
Anything special in your setup, like username resolution coming from a domain
server ? Any hints on what "net usershare info" is doing while it hangs (strace
?). Couldn't find anything related in
** Summary changed:
- Nautilus hangs from time to time
+ net usershare info takes too long (was: Nautilus hangs from time to time)
--
net usershare info takes too long (was: Nautilus hangs from time to time)
https://bugs.launchpad.net/bugs/479614
You received this bug notification because you ar
13 matches
Mail list logo