Re: slim (simple login manager)

[Derek Tracy <tracyde@xxxxxxxxx>]

I tried installing slim last night to see if I could get it to work.  I think there is a bug in slim, I tried editing the prefdm file along with Xclients, I can get slim to start from command line and all is well but no go from system startup.

Does anybody know the xauth command line slim uses when it is starting up?

---------------------------------
Derek Tracy
tracyde@xxxxxxxxx
---------------------------------

On Fri, Sep 2, 2011 at 3:16 AM, John Schmitt <cromworshipper-fedorastuff@xxxxxxxxx> wrote:

On Thu, Sep 01, 2011 at 03:05:15PM -0400, Daniel J Walsh wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 09/01/2011 02:58 PM, cromworshipper-fedorastuff@xxxxxxxxx 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@xxxxxxxxx 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?

I don't think it is, which is why I filed my bug against slim and not selinux.

https://bugzilla.redhat.com/show_bug.cgi?id=733944

If we've ruled out SELinux, what else could it be?

John

--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines