FS#37875 - [deluge] differences in x86_64 and i686 regarding /usr/sbin

Attached to Project: Arch Linux
Opened by John (graysky) - Friday, 22 November 2013, 11:08 GMT
Last edited by Jan Alexander Steffens (heftig) - Saturday, 23 November 2013, 13:22 GMT
Task Type Support Request
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Can someone explain this observation?

Grepping the relevant parts from `ps aux | grep deluge` an i686 machine shows that python2 is calling /usr/sbin/deluge-gtk but the same command on an x86_64 box shows python2 calling /usr/bin/deluge-gtk

On i686: /usr/bin/python2 /usr/sbin/deluge-gtk
On x86_64: /usr/bin/python2 /usr/bin/deluge-gtk

Additional info:
* package version(s): 1.3.6-3

Steps to reproduce:
1) Run deluged
2) Run deluge-gtk
3) Run: ps aux | grep deluge
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Saturday, 23 November 2013, 13:22 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Inconsequential. Probably more a problem of LXDE's PATH, anyway.
Comment by John (graysky) - Friday, 22 November 2013, 20:38 GMT
Upon further study, it seems that launching deluge-gtk from the provided deluge.desktop (lxde) causes this behavior. Launching deluge-gtk from a shell does not. This is true for both i686 and x86_64.

If I modify /usr/share/applications/deluge.desktop using the fully qualified paths for the "TryExec=" and "Exec=" entries, deluge-gtk shows up as /usr/bin/deluge-gtk as it should, but the backend daemon, deluged, still shows up as /usr/sbin/deluged if I don't manually start it from the shell.

Loading...