VSCodium/vscodium
1
0
Fork 0
mirror of https://github.com/VSCodium/vscodium.git synced 2026-02-04 03:51:16 -06:00
Code Issues 135 Packages Projects Releases 10 Wiki Activity

PHP Debug don't work #1192

New Issue
Closed
opened 2025-09-10 23:50:58 -05:00 by giteasync · 13 comments
giteasync commented 2025-09-10 23:50:58 -05:00
Owner
Copy Link

Originally created by @zacjack on GitHub.

Hello everyone, thanks in advance for any help.

I'm trying to migrate to VSCodium, but i has a problem with this extension for PHP Debugging

PHP Debug 1.13.0 from felixfbecker

[2020-07-28 23:16:36.862] [renderer1] [error] timeout after 1000 ms: Error: timeout after 1000 ms at t.RawDebugSession.handleErrorResponse (file:///usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:3160:190) at file:///usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:3159:451 at async t.RawDebugSession.shutdown (file:///usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:3157:536)

this work fine on VSCode,

Originally created by @zacjack on GitHub. Hello everyone, thanks in advance for any help. I'm trying to migrate to VSCodium, but i has a problem with this extension for PHP Debugging PHP Debug 1.13.0 from felixfbecker `[2020-07-28 23:16:36.862] [renderer1] [error] timeout after 1000 ms: Error: timeout after 1000 ms at t.RawDebugSession.handleErrorResponse (file:///usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:3160:190) at file:///usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:3159:451 at async t.RawDebugSession.shutdown (file:///usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:3157:536)` this work fine on VSCode,
giteasync commented 2025-09-10 23:50:59 -05:00
Author
Owner
Copy Link

@kevinfiol commented on GitHub:

Ah I'm having this same issue on my Linux Mint machine. Glad to see I'm not alone.

@kevinfiol commented on GitHub: Ah I'm having this same issue on my Linux Mint machine. Glad to see I'm not alone.
giteasync commented 2025-09-10 23:50:59 -05:00
Author
Owner
Copy Link

@software-artificer commented on GitHub:

There is #464, so I think that affects all platforms. I am having the same issue on macOS Catalina. There is also a similar report on the Xdebug plugin repo: felixfbecker/vscode-php-debug#414. I think VSCodium builds are messed up presently, because VSCode works just fine.

@software-artificer commented on GitHub: There is #464, so I think that affects all platforms. I am having the same issue on macOS Catalina. There is also a similar report on the Xdebug plugin repo: felixfbecker/vscode-php-debug#414. I think VSCodium builds are messed up presently, because VSCode works just fine.
giteasync commented 2025-09-10 23:50:59 -05:00
Author
Owner
Copy Link

@TomaszGasior commented on GitHub:

Maybe it's related to https://github.com/microsoft/vscode/issues/103105 and 21e633cc63.

@TomaszGasior commented on GitHub: Maybe it's related to https://github.com/microsoft/vscode/issues/103105 and https://github.com/microsoft/vscode/commit/21e633cc63a58c7403dffbf242e1ce29416c2143.
giteasync commented 2025-09-10 23:50:59 -05:00
Author
Owner
Copy Link

@TomaszGasior commented on GitHub:

I managed to fix this issue by downloading PHP Debug extension from Microsoft's Visual Studio Marketplace instead of using VSCodium alternative marketplace. It works at least on Linux (Fedora and Ubuntu). Step by step guide is

  1. make sure you don't have PHP Debug extension installed;
  2. go to https://marketplace.visualstudio.com/items?itemName=felixfbecker.php-debug and download vsix file using "Resources" → "Download Extension";
  3. in VSCodium go to "Extensions" sidebar and then click three dots icon near to "Extensions" title;
  4. choose "Install from VSIX…" and select downloaded file.
@TomaszGasior commented on GitHub: I managed to fix this issue by downloading PHP Debug extension from Microsoft's Visual Studio Marketplace instead of using VSCodium alternative marketplace. It works at least on Linux (Fedora and Ubuntu). Step by step guide is 0. make sure you don't have PHP Debug extension installed; 1. go to https://marketplace.visualstudio.com/items?itemName=felixfbecker.php-debug and download vsix file using "Resources" → "Download Extension"; 2. in VSCodium go to "Extensions" sidebar and then click three dots icon near to "Extensions" title; 3. choose "Install from VSIX…" and select downloaded file.
giteasync commented 2025-09-10 23:50:59 -05:00
Author
Owner
Copy Link

@T200proX7 commented on GitHub:

LINUX / DEBIAN:

I have the same /almost same problem. Xdebug does not listen on the port when clicking on Start Debugging. More just seconds after clicking the button it stop the debug mode.

No there is no port collision with php-fpm and also no config problem.
I tried several ways and xdebug work fine with Sublime or VSCode (but no codium).

@T200proX7 commented on GitHub: LINUX / DEBIAN: I have the same /almost same problem. Xdebug does not listen on the port when clicking on Start Debugging. More just seconds after clicking the button it stop the debug mode. No there is no port collision with php-fpm and also no config problem. I tried several ways and xdebug work fine with Sublime or VSCode (but no codium).
giteasync commented 2025-09-10 23:50:59 -05:00
Author
Owner
Copy Link

@lucrus73 commented on GitHub:

This issue may be closed :)

