ThaDaVos
commented
7 months ago Having the same issue on Windows - albeit, changing the size of the VSCODE window does nothing - it only seems to happen on my primary monitor - if I move the window to one of the others there is no issue - the only difference I see between them is that my main monitor has a higher refresh rate and higher resolution - 2560x1600 by 165hz vs 1920x1080 by 60hz.
My cursor is only gone in the main text window, so the file editing - I can restore it by changing the cursor size or switching to a different color, though, the "Invert" option of the mouse pointer in windows (where it changes based on background) doesn't fix it.
Seems to be a re-introducting of this bug: https://github.com/microsoft/vscode/issues/44211
Type: Bug
The pointer (= hand+finger or arrow-pointer or I bar, that is moved by the mouse) (not the cursor =the vertical bar at the insertion point in the text) disappears after any ONE click anywhere in vscode when vscode is in a maximised window on one monitor of a 3 monitor system.
When the ppointer has disappeared moving the mouse changes things that respond to hovering (like files in the vscode's file explorer) but the pointer is not visible in any area of the vscode window including the window title bar and the minimized/unmaximised/close icons in the top right. The cursor (|) in the editor remains visible, and can be moved by clicking the mouse, but there's no pointer visible to show where it is going to be moved to.
The pointer can be restored by moving to a window on another monitor, even if that is another vscode instance window, but the pointer is gone when moved back to the vscode instance that lost it.
It can be restored by changing the Cursor Size in Gnome Settings and then moving back to vscode where it does appear, but only until ONE mouse click, then it disappears again. (This includes changing the Cursor Size and changing it back again so it didn't actually change)
Narrowing the Problem The problem ONLY occurs if vscode's window is maximized. The pointer disappears when the vscode window is maximized and reappears when in unmaximized state. The bug does not show if the gnome "dock", without autohide, is on the same monitor (so "maximised" is not the whole monitor) The bug does show with gnome dock autohide ON (so maximised is whole monitor) The "unmaximized" behavior(=bug does not show) is true if the window is manually resized to fill the monitor but may be "full" is approximate So I suspect the bug only occurs when the window size === the monitor size.
Changing themes (eg dark to light) does not change the bug behavior (so it's not a black pointer on a black background) Problem behavior occurs with all extensions disabled.
Using ubuntu 22.04.3 LTS, Gnome 42.9, multiple monitors(3) Vscode (about): Version: 1.85.1 Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2 Date: 2023-12-13T09:47:11.635Z Electron: 25.9.7 ElectronBuildId: 25551756 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: 11.4.183.29-electron.0 OS: Linux x64 6.2.0-39-generic
newly removed and reinstalled vscode
cat ~/.config/Code/User/settings.json { "workbench.colorTheme": "Abyss" }
cat ./settings.json { "workbench.colorTheme": "Abyss" }
VS Code version: Code 1.85.1 (0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2, 2023-12-13T09:47:11.635Z) OS version: Linux x64 6.2.0-39-generic Modes:
System Info
|Item|Value| |---|---| |CPUs|Intel(R) Xeon(R) CPU E5-1660 v3 @ 3.00GHz (16 x 1197)| |GPU Status|2d_canvas: enabledcanvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off| |Load (avg)|0, 0, 0| |Memory (System)|31.10GB (26.60GB free)| |Process Argv|. --crash-reporter-id 18dd3855-4ecd-43f1-ad32-c4eccea7ed5f| |Screen Reader|no| |VM|0%| |DESKTOP_SESSION|ubuntu| |XDG_CURRENT_DESKTOP|Unity| |XDG_SESSION_DESKTOP|ubuntu| |XDG_SESSION_TYPE|wayland|
A/B Experiments
``` vsliv368cf:30146710 vsreu685:30147344 vspor879:30202332 vspor708:30202333 vspor363:30204092 vstes627:30244334 vslsvsres303:30308271 vshan820:30294714 vscorecescf:30445987 vscod805:30301674 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 vsaa593cf:30376535 py29gd2263:30899288 vsclangdf:30486550 c4g48928:30535728 azure-dev_surveyone:30548225 f6dab269:30613381 pythongtdpath:30769146 i26e3531:30792625 welcomedialogc:30910334 pythonidxpt:30866567 pythonnoceb:30805159 asynctok:30898717 pythontestfixt:30902429 pythonregdiag2cf:30928864 pyreplss1:30897532 pythonmypyd1:30879173 pythoncet0:30885854 pythontbext0:30879054 accentitlementst:30887150 dsvsc016:30899300 dsvsc017:30899301 dsvsc018:30899302 aa_t_chat:30882232 dsvsc019cf:30917260 cp7184t3:30927821 ```