On Fri, Apr 15, 2011 at 6:50 PM, Felipe Sateler <fsate...@debian.org> wrote: >> Could those thread participants who have gripes from their last NM >> experience many years ago please confirm that their gripes still apply >> before continuing with the discussion? > > felipe@pcfelipe:supercollider% apt-cache policy network-manager > network-manager: > Installed: 0.8.3.999-1 > Candidate: 0.8.3.999-1 > Version table: > 0.8.998-1 0 > 1 http://ftp.br.debian.org/debian/ experimental/main amd64 > Packages > *** 0.8.3.999-1 0 > 500 http://ftp.br.debian.org/debian/ sid/main amd64 Packages > 500 http://ftp.br.debian.org/debian/ testing/main amd64 Packages > 100 /var/lib/dpkg/status > felipe@pcfelipe:supercollider% sudo aptitude reinstall network-manager > The following packages will be REINSTALLED: > network-manager > 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and > 216 not upgraded. > Need to get 0 B/1,102 kB of archives. After unpacking 0 B will be used. > Reading package fields... Done > Reading package status... Done > Retrieving bug reports... Done > Parsing Found/Fixed information... Done > (Reading database ... 219815 files and directories currently installed.) > Preparing to replace network-manager 0.8.3.999-1 (using .../network- > manager_0.8.3.999-1_amd64.deb) ... > Unpacking replacement network-manager ... > Setting up network-manager (0.8.3.999-1) ... > Reloading system message bus config...done. > Stopping network connection manager: NetworkManager. > <oooops, wifi connection gone> > Starting network connection manager: NetworkManager. > Processing triggers for man-db ...
As it was said before (*multiple* times, unfortunately), that's expected. Your *wired* connection won't go down... -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/BANLkTi=ASmGeu+jL0LmULrnrLmpi=cr...@mail.gmail.com