Hi,
I tried to test current sddm status, so i used these instructions:
fedoraproject.org/wiki/Changes/SDDMinsteadOfKDM#How_To_Test
In section "How To Test" it says:
"Anybody able to run KDE Plasma Workspaces as his desktop can test."
So, is it safe to assume that one can test with a F20 host?
I tested with a F20 host, after enabling sddm i performed a reboot.
On the next boot, sddm appeared, but i am unable log in with any user.
It is like enter does nothing. I can login with those users on another
VT or via ssh, so the user/passwords are ok.
I tried setting SELinux to Permissive, but it did not help.
# systemctl status sddm.service -l
sddm.service - Simple Desktop Display Manager
Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled)
Active: active (running) since Thu 2014-03-13 12:49:28 ART; 7min ago
Main PID: 832 (sddm)
CGroup: /system.slice/sddm.service
├─832 /usr/bin/sddm
├─856 /usr/bin/X :0 -auth /var/run/sddm//A:0-RfaIBo
-nolisten tcp vt01
├─860 /usr/bin/sddm-greeter --socket sddm-:0-hwOZXu --theme
/usr/share/apps/sddm/themes//fedora
├─954 dbus-launch --autolaunch
e837339228d144d7978eae4231db458b --binary-syntax --close-stderr
└─958 /bin/dbus-daemon --fork --print-pid 5 --print-address
7 --session
Mar 13 12:49:28 stark.espada sddm[832]: DAEMON: Adding new display : 0
on vt 1 ...
Mar 13 12:49:28 stark.espada sddm[832]: DAEMON: Adding cookie to
"/var/run/sddm//A:0-RfaIBo"
Mar 13 12:49:28 stark.espada sddm[832]: /usr/bin/xauth: file
/var/run/sddm//A:0-RfaIBo does not exist
Mar 13 12:49:28 stark.espada sddm[832]: DAEMON: Display server starting...
Mar 13 12:49:28 stark.espada sddm[832]: DAEMON: Display server started.
Mar 13 12:49:28 stark.espada sddm[832]: DAEMON: Socket server starting...
Mar 13 12:49:28 stark.espada sddm[832]: DAEMON: Socket server started.
Mar 13 12:49:28 stark.espada sddm[832]: DAEMON: Greeter starting...
Mar 13 12:49:28 stark.espada sddm[832]: DAEMON: Greeter started.
Mar 13 12:49:29 stark.espada python[992]: SELinux is preventing
/usr/bin/sddm-greeter from write access on the sock_file .
***** Plugin catchall (100.
confidence) suggests **************************
If you believe that
sddm-greeter should be allowed write access on the sock_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 sddm-greeter
/var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
Mar 13 12:56:35 stark.espada dbus[958]: avc: received setenforce
notice (enforcing=0)
Mar 13 12:56:47 stark.espada dbus[958]: avc: received setenforce
notice (enforcing=1)
Is there a dedicated logfile? (like kdm.log)
Cheers.
_______________________________________________
kde mailing list
kde@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/kde
New to KDE4? - get help from http://userbase.kde.org
