Version: revision 958058 (using Devel) Installed from: Compiled sources Steps to reproduce: 1. Login to kde4 installation using normal user. 2. Open dolphin in super user mode entering root password. 3. Try to open any file by clicking it(I have single click to open files). Expected result: File should be opened using respective information. Actual result: File not opened. More information: When I try to open text file, it show error "KDEInit could not launch '/usr/bin/kwrite'." My kde installation is in /home/kde-devel/kde4
Same problem here. I use "kdesu dbus-launch dolphin" through "Link to application" but cannot open most files (images, text, etc) and consequently cannot preview anything, which I would like to have. To have not to logon in a determined user or use bash shell to do some root tasks, I (would like to) use dolphin as super user privileges for it. I remember in KDE3 I could use it. I'm using KDE 4.3 RC2 (downloading right now RC3), Kubuntu amd64 OS.
Doesn't it seem like a blocker for 4.3.0?
(In reply to comment #2) > Doesn't it seem like a blocker for 4.3.0? Like a blocker? What you mean?
Blocker means stopping 4.3.0 to be released :)
I'm on 4.4 beta1 now and I can reproduce it.
*** Bug 217858 has been marked as a duplicate of this bug. ***
I am on KDE 4.3.4 openSUSE 11.2. I can confirm the bug.
By the way, there are one related bug report: 185089
*** Bug 199650 has been marked as a duplicate of this bug. ***
*** Bug 229051 has been marked as a duplicate of this bug. ***
*** Bug 185089 has been marked as a duplicate of this bug. ***
*** Bug 232311 has been marked as a duplicate of this bug. ***
Additional information from the reporter of bug 232311 (I don't know if that is really the problem though): > So i debug it and here is the problem: > > (gdb) dolphin(28076)/kdeui (KNotification) KNotification::slotReceivedIdError: > Error while contacting notify daemon "Message did not receive a reply (timeout > by message bus)"
Wilson_Phillips gives a simple solution to this problem here: http://forums.opensuse.org/applications/434206-cannot-open-files-dolphin-superuser.html#post2129001 I can confirm that a file such as this: [code] #!/bin/bash # Allows root to open windows on your display. Example: KWrite and Kate xhost +local:0 [/code] when made executable and placed in the user's ~/.kde4/Autostart directory, fixes the problem cited in this bug, plus that of any other program launching with root's permission. Is there any problem with this script? For such a long-standing KDE problem, it seems strange that this has not been tried before in KDE. Can this function be embedded in KDE startup, rather than being put in a users Autostart directory? If not, can KDE make such a file part of the standard distribution? Are there any reasons that this method should *not* be used?
In case geoff's script is ok, it would be cool to have a checkbox somewhere in KDE configuration or Dolphin's like "Allow launching applications as root from Dolphin", or similar. I mean, a friendly way to get this working.
Thats a per distro problem, that should be resolved by msec, in mandriva we have /etc/X11/xinit.d/msec in wich sets INET localhost access, So i have created the file /etc/X11/xinit.d/xhost_local wich haves: /usr/bin/xhost local: This way the problem remains fixed until the distro handles it in next release.
That's excellent information Zé. In openSUSE 11.2, the equivalent location is /etc/X11/xinit/xinitrc.d/. Transferring the above script from a user's Autostart directory to that directory (and making it root-owned, with permissions 755) also fixes this bug. This makes it more appropriate for the distros to fix, as it seems that their X environment needs better preparation, rather than getting KDE to fix it. I'm going to suggest that to openSUSE Bugzilla (#450203).
*** Bug 236184 has been marked as a duplicate of this bug. ***
I am not sure though that files opened from the administrator mode should be opened by applications running as root. I need to know which window is root’s and which is mine, otherwise it is too easy to make a mistake. File in administrator mode is OK; but I do not see a compelling reason to start e.g. image viewer as root.
I am not sure though that files opened from the administrator mode should be opened by applications running as root. I need to know which window is root’s and which is mine, otherwise it is too easy to make a mistake. File manager in administrator mode is OK; but I do not see a compelling reason to start e.g. image viewer as root.
> I need to know which window is root’s and which is mine, otherwise it is too easy to make a mistake. Just by the way: It's easy to give the root windows another color theme or even other icons. I wonder why that'S not the default. Could avoid a lot of mistakes I guess. It really is helpful to open a file in a text editor from root filemanager. Or something like kompare. That should be possible in an easy way. I agree, no need for a picture viewer in root mode.
This has been fixed in openSUSE. See from Comment #31 onwards: [url]https://bugzilla.novell.com/show_bug.cgi?id=450203[/url]
*** Bug 278614 has been marked as a duplicate of this bug. ***
All works ok for me in Kubuntu 11.10, using KDE 4.8.0 with Dolphin 2.0. I think that this bug should be marked as fixed if other distros using same KDE version don't have the problem.
Resetting assignee to default as per bug #305719
Thanks for the feedback, I'll close this report then (DOWNSTREAM because it seems to be a distro issue).