Siduction Forum

Siduction Forum => Software - Support => Topic started by: mylo on 2013/12/26, 21:44:44

Title: Problem on RC1 with cuops or krusader called in root mode
Post by: mylo on 2013/12/26, 21:44:44

Hi all,

I made a fresh install of the RC1 to a new box onto a SSD. from a boot-installer stick.
Everything went fine, but I have a problem:

If I call krusader in root-mode (from the menu), the root-PW is requested. After input, the window stalls and does not come back.
What can I do?
I have comparable problems with cups (configuring printer via menu item). After root-PW input also nothing happens (here just after some trials, but no success).

Title: Re: Problem on RC1 with cuops or krusader called in root mode
Post by: devil on 2013/12/27, 00:33:25

do these things work if you call them from a root shell where you became root with suxterm instead of su/sux?


greetz
devil

Title: Re: Problem on RC1 with cuops or krusader called in root mode
Post by: melmarker on 2013/12/27, 01:50:02

mylo - try the right pw? It's only a vague guess :)

Title: Re: Problem on RC1 with cuops or krusader called in root mode
Post by: ayla on 2013/12/27, 16:00:53

same problem here with root-krusader and configure-cups (two machines amd64).
Calling from suxterm works.

But: e.g. gparted started from menue and password requester works.

Title: Re: Problem on RC1 with cuops or krusader called in root mode
Post by: bevo on 2013/12/27, 19:40:58

I have this problem on one system (amd64) after todays DU. This is not the RC1 Installation. Two other 64bit systems also DUed today working fine.

bevo

Title: Re: Problem on RC1 with cuops or krusader called in root mode
Post by: mylo on 2013/12/27, 23:20:41

Quote from: ayla on 2013/12/27, 16:00:53

same problem here with root-krusader and configure-cups (two machines amd64).
Calling from suxterm works.

But: e.g. gparted started from menue and password requester works.

Hi ayla, I confirm your experience. However, I am wondering, that hints from the following thread do not help (as "krusaderrc" file is not avail):

Quote from: mylo on 2013/08/07, 23:31:14

Quote from: qwerthi

Hallo mylo,
hatte auch diese Probleme.
Mein kdesurc unter /home/user/.kde/share/config/ gehörte root und in der config stand
  "super-user-command=sudo".
Ich habe die config auf
  "super-user-command=kdesu" geändert und den Besitz wieder an den Standarduser übergeben.
...

Title: Re: Problem on RC1 with cuops or krusader called in root mode
Post by: devil on 2013/12/28, 02:22:46

.kde/share/config/krusaderrc
mlocate would have told you that


greetz
devil

Title: Re: Problem on RC1 with cuops or krusader called in root mode
Post by: mylo on 2013/12/28, 11:24:56

Hi devil,

you are right , the file is there. Yesterday I looked and searched --> nothing. I have the feeling my inst is incomplete as kmail and vlc are missing in the kmenu.
Back to krusader:
The file krusaderrc does not contain a line like

Code: [Select]

super-user-command=...Just under

Code: [Select]

[Dependencies]
.....
kdesu=/usr/lib/kde4/libexec/kdesu
....[Search]
ContainsText Completion=super-user-command
ContainsText History=super-user-command
SearchFor Completion=kdesurc,kdesurc*,*
SearchFor History=*,kdesurc*,kdesurc...lines deal with kdesu, no line deals with sudo.

Can I just add the line

Code: [Select]

super-user-command=kdesuto get it working? Under which section does this have to appear?

May be a full inst by dvd works better, I have to think about, as other progs are missing.