| Suse/Novell This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
Due to network maintenance being performed by our provider, LQ will be down starting at 05:01 AM UTC. The exact duration of the downtime isn't currently known. We apologize for the inconvenience.
|
 |
05-05-2007, 10:36 AM
|
#1
|
|
Member
Registered: Jan 2006
Location: Austin
Distribution: openSUSE 11.2
Posts: 167
Rep:
|
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.
Thank You,
|
|
|
|
05-08-2007, 05:02 AM
|
#2
|
|
LQ Newbie
Registered: Oct 2005
Location: Wellington New Zealand
Distribution: SuSe Linux 9.3 pro and SLES9
Posts: 2
Rep:
|
Login with kdesu failed
Quote:
|
Originally Posted by jdmcdaniel3
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).
|
|
|
|
05-09-2007, 07:45 AM
|
#3
|
|
Member
Registered: Oct 2005
Location: Scotland, UK
Distribution: Kubuntu 9.10, ubuntu 8.04.2 server
Posts: 156
Rep:
|
^^ 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?
Thanks
ryan
|
|
|
|
05-10-2007, 12:55 AM
|
#4
|
|
LQ Newbie
Registered: May 2007
Posts: 1
Rep:
|
same old problem i guess.
thanks for the info, kdeglobals worked like a charm. was quite painful logging in as root every time i needed to use yast.
|
|
|
|
05-24-2007, 06:20 AM
|
#5
|
|
Member
Registered: Feb 2004
Location: UK Hertfordshire
Distribution: Opensuse 11.1 plus Macs and a Vista computer on the network
Posts: 42
Rep:
|
Thanks James
I got pointed to your good work by mmn357157
My problem was v.sim .. see http://www.linuxquestions.org/questi....php?p=2761387
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 11:56 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|