Bug 78948

I'm having the same problem, 
	using compiled sources (CVS, kdelibs from 4 April 2004) on gentoo
	gcc 3.3.3
	Linux 2.6.3

though i can't see the console output you mention

I fixed this bug with the attached patch.
Pratically the line 81 in kdelibs/kdesu/su.cpp in KDE_3_2_BRANCH and into HEAD 
(if into HEAD it's yet present I don't checked if it is so because I did not 
compiled HEAD but I think it's so because the file is the same till 5 days 
ago) have to be deleted. If you tell me ok I can commit into BRANCH and HEAD.


Created an attachment (id=5618)
bugfix-78948.diff

Patch is not correct, we want to get a login shell.

Does it help if you change:
    args += "-";
    args += "-c";
    args += QCString(__KDE_BINDIR) + "/kdesu_stub";
to
    args += "-c";
    args += QCString(__KDE_BINDIR) + "/kdesu_stub";
    args += "-";
?

> Patch is not correct, we want to get a login shell.
>
Well, I didn't understand how the things work, I just see the difference with 
a KDE 3.2.0 that it works. I tryed to understand the code, but in few time 
it's difficult.
> Does it help if you change:
>     args += "-";
>     args += "-c";
>     args += QCString(__KDE_BINDIR) + "/kdesu_stub";
> to
>     args += "-c";
>     args += QCString(__KDE_BINDIR) + "/kdesu_stub";
>     args += "-";
> ?
Yes. I tryed your suggest and it works. We can close this bug applying your 
chainge to KDE_3_2_BRANCH  and to the HEAD into kdelibs/kdesu/su.cpp.

> Patch is not correct, we want to get a login shell.
>
Well, I didn't understand how the things work, I just see the difference with 
a KDE 3.2.0 that it works. I tryed to understand the code, but in few time 
it's difficult.
> Does it help if you change:
>     args += "-";
>     args += "-c";
>     args += QCString(__KDE_BINDIR) + "/kdesu_stub";
> to
>     args += "-c";
>     args += QCString(__KDE_BINDIR) + "/kdesu_stub";
>     args += "-";
> ?
Yes. I tryed your suggest and it works. We can close this bug applying your 
chainge to KDE_3_2_BRANCH  and to the HEAD into kdelibs/kdesu/su.cpp.

CVS commit by waba: 

put "-" after "-c <command>" (BR78948)
CCMAIL: 78948-done@bugs.kde.org


  M +2 -2      su.cpp   1.35


--- kdelibs/kdesu/su.cpp  #1.34:1.35
@@ -79,7 +79,7 @@ int SuProcess::exec(const char *password
     else
         args += m_User;
-    args += "-";
     args += "-c";
     args += QCString(__KDE_BINDIR) + "/kdesu_stub";
+    args += "-";
 
     QCString command = __PATH_SU;

*** Bug 80049 has been marked as a duplicate of this bug. ***

*** Bug 80034 has been marked as a duplicate of this bug. ***

*** Bug 80055 has been marked as a duplicate of this bug. ***

The bug made it into KDE 3.2.2. The fix mentioned above solves the problem.

*** Bug 81757 has been marked as a duplicate of this bug. ***

I have the same problem with kdesu in KDE 3.5.5.
Debian SID
Kernel 2.6.17

Same here on Debian Etch. KDE 3.5.5, kernel 2.6.16-i686

Yep, please reopen for kde 3.5.5 (Debian Etch, Kernel 2.6.17)

One more here..
Debian Etch, kernel 2.6.17-2-amd64, KDE 3.5.5

Another one:
Debian Etch, kernel 2.6.18-1, KDE 3.5.5
kdesu does not accept root password ("wrong password")

I can confirm on suse 10.2 w/ kde 3.5.5 release 45 on kernel 2.6.18.2-34.
kdesu does not accept root password ("wrong password")

Same problem here on some Debian systems/KDE 3.5. I think that 
the problem is that kdesu fails to interpret the reason for failure
which seems to be that root is not allow to open X windows any
more. If I open a Konsole, type host +, su - and then try to start 
any KDE application, I get also some error message for invalid display.

If it is not possible to evaluate the error message from the called application, then I suggest to just change the error message string
into: 

Error while trying to run $application with root privileges. 
Maybe you mistyped root password, or root has no access to current display.

The comment I posted above is not valid, as I could trace back the error to a bug in the sudo - yast module. Using visudo manually fixes the prob for me.

Same issue here on SUSE 10.2 with KDE 3.5.5... but in my case, the problem is that the message is wrong.  It prompts me for the root/administrator password, when what it really wants is my *user* password.  When I enter my *user* password, it works.  (I had added myself to the sudoers file and allowed myself to use sudo to run all commands as root by entering my user password).

Argh... I should've read Comment 19 before posting...