GNOME Bugzilla – Bug 96581
g_spawn* do not expand ~/ => launchers don't understand ~/
Last modified: 2004-12-22 21:47:04 UTC
Hi, http://bugs.debian.org/165989 I tried creating a launcher on the panel for a script lying in ~/bin. Putting ~/bin/myscript in the "command" textbox of the launcher properties should have worked. But clicking on the launcher gives an error message saying failed to execute child process ... no such file or directory. Giving the full path as /home/sameerds/bin/myscript works correctly.
Still seeing this in 2.1.x
This seems to be a glib bug. Moving there and changing the summary.
*** Bug 96334 has been marked as a duplicate of this bug. ***
This is intentional, see the huge-ass security patch that KDE just came out with. That's why g_spawn_ doesn't expand things. You can make the shortcut something like "bash -c whatever" or the particular app such as the panel could add a shell to the command line. But g_spawn doesn't and shouldn't do it by default.
So... Moving this one back to gnome-desktop. Mark: glib doesn't expand things in g_spawn_, so do you think the libgnome-desktop should do it ?
I forgot to update the summary...
Hi, I'm taking a look at the debian bts bug reports about gnome-panel and found this bug to be still there on gnome 2.6.0. Will this be a wontfix or a patch for this would be welcome? Thanks,
I don't think doing tilde expansion for Exec in .desktop files is necessarily a security hole, but I still don't like the idea of us doing it. Also, the fact that this is very much an edge case makes me think this isn't worth doing.