P: Photoshop 22:0: Text selecting/editing UI not displaying in CMYK, LAB modes

Go to Preferences > Technology Previews... and check "Disable Native Canvas" - then restart Photoshop. Does the problem still occur?

This issue is back for me in version 23 on windows 10. When I create a text box by dragging, the text inside as well as the bounding box is invisible. I can see it in the layers panel but not in the document. Clicking and typing works fine. The problem only occurs when creating a text box.

Forgot to include system info:

Adobe Photoshop Version: 22.0.0 20201006.r.35 2020/10/06: 4587a1caa63 x64

Number of Launches: 1243

Operating System: Windows 10 64-bit

Version: 10 or greater 10.0.18362.1110

System architecture: Intel CPU Family:6, Model:15, Stepping:2 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, AVX, AVX2, HyperThreading

Physical processor count: 6

Logical processor count: 12

Processor speed: 3298 MHz

Built-in memory: 32679 MB

Free memory: 17656 MB

Memory available to Photoshop: 29926 MB

Memory used by Photoshop: 59 %

ACP.local Status:

- SDK Version: 1.34.1.4

- Core Sync Status: Reachable and compatible

- Core Sync Running: 4.3.61.1

- Min Core Sync Required: 4.3.28.24

ACPL Cache Config:

- Time to Live: 5184000 seconds

- Max Size: 20480 MB

- Purge Percentage: 50%

- Threshold Percentage: 85%

- Purge Interval: 60 seconds

Native GPU: Disabled.

Manta Canvas: Enabled.

Alias Layers: Disabled.

Modifier Palette: Enabled.

Highbeam: Enabled.

Image tile size: 1024K

Image cache levels: 4

Font Preview: Medium

TextComposer: Latin

"margin: 0;">Display Bounds: top=0, left=0, bottom=1440, right=2560

OpenGL Drawing: Disabled.

OpenGL Allow Old GPUs: Not Detected.

NumGLGPUs=1

NumCLGPUs=1

NumNativeGPUs=1

glgpu[0].GLVersion="4.6"

glgpu[0].IsIntegratedGLGPU=0

glgpu[0].GLMemoryMB=4043

glgpu[0].GLName="GeForce GTX 970/PCIe/SSE2"

glgpu[0].GLVendor="NVIDIA"

glgpu[0].GLDriverVersion="26.21.14.3200"

glgpu[0].GLDriver="C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_db678424d2641c3d\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_db678424d2641c3d\nvldumdx.dll,C:\WINDOWS\System32\

I just updated PhotoShop and the text cursor does not show. I checked previous similar issues on previous versions. One solution recommended was to turn off the Graphic Processor. I did that it the cursor now appears.

But won't that slow down processing in PS generally??

I checked before updating to new version that my graphics card would be Ok and it seemed to indicate that. 

System info below (first page of system info)

Preferences Performance tab screen grab

attached

@JeffreyTranberry  I can confirm the fix with 22.0.1 update on Mac 10.14 (Mojave). 

Thank you for the quick resolution.

Exactly! The only work around seems to be to turn off graphics acceleration. However, that is definitely not a solution because other problems arise: lagging functionality, tool indicators stay on screen after they should disappear and/or item images stick in place and stretch on the screen when being dragged; slices of layers visually stick in place when scrolling or enlarging/reducing view and leave gaps in the screen image that are only resolved by deselecting the item and scrolling the window.

Just upgraded to Big Sur on a MacBook Pro (Retina, 13-inch, Early 2015) with a Intel Iris Graphics 6100 1536 MB graphics card.

When graphics acceleration is enabled (\preferences\performance\Graphics Processor Settings\"Use Graphics Processor") no cursor appears, and no selection highlighting is visible when editing text. 

Turning off the graphics processor allows me to see the cursor and text selection, but besides presumed speed reductions, there is no anti-aliasing and areas of the screen tend to randomly blank out when selecting text as shown in the attached image. It is just a temporary display issue, clicking off the text redraws the missing portions of the image, but obviously it is a pain to work with.

Is this STILL not fixed? It's been like 2 weeks now - this is an extremely frustrating bug and the fix should take top priority as it is one of the most basic tools. I'm downgrading to 2020 in the mean time.