Comment 5 for bug 668951

Thanks for the response, but I'm a bit reluctant to venture into a
complete reinstall.

It doesn't seem as though the problem with update-manager AND
computer-janitor should be difficult.

AND I see from another forum that I'm not the only one experiencing
failure on both of these in 10.10.

Dunno if the other guy had upgraded as well or whether he was on 32 or
64 bit.

When running "computer-janitor clean --all" in terminal, however, I got
the following:

ERROR:dbus.proxies:Introspect error on :1.52:/:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied:
Rejected send message, 1 matched rules; type="method_call",
sender=":1.58" (uid=1000 pid=9547 comm="/usr/bin/python)
interface="org.freedesktop.DBus.Introspectable" member="Introspect"
error name="(unset)" requested_reply=0 destination=":1.52" (uid=0
pid=9127 comm="/usr/bin/python))
ERROR:dbus.connection:Unable to set arguments
(set([dbus.String(u'deb:googleearth-data'),
dbus.String(u'deb:apport-hooks-medibuntu'),
dbus.String(u'deb:google-chrome-beta'),
dbus.String(u'deb:ubuntu-tweak'), dbus.String(u'deb:medibuntu-keyring'),
dbus.String(u'deb:linux-image-2.6.32-25-generic'),
dbus.String(u'file:/etc/grub.d/00_header.dpkg-old'),
dbus.String(u'deb:googleearth')]),) according to signature None: <type
'exceptions.TypeError'>: Don't know how which D-Bus type to use to
encode type "set"
Traceback (most recent call last):
File "/usr/sbin/computer-janitor", line 35, in <module>
main()
File "/usr/share/computerjanitor/computerjanitorapp/cli/main.py", line
312, in main
options.arguments.func(options.arguments)
File "/usr/share/computerjanitor/computerjanitorapp/cli/main.py", line
293, in clean
timeout=3600)
File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 132, in __call__
**keywords)
File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 556, in
call_async
message.append(signature=signature, *args)
TypeError: Don't know how which D-Bus type to use to encode type "set"

On 11/20/2010 12:45 PM, manny wrote:
> "Do I need to convert this to a question (just saw the link on the
> page)?"
>
> Nah, no need for that.
>
> Thanks for taking the time to make a nice detailed report. We need as
> much feedback as possible, so this will definitely help.
>
> > From experience, 32bit is little less prone to upgrade bugs, but even if
> its 32 or 64bit , a small portion of users still may experience them.
>
> Usually, small updates patches always fix most of those issues, but in
> your case you're not getting them! This is indeed weird...
>
> At this time the quickest fix, is to reinstall to a separate partition.
>
> In fact upgrading directly is not the default anymore (to avoid stuff
> like this from occurring). Installing using a cd or usb is much more
> "fail-proof".
>
> Note: am not a direct developer or staff member, just a normal volunteer
> around here, because the developers have been extremely busy lately
> stomping on some of the older, bigger bugs and making sure they're not
> left out from the next Ubuntu release in april.
>
> Hope to have been of some help!
>
> Cheers!
>

--

"Isa - Jesus - Y'shua : *TRUST*Him"