Is this a bug? computer-janitor error:dbus

Asked by David M on 2011-04-01

Was about to make first bug report and it said that I should ask.
Here's the terminal output if I try manually:

dave@TQCi7:~$ computer-janitor find
ERROR:dbus.proxies:Introspect error on :1.68:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.87" (uid=1000 pid=5628 comm="/usr/bin/python) interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination=":1.68" (uid=0 pid=2686 comm="/usr/bin/python))
dave@TQCi7:~$

If I try using the gtk version I get:

/usr/share/computerjanitor/computerjanitorapp/gtk/ui.py:94: GtkWarning: Could not load image 'computerjanitor-24x24.png': Failed to open file '/usr/share/computer-janitor/computerjanitor-24x24.png': No such file or directory
  builder.add_from_file(glade_file)
ERROR:dbus.proxies:Introspect error on :1.68:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.88" (uid=1000 pid=5905 comm="/usr/bin/python) interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination=":1.68" (uid=0 pid=2686 comm="/usr/bin/python))

I couldn't find a solution, maybe I just suck...IDK...All I know right now is that it doesn't seem to be working :(
Help?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu computer-janitor Edit question
Assignee:
No assignee Edit question
Solved by:
Eliah Kagan
Solved:
2011-04-01
Last query:
2011-04-01
Last reply:
2011-04-01

This looks like bug 715707. Assuming that you agree it's that bug and not a new bug, you should indicate that you're affected by that bug (using the green "This bug affects ..." link near the top of the bug 715707 page), perhaps also subscribe to the bug (this is usually a good idea), and provide any additional information that you have which is currently missing. In particular, you should mention what Ubuntu release you're running, since if it's Maverick or Natty, you will have confirmed that the bug occurs in that release (so far it's one person with Maverick and one with Natty), and if it's something else, you will have provided information to the effect that the bug affect some third release that it is thus-far not documented to affect. If you don't know what Ubuntu release you're running, you can get that information by going to Help > About Ubuntu or by running the command "lsb_release -rd" (without the quotes) in the Terminal.

David M (theohcat) said : #2

Thanks I'm going to add the info in a comment. I don't know how I missed that one.

David M (theohcat) said : #3

Thanks Eliah Kagan, that solved my question.