Description of problem:
xorg-x11-xinit-1.0.2-16.fc6 installed yesterday; ~/.xsession-errors file stopped
growing (which would ordinarily be a good thing...); I found in my
~/.xsession-errors-:0 the following single line: "/etc/X11/xinit/Xsession: line
15: unask: command not found". This appears to be a typo for "umask" in line 15
" if ( unask 077 && cp /dev/null "$errfile" 2> /dev/null ); then"
I fixed it, and ran "sh /etc/X11/xinit/Xsession", but no change - maybe I have
to reboot/restart X???
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Upgrade/install xorg-x11-xinit-1.0.2-16.fc6;
2. Observe meltdown.
Script failed as noted.
Script succeeds/ ~/.xsession-errors grows to alarming proportions with the usual
uname -a: Linux presario.localdomain 126.96.36.199-32.fc6 #1 SMP Wed Aug 1 15:15:33
EDT 2007 i686 athlon i386 GNU/Linux
I just found this, must have missed it somehow on my first search: Bug #250882.
If you do change it to 'umask', does it work then?
I already changed "unask" to "umask" as noted above, '... and ran "sh
/etc/X11/xinit/Xsession", but no change - maybe I have to reboot/restart X...'.
So I ended the session, restarted X at the login screen, logged back in, and
now I'm once again receiving copious amounts of warnings, errors, and other
chatter in ~/.xsession-errors. So I guess the answer to your question is: Yes,
if I then also restart X.
Thanx and Regards,
Fedora Core 6 is no longer supported, could you please reproduce this with the
updated version of the currently supported distribution (Fedora 7, 8, or
Rawhide)? If this issue turns out to still be reproducible, please let us know
in this bug report. If after a month's time we have not heard back from you, we
will have to close this bug as CANTFIX.
Setting status to NEEDINFO, and awaiting information from the reporter.
[This is mass-filed message to all open Fedora Core 6 bugs related to Xorg or
Gecko. If you see any other reason, why this bug shouldn't be closed, please,
comment on it here.]
To the best of my knowledge, this is already fixed/doesn't exist in F7, since my
other two machines never showed this problem (they're both already upgraded to
F7). Besides, it was a simple typo and I long since fixed it myself.
Thanx and Regards,