On 09/07/2015 02:43 PM, Matthias Klumpp wrote:
2015-09-07 14:30 GMT+02:00 <eric2.vale...@orange.com>:
Konsole output
ls -ld /etc/sddm/Xsession
-rwxr-xr-x 1 root root 1426 Sep 3 17:24 /etc/sddm/Xsession
Konsole output
ls -l /var/lib/sddm/
ls: cannot open directory /var/lib/sddm/: Permission denied
ls -ld /var/lib/sddm/
drwxr-x--- 5 sddm sddm 4096 Sep 3 09:45 /var/lib/sddm/
Again kdm works, no log /var/log/sddm.log empty, nothing in
xsession-errors...
Does
journalctl -b | grep sddm
show anything interesting?
Konsole output
journalctl -b | grep sddm
Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Control process
exited, code=exited status=1
Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Unit entered
failed state.
Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Failed with
result 'exit-code'.
Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Service hold-off
time over, scheduling restart.
Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Control process
exited, code=exited status=1
Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Unit entered
failed state.
Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Failed with
result 'exit-code'.
Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Service hold-off
time over, scheduling restart.
Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Control process
exited, code=exited status=1
Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Unit entered
failed state.
Sep 07 10:54:29 r-x-ceva6380 systemd[1]: sddm.service: Failed with
result 'exit-code'.
Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Service hold-off
time over, scheduling restart.
Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Control process
exited, code=exited status=1
Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Unit entered
failed state.
Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Failed with
result 'exit-code'.
Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Service hold-off
time over, scheduling restart.
Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Control process
exited, code=exited status=1
Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Unit entered
failed state.
Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Failed with
result 'exit-code'.
Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Service hold-off
time over, scheduling restart.
Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Start request
repeated too quickly.
Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Unit entered
failed state.
Sep 07 10:54:30 r-x-ceva6380 systemd[1]: sddm.service: Failed with
result 'start-limit'.
-- eric
_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
