KDE Error "Conversation with su failed" SuSE 10.2 Fix
SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
KDE Error "Conversation with su failed" SuSE 10.2 Fix
The other day I upgraded my kernel software and after the upgrade I had a new problem. For some reason I was unable to run Yast2 or konqueror using the --profile filemanagement option, both of which require you enter the root password. I downgraded the kernel back to my orginal version, but the problem still was present. When you would enter your root password in KDE, which uses KDESU as I understand it, you would get an error that read "Conversation with su failed" and the command would not work. I searched the net high and low and finally found the following fix.
You need to edit the file /opt/kde3/share/config/kdeglobals as a root user and add the following line at the end of the file and save it:
[super-user-command]
super-user-command=su
Once I added these two lines, all was back to normal. I would like to know if anyone else has had the same error message "Conversation with su failed" when using KDE and what you did to fix the problem.
The other day I upgraded my kernel software and after the upgrade I had a new problem. For some reason I was unable to run Yast2 or konqueror using the --profile filemanagement option, both of which require you enter the root password. I downgraded the kernel back to my orginal version, but the problem still was present. When you would enter your root password in KDE, which uses KDESU as I understand it, you would get an error that read "Conversation with su failed" and the command would not work. I searched the net high and low and finally found the following fix.
You need to edit the file /opt/kde3/share/config/kdeglobals as a root user and add the following line at the end of the file and save it:
[super-user-command]
super-user-command=su
Once I added these two lines, all was back to normal. I would like to know if anyone else has had the same error message "Conversation with su failed" when using KDE and what you did to fix the problem.
Thank You,
Thanks, this worked a charm for me too. Mine broke when I used yast to edit the sudo config to set a couple of commands to act more like ubuntu, to use my users password rather than root for mounting remote shares. I removed my changes using yast, but the problem did not go away. The sudoers file looked OK too so I was stumped as to why it wasn't working. Annoying as I was just trying to show a fellow Windows admin why sudo was better than vista's UAC (much more flexible).
^^ Thanks, it happened on my desktop, and didnt have time to research it so i just reinstalled. I didnt do any kernel updates or anything though, so does anyone have any ideas of what caused this? Its not happened on my friends desktop or my server yet. So is it just a matter of time?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.