Ubuntu QA:
BlogBrainstormPackage status
Log in
Ubuntu QA
The Ubuntu community has contributed 13963 ideas, 66846 comments, 1291785 votes

Idea #8855: Attach hidden terminal to each application



up
12
down
Written by chig00 the 20 May 08 at 10:21. Category: System.
Related to: Nothing/Others. Status: New
Description
For every application which is running automatically create terminal, but don't show it by default. It should be accessible through button in WM menu for example after "move" and "resize" buttons, which will pop-up default terminal program with all messages that program has written to stdout. In this way it would be much more easier to diagnose some software problems for experienced users, and it won't influence usability of system for beginner users.
Tags: (none)

Attachments
No attachments.


Duplicates


Comments
cosechy wrote on the 20 May 08 at 11:20
I think a way redirecting output at run time for every program is better, just like the jackd for sound, but of course it will hard to implement :(

Auzy wrote on the 20 May 08 at 12:25
Actually, that should be easy cosechy.. Both is a good approach.. +1

Eldmannen wrote on the 20 May 08 at 13:35
It would use a lot of RAM, I think.

steve196 wrote on the 20 May 08 at 13:40
It stores short pieces of text and shows them on demand. That needs almost no RAM.

Auzy wrote on the 20 May 08 at 13:42
Yeah, you would do what terminal already does, a 100line buffer or so only

Lex wrote on the 20 May 08 at 14:04
There is another think to consider. Terminal output must be accessible if application just crashed. There could be some notification with terminal output or some log...

Primož Papič wrote on the 20 May 08 at 14:47
This would be a nice feature to go with Yakuke terminal.
You just pre F12 and get all the information about the program running. It should also show how much of the ram this particular programs is using.
Only problem that I think is, what if there are several programs running.
The one way to solve that is that terminal shows only the "focused" problem; right now this would be for me now Firefox.
The other maybe even better is to open tab for every program running. Lets say that while i surf the net i listen to some music, so I would have an tab for Firefox and one for Amarok.
+1

Rioting_Pacifist wrote on the 20 May 08 at 15:36
it can cause a major bottleneck on verbose programs.

Primož Papič wrote on the 21 May 08 at 10:38
You can start programs from terminal. Write firefox in terminal, and you'll see that it will start it. Only thing it writes just "loading" sequence, meaning it writes just when the program is started and then it dosen't change whatever your working with app (firefox in example).

Fevrin wrote on the 2 Jun 08 at 14:11
Wouldn't it be best to have all output be organized in the system logs?

gazilla wrote on the 2 Jun 08 at 14:32
Comments regarding RAM usage and the potential for bottleneck are implementation issues; something for the programmer to chew on later.
I'd love to be able to see what a given GUI app is spewing out to stdout, stderr and possibly syslog while it is running, without having to trawl through the logs. This feature should be seen to augment, not replace the existing logs.
We do something like this now with cron jobs. Extending it to screen apps should not be a biggy. In fact you could write the output away to somewhere like /var/log/pid/NNNN, then if the app crashed you'd have a record.
+1


Post your comment