On 10.07.2010 14:28, sean finney wrote:
hi michael,
On Sat, Jul 10, 2010 at 02:12:30PM +0200, Michael Biebl wrote:
Could you be more specific, what you did and what problems you had.
the applet remains visible but the enable networking option remains
unselectable (if you select it it stays disabled). so it is not possible
to use either wired or wireless networking without manually configuring
it via dhclient/iwconfig etc.
Did you do a partial upgrade of the network-manager, i.e. you only upgrade
the
libnm-* libs to 0.8.0.999 but not network-manager itself?
yeah. when i did an apt-get upgrade it brought in libnm-util1
libnm-glib-vpn1 libnm-glib2 and network-manager-gnome, but network-manager
remained at the previous version because of the situation with isc-dhcp-client
and resolvconf.
Ok, I just tested this combination.
networkmanager-gnome 0.8.0.999
libnm-* libs 0.8.0.999
network-manager 0.8
And this combination works more or less fine for me.
I can activate existing connections (system/user), create new ones, delete
existing ones.
The only issue I can confirm is, that indeed, the Enable/Disable network button
is not selectable. (The reason for this is, that in 0.8.0.999, there is a
distinction between user intiated or system initiated state changes and the new
nm-gnome makes use of this new API which nm 0.8 doesn't offer).
That said, while I agree, that bumping the dep on nm to = 0.8.0.999 in nm-gnome
is probably the right thing to do, the severity grave is not justified given
that I'm still able to use nm-applet.
How did you end up with a disabled networkmanager?
Did you disable it before you upgraded or did you have a failed suspend/resume
in between?
Michael
Did you perhaps disable network, upgrade nm-gnome and afterwards you
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature