Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
KDE5 upgrade and SDDM not loading
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Xploderman90
n00b
n00b


Joined: 27 Aug 2012
Posts: 57

PostPosted: Wed Apr 13, 2016 11:06 am    Post subject: KDE5 upgrade and SDDM not loading Reply with quote

Hi,
I've done the upgrade from kde4 to plasma 5 but sddm doesn't want to get up! I have a black screen and can't do nothing.

In /var/log/sddm.log i notice that it writes:

Code:

Greeter session started succesfully
Message received from greeter: Connect
[PAM] Ended.
Auth: sddm-helper exited with 6
Greeter stopped


I removed all kde-base and kde-apps packages, re-emerged plasma-meta, xorg-x11 and drivers but nothing works..what to do?

Thanks in advance
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6827
Location: Austria

PostPosted: Wed Apr 13, 2016 11:14 am    Post subject: Reply with quote

Re-emerging KDE packages rarely solves anything when SDDM is involved. Add the sddm user to the video group.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Xploderman90
n00b
n00b


Joined: 27 Aug 2012
Posts: 57

PostPosted: Wed Apr 13, 2016 11:26 am    Post subject: Reply with quote

genstorm wrote:
Re-emerging KDE packages rarely solves anything when SDDM is involved. Add the sddm user to the video group.


Already added but it doesn't work...
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6827
Location: Austria

PostPosted: Wed Apr 13, 2016 11:32 am    Post subject: Reply with quote

Do you have an /etc/sddm.conf? I've also heard xinerama in xorg.conf leads to such problems.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Xploderman90
n00b
n00b


Joined: 27 Aug 2012
Posts: 57

PostPosted: Wed Apr 13, 2016 11:37 am    Post subject: Reply with quote

genstorm wrote:
Do you have an /etc/sddm.conf? I've also heard xinerama in xorg.conf leads to such problems.

I have already done

Code:

sddm --example-config > /etc/sddm.conf


and i don't use xorg.conf (i use integrated intel video card), and it doesn't work..it's always showing black screen.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6827
Location: Austria

PostPosted: Wed Apr 13, 2016 11:43 am    Post subject: Reply with quote

(if you use openrc) consolekit and dbus are in default runlevel?

You don't by chance, try to log into the Plasma (Wayland) session? Because that most likely won't work.

One issue that has also come is SDDM being broken after Qt upgrade - however for that it must have been present on your system prior to Qt-5.5.1 upgrade already.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Xploderman90
n00b
n00b


Joined: 27 Aug 2012
Posts: 57

PostPosted: Wed Apr 13, 2016 11:56 am    Post subject: Reply with quote

genstorm wrote:
(if you use openrc) consolekit and dbus are in default runlevel?

You don't by chance, try to log into the Plasma (Wayland) session? Because that most likely won't work.

One issue that has also come is SDDM being broken after Qt upgrade - however for that it must have been present on your system prior to Qt-5.5.1 upgrade already.


Yes, dbus and consolekit are already in default runlevel. I have XDM and i have set
Code:

DISPLAYMANAGER="sddm"


in

Code:

/etc/conf.d/xdm


and xdm is in default runlevel.

I don't know what you mean by
Code:

try to log into the Plasma (Wayland) session?
.

I always tried xdm start or sddm
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6827
Location: Austria

PostPosted: Wed Apr 13, 2016 12:05 pm    Post subject: Reply with quote

You can choose the session you want to log in from SDDM using a drop-down. It should be the regular "Plasma" session, _not_ "Plasma (Wayland)".
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Xploderman90
n00b
n00b


Joined: 27 Aug 2012
Posts: 57

PostPosted: Wed Apr 13, 2016 12:23 pm    Post subject: Reply with quote

genstorm wrote:
You can choose the session you want to log in from SDDM using a drop-down. It should be the regular "Plasma" session, _not_ "Plasma (Wayland)".


I can't sede anything, sddm shows a full black screen (not even login)
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6827
Location: Austria

PostPosted: Wed Apr 13, 2016 12:29 pm    Post subject: Reply with quote

Oh sorry, I misinterpreted it then. Anyway, what about SDDM itself, did it get emerged by your Plasma upgrade or was it present before already? /me hints at possible Qt upgrade problem.

Anything in Xorg.log?
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Xploderman90
n00b
n00b


Joined: 27 Aug 2012
Posts: 57

PostPosted: Wed Apr 13, 2016 2:00 pm    Post subject: Reply with quote

genstorm wrote:
Oh sorry, I misinterpreted it then. Anyway, what about SDDM itself, did it get emerged by your Plasma upgrade or was it present before already? /me hints at possible Qt upgrade problem.

Anything in Xorg.log?


First, I tried with ssdm installed with plasma-meta, then i reinstalled myself but none of them worked.
In Xorg.log everything seems fine!
Back to top
View user's profile Send private message
Section_8
Guru
Guru


Joined: 22 May 2004
Posts: 566
Location: Arlington, TX, US

PostPosted: Wed Apr 13, 2016 3:39 pm    Post subject: Reply with quote

I had a similar problem after the upgrade. Just to get past it, I temporarily set DISPLAYMANAGER back to KDM (which was still installed) and was able to get a Plasma 5 session running. I then went to the Systemsettings startup options and updated the SDDM settings there. After that, SDDM worked fine.
Back to top
View user's profile Send private message
papas
n00b
n00b


Joined: 01 Dec 2014
Posts: 73
Location: Athens

PostPosted: Wed Apr 13, 2016 5:21 pm    Post subject: Reply with quote

same problem for me after upgrade my second pc from kde4 to plasma cant log on. ( kdm not working )
my sddm.log
Code:

[17:53:24.899] (II) DAEMON: Initializing...
[17:53:24.934] (II) DAEMON: Starting...
[17:53:24.934] (II) DAEMON: Adding new display on vt 7 ...
[17:53:24.972] (II) DAEMON: Display server starting...
[17:53:24.972] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{0ea9ebc4-ce16-455e-bed6-5defda9508a4} -background none -noreset -displayfd 17 vt7
[17:53:27.315] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[17:53:27.366] (II) DAEMON: Display server started.
[17:53:27.366] (II) DAEMON: Socket server starting...
[17:53:27.366] (II) DAEMON: Socket server started.
[17:53:27.378] (II) DAEMON: Greeter starting...
[17:53:27.378] (II) DAEMON: Adding cookie to "/var/run/sddm/{0ea9ebc4-ce16-455e-bed6-5defda9508a4}"
[17:53:27.437] (II) HELPER: [PAM] Starting...
[17:53:27.437] (II) HELPER: [PAM] Authenticating...
[17:53:27.437] (II) HELPER: [PAM] returning.
[17:53:27.534] (II) DAEMON: Greeter session started successfully
[17:53:28.779] (II) DAEMON: Message received from greeter: Connect
[17:53:31.259] (II) HELPER: [PAM] Ended.
[17:53:31.294] (WW) DAEMON: Auth: sddm-helper exited with 6
[17:53:31.294] (II) DAEMON: Greeter stopped.
[17:57:47.794] (WW) DAEMON: Signal received: SIGTERM
[17:57:47.794] (II) DAEMON: Socket server stopping...
[17:57:47.794] (II) DAEMON: Socket server stopped.
[17:57:47.794] (II) DAEMON: Display server stopping...
[17:57:48.111] (II) DAEMON: Display server stopped.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6827
Location: Austria

PostPosted: Wed Apr 13, 2016 5:27 pm    Post subject: Reply with quote

...did you follow the points made in this thread?
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
papas
n00b
n00b


Joined: 01 Dec 2014
Posts: 73
Location: Athens

PostPosted: Wed Apr 13, 2016 5:34 pm    Post subject: Reply with quote

yes everything.
I think there is something wrong in my installation I tried to use kdm and I got a strange message from my X session about "ksmserver" missing or something....
I am on line with my second gentoo installation now i have to update it, then I will try again.
Thank you anyway
Back to top
View user's profile Send private message
Xploderman90
n00b
n00b


Joined: 27 Aug 2012
Posts: 57

PostPosted: Thu Apr 14, 2016 9:22 am    Post subject: Reply with quote

