Crouton: Chroot Setup Issue For Kali-Rolling

[dethslayer999]

name: kali-rolling
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/kali-rolling...
crouton: version 1-20190902190258~master:9a594a66
release: kali-rolling
architecture: amd64
xmethod: xorg
targets: xfce
host: version 12371.75.0 (Official Build) stable-channel snappy 
kernel: Linux localhost 4.4.186-16721-gcdc0ab99cc00 #1 SMP PREEMPT Wed Sep 25 23:41:02 PDT 2019 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/kali-rolling...
name: xenial
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/xenial...
crouton: version 1-20190902190258~master:9a594a66
release: xenial
architecture: amd64
xmethod: xorg
targets: xfce
host: version 12371.75.0 (Official Build) stable-channel snappy 
kernel: Linux localhost 4.4.186-16721-gcdc0ab99cc00 #1 SMP PREEMPT Wed Sep 25 23:41:02 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...

So when i tried reinstalling Kali Rolling It Give's Me This Error

Package xbindkeys is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'xbindkeys' has no installation candidate
Failed to complete chroot setup.
The chroot setup script may be broken. Your chroot is not fully configured.
Removing the chroot setup script. You may want to update your chroot again.
UID 1000 not found in kali-rolling
Unmounting /mnt/stateful_partition/crouton/chroots/kali-rolling...

Well all i really Did Was

sudo sh -e ~/Downloads/crouton -r kali-rolling -t xfce
and i have tried removing the -e still same stuff

[spaceinvators]

Same issue after a wipe... Very frustrating

[tdugger]

Hitting same issue. I could swear that it was working fine on Oct 7 and then started failing on Oct 8. I was doing the install many times with different -t options and then suddenly what worked no longer worked on Oct. 8.

[tdugger]

installing xenial/unity works fine.
$ sudo sh ~/Downloads/crouton -r xenial -t unity
I think something changed in kali-rolling that caused this recently.

[Tuxerito]

Same error installing Debian Bullseye + XFCE

[spaceinvators]

Any update?

[Rimulator]

Any way to install build from month ago until this gets resolved?

E: Package 'xbindkeys' has no installation candidate
Failed to complete chroot setup.
Unmounting /mnt/stateful_partition/crouton/chroots/KALI...

[mstair]

Until this gets addressed (xbindkeys pkg seems like got removed from a repo), a workaround to get kali installed (kali-last-snapshot, which has a timestamp of 20190823 at http://archive.linux.duke.edu/kalilinux/kali/dists/ as of writing).

It may be easier to just fork/clone and make changes below, I just made changes inline...

Find one of the recent crouton cache dirs under /tmp/crouton-installer-cache (/tmp/crouton-installer-cache/crouton.F8M for examples below).

Sudo and edit /tmp/crouton-installer-cache/crouton.F8M/installer/kali/releases and append kali-last-snapshot.

Then run following from /tmp/crouton-installer-cache dir:
sudo crouton.F8M/installer/main.sh -r kali-last-snapshot -t xfce

I have never installed kali-rolling via crouton before, so not sure if it includes all the tools. I had to run apt-get install kali-linux-all from inside kali-last-snapshot.

[Rimulator]

Anyone know what the mirror URL is for kali crouton builds? Regular mirrors generate platform errors. If we can identify the mirrors, we can use "-m" with an explicit URL to get an older version.

[mstair]

It looks like kali.org, you can export CROUTON_MIRROR_kali env var in the sudo, if you know of a better mirror:

https://github.com/dnschneid/crouton/blob/master/installer/kali/defaults#L23

[spaceinvators]

Do we have a solution :)?

[BlackAssassin]

