On 20 September 2012 19:48, Sworddragon <819...@bugs.launchpad.net> wrote:
> So there is no difference for me.
My mistake then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/819842
Title:
Commands
> If so then do not use nohup for this purpose.
Is there a special reason? For example I'm opening htop to watch the
process list and after this I'm opening a new terminal and executing
"nohup scite > /dev/null 2>&1 &" in it:
| /sbin/init
|- x-terminal-emulator -e htop
|-- /bin/bash
|--- scite
|
On 20 September 2012 19:17, Sworddragon <819...@bugs.launchpad.net> wrote:
> I don't know it but with nohup the process will be a direct child of
> init after closing the terminal.
If so then do not use nohup for this purpose.
--
You received this bug notification because you are a member of Ubu
> If you want to start an arbitrary program, use the run dialog (ALT-F2)
– this is what it's for.
I have never thought to use this but it is a good idea.
> Not init (exit from the desktop session and see that the program in
question is closed).
I don't know it but with nohup the process will be
On 20 September 2012 18:29, Sworddragon <819...@bugs.launchpad.net> wrote:
> Are you sure that this is the correct behavior?
Yes.
> Some time before I have
> opened this ticket it worked like expected: If I have started an
> application in the background I could close the terminal without closing
Are you sure that this is the correct behavior? Some time before I have
opened this ticket it worked like expected: If I have started an
application in the background I could close the terminal without closing
the application. The only explanation would be that another process
become the new parent
Bug #376147 tracks the issue of gnome-terminal not warning that closing
the terminal will terminate background processes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/819842
Title:
Commands in the
> The same problem appears in LXTerminal too. Maybe a
> shared component is affected by this problem.
FYI the shared component in this case is the shell (usually
/usr/bin/bash or similar) which is run by these terminal programs.
Processes started by a shell are (typically) terminated when that sh
Comment #1 is correct. This is the intended behaviour of the system.
When you start a process it is always as a child of another, usually
some session. Graphically, you log in to a desktop session. When you
start gnome-terminal you are beginning a separate shell session and any
programs started
I have Ubuntu 10.04 (should be up-to-date) and this is what happens with
gnome-terminal:
1. gedit
2. Close terminal with the close button on the title bar (or close the
corresponding tab).
-> A dialog opens saying "Close this terminal? There is still a process running
in this terminal. Closing t
lxpanel is throwing a BadWindow on these steps. Maybe it has something
to do with this.
** Attachment added: ".xsession-errors"
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/819842/+attachment/2595429/+files/.xsession-errors
** Changed in: gnome-terminal (Ubuntu)
Status
is there anything on ~/.xsession-errors ? I cannto reproduce this issue,
could you please attach that file to the reporT? thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/819842
Title:
Commands
I have tested this now with lxterminal and gedit but the problem still
exists. I have tried xterm too but the problem appears here too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/819842
Title:
Co
Hi Sworddragon,
Thanks for testing this!
Could you confirm whether this happens in other programs? I tested
mainly using gedit and gitg and I am able to leave them running even
after the terminal closes. This is using lxterminal and gnome-terminal.
git gui invokes, I think, gitk, which is writte
My system was already fully upgraded in the previous post to Ubuntu
12.04 dev. The lxterminal version is 0.1.11-0ubuntu1. I'm starting
LXTerminal over the startmenu from lxpanel, typing "git gui &" in it and
pressing enter. After git gui ist started I'm closing lxterminal by
clicking on the x in th
I'm running 11.10 with all updates and I'm unable to reproduce this
behavior anymore. I'll mark the bug as Fix Released (fixed by an unknown
upgrade).
If you're still experiencing this problem, please make sure to fully
upgrade your system and try again; if it still happens, please provide
detaile
The same problem appears in LXTerminal too. Maybe a shared component is
affected by this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/819842
Title:
Commands in the background are terminate
** Package changed: ubuntu => gnome-terminal (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/819842
Title:
Commands in the background are terminated after closing the terminal
To manage noti
Hi, I can confirm the original report.
Steps to reproduce (on an 11.10 system, daily image from 20110802.1)
1- Start the terminal (gnome-terminal)
2- Launch for example gedit &
3- Close the terminal
Expected behavior:
- The gedit instance that was launched through the terminal remains
Actual be
This never happened some months ago. I could start git gui in the
background and close the terminal without a problem (I do this because
there is no start menu entry for git gui). But after some time git gui
was closed too if I closed the terminal. Now after some months I
reinstalled Ubuntu 11.04 a
Using the & symbol backgrounds the task in that shell session. Even
though they are backgrounded, they are still connected to the shell and
will die when you kill the shell.
Doesn't this happen in other versions of ubuntu?
--
You received this bug notification because you are a member of Ubuntu
21 matches
Mail list logo