From: "David C. Rankin" Date: Mon, 10 Dec 2018 02:30:23 -0600 Message-id: <66aaaea5-7e50-9c81-b973-75e3b3e867aa@suddenlinkmail.com>

...

On 12/09/2018 03:21 PM, Felix Miata wrote:

Konsole -> Session -> New Root Shell -> yast2

Won't workaround?

Or just Konsole -> su to root.

David, Felix, Konsole root shell or su-ing in any terminal window works, so it is not that I cannot run programs as root at all.

Another possibility is the Yast package you have installed may conflict with the non-kde3 version. Specifically,

yast2-control-center-qt3-2.17.3-10.1.x86_6

is provided in the KDE3 repo, while there is a comparable "yast2-control-center" provided by the main OSS repo.

I installed yast2-control-center-qt3 when I installed KDE3. Now I replaced it with yast2-control-center-4.0.4. None of them works. And not only yast is affected, I cannot start other applications as root either, eg krusader root mode or kde3 control center administrator mode.

Another possible issue is the lack of a pinentry package to prompt for the root password upon su (as well as any time GPG is invoked, etc..) Make sure you have the following:

pinentry pinentry-gtk2

(or similar gui edition)

rpm -qa|grep -i pinentry pinentry-gtk2-1.1.0-lp150.2.4.x86_64 pinentry-qt5-1.1.0-lp150.2.4.x86_64 pinentry-1.1.0-lp150.2.4.x86_64 /var/log/messages show these line just after a kdesu attempt: 2018-12-11T20:06:08.117728+01:00 linux su: gkr-pam: couldn't get the password from user: Conversation error 2018-12-11T20:06:08.118334+01:00 linux su: pam_unix(su:auth): auth could not identify password for [root] 2018-12-11T20:06:08.124978+01:00 linux su: FAILED SU (to root) test on pts/4 I have also Leap 42.3 with KDE3 and it doesn't have this problem. Thanks your reply, Istvan -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde3+owner@opensuse.org