[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 179289] New: Improve dolphin behaviour in situations when user
From:       Diego <panda84 () inwind ! it>
Date:       2009-01-01 15:25:13
Message-ID: bug-179289-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

http://bugs.kde.org/show_bug.cgi?id=179289

           Summary: Improve dolphin behaviour in situations when user
                    "doesn't have enough permission".
           Product: dolphin
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: peter.penz@gmx.at
        ReportedBy: panda84@inwind.it


Version:           1.1.80 (using 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2)),
4.1.85-6.fc10 Fedora)
Compiler:          gcc
OS:                Linux (i686) release 2.6.27.9-163.fc10.i686

The basic idea is the same of this bug:
https://bugs.kde.org/show_bug.cgi?id=141604
but with some updates (e.g. use PolicyKit instead of sudo).

A similar idea (analogous considerations) for the save dialog is described
here:
https://bugs.kde.org/show_bug.cgi?id=178590
Maybe it is possible to (eventually) share some code...

The problem:
"You don't have enough permission" confuses a lot non technical users.

Example:
Suppose your new foo device requires x.y version of the bar firmware. You found
in the internet or somewhere else that you have to download the firmware file
and you have to copy it to /lib/firmware. So you:
- download the firmware;
- open Dolphin;
- split view in two;
- open in the left side the directory where you downloaded the firmware and in
the right side /lib/firmware;
- drag and drop the firmware to the desired directory;
- get a laconinc windows telling "Permission denied. You cannot write to
/lib/firmware".

Currently the only solution is running Dolphin as root (it is bad to run a
whole application as root only to perform a single specific action) or to copy
the file from the command line using su or sudo.


Proposal:
A possible intutive solution could be:
- check if the user running the GUI can perform the desired action;
- if he can then perform it;
- if he can't then open another dialog asking if he wants to abort the action
or he wants to be asked for password to perform the action as privileged user;
- if the user chooses to be asked for password then do the things needed to
actually perform the action (PolicyKit-KDE?).


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]