Le vendredi 11 mai 2012, à 10:38 +0100, Alin M Elena a écrit :

On Fri 11 May 2012 11:34:22 Vincent Untz wrote:

...

Hey,

If you see NetworkManager crashing in Factory, it might be because of libnl3-200 3.2.8. There's a change in this version that seems to make NetworkManager unhappy.

If you hit this, you can either:

- temporary go back to ifup network management (in yast) - downgrade libnl3-200 to 3.2.7 (untested, but should work) - wait for libnl3-200 3.2.9 to hit Factory (worked for me); the new version has been submitted to the devel project (sr#120694)

Cheers,

Vincent

one minute to late... for me... and yast is broken too... so we have the perfect ingredients for havoc...

"yast --ncurses" was working for me Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

"yast --ncurses" was working for me

still crushes for me.. yast Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 11/05/12 10:09, Raymond Wooninck wrote:

Hi Vincent,

On Friday, May 11, 2012, Vincent Untz wrote:

...

Hey,

If you see NetworkManager crashing in Factory, it might be because of libnl3-200 3.2.8. There's a change in this version that seems to make NetworkManager unhappy.

Unfortunately I didn't see this message as that it would have saved me quite some work. Some this 3.2.8 version of libnl3 makes more things unhappy. NetworkManager is indeed crashing and my KDE desktop took ages to startup. (Literally more than 15 or 30 minutes).

...

- temporary go back to ifup network management (in yast) - downgrade libnl3-200 to 3.2.7 (untested, but should work)

I reverted back to the old libnl3 version 3.2.7 and have a working system again. (After fighting with the systemd for almost 3 hrs :-( )

Just got hit by this as well :-( I wonder why it hangs the whole system, I would expect KDE to start without network instead of a hang,,, -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 11/05/12 15:34, Raymond Wooninck escribió:

On 05/11/2012 06:15 PM, Cristian Rodríguez wrote:

...

Just got hit by this as well :-( I wonder why it hangs the whole system, I would expect KDE to start without network instead of a hang,,,

I don't think this is caused by a crashing NetworkManager.

Correct, It was a different problem, in my case Xorg drm_nouveau made X crash, worked around by reenabling Nvidia propietary driver. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org