Bug 571576 - kde4-printer-applet can't start because of security policies
Summary: kde4-printer-applet can't start because of security policies
Status: RESOLVED DUPLICATE of bug 551958
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: KDE4 Applications (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-18 11:23 UTC by Forgotten User QFh0D9oMPg
Modified: 2010-01-18 12:34 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User QFh0D9oMPg 2010-01-18 11:23:10 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.6) Gecko/20091201 SUSE/3.5.6-1.1.1 Firefox/3.5.6

When trying to start printer-applet from kde4-printer-applet-4.3.90-111.2, the following error occurs:

Traceback (most recent call last):
  File "/usr/bin/printer-applet", line 1161, in <module>
    applet = JobManager()
  File "/usr/bin/printer-applet", line 297, in __init__
    notification = NewPrinterNotification(bus, self)
  File "/usr/bin/printer-applet", line 1050, in __init__
    bus_name = dbus.service.BusName (PDS_OBJ, bus=bus)
  File "/usr/lib/python2.6/site-packages/dbus/service.py", line 129, in __new__
    retval = bus.request_name(name, name_flags)
  File "/usr/lib/python2.6/site-packages/dbus/bus.py", line 306, in request_name
    'su', (name, flags))
  File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 622, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.61" is not allowed to own the service "com.redhat.NewPrinterNotification" due to security policies in the configuration file


Reproducible: Always
Comment 1 Christian Trippe 2010-01-18 12:34:42 UTC
.

*** This bug has been marked as a duplicate of bug 551958 ***