After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 81199 - gsearchtool should use g_spawn* instead of custom fork/exec commands
gsearchtool should use g_spawn* instead of custom fork/exec commands
Status: VERIFIED FIXED
Product: gnome-utils
Classification: Deprecated
Component: gsearchtool
trunk
Other All
: High enhancement
: GNOME2.2
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-05-09 03:34 UTC by Jonathan Blandford
Modified: 2014-07-17 07:58 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Jonathan Blandford 2002-05-09 03:34:43 UTC 
SSIA
Comment 1 Glynn Foster 2002-05-10 23:49:12 UTC 
g_spawn...hum, scarey code.
Comment 2 Luis Villa 2002-05-13 01:22:32 UTC 
If the current code works, why is this 2.0.0?
Comment 3 Glynn Foster 2002-05-14 12:14:46 UTC 
punt.
Comment 4 George Lebl 2002-06-04 14:29:58 UTC 
Why is this even 2.0.1, it doesn't matter.  In fact I think it just
might be harder to use gspawn then custom fork/exec given what I
remember of how gsearchtool works.  I definately WONTFIX this :).  I
dunno, jrb: what do you think?
Comment 5 Jonathan Blandford 2002-06-04 15:55:28 UTC 
it certainly isn't a blocker.  It was just a suggestion for cleaning
up the code.  It definitely is easier than the custom code, though.
Comment 6 Luis Villa 2002-07-02 16:54:37 UTC 
High priority enhancement for 2.1.x?
Comment 7 Glynn Foster 2002-07-03 18:42:59 UTC 
definitely not 2.0.x now ;)
Comment 8 Dennis Cranston 2002-07-24 15:48:32 UTC 
FYI, I am doing the coding for this bug.  I have it working, but I
need to cleanup my patch.
Comment 9 Dennis Cranston 2002-07-31 02:39:25 UTC 
Fix applied to CVS (HEAD).
Comment 10 frank.huber 2014-07-17 07:58:06 UTC 
*** Bug 731192 has been marked as a duplicate of this bug. ***