bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Weird background crashing bug


From: Greg Wooledge
Subject: Re: Weird background crashing bug
Date: Mon, 29 Jun 2015 16:49:10 -0400
User-agent: Mutt/1.4.2.3i

Forwarding to the mailing list:

On Mon, Jun 29, 2015 at 02:28:32PM -0600, Braden Best wrote:
> Yes, the back tick is a quoting mechanism I picked up from stack exchange.
> In those sites, it highlights the text and renders it in a fixed width font.
> 
> cnf handle is : command not found
> 
> Also, I misinterpreted one of the bullet points as "which *version* of GCC
> was used" instead of simply "which compiler". As this version of bash is
> what comes default from the Ubuntu repo, I'd assume it's GCC.
> 
> Setting PS1 to something else prevents the crash for me. So since the root
> of the problem appears to be $PS1...
> 
> ~ $ echo $PS1
> 
> \[\e]0;address@hidden: 
> \w\a\]${debian_chroot:+($debian_chroot)address@hidden:\w\$
> 
> Also, just to show that the terminal really *is* crashing, and not somehow
> vanishing into the background itself, I made a gif. I don't usually embed
> or attach gifs via email, so here's a link: http://i.imgur.com/epCwOlI.gif
> 
> What do you make of this?
> 
> --Braden
> On Jun 29, 2015 5:59 AM, "Greg Wooledge" <address@hidden> wrote:
> 
> > On Mon, Jun 29, 2015 at 09:28:11AM +0300, Pierre Gaston wrote:
> > > On Mon, Jun 29, 2015 at 5:54 AM, Braden Best <address@hidden>
> > wrote:
> > > > I noticed it when I tried to branch an xterm off into multiple sessions
> > > > and mistyped its name:
> > > >
> > > > `xter m&`
> >
> > I'm assuming the backticks are NOT actually part of the command.  I.e.
> > you are really just typing:
> >
> > xter m&
> >
> > > > * both xterm and gnome-terminal crash
> >
> > > I don't seem to be able to reproduce with 4.3.30(1)-release, just in
> > case,
> > > can you try it after running:
> > >
> > > PS1='$ ' PROMPT_COMMAND=''; unset -f  command_not_found_handle
> >
> > It would also be useful to report what this command says:
> >
> > type command_not_found_handle
> >
> > There's a good chance the problem is being caused by some OS
> > vendor-installed command_not_found_handle that can't handle being
> > run as a background job.
> >



reply via email to

[Prev in Thread] Current Thread [Next in Thread]