| View previous topic :: View next topic |
| Author |
Message |
trubicoid
Tux's lil' helper
Joined: 04 Aug 2009
Posts: 79
|
 Posted: Sat Jul 02, 2016 8:00 pm Post subject: su in KDE5 takes 20 seconds [SOLVED] |
 |
|
I recently upgraded from KDE4 to KDE5 as per news "KDE Plasma 5 Upgrade". There is a strange thing after the upgrade, when doing su in terminal in KDE5 it takes 20 seconds, although before the upgrade or in the console it is immediate. Anyone has an idea, what could be wrong?
strace su somehow does not show anything useful, it ends with failure after 5 seconds, i.e. not switching to root
new su as a root is immediate in KDE5
Last edited by trubicoid on Fri Aug 12, 2016 8:55 am; edited 1 time in total |
|
| Back to top |
|
 |
trubicoid
Tux's lil' helper
Joined: 04 Aug 2009
Posts: 79
|
| Posted: Wed Jul 13, 2016 3:39 pm Post subject: |
|
|
| No one? Can at least someone with KDE5 try su and tell, if it is fast as usual or if he experiences a delay as me? |
|
| Back to top |
|
|
davidbrooke
Guru
Joined: 03 Jan 2015
Posts: 341
|
| Posted: Wed Jul 13, 2016 4:15 pm Post subject: |
|
|
Using "su" is immediate on my KDE5 installation.
I have no clue as to your issue but I don't upgrade....only do new installations. |
|
| Back to top |
|
|
asturm
Developer
Joined: 05 Apr 2007
Posts: 8935
|
| Posted: Wed Jul 13, 2016 4:43 pm Post subject: |
|
|
| It doesn't sound like anything related to Plasma or konsole... can you try with a different terminal emulator from within your Plasma session or with konsole in a different window manager, a new user? |
|
| Back to top |
|
|
trubicoid
Tux's lil' helper
Joined: 04 Aug 2009
Posts: 79
|
| Posted: Wed Jul 13, 2016 8:30 pm Post subject: |
|
|
I think the problem is related to something Plasma runs, not directly to Plasma nor konsole, e.g. polkit?
In TWM there is no delay in xterm nor konsole.
New user in plasma has the same delay (if he is in wheel group, otherwise it is a bit shorter).
In Plasma the console emulator does not matter, the same delay in konsole and xterm.
There are some sddm complains during the logging in about pam_systemd.so (I don't use systemd) and pam_kwallet, however I'm logged in fine, no delay. Nothing in the logs during the su delay.
| Code: | Jul 13 22:12:31 [sddm-helper] PAM unable to dlopen(/lib64/security/pam_systemd.so): /lib64/security/pam_systemd.so: cannot open shared object file: No such file or directory
Jul 13 22:12:31 [sddm-helper] PAM adding faulty module: /lib64/security/pam_systemd.so
Jul 13 22:12:31 [sddm-helper] pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Jul 13 22:12:39 [sddm-helper] pam_kwallet(sddm:auth): (null): pam_sm_authenticate_
Jul 13 22:12:39 [sddm-helper] pam_kwallet5(sddm:auth): (null): pam_sm_authenticate_
Jul 13 22:12:40 [sddm-helper] pam_kwallet(sddm:setcred): pam_kwallet: pam_sm_setcred
Jul 13 22:12:40 [sddm-helper] pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Jul 13 22:12:40 [sddm-helper] pam_unix(sddm:session): session opened for user fik by (uid=0)
Jul 13 22:12:40 [sddm-helper] pam_ck_connector(sddm:session): nox11 mode, ignoring PAM_TTY :0
Jul 13 22:12:40 [sddm-helper] pam_kwallet(sddm:session): pam_kwallet: pam_sm_open_session_
Jul 13 22:12:40 [sddm-helper] pam_kwallet(sddm:session): pam_kwallet: final socket path: /tmp/kwallet_fik.socket
Jul 13 22:12:40 [sddm-helper] pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session_
Jul 13 22:12:40 [sddm-helper] pam_kwallet5(sddm:session): pam_kwallet5: final socket path: /tmp/kwallet5_fik.socket
Jul 13 22:12:41 [polkitd] Registered Authentication Agent for unix-session:/org/freedesktop/ConsoleKit/Session7 (system bus name :1.41 [/usr/lib64/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jul 13 22:14:12 [su] Successful su for root by fik
Jul 13 22:14:12 [su] + /dev/pts/1 fik:root
Jul 13 22:14:12 [su] pam_unix(su:session): session opened for user root by fik(uid=1000) |
|
|
| Back to top |
|
|
toralf
Developer
Joined: 01 Feb 2004
Posts: 3922
Location: Hamburg
|
| Posted: Wed Jul 13, 2016 10:11 pm Post subject: |
|
|
| I had experiences annoying delays during log out from the desktop. It vanished when I switched to kf 5.23 + plasma 5.6.5. |
|
| Back to top |
|
|
trubicoid
Tux's lil' helper
Joined: 04 Aug 2009
Posts: 79
|
| Posted: Thu Jul 14, 2016 7:45 am Post subject: |
|
|
interesting, by kf 5.23 you mean kde-frameworks/kfilemetadata?
I have found an error message in ~/.xsession-errors
| Code: | | QXcbConnection: XCB error: 2 (BadValue), sequence: 56705, resource id: 23068702, major code: 141 (Unknown), minor code: 3 |
And there is probably related bug in kde, where they observe 20s delay but during logging in https://bugs.kde.org/show_bug.cgi?id=353203 |
|
| Back to top |
|
|
asturm
Developer
Joined: 05 Apr 2007
Posts: 8935
|
| Posted: Thu Jul 14, 2016 8:02 am Post subject: |
|
|
Yeah that QXcbConnection thing is a well-known error but won't cause any su delay.
On plasma workspace startup so many things are going on that issues with delays sometimes are caused by race conditions (I've seen dbus timeouts, splash screen timeout in a much earlier version) but again nothing that would cause any trouble for su.
Someone with more knowledge about what is going on when you 'su' would be helpful... |
|
| Back to top |
|
|
trubicoid
Tux's lil' helper
Joined: 04 Aug 2009
Posts: 79
|
| Posted: Sat Jul 16, 2016 4:20 pm Post subject: |
|
|
| Upgrading to unstable plasma 5.7.1 didn't solve the problem |
|
| Back to top |
|
|
roarinelk
Guru
Joined: 04 Mar 2004
Posts: 520
|
| Posted: Sun Jul 17, 2016 5:49 pm Post subject: |
|
|
are you using sddm?
What happens if you disable sddm, log in as your normal user in the text console, and then start KDE5 manually? In my case the "su" succeeds immediately. |
|
| Back to top |
|
|
trubicoid
Tux's lil' helper
Joined: 04 Aug 2009
Posts: 79
|
| Posted: Tue Aug 09, 2016 4:00 pm Post subject: |
|
|
yes, it is with sddm
strange thing, I just upgraded a second laptop to KDE5 and there is no 20s delay after su, I'll have to find the difference... |
|
| Back to top |
|
|
trubicoid
Tux's lil' helper
Joined: 04 Aug 2009
Posts: 79
|
| Posted: Fri Aug 12, 2016 8:56 am Post subject: |
|
|
the problem was in wrong primary group for the user, after setting the correct group and restart, the problem is gone
interestingly, the wrong group caused no problems in KDE4 |
|
| Back to top |
|
|
|
Desktop Environments