papas wrote:
same problem for me after upgrade my second pc from kde4 to plasma cant log on. ( kdm not working )
my sddm.log
Code:

[17:53:24.899] (II) DAEMON: Initializing...
[17:53:24.934] (II) DAEMON: Starting...
[17:53:24.934] (II) DAEMON: Adding new display on vt 7 ...
[17:53:24.972] (II) DAEMON: Display server starting...
[17:53:24.972] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{0ea9ebc4-ce16-455e-bed6-5defda9508a4} -background none -noreset -displayfd 17 vt7
[17:53:27.315] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[17:53:27.366] (II) DAEMON: Display server started.
[17:53:27.366] (II) DAEMON: Socket server starting...
[17:53:27.366] (II) DAEMON: Socket server started.
[17:53:27.378] (II) DAEMON: Greeter starting...
[17:53:27.378] (II) DAEMON: Adding cookie to "/var/run/sddm/{0ea9ebc4-ce16-455e-bed6-5defda9508a4}"
[17:53:27.437] (II) HELPER: [PAM] Starting...
[17:53:27.437] (II) HELPER: [PAM] Authenticating...
[17:53:27.437] (II) HELPER: [PAM] returning.
[17:53:27.534] (II) DAEMON: Greeter session started successfully
[17:53:28.779] (II) DAEMON: Message received from greeter: Connect
[17:53:31.259] (II) HELPER: [PAM] Ended.
[17:53:31.294] (WW) DAEMON: Auth: sddm-helper exited with 6
[17:53:31.294] (II) DAEMON: Greeter stopped.
[17:57:47.794] (WW) DAEMON: Signal received: SIGTERM
[17:57:47.794] (II) DAEMON: Socket server stopping...
[17:57:47.794] (II) DAEMON: Socket server stopped.
[17:57:47.794] (II) DAEMON: Display server stopping...
[17:57:48.111] (II) DAEMON: Display server stopped.


I have the very same log in sddm.log
I reemerged @world, emerged some of kde-apps utilities (like admin, graphics..) still can't log in, I'm blocked.

I use intel graphics, i have sddm in video group, i followed the guide and the logs don't tell anything useful..what to do?
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6827
Location: Austria

PostPosted: Thu Apr 14, 2016 9:36 am    Post subject: Reply with quote

Try lightdm alternatively.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Xploderman90
n00b
n00b


Joined: 27 Aug 2012
Posts: 57

PostPosted: Thu Apr 14, 2016 10:09 am    Post subject: Reply with quote

genstorm wrote:
Try lightdm alternatively.


It's the only solution? I want to make sddm work...i'm sure it's a stupid error, something little but i can't figure out what it is
Back to top
View user's profile Send private message
papas
n00b
n00b


Joined: 01 Dec 2014
Posts: 73
Location: Athens

PostPosted: Thu Apr 14, 2016 10:32 am    Post subject: Reply with quote

I remember that I have not add my user in video group ( sddm is in video group) my last chance before move to lightdm
Back to top
View user's profile Send private message
Xploderman90
n00b
n00b


Joined: 27 Aug 2012
Posts: 57

PostPosted: Thu Apr 14, 2016 11:01 am    Post subject: Reply with quote

papas wrote:
I remember that I have not add my user in video group ( sddm is in video group) my last chance before move to lightdm


I have all users in video group, still doesn't work...
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6827
Location: Austria

PostPosted: Thu Apr 14, 2016 11:05 am    Post subject: Reply with quote

Your user isn't involved when SDDM doesn't even load. Even if you want to go with SDDM eventually, it can't hurt to see if it would actually work with lightdm, no?
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
davidm
Guru
Guru


Joined: 26 Apr 2009
Posts: 557
Location: US

PostPosted: Thu Apr 14, 2016 1:13 pm    Post subject: Reply with quote

This is going to sound stupid but are you sure you have KDM disabled from startup? In fact it probably makes sense to just remove it.

Sorry if it's obvious but sometimes people do make these silly mistakes. I did it once (or twice, three times ... lol) myself. :/

