Announcement

Collapse
No announcement yet.

SUDO password problem fix

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    SUDO password problem fix

    A lot of folks have had an issue with their password not being accepted by KDESU in certain applications like Discover, Muon, and Ksystemlogs. I am one of them. It has taken a major amount of searching to find the correct answer, as most fixes are either way out of date, or do not conform to the "Kubuntu way". So I thought I would post the solution here so it is not buried deep within an older thread.

    I have not yet been able to determine what is causing the problem, but I did discover one fix that actually works. You need to create the file "kdesu" in /etc/sudoers.d and add the following line:

    Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty

    CLI instructions:

    $: cd /etc/sudoers.d
    $: sudo touch kdesu (enter user password)
    $: sudo pico kdesu (or use kate from Dolphin) (enter user password)

    Add the line "Defaults!/usr/lib/*/libexec/kf5/kdesu_stub !use_pty" (without the quotes) and save (in Pico its "<ctrl>o" to save, <ctrl>x to quit).


    Reboot.

    This is a significant PITA and I have no idea if there are any security implications. The seems to be a debian issue. If you have a better way to accomplish this in 22.04 and KDE 5, please feel free to comment below and I will test and add the solution here.

    Cheers
    Tags: None
    • Top
    • Bottom
    #2
    Recent updates should have added this configuration, though using a different file name - kdesu-sudoers instead of the file you created.
    This fix has been in the kubuntu-backports PPA, but it is making its way to users via normal updates, in phases.

    I don't think that this extra redundant file will cause any issues, worst case is that the one you added would need to be removed.
    Last edited by claydoh; Sep 12, 2022, 10:15 AM.
    • Top
    • Bottom

    Comment

      #3
      Originally posted by claydoh View Post
      Recent updates should have added this configuration, though using a different file name - kdesu-sudoers instead of the file you created.
      This fix has been in the kubuntu-backports PPA, but it is making its way to users via normal updates, in phases.

      I don't think that this extra redundant file will cause any issues, worst case is that the one you added would need to be removed.
      This is indeed the case. Once I got Muon working, I could force it to apply the update as dist-upgrade didn't do the trick. I deleted the file I created. I also have the "empty device name" issue, the fix should be available in a week. I could force it now but some people have has some problems so I will wait until its official. I am a bit surprised its taking this long to fix basic problems thar really shouldn't be there to start with.
      • Top
      • Bottom
      • Likes 1

      Comment

        #4
        Originally posted by ShadYoung View Post
        I am a bit surprised its taking this long to fix basic problems thar really shouldn't be there to start with.
        Patching, programming, and debuggings skills are always welcome to assist the volunteers....

        Though I am sure there was a small amount of finger pointing (where the bug actually is) and some bureaucracy involved (22.04 being LTS, and needing to follow an SRU process as opposed to only shunting updates to a PPA)

        In any case, this is more a workaround or hack, than a fix, which may explain the delay, if someone was looking into an actual remedy.
        https://bugs.kde.org/show_bug.cgi?id=452532
        https://bugs.debian.org/cgi-bin/bugr...gi?bug=1011624
        • Top
        • Bottom

        Comment

        Previous template Next
        Working...
        X