gnome-terminal crashes with forked command not found if path is too long

[Richard Eames]

The affected package could also be the command-not-found package.

There seems to be a bug with the way either gnome-terminal or command-not-found handles unknown commands that are forked. It also seems to be dependent on the length of the full path.

My testcase (which may have to be fiddled with):
~$ mkdir 123456789012345678
~$ cd 123456789012345678
~/123456789012345678$ pwd
/home/redbrick/123456789012345678
~/123456789012345678$ a&
* gnome-terminal crashes *

I've reproduced this on three different machines.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-terminal 3.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Wed Mar 14 15:55:24 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

[Vadim Rutkovsky (roignac)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Richard Eames (naddiseo)]

Unfortunately, there isn't a crash report. I've tried to get a backtrace in gdb, but gnome-terminal forks or something so I don't know how to follow it.

I've also managed to reproduce this on precise.

[Vadim Rutkovsky (roignac)]

Reproduced in Precise also. Doesn't crash after I remove command-not-found package

[Paul White (paulw2u)]

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.

Do you still see a problem related to the one that you reported in a currently supported version of Ubuntu? Please let us know if you do and in which version of Ubuntu otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

[Richard Eames (naddiseo)]

No worries. I can't reproduce it any more, I assume it was fixed at some point.

[Paul White (paulw2u)]

Thanks Richard. Marking as fixed as reproducible by another user.