Deluge not recognised

[Paddy Landau]

Caffeine is such a lovely app to have, thank you.

In Preferences, I have added virtualbox to the list of processes, and it works: whenever I have Virtual Box running, Caffeine prevents the screen-saver.

However, it does not recognise Deluge. I have added deluge-gtk to the list of processes, but Caffeine does not recognise when Deluge is running.

What am I doing wrong?

[Brad Smith]

That's a tricky one. I'm afraid I'm not familiar with Deluge. Perhaps
there is another process that is involved that also needs to be added
to the list? Maybe there are two processes, 'deluge-gtk' and 'deluge'
or something.

That's the only suggestion that comes to mind at the moment. It may be
possible also to try writing a little wrapper bash script around
deluge and then perhaps adding that to Caffeine's list.

Best of luck,
Brad

[Paddy Landau]

Brad, thanks for the reply.

Unfortunately, your idea does not work. Here is why...

I have been taking a close look at the process names, and I am now thoroughly confused.

If I add virtualbox to Caffeine's list, I can see that Caffeine recognises it, because (1) it adds the Virtual Box logo next to the item, and (2) it suspends the screen-saver when I start Virtual Box.

However, if I instead add VirtualBox (note the change in case), Caffeine does neither.

The process names for Virtual Box are:

• /usr/lib/virtualbox/VirtualBox
• /usr/lib/virtualbox/VBoxXPCOMIPCD
• /usr/lib/virtualbox/VBoxSVC --auto-shutdown

I notice that Deluge is somewhat different. Caffeine does not recognise it in the list (i.e. no logo and no suspend) whether I use deluge or Deluge. However, I notice the Deluge is, in fact, a Python program, and so the process name is Python's with Deluge as the parameter:

• /usr/bin/python /usr/bin/deluge-gtk
  

That may well explain why Caffeine does not recognise it.

Creating a wrapper does exactly the same thing, sadly. I wrote a tiny script to start Deluge, hoping for Caffeine to catch that name, but it does not. Look at the process name:

• /bin/bash /home/paddy/bin/startDeluge
  

It's no good having Caffeine check for python or bash, since there are always such processes running!

Is there any documentation that explains how Caffeine checks for process names? That may help me find what to do. It would also explain why Caffeine recognises virtualbox but not VirtualBox. (I don't know Python, so trying to look through the code would probably take me days, if not weeks!)