Re: Wifi GNOME network manager version into KUbuntu, Debian pinning method, etc. ; jor debian
On 08/07/2010 11:44 AM, giovanni_re wrote: KUbuntu 10.4, = Failing to get wifi to connect to access point. It can see APs, but fails to get dhcp via command mode, fails connect with wicd. = It has been suggested (on KUbuntu list?) to remove the KU network manager package, that might get wicd console command wifi working. --deleted-- My apologies for an Ubuntu/Kubuntu question/answer on a Debian list. But, this could also be an issue in Debian, depending. See explanation. I think the problem with recent Kubuntu *and* Ubuntu *upgrades* is that they allow both wicd and network manager to exist simultaneously on a system. This is the cause for failures, in my opinion. Let me explain: When I first tried out 'wicd', on a system with Network Manager installed, I simply had the installer process the new package. And the installer forced the removal of network manager. I recently upgraded to the latest Kubuntu release. My 'old' setup was using wicd, and nw was *not* installed. After the upgrade, networking failed in odd ways. After some research, I found that the upgrade had installed network manager while leaving wicd in place. I removed nw and wicd now works as expected. I think nw would have worked 'as expected' had I removed wicd instead. I don't know if this is an issue for Debian or not, as I don't know how much of the Debian upgrade/installation configuration is kept 'as is' in Ubuntu/Kubuntu. And I have not done an upgrade of a wireless based Debian system. However, if you simply remove the KDE frontend for nw and install the Gnome one (with all the related dependencies), or install wicd instead, there should be no issue with updates to the *existing installed* packages, hence no pinning should be needed. This is how I'm doing it and everything continues to work well. The only thing that could be a problem would be a future upgrade, assuming the installer processing is not fixed. -- Bob McGowan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c62f48c.5060...@symantec.com
RE: Wifi GNOME network manager version into KUbuntu, Debian pinning method, etc. ; jor debian
Original Message From: Bob McGowan [mailto:bob_mcgo...@symantec.com] Sent: Wednesday, August 11, 2010 11:06 AM To: debian-user@lists.debian.org Subject: Re: Wifi GNOME network manager version into KUbuntu, Debian pinning method, etc. ; jor debian On 08/07/2010 11:44 AM, giovanni_re wrote: I recently upgraded to the latest Kubuntu release. My 'old' setup was using wicd, and nw was *not* installed. After the upgrade, networking failed in odd ways. After some research, I found that the upgrade had installed network manager while leaving wicd in place. I removed nw and wicd now works as expected. I think nw would have worked 'as expected' had I removed wicd instead. I don't know if this is an issue for Debian or not, as I don't know how much of the Debian upgrade/installation configuration is kept 'as is' in Ubuntu/Kubuntu. And I have not done an upgrade of a wireless based Debian system. I just saw this behavior Monday when I upgraded a Squeeze KDE based laptop that had wicd installed. I did a full-upgrade and lost my wireless. I realized that network-manager and wicd were fighting over it, and uninstalled network-manager. Aptitude complained about unresolved KDE dependencies (actually only a recommend, but I guess recommends are dependencies these days) but let me get rid of network-manager anyway. After network-manager went away, wicd was happy and everything works as expected. IMHO network-manager and wicd should be in a wifi section for debian alternatives. KDE works fine with wicd instead of network-manger, and so does Gnome as far as I can tell. James -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4a09477d575c2c4b86497161427dd94c15b0d1f...@city-exchange07
Wifi GNOME network manager version into KUbuntu, Debian pinning method, etc. ; jor debian
KUbuntu 10.4, = Failing to get wifi to connect to access point. It can see APs, but fails to get dhcp via command mode, fails connect with wicd. = It has been suggested (on KUbuntu list?) to remove the KU network manager package, that might get wicd console command wifi working. Previously, I was told that there is more networking success if one installs Ubuntu (not KUbuntu) [to get the Ubuntu/Gnome network manager sw], then install KDE on top of that. = For a system that was installed as KUbuntu: Might it be possible to use something like Debian pinning to hold back the KU network manager package, then install the Ubuntu NetworkManager package? Guess I'd at least have to ad the Ubuntu repositories to /etc/apt/sources.list. There might also be another debian method to do this. = Being as Ubuntu is Debian based, is there some way to make this work? = I ran Debian from about 2000-2005, so haven't done pinning for a long time. = Thanks :) == Join in the Global weekly meetings, via VOIP, about all Free SW HW Culture http://sites.google.com/site/berkeleytip/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1281206659.31161.1388795...@webmail.messagingengine.com
