I now have updated my fourth computer to Jaunty. And I had trouble with Konsole, again. The update was uneventful, and the problem occurred as described in comment 1.
However, the pty* devices did not exist this time. Trying to run konsole from a virtual terminal resulted in warnings about flow control, and could not connect to dbus. Again, I am sorry but the exact message was lost since I cannot cut and paste from my virtual terminal, and it has scrolled off the display after I performed the fix.
I found a strong hint for at least an interim fix here:
solved the problem. Apparently one needs to reorder the init scripts to make sure it (and my RAID -- another story) work on reboot. I noticed that /dev/pty* devices still do not exist, but that is not a worry to me. Seems like a much more appropriate and less risky fix than adding a user to a group.
I now have updated my fourth computer to Jaunty. And I had trouble with Konsole, again. The update was uneventful, and the problem occurred as described in comment 1.
However, the pty* devices did not exist this time. Trying to run konsole from a virtual terminal resulted in warnings about flow control, and could not connect to dbus. Again, I am sorry but the exact message was lost since I cannot cut and paste from my virtual terminal, and it has scrolled off the display after I performed the fix.
I found a strong hint for at least an interim fix here:
http:// www.splatdot. com/2009/ 04/24/ubuntu- 904-jaunty- jackalope- upgrade- notes
See the notes about adding /dev/pts into the fstab. Specifically, adding this line to /etc/fstab:
devpts /dev/pts devpts rw,noexec, nosuid, gid=5,mode= 620 0 0
and then running in a virtual terminal:
$ sudo mount -a
solved the problem. Apparently one needs to reorder the init scripts to make sure it (and my RAID -- another story) work on reboot. I noticed that /dev/pty* devices still do not exist, but that is not a worry to me. Seems like a much more appropriate and less risky fix than adding a user to a group.
Hope this helps.