nokyan / resources

Keep an eye on system resources
GNU General Public License v3.0
748 stars 56 forks source link

[BUG] Apps and Processes tabs do not work #374

Open cassiofb-dev opened 2 weeks ago

cassiofb-dev commented 2 weeks ago

Is there an existing issue for this?

Current Behavior

Apps and Processes tab do not work. (The others like CPU, memory, gpu, drives and network are ok).

Expected Behavior

Both tabs (Apps and Processes) are only a screen without info. I think my system is not supported but it would be good to have a user friendly message.

Steps To Reproduce

  1. Open the app
  2. Got to processes or apps tab
  3. See a blank screen without any message

Environment

Program Version: 1.6.0
Package type: Flatpak
System: Chimera Linux (KDE Plasma 6.2)
Hardware info: R7 5700x, 32GB RAM, RX 6750XT

Anything else?

image

nokyan commented 2 weeks ago

Hi, Resources requires systemd for application detection. There may also be something going wrong when scanning processes since Resources could also rely on some systemd-specific features. I'll see if I can implement an error message when process scanning breaks, though I'm afraid that I'm currently not planning to support init systems other than systemd.

cassiofb-dev commented 2 weeks ago

Thats fine, only an warning message is ok. Was the processes tab supposed to work without systemd tho?

nokyan commented 2 weeks ago

Processes tab should work, can you please run one of the following command in your terminal and send me the output? If you've installed Resources as a user-wide Flatpak: ~/.local/share/flatpak/app/net.nokyan.Resources/current/active/files/libexec/resources/resources-processes -o -r If you've installed Resources as a system-wide Flatpak: /var/lib/flatpak/app/net.nokyan.Resources/current/active/files/libexec/resources/resources-processes -o -r

nokyan commented 2 weeks ago

Doing some further reseach about Chimera Linux, it seems that Chimera uses musl as its libc while Resources is built against glibc. Since Resources uses a binary (also built against glibc) that is spawned outside Flatpak's sandbox to gather process information, it won't work on non-glibc distros.

cassiofb-dev commented 2 weeks ago

yeah, this is the output of the command:

❯ ~/.local/share/flatpak/app/net.nokyan.Resources/current/active/files/libexec/resources/resources-processes -o -r
exec: Failed to execute process '/home/cassio/.local/share/flatpak/app/net.nokyan.Resources/current/active/files/libexec/resources/resources-processes': The file exists and is executable. Check the interpreter or linker?

For now its better to close this issue with not planned tag?

nokyan commented 2 weeks ago

yeah, this is the output of the command:

❯ ~/.local/share/flatpak/app/net.nokyan.Resources/current/active/files/libexec/resources/resources-processes -o -r
exec: Failed to execute process '/home/cassio/.local/share/flatpak/app/net.nokyan.Resources/current/active/files/libexec/resources/resources-processes': The file exists and is executable. Check the interpreter or linker?

For now its better to close this issue with not planned tag?

I think I'll use this issue for the error message and maybe some form of musl compatibility if it's not too much of a maintenance burden for me. :)