Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 452361 - gnome terminal "There was an error creating the child process for this terminal"
Summary: gnome terminal "There was an error creating the child process for this terminal"
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-terminal
Version: rawhide
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-21 12:29 UTC by Richard W.M. Jones
Modified: 2008-06-21 20:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-06-21 20:40:48 UTC


Attachments (Terms of Use)
strace -f -s 1500 from gnome-terminal (deleted)
2008-06-21 12:30 UTC, Richard W.M. Jones
no flags Details

Description Richard W.M. Jones 2008-06-21 12:29:07 UTC
Since recently upgrading something in Rawhide, gnome-terminal
doesn't start up.  I see the error message "There was an error
creating the child process for this terminal".

Version: 2.23.4.2-1.fc10

I don't know if this is related, but xterm doesn't start up
either.  It says:
xterm: Error 32, errno 2: No such file or directory
Reason: get_pty: Not enough ptys

I have set SELinux to Permissive, so it's probably not an SELinux
problem.

Comment 1 Richard W.M. Jones 2008-06-21 12:30:30 UTC
Created attachment 309966 [details]
strace -f -s 1500 from gnome-terminal

This is an strace of gnome-terminal starting up, failing, then
closing down.  It appears to be a pty problem as far as I can see.

Comment 2 Yanko Kaneti 2008-06-21 13:46:45 UTC
initscripts-8.77-1  busted
fixed in initscripts-8.78-1 in koji


Comment 3 Richard W.M. Jones 2008-06-21 20:40:48 UTC
Yes, the new initscripts fixes this.


Note You need to log in before you can comment on or make changes to this bug.