What happened? NetworkManager broke?

***glennzo*** · #1 21st October 2009, 12:19 AM

Fired up the trusty old laptop tonight only to be greeted with this (screenshot attached). No networking at all, wireless or wired. Had to disable NetworkManager and enable network so I could get hooked up and see if there were important updates. I was hoping that something would magically fix my issue but no such luck. Now I'm tethered to an Ethernet cable. This stinks. Anyone else with the same trouble?

#2 21st October 2009, 12:57 AM

love the screenshot there....had a look in Bugzilla for a similiar issue glenn?. i havent even tried the livecd yet but i'll let you know if i get the same problem

***glennzo*** · #3 21st October 2009, 01:06 AM

Haven't looked at all Demz. I'm dead tired and am shutting this thing down as soon as I press "Post Quick Reply". I've been using "12" since it was available as rawhide. It has been an excellent OS for me and has actually been my daily user, totally ignoring the Fedora 11 install on this same computer. This morning all was well. May have done some updates. Don't remember at the moment. Booted tonight to this ...

Thanks for the reply Demz. Off to the couch with me. If I turn the TV on I'll surely be asleep in 20 minutes

leigh123linux · #4 21st October 2009, 03:07 AM

Press Alt+F2 and run

Code:

nm-applet --sm-disable

I have the same issue

**AdamW** · #5 21st October 2009, 06:11 AM

https://bugzilla.redhat.com/show_bug.cgi?id=529766

***glennzo*** · #6 21st October 2009, 08:12 AM

Quote:

Originally Posted by leigh123linux

Press Alt+F2 and run

Code:

nm-applet --sm-disable

I have the same issue

Thank you Leigh! That worked

**AdamW** · #7 21st October 2009, 10:57 PM

right - as mentioned in the bug report, only the *first* attempt to run nm-applet in any session fails. all subsequent attempts work.

korpenkraxar · #8 21st October 2009, 11:13 PM

Hi all!

I can report the same problem running a Thinkpad W500 a fresh 32-bit install. I get the same error as the OP and the suggested workaround works. But in my case I can start nm-applet manually any way I want, even without the --sm-disable flag. nm-applet actually starts as long as it is not called immediately at login.

If I let nm-applet start through a small bash script instead of being called directly in Startup Applications, it starts just fine if the script looks like this:

Code:

#!/bin/sh
sleep 1
nm-applet --sm-disable &

but not like this:

Code:

#!/bin/sh
sleep 0
nm-applet --sm-disable &

Weird stuff but might be a clue for what is going on. Something is not in its right state at login but seems to become so very quickly.

I have not figured out how to execute multiple executive commands in a single Startup Applications field. Tweaking the Network Manager command line:

Code:

nm-applet --sm-disable

so that it instead reads:

Code:

sleep 1 && nm-applet --sm-disable

seems to result in nm-applet not being executed at all.

**AdamW** · #9 21st October 2009, 11:31 PM

the --sm-disable isn't strictly required, but it's sensible to run it with that parameter. running it with that parameter is not the workaround for this issue, simply running it *twice* is the workaround...we just recommend doing it with that parameter as that's the right way to run it in any case

korpenkraxar · #10 22nd October 2009, 12:01 AM

Quote:

Originally Posted by AdamW

simply running it *twice* is the workaround...

Hi Adam!

Is it really running it twice that is the workaround? What happens if you just duplicate Network Manager in Startup Applications?

I would rather suggest that we need to wait for something else to settle before nm-applet works. I can start it successfully at the first attempt as long as it is not started immediately.

Googling around I found some old Ubuntu references to an icon cache needing to be updated which apparently triggered the same error. While I do not think that it is the very same problem here (and their fix did not work for me), it may still be something related to the graphical interface that nm-applet tries to attach to.

Actually, if I do a full reboot I need to up the sleep time in my script to something like ten seconds for it to work reliably at the first login. As long as the gnome-panel has had time to settle it works, for me.

***glennzo*** · #11 22nd October 2009, 12:08 AM

Quote:

Originally Posted by AdamW

right - as mentioned in the bug report, only the *first* attempt to run nm-applet in any session fails. all subsequent attempts work.

Adam, next time I boot the F12 machines I'll try running nm-applet without --sm-disable and will try to remember to let you know how I make out. Thanks for the reply(s).

Reading further down this thread, would you like me to try with or without?

**AdamW** · #12 22nd October 2009, 12:18 AM

glennzo: either will work, but with --sm-disable is the right way to run it. to be clear: the --sm-disable parameter has *absolutely nothing to do* with this bug at all. it's just a parameter that is usually used when running nm-applet. if you check how it's run automatically when you log in, it's run with --sm-disable.

korpen: yeah, it's more running it later that's the fix, you're right. this is the icon cache issue you mention, in fact, according to the bug report.

korpenkraxar · #13 22nd October 2009, 12:41 AM

Haha! I just had a second look at the report. Silly bug that is going to cause a lot of headaches and grumpy beta reviewers/testers. Well, this is why there are betas in the first place. Looking forward to the fix.

thomthom · #14 22nd October 2009, 09:23 AM

the start-up script works fine... will be glad when they fix the problem though

leigh123linux · #15 22nd October 2009, 05:22 PM

This new NetworkManager version fixes the issue for me.

http://koji.fedoraproject.org/koji/b...buildID=137758