Created attachment 504041 [details] LXDE desktop session settings image Description of problem: What is the cause of this (pointed to by <=============== ) ? My desktop is LXDE, but it may not be specific to it. Preferences - Desktop Session Settings as captured in an attachment. $ cat .startx.log xauth: creating new authority file /home/jb/.serverauth.1770 X.Org X Server 1.10.2 Release Date: 2011-05-28 X Protocol Version 11, Revision 0 Build Operating System: x86-17 2.6.32-71.14.1.el6.x86_64 Current Operating System: Linux localhost.localdomain 2.6.38.7-30.fc15.i686 #1 SMP Fri May 27 06:02:17 UTC 2011 i686 Kernel command line: ro root=UUID=38f5a373-b061-4fa7-b41f-1e656e715012 rd_NO_LU KS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBO ARDTYPE=pc KEYTABLE=us rhgb quiet Build Date: 30 May 2011 12:42:31AM Build ID: xorg-x11-server 1.10.2-1.fc15 Current version of pixman: 0.20.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jun 10 09:05:09 2011 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" GNOME_KEYRING_CONTROL=/tmp/keyring-L6Wo32 SSH_AUTH_SOCK=/tmp/keyring-L6Wo32/ssh GNOME_KEYRING_PID=1828 Applet requires SELinux be enabled to run. E: main.c: Daemon startup failed. <============================ GNOME_KEYRING_CONTROL=/tmp/keyring-L6Wo32 SSH_AUTH_SOCK=/tmp/keyring-L6Wo32/ssh ... Version-Release number of selected component (if applicable): Installed Packages lxsession.i686 0.4.5-3.fc15 @koji-override-0/$releasever lxsession-edit.i686 0.1.1-5.fc15 @koji-override-0/$releasever How reproducible: start LXDE Steps to Reproduce: 1. $ startx > ~/.startx.log 2>&1 2. 3. Actual results: as above Expected results: no error Additional info:
So an applet returning an error causes lcde to fail to start. Basically you have setroubleshoot installed and seaplet notices that SELinux is not running so it exits out with an error, telling you that SELinux is not enabled so don't run this app. You can remove setroubleshoot if you are not going to enable SELinux.
(In reply to comment #1) > So an applet returning an error causes lcde to fail to start. Basically you > have setroubleshoot installed and seaplet notices that SELinux is not running > so it exits out with an error, telling you that SELinux is not enabled so don't > run this app. > > You can remove setroubleshoot if you are not going to enable SELinux. Right, SELinux is disabled, and setroubleshoot is installed. But I want it to stay that way (no related original packages removal). But, the LXDE is not failing to start. Btw, this error is "floating" in subsequent .startx.log files as you can see below: $ cat .startx.log ... (==) Using system config directory "/usr/share/X11/xorg.conf.d" GNOME_KEYRING_CONTROL=/tmp/keyring-oSHOt9 SSH_AUTH_SOCK=/tmp/keyring-oSHOt9/ssh GNOME_KEYRING_PID=7565 Applet requires SELinux be enabled to run. <--------------------- GNOME_KEYRING_CONTROL=/tmp/keyring-oSHOt9 SSH_AUTH_SOCK=/tmp/keyring-oSHOt9/ssh GNOME_KEYRING_CONTROL=/tmp/keyring-oSHOt9 SSH_AUTH_SOCK=/tmp/keyring-oSHOt9/ssh GPG_AGENT_INFO=/tmp/keyring-oSHOt9/gpg:0:1 GNOME_KEYRING_CONTROL=/tmp/keyring-oSHOt9 SSH_AUTH_SOCK=/tmp/keyring-oSHOt9/ssh GPG_AGENT_INFO=/tmp/keyring-oSHOt9/gpg:0:1 E: main.c: Daemon startup failed. <======================= ** (lxpolkit:7584): CRITICAL **: polkit_agent_listener_register: assertion `POLKIT_IS_SUBJECT (subject)' failed ... Now, this line is not clear. What applet ? You say "do not run it" ... If SELinux is *disabled*, there should not be any impact on running system, nil, not even an error or a diagnostic run-time messages that something is "bothered" by SELinux; sure, unless some catastrophic error condition. ... Applet requires SELinux be enabled to run. ... Next, this error message is unclear as to what is causing it (main.c belongs to some program and it should be clearly stated here); also which daemon failed ?; also what's that "E:" ? ... E: main.c: Daemon startup failed. ... Are the above two lines related ? Are they cause and effect ? Not clear. JB
E: main.c: Daemon startup failed. <============================ I am not sure this is my app outputting this? If you just run seapplet from the command line, what does it output?
(In reply to comment #3) > E: main.c: Daemon startup failed. <============================ > > I am not sure this is my app outputting this? > > If you just run seapplet from the command line, what does it output? $ seapplet Applet requires SELinux be enabled to run. JB
OK. I have done additional testing and the results are in. With regard to LXDE Preferences - Desktop Session Settings and SELinux Troubleshooter applet therein turned off, this message not present any more in .startx.log: Applet requires SELinux be enabled to run. <==================== So, this message is issued by, I assume, LXDE lxsession package that manages autostart applets. Regarding this message: E: main.c: Daemon startup failed. <======================= the testing showed that it is related to NetworkManager's nm-applet and also, I assume, the LXDE lxsession package manages autostart of this applet. I have to submit a new report to maintainer of LXDE lxsession package. Thanks for cooperation. This report can be closed. JB
(In reply to comment #5) > OK. I have done additional testing and the results are in. > > With regard to LXDE > Preferences - Desktop Session Settings > and SELinux Troubleshooter applet therein turned off, this message not present > any more in .startx.log: > Applet requires SELinux be enabled to run. <==================== > > So, this message is issued by, I assume, LXDE lxsession package that manages > autostart applets. > Oh man ! That conclusion would be true if LXDE lxsession, being a "driver" program for autostarting applets, were either: - testing for SELinux state before calling the SELinux related applet, or - calling the applet "blindly" and waiting for a return code, which would tell it that it can not be executed because SELinux is disabled But it does not do it this way - it just calls the applet and lets it fail with that error message after checking SELinux state. So, I would like to ask the maintainer of setroubleshoot package (owner of SELinux Troubleshooter applet) to append a prefix indicating clearly from which applet the message comes from (in case it is a common message and there are multiple SELinux related applets autostarted), e.g. SELinux Troubleshooter: Applet requires SELinux be enabled to run. > Regarding this message: > E: main.c: Daemon startup failed. <======================= > the testing showed that it is related to NetworkManager's nm-applet and also, > I assume, the LXDE lxsession package manages autostart of this applet. > > I have to submit a new report to maintainer of LXDE lxsession package. > ... The second problem has been taken care of as stated above. JB
Ok I lost this bug in the flood of bugzillas. I think I can close this as expected behaviour. Only app started at boot is seapplet, And I guess if the user does not want to run with SELinux turned on and does not want the message in his log, he should turn off autostarting of seapplet or remove it from his system.