@johnandmegh , I was under the impression that that was remediated two years ago. Irrespective, when I reported that issue downstream to VS Code, the solution was to delete the shader cache:
  
  
    
  
  
    
    
      
        opened 06:28PM - 14 Aug 23 UTC 
      
        
          closed 07:44PM - 13 Nov 23 UTC 
        
      
     
    
        
          bug
         
        
          verified
         
        
          linux
         
        
          gpu
         
        
          upstream-issue-fixed
         
        
          chromium
         
        
          author-verification-requested
         
        
          mitigated
         
        
          insiders-released
         
        
          electron-25-update
         
    
   
 
  
    1.	## **Workaround**
	
	This is an issue in Chromium itself. For now there are…  the following two workarounds:
	
	1.	### **https://github.com/microsoft/vscode/issues/190437#issuecomment-1722228671**
		
		<blockQuote>
		
		```sh
		rm -rf "$HOME/.config/Code/GPUCache"
		```
		
		</blockQuote>
		
	1.	### **https://github.com/microsoft/vscode/issues/190437#issuecomment-1679815094**
		
		<blockQuote>
		
		```pwsh
		If ($IsLinux) {Remove-Item -Path "$HOME/.config/Code - Insiders/GPUCache"}
		```
		
		</blockQuote>
	
1.	## **Bug**
	
	
	
	
	
	
	
	
	
	| Does this issue occur when all extensions are disabled? |
	| - |
	| I can't test that. |
	
	
	
	
	1.	### **VS Code Version**
		Per:
	
		```pwsh
		code-insiders
		```
		...the affected version is:
	
		<blockQuote>
		
		Type            | Data
		----------------|-----------------------------------------
		Version         | 1.82.0-insider
		Commit          | 76985ae7814f7cb28e2df6f1025d279bb77cbec1
		Date            | 2023-08-11T17:10:45.392Z
		Electron        | 25.4.0
		ElectronBuildId | 22958381
		Chromium        | 114.0.5735.248
		Node.js         | 18.15.0
		V8              | 11.4.183.27-electron.0
		OS              | Linux x64 6.4.9-1-default
		
		</blockQuote>
		However, per:
		```.PS1
		code
		```
		...note that `--channel=latest/stable`, that is:
		
		<blockQuote>
			
		Type            | Data
		----------------|-----------------------------------------
		Version         | 1.81.1
		Commit          | 6c3e3dba23e8fadc360aed75ce363ba185c49794
		Date            | 2023-08-09T22:18:39.991Z
		Electron        | 22.3.18
		ElectronBuildId | 22689846
		Chromium        | 108.0.5359.215
		Node.js         | 16.17.1
		V8              | 10.8.168.25-electron.0
		OS              | Linux x64 6.4.9-1-default snap
			
		</blockQuote>
		
		...works:
			
		> 
	1.	### **OS Version**
		```.PS1
		cat -vbET '/etc/os-release'
		```
		> ```.log
		>      8  CPE_NAME="cpe:/o:opensuse:tumbleweed:20231119"$
		> ```
		<details>
	
		```pwsh
		uname -a
		```
	
		<blockQuote>
	
		```log
		PS /home/rokejulianlockhart> uname -a
		Linux RQN6C6 6.4.9-1-default #1 SMP PREEMPT_DYNAMIC Wed Aug  9 05:07:55 UTC 2023 (5b9ad20) x86_64 x86_64 x86_64 GNU/Linux
		PS /home/rokejulianlockhart>
		```
	
		</blockQuote>
		</details>
	
1.	## **Steps to Reproduce**
	
	1.	```pwsh
		code-insiders
		```
	1.	The GUI is invisible:
	
		> 
	
		...yet the menubar continues to operate correctly. 
   
   
  
    
    
  
  
 
I’ve yet to confirm whether the solution applies to this, but am not hopeful, considering the different symptoms.
@olib , thank you! That works for me:
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.4-300.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Graphics Processor 1: AMD Radeon RX 5700
Graphics Processor 2: AMD Radeon Graphics