Until this gets addressed (xbindkeys pkg seems like got removed from a repo), a workaround to get kali installed (kali-last-snapshot, which has a timestamp of 20190823 at http://archive.linux.duke.edu/kalilinux/kali/dists/ as of writing).

It may be easier to just fork/clone and make changes below, I just made changes inline...

Find one of the recent crouton cache dirs under /tmp/crouton-installer-cache (/tmp/crouton-installer-cache/crouton.F8M for examples below).

Sudo and edit /tmp/crouton-installer-cache/crouton.F8M/installer/kali/releases and append kali-last-snapshot.

Then run following from /tmp/crouton-installer-cache dir:
sudo crouton.F8M/installer/main.sh -r kali-last-snapshot -t xfce

I have never installed kali-rolling via crouton before, so not sure if it includes all the tools. I had to run apt-get install kali-linux-all from inside kali-last-snapshot.

Thanks for your method.I've tried it.But It's not work in the last-snap version too.How can fix it?

[stestereichert]

Still no solution to this? Having the same issue

[meanderpaul]

I’m also experiencing this issue. Is there a way we can find the part calling for the xbindkeys and remove it or have the installer ignore it?

[kadenbcampbell]

I'm also having this issue. Has anyone found a solution?

[cLussE]

I'm having this same issue, any solutions yet?

[e636]

I’m also having same issue. Any solutions?

[RomHtK]

I didn't understand, I thought it was coming from me because I had installed the Mrchromebox firmware and changed the size of the SSD partitions to test the dual-boot
So for the moment it's due to a missing package.

[skilfoy]

I'm having the same issue! Any help would be greatly appreciated.

[Rimulator]

Seems like we need to collectively mirror this image. Can we collectively
determine a build process? I can host everything.

On Thu, Nov 14, 2019 at 11:53 PM skilfoy [e-mail] wrote:

I'm having the same issue! Any help would be greatly appreciated.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/4153?email_source=notifications&email_token=AAZ4SDSIEIOYV3CUVQZRB6LQTYTOFA5CNFSM4I73NY22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEEJTWQ#issuecomment-554211802,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZ4SDV2CVUQ5VA5G4KP6ALQTYTOFANCNFSM4I73NY2Q
.

[skilfoy]

Getting a bit desperate here. The USB stick I put Kali on works for my Mac but not on my Chromebook... It'd be so much easier if the crouton method worked properly!

[RomHtK]

I just found this https://github.com/dnschneid/crouton/issues/4130#issuecomment-528161403 in another post that was written before this one, there were apparently some concerns with Debian as well.
I'll try this, don't hesitate to come and comment if you try on your side

Original post : https://github.com/dnschneid/crouton/issues/4130

[twonklesDev]

Solution:
Download package based on your architecture using one of the mirrors from the link: https://packages.debian.org/jessie/xbindkeys

sudo enter-chroot -u root -n kali-rolling

sudo apt-get install curl

curl -O "insert bindkeys download here.deb"

install with dpkg

dpkg -i "bindkeys.deb"

continue the install with:

sudo enter-chroot -u root -n kali-rolling

The install should continue now with no issues.

Original post : https://github.com/dnschneid/crouton/issues/4130

Tried and confirmed working.

[Rimulator]

Chromebook packages are AMD64 based.

So . . .

1. [ctrl]+[alt]+t

2. _shell_

SSD. This is to install to an external drive. This gives you the option of as much space as you need and the security that your kali build is on a tiny SD card.

a) _sudo su_
b) _fdisk -l_
c) _umount /dev/sdb1_ (or unmount your removable media)
d) mkfs -t ext4 /dev/sdb1 (or whatever your removable media is)
e) mount /dev/sdb1

• -e = Encryption

• -r = Release

• -t = Target

• -n = Name of chroot
  Note: Don't install xiwi at this point. It might hang the install with a weird error.

• _sudo sh -e ~/Downloads/crouton -r kali-rolling -t xfce -n Kali_

    ~ else ~
  

(if installing to external drive)
SSD. _sudo sh -e ~/Downloads/crouton -r kali-rolling -t xfce -n Kali -p '/media/removable/SD Card'_

1. _sudo enter-chroot -n Kali_

     ~ else ~
   

SSD. _sudo enter-chroot -c /media/removable/'SD Card'/chroots -n Kali_ -u root

1. "d"

2. _sudo apt-get install curl_

3. "y"

4. curl -O "http://http.us.debian.org/debian/pool/main/x/xbindkeys/xbindkeys_1.8.6-1_amd64.deb"

