Executing phcode in terminal does nothing.

[anoduck]

It might have to do with running Kali Linux and not your standard Debian or Ubuntu, but when I attempt to run phoenix from the terminal with phcode, it does nothing and never backgrounds or outputs any errors. I literally type phcode, then hit <enter>, the cursor drops to the next line, and it stays that way until I hit Ctrl-c several minutes later.

[charlypa]

@anoduck
are you able to launch application from start menu?

[charlypa]

@anoduck
Technically we just need webkit alone to work desktop type does not matter. There are a few cases where graphics drivers could cause issues.

@abose would you guide @anoduck on how to debug?

[anoduck]

@charlypa It might be the case my old development box is just too old. It is a real possibility.

[abose]

phnode is not supported to be executed directly, so the logs above for phnode can be ignored.

Try running phoenix-code binary directly and you should see any errors if any in console.

Please try this docs https://docs.phcode.dev/docs/Linux/#manual-installation

[anoduck]

Exactly the same result with no output. The cursor drops to the next line, there is a short increase in system load, and then the program sleeps. I have even gone so far as building Phoenix manually, and it didn't make a difference.

Since the configuration of Sway on Kali is something wholly of my own concoction, the ability to reproduce the error is questionable under best circumstances. Kali Linux does have an official port of Kali for the i3 Desktop, something I have wanted to revert to. This should provide nearly identical testing conditions to my current Desktop, less one critical factor, me.

So, unless similar issues occur with Sway involving different users, I suggest we put this one on the back burner, and I will revisit when I reconfigure my desktop to run I3.

[anoduck]

Reopening this issue since it was never resolved. The desktop has migrated from sway to hyprland, and nothing has changed. I was wondering if more headway has been made towards discovering what could possibly be causing this issue.