VSCodium not visible in system monitor (KDE Plasma)

Desktop Environments Plasma
1

Hello everyone,
I know this is not directly related to EOS but this is the only Linux community that i am a part of, so any help is appreciated

Recently i installed vscodium-bin from AUR and I was curious to know its resource usage but this app isn’t visible in system monitor.

vscodium-kde-problem
vscodium-kde-problem1742×428 79.5 KB

Is this the case with everyone else or do i need to setup something ?

2

What user was vscodium launched as? Can you check with top or htop?

3

Should be visible under “Processes” tab. Type “code” in search box and you’ll see it.

4

I’ve only one user.
Yes i can see it using htop

5

Yes i can see it now.
The processes tab is like using htop (No consolidated figures)
But why isn’t it like other applications like firefox and obsidian

6

Apparently, applications started via dbus won’t show up on the system monitor’s applications list. Someone reported a bug here: https://bugs.kde.org/show_bug.cgi?id=463780

You can verify if this is true by looking at vscodium’s desktop file. Navigate to /usr/share/applications and look for vscodium.desktop or something similar. Inside the desktop file, look for the Exec entry.

7

These are the contents of the .desktop file

[Desktop Entry]
Name=VSCodium
Comment=Code Editing. Redefined.
GenericName=Text Editor
Exec=/usr/bin/codium --unity-launch %F
Icon=vscodium
Type=Application
StartupNotify=false
StartupWMClass=VSCodium
Categories=Utility;Development;IDE;
MimeType=text/plain;inode/directory;
Actions=new-empty-window;
Keywords=vscode;

[Desktop Action new-empty-window]
Name=New Empty Window
Exec=/usr/bin/codium --new-window %F
Icon=vscodium

Is it started via dbus ?

8

According to the Desktop Entry Specification, for Dbus activation:

Applications that support being launched by D-Bus must implement the following interface (given in D-Bus introspection XML format):

  <interface name='org.freedesktop.Application'>
    <method name='Activate'>
      <arg type='a{sv}' name='platform_data' direction='in'/>
    </method>
    <method name='Open'>
      <arg type='as' name='uris' direction='in'/>
      <arg type='a{sv}' name='platform_data' direction='in'/>
    </method>
    <method name='ActivateAction'>
      <arg type='s' name='action_name' direction='in'/>
      <arg type='av' name='parameter' direction='in'/>
      <arg type='a{sv}' name='platform_data' direction='in'/>
    </method>
  </interface>

The application must name its desktop file in accordance with the naming recommendations in the introduction section (e.g. the filename must be like org.example.FooViewer.desktop). The application must have a D-Bus service activatable at the well-known name that is equal to the desktop file name with the .desktop portion removed (for our example, org.example.FooViewer). The above interface must be implemented at an object path determined as follows: starting with the well-known D-Bus name of the application, change all dots to slashes and prefix a slash. If a dash (‘-’) is found, convert it to an underscore (‘_’). For our example, this is /org/example/FooViewer.

9

Ok so from what i can understand this is not related to dbus

10

I just installed Code - OSS to check whether that will be shown and yes it does show in the system monitor

image
image889×154 18.2 KB

This is the corresponding .desktop file:

[Desktop Entry]
Name=Code - OSS
Comment=Code Editing. Redefined.
GenericName=Text Editor
Exec=/usr/bin/code-oss --unity-launch %F
Icon=com.visualstudio.code.oss
Type=Application
StartupNotify=false
StartupWMClass=code-oss
Categories=TextEditor;Development;IDE;
MimeType=text/plain;application/x-code-oss-workspace;
Actions=new-empty-window;
Keywords=vscode;

X-Desktop-File-Install-Version=0.26

[Desktop Action new-empty-window]
Name=New Empty Window
Exec=/usr/bin/code-oss --new-window %F
Icon=com.visualstudio.code.oss

Note: Code-OSS is from official repository while VSCodium-bin is from the AUR

1 Like