Bug 510041 - Start debug button is not clickable after starting a misconfigured debug session
Summary: Start debug button is not clickable after starting a misconfigured debug session
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.08.1
Platform: NixOS Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-29 08:33 UTC by p3dimaria
Modified: 2025-11-19 03:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description p3dimaria 2025-09-29 08:33:58 UTC 
SUMMARY
Start debug button is not clickable after starting a misconfigured debug session


STEPS TO REPRODUCE
1.  Configure a debugger session so that it fails
2. Start said debug
3. Wait for it to fail

OBSERVED RESULT

4. The start debug session is not selectable

EXPECTED RESULT
I can click on the start debug session button to start a new session

SOFTWARE/OS VERSIONS

Operating System: NixOS 25.11
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.8 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics
Memory: 16 GiB of RAM (14.8 GiB usable)
Graphics Processor: AMD Radeon Graphics
Comment 1 Waqar Ahmed 2025-10-05 11:07:36 UTC 
which debugger is it? Can you list exact steps to reproduce the issue?
Comment 2 Bug Janitor Service 2025-10-20 03:47:09 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 p3dimaria 2025-10-20 08:36:32 UTC 
(In reply to Waqar Ahmed from comment #1)
> which debugger is it? Can you list exact steps to reproduce the issue?

1. Add the folliwing configuration to debuggers.json (Note that this is nix language and will generate the correct json)

      node = {
        run = {
          request = ["${pkgs.vscode-js-debug}/bin/js-debug""\${#run.port}"];
          port = 0;
        };
        configurations = {
          "Node (Launch)".request = {
            type = "pwa-node";
            request = "launch";
            program = ''''${file}'';
            args = ''''${args|list}'';
            cwd = ''''${workdir}'';
            stopOnEntry = true;
            sourceMaps = true;
            protocol = "inspector";
            console = "integratedTerminal";
            enableDWARF = true;
            env = ''''${env|list}'';
          };
        };
      };
2. Select in the debug panel the Node configuration
3. Press the start debug
4. see it fail
5.see that the play button is now inactive
Comment 4 Bug Janitor Service 2025-11-04 03:47:46 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2025-11-19 03:47:07 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.