LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Desktop (http://www.linuxquestions.org/questions/linux-desktop-74/)
-   -   passing arguments to binary file called by launcher in GNOME desktop (http://www.linuxquestions.org/questions/linux-desktop-74/passing-arguments-to-binary-file-called-by-launcher-in-gnome-desktop-685569/)

majrys1962 11-23-2008 11:07 AM

passing arguments to binary file called by launcher in GNOME desktop
 
My distro is Debian Etch 4.0 , proc. AMD64,
Printing server CUPS.

The problem is that status monitor "cngpijmonip4500"
for my printer (original binary from *deb package from Canon Inc.)
works fine calling by command in terminal window (within GNOME-desktop)
and does not work guite properly when is called
as a GNOME desktop menu item.

Let's explain a little bit closer:
- in terminal window it gets correctly printer name
as an argument and every thing is O.K.
Title bar says "Canon iP4500 printer .." so it has received
the printer correctly from CUPS.
Executed (typed) in terminal window command is: cngpijmonip4500 iP4500

- when it is run as an menu item of GNOME desktop command:
Exec=/usr/bin/cngpijmonip4500 iP4500
in file: /usr/share/applications/xxx.desktop
it does not recognize the printer.
Title bar says: "Unknown printer ..."

Maybe it does not parse properly an argument in xxx.desktop
file or maybe there is any delay or something like this
in sequence of binary execution fromwithin
the GNOME desktop. And a client cngpijmonip4500
does not get the correct data from CUPS server.
Or maybe there is something wrong with permissions, but where ?

What is the difference in GNOME between calling binaries
from menu (launcher) and from terminal window ???
Does each of above ways require different permissions ???

Have anybody any suggestions how to fix it ?

penguiniator 12-11-2008 04:00 PM

The difference may be in the environment each startup method provides to the running program.


All times are GMT -5. The time now is 05:24 AM.