I'm running 1.49.0 and I'm facing this issue.

@lucrus73 commented on GitHub: > This issue may be closed :) I'm running 1.49.0 and I'm facing this issue.
giteasync commented 2025-09-10 23:50:59 -05:00
Author
Owner
Copy Link

@greduan commented on GitHub:

I faced this issue v1.49.3. Tomasz's fix worked for me.

@greduan commented on GitHub: I faced this issue v1.49.3. Tomasz's fix worked for me.
giteasync commented 2025-09-10 23:50:59 -05:00
Author
Owner
Copy Link

@brunob commented on GitHub:

nice but strange @TomaszGasior :)

@brunob commented on GitHub: nice but strange @TomaszGasior :)
giteasync commented 2025-09-10 23:50:59 -05:00
Author
Owner
Copy Link

@brunob commented on GitHub:

FTR, v1.49.0 seems to fix the bug for me : i've removed PHP Debug extension and reinstalled it from the GUI => debug is working.

It may be related to this PR https://github.com/microsoft/vscode/issues/95162

This issue may be closed :)

@brunob commented on GitHub: FTR, v1.49.0 seems to fix the bug for me : i've removed PHP Debug extension and reinstalled it from the GUI => debug is working. It may be related to this PR https://github.com/microsoft/vscode/issues/95162 This issue may be closed :)
giteasync commented 2025-09-10 23:50:59 -05:00
Author
Owner
Copy Link

@eandersons commented on GitHub:

I had the same problem with VSCodium 1.51.1. Solved it by downloading extension from Visual Studio Code marketplace and installing it manually (as per steps described by Tomasz).

@eandersons commented on GitHub: I had the same problem with VSCodium 1.51.1. Solved it by downloading extension from Visual Studio Code marketplace and installing it manually (as per steps described by Tomasz).
giteasync commented 2025-09-10 23:50:59 -05:00
Author
Owner
Copy Link

@stripedpajamas commented on GitHub:

Sounds like the extension on Open VSX may be out of date or broken. Based on the extension page, it looks like Open VSX manually published that extension. I recommend reaching out to the developers of the extension (https://github.com/xdebug/vscode-php-debug) and asking them to publish to Open VSX as per the docs.

Otherwise, either switching to the MS marketplace or downloading the latest vsix file from the MS marketplace and installing it manually should work, as per @TomaszGasior's comment.

@stripedpajamas commented on GitHub: Sounds like [the extension on Open VSX](https://open-vsx.org/extension/felixfbecker/php-debug) may be out of date or broken. Based on the extension page, it looks like Open VSX manually published that extension. I recommend reaching out to the developers of the extension (https://github.com/xdebug/vscode-php-debug) and asking them to publish to Open VSX as per [the docs](https://github.com/VSCodium/vscodium/blob/master/DOCS.md#extensions--marketplace). Otherwise, either switching to the MS marketplace or downloading the latest vsix file from the MS marketplace and installing it manually should work, as per @TomaszGasior's comment.
giteasync commented 2025-09-10 23:50:59 -05:00
Author
Owner
Copy Link

@ngdangtu-vn commented on GitHub:

@brunob

Version: 1.52.1
Commit: ea3859d4ba2f3e577a159bc91e3074c5d85c0523
Date: 2020-12-17T00:37:28.692Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux arm64 5.8.0-1010-raspi

Mine didn't work.

@ngdangtu-vn commented on GitHub: @brunob ``` Version: 1.52.1 Commit: ea3859d4ba2f3e577a159bc91e3074c5d85c0523 Date: 2020-12-17T00:37:28.692Z Electron: 9.3.5 Chrome: 83.0.4103.122 Node.js: 12.14.1 V8: 8.3.110.13-electron.0 OS: Linux arm64 5.8.0-1010-raspi ``` Mine didn't work.
giteasync commented 2025-09-10 23:50:59 -05:00
Author
Owner
Copy Link

@xoxefdp commented on GitHub:

Got sae conditions as @ngdangtu-vn , except os is xubuntu 20.04.

@xoxefdp commented on GitHub: Got sae conditions as @ngdangtu-vn , except os is xubuntu 20.04.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
discussion
documentation
downstream
duplicate
enhancement
extension
good first issue
help wanted
invalid
never-stale
pull-request
Mirrored from GitHub Pull Request
question
stale
telemetry
upstream
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
giteasync
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: VSCodium/vscodium#1192
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?