EDB won't function

ARobin

I am not a Linux expert, having been with Linux for about 1.5 years now. I recently installed and configured Solus, and everything works just fine, except for EDB. EDB is debugger that is only provided as a flatpak program. I have an app I am testing with EDB that runs just fine when I select it from Dolphin, but EDB won't run it at all, saying "Failed to open and attach to process: execv() failed: No such file or directory". I searched the Internet and I guess no one has ever used the flatpack version of EDB, so I can't find any help. The error message makes no sense whatsoever, as both the file and directory most definitely do exist, so what is the actual error and how can I resolve it?

I am using Solus 4.7 with the following details:
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.8.3
Kernel Version: 6.14.6-319.current (64-bit)
Graphics Platform: Wayland
Processors: 20 × 12th Gen Intel® Core™ i7-12700F
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060
Manufacturer: Micro-Star International Co., Ltd.
Product Name: US Desktop Codex R
System Version: 1.0

PS -- I installed flatseal and enabled everything, but it still won't function properly. In fact, loading an app will often cause EDB to freeze so I am forced to terminate the process.

brent

ARobin
I searched the internet and this is a common error message but I can't find the commonalities...but did find a discussion about EBD and this message: https://github.com/eteran/edb-debugger/issues/805

looks like they gave the solution to OP in a very vague way then walked away from the thread..maybe someone could read that thread and explain it. I didn't get it

you could also install and uninstall it. make sure solus is up to date. find an appimage? or a standalone binary app?

ARobin

brent I searched the internet and this is a common error message but I can't find the commonalities...but did find a discussion about EBD and this message: https://github.com/eteran/edb-debugger/issues/805

brent looks like they gave the solution to OP in a very vague way then walked away from the thread..maybe someone could read that thread and explain it. I didn't get it

The way I understood it, they can tell that "No such file or directory" means the client app requires a certain library to run, but it can't be accessed within a flatpak. To me that sounds like the EDB flatpak is incomplete. I then looked up the prerequisites for EDB and I noticed that EDB required Capstone and Graphviz, but Capstone wasn't installed, yet installing Capstone didn't change anything. That in turn made me wonder if Capstone and Graphviz needed to be a part of the EDB environment instead of being installed outside of the EDB environment as is being done now? I don't understand flatpaks enough to determine anything for a fact yet.

brent you could also install and uninstall it. make sure solus is up to date. find an appimage? or a standalone binary app?

I have uninstalled and installed EDB with a very up-to-date Solus distro. EDB used to have an appimage but since they couldn't maintain it, they deleted it. See https://github.com/eteran/edb-debugger/issues/781.

There is no standalone binary app for Solus, but I guess I could create one myself in a worse case scenario. I mean although I am not a programming newbie, I am a Linux newbie, so I still have no idea how to do this properly. I went to https://help.getsol.us/docs/packaging/creating-a-new-package which says I need a a GIT account, and I am trying to get as far away from Microsoft as possible, so I have no GIT account (I use Fossil for version control). So if I get the source code and follow the rest of the directions, would it work? That sounds horrifying to a newbie like me so I want to delay that option as long as possible.

Speaking of not having a GIT account, could someone go to https://github.com/eteran/edb-debugger and ask Evan Teran if he would be willing to look into this for me?

ARobin

brent I searched the internet and this is a common error message but I can't find the commonalities

Okay, I found out something new. I tried running edb from the command line, first with a running program using its PID:

flatpak run io.github.eteran.edb-debugger --attach 54321

This process will not load and the command line responds with

Failed to attach to process. No such process

Which of course is incorrect. So then I tried the same thing with a non-graphical-based program:

flatpak run io.github.eteran.edb-debugger --run /bin/ls

ls will load BUT the command line responds with

Wayland does not support QWindow::requestActivate()

I didn't go beyond that point because the fact I can load command line programs but not graphical ones, seems to strongly indicate the edb can't run Wayland. Apparently edb is incompatible with Wayland.

Staudey

ARobin I went to https://help.getsol.us/docs/packaging/creating-a-new-package which says I need a a GIT account, and I am trying to get as far away from Microsoft as possible, so I have no GIT account (I use Fossil for version control). So if I get the source code and follow the rest of the directions, would it work? That sounds horrifying to a newbie like me so I want to delay that option as long as possible.

To be clear, you only need a GitHub account (not "GIT") to submit pull requests. If you just want to clone the repository and work on it for your own purposes, that's not necessary. You only need git, the software, for this, which is not associated with Microsoft. But you won't be able to submit your changes/additions back to the Solus repository.

ARobin

Staudey To be clear, you only need a GitHub account (not "GIT") to submit pull requests. If you just want to clone the repository and work on it for your own purposes, that's not necessary. You only need git, the software, for this, which is not associated with Microsoft. But you won't be able to submit your changes/additions back to the Solus repository.

That's good news, so thanks so much for the clarification. I didn't know that.

As for participating in discussions or making requests, Microsoft makes it very clear I need to sign up, and I apologize, but I don't trust Microsoft. But you know what? It's ok because I found Evan Teran's email on his webpage (and Evan is the author of EDB), so I'm going to email him now and see what he thinks about this issue.

brent

ARobin . Apparently edb is incompatible with Wayland.

I wish there was a lit of apps published that were incompatible with Wayland. that way one might be prepared for alternatives while using that environment. This was a long battle for you.