OMG OMG OMG OMG OMG
I take it that’s a good sign 
yeaa mate … thnks a million …
You’re welcome
Check it survives a reboot though.
There may also be a fix for the “unable to connect to dbus” message if that still comes up after a reboot.
Check it survives a reboot though.
oh yea … ur right !!! il do tht ryt away …
There may also be a fix for the “unable to connect to dbus” message if that still comes up after a reboot.
Not that it stops anything working though … just an annoyance really.
–
i rebooted … the wireless works fine … thnks a million…
and u r right … i still get the error msg …
Do you wanna try fix it, or are you happy to just ignore that message ?
for future reference -
the possible fix is in n post #2 here:
http://www.backtrack-linux.org/forums/showthread.php?t=41769
But there’s always the risk it may break things again … I doubt it, but you never know 
for future reference - the possible fix is in n post #2 here: http://www.backtrack-linux.org/forums/showthread.php?t=41769 But there's always the risk it may break things again .. I doubt it, but you never know ;)
ok … wat do u suggest ???
This is why I gave up on wicd - it used to be awesome, better than Gnome’s network manager, but not so much anymore. I’ve been happily using the inbuilt network manager since about Ubuntu 11.10.
If it hadn’t have been working, I’d have suggested removing wicd & installing network-manager (if it’s not already installed)
@ ezee_2011
OK, let’s give it a shot … run:
sudo dpkg-reconfigure wicd
then
sudo update-rc.d wicd defaults
now see if you still get the message after a reboot.
Remember, if wireless stops working again, change the wicd network interface setting to eth1 and rescan for networks
–
@ chemicalfan
wicd still works, just requires some tweaking now in recent distros (13.04 for example) … the main issue here was wireless drivers, not so much wicd.
networkmanager was going to be my next suggestion, had we not got wicd working
I use network manager all the time, but have no idea why backtrack went for wicd … maybe backtrack didn’t want all the networkmanager gnome dependencies for some reason
–
Yeah, damn Broadcom chipset (and I thought Atheros was bad!!)
Good point about the dependencies though - when I used to run Arch with XFCE, I went with wicd to avoid extra dependencies. I’d have though BackTrack, being based on Ubuntu, probably had them all anyway though?
WHAT … you mean there’s actually life outside Peppermint’s Ubutnu/LXDE … well I never
Haha, I’ve actually never used Peppermint :-[
Read about it on Distrowatch though 
Im sorry i din see ur reply here … i got a notification kinda late cuz my service was down …
so il try the codes u gav me …
OK, let's give it a shot .. run: Code: [Select]sudo dpkg-reconfigure wicd
then
Code: [Select]sudo update-rc.d wicd defaults
now see if you still get the message after a reboot.
Remember, if wireless stops working again, change the wicd network interface setting to eth1 and rescan for networks
–
Mark, this totally worked … also to let u kno tht the wireless did not stop wrking … the prefrences were still the same …
Mad props to you Mark !!!
Another question i have for u is, do you think by any chance the whole troubleshooting tht we did could by any ways cause another application or service to stop working ?? ?? ?? …
I suppose it’s possible … we did change the kernel headers and Backtrack may use modified ones … why what’s broken ?
I have no clue wats wrong … but today wen i went for my classes my professor informed tht there have been some major chnges tht have caused some services to function otherwise…
he informed tht maybe i should update the services …
Would the following codes update the services ???
sudo apt-get update
sudo apt-get upgrade
Could you pls throw some light on what exctly does it do ?? ? ?
update and upgrade will update any older packages with the newer versions.
If he’s saying there are some broken services, we’d need to know what exactly ? … kinda hard to fix something if we don’t know what’s broken.
Ask him to clarify what he’s expecting, and what isn’t working as expected.