automated updates do not run

[Paul Hubert]

Binary package hint: ubuntu-docs

I upgraded from 64 bit Ubuntu 10.4 to 10.10.

Following the upgrade, the "Install updates" function in Update Manager no longer worked.

I REMOVED Update Manager and then downloaded and reinstalled it, via Synaptic to no avail.

Similarly, the update under PlayOnLinux does not function.

In addition, I now have outstanding updates identified in Update Manager that are being "kept back"

I used:

sudo apt-get update && sudo apt-get upgrade

With this result:

The following packages have been kept back:
  linux-generic linux-headers-generic linux-image-generic
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

I see no other error messages.

[Paul Hubert (phubertgm)]

I am running Ubuntu on a Dell Optiplex 360 with an Nvidia dual-head card and 4GB RAM.

[Paul Hubert (phubertgm)]

Just found out that Computer Janitor is also non-functional.

As with Update Manager, I removed completely and then reinstalled. No dice.

I am unable to Unselect All or to run the cleanup.

It THINKS I have something like Synaptic running (which I didn't) ... ran right after boot and killed Update Notifier.

So, is my 10.10 upgrade simply screwed?

[Paul Hubert (phubertgm)]

Do I need to convert this to a question (just saw the link on the page)?????

[manny (estelar57)]

"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!

[Paul Hubert (phubertgm)]

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"

[Robert Roth (evfool)]

The crash from the last comment I think belongs to a separate computer-janitor bug. The root cause might be the same, but all applications should handle extreme situations, they should not display tracebacks, but user-friendly error messages with some concise pointers to some solution for the problem.

[Paul Hubert (phubertgm)]

I AM able to update manually OR through Synaptic. So I have gotten
updates TO update manager. That said, I suspect the bug is NOT an update
manager bug but, as I may have said elsewhere, possibly some switch that
is set when it should not be. But where? AND is it related to the
computer janitor issue I have that 'thinks' I have Synaptic or update
manager running.

Could not update manager's problem, then, be the same root cause???

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"