Still trying to fix: "error failed to fork pty"
 

I have been trying to find a solution to problems created by Mediabuntu during installation.
There have been a couple of possible fixes, but they have not worked so far.

When I try to use or use Synaptic Package Manager to fix the broken dependencies it says there are broken packages. However, when I mark for re-installation and hit Apply, I get the "Error Failed to Fork PTY" message. If I try to use the terminal I get "error creating the child process"

So far, I have attempted to enter the following commands using the console:

A) sudo cp /etc/init.d/mountdevsubfs.sh. dpkg-dist /etc/init.d/mountdevsubfs.sh
This is the response: "Failed to execute child process "

B) sudo echo "devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0" >> /etc/fstab sudo mount /dev/pts
I get -bash: /etc/fstab permission denied

I changed my system permissions, but I still get the same error

I also tried "sudo dpkg --configure -A" followed by
"Sudo apt-get upddate"
The updates were shown, but would not install. Either the "Error failed to fork pty" error or message " -bash: /etc/fstab permission denied"

I tried another entry: "sudo apt-get update" Then
"sudo apt-get install" where I again get "permission denied"

C) I appreciate the help from everyone, but what I have done so far does not seem to work. As a newbie, I may not be entering the commands properly, or something.
I have searched the forumns, wiki and google, but there is noclose similarity to the solutions they show. I'm stymied.
If anyone could take a few minutes to lead me through this I would be a very hacppy camper. If I can't get this fixed, I can't get updates or programs and there is still a lot of things I need to do.

So, I really hope someone will offer the solution I need before I start chewing DDR sticks.
Thanks in advance






Trying to use the terminal I get "error creating the child process"

sudo echo "devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0" >> /etc/fstab
sudo mount /dev/pts

Continued from another thread

do:

sudo apt-get clean

what happens when you:

sudo apt-get check

(copy and paste outputs and the command you entered, as they appear in the terminal)

sudo apt-get -f packagename

... on the missing or broken dependencies.



To understand what the others have been on about, have a look at the following bug report.

Some users found tha adding the line:

devpts /dev/pts devpts (rw,noexec,nosuid,gid=5,mode=620 0 0

to /etc/fstab - then the problem went away.
That is what the echo command was supposed to do ... try

sudo gedit /etc/fstab

and paste it in.


What makes you think Medibuntu has caused this issue? (i.e. what did you do which precipitated the problem?)

Hi,

Welcome. In Linux there are different privilege levels.

su
password:

will get you into the root account. I think Ubuntu also automatically adds the user to the sudoers file. That means

sudo <command>
password:

will run the command with root privileges. Once you understand the different privilege levels, you can use the proper privilege level running commands. Most of the commands you are trying to run require root privileges to work properly.

So, try

sudo synaptic
password:

And see if that works for you.

Hi,

Welcome. In Linux there are different privilege levels.

su
password:

will get you into the root account. I think Ubuntu also automatically adds the user to the sudoers file. That means

sudo <command>
password:

will run the command with root privileges. Once you understand the different privilege levels, you can use the proper privilege level running commands. Most of the commands you are trying to run require root privileges to work properly.

So, try

sudo synaptic
password:

And see if that works for you.

su does not work in Ubuntu - but, as noted, the first user is added to the sudoers file so sudo will work. You will have noticed that OP has been putting "sudo" in front of his commands, so I guess you must be thinking of something else?

In ubuntu, synaptic is accessed as a menu item which runs

gksudo synaptic

which is usually better for apps which have to run a gui in gnome. Use it in launchers.
(man gksudo)

While i do appreciate all suggestions, I have tried all of them, but noting (so far) seems to work. I do get into the root - I was in root - when I got the permission denied message. Yesterday I did ALT-F2 - entered "Run application"
and entered:

sudo gedit /etc/fstab
---------
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0
--------
sudo mount /dev/pts

Saved it and exited.

I still have the exact same problems! I Do Not have access to a "Terminal" and the command line interface will not allow me into an "fstab" file.
The "run application" interface does not appear to solve the problem - regardless of the code entered.

Therefore, I continue to get "Error Failed to fork PTY"
Attempt to open "terminal" gives "error creating the child process for this terminal"

To explain again; I do not have access to the "terminal" and cannot use that to enter whatever code recommended.

If there is any way other than the "command line" (CTL-ALT-F1) or (Applications + Accessories +Terminal)
that will allow me to enter the proper code, save it and have it function, I am eager to receive it and fix these problems.

Additionally, I now have an error message when logging in that tells me that the "$Home" disectory is not owned by login, or whatever. It does not interfere with most of the things I normally do, but I'd like to fix it as well.

Any suggestions?

Thanks

Unfortunately, that kind of message means nothing to us. The questions you are getting need you to tell us the manner of failure so we can diagnose the issue.
Applications > Accessories > Terminal
(when something fails you need to be explicit about what you did.)

Now that is useful - add yourself to the tty group.

System > Administration > Users and Groups
unlock and edit yourself, look for tty in the group listing.

You are supposed to be added to this group automatically when you installed Ubuntu. Have you ever been able to access a terminal this way?
You are experiencing progressive data failure - you need to boot from the install CD, enter live mode, and run fsck on your root HDD. Before you do that, use the live session to backup your important data right away.

Reply to Simon on "error failed to fork pty"
 

Simon
Thanks for your reply. First off, I opened sys/admin/users and groups, but there is no tty group listed. I am listed in the root group and the admin group, as well as all the other groups. My user name or root do not have check marks next to them. Is that important? When I checked my name in the admin group, an error message said it would make the system unstable. Should I assume that my user name and root listed are all that is necessary - without a check mark?
Do I need to add the tty group? How do I do that?
Will it be added when I boot off the CD?
Also: there is a user group listed called "Polkituser" Do you know the what and why of this?

Also,,, when I run a live session off the Ubuntu 9.04 disk to fix the $Home problem, can I then upgrade to 9.10 and it that release stable?
For the past 3 days, when I login, I have another error message saying "$Home/.drmc file is being ignored. File should be owned by user. User $Home directory should be owned by user and not writable by others"
When I click on it, I am prompted for my password, which then allows me into the system. Previously, there was no PW verification needed at this stage. What do I need to know?

Again, thank you for your help. I am hoping to get everything back to proper, so I can keep studying the manual and maybe become able to complete these tasks myself.
Gnusboy

You are experiencing progressive data corruption which could indicate a failing HDD.

Back up your data now.

Since you indicate that you want to install 9.10, which is stable, then you are best advised to perform a fresh install. Bearing in mind that if you HDD or HDD controller is failing, then there is not much you can do. This should work, though, if you have some corrupt sectors.

If you want to save this install, you should run fsck on your, unmounted, root partition from a live CD. Select the option to repair.