Gene Heskett wrote: > On Friday 26 January 2007 14:45, Dmitriy Kropivnitskiy wrote: >> Gene Heskett wrote: >>> On Friday 26 January 2007 13:30, Dmitriy Kropivnitskiy wrote: >>>> Why are you trying to use fonts in /root/.fonts? Are you running your >>>> GUI sessions as root? >>> Usually, otherwise the stuff I want to do fails to open a path to the >>> x-session when I sudo or su -. Kino was one such app that I could run >>> as a user even when I did the su thing to gain access to the ieee1394 >>> hardware. >> I am sorry. I will not help you with problems running GUI as root. >> Basically you have problems because this is not intended usage of the >> system. I CAN help you run kino as a regular user though. BTW, does >> kino not run as a use weather or not you have selinux enabled? If so, >> why did you bring it up as an argument against selinux? > > Gee, simple I'd think, I read the logs when it failed, and it was selinux > that denied me access to the ieee1394 hardware when i ran it as the user > gene, uid 500. So, after you disabled selinux you were able to run kino as user right? Did you try to use audit2allow? >>> write(2, "/usr/share/fonts: failed to writ"..., 40/usr/share/fonts: >>> failed to write cache >>> ) = 40 >> I think the strace is incomplete. This write() call is trying to write >> to file handle 2 and I don't see any open() call that returns 2. Sorry, 2 is one of the standard I/O handles, probably stderr. So there shouldn't have been an open call for that I suppose.
