deadbeef and conky's ${if_running} conditional

[Oleksiy-Yakovenko]

Original issue 1189 created by Alexey-Yakovenko on 2014-09-05T18:02:10.000Z:

(This is a conky issue, so if you don't have conky installed, just disregard this report.)

I've run into a problem that deadbeef doesn't seem to identify itself as 'deadbeef' although it shows so in ps -ef | grep dead .

First of all, some example (within ~/.conkyrc) that DOES work:

${if_running firefox} ${color ff0000}this is a test ${endif}

But the following will fail:

${if_running deadbeef} ${color ff0000}this is another test ${endif}

Tried them ALL. deadbeef /usr/bin/deadbeef deadbeef-devel deadbeef-main (as I found on some forum)

...no avail. Also tried -x flag (see below for that).

A line like ${execp /usr/bin/deadbeef --nowplaying "%a - %t"}

will works perfectly once the ${if...}...${endif} block is commented out. Somehow deadbeef must be using an internal name I don't know of?

Additional info excerpt from http://conky.sourceforge.net/variables.html :

if_running (process)

if PROCESS is running, display everything $if_running and the matching $endif. This uses the ``pidof'' command, so the -x switch is also supported.

[Oleksiy-Yakovenko]

Comment #1 originally posted by Alexey-Yakovenko on 2014-09-05T19:44:58.000Z:

such questions should be posted on general linux forums.

[Oleksiy-Yakovenko]

Comment #2 originally posted by Alexey-Yakovenko on 2014-09-05T22:04:39.000Z:

Normally they should!

But as I've shown you, the very same attempt with firefox (et al) works, just with ddb it fails. It would only be sensible to post it on general linux forums if it failed with ALL programs. But with other programs it worked...(tried 5)

[Oleksiy-Yakovenko]

Comment #3 originally posted by Alexey-Yakovenko on 2014-09-06T09:10:44.000Z:

conky will use "pidof deadbeef" shell command. find the name that works, and use that in config. perhaps using htop will help to find the process name. it might be called something like deadbeef-main.

[Oleksiy-Yakovenko]

Comment #4 originally posted by Alexey-Yakovenko on 2014-09-06T20:27:37.000Z:

htop? Never heard of it. Thanks, will RTFM myself thru it a little...

And yes, I knew about "pidof deadbeef" and that conky does it that way. But pidof gives a PID, and that is a number. This is my actual problem. I'm in need of the name, not the ID number.

[Oleksiy-Yakovenko]

Comment #5 originally posted by Alexey-Yakovenko on 2014-09-06T20:31:14.000Z:

htop? Never heard of it. Thanks, will might myself thru it a little...

And yes, I knew about "pidof deadbeef" and that conky does it that way. But pidof gives a PID, and that is a number. This was my actual problem. I'm in need of the name, not the ID number.

-- SOLVED --

Excuse me for having misused this bug tracker, but it would really be nicer if deadbeef did identify itself as 'deadbeef'.

Currently, it will identify itself in TASK MANAGER (this is how I "solved" the problem) as:

'deadbeef-gtkui'. No wonder I was unable to figure out the correct directive.

[Oleksiy-Yakovenko]

Comment #6 originally posted by Alexey-Yakovenko on 2014-09-06T20:34:53.000Z:

htop? Never heard of it. Thanks, might RTFM myself thru it a little... Well, maybe my 'Buntu "Task Manager" might do the trick as well...

BTW, I knew about "pidof deadbeef" and that conky does it that way. But pidof gives a PID, and that is a number. This was my actual problem. I'm in need of the name, not the ID number.

-- SOLVED --

Excuse me for having misused this bug tracker, but I stand my point that it would really be nicer if deadbeef did identify itself as 'deadbeef'. So there was no need to treat me like a rookie who doesn't know why he should not ask general linux questions on bug trackers.)

Currently, it will identify itself in TASK MANAGER as:

'deadbeef-gtkui'.

No wonder I was unable to figure out the correct directive. Anyways, I have a solution now, albeit not an ideal one.

[Oleksiy-Yakovenko]

Comment #7 originally posted by Alexey-Yakovenko on 2014-09-06T20:35:54.000Z:

htop? Never heard of it. Thanks, might RTFM myself thru it a little... Well, maybe my 'Buntu "Task Manager" might do the trick as well...

BTW, I knew about "pidof deadbeef" and that conky does it that way. But pidof gives a PID, and that is a number. This was my actual problem. I'm in need of the name, not the ID number.

-- SOLVED --

Excuse me for having misused this bug tracker, but I stand my point that it would really be nicer if deadbeef did identify itself as 'deadbeef'. (So there was no need to treat me like a rookie who doesn't know why he should refrain from asking general linux questions on bug trackers. Whenever I do, I have a good reason why.)

Currently, it will identify itself in TASK MANAGER as:

'deadbeef-gtkui'.

No wonder I was unable to figure out the correct directive. Anyways, I have a solution now, albeit not an ideal one.

[Oleksiy-Yakovenko]

Comment #8 originally posted by Alexey-Yakovenko on 2014-09-06T20:51:36.000Z:

htop? Never heard of it. Thanks, might RTFM myself thru it a little... Well, maybe my 'Buntu "Task Manager" might do the trick as well...

BTW, I knew about "pidof deadbeef" and that conky does it that way. But pidof gives a PID, and that is a number. This was my actual problem. I'm in need of the name, not the ID number.

-- SOLVED --

Excuse me for having misused this bug tracker (IYO), but I stand my point that it would really make things a lot easier if deadbeef did identify itself as 'deadbeef'. (So there was no need to treat me like a rookie who doesn't know why he should refrain from asking general linux questions on bug trackers. Whenever I do, I have a good reason why.)

Well, currently, it will identify itself in TASK MANAGER as:

'deadbeef-gtkui'.

No wonder I was unable to figure out the correct directive. Anyways, I have a solution now, albeit not an ideal one.

Here's another handy tool:

$ pstree -pc | grep deadb

reveals ddb is split up in SIX different sub-processes. Not too shabby.