Also in the past some people delayed sddm startup by about 30 seconds to get around a bug (which was supposed to be fixed) :
https://bugs.gentoo.org/show_bug.cgi?id=553996

It might be worth giving it a shot to see what happens. There is a timer provided for systemd. If using openrc there is probably also a way to do it I'm sure.
Back to top
View user's profile Send private message
Xploderman90
n00b
n00b


Joined: 27 Aug 2012
Posts: 57

PostPosted: Thu Apr 14, 2016 3:30 pm    Post subject: Reply with quote

davidm wrote:
This is going to sound stupid but are you sure you have KDM disabled from startup? In fact it probably makes sense to just remove it.

Sorry if it's obvious but sometimes people do make these silly mistakes. I did it once (or twice, three times ... lol) myself. :/

Also in the past some people delayed sddm startup by about 30 seconds to get around a bug (which was supposed to be fixed) :
https://bugs.gentoo.org/show_bug.cgi?id=553996

It might be worth giving it a shot to see what happens. There is a timer provided for systemd. If using openrc there is probably also a way to do it I'm sure.


I don't have kdm anymore, in /etc/conf.d/xdm i have

Code:

DISPLAYMANAGER="sddm"


In the bug showed in
https://bugs.gentoo.org/show_bug.cgi?id=553996
the log clearly says that there is an error connecting to display
Code:

sddm-greeter[382]: QXcbConnection: Could not connect to display :0


in my case i don't have this error. I tried reemerging @world putting egl and gles2 use flags but nothing changed..
Back to top
View user's profile Send private message
Xploderman90
n00b
n00b


Joined: 27 Aug 2012
Posts: 57

PostPosted: Fri Apr 15, 2016 10:13 am    Post subject: Reply with quote

Installed qtcore 5, tried clearing some configurations, tried giving sddm:sddm permission to /usr/share/sddm but it doesn't work.
I don't know why but only one time it showed me the cross-shaped pointer, then only black screens.

If i give "startx" from command line, i can see XDM so i suppose X works...please help me, sddm is the standard with kde so it have to work!
Back to top
View user's profile Send private message
mrbassie
Guru
Guru


Joined: 31 May 2013
Posts: 526

PostPosted: Fri Apr 15, 2016 11:20 am    Post subject: Reply with quote

Similar for me:
Code:
 [12:16:28.444] (II) DAEMON: Starting...
[12:16:28.444] (II) DAEMON: Adding new display on vt 7 ...
[12:16:28.445] (II) DAEMON: Display server starting...
[12:16:28.445] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{d887fad1-6385-419f-a83e-38218e552a6c} -background none -noreset -displayfd 17 vt7
[12:16:29.309] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[12:16:29.310] (II) DAEMON: Display server started.
[12:16:29.310] (II) DAEMON: Reading from "/usr/share/xsessions/plasma.desktop"
[12:16:29.310] (II) DAEMON: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startkde"
[12:16:29.310] (II) DAEMON: Adding cookie to "/var/run/sddm/{d887fad1-6385-419f-a83e-38218e552a6c}"
[12:16:29.316] (II) HELPER: [PAM] Starting...
[12:16:29.316] (II) HELPER: [PAM] Authenticating...
[12:16:29.318] (II) HELPER: [PAM] returning.
[12:16:29.318] (II) DAEMON: Authenticated successfully
[12:16:29.319] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession" "/usr/bin/startkde"
[12:16:29.320] (II) HELPER: Adding cookie to "/home/rick/.Xauthority"
[12:16:29.322] (II) DAEMON: Session started
[12:16:44.942] (WW) DAEMON: Signal received: SIGTERM
[12:16:44.942] (II) DAEMON: Display server stopping...
[12:16:44.989] (II) DAEMON: Display server stopped.
[12:16:44.989] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[12:16:44.990] (WW) DAEMON: QProcess: Destroyed while process ("/usr/libexec/sddm-helper") is still running.


In my case a black screen (laptop, hybrid gfx=culprit?) means no backlight.

KDM works perfectly for me too. I also got the same behaviour as sddm when trying lightdm.

The first machine I upgraded with intel gfx it works fine.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum