YaST login usually doesn't work until I logoff and log back on...

I have a continuing problem now - every time I invoke YaST (KDE) and supply the password, the “Run as root” window seems to freeze. The fix is to close all apps and logout, then log back in and it works fine. Does this sound familiar to anyone? Can anyone suggest a procedure for troubleshooting?

Thank You!
PattiM

Hi PattiMichelle

Open a terminal and run

sudo journalctl -f

then launch YaST and enter your root credentials. Observe/capture the output, and report back here.

Possibly.

I don’t do Yast that way, so I’m not sure.

Check the output of

uname -a

The purpose of this is to find out which kernel you are using.

If it turns out that you are using kernel 4.12.14-lp150.12.25-default, then run updates to get you to kernel 4.12.14-lp150.12.28-default and that should fix your problem.

If you are running a different kernel, then my diagnosis is probably wrong.

Please open the editor of the KDE program starter check the command being used by the YaST menu entry – it should be:

/usr/bin/xdg-su -c /sbin/yast2

Please also check the contents of ‘/etc/sudoers’ – use “visudo” from the user “root” …

  • You may have to download the “.rpm” file of the “sudo” package to obtain a clean copy of the ‘sudoers’ file for comparison with your current “sudo” settings …

Besides the above which are all good troubleshooting tries to gather useful info,
You also try launching YaST from a root console to narrow down what might be your cause… and might be a practical workaround until your problem is fixed…

su
yast2

TSU

Aye, que bueno! Muchas gracias, Deano!! lol!

Dec 19 12:31:35 linux-iczo org_kde_powerdevil[3418]: powerdevil: Releasing inhibition with cookie  24
Dec 19 12:31:35 linux-iczo org_kde_powerdevil[3418]: powerdevil: It was only scheduled for inhibition but not enforced yet, just discarding it
Dec 19 12:31:37 linux-iczo org_kde_powerdevil[3418]: powerdevil: Enforcing inhibition from ":1.11" "firefox" with cookie 24 and reason "video-playing"
Dec 19 12:31:37 linux-iczo org_kde_powerdevil[3418]: powerdevil: By the time we wanted to enforce the inhibition it was already gone; discarding it
Dec 19 12:31:40 linux-iczo su[10822]: pam_kwallet5(su:auth): (null): pam_sm_authenticate
Dec 19 12:31:40 linux-iczo su[10822]: (to root) patti on pts/3
Dec 19 12:31:40 linux-iczo su[10822]: pam_kwallet5(su:setcred): pam_kwallet5: pam_sm_setcred
Dec 19 12:31:40 linux-iczo su[10822]: pam_systemd(su:session): Cannot create session: Already running in a session or user slice
Dec 19 12:31:40 linux-iczo su[10822]: pam_unix(su:session): session opened for user root by (uid=1000)
Dec 19 12:31:40 linux-iczo su[10822]: pam_kwallet5(su:session): pam_kwallet5: pam_sm_open_session
Dec 19 12:31:40 linux-iczo su[10825]: pam_kwallet5(su:session): pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Dec 19 12:31:40 linux-iczo su[10825]: pam_kwallet5(su:session): pam_kwallet5-kwalletd: Couldn't listen in socket
Dec 19 12:31:40 linux-iczo su[10825]: pam_kwallet5(su:session): pam_kwallet5: Impossible to write walletKey to walletPipe
Dec 19 12:31:40 linux-iczo su[10825]: pam_unix(su:session): session closed for user root
Dec 19 12:31:40 linux-iczo su[10825]: pam_kwallet5(su:session): pam_kwallet5: pam_sm_close_session
Dec 19 12:31:40 linux-iczo su[10825]: pam_kwallet5(su:setcred): pam_kwallet5: pam_sm_setcred
Dec 19 12:31:40 linux-iczo su[10822]: pam_kwallet5(su:session): pam_kwallet5: Impossible to write walletKey to walletPipe

I note that pam-kwallet5 seems to be the culprit here. I’m running openSUSE 15 with KDE and don’t have pam-kwallet installed. My comparable authentication dialogue looks like this…

Dec 20 08:53:24 linux-kgxs su[7009]: (to root) dean on pts/3
Dec 20 08:53:24 linux-kgxs su[7009]: pam_systemd(su:session): Cannot create session: Already running in a session or user slice
Dec 20 08:53:24 linux-kgxs su[7009]: pam_unix(su:session): session opened for user root by (uid=1000)
Dec 20 08:53:24 linux-kgxs su[7009]: pam_unix(su:session): session closed for user root
Dec 20 08:53:24 linux-kgxs kdesu[7001]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 895, resource id: 39870514, major code: 40 (TranslateCoords), minor code: 0
Dec 20 08:53:24 linux-kgxs kwin_x11[6527]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 60083, resource id: 65011731, major code: 18 (ChangeProperty), minor code: 0
Dec 20 08:53:24 linux-kgxs su[7014]: (to root) dean on pts/3
Dec 20 08:53:24 linux-kgxs su[7014]: pam_systemd(su:session): Cannot create session: Already running in a session or user slice
Dec 20 08:53:24 linux-kgxs su[7014]: pam_unix(su:session): session opened for user root by (uid=1000)

What repos are you using BTW?

zypper lr -d

Hi PattiMichelle,

I suppose you invoke the default KDE launcher, which does


kdesu yast2

I suggest you run that from a terminal window ( mentioning it, consider yakuake - install, run, from there hit F12 and it’ll drop down from the top of the KDE desktop ), and have a close look at the output it generates. A second thing, to make sure it’s not some user config, would be to create a fresh test user, login as that user and see if the test user experiences the same issue.

I note that there are a number of bug reports concerning pam-kwallet5. This one seems to reflect the behaviour you describe…
https://bugzilla.redhat.com/show_bug.cgi?id=1581495
and this may also be relevant…
https://bugzilla.opensuse.org/show_bug.cgi?id=1012781

linux-iczo:/home/patti # zypper lr -d
Repository priorities are without effect. All enabled repositories share the same priority.                                                                                                                                

#  | Alias                               | Name                                    | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                            | Service
---+-------------------------------------+-----------------------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------------------------+--------
 1 | http-download.opensuse.org-666493bd | home:ecsos:gcc                          | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/repositories/home:/ecsos:/gcc/openSUSE_Leap_15.0/ |        
 2 | openSUSE-Leap-15.0-1                | openSUSE-Leap-15.0-1                    | No      | ----      | ----    |   99     | rpm-md | hd:///?device=/dev/disk/by-id/usb-_Patriot_Memory_07BA1101B2F91C70-0:0-part2   |        
 3 | openSUSE_Leap_15.0                  | packman/suse/openSUSE_Leap_15.0/        | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.0/            |        
 4 | openSUSE_Leap_15.0_1                | science/openSUSE_Leap_15.0/             | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/science/openSUSE_Leap_15.0/          |        
 5 | openSUSE_Leap_15.0_2                | mozilla/openSUSE_Leap_15.0/             | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.0/          |        
 6 | openSUSE_Leap_15.0_3                | games/openSUSE_Leap_15.0/               | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/games/openSUSE_Leap_15.0/            |        
 7 | openSUSE_Leap_15.0_4                | /Wine/openSUSE_Leap_15.0/               | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_Leap_15.0/  |        
 8 | repo-debug                          | openSUSE-Leap-15.0-Debug                | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/distribution/leap/15.0/repo/oss/            |        
 9 | repo-debug-non-oss                  | openSUSE-Leap-15.0-Debug-Non-Oss        | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/distribution/leap/15.0/repo/non-oss/        |        
10 | repo-debug-update                   | openSUSE-Leap-15.0-Update-Debug         | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/update/leap/15.0/oss/                       |        
11 | repo-debug-update-non-oss           | openSUSE-Leap-15.0-Update-Debug-Non-Oss | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/update/leap/15.0/non-oss/                   |        
12 | repo-non-oss                        | openSUSE-Leap-15.0-Non-Oss              | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/non-oss/              |        
13 | repo-oss                            | openSUSE-Leap-15.0-Oss                  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/oss/                  |        
14 | repo-source                         | openSUSE-Leap-15.0-Source               | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/distribution/leap/15.0/repo/oss/           |        
15 | repo-source-non-oss                 | openSUSE-Leap-15.0-Source-Non-Oss       | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/distribution/leap/15.0/repo/non-oss/       |        
16 | repo-update                         | openSUSE-Leap-15.0-Update               | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.0/oss/                             |        
17 | repo-update-non-oss                 | openSUSE-Leap-15.0-Update-Non-Oss       | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.0/non-oss/                         |        


After logoff and log on - YaST worked. This is the output. I also cannot find pam-kwallet5 with YaST. I’ll keep an eye on it until it fails again.

