Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: KDE4 root problems

  1. #1
    Jon_Freeman NNTP User

    Default KDE4 root problems

    I'd noticed some of this before on 11.1 with KD4 versions but until now, I've had KDE3 options so it hasn't bothered me:

    If (I know some may not approve but it's there and the way I like to work) If I open Dolphin in SuperUser mode, I can not open a file using KWrite or Kate. , eg. Open with KWrite will give "KDEInit could not launch /usr/bin/kwrite"

    If I su in a terminal and try to use KWrite or Kate, I get the error messages: "Communication error with launcher. Exiting!". The programs do open though but I can't open files using the menu. If I try, I get a popup window saying "Could not start process. Cannot talk to klauncher. Not connected to D-Bus server."

    Any ideas how to resolve this?

  2. #2
    Join Date
    Jun 2008
    Location
    Finland, European Union
    Posts
    1,879

    Default Re: KDE4 root problems

    Use kdesu to launch kwrite instead of su.

  3. #3
    Jon_Freeman NNTP User

    Default Re: KDE4 root problems

    Thanks. That has solved the second part.

    How do I open a file using KWrite from Dolphin

    I've tried changing dbus-launch dolphin %i -caption "%c" "%u" to kdesu dolphin in the KDE Menu but that doesn't help.

  4. #4
    Jon_Freeman NNTP User

    Default Re: KDE4 root problems

    Done some more searching. Seems xhost + will make Dolphin work as I want in Super User mode.

  5. #5
    Join Date
    Jun 2008
    Location
    Finland, European Union
    Posts
    1,879

    Default Re: KDE4 root problems

    And allow everyone to connect to your X sesssion.

  6. #6
    Jon_Freeman NNTP User

    Default Re: KDE4 root problems

    How was it before on KDE3 and Konqueror in SuperUser mode? Did the default settings allow that then?

    Anyway, for the length of a likely root Dolphin session, I prefer the convenience to what be a very slight risk if someone hacked the PC, I'm suppose. Can't say I'm bothered about parents on the LAN doing it.

  7. #7

    Default Re: KDE4 root problems

    Actually this is a "feature" of KDE, locking out root access to practically all apps that can alter root files such as kwrite.
    This is why I often install Gedit or another text edtor on the side
    https://features.opensuse.org/308357

  8. #8
    Join Date
    Jul 2008
    Location
    Athens
    Posts
    275

    Default Re: KDE4 root problems

    How do we bypass that? It is really stupid, since you have to enter root password to edit files! Remember, we start File Manager in SU mode!

  9. #9
    Join Date
    Jun 2008
    Location
    Florida, USA
    Posts
    970

    Default Re: KDE4 root problems

    I sort of agree with tpe, but also understand the need/desire for integrity of the security architecture.

    Is there a way to get Dolphin(in root mode) to open files in "Read-Only" mode, such as the "Preview in embedded text editor" that was in Konquerer-KDE3?
    I find I use file manager-super user a lot when tracking down problems. Frequently need to be able to look everywhere (root privileges) but really only want to read-only.

    Switching out to a console for a true edit session, when needed, would be a necessary but workable solution.

  10. #10

    Default Re: KDE4 root problems

    Quote Originally Posted by Jon_Freeman View Post
    How was it before on KDE3 and Konqueror in SuperUser mode? Did the default settings allow that then?

    Anyway, for the length of a likely root Dolphin session, I prefer the convenience to what be a very slight risk if someone hacked the PC, I'm suppose. Can't say I'm bothered about parents on the LAN doing it.
    You can use konqueror in super user mode to open a file with kwrite as a substitute for dolphin.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •