http://bugzilla.opensuse.org/show_bug.cgi?id=916737 Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joschibrauchle@gmx.de --- Comment #3 from Joschi Brauchle --- Just FYI: I can confirm the problem on my laptop! AutoFS does not restart after standby+resume! I have identical log entries... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916737 --- Comment #10 from Frerk Meyer --- I debug the autofs script with 'logger' statements like this: #! /bin/sh # # autofs dispatcher script for NetworkManager # # Matthias Koenig # . /etc/rc.status case "$2" in up) logger "NetworkManager network link is up, test autofs service" if test -x /bin/systemctl && systemctl -q is-enabled autofs.service; then logger "NetworkManager: autofs is enabled, try to restart" systemctl restart autofs.service logger "NetworkManager: autofs was restarted" elif rc_active autofs; then logger "NetworkManager: network link is up, restart autofs without systemd" /etc/init.d/autofs restart logger "NetworkManager: autofs was restarted without systemd" fi ;; *) logger "NetworkManager network link is down?" exit 0 ;; esac Result of booting, logging in and several times suspend & resume is # journalctl |grep logger .. Feb 17 20:50:56 moby.o2.box logger[817]: NetworkManager network link is down? Feb 17 20:51:05 moby.o2.box logger[951]: NetworkManager network link is up, test autofs service Feb 17 20:51:05 moby.o2.box logger[982]: NetworkManager: autofs is enabled, try to restart Feb 17 20:51:06 moby.o2.box logger[1081]: NetworkManager: autofs was restarted Feb 17 20:51:06 moby.o2.box logger[1085]: NetworkManager: network link is up, start nfs Feb 17 20:51:45 moby.o2.box logger[1674]: NetworkManager network link is down? Conclusion: in the boot process autofs script is called with parameter 'up' once, which is correct. Afterwards it was called once with another parameter (down?). And after that it is never called, may it be during suspend or resume. Now I use the workaround from Joschi Brauchle, that is not to wait for NetworkManager and restart autofs anyways. But NetworkManager should call autofs and log "NetworkManager network link is up, test autofs service" which it doesn't. BTW: NetworkManager seems to me like a total rewrite, the GUI has changed completly. Maybe some new bugs were introduced? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916737 Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(frerk.meyer@gmx.d | |e) | --- Comment #12 from Joschi Brauchle --- Is there any progress here? I think the need_info was provided in C9-C11, right? It looks like the NetworkManager dispatcher scripts are not called or called only after first standby, but then never again. Also it looks like they may be called with wrong parameters. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916737 --- Comment #13 from Joschi Brauchle --- I've done some more debugging on this annoying issue and found the following interesting info. I put NetworkManager in debug mode and found that NetworkManager does NOT AT ALL call the dispatcher on sleep/resume (it does call dispatcher for other changes in interfaces like WIFI connect or so) UNTIL NetworkManager is restarted. Then it does call the dispatcher on sleep/resume actions. So for me this looks like NetworkManager-dispatcher does not get notified correctly on sleep/resume when it is started during boot. Once it is restarted at a later time, it seems to work correctly. Maybe this is a DBUS issue? @Frerk: Could you please check if the dispatcher is running correctly after you run 'systemctl restart NetworkManager.service'? For me this is the case. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916737 Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |905639 --- Comment #15 from Joschi Brauchle --- This bug possibly depends on https://bugzilla.opensuse.org/show_bug.cgi?id=905639 I can confirm the behavior of above bug, i.e. logind service fails on boot. This seems to be due to dependency cycle with NetworkManager. Somehow, the system recovers and still boots, but NetworkManager is not correctly registered with dbus. After installing the patches NetworkManager package from here: http://download.opensuse.org/repositories/home:/arvidjaar:/bnc:/905639/stand... the problem described in this bug goes away! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916737 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |925873 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916737 http://bugzilla.opensuse.org/show_bug.cgi?id=916737#c17 --- Comment #17 from Frerk Meyer --- After an update (upower replaced pmutils ?) the problem reappeared, since the workaround with the script 06autofs does no longer work. Here is a snippet from the system journal after opening the lid and resume (unnessary entries removed): Aug 02 11:11:48 moby.o2.box kernel: PM: Finishing wakeup. Aug 02 11:11:48 moby.o2.box kernel: Restarting tasks ... done. Aug 02 11:11:48 moby.o2.box NetworkManager[893]: <info> (enp0s25): link disconnected (deferring action for 4 seconds) Aug 02 11:11:50 moby.o2.box kernel: e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 02 11:11:50 moby.o2.box NetworkManager[893]: <info> (enp0s25): link connected Aug 02 11:11:55 moby.o2.box kernel: e1000e: enp0s25 NIC Link is Down Aug 02 11:11:55 moby.o2.box NetworkManager[893]: <info> (enp0s25): link disconnected (deferring action for 4 seconds) Aug 02 11:11:58 moby.o2.box kernel: e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx Aug 02 11:11:58 moby.o2.box NetworkManager[893]: <info> (enp0s25): link connected Aug 02 11:12:10 moby.o2.box su[16876]: (to root) frerk on pts/1 Aug 02 11:12:10 moby.o2.box su[16876]: pam_unix(su-l:session): session opened for user root by frerk(uid=1026) 2 things noticed: 1) when NetworkManager starts again the link is down 2) link goes up and NetworkManager notices it, but doesn't start the autofs script 3) link goes down briefly (I don't know why, I do nothing to the network cable, it does this every time in resume) 4) NetworkManager notices link down 5) link goes up second time 6) NetworkManager notices link is up but doesn't start autofs script the second time This is with NetworkManager-0.9.10.0-3.11.1.x86_64 from OpenSuse 13.2. Newer versions of NetworkManager are reported here to work. So my possible workarounds are: - install NetworkManager in a newer version alone - upgrade to TumbleWeed - learn upowerd and see if i can insert a autofs restart anywhere If an update of OpenSuse 13.2 is able to replace pmutils with upowerd, why is it impossible to update NetworkManager to a working version? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=916737 Bug 916737 depends on bug 905639, which changed state. Bug 905639 Summary: Enabling autofs delays login by letting systemd-logind fail http://bugzilla.opensuse.org/show_bug.cgi?id=905639 What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.