Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 585108 - Plasma 5: Login fails
Summary: Plasma 5: Login fails
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-05 13:24 UTC by Bartosz Krzeszewski
Modified: 2017-02-16 23:49 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
sddm.log (sddm.log,61.05 KB, text/plain)
2016-06-05 15:30 UTC, Bartosz Krzeszewski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bartosz Krzeszewski 2016-06-05 13:24:19 UTC
Using this howto https://wiki.gentoo.org/wiki/KDE/Plasma_5_upgrade I upgraded my system from kde4 to plasma. After reboot I couldn't login into my desktop. Sddm shows me available accounts but when I select one and enter password sddm starts to do something but it stops.
It have to be something related to consolekit because ck-list-sessions shows me that my vt7 session is active=false and realname =(null). But when I'm logged in into terminal consolekit shows that this session is active and realname = root. So consolekit is working with terminal but it dosen't want to work with sddm.
Comment 1 Andreas Sturmlechner gentoo-dev 2016-06-05 13:30:19 UTC
Make sure that consolekit is started in default runlevel, make sure that /etc/sddm.conf exists and pay attention to the sddm postinst message (check /etc/pam.d/system-login for sanity).
Comment 2 Johannes Huber (RETIRED) gentoo-dev 2016-06-05 13:42:25 UTC
(In reply to Andreas Sturmlechner from comment #1)
> Make sure that consolekit is started in default runlevel, make sure that
> /etc/sddm.conf exists and pay attention to the sddm postinst message (check
> /etc/pam.d/system-login for sanity).

If this doesn't a little bit more debug info could help.
Comment 3 Bartosz Krzeszewski 2016-06-05 14:00:00 UTC
(In reply to Andreas Sturmlechner from comment #1)
> Make sure that consolekit is started in default runlevel, make sure that
> /etc/sddm.conf exists and pay attention to the sddm postinst message (check
> /etc/pam.d/system-login for sanity).

It doesn't matter if sddm is in default runlevel because xdm requires it to start. I tryed with consolkit started in default runlevel and not.

/etc/sddm.conf does not exist.

sddm postinst message: emerge --oneshot sddm                                                                                                                                                                                                                               
Calculating dependencies... done!                                                                                                                                                                                                                                                 
>>> Verifying ebuild manifests                                                                                                                                                                                                                                                    
>>> Running pre-merge checks for x11-misc/sddm-0.13.0-r3                                                                                                                                                                                                                          
>>> Emerging (1 of 1) x11-misc/sddm-0.13.0-r3::gentoo
>>> Installing (1 of 1) x11-misc/sddm-0.13.0-r3::gentoo
>>> Jobs: 1 of 1 complete                           Load avg: 3.58, 2.75, 2.33
>>> Auto-cleaning packages...                                                                                                                                                                                                                                                     
                                                                                                                                                                                                                                                                                  
>>> No outdated packages were found on your system.                                                                                                                                                                                                                               
                                                                                                                                                                                                                                                                                  
 * GNU info directory index is up-to-date.    

cat /etc/pam.d/system-login
auth            required        pam_tally2.so onerr=succeed
auth            required        pam_shells.so 
auth            required        pam_nologin.so 
auth            include         system-auth
account         required        pam_access.so 
account         required        pam_nologin.so 
account         include         system-auth
account         required        pam_tally2.so onerr=succeed 
password        include         system-auth
session         optional        pam_loginuid.so
session         required        pam_env.so 
session         optional        pam_lastlog.so silent 
session         include         system-auth
session         optional        pam_ck_connector.so nox11
session         optional        pam_motd.so motd=/etc/motd
session         optional        pam_mail.so
Comment 4 Johannes Huber (RETIRED) gentoo-dev 2016-06-05 15:01:12 UTC
Is the sddm user in video group? Xsession Error log?
Comment 5 Bartosz Krzeszewski 2016-06-05 15:30:10 UTC
Created attachment 436562 [details]
sddm.log
Comment 6 Andreas Sturmlechner gentoo-dev 2016-06-05 18:06:36 UTC
(In reply to Bartosz Krzeszewski from comment #3)
> /etc/sddm.conf does not exist.
Then you need to create one. No idea why sddm doesn't do it automatically.

# sddm --example-config > /etc/sddm.conf
Comment 7 Bartosz Krzeszewski 2016-06-05 21:55:27 UTC
(In reply to Andreas Sturmlechner from comment #6)
> (In reply to Bartosz Krzeszewski from comment #3)
> > /etc/sddm.conf does not exist.
> Then you need to create one. No idea why sddm doesn't do it automatically.
> 
> # sddm --example-config > /etc/sddm.conf

I made it but nothing has changed. I can see that plasma and my apps (eg ktorrent - autostart) are started but I don't have access to the desktop. I see only sddm splash screen. When I hit alt+ctrl+del there is this kde logout message (a top of sddm splash screen) but when I click logout this message disappers but nothing else happens. It is very strange. It seems that my plasma session is starting but something prevents me to interact with it.

p.s.
I wonder why such unstable and untested software like plasma has stable status in portage?
Comment 8 Andreas Sturmlechner gentoo-dev 2016-06-05 23:30:30 UTC
Delete any *.lock files inside ~/.config and ~/.cache
Comment 9 Bartosz Krzeszewski 2016-06-06 17:52:47 UTC
(In reply to Andreas Sturmlechner from comment #8)
> Delete any *.lock files inside ~/.config and ~/.cache

It happens on account with empty home directory so it is not it.

 I can use my desktop when I do this tick: when sddm splash screen stops I have to hit alt+ctr+del then esc and then alt+ctrl+del... (repeat 2-3 times) and my desktop appears but everything is locked, I cen see mouse cursor and move it but nothing is clickable. Then I have to wait for monitor turn off (power managment I think) and then when I move mouse screen is turned on and everything is working.
Comment 10 Bartosz Krzeszewski 2016-06-09 19:50:55 UTC
It looks like it is plasma bug. To login without problems I have to:
1. enter password
2. wait for splash screen (plasma splash) to stop
3. hit ctrl+alt+esc and kill splash, black screen appears and I can move mouse but no clicking
4. hit ctrl+esc (starts task manager) 2 or 3 times, sometimes more and then normal desktop appears
5. from start menu go to kde control center and select monitor settings
6. change my tv settings (I have tv and monitor)
7. now when I login again everything works without problems, no splash freezing
Comment 11 Andreas Sturmlechner gentoo-dev 2017-02-12 02:43:49 UTC
Any update on the matter?
Comment 12 Bartosz Krzeszewski 2017-02-16 23:23:08 UTC
(In reply to Andreas Sturmlechner from comment #11)
> Any update on the matter?

I think later KDE version fixed this issue.
Comment 13 Andreas Sturmlechner gentoo-dev 2017-02-16 23:49:02 UTC
Thanks for checking back.