[Bug 116351] Re: terminal window fork bomb

2007-08-23 Thread Kees Cook
This is not a software bug. One should not be running "grep" in /dev and /sys -- there can be multiple side-effects from attempting to read certain kernel files. ** Changed in: ubuntu Sourcepackagename: gnome-terminal => None Assignee: Ubuntu Desktop Bugs => Kees Cook Status: Incomple

[Bug 116351] Re: terminal window fork bomb

2007-08-23 Thread Pedro Villavicencio
It this still an issue? i don't get it in my desktop and as Sebastien said this is probably not a gnome bug. ** Changed in: gnome-terminal (Ubuntu) Status: New => Incomplete -- terminal window fork bomb https://bugs.launchpad.net/bugs/116351 You received this bug notification because you

[Bug 116351] Re: terminal window fork bomb

2007-06-28 Thread Micah Cowan
Gerald, note that X-ing out of a terminal because of some program may not be the best way to deal with that: if the program is ignoring SIGINT (the ^C signal), it could be ignoring SIGHUP (the "lost terminal" signal) as well; better to open another terminal, find the offending process's pid, and us

[Bug 116351] Re: terminal window fork bomb

2007-06-28 Thread Sebastien Bacher
doesn't really look like a gnome bug -- terminal window fork bomb https://bugs.launchpad.net/bugs/116351 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu

[Bug 116351] Re: terminal window fork bomb

2007-06-02 Thread Gerald M
Did some more digging.. the last entry in kern.log when the above command is excuted looks like this Jun 3 01:18:21 gerry-desktop kernel: [ 362.399025] PPP generic driver version 2.4.2 Jun 3 01:18:21 gerry-desktop kernel: [ 362.445381] tun: Universal TUN/TAP device driver, 1.6 Jun 3 01:18:

[Bug 116351] Re: terminal window fork bomb

2007-06-02 Thread Anders Kaseorg
Try using grep --devices=skip, so that grep doesn’t try to read from special devices (which can cause unpredictable results). See the grep manpage for more information. -- terminal window fork bomb https://bugs.launchpad.net/bugs/116351 You received this bug notification because you are a member

[Bug 116351] Re: terminal window fork bomb

2007-05-29 Thread Gerald M
I will investigate further on my end. The only thing that comes to mind is that i'm using an nvidia restricted driver. Also the line "grep: /lib/udev/devices/net/tun: File descriptor in bad state" has popped up before when doing grep searches and forced me to X out of the terminal window because

[Bug 116351] Re: terminal window fork bomb

2007-05-29 Thread Sebastien Bacher
Doesn't happen on my desktop ** Changed in: gnome-terminal (Ubuntu) Importance: Undecided => Medium Assignee: (unassigned) => Ubuntu Desktop Bugs -- terminal window fork bomb https://bugs.launchpad.net/bugs/116351 You received this bug notification because you are a member of Ubuntu Bugs

[Bug 116351] Re: terminal window fork bomb

2007-05-27 Thread Jérôme Guelfucci
I can't reproduce this, the first time, as well as the second, I get : grep: /dev/.tmp-22-0: Aucun medium trouvé(no media found) grep: /dev/vboxdrv: Argument invalide(invalid argument) grep: /dev/parport0: Argument invalide grep: /dev/nvidia0: Argument invalide grep: /dev/n

[Bug 116351] Re: terminal window fork bomb

2007-05-23 Thread didier
** Changed in: gnome-terminal (Ubuntu) Sourcepackagename: None => gnome-terminal -- terminal window fork bomb https://bugs.launchpad.net/bugs/116351 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubunt

[Bug 116351] Re: terminal window fork bomb

2007-05-22 Thread Gerald M
** Description changed: - Ubuntu 7.10 using gnome + Ubuntu 7.04 using gnome grep (GNU grep) 2.5.1 Note: I did not test with any other variation of the command, I simply stuck to the command that caused the problem (even if the command is not proper). Following the steps below I can re

[Bug 116351] Re: terminal window fork bomb

2007-05-22 Thread Gerald M
** Description changed: Ubuntu 7.10 using gnome grep (GNU grep) 2.5.1 Note: I did not test with any other variation of the command, I simply stuck to the command that caused the problem (even if the command is not proper). Following the steps below I can replicate the problem every