Red Hat Bugzilla – Bug 664885
sec policy crashing kde printer-applet
Last modified: 2012-08-16 19:31:26 EDT
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.setup a vnc-server desktop running kde
2.login to desktop
Latest Crash: Mon 20 Dec 2010 09:22:05 PM
Command: python /usr/bin/printer-applet
Reason: connection.py:630:call_blocking:DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.50" is not allowed to own the service "com.redhat.NewPrinterNotification" due to security policies in the configuration file
Comment: have a vnc desktop.
Bug Reports: Status: CLOSED ERRATA
Possibly related bug upstream.
In your case, it's ConsoleKit treating you as a non-local user (which is true), and denying access.
What *should* happen is for the kde printer applet to handle that more gracefully (and probably just quit/exit).
(In reply to comment #2)
> In your case, it's ConsoleKit treating you as a non-local user (which is true),
> and denying access.
That, then, seems to be the underlying problem - a "single user" ideology being applied to what has always been, and always will be, a multi-user system.
> What *should* happen is for the kde printer applet to handle that more
> gracefully (and probably just quit/exit).
I don't see a problem with "NewPrinterNotification" functioning correctly for any user logged into a system.
Re-assigned to ConsoleKit.
ConsoleKit is working as designed.
There are 2 issues here:
1. The interface is locked down at D-Bus level. IMHO it would make more sense to control this through PolicyKit, where it's easier for admins to tweak the ACLs to allow remote access.
2. The kdeutils-printer-applet is throwing an uncaught exception instead of doing something sensible (most likely just not show the applet at all if you're not allowed to print).
I'm also CCing Tim Waugh, the author and maintainer of the system-config-printer core (and the GTK+ interface and applet) on this report.
The system-config-printer-applet program handles this case correctly and simply does not register that D-Bus service.
I had a similar issue, though I use NoMachine server as opposed to VNC.
I solved it by creating a file named 'printer-applet.desktop' in '~/.config/autostart/' and adding the following information.
Another viable option would be to add 'exit()' to the 3rd line of /usr/bin/printer-applet
Almost forgot, my above comment is ok if you don't want to see printer-applet at all, you should still have no issues printing.
This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
This is still current, now tracked under bug #711719 with many duplicates ("thanks" to ABRT).
*** This bug has been marked as a duplicate of bug 711719 ***