Gnome-Do crashes on startup after distupgrade from 9.10 to 10.04 beta 1

See attached log of the startup for error details.

I've been having similar problems, running Lucid for the past couple of weeks on my desktop and netbook.

On my desktop, Do will occasionally start and work fine, but more often when launched it will just crash straight away. If I keep launching it, it eventually works but this gets quite irritating.

On my netbook, I was having similar problems, but now it seems to be working okay since a couple of days ago.

Please let me know if I can do anything to help.

Same for me, but my log is slightly different, and the stack-trace seems to mention the RememberTheMilk API - should I file this separately?

It works now after I have removed my existing configuration. I have backed up the old config, should I post it here?

Did you have either the Tasque or RememberTheMilk plugins on? I had both - pretty useless, since I sync my Tasque with RememberTheMilk, but I did.

This is a bad interaction with the new gnome-keyring-sharp. I've got a patch to fix it, I just need to give it a little polish and I'll push it to Ubuntu.

It's true. Happened to me again for the Gmail plugin, because it also uses GNOME's keyring.

I had to manually remove configuration files that GNOME-Do leaves all over the place after purging it with apt.

That sucks. It should truly remove configuration files when purged.

As a temporary for anybody with this problem, purge Do as well as its Plugin and Docklets packages and do a
> find -type d -name gnome-do
on your home directory. Remove any directory found that you haven't created yourself with
> rm -rf path/to/dir

After re-installing Do, make sure not to enable any plug-ins that make use of user names or passwords.

You can also delete the usernames/passwords from your gnome-keyring - install the “seahorse” package and you can view & edit your keyring.

The gnome-do package is forbidden by (my memory of) policy from removing this sort of configuration on purge. Debian packages may not touch user-local configuration.

You are kidding... Really?

But then, if you truly want to wipe out *your* configuration, you are stuck with manually removing files? That's non-sense. If purge doesn't do what it suggest it does, then there should be a MEGAPURGE to actually get the job done.

Geez.

Anyway, thanks!

PS: I thought seahorse was installed by default - at least it was on Karmic, haven't checked on Lucid yet (I'm on a Karmic machine right now).

@Javier: Even if it is off-topic here, but packages really never ever should mess around with user configuration when managed over the system global packaging system. The user's configuration belongs to the user. Just because a system administrator decides to remove a certain package does not mean you want your home directory to be purged, too. Instead the software itself should be robust enough to handle broken configurations.

The purge option is intended to remove the global configuration in /etc, and it does that job well.

@Philipp You are indeed right-o, sir. Hence, my message, which read something like "how does a user then purge his own configuration in order to procure himself a truly fresh install?".

Also, you sound like a sysadmin. This isn't Debian, it's Ubuntu. We are dealing with desktops here, not servers. "The administrator" is likely your dad, or older brother, if anybody. So - how do I get a fresh install *without* knowing my way around a terminal?

This is a question that the people working on the Ubuntu Software Store or whatever it's called should think about.

By the way, I haven't re-added my key-ring dependent plug-ins yet - does "fix released" mean it's already on the repos?

I am experiencing gnome-do crashes that sound similar, attached is my log