http://bugzilla.opensuse.org/show_bug.cgi?id=905639 Manuel Bernhardt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #2 from Manuel Bernhardt --- Can confirm autofs bug. I also use autofs on my systems and every system hangs during first start and user isn't registered right on d-bus. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905639 --- Comment #3 from Jan Ritzerfeld --- Use this workaround if you do not mind users logging in before the autofs mounts are available: disable autofs.service, copy /usr/lib/systemd/system/autofs.service to /etc/systemd/system/autofs.service, remove the line "Before=systemd-logind.service" from /etc/systemd/system/autofs.service, enable autofs.service. I am no expert, so if I understand the problem correctly, NetworkManager depends implicitly on systemd-logind.service: Nov 16 12:08:56 linux-ykuq NetworkManager[732]: <info> Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc. To report bugs please use the NetworkMa nager mailing list. Nov 16 12:08:56 linux-ykuq NetworkManager[732]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the Netw orkManager mailing list. Nov 16 12:08:56 linux-ykuq dbus[641]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1. service' And this implicit dependency yields to a ordering cycle! If you model this explicitly in NetworkManager.service by adding "After=systemd-logind.service" to it, systemd will notice the cycle and disable autofs.service: Nov 16 12:12:50 linux-ykuq.site systemd[1]: Breaking ordering cycle by deleting job autofs.service/stop Nov 16 12:12:50 linux-ykuq.site systemd[1]: Job autofs.service/stop deleted to break ordering cycle starting with systemd-logind.service/stop -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905639 Jan Ritzerfeld changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dimstar@opensuse. |needinfo?(opensource@prodig |org) |y7.de), | |needinfo?(igaldino@gmail.co | |m) --- Comment #30 from Jan Ritzerfeld --- (In reply to Werner Fink from comment #27)

[...] ugly and also the question rises if this dirty hack works with NetworkManager?

It works for me using NetworkManager. Many thanks for your help, Werner! Most likely unrelated, a shutdown or reboot hangs for a few seconds and often there is a WiFi Firmware error displayed. To be sure, I would recommend Manuel or Isaque to test it, too. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905639 --- Comment #32 from Manuel Bernhardt --- Graphic cards Crashing system 1 -> NVIDIA Corporation GF116 [GeForce GTS 450 Rev. 2] (rev a1) Working system 1 -> Intel Corporation 3rd Gen Core processor Graphics Controller Working system 2 -> Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] RAM Crashing system 1 -> 8GB Working system 1 -> 4GB Working system 2 -> 4GB -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905639 --- Comment #36 from Andrei Borzenkov --- (In reply to Jan Ritzerfeld from comment #5)

I am not sure whether NetworkManager really depends on it. Maybe it just uses polkit and this depends on systemd-logind.

NM obtains suspend inhibitor lock so it can complete "prepare to sleep" processing: Who: NetworkManager (UID 0/root, PID 998/NetworkManager) What: sleep Why: NetworkManager needs to turn off networks Mode: delay This is done in src/nm-sleep-monitor-systemd.c. Currently it simply tries to unconditionally connect to logind. I think that this /could/ be changed to listen to name owner events on D-Bus and only try to connect to logind when it is started. (In reply to Werner Fink from comment #4)

There are no implicitly dependencies ...

there are as I have shown above.

if NetworkManager depends on systemd-logind.service than it has to requires this.

I agree. This would make this problem immediately obvious long ago.

But IMHO it should *NOT* depend on remote informations like NIS and/or NFS shares.

The reason for requiring logind has nothing to do with NIS or NFS. But it does put NM in a loop with logind when NSS lookup requires networking. Note that I do not claim it is NM bug. It can be considered logind bug as much - why logind needs networking for managing local system suspend/resume? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905639 --- Comment #50 from Manuel Bernhardt --- Any new? Updated today my system, got a new networkmanager version and fall back to this bug. Please overtake the fix to distribution! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905639 Nina Kuckländer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |it@clearingstelle-eeg.de -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905639 Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joschibrauchle@gmx.de --- Comment #53 from Joschi Brauchle --- Boo#905639 depends on this bug. Funny enough, in boo#905639 the problem is that autofs does not get restarted after a standby/resume. It turns out, that the NetworkManager-dispatcher is completely not working until a restart of NetworkManager after boot. The reason seems to be that NetworkManager-dispatcher is not registered correctly with DBUS, which seems to be due to this bug here. I am not an expert on DBUS, NetworkManager or AutoFS, but installing the patched package from http://download.opensuse.org/repositories/home:/arvidjaar:/bnc:/905639/stand... makes this bug and boo#905639 go away for me. I would be happy if there would be progress with this issue! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905639 --- Comment #57 from Joschi Brauchle --- Sorry for the wrong reference to the other bug boo#916737 that depends on this bug: (Correction to Joschi Brauchle from comment #53)

Boo#916737 depends on this bug.

Funny enough, in boo#916737 the problem is that autofs does not get restarted after a standby/resume. It turns out, that the NetworkManager-dispatcher is completely not working until a restart of NetworkManager after boot.

The reason seems to be that NetworkManager-dispatcher is not registered correctly with DBUS, which seems to be due to this bug here.

I am not an expert on DBUS, NetworkManager or AutoFS, but installing the patched package from https://build.opensuse.org/project/show/home:endzone:boo905639 makes this bug and boo#916737 go away for me.

I have packaged the currently latest NetworkManager from openSUSE 13.2 plus this patch here: https://build.opensuse.org/project/show/home:endzone:boo905639 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905639 --- Comment #60 from Hans-Peter Jansen --- Is there anything planned for us poor 13.2 users? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905639 --- Comment #62 from Bjørn Lie --- Please test the packages from https://bugzilla.opensuse.org/show_bug.cgi?id=922370 This versionbump should contain the above patch too. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905639 Stefan Quandt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |squan@web.de -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905639 http://bugzilla.opensuse.org/show_bug.cgi?id=905639#c64 matthias sweertvaegher changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthias.sweertvaegher@gmai | |l.com --- Comment #64 from matthias sweertvaegher --- (In reply to Joschi Brauchle from comment #57)

I have packaged the currently latest NetworkManager from openSUSE 13.2 plus this patch here: https://build.opensuse.org/project/show/home:endzone:boo905639

Joschi, does your patch still work? Because when I surf to https://build.opensuse.org/package/show/home:endzone:boo905639/NetworkManage... it says "Files could not be expanded: conflict in file NetworkManager.spec" build seems broken -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905639 http://bugzilla.opensuse.org/show_bug.cgi?id=905639#c66 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|os.gnome.maintainers@gmail. |badshah400@gmail.com |com | Flags|needinfo?(dimstar@opensuse. | |org) | --- Comment #66 from Dominique Leuenberger --- @Atri as we stopped the version updates for too many issues: can you please add the explicit patch for this issue in the the NM stack for 13.2 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905639 http://bugzilla.opensuse.org/show_bug.cgi?id=905639#c69 --- Comment #69 from Atri Bhattacharya ---

From talking to the nm-devs, 0.9.10.4 might get released eventually, but not rightaway. Until then, there is https://build.opensuse.org/request/show/346072

-- You are receiving this mail because: You are on the CC list for the bug.