SavingGoogleCode / tint2

tint2 is a lightweight panel/taskbar.
GNU General Public License v2.0
0 stars 0 forks source link

tint2 - running a launcher from .desktop file creates two processes, how stop? #452

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Run tint2 svn and create a launcher in the config
2. launcher_item_app = /path/to/appname.desktop
3. Click on the launcher and then check htop and you'll see two processes

What is the expected output? What do you see instead?

Should only see one process for the application not two, one which is sh -c 
being run.

What version of the product are you using? On what operating system?

Tint2 svn on Slackware 14.1 x86_64 with Openbox 3.5.2

So again, as example when I click a launcher I created in the tint2 config at;

~/.config/tint2/tint2

# Each launcher_item_app must be a full path to a .desktop file
launcher_item_app = /usr/share/applications/spacefm.desktop
launcher_item_app = /home/user/.local/share/applications/openvpn.desktop
launcher_item_app = /home/user/.local/share/applications/keepassx.desktop
launcher_item_app = /home/user/.local/share/applications/bleachbit.desktop

And then I click on one of the launcer icons, bleachbit as an example I see in 
htop two process like this;

/bin/sh -c bleachbit > /dev/null 2>&1
python /usr/bin/bleachbit

I should not be seeing the top process for running sh -c which seems to come 
from how the tint2 config works as a .sh shell file.

Does anyone know how I can disable this so I only get one running process like 
only the?

python /usr/bin/bleachbit

Thank you...

Original issue reported on code.google.com by ears....@gmail.com on 3 Nov 2014 at 1:29

GoogleCodeExporter commented 9 years ago
My mistake it was the .desktop file causing this, I've fixed the issue, so 
please disregard this!

Original comment by ears....@gmail.com on 3 Nov 2014 at 4:10

GoogleCodeExporter commented 9 years ago
Thanks for letting us know it's not a problem, closing the bug report.

Original comment by mrovi9...@gmail.com on 21 Jan 2015 at 10:38