sddm can't lanuch after update KaOS

First see if it is sddm only. On the error, go to tty2 > Ctrl-Alt-F2

Login there with username and password.

Next disable or stop sddm > sudo systemctl stop sddm

Then run "startx" to get to your desktop.

Once there get the full sysinfo from Octopi.

Same problem here.

Open octopi and go to last tab - get fullsysinfo from github (or similar,i'm not in Kaos now)

Here is mine:

You use --force to remove and install packages, you remove mesa and xorg-server and wonder why things are broken?

NEVER, NEVER use --force as you see now......

You're pacman log show at least 6 instances of the "--force" call (that is from the first and last ~ 500 lines, did not look further then that). Unless the log you posted is not from your system, you obviously are using force.

Same person with 2 machines and 2 nicknames? First of all when you use, no matter what, you must know how to use it and second you must take responsibility for your decisions. If you not clean caches all versions stays at /var/cache/pacman/pkg

alt+ctrl+f2 -> login, first disable kde-next and build repos, vi / nano, what you prefer, and place '#' (comment) looks like

#[kde-next]

#Include = /etc/pacman.d/mirrorlist

#[build]

#Include = /etc/pacman.d/mirrorlist

then downgrade system and install desired sddm

sudo pacman -Suu

sudo pacman -U /var/cache/pacman/pkg/sddm-XXX.pkg.tar.gz

XXX - depends on version, after sddm click 'tab' to see versions.

And what about me?

I have the same problem, sddm can't launch after update.

Is a fresh and clean installation with 3 days of life. (there are no --force commands in my sysinfo) (there are no sddm-XXX.pkg.tar.gz in my /var/cache/pacman/pkg/ folder)

And what about me?

I have the same problem, sddm can't launch after update.

Is a fresh and clean installation with 3 days of life. (there are no --force commands in my sysinfo) (there are no sddm-XXX.pkg.tar.gz in my /var/cache/pacman/pkg/ folder)

When did this start for you? Last update was the 13th (and updates done very strangely, you show there were updates 3 times in one day, while only once were your repos updated). You post here your issue started after 3 days of use, last update was the day of the install, so it seems your sddm fail was not caused by an update.

What settings did you change? What themes installed/added? Post any info of what you did after the last update on the 13th, then someone might be able to help you.

And looking at how you updated the 13th make sure your mirror is synced before updating. There are quite a few tools in KaOS to check that, easiest is to just open Octopi, it will tell you right away if your mirror is synced, don't update or install any until your mirror is synced.

System was installed 13th day at 03, big updated (620mb) at 03. Lot of tweaks along 13th day (including sddm login theme) Installed Kark-dark-theme, numix-icon-circle, firefox and other programs, 4 or 5 reboots and everything works well. Updated system 13th day at 22 (internet conection fail) and continue update at 22. Changed setting: "disable effects or compositing in full screen" (more or less) Go to sleep. 14th day sddm can't launch. 14th and 15th day searching google, 16th day posting here when i see other user with the same problem.

My system is a optimus hybrid graphics cards but don't use nvidia-card nvidia-drivers.

I have a journalctl -b -p error but is dnscrypt-proxy related and dnscrypt-proxy works well.

I always use your bashrc alias "upd" or "sudo pacman -Syyu". Is not correct "sudo pacman -Syyu"?

Nope, all correct, "upd" is the save one to use :)

Did you reboot after changing the sddm theme the 13th?

This most probably is an issue in either your ~/.config or a broken sddm theme.

Be very careful still with using themes other then Breeze and Midna.

Your journalctl does not show any issue with sddm though, so it looks more that plasma itself can't start because of a broken theme used.

Yes. 4 or 5 reboots after changing sddm theme and without problems.

Going to tty2 > Log with user and pass > sudo systemctl stop sddm > startx > and Plasma works well and plasmoids, kickoff...everything. The whole system works fine.

I don't install sddm themes, only defaults, but broken plasma theme is a possibility because all dark themes i tried (with "get new themes" option) looks broken with main bar in white colour.

Good to know startx works.

Then log out of plasma and go back to tty2 and run sudo systemctl start sddmon fail run sudo systemctl status sddmsee if it gives a clue where the issue is.

Solved issue.

sudo systemctl status sddm -l

● sddm.service - Simple Desktop Display Manager

Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled; vendor preset: enabled)

Active: active (running) since Wed 2015-11-18 13 WET; 9min ago

Docs: man(1)

man.conf(5)

Main PID: 513 (sddm)

CGroup: /system.slice/sddm.service

├─ 513 /usr/bin/sddm

└─1944 /usr/lib/xorg-server/Xorg -nolisten tcp -auth /var/run/sddm/{afded5af-d447-4f22-a91b-7a5884958899} -background none -noreset -displayfd 18 vt1

Nov 18 13 Server sddm-helper: Starting...

Nov 18 13 Server sddm-helper: Authenticating...

Nov 18 13 Server sddm-helper: Preparing to converse...

Nov 18 13 Server sddm-helper: Conversation with 1 messages

Nov 18 13 Server sddm-helper: returning.

Nov 18 13 Server sddm: Authenticated successfully

Nov 18 13 Server sddm-helper: pam_unix(sddm): session opened for user server by (uid=0)

Nov 18 13 Server sddm: Auth: sddm-helper exited successfully

Nov 18 13 Server sddm: Greeter stopped.

Nov 18 13 Server sddm: Session started

I have broken Brisa and Maldives sddm themes. Maybe my mix of plasma-icons-sddm-color schemes-windows decorations-themes breaks something but the White-brilliant-Midna-sddm-theme still working

I only need my sunglasses each time i start session.

Thank you for everything.