Spyder under WSL2 loss of mouse click ability (corruption of transient.ini file??) #20851
Comments
|
Hi @clayjstanek thank you for the feedback! Could it be possible for you to check if running Spyder with the Let us know if the info above helps! |
|
I have the exact same problem and no, |
|
Thank you for trying the flag @aabdulaal ! Could you then try to run spyder with the Could it be possible for you to change this part of the Spyder code: spyder/spyder/plugins/layout/plugin.py Lines 546 to 549 in 11dee3c To be something like: hexstate_valid = FalseLet us know if something of the above helps! |
|
@dalthviz I edited plugin.py as you suggested and it appears to have prevented the problem for me. I've started it multiple times since the edit without problems. |
|
@dalthviz, what should we do about this one? |
|
Not sure if there is a way to try the code without it ending in a segmentation fault. Maybe adding an option to prevent saving the hex state or using it could help this specific setup (Spyder + WSL2). Also, not sure why this is happening, maybe is a more general issue/incompatibility between the display system WSL2 uses and Qt? 🤔 |
|
Perhaps we can validate if the hex state is valid before trying to load it? I don't know if that's possible though. |
|
I have a similar issue. I am running:
under WSL2: WSL version: 2.0.9.0 When I initiate Spyder (Spyder --reset) everything works fine. On a second start, just calling Spyder, I usually get mouse control but everything is shifted by a couple lines. (I have to click above the line and to the left of anything I want to highlight). On subsequent startups I lose all mouse control and need to use keyboard shortcuts to function. I have recently tried calling 'Spyder --no-web-widgets' and this seems to have corrected the issue for me (calling Spyder without qualifiers). However, I do get the warning: QStandardPaths: wrong permissions on runtime directory /run/user/1000/, 0755 instead of 0700 but it does not seem to effect the usage of spyder. |
That's great! Thanks for letting us know about it.
Don't worry, those are harmless warnings. |
|
Hello, I am running
under WSL: And I have the same problem reported by JC-NH: When I initiate Spyder (Spyder --reset) everything works fine. HOWEVER, in my case calling 'spyder --no-web-widgets' does not solve the problem. The only way is --reset (and lose all config) UPDATE: Now even after doing "spyder --reset", the issue of the shifted cursor behavior appears at first run. UPDATE2: The issue of the mouse control being shifted more or less two lines, only happens in the main spyder window. If I open another window such as Preferences or 'Open File', inside that one the mouse and cursor behave normally. |
|
I found what seems to be a good workaround. And maybe a clue? I hope this is useful. UPDATE:
|
|
Hello, I have the same issue. Based on the solution of #12367 , I "fixed" it by adding the following alias to my .bashrc alias spyder="sed -i '/window\/position = (.*)/c\window/position = (0,0)' ~/.config/spyder-py3/config/transient.ini ; spyder " |
ccordoba12
changed the title
|
@Zybulon, thanks for the confirmation. Could you post the value (or values) of According to #12367 (comment), it seems the problem is we're trying to save negative values for that setting. And that should be an easy fix. |
|
Without that alias the values were exactly the same negative values : (-32, -32). |
|
It works perfectly, thanks for you reactivity ! |
|
That's great! Thanks for your help too. I'll include that in 6.0.1 then, to be released tomorrow. |
Issue Report Checklist
conda update spyder(orpip, if not using Anaconda)jupyter qtconsole(if console-related)spyder --resetProblem Description
I've just purchased a high end HP Omen with an RTX 4080 GPU and 32 GB RAM and 2 TB SSD with i9 CPU and am having a real problem debugging a Spyder issue when running it on the Ubuntu side of my installation. I am NOT trying to run a spyder kernel from Ubuntu in a Spyder instantiation on Windows, everything is straight-up on Ubuntu side.
Ultimately, the Spyder GUI does not allow me to click anywhere in the display. All the keyboard shortcuts do work and mouse movement works.
What steps reproduce the problem?
What is the expected output? What do you see instead?
I would expect spyder to open where it was closed in step 2 of setting preferences and the mouse clicking to activate on top of the item it is over, not offset by a set number of pixels down and to the right. And I certainly don't expect to lose all mouse clicking functionality when restarting a second time.
Paste Traceback/Error Below (if applicable)
PASTE TRACEBACK HERE Got keys from plugin meta data ("webp") QFactoryLoader::QFactoryLoader() checking directory path "/home/cstanek/anaconda3/envs/plotting/bin/imageformats" ... loaded library "/home/cstanek/anaconda3/envs/plotting/plugins/imageformats/libqgif.so" loaded library "/home/cstanek/anaconda3/envs/plotting/plugins/imageformats/libqicns.so" loaded library "/home/cstanek/anaconda3/envs/plotting/plugins/imageformats/libqico.so" loaded library "/home/cstanek/anaconda3/envs/plotting/plugins/imageformats/libqjpeg.so" fromIccProfile: failed minimal tag size sanity loaded library "/home/cstanek/anaconda3/envs/plotting/plugins/imageformats/libqpdf.so" loaded library "/home/cstanek/anaconda3/envs/plotting/plugins/imageformats/libqsvg.so" loaded library "/home/cstanek/anaconda3/envs/plotting/plugins/imageformats/libqtga.so" loaded library "/home/cstanek/anaconda3/envs/plotting/plugins/imageformats/libqtiff.so" loaded library "/home/cstanek/anaconda3/envs/plotting/plugins/imageformats/libqwbmp.so" loaded library "/home/cstanek/anaconda3/envs/plotting/plugins/imageformats/libqwebp.so" QFactoryLoader::QFactoryLoader() checking directory path "/home/cstanek/anaconda3/envs/plotting/plugins/accessible" ... QFactoryLoader::QFactoryLoader() checking directory path "/home/cstanek/anaconda3/envs/plotting/bin/accessible" ... QGLXContext: Failed to create dummy context ##### CTRL-Q here ###### [1]+ Segmentation fault spyderVersions
Dependencies
The text was updated successfully, but these errors were encountered: