Copilot Chat extenson broken after 1.105.16954

[BenBE]

Describe the bug In versions after 1.105.16954, the chat window in the right side bar cannot be opened for the Copilot Chat extension. With 1.105.16954 the extension works just fine and can be used as normal.

Please confirm that this problem is VSCodium-specific

• [X] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

• [X] I checked the Docs page and the Troubleshooting page and my issue is not mentioned there.

To Reproduce Steps to reproduce the behavior:

1. Open VSCodium
2. Press Ctrl+Shift+P
3. Chat: Focus on Chat View
4. See blank side panel without Copilot chat

Expected behavior See Copilot chat window like in previous versions

Desktop (please complete the following information):

• OS: Linux 6.14, Lubuntu 25.10
• Architecture x86-64 / amd64
• Version 1.105.16999, 1.105.17017, 1.105.17075
• App Manager: apt/dpkg
• Sandboxed: no

Additional context Worked in 1.105.16954 and before. GitHub Copilot Chat version 0.32.5

[daiyam]

https://github.com/VSCodium/vscodium/blob/master/docs/ext-github-copilot.md

[MegaMcVolt]

I also have this problem (I tried different versions), but also with an auxiliary bug, such as - not all extensions load (even in the sidebar of extensions - emptiness and the loading indicator constantly runs)

Desktop (please complete the following information):

• OS: Linux 6.12.55, Slackware 15.0 (post 15.0 - current)
• Architecture x86-64
• Version 1.105.16999 and later (last - 1.106.27818)
• Sandboxed: no

Worked in 1.105.16954 and before	Not worked in 1.105.16999 and later

https://github.com/VSCodium/vscodium/issues/2600#issuecomment-3534924182 - doesn't help

In my opinion, something broke after you introduced these changes:

What else do you advise to check/fix?

[daiyam]

Can you check the logs under View/Output then for:

• Extension Host
• Main

[MegaMcVolt]

That's the trouble that there is nothing suspicious in the logs.

The only log that raises suspicion is main.log: 2025-11-23 15:39:06.133 [info] update#setState disabled 2025-11-23 15:39:06.133 [info] update#ctor - updates are disabled as there is no update URL 2025-11-23 15:39:07.409 [error] TypeError: Cannot read properties of undefined (reading 'info') 2025-11-23 15:43:51.003 [info] Extension host with pid 5548 exited with code: 0, signal: unknown.

The rest of the logs are of zero length, probably because some process (possibly running 'Extension host') is freezing.

[daiyam]

2025-11-23 15:43:51.003 [info] Extension host with pid 5548 exited with code: 0, signal: unknown.

This is the issue. Something is crashing the Extension host, this is why you have blank sidebars. Try the command > Help: Start Extension Bisect

[MegaMcVolt]

Ha, this is obvious. That's exactly - the first thing I tried to do, but neither with the command nor with the GUI - nothing helps, because as I said above, the 'Extension host' process freezes (does not allow 'Start Extension Bisect' to be executed) - just nothing happens after entering the command. I even deleted all the extensions in the user folder (not built-in extensions), it doesn't help either.

You know what's the matter, I don't think that extensions have any effect on hanging, it's something related to a breakdown in the UI in my opinion (by the way, you made some changes in this direction 1.105.16954...1.105.16999)

But, don't be offended, I could be wrong, because you know better how everything works under the hood.

[daiyam]

Try by deleting for the UI state db (maybe in ~/.config/VSCodium/User/globalStorage/state.vscdb and globally the ~/.config/VSCodium directory)

But, don't be offended, I could be wrong, because you know better how everything works under the hood.

Don't worry, you are fine. It's just that I don't have the issue and I don't see any other report of that issue, sorry :wink: It's just that it's remind me of the issue of VSCode is currently having on macOS due to bugs in Chromium. I did delay and released 1.106 with the newest Electron version. Maybe, there is an issue with the Slackware package. From what I could see, it uses the packaged Electron but if you use a system-wide Electron, try update it.

[MegaMcVolt]

Yes, the problem occurred in the Slackware package, but not with Electron, but with the /opt/vscode-bin/resources/app/product.json

The Slackware package is created as follows:

1. Used VSCodium-linux-x64-1.106.27818.tar.gz

2. Overlay patches from the Arch Linux (AUR) guys on the file ./resources/app/product.json:

   • code-features 1.106.0-1

   • code-marketplace 1.106.0-1

3. A Slackware package is being built (according to system requirements).

After removing the following parameters from ./resources/app/product.json, 'Extension host' started working properly:

	"configurationSync.store": {
		"authenticationProviders": {
			"github": {
				"scopes": [
					"user:email"
				]
			},
			"microsoft": {
				"scopes": [
					"openid",
					"profile",
					"email",
					"offline_access"
				]
			}
		},
		"canSwitch": false,
		"insidersUrl": "https://vscode-sync-insiders.trafficmanager.net/",
		"stableUrl": "https://vscode-sync.trafficmanager.net/",
		"url": "https://vscode-sync.trafficmanager.net/"
	},
	"editSessions.store": {
		"authenticationProviders": {
			"github": {
				"scopes": [
					"user:email"
				]
			},
			"microsoft": {
				"scopes": [
					"openid",
					"profile",
					"email",
					"offline_access"
				]
			}
		},
		"url": "https://vscode-sync.trafficmanager.net/"
	},

But Chat never appeared in the sidebar:

Here's my final file product.json, maybe you can tell me how to resuscitate Chat again.

[MegaMcVolt]

That's it, you don't need to do anything! I tried your hack https://github.com/VSCodium/vscodium/issues/2600#issuecomment-3534924182 and everything works:

Sorry to bother you and thank you for your time on me!

[daiyam]

Where can I see the build definition for the Slackware package? I did found https://slackbuilds.org/repository/15.0/development/vscodium/ but I can find any references to the AUR.

I can see the issue with configurationSync.store since I've removed the UserDataSyncLogService (https://github.com/VSCodium/vscodium/pull/2562) since it doesn't work with VSCodium. I didn't think people were editing the product.json to have that feature since it's a bit an opaque feature. So I should maybe remove that patch. Do you use that feature?

(by the way, you made some changes in this direction 1.105.16954...1.105.16999)

You were right :wink:

[MegaMcVolt]

The Slackware ecosystem is not very developed in relation to other distributions (it is quite puritanical). I am creating this package for myself for my needs (of course, you will not access it on the Internet, but in the future I plan to make my small repository available to people). I don't use UserDataSyncLogService, it happened to be left over from previous patches from the Arch Linux guys (now they don't have it either), so your patch #2562 needs to be left.

I understand that you are not obliged to do this, but it would be nice if in the future you somehow warned people (like me) who edit product.json that this or that next patch for VSCodium will affect the parameters in product.json, that attention needs to be paid to the fact that some feature with product.json is invalid/removed. For example, in the description for the patch.

Thank you for your work!

[daiyam]

I understand that you are not obliged to do this, but it would be nice if in the future you somehow warned people (like me) who edit product.json that this or that next patch for VSCodium will affect the parameters in product.json, that attention needs to be paid to the fact that some feature with product.json is invalid/removed. For example, in the description for the patch.

I agree.