Dec 19 14:03:20 linux-iczo plasmashell[12972]: QXcbConnection: XCB error: 2 (BadValue), sequence: 3222, resource id: 69206021, major code: 142 (Unknown), minor code: 3
Dec 19 14:03:20 linux-iczo plasmashell[12972]: QXcbConnection: XCB error: 2 (BadValue), sequence: 3223, resource id: 71303173, major code: 142 (Unknown), minor code: 3
Dec 19 14:03:20 linux-iczo plasmashell[12972]: QXcbConnection: XCB error: 2 (BadValue), sequence: 3224, resource id: 73400325, major code: 142 (Unknown), minor code: 3
Dec 19 14:03:28 linux-iczo sudo[13693]: pam_kwallet5(sudo:auth): (null): pam_sm_authenticate
Dec 19 14:03:28 linux-iczo sudo[13693]:    patti : TTY=pts/3 ; PWD=/home/patti ; USER=root ; COMMAND=/usr/bin/journalctl -f
Dec 19 14:03:28 linux-iczo sudo[13693]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred
Dec 19 14:03:28 linux-iczo sudo[13693]: pam_systemd(sudo:session): Cannot create session: Already running in a session or user slice
Dec 19 14:03:28 linux-iczo sudo[13693]: pam_unix(sudo:session): session opened for user root by patti(uid=0)
Dec 19 14:03:28 linux-iczo sudo[13693]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_open_session
Dec 19 14:03:28 linux-iczo sudo[13693]: pam_kwallet5(sudo:session): pam_kwallet5: we were already executed
Dec 19 14:03:35 linux-iczo su[13756]: pam_kwallet5(su:auth): (null): pam_sm_authenticate
Dec 19 14:03:35 linux-iczo su[13756]: pam_kwallet5(su:auth): (null): we were already executed
Dec 19 14:03:35 linux-iczo su[13756]: (to root) patti on pts/4
Dec 19 14:03:35 linux-iczo su[13756]: pam_kwallet5(su:setcred): (null): pam_sm_setcred
Dec 19 14:03:35 linux-iczo su[13756]: pam_systemd(su:session): Cannot create session: Already running in a session or user slice
Dec 19 14:03:35 linux-iczo su[13756]: pam_unix(su:session): session opened for user root by (uid=1000)
Dec 19 14:03:35 linux-iczo su[13756]: pam_kwallet5(su:session): (null): pam_sm_open_session
Dec 19 14:03:35 linux-iczo su[13756]: pam_kwallet5(su:session): (null): we were already executed
Dec 19 14:03:35 linux-iczo su[13756]: pam_unix(su:session): session closed for user root
Dec 19 14:03:35 linux-iczo su[13756]: pam_kwallet5(su:session): (null): pam_sm_close_session
Dec 19 14:03:35 linux-iczo su[13756]: pam_kwallet5(su:setcred): (null): pam_sm_setcred
Dec 19 14:03:35 linux-iczo kwin_x11[12966]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 29830, resource id: 115343379, major code: 18 (ChangeProperty), minor code: 0
Dec 19 14:03:35 linux-iczo su[13761]: pam_kwallet5(su:auth): (null): pam_sm_authenticate
Dec 19 14:03:35 linux-iczo su[13761]: pam_kwallet5(su:auth): (null): we were already executed
Dec 19 14:03:35 linux-iczo su[13761]: (to root) patti on pts/4
Dec 19 14:03:35 linux-iczo su[13761]: pam_kwallet5(su:setcred): (null): pam_sm_setcred
Dec 19 14:03:35 linux-iczo su[13761]: pam_systemd(su:session): Cannot create session: Already running in a session or user slice
Dec 19 14:03:35 linux-iczo su[13761]: pam_unix(su:session): session opened for user root by (uid=1000)
Dec 19 14:03:35 linux-iczo su[13761]: pam_kwallet5(su:session): (null): pam_sm_open_session
Dec 19 14:03:35 linux-iczo su[13761]: pam_kwallet5(su:session): (null): we were already executed
Dec 19 14:03:36 linux-iczo plasmashell[12972]: plasma-pk-updates: Transaction status changed: "finished" "(100%)"
Dec 19 14:03:36 linux-iczo PackageKit[13526]: refresh-cache transaction /1_dcaacaad from uid 1000 finished with success after 24112ms
Dec 19 14:03:36 linux-iczo plasmashell[12972]: plasma-pk-updates: Transaction "/1_dcaacaad" finished with status "success" in 24 seconds
Dec 19 14:03:36 linux-iczo plasmashell[12972]: plasma-pk-updates: Cache transaction finished successfully
Dec 19 14:03:36 linux-iczo plasmashell[12972]: plasma-pk-updates: Updates changed, getting updates!
Dec 19 14:03:36 linux-iczo plasmashell[12972]: plasma-pk-updates: Is net online: true
Dec 19 14:03:36 linux-iczo plasmashell[12972]: plasma-pk-updates: Is net online: true
Dec 19 14:03:36 linux-iczo plasmashell[12972]: plasma-pk-updates: Transaction status changed: "wait" "(101%)"
Dec 19 14:03:36 linux-iczo plasmashell[12972]: plasma-pk-updates: Transaction status changed: "setup" "(101%)"
Dec 19 14:03:36 linux-iczo plasmashell[12972]: plasma-pk-updates: Transaction status changed: "query" "(101%)"
Dec 19 14:03:37 linux-iczo plasmashell[12972]: plasma-pk-updates: Transaction status changed: "refresh-cache" "(0%)"
Dec 19 14:03:43 linux-iczo PackageKit[13526]: get-updates transaction /2_eaeeceec from uid 1000 finished with success after 6406ms
Dec 19 14:03:43 linux-iczo plasmashell[12972]: plasma-pk-updates: Transaction status changed: "finished" "(100%)"
Dec 19 14:03:43 linux-iczo plasmashell[12972]: plasma-pk-updates: Transaction "/2_eaeeceec" finished with status "success" in 6 seconds
Dec 19 14:03:43 linux-iczo plasmashell[12972]: plasma-pk-updates: Check updates transaction finished successfully
Dec 19 14:03:43 linux-iczo plasmashell[12972]: plasma-pk-updates: Total number of updates:  0
Dec 19 14:03:43 linux-iczo plasmashell[12972]: plasma-pk-updates: Is net online: true
Dec 19 14:03:43 linux-iczo plasmashell[12972]: plasma-pk-updates: Is net online: true
Dec 19 14:03:43 linux-iczo plasmashell[12972]: plasma-pk-updates: Is net online: true
Dec 19 14:03:43 linux-iczo plasmashell[12972]: plasma-pk-updates: Is net online: true
Dec 19 14:03:43 linux-iczo plasmashell[12972]: plasma-pk-updates: Is net online: true
Dec 19 14:03:43 linux-iczo plasmashell[12972]: plasma-pk-updates: Is net online: true
Dec 19 14:03:43 linux-iczo plasmashell[12972]: qml: Populating model

