Re: [Bug 512777] Re: first login fails when NIC is managed by NM-wicd

2010-01-28 Thread Roman
Hi

Static IPs: Some friends have the same config working on a static 
network  since some 2 years (Debian Etch IIRC). With karmic they report 
it's working as long as they use wicd: but they are unable to use 
NetworkManager (no logon servers). They are now planning to migrate all 
the school within a 2 months deadline so it seems they feel happy. I 
could get a syslog from them if needed.

DHCP: tried on another machine with samba package installed, so smbd and 
nmbd appear on syslog too. I tried the four combinations of lines/no 
lines about eth0 on /etc/network/interfaces and managed = false/true on 
/etc/NetworkManager/nm-system-settings.conf.

Two of them (managed = false) follow below. I guess this covers the two 
usual scenarios. Behaviour is always the same in all four cases. No wicd 
tests done.

It seems that, with any config, and even if everybody gets fired up just 
in time, dhclient does not finish before samba daemons start. I hope you 
can see the causes I'm unable to see.

After some googling, it seems that there is a NETWORKWAIT option on 
RedHat that goes in /etc/network/interfaces equivalent, but I'm unable 
to see any mention about it on .deb-based distros. I know this is a 
samba bug report, but does anybody knows about it?

Funniest thing is, if you wait some 30 seconds after gdm appears on 
screen, you can login at first attemp; if you don't wait, first login 
fails (?) Second login attempt always work.

Syslog snippets follow, I could send corresponding samba logs with 
loglevel = 3 if needed.

Best regards,
Roman

syslog snippet 0:
eth0 lines on /etc/network/interfaces
managed = false on /etc/NetworkManager/nm-system-settings.conf
==
Jan 26 12:00:32 u034755 kernel: imklog 4.2.0, log source = 
/var/run/rsyslog/kmsg started.
Jan 26 12:00:32 u034755 NetworkManager:   starting...
Jan 26 12:00:32 u034755 NetworkManager:   Trying to start the 
modem-manager...
Jan 26 12:00:32 u034755 NetworkManager:SCPlugin-Ifupdown: init!
Jan 26 12:00:32 u034755 NetworkManager:SCPlugin-Ifupdown: 
update_system_hostname
Jan 26 12:00:32 u034755 NetworkManager:SCPluginIfupdown: guessed 
connection type (eth0) = 802-3-ethernet
Jan 26 12:00:32 u034755 NetworkManager:SCPlugin-Ifupdown: 
update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, 
id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e
Jan 26 12:00:32 u034755 NetworkManager:SCPlugin-Ifupdown: autoconnect
Jan 26 12:00:32 u034755 modem-manager: Loaded plugin Nokia
Jan 26 12:00:32 u034755 NetworkManager:SCPluginIfupdown: management 
mode: unmanaged
Jan 26 12:00:32 u034755 modem-manager: Loaded plugin Sierra
Jan 26 12:00:32 u034755 NetworkManager:SCPlugin-Ifupdown: devices 
added (path: /sys/devices/pci:00/:00:1c.4/:04:00.0/net/eth0, 
iface: eth0)
Jan 26 12:00:32 u034755 modem-manager: Loaded plugin Ericsson MBM
Jan 26 12:00:32 u034755 NetworkManager:SCPluginIfupdown: locking 
wired connection setting
Jan 26 12:00:32 u034755 modem-manager: Loaded plugin Generic
Jan 26 12:00:32 u034755 NetworkManager:Ifupdown: get unmanaged 
devices count: 1
Jan 26 12:00:32 u034755 modem-manager: Loaded plugin Huawei
Jan 26 12:00:32 u034755 NetworkManager:SCPlugin-Ifupdown: 
(155470576) ... get_connections.
Jan 26 12:00:32 u034755 modem-manager: Loaded plugin ZTE
Jan 26 12:00:32 u034755 NetworkManager:SCPlugin-Ifupdown: 
(155470576) ... get_connections (managed=false): return empty list.
Jan 26 12:00:32 u034755 modem-manager: Loaded plugin Option
Jan 26 12:00:32 u034755 NetworkManager:Ifupdown: get unmanaged 
devices count
: 1
Jan 26 12:00:32 u034755 modem-manager: Loaded plugin Gobi
Jan 26 12:00:32 u034755 NetworkManager:SCPlugin-Ifupdown: devices 
added (path: /sys/devices/virtual/net/lo, iface: lo)
Jan 26 12:00:32 u034755 modem-manager: Loaded plugin MotoC
Jan 26 12:00:32 u034755 NetworkManager:SCPlugin-Ifupdown: device 
added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown 
configuration found.
Jan 26 12:00:32 u034755 modem-manager: Loaded plugin Option High-Speed
Jan 26 12:00:32 u034755 NetworkManager:SCPlugin-Ifupdown: end _init.
Jan 26 12:00:32 u034755 modem-manager: Loaded plugin Novatel
Jan 26 12:00:32 u034755 NetworkManager: Loaded plugin ifupdown: (C) 2008 
Canonical Ltd.  To report bugs please use the NetworkManager mailing list.
Jan 26 12:00:32 u034755 NetworkManager: Loaded plugin keyfile: (c) 2007 
- 2008 Red Hat, Inc.  To report bugs please use the NetworkManager 
mailing list.
Jan 26 12:00:32 u034755 NetworkManager:   Wireless now enabled by 
radio killswitch
Jan 26 12:00:32 u034755 NetworkManager:   (eth0): carrier is ON
Jan 26 12:00:32 u034755 NetworkManager:   (eth0): new Ethernet 
device (driver: 'r8169')
Jan 26 12:00:32 u034755 NetworkManager:   (eth0): exported as 
/org/freedesktop/NetworkManager/Devices/0
Jan 26 12:00:32 u034755 kernel: [0.00] Linux version 
2.6.31-17-gen

[Bug 512777] Re: first login fails when NIC is managed by NM-wicd

2010-01-27 Thread Thierry Carrez
I'm not surprised that user networking setup, as defined by NM/WICD, is
not available until the fully user logs in... so winbind won't work
until then, chicken and egg.

I'm more surprised that winbind fails when systemwide networking is defined 
though.
I suppose the syslog snippet you attached comes from a DHCP configuration 
defined in /etc/networking/interfaces ?
If not, could you test that ?
Also could you try with static networking instead and let us know how that goes 
?

** Changed in: samba (Ubuntu)
   Importance: Undecided => Medium

** Changed in: samba (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- first login fails when NIC is managed by NM-wicd
+ [winbind] first login fails when NIC is managed by NM-wicd

-- 
[winbind] first login fails when NIC is managed by NM-wicd
https://bugs.launchpad.net/bugs/512777
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs