Package: hal Version: 0.4.7-2 After a regular update of my sarge implementation (Feb 27, 2005) I had severe problems to get an X-session (using gdm) running.
.xsession-errors reported something like /usr/bin/gnome-session ...... line1: /dev/null permission denied line83: /dev/null permission denied running x-terminal-emulator instead Sorry, because .xsession-errors does not provide a history of the log, I can not provide the exact message. After logging in with gdm, a terminal window opened but there was an error message that a child process can not be forked. In my attempts to get X running, I removed gdm and tried startx. The error message now was "PRNG" not seeded. After a google search I learned that /dev/urandom is involved. In the next step I found out that both /dev/null /dev/urandom had no read / write permission for others. Consequently, startx worked now but only for root. Next, I changed manually the permissions for /dev/null and /dev/urandom to rw for others. Now, I could run startx as a plain user. However, when I tried to start a x-term I got an error message that "no pty devices are available". I looked into /dev and into ./dev and found out, that there were no pty devices. At this point, it was clear to me that there is a general problem with devices. Consequently, I deinastalled hal, installed gdm .... and everything worked fine again. I had hal running since months, I am updating sarge regulary and I had no problems before the yesterday update. Michael J Tauber -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
