Network Manager broken after update (Page 2 of 2)

The replies by Aaro and Anonymous confirm the confusion about a possible post-freeze difference between Squeeze and Testing – thanks for the clarifications – but I am still wondering what I could do if I want to have a working mobile broadband (HSDPA) connection tomorrow, since it seems that it's broken with NM version 0.8.1-1. How do I downgrade to the previous version (apparently 0.8.1)? Perhaps by uninstalling (purging) NM and reinstalling from an older DEB package (0.8.1) or compiling it from source? Or can I do it via apt (I'm using aptitude as front-end) somehow?

I never use smilies, but there are exceptions that prove the rule
Now playing: Libre.fm

I have a different network problem and I can confirm it has to do with Squeeze, rather than being #!-specific.

I use a wired eth0 with DHCP on my main box.  My primary boot was a different partition with Squeeze/LXDE and I installed Network Manager about 10 days ago so that I could use a WiFi dongle.  It broke my wired/DHCP connection.  Lots of troubleshooting and I finally had to go to static IP and stop/start eth0 after boot to get a connection.  First time Squeeze "left a deposit on my feet."     No help on the Debian forums.

I switched to my #! partition.  Worked fine.  Finally decided to allow the DHCP and Network Manager updates to run.  Bad idea.  My wired connection is initialized correctly at boot 50-70% of the time.  Otherwise, I have to "Disable Networking" and then "Enable Networking" to get a DHCP lease.  That works about 95% of the time on the first manual Disable/Enable attempt.  If it doesn't, I Disable/Enable again.

The same box runs Windows Vista (all together...Yuuck!) via the same ethernet, router, and DHCP server perfectly every time. 

Over the past ten days of so, I've noticed numerous upgrades of the DHCP components and Network Manager.  FWIW, I think these were all promoted to Testing before they were ready.  (To beat the Freeze...?)

The only other issue I've ever had with Squeeze has been maintenance of Iceweasel.  I gave up and installed Firefox from the Mozilla site.  Much better.

Experienced this as well on my netbook a few days ago when I tried out the latest nm-applet. When trying to connect the first time I think it switched the 3g dongle from modem mode to regular usb stick mode, or something, cause you couldn't dial out with the ppp daemon/wvdial after that (until mode switch or reboot). Good to know it's been fixed.

Same problem here kinda/sorta. 

I did an "aptitude full-upgrade" to my #!Statler/Debian Sid install . . . it removed many, many packages and apps.
I noticed that Gnome-Network-Manager was one of them.

I was still able to connect to the internet and D/L stuff, but the NM Applet had changed.

So, today . . . I re-installed Network-Manager-Gnome . . . just in case. 

I noticed a while ago that apt-get wanted to remove network-manager-gnome in an autoremove; I simply canceled the autoremove, sudo'd `apt-get install network-manager-gnome` to set it to manually installed, then went back to the autoremove.

Hopefully the "gold" release of Statler will come with network-manager-gnome as a manual install and not an autoinstall.

A tip for those of us who have 3g mobile broadband as our only method of connecting to the Internet (no Ethernet, no WLAN):

Download sakis3g script [1] and save it to an USB stick.

If network-manager or usb-modeswitch gets broken, you will be able to connect with sakis3g. Just make the script executable (chmod +x) and run it with:

sudo /path/to/sakis3g connect

It will try to autodetect what ever it can (and it seems to be very good at it too!) and has the latest modeswitch embedded. More information at the site. Good addition to your toolbox.

[1] http://www.sakis3g.org/

I just reinstalled the whole system from scratch (this past week), using the "old" (at this point) Statler Alpha2 CD, the cb-welcome script ran, and the upgrades DID NOT remove the network-manager-gnome (I got caught up when it was removed in an "upgrade" in September and my wifi stopped working).  I did nothing special, no "apt-get HOLD pkg" or whatever.

Since we're so close to the release, I'm hoping that this was just a bump in the road.  I'm not going to save the .deb

Regards,
JustCreepin'