[maemo-developers] [maemo-developers] use shell script to start application
From: Jari Tenhunen jari.tenhunen at iki.fiDate: Fri Jan 20 14:48:21 EET 2006
- Previous message: [maemo-developers] use shell script to start application
- Next message: [maemo-developers] use shell script to start application
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Jan 20, 2006 at 12:37:03PM +0100, Johannes Eickhold wrote: > > gpsdrive has to be started via the script "usr/bin/gpsdrive.sh". > > If I specify this file in the .desktop file, gpsdrive can be started in > > the correct way from the menu and via "run-standalone.sh > > usr/bin/gpsdrive.sh" but doesn't show up in the task navigator. > > > > If I specify ".../usr/bingpsdrive" (the binary executable) in > > the .desktop file, only the application is startet broken (needed parts > > from the script are not executed) BUT it shows up in the task navigator > > after that. If I start it via run-standalone.sh everyting is fine (e.g. > > correct startup AND showing in task navigator). > > > > How can I fix this? For me it works when I add the name of the binary (in this case gpsdrive) to the StartupWMClass field of the .desktop file. According to the tutorial, StartupWMClass is needed "when binary name is different than D-BUS service name". Based on my experiments it is also needed if there is no X-Osso-Service field in the .desktop file. To my knowledge, StartupWMClass should actually match the WM_CLASS property of the application, which usually is the name of the binary but not always. I recently had a similar problem where the application had a weird WM_CLASS that differed from the binary name. How this thing connects to the shell script issue, I don't know. Br, Jari -- Jari Tenhunen, stardate [-29]5191.33 :wq
- Previous message: [maemo-developers] use shell script to start application
- Next message: [maemo-developers] use shell script to start application
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]