network-manager is almost unusable since the latest update

[8200]

I use Ubuntu 12.04 amd64 with all latest update.

Network-manager almost worked well (only one bug with wpa hotspot) but today the latest update brought a very buggy version of network-manager.

When I click on "Edit Connections" it takes about 20 seconds until the window pops up.
Then in the "Network Connections" window all the settings are empty. But I have already added some connections so it should not be empty.

The notification icon alway blinks like it is connecting to some network. But all my connections are already connected and working...

So there are many bugs with current version.

But maybe it's not only a problem of network-manager because Software Center also opens very very slowly (also about 20 seconds).

I hope those problems are getting fixed soon.

Thanks!

[8200 (8200)]

Maybe it is a problem of "network-manager-gnome". I don't know.

But I have attached a screenshot of the network-manager and the apt history.

[Christian Mertes (cmertes)]

I'm seeing slightly different symptoms. My nm-applet reports that there are no network devices and I can't enable networking. Sometimes it also says that network-manager is not running. It started today and luckily I still get Ethernet although wifi is completely down.

I don't see the extremely bad responsiveness though. I'm using Lubuntu Precise.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christian Mertes (cmertes)]

Oh, in the syslog only this turns up on *starting* the network manager service:

Mar 15 23:15:35 Saffron kernel: [16250.034467] init: network-manager main process (13864) terminated with status 1
Mar 15 23:15:35 Saffron kernel: [16250.034556] init: network-manager main process ended, respawning

I couldn't find the PID mentioned before I restarted the service but after the termination and respawning I do see a NetworkManager process. Does this thing log to some other file than the syslog? Or can I make it more verbose?

[Christian Mertes (cmertes)]

Here's what nm-applet says when started on a freshly booted system:

** WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
** Message: applet now removed from the notification area

GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed
** Message: using fallback from indicator to GtkStatusIcon
** Message: applet now embedded in the notification area

** WARNING **: Failed to register as an agent: (4) Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

BTW, I should add that I am only online because I manually started dhclient. If this bug isn't seeing enough attention then it might also be because many people can't get online to report ;)

[Christian Mertes (cmertes)]

It seems fixed for me with the latest update.

[Mathieu Trudel-Lapierre (cyphermox)]

Yep, that's supposed to be fixed now and was due to issues in libnl code for wireless. Sorry ;)

[8200 (8200)]

It does work just fine currently :-)

[Christian Mertes (cmertes)]

Great this was fixed so quickly and thanks for the feedback Mathieu :)

[ilektron (robotoman)]

I am experiencing this exact error in Kubuntu 13.04 amd64. It only happens 75% of the time.