slim (simple login manager)

[Daniel J Walsh]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/01/2011 02:58 PM, cromworshipper-fedorastuff at yahoo.com wrote:
> On Thu, Sep 01, 2011 at 09:49:59AM -0400, Daniel J Walsh wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> On 08/31/2011 06:17 PM, John Schmitt wrote:
>>> On Wed, Aug 31, 2011 at 09:13:42AM -0400, Daniel J Walsh
>>> wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>> 
>>>> On 08/30/2011 07:01 PM, John Schmitt wrote:
>>>>> On Mon, Aug 29, 2011 at 10:52:54AM -0400, Daniel J Walsh 
>>>>> wrote:
>>>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>>>> 
>>>>>> On 08/28/2011 09:23 AM, Roberto Ragusa wrote:
>>>>>>> On 08/28/2011 03:21 AM, 
>>>>>>> cromworshipper-fedorastuff at yahoo.com wrote:
>>>>>>>> slim started up fine when this machine was running
>>>>>>>> Fedora 14. I installed it from for Fedora 15:
>>>>>>>> 
>>>>>>>> slim-1.3.2-8.fc15.x86_64
>>>>>>>> 
>>>>>>>> It doesn't start any more.  I get this in 
>>>>>>>> /var/log/slim.log:
>>>>>>>> 
>>>>>>>> slim: unexpected signal 15 sh: /usr/bin/xauth: 
>>>>>>>> Permission denied
>>>>>>>> 
>>>>>>> 
>>>>>>> Check the permission of /usr/bin/xauth. They will be 
>>>>>>> probably ok, so next move will be blaming selinux.
>>>>>>> 
>>>>>> Looks to me like selinux.  I would check your labeling
>>>>>> on xaut ahd maybe on slim.
>>>>> 
>>>>> 
>>>>> $ ps -eZ | grep -i slim
>>>>> 
>>>>> yields nothing because slim is not running.
>>>>> 
>>>>> John
>>>> Well can you logout of the X session and log in via a
>>>> termanal or sshd to see what it is running as.
>>> 
>>> I guess I don't understand.  The start up process has stopped, 
>>> systemd says something about 'waiting for plymouth graphical
>>> boot screen' to end and then stops.  X is not running at this
>>> point.  I can press ALT+CTRL+F2 to open another terminal
>>> session and log in to look at /var/log/messages,
>>> /var/log/slim.log, and /var/log/Xorg.0.log.
>>> 
>>> I don't know if this helps, but I tried it again a few minutes
>>> ago and saw this in /var/log/messages:
>>> 
>>> Aug 31 13:17:24 badboy systemd[1]: prefdm.service holdoff time 
>>> over, scheduling restart. Aug 31 13:17:25 badboy ntpd[1047]: 
>>> 0.0.0.0 c61c 0c clock_step +0.823605 s Aug 31 13:17:25 badboy 
>>> ntpd[1047]: 0.0.0.0 c614 04 freq_mode Aug 31 13:17:25 badboy 
>>> systemd[1]: prefdm.service holdoff time over, scheduling
>>> restart. Aug 31 13:17:26 badboy systemd[1]: prefdm.service
>>> holdoff time over, scheduling restart. Aug 31 13:17:26 badboy
>>> systemd[1]: prefdm.service holdoff time over, scheduling
>>> restart. Aug 31 13:17:26 badboy systemd[1]: prefdm.service
>>> holdoff time over, scheduling restart. Aug 31 13:17:26 badboy
>>> systemd[1]: prefdm.service holdoff time over, scheduling
>>> restart. Aug 31 13:17:26 badboy systemd[1]: prefdm.service
>>> start request repeated too quickly, refusing to start.
>>> 
>>> 
>>> 
>>> Thanks for helping me with this, Daniel.
>>> 
>>> 
>>> John
>> 
>> 
>> Ok get me the output of
>> 
>> ausearch -m avc -ts recent or if audit is not runnind
>> 
>> dmesg | grep avc
> 
> $ sudo ausearch -m avc -ts recent <no matches>
> 
> $ dmesg | grep -i avc [   79.382138] dbus[1072]: avc:  netlink
> poll: error 4
> 
> Going back a few days I can see that ausearch reports a lot of AVC
> messages regarding wine-preloader and skype, but I can't imagine
> they're relevant here.
> 
> John


I guess the question then is are we sure this is an SELinux issue?


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5f12sACgkQrlYvE4MpobN89ACgp1MNSOi8aMHR/ggaUEfr4Mhp
3JkAoLHYS9MBtY5M21zw2TAcVzie8Rkp
=JLLN
-----END PGP SIGNATURE-----