Bug 106642 - The user account was saved by the application..no way to clear that user
Summary: The user account was saved by the application..no way to clear that user
Status: CLOSED WORKSFORME
Alias: None
Product: kdeprint
Classification: Unmaintained
Component: kjobviewer (show other bugs)
Version: 0.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-01 23:45 UTC by James Porter
Modified: 2008-12-31 18:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Porter 2005-06-01 23:45:19 UTC
Version:           0.1 (using KDE 3.3.2%2C%2520Gentoo)
Compiler:          gcc%2520version%25203.3.5-20050130%2520%28Gentoo%2520Linux%25203.3.5.20050130-r1%2C%2520ssp-3.3.5.20050130-1%2C%2520pie-8.7.7.1%29
OS:                Linux%2520%28i686%29%2520release%25202.6.5-gentoo-r1

I used the user's unix password when the authorization box came up..I did not know her wallet password so I canceled the wallet. Her account does not have permissions to cancel a cups print job..I can't find how to let it let me log in as a privileged user. It will always try to do all tasks as her user account and fails without asking me for a privileged user account.
Comment 1 Michael Goffioul 2005-06-02 09:31:10 UTC
Try to change the username in the CUPS section of "kaddprinterwizard --kdeconfig". Or you can try to concel the job from the web interface http://localhost:631

Michael.
Comment 2 Cristian Tibirna 2005-09-27 07:38:34 UTC
I don't know if it's a bug the fact that the interface that is intended to end-users doesn't ask for priviledged rights.

Did you try what comment #1 suggests?
Comment 3 James Porter 2005-09-27 07:51:57 UTC
It was just the fact that it would ask for a username, fail because
the given username was not root. Then there was no way to change which
username to use, it would only fail if the password was wrong. It
would check that the user exsisted and password matched, it did not
check to see if it had proper permissions with cups.

Jim

On 27 Sep 2005 05:38:35 -0000, Cristian Tibirna <tibirna@kde.org> wrote:
[bugs.kde.org quoted mail]
Comment 4 Cristian Tibirna 2005-09-27 08:36:27 UTC
Now this is clearer. For a start, I believe that the problem comes more from the configuration of your printing server than from kdeprint system. I will keep this report open until I get a chance to look more closely.
Comment 5 Michael Goffioul 2005-09-27 08:45:02 UTC
Just a few words about how it works. Kdeprint registers an authentication callback to CUPS, such that when CUPS needs an authentication, a nice KDE dialog is shown. This means that it is CUPS that determines if it requires authentication or not, not kdeprint.

Michael.
Comment 6 James Porter 2005-09-27 18:04:40 UTC
So maybe we need to send a bug upstream so that CUPS auth mechanism
can tell what permissions the specific user. It is a pain in the but
to be able to print, but not be able to delete, pause, etc print jobs.
I had to do everything with the web interface as root, but that is not
acceptable for a user to have to do that (grandmothers machine).

On 27 Sep 2005 06:45:04 -0000, Michael Goffioul <kdeprint_bugs@swing.be> wrote:
[bugs.kde.org quoted mail]
Comment 7 Michael Goffioul 2005-09-28 11:32:25 UTC
In this case, it would be interesting to have a look at the CUPS configuration for the various resources involved ("/", "/printers", "/jobs")
Comment 8 Kurt Pfeifle 2007-01-13 07:52:55 UTC
Timeout for this bug...
Comment 9 John Layt 2008-12-31 18:37:05 UTC
Closing old Resolved status bug.