Bug 121671 - kjobviewer denies access for deleteing printerjob
Summary: kjobviewer denies access for deleteing printerjob
Status: CLOSED NOT A BUG
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: 2006-02-09 21:53 UTC by armineasy
Modified: 2008-12-31 19:31 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 armineasy 2006-02-09 21:53:09 UTC
Version:           0.1 (using KDE 3.4.2 Level "b" , SUSE 10.0)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.13-15.7-default

Hallo,

I have installed Linux (SuSE 10.0) with KDE 3.4.2 Level b on a single machine.
Printer is a HP DeskJet 510.

I looked on kde.printing.org for an advice, but so far I have not found a solution.

When I run a printer job I can' t delete any job as normal user, e. g. user armin.
KJobViewer shows a errormessage like: You don't have access to the requested resource.

As root I can delete the jobs sent from root.
Please, can you tell me, how I can get access to delete printer jobs from a user as the user himself. Do I have to set a SUID- or SGID-Bit?

Thank you for your help.

Armin Thiele
Comment 1 Michael Goffioul 2006-02-10 08:55:45 UTC
Access permissions are defined in the CUPS configuration file /etc/cupsd.conf. Look into the CUPS documentation to learn how to define those settings. Alternatively, you can also use the kdeprint CUPS config tool available from the printers control module.

Michael.
Comment 2 Cristian Tibirna 2006-04-07 01:20:13 UTC
This is an issue with CUPS authorization configurations in SuSE-10. Please consider contacting the OpenSuSE-10 developers or the support service at Novell. KDEPrint obeys whatever underlying policy the distribution you use decided to employ.

You might also consider perusing the CUPS admin documentation, as suggested in the previous message.
Comment 3 John Layt 2008-12-31 19:31:31 UTC
Closing old Resolved status bug.