Friday, 24. April 2009
I upgraded from Ubuntu 8.10 (Intrepid Ibix) to Ubuntu 9.04 (Jaunty Jackalope). It went fairly well but after the upgrade I found three major problems.
When I tried to launch GNOME Terminal from the menu I got this message:
There was an error creating the child process for this terminal
Not good. The first thing I tried was to start Update Manager and apply any patches. Update Manager showed me a list of patches but when I tried to install the updates it failed with the message:
Error failed to fork pty
At this point I wasn't getting warm, fuzzy feelings. Googling for the error messages turned up several Ubuntu bug reports for both problems. Many commenters reported that adding
devpts to the
fstab resolved the problem for them. So I tried their suggestion and it solved the problem for me as well. To apply this fix you need to add the following line to
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0
ALT+F2 to bring up the Run Application dialog. Then type in either”
gksudo gedit /etc/fstab
gksudo gedit /etc/fstab
After adding the entry for
devpts you need to mount it. You can either reboot or you press
CTRL+ALT+F1 to temporarily switch to console mode. Once in console mode, login as root and run:
After exiting console mode you should now be able to successfully launch GNOME Terminal from the menu. It worked for me anyway.
NOTE: After rebooting, GNOME Terminal would not work again. After running
mount -a from console mode it started working. So the problem is only partially solved if I have to manually mount the device after each boot.
After the upgrade my RAID volume would not mount. When I tried to mount it I got this error message:
mount: special device /dev/md0 does not exist
sudo mdadm --detail --scan and it showed the RAID array, but it didn't match the entries in either
/etc/fstab. It turned out that the RAID device had changed from
/dev/md/d0 in the upgrade. Fixing the problem required two steps:
- Replace the ARRAY entry in
/etc/mdadm/mdadm.confwith the output from
sudo mdadm --detail --scan.
NOTE: If the output contains the phrase
metadata=00.90, then delete that phrase.
mdadmdoesn't like metadata format 00.90 and gave me an error message:
mdadm: metadata format 00.90 unknown, ignored.
- Change the entry in
/etc/fstabto the new device, i.e. from
NOTE: The RAID volume does not auto-mount after rebooting. So this problem is also only partially solved.
When anything tries to play sound I just get a crackling sound from the speakers. I'm still working on this problem…
Update: Sound problem fixed.
Final Update: All problems fixed.