Attachment 949858 Details for Bug 1156030 – File: journal.txt

File: journal.txt

journal.txt (text/plain), 2.35 KB, created by Jozef Mlich on 2014-10-23 12:42:33 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Jozef Mlich

Created: 2014-10-23 12:42:33 UTC

Size: 2.35 KB

patch

obsolete

>Oct 23 14:33:41 localhost.localdomain login[18419]: pam_unix(login:session): session opened for user jmlich by LOGIN(uid=0)
>Oct 23 14:33:41 localhost.localdomain login[18618]: gkr-pam: couldn't run gnome-keyring-daemon: Permission denied
>Oct 23 14:33:41 localhost.localdomain login[18419]: gkr-pam: gnome-keyring-daemon didn't start properly
>Oct 23 14:33:41 localhost.localdomain dbus[762]: [system] Activating service name='org.fedoraproject.Setroubleshootd' (using servicehelper)
>Oct 23 14:33:41 localhost.localdomain login[18419]: LOGIN ON tty2 BY jmlich
>Oct 23 14:33:42 localhost.localdomain dbus[762]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd'
>Oct 23 14:33:42 localhost.localdomain setroubleshoot[18621]: SELinux is preventing login from execute access on the file /usr/bin/gnome-keyring-daemon. For complete SELinux messages. run sealert -l 0fba0e55-f438-4c70-95bc-f27af0249785
>Oct 23 14:33:42 localhost.localdomain python[18621]: SELinux is preventing login from execute access on the file /usr/bin/gnome-keyring-daemon.
>                                                     
>                                                     *****  Plugin catchall (100. confidence) suggests   **************************
>                                                     
>                                                     If you believe that login should be allowed execute access on the gnome-keyring-daemon file by default.
>                                                     Then you should report this as a bug.
>                                                     You can generate a local policy module to allow this access.
>                                                     Do
>                                                     allow this access for now by executing:
>                                                     # grep login /var/log/audit/audit.log | audit2allow -M mypol
>                                                     # semodule -i mypol.pp
>                                                     
>Oct 23 14:34:09 localhost.localdomain fprintd[18612]: ** Message: No devices in use, exit
>Oct 23 14:34:29 localhost.localdomain dbus[762]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
>Oct 23 14:34:29 localhost.localdomain dbus[762]: [system] Successfully activated service 'net.reactivated.Fprint'

Actions: View

Attachments on bug 1156030: 949851 | 949852 | 949853 | 949854 | 949855 | 949856 | 949857 | 949858 | 949859 | 949860 | 949861 | 949862 | 949863