<!-- READ THE FOLLOWING FIRST:

Also read the FAQ: https://faq.octoprint.org

This is a bug and feature tracker, please only use it to report bugs or request features within OctoPi. If its not a bug please use the community forum: https://discourse.octoprint.org/

Do not seek support here ("I need help with ...", "I have a question ..."), that belongs on the community forum at discourse.octoprint.org, NOT here.

Mark requests with a "[Request]" prefix in the title please. For bug reports fully fill out the bug reporting template (if you don't know where to find some information - it's all described in the Contribution Guidelines linked up there in the big yellow box).

When reporting a bug do not delete any lines from the template. Its here to help you report relevant information, and the help text will not be displayed.

Thank you! -->

What were you doing?

<!-- Please be as specific as possible here. The maintainers will need to reproduce your issue in order to fix it and that is not possible if they don't know what you did to get it to happen in the first place.

Ideally provide exact steps to follow in order to reproduce your problem: -->

1. Unplug Pi from power
2. Plug in TFT ribbon cable to the screen and pi
3. Power on Pi
4. Notice how the wifi doesn't turn on (no ip address appears on the terminal screen)

<!-- If you encountered a problem with specific files of any sorts, make sure to also include a link to a file with which to reproduce the problem. -->

What did you expect to happen?

The pi should boot like normal to connect to wifi

What happened instead?

Whenever I have the TFT screen plugged into the pi when I boot, the wifi just completely turns off with no way to turn it back on

Did the same happen when running OctoPrint in safe mode?

Yes

<!-- Test if you can reproduce your problem in safe mode. You can find information on how to enable safe mode in the Contribution Guidelines.

If you can't reproduce in safe mode, this is a bug with one of your installed third party plugins. Don't open a ticket here!

If you can't test this in safe mode, state why. -->

Version of OctoPi

0.18.0

<!-- Can be found in the lower left corner of the web interface. ALWAYS INCLUDE. -->

Printer model & used firmware incl. version

Creality Ender 3, Klipper

<!-- If applicable, always include if unsure. -->

Screenshot(s)/video(s) showing the problem:

<!-- If applicable. Always include if unsure or reporting UI issues. -->

I have read the FAQ.

I'm using the official raspberry pi 2.5A psu. One thing I noticed was that when I unplugged the screen while it was turned on, the wifi immediately turned back on. I ended up grabbing another pi as I tried multiple different powers (even took some of my high powered type c chargers, converted them to micro USB via an adapter) and the same issue happened, even tried my NAS Pi 4 and it worked just fine with the screen.. I think my pi 3 might be defective

Here are my version, in case it helps (they are the same):

pi@octopi:~$ /home/pi/oprint/bin/python -m pip --version
pip 21.0.1 from /home/pi/oprint/lib/python3.8/site-packages/pip (python 3.8)
pi@octopi:~$ /home/pi/oprint/bin/python --version
Python 3.8.6 

pi@octopi:~$ python3 -m pip --version
pip 21.0.1 from /home/pi/.local/lib/python3.8/site-packages/pip (python 3.8)
pi@octopi:~$ python3 --version
Python 3.8.6 

<!-- READ THE FOLLOWING FIRST:

Also read the FAQ: https://faq.octoprint.org

This is a bug and feature tracker, please only use it to report bugs or request features within OctoPi. If its not a bug please use the community forum: https://discourse.octoprint.org/

Do not seek support here ("I need help with ...", "I have a question ..."), that belongs on the community forum at discourse.octoprint.org, NOT here.

Mark requests with a "[Request]" prefix in the title please. For bug reports fully fill out the bug reporting template (if you don't know where to find some information - it's all described in the Contribution Guidelines linked up there in the big yellow box).

When reporting a bug do not delete any lines from the template. Its here to help you report relevant information, and the help text will not be displayed.

Thank you! -->

What were you doing?

<!-- Please be as specific as possible here. The maintainers will need to reproduce your issue in order to fix it and that is not possible if they don't know what you did to get it to happen in the first place.

Ideally provide exact steps to follow in order to reproduce your problem: -->

1. Unplug Pi from power
2. Plug in TFT ribbon cable to the screen and pi
3. Power on Pi
4. Notice how the wifi doesn't turn on (no ip address appears on the terminal screen)

<!-- If you encountered a problem with specific files of any sorts, make sure to also include a link to a file with which to reproduce the problem. -->

What did you expect to happen?

The pi should boot like normal to connect to wifi

What happened instead?

Whenever I have the TFT screen plugged into the pi when I boot, the wifi just completely turns off with no way to turn it back on

Did the same happen when running OctoPrint in safe mode?

Yes

<!-- Test if you can reproduce your problem in safe mode. You can find information on how to enable safe mode in the Contribution Guidelines.

If you can't reproduce in safe mode, this is a bug with one of your installed third party plugins. Don't open a ticket here!

If you can't test this in safe mode, state why. -->

Version of OctoPi

0.18.0

<!-- Can be found in the lower left corner of the web interface. ALWAYS INCLUDE. -->

Printer model & used firmware incl. version

Creality Ender 3, Klipper

<!-- If applicable, always include if unsure. -->

Screenshot(s)/video(s) showing the problem:

<!-- If applicable. Always include if unsure or reporting UI issues. -->

I have read the FAQ.

@guysoft Negative, the plugin manager isn't involved anymore at this point, that's a failing pip install during intake of a dependency.

@ping-localhost That error seem seems to be from the plugin manager console or something like it might be unrelated.

I think you are right, because when I install the plugin directly through SSH, on the pi account and in the home dir, using pip install "https://github.com/kantlivelong/OctoPrint-PSUControl/archive/master.zip", everything works as expected.

However, I get a massive error when I run the following (which is what OctoPrint runs, but without the no cache dir):

/home/pi/oprint/bin/python -m pip --disable-pip-version-check install https://codeload.github.com/kantlivelong/OctoPrint-PSUControl/zip/master

Error it outputs: https://gist.github.com/ping-localhost/aad12f9619b13deaf5e2d6810407a0f5#file-terminal-log

The build proceeds normally but then provides a “error: Can not find Rust Compiler” message. Debug assistance is provided on the screen but a subsequent message reads “ERROR: Failed building wheel for cryptography” The build gets stuck on “Building wheel for pymacl (PEP 517): still running”. Build fails.