5. _dpkg -i "xbindkeys_1.8.6-1_amd64.deb"_

Note: error messages from missing dependencies. Skip 10, 11 and 12 if you don't see these messages.

1. _sudo apt-get install xbindkeys_

2. _apt --fix-broken install_

3. "Y"

4. (install is not complete here, but close) _exit_

     ~ else ~
   

Close and restart shell, items 1, then 2 above.

1. (Important) _sudo sh -e ~/Downloads/crouton -u -n Kali -t xiwi_

     ~ else ~
   

SSD. _sudo sh -e ~/Downloads/crouton -u -n Kali -t xiwi -p '/media/removable/SD Card'_

1. _sudo enter-chroot -n Kali_

     ~ else ~
   

SSD. _sudo enter-chroot -n Kali -c /media/removable/'SD Card'/chroots_

1. _sudo su apt-get update_

2. _sudo su apt-get upgrade_

3. (If you have space, like Google Pixel Go, Pixelbook, older HP Chromebook G1) _sudo apt-get install kali-linux-full_ (about 30 minutes and 7gb)

     ~ else ~
   

• _sudo apt-get install nmap_

• _sudo apt-get install metasploit-framework_

• _sudo apt-get install nikto_

1. "Y"

2. sudo startxfce4 -n Kali_

     ~ else ~
   

SSD. sudo startxfce4 -n nameofchroot -c /media/removable/'SD Card'/chroots_

1. Enjoy.

Credit to twonklesDev for this working install. Strange that the kali linux crouton as installed is an old, almost unsupported version.

https://github.com/dnschneid/crouton/wiki/Kali

[spaceinvators]

Chromebook packages are AMD64 based.

So . . .

1. [ctrl]+[alt]+t
2. _shell_

SSD. This is to install to an external drive. This gives you the option of as much space as you need and the security that your kali build is on a tiny SD card.

a) _sudo su_
b) _fdisk -l_
c) _umount /dev/sdb1_ (or unmount your removable media)
d) mkfs -t ext4 /dev/sdb1 (or whatever your removable media is)
e) mount /dev/sdb1

• -e = Encryption
• -r = Release
• -t = Target
• -n = Name of chroot
  Note: Don't install xiwi at this point. It might hang the install with a weird error.

1. _sudo sh -e ~/Downloads/crouton -r kali-rolling -t xfce -n Kali_
   ~ else ~

(if installing to external drive)
SSD. _sudo sh -e ~/Downloads/crouton -r kali-rolling -t xfce -n Kali -p '/media/removable/SD Card'_

1. _sudo enter-chroot -n Kali_
   ~ else ~

SSD. _sudo enter-chroot -c /media/removable/'SD Card'/chroots -n Kali_ -u root

1. "d"
2. _sudo apt-get install curl_
3. "y"
4. curl -O "http://http.us.debian.org/debian/pool/main/x/xbindkeys/xbindkeys_1.8.6-1_amd64.deb"
5. _dpkg -i "xbindkeys_1.8.6-1_amd64.deb"_

Note: error messages from missing dependencies. Skip 10, 11 and 12 if you don't see these messages.

1. _sudo apt-get install xbindkeys_
2. _apt --fix-broken install_
3. "Y"
4. (install is not complete here, but close) _exit_
   ~ else ~

Close and restart shell, items 1, then 2 above.

1. (Important) _sudo sh -e ~/Downloads/crouton -u -n Kali -t xiwi_
   ~ else ~

SSD. _sudo sh -e ~/Downloads/crouton -u -n Kali -t xiwi -p '/media/removable/SD Card'_

1. _sudo enter-chroot -n Kali_
   ~ else ~

SSD. _sudo enter-chroot -n Kali -c /media/removable/'SD Card'/chroots_

1. _sudo su apt-get update_
2. _sudo su apt-get upgrade_
3. (If you have space, like Google Pixel Go, Pixelbook, older HP Chromebook G1) _sudo apt-get install kali-linux-full_ (about 30 minutes and 7gb)
   ~ else ~

• _sudo apt-get install nmap_
• _sudo apt-get install metasploit-framework_
• _sudo apt-get install nikto_

