OH BOY. I suspect the problem is a missing driver, so I went looking. I was browsing through the system log and while I am not certain of what I read, the best I can understand is some firmware/driver file is missing. One line in the log says I have to go to this site: http://linuxwireless.org/en/users/Drivers/b43#devicefirmware (A short excerpt from the log is at the bottom of this message) I went there and wish I hadn't. Lordy mercy I can not believe something as simple as a driver requires a PhD in computer gobbledy-gook just to learn how to find/install a missing driver. And all for a ubiquitous generic Broadcom 802.11g network adapter driver that should be packaged with the distro. Somebody please remind me why I wanted to install a Linux distro. I will uninstall and wait a few months to see if they add the driver in the next update. Except for that, so far I really like the look and feel of it. I'll never know the command line as well as I would like to but the GUI is very nice. Much better than Vista. -*-*-*-LOG FILE-*-*-*-* 09/15/2008 06:44:58 PM ubuntu NetworkManager <WARN> nm_device_802_11_wireless_scan(): (wlan0): could not trigger wireless scan: Network is down 09/15/2008 06:45:09 PM ubuntu firmware_helper[6541] main: error loading '/lib/firmware/b43/ucode5.fw' for device /devices/pci0000:00/0000:00:14.4/0000:06:02.0/ssb0:0/firmware/ssb0:0' with driver '(unknown)' 09/15/2008 06:45:09 PM ubuntu kernel [ 285.393154] input: b43-phy0 as /devices/virtual/input/input57 09/15/2008 06:45:09 PM ubuntu kernel [ 285.400292] evdev: no more free evdev devices 09/15/2008 06:45:09 PM ubuntu kernel [ 285.400300] input: failed to attach handler evdev to device input57, error: -23 09/15/2008 06:45:09 PM ubuntu kernel [ 285.418240] b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed. 09/15/2008 06:45:09 PM ubuntu kernel [ 285.418247] b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4). 09/15/2008 06:45:11 PM ubuntu firmware_helper[6549] main: error loading '/lib/firmware/b43/ucode5.fw' for device '/devices/pci0000:00/0000:00:14.4/0000:06:02.0/ssb0:0/firmware/ssb0:0' with driver '(unknown)' 09/15/2008 06:45:11 PM ubuntu kernel [ 286.335278] input: b43-phy0 as /devices/virtual/input/input58 09/15/2008 06:45:11 PM ubuntu kernel [ 286.339796] evdev: no more free evdev devices 09/15/2008 06:45:11 PM ubuntu kernel [ 286.339804] input: failed to attach handler evdev to device input58, error: -23 09/15/2008 06:45:11 PM ubuntu kernel [ 286.357447] b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found or load failed. 09/15/2008 06:45:11 PM ubuntu kernel [ 286.357454] b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the correct firmware (version 4). 09/15/2008 06:45:11 PM ubuntu NetworkManager <WARN> nm_device_802_11_wireless_scan(): (wlan0): could not trigger wireless scan: Network is down *-*-*-*END-*-*-*-* ----- Original Message ----- From: <dsw32952@xxxxxxxxx> To: <pctechtalk@xxxxxxxxxxxxx> Sent: Monday, September 15, 2008 9:51 PM Subject: -=PCTechTalk=- Kubuntu WLAN setup >I opened network settings/configuration and inputted passkey and >SSID. > and left it at Automatic DHCP > I saved the configuration and tried to enable and got an "Error > while listing network interfaces-KDE Control Module" dialog box with > this narrative: > > Could not parse the XML output from the network configuration > backend. > > The only option is an OK button. > > Clicking OK closes the dialog box but does nothing else. > > I've been through this twice. > > I tried disabling the ethernet device with negative results. > > Any ideas? All I can think of is the installation does not have a > drive for the LAN. I navigated to the System/Hardware Drivers > Manager and it reports: "No proprietary drivers are in use on this > system". I can not find the path to a list of drivers in use to see > if one is installed for the WLAN card. > > Don > --------------------------------------------------------------- > Please remember to trim your replies (including this sentence and > everything below it) and adjust the subject line as necessary. > > To unsubscribe or change your email settings: > //www.freelists.org/webpage/pctechtalk > > To access our Archives: > http://groups.yahoo.com/group/PCTechTalk/messages/ > //www.freelists.org/archives/pctechtalk/ > > To contact only the PCTT Mod Squad, write to: > pctechtalk-moderators@xxxxxxxxxxxxx > > To join the PCTableTalk off-topic group, send a blank email to: > pctabletalk+subscribe@xxxxxxxxxxxxxxxx > --------------------------------------------------------------- > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------- Please remember to trim your replies (including this sentence and everything below it) and adjust the subject line as necessary. To unsubscribe or change your email settings: //www.freelists.org/webpage/pctechtalk To access our Archives: http://groups.yahoo.com/group/PCTechTalk/messages/ //www.freelists.org/archives/pctechtalk/ To contact only the PCTT Mod Squad, write to: pctechtalk-moderators@xxxxxxxxxxxxx To join the PCTableTalk off-topic group, send a blank email to: pctabletalk+subscribe@xxxxxxxxxxxxxxxx ---------------------------------------------------------------