> From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
> Date: Mon, 10 Dec 2018 02:30:23 -0600
>> 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.
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,
> 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
> 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:
> (or similar gui edition)
rpm -qa|grep -i pinentry
/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
I have also Leap 42.3 with KDE3 and it doesn't have this
Thanks your reply,
To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org