1. "Y"
2. sudo startxfce4 -n Kali_
   ~ else ~

SSD. sudo startxfce4 -n nameofchroot -c /media/removable/'SD Card'/chroots_

1. Enjoy.

Credit to twonklesDev for this working install. Strange that the kali linux crouton as installed is an old, almost unsupported version.

https://github.com/dnschneid/crouton/wiki/Kali

Still not working, after step 5: UID 1000 not found
Any help?

[Anonymoustank]

How I got Kali-Rolling amd64 with Xfce working:

1. sudo crouton -r kali-rolling -t audio,core

2. sudo enter-chroot -n kali-rolling

   a. sudo apt install curl

   b. sudo curl -O "http://http.us.debian.org/debian/pool/main/x/xbindkeys/xbindkeys_1.8.6-1_amd64.deb"

   c. sudo apt install ./xbindkeys*

   d. exit

3. sudo crouton -r kali-rolling -t xfce -u

[wi1helmz]

How I got Kali-Rolling amd64 with Xfce working:

1. sudo crouton -r kali-rolling -t audio,core
2. sudo enter-chroot -n kali-rolling
   a. sudo apt install curl
   b. sudo curl -O "http://http.us.debian.org/debian/pool/main/x/xbindkeys/xbindkeys_1.8.6-1_amd64.deb"
   c. sudo apt install ./xbindkeys*
   d. exit
3. sudo crouton -r kali-rolling -t xfce -u

That's working perfectly!

[thatonetechdude]

@Anonymoustank thank you so much, I have been waiting for over half a monthe too get the darn thing installed and you gave it the last push it needed thank you so much!

[Anonymoustank]

No problem :)

[thatonetechdude]

@Anonymoustank I must simply ask, are you tech jesus? You solved my problem with 1 short post thank you so much.

[cserg8621]

Life saver

[tdugger]

After doing the install steps provided above (thanks @Anonymoustank) what's the best way to install all the kali linux tools? I'm trying to mimick what is in the offensive security's virtualbox image. https://www.offensive-security.com/kali-linux-vm-vmware-virtualbox-image-download/
Is the katoolin something you guys use? https://www.tecmint.com/install-kali-linux-tools-using-katoolin-on-ubuntu-debian/
Thanks.

[cserg8621]

The Katoolin is actually a headache to use IMO

On Sat, Dec 7, 2019, 1:34 PM T [e-mail] wrote:

After doing the install steps provided above (thanks @Anonymoustank
https://github.com/Anonymoustank) what's the best way to install all
the kali linux tools? I'm trying to mimick what is in the offensive
security's virtualbox image.
https://www.offensive-security.com/kali-linux-vm-vmware-virtualbox-image-download/
Is the katoolin something you guys use?
https://www.tecmint.com/install-kali-linux-tools-using-katoolin-on-ubuntu-debian/
Thanks.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/4153?email_source=notifications&email_token=ANVBNB4F5CXTN52CA3ZHKN3QXPUCDA5CNFSM4I73NY22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGGMXZY#issuecomment-562875367,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANVBNB2XJ3UZP6HDPA3UPPLQXPUCDANCNFSM4I73NY2Q
.

[tdugger]

The Katoolin is actually a headache to use IMO

Thanks for the reply @cserg8621.

How would you suggest to install all the kali tools then? After following anonymoustank's steps, the tools don't show up in the Applications menu like it does in the virtualbox image from OS.

[Rimulator]

This is an installation option

sudo su apt-get update
sudo su apt-get upgrade
(If you have space, like Google Pixel Go, Pixelbook, older HP Chromebook G1) sudo apt-get install kali-linux-full (about 30 minutes and 7gb)
~ else ~
sudo apt-get install nmap
sudo apt-get install metasploit-framework
sudo apt-get install nikto

[Rimulator]

sudo su
git clone https://github.com/LionSec/katoolin.git && cp katoolin/katoolin.py /usr/bin/katoolin
chmod +x /usr/bin/katoolin
sudo katoolin

[tdugger]

Thanks @Rimulator

Anyone know the window manager that is used by the offensive security's virtualbox kali linux image?

It's nice cause all the tools are on the menu and categorized. I'm assuming after installing kali-linux-full that the tools won't be in a menu like this.

[Rimulator]

You are right. We will want . .

1. Encrypted Kali on Chromebook
2. All tools
3. Easy navigation, like the VMWARE image
4. Disposable - installation to external SD card, external encryption key, no PII on image, key or decryption tied to MAC or hardware specific data and user specific data

So, we have #1 and possibly #2. #3 just needs documentation and testing. #4 needs to be investigated.

Bonus - how do we clean up the desktop folders to a dozen drives that don't exist?

Should we fork this as a separate project?

[tdugger]

That's exactly what I'm looking for. And definitely #4. I did some searching on #4 and didn't find how to put a chroot on an SD card. For #3, we probably want to get in touch with someone at offensive security. Maybe they have a script that creates these menus or someone just did it once and done.

[tdugger]

Also, I tried to do the sudo apt-get install kali-linux-full command and it churned for awhile and then failed at installing maltego.

[HPchrome]

Still i have the same problem, after sudo sh -e ~/Downloads/crouton -r kali-rolling -t xfce -n Kali have

E: Package 'xbindkeys' has no installation candidate

i m not installing on external drive.
Which code should i enter ?

[DennisLfromGA]

@HPchrome,

Did you run steps 2 & up in this comment?

• https://github.com/dnschneid/crouton/issues/4153#issuecomment-560190450

Hope this helps,
-DennisLfromGA

[HPchrome]

Ok... maybe i write so short about the steps that reproduce this problem.

1. I Open my browser and press ctrl+alt+t
2. shell
3. sudo su
4. sudo sh -e ~/Downloads/crouton -r kali-rolling -t xfce -n Kali
   after some time

E: Package 'xbindkeys' has no installation candidate

and here i stop with the installation.
On this command sudo edit-chroot -all it gave

name: Kali
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/Kali...
WARNING: Unable to register core dump handler.
crouton: version 1-20190902190258~master:9a594a66
release: kali-rolling
architecture: amd64
xmethod: xorg
targets: xfce
host: version 12739.4.0 (Official Build) dev-channel setzer
kernel: Linux localhost 3.18.0-19937-g5da699e3897c #1 SMP PREEMPT Tue Dec 10 00:01:28 PST 2019 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/Kali...

how can i continue with installation and to have a Kali...?
or maybe steps that i`m doing are not correct and please explain more.
Which command should i use to continue?

[DennisLfromGA]

@HPchrome,

I'll ask again -

• Did you run steps 2 & up in this comment?
• 
  
  • #4153 (comment)
  
  

Hope this helps,
-DennisLfromGA

[HPchrome]

@DennisLfromGA
Sorry,
in browser shell gave

chronos@localhost / $ sudo crouton -r kali-rolling -t audio,core
sudo: crouton: command not found

and

chronos@localhost / $ sudo enter-chroot -n kali-rolling
/mnt/stateful_partition/crouton/chroots/kali-rolling not found.

[Rimulator]

Try this - https://github.com/dnschneid/crouton/issues/4153#issuecomment-555943965

My answer is longer than some of the other solutions, but it is the same. Do not skip any steps.

When complete, do this - https://github.com/dnschneid/crouton/issues/4153#issuecomment-562892794

[thatonetechdude]

@HPchrome you must install "http://http.us.debian.org/debian/pool/main/x/xbindkeys/xbindkeys_1.8.6-1_amd64.deb"
from @Anonymoustank previous comment, then run sudo sh -e ~/Downloads/crouton -r kali-rolling -t xfce -n Kali

[HPchrome]

@Rimulator

chronos@localhost / $ sudo su
localhost / # fdisk -l
Disk /dev/loop0: 3.1 GiB, 3312095232 bytes, 6468936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop1: 407.5 MiB, 427315200 bytes, 834600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop2: 4 KiB, 4096 bytes, 8 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop3: 4 KiB, 4096 bytes, 8 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop4: 49.6 MiB, 51994624 bytes, 101552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop5: 415.6 MiB, 435802112 bytes, 851176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mmcblk0: 14.7 GiB, 15758000128 bytes, 30777344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 83B0C87C-47E7-134B-AFEE-6C72D3348DC9

Device Start End Sectors Size Type
/dev/mmcblk0p1 8704000 30744575 22040576 10.5G Microsoft basic data
/dev/mmcblk0p2 20480 53247 32768 16M ChromeOS kernel
/dev/mmcblk0p3 4509696 8703999 4194304 2G ChromeOS root fs
/dev/mmcblk0p4 53248 86015 32768 16M ChromeOS kernel
/dev/mmcblk0p5 315392 4509695 4194304 2G ChromeOS root fs
/dev/mmcblk0p6 16448 16448 1 512B ChromeOS kernel
/dev/mmcblk0p7 16449 16449 1 512B ChromeOS root fs
/dev/mmcblk0p8 86016 118783 32768 16M Microsoft basic data
/dev/mmcblk0p9 16450 16450 1 512B ChromeOS reserved
/dev/mmcblk0p10 16451 16451 1 512B ChromeOS reserved
/dev/mmcblk0p11 64 16447 16384 8M unknown
/dev/mmcblk0p12 249856 315391 65536 32M EFI System

Partition table entries are not in disk order.

Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/dm-0: 2 GiB, 2087714816 bytes, 509696 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mapper/encstateful: 3.1 GiB, 3312095232 bytes, 6468936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/F8BFEC3E073D0AD3DB85885D427CD20B4E14527BB6E5C1653A5EC4BA6B41DEDF: 412.4 MiB, 432390144 bytes, 105564 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
localhost / # umount /dev/sdb1
umount: /dev/sdb1: no mount point specified.

what to umount ?

@thatonetechdude

chronos@localhost / $ sudo apt install curl
sudo: apt: command not found
chronos@localhost / $ sudo curl -O "http://http.us.debian.org/debian/pool/main/x/xbindkeys/xbindkeys_1.8.6-1_amd64.deb"
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Warning: Failed to create the file xbindkeys_1.8.6-1_amd64.deb: Read-only file
Warning: system
3 37136 3 1230 0 0 1194 0 0:00:31 0:00:01 0:00:30 1940
curl: (23) Failed writing body (0 != 1230)
chronos@localhost / $ sudo apt install ./xbindkeys*
sudo: apt: command not found

[Rimulator]

What kind of machine is this? What OSes are installed?

[HPchrome]

hp chromebook model 11-v001nd about OS i only know that run chrome OS i made power wash recently before that i only installed ubuntu as same way as i want to install Kali now.

[n5q]

How I got Kali-Rolling amd64 with Xfce working:

1. sudo crouton -r kali-rolling -t audio,core
2. sudo enter-chroot -n kali-rolling
   a. sudo apt install curl
   b. sudo curl -O "http://http.us.debian.org/debian/pool/main/x/xbindkeys/xbindkeys_1.8.6-1_amd64.deb"
   c. sudo apt install ./xbindkeys*
   d. exit
3. sudo crouton -r kali-rolling -t xfce -u

Thanks, this works for me

[DennisLfromGA]

Closing. Please re-open if this issue is still a concern.

[jeffvader90]

@NasifQadri How did you get the xbindkeys deb package to install? I tried using apt, dpkg and I also forced it with dpkg but I kept getting an error. I have tried everything suggested in this thread and no luck.

[Rimulator]

There are a dozen working examples herein, each describing how the package and dependencies were installed. Specifically which set of instructions did you carefully follow?

[GunnerBasil]

@Anonymoustank when I run the sudo enter-chroot, my terminal prompt changes from:

chronos@localhost / $
to
(kali-rolling)gunnerbasil@localhost:~$

I thought that this would open kali-rolling like it opened xfce, as a desktop, but instead it is just a prompt. is this supposed to happen? How would I be able to make it a desktop?

[GunnerBasil]

I made a reddit post about it: https://www.reddit.com/r/Crouton/comments/enfcwf/clarification_and_questions_regarding_kali_linux/

[GunnerBasil]

never mind, I was just stoopid.