[Bug 104013] Re: System monitor: Resources displays 99% to 100% cpu

2007-11-06 Thread Jesse Aldridge
I was having the same problem, but brettalton's explanation helped understand it. I hadn't realized the system monitor only showed "My Processes" by default. I think most semi-technical people like me would have this problem. Maybe the "view process" options should be moved outside of the main me

[Bug 157266] Re: gnome-terminal with --command option fails after first time

2007-10-28 Thread Jesse Aldridge
Well, I wanted to make a nautilus script (http://g-scripts.sourceforge.net/faq.php";>like these) so that I could right-click on any ruby file and run it through the ruby interpreter. I ended up getting it to work via the two solutions mentioned, so it's not really a problem for me any more. The

[Bug 157266] Re: gnome-terminal with --command option fails after first time

2007-10-27 Thread Jesse Aldridge
In the terminal you can go "Edit"->"Current Profile"->"Title and Command" and set "When command exits" to "Hold terminal open." Your example works for me also, so there's another work-around. Note that I'm still new to Linux so I may just be doing something dumb :) -- gnome-terminal with --comm

[Bug 157266] Re: gnome-terminal with --command option fails after first time

2007-10-25 Thread Jesse Aldridge
Can work around by using xterm instead: >xterm -e "echo test; read" -- gnome-terminal with --command option fails after first time https://bugs.launchpad.net/bugs/157266 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bu

[Bug 157266] gnome-terminal with --command option fails after first time

2007-10-25 Thread Jesse Aldridge
Public bug reported: Binary package hint: gnome-terminal Open the terminal ( Accessories -> Terminal ) > gnome-terminal --command "echo test" Close the spawned window. > gnome-terminal --command "echo test" Window spawns, but there's no output. Using Ubuntu 7.10 ** Affects: gnome-terminal (