From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020311
Description of problem:
xcdroast-0.98a9-7 does not work with pam_xauth. Specifically, when doing "su -"
from a user account an attempt by the resulting process to connect with the X
server gets "connection refused by server". This functionality _did_ work with
7.2 and xcdroast-0.98a9-2.
The problem seems to be that xcdroast does not look in the pam_xauth
file ~/.xauth* for its xauth keys. However, if the ~/.xauth* file created by
pam_xauth is copied into ~/.Xauthority, xcdroast will run OK.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.From a user account, "su -" (or, presumably, "su - anywhere")
2.Enter command "xcdroast"
Actual Results: Xlib: connection to ":0.0" refused by server
Expected Results: xcdroast should have connected to the X server and begun
Other X programs (such as xterm) work OK in the scenario given above.
This problem is specific to (at least) xcdroast.
If I copy pam_xauth's file ~/.xauth* into ~/.Xauthority, xcdroast
works OK. This leads me to the conclusion that xcdroast is not looking in all
the places that it should for the xauth keys.
This bug report came about as a result of a submission to skipjack-list mailing
list by Joey Grasty <email@example.com>.
If you change 'SESSION=false' to 'SESSION=true' in
/etc/security/console.apps/xcdroast, does that fix it for you?
Yes. Changing 'SESSION=false' to 'SESSION=true' in
/etc/security/console.apps/xcdroast does make it work.
Is the content of that file documented anywhere?
I'm curious what the parameters mean.
*** Bug 64500 has been marked as a duplicate of this bug. ***
Fixed in xcdroast-0.98a9-11.