Default kdesu to use sudo and not su

Have you recently installed openSUSE 11.0 and added:

username ALL=(ALL) NOPASSWD: ALL

Into your /etc/sudoers files, only to find out now when you launch yast it still prompts for a password?
The issue is actually that kdesu was switched from using sudo to su when elevating priviledges. This was not the behavior in openSUSE 10.3 and earlier versions of 11.0 (RC / Beta etc).

To restore this configuration you can running the following command:
kwriteconfig –file kdesurc –group super-user-command –key super-user-command sudo

Hope this actually helps someone.

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading ... Loading ...

About ben.kevan

I am ben kevan.. Well yeah. .that's about it.

14 Comments

  • ra100
    July 8, 2008 | Permalink |

    What can i say? Thanks, many thanks.I missed this very much.

  • blake
    July 8, 2008 | Permalink |

    It didn’t work on my system :( openSUSE11, using KDE 4.1 beta if that makes any difference. But thanks for trying :) .

  • tom
    July 8, 2008 | Permalink |

    Thanks a lot, I had the same annoying problem. For “copy and paste” users, please replace the “–” with “–” in your command.

  • ben.kevan
    July 8, 2008 | Permalink |

    Thank you for pointing that out Tom.

    Blake, and others using this.. please note that – in front of group and key are actually 2 dashes

    - – and not just one dash – (there is no space inbetween them)

  • July 8, 2008 | Permalink |

    Blake:

    cd ~/.kde4/share/config

    edit kdesurc

    Add this lines:

    [super-user-command]
    super-user-command=sudo

    Work on my opensuse 11.0 KDE 4.0 :D

  • Ricky
    July 8, 2008 | Permalink |

    thanks for the tip! it works!

  • July 8, 2008 | Permalink |

    Thank you!!! That was driving me crazy! :-)

  • ben.kevan
    July 8, 2008 | Permalink |

    Loni from http://forums.opensuse.org posted this:

    Did some research, discovered I have TWO versions of kwriteconfig (and
    others!) installed, one for kde3, another for kde4. imagine it’s because
    I’m running 3.5.9, but with some 4.x apps, so I get both runtimes.

    This can cause issues, because the two programs use slightly different syntax,
    the KDE4 kwriteconfig app uses single dash ‘-’ for options while the KDE3
    version uses double-dash ‘–’. grrr!

    Better solution is to actually create the file entry that command is
    *supposed* to be doing.

    look in .kde/share/config and .kde4/share/config for a file named ‘kdesurc’.

    If it doesn’t exist, create a new file named ‘kdesurc’.

    Add these two lines to the file:

    [super-user-command]
    super-user-command=sudo

    I did both .kde and .kde4 to make sure I catch whichever kdesu is called (v3
    or v4).

    This has worked for me, on both 32bit and 64bit systems, opensuse 11.0, KDE
    3.5.9 installs. Should also fix KDE4.x systems.

    Loni

    Thanks for that update Loni..

  • JP
    August 27, 2008 | Permalink |

    Doesn’t seem to work. It accepts the suoder password but no application is launched when typed from the shell( example kdesu /sbin/yast2 ) it just sits there. If I launch it from root it opens.

  • ben.kevan
    September 9, 2008 | Permalink |

    JP,

    Make sure you use double – and not a single -. Wordpress puts a double – into a single -.. so copy and paste will not work.

    I’ll have to fix this when I have time.

    Thanks

  • March 1, 2009 | Permalink |

    Every time i come here I am not dissapointed, nice post

  • September 10, 2009 | Permalink |

    Hi! I was surfing and found your blog post… nice! I love your blog. :) Cheers! Sandra. R.

  • September 11, 2009 | Permalink |

    Sign: umsun Hello!!! rcuwwymhyw and 1621ssgfhphzye and 5888I like your blog. cool post!

  • October 7, 2009 | Permalink |

    Sign: gfndc Hello!!! ybsvp and 3690hbunhfaxhf and 3334 : I will try to recommend this post to my friends and family, cuz its really helpful.

5 Trackbacks

Leave a comment

Add your comment below, or trackback from your own site. You can also subscribe to these comments via RSS.

Your email is never shared. Required fields are marked *