KDE file manager problem

[GreyGeek]

did you reboot,,,,I had to

VINNY

yup

[oshunluvr]

That fixes the protocol died error when launching kdesudo dolphin from the Desktop. Thanks!

Yeah, I just discovered that this week.

[wizard10000]

Start with 'kdesudo dbus-run-session konqueror'

This is (sort of) the way I start dolphin as root. I was still not happy with the result using kdesudo so I symlinked kdesu into /usr/bin and running dolphin as root works the way I want it to when used with dbus-run-session.

wizard@wizard-laptop:/usr/bin$ ls -la kdesu
lrwxrwxrwx 1 root root 27 Nov 25 11:42 kdesu -> /usr/lib/kde4/libexec/kdesu

On identifying applications run as root, my ~/.bashrc uses a green prompt where root's is red and with the gooey applications in KDE the color scheme I use is *slightly* different.

In "View Background" my user's color is #eaeaeb (slightly off-white) while root's color scheme uses #f7e7ff (just enough pink that you notice it).

edit: My ~/.config/kdesurc is also a little different based on recommendations I got here. When I do 'kdesudo dbus-run-session dolphin' I get no icons but it works just fine with kdesu.

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

edit v2.0: Using kdesu instead of kdesudo also causes krusader to theme correctly for me. I have no idea why as I copied krusader's config from my home directory to root's

[wizard10000]

I liked vinny's method of coloring icons better than my idea of coloring background, so check it out -

[kubicle]

I skimmed through the thing looking for a way to turn krusader single-pane for you

The panes are resizable, and you can make one or the other 100% width, effectively giving you a "single panel"...both panels also support individual tree view panes, so you can make krusader have a "treeview+single panel" look if you prefer.

You can create a profile for it (and make it the start profile)...and you'd probably want to save the panel settings in krusader configuration, but krusader is really configurable.

EDIT: obligatory screenshot added:

[GreyGeek]

The panes are resizable, and you can make one or the other 100% width, effectively giving you a "single panel"...both panels also support individual tree view panes, so you can make krusader have a "treeview+single panel" look if you prefer.

You can create a profile for it (and make it the start profile)...and you'd probably want to save the panel settings in krusader configuration, but krusader is really configurable.

EDIT: obligatory screenshot added:

Does that setup behave like Dolphin? When you click on a directory in the left panel does it open the listing of the contents in the right panel? Mine doesn't.

[kubicle]

Does that setup behave like Dolphin? When you click on a directory in the left panel does it open the listing of the contents in the right panel? Mine doesn't.

Does your visible panel have focus (the hidden panel still exists and if it has focus, it follows your tree-view clicks...and not the visible panel). press "Tab" or click on the visible panel to witch focus.

[GreyGeek]

Ah, like this!


Thanks!

[vinnywright]

ok ,,,so I got upgraded to kate-17.03.90 today ,,,,,,,,,,no more using Kate with sudo to edit root files ;(

sudoedit gives a vi terminal ,,,,,,,,,,,,,guess I must learn vi ?

however Krusaders built it advanced text editor will edit root files (wile in root mode),,,,,,,,for now.

VINNY

[wizard10000]

sudoedit gives a vi terminal ,,,,,,,,,,,,,guess I must learn vi ?

You can change it to nano in ~/.bashrc - add this:

export VISUAL=nano
export EDITOR="$VISUAL"

edit: I don't know whose environment sudoedit uses, so you may need to change /root/.bashrc as well.

[GreyGeek]

Why not just
export EDITOR=nano



Sent from my iPhone using Tapatalk

[wizard10000]

Why not just
export EDITOR=nano

That's what I thought as well, but when you get back at a PC there's a pretty good discussion here -

https://unix.stackexchange.com/quest...the-difference

Apparently the two variables have different meanings in bash; both of them are text editors and bash apparently calls $VISUAL and if that fails, calls $EDITOR.

I probably shouldn't mention there's also a $SYSTEMD_EDITOR variable in there

[GreyGeek]

That's what I thought as well, but when you get back at a PC there's a pretty good discussion here -

https://unix.stackexchange.com/quest...the-difference

Apparently the two variables have different meanings in bash; both of them are text editors and bash apparently calls $VISUAL and if that fails, calls $EDITOR.

I probably shouldn't mention there's also a $SYSTEMD_EDITOR variable in there

I checked my environment using "env" and didn't notice either EDITOR or VISUAL in my env settings, nor did I see them in the root env settings.

The man page of sudoedit states:

2. The editor specified by the policy is run to edit the temporary files. The sudoers policy uses
the SUDO_EDITOR, VISUAL and EDITOR environment variables (in that order). If none of
SUDO_EDITOR, VISUAL or EDITOR are set, the first program listed in the editor sudoers(5) option
is used.

In that quote you gave one person suspected that VISUAL was for GUI editors (which might require a KDESUDO prepend) and EDITOR was for the CLI.

So, I suspect that in order to avoid confusion with other programs that may use either "EDITOR" or "VISUAL" (which is a new one to me) it might be best to set
export SUDO_EDITOR=nano
in ~./bashrc
specifically for sudoedit. At least that's what I'm going to do. Or, better yet, set it to mc. That way I have both file management and editing capabilities.

[wizard10000]

...So, I suspect that in order to avoid confusion with other programs that may use either "EDITOR" or "VISUAL" (which is a new one to me) it might be best to set
export SUDO_EDITOR=nano
in ~./bashrc
specifically for sudoedit. At least that's what I'm going to do. Or, better yet, set it to mc. That way I have both file management and editing capabilities.

Makes sense to me. I haven't received the new security "feature" in Sid yet but it appears collectively we're pretty well prepared for it

[Rog131]

ok ,,,so I got upgraded to kate-17.03.90 today ,,,,,,,,,,no more using Kate with sudo to edit root files ;(

sudoedit gives a vi terminal ,,,,,,,,,,,,,guess I must learn vi ?

VINNY

You could launch the kate with the sudoedit - earlier:

- https://www.kubuntuforums.net/showth...l=1#post397654
- https://www.kubuntuforums.net/showth...l=1#post397659

As a KDE Service Menu: https://www.kubuntuforums.net/showth...156#post399156