Error on start.
See original GitHub issueDescription
What steps will reproduce the problem?
When I switch spyder on it always gives this error.
Traceback
File "C:\ProgramData\Anaconda3\lib\site-packages\psutil\_pswindows.py", line 679, in wrapper
return fun(self, *args, **kwargs)
File "C:\ProgramData\Anaconda3\lib\site-packages\psutil\_pswindows.py", line 868, in send_signal
cext.proc_kill(self.pid)
PermissionError: [WinError 5] Access is denied
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\ProgramData\Anaconda3\lib\site-packages\jupyter_client\manager.py", line 394, in shutdown_kernel
self.finish_shutdown()
File "C:\ProgramData\Anaconda3\lib\site-packages\jupyter_client\manager.py", line 346, in finish_shutdown
self._kill_kernel()
File "C:\ProgramData\Anaconda3\lib\site-packages\spyder\plugins\ipythonconsole\utils\manager.py", line 86, in _kill_kernel
self.kill_proc_tree(self.kernel.pid)
File "C:\ProgramData\Anaconda3\lib\site-packages\spyder\plugins\ipythonconsole\utils\manager.py", line 59, in kill_proc_tree
child_process.send_signal(sig)
File "C:\ProgramData\Anaconda3\lib\site-packages\psutil\__init__.py", line 289, in wrapper
return fun(self, *args, **kwargs)
File "C:\ProgramData\Anaconda3\lib\site-packages\psutil\__init__.py", line 1218, in send_signal
self._proc.send_signal(sig)
File "C:\ProgramData\Anaconda3\lib\site-packages\psutil\_pswindows.py", line 681, in wrapper
raise convert_oserror(err, pid=self.pid, name=self._name)
psutil.AccessDenied: psutil.AccessDenied (pid=20712)
Versions
- Spyder version: 4.1.5
- Python version: 3.8.5
- Qt version: 5.9.7
- PyQt5 version: 5.9.2
- Operating System: Windows 10
Dependencies
# Mandatory:
atomicwrites >=1.2.0 : 1.4.0 (OK)
chardet >=2.0.0 : 3.0.4 (OK)
cloudpickle >=0.5.0 : 1.6.0 (OK)
diff_match_patch >=20181111 : 20200713 (OK)
intervaltree : None (OK)
IPython >=4.0 : 7.19.0 (OK)
jedi =0.17.1 : 0.17.1 (OK)
nbconvert >=4.0 : 6.0.7 (OK)
numpydoc >=0.6.0 : 1.1.0 (OK)
paramiko >=2.4.0 : 2.7.2 (OK)
parso =0.7.0 : 0.7.0 (OK)
pexpect >=4.4.0 : 4.8.0 (OK)
pickleshare >=0.4 : 0.7.5 (OK)
psutil >=5.3 : 5.7.2 (OK)
pygments >=2.0 : 2.7.2 (OK)
pylint >=1.0 : 2.6.0 (OK)
pyls >=0.34.0;<1.0.0 : 0.35.1 (OK)
qdarkstyle >=2.8 : 2.8.1 (OK)
qtawesome >=0.5.7 : 1.0.1 (OK)
qtconsole >=4.6.0 : 4.7.7 (OK)
qtpy >=1.5.0 : 1.9.0 (OK)
rtree >=0.8.3 : 0.9.4 (OK)
sphinx >=0.6.6 : 3.2.1 (OK)
spyder_kernels >=1.9.4;<1.10.0 : 1.9.4 (OK)
watchdog : None (OK)
zmq >=17 : 19.0.2 (OK)
# Optional:
cython >=0.21 : 0.29.21 (OK)
matplotlib >=2.0.0 : 3.3.2 (OK)
numpy >=1.7 : 1.19.2 (OK)
pandas >=0.13.1 : 1.1.3 (OK)
scipy >=0.17.0 : 1.5.2 (OK)
sympy >=0.7.3 : 1.6.2 (OK)
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
How to Fix Critical Error Your Start Menu Isn't Working ...
Fix 1: Enter Safe Mode and Restart Computer Step 2: Keep holding the Shift button on your keyboard and click the Power button,...
Read more >What Is the Start Menu Critical Error and How Do You Fix It?
The Start menu critical error mainly occurs when Windows force-stops a program that is causing internal issues. Corrupt system files and lack of ......
Read more >Critical Error – Your Start menu isn't working.
Try to re-register Start Menu: 1. Open Task Manager, click File > Run new task. 2. Type powershell in the Create new task...
Read more >How To Fix "Critical Error Your Start Menu Isn't Working"
Critical Error: Your Start Menu Isn't Working · Re-install Your Start Menu · Restart Windows Explorer · Run the System File Checker ·...
Read more >How to Fix Windows 10 Start Menu Critical Error - EaseUS
Step 3. Your computer should now restart to boot options. Go to "Troubleshoot" > "Advanced options" > "Startup Settings". Click the "Restart" ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the tip!
On Fri, Nov 19, 2021 at 8:29 PM Carlos Cordoba @.***> wrote:
I don’t know what happens then. You probably need to wait until the next version of Anaconda to get a more recent Spyder version. Or you can remove and reinstall Anaconda if you want to see if the update is successful after that.