New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error, Kali 2016 Rolling Release #11

Closed
lgcambero opened this Issue Apr 17, 2016 · 31 comments

Comments

Projects
None yet
4 participants
@lgcambero

lgcambero commented Apr 17, 2016

screenshot from 2016-04-17 17-14-14
Thanks!!

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 18, 2016

Collaborator

Hey @lgcambero,

It seems like it can't pull the right version. This may be do to a few things, could you please do a "git pull" and re-run the ./Setup.sh script and report back with any issues? Or have you done this already?

Collaborator

killswitch-GUI commented Apr 18, 2016

Hey @lgcambero,

It seems like it can't pull the right version. This may be do to a few things, could you please do a "git pull" and re-run the ./Setup.sh script and report back with any issues? Or have you done this already?

@killswitch-GUI killswitch-GUI added the bug label Apr 18, 2016

@lgcambero

This comment has been minimized.

Show comment
Hide comment
@lgcambero

lgcambero Apr 18, 2016

I did everything as you indicated, but the error remains the same, any other ideas? please help me, I need the tool to the next class. :(

lgcambero commented Apr 18, 2016

I did everything as you indicated, but the error remains the same, any other ideas? please help me, I need the tool to the next class. :(

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 18, 2016

Collaborator

Yea in some rare cases Git could clober the repo. As of right now on a Kali 2.0 out of the box SimplyEmail runs and starts up. Please try to
rm -rf SimplyEmail repo
&
git clone https://github.com/killswitch-GUI/SimplyEmail.git
than go ahead and try to run:
./SimplyEmail.py -l

If this does not work we can dig deeper. Some times its something simple, if not I will download the rolling release

Collaborator

killswitch-GUI commented Apr 18, 2016

Yea in some rare cases Git could clober the repo. As of right now on a Kali 2.0 out of the box SimplyEmail runs and starts up. Please try to
rm -rf SimplyEmail repo
&
git clone https://github.com/killswitch-GUI/SimplyEmail.git
than go ahead and try to run:
./SimplyEmail.py -l

If this does not work we can dig deeper. Some times its something simple, if not I will download the rolling release

@lgcambero

This comment has been minimized.

Show comment
Hide comment
@lgcambero

lgcambero Apr 18, 2016

I am losing hope...

sin titulo

lgcambero commented Apr 18, 2016

I am losing hope...

sin titulo

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 18, 2016

Collaborator

Which one are you on so I can reproduce: https://www.kali.org/downloads/

Dont worry lol, prob a package issue with rolling Debian.

Collaborator

killswitch-GUI commented Apr 18, 2016

Which one are you on so I can reproduce: https://www.kali.org/downloads/

Dont worry lol, prob a package issue with rolling Debian.

@lgcambero

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 18, 2016

Collaborator

Downloading now will report back with a fix.

Collaborator

killswitch-GUI commented Apr 18, 2016

Downloading now will report back with a fix.

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 18, 2016

Collaborator

@lgcambero please run:
uname -a and report back with the results. As of right now on a clean image and install I can not reproduce the issue. Also make sure you
apt-get update
apt-get upgrade
and test as well

Collaborator

killswitch-GUI commented Apr 18, 2016

@lgcambero please run:
uname -a and report back with the results. As of right now on a clean image and install I can not reproduce the issue. Also make sure you
apt-get update
apt-get upgrade
and test as well

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 18, 2016

Collaborator

Pip has had issues in the past, maybe re install PIP
pip install -U pip
and try pip install configparser --upgrade

Collaborator

killswitch-GUI commented Apr 18, 2016

Pip has had issues in the past, maybe re install PIP
pip install -U pip
and try pip install configparser --upgrade

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 18, 2016

Collaborator

Im thinking you cant read the SimplyEmail.ini

Collaborator

killswitch-GUI commented Apr 18, 2016

Im thinking you cant read the SimplyEmail.ini

@lgcambero

This comment has been minimized.

Show comment
Hide comment
@lgcambero

lgcambero Apr 19, 2016

Thanks for the help, none of the answers work for me. I have everything updated. The error persists.
sin titulo

lgcambero commented Apr 19, 2016

Thanks for the help, none of the answers work for me. I have everything updated. The error persists.
sin titulo

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 19, 2016

Collaborator

@lgcambero at this point I don’t know how to reproduce the error your receiving. I’m thinking it may be environmental to a setting or package installed on your system that I cant reproduce. If possible could you try a clean install of the rolling Kali or Debian image. I have tested on all 3 clean distros with no issues. Im sorry I couldn’t figure out what was causing this!

Collaborator

killswitch-GUI commented Apr 19, 2016

@lgcambero at this point I don’t know how to reproduce the error your receiving. I’m thinking it may be environmental to a setting or package installed on your system that I cant reproduce. If possible could you try a clean install of the rolling Kali or Debian image. I have tested on all 3 clean distros with no issues. Im sorry I couldn’t figure out what was causing this!

@JeffBolle

This comment has been minimized.

Show comment
Hide comment
@JeffBolle

JeffBolle Apr 20, 2016

I believe this has to do with some of the dependencies. I was having this issue this morning with Pillow. Once I fixed that it installed, though it still doesn't actually run properly.

JeffBolle commented Apr 20, 2016

I believe this has to do with some of the dependencies. I was having this issue this morning with Pillow. Once I fixed that it installed, though it still doesn't actually run properly.

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 20, 2016

Collaborator

@FastandLight Yes this just took place for me too. It has to do with Pillow not installing properly. Hunting it down at lunch today! Thanks for the report.

Collaborator

killswitch-GUI commented Apr 20, 2016

@FastandLight Yes this just took place for me too. It has to do with Pillow not installing properly. Hunting it down at lunch today! Thanks for the report.

@lgcambero

This comment has been minimized.

Show comment
Hide comment
@lgcambero

lgcambero Apr 20, 2016

Good news, I await the solution...

2016-04-20 12:19 GMT-03:00 Alexander Rymdeko-Harvey <
notifications@github.com>:

@FastandLight https://github.com/FastandLight Yes this just took place
for me too. It has to do with Pillow not installing properly. Hunting it
down at lunch today! Thats for the report.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#11 (comment)

lgcambero commented Apr 20, 2016

Good news, I await the solution...

2016-04-20 12:19 GMT-03:00 Alexander Rymdeko-Harvey <
notifications@github.com>:

@FastandLight https://github.com/FastandLight Yes this just took place
for me too. It has to do with Pillow not installing properly. Hunting it
down at lunch today! Thats for the report.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#11 (comment)

@JeffBolle

This comment has been minimized.

Show comment
Hide comment
@JeffBolle

JeffBolle Apr 20, 2016

The following worked for me to get Pillow installed.

sudo apt-get install python-dev python-setuptools libtiff5-dev  zlib1g-dev libfreetype6-dev liblcms2-dev libwebp-dev tcl8.6-dev tk8.6-dev python-tk
pip install --upgrade Pillow

Then Setup.sh was able to complete successfully, but after that, it still doesn't run right:

image

JeffBolle commented Apr 20, 2016

The following worked for me to get Pillow installed.

sudo apt-get install python-dev python-setuptools libtiff5-dev  zlib1g-dev libfreetype6-dev liblcms2-dev libwebp-dev tcl8.6-dev tk8.6-dev python-tk
pip install --upgrade Pillow

Then Setup.sh was able to complete successfully, but after that, it still doesn't run right:

image

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 20, 2016

Collaborator

@FastandLight fixed the pillow install issues which are new. Still cant reproduce this error.. are you on kali 2.0?

Collaborator

killswitch-GUI commented Apr 20, 2016

@FastandLight fixed the pillow install issues which are new. Still cant reproduce this error.. are you on kali 2.0?

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 20, 2016

Collaborator

@FastandLight please, rm -rf the dir, clone SimplyEmail, run the setup.sh script and try to run
python2.7 ./SimplyEmail.py -l
Thanks!

Collaborator

killswitch-GUI commented Apr 20, 2016

@FastandLight please, rm -rf the dir, clone SimplyEmail, run the setup.sh script and try to run
python2.7 ./SimplyEmail.py -l
Thanks!

@JeffBolle

This comment has been minimized.

Show comment
Hide comment
@JeffBolle

JeffBolle Apr 20, 2016

Kali-rolling.

I just stood up a clean VM from the download image (without updating) to try things out. Was still broken. I'll try your fix in just a minute.

JeffBolle commented Apr 20, 2016

Kali-rolling.

I just stood up a clean VM from the download image (without updating) to try things out. Was still broken. I'll try your fix in just a minute.

@JeffBolle

This comment has been minimized.

Show comment
Hide comment
@JeffBolle

JeffBolle Apr 20, 2016

Works now. I'll try on my fully updated machine in a moment.

JeffBolle commented Apr 20, 2016

Works now. I'll try on my fully updated machine in a moment.

@JeffBolle

This comment has been minimized.

Show comment
Hide comment
@JeffBolle

JeffBolle Apr 20, 2016

Still broken on my fully up to date Kali image. I'm going to take a snapshot of my working one, update, and see what happens.

JeffBolle commented Apr 20, 2016

Still broken on my fully up to date Kali image. I'm going to take a snapshot of my working one, update, and see what happens.

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 20, 2016

Collaborator

@FastandLight ok sounds good, this is tracing back to the python-pptx module. Its weired how it works fine for all my boxes, even the download from Kali-rolling (VM)

Collaborator

killswitch-GUI commented Apr 20, 2016

@FastandLight ok sounds good, this is tracing back to the python-pptx module. Its weired how it works fine for all my boxes, even the download from Kali-rolling (VM)

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 20, 2016

Collaborator

I just cloned and it worked. Doing full apt-get update/upgrade now

Collaborator

killswitch-GUI commented Apr 20, 2016

I just cloned and it worked. Doing full apt-get update/upgrade now

@JeffBolle

This comment has been minimized.

Show comment
Hide comment
@JeffBolle

JeffBolle Apr 20, 2016

Yeah, I think one of the dependencies gets impacted by a newer version or something when updating.

JeffBolle commented Apr 20, 2016

Yeah, I think one of the dependencies gets impacted by a newer version or something when updating.

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 20, 2016

Collaborator

After the Update it still wored fine. Maybe I need to update/upgrade than try to install

Collaborator

killswitch-GUI commented Apr 20, 2016

After the Update it still wored fine. Maybe I need to update/upgrade than try to install

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 20, 2016

Collaborator

Finally got the issue to produce. Looking into the regression now

Collaborator

killswitch-GUI commented Apr 20, 2016

Finally got the issue to produce. Looking into the regression now

@JeffBolle

This comment has been minimized.

Show comment
Hide comment
@JeffBolle

JeffBolle Apr 20, 2016

Glad to know we weren't crazy.

JeffBolle commented Apr 20, 2016

Glad to know we weren't crazy.

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 20, 2016

Collaborator

@FastandLight @lgcambero Please git pull and re run Setup.sh script!

It appears that during apt-get dist-upgrade that Kali-rr installs the configparser from the apt package. After testing this issue out it appears it can be fixed by first removing config parser: sudo apt-get remove python-configparser. Turns out this was a isolated issue to Kali, since they install configparser during install to python 2.7.11+ in the last dist update. This caused pip to think it was installed and not installing during setup. I will be reporting this bug to Kali as well, thanks for bearing with me on this guys!

Please let me know!

Collaborator

killswitch-GUI commented Apr 20, 2016

@FastandLight @lgcambero Please git pull and re run Setup.sh script!

It appears that during apt-get dist-upgrade that Kali-rr installs the configparser from the apt package. After testing this issue out it appears it can be fixed by first removing config parser: sudo apt-get remove python-configparser. Turns out this was a isolated issue to Kali, since they install configparser during install to python 2.7.11+ in the last dist update. This caused pip to think it was installed and not installing during setup. I will be reporting this bug to Kali as well, thanks for bearing with me on this guys!

Please let me know!

@rhertzog

This comment has been minimized.

Show comment
Hide comment
@rhertzog

rhertzog Apr 21, 2016

I think you have not yet found the root cause of your issue. I would look into incompatibilities between what you install with pip and what gets installed via the debian packaging system. Best to not use pip outside of virtualenv! (https://bugs.kali.org/view.php?id=3245 is the report made by @killswitch-GUI on Kali but I can't reproduce the alleged problem)

rhertzog commented Apr 21, 2016

I think you have not yet found the root cause of your issue. I would look into incompatibilities between what you install with pip and what gets installed via the debian packaging system. Best to not use pip outside of virtualenv! (https://bugs.kali.org/view.php?id=3245 is the report made by @killswitch-GUI on Kali but I can't reproduce the alleged problem)

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI Apr 23, 2016

Collaborator

@lgcambero @FastandLight Issues has been confirmed by Kali. At this point unistall python-futures, remove python-configparser. @rhertzog thanks for getting this issue raised

Collaborator

killswitch-GUI commented Apr 23, 2016

@lgcambero @FastandLight Issues has been confirmed by Kali. At this point unistall python-futures, remove python-configparser. @rhertzog thanks for getting this issue raised

@killswitch-GUI

This comment has been minimized.

Show comment
Hide comment
@killswitch-GUI

killswitch-GUI May 11, 2016

Collaborator

This issue had been fixed in python futures! Closing issue.

Collaborator

killswitch-GUI commented May 11, 2016

This issue had been fixed in python futures! Closing issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment