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 621507 - External tools can't be stopped
External tools can't be stopped
Status: RESOLVED INCOMPLETE
Product: gedit-plugins
Classification: Other
Component: General
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2010-06-14 08:36 UTC by Jef Driesen
Modified: 2019-03-23 20:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jef Driesen 2010-06-14 08:36:38 UTC 
When I launch an external tool like the builtin make, and try to abort it with the stop button, it doesn't work. The shell output pane shows the message "Stopped. Exited: 15", but then it keeps running.
Comment 1 Raphaël 2011-09-20 13:08:24 UTC 
Same here, I had a while(true) running in a C program launched from external tools, and clicking stop didn't stop anything. I had to kill the program from the command line.

(gedit 2.30.3)
Comment 2 Ignacio Casal Quinteiro (nacho) 2011-10-11 20:53:48 UTC 
Here it works perfect,
I tried the next:

#!/bin/sh
while(true)
do
	echo "blah"
done

The button was available to be stopped and after pressing the tool was stopped correctly. Please let us know if you still have this problem with gedit >= 3.0
Comment 3 Raphaël 2011-11-01 15:26:56 UTC 
Well, I switched to Ubuntu 11.10 (gedit 3.2.1) and it seems external tools are completely f*cked up here...
I tried :
  #!/bin/sh
  while(true)
  do
      echo "blah"
  done
and it froze gedit, then I tried the same with a c program (while(1) printf(...);) and an external tool launching a.out; "stop" didn't work, so I killed a.out, and then gedit took the whole CPU again...
Plus there is this : https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/877237

So I cannot help much right now I guess.
I'll keep you up if I manage to reproduce the problem, or if I see it disappeared.
Comment 4 Fabio Durán Verdugo 2011-12-21 03:07:09 UTC 
for me work fine at ubuntu 12.04
Comment 5 Akhil Laddha 2012-02-13 12:08:27 UTC 
Raphaël, can we close the bug ?
Comment 6 Pedro Villavicencio 2012-04-01 00:21:02 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!