X server error
by T
XKB config activate error.
... Internal X server problem.
X szerver verzió adatok:
The X.Org Foundation
60700000
[root@MainLinux root]# gconftool-2 -R
/desktop/gnome/peripherals/keyboard/xkb
layouts = [hu,us]
model = pc105
overrideSettings = false
options = []
[root@MainLinux root]#
[root@MainLinux root]#
19 years, 10 months
building rpms with custom contexts
by Fritz Elfert
Hi,
I want to build several rpms for Fedora Core 2 which should install/use
some custom domains/file-contexts. Is there any doc or how-to for
this. Do i have to load the custom policy on the build-machine
at build-time or is there something similar like the %attr(...) macro for
setting file-contexts in the %files section of a spec? How are new
policies installed _without_ having policy-sources installed on the
target machine?
Thanks for any hint
-Fritz
19 years, 10 months
Re: graphical login problems with latest from development tree (solved)
by Tom London
OK. I think I figured this out.
/etc/rc.sysinit now recreates /tmp/.ICE-unix on each boot. It appears
that in doing so,
it does not assign it the expected context, so it is 'defaulting' to
system_u:object_r:initrc_tmp_t.
If I boot up single user, do a 'restorecon -v /tmp/.ICE-unix' to assign
it context
system_u:object_r:xdm_xserver_tmp_t, and then an 'exit', the resulting
graphical login works just fine.
Looks like /etc/rc.sysinit needs to do a 'restorecon':
[ -n "$SELINUX" ] && restorecon /tmp/.ICE-unix
after creating it....
Bugzilla'ed here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=127099
tom
[If you decide to try manually edit /etc/rc.d/rc.sysinit to add the
'restorecon', make sure you do a 'restorecon /etc/rc.d/rc.sysinit'
before rebooting. Otherwise, your system will not be happy.
(In case that happens, reboot with 'enforcing=0' and do the
'restorecon /etc/rc.d/rc.sysinit')].
19 years, 10 months
graphical login problems with latest from development tree
by Tom London
The latest packages from the development tree leave me with the following
situation: the system boots fine with no unusual messages/AVCs (in fact,
the latest policy files seem to have some 'dontaudit' rules that quiet
things down
a bit).
gdm starts, but after providing username/password, the effort fails with
a message
about session lasting 10 seconds or less. etc. and I'm back to the login
screen.
It works with 'enforcing=0', and interestingly, it also works with
'enforcing=1' if
I ctrl-alt-F2, login text mode, su to root, and then 'gdm-restart'.
The only difference I could detect is the contexts for /tmp/.ICE-unix
(initrc_tmp_t
vs. xdm_xserver_tmp_t) and .X11-unix (xdm_tmp_t vs. xdm_xserver_tmp_t).
Known issue?
tom
19 years, 10 months