pam_kwallet is not installed by default
The messages only show the updater applet running and getting a list of new updates.

Whilst it’s doing that, YaST’s softwaremanager will be locked for obvious reasons.

Yes, I have been noticing a number of problems attributed to pam_kwallet.

No, the problem is not that YaST locks up - it is that the applet which requests my root password “Run as root - KDE su” locks up. It won’t respond to mouse clicks except the ctrl-alt-esc kill. After killing Run as root, it locks up again until I log out and log back in - then it operates normally.

I tried finding pam-kwallet with YaST in order to try removing it, but YaST can’t find it.

It is “pam_kwallet” – not “pam-kwallet”.

As nrickert mentioned, pam_kwallet is the name of the package. Remove it with

zypper rm pam-kwallet

then see how the YaST authentication process goes.

:open_mouth: Oops. Yes, I found it. What’s very odd, is that since I’ve left the command “sudo journalctl -f” running in konsole, that problem hasn’t happened. I was hoping to catch it when it occurred. I haven’t removed pam_kwallet yet. (Is it safe to simply remove?) It may be an intermittent problem, but had been happening daily for a couple of weeks…

Yes, it is safe to remove “pam_kwallet”.

However, you may then find that you are prompted to open kdewallet. If you see such a prompt, then you probably need to use your login password as the password to unlock “kdewallet”.

@PattiMichelle:

If you’re using KWallet to store the information KMail uses to access the POP3 or IMAP services of your ISP or, WLAN access keys then,

  • Consider migrating the Wallet named “kdewallet” to a Wallet (only for KMail and WLAN data) using the Blowfish encryption and «an empty (NULL) password
    » …

You’ll have to move the existing Wallet named “kdewallet” to another name before recreating the Wallet named “kdewallet” as a Wallet which works at login (without “pam_kwallet”) in a simple and reliable way …