I’ve recently installed from scratch Suse 11.2, and I’m having a bit of an issue with kdesu.
Basically everytime I try to start an application using kdesu (e.g. Yast), the windows where to put the password appears, but when I click on OK, or I press enter nothing happens, the windows stays where it was, and of course the program does not start.
The same issue occurs when I type the password to open kwalletmanager, I suppose the two things are connected.
You don’t need to do kdesu when starting Yast. If you click on Yast it will automatically ask for the admin/root password before it opens. I would assume that would be the same for kwallet but I don’t use it.
That’s the problem!
When Yast (or any other program that requires root privileges) automatically ask for the admin/root password, it opens the window I mentioned in my first post, the one I get stuck in.
If you notice it, the title of this window is something like “Execute as root - <<su>> for KDE”, i.e. the program launches kdesu for you, and I cannot go further
>
> Hi there,
>
> I’ve recently installed from scratch Suse 11.2, and I’m having a bit
> of an issue with kdesu.
>
> Basically everytime I try to start an application using kdesu (e.g.
> Yast), the windows where to put the password appears, but when I
> click on OK, or I press enter nothing happens, the windows stays
> where it was, and of course the program does not start.
>
> The same issue occurs when I type the password to open
> kwalletmanager, I suppose the two things are connected.
>
> Any suggestion would be much appreciated
>
What version of KDE are you using? I have openSUSE2 with KDE 4.3.4 and
kdesu works fine. Did you put in the correct root password? If not it
will go away and nothing happen.
I’m using KDE 4.3.1 release 6.
It doesn’t matter using the right password. Either if I use the right one, a wrong one or I leave it blank, the result is the same
Let me try to explain better…
Let’s say for simplicity that I want to start Yast (but again, it is the same with every program that needs root privileges)
Using su then launching yast, does work.
Using kdesu yast, OR clicking on the yast icon, does NOT work, because in both cases you are using the kdesu interface
I get no output at all…
Since pressing enter (or clicking on ok) when the kdesu window appears does not have any effect, there is no output yet in the console…
Do you think that reinstalling some packages will help someway? If so, which one?
I get no output at all, but in this case is pretty normal I think…
Usually you get an output after you have clicked on ok or pressed enter whether the password you entered was correct or not.
In my case, since both enter and click don’t work, the console is still waiting for an input that can’t see.
Since it seems that I am the only one experiencing this problem, do you think that reinstalling some packages will help? If so, which one?
On 12/27/2009 10:46 AM, MadSplinter wrote:
>
> caf4926;2094176 Wrote:
>> How else did you expect to do it?
>>
>> Are you saying using the launcher from the menu doesn’t start yast.
>
> Let me try to explain better…
> Let’s say for simplicity that I want to start Yast (but again, it is
> the same with every program that needs root privileges)
>
> Using su then launching yast, does work.
>
> Using kdesu yast, OR clicking on the yast icon, does NOT work, because
> in both cases you are using the kdesu interface
Have you messed with the /etc/sudoers file? If so, try using your
password instead of the root password at the dialog prompt…
To the op,
Does your machine running 24/7? I noticed it in this side, when not powering off my machine for a couple of days, sometimes kdesu stops working nor the yast icon from the kickoff menu when clicking it does nothing. When I restart the machine it works.
To caf4926:
I followed your procedure, but still having the same issue.
To Kevin Miller:
I did not configure the sudoers at all. Moreover, as I already said, putting in the correct password, the wrong one or no password at all does not make any difference.
To joerione:
The machine is a laptop, so it never stays on for long periods