question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Spyder crashes after Monitor Scale change

See original GitHub issue

Description

Spyder crashes after closing (“dismiss”) the Monitor Scale change detected pop-up on remote machine.

What steps will reproduce the problem?

Specific scenario:

  1. Connect to a Remote Desktop with one monitor scale size.
  2. Open Spyder on that Remote Desktop machine.
  3. Close Remote Desktop connection (keep Spyder open on the remote machine).
  4. Re-connect to the same Remote Desktop with a different monitor scale size (e.g. a different local machine).
  5. Spyder produces Monitor Scale change detected pop-up. Click dismiss.
  6. Spyder will crash/close with no error thrown.

Note: monitor scale change pop up seems to work normally when I move Spyder (in the RD window) between monitors on the local machine.

Pure speculation: could it be that there are three monitor scale changes going on (local machine #1 > remote machine (when RD connection from LM1 is closed) > local machine #2) which is what’s causing the issue?

Versions

  • Spyder version: 4.1.5
  • Python version: 3.8.3
  • 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.18.1 (OK)
jedi =0.17.1                   :  0.17.1 (OK)
nbconvert >=4.0                :  5.6.1 (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.6.1 (OK)
pylint >=1.0                   :  2.6.0 (OK)
pyls >=0.34.0;<1.0.0           :  0.34.1 (OK)
qdarkstyle >=2.8               :  2.8.1 (OK)
qtawesome >=0.5.7              :  0.7.2 (OK)
qtconsole >=4.6.0              :  4.7.6 (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.1 (OK)

# Optional:
cython >=0.21                  :  0.29.21 (OK)
matplotlib >=2.0.0             :  3.3.1 (OK)
numpy >=1.7                    :  1.19.1 (OK)
pandas >=0.13.1                :  1.1.1 (OK)
scipy >=0.17.0                 :  1.5.0 (OK)
sympy >=0.7.3                  :  1.6.2 (OK)

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:63 (26 by maintainers)

github_iconTop GitHub Comments

3reactions
Caseyb87commented, Feb 10, 2021

You need to check out the PR branch before running Spyder; there are aliases to do that or a manual method involving several steps, but the easiest way is to just download and use hub (e.g. with conda install -c conda-forge hub, or with choco, snoop or as a standalone executable), a git wrapper from Github. Once you install it, you just run hub pr checkout 14696 to check out the above PR #14696 .

Thank you. I tried as you suggested but got a “Not Found” error - must have done something wrong there. In the end, I just copied/pasted new mainwindow.py file into the installation directory and it worked!

I was able to connect/disconnect/reconnect from the remote machine with different local machines and Spyder did not crash. Got the warning (only once), clicked dismiss and was able to continue as expected.

1reaction
bilderbuchicommented, Feb 10, 2021

Thanks for checking, I did not get the opportunity to quickly test this time around! And also thanks for the fix, of course! 👍

Read more comments on GitHub >

github_iconTop Results From Across the Web

How To: Fix Spyder gui terrible scaling with high dpi monitor ...
1) Locate the qt.conf file · 2) Modify the qt.conf file · 3) Restart Spyder.
Read more >
Spyder crashes at launch: "python.exe has stopped working"
1. Uninstalling and reinstalling · 2. Resetting spyder (spyder --reset) · 3. deleting the .spyder2 directory · 4. changing the spyder config file,...
Read more >
How do you reset Spyder's GUI to default scaling?
I messed around with the display scale settings (windows11) and changed the scale to 100%. My Spyder IDE had its buttons resized and...
Read more >
spyder-ide/public - Gitter
Whenever I run Spyder on my Mac and switch between different windows, a box with the warning "A monitor scale change was detected....
Read more >
First Steps — Spyder 5 documentation
If Spyder crashes or you receive an error message, please read the following troubleshooting steps before opening a new issue. There's a good...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found