This post is a bad example of a bug report, for several reasons.

1) The title of this vulnerability should probably be "WICD Priv Escalation". As such, it should probably be reported to the WICD...

Your output says it all, a more careful read would have pointed out the issue:

rsync: write failed on "/mnt/sdf1/casper/filesystem.squashfs": No space left on device (28)

Try using +3000M...

We have recently rebuilt the BackTrack forums from scratch, eliminating many issues we had on the way.
The forums should now be much more responsive, and fully functional.
Thanks to all that...

1. brcmsmac injection worked fine on my mac with BT5r2, kernel 3.2.6.
2. b43 can not co-exist with brcmsmac in kernel 3.2.6. If you need to change to b43, check the wiki....

Yeppers. Kernel 3.2.6 has a kernel config which brings back the bluez :)
Please report any bluetooth issues you may have with the 3.2.6 kernel in a new thread.

I've never seen this error before on BT5. Without further info, we cant help you...
For example - have you enabled any other repositories in sources.list ?
Which package failed specifically ?
Try...

That would be a VMWare issue, as opposed to a Backtrack or Kernel issue.

Bugfix committed with unicornscan-0.4.7-bt8. Please apt-get update, apt-get upgrade and report back in this thread, or in redmine.

Make sure you dont have any apps stored on the "external" storage... this solved the issue for me.

in a console, type:

xrandr -s 1024x768


replace 1024x768 with the resolution you need.

What card ,chipset and drivers are you using ?

The RPC portmapper is not required for the normal operation of BackTrack and will be disabled in an upcoming fix and in the next release.

Updated with upgrade #14.

apt-get update
apt-get upgrade

or

apt-get update
apt-get install ncrack

Occasionally while running an apt-get update, you might see messages such as this:



Fetched 188kB in 2s (90.0kB/s)
W: Failed to fetch...

Excellent writeup! Thanks for getting BT5 on more and more devices!

Just a quick reminder...once you are in chroot, the commands:

startvnc

and

stopvnc

Make sure you don't have funky chars in the spk file.

For example ” vs " . Not the same. If in doubt, re-write the spk file from scratch in your favorite editor.

Fixed in linux-firmware-2.0-bt4

apt-get update
apt-get upgrade

please report back if you still have issues with this.

Metasploit has it's own version of ruby which is independent of either ruby1.8 or ruby1.9.2.
I am unclear how you managed to mingle the msf ruby and the BT5 ruby....

Your wireless card will not work in an virtualized environment unless it uses a USB bus.
Please do everyone a favor - SEARCH and READ before posting.

Thanks. What chipset does that card have?

You're doing something horribly wrong.
Remember that during a live session (ie, before you run an install), there is NO root password set.

Install virtualbox manually, not from the repos. We will remove that package form the repos soon.

Thanks!

Once in the chroot, you can simply type:



startvnc
to start the vnc server... and:

i think he is referring to apt....

apt-get install <package name>
apt-cache search <package name>

Try this:

1) At the BackTrack boot menu, choose "Debug mode" (do not hit enter).
2) press tab while the "BackTrack Debug" menu option is selected.
3) Edit the boot parameter, and